-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Declarative ADB keys; adb at boot #267
Comments
Not sure if any helpful, but IIRC setting the build variant to
I'm thinking a bit more here, and I seem to recall that maybe LinageOS made their Not sure if any of those hints will help. Those, in any way, don't help with the adb key. |
This makes sense because most LOS devices are userdebug rather than user. I'm wondering though whether it's possible to override this setting somehow. I guess you can always patch the sources... |
🤔 I don't grok the big picture enough to know how I don't see any usage that would make any keys disallowed
So that leaves the Except that it looks like it should be fine: Only if So, my gut feeling here is that it's “just” (lol) a matter of having a way to override |
Speaking of
Ignoring the satire...
Oh, documentation here: |
Thanks a bunch for the research notes! How would I set those additional properties in Robotnix though? |
I don't know, but I believe this is the current best(?) mechanism for LineageOS:
So something like Though I wonder if AOSP has such a thing. If it doesn't, it would require patching the AOSP |
For debugging purposes, it'd be incredibly useful to be able to declaratively enable ADB on boot and have your keys be trusted.
The following props need to be set in order to enable ADB on boot:
There probably is a way to set these but I haven't found it yet or how to do it via robotnix.
Trusted ADB keys go in
/data/misc/adb/adb_keys
. This is a lot harder to bake into the ROM as that's a runtime state directory. It also gets reset frequently. Perhaps there's a way to bake in the key into the ROM though.The text was updated successfully, but these errors were encountered: