# android-permissions

Android permissions control an app's access to restricted data and actions, including install-time, runtime, and special permissions.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Italy fines Meta EUR 805 million over a Facebook feature that scanned Android camera rolls

DevFeed: [Italy fines Meta EUR 805 million over a Facebook feature that scanned Android camera rolls](<https://devfeed.tech/articles/italy-fines-meta-805-million-over-a-facebook-feature-that-scanned-android-camera-rolls-136070.md>)

Original publisher: [Read original article](<https://www.techspot.com/news/114565-italy-fines-meta-805-million-over-facebook-feature.html>)

Author: Alfonso Maruccia

Published: 2026-11-16T18:28:00Z

Content type: news

Language: en

Sources: [TechSpot](<https://devfeed.tech/sources/techspot.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [camera](<https://devfeed.tech/tags/camera.md>), [facebook](<https://devfeed.tech/tags/facebook.md>), [feature](<https://devfeed.tech/tags/feature.md>), [fine](<https://devfeed.tech/tags/fine.md>), [fines](<https://devfeed.tech/tags/fines.md>), [italy](<https://devfeed.tech/tags/italy.md>), [meta](<https://devfeed.tech/tags/meta.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [security](<https://devfeed.tech/tags/security.md>), [social](<https://devfeed.tech/tags/social.md>)

### AI overview

Italy's Garante Privacy fined Meta EUR 805 million over Facebook's Android "Get camera roll suggestions" feature, which the regulator said accessed photos and videos without adequate permission. The feature was enabled by default, relied on a single app-wide permission and used an unclear privacy notice; the authority found this unlawful under Italy's privacy code. It estimated about 20 million Italian Android users were affected, with the issue continuing for users who had not updated the app. Meta must disable the feature within 60 days and request new permission even from users who previously granted access. The regulator said Meta's limited cooperation contributed to the penalty. Meta called the fine disproportionate and said it will appeal.

### Source excerpt

The Italian Data Protection Authority (GPDP) recently announced a new, massive fine against Meta. According to the announcement, the social network giant accessed photos and videos of millions of Italian Android users without asking for proper permission first. Meta has been ordered to comply within two months, or face an... Read Entire Article

## Italy Fines Meta EUR 805m Over Accessing Android Users' Photos with Facebook App

DevFeed: [Italy Fines Meta EUR 805m Over Accessing Android Users' Photos with Facebook App](<https://devfeed.tech/articles/italy-fines-meta-805m-over-accessing-android-users-photos-with-facebook-app-134283.md>)

Original publisher: [Read original article](<https://tech.slashdot.org/story/26/11/15/0823213/italy-fines-meta-805m-over-accessing-android-users-photos-with-facebook-app>)

Author: EditorDavid

Published: 2026-11-15T08:34:00Z

Content type: news

Language: en

Sources: [Slashdot](<https://devfeed.tech/sources/slashdot.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Android](<https://devfeed.tech/topics/android.md>), [Image](<https://devfeed.tech/topics/image.md>)

Tags: [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [authorization](<https://devfeed.tech/tags/authorization.md>), [based](<https://devfeed.tech/tags/based.md>), [bbc](<https://devfeed.tech/tags/bbc.md>), [consent](<https://devfeed.tech/tags/consent.md>), [covering](<https://devfeed.tech/tags/covering.md>), [days](<https://devfeed.tech/tags/days.md>), [disclosure](<https://devfeed.tech/tags/disclosure.md>), [facebook](<https://devfeed.tech/tags/facebook.md>), [feature](<https://devfeed.tech/tags/feature.md>), [fine](<https://devfeed.tech/tags/fine.md>), [italy](<https://devfeed.tech/tags/italy.md>), [meta](<https://devfeed.tech/tags/meta.md>), [photos](<https://devfeed.tech/tags/photos.md>), [users](<https://devfeed.tech/tags/users.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

Italy fined Meta EUR 805 million over Facebook's use of Android users' gallery photos and videos to suggest post ideas. Investigators said the feature was enabled by default and that one gallery permission covered app functions with different purposes; the preceding notice did not clearly explain that gallery content could be used for suggestions. Italy's authority ordered Meta to disable the feature within 60 days and obtain separate consent. It cited the number of people affected, continued operation for some users, and Meta's lack of cooperation. Meta said it planned to appeal.

### Source excerpt

The Associated Press reports: Italy announced an EUR 805 million ($887 million) fine against Meta on Saturday for using photos and videos from Android users' galleries on Facebook without specific consent or adequate disclosure... Investigators found that the feature was enabled by default and that Facebook requested gallery access through a single permission covering multiple app functions with different purposes. The authority gave Meta 60 days to disable the feature and seek separate consent for its use. Italy has about 20 million Android users, notes the BBC, and this fine "is among the largest an Italian authority has ever imposed on a tech giant." The charge is related to a feature which suggests photos and videos from a user's phone gallery as ideas for posts... According to the Italian regulator, a preceding [authorization] notice did not make clear that this would also allow Facebook to generate suggestions based on photos in their gallery. The regulator said it took into account "the high number of people affected" and the fact it is "still ongoing for those who have not updated the app and for those who have already given their consent to the system". It also cited "Meta's lack of co-operation". "A Meta spokesperson told the BBC that it planned to appeal..." Read more of this story at Slashdot.

## Meta Fined EUR 805 Million by Italian Regulator Over 'Blanket Permission' for Photo Access; Granularity of Consent at Issue

DevFeed: [Meta Fined EUR 805 Million by Italian Regulator Over 'Blanket Permission' for Photo Access; Granularity of Consent at Issue](<https://devfeed.tech/articles/meta-fined-805-million-by-italian-regulator-over-blanket-permission-for-photo-access-granularity-of-consent-at-issue-134225.md>)

Original publisher: [Read original article](<https://joho-todai.com/en/meta-italy-fine-photo-access-consent/>)

Author: Toru Misaki

Published: 2026-11-15T04:08:07Z

Content type: news

Language: en

Sources: [Joho no Todai](<https://devfeed.tech/sources/joho-no-todai.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [permission](<https://devfeed.tech/topics/permission.md>)

Tags: [ai-training](<https://devfeed.tech/tags/ai-training.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [consent](<https://devfeed.tech/tags/consent.md>), [data-protection](<https://devfeed.tech/tags/data-protection.md>), [facebook](<https://devfeed.tech/tags/facebook.md>), [italy](<https://devfeed.tech/tags/italy.md>), [meta](<https://devfeed.tech/tags/meta.md>), [meta-fined-805-million](<https://devfeed.tech/tags/meta-fined-805-million.md>), [permission](<https://devfeed.tech/tags/permission.md>), [photo](<https://devfeed.tech/tags/photo.md>)

### AI overview

Italy's data protection authority fined Meta EUR 805 million over Facebook's Android photo-suggestion feature. It found that one broad device permission, described only as enabling "other features," did not clearly inform users that their gallery would be used to suggest posts; the feature was on by default, and gallery access could extend to the full archive. The authority applied Italy's ePrivacy rules, which require freely given, informed consent for access to device information, and rejected Meta's argument that Ireland had jurisdiction because the GDPR's one-stop-shop system does not apply to this issue. It ordered separate explicit consent, default-off operation (including for existing users), and clear instructions within 60 days. Meta called the fine disproportionate and said it would appeal. The proceeding did not examine photo use for AI training; the authority reserved review of a separate cloud-processing feature.

### Source excerpt

Italy's data protection authority fined Meta EUR 805 million. It found that the Facebook app obtained access to photos on users' devices through a single blanket permission without securing separate consent for each purpose.

## Meta Fined $887 Million in Italy Over Android Gallery Photos and Videos on Facebook

DevFeed: [Meta Fined $887 Million in Italy Over Android Gallery Photos and Videos on Facebook](<https://devfeed.tech/articles/meta-fined-887-million-in-italy-over-android-gallery-photos-and-videos-on-facebook-134408.md>)

Original publisher: [Read original article](<https://www.securityweek.com/meta-fined-887-million-in-italy-over-android-gallery-photos-and-videos-on-facebook/>)

Author: Associated Press

Published: 2026-11-14T19:00:00Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Android](<https://devfeed.tech/topics/android.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [consent](<https://devfeed.tech/tags/consent.md>), [facebook](<https://devfeed.tech/tags/facebook.md>), [fine](<https://devfeed.tech/tags/fine.md>), [gallery](<https://devfeed.tech/tags/gallery.md>), [italy](<https://devfeed.tech/tags/italy.md>), [meta](<https://devfeed.tech/tags/meta.md>), [photos](<https://devfeed.tech/tags/photos.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [privacy-compliance](<https://devfeed.tech/tags/privacy-compliance.md>), [videos](<https://devfeed.tech/tags/videos.md>)

### AI overview

Italy's Data Protection Authority fined Meta EUR 805 million ($887 million) over Facebook's Android gallery-suggestion feature, finding it accessed photos and videos without specific consent or adequate disclosure. The feature was enabled by default, and gallery access was bundled into one permission covering app functions with different purposes. The authority said Italian law requires free and informed consent for access to a smartphone's private sphere, and ordered Meta to disable the feature within 60 days and obtain separate consent. The fine was imposed on Meta Platforms Ireland Limited, which challenged Italy's jurisdiction; the authority cited Meta's lack of cooperation as a factor in the penalty, about 0.47% of group global turnover.

### Source excerpt

The directive protects smartphones as part of a person's private sphere and requires "free and informed consent" for such access, the authority said. The post Meta Fined $887 Million in Italy Over Android Gallery Photos and Videos on Facebook appeared first on SecurityWeek.

## GhostMap Android flaw lets malicious app trigger persistent boot loop

DevFeed: [GhostMap Android flaw lets malicious app trigger persistent boot loop](<https://devfeed.tech/articles/ghostmap-android-flaw-lets-malicious-app-trigger-persistent-boot-loop-118727.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/ghostmap-android-flaw-lets-malicious-app-trigger-persistent-boot-loop/>)

Author: Bill Toulas

Published: 2026-11-05T09:18:29Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [Android Security](<https://devfeed.tech/topics/android-security.md>), [Android](<https://devfeed.tech/topics/android.md>), [APK](<https://devfeed.tech/topics/apk.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [adb](<https://devfeed.tech/topics/adb.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [android](<https://devfeed.tech/tags/android.md>), [apk](<https://devfeed.tech/tags/apk.md>), [app](<https://devfeed.tech/tags/app.md>), [attack](<https://devfeed.tech/tags/attack.md>), [bitdefender](<https://devfeed.tech/tags/bitdefender.md>), [boot](<https://devfeed.tech/tags/boot.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [continuous](<https://devfeed.tech/tags/continuous.md>), [crash](<https://devfeed.tech/tags/crash.md>), [denial-of-service](<https://devfeed.tech/tags/denial-of-service.md>), [dos](<https://devfeed.tech/tags/dos.md>), [ghostmap](<https://devfeed.tech/tags/ghostmap.md>), [google](<https://devfeed.tech/tags/google.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [reboot-loop](<https://devfeed.tech/tags/reboot-loop.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

GhostMap can make an Android device repeatedly crash after a specially crafted app is installed; the app needs no permissions and does not need to be opened. Bitdefender attributes the flaw to two Android libraries interpreting ZIP compression methods differently, allowing a malformed APK to map a file beyond its contents. When Android's system_server reads that resource, it crashes and restarts, triggering the read again. Bitdefender reproduced the loop on a Pixel 10 running Android 17 with the August 5 security patch; Safe Mode did not stop it. The excerpt says recovery requires a factory reset, which erases local data, or deleting the malformed file through ADB, which depends on debugging already being enabled and acting before another crash. Google reportedly classified the reports as out of scope and not reproducible, while reserving the issue for possible future consideration. Third-party security tools may warn about a threat but cannot block installation.

### Source excerpt

Attackers can force Android devices into a continuous boot loop using a specially crafted app that requires no permissions and only needs to be installed. [...]

## Microsoft Authenticator Flaw Let Permissionless Android Apps Steal Work Account Tokens

DevFeed: [Microsoft Authenticator Flaw Let Permissionless Android Apps Steal Work Account Tokens](<https://devfeed.tech/articles/microsoft-authenticator-flaw-let-permissionless-android-apps-steal-work-account-tokens-102242.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/10/microsoft-authenticator-flaw-let.html>)

Author: The Hacker News

Published: 2026-10-27T12:09:50Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [Android Security](<https://devfeed.tech/topics/android-security.md>), [Android](<https://devfeed.tech/topics/android.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [attack](<https://devfeed.tech/tags/attack.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [broker](<https://devfeed.tech/tags/broker.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [cve](<https://devfeed.tech/tags/cve.md>), [email](<https://devfeed.tech/tags/email.md>), [exploitation](<https://devfeed.tech/tags/exploitation.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [files](<https://devfeed.tech/tags/files.md>), [identity-security](<https://devfeed.tech/tags/identity-security.md>), [malicious](<https://devfeed.tech/tags/malicious.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-authenticator](<https://devfeed.tech/tags/microsoft-authenticator.md>), [microsoft-graph](<https://devfeed.tech/tags/microsoft-graph.md>), [mobile-security](<https://devfeed.tech/tags/mobile-security.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [teams](<https://devfeed.tech/tags/teams.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Microsoft fixed CVE-2026-80097 in Authenticator for Android 6.2606.4246. A permissionless malicious app could launch the exposed AccountChooserActivity, claim to be a trusted Microsoft app such as Teams, and obtain work-account tokens; the signature check verified the installed app's signature but did not verify which app had actually made the request. Enclave's tests found tokens could permit access to email, files, and calendars. Enclave reported no user interaction beyond having a signed-in account, while Microsoft says exploitation requires the user to complete an authentication flow. Microsoft reports no exploitation in attacks. Update to version 6.2606.4246 or later; organizations can enforce that minimum through device management. The sources do not establish whether updating revokes tokens already obtained.

### Source excerpt

Microsoft Authenticator Flaw Let Permissionless Android Apps Steal Work Account Tokens Microsoft has fixed a flaw in its Authenticator app for Android that let a malicious app with no permissions pose as a trusted Microsoft app, such as Teams, and collect sign-in tokens for a victim's w ... Read more Published Date: Oct 27, 2026 (3 hours, 58 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-80097

## Microsoft Authenticator vulnerability let rogue Android apps steal work account access

DevFeed: [Microsoft Authenticator vulnerability let rogue Android apps steal work account access](<https://devfeed.tech/articles/microsoft-authenticator-vulnerability-let-rogue-android-apps-steal-work-account-access-101235.md>)

Original publisher: [Read original article](<https://www.helpnetsecurity.com/2026/10/27/microsoft-authenticator-vulnerability-patchedcve-2026-80097/>)

Author: Mirko Zorz

Published: 2026-10-27T06:14:22Z

Content type: news

Language: en

Sources: [Help Net Security](<https://devfeed.tech/sources/help-net-security.md>)

Topics: [account takeover](<https://devfeed.tech/topics/account-takeover.md>), [Android Security](<https://devfeed.tech/topics/android-security.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [Android](<https://devfeed.tech/topics/android.md>), [Security](<https://devfeed.tech/topics/security.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [Microsoft](<https://devfeed.tech/topics/microsoft.md>), [Microsoft Teams](<https://devfeed.tech/topics/microsoft-teams.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [also](<https://devfeed.tech/tags/also.md>), [android](<https://devfeed.tech/tags/android.md>), [android-apps](<https://devfeed.tech/tags/android-apps.md>), [app](<https://devfeed.tech/tags/app.md>), [apps](<https://devfeed.tech/tags/apps.md>), [broker](<https://devfeed.tech/tags/broker.md>), [don-t-miss](<https://devfeed.tech/tags/don-t-miss.md>), [found](<https://devfeed.tech/tags/found.md>), [here](<https://devfeed.tech/tags/here.md>), [here-s](<https://devfeed.tech/tags/here-s.md>), [heres](<https://devfeed.tech/tags/heres.md>), [let](<https://devfeed.tech/tags/let.md>), [microsoft](<https://devfeed.tech/tags/microsoft.md>), [microsoft-authenticator](<https://devfeed.tech/tags/microsoft-authenticator.md>), [need](<https://devfeed.tech/tags/need.md>), [needs](<https://devfeed.tech/tags/needs.md>), [news](<https://devfeed.tech/tags/news.md>), [outlook](<https://devfeed.tech/tags/outlook.md>), [rogue](<https://devfeed.tech/tags/rogue.md>), [security-update](<https://devfeed.tech/tags/security-update.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [vulnerability-disclosure](<https://devfeed.tech/tags/vulnerability-disclosure.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

Researchers found that Microsoft Authenticator for Android could issue work-account tokens to a malicious app posing as Teams because it trusted request details that any app could read, despite knowing which app was actually calling. A malicious app had to be installed, but the token theft required no permissions, user tap, prompt, or warning. The researchers' test app could access email, files, calendars, SharePoint, and Teams, and impersonating Authenticator could change sign-in methods, including adding a passkey that might preserve access after app removal. Microsoft fixed the flaw in version 6.2606.4246, released September 8, 2026 (CVE-2026-80097; CVSS 8.6). Update to that version or later; organizations can enforce the minimum through MDM. The supplied text also advises caution with sideloaded or unfamiliar apps.

### Source excerpt

If you use Microsoft Authenticator on Android, update it. Researchers at Enclave found a flaw that let any app on your phone quietly take over your work account. The app didn't need permissions, and you didn't need to tap anything. Here's what happened Authenticator does more than show six-digit codes. On Android it also acts as a "broker." When Teams, Outlook or another Microsoft app needs to sign you in, it asks Authenticator, and Authenticator ... More -> The post Microsoft Authenticator vulnerability let rogue Android apps steal work account access appeared first on Help Net Security.

## AI, Meet App: Enable or Disable Android AppFunctions at runtime

DevFeed: [AI, Meet App: Enable or Disable Android AppFunctions at runtime](<https://devfeed.tech/articles/ai-meet-app-enable-or-disable-android-appfunctions-at-runtime-100950.md>)

Original publisher: [Read original article](<https://proandroiddev.com/ai-meet-app-enable-or-disable-android-appfunctions-at-runtime-77e18ca3ec95?source=rss----c72404660798---4>)

Author: Katie Barnett

Published: 2026-10-26T23:30:41Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [annotation](<https://devfeed.tech/tags/annotation.md>), [api](<https://devfeed.tech/tags/api.md>), [consent](<https://devfeed.tech/tags/consent.md>), [feature-toggle](<https://devfeed.tech/tags/feature-toggle.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [llm](<https://devfeed.tech/tags/llm.md>), [october-2026](<https://devfeed.tech/tags/october-2026.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [testing](<https://devfeed.tech/tags/testing.md>)

### AI overview

Android AppFunctions can be disabled by default and enabled selectively when conditions are met, such as user consent, a paid feature, or a feature toggle. Set `isEnabled = false` in `@AppFunctionDeclaration`, then use `AppFunctionManager.setAppFunctionEnabled` with each function's identifier to enable or disable it as needed. The setter is a suspend function and must run in a coroutine; `isAppFunctionEnabled` can check the current state. The article says the API was in private preview with trusted testers as of October 2026, so it was not immediately testable in a production app.

### Source excerpt

Now that you have implemented Android AppFunctions, how to conditionally make them available?What a cool droid. Generated with Gemini Nano Banana. If you haven't yet played around with adding Android AppFunctions to your app, check out my blog post to get started, and get testing! Just note, as of writing this article (October 2026), the AppFunctions API is in a private preview with trusted testers, so you are not able to test it out immediately in a production app -- but get your app ready now! Android AppFunctions are a great idea to enable on device models to interact with your app, but there are several reasons why you may not want them enabled all the time: Require user consent: Before sharing private data with the LLM, you might want to ask the user first, giving them a chance to decide whether to share it and how much to share. Feature toggle: Extra protection can sometimes be good. You can put some or all of your AppFunctions behind a feature toggle and disable them remotely if something goes wrong. Pro feature: If implementing your AppFunction features has been a significant investment in time for you, you may not want to give all users access for free! If you have a pro or paid version of your app, you can enable the functions for them, and disable them for free users. No matter what the reason, there is an easy way to do this! Disabling AppFunctions by default It all goes back to the @AppFunctionDeclaration annotation. We first saw this when writing our AppFunctions (where we had to set isDescribedByKDoc = true to use our KDoc to describe the function). It has another parameter isEnabled. This is true by default, but if we instead set this to false then we can enable and disable the functions at runtime. So as an example: https://medium.com/media/a8e0c7f72f9c19a97061a4f7a0a364c4/href When disabling the functions, we can verify this in the testing app: Note the 'Disabled' label next to each function. Now that we have them disabled, how do we re-enable them

## A more reliable way to add and edit contacts on Android

DevFeed: [A more reliable way to add and edit contacts on Android](<https://devfeed.tech/articles/a-more-reliable-way-to-add-and-edit-contacts-on-android-93139.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/reliable-way-to-add-and-edit-contacts-android>)

Author: Roxanna Aliabadi Walker

Published: 2026-10-21T00:00:00Z

Content type: release

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [apps](<https://devfeed.tech/tags/apps.md>), [permission](<https://devfeed.tech/tags/permission.md>), [product-news](<https://devfeed.tech/tags/product-news.md>), [release](<https://devfeed.tech/tags/release.md>), [target](<https://devfeed.tech/tags/target.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

Apps targeting the upcoming Android release can no longer write contacts directly with `WRITE_CONTACTS`; such writes will fail with a `SecurityException` or permission denial. For user-requested additions or edits, use `ACTION_INSERT`, `ACTION_EDIT`, or `ACTION_INSERT_OR_EDIT`, which open a standardized system editor without write permission. The editor accepts standard contact data types and may ignore custom MIME types. Use the Contact Picker to read contacts a user selects, and move call or messaging actions stored in contacts to People Directory, planned for Android 17 QPR2 (Q4 2026). `MANAGE_CONTACTS` is intended for apps whose core contact-management functionality requires broad access; it is enabled in Special app access, covers reading and modifying contacts, and requires a Google Play declaration. Migration includes finding direct writes, replacing user-driven changes with intents, and removing `WRITE_CONTACTS`. The change applies to apps targeting the upcoming release; the new editor is available to all apps on that OS. The excerpt says there is no intent for deleting contacts.

### Source excerpt

Apps that target the upcoming Android release will no longer be able to directly write to contacts with the WRITE_CONTACTS permission.

## Novel Android RAT 'Hirudo' Replaces Banking Apps With Trojanized Copies

DevFeed: [Novel Android RAT 'Hirudo' Replaces Banking Apps With Trojanized Copies](<https://devfeed.tech/articles/novel-android-rat-hirudo-replaces-banking-apps-with-trojanized-copies-87751.md>)

Original publisher: [Read original article](<https://www.securityweek.com/novel-android-banking-rat-hirudo-replaces-banking-apps-with-trojanized-copies/>)

Author: Kevin Townsend

Published: 2026-10-15T10:15:32Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [StreamRAT](<https://devfeed.tech/topics/streamrat.md>), [Android Security](<https://devfeed.tech/topics/android-security.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Remote Access Trojan](<https://devfeed.tech/topics/remote-access-trojan.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-malware](<https://devfeed.tech/tags/android-malware.md>), [android-rat](<https://devfeed.tech/tags/android-rat.md>), [banking-trojan](<https://devfeed.tech/tags/banking-trojan.md>), [behavioral-analytics](<https://devfeed.tech/tags/behavioral-analytics.md>), [credential-theft](<https://devfeed.tech/tags/credential-theft.md>), [hirudo](<https://devfeed.tech/tags/hirudo.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-threats](<https://devfeed.tech/tags/malware-threats.md>), [rat](<https://devfeed.tech/tags/rat.md>)

### AI overview

The Android Hirudo banking trojan replaces legitimate banking apps with modified copies that conceal its security checks. It steals credentials and enables remote device control; researchers recommend server-side Play Integrity verification, behavioral analytics and backend transaction-risk controls for financial institutions.

### Source excerpt

The Hirudo malware combines elements of a traditional banking trojan and a full-featured RAT. The post Novel Android RAT 'Hirudo' Replaces Banking Apps With Trojanized Copies appeared first on SecurityWeek.

## Building a Camera-Aware Voice AI App on Android

DevFeed: [Building a Camera-Aware Voice AI App on Android](<https://devfeed.tech/articles/building-a-camera-aware-voice-ai-app-on-android-55441.md>)

Original publisher: [Read original article](<https://proandroiddev.com/building-a-camera-aware-voice-ai-app-on-android-58cba07629bb?source=rss----c72404660798---4>)

Author: Akshay Nandwana

Published: 2026-09-19T16:19:24Z

Content type: article

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [Conversational AI](<https://devfeed.tech/topics/conversational-ai.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Image](<https://devfeed.tech/topics/image.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [cameraX](<https://devfeed.tech/topics/camerax.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [camera](<https://devfeed.tech/tags/camera.md>), [compose](<https://devfeed.tech/tags/compose.md>), [context](<https://devfeed.tech/tags/context.md>), [conversational-ai](<https://devfeed.tech/tags/conversational-ai.md>), [gemini](<https://devfeed.tech/tags/gemini.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [live](<https://devfeed.tech/tags/live.md>), [realtime](<https://devfeed.tech/tags/realtime.md>), [realtime-voice](<https://devfeed.tech/tags/realtime-voice.md>), [rtc](<https://devfeed.tech/tags/rtc.md>), [voice](<https://devfeed.tech/tags/voice.md>), [voice-ai](<https://devfeed.tech/tags/voice-ai.md>)

### AI overview

Live Lens combines an Android Kotlin/Jetpack Compose app, Agora real-time voice sessions, and a Python backend that uses Gemini for conversation and camera-image understanding. The app sends selected camera snapshots to the backend; Gemini Vision summarizes them, and the backend injects that context into the active Agora agent. Camera understanding is periodic frame analysis, not continuous video ingestion. Agora RTC also handles audio, camera preview, and session events. The backend generates short-lived RTC/RTM tokens and holds provider credentials, keeping Agora and Gemini secrets out of the Android app. The demo uses Agora RTC preview because the camera is part of a real-time communication session; CameraX is a better fit when local per-frame analysis, advanced image pipelines, or offline capture are needed. Setup requires Android Studio/JDK 17+, Python 3.10+, an Android device, an Agora project with Conversational AI enabled, and a Gemini API key.

### Source excerpt

How Live Lens uses Agora Conversational AI, Gemini Live, and Jetpack Compose to create a realtime assistant that can listen, speak, and understand camera context. Live Lens is an experimental Android demo where a user can point their phone camera at a real-world workspace and talk to an AI agent while the session is running. The project is built on top of the Agora Conversational AI Android quickstart. It combines a Kotlin + Jetpack Compose Android app, Agora realtime voice infrastructure, a small Python backend, Gemini Live for voice conversation, and Gemini Vision for camera-frame understanding. Repository: github.com/AgoraIO-Conversational-AI/agent-quickstart-android Demo video The video version of this project should appear early in the article, before the implementation details. The main thing to communicate is the division of responsibilities: Android camera feed -> Gemini visual understanding -> Agora real-time voice conversation The phone becomes the agent's eyes. Gemini handles the visual reasoning. Agora provides the realtime conversational layer around that reasoning: session start, RTC audio, agent audio, RTM events, interruption, and lifecycle control. https://medium.com/media/f0f34f25bd3a49f1700749c7295c634f/hrefLive Lens running on a physical Android device: the user points the phone camera at a tic-tac-toe game on paper, makes moves naturally, and the agent responds with visual context during the same live voice session.What the demo does The Android app has a simple Live Lens flow: - Start from a clean Compose home screen. - Request camera and microphone permissions. - Open a live camera session using Agora RTC preview. - Start a realtime voice conversation with an Agora Conversational AI agent. - Use the rear camera by default. - Refresh visual context automatically, or manually with the eye button. - Control camera switch, torch, zoom, mute, and session end from the camera screen. The backend handles everything that should not live inside the Androi

## From Permissions to Sessions: Rethinking Location Access in Android 17

DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17](<https://devfeed.tech/articles/from-permissions-to-sessions-rethinking-location-access-in-android-17-22946.md>)

Original publisher: [Read original article](<https://proandroiddev.com/from-permissions-to-sessions-rethinking-location-access-in-android-17-5a13124b777d?source=rss----c72404660798---4>)

Author: Nav Singh

Published: 2026-09-09T01:15:51Z

Content type: tutorial

Language: en

Sources: [ProAndroidDev](<https://devfeed.tech/sources/proandroiddev-medium.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-permissions](<https://devfeed.tech/tags/android-permissions.md>), [android17](<https://devfeed.tech/tags/android17.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [boilerplate](<https://devfeed.tech/tags/boilerplate.md>), [button](<https://devfeed.tech/tags/button.md>), [compose](<https://devfeed.tech/tags/compose.md>), [consent](<https://devfeed.tech/tags/consent.md>), [feature](<https://devfeed.tech/tags/feature.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [implement](<https://devfeed.tech/tags/implement.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jetpack](<https://devfeed.tech/tags/jetpack.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [layout](<https://devfeed.tech/tags/layout.md>), [libraries](<https://devfeed.tech/tags/libraries.md>), [library](<https://devfeed.tech/tags/library.md>), [location](<https://devfeed.tech/tags/location.md>), [permission](<https://devfeed.tech/tags/permission.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [sessions](<https://devfeed.tech/tags/sessions.md>)

### AI overview

Android 17's system-rendered LocationButton is presented as a way to request precise location for the current session through system-managed consent. The excerpt's setup declares USE_LOCATION_BUTTON and coarse/fine location permissions, marks ACCESS_FINE_LOCATION with onlyForLocationButton, adds the androidx.core.locationbutton:locationbutton-compose library (shown as 1.0.0-alpha01), and uses its LocationButton composable to handle grant or denial callbacks. The library uses remote system rendering on Android Cinnamon Bun (API 37) and later, with a local Compose fallback on older versions or if remote rendering fails. The excerpt also shows optional styling for colors, outlines, size, and corner radii.

### Source excerpt

Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. <!-- Standard Coarse and Fine Location Permissions + onlyForLocationButton --> <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" android:usesPermissionFlags="onlyForLocationButton"/> <!-- Required system permission for rendering the LocationButton --> <uses-permission android:name="android.permission.USE_LOCATION_BUTTON" />Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th

## From Permissions to Sessions: Rethinking Location Access in Android 17

DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17](<https://devfeed.tech/articles/from-permissions-to-sessions-rethinking-location-access-in-android-17-25982.md>)

Original publisher: [Read original article](<https://proandroiddev.com/from-permissions-to-sessions-rethinking-location-access-in-android-17-5a13124b777d?source=rss-711ab22c5c77------2>)

Author: Nav Singh

Published: 2026-09-03T18:18:32Z

Content type: tutorial

Language: en

Sources: [Nav Singh](<https://devfeed.tech/sources/stories-by-nav-singh-on-medium.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Jetpack Compose](<https://devfeed.tech/topics/jetpack-compose.md>), [Android](<https://devfeed.tech/topics/android.md>), [Jetpack](<https://devfeed.tech/topics/jetpack.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [Boilerplate](<https://devfeed.tech/topics/boilerplate.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-17](<https://devfeed.tech/tags/android-17.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [android-permissions](<https://devfeed.tech/tags/android-permissions.md>), [android17](<https://devfeed.tech/tags/android17.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [compose](<https://devfeed.tech/tags/compose.md>), [implementation](<https://devfeed.tech/tags/implementation.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [location](<https://devfeed.tech/tags/location.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [sessions](<https://devfeed.tech/tags/sessions.md>)

### AI overview

Android 17's Jetpack Compose LocationButton lets users grant precise location for the current session through a system-handled consent flow. The excerpt says to declare USE_LOCATION_BUTTON and ACCESS_COARSE_LOCATION, and to mark ACCESS_FINE_LOCATION with onlyForLocationButton, then add the androidx.core.locationbutton:locationbutton-compose dependency (shown as version 1.0.0-alpha01) and use the LocationButton composable to handle grant or denial. On Android Cinnamon Bun (API 37) and later it uses system remote rendering; on older versions or if that fails, it falls back to local Compose rendering. The button's colors, outline, size, shape, and pressed corner radius can be customized. The excerpt presents this as reducing custom permission-flow work and making session-only access clearer, but supplies no comparison or further limitations.

### Source excerpt

Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. <!-- Standard Coarse and Fine Location Permissions + onlyForLocationButton --> <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" /> <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" android:usesPermissionFlags="onlyForLocationButton"/> <!-- Required system permission for rendering the LocationButton --> <uses-permission android:name="android.permission.USE_LOCATION_BUTTON" />Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th

## Elevating app quality: Reducing memory usage and improving device migration

DevFeed: [Elevating app quality: Reducing memory usage and improving device migration](<https://devfeed.tech/articles/elevating-app-quality-reducing-memory-usage-and-improving-device-migration-88692.md>)

Original publisher: [Read original article](<https://developer.android.com/blog/posts/elevating-app-quality-reducing-memory-usage-and-improving-device-migration>)

Author: Raghavendra Hareesh Pottamsetty

Published: 2026-08-26T00:00:00Z

Content type: news

Language: en

Sources: [Android Developers](<https://devfeed.tech/sources/android-developers-blog.md>)

Topics: [Google Play](<https://devfeed.tech/topics/google-play.md>), [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [android-app-bundle](<https://devfeed.tech/topics/android-app-bundle.md>), [R8](<https://devfeed.tech/topics/r8.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-vitals](<https://devfeed.tech/tags/android-vitals.md>), [app-quality](<https://devfeed.tech/tags/app-quality.md>), [developers](<https://devfeed.tech/tags/developers.md>), [memory](<https://devfeed.tech/tags/memory.md>), [migration](<https://devfeed.tech/tags/migration.md>), [product-news](<https://devfeed.tech/tags/product-news.md>)

### AI overview

Google Play is introducing app quality requirements for memory usage, bitmap handling, and DEX optimization, with enforcement beginning in February 2027. Starting in April 2027, apps that support sign-in must use the Android Restore Credentials API to restore users' sign-in state during device transfers. Play Console tools are rolling out to help developers measure memory use, identify crashes, and assess code optimization.

### Source excerpt

Maintaining a healthy Android ecosystem is a shared commitment where every app and game has a role to play.

## PermissionFlow: A Reactive API for knowing the status of Android app permissions

DevFeed: [PermissionFlow: A Reactive API for knowing the status of Android app permissions](<https://devfeed.tech/articles/permissionflow-a-reactive-api-for-knowing-the-status-of-android-app-permissions-25740.md>)

Original publisher: [Read original article](<https://blog.shreyaspatil.dev/permissionflow-a-reactive-api-for-knowing-the-status-of-android-app-permissions/>)

Author: Shreyas Patil

Published: 2023-05-22T05:19:08Z

Content type: article

Language: en

Sources: [Shreyas Patil's Blog](<https://devfeed.tech/sources/shreyas-patil-s-blog.md>)

Topics: [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [Android](<https://devfeed.tech/topics/android.md>), [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [reactive](<https://devfeed.tech/topics/reactive.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [android-development](<https://devfeed.tech/tags/android-development.md>), [api](<https://devfeed.tech/tags/api.md>), [compose](<https://devfeed.tech/tags/compose.md>), [coroutines](<https://devfeed.tech/tags/coroutines.md>), [flow](<https://devfeed.tech/tags/flow.md>), [jetpack-compose](<https://devfeed.tech/tags/jetpack-compose.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [reactive](<https://devfeed.tech/tags/reactive.md>), [tracking](<https://devfeed.tech/tags/tracking.md>)

### AI overview

PermissionFlow is an open-source Android library that exposes permission status as a reactive API. Any app layer, such as a data module that needs contacts access, can subscribe to a permission's state and receive updates when it changes, including changes users make in app settings. The excerpt says the library uses Kotlin Flow, supports Jetpack Compose, and offers an API that can be tested with mocks or fakes. It presents this approach as an alternative to manually notifying modules when permission status changes. The excerpt does not include implementation details or the remainder of the article.

### Source excerpt

Introduction to PermissionFlow: A reactive API for Android that simplifies tracking permission status changes using Kotlin Coroutines and Flow.

## Revision of restrictions on background work from Android 5.0 to 13

DevFeed: [Revision of restrictions on background work from Android 5.0 to 13](<https://devfeed.tech/articles/revision-of-restrictions-on-background-work-from-android-5-0-to-13-25961.md>)

Original publisher: [Read original article](<https://medium.com/its-tinkoff/android-background-restrictions-b63e73fe508?source=rss-7a0a233f88a2------2>)

Author: Kirill Rozov

Published: 2022-11-29T12:54:28Z

Content type: article

Language: en

Sources: [Kirill Rozov](<https://devfeed.tech/sources/stories-by-kirill-rozov-on-medium.md>)

Topics: [Android](<https://devfeed.tech/topics/android.md>), [Doze Mode](<https://devfeed.tech/topics/doze-mode.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>)

Tags: [account-management](<https://devfeed.tech/tags/account-management.md>), [adapter](<https://devfeed.tech/tags/adapter.md>), [alarm](<https://devfeed.tech/tags/alarm.md>), [android](<https://devfeed.tech/tags/android.md>), [android-app-development](<https://devfeed.tech/tags/android-app-development.md>), [androiddev](<https://devfeed.tech/tags/androiddev.md>), [applications](<https://devfeed.tech/tags/applications.md>), [background](<https://devfeed.tech/tags/background.md>), [background-work](<https://devfeed.tech/tags/background-work.md>), [battery](<https://devfeed.tech/tags/battery.md>), [broadcast](<https://devfeed.tech/tags/broadcast.md>), [calendar](<https://devfeed.tech/tags/calendar.md>), [data-synchronization](<https://devfeed.tech/tags/data-synchronization.md>), [developers](<https://devfeed.tech/tags/developers.md>), [device](<https://devfeed.tech/tags/device.md>), [download](<https://devfeed.tech/tags/download.md>), [file-system](<https://devfeed.tech/tags/file-system.md>), [firebase](<https://devfeed.tech/tags/firebase.md>), [google](<https://devfeed.tech/tags/google.md>), [google-account](<https://devfeed.tech/tags/google-account.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [iphone](<https://devfeed.tech/tags/iphone.md>), [notifications](<https://devfeed.tech/tags/notifications.md>)

### AI overview

The excerpt traces Android's shift from flexible background work toward system-managed, battery-conscious execution. Android 5.0 introduced JobScheduler with conditions such as charging and network availability, though the text says it worked reliably only from Android 6.0. Doze and App Standby later constrained network access and triggers; high-priority FCM could wake devices but should be reserved for important events. Android 7 and 8 restricted implicit broadcasts and background services, directing developers toward jobs and foreground services; Android 8 required foreground promotion within five seconds. Later releases added app-use buckets, limits on background location and sensors, foreground-service types, user permission for background location, and tighter rules for starting foreground services and exact alarms. Android 12 expedited jobs offer fewer restrictions but have quotas and execution limits. Android 13 lets users stop foreground work and restrict an app's background activity, while JobScheduler gained upload support and job priorities. The excerpt notes that device vendors can add or change some restrictions and that exact alarms may be delayed.

### Source excerpt

Background restrictions in Android Once upon a time, running in the background was easy. Now Android has a lot of restrictions: running in the background, access to the file system, permissions that need to be approved by Google Play moderators, and others. Developers have to work with all of them. Let's remember where it all started and how the requirements changed with each new version of Android How it started Before Android 5.0, we had the set of tools to run tasks in the background: Alarm Manager. The tool that allows you to set an alarm on your system and receive notifications. Broadcast Intent. It sends notifications about events that are happening on the system (new messages, for example). Service -- Background, Foreground & Bound. Sync Adapter. A special ancient stuff, which is connected to account management for data synchronization. A clear example: when you set up a Google account in Android, you can set up synchronization of your calendar, contacts and other services. Under the hood, it works through the Sync Adapter. The tool has not lived up to our days. Download Manager. A utility that allows you to download files. It is not very smart, but it is simple and convenient. Google Play, for example, is what downloads files with it. The problems appeared because developers did not follow Spider-Man's rule: "With great opportunities for developers comes responsibility for the speed of the system". Google gave them huge opportunities from the first versions of Android, but did not warn them that they were working in a system that was responsible for quality. When users broke something, they didn't blame third-party developers, they said, "Android is lagging, but everything is fast on the iPhone." It turned out that the developers were good and Google was bad. Google decided to deal with this, but to do this, they had to find "enemies" affecting the quality of applications. They turned out to be: Battery size vs. device size. Everyone wants a thin device that

## Android 12 review for Developers

DevFeed: [Android 12 review for Developers](<https://devfeed.tech/articles/android-12-review-for-developers-25965.md>)

Original publisher: [Read original article](<https://proandroiddev.com/review-of-android-12-for-developers-ea3ce9247e0?source=rss-7a0a233f88a2------2>)

Author: Kirill Rozov

Published: 2021-06-29T14:42:14Z

Content type: article

Language: en

Sources: [Kirill Rozov](<https://devfeed.tech/sources/stories-by-kirill-rozov-on-medium.md>)

Topics: [Android Security](<https://devfeed.tech/topics/android-security.md>), [android-permissions](<https://devfeed.tech/topics/android-permissions.md>), [material-you](<https://devfeed.tech/topics/material-you.md>), [Material Design](<https://devfeed.tech/topics/material-design.md>), [User Interfaces](<https://devfeed.tech/topics/user-interfaces.md>), [User interface design](<https://devfeed.tech/topics/ui-design.md>), [Macrobenchmark](<https://devfeed.tech/topics/macrobenchmark.md>)

Tags: [android](<https://devfeed.tech/tags/android.md>), [android-12](<https://devfeed.tech/tags/android-12.md>), [data-privacy](<https://devfeed.tech/tags/data-privacy.md>), [design](<https://devfeed.tech/tags/design.md>), [developers](<https://devfeed.tech/tags/developers.md>), [firmware](<https://devfeed.tech/tags/firmware.md>), [for-developers](<https://devfeed.tech/tags/for-developers.md>), [google-i-o](<https://devfeed.tech/tags/google-i-o.md>), [material-design](<https://devfeed.tech/tags/material-design.md>), [material-you](<https://devfeed.tech/tags/material-you.md>), [palette](<https://devfeed.tech/tags/palette.md>), [pixel](<https://devfeed.tech/tags/pixel.md>), [review](<https://devfeed.tech/tags/review.md>), [security](<https://devfeed.tech/tags/security.md>), [splash-screen](<https://devfeed.tech/tags/splash-screen.md>), [widget](<https://devfeed.tech/tags/widget.md>)

### AI overview

Android 12 combines a Material You redesign with stronger privacy controls and new developer requirements. Developers can use RenderEffect for blur and other effects, support richer widgets, and handle shared content through the unified Rich Content Insertion API. For media compatibility, the system can transcode HEVC to AVC and HDR10 to SDR, with conversion time varying by device; Performance Class lets apps adapt to device capabilities. Privacy and background-work changes include approximate-location choices, separate Bluetooth scan/connect permissions, clipboard access notices, and limits on starting foreground services from the background. Expedited jobs are an alternative for short, important work, but may be stopped if they exceed a few minutes or system resource limits. Apps targeting Android 12 must explicitly set android:exported for manifest components; missing values can block installation. The excerpt also notes that some Material You adoption and upcoming features were still uncertain or beta-dependent.

### Source excerpt

Android 12 review for developershttps://medium.com/media/14d506cb3ec570f8bf99b03256759f2e/href The Google I/O'21 conference took place, and we learned absolutely everything about the new version of Android, and we can also try it all in Beta 1, which we can install on the Pixel, and other manufacturers also allow you to install the GSI image. The main emphasis in the release was made on enhancing OS security and data privacy, as well as redesigning the system. They have done a very good job of supporting today's new media standards, and they have minimized the amount of pain that flagship devices will experience from older or budget smartphones. App Widgets have been improved, as users have been asking for since the first version of Android. DesignNew Material You designhttps://medium.com/media/94c8a2d0eca25e4d6931df11976a8884/href Google has unveiled an updated version of Material Design that focuses on personalizing the color palette. For example, colors in Pixel devices will be determined based on the background image. You will be able to fully experience Material You in the second Beta version of Android 12. The most important question is: "How will vendors adapt Material You in their firmware?" The chances are that this concept of colors will remain in pure Android, and vendors and third-party applications will ignore the design and use their own ideas. The entire color palette in Material was based on the app's brand colors, and now it has to be user-definable. Much depends on how the app interface designers adapt the new design. Write in the comments if you like Google's new visual style Standard Splash Screen for all apps SplashScreen API allows you to customize it for your brand: set a background, animated icon and other parameters. You cannot turn off the new Splash Screen, so everyone who has their own variation of such a screen -- pay attention. Splash Screen is a fairly popular practice in Android applications to hide long initialization. Now a standard