Plugged in: Port 7: 0000.0101 power connect Using the -v option with the lsusb command i get one different line:
#Ubuntu lsusb not showing android phone android#
HTC - 1, Associated Dairies' supplier of cables - 0.I've installed Linux Mint 16 on my new PC and found out that my plugged in Huawei U8850 Android 2.3.5 device is not listed with the lsusb command:īus 002 Device 002: ID 8087:8000 Intel Corp.īus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 001 Device 002: ID 8087:8008 Intel Corp.īus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hubīus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 003 Device 011: ID 057c:6201 AVM GmbH AVM Fritz!WLAN v1.1 īus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub What I learnt here: Check the simpler stuff first, before pulling out your hair getting nowhere with installed software, all of which was put back up as it had been prior to the fault's manifesting itself in the first place! R value of the o/e, HTC tagged lead's +5V strand was only slightly more resistive than a dead short would be and not being especially well up on the workings or layout of micro USB no, I couldn't fathom out how this affected data transfer either so can only assume that the supply rail in the I/O board on either or both device(s) uses the +5V part of one or both sockets for data transfer too. The DMM was then employed to show how exactly this state of affairs had come about: Resistance of the +5V supply strand in that lead had increased to the point where it read almost open. The USB lead to the handset's micro USB socket was faulty.īy using the o/e lead that had always seemed stiffer and less likely to last than the generic one bought at the AsDa, normal service was resumed. Let is know what is happening.Īfter trying every one of the potential solutions detailed above and in other threads from other fora, I discovered that the reason my HOX had decided not to communicate with my laptop any longer (14.04) was a simpler, mechanical one. Then log off, unplug the mobile, log on again, plug it in and try adb devices again. Use this command: sudo useradd -G plugdev crazydeveloper Make sure you are a member of group plugdev. It didn't set the owner to crazydeveloper for some reason but that isn't that important. udev picked up the device and set its permissions to 666 and the group to plugdev. You did actually replace that with OWNER="crazydeveloper", didn't you ? Please show us the device permissions using command: ls -l /dev/bus/usb/002/004Īs a temporary workaround you could make the device world readable/writeable with this command (make sure your phone is plugged in): sudo chmod 666 /dev/bus/usb/002/004Īlso I noticed that at the end of the udev rule you have OWNER="". Therefore udev created device object /dev/bus/usb/002/004. Means that your mobile is connected to Bus 002 as a device 004. The fact that lsusb gave us: Bus 002 Device 004: ID 0bb4:0c03 HTC (High Tech Computer Corp.) Then check the permissions: ls -l /dev/bus/usb/YOUR_USB_BUS_NO/ If this doesn't work find out where exactly your device is connected with lsusb. Then restart udev: sudo udevadm control -reload-rules
#Ubuntu lsusb not showing android phone update#
Restart udev (you may need to log off and log back in to update user group): sudo service udev restart Here's the les SUBSYSTEMS="usb", ATTR username): useradd -G plugdev billy I have googled and was brought up with this as my solution, but that also didn't worked. Now when I run the application from eclipse, my device is not getting detected. I have just downloaded and installed android sdk.
0 kommentar(er)
