I think it may have to do with the sometimes happening cpu overload of SurfaceFlinger. I played around with Firefox and at one point i could play the videos fine with Firefox, but everything felt kinda sluggish and at other times the video was distorted like in the Screenshot i posted.Strange. This morning even duckduckgo won't show up vids... Yesterday it did....
Hmm, ok. If I can distribute in any way to analyze or even solve that issue.... But i'm afraid my expierience is not wide enoughI think it may have to do with the sometimes happening cpu overload of SurfaceFlinger. I played around with Firefox and at one point i could play the videos fine with Firefox, but everything felt kinda sluggish and at other times the video was distorted like in the Screenshot i posted.
Did a clean reinstall oft current suez rom 20220506, no magisk, no gapps, activated power saving, installed Android system webview manually, also duckduckgo Browser, matlog and fennec. In fennec i set the prevent tracking mode to normal (not strict) and activated Storage access for Fennec manually in APP settings. I could play videos then. Interestingly Fennec also crashed and put a crash dump into logcat file, pointing to /system/vendor/lib64/egl/libGLESv2_POWERVR_ROGUE.soHmm, ok. If I can distribute in any way to analyze or even solve that issue.... But i'm afraid my expierience is not wide enough![]()
Neat find, I'm a new person here. Been trying different versions of Lineage OS as the latest MAY release made my processing.org sketch slow slow.Did a clean reinstall oft current suez rom 20220506, no magisk, no gapps, activated power saving, installed Android system webview manually, also duckduckgo Browser, matlog and fennec. In fennec i set the prevent tracking mode to normal (not strict) and activated Storage access for Fennec manually in APP settings. I could play videos then. Interestingly Fennec also crashed and put a crash dump into logcat file, pointing to /system/vendor/lib64/egl/libGLESv2_POWERVR_ROGUE.so
@ggow when looking at this chart
possibly SurfaceFlinger itself is not the culprit but maybe SurfaceFlinger trying to access already deregistered Buffers, leading to high CPU usage because of compositing surfaces anew instead of utilizing the buffer. So possibly the gralloc, libegl, libgles, or liboverlay libraries have a malfunction.![]()
I get repeated errors from IMGSRV and gralloc reporting a broken pipe. See Screenshot,Did a clean reinstall oft current suez rom 20220506, no magisk, no gapps, activated power saving, installed Android system webview manually, also duckduckgo Browser, matlog and fennec. In fennec i set the prevent tracking mode to normal (not strict) and activated Storage access for Fennec manually in APP settings. I could play videos then. Interestingly Fennec also crashed and put a crash dump into logcat file, pointing to /system/vendor/lib64/egl/libGLESv2_POWERVR_ROGUE.so
@ggow when looking at this chart
possibly SurfaceFlinger itself is not the culprit but maybe SurfaceFlinger trying to access already deregistered Buffers, leading to high CPU usage because of compositing surfaces anew instead of utilizing the buffer. So possibly the gralloc, libegl, libgles, or liboverlay libraries have a malfunction.![]()
Can you compare one release to another? Perhaps if you did that you could compare with what changed..I get repeated errors from IMGSRV and gralloc reporting a broken pipe. See Screenshot,
so maybe it would be helpful to trace I/O for gralloc, surfaceflinger. Don't know how to do that though other than potentially using Android SDK and the Rom in Android Emulator, enable a trace and analyze it![]()
Those gralloc errors occured also with 20220413Can you compare one release to another? Perhaps if you did that you could compare with what changed..
Not sure if thats how you would do it, or technically how much stuff changes between one version and another... but ideas.
You are over my head manThose gralloc errors occured also with 20220413
Back in the times when i used 20220301 worked kinda fine in some regards, though it had massive battery performance drain sometimes, don't know if those gralloc errors occured also there, but i guess it. Some other changes of the rom probably in the meantime (blob libraries i guess), of which only ggow probably knows.
Interesting thing is though that for ROM version 20220506 CPU2 and CPU3 (which have the high cpu usage malfunction errors) dmesg shows errors like this (which i didn't see in 20220413, but may depend on the boot state - 20220413 and i think also 20220301 had no problems after cold boot, but after reboot):
[ 2251.278622] -(2)[0:swapper/2]SANITY CHECK: Unexpected variation in id_mmfr0. Boot CPU: 0x00000010101105, CPU2: 0x00000010201105
[ 2251.280158] -(3)[0:swapper/3]SANITY CHECK: Unexpected variation in id_mmfr0. Boot CPU: 0x00000010101105, CPU3: 0x00000010201105
Apparently these errors are a sign for mismatching CPU features in version 20220506 of the ROM.
See also https://patchwork.kernel.org/[email protected]/
Edit:
I tested the ROM versions 20220301 / 20220316 / 20220406 / 20220413 / 20220506 with Passmark Performance Test app from Playstore, and Power Saving mode enabled:
2D score was 9089 / x / 15786 / 16712 / 17150 respectively. (x: Passmark 2D didn't work with 20220316)
CPU Score was 912 / x / 1390 / 1398 / 1482 respectively.
So latest version of the rom had the best performance overall (in that benchmark at least).
But not when CPU2 was hogged by SurfaceFlinger in idle mode with 20220301 or 20220506 version of the rom (mostly occuring with Power Saving off in idle mode), the Passmark CPU score was like 900-1000, so worse then.
The interesting thing is (tested with current ROM 20220506):
After running the "Unreal System Benchmark" from Playstore, exiting that app, then restarting "Passmark Performance Test" the 2D score of passmark goes down to like ~6000 (!) compared to ~17000 before, and CPU2 and CPU3 are at full throttle in idle mode then, and Passmark CPU score goes down to like 600 compared to 1400 before. This didn't happen everytime though and i had the impression with Power Saving on the risk was less.
Your best bet at the current state of the rom is:
Enable Power Saving mode to minimize the risk of the CPUs getting hogged by SurfaceFlinger (for whatever reason).
And before you continue doing anything after startup, check with a program like CPU info if the CPU cores 2 and 3 are powering down normally.
Edit: Also tested 20220301 and 20220316 (see above)
Have you tried older roms?Hi
Is there any update planned for this rom?
my tablet work fine except for the youtube video zoom and the random netflix crack .
thanks in advance
I haven't tried it, but it should work. Let me know how you get on.Thanks for updating. Is Magisk working again with this version?
thanks for the update!New Build is Up
Dated: 05 July 2022
- [fixed] Backlight HAL Errors
- [fixed] LiveDisplay not working
Which would mean that any update with GApps should fail?!thanks for the update!
heads up: the file size is about 10MB larger than before, hence even with pico gapps there is not enough space in the system partition. i removed the stock email and calendar to make some room.
thanks
That's indeed what I experienced. I wiped system, cache and davlik. Then installed rom, rebooted to recovery, installed gapps and got error 70.
Thanks for the warning.That's indeed what I experienced. I wiped system, cache and davlik. Then installed rom, rebooted to recovery, installed gapps and got error 70.
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/