2

I used to use the Android emulator for debugging. Everything was fine. But when I tried emulator for Android 4 it was lagging so much. It was almost impossible to use it. So I tried to use USB debugging with Samsung Galaxy SII with Android 4.0.4. I've enabled USB Debugging on device, installed drivers, tried to use Kies, but it just doesn't work. When I started debugging and selected this device in Android device chooser, it was looking like this:

samsung-gt_i9100-0019caae19649e | N/A | 4.0.4 | --- | Online

Then in the console it gave me this code:

[2013-01-28 20:30:58 - UniqueFileExplorer] Android Launch!
[2013-01-28 20:30:58 - UniqueFileExplorer] adb is running normally.
[2013-01-28 20:30:58 - UniqueFileExplorer] Performing sync
[2013-01-28 20:31:01 - UniqueFileExplorer] Uploading UniqueFileExplorer.apk onto device '0019caae19649e'
[2013-01-28 20:31:11 - UniqueFileExplorer] Failed to install UniqueFileExplorer.apk on device '0019caae19649e': timeout
[2013-01-28 20:31:11 - UniqueFileExplorer] Launch canceled!

So does somebody know what's the problem?

I'll be grateful for any help.

And sry for my bad english.

egst
  • 1,605
  • 3
  • 18
  • 25
  • Have you tried like reboot the phone? Reboot the computer? Disable & Unable USB Debugging? – GuiceU Jan 28 '13 at 20:01
  • What operating system is your computer using? I have been having horrible trouble trying to get Windows 8.1 to connect to my Galaxy S3. – mjanes Jan 10 '14 at 22:19

1 Answers1

1

Insctructions :

1 Restart phone.

2 Restart computer.

3 Check enabling "USB Debbuging" in phone settings.

4 Enable debuggable in mainfest.

TN888
  • 7,659
  • 9
  • 48
  • 84
  • I have tried this few minutes ago. I have restarted phone. Then reinstalled drivers, reinstalled Eclipse and reinstalled ADT. Then I wrote android:debuggable="true" in the in manifest. And still doesen't work. Now when I open the device chooser it is looking like this: 0019caae19649e | N/A | unknown | --- | Offline | – egst Jan 28 '13 at 21:39
  • Try to use another device, if you have, and give results. Ps did you restart computer ? – TN888 Jan 28 '13 at 21:42
  • Yes I have restarted computer. I have HTC Desire, but it has Android 2.2. I was trying it with this device and it was worst. It hasn't even detected it. I could try to use Galaxy SIII, but it's not my device, so I'll try it later. – egst Jan 28 '13 at 21:47
  • I just hate this Samsung logic. It's getting worst and worst. I can't even connect this device without Samsungs Kies. That's why I still use my old HTC. – egst Jan 28 '13 at 21:49
  • If you have kies, update it and download newest version of application and drivers. Sorry for my bad English – TN888 Jan 28 '13 at 21:56
  • I'll try it. And it's ok, I'm not english speaker too. – egst Jan 28 '13 at 22:06
  • And I have the newest Kies and actual drivers. – egst Jan 29 '13 at 20:18
  • Nothing changed... All the same. – egst Jan 29 '13 at 21:31
  • but wait... there is some new actualization prompted few second ago by Kies. – egst Jan 29 '13 at 21:33
  • That awkward moment when you realize that the problem was with old framework version... – egst Jan 30 '13 at 14:02
  • My last request for you : install adb on another computer and try again. I must know where is error . – TN888 Jan 30 '13 at 14:11
  • The problem was with the framework version. It was saying that it's the newest version and one day it just prompted something like "The version of you framework is old. Do you want to instal the newest?" And now it's woring fine on both devices. So anyway thank you for help. – egst Jan 30 '13 at 14:59