Author Topic: Android debugging: "Device not ready, sleeping"  (Read 4794 times)

davew

  • Senior Community Member
  • Posts: 224
  • Hero Points: 6
Android debugging: "Device not ready, sleeping"
« on: March 31, 2013, 06:30:04 PM »
I'm new to Android and I hate Eclipse, so I decided to setup SE to build and debug an existing Android project on my phone. The project built successfully (debug configuration), so I decided to try and use the debugger.

When I select Build > Execute on device ..., and choose my phone, I get the following continuously:
...running C:\\Users\\wallaced\\Documents\\android\\adt-bundle-windows-x86_64\\sdk\platform-tools\adb.exe -s 856039a shell getprop init.svc.bootanim...success.
Device not ready, sleeping.


Of course, I made sure my phone was not "sleeping" and I tried the wait for debugger checkbox as well.

What am I doing wrong?

Ryan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 986
  • Hero Points: 77
Re: Android debugging: "Device not ready, sleeping"
« Reply #1 on: April 01, 2013, 04:16:06 PM »
Hi there.  So if I am understanding correctly you can't just run the app, not attempting to debug, from SlickEdit?  If you do Build > Execute on Device (don't select Wait for debugger), you get the same behavior where SlickEdit is continuously waiting for the phone to become available, even though it's obviously ready?  Or does that actually work?

Also, have you installed the latest hotfix for v17?  I think there was a hotfix built for phones which don't have the init.svc.bootanim property...which might be your problem.  If you haven't already, apply the hotfix for v17.0.3 (upgrade to v17.0.3 if you haven't already), and retest.

Thanks,

Ryan

davew

  • Senior Community Member
  • Posts: 224
  • Hero Points: 6
Re: Android debugging: "Device not ready, sleeping"
« Reply #2 on: April 02, 2013, 12:39:14 AM »
Correct, just choosing "Build > Execute on device" results in the "sleeping" message.

Here is my config:
SlickEdit 2012 (v17.0.3.0 64-bit)

Licensed number of users: Single user
License file: C:\ProgramData\slickedit\17\slickedit.lic

Build Date: November 27, 2012
Emulation: Vim

OS: Windows 7 x64
OS Version: 6.01.7601  Service Pack 1
Memory: 56% Load, 2281MB/4021MB Physical, 2275MB/8041MB Page File, 375MB/8388607MB Virtual
Shell Info: C:\Windows\system32\cmd.exe /q
Screen Size: 1440 x 900

Project Type: Java
Language: .xml (Plain Text)

Installation Directory: C:\Program Files\SlickEditV17.0.3 x64\ (non-removable drive,NTFS,126033MB free)
Configuration Directory: C:\Users\...\Documents\My SlickEdit Config\17.0.3\ (non-removable drive,NTFS,126033MB free)

Hotfixes:
C:\Users\...\Documents\My SlickEdit Config\17.0.3\hotfixes\hotfix_se1703_10_cumulative.zip (Revision: 10)

davew

  • Senior Community Member
  • Posts: 224
  • Hero Points: 6
Re: Android debugging: "Device not ready, sleeping"
« Reply #3 on: April 02, 2013, 01:49:31 AM »
I forgot to mention that I have an AT&T Galaxy 2 Skyrocket with stock ICS 4.04.

Also, I imported existing projects from http://ndef-tools-for-android.googlecode.com/files/ndeftools-all-src-1.2.3.zip with no changes. If you want to download and build it, I had to import/build ndeftools, ndeftools-utils, then ndeftools-boilerplate.

Ryan

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 986
  • Hero Points: 77
Re: Android debugging: "Device not ready, sleeping"
« Reply #4 on: April 02, 2013, 03:07:12 PM »
Thanks for the info.  I think it is the problem that I mentioned before, however I was mistaken in thinking that there was a hotfix which addressed this...it requires a new executable.  Can you submit a support case and reference this thread, and inform them that you need an updated vsandroidrun executable?  They should be able to get it to you, along with instructions on where it goes.  I will let them know you will be contacting them for this.

Hopefully this will fix it.

- Ryan

davew

  • Senior Community Member
  • Posts: 224
  • Hero Points: 6
Re: Android debugging: "Device not ready, sleeping"
« Reply #5 on: April 02, 2013, 06:31:31 PM »
Thanks Ryan. Here is the support case number: CAS-63592-3HTQ