Summary
After manually changing an app's battery optimization setting from Unrestricted to Optimized or Restricted, the app still appears in the "Battery unrestricted apps" list inside Permission Pilot. This persists even after reopening the app or refreshing the list.
Steps to Reproduce
- Open Permission Pilot.
- Go to the Battery unrestricted apps category.
- Tap the info icon (i) next to an app listed there.
- Navigate to the system Battery settings for that app.
- Change the setting from Unrestricted to Optimized or Restricted.
- Return to Permission Pilot and check the Battery unrestricted apps list again.
Expected Behavior
The app should no longer appear in the Battery unrestricted apps list after its battery setting is changed to Optimized or Restricted.
Actual Behavior
The app remains in the list, even after a refresh or app restart.
Device & Environment
Device: Samsung A50
Android Version: 14 (Fresh OS)
Permission Pilot Version: 2.1.0-rc0
One UI Version: 6.1.1
Additional Context
This might be an Android system-level behavior (possibly Samsung-specific), or a caching/refresh issue within Permission Pilot. I’m reporting this in case it can be fixed or worked around on the app side.
Thank you for looking into this!
Summary
After manually changing an app's battery optimization setting from Unrestricted to Optimized or Restricted, the app still appears in the "Battery unrestricted apps" list inside Permission Pilot. This persists even after reopening the app or refreshing the list.
Steps to Reproduce
Expected Behavior
The app should no longer appear in the Battery unrestricted apps list after its battery setting is changed to Optimized or Restricted.
Actual Behavior
The app remains in the list, even after a refresh or app restart.
Device & Environment
Device: Samsung A50
Android Version: 14 (Fresh OS)
Permission Pilot Version: 2.1.0-rc0
One UI Version: 6.1.1
Additional Context
This might be an Android system-level behavior (possibly Samsung-specific), or a caching/refresh issue within Permission Pilot. I’m reporting this in case it can be fixed or worked around on the app side.
Thank you for looking into this!