This deadlocking bug is terrible. Replacing the mutex with an error checking mutex using an abort on errors makes the issue simply vanish.
Seems like for (all but final) testing you'd want all the lockdown disabled.
-
-
Usually develop via userdebug builds signed with the same release keys, to allow switching back and forth with user builds.
-
A userdebug build has default-enabled adb with no whitelist, including in early boot along with adb root and su for shell user.
End of conversation
New conversation -
-
-
BTW been meaning to ask - could
@CopperheadOS be easily tweaked by installing user to add a uid-0 sshd? -
If you make a userdebug build, you get root access via adb. For root sshd, you could probably repurpose the su SELinux domain.
-
For simply debugging, adb shell access is already enough though. Especially in userdebug builds where it has adb root / su.
-
Main annoyance is having to deal with local gdb with symbol directory + gdbserver on the device. Symbols won't fit on them.
-
Other than having to use custom made uart-via-headphone-port debug cables in order to debug the kernel and early boot at least.
-
At least Nexus devices (and hopefully the Pixel phones) have a standard way to deal with this without disassembly though.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.