What is Reddit's opinion of
CatLog - Logcat Reader!?
From 3.5 billion Reddit comments
Popularity Score: 31
This app was mentioned in 34 comments, with an average of 1.44 upvotes
Best Comments
Its hard to known for sure yet. This doesn't seem to be an area that Xiaomi are to focused on.
It does require that Xiaomi pay the license fees. For example my Mi Note 3 has a 660 cpu which is able to support aptx but running stock MIUI it does not use it. There is also no mention of aptx support by Xiaomi or anyone else. But the hardware is there. Im currently running epicrom and aptx is working perfectly. There are also other zip files that can be flashed to possibly enable it. This all requires root though.
Obviously out of the box support would be great. But there are ways around it if needed.
For those curious, who are rooted with aptx enabled headsets. Root is needed, CatLog needs to be installed. And with it running if you connect to your headset and use the search bar for look for any mention of "aptx"
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
Download Catlog. Google Play Link
You can choose to record and instantly write to a .txt file, if your phone reboots, you may find the app/service/.. that causes it at the end of this file.
You should be able to find the smoking gun with catlog:
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
​
It reads all the system log
Can you install something like Catlog and see if anything is logged in general? https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en CatLog - Logcat Reader! - Android Apps on Google Play
The app just...closes itself? Where does it pushes you to? Your homescreen? And what OS are you using?
Do you have any "battery saver app" or Greenify app maybe?
It could be that there is some apps interfering. One other thing you could do is download a Logcat app to read the log after the app closes itself but only if you have Android phone though.
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
CatLog requires root, but if you have crashes and such, you just open it up, hit record, launch the game, play until your problems appear, stop the log recording, save it, and upload to a support ticket.
seriously, this is the best way to get your problems resolved.
just going to the forum and saying 'my game crashed while i was spamming bombs in the cavern layer' isn't sufficient.
You could use CatLog to create a logfile; maybe there'll be a more specific error or warning you could troubleshoot further.
Install the app > start logging > turn bluetooth on, and wait for it to go wonky > stop logging
Alternatively, you could use ADB to create the same logfile, should you prefer.
It's just a suggestion, I am by no means a troubleshooting expert, but maybe you'll find out what's causing this behaviour.
Good luck!
> To see if aptX is being activated, you can check your device’s logcat using an app called CatLog. Turn on Bluetooth, pair with some aptX headphones, and play some music. If everything is working correctly, you should be able to search for aptX in CatLog and see that the a2dp encoder ‘selected codec aptX’.
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en_GB
Yep, you can use CatLog or similar to check your logs. If you want something more powerful, then enable Developer Options in your Settings app, then within there click on "Take Bug Report".
awesome. glad you got it. for others... run the app linked here while you encounter the error, then email/attach to Chainfire.
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
Alright, if you insist :)
CatLog seems like a decent logcat app, although I haven't used it since I always read logs directly from Android Studio during development.
And the systemwide bug report (assuming you are talking about "Take bug report" in Developer Options) generally isn't very helpful, so we can skip that
It sounds like it's either a ram issue, or a graphics acceleration issue.
Let's assume RAM since that's easy to check and most likely. If you go back to the settings menu and click about, one of the things on the next page should show the system RAM. Anything less than 1GB won't be able to play the game, and 1GB will probably struggle. If it is a ram issue you might get further if you killed any processes you're not using to make sure as much as possible is free(go into settings, apps, the sweep right to the running tab, and kill of everything in the list you don't need running), see if that helps.
If that isn't the issue/doesn't help there's probably not much I can help with, I'd suggest making a log cat log of the crash, and sending it on to their support email since they're likely to have more resources to understand the issue. You can do this by installing catlog and starting it recording, then generate the crash, and stop it recording(from the notification bar), then export the log by going pressing the settings button(3 dots/lines in a vertical line) and choosing save.
Hope you get it working, and do let me know if any instructions are unclear.
Is the phone still working where you can install apps or no? If so, you should INSTALL CATLOG, chances are one of the apps you've installed is corrupting the system.
I would try a factory restore again, and pay attention to what the messages are saying through the process. If done properly, there should be no reason why a reset wouldn't fix the issues with the process system.
there used to be back in the gingerbread days.. sometime in 4.x they removed the ability
edit: this was the app i used to use https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
If you have a rooted phone you can use this app to see your logcat without having to plug it into your PC.
Are you rooted by chance? I just remember this app but if you're not rooted it won't work
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
Try using catlogcatlog
It may help debug whats causing the issue.
> I need an USB cable and adb logcat to get them.
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
Install CatLog and post a log of what happens when Titanium crashes
Sorry, for not get back to you.
CatLog is the app
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
that is the app
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en
that's an example log reader ... but it does need root permissions to use which most devices won't have by default
try installing https://play.google.com/store/apps/details?id=com.nolanlawson.logcat and posting the log here (the app requires root , it might not work on your phone)
I was reading some more about this on XDA and you can enable band 12 for T-Mobile by flashing this radio in fastboot http://forum.xda-developers.com/nexus-6p/general/fastboot-activate-band-12-volte-t3239652
That also makes me think this would still be doable, if we can enable bands why couldn't we disable them with a custom radio? I'm just waiting on someone to make one :)
Really annoying my phone doesn't prefer 41 over 25 The speeds are insane, this guy is getting over 80 mbps https://www.youtube.com/watch?v=IysRUOi_RBk
Also do you know your MSL? Usually the carriers will tell you for Nexus phones since they're unlocked anyways. Basically what I said to the Sprint rep was "I have bad coverage in my area, I'd like to know my MSL to adjust band priority and hopefully obtain a better signal"
Also if you're rooted I believe you can find the MSL with CatLog https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en_GB
Basically you'll connect your device over usb to a computer, install android tools (which includes a program called adb), enable developer settings on your device, enable usb debugging on the device, then on the computer run "adb logcat") to dump the log. The [CM wiki has an intro ](to using logcat.
Alternatively, there are some apps (like the opensource app catlog ) that allow you to grab the log without doing all of that.. it just requires giving the app root permission to be able to read the system log.
You could run catlog and check if you see anything.
> adb logcat
CatLog is pretty fantastic, for future reference.
If your device can run root apps, CatLog is brilliant:
https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
(if you have multi-window support, it gets even better)