Loading page
About this tool
Identify unnecessary permissions and ad SDK risk in wallpaper and live wallpaper apps.
The Wallpaper App Permission Audit scores a wallpaper or live-wallpaper app against the smallest honest permission set on your phone: SET_WALLPAPER, an internet connection for the catalogue, and the system photo picker. Everything else is scored as exposure, because the usual reason for it is the bundled advertising SDK rather than any wallpaper feature. Eighteen permissions are weighted by sensitivity, with overlay, install-other-apps and accessibility access at the top — the three that turn a free wallpaper pack into an adware delivery route.
Open Wallpaper App Permission Audit on AltFTool — it loads instantly in your browser.
Add your input to the workspace.
Adjust the options until the result looks right.
Copy or download the output and put it to work.
SET_WALLPAPER plus internet is the whole legitimate set, so anything extra is visible at a glance.
Overlay, install-packages and boot-start grants are explained as what they usually are rather than as features.
A foreground service and start-at-boot are treated as reasonable for an animated wallpaper and needless for a static one.
SET_WALLPAPER — a normal permission with no prompt — and, if it has an online catalogue, INTERNET. To use one of your own pictures it can go through the system photo picker, which needs no permission at all. Anything more deserves an explanation.
Because the app is usually a thin shell around an advertising SDK, and the SDK wants an advertising ID, device identifiers, the installed-app list and sometimes an overlay to show ads outside the app. The wallpapers themselves need none of it.
Yes. REQUEST_INSTALL_PACKAGES lets it push an APK installer at you, which is how sideloaded adware spreads from free wallpaper packs. No wallpaper feature needs it — uninstall rather than trying to tune the permission.
A live wallpaper legitimately uses a foreground service to run its animation and RECEIVE_BOOT_COMPLETED to restart after a reboot. A static wallpaper app has nothing to run, so the same grants there usually keep an ad SDK alive instead.