FlashDroid Kid Keeps Losing Permissions: Why Android Resets Them

You set up FlashDroid Kid correctly.

A week later, the parent app says a required permission is missing.

You enable it again.

Then it happens again.

That pattern usually means you need to identify which Android mechanism is changing state rather than repeatedly toggling the permission.

First identify the exact permission that changed

Do not treat “permissions” as one bucket.

Write down the one that changed:

• location
• notifications
• camera
• microphone
• accessibility or service state
• another required Android permission

Different permissions have different causes and different fixes.

Android can revoke permissions for unused apps

Android's unused-app optimisation can:

• remove temporary files
• revoke app permissions
• stop unused apps from running in the background
• stop unused apps from sending notifications

Google documents this under Pause app activity if unused.

Source: https://support.google.com/android/answer/13627979

On a child protection app that needs ongoing operation, check whether Android is treating the app as unused and pause or optimisation settings are enabled.

Check the unused-app setting

On many Android versions the path is roughly:

Settings → Apps → FlashDroid Kid → Unused app settings

Look for:

• Pause app activity if unused
• Remove permissions if app isn't used

Exact wording varies.

If your FlashDroid setup requires continuous background functionality, exclude the app from that unused-app behaviour.

OEM battery management is separate

Even when permissions remain granted, the manufacturer can restrict background work.

This can make the app look as if a permission “stopped working.”

Use the exact brand guide:

• Xiaomi
• Oppo
• Vivo
• generic Android

Do not assume the menu is identical across brands or Android versions.

Accessibility needs its own diagnosis

Android accessibility services are system-managed services. The service starts when the user enables it and Android binds to it.

Source: https://developer.android.com/reference/android/accessibilityservice/AccessibilityService

If the Settings toggle looks enabled but FlashDroid reports the service is not healthy:

• restart the phone
• use the FlashDroid repair flow
• if necessary, toggle the service off and on once
• record the phone model and Android version if it repeats

Do not repeatedly change unrelated permissions.

Re-check after app or OS updates

Major changes can expose problems:

• Android version update
• OEM firmware update
• FlashDroid Kid update
• device restore or profile migration

After a major update, open the child app's health screen and verify required state once.

That is faster than discovering a broken permission days later.

Distinguish system reset from child action

A permission can change because:

• Android removed it
• OEM software interfered
• the child changed it manually

Look at the pattern.

If multiple permissions disappear after long inactivity, unused-app management is plausible.

If one specific protection permission changes immediately after a rule conflict, deliberate action becomes more plausible.

Do not accuse before checking.

Create a simple permission-health routine

When you first set up a new phone:

1. complete all required permissions
2. exclude FlashDroid Kid from unused-app pausing if needed
3. apply the correct OEM background settings
4. restart the phone once
5. verify the child app still reports healthy state

Repeat after a major Android upgrade.

That is easier than troubleshooting from memory months later.

What FlashDroid can do

FlashDroid can make protection-state problems visible where supported.

It still depends on Android-granted permissions and system services.

It cannot make a permission impossible to change.

See:

• Android parental-controls guide
• limit games and apps use case
• background reliability guide

Related symptoms

If app blocking fails after the permission change: FlashDroid isn't blocking apps.

If a child deliberately changed the permission: my child turned off or got around FlashDroid.

Fast fix order

1. Identify exact permission or service.
2. Re-enable through the FlashDroid setup flow.
3. Check unused-app pausing.
4. Check app-specific battery and background settings.
5. Restart.
6. Check after the next idle period.
7. Record model and Android or OEM version if recurring.
8. Follow the exact brand guide.

Keep a small health checklist after setup

You do not need to inspect every Android setting every day.

After setup, record:

• phone model
• Android/OEM version
• which permissions are required
• which background setting was changed
• whether unused-app pausing was disabled

If the issue returns after an update, you can compare what changed instead of starting from zero.

If only one permission keeps changing

That is useful diagnostic information.

Examples:

Only notifications

Focus on notification permission and channels.

Only location

Focus on location permission, device location services and background access.

Only accessibility/service state

Focus on service lifecycle and OEM/background behaviour.

When one permission repeatedly changes, avoid resetting the entire app configuration. Fix the narrow path first.

Sources

• Android Help — Manage unused apps
  https://support.google.com/android/answer/13627979
• Android Help — Change app permissions
  https://support.google.com/android/answer/9431959
• Android Developers — AccessibilityService
  https://developer.android.com/reference/android/accessibilityservice/AccessibilityService