2

I'm running Liquid Smooth 3.2 on my Motorola Droid 1. This ROM comes with logcat disabled (/dev/log/main doesn't exist). I tried starting the logcat service myself by adding the following to /etc/init.local.rc:

#start logcat service
service logcat /system/bin/logcat -f /dev/log/main
   oneshot 

However, this didn't seem to work as /dev/log/main still doesn't exist on boot. I'm getting...

$ logcat
logcat
Unable to open log device '/dev/log/main': No such file or directory

Does anyone know how to re-enable logcat in a ROM that has it disabled?

1
3

The ROM might call "rm /dev/log/main" during init to cripple logcat. If you can find that line and remove it logcat should be happy.

3
  • Thanks for the hint! I'll do some grepping and see if that's the issue.
    – Will Tate
    Nov 27 '11 at 20:07
  • Why would a rom do that?
    – NoBugs
    Mar 20 '13 at 2:49
  • @NoBugs There's a slight speedup if the OS isn't logging as it's running.
    – jarvisteve
    Mar 20 '13 at 3:33
2

I figured it out. It was the kernel that came with Liquid Smooth ROM. The kernel developer, chevyno1 (of Simply Stunning MOD), disabled logging in the kernel. I switched to a different kernel by JDLFG and logging immediately turned on with the next boot.

1
  • Switching kernels helps - in my case Goldenleaf works instead of the old Franco's.
    – NoBugs
    Jun 12 '13 at 5:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.