I think it would be useful if we could create a blacklist or simply exclude messages by their tag. I have some common messages from sources that I don't need or want to see, which end up clogging recording session.

Thank you!

Would it be possible to show the process details alongside the messages?

Hello,
steps to reproduce:

1. Run app and type in some filters (or only one)
2. Close app and exit logging
3. Run app again
4. See unfiltered log appear <- Bug!
5. Open Filter list to just view the filters typed in at step 1
6. Log is now filtered

Expected would be that the existing filters are instantly applied.

And thanks for this app!

Hi,
Could you add an option to clear the logs?
Thank you.

A lot of people simply grep the logcat file for the affected app or uid when they want to report a bug. Could you please make LogcatReader put the app and the actual message on the same line in the exported file?

Current format:
[04-07 17:26:28.915 14142:14167 I/Adreno]
QUALCOMM build : 2371bd1, I8ebe47d372
Build Date : 03/12/18

Suggested format:
[04-07 17:26:28.915 14142:14167 I/Adreno] QUALCOMM build : 2371bd1, I8ebe47d372
[04-07 17:26:28.915 14142:14167 I/Adreno] Build Date : 03/12/18

Thanks for your awesome app, and especially for publishing the source code.

I think it would be great to see your app in the F-Droid store and made an request for packaging, already here.
Would this be OK for you and would you support the inclusion?

I used to use this app but when I updated to an Android 11 custom ROM the app now crashes immediately upon opening. I checked the reviews and it seems there is at least one other person who has mentioned Android 11 being the cause of this crash.

Android crash log url: https://del.dog/ecrockebuc

If my app crashes, and I open LogcatReader the stacktrace doesn't show.

In /app/src/main/res/values-zh-rCN/strings.xml line 90, the Chinese translation of 'clear' is '清除' not '清楚'.

when doing the manual, non root method to give permissions through adb, when it says it only needs to be done once, does this mean it needs to be done once but if the phone is restarted, or goes to the lockscreen, it kills it and needs to be done again the next time you use the app?

or is it persistent and doesn't need a connection to adb ever again, and can just read logs straight off the device?
(non root, android 10)

Maybe this is a bug or maybe only a stupid question: after using logcat reader I retain a notification saying "logcat reader service". Does this mean the service keeps running? Is there a way to stop it other than force stop the app? A menu option like "Exit" would be good. After viewing logs I often do not use the app for weeks and it feels odd to leave the service running when it's not needed (like for battery life etc).

Log recorder which writes the logs on storage in real-time, not after the recording has stopped. This helps to capture logs of buggy apps which trigger the device to reboot.
I only found one app which can do that, Logcat Extreme.

I want to copy the whole logcat entry. It is overly tedious to copy each part individually, pasting one before going to the next, so I end up saving the log, then copying from that.

TLDR: when saving a "saved log" somewhere else, an empty file name is suggested as new file name (rather than eg. the "logcat_timestamp.txt" name).

Long description: I saved the current log with Menu -> Save, then went to "Saved Logs", long-pressed on the new entry, and hit the "disk" icon. A save dialog appeared, with a text entry field at the bottom (next to the "Save" button). The text entry field was empty. When hitting Save, the log was saved in a file named "(invalid).txt".

I would suggest to pre-fill the text field with the log file name shown in the Saved Logs list instead.

This happened with Logcat Reader 1.5.4 from F-Droid under Android 7.1.2 (LineageOS 14.1).

Crashed when attempting to deselect the "main" log buffer.

Android 7.1.2, LineageOS, latest nightly.

3ed82e6
ddbc5ee

when pressing on logcat message the user can filter or exclude with pressed log message

When I try to execute adb shell pm grant com.dp.logcatapp android.permission.READ_LOGS I get the following exception with the stack trace below

Exception occurred while executing 'grant':
java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
	at android.app.ContextImpl.enforce(ContextImpl.java:2253)
	at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:2281)
	at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermissionInternal(PermissionManagerServiceImpl.java:1359)
	at com.android.server.pm.permission.PermissionManagerServiceImpl.grantRuntimePermission(PermissionManagerServiceImpl.java:1341)
	at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:553)
	at android.permission.PermissionManager.grantRuntimePermission(PermissionManager.java:597)
	at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(PackageManagerShellCommand.java:2591)
	at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:302)
	at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97)
	at android.os.ShellCommand.exec(ShellCommand.java:38)
	at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6332)
	at android.os.Binder.shellCommand(Binder.java:1073)
	at android.os.Binder.onTransact(Binder.java:901)
	at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4313)
	at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6316)
	at android.os.Binder.execTransactInternal(Binder.java:1331)
	at android.os.Binder.execTransact(Binder.java:1268)

Some android swipe down menus aren't good at showing buttons, so I have to use "force stop app" when I'm finished using this app. Please include an exit button by the restart button in the app interface! Thanks

A popup will show up by Android 13 to prompt user access to "usage logs", have you noticed it @darshanparajuli

There is unfortunately no way to bypass it on Android 13, we may need some change to the instructions on granting permissions manually

Hi,
When using the Record button we have to go to the Saved logs screen and long press a file to be able to share it.
A direct option to share it right after the record would be appreciated.
Thanks.

Hey, thanks for a great app!

I've noticed the below behavior:

1. Open the app, search for something:

2. Use the Recents button to go to another app or the Home button to go to the launcher
3. Use the Recents button to turn back into the app
4. The app will retain the search view and the search value but the results will be different:

5. Pressing "Enter" into the search text box won't refresh the results. You need to delete everything, then re-type, then press "Enter" again to get the same results as before onResume.

Hi!

I have just noticed that your app is outputting logs in a slightly different format that the one specified on Android Developer website: https://developer.android.com/studio/debug/am-logcat#format

There it is described as
date time PID-TID/package priority/tag: message

Outputted from your app, it seems like it is rather
[date time PID:TID priority/tag]
message

Is there something I am missing in the official documentation?

You should add a changelog file or simply specified the changes between each version in the release tab on Github.

I can't use this app for the one use case that I need- to inspect the logs after a system crash. The reason is because to save you need to press Start and then Stop again. When the OS crashes I need to inspect the log and find out why but I can't because there is no opportunity to save the log after a crash.

I request you allow the user to press start logging and this will save the log results to a file right away.

shizuku is a tool for using some operations in only ADB permission, details: https://shizuku.rikka.app/

if the user has uses shizuku, then he could use Logcatapp without adb command again

then i made the support for this tool (this commit might have api level requirement, might not. worked as expected on AOSP Android 10): https://github.com/NewBugger/LogcatReader/commit/95ce84b41cc424b97935a7a2140ba14817733449

i did not create pull request because i thought my code is not the fimiliar style as yours.

thanks all yours credits.

Hi there,
The title itself says my issue. When I open the app it doesn't shows any logs just blank. I gave READ_LOGS permission using adb as my device ( android 6 ) is not rooted. But when I put the app in background and come back after a while, the logs becomes visible and stucks around there.
It was just working fine before the updates.

Anyway love your work man !

Hi, I want to design a new logo for the project completely free...

showing no log after a moment. Have tried reinstall and restart app, still dont work

Security exception: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.

Phone: Redmi Note 8 Pro, Android 9

an option to show the last kmsg would be great! thanks.

My device is a Redmi Note 10 Pro with android 12. Activated all USB debugging options on developer mode.
I tried to use the command to grant the permissions to LogcatReader, and got the exception message above.

"Exception occurred while executing 'grant': java.lang.SecurityException: grantRuntimePermission: Neither user 2000 nor current process has android.permission.GRANT_RUNTIME_PERMISSIONS.
at android.app.ContextImpl.enforce(Unknown Source:97)
at android.app.ContextImpl.enforceCallingOrSelfPermission(Unknown Source:13)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermissionInternal(Unknown Source:49)
at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(Unknown Source:24)
at android.permission.PermissionManager.grantRuntimePermission(Unknown Source:6)
at com.android.server.pm.PackageManagerShellCommand.runGrantRevokePermission(Unknown Source:75)
at com.android.server.pm.PackageManagerShellCommand.onCommand(Unknown Source:955)
at com.android.modules.utils.BasicShellCommandHandler.exec(Unknown Source:27)
at android.os.ShellCommand.exec(Unknown Source:4)
at com.android.server.pm.PackageManagerService.onShellCommand(Unknown Source:20)
at android.os.Binder.shellCommand(Unknown Source:0)
at android.os.Binder.onTransact(Unknown Source:148)
at android.content.pm.IPackageManager$Stub.onTransact(Unknown Source:17)
at com.android.server.pm.PackageManagerService.onTransact(Unknown Source:0)
at android.os.Binder.execTransactInternal(Unknown Source:118)
at android.os.Binder.execTransact(Unknown Source:16)"

The dialog to add a new filter allows to select among multiple LOG LEVEL constraints, which -- judging by the result -- are applied conjunctively (conjoined by a logical AND). This doesn't make sense, as selecting more than one will inevitably result in mismatching all.

I suppose the only "proper" solution is generalizing Filters (and Exclusions, to which this should also apply) to allow both AND and OR. Suggestion: In the spirit of boolean algebra associativity, maybe have list items be conjoined by OR whereas each list item can hold all of the fields, which are in turn conjoined by AND.

Very useful app, by the way, thanks!

Sometimes I need to read a logcat that has been taken with ADB (e.g: An user took a logcat with ADB and sent it to me). So it would be nice if there's an option to read/open these log files taken from ADB.

Logcat Reader does not show logs of application crash.

LogcatReader best view logging UI.
Pls make broadcast listener and create logger appender.
logback send logging message you appender, appender send app log in broadcast message, LogcatReader view this log!
Push appender in maven or bintray.
PROFIT.
Sometimes there is not enough opportunity to show the customer application logs. (Не уверен что правильно донес мысль этого предложения. Продублирую на русском: Иногда не хватает возможности показать заказчику логи приложения. Можно конечно настроить logback логирование в файл. Но иногда хочется наглядного отображения логов.)

Steps:

• open the app
• hit "save"
• saved logs
• go to the lasts
• rename to anything
• see that the name hasn't changed
• see that the size is 0
• click on it
• see that it's empty
• try to delete it
• see that it's still here
• open the rename prompt
• validate without changing anything
• see that there is an "Error" toast message

Context:

version: 1.5.3
Nexus 5
Android 7.1.2 (LineageOS for microG)

Logcat:

logcatReader-rename-bug.txt

It's be really great to not split lines between the tag and the actual log text. This makes grepping a lot easier. Best would be if it it was impossible to differentiate between the app's logcat files and a usual adb logcat > log.txt

Running the adb command to set the permission results in a 'no permission specified' error. Google seems to agree with the command itself, so I suspect a wrong id?

Support adaptive launcher icons.

Can you make it possible to make minimal view like Matlog, so it looks cleaner and easier to read and you click to expand?

I'm too used to Matlog. Unfortunately the developer is inactive. Matlog is also open source https://github.com/plusCubed/matlog

The application could get the logs from tcpip? This is a strategy used in other applications to devices without root, this application is the best for logging but it depends on a computer to run the commands and It doesn't work on some devices.

Hi I would like to write the following for this project. About us and FAQ, which would improve the project.

Hi,

I'm getting the following error when trying to run the adb command (and yes I know it's all one line):
java.lang.IllegalArgumentException: Unknown permission: android.permissions.READ_LOGS
Any suggestions?

When logging, if the Android hangs, the logs are not automatically saved.
So I can't track the cause of the hang.
Can you come up with something?

Please add an option to control the location of saved log files. Requiring a root file manager to extract the saved logs from the app directory under /data/data is very inconvenient.

Thanks!

Maybe I don't how to use it. I really need to catch when a certain application crashes. For some reason when I apply filter 'error' it doesn't show anything while in adb it shows errors. Also what are buffers in the settings?