I'm trying to get "adb devices" working on either Windows 10 or Ubuntu 17.04. On both operation systems everything is configured for adb to work. A Honor 5X works on both machines as expected.
But no luck with the LGs. I have a few of them for testing, but not a single one is working with adb.
The Version of the Android Debug Bridge is 1.0.39.
The LG is running Android 5.0 Kernel-Version 3.4.0
The Honor 5X is running Android 6.0.1 Kernel Version 3.10.49-g91e5af6
The strange thing about the LGs behaviour is, that in the Notification Area it says, that USB Debugging is enabled but it never asked for authorization. Even when I clear all authorizations it does not ask me for it.
And a "adb devices" does not show the LGs as unauthorized but instead does not show the at all.
That is something all other Smartphones of different brands I tested did consistently.
Accessing the LGs via MTP does work.
I currently do not have an idea how to analyze this any further. I would appreciate any suggestion directing me towards a solution.
Edit: I'm using the adb commandline version.
Edit: This solution (activate USB Tethering) made it better, but this is disabled every time the usb connection is removed and I need a permanent solution working without user interaction.
See LG Device Not Listed in ADB Devices.
Edit: In Windows 10 I got this working these USB Drivers:
http://www.lg.com/us/support-mobile/lg-LGD850
But I need to get it working on ubuntu 17.04
Thank you very much!
I had this kind of smart phone. I changed the cable and it worked.
(use a thicker cable)
I found the solution myself to get it working on Ubuntu 17.04. It is necessary, that you select PTP instead of MTP. This seems to be an specific issue when the LG USB Drivers are not installed, which is never the case in Linux because there LG does not provide any drivers.
Related
I am trying to debug an app on android but found out that my chrome://inspect doesn't show any apps or pages anymore for my device despite showing the device itself.
I followed multiple tutorials, search for my problem on the internet but nothing came in useful and as it used to work I don't really know where to start with this issue. I will try to give you as much informations as possible:
I tested my build on emulator and on another phone (ungoogled rom, android 11.0) and everything worked just fine, I could see and debug the app
USB debugging is enabled in my developer options on the phone
my android version is 11.0
my webview version is 92.0.4515.131.
my build is a debug one (not production)
I recently changed my rom (from paranoid quartz 5 to ArrowOs 11.0) but I didn't use the inspector for a while before changing, so I suspect I affects the issue but I don't know how much
I tested it on MacOS Big Sur and ArchLinux, as well as with multiple chrome versions (eloston chromium, chrome, brave)
When trying to inspect other pages from just chrome from my phone, nothing appears either
The app runs with cordova
What am I missing here and is there a solution for my problem other than change rom again ?
Thank you very much for your answers
First, try to restart adb server. It can be done with these commands on unix if adb command is available to you in terminal. If not, then on unix instead of adb, type path (absolute to be sure) to adb executable.
adb kill-server
adb start-server
adb devices
If you can see your device in output of adb devices (only device ID will be visible), then try to disable ipv6 for your network. Adb server might not work properly when ipv6 is enabled on your computer. In my case, disabling ipv6 have fixed that issue and I could see 'Remote target' section (which was not visible when ipv6 was enabled) and my devices once connected.
I'm trying to test an Android Application on my Galaxy Nexus (from Google). I use Windows 7 Home Premium 64 bit and Eclipse Java EE IDE for Web Developers.
My device doesn't show in Eclipse DDMS view. My device also doesn't show when I run adb devices in cmd.
I have USB debugging enabled.
When I try to install the USB driver as shown here I get a message that my device software is up to date.
I also tried killing the adb server and starting it again.
Give the Universal Naked Driver a try? Be sure to follow the steps in the forum post.
Nexus devices require the Google USB Drivers, you can get them through the SDK Manager.
If you have them installed and the device still is not detected try the following:
Use a different USB port (for me the USB 3.0 port is always making problems)
Restart the device and the computer
Restart ADB
Also take a look here, which explains how to install drivers for the Nexus S.
I had a similar problem. I could not get my device to show up in my Eclipse devices window. When I typed adb devices, no devices were discovered. Fortunately, I discovered this website. It basically had me install a generic driver for my Motorola (Android 2). It had other drivers for Samsung and other manufacturers. After the install, my Motorola phone became visible with ADB.
My problem is that adb devices does not detect my galaxy ace (s5830) using Ubuntu 12.04,
I tried everything but still not working.
Can help me where fault.
I have installed oracle sdk 1.7, last android sdk and I have created the rule 51-android.rules with permissions a+r
I had the same problem. Despite the rules file my device was not getting detected.
I did the following:
Restarted my device
Connected as "Charge only" (an HTC device).
The device was detected and I was able to install the app.
Do the following things
Download Kies for Samsung Smart Phone
Restart eclipse
In DDMS section, go windows->Show View->Devices, then click small down arrow(View Menu) and click on Reset ADB. Then it should work properly...
Android uses Java 1.6, so upgrading to 1.7 wasn't necessary.
Did you really use the Samsung vendor id 04e8 for your udev rules? And did you set debugging "on" on your actual device? Do you have any tethering app on your device (that makes use of adb)? Some do.
Also you need to restart your terminal window (or restart Eclipse) for your udev rules to be loaded for the first time, but I assume you did that already.
Also for good measure, you should restart your device as well.
If you're really desperate to get this working, you could always root your phone and use a free app like adbwireless (which only works on rooted devices and local wifi which does not have wifi isolation turned on). That's what I had to do with my Samsung Tab 10.1 (until I sent it back for repair).
Adb wasn't finding my Tab from my Ubuntu 12.04 laptop either, nor was it finding it from the Mac and the Windows PC of my developer friends, but when I tried to connect the Samsung Tab 10.1 that belonged to a friend of mine, adb was seeing it just fine on it, so this is what pinpointed the problem for me.
Try restarting adb
adb kill-server
adb devices
Make yourself a shortcut to this.
I have a Wi-Fi Motorola Xoom that I am connecting via ADB for development. I am seeing an intermittent problem where the device (with ID number) shows up in the adb devices list, but will present as being offline.
The device and computer both show the tablet as being connected. I've tried a combination of rebooting each device and swapping USB ports, but the only thing that solves the issue is switching out the cable. Furthermore, a cable that I used yesterday doesn't work today -- I am having to use a previously non-functioning cable to connect.
Is this a driver issue? Device port issue? I have seen this issue with several versions of the Motorola drivers as well as the PdaNet drivers. I am currently using Motorola Mobile Drivers 4.7.1.
WARNING: this question referred to an older device and as such the answers may no longer be relevant to current ADB connection issues.
I met the same problems like yours, and I found out that the USB cable has mal-functions in the PIN of head USB. So I switch to the new USB cable, it just works fine and detect device as online.
I had the same problem, and switching from the USB port on the front of my machine to the port on the back made things work. It could be related to a difference in port power or USB type.
From XDA: nouvelle_adr http://forum.xda-developers.com/showthread.php?t=2247471
I downloaded the adb version and it worked.
When you connect a device running Android 4.2.2 or higher to your computer, the system shows a dialog asking whether to accept an RSA key that allows debugging through this computer.
This security mechanism protects user devices because it ensures that USB debugging and other adb commands cannot be executed unless you're able to unlock the device and acknowledge the dialog.
This requires that you have adb version 1.0.31 (available with SDK Platform-tools r16.0.1 and higher) in order to debug on a device running Android 4.2.2 or higher.
If you haven't this pop-up mesage in your device, there is the solution :
1) Install SDK in your PC
It may asks you to install JAVA, if so, do it.
2) make sure that your adb is 1.0.31 or upper, to know the version, tape : adb version in your commande window"
I have tried downloading the Samsung specific drivers. It installs the modem, not sure if the adb bridge got installed. I don't see it in the device manager. I have installed kies 2.0, I have tried connecting USB via MASS storage, via Kies, and under no circumstances so far will ADB detect the device when running adb devices command. I got lots of suggestions to use Kies, I tried this. Don't see any real relationship between Kies and ADB which is a debug bridge. I simply have no clue what ADB is doing when I type adb devices. How does it look for devices, where does it check, where can i register my device with ADB?
Apparently sometimes you need to uninstall and reinstall the driver multiple times before it works (http://androidforums.com/captivate-all-things-root/136373-adb-shell-error-device-not-found.html). Also, make sure that USB debugging is turned in your application settings.
make sure you are using the correct drivers (32 bit or 64 bit). when you connect your phone in debug mode check device manager. I would bet you have an error in there. Try and delete the error and rescan for changes.