search

rovo89 / Xposed

The native part of the Xposed framework (mainly the modified app_process binary).
Other
7.45k stars 1.47k forks source link

Xposed logs not available with ro.build.type=user #154

Open KaMyKaSii opened 8 years ago

KaMyKaSii commented 8 years ago

I realized that my Xposed shows no log, and I participate in the topics of some modules, then it is difficult to show the problem without any log. But one day I had to make an "advanced function" in my MTK device, and for that I had to go in build.prop and change the line "ro.build.type=user" to "ro.build.type=eng", and then restarting finally realized that the logs were showing, again returned to "ro.build.type=user" and realized that stopped, so really this line at least on my device that determines whether the logs are recorded or not. Some time later someone had the same problem, and I suggested it and it worked, unfortunately did not ask what the device him to find some common factor. I wanted to leave with "ro.build.type=eng", but so are appearing red edges in the corner, and I could not turn the developer menu or other tweaks in build.prop. But then, this is a bug and can be fixed? My device is a Infinix Zero 2 LTE

rovo89 commented 8 years ago

Are you able to see the logcat using adb or apps like CatLog?

KaMyKaSii commented 8 years ago

Yes, logcat functions normally

rovo89 commented 8 years ago

OK, and do you see any log lines with tag "Xposed", especially during startup?

KaMyKaSii commented 8 years ago

I believe that when you ask for a logcat on boot, the adb was to be active after the phone leaving the logo and go to bootanimation, right? My rom does not, the adb is only available after bootanimation, perhaps at the very end of it. Earlier I made a "adb logcat -d -v time > logcat.txt" because I had a problem that the message "The android is starting apps" appears on every boot, and believed it was the Xposed, but found it was an system application updated, then simply deleted the update and the problem was solved. Yet I will send this log that was done so the adb was available for you to check: https://drive.google.com/file/d/0B1uvONk-jlRiT3Fuc001dHJZM0E/view?usp=sharing

KaMyKaSii commented 8 years ago

Correction: "adb -d logcat -v time > logcat.txt"