Skip to content
Advertisement

adb logcat returns “Logcat read failure”

After noticing that Logcat messages were not showing up in Android Studio, I tried every solution out there, and nothing worked. I eventually tried the command adb devices and sure enough my device was there, but as soon as I tried adb logcat it returned “logcat read failure”.

Developer settings are turned on, and so it debugging. I’m on a rooted phone running 7.0 Nougat, with an open bootloader.

Could it be that I’m rooted and it somehow messed up some permissions? I’ve never encountered this issue before, even on a rooted phone.

Logcat works when using an emulator.

Advertisement

Answer

I was facing the same issue as yours. Then I asked the developer of the ROM if he is facing the same issue. The developer said that it is working fine for him. So I flashed the ROM again and noticed that logcat was properly working. So it was clear that the problem was due to some apps or changes that I did on the ROM.

After debugging , I found that it was ARISE Sound System that was the root cause of this problem for me.

So if your are using ARISE Sound System dirty flash the ROM to remove it and check if this solves the problem for you. For now I am only using Viper4Android.

User contributions licensed under: CC BY-SA
1 People found this is helpful
Advertisement