Notifications in Chrome are a useful feature to keep up with updates from your favorite sites. However, we know that some notifications may be spammy or even deceptive. We’ve received reports of notifications diverting you to download suspicious software, tricking you into sharing personal information or asking you to make purchases on potentially fraudulent online store fronts.

To defend against these threats, Chrome is launching warnings of unwanted notifications on Android. This new feature uses on-device machine learning to detect and warn you about potentially deceptive or spammy notifications, giving you an extra level of control over the information displayed on your device.

When a notification is flagged by Chrome, you’ll see the name of the site sending the notification, a message warning that the contents of the notification are potentially deceptive or spammy, and the option to either unsubscribe from the site or see the flagged content..

TL;DR

• Android’s long-awaited Battery Health menu has arrived in Android 16 Beta 3, but only for the Pixel 9 series and the Pixel 8a.
• Google has confirmed that older Pixels, including the not-so-old Pixel 8 and Pixel 8 Pro, will not receive this feature.
• The decision is due to unspecified “product limitations,” leaving aging device users without means for native battery diagnostics.

The zero-day, tracked as CVE-2025-27363, resides in the System component and stems from a memory handling bug in FreeType — an open-source library widely used for font rendering. The flaw allows for local code execution without requiring additional privileges or user interaction. According to Facebook’s security team, which first disclosed details about the vulnerability in March 2025, attackers can exploit the issue through malformed TrueType GX or variable font files, leading to heap buffer overflows and potentially arbitrary code execution. While the vulnerability was fixed in FreeType 2.13.0 over two years ago, older versions remain embedded in many Android builds and third-party software, making the risk of exploitation significant.

Google has acknowledged signs of limited, targeted exploitation of CVE-2025-27363 in the wild, reinforcing the urgency for users and OEMs to apply the update. Devices patched with the 2025-05-05 security level will receive a fix for this vulnerability, along with all other patches from earlier levels.

Beyond the zero-day, the May 2025 bulletin addresses over 40 high-severity vulnerabilities affecting Android components such as the Framework, System, kernel, and key third-party hardware modules from Arm, MediaTek, Qualcomm, and Imagination Technologies.

Android device manufacturers are expected to incorporate these fixes into their firmware. Devices running Android 10 and later will receive some of these patches through Google Play system updates, covering components like the Wi-Fi stack, Permission Controller, and Documents UI. However, it is recommended that users of older models move to a newer device running Android version 13 or later. For some models, third-party Android distributions like GrapheneOS and LineageOS exist, which might provide security in aging devices.

Summary

• Google Messages is rolling out an Unsubscribe button to combat spam.
• Pressing the button sends a 'STOP' message from the user to the sender, blocking non-essential texts.
• The Unsubscribe button is available for RCS for business messages and texts from short codes.

I do not know the reason for this. But, Voyager minimizes once a while like my keyboard is on when its not. I use Futo keyboard and have experienced this bug for a long time across voyager versions. My android version is 15 but I also used to experience this in android 14.

At the time of the screenshot I was using Niagara launcher which could perhaps be related.

Voyager should be able to cache posts & comments offline. Also, have the ability to save state even if android reclaims memory from the app.

Hope this is not imposing. Voyager is a neat app but can use some refinements.

I'm on android v2.30.0 native app.

So, recently I read an article stating that apps can still access installed apps on your phone as long as they list the apps in their manifest or use intent based hacks. Unfortunately, the app I use to restrict permissions (App OPS) does not have any measure against this.

Is there anything that can be done from adb, etc to restrict an app's ability to view other apps?

The article in question, it talks about indian apps but the info it shared should apply globally: https://peabee.substack.com/p/everyone-knows-what-apps-you-use

Pros

• Lightweight, grippy and durable build with IP68/69 and MIL-STD-810H certifications.
• Bright OLED panel with HDR10+ support.
• Very loud and nice-sounding speakers.
• Solid camera performance.
• Dependable battery life, fast charging.
• Hard-to-find connectivity features (SmartConnect), microSD card slot.

Cons

• The chipset could be more powerful for the price.
• Camera app can be laggy and unresponsive at times.
• Ultrawide camera has focus-hunting issues during video recording.
• No charger in the box (in some markets).

I downloaded and successfully setup buzzkill. Then a day or two later found FilterBox. It was created at the same time as buzzkill but has AI spam filtering – I'm guessing a traditional algorithm for spam filtering used in emails and not an an actual LLM.

So, why is it not recommended more instead of buzzkill.

Tap for spoiler

On ~~reddit~~..

It also has a nice UI and supports analytics for your notifications history. Also has double the downloads of buzzkill. Although, buzzkill has a simple UI.

The algorithm spam filtering which is based on your recommendation is neat. Especially, since you do not need to manually create rules for each and every spam message/notification across messaging apps.

What are your thoughts?

Since I just paid for buzzkill and did a thorough setup I hesitate to jump ship. But, spam filtering is enticing. For those 10-20% of use cases which cannot be filtered by regular rules unless you keep on adding more.

cross-posted from: https://reddthat.com/post/37812176

The sync developer has been MIA for a long time (1 year or longer) and I fear it will stop working sooner or later when Lemmy instances start updating to v1.0 in future.

I use Sync because it has a nice Material you theme, is smooth, supports caching posts & media offline (also keeps the comments, posts loaded even if android reclaims memory from the app)

I can open posts, comments, and even communities in a seperate window if I choose to do so.

Anything with multi window support out there yet? I used voyager for posting. But, want sync like multi window capabilities.

The sync developer has been MIA for a long time (1 year or longer) and I fear it will stop working sooner or later when Lemmy instances start updating to v1.0 in future.

I use Sync because it has a nice Material you theme, is smooth, supports caching posts & media offline (also keeps the comments, posts loaded even if android reclaims memory from the app)

I can open posts, comments, and even communities in a seperate window if I choose to do so.

Anything with multi window support out there yet? I used voyager for posting. But, want sync like multi window capabilities.

TL;DR

• Google is working on a change to Android’s early boot process that improves how quickly kernel modules are loaded.
• This change has resulted in a 30% reduction in loading time for the Pixel 10, according to a Google engineer.
• As a result of this change, the Pixel 10 and other Android devices should boot up slightly faster, though it’s unclear how much of a difference it’ll make.