MD set Mobile Data tile off but connection still on
- Thread starter solquest
- Start date
Turning off battery optimization didn't change much...
So I wanted to do that test, but when running adb tcpip 5555 I got the message 'error: more than one device/emulater' (tried twice, same error):
As I was saying, I'm not on a private wi-fi and I've just seen my IP changes everyday (or something like that).
But given that if I run 'adb tcpip 5555' macro just before setting mobile data on or off, it works, I can simple run those two macros one after the other one, no?
The issue I see is that for having success with 'adb tcpip 5555' macro I guess I have to be connected to Wi-FI and I'm not always connected when I want to turn mobile data on or off...
So I wanted to do that test, but when running adb tcpip 5555 I got the message 'error: more than one device/emulater' (tried twice, same error):
As I was saying, I'm not on a private wi-fi and I've just seen my IP changes everyday (or something like that).
But given that if I run 'adb tcpip 5555' macro just before setting mobile data on or off, it works, I can simple run those two macros one after the other one, no?
The issue I see is that for having success with 'adb tcpip 5555' macro I guess I have to be connected to Wi-FI and I'm not always connected when I want to turn mobile data on or off...
Endercraft
Moderator (& bug finder :D)
It seems to be caused by the ADB shell plugin ? I just tried setting it up in Termux and it worked fine until I enabled tcpip. Try rebooting.
The "more than one device/emulater" is more likely to appear after many attempts. It is an error that the program does not know which device to command because multiple devices are connected.
In nmap.sh, there is a workaround for this kind of situation, so it should be easy to succeed.
It is possible to work around it if you do everything manually, but it is tedious to type long commands, so rebooting as @Endercraft said is quicker.
It may be difficult to automate the process since there are some puzzling phenomena such as adb tcpip 5555 becoming 555. We can only verify that it works in a typical home Wi-Fi environment, so it may be difficult to get it to work in your environment.
If possible, run adb tcpip 5555 with a USB connection to your PC and verify that it works with the plug-in. If this does not seem to work, we are out of luck.
In nmap.sh, there is a workaround for this kind of situation, so it should be easy to succeed.
It is possible to work around it if you do everything manually, but it is tedious to type long commands, so rebooting as @Endercraft said is quicker.
It may be difficult to automate the process since there are some puzzling phenomena such as adb tcpip 5555 becoming 555. We can only verify that it works in a typical home Wi-Fi environment, so it may be difficult to get it to work in your environment.
If possible, run adb tcpip 5555 with a USB connection to your PC and verify that it works with the plug-in. If this does not seem to work, we are out of luck.
Endercraft
Moderator (& bug finder :D)
I happened to me too but only when getting the error (you can use 55555 instead).
Thanks guys this workaround works on a Xiaomi smartphone. I have a question. Are there other scenarios which necessitate to rerun the adb tcpip command apart from a reboot? As in situations which would cause the tasker plugin not to work and I would need to run the adb tcpip command again to make it work?
Thanks alot
Endercraft
Moderator (& bug finder :D)
Apart from reboot the only case where you'd need to run again is if you run
adb usb.