Thread: Log Files
View Single Post
Old 10-10-2022, 07:08 PM   #2
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by Fatespinner View Post
Hi all,

I have a problem with my reader. It randomly freezes. I want to find the root cause of the failure. Are there any log files where errors and exceptions and problems are recorded?
If yes, how can I access them?
There're no log files on android. There is a (fairly large) ring buffer where all apps and services dump their messages. It can be pretty messy as most android devices out there are very verbose in nature.

You can access with
Code:
adb logcat
but usually, without any kind of filters, is impossible to read in real time.


You can do some filtering by telling logcat you're interested in warnings or above for all tags.

Code:
adb logcat *:W
, find meaningless tags that are superverbose, filter them with
Code:
adb logcat *:W AnnoyingTag:S
and repeat it n times until you get something readable.

But if the device in question is the one of the signature I would recommend (in order, accumulative)

1. try to reproduce freezes with a different launcher
2. try to reproduce freezes with all your documents in a folder with a ".nomedia" file
3. try to reproduce freezes with google play services disabled.

Hopefully it is the launcher
pazos is offline   Reply With Quote