user1210233
user1210233

Reputation: 2930

Android device appears offline despite plugging in USB and switching on USB debugging

I'm trying to run my Android app on a Samsung Galaxy Ace. Despite plugging in the USB and enabling debugging, when I try to run the app, Eclipse prints out a message saying

[2012-07-14 22:56:19 - Cricket] Android Launch!
[2012-07-14 22:56:19 - Cricket] adb is running normally.
[2012-07-14 22:56:19 - Cricket] Performing nikhil.android.cricket.MainActivity activity launch
[2012-07-14 22:56:19 - Cricket] No active compatible AVD's or devices found. Relaunch this configuration                     after connecting a device or starting an AVD.

I'd like to add that I've been trying a lot but am unable to do anything. I tried killing adb and restarting it. Same error. Also, I am able to run it instantly when I connect my friend's Samsung Galaxy Note. But it won't run on my Samsung Galaxy Ace. I'd appreciate any help I can get on this.

Upvotes: 15

Views: 35685

Answers (18)

Zar E Ahmer
Zar E Ahmer

Reputation: 34370

Open Window Task Manager and and close adb.exe. Resolve my issue. And also reset USB Debugging.

Upvotes: 0

Dmitry Bryliuk
Dmitry Bryliuk

Reputation: 106

using newest adb helped, thanks Akif. use kill-server and then start-server with newest adb. also it will fix some other issues.

Upvotes: 0

akifusenet
akifusenet

Reputation: 192

I had this problem with my new updated to Kitkat GT-N7100. I tried everything

  • unhidden developer menu & enable USB debugging
  • reset ADB
  • installing latest USB device driver
  • installing laest KIES

none worked.

Device always looked offline in ddms.

If you tried all this and still no use then try this:

http://www.droidextra.org/2013/12/24/solved-fix-adb-devices-offline-100-working.html

It worked for me.

Akif,

Upvotes: 1

NameSpace
NameSpace

Reputation: 10177

I tried everything in this list to no avail, with a Samsung galaxy 5 (4.4.2). The only way I got it to work finally was to select the option to "revoke USB debugging authorization" which caused my phone to prompt me to authorize my computer to debug with it -- only then did it appear "online."

Installing the newer newer google / samsung drivers with the enhanced usb debugging security seems not to trigger an authorization prompt by itself. Seems you need to help it along by revoking all previous authorizations even on a new phone.

Upvotes: 1

Sourav Saica
Sourav Saica

Reputation: 1

No need of doing this all .

Just restore your pc to earlier time . it is on control panel,system and security.

Upvotes: -3

user3137648
user3137648

Reputation: 786

  1. First download the USB driver for your android phone from their respective site. For samsung phone you can use this link.
  2. Click on reset abd.
  3. Reboot your phone.

This worked for me when I encountered the same problem.

Upvotes: 0

António Almeida
António Almeida

Reputation: 10117

Windows:

Start Menu button > type: cmd

Problem, the device is offline:

adb devices

List of devices attached
07952b41offline

  1. adb kill-server
  2. adb start-server (Wait some seconds ...)
  3. adb devices

List of devices attached
07952b41device

Upvotes: 1

UMAR-MOBITSOLUTIONS
UMAR-MOBITSOLUTIONS

Reputation: 78004

Just reboot the phone, it will solve your issue. no need to adb restart is required.

Upvotes: 5

Fakhar Iqbal
Fakhar Iqbal

Reputation: 4069

To install the Android USB driver on Windows 7 for the first time:

  1. Connect your Android-powered device to your computer's USB port.
  2. Right-click on Computer from your desktop or Windows Explorer, and select Manage.
  3. Select Devices in the left pane.
  4. Locate and expand Other device in the right pane.
  5. Right-click the device name (such as Nexus S) and select Update Driver Software. This will launch the Hardware Update Wizard.
  6. Select Browse my computer for driver software and click Next.
  7. Click Browse and locate the USB driver folder. (The Google USB Driver is located in \extras\google\usb_driver.)
  8. Click Next to install the driver. Or, to upgrade an existing Android USB driver on Windows 7 with the new driver:

Upvotes: 1

nikos.t
nikos.t

Reputation: 51

You might have to change the active USB computer connection setting. I had the same problem while running a Beanstalk custom rom based on Android 4.3. It was solved by switching from the default Media device (MTP) to Mass storage. The device was then automatically recognized by eclipse.

Upvotes: 1

Mehmet Melik Kose
Mehmet Melik Kose

Reputation: 348

You need to "reset ADB". After that your device may ask

Allow USB debugging?

On that screen, checking

always allow from this computer

may resolve your problems in the future for that device and computer. See more info: https://stackoverflow.com/a/16224992/143808

Upvotes: 0

K.T.
K.T.

Reputation: 83

Just do one thing change you minsdkVersion to 8,in your manifest file it surely works....

> android:minSdkVersion="8"

Upvotes: 0

jackie
jackie

Reputation: 21

I had same problem with my HTC phone, which works well with other app until I use the android google play services for maps v2. You may find the link below for how to install the sample.

http://nlabs.wordpress.com/2012/12/13/the_maps_sample_from_google_play_services/

I tried the suggestions made in this thread with no progress.

I then found my error that I did not overwrite the default setting below, but instead I add my entries. So I made the correct, and still got the same error.

<meta-data
    android:name="com.google.android.maps.v2.API_KEY"
    android:value="inter your code" />

I then run the debug mode. It worked. Once at the HTC, I was prompted to install the 'Google Play Services', which is expected and install works.

Upvotes: 0

Nicholas Chubrich
Nicholas Chubrich

Reputation: 23

There may be no problem with Eclipse. Try running adb shell and see if it connects to your device. If it doesn't, this may signal any number of problems: with your USB port (try a different one and/or unplugging other peripherals), with your OS (try restarting), with your USB cable (try a different one), or the phone (try rebooting it or try a different one).

Eclipse is only the last link in the chain.

Upvotes: 0

love2script12
love2script12

Reputation: 210

In AndroidManifest.xml, see that your minSdkVersion and targetSdkVersion match your device.

Upvotes: 0

mobile
mobile

Reputation: 361

Go to DDMS in Eclipse IDE.

There is one menu: Expand that menu and select the Reset adb option.

Wait for a few seconds, it will reset your selected ADB device.

Upvotes: 32

Smily
Smily

Reputation: 2674

if your Samsung mobile driver not install successfully then also this problem may occur

so download driver from following link and install it in your PC link

Upvotes: 0

Vikas
Vikas

Reputation: 4301

I also faced the same problem with Samsung Google nexus. I use Mac and I followed these steps to solve my problem

If you are developing on eclipse skip step 2

1: Enable USB debugging on your phone.
for lesser than 3.2 version go to Settings->Applications-> development
for versions 4.0 and higher its in Settings->development
for 4.2 its hidden. Go to Settings->about phone and tap build number 7 times (message will appear that you are a developer now)

2: In your manifest file add android:debuggable="true" to the application element

Upvotes: 1

Related Questions