If you connect via usb, then use adb tcpip 5555 you can connect over wifi until you reboot/disconnect (at which point you have to reconnect to usb again).
Is there a way of connecting over wifi without needing that initial connection? I'm used to slimroms where you only need to connect to usb once ever (for security reasons).
I've tried some of the `no root` apps but they don't work.
Please leave the development section free for development threads
Questions belong in the Q&A section
Thread moved
I'm late to this thread, but luckily, as of non-rooted Android 11 and up, adb works over wi-fi (without USB) on non-rooted Android phones via Developer options Wireless debugging switches.
Related
Hi all,
I have been testing the wonderful ROMs for Inspire 4G, for example
AoCP: http://forum.xda-developers.com/showthread.php?t=2334107
moProject42: http://forum.xda-developers.com/showthread.php?t=2354076
I have 2 issues that I'd like to resolve. I would have posted in those threads, but I'm not allowed as a new user to this forum.
1. In both cases, after updating to the 4.2.2 ROM, I have not been able to shell in from my Win7 32bit laptop using ADB, as the device shows up as offline.
[Sat Sep 14 13:09:13 ~] $ adb devices
List of devices attached
HT19GT202387 offline
On the phone, my laptop's RSA Key was shown, and I accepted it, but it never seems to come online.
I have tried all the usual methods to try to fix this:
- upgraded my SDK and Google USB drivers for 4.2.2
- turn ADB debugging off/on on the device
- pull out/plug in the device
- Delete and reinstall the USB drivers on the laptop
2. After turning on Portable WiFi Hotspot, my 3G connection dies, so any devices that successfully connect to the hotspot are unable to browse the web.
Also, the device itself can no longer use 3G until I turn off the hotspot, and reboot the phone.
Any ideas? Thanks in advance.
Q&A for [GUIDE] HOW TO Enable Wi-Fi Tether on stock Kit Kat 4.4.2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GUIDE] HOW TO Enable Wi-Fi Tether on stock Kit Kat 4.4.2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
thread: [GUIDE] HOW TO Enable Wi-Fi Tether on stock Kit Kat 4.4.2
riceknight said:
Doesn't seem to work for me. Tried using my tablet connected to foxfi hotspot and got the usual T-Mobile error notice that hotspot isn't enabled when I opened the browser.
Click to expand...
Click to collapse
This worked for me on my stock non rooted tablet to get wifi tethering operational
Enable developer mode (Go to Settings -> About phone, and click on the build number until the developer mode is enabled 7 times?).
Enable USB debugging under Settings -> Developer options
Connect the device with a USB cable to a computer with the Android SDK platform tools installed
Start an adb shell: adb shell
( in windows 7 start command prompt as administrator, cd to the directory with adb in then run the command adb shell)
(if get unauthorized device error connect and disconnect USB cable and turn off and turn on USB debugging until the authorisation for the PC dialog box appears then OK)
In the adb shell, run this command: settings put global tether_dun_required 0
Access point was then operational and could see the password in the settings
Hello, another question in quick succession.
I have used the installer featured in this topic: http://forum.xda-developers.com/showthread.php?t=2588979 - to install all the necessary drivers so I can connect my phone through USB and hopefully install Android 5.1 onto my phone.
I went through every step in the topic and ADB Composite Device appear listed. My phone is also definitely connected as I check for 'adb devices' in command prompt. However, when connected in fastboot mode, it still asks to Connect to USB Device. USB Debugging has been enable on my device, also.
Help would be much appreciated! I'm new to this so it's a teensy bit of a rigmarole.
Could really do with help here, I'm stalling on it and it's bugging me - wanna get it sorted.
Hello, I have little problem. I'd to debug my phone via WiFi so I have done this few steps:
adb tcpip 5555
adb connect <hereMyIp>:5555
unplug phone
And device disconnect from wifi adb, also I have turned on dev ops and it's work when phone is connected but when not no.
I tried this same to second phone and it's works fine so problem is with EMUI, anyone solve it ?
(Android 7.0 EMUI 5.0)
I have the same problem...
I solved problem on my Honor 8:
In developer options 1) turn on "Allow USB debugging", 2) turn on "Allow ADB debugging in charge only mode" and 3) turn off "Always prompt when connecting to USB".
Then do usuall steps:
1. adb tcpip 5555
2. adb connect <ip>:5555
3. unplug phone
So ADB over WiFi works!
Found this solution here:
https://forum.xda-developers.com/mate-9/help/udb-debugging-wont-stay-t3711939
In my case, it shows connected, but when I debug my application, all of a sudden it gets disconnected.
I solved the problem when I moved to Android 11 which has a new Developer option for Wireless debugging which enables adb to work completely over Wi-Fi with Android (no USB cable needed).
If a device has no root, what ADB commands can I use to connect that device to WiFi? I need to be able to input SSID name, password, static local IP, DNS, etc. - all over ADB and without root.
I am not talking about ADB over WiFi over TCP port 5555. I am talking about connecting an Android device via USB cable and the connecting that Android device to WiFi, assuming the device has no WiFi networks added.
To bring up Android's Wi-Fi Settings via ADB you run
Code:
adb devices
adb shell "am start -a android.settings.WIFI_SETTINGS"
I'm not sure I understand the OP's question where it matters greatly whether the OP is on non-rooted Android 10 and below or non-rooted Android 11 and above.
Non-root Android 11 and above no longer needs the USB cable for adb to connect between Android and the PC via Wi-Fi.
There's more information here...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
(PSA) Using the new Android 12 TILE for 'Developer options' 'Wireless debugging' to establish adb connection over Wi-Fi without USB
What's the difference between Windows/Android adb "connect" versus adb "pair" when mirroring Android 12 over Wi-Fi onto a Windows PC?
some newer devices, like Samsung will let you use cmd binary.
So to connect to network look at "adb shell cmd wifi"
Currently, it's somethig like $ adb shell cmd wifi connect-network bssid passphrase network_type