Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On the device, Helper.apk
- Turns on WiFi if not already on.
- Checks and shows if the adb port was indeed opened.
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
UPDATE!!
A new tool I am calling "ADB Master" that includes all functionality of ADB-Over-WiFi-Helper plus a lot more is now also available for free to XDA users.
Get the new ADB Master here: http://forum.xda-developers.com/showthread.php?t=2707556
It is highly recommended to use the new download rather than the file attached to this post!
Thanks for this. Much appreciated. :good:
If you need an icon or Banner created let me know.
Nice work!
so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4
ADB over wireless
I think this will be a very useful application for anybody requiring to make changes when on the road, or away from one's main computer.
Running ADB over WiFi should be a great addition to anybody's 'tool kit', I for one, look forward to making use of this application.
Many thanks for bringing this to all of us at XDA.
Thank you!
this apps is awesome make adb over wifi easier
Nice
extremewing said:
Free for XDA members and as a thank you for all the information, tools and roms XDA Developers has provided over the years here is something I created that makes it easy to connect adb over tcpip to multiple Android devices. Get rid of the wires!
One click to switch adb on all usb connected devices to tcpip.
One click to switch adb on all tcpip connected device back to usb.
Auto discovery of the devices listening on tcpip.
The application consists of two parts. "Helper.jar" to run on the pc and "Helper.apk" for the device.
View attachment 2455389Helper.jar
- Installs the Helper.apk on the device.
- Attempts to switch adb on the device to use tcpip.
- Sends broadcast messages to look for devices on the network.
- Initiates an adb connection over tcp to any ip that responds to the broadcast.
- Provides a button to switch all usb devices to tcpip.
- Provides a button to switch all tcpip devices to usb which also uninstalls the helper.apk file, leaving no "junk" on the device.
View attachment 2455388On the device, Helper.apk
- Checks and shows if the adb port was indeed opened
- Listens and responds to udp broadcasts from Helper.jar.
Some android devices will work without root but if you get a red message from the helper on the device, you will need to root it to enable adb in tcpip mode. The rooted method to set adb to use tcpip is used in case the device is rooted.
If you like the tool and want to contribute, please feel free to buy the app on the Play store. The attachment contains exactly the same files for free.
Feedback is welcome and I hope someone finds this useful!
Adrian
Click to expand...
Click to collapse
Nice tool Bro :good:
Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.
rayjr13 said:
Thank you for the Christmas gift. I'm on HTC DNA and I am rooted but I get the red port closed message about root required.
No request for root occurs in supersu from this app.
Click to expand...
Click to collapse
Same issue here, on my rooted Xperia J. No entry regarding this apk's request for root is found in Super-SU's logs, whatsoever.
Wow, thanks for all the comments!
The helper on the device does not use or need su and ONLY does the following:
1) Checks if the adb tcp port was indeed opened on the device (by creating a tcp connection attempt to it)
2) Listens and then responds to a udp broadcast from the java app.
In future, it could do more.
All the work is done over the USB cable (or WiFi to switch back) using adb from the java app.
In essence, the java app executes the following abd commands to each device (both the "rooted" and non rooted methods are attempted each time):
To turn ON tcpip mode:
adb -s <devicename> tcpip 5555
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port 5555'
To turn OFF tcpip mode:
adb -s <devicename> usb
adb -s <devicename> shell su -c 'setprop service.adb.tcp.port -1'
Please explain a bit more what is happening when the red message appears?
Is the device connected over USB and appearing in the left hand list on the java app?
Perhaps post the output from the java app when you press Switch to WiFi.
darkmatthew said:
so now if i broke my USB port i can lock bootloader with this?Yes?
Nexus 4
Click to expand...
Click to collapse
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.
Thank you in advance for this very important tool!
extremewing said:
This app needs you to be able to first connect the USB and is intended to make it easier to work with lots of devices at the same time. For a rooted device without USB / damaged USB, any ADB to WiFi switching app on the play store should work to get adb onto WiFi and then, yes, you should be able to execute your required adb commands.
Click to expand...
Click to collapse
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.
spereree said:
I have a HTC One, 4.3 Sense 5.5, ( 3.62.771.3 ), and need to reset it back to stock. My USB port doesn't function when the phone is on.
(Works OK in fastboot mode) - and I need to be S-off, then S-on again (locked, remove tampared via revone, moonshine,
or rumrunner) but all those require USB adb. and I can't do that.
So I'll try this and let you know how it goes.
Click to expand...
Click to collapse
Please note, this app also requires USB ADB to start off.
Tried it...
extremewing said:
Please note, this app also requires USB ADB to start off.
Click to expand...
Click to collapse
OK, so I've tried it, and it seems like it can only pick up an ongoing ADB WiFi connection but I'm sure I'm doing something wrong.
Remember; I can't use USB debugging coz my usb doesn't work when the phone is on. so USB debugging is off, and there is no point using it. I'm using this as an alternative to restore back 100%.
(1) I pushed the apk file to the phone, using "WiFi File explorer pro"
(2) I installed it using "APK installer"
(3) Ran Helper.jar
(4) Opened an already installed WiFi ADB app on my phone, and established a connection (granted SU first)
(5) ran your app, "ADB over wifi helper" - it picked up the connection (showed green, " ... listening on port 5555 ... ", etc)
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Also, what is the use of the large text entry form below the "Searching" indication?
Again, thanks for this tool!!!
P.S. imagine a user trying to do what is said in this thread, but doesn't have a functioning USB port to use adb with, and has to result with your app (alongside another WiFi adb app) - This will fill the gap! as in ANYONE can recover / flash roms, etc, even if you have a broken USB port!!!
spereree said:
Back to the Helper.jar, all it does is saying "Searching - Hello to 255.255.255.255" "Timeout"
I was assuming it would have automatically connected it for me (say running a command like "adb connect ip.address:5555" )
or am I getting this wrong?
Click to expand...
Click to collapse
This is not wrong. After the helper.apk was running on the device, and showing you the port was open, the jar app should be able to discover it. Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
spereree said:
I kept the path to my android sdk
****Also, I used the mini sdk (It's quite popular, so I'm assuming most users will have this) and I'm missing the "platform-tools" folder. I just have fastboot and adb,exe and some dll files. So, can you provide a link we could get the required "platform-tools" folder alone? (zipped) ****
Click to expand...
Click to collapse
Just point the app to the folder containing the adb executable.
spereree said:
However, when I connect manually via command prompt, "adb connect ip.address:5555" the Helper.jar automatically detects it, and the option to Switch devices to USB appears (which I will not use, personally)
But the "Searching" cycle still continues.
Click to expand...
Click to collapse
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
spereree said:
Also, what is the use of the large text entry form below the "Searching" indication?
Click to expand...
Click to collapse
That is a log of what the app is doing
extremewing said:
Are both the pc and device connected to the same wifi access point, and that access point allows the two to talk? I assume so based on your later comments. What OS version?
Click to expand...
Click to collapse
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
Just point the app to the folder containing the adb executable.
Click to expand...
Click to collapse
So that means I've done that OK...
Searching will always continue. Something is either blocking the udp broadcast or the device is not allowing helper.apk to get them.
Click to expand...
Click to collapse
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?
spereree said:
I'm on Windows 8.1 x64
and both devices are on the same network (I'm using my PC as the hotspot via a program called connectify. I'm using a USB 3G dongle for internet.
So that means I've done that OK...
I believe that might be the problem, but I don't see where that issue comes from...
Also as an addition, When I connect adb over WiFi on my phone, and I list all devices, I see my phone (as an IP address) but with "unauthorized" next to it (please search on the this issue for more info)... This was a brick wall I hit, when I was trying to get my phone 100% to stock, to send it to repairs for my USB issue... MEaning I can't run any shell commands, etc... via ADB... I was hopping this app could find a way around that?
Click to expand...
Click to collapse
You have more than one thing going on here.
1) The program you mentioned "connectify" *may* be blocking the broadcast for discovery to work.
2) The "unauthorized" message is due to an out of date adb on the pc. You should upgrade to the latest version in order to connect to newer android devices. Note that you would also need to accept a permission prompt on the android screen.
3) I am also thinking you need to enable USB debugging for anything to work properly when executing adb commands (even over wifi with a faulty usb port).
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?
Hi, Thanks for the reply.
I'll try all the options and get back to you.
extremewing said:
4) If you get it back to stock, you may want to see if the USB issue you have is fixed.
5) You may also actually use fastboot to flash it back to stock?
Click to expand...
Click to collapse
As for getting back to stock, I would also love to remove the tampered and "unlocked"
warnings from the top, so that I can take it back to repairs under warranty.
So actually ADB over WiFi need to work flawlessly as if I connected the USB cable,
This is so that when rumrunner is run on the device, no problems should be encountered.
Even after multiple reboots (hence, this application should load ASAP when Android booted.)
This tool is so awsome.
Saved alot of time here.
Tyvm
New version out soon
Since there are nearly 1000 downloads, I was going to bring out a new version I've been working on and I wanted some feedback or thoughts about what you would like to see.
The new version at the moment will give you these new features in the JAR app:
- Improved: device lists that will allow you to multi-select devices to perform actions on
- New: list of all apps on all devices (replaces the "console" at the bottom)
- New: Install an APK from your PC onto all selected devices
- New: One click uninstall of multiple apps on all selected devices
- New: One click enable / disable of multiple apps on all selected devices
Is there anything else one would want to do on all devices?
Hi All,
I have been trying for hours (more than a week actually all in all) to sideload apps to my Lg Smart Watch Sport.
I have found more than one thread that speaks to how to achieve this and I have followed to a T as far as I know.
I have ADB and Fastboot installed and when I enter adb devices it shows my phone is connected.
Each time I follow the script after the adb connect localhost:4444 script I get the message 'no connection could be made because the target machine actively refused it (10061)'
I have debugging and bluetooth debugging on my Sport and phone has debugging as well.
I have tried the Android Wear APK Tools app as well and it just say error, cannot install.
I am using a MI Mix in case it matters.
Im not sure if the problem is my computer (Windows 10) or the Mi Mix but I have hit a dead end.
Anyone out there that can help I would sure appreciate it!
Best source is this: https://developer.android.com/training/wearables/apps/debugging.html
Edit: on the first connection with "adb devices" you should get a dialogue on your watch asking for authorization
ranf said:
Best source is this: https://developer.android.com/training/wearables/apps/debugging.html
Edit: on the first connection with "adb devices" you should get a dialogue on your watch asking for authorization
Click to expand...
Click to collapse
I have been trying for days to get this to work and that tutorial got me up and running.....I cant thank you enough.
make sure you open Command Prompt with Admin privileges.
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I am having the same issue. ADB will not work at all with this tablet
Same here
I have the same problem; enabling USB debugging in the Developer Options menu does not seem to have any effect. Closing the settings app and restarting it results in the option being switched "off" again.
This on an unrooted, locked stock device with EMUI version 5.0 / Android 7.0
Weird ....
shamm1987 said:
I can't seem to get the authorization pop up to allow adb to work. I have usb debugging enabled and adb shows the device as offline when using the command adb devices. Has anyone else experienced this issue before or have any way to fix it?
Click to expand...
Click to collapse
I work around this by enabling usb debugging, going into another setting menu option, then back to developer options, disabling it, enabling it, adb kill-server, adb devices, trying different combinations and eventually it works.. It's a real pain but eventually it works. Once the computer is trusted I don't need to do this anymore.
Is adb not able to connect over even see these Joying FYT Airmont units with Oreo on it?
The head unit has a switch to allow debug over usb but when I connect a usb to my laptop I don't get the dialogue screen on the head unit asking if I want to connect to this device and the laptop cannot see the unit at all.
I figured maybe it needed device specific drivers in Windows so figuring Joying hasn't made any I found universal usb drivers for it. Nothing.
I got an app called Naptime or something that's supposed to be able to put the unit in full doze. It's designed to work on rooted devices but also says that can be worked around by using adb to give certain permissions. I can't do that if I can't even connect adb to the damn thing.
Also, is rooting these using that Magisk method result in the same type of full root the normal way on other devices? It isn't limited compared to the normal way is it?
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
Click to expand...
Click to collapse
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
rigattoni said:
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
Click to expand...
Click to collapse
These commands require root
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
Click to expand...
Click to collapse
Maybe I'm doing something wrong then. The developer options are enabled and I have it set for unlocked bootloader but my laptop can't see it whether I'm connected through the OTG usb port or the standard one and the HU doesn't give the popup dialogue asking if I want to allow the connection like my tablet and phone did. Maybe they changed something with these particular units with the new UI?
I did notice on another thread someone that had a FYT Joying Airmont with 8.1 and they said something about the 3 dot menu on the top right for "USB Connection" that brings up two options both in Chinese an his only worked on the lower option. I did try that too but still nothing. IDK. Maybe I had something else set wrong when I tried that lower option that made it not work in all my effort yesterday to get adb to see it and connect.
Hello - I'm trying to set up remote access of my android head unit to monitor system vitals remotely.
I have an Xtrons head unit (MCU Version: T8.3. 19-94-14-E06101-190118) and am struggling to get any remote access Apps to function fully. Apparently, I need to enable a setting on the accessibility setting, but I can't find these?
Nearly all apps (Team Viewer, etc) allow the connection and allow me to move a mouse around the screen however non allow me to 'click' remotely. The App AnyDesk has been the most helpful with their development team providing access to a universal plugin that will supposedly enable the functionality, however it requires access to the device's accessibility settings. Does anyone know how to access this?
The below post raised a simial question but remained unanswered: https://forum.xda-developers.com/an...essibility-settings-lost-android-8-1-t3906920
Android Version:
8.1.0
MCU Version:
T8.3. 19-94-14-E06101-190118
System Version:
V9.3.1_20181128.105007_HC2-FD
https://www.dropbox.com/s/znppnvmt1jc5pha/IMG_4652.PNG?dl=0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dale_oxford said:
Hello - I'm trying to set up remote access of my android head unit to monitor system vitals remotely.
I have an Xtrons head unit (MCU Version: T8.3. 19-94-14-E06101-190118) and am struggling to get any remote access Apps to function fully. Apparently, I need to enable a setting on the accessibility setting, but I can't find these?
Nearly all apps (Team Viewer, etc) allow the connection and allow me to move a mouse around the screen however non allow me to 'click' remotely. The App AnyDesk has been the most helpful with their development team providing access to a universal plugin that will supposedly enable the functionality, however it requires access to the device's accessibility settings. Does anyone know how to access this?
The below post raised a simial question but remained unanswered: https://forum.xda-developers.com/an...essibility-settings-lost-android-8-1-t3906920
Android Version:
8.1.0
MCU Version:
T8.3. 19-94-14-E06101-190118
System Version:
V9.3.1_20181128.105007_HC2-FD
https://www.dropbox.com/s/znppnvmt1jc5pha/IMG_4652.PNG?dl=0
Click to expand...
Click to collapse
I have been given the following advice from Xtrons (the device reseller), as they say, the model is now discontinued and won't forward on any support inquiries to the manufacturer.
"After entering "adbon "in the factory set and opening ADB, you can apply on the machine by yourself directly."
Does this mean "adbon" is the password to access the factory settings, or are they saying that I need to set up an ADB connection to the HU via a computer?
Many thanks
dale_oxford said:
I have been given the following advice from Xtrons (the device reseller), as they say, the model is now discontinued and won't forward on any support inquiries to the manufacturer.
"After entering "adbon "in the factory set and opening ADB, you can apply on the machine by yourself directly."
Does this mean "adbon" is the password to access the factory settings, or are they saying that I need to set up an ADB connection to the HU via a computer?
Many thanks
Click to expand...
Click to collapse
ADBON is the password for the factory settings, to get ADB activated... but this does not allow you to edit the accessibility settings, because the entry is hidden by manufacture.
With activating ADB on your device you are able to run console commands on your PC via ADB on your unit.
Code:
adb shell settings put secure enabled_accessibility_services [package name/service name]
You can try the app "Accessibility Settings Shortcut" app from play store. But I guess you have to activate it after each reboot.
If your unit is rooted you also can use Tasker with Secure Settings app to get this done on each boot.
rigattoni said:
ADBON is the password for the factory settings, to get ADB activated... but this does not allow you to edit the accessibility settings, because the entry is hidden by manufacture.
With activating ADB on your device you are able to run console commands on your PC via ADB on your unit.
Code:
adb shell settings put secure enabled_accessibility_services [package name/service name]
You can try the app "Accessibility Settings Shortcut" app from play store. But I guess you have to activate it after each reboot.
If your unit is rooted you also can use Tasker with Secure Settings app to get this done on each boot.
Click to expand...
Click to collapse
Hello Rigattoni,
Thank you so much for this advice. I’ve installed a number of ‘Accessibility Settings Shortcut’ apps from the PlayStore as some seemed incompatible. This has allowed me to many system changes but hasn’t solved the problem.
Do you know what specific setting the AnyDesk plugin is asking to be modified? I’ve looked through all of the settings I can but can’t see what it would need? I would very much prefer that I don’t have to ADB the device as I am MAC only and have no experience in performing this task.
Where would the AnyDesk Control Setting be within the accessibility settings?
Below are a few photos which might help:
1 - MCU Version.
2 - What the application requires to run (prompt).
3 - Application error (on opening).
https://i.ibb.co/mNwC1pP/IMG-4665.jpg
https://i.ibb.co/gSYjRcL/IMG-4652.jpg
https://i.ibb.co/C66FCY2/IMG-4653.jpg
On a separate note, I found in the setting that I could run my HU as a higher resolution and now it looks a lot better!
@dale_oxford,
Sorry I don´t use this AnyDesk application, so no advice possible from my side.
ADB is available for MAC too... so if you want to get this fixed....
Assuming the setting is persisted, you just need to do it once.
Laptop and unit just need to be in the same WiFi network and ADB available on your laptop.
Setup instructions --> https://www.xda-developers.com/install-adb-windows-macos-linux/
rigattoni said:
@dale_oxford,
Sorry I don´t use this AnyDesk application, so no advice possible from my side.
ADB is available for MAC too... so if you want to get this fixed....
Assuming the setting is persisted, you just need to do it once.
Laptop and unit just need to be in the same WiFi network and ADB available on your laptop.
Setup instructions --> https://www.xda-developers.com/install-adb-windows-macos-linux/
Click to expand...
Click to collapse
Thank you.
I appreciate that you may have no experience with the particular App, but I too have limited experience with Android. I hoped that with your experience you may have a gut feeling as to what the dialogue box was advising?
I’ve read though this tutorial and wanted to check something before proceeding:
1. Will a USB to USB cable work ok as both devices (laptop and the HU) only have female connections? Hopefully this will work without additional software?
2. In the code that you provided, where can I find the specifics which you listed as options? What is the “package name/ service name”? adb shell settings put secure enabled_accessibility_services [package name/service name]
Can you please direct to me some of the commands which would be applicable in solving this problem maybe?
Many thanks,
Dale
dale_oxford said:
Thank you.
I appreciate that you may have no experience with the particular App, but I too have limited experience with Android. I hoped that with your experience you may have a gut feeling as to what the dialogue box was advising?
I’ve read though this tutorial and wanted to check something before proceeding:
1. Will a USB to USB cable work ok as both devices (laptop and the HU) only have female connections? Hopefully this will work without additional software?
2. In the code that you provided, where can I find the specifics which you listed as options? What is the “package name/ service name”? adb shell settings put secure enabled_accessibility_services [package name/service name]
Can you please direct to me some of the commands which would be applicable in solving this problem maybe?
Many thanks,
Dale
Click to expand...
Click to collapse
Dale,
you need to use WiFi for it.
Get the unit to exact the point with the error message.
Open the Commandline Box in the ADB folder and type:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
ADB shell
top
You will get some output in the CMD.
press the "q" on your keyboard to quit the refresh of the CMD.
Post a screenshot of the CMD in here.
Hopefully we can find the name of the needed accessibility.
If we found the name you just connect again both (laptop and unit) to the same WiFi, open again the CMD on your laptop and use the following commands:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
adb shell settings put secure enabled_accessibility_services [package name/service name] <-- The package name of the app without brackets.
exit
exit
rigattoni said:
Dale,
you need to use WiFi for it.
Get the unit to exact the point with the error message.
Open the Commandline Box in the ADB folder and type:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
ADB shell
top
You will get some output in the CMD.
press the "q" on your keyboard to quit the refresh of the CMD.
Post a screenshot of the CMD in here.
Hopefully we can find the name of the needed accessibility.
If we found the name you just connect again both (laptop and unit) to the same WiFi, open again the CMD on your laptop and use the following commands:
Code:
ADB connect 192.***.***.*** (put in the IP-Address of your unit instead)
adb shell settings put secure enabled_accessibility_services [package name/service name] <-- The package name of the app without brackets.
exit
exit
Click to expand...
Click to collapse
Hi - Thanks for this this looks great. I haven’t been able to try this yet as I’ve been away from my car.
in the meantime I’ve done a little research into this and my understanding was that I would still need to initially do a USB connection in order to activate the ADB mode. Please have a look at the attached tutorial:
https://futurestud.io/tutorials/how-to-debug-your-android-app-over-wifi-without-root
Are you saying that I can connect via Wi-Fi without having to use a USB cable in the first instance or will I still need to do this? If so with a USB male to male cable work given that both my computer and the android headset have female connectors?
dale_oxford said:
Hi - Thanks for this this looks great. I haven’t been able to try this yet as I’ve been away from my car.
in the meantime I’ve done a little research into this and my understanding was that I would still need to initially do a USB connection in order to activate the ADB mode. Please have a look at the attached tutorial:
https://futurestud.io/tutorials/how-to-debug-your-android-app-over-wifi-without-root
Are you saying that I can connect via Wi-Fi without having to use a USB cable in the first instance or will I still need to do this? If so with a USB male to male cable work given that both my computer and the android headset have female connectors?
Click to expand...
Click to collapse
Once again...
You are not able to use a female/female USB cable to get connected to your unit as there is not real OTG available on the unit.
You need to use WiFi as I wrote.
It works exactly the same way.