Hello,
I'm working on little Android SDK project. We (company I working for) decided to buy some Intel Atom based devices for testing SDK and mini-apps using it. We bought Dell Venue 7 and I have problem with connecting it vie USB to my Linux powered PC (Ubuntu 13.10).
I have udev rules for most known devices. What I have done for now with Venue was:
Code:
lsusb
which give me
Code:
Bus 002 Device 006: ID 413c:b11b Dell Computer Corp.
so my id vendor is: 413c. In /etc/udev/rules.d/51-android.rules I have:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="413c", MODE="0666", GROUP="plugdev"
I have applied similar rules to 31 vendors for now, and never noticed any problems (eg. with samsung tablets which also need udev rules).
Unfortunately Venue 7 is not visible by ADB:
Code:
~$ adb devices
List of devices attached
???????????? unauthorized
I tried to find answer on XDA and Google, but from yesterday I stucked.
My device details:
Dell Venue 7 3730
Android 4.3
Kernel v. 3.4.43
Developer mode unlocked, USB debugging turned ON, my PC was authorized, when device asks me for this.
Device is ordered few days ago as fabric-new, but there was no Dell branded software (I don''t know if any should be). Device is NOT rooted
[EDIT 02-05-2014]
Last I found solution. Everything in my setup was OK. One thing I've changed was my udev rule to line without "GROUP" so now it looks like:
Code:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="413c", MODE="0666"
but this was just small improvement to working setup
My problem was simply stupid - I used not supported cable . I was using cable which I used for lot of my devices, but actually when I changed to cable distributed with Venue, all starts to work.
Related
Well, after many searches both here and on google, I can't seem to find anything referring to my specific problem, so if this has been answered before, I apologize.
I am attempting to teach myself how to use adb in Ubuntu. I have it all set up, have updated the sdk, etc., thanks to many wonderful guides both here and elsewhere, and I have a 99-android.rules in /etc/udev/rules.d with the proper Vendor ID for the EVO 3d, and adb added to my path. Howerever, when I use adb devices, it shows no devices installed. I checked lsusb, and noticed that my phone is showing as High Tech Computers Desire/Hero with the wrong Vendor ID, which is obviously wrong. I was wondering if anyone knew what might cause this and how it can be resolved. The contents of my 99-android.rules are as follows:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Also, I am fairly new to linux, so if there is some command line magic involved, could you please explain what the commands are doing so I can understand what I'm fixing, instead of just doing a copy/paste?
Thank you in advance.
darthstewie said:
Well, after many searches both here and on google, I can't seem to find anything referring to my specific problem, so if this has been answered before, I apologize.
I am attempting to teach myself how to use adb in Ubuntu. I have it all set up, have updated the sdk, etc., thanks to many wonderful guides both here and elsewhere, and I have a 99-android.rules in /etc/udev/rules.d with the proper Vendor ID for the EVO 3d, and adb added to my path. Howerever, when I use adb devices, it shows no devices installed. I checked lsusb, and noticed that my phone is showing as High Tech Computers Desire/Hero with the wrong Vendor ID, which is obviously wrong. I was wondering if anyone knew what might cause this and how it can be resolved. The contents of my 99-android.rules are as follows:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4:0cba", SYMLINK+="android_adb", MODE="0666" GROUP="plugdev"
TEST=="/var/run/ConsoleKit/database", \
RUN+="udev-acl --action=$env{action} --device=$env{DEVNAME}"
Also, I am fairly new to linux, so if there is some command line magic involved, could you please explain what the commands are doing so I can understand what I'm fixing, instead of just doing a copy/paste?
Thank you in advance.
Click to expand...
Click to collapse
On the 100% stock Ubuntu 11.10 64 bit system, should be able to simply plug in the device and access it via adb. Only caveat will be, you'll need root access w/o setting up the udev rules. Simple command: sudo ./adb devices from the sdk/platform-tools directory should list the device.
The only issue I've had is when using VirtualBox, by default, it grabs USB connections and forwards them to the Virtual Machine which results in the linux side of ./adb devices showing nothing.
Hope that might help!
Thanks for that, but I do know how to use adb. My problem is that adb is showing no devices listed, and when I lsusb so that I can see what linux is reporting as being listed to my ports, it is showing up as being a desire/hero with the wrong vendor id, which is what I think is causing adb not to see it.
Try this
reboot your pc/laptop.
Then boot your phone into recovery and plug it in. Then from command line
./adb kill-server
Then to enabled it
./adb start-server
Then
./adb devices
See if that helps any.
Locked & Loaded
""shooter on Deck""
Actually, I think I figured it out. Whenever I reboot my phone, it switches from being ok to adb not seeing it and the wierd lsusb reporting. If I reboot without it connect via usb, everything is fine. I'm thinking it's in the ROM and/or kernel I'm using.
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
craterib said:
Hi,
The problem got solved for me when I started adb server as root process.
Open a terminal and go to android-sdk-linux_x86/platform-tools or wherever adb resides, and type
Code:
adb kill-server
sudo ./adb start-server
Now hopefully when you type adb-devices, adb-server will recognize your device provided the udev-rules are correct.
All the best !
Click to expand...
Click to collapse
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
sz_gergo said:
Hi craterib !!
Firstly thanks for your answere.
I will try your sollution when i arrive at home, today.
I will provide you the results. Could you paste your udev rules ??
Just for the case that mine are not the best ones
THX
Gergo
Click to expand...
Click to collapse
Code:
[email protected]:/etc/udev/rules.d$ more 51-android.rules
# Sony Ericsson Mobile Communications AB
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="6168", MODE="0600", OWNER="kuisma"
Using this, you don't have to run the adb server as root. Use the "lsusb" to get Vendor and Product id for your device.
Also, change "kuisma" to your user, of course, unless toy happen to be me.
Restart udev (/etc/init.d/udev restart) once you've edited this.
sz_gergo said:
Hi All
i have a problem on Ubuntu 12.04 with the adb .
My device is simply not detected by adb. ( there are no devices in the device list.
I have updated the udev rules many times , and it seems to me that the device itself is detected by the system.
I wiould need any help with that problem , which makes me slowly really mad.
Thank you for your help
BR
sz_gergo
Click to expand...
Click to collapse
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
bronzext said:
To get your newly build Apps down to your device you have to use the ADB (Android Debug Bridge). The common way to make your device ready for playing is to download the USB driver package which is included in the SDK Manager.
But these drivers are only for a couple of common mobile devices, so what if you have an ARCHOS 8 like me…. You will still get stuck with a nice…. device not found ….
The first part is easy, Archos in my case, offers his own usb drivers .
After downloading the USB driver I got a shiny “Archos 7 ADB” item under “Android Phone” in my windows device manager. But what is this,…. after restarting the ADB daemon,…. “ADB devices” was only showing an annoying message… “device not found….” Gees.
Hmm, Google is your best friend …… The solution is that the ADB daemon needs also your USB device vendor ID (VID)
If you cannot get it from your device vendor you may look under device manager -> device details -> hardware ID -> USB\VID_xxxx.
The VID for the adb should be placed in a file under {user home}/.android/adb_usb.ini.
Insert the VID in HEX notation {0x0e79}
If this file does not exist, just create it!
Click to expand...
Click to collapse
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
I did not see anybody here mention Knives-And-Forks Tools which is easiest way to Install adb and Fastboot on multiplatform computer. I did it and works like a charm
sz_gergo said:
Dear all suddenly it is solved !!!!!!
Well the sollution was for me to insert the Vendor Id of my box into the $HOME/.android/abd_usb.ini in the hex notation.
After that i have killed the server and restarted it as a normal user.
It is working fine now and the device is shown by the adb devices
Thank you for your help
BR
Gergo
Click to expand...
Click to collapse
hello i have question how to insert vid in hex notation...
digitized007 said:
hello i have question how to insert vid in hex notation...
Click to expand...
Click to collapse
Well therefor you will need an editor. I have used vi , but it is possible to use any editor.
2. step open the file in the editor
3. in a terminal window type " lsusb -v " that will give you the information of all the usb devices
look for the line beginning with idVendor of your device
for me it looks like: " idVendor 0x12d1 Huawei Technologies Co., Ltd."
4. copy the hexcode: 0x12d1 (yours may be another number) into the file
5. save the file
6. restart the server
only that number is needed nothing else
for every device you will get such a code , and each device code should came into a separate line
Hope that helps
br
sz_gergo
hi.
forum search did not help with this
after successfully setting up and using adb for a couple of days with my viewpad 7e (device-id is 0x0bb0 - this value is in my adb_usb.ini - although i believe it once worked with 0xbb0 - now both doesnt) adb decided not to see my tablet anymore.
EDIT: of course usb debugging is enabled.
i can use the binaries, only my device does not show up anymore. mac os x knows about the device:
Code:
ViewPad 7e:
Product ID: 0x0005
Vendor ID: 0x0bb0 (Concord Camera Corp.)
Version: 2.27
Serial Number: ViewSonic
Speed: Up to 480 Mb/sec
Manufacturer: VS
Location ID: 0xfd120000 / 4
Current Available (mA): 500
Current Required (mA): 500
mac osx 10.7.5
android-sdk downloaded again yesterday, so it should be pretty damn new.
besides the adb_usb.ini the installation is straight forward what you'll find in almost any howto on setting up adb. so where did i go wrong? or, what other stuff between my macbook and adb could keep adb from seeing the device? i got no ideas. if you need any more info about the device or the host, please let me know.
EDIT2: i use vmware fusion on my macbook. this normally asks me wether to pass on a usb device to the VM or connect it to the host. it does _NOT_ (however, settings regarding this are correct as in 'always ask') ask me anymore. i suspect this could be the problem. did anyone have this issue before?
[SOLVED] VMWare Fusion
solved.
as i suspected, VMWare Fusion/Mac OS X had their way with the devices. cleaning this up, rebooting, everything works again.
Hi guys, I've been tearing my hair out for the past 24hrs trying to get ADB to communicate with my devices (Amazon Fire tablet + Nexus 5x).
I've installed ADB and drivers for my devices. They currently show up as Android Device > Google Nexus ADB Interface (ClockworkMod driver installed) and Android Device > Android Composite ADB Interface (Amazon.com driver installed).
I have enabled ADB on my Amazon Fire tablet (5th Gen - 5.1.3) and USB debugging on my Nexus 5x.
When I run ADB, all it sees is my Fire tablet but says "unauthorized" next to it.
On both devices, when plugged into the computer via USB, I get no message about enabling the computer to access the device etc. They just sit there, charging with "USB Debugging Connected" on both devices.
Could someone point me in the right direction to get ADB communicating properly with both devices? I originally wanted to use it to root my Fire Tablet to load a different OS on to it, so I used my Nexus 5x to see if that could communicate with ADB but it appears that neither do.... properly anyway.
Another flag that I'm wondering is that in Device Manager, I do have an exclamation mark next to a USB controller - I've found drivers for it (Renesas USB 3.0 Host Controller) - but it came up with an error saying the device cannot start (code 10) - I don't think this is anything to do with my issue as the drivers are installed correctly it appears for the Android devices.
Thanks a lot in advance.
I've done it! I had to delete adbkey from .android folder on my PC - god knows why! all fixed though. yay.
Hi all,
I'm sorry, I tried to provide direct links/images but unfortunately only after 10 posts I'm allowed to post URLs
The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( find the chromium org url "chrome-os-systems-supporting-adb-debugging-over-usb" ).
However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of yesterday) to a Windows 10 machine, and using the guide provided on developer (dot) android topic/arc/#adb-usb
Did anyone get this work successfully?
If so, can anyone point me in the right direction?
Using hardware:
- Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
- Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
My steps:
- Powerwashed the Pixelbook
- Set Pixelbook to 'Developer Mode', see image:
h ttps://ibb.co/cRmiEo
- Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
h tt ps://ibb.co/mLikS8
- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:
h tt ps://ibb.co/j8m5S8
- Attached the USB-C cable to the W10 laptop and run ADB devices.
- No devices show up in cmd (adb devices)
- Android Studio also does not list any devices to run on
- This is what I'm seeing in Device Manager, a 'malfunctioning adb device'
h tt ps://ibb.co/cpXen8
Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!
No solution (yet)
Let me know whenever someone has given this a shot with their Chromebook.
I still haven't managed to solve it, also posted it to the Google Product forums now
Quick search of this forum shows this.
https://forum.xda-developers.com/ha...oks/guide-setting-adb-fastboot-x8664-t3806428
Brounzer said:
Hi all,
I'm sorry, I tried to provide direct links/images but unfortunately only after 10 posts I'm allowed to post URLs
The most recent, much welcomed, update to ChromeOS has introduced ADB over USB for a select few models ( find the chromium org url "chrome-os-systems-supporting-adb-debugging-over-usb" ).
However, I have yet failed to get this to work by connecting my brand new Pixelbook (as of yesterday) to a Windows 10 machine, and using the guide provided on developer (dot) android topic/arc/#adb-usb
Did anyone get this work successfully?
If so, can anyone point me in the right direction?
Using hardware:
- Pixelbook with Stable Build 67, and also attempted Dev Channel with build 69.
- Connected USB0 (left side) to my Windows 10 laptop USB-A port, but also attempted connecting it to my laptop's USB-C port (so a USB-C to USB-C cable).
My steps:
- Powerwashed the Pixelbook
- Set Pixelbook to 'Developer Mode', see image:
h ttps://ibb.co/cRmiEo
- Enable Android Developer Options by going to Settings in ChromeOS, Manage Android --> 7 taps on Build Number and then opening the 'Android Developer Options' and enable ADB Debugging:
h tt ps://ibb.co/mLikS8
- Run the setup commands in crosh/shell as described in the guide (link above), such as dev_enable_udc , and dr_swap commands. As stated by the guide on developer.android: "Use this command each time you disconnect and reconnect a USB cable. To ensure your Chromebook is in UFP mode, you can run ectool usbpd <port number>" . See attached:
h tt ps://ibb.co/j8m5S8
- Attached the USB-C cable to the W10 laptop and run ADB devices.
- No devices show up in cmd (adb devices)
- Android Studio also does not list any devices to run on
- This is what I'm seeing in Device Manager, a 'malfunctioning adb device'
h tt ps://ibb.co/cpXen8
Any help would be greatly appreciated if anyone has already managed to the ADB USB to work!
Click to expand...
Click to collapse
I have suceeded in doing this in my Samsung Chromebook Pro. There are a few problems off the bat.
1) Chrome OS ships with a very outdated version of ADB
2) There is no rule by default for accepting usb connections from vendors. You have to add it to your rules.d folder.
If you know what you're doing you can install the dependencies directly to your system and update the shipped adb using debian resources. You could also use crouton. I made a tutorial a while back. Things have changed a tab, but not much. tutorial link
Also I will attatch the script I made to automate the process on my CBP. With a little tweaking you could make it work for yourself. I know this probably isn't what you are looking for. But installing the debian resources will almost certainly get it running in the native crosh shell.