I'm having problems where wireless ADB is interfering with PDAnet USB tethering. I don't have a wireless ADB app downloaded, so turning this function off isn't as simple as going into some fancy User Interface, and disabling the feature. It is built into the ROM, apparently. Question is, how is it implemented, and how can I manually turn it off? I never have used the feature. I use PDAnet fairly often, but since installing this ROM, I haven't been able to maintain a steady connection due to wireless ADB initiating without my asking it to.
Anybody have any advice as to how to manually turn this off? Any system files I can edit?
Any help is greatly appreciated.
OK, I did a bit more digging around (Google searches), and found something from another site that looks potentially promising.
They advised that to set adb to use USB connection only to enter this command from terminal:
setprop service.adb.tcp.port -1
stop adbd
start adbd
I have done this, but have not yet had a chance to test it out. Can anyone familiar with wireless adb implementation confirm this command and its purpose?
Thanks again! Will report back once I get a chance to try it out.
EDIT: This doesn't seem to have made any difference. Still dropping my connection shortly after establishing it.
Sent from my ADR6400L using XDA App
boostjunky,
i dont have the same phone as you, but thought i would throw out a few suggestions.
are you opposed to installing adb wireless and disabling it via the app? i got it as a free app from the market.
if so, can you use a root uninstaller and delete the functionality from your rom's system folder?
Pj
Phoenix
Related
i get connection refused when trying to connect, is this normal or am i doing something wrong, telnet worked fine before i upgraded to this build
I have same issue. Frustrating. I've seen the response in another thread that you can still connect from your PC and run shell commands (so you still have root) but honestly there isn't anything I can't do right on the device in telnet and I really miss it. The Haykuro G supposedly has telnet, just the H doesn't.
Copying files between sdcard/apps storage, renaming and deleting, cleaning up the . Heck I even got my enterprise WPA network access at work running using Vi.
Not to mention it's a hassle having to be plugged in to my machine to do any mod work.
I can install telnet on the device ok and it launches, but I can't connect. Anyone have an alternative client that might work?
deslock said:
I have same issue. Frustrating. I've seen the response in another thread that you can still connect from your PC and run shell commands (so you still have root) but honestly there isn't anything I can't do right on the device in telnet and I really miss it. The Haykuro G supposedly has telnet, just the H doesn't.
Copying files between sdcard/apps storage, renaming and deleting, cleaning up the . Heck I even got my enterprise WPA network access at work running using Vi.
Not to mention it's a hassle having to be plugged in to my machine to do any mod work.
I can install telnet on the device ok and it launches, but I can't connect. Anyone have an alternative client that might work?
Click to expand...
Click to collapse
its good to know that im am not alone.
Wireless ADB is great, and a handful of apps already exist, but I got sick of typing 'adb connect .....' and firing up the wireless ADB app every time I reconnected to my wifi. I put together the 'Easy ADB' app, which allows individual networks to be white-listed for automatic wireless adb. The app also comes with a script to connect to the device from a computer using the host name rather than ip address. Of course, root is still a requirement.
Easy ADB is available on Google Play.
Hope this app can make someone's life a little bit easier. Of course, any feedback is appreciated.
I wanted to strip a phone down to it's bare necessities so it would fit into a laptops spare hard drive slot to be used as an 3G modem (provider only allows phones to use unlimited plans).
If I remove the screen will it still function enough to be commanded via ADB?
The screen is just an output device, so you should still be able to give it commands remotely, similar to a rasberry pi, but how would you enable usb debugging and/or troubleshoot issues that may arise with the device?
syung said:
The screen is just an output device, so you should still be able to give it commands remotely, similar to a rasberry pi, but how would you enable usb debugging and/or troubleshoot issues that may arise with the device?
Click to expand...
Click to collapse
I'd enable debugging beforehand, the idea was to just toggle tether via ADB, nothing major so the only issue I could think of would be heat, but shouldn't be an issue hopefully.
Possible.
Sent from my WT19i using xda premium
If I Have Helped You Can You Press
.
.
THANKS BUTTON
.
.
To support Me.
The amazon fire devices are a little weird. I currently have them integrated with home assistant through ADB. The problem I am running into is that if the ADB connection is lost from my computer to the firetv, then either the ADB debugging needs to be toggled in developer options, or I can restart the firetv itself. If the ADB connection is lost then some of my automations and controls do not work on home assistant.
Couple things:
I am willing to root the device
If I cannot toggle adb debugging, I could just reboot the device. I have considered using a smart plug to do this, but I would rather let the fire handle it.
Would tasker or termux be an option? I've considered moving ADB from the computer server to termux with https://github.com/MasterDevX/Termux-ADB, but I am not sure that would be more reliable.
Basically I want to toggle ADB debugging or a reboot on a set schedule (eg. every night @ 4am).
Hi Moosefist
Parhaps this might help you toggling the ADB based on a schedule:
App: Automate playstore link
The app Automate let you create a schema flow where you can specify what your device should do. For example, turn off bluetooth when connected to wifi network XYZ if time is greater than 10pm.
I think even that it doesn't require root, but I am not sure since mine it rooted anyway...
Hi , I have made an app that enables you to connect 2 your phone wirelessly, using ADB. The app opens port tcp port 4774 n showcasesthe command needed to connect the device, the app also showcases the devices IP so you don't have to look it up, root is required 4 the root method. There are also premium versions available which remove adds, two are obtainable UnLockKkAyyy which should also unlock any other apps w/ it in the description, if they ever might be released n Start ADB Over Wi-Fi Unlocker which should only unlock this app.
Google play LiNKs:
Start ADB Over Wi-Fi [Root]
Start ADB Over Wi-Fi Unlocker
UnLockKkAyyy
This should be about it for now .
Reserved...
Reserved...
What's great is the OP is helping people connect rooted Android to PC adb completely wirelessly (without the initial need for the USB cable), where I'd like to ask the kind-hearted developer if he knows of a Windows PC networking command that we can run from the PC which tells us which port is being used for that adb connection.
More details on WHY I ask that question are over here...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Bearing in mind I'm NOT ROOTED (and my phone can't be rooted); so that's why I ask for help in determining the random Developer options Wireless debugging port after the fact...
I think I am missing the point of this app. Isn't ADB over WiFI a standard feature of android, under developer options?
>>>>:>>
GalaxyA325G said:
What's great is the OP is helping people connect rooted Android to PC adb completely wirelessly (without the initial need for the USB cable), where I'd like to ask the kind-hearted developer if he knows of a Windows PC networking command that we can run from the PC which tells us which port is being used for that adb connection.
More details on WHY I ask that question are over here...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Bearing in mind I'm NOT ROOTED (and my phone can't be rooted); so that's why I ask for help in determining the random Developer options Wireless debugging port after the fact...
Click to expand...
Click to collapse
You could try brute forcing it in CMD.
DiamondJohn said:
I think I am missing the point of this app. Isn't ADB over WiFI a standard feature of android, under developer options?
View attachment 5676389>>>View attachment 5676391>:>>View attachment 5676393
Click to expand...
Click to collapse
I don't think it was out while I was making it, I think is random and I prefer a static port.
Dev.4.fuN said:
Basically I don't think it was out while I was making it, I think is random and I prefer a static port.
Click to expand...
Click to collapse
The first post is from 2021, I definitely basically have used it well before that. However I do use custom ROMs. And as I implied it’s already there. One of the big concepts of Android OS is to use what’s there, not add on , which is basically a duplication.
DiamondJohn said:
The first post is from 2021, I definitely basically have used it well before that. However I do use custom ROMs. And as I implied it’s already there. One of the big concepts of Android OS is to use what’s there, not add on , which is basically a duplication.
Click to expand...
Click to collapse
Static port, so it's not.