I am having problem connecting my 4.2.2 android device with PC after I select "Always allow from this computer".
I have selected "Always allow from this computer" in 4.2.2 USB debugging and it works fine the first time but when I tried other time my devices always appear offline. I have tried with another device that is also 4.2.2 and the USB debugging popup and when I click ok (without selecting "Always allow from this computer") with device list became online.
I have tried the following method and it didn't work
Are there anyway to get rid of "Always allow from this computer" once I selected?
As described in this issue, this can happen if you run
adb for the first time as root. It creates a key file on your computer owned by the root user, so your normal user account can't read or overwrite it.
To check if this is the case:
$ ls -l ~/.android/adbkey -rw------- 1 root root 1708 Nov 13 2012 .android/adbkey ^ notice root here
To fix it:
$ sudo chown $USER: ~/.android/adbkey $ ls -l ~/.android/adbkey $ -rw------- 1 thomas thomas 1708 Nov 13 2012 /home/thomas/.android/adbkey ^ now shows your username and primary group
When i connected my Galaxy S3 running a 4.2.2 AOSP build, im presented with the pop up to allow debugging with the computer on my device.
On Eclipse - you see the following until you click "OK" on your device to allow USB debugging with the machine. It should change to the Target Android OS after you Press OK.
In your case - Your device seems to keep going offline after the first time you press the debugging dialog.
Revoke USB Debugging authorization from Settings in Android device and restart adb server on PC. The dialog will appear again while connecting to PC.
for restarting ADB server
$ adb kill-server
$ adb start-server
I've had nothing but problems with this since upgrading to 4.2.2 (Google Nexus 10).
In device chooser I keep getting 'Unknown' as the target.
The only thing that works for me is to:
It's a bit of a pain, but it works for me!
Its quite commonplace for devices to go offline... when that happens I just un-plug and plug the device no restarts nothing!
I had the same problem and realized I'm better off just using the emulator. To use an emulator, click on the "Windows" tab in eclipse, and select "Android Virtual Device Manager". From there create a new emulator and click "Start" on the right hand side. After that, you can select the size, and press "Launch". It takes about 2-3 minutes to start off, but it works perfectly and is very convenient!
Good luck pal! :)
This was pulled from a comment in the 3rd answer.
After verifying ownership of $HOME/.android/adbkey and adbkey.pub to be appropriate user double check they're actually non-zero filesize ( ls -al $HOME/.android ).
Same thing happened to me as the original comment. Just delete those two files and restart adb ( adb kill-server ; adb start-server ) and you should be right as rain. Well it worked for me atleast.