Repository navigation
Android app: the programmer after a reboot, with nobody at the device - #99
Conversation
…-boot-aware attach activity), 1.47.4
PR Summary by QodoRestore Android USB programmer access after reboot
AI Description
Merge Risk
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can enable the Remediation agent and Qodo fixes findings in a dedicated fix PR |
A programmer that stays plugged in was not the app's after a reboot, so remote access needed somebody at the device to replug it.
Cause. Android finds the programmer early in the boot, before the user's storage is unlocked. Then it sees only direct-boot-aware components, so it did not find
UsbAttachActivity, the app chosen with Always, and did not grant the programmer.Fix.
UsbAttachActivityisandroid:directBootAware="true". Before the unlock it only finishes (the system has granted the programmer by then; the settings are not readable yet). The service comes withBOOT_COMPLETED, as before.adb rebootwill do).RemoteService: theaddresses()comment back over its method (Qodo on Android app: remote access (web mode, camex tunnel, optional password) #98).Checked.
UsbAttachActivityat the attach, and a Detect through a camex 4.0.0 tunnel found "CH341A with BY25Q64AS, 8 MB", nobody at the device. Before the fix the same steps gave "no access".tests/run.sh, AndroidassembleDebug lintDebug assembleRelease,tests/android/remote-e2e.shon API 34 and 21: 11/11.