Wifi ADB debug mode lost on restart?

[Endercraft]

Copy nmap.sh

Where did you get the nmap.sh file from ?

 

[Dimlos]

Here is the script I wrote.

https://www.mediafire.com/file/03869ly4rq9h7gl/nmap.sh/file

 

[Dimlos]

The nmap.sh is something I managed to get working by trial and error, so if you have a better way, please suggest it.
I see that several people have downloaded this script, if you don't mind, please let me know what you think.

 

[Christoph]

@Dimlos thank you very for all these detailed steps !

Install FX File Explorer.

Connect to Storage
Select Termux
USE THIS FOLDER
Show Hidden
Copy nmap.sh

I have completed all these steps, successfully.

Wireless debugging
Use split screen
Pair device with pairring code
adb pair 192.168.0.xx:xxxxx
Enter pairing code:xxxxxx

Here I first thought you were talking about the Wireless debugging option in the Android Developer options, but from the picture I see it is not the case. In which app did you take these screenshots ? Is It FX File Explorer?

 

[Dimlos]

Are you talking about a split display?

 

[Dimlos]

Developer options > Wireless debugging > Pair device with pairring code

 

[Dimlos]

Pair device with pairring code requires screen splitting because IP and port will change when switching screens.
Some devices omit screen splitting, so in such cases, please use the application to split the screen.

 

[Christoph]

Developer options > Wireless debugging > Pair device with pairring code

I get it now, I did not, I had never seen that 'Wireless debugging' has a setting display behind. I was spoiled by 'USB debugging' having to setting display behind.

 

[Christoph]

Wireless debugging
Use split screen
Pair device with pairring code
adb pair 192.168.0.xx:xxxxx
Enter pairing code:xxxxxx

I have done this successfully.

operation check.

chmod +x nmap.sh
./nmap.sh

Contrary to what happens for you, I do not have any output after running nmap.sh

 

[Christoph]

Termux permission allow

MacroDroid app info
Run commands in Termux environment

I have done it successfully

 

[Christoph]

Then start from the macro and check the operation.
If a success popup appears, ADB Shell [Tasker Plugin] should now be available.

When I run the script, I have this pop-up :

and then nothing happens, I neither have the success, not the fail pop-up.

Here is what I have in the System Log :

 

[linamorar]

When I run the script, I have this pop-up

this is the adb pop up if you do not allow adb will not work

 

[Christoph]

this is the adb pop up if you do not allow adb will not work

I have not precised, but I have each time clicked on Allow.

 

[Endercraft]

Worked for me. I have one problem however that may be related to my device but I can't configure any plugin action. The action resets every time I click OK.

 

[Dimlos]

Check Always allow on this network and tap Allow, and the dialog should not appear every time.

 

[Dimlos]

@Christoph
First, run it from Termux and get it working before moving on to the next step.
I will upload an image of the successful result.

 

[Dimlos]

@Endercraft
Plugin action? Which setting?
Basically, it's already set up, so you shouldn't have to play with it.

 

[Dimlos]

I will reply when I have time.
If you have any questions, please write to me.

 

[Endercraft]

@Endercraft
Plugin action? Which setting?
Basically, it's already set up, so you shouldn't have to play with it.

Just any plugin. It's not the only affected action however.

 

[Dimlos]

@Endercraft
I am not sure what the problem is, but is there an easy way to reproduce it?
If it is caused by wireless debugging being on, it is possible to turn it off.
We have started the script and checked the operation with ADB Shell [Tasker Plugin], and the problem is not particularly problematic.