“Unable to open log device ‘/dev/log/main’: No such file or directory” –

Development issue/problem:

I’m new to Android development and I bought a cheap Huawei Sonic (U8650 apparently) to test my first attempts to create an application on a real device.

However, if I try to use adb logcat or adb shell and then logcat on the device, I get :

The logging system /dev/log/main cannot be opened: Such a file or folder does not exist

I’ve already enabled usb debugging under Settings -> Developers.

I don’t know enough about Android to know if I can fix it.

I found two other questions with similar problems:

/dev/log/hand not found

??- ?? ?? : ?? : ?? : ?? : INFO/() : The logging system /dev/log/main cannot be opened: Such a file or folder does not exist

…but it turns out they both use a non-standard kernel with logging disabled. Mine’s a flip phone from the box.

This is a very cheap but very fast Android 2.3 phone, so let’s hope it wasn’t a complete waste of money.

Any help would be greatly appreciated.

How can I solve this problem?

Solution 1:

Dial the number: *#*### The service menu
appears.
Go to the menu Project -> Background settings -> Log settings.

Open the log switch and turn it to the ON position.
Open Log level setting and set the desired log level.

Restart the phone.

Solution 2:

1. Open : /system/etc/init.d/×× (not the same file on different ROMs, look for the correct file).
2. Find a line that reads: rm /dev/log/main
3. Change the line to : # rm /dev/log/main (comments outside the line, rm = delete, if you are interested).
4. Save and reload

Solution 3:

I share my case and my decision:

My phone had a performance version (Slim Bean ROM to be precise) with the semaphore kernel (you can say it is a semaphore because the logo of the semaphore is displayed when the phone boots up). These ROMs have disabled logging by default, so I had to download the Semaphore Manager application (you can download it here). Then I had to activate the ‘Journalist’ option in the ‘Modules’ section, as shown in the figure.

Restart and the protocol should work now!

Solution 4:

I finally found the answer to that question!

I was aimlessly checking to see if anything had been updated, and I came across a message on xda developers about a slightly different Huawei camera with the same problem.

http://forum.xda-developers.com/showpost.php?p=17774398&postcount=93

It really worked. I now have a complete logbook on my Huawei Sonic (U8650).

Three cheers for not giving up.

Solution copied from xda (in case it is deleted, etc.) :

There is a hidden service menu where you can configure the login. Dialling this number opens the service menu
:

*#*#2846579#*#*

Solution No 5:

I have a custom problem on Samsung Captivate, but my approach could also work for others:

Open CMD or a terminal and type :

Display Shell
Reload
with log code

I have Continuum v6.1, but it could also work for others.
If you have a terminal emulator on your phone, you can also do this:

Locate the release

and then just reboot the phone. I didn’t try, but it would probably work. My phone’s rooted, too. I don’t know if that makes any difference.

Solution No 6:

It was enough to restart the Huawei device.

Show Shell
Reboot

Solution No 7:

I have exactly the same problem.
One of the xda developers wrote something like this in issue 33 of the publication.

http://forum.xda-developers.com/showthread.php?t=1169869&page=4

One of the reasons it cannot be rooted is that the
Logcat engine of this phone has been removed from the android. This means that most people’s rooting methods are imperfect.

Maybe right, maybe wrong, I don’t know. In any case, it gives an overview of the case.

Good luck!

Related Tags:

textnow logcat,how to get logcat from android device