search

rovo89 / Xposed

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

Cannot write xposed logs on the first boot on TW 5.1.1 #94

Open wanam opened 9 years ago

wanam commented 9 years ago

Update 01/12/2015: https://github.com/rovo89/Xposed/issues/94#issuecomment-160933938

I remember you fixed an xposed logcat issue https://github.com/rovo89/Xposed/issues/34 for Samsung TW and maybe others.

I just noticed that i cannot write any logs through "XposedBridge.log()" inside any XC_Callback, logs outside are working just fine (thrown exceptions for example).

I'm not sure if this was the case for the beginning or just a new SeLinux update introduced on the latest TW 5.1.1 Roms.

But changing the group ID of the process to AID_LOG seems to work fine.

rovo89 commented 9 years ago

Meanwhile, this function does nothing more than Log.i("Xposed", text), or Log.e("Xposed", Log.getStackTraceString(t)). If this doesn't end up in the logcat, I would be very surprised and don't know where to start looking for the issue.

Did you check the logcat manually? It might also be an issue with reading the logcat and writing it to the logfile, like #34 was. In that case, it would also be worth checking whether the working logging is actually done from the same processes and not in Zygote or something.

wanam commented 9 years ago

Actually I didn't check the logcat, but i guess it's the same issue as https://github.com/rovo89/Xposed/issues/34 , the fix you introduced there fixed tw one too.

I will check the logcat to confirm if it's a reading issue.

wanam commented 9 years ago

After various tests, i can confirm that this issue occurs only on the first boot (after flashing a Rom/Xposed) and i can also confirm it's writing correctly to the logcat all the time

But like the https://github.com/rovo89/Xposed/issues/34 it is logging to xposed logcat only during boot, and it stops writing logs later.

And to rectify the title, i think it should stop logging for both cases, inside and outside the XC_Callback, i tough it was only inside the XC_Callback because my outside log test case was fired during boot.