Over-heating caused by LSPosed on Android 16 beta 2

[aayushrautela]

Steps to reproduce/复现步骤

Lsposed is broken on A16 B2, the phone heats up excessively with same setup.

Expected behaviour/预期行为

Should would like in A16 B1

Actual behaviour/实际行为

Heats up excessively

Xposed Module List/Xposed 模块列表

Wa enhancer, snap Enhance

Magisk Module List/Magisk 模块列表

Pif, tricky store and YouTube on Ksu

LSPosed version/LSPosed 版本

Lastest build from CI

Android version/Android 版本

16 beta 2

Magisk version/Magisk 版本

Ksu next 1.0.4

Riru version/Riru 版本

None, zygisk next

Version requirement/版本要求

• I am using latest debug CI version of LSPosed and enable verbose log/我正在使用最新 CI 调试版本且启用详细日志

Logs/日志

LSPosed_2025-02-15T00_00_15.449646.zip

[JingMatrix]

It seems that dex2oat is broken on your device.
Please pen the LSPosed manager, choose an app from the scope selection panel, and do re-optimize through the context menu, to test if dex2oat is working.

If it fails, please upload logs again.

[aayushrautela]

Yes you are right, dex2oat is broken again. Device is Pixel 6, stock os.

LSPosed_2025-02-15T01_36_44.762743.zip

[JingMatrix]

I am using the same device and OS as you but have no problem.

Please record the following log while re-optimize an app.

adb logcat -s LSPosedDex2Oat dex2oat64 > dex2oat.log

Then upload file dex2oat.log.

[aayushrautela]

Here is the log file

dex2oat.log

tried to run it on few apps.

--------- beginning of main
02-15 10:17:24.692 19083 19083 W dex2oat64: type=1400 audit(0.0:922): avc: denied { read } for path="/data/adb/modules/zygisk_lsposed/bin/liboat_hook64.so" dev="dm-58" ino=91204 scontext=u:r:dex2oat:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0
02-15 10:18:53.920 19426 19426 W dex2oat64: type=1400 audit(0.0:953): avc: denied { read } for path="/data/adb/modules/zygisk_lsposed/bin/liboat_hook64.so" dev="dm-58" ino=91204 scontext=u:r:dex2oat:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0
02-15 10:19:00.336 19439 19439 W dex2oat64: type=1400 audit(0.0:959): avc: denied { read } for path="/data/adb/modules/zygisk_lsposed/bin/liboat_hook64.so" dev="dm-58" ino=91204 scontext=u:r:dex2oat:s0 tcontext=u:object_r:adb_data_file:s0 tclass=file permissive=0

[JingMatrix]

It seems that you have a SELinux problem, which is stange since I don't have this problem.
Please share the output of this command:

adb shell su -c 'ls -aZ /data/adb/modules/zygisk_lsposed/bin'

[aayushrautela]

The issue seem to be fixed. Here is the output
u:object_r:adb_data_file:s0 .
u:object_r:system_file:s0 ..
u:object_r:dex2oat_exec:s0 dex2oat32
u:object_r:dex2oat_exec:s0 dex2oat64
u:object_r:adb_data_file:s0 liboat_hook32.so
u:object_r:adb_data_file:s0 liboat_hook64.so

[JingMatrix]

Okay, we may wait a bit to see if the overheating is solved.

[JingMatrix]

Please try the latest CI, and record logs when you re-optimize an app:

adb logcat -s LSPosedDex2Oat dex2oat64 > dex2oat.log

Also, please send again the output of

adb shell su -c 'ls -aZ /data/adb/modules/zygisk_lsposed/bin'

[aayushrautela]

I already instlled the latest CI build.

u:object_r:adb_data_file:s0 .
u:object_r:system_file:s0 ..
u:object_r:dex2oat_exec:s0 dex2oat32
u:object_r:dex2oat_exec:s0 dex2oat64
u:object_r:adb_data_file:s0 liboat_hook32.so
u:object_r:adb_data_file:s0 liboat_hook64.so

dex2oat.log

[JingMatrix]

Are you using this build? https://github.com/JingMatrix/LSPosed/actions/runs/13354443445
If so, could you please also upload the dex2oat.log for this build ? https://github.com/JingMatrix/LSPosed/actions/runs/13343860418

We are trying to figure out the cause, thank for joining the debugging session.
To do so, I need to compare the logs and the outputs.

[JingMatrix]

Please try the latest CI build, and upload your logs and output of the command in #189 (comment).

[aayushrautela]

Using latest CI build.

u:object_r:system_file:s0 .
u:object_r:system_file:s0 ..
u:object_r:dex2oat_exec:s0 dex2oat32
u:object_r:dex2oat_exec:s0 dex2oat64
u:object_r:xposed_file:s0 liboat_hook32.so
u:object_r:xposed_file:s0 liboat_hook64.so

dex2oat.log

[JingMatrix]

From the log, this problem is now perfectly solved.