I am trying to connect my android phone (Qmobile) with Linux mint but its not appearing in eclipse.. Actually i was appearing as unknown device before but i tried some commands from internet it is disappeared now :( can anyone help me how to connect Android phone with Linux for debugging with eclipse.
i used following commands in terminal before:
adb kill-server
sudo adb start-server
sudo gedit /etc/udev/rules.d/51-android.rules.
chmod a+r /etc/udev/rules.d/51-android.rules
Kindly Answer me if you can Thanks.
Related
I am trying to install ADT without using standalone installer.With help of this guide http://forum.xda-developers.com/showthread.php?t=2302780
I am using ubuntu 13.04 , so when I try to call adb or fastboot, it alwasys ends up as permission denied.
parthiban#upk-sys:~$ adb
bash: /media/parthiban/New Volume1/idea-IC-129.1359/android-sdk-linux/platform- tools/adb: Permission denied
parthiban#upk-sys:~$ fastboot
bash: /media/parthiban/New Volume1/idea-IC-129.1359/android-sdk-linux/platform-tools/fastboot: Permission denied
I have edited .bashrc as instructed in that guide . Any idea ??
Seems like your device needs to be accessed by a privileged user. Simply put 'sudo' in front of the command adb or fastboot.
Or you could try and restart the adb server with the root account.
Like
sudo -s
adb kill-server
adb start-server
Afterwards you should be able to call adb (or fastboot)
I'm developing android apps in eclipse and I upgraded recently from Ubuntu 12.10 (Quantal Quetzal) to Ubuntu 13.04 (Raring Ringtail).
In the previous Ubuntu version I had zero problems in recognizing my android device.In this new Ubuntu version I must do:
sudo adb kill-server
and
sudo adb start-server
in order to Ubuntu recognize my android device.
Everytime I restart my computer it appears question marks in eclipse when I try to debug an app, and I have to run these command lines everytime to make it work.
Anyone knows if there is a way to recognize my phone permantelly?
adb "flakiness" is a common problem, you have the right idea to start adb with root permissions.
If you have eclipse running and run it as two separate commands, there is a chance that eclipse will have tried to startup adb as a non-root user before you have run your start-server, so I recommend running in a single command line:
sudo adb kill-server && sudo adb start-server
Also you want to make sure you have only one copy of the sdk installed and that eclipse is using the same copy as is on your path at the command line.
Possibly could throw the run-as-root logic into an init script so that when you restart the computer it comes up as root - I haven't tried this though, always just "control-r, start-ser" from the command line =)
I had the same problem and solved it by
just change the owner of adb to root and restart then in future the problem won't happen again.
use this:
sudo chown root:root -R /opt/..../sdk/platform-tools/*
sudo /opt/..../sdk/platform-tools/adb kill-server
sudo /opt/..../sdk/platform-tools/adb start-server
I'm trying to debug an Application on a Xperia cellphone with Cyanogenmod installed, but it doesn't seem to recognize my cell phone. Also, adb seems to be gone, I followed http://developer.android.com/guide/developing/device.html the official guide, but when executing:
$./adb devices
on the plataform-tools/ directory the system doesn't recognize the device.
also I tried
$sudo ./adb devices
any ideas?
thanks to everyone for the help.!! I solved
the problem was that I needed to restart the adb server I did it like this:
$sudo ./adb kill-server
$sudo ./adb start-server
Adb devices is not listing my Samsung Pop 5570 wen connected in with USB debugging on in ubuntu 10.10
adb devices
?????????? no permissions
i did add the 51-android.rules file in /etc/udev/rules.d folder but still adb devices shows that devices wit ?????? no permissions.
51-android.rules file has the following contents:
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="04e8", MODE="0666"
please let me know if i am missing something
I resolved the issue by appending #samsung in the 51-android.rules file and copying the "adb" command to /bin folder.
$ restart udev
$ cp adb /bin
$ sudo adb kill-server
$ sudo adb start-server
$ sudo adb devices
List of devices attached
S5570e905be1c device
Edit: I suspect your subsystem name is the culprit (simply try "usb" instead). However, I am unable to comment as to whether or not that subsystem name is still valid in 10.10 as I do not know what changes have been made to udev.
First step would be to verify that your vendor id is correct with lsusb (that appears to be Samsung's vendor id, but it can't hurt to check).
I am also running 10.10, but I have an HTC device. Here is my rule file's content:
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
After editing the file, I unplugged my device. Just in case, I kill adb's daemon:
sudo adb kill-server
I then reconnected my device and executed "adb devices". adb started the daemon without sudo. My device was listed properly.
I resolved the above problem by prefixing the 51-android-rules file with #samsung, i mean,
'#samsung SUBSYSTEM=="usb_device", SYSFS{idVendor}=="04e8", MODE="0666"'.
I killed the adb server and restarted in SU mode and then ran
$sudo adb devices,
i was able to see my device listed.
I have been developing a project app to learn about android, I can upload my app to my htc desire on my desktop using linux ubuntu and eclipse, I have the same setup on my laptop but I cannot upload apps to my phone. When I try to install the app to the phone it shows up in avd manager as ??????? ????? Unknown, I've googled this and the general advice is to setup a script which I have tried but I get an error message saying path does not exist, when I try to kill the adb server it says no such command even though I am in root and can see the adb file in the sdk folder, I am completely lost here anyone help with this.....
Thanks in advance
Looks like you are running Linux on your laptop. Try these steps as your normal user:
If you haven't already set up the udev rules for your device, follow these steps:
1. sudo gedit /etc/udev/rules.d/51-android.rules
2. copy/paste this line into that rules file: SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
3. sudo service udev restart
Then, restart the adb server:
cd </path/to/your>/android-sdk/tools directory
sudo ./adb kill-server
sudo ./adb start-server
If it's not there already, you can add the /path/to/your/android-sdk/tools to your $PATH variable so you don't need to cd to the directory and also won't have to use the ./ to use the adb command.
You may need to unplug/replug the USB cable to your phone after you do all this.