[EOL][ROM][13.0_r82][raphael][OFFICIAL] Evolution X [11/02/23]

[joeyhuab]

The final update for September should be available. Many useful features have been brought back such as App lock, Hidden apps, UDFPS icons/animations, OOS clear all notification button styles, QS footer icon customization, and many more. Tons of fixes were made too.

Changelog for the latest (09/27/2022) update

Device changes:
==============================

• None

------------------------------
ROM changes:
==============================

• Add check for empty TTS engine name
• Add missing INTERACT_ACROSS_USERS_FULL permission
• Always show APN settings on CDMA carriers
• Disable FP lockouts
• Disable bluetooth by default
• Do not preload ThreadLocalRandom class
• Evolver: Bring back App lock feature
• Evolver: Bring back Hidden apps feature
• Evolver: Bring back OOS style notification clear all button feature
• Evolver: Bring back QS footer icon visibilities
• Evolver: Replace QS footer Daily data usage with customizable QS footer text
• Evolver: UDFPS: Bring back customization options
• Fix NPE with void android.view.VelocityTracker.clear()
• Fix SystemUI build for kotlin 1.7.0
• Fix unqualified-std-cast-call compiler warning
• IllustrationPreference: Hide illustration when we fail to play anim
• PackageInstaller: Remove side padding from the dialog
• PixelPropsUtils: Spoof device as Pixel for Wallpapers app
• QSPanel: Fix NPE in updateViewPositions()
• Remove wtf if no display nits mapping exists
• Settings: Add sim status listener in about phone
• Settings: Call CardDatabaseHelper.getInstance() when used and not in onCreate
• Settings: Fix ExtraText lint errors
• Settings: Fix SIM name in Network Details to show the selected SIM
• Settings: Kang duplicate baseband fix from CAF
• SystemUI: Avoid altering page indicator layout when hiding qs footer icons
• SystemUI: FPSInfoService: extend LifecycleService and fix overlay not being visible in secondary user
• SystemUI: FPSInfoService: get status bar insets ignoring visibility
• SystemUI: Fix QS customizer corner radius
• SystemUI: Fix pulseOut fails before fully pulsing
• SystemUI: Refactor data usage code and typography
• SystemUI: cleanup fps info tile and service
• SystemUI: fix MediaProjection cast crash
• SystemUI: rewrite FPSInfoService in kt from scratch and bind service with tile
• fixup! Settings: add option to enable AOD on charging only
• fixup! SystemUI: Enable NFC quick settings tile
• overlay: SystemUI: force dark theme on global actions dialog

DOWNLOAD

 

[Umesh gautam]

Guys I beg u all and you @joeyhuab . I'm in work in different country and I activate double tap on back of phone, and now my phone turn off and Don't wanna go in system. Beg u all help me what can I do now, mayby from recovery I can disable this feature tell me how i can fix my phone without wipe data... Or mayby someone will made zip file to disable this one feature God damn guys I beg u I need my phone now. I write this message from my friend phone.

The sep 26 build fixed the problem. Have you tried that?

 

[coleckion]

Dirty flashed 0926 build, all seemed OK. Turned on sim pin + screen lock pin + fingerprint and restart: went straight to recovery. Maybe clean flash will be different. I don't use sim pin or any screen lock so I don't mind. @joeyhuab Here is the log:

log7.txt

drive.google.com

 

[Imperator_Dei]

Dirty flashed 0926 build, all seemed OK. Turned on sim pin + screen lock pin + fingerprint and restart: went straight to recovery. Maybe clean flash will be different. I don't use sim pin or any screen lock so I don't mind. @joeyhuab Here is the log:

log7.txt

drive.google.com

It has been said before, remove sim card before rebooting, I had the same problem with today's build and I managed to boot (semi-dirty flash, wipe system and vendor then sideload latest build without wiping data)

 

[joeyhuab]

Dirty flashed 0926 build, all seemed OK. Turned on sim pin + screen lock pin + fingerprint and restart: went straight to recovery. Maybe clean flash will be different. I don't use sim pin or any screen lock so I don't mind. @joeyhuab Here is the log:

log7.txt

drive.google.com

Yeah I suggest everyone to just disable sim pin for now. It's something i really can't bother to fix right now as not everyone uses that.

 

[scorthyn]

Flashed latest build and while using phone it restarted and now its bootlooping lol, wtf. Any ideas? Not using sim pin

 

[joeyhuab]

Flashed latest build and while using phone it restarted and now its bootlooping lol, wtf. Any ideas? Not using sim pin

Google Drive - Virus scan warning

drive.google.com

Can the guys experiencing bootloops test this real quick and report back?

 

[Polax Troy]

Can the guys experiencing bootloops test this real quick and report back?

Same bootloop, but after 5 minutes of usage. Phone was updating long when started (android update notification). Fingerprint was broken - trying to scan yet no success or fail.

Dirty flash recent evolution_raphael-ota-tp1a.220905.004.a2-09151416-unsigned.zip doesn't help.
Clean flash didn't try cause new update released. last ones looks fine after clean flash anyway

 

[joeyhuab]

Same bootloop, but after 5 minutes of usage. Phone was updating long when started (android update notification). Fingerprint was broken - trying to scan yet no success or fail.

Trying to dirty flash recent. will update

New update pushed out. Data usage feature was replaced with QS footer text.

 

[Raphael S]

snipped (double post)

 

[Raphael S]

Hey @joeyhuab, I've got some logdumps regarding the center clock mode (icons are somehow shifted to the right sometimes) and regarding the app crashes/freezes... However, my logs are a bit older, forgot to upload them

The time written in the filename is the time I encountered it (I think logcat via termux buffers some data, so there are dumps of previous tries as well)

Uugh, upload won't work

https://transfer.sh/cmul8h/2022-09-15_12-07.centerclock-bug.log

https://transfer.sh/gYPo4t/2022-09-15_12-54.crashing-apps.log

Many thanks for this great rom!

 

[eqxteh]

I've been on this rom since the first release but for the first time I'm having bootloop with version 27.09. Although I removed the sim card, my bootloop problem was not resolved.

 

[n0_alterNative__]

It is such a pity 72Hz is not available. This ROM would be perfect then ...

 

[coleckion]

Dirty flashed 0927 build, all seemed OK. Even with sim pin + screen lock pin + fingerprint, who needs this may want to try.

It is such a pity 72Hz is not available. This ROM would be perfect then ...

This feature only brings more pain to the dev, to those with replaced screens, to those with battery issues, etc.

 

[Alexintheecho]

Google Drive - Virus scan warning

drive.google.com

Can the guys experiencing bootloops test this real quick and report back?

I can confirm the bootloop caused because of sim's card pin it's fixed, I just try it and the phone reboot flawlessly, and I dirty flashed

 

[TheSourceNL]

Can somebody pls help me...

Already 2 times I did a clean install however at one moment stability gets less and I think a reboot helps, but I end up booting to the OS while the display flashes (status/taskbar) and I cannot give in my sim pin. After 2 or 3 times I end up in orange fox. Everything is encrypted so from windows MNT I cannot upload anything. After a format of DATA I can upload stuff via windows again. Last time I wanted to make sure my firmware was up to date, after flashing everything worked again, so it looks like the boot was broken....

After a complete clean install I have a few issues;
- audio slider goes down automatic when opening some apps (like pokemon go).
- when using youtube vanced over screen display the vanced screen freezed which get stuck in the video memory and each time I either login or swich app the it shows that vanced image.
- when using spotify when playing pokemon the game crashes.
- making screenshots with the hardware keys, i got a black screenshot.

I'm now going to do another clean install, yet after 2 times i'm afraid I encouter the same issues.
This is what I do:

1. Reboot to Fastboot
2. Download your desired recovery for your device

I have OrangeFox R11.1_3 statble installed.

3. Flash whichever recovery you desire and make sure you're on latest A11 firmware.
If not, flash A11 firmware.
4. FORMAT data. (Requires full backup of internal storage)

I format data, reboot to recovery, enable MTP, drag
fw_raphael_miui_RAPHAEL_21.11.24_34c2411b8d_11.0.zip
to the fox directory and install it.
I reboot system (I don't hit wipe caches)
Now my OS boots normally, wizard comes up and PIN comes up.
However I want a clear flash so I reboot to recovery
My data shows up encrypted.

4. FORMAT data. (Requires full backup of internal storage)

Again format data, back (i do NOT reboot here)

5. Flash the ROM

MTP still one, so I upload the ROM
I check reboot after flash complete.


6. Reboot to System and #KeepEvolving
7. Don't restore DEVICE SETTINGS during Setup Wizard.

During setup I import my online google check without any settings.

Above setup is like always. What am I missing?
Something with encryption?

 

[KlaverBoer]

After flashing the latest rom i have no issues with both sims and pin codes. I only noticed that the background colors changed and i cannot change them back to one i used before. But that is not a big issue for me.

 

[0TheNinja0]

Hello guys.
Could you suggest me kernel for better battery life?

 

[space_runner]

Is this new evolution A13 better bb than maybe ancient 6.4 ? If anyone can tell I'll appreciate.

 

[DFK79]

Hello guys.
Could you suggest me kernel for better battery life?

I suggest sticking to the kernel that comes with the ROM. I had almost 9 hours SOT recently on a full charge, and that even included hours of youtube audio under the lockscreen, so that should be enough for pretty much anybody. It's possible that the recent updates have some slight variations between themselves; I don't benchmark the battery for every single one but in general, you should be fine. If there's some kind of battery drain that only you seem to experience, maybe one of your apps is the culprit or, if it's been a while, a good old clean flash never hurts, even though it involves backing up stuff and some spare time.

Oh, and always consider the age of your battery. Ideally, you have access to a USB Meter which will tell you pretty accurately how many mAhs your battery takes from 0% to 100%. Apps like Capacity Info also work somewhat, YMMV.