What is Reddit's opinion of
MatLog: Material Logcat Reader?
From 3.5 billion Reddit comments
Popularity Score: 17
This app was mentioned in 28 comments, with an average of 1.68 upvotes
Best Comments
I am not seeing that, but you can report the issue by capturing a logcat from your phone.
You can use https://play.google.com/store/apps/details?id=com.pluscubed.matlog to capture a log during a crash and report it to https://github.com/mozilla-mobile/fenix/issues
Reach out if you need help with this.
Perhaps you can try running a catlog and try to get that crash come up again, then stop the catlog recording and look for error or crash entry.
I don't use catlogs much but it should pick those crashes up.
I like using this app whenever I need to do one: https://play.google.com/store/apps/details?id=com.pluscubed.matlog
If you don't have root access, you can just grant the app extra permissions via ADB.
Alternatively, you can use ADB to capture a catlog.
Grab Matlog and grant it root. Then click the overflow (triple dot) menu, press log level and set it to debug. Then, go back into the overflow menu, press file and then record. When you're done, click the save button.
Alternatively, if you don't have root access, you can use the Android Debugging Bridge. adb logcat -f [/path/to/file/on/phone.txt] *:D (the level of logging). Once you press enter, it will begin logging. When you're ready to stop, press Ctrl+C.
Logcat is an Android tool that serves to dump a bunch of random system output into readable form for investigating crashes, bugs, and all kinds of other things.
You can access it with apps like these but I don't know whether DBrady would rather have a saved logfile or a screenshot of the log at the time of the app's crash. The general way to use it is to open logcat right after the crash, hit pause, save the file, and send it to the developer.
>u/Giiiirico - Essential-ph1 on 19-20220912-NIGHTLY-mata sometimes it hang and boot by itself
It could be a hardware issue, something you installed or a LineageOS issue.
You could try using an app on the phone like MatLog on F-Droid (or MatLog in Play Store) to capture a logcat of the moment it's crashing before rebooting.
MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:
adb devices
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem. After automatically stopping the recording when the device is crashing & rebooting the logcat is automatically saved in > internal sdcard > matlog > saved_logs.
Then open the logcat in Notepad++, WordPad or similar & search it with chatty or crash or Beginning of crash or killing for example, etc.
>u/AMinfinity1981 - LineageOS on Moto G7 Plus reboots randomly and sporadically resulting in corrupted SD Card.
No setup description (GApps, Magisk & modules, etc) makes it very difficult to troubleshoot.
It could be a hardware issue, something you installed or a LineageOS issue.
If you chose Internal storage for the Micro SD card (a.k.a. adoptable storage) when formatting the card in the device that may explain your issue because it's unstable & not recommended.
You could try using an app on the phone like MatLog on F-Droid (or MatLog in Play Store) to capture a logcat of the moment it's crashing before rebooting.
MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:
adb devices
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem. After automatically stopping the recording when the device is crashing & rebooting the logcat is automatically saved in > internal sdcard > matlog > saved_logs.
Then open the logcat in Notepad++, WordPad or similar & search it with chatty or crash or Beginning of crash or killing for example, etc.
The best way to confirm or rule out a hardware issue is to flash the most recent stock manufacturer's OS for your device & test thoroughly.
This will also update the vendor's firmware, modem, bootloader etc.
>u/elfamosoxd56 - ...Poco X3 NFC with LineageOS 19.1 and get freezes and auto restart several times a day...
It could be a hardware issue, something you installed or a LineageOS issue.
You could try using an app on the phone like MatLog on F-Droid (or MatLog in Play Store to capture a logcat of the moment it's crashing before rebooting.
MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:
adb devices
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem. After automaticlly stopping the recording when the device is crashing & rebooting the logcat is automatically saved in > internal sdcard > matlog > saved_logs.
Then open the logcat in Notepad++, WordPad or similar & search it with chatty or crash or Beginning of crash or killing for example, etc.
The best way to confirm or rule out a hardware issue is to flash the most recent stock manufacturer's OS for your device & test thoroughly.
This will also update the vendor's firmware, modem, bootloader etc.
I normally use a computer to troubleshoot a logcat because there is too much stuff in there for a small screen IMO.
You could try using an app on the phone like MatLog on F-Droid (or MatLog in Play Store to capture a logcat
MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:
adb devices
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem.
After you stop the recording you can search it using MatLog's features.
Or you can pause the live logcat & search it.
I have had good luck with:
- opening https://play.google.com/store/apps/details?id=com.pluscubed.matlog
- Clearing the log
- Causing the crash
- Saving the log
Hope that helps. Otherwise, there is https://github.com/mozilla-mobile/fenix/wiki/Logging-Crash-Information
Have you tried searching for just "aptx" or "codec" since "select codec" seems a bit specific and doesn't return anything. If it isn't using aptx, it's probably defaulting to sbc.
Check out matlog btw, it's a little newer.
Maybe a Logcat might show something. The trick is catching the freeze or reboot. An app, this one has the ability to record logs I believe and might help: https://play.google.com/store/apps/details?id=com.pluscubed.matlog
Scaricati MatLog e genera un log della radio oppure, se sai usare ADB, fai un
adb logcat -b radio
E postaci da qualche parte il contenuto del buffer radio di logcat. Togli i riferimenti all'ICCID o gli ID delle celle.
Così vediamo cosa combina il RIL quando perdi il segnale.
Considera che LineageOS non modifica il modem/baseband del cellulare e che questi fenomeni possono essere dovuti solo al modem stesso.
you don't need root to get logs, can do it via adb alone.
Matlog, you just need to run the commad(shown within the app) once.
>u/rwmarch - Moto X4 {payton} Spontaneous reboot ...Google Apps ARM64 package. On restart, I installed my X4 apps and data from a Google cloud backup...
To try to find the issue connect your device to a computer and try capturing a continuous logcat that will be saved in the folder where you are running adb when the device turns off or reboots or until you stop it with ctrl+c:
adb devices
adb logcat > logcat_Unwanted_Reboot.txt
Then open the logcat in Notepad++, WordPad or similar & search it with chatty or crash or Beginning of crash or killing for example, etc.
Or use an app on the phone like MatLog (also available on F-Droid) or Logcat Extreme to record the crash & reboot.
MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem & after the device reboots > internal sdcard > matlog > saved_logs.
Or press on the MatLog icon to create a Record shortcut.
Rule of thumb: the larger the GApps package the more chance of errors.
I prefer the smaller Pico package & just add the extra apps I need from Play Store and https://f-droid.org/
See Open GApps Package Comparison.
Which one did you install? Pico, Nano, etc?
Looks like the post/link was removed so I'll just leave this link here:
https://play.google.com/store/apps/details?id=com.pluscubed.matlog
Root and this app: https://play.google.com/store/apps/details?id=com.pluscubed.matlog
Or Matlog
You can try something like https://play.google.com/store/apps/details?id=com.pluscubed.matlog but I haven't tried it on Android TV.
https://wiki.lineageos.org/how-to/logcat
https://developer.android.com/studio/command-line/logcat
https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=pt_BR&gl=US
That last one (app) save the logs on sd card. The commands via adb I think save the logs on PC.
>u/EetsGeets - Problem with frequent restarting on Galaxy Note 10+ 5G (SM-N976B)
You could try using an app on the phone like MatLog on F-Droid (or MatLog in Play Store to capture a logcat of the moment it's crashing before rebooting.
MatLog requires root permission or if you don't have root, connect to a computer & copy/paste this in adb to grant the required permission:
adb devices
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Reboot to make the logcat shorter & more relevant, MatLog > 3-dots > File > Record then reproduce the problem. After automaticlly stopping the recording when the device is crashing & rebooting the logcat is automatically saved in > internal sdcard > matlog > saved_logs.
Then open the logcat in Notepad++, WordPad or similar & search it with chatty or crash or Beginning of crash or killing for example, etc.
>...I bought this phone refurbished a...it may have been damaged when I bought it. I only did a cursory test with Samsung's OS before installing Lineage...
The best way to confirm or rule out a hardware issue is to flash the most recent stock Samsung manufacturer's OS for your device.
This will also update the vendor's firmware, modem, bootloader etc.
Their paywall policies varies apparently randomly depending on the device & age of the OS but I used both sammobile.com & updato.com to download stock Samsung OS. Some users recommend samfw.com.
They all have flashing instructions using Odin3 in their respective download pages.
It does not matter for which country as long as it's made for your exact model number.
Usually the more recent, the better.
Test thoroughly while on stock Samsung OS for a couple of days.
>...Another issue that I keep having is losing LTE connection. This mostly happens while on the move, presumably when my connection changes towers. It typically reverts to 3G...
Maybe not directly related tp your issue but FYI LineageOS does no support VoLTE on any Samsung devices @ the present because the devs could not reverse engineer Samsung's proprietary VoLTE implementation so far.
That could be a deal breaker if your network provider drops 2G & 3G as only VoLTE will work for voice calls after that.
This works for me - https://play.google.com/store/apps/details?id=com.pluscubed.matlog
>u/stressedtux - ...Lineage Mido (build Jan 16 2020). The thing is, it reboots literally every time that i reach a subway station (in fact, this happens with 3 specific stations). Im not sure if its because there is no signal for a moment or something but is it possible that somekind of behaviour triggers that reboot?...
Not enough setup description to troubleshoot: Magisk & modules if any, GApps package name & build date, etc.
Do you have the most recent baseband/modem/radio for your device?
Did you install a GApps package & have Smart Lock > Trusted location enabled?
You could use an app like MatLog: Material Logcat Reader & capture in real time what's causing the crash in a logcat.
If you don't have root, connect to computer & copy/paste this in adb to grant permission to Matlog:
adb shell pm grant com.pluscubed.matlog android.permission.READ_LOGS
Before reaching the subway station: * Matlog > Settings > Clear > File > Record. * Reproduce the problem by reaching the subway station. * After the unwanted reboot: copy to computer the logcat created in /data/media/0/matlog/saved_logs (a.k.a. the internal sdcard). * Open the logcat with WordPad, Notepad++ or similar & search the logcat with "crash" or "beginning of crash" or "has died". Or "fatal".
You could also upload it somewhere like pastebin, share the link & we could take a look in it.
>...I know that is a nightly version and that there are a lot of bugs going on about reboots...
Nightly is just a label for the 16.0 builds which are currently automatically built every day regardless if they are changes or not.
LineageOS 16.0 will be changed to weekly once the official 17.1 is launched which will be build nightly.
They are stable & official, not WIP or beta.
I had exactly zero unwanted reboots in 10 months which is when I clean installed including Format Data instead of a simple wipe my daily driver: Galaxy S5 G900M LineageOS 16.0 klte currently updated to build 2020-02-06 + Open GApps Pico + LineageOS AddonSU.
I noticed in your Reddit profile created in 2017 that you have only 1 post & 0 comment @ the present. Are you one of those throwaway people that will delete this thread & destroy our posts? (>_<)
Can you install Matlog https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=en_US - collect a log and report a bug?
Download an app like Matlog. Then watch as you perform the action in the application. You should get some clues.
https://play.google.com/store/apps/details?id=com.pluscubed.matlog
I use matlog which I 'think' is what you are looking for?
https://play.google.com/store/apps/details?id=com.pluscubed.matlog&hl=en_GB