101
44
submitted 4 weeks ago by neme@lemm.ee to c/android@lemdro.id
102
30
submitted 4 weeks ago by neme@lemm.ee to c/android@lemdro.id
103
168
submitted 1 month ago by sabreW4K3@lazysoci.al to c/android@lemdro.id
104
9
submitted 1 month ago by baatliwala@lemmy.world to c/android@lemdro.id
105
43
Sony Xperia 1 VII review (www.gsmarena.com)
submitted 1 month ago by Matt@lemdro.id to c/android@lemdro.id
106
35
submitted 1 month ago by schizoidman@lemm.ee to c/android@lemdro.id
107
29
submitted 1 month ago* (last edited 1 month ago) by Pro@programming.dev to c/android@lemdro.id
108
20
submitted 1 month ago by limerod@reddthat.com to c/android@lemdro.id

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..

109
60
submitted 1 month ago by cm0002@lemmy.world to c/android@lemdro.id
110
46
submitted 1 month ago by Pro@programming.dev to c/android@lemdro.id
111
26
112
42
submitted 1 month ago by cm0002@lemmy.world to c/android@lemdro.id
113
85
submitted 1 month ago by baatliwala@lemmy.world to c/android@lemdro.id
114
50
submitted 1 month ago by Blaze@lemm.ee to c/android@lemdro.id
115
12
submitted 1 month ago by Blaze@lemm.ee to c/android@lemdro.id
116
86
submitted 1 month ago by limerod@reddthat.com to c/android@lemdro.id

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.
117
78
submitted 1 month ago by schizoidman@lemm.ee to c/android@lemdro.id
118
123
submitted 1 month ago by cm0002@lemmy.world to c/android@lemdro.id
119
37
submitted 1 month ago by cm0002@lemmy.world to c/android@lemdro.id
120
15
submitted 1 month ago by limerod@reddthat.com to c/android@lemdro.id

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.

121
11
122
4
submitted 1 month ago* (last edited 1 month ago) by Pro@programming.dev to c/android@lemdro.id
123
7
  • Google is working on an Intrusion Detection system for Android, according to a teardown of the Play Services app.
  • The system will collect a log of your device/network activities that can be accessed if you notice suspicious activity across your account or devices.
  • Google’s code suggests this log is end-to-end encrypted and can only be accessed with your Google account password and device authentication.
124
9
submitted 1 month ago by neme@lemm.ee to c/android@lemdro.id
125
26
submitted 1 month ago by neme@lemm.ee to c/android@lemdro.id
view more: ‹ prev next ›

Android

19392 readers
391 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

🔗Universal Link: !android@lemdro.id


💡Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

💬Matrix Chat

💬Telegram channels / chats

📰Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 2 years ago
MODERATORS