so that tiktok, netflix and others to close, reset the mobile or more bugs I install the kernel INFINITY-2.0.0 and voila, solution at the expert level ....
thank you¡¡¡so that tiktok, netflix and others to close, reset the mobile or more bugs I install the kernel INFINITY-2.0.0 and voila, solution at the expert level ....
Release 2.0.0: Massive update for thermals/optimizations and the start of FBEv2-casefolding builds · LuanHalaiko/kernel_raphael_sm8150Main changes --> Upstreamed to 4.14.262 --> Inline with latest CAF tag LA.UM.9.1.r1-11500.02-SMxxx0.QSSI12.0 --> Upstreamed fw-api and techpack/audio to latest CAF tag LA.UM.9.1.r1-11500.02-SMxxx0....github.com
I think burn in protection is enabled by default. It was the case with EvoX A11 at least.
Yeah on status bar i can confirm, it works, but on AOD not, the clock and notifications still in same place for ever.
Yes, I have same problem. ROM only suggest format NTFS drive. How can we fix that?
Burn-in code for AOD is already in SystemUI, incase you guys had no idea.
NTFS format will be enabled for the next update as the current kernel didn't enable support for it.Yes, I have same problem. ROM only suggest format NTFS drive. How can we fix that?
On latest clean flashed ROM i also have issues with playing video in applications: blue colors and green artifacts. Stock kennel, no root.
Also misplaced fingerprint icon in apps but on unlock screen it displayed correctly
It's unrelated. Safetynet requires the following:Very smooth experience on Android 12. Thanks Joey !
One question though: I clean installed the latest build, decrypted storage with DfE and I can't pass safety net check. On the previous build, storage encrypted it was okay.
Is safety net check related to storage encryption ?
If not do you have an idea why I get the "can't access to Google play service" error ?
There are so many factors that influence SoT, like how many apps running in background, did you connect to any bluetooth devices, do you use mostly LTE or wifi, do you play games or use heavy apps, do you often get calls or emails etc.
This thread is for K20 Pro/Mi 9T Pro (raphael/raphaelin) and not for Redmi Note 9s.I have installed the May 5th version on a Redmi Note 9s (miatoll).
Everything works correctly, but the phone won't connect to my car via Android Auto. Apparently, as android auto is not installed in system partition (which you can check by going to "Settings > Connected devices" to see if you have the "Android Auto" menu), the connection is not possible.
If I install Android Auto from the Play Store, it complains that in order to be able to connect to the car, it needs to be pre-installed on the device (I think it actually means to be installed in the system partition).
Does any of you have the same issue? Would it work if I flash another package of gapps on top of the ROM, to get this missing feature?
/* * Your warranty is void. Or valid, probably? * * I am not responsible for bricked devices, dead SD cards, Ebolation X, * thermonuclear war, or the current economic crisis caused by you following * these directions. YOU are choosing to make these modifications, and if * you point your finger at me for messing up your device, I will LMAO at you. */