ADB working mode gets lost
Please check before submitting an issue
- I know what my device, OS and App Manager versions are
- I know how to take logs
- I know how to reproduce the issue which may not be specific to my device
Describe the bug
My phone doesn't have root, so I used the ADB mode to let it work. Just ahead, I don't blame any developer - they did and do a great job here. The issue is likly systematic and can't be avoided or doesn't depend on the app itself. Bit behavior does cause me some headache, mostly because I didn't understand it all.
After a while (so by time), by change of WiFi network or any other event the Init fails. That means starting of app takes long, showing an "Init ...." and finally reports the "requested mode can't be used". Than I need to do a longer sequence:
- Settings/DeveloperSettings/Enable Debugging via Wifi (again)
- Long press on AppManager icon, App-info/Force stop/Open
I wasn't aware that "Debugging via Wifi" is responsible, as it sometimes work after that has been already disabled (by system?). I understand it like that, that is might be some caching/background issue.
Does anybody found a shortcut to enable Debugging via Wifi or get AppManager back in ADB mode running? Could AppManager maybe gets some info that "Debug via Wifi" is enabled again and switches its mode back atomically?
Thanks for this great tool, I like it to create the Icons to freeze apps automatically when Screen is off. The only thing that confuses me is that "Select all" is preselected, but I need to enably all 3 buttons below too?!? But that a different thing - sorry to mentioned that here.
To Reproduce
No response
Expected behavior
No response
Screenshots
No response
Logs
No response
Device info
- Device:
- OS Version:
- App Manager Version:
- Mode: Root/ADB/NonRoot
Additional context
No response
Source: MuntashirAkon/AppManager