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

Logcat not producing logs

Discussion in 'Android Rooting' started by SavageRobot, May 31, 2016.

  1. SavageRobot

    SavageRobot Android Expert
    Thread Starter
    Rank:
    None
    Points:
    173
    Posts:
    870
    Joined:
    Jan 23, 2012

    Jan 23, 2012
    870
    477
    173
    Male
    Wales
    I have used Logcat before and I'm sure all I did was open app and it would populate with the logs. I haven't used them much so maybe there is something I am missing. I have installed CatLog and aLogcat and both just come up with nothing.

    I have an app that force closes when I use it and would like to send the dev a log to see if he knows whats happening.
     

    Advertisement

  2. scary alien

    scary alien not really so scary
    Moderator
    Rank:
     #8
    Points:
    2,138
    Posts:
    22,293
    Joined:
    Mar 5, 2010

    Mar 5, 2010
    22,293
    23,649
    2,138
    Male
    space alien ;)
    Indy
    Hey @SavageRobot, I know Google made some security changes to accessing the logcat a few versions back, but you might want to try using (invoking) the "logcat" command from an adb or Terminal Emualator for Android session as a first step.

    Then you can fire-up one of the apps you mentioned above and see if the logcat command's output reveals what might be going on with those apps...

    edit: running the paid (donate) version of aLogcat doesn't produce much output for me--I kind of think an app can only see its own logcat entries (i.e., again, related to recent security changes to the API related to logcat--not a restriction imposed on the logcat command itself when launched from a shell prompt).
     
    #2 scary alien, May 31, 2016
    Last edited: May 31, 2016
    SavageRobot likes this.
  3. scary alien

    scary alien not really so scary
    Moderator
    Rank:
     #8
    Points:
    2,138
    Posts:
    22,293
    Joined:
    Mar 5, 2010

    Mar 5, 2010
    22,293
    23,649
    2,138
    Male
    space alien ;)
    Indy
    Also, the logcat command (from a terminal emulator session) has a few options that you can do a "one-shot" launch of it instead of having it continuously output/monitor (i.e., the default behavior w/out arguments).

    So, doing logcat -f /sdcard/mylogcat -d is a useful command to dump the current contents of the system log to the specified file (i.e., for later review).

    Other options are available, too, that might be useful in your case:

    -t <count> (prints only the most recent <count> lines)​
     
    SavageRobot likes this.
  4. SavageRobot

    SavageRobot Android Expert
    Thread Starter
    Rank:
    None
    Points:
    173
    Posts:
    870
    Joined:
    Jan 23, 2012

    Jan 23, 2012
    870
    477
    173
    Male
    Wales
    Thanks @scary alien my head is hurting too much to look at this now, I don't have that much experience at all with terminals etc so didn't know how to get the logcat authorised. As it happens the dev actually posted a fix for my problem anyway so don't need it now. I'll look more into ADB way another time as I don't have my cable with me anyway and it has been a long day, the pub is calling :)
     
    scary alien likes this.
  5. scary alien

    scary alien not really so scary
    Moderator
    Rank:
     #8
    Points:
    2,138
    Posts:
    22,293
    Joined:
    Mar 5, 2010

    Mar 5, 2010
    22,293
    23,649
    2,138
    Male
    space alien ;)
    Indy
    Cheers, @SavageRobot -- no hurry or worries :).

    You can do all of the above commands from a Terminal Emulator for Android session, so adb isn't actually required.

    Ping me back if you ever need help with this :).
     
    SavageRobot likes this.

Share This Page

Loading...