aLogrec (free)

It doesn't work on rooted Android 6. Only creates empty file.

The point was to record the logs of a crash but this does not save the log.

0kb files is all that it produces - also on android 6.0 Permissions to access storage are granted.

The app records (for me) only these two lines for each session, plus an exception and one more line saying something is null: Classloader referenced unknown path: /data/app/org.jtp.alogrec-1/lib/arm64 Classloader referenced unknown path: /system/framework/QPerformance.jar

Apparently it still doesn't work with Android 4x. I'm on KK (rooted SM-G900T with 4.4.2) and get 0kb files. I was so hoping this would be able to tell me what's causing random reboots when I'm talking on the phone.

Was requested by a dev company to use this tool to create a log that could be used for debugging purposes. Recorded for 50 minutes, but log file was empty. Reading reviews, looks like this is an old problem that has not been fixed. HTC M8 One on Lollipop

Ran this for several hours a couple of times, produces a 0Kb file. Running android 4.4.2

Logs to internal storage on my phone, but there is no option to change the location, such as to write to SD card.

Needs root but doesn't request it. Not updated since 2012.

Doesn't seem to be able to log anything without root, and it doesn't prompt for it.

Does not record log of other Apps on not rooted, stock Samsung S5 with Android 5.0

Clean, simple, reliable.

The sole function it is supposed to fulfil, to record the output of logcat, is malfunctioning on all devices I tested it with. Other people have indicated it is happening on Android 4.x devices. At any rate, the app is worthless without a fix. However, when fixed, it deserves much praise.

Hasn't worked for a while..

Google changed the permissions in Android 4.1 (Jelly Bean), and apps now require root access to read logs other than their own. This app, and others like it, will no longer work without root access.

Timestamp is not output in ICS 4.0.3

Nice idea but without timestamps the recorded data is significantly less useful.

doesn't work

Can't say it helps, I installed it to see why my phone kept rebooting on its own, but while the recorder is running the phone doesn't reboot, but 2 minutes after I stop the recording, the phone reboots. Still hoping a reboot will occur while it's running.

I've been testing this on a Galaxy Note II and S3 and the log files are blank - not helpful when this is the only decent log app available!

My Android had the external SDcard at /mnt/sdcard/external_sdcard so the current location hardcoded into this app won't write to it...

0 byte files

I'm trying to resolve a hang, and when you reboot it concats to the prior log! Why does it do that? It should start a new one on reboot.

useless on my crashing Nexus 10

This app has just gone up with the reboot feature added to it.

Thanks!

The logging works very well and survives restarts, but the log is almost useless without any time stamps.

It creates a file in the SD card but is not capturing any logs on Samsung S3. It was completely useless for my use case.

If your on Jelly Bean you have to make it a system app, just like alogcat, I'm sure that could be fixed. It also needs more options than just start and stop. I would like to see html output as an option, as well as the same format options as alogcat has. It does enough to keep around though.

The only improvement I'd want would be timestamps in the logs, if it is possible.

Just I note, I'm using Jelly Bean and had to root my device and convert this app to a system app with Titanium Backup so that it would log as it did before Jelly Bean. Not a fault of the developer, but a change in the permissions Google made to protect users some more. I often test new apps and with this if I'm having an error it is easier for my to relay information back to the developers.

Useful event log dumps for identifying wayward apps. It's done pretty well for me so far but is a little limited by a lack of time stamps on events.

Running on a Nexus for with Cyanogen Mod 10.1 (android 4.2.x) aLogRec just produces 0kb files. If there are permission issues on these newer 4.x builds, the dev needs to update this to be distributed as incompatible with those devices.

Simple and effective. I can send clients out to test apps in the field and not worry about getting a pile of vague bug reports.

Comes up empty, I think it doesn't have permission to see any logcat events other than from its own process. Fix!

Getting Empty Logs on CM10.1 with Galaxy SIII. Will adjust stars if I can get it to write logs. Adjusted rating after I went and gave it permissions to read the logs from terminal window.

Log file always 0B in size.

a desktop tool for reading log file. please web search: androidlogcatviewer

All log files are at 0 bytes.

Sadly I must only give two stars as the application does nothing when recording on 4.x devices.