• [x] It is my understanding that Settings.Global.ADB_WIFI_ENABLED can programmatically detect what it has written on the tin
  • [x] 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
• [x] improve the "waiting for device respond" line, that leaves clueless users like in https://github.com/tytydraco/LADB/issues/65

Assume I'm pm granting something. If you insert the wrong command, you get something like in #66. But, if do everything good, you don't get any feedback that the thing even run at all.

I'm not necessarily saying to clutter the simple interface with a "line repeating the command that has just been inserted and then following it with a newline" like in a normal desktop CLI, but there should be some visual indication something happened.

Hello, @tytydraco @IzzySoft

I'm a big fan of FOSS, and it would be very helpful to me and to other FOSS enthusiasts, if you allow this application to be packaged for an alternate FOSS-only Application Repository.

Please note that, this would(and not can/may) put a dent on your Sales of 'LADB' on the Play Store Marketplace. 'LADB' would not be the first app which is Paid on Play Store, but free at F-Droid, like the "Librera Reader", "OsmAnd+", "FTP Server", and maybe more...

If you do not have any problem with all the above, then please have a look at this.

Thanking you...

Hey, i see you are using the very first available arm version compiled from Osmosis in the magisk repo 2 years ago (i was so thankful for it back then, after i learned that for cross compiling i need smth like Xeon with 32G ram and 500GB source code :) ) .

It seems things have moved a bit in these 2 years. There is a newer version in Termux in the android-tools package, and there is even newer and very current version from rendiix here

https://github.com/rendiix/termux-adb-fastboot

I think it's worth replacing, maybe will fix some weird problems with newer phones.

P.s. maybe you want to close/delete some issues to, from the 30 open probably 20 are spam or people that do not read the manual...

I thought that I had made mention of this previously but I don't see any mention of it in any issues or even comments so I could be wrong and if I'm not I don't know where I made mention of it but many times now when I've gone to use LADB instead of it trying to initiate wireless debugging on my phone (Google Pixel 6 Pro Android 13) It seems to somehow be communicating with my Pixelbook, which is obviously a completely separate device. I'm at a loss for why this is happening. I do have the Pixelbook connected to my Pixel via the Phone Hub feature/functionality of ChromeOS, but that's just connecting via Bluetooth as far as I know but even if it was connecting via a Wi-Fi connection or even over the network, I don't see why that would cause this to happen. Am I missing something or is this completely weird behavior?

I wanted to run a permission revoke command from this app and got 'neither user nor current process has android.permission.REVOKE_RUNTIME_PERMISSIONS' for example the command I was trying to run looked like pm revoke com.offendingapp android.permission.INTERNET there's a secure mode you can run ADB in that allows you to do such things

The wifi ADB needs a reset every time I restart the device. THe solution is to do a factory reset and reenter the port and wifi code, but I also lose the bookmarks in the process. Would it be possible to allow reseting the connection information without losing the bookmarks?

I have some minor issues ...

On my Android 10 there is an message that an error occurred while connecting automatically:

adb (true, listOf ("- t", "1", "shell"))

-t is unknown.

The second is maybe because of my misconceptions. I've created a couple of .txt files that contain one ADB command per line. If I cut out a command line from one of these .txt files and paste it into the Shell Command field, this ADB command will be executed correctly. I have now assumed that you can transfer these .txt files to LADB via share so that LADP executes these command lines one after the other. But that doesn't work. A new instance of LADB is started for each share, but not a single command is executed. Do I have wrong ideas or is it more of a mistake that is not intended?

Cant type commands iv tried all the things airplane mode even an apk online instead of playstore cant figure it out still trying though lmk what I can do I'm running android 11 on a tab s6

Awesome work. I'm running aosp_flame-userdebug S AOSP.MASTER. When the keyboard pops up to type in shell cmds, there's no return key; in it's place is the emoji keyboard button. This can be fixed by changing android:inputType="textNoSuggestions|textShortMessage" to android:inputType="textNoSuggestions|text" in activity_main.xml, for example.

Hi

Do you know ServerAssistant for android? Here you can send predefined commands to linux severs.

Here you can store commands on server based setup, to re-run commands easy

This would be a nice feature for your app.

Some commands are pretty long, and if you need to re-run them often, its very practical to have them stored.

Kind regards Requaero

As described by title, sometimes when I try to do the pairing, the wireless debugging screen indicates a successful pairing (and even may indicate there's a debugging connection), but LADB goes back to pairing mode instead of showing the terminal output. I don't know of a specific way to reproduce it, just seems to happen at random.

Meu dispositivo é um A02s , ja tentei de todas as formas usar o ladb mais sempre que eu coloco o código de pareamento é o codigo de porta é aperto OKAY ele apresenta essa mensagem, adb unknown command pair

I have been using this app for a very long time to enable ADB WI-FI in my Pixel 6 wirelessly without use of a PC.

But it looks like this stopped working since A13. Tried resetting but no luck.