Hi there and sorry for my grammar
Summary: I found a bug In privilege system Service(shizuku api) If axmaneger isn't running in background and Some apps lose connection with adb then they can't execute command, if I try few more Times The axmaneger lose connection with adb(service crash)
For example: I am using Inure app maneger and If I dont force Lock Axm in background(always open) Inure never can access Shizuku api and stuck with throbber the app goes into inf loop
Solution: Activate the axmaneger and LOCK It to the background(keep it open button)
The bug:if I remove axm from background (close all button) axm forgets who I give the Privilege to the apps, When I open Axm I see Privileges ls ZERO after 5secs later Axm finally remember Privileges and load them, after that app can finally access api
What does It mean: I think Axm Forgets the apps who have permission to use it, When this happens The Apps try to access Axm Service Service looks out for Privileges and finds Absolute nothing! So cant answer app or service goes into a inf loop again... and Never can load the Privileges, if I pushed Service so hard(make to much API request from app) the axm SELF destructed itself(adb connection lost This means Service is crashed)
My humble suggestion to fix that bug(I am not a dev I am only making Suggestion) Add background work API (like YouTube Music like FDE.AI etc.) So app never can stop by android Battery Optimizater Or store the Privileges In a folder so service can look the folder and can see who have access permission to API
and more thing THANK YOU GUYS FOR MAKING THIS APP And I hope you guys can fix it I love axmaneger and community
Almost forget device: android 16, no root, Sdk36, samsung z fold, oneui 8 (yes I did Stop optimizations for this app and add to white list)
Hi there and sorry for my grammar
Summary: I found a bug In privilege system Service(shizuku api) If axmaneger isn't running in background and Some apps lose connection with adb then they can't execute command, if I try few more Times The axmaneger lose connection with adb(service crash)
For example: I am using Inure app maneger and If I dont force Lock Axm in background(always open) Inure never can access Shizuku api and stuck with throbber the app goes into inf loop
Solution: Activate the axmaneger and LOCK It to the background(keep it open button)
The bug:if I remove axm from background (close all button) axm forgets who I give the Privilege to the apps, When I open Axm I see Privileges ls ZERO after 5secs later Axm finally remember Privileges and load them, after that app can finally access api
What does It mean: I think Axm Forgets the apps who have permission to use it, When this happens The Apps try to access Axm Service Service looks out for Privileges and finds Absolute nothing! So cant answer app or service goes into a inf loop again... and Never can load the Privileges, if I pushed Service so hard(make to much API request from app) the axm SELF destructed itself(adb connection lost This means Service is crashed)
My humble suggestion to fix that bug(I am not a dev I am only making Suggestion) Add background work API (like YouTube Music like FDE.AI etc.) So app never can stop by android Battery Optimizater Or store the Privileges In a folder so service can look the folder and can see who have access permission to API
and more thing THANK YOU GUYS FOR MAKING THIS APP And I hope you guys can fix it I love axmaneger and community
Almost forget device: android 16, no root, Sdk36, samsung z fold, oneui 8 (yes I did Stop optimizations for this app and add to white list)