Connect my G1 with my laptop(Ubuntu 8.10 x64)
When I run the adb devices, it only said: List of devices attached
No devices line; It lists one line when I start the emulator program.
And not like the SDK for windows, there is not some folder related to drivers.
Does it support for linux x64? plz help.~
have you activated the debugger in your g1 ?
oh I remember when I was in ubuntu now
you gotta launch adb daemon as root
try this :
adb kill-server && sudo adb devices
and let me know if it worked
dixxa said:
have you activated the debugger in your g1 ?
Click to expand...
Click to collapse
Absolutely, it works fine in Vista x64 with SDK 1.1 r1
I had to do two things to get this to work (although this was on x86) -
1) Build the kernel with the Android drivers enabled. This might not be necessary; I have no idea if they are turned on in the kernels you get from the Ubuntu repository as mine has been custom built for a while, but I'm guessing that they aren't enabled by default because they are in the "staging" area as of 2.6.29.1. So these were in Device Drivers/Staging Drivers/Android.
2) Add a "50-android.rules" file to /etc/udev/rules.d that has this line:
SUBSYSTEM=="usb",SYSFS{idVendor}=="0bb4",SYMLINK+="android_adb",MODE="0666"
The idVendor is different if you have an ADP phone, I believe; this was the value worked for mine (non-dev). You can do an 'lsusb' after it's been plugged in and see what shows up. Also, try grepping /var/log/messages for "udev" after you plug it into a USB port and see if there are meaningful messages.
- Chris
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
noz.geek said:
Hi all,
I got similar issue here, the main difference is that i got ubuntu 9.04.
running adb daemons as root permit to see devices when it's started normally, but not when in fastboot mode.
I tried all suggestions above (and others!) without success :/
Thanks for any help
Click to expand...
Click to collapse
copy the 50-android.rules file you created into a file called 51-android.rules. The problem is related to the order in which things are launched and copying this file to the new name will solve your problem.
I should also note that you will have to restart udev Or reboot or logout/in
to restart udev, In terminal type:
Code:
sudo /etc/init.d/udev restart
sudo is necessary~ thx
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
npak243 said:
Hi all,
After creating 50-android.rules file in /etc/udev/rules.d, I can mount my sdcard on my gPhone to Ubuntu8.04 but I still see no thing when i type command : adb devices. I also did some commands which you gave here. Can anybody help me?
Thanks so much,
NPAK
Click to expand...
Click to collapse
Code:
$ sudo mv /etc/udev/rules.d/50-android.rules /etc/udev/rules.d/51-android.rules/code]
that should fix it ;)
Thanks,
It can work now!
I have the same problem here. adb used to be able to see my phone when I was using Ubuntu 8.10. After I upgraded to 9.04, it never worked. I tried change the udev rule file from 50-** to 51-** or as haykuro suggested to 51-**/code. I also changed the permission to 777. And I did kill and restart adb-server several times under root, but I still get nothing~~~
Can anyone help?
When I open up my terminal emulator it says:
export PATH=/data/local/bin:$PATH
and no commands work anymore
I then tried to use adb through cmd in windows and I can't get anything to work that way. Everything was working fine yesterday, but now I can't get any commands to work. Any ideas?
bigupurself7 said:
When I open up my terminal emulator it says:
export PATH=/data/local/bin:$PATH
and no commands work anymore
I then tried to use adb through cmd in windows and I can't get anything to work that way. Everything was working fine yesterday, but now I can't get any commands to work. Any ideas?
Click to expand...
Click to collapse
When you say, terminal emulator... you mean on your phone, right?
When you try running adb commands in windows -- what's the exact error message you're getting?
I was trying to get adb to work on my mac by following this guide.
http://www.droidforums.net/forum/droid-hacks/11770-adb-mac.html
After going through it i made the bash.profile wrong (im guessing) and adb isn't working. when I try to get in to remake the bash.profile I keep getting
Code:
-bash: pico: command not found
How do i fix this?
Hi,
This is my first thread on XDA so forgive me if this question has already been answered somewhere else.
I've been using Android Terminal Emulator for a while now my TF101 (with ICS).The device is rooted with busybox 1.20.2-cm9 installed.
Everytime I try to enquire on disk space using the "du" command I get a segmentation fault/ Stopped Signal error. I've attached a picture to show what I mean
I've also got linuxonadroid installed running ubuntu 12.04. When I use the same command line in that environment, no such errors appears.
Please advise .
Thanks
Hello
Im using Android 4.0.4 samsung GT I9100 in Bluestacks
what should i do to solve the issue im having
basically i cant do sendevents for mouse clicks. I followed some guides to do a getevent for touch emulation
I was able to install an emulator terminal for bluestacks adb and watch the getevents i needed to send a touch. However, whenever i use the commands, either in Taskker command shell or in the terminal. Nothing happens
it returns the error that the path could not be found even though i used a root file explorer to find the input directory and it was in fact there!
what should i try next?
-DM123:cyclops: