So I'm following the instructions exactly how they're written on Google's documentation and my Gear Live keeps showing up as offline. I've rebooted both the phone and watch multiple times and reconnected bluetooth but it still shows offline.
Here's what I'm typing in:
adb forward tcp:4444 localabstract:/adb-hub
adb connect localhost:4444
adb devices
shows locahost:4444 as offline.
Nevermind, I'm an idiot. If you go into the setting within Google Now on the device, there's an option enable USB debugging and debugging over bluetooth.
Related
My Laptop running XP SP3 has an issue with the Nexus USB driver.
It worked great since Jan, but yesterday adb started getting disconnected sporadically. Now my laptop freezes every time I plug in the N1. The mouse gets stuck and it does not allow keystrokes either. The instant I unplug the phone it goes back to normal.
I sometimes get the device not recognized icon before it freezes.
Here is the system error from event viewer, it repeats.
Code:
The description for Event ID ( 6 ) in Source ( USBSTOR ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: \Device\000000da.
What I have tried:
Disable/enable usb debugging
Restart the phone, Restart the PC
Using other USB ports
Deleting all the USB root hubs and restarting
Disabling USB debugging and plugging it in, still gets stuck
deleting the adb, composite, nexus devices using USBDeview
deleting the keys corresponding to the two vendor/device ids from teh registry, restart and the reinstall the driver.
Dont know if its related but I added the device IDs for the Droid-Incredible to the driver .inf and successfully used it two days ago.
Another change was the installation of XP SP3 a week ago.
I think the next step is to delete all the Nexus driver files and reinstall them...
Anyone else experience this?
updates:
Followed this and deleted all teh "unknown devices" under USB Controllers. Now the USB mass storage mode works, still gets stuck when I turn on usb debugging
Deleted all the non connected Google/Nexus devices under "Disk Drives" too. Next I connected the N1, it froze for a few seconds, showed both "new device" and "device error" icons...
works a few times.... then bluescreens.
still hangs, BSODs.... can hardly develop as my laptop spends most of the time restarting when I try.
Heres the text from the article that helped...in case it goes down.
To get rid of that unwanted driver, device, or service:
1) Open the “Start” menu and choose “Run…”
2) Type in “cmd” (without the quotes) and click “ok”.
3) At the cmd prompt, type in “set devmgr_show_nonpresent_devices=1″ (without the quotes) and press enter. (Note that nothing seems to happen–this is ok. We are actually setting an environment variable which is going to help us to see hidden devices)
4) On the next cmd prompt line, type in “devmgmt.msc” (without the quotes) and press enter. This will launch the Windows Device Manager Console.
5) In the Device Manager Console, from the “View” menu, select “Show Hidden Devices”.
Now, as you expand the different drivers and devices in device manager you will see not only the items that Windows currently detects as installed on your pc (these are the usual items displayed), but you will also see drivers, devices, and services which have been loaded in the past but were not uninstalled or are not currently started. You can find your offending device, right-click, and choose “uninstall” to remove it from the system completely.
Click to expand...
Click to collapse
Heres an official howto on installing the ADB driver.
http://developer.android.com/sdk/win-usb.html
I think it has something to do with XP SP3 that was isntalled recently.
Any more suggestions other than the ones I've tried above?
Going to try and get this 3 year old laptop replaced asap.
i'm 99.9% sure this is due to a bad usb cable.
Who would have thought!
My sons got two hd+'s for xmas and I'm in the process of attempting to connect through adb, which I have done many times with v various phones, yet when I plug the nook in I hear and see it connect and then immediately disconnect over and over again. Ideas?
It seems its only when I'm in usb debugging mode. Both are doing it.
I've rooted, installed GAPPS and so on many Nook HD+ tablets; most for my friends, since they have no idea how to do it. I've noticed this problem occurs due to the Nook not being installed correctly in ADB mode.
What I would recommend is going into Device Manager, find "Android Composite ADB Interface" and make sure it has a green-chip-like icon on the bottom left corner of the icon. If not, then it's not functional. To solve this, once your tablet is connected, it should be detected as a media player/portable device, with the name BNTV600 (I think it is/was - all this is still in Device Manager by the way). Right click on the device, and attempt to change the portable media player into a "USB Composite" device. That should solve the trick.
If you're still having problems, I can connect to you via TeamViewer remotely to access your computer, whilst your tablet is connected and solve the problem for you (if I can). If you'd like, I can completely root your tablet for you. I've done it for a couple of friends over TeamViewer, so if you'd like, I can do it for you too.
Best of luck.
P.S. Try disabling "USB Debugging" mode and set "Enable ADB".
While at work last night, I dropped my phone and it took a good bang,
the screen has a small crack but also the led underneath has gone so the phone is totally finished.
problem is, i have lots of pictures on the phone that i want to transfer onto my laptop before i buy a new phone.
so how can this be done?
because the battery come off, i now need to enter my pin number, but i cant see the screen, so have no way of connecting my phone to my laptop.
is there any way or programme i can get so i can access my phone via the computer?
Connect your device to your PC and try to use "adb.exe" (part of the Android SDK).
With adb you can connect to your device and "pull" the files you need to your PC.
First download and install the Android SDK (see at google's website for installation instructions).
The search with "adb devices" if your device is connected and recognized.
If yes you can check the files in a shell ("adb shell").
And if you know the path to them you can pull the pictures with "adb pull [remote path] [local path]".
Have tried every blog, every setting change, every type of cord. Will not connect. Everything I plug in get "allow MTP connection" usually multiple times as it times out almost instantly. When I time it and hit allow, nothing. Have tried, developer mode, USB debugging, MTP already active....screen on GMC supposedly uses "project ton app" but when I push it says attach USB device. Tried all 4 USB ports, have all marshmallow ATT updates including 1 today. Still nothing. Bluetooth conneats fine. Any suggestions.
Geesix39 said:
Have tried every blog, every setting change, every type of cord. Will not connect. Everything I plug in get "allow MTP connection" usually multiple times as it times out almost instantly. When I time it and hit allow, nothing. Have tried, developer mode, USB debugging, MTP already active....screen on GMC supposedly uses "project ton app" but when I push it says attach USB device. Tried all 4 USB ports, have all marshmallow ATT updates including 1 today. Still nothing. Bluetooth conneats fine. Any suggestions.
Click to expand...
Click to collapse
Have you had a dealership do the software update to add Android Auto to the Infotainment system?
Have the same problem.
Have you found a solution?
On my Pixel 7 (Android 13) I just tried doing "adb connect {IP-addr}:5555 and get connection refused. I can do adb with a USB cable connected, and adb connect over the network does work with some firesticks.
I do have USB debugging, and Wireless Debugging enabled in Developer options.
I'm running ADB on Linux.
What am I missing?
Enable wireless debugging then tap it > pair device with paring code.
Code:
adb pair (IP:PORT) shown in pairing box
after pairing
Code:
adb connect (IP:PORT) shown above pairing options
Still a problem
$ adb pair 192.168.10.114:40479
Enter pairing code: 665364
Successfully paired to 192.168.10.114:40479 [guid=adb-2C190DLH2000SS-IXWUPg]
$ adb connect 192.168.10.114:40479
failed to connect to '192.168.10.114:40479': Connection refused
obitest11 said:
Still a problem
$ adb pair 192.168.10.114:40479
Enter pairing code: 665364
Successfully paired to 192.168.10.114:40479 [guid=adb-2C190DLH2000SS-IXWUPg]
$ adb connect 192.168.10.114:40479
failed to connect to '192.168.10.114:40479': Connection refused
Click to expand...
Click to collapse
I think the pairing and connecting port numbers should be different, one for client and the other for server; and one is static and the other is dynamic. It's been a while since I tried wireless debugging but that's how I remember doing it. Either that or adb daemon isn't running on both sides.
I tried doing the connect with the normal 5555 port, after the pairing succeeded, but that didn't work either
obitest11 said:
I tried doing the connect with the normal 5555 port, after the pairing succeeded, but that didn't work either
Click to expand...
Click to collapse
No VPN right? Same network I presume. Did you get the message to always allow adb on this device? I have a Galaxy watch and couldn't connect until I turned off the adb debugging, wifi connections rebooted and tried again. Then the alert came up I clicked always allow and that did it.
The ports are different when pairing and connecting. Looks like you used the same port.