[GUIDE] Easiest Way to Utilize Matlog

Search This thread

skingg

Senior Member
Dec 25, 2011
262
56
Google Pixel 7 Pro
This will not help determine the kind of problems a random reboot is caused by. You need to look in proc/last_kmsg, or send your dev the last_kmsg when that occurs

Team BlackOut... or Back Out - "These colors that you've shined are surely not your style”

Sorry but I'm relatively new in this. Where can I locate the last_kmsg? So do I just 'not record' the logs, but when I get a random reboot and go back into home, I go into Catlog and save the log file?
 

Primokorn

Senior Member
Nov 17, 2012
11,560
7,754
OnePlus 8 Pro
Sorry but I'm relatively new in this. Where can I locate the last_kmsg? So do I just 'not record' the logs, but when I get a random reboot and go back into home, I go into Catlog and save the log file?
You can't take last_kmsg through Catlog app.
Give a try to this one instead: http://xdaforums.com/android/apps-games/root-andy-log-spare-logging-scenarios-t2910334

EDIT: the file is located into /proc/last_msg so you don't even need an app to grab it.
 
Last edited:

skingg

Senior Member
Dec 25, 2011
262
56
Google Pixel 7 Pro
By the way, I finally got what you guys meant by /proc/last_msg. I'll post it in the appropriate thread when and if I get another reboot. Thanks again.
 

Train88

Inactive Recognized Themer
Oct 8, 2013
1,938
14,182
Greenville, SC
OnePlus 8

mwebb34

Senior Member
Sep 9, 2012
3,171
396
I have nexus 6 and I'm currently running dirty unicorns V9.5 5.1.1 I'm having FCs on stock browser like 3 or 4 a day, I know it's hard to believe that I'm having FCs on stock but I am. I'm need to find out why this is happening so I can help the DEV find a fix. I downloaded Andy-root but like I said I'm clueless on log-cat stuff.,lol. Thanks for any help.

Sent from my Nexus 6 using Tapatalk
 

gordo2212

Senior Member
Aug 31, 2013
184
139
I have nexus 6 and I'm currently running dirty unicorns V9.5 5.1.1 I'm having FCs on stock browser like 3 or 4 a day, I know it's hard to believe that I'm having FCs on stock but I am. I'm need to find out why this is happening so I can help the DEV find a fix. I downloaded Andy-root but like I said I'm clueless on log-cat stuff.,lol. Thanks for any help.

Sent from my Nexus 6 using Tapatalk

Just follow the OP step by step. There's pictures and everything.

Sent from my LG-D851 using Xparent Skyblue Tapatalk 2
 

Primokorn

Senior Member
Nov 17, 2012
11,560
7,754
OnePlus 8 Pro
Hmm, that's odd. I've used it on Pure Nexus and DU. I love the widget for recording

Sent from my Nexus 6P using Tapatalk

I'm using it on CM13 just fine

Sent from my Nexus 5 using Tapatalk
Probably related to CM13 CAF since Logcat Extreme doesn't work either...

EDIT @djdarkknight96 I guess you are using the built-in CM SuperUser, right? Chainfire said that root apps will have to be updated to support the systemless root.
I think it doesn't work with SuperSU v2.6+ only.

EDIT2
It works well with CM SuperUser...
 
Last edited:
Probably related to CM13 CAF since Logcat Extreme doesn't work either...

EDIT @djdarkknight96 I guess you are using the built-in CM SuperUser, right? Chainfire said that root apps will have to be updated to support the systemless root.
I think it doesn't work with SuperSU v2.6+ only.

EDIT2
It works well with CM SuperUser...
Yep I use what's included and it's working great.

Sent from my Nexus 7 using Tapatalk
 

Primokorn

Senior Member
Nov 17, 2012
11,560
7,754
OnePlus 8 Pro
As you know Catlog app is discontinued for several years. Its dev recommends MatLog (fork of Catlog).
I have a little issue when recording from the widget so I hope it will be fixed soon :)
MatLog is a free and open-source material-style log reader for Android based on CatLog.

It shows a scrolling (tailed) view of the Android "logcat" system log, hence the goofy name. It also allows you to record logs in real time, send logs via email, and filter using a variety of criteria.
 
  • Like
Reactions: djdarkknight96

Top Liked Posts

  • There are no posts matching your filters.
  • 44
    Due to the numerous times we (Developers/Team BlackOut) have to ask for logcats on miscellaneous crashes, I searched for different guides to link people to. There are several, but none were as simple and straightforward to understand as the method that I personally use for both theme chooser and my Team BlackOut apps. You may have heard of, or used, Matlog before...But it appears that this method of using Matlog is not as well known (or only used by people like me), which is another reason I am creating this thread. NOTE: this method is for those who can replicate the actions needed to cause a crash fairly quickly (I hate long logcats!)

    If you are a Team BlackOut follower, I assume you have read DJ's instructions on giving us a log before. It is simple and logical, but the information we need is not necessarily always in the screenshots you send us via that method.


    YOU MUST BE ROOTED IN ORDER TO GET A LOGCAT (with apps like Catlog, matlog, or by using ADB).


    PLEASE NOTE, THIS DOES NOT WORK FOR KERNEL RELATED ISSUES! Getting the "last_kmsg" from /proc/ is the best method for random reboots and other kernel related problems.


    PROCEDURE:

    1. Search for, and download, Matlog from the Play Store (or the Holo version floating around xda; I assume it works the same)
    Play Store Listing


    2. Long press on your homescreen, create the Matlog widget (1x1)






    3. Click on the Matlog widget. This will prompt a dialog for you to change/confirm the name for the log's .txt file (if you so please)





    4. Repeat the action (such as opening an app) that caused you to get a force close.



    5. As soon as you get the "XXX has force closed/stopped working", go back to your homescreen (or whichever screen you placed the widget on) and click on the widget again. NOTE: This will open your recorded log within the Matlog app. Unless you know how to debug, you don't need to worry about that...you can just close it.





    6. After exiting the log that you just recorded, open up the file explorer of your choice. Scroll down until you see the "catlog" folder. Inside of that will be "Saved Logs", which is where you will find the .txt file containing the recorded logcat.






    7. Then send that puppy on over to your developer of choice. :D


    AND THAT'S IT! :good: (Although, I must say...Please send them in a PM unless the devs specify otherwise. Logs quickly clutter threads IMO)
    6
    Mine to even though it's trouble shooting 101 basics.
    5
    Sweet!!!! Going in the sig!!! :good::good::good::good:
    4
    Mine to even though it's trouble shooting 101 basics.
    True, but unfortunately not everyone appears to know much of the logcat methods despite all the guides. None of them are technically difficult though

    Team BlackOut... or Back Out
    4
    @Train88

    Nice little writeup! It may be outside the scope of the thread, but you got any good resources for actually reading and using logs? Before I ask someone else to help me solve an issue I'm having with an app I'm inverting, I'd like to see if I can figure it out myself. Thanks!

    Edit: nvm. I just found some stuff [emoji4]

    http://xdaforums.com/showthread.php?t=2274119
    While that is definitely a nice write up, it seems more for general debugging from quickly skimming it. There are ways for a log to point you directly to the mistake, but I just kinda learned as I went along with theming.

    For example, I have this error, as we speak, with the newest Pandora.

    4d39e697f69c0b3da443370e64025939.jpg



    Because I've been responsible for Pandora and themed it so many times now, I know to go look in the android manifest and see what style is associated with that activity causing the error. Then I go redirect that style accordingly and hopefully its fixed lol [emoji28]

    Team BlackOut... or Back Out