Android Policy Scanner

File: sample_app_fdroid.apk

Timestamp: 2026-04-22 16:02:39 UTC

Total findings: 21

Risk Summary

Critical

16

High

1

Medium

4

Low

0

What to Fix First

Findings

SDK_001

Target SDK Lag

Confidence: high

android:targetSdkVersion=30

The target SDK version is below the current Play requirement, which can block app updates.

  1. Open build.gradle (app module).
  2. Set targetSdk = 35.
  3. Run full regression test on Android 15.
  4. Resubmit to Play Store.

Outdated target SDKs are commonly rejected during Play policy review.

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.nearby.SwapService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.nearby.LocalRepoService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.nearby.TreeUriScannerIntentService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.nearby.SDCardScannerService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.net.DownloaderService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.installer.InstallerService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.DeleteCacheService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.net.ConnectivityMonitorService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.installer.InstallHistoryService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.fdroid.fdroid.installer.ObfInstallerService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=androidx.work.impl.background.systemalarm.SystemAlarmService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=androidx.work.impl.background.systemjob.SystemJobService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=androidx.room.MultiInstanceInvalidationService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.acra.sender.LegacySenderService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_001

Foreground Service Missing Type

Confidence: high

service=org.acra.sender.JobSenderService, foregroundServiceType=

Foreground services must declare a foreground service type for Play and runtime policy compliance.

  1. Declare android:foregroundServiceType on each foreground service.
  2. Ensure the declared type matches runtime behavior.
  3. Re-test foreground service launch behavior on Android 14+.

Play policy enforcement for foreground service type declarations is active since API 34 (Android 14).

SVC_002

Boot Start + Foreground Service

Confidence: medium

BOOT_COMPLETED receiver with foreground service declaration detected

Combining boot auto-start behavior with foreground service execution is a high-scrutiny Play policy pattern.

  1. Remove automatic boot start where not essential.
  2. Require explicit user action before starting long-running foreground services.

PERM_001

Dangerous Permission Surface

Confidence: high

uses-permission: android.permission.READ_EXTERNAL_STORAGE

This dangerous permission expands data or device access and may trigger additional Play policy review.

  1. Confirm the permission is strictly required for core user value.
  2. Remove the permission if it is no longer needed.
  3. Document user-facing justification and consent flow.

PERM_001

Dangerous Permission Surface

Confidence: high

uses-permission: android.permission.WRITE_EXTERNAL_STORAGE

This dangerous permission expands data or device access and may trigger additional Play policy review.

  1. Confirm the permission is strictly required for core user value.
  2. Remove the permission if it is no longer needed.
  3. Document user-facing justification and consent flow.

PERM_001

Dangerous Permission Surface

Confidence: high

uses-permission: android.permission.CAMERA

This dangerous permission expands data or device access and may trigger additional Play policy review.

  1. Confirm the permission is strictly required for core user value.
  2. Remove the permission if it is no longer needed.
  3. Document user-facing justification and consent flow.

PERM_001

Dangerous Permission Surface

Confidence: high

uses-permission: android.permission.ACCESS_COARSE_LOCATION

This dangerous permission expands data or device access and may trigger additional Play policy review.

  1. Confirm the permission is strictly required for core user value.
  2. Remove the permission if it is no longer needed.
  3. Document user-facing justification and consent flow.

Scan duration: 0.42s

Tool version: 1.0.0

This report is generated by automated static analysis and does not guarantee Play Store approval.