[ROM][12.1][raphael][OFFICIAL] Evolution X [05/23/22]

[daser4berlin]

Thx for answering Joey...

 

[kevrlbx_]

tik tok freezes and restarts the mobile

 

[nerzwerk]

tik tok freezes and restarts the mobile

Solution: uninstall tiktok

 

[abhishek biswas]

I want to report. A problem. Should I report here?

 

[Lyan]

UDFPS is super quick in latest build! TOP!

 

[rafita29]

tik tok freezes and restarts the mobile

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 ....

LuHaKo's cafeteria

☕ Welcome to Raphael's best place for a sipping hot kernel! You can donate to me on Ko-fi: https://ko-fi.com/luhako My portfolio: https://luanhalaiko.github.io/

t.me

Release 2.0.0: Massive update for thermals/optimizations and the start of FBEv2-casefolding builds · LuanHalaiko/kernel_raphael_sm8150

Main 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

 

[kevrlbx_]

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 ....

LuHaKo's cafeteria

☕ Welcome to Raphael's best place for a sipping hot kernel! You can donate to me on Ko-fi: https://ko-fi.com/luhako My portfolio: https://luanhalaiko.github.io/

t.me

Release 2.0.0: Massive update for thermals/optimizations and the start of FBEv2-casefolding builds · LuanHalaiko/kernel_raphael_sm8150

Main 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

thank you¡¡¡

 

[Henriqueceni]

Nice rom, but there is anyway to make AOD have any burn in protection?

 

[suisujin2]

Nice rom, but there is anyway to make AOD have any burn in protection?

I think burn in protection is enabled by default. It was the case with EvoX A11 at least.

Burn in protection for the status bar is a little bit overaggressive. The clock on the left side gets often cut off.

 

[Henriqueceni]

I think burn in protection is enabled by default. It was the case with EvoX A11 at least.

Burn in protection for the status bar is a little bit overaggressive. The clock on the left side gets often cut off.
View attachment 5523307

Yeah on status bar i can confirm, it works, but on AOD not, the clock and notifications still in same place for ever.

 

[90amper]

The last version(2021-12-04) OTG can't read NTFS U disk. format U disk to FAT32 or exFAT, it's worked. Any one have this problem?

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

 

[suisujin2]

Also misplaced fingerprint icon in apps but on unlock screen it displayed correctly

Same.
I also find it strange that the fingerprint prompt blocks the whole screen but not completely. The edges of the app to unlock are still visible.

 

[joeyhuab]

Yeah on status bar i can confirm, it works, but on AOD not, the clock and notifications still in same place for ever.

Burn-in code for AOD is already in SystemUI, incase you guys had no idea.

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

NTFS format will be enabled for the next update as the current kernel didn't enable support for it.

Make sure you're on evolution_raphael-ota-sq1d.220105.007-01281730-unsigned.zip to avoid any of the graphical glitches.

Apps that did not update their fingerprint support for Android 12 will have it misplaced.

 

[90amper]

@joeyhuab,

Make sure you're on evolution_raphael-ota-sq1d.220105.007-01281730-unsigned.zip to avoid any of the graphical glitches.

Yes, I'm on that build, but faced with that bugs

Examples:

 

[Temaki]

@joeyhuab,

Yes, I'm on that build, but faced with that bugs
View attachment 5523457
Examples:
View attachment 5523465View attachment 5523469

No, you are not. Check the release key.

 

[90amper]

@Temaki , sorry, you are right, time different. Ok, trying to update

 

[MCtepor]

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 ?

 

[joeyhuab]

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 ?

It's unrelated. Safetynet requires the following:

1. Download latest Magisk
2. Download latest Safetynet fix
3. Install Magisk by flashing in recovery and reboot after
4. Open Magisk, install SafetyNet fix module
5. Go to settings, enable Zygisk
6. Enable Enforce Denylist, tap configure Denylist, tap 3 buttons on the top right, check Show system apps
7. Look for Google play services
8. Enable com.google.android.gms toggle
9. Return to settings, Hide Magisk package
10. Reboot device
11. Clear data of Play store app
12. Force stop Play store then re-open
13. Download YASNAC and check the status

 

[PoulGT]

̶H̶e̶l̶l̶o̶ ̶g̶u̶y̶s̶.̶ ̶I̶ ̶v̶e̶r̶y̶ ̶l̶i̶k̶e̶ ̶y̶o̶u̶r̶ ̶R̶O̶M̶,̶ ̶b̶u̶t̶ ̶I̶ ̶h̶a̶v̶e̶ ̶o̶n̶e̶ ̶p̶r̶o̶b̶l̶e̶m̶ ̶t̶h̶a̶t̶ ̶I̶ ̶s̶t̶i̶l̶l̶ ̶d̶i̶d̶n̶'̶t̶ ̶g̶e̶t̶ ̶h̶o̶w̶ ̶t̶o̶ ̶s̶o̶l̶v̶e̶.̶ ̶I̶ ̶w̶a̶n̶t̶ ̶t̶o̶ ̶t̶u̶r̶n̶ ̶o̶f̶f̶ ̶A̶o̶D̶ ̶f̶o̶r̶e̶v̶e̶r̶,̶ ̶b̶u̶t̶ ̶i̶t̶ ̶k̶e̶e̶p̶s̶
̶t̶u̶r̶n̶i̶n̶g̶ ̶o̶n̶ ̶s̶o̶m̶e̶t̶i̶m̶e̶s̶.̶ ̶T̶h̶i̶s̶ ̶p̶r̶o̶b̶l̶e̶m̶ ̶e̶x̶i̶s̶t̶ ̶f̶r̶o̶m̶ ̶a̶b̶o̶u̶t̶ ̶4̶ ̶u̶p̶d̶a̶t̶e̶s̶ ̶a̶n̶d̶ ̶n̶o̶w̶ ̶I̶ ̶h̶a̶v̶e̶ ̶l̶a̶t̶e̶s̶t̶ ̶b̶u̶i̶l̶d̶.̶ ̶I̶ ̶w̶i̶l̶l̶ ̶g̶l̶a̶d̶ ̶t̶o̶ ̶g̶e̶t̶ ̶a̶n̶y̶ ̶h̶e̶l̶p̶ ̶t̶h̶a̶n̶k̶ ̶y̶o̶u̶ ̶i̶n̶ ̶̶a̶d̶v̶a̶n̶c̶e̶

Problem solved. I have found that I turn on schedule for AoD.

Thank you again for great work. You have the best ROM

 

[vicgomez]

Hi guys, I have a problem with battery drain due to phone not entering doze mode, and I'd like to ask if there's a way to check why the kernel is keeping the phone awake, preferably without root.

I've disabled aod because gsam battery said that the proximity sensor was keeping the phone awake and disabling that did stop that wakelock. But now the kernel is keeping the device awake according to gsam, only there's no detail or any clue on what's the process that triggers it.

I tried to Google it but I've seen that since A10, access to processes has been restricted, so I haven't seen an answer but maybe I missed something.