You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device: Samsung Galaxy Note 4 (SM-N910F) OS:Lineage OS 16 unofficial by kevintm78, Build: lineage_trlte-userdebug 9 PQ2a.190305.002eng.kevint.20190312.063803 test-keys Configuration: OS encrypted and rooted via su arm AppOpsX version: 1.2.5
Description
Upon attempting to see the permissions of any app, AppOpsX will show the following error message:
Attempt to invoke virtual method 'android.os.Parcelable android.os.Bundle.getParcelable(java.lang.String)' on a null object reference
Steps to reproduce
Open AppOpsX
Tap on any app
Expected result
Seeing app permissions and being able to toggle them on/off.
What I've attempted to solve the problem
Reboot
Reinstall AppOpsX
Turn on Root compatibility mode in AppOpsX > Settings
Turn on ADB mode in AppOpsX > Settings
The problem puzzles me because I have used AppOpsX before and without problems, but at that time I hadn't encrypted the device. My prime suspect is the device encryption.
The text was updated successfully, but these errors were encountered:
Apologies. I wasn't aware that turning on root compatibility mode requires a reboot. After the reboot, it works, although I cannot turn off certain permissions (WiFi / data access). But I suppose that is part of the workaround. I'm closing this report.
Occurs on:
Device: Samsung Galaxy Note 4 (SM-N910F)
OS: Lineage OS 16 unofficial by kevintm78, Build: lineage_trlte-userdebug 9 PQ2a.190305.002eng.kevint.20190312.063803 test-keys
Configuration: OS encrypted and rooted via su arm
AppOpsX version: 1.2.5
Description
Upon attempting to see the permissions of any app, AppOpsX will show the following error message:
Steps to reproduce
Expected result
Seeing app permissions and being able to toggle them on/off.
What I've attempted to solve the problem
The problem puzzles me because I have used AppOpsX before and without problems, but at that time I hadn't encrypted the device. My prime suspect is the device encryption.
The text was updated successfully, but these errors were encountered: