1. Download our Official Android App: Forums for Android!

Support Something is "crashing" my TB. How do I read this logcat log?

Discussion in 'Android Devices' started by mudking, Apr 10, 2011.

  1. mudking

    mudking Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    136
    Joined:
    Mar 12, 2011

    Mar 12, 2011
    136
    6
    36
    My phone turned itself off today in my pocket 3 times. It don't reboot, it was just off. I assume it has something to do with lockbot, because I just installed it today. I want to double check though, and possibly contact the developer about it. So, I set up in adb and got the log with the logcat command. Looking at this, I have no idea how to read it to see where the shutdown occurred. It has no time stamps or anything either. Is this even the right log to be looking for what I'm looking for? How do I find the last running process before the shutdown?
     

    Advertisement

  2. Dark Jedi

    Dark Jedi Guest
    Rank:
    None
    Posts:
    0
    Joined:

    Just uninstall the app.and if the phone don't turn itself off then it was the app
     
  3. mudking

    mudking Well-Known Member
    Thread Starter
    Rank:
    None
    Points:
    36
    Posts:
    136
    Joined:
    Mar 12, 2011

    Mar 12, 2011
    136
    6
    36
    But I really want to learn how to troubleshoot things like this. I'd like to have a very basic understanding of how to read the logs. Am I on the right track with the log I have? Is there a reference somewhere that will help me learn how to check logs for errors?
     
  4. ska.t73

    ska.t73 Android Expert
    Rank:
    None
    Points:
    163
    Posts:
    1,659
    Joined:
    Mar 11, 2010

    Mar 11, 2010
    1,659
    305
    163
    Phoenix, AZ
    Logcat is deffinetely what you are looking for. Not sure how to read them really but there are guides out there on google that should be able to help you with it.
     
  5. Silent Thunder

    Silent Thunder Well-Known Member
    Rank:
    None
    Points:
    38
    Posts:
    201
    Joined:
    Mar 17, 2011

    Mar 17, 2011
    201
    14
    38
    Do a master reset then just don't re install the bad app.
     

Share This Page

Loading...