FORUMS

[GUIDE] Easiest Way to Utilize Matlog

1,936 posts
Thanks Meter: 14,214
 
By Train88, Recognized Themer on 3rd September 2014, 05:36 AM
Post Reply Email Thread
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.


AND THAT'S IT! (Although, I must say...Please send them in a PM unless the devs specify otherwise. Logs quickly clutter threads IMO)
The Following 44 Users Say Thank You to Train88 For This Useful Post: [ View ] Gift Train88 Ad-Free
3rd September 2014, 05:40 AM |#2  
djdarkknight96's Avatar
Recognized Themer
Flag Springfield
Thanks Meter: 47,070
 
Donate to Me
More
Sweet!!!! Going in the sig!!!
The Following 5 Users Say Thank You to djdarkknight96 For This Useful Post: [ View ] Gift djdarkknight96 Ad-Free
3rd September 2014, 05:59 AM |#3  
Senior Member
Flag Anchorage
Thanks Meter: 20,983
 
More
Mine to even though it's trouble shooting 101 basics.
The Following 6 Users Say Thank You to zelendel For This Useful Post: [ View ] Gift zelendel Ad-Free
3rd September 2014, 06:03 AM |#4  
Train88's Avatar
OP Recognized Themer
Flag Greenville, SC
Thanks Meter: 14,214
 
Donate to Me
More
Quote:
Originally Posted by zelendel

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
The Following 4 Users Say Thank You to Train88 For This Useful Post: [ View ] Gift Train88 Ad-Free
3rd September 2014, 06:30 AM |#5  
Mazda's Avatar
Retired Recognized Developer
Flag Milton, Florida
Thanks Meter: 12,605
 
More
Good job @Train88
The Following 2 Users Say Thank You to Mazda For This Useful Post: [ View ] Gift Mazda Ad-Free
3rd September 2014, 06:59 AM |#6  
Senior Member
Thanks Meter: 162
 
More
Thanks Train, excellent help as always.
The Following User Says Thank You to Mao04 For This Useful Post: [ View ] Gift Mao04 Ad-Free
3rd September 2014, 07:52 AM |#7  
matrixzone's Avatar
Senior Member
Thanks Meter: 3,596
 
Donate to Me
More
Thanks
16th September 2014, 12:16 AM |#9  
LeftyGR's Avatar
Senior Member
Flag Bloomington, IL
Thanks Meter: 1,722
 
More
@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

http://forum.xda-developers.com/show....php?t=2274119
16th September 2014, 12:52 AM |#10  
Train88's Avatar
OP Recognized Themer
Flag Greenville, SC
Thanks Meter: 14,214
 
Donate to Me
More
Quote:
Originally Posted by LeftyGR

@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

http://forum.xda-developers.com/show....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.




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

Team BlackOut... or Back Out
The Following 4 Users Say Thank You to Train88 For This Useful Post: [ View ] Gift Train88 Ad-Free
16th September 2014, 03:03 AM |#11  
LeftyGR's Avatar
Senior Member
Flag Bloomington, IL
Thanks Meter: 1,722
 
More
Yeah. So learning this is a bit o' trial and error. . Which is what I figured. I got two smali files that show errors, and I figured out the lines for each. But fuzzy past that right now. But if I follow your logic, it's a good bet the error is linked to those lines in smali and androidmanifest? Thanks for the reply, and I'll stop stretching the topic.
The Following User Says Thank You to LeftyGR For This Useful Post: [ View ] Gift LeftyGR Ad-Free
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes