starred/LADB

Fork 0

mirror of https://github.com/tytydraco/LADB.git synced 2026-04-27 00:15:59 +03:00

[GH-ISSUE #75] First time setup improvements #57

New issue

Closed

opened 2026-03-04 02:11:13 +03:00 by kerem · 10 comments

kerem commented

2026-03-04 02:11:13 +03:00

Owner

Originally created by @mirh on GitHub (Jun 10, 2022).
Original GitHub issue: https://github.com/tytydraco/LADB/issues/75

It is my understanding that Settings.Global.ADB_WIFI_ENABLED can programmatically detect what it has written on the tin
- I believe the WRITE_SECURE_SETTINGS permission could also allow for that to be started automatically
none of that is going to be a thing before 11, but for starters you could at least check the normal ADB_ENABLED property
improve the "waiting for device respond" line, that leaves clueless users like in https://github.com/tytydraco/LADB/issues/65

Originally created by @mirh on GitHub (Jun 10, 2022). Original GitHub issue: https://github.com/tytydraco/LADB/issues/75 - [x] It is my understanding that `Settings.Global.ADB_WIFI_ENABLED` can programmatically detect what it has written on the tin * [x] I [believe](https://old.reddit.com/r/androiddev/comments/j6p8q4/wireless_debugging_in_android_11_off/gte71jd/) the WRITE_SECURE_SETTINGS permission could also allow for that to be started automatically - [ ] none of that is going to be a thing [before](https://android.googlesource.com/platform/frameworks/base/+/2076c04333781235021369d10752c22ff6bf8ced) 11, but for starters you could at least check the normal ADB_ENABLED property - [x] improve the "waiting for device respond" line, that leaves clueless users like in https://github.com/tytydraco/LADB/issues/65

kerem

2026-03-04 02:11:13 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@nilsingha112 commented on GitHub (Jul 26, 2022):

LADB sowed
Enter pairing code: failed to parse address

@nilsingha112 commented on GitHub (Jul 26, 2022): LADB sowed Enter pairing code: failed to parse address

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@tytydraco commented on GitHub (Oct 15, 2022):

It is my understanding that Settings.Global.ADB_WIFI_ENABLED can programmatically detect what it has written on the tin
* [ ]  I [believe](https://old.reddit.com/r/androiddev/comments/j6p8q4/wireless_debugging_in_android_11_off/gte71jd/) the WRITE_SECURE_SETTINGS permission could also allow for that to be started automatically
none of that is going to be a thing before 11, but for starters you could at least check the normal ADB_ENABLED property

improve the "waiting for device respond" line, that leaves clueless users like in Android 9 ladb can't use #65

Very very true, I will have it not toggle the state for A10 and below! And I will implement those other changes as well.

@tytydraco commented on GitHub (Oct 15, 2022): > * [x] It is my understanding that `Settings.Global.ADB_WIFI_ENABLED` can programmatically detect what it has written on the tin > > * [ ] I [believe](https://old.reddit.com/r/androiddev/comments/j6p8q4/wireless_debugging_in_android_11_off/gte71jd/) the WRITE_SECURE_SETTINGS permission could also allow for that to be started automatically > > * [x] none of that is going to be a thing [before](https://android.googlesource.com/platform/frameworks/base/+/2076c04333781235021369d10752c22ff6bf8ced) 11, but for starters you could at least check the normal ADB_ENABLED property > > * [x] improve the "waiting for device respond" line, that leaves clueless users like in [Android 9 ladb can't use #65](https://github.com/tytydraco/LADB/issues/65) Very very true, I will have it not toggle the state for A10 and below! And I will implement those other changes as well.

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@tytydraco commented on GitHub (Oct 16, 2022):

Added

@tytydraco commented on GitHub (Oct 16, 2022): Added

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@mirh commented on GitHub (Oct 16, 2022):

Nothing of what I left unchecked seems to have happened actually.

@mirh commented on GitHub (Oct 16, 2022): Nothing of what I left unchecked seems to have happened actually.

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@tytydraco commented on GitHub (Oct 16, 2022):

Nothing of what I left unchecked seems to have happened actually.

I already had the auto wireless debugging thing in a previous update. And I made sure that it only happens on Android 11+. And I added a little note in the new update for more details about the waiting screen. I think that's what you meant right?

@tytydraco commented on GitHub (Oct 16, 2022): > Nothing of what I left unchecked seems to have happened actually. I already had the auto wireless debugging thing in a previous update. And I made sure that it only happens on Android 11+. And I added a little note in the new update for more details about the waiting screen. I think that's what you meant right?

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@mirh commented on GitHub (Oct 16, 2022):

Duh, I see #49 now sorry.
Idk why I started talking/worrying about A11 when my phone didn't even have it.

I think you are still missing the super dumb ADB_ENABLED check though.

@mirh commented on GitHub (Oct 16, 2022): Duh, I see #49 now sorry. Idk why I started talking/worrying about A11 when my phone didn't even have it. I think you are still missing the super dumb ADB_ENABLED check though.

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@tytydraco commented on GitHub (Oct 16, 2022):

Duh, I see #49 now sorry. Idk why I started talking/worrying about A11 when my phone didn't even have it.

I think you are still missing the super dumb ADB_ENABLED check though.

Ah right. Does this actually enable USB debugging when you set the global setting? I know some stuff it doesn't actually toggle.

@tytydraco commented on GitHub (Oct 16, 2022): > Duh, I see #49 now sorry. Idk why I started talking/worrying about A11 when my phone didn't even have it. > > I think you are still missing the super dumb ADB_ENABLED check though. Ah right. Does this actually enable USB debugging when you set the global setting? I know some stuff it doesn't actually toggle.

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@mirh commented on GitHub (Oct 16, 2022):

https://stackoverflow.com/questions/11314145/looking-to-enable-and-disable-toggle-adb-or-usb-debugging-using-command-line-o
It should AFAICT, but you need some unclear special permission to modify the setting. Unclear if it couldn't even just be the usual WRITE_SECURE_SETTINGS.
Nevertheless at least the check should be always possible.

@mirh commented on GitHub (Oct 16, 2022): https://stackoverflow.com/questions/11314145/looking-to-enable-and-disable-toggle-adb-or-usb-debugging-using-command-line-o It should AFAICT, but you need some unclear special permission to modify the setting. Unclear if it couldn't even just be the usual WRITE_SECURE_SETTINGS. Nevertheless at least the check should be always possible.

kerem commented

2026-03-04 02:11:14 +03:00

Author

Owner

@tytydraco commented on GitHub (Oct 18, 2022):

https://stackoverflow.com/questions/11314145/looking-to-enable-and-disable-toggle-adb-or-usb-debugging-using-command-line-o It should AFAICT, but you need some unclear special permission to modify the setting. Unclear if it couldn't even just be the usual WRITE_SECURE_SETTINGS. Nevertheless at least the check should be always possible.

github.com/tytydraco/LADB@f10143fb90

Looks good?

@tytydraco commented on GitHub (Oct 18, 2022): > https://stackoverflow.com/questions/11314145/looking-to-enable-and-disable-toggle-adb-or-usb-debugging-using-command-line-o It should AFAICT, but you need some unclear special permission to modify the setting. Unclear if it couldn't even just be the usual WRITE_SECURE_SETTINGS. Nevertheless at least the check should be always possible. https://github.com/tytydraco/LADB/commit/f10143fb90f6aaa7515a983c9e98f2f24235c868 Looks good?

kerem commented

2026-03-04 02:11:15 +03:00

Author

Owner

@mirh commented on GitHub (Oct 20, 2022):

Looks gucci to me, even though I didn't personally test it.

@mirh commented on GitHub (Oct 20, 2022): Looks gucci to me, even though I didn't personally test it.