the kernel has issues with offline charging(phone turned off) things appear on the screen, dots flickering squares, i had the same problem with all the tw kernels r1-r3
Caused by panel overclocking. Doesn't really matter as long as the phone is actually charging, and it seems that the glitch goes away once the screen is turned off, after a few seconds.the kernel has issues with offline charging(phone turned off) things appear on the screen, dots flickering squares, i had the same problem with all the tw kernels r1-r3
Never mind my friend:thumbup: I am already using quickpic n work wonders. Just that whenever I took a camera pic n want to view it directly it always goes to stock gallery. Thank you for the effort well done.No. It won't unless I manage to upgrade Mali drivers again. Even then, I'm not sure it will fix anything. Use QuickPic.
You've gone 400MHz, right?With r3 fixed [emoji12]
![]()
Yea, 400MHz I really like and with this strange MIUI 6 hybrid the battery remains good [emoji16]You've gone 400MHz, right?![]()
As far as I know there is no boot corruption on Touchwiz. Here you go.Hi Geecko,
was just wondering if you could build one for TW but without panel overclocking? Not a fan of boot and offline charging corruption, but i certainly am of everything else you've done with the kernel.
Thanks.
Wow, that was fast. Thank you based Geecko!As far as I know there is no boot corruption on Touchwiz. Here you go.
What about r4p0?Mali r5p0 kernel drivers available since Nov 11.
Still useless without blobs, also we still don't have r4p1 blobs yet, so don't expect anything soon...
Yea, this is a MIUI 5 - 4.10.31 with customization MIUI6 based on 4.1.2 ZSLR1Can i use this on MIUI based rom? Just like panamera2011 posted?
Once I get back my desktop pc I'll try to merge r4p0 and fixed gralloc from Nameless/Hardkernel to Omni. This could possibly resolve performance and tearing issues on AOSP, though not as good as the Insignal merge I attempted earlier this year (although Insignal used r3p1 blobs that may be far inferior in perfomance than r4p0, so maybe it's better after all). Nameless merged it only on 4412 devices, but I don't see any barrier for our 4210 devices, so I'll try anyway. :fingers-crossed:What about r4p0?Can be implemented on Exynos 4210 platform?
![]()