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 1051523
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T16:56:49+00:00 2026-05-16T16:56:49+00:00

I am testing my app on my actual device, and it seems like there

  • 0

I am testing my app on my actual device, and it seems like there is a memory leak. The app has crashed after a couple of hours. How can I pull up the log of the crash?

I plugged my phone in via USB and tried:

adb logcat -v

but I get the following message in my terminal:

- waiting for device -
error: more than one device and emulator

How can I diagnose my crash?

  • 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-05-16T16:56:50+00:00Added an answer on May 16, 2026 at 4:56 pm

    That’s because there’s…

    more than one device and emulator

    The error is fairly clear. So, what you do in this case is:

    adb devices
    

    And it lists the name of your devices/emulators. Then:

    adb -s name-of-your-device logcat 
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am testing a blackberry app that sends SMS messages. I would like to
The Info I recently launched an app on the AppStore. After testing on the
I'm trying to build a small testing app with erlang+mnesia. I have a user
In testing an app, I keep getting errors that occur sporadically on only one
I'm testing an app that reads thousands of small objects and sends then back
I am testing my app in two different devices. My app is relies heavily
I am just testing an app to get data off our web server, previously
I am testing my app on a rooted Nexus S phone. I finally have
I am testing my app on different devices and on the Motorola Razr the
I have been recently testing my app in a strict mode to detect disk

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.