Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8737899
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 13, 20262026-06-13T10:37:31+00:00 2026-06-13T10:37:31+00:00

Possible Duplicate: Android error: Failed to install *.apk on device *: timeout keep getting

  • 0

Possible Duplicate:
Android error: Failed to install *.apk on device *: timeout

keep getting error messages when I try to launch any mobile app with android. These errors are not predictable – sometimes (like once out of 10 times) a miracle happens and everything works. But most of the time I get this error:

[ERROR] C:\Program Files\Titanium Developer\android-sdk-windows\tools\adb.exe
error: protocol fault (no status)

followed by this error later on:

[DEBUG] Waiting for device to be ready ...
[TRACE] adb devices returned 0 devices/emulators
......
[ERROR] Timed out waiting for emulator to be ready,
you may need to close the emulator and try again

The emulator starts and I get the locked screen but somehow the connection with it is lost.

I tried launching the emulator separately from a batch file as someone else suggested before I open the ti developer but I get the same errors.

Even if it runs correctly once, if I make changes and want to relaunch (without stopping or closing the emulator) I always get the errors above. I thought we are supposed to be able to keep reusing the emulator once it’s up and running but for me it never works like that.

When i try to run from eclipse it used to give the following message Failed to install Demo.apk on device 'emulator-5554': timeout

I want to run the same application without killing adb server or without closing the emulator again.

Please any help would be appreciated lot!!!!!!!!!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-13T10:37:33+00:00Added an answer on June 13, 2026 at 10:37 am

    That’s because the default ADB idle time out is 5000ms.

    Take Window -> Preferences -> Android -> DDMS. Increase your ADB time out. This will solve your problem

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Possible Duplicate: Building android source code I am getting the following error while building
Possible Duplicate: Android Launch an application from another application I am having a problem
Possible Duplicate: Problem installing my Android apps Any body can tell me how can
Possible Duplicate: Android error - close() was never explicitly called on database I have
Possible Duplicate: @Override annotation error (android prefs) I have imported a project into my
Possible Duplicate: R cannot be resolved - Android error The errors I have are
Possible Duplicate: error is showing for Digital Clock widget Application in Android I want
Possible Duplicate: Android Button Tooltip Is there any way to construct a view where
Possible Duplicate: Android Webview - Webpage should fit the device screen I want to
Possible Duplicate: R cannot be resolved - Android error I am having a issue

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.