[ROM][13.0_r13][OFFICIAL] Evolution X 7.3 [11/24/2022]

Search This thread

parcou

Senior Member
Jun 7, 2008
1,397
176
TN
Please read through the thread before mentioning things that have already been addressed.


View attachment 5721477

Forgive not understanding the file name or revisions. Why does the date keep changing on the post: https://sourceforge.net/projects/ev....220905.004.a2-09270551-unsigned.zip/download

09270551 is dated for today. I downloaded and installed the one 09192130. Should I be updating or anything? I do not see the r4 change, but I just do not understand the new date and if there are any updates I am missing?

Thx

Edit: I looked in the rom and selected update for the first time. I see there is an update so makes sense. I thought there was going to be an OTA prompt been on OOS for too long.

Need to flash Magisk in one of the sockets to keep root, right.
 
Last edited:

allen-evan

Member
Nov 3, 2021
17
1
Is it possible to use quick switch or lawnchair 12 on this rom ??? It's a must have feature.. Don't know why after this update app opening closing animation become Soo laggy and slow... Please fix it 😊
 
Last edited:

AdmiralKirk

Senior Member
Feb 13, 2012
81
85
Manchester
Hello developers!
The ROM is excellent, I've been using it for 4 days, OP 9R, in general I'm happy with everything, everything works fine. I wanted to ask you to correct some points, if possible:
1) When you get the phone out of your pocket, the fingerprint scanner glows like a lantern, it's inconvenient in the dark.
2) Replace Google camera with a camera from OOS 12, if possible.
3) Add Dolby Atmos.
4) Add face unlock.

So normally we'd all ignore someone asking questions that have been repeatedly answered in a given thread. But now that I'm thinking about it, these may not have been answered in this new thread yet. So I'll give you the quick rundown.

1) Not 100% sure on this one, but I believe it's intentional. There were a lot of problems in regard to the fingerprint sensor not picking up fingerprints quickly or well, and I believe the solution was to make the backlight for it full intensity white to get it working better.
2) That has been an emphatic NO from the devs. I believe (don't quote me, my memory isn't what it used to be. Anierin feel free to correct me.) a lot of time and effort was required to port the OOS cam last time, and they likely believe their limited time and efforts better spent on other aspects since for 90% of cases, GCam is as good or better (there has been some discussion of OIS being inferior for some models though).
3) That would be another emphatic NO. I believe (again, don't quote me, this is from memory on a convo on Tele awhile back), that the reasoning here is that everyone likes something a little different with Audio, so they're leaving it each to their own. There are Magisk modules for Dolby, Viper, Ainur and others. Although I'm not sure how compatible each of those is with Android 13.
4) As I understand it, this is a Google thing that hasn't yet been implemented for A13 yet. I believe it doesn't even exist on the Pixel's at the moment. (As always, please correct me if I'm wrong).
 

Koshukar

Member
Jan 23, 2022
7
3
So normally we'd all ignore someone asking questions that have been repeatedly answered in a given thread. But now that I'm thinking about it, these may not have been answered in this new thread yet. So I'll give you the quick rundown.

1) Not 100% sure on this one, but I believe it's intentional. There were a lot of problems in regard to the fingerprint sensor not picking up fingerprints quickly or well, and I believe the solution was to make the backlight for it full intensity white to get it working better.
2) That has been an emphatic NO from the devs. I believe (don't quote me, my memory isn't what it used to be. Anierin feel free to correct me.) a lot of time and effort was required to port the OOS cam last time, and they likely believe their limited time and efforts better spent on other aspects since for 90% of cases, GCam is as good or better (there has been some discussion of OIS being inferior for some models though).
3) That would be another emphatic NO. I believe (again, don't quote me, this is from memory on a convo on Tele awhile back), that the reasoning here is that everyone likes something a little different with Audio, so they're leaving it each to their own. There are Magisk modules for Dolby, Viper, Ainur and others. Although I'm not sure how compatible each of those is with Android 13.
4) As I understand it, this is a Google thing that hasn't yet been implemented for A13 yet. I believe it doesn't even exist on the Pixel's at the moment. (As always, please correct me if I'm wrong).
I don’t know exactly how things are with other A13 firmwares, but even if we discard what I wrote above, this is a very worthy ROM. The fact that it is often updated over the air is good news.
 

Klusio19

Senior Member
Nov 13, 2018
180
42
Tarnobrzeg
OnePlus 8T
GCam is as good or better (there has been some discussion of OIS being inferior for some models though).
Exactly that. For OnePlus 8 series, (I don't know about other OnePlus devices, I don't own them) videos taken from anything but OOS cam are basically not usable, because they are shaky af. For the rest - GCam is godlike, that's obvious. But still, cringe fanboys will say that "GCam is the best, and they see no difference in video stabilization", etc, etc. You basically have to not take any videos at all to say that.
Also someone will also cite an argument, that you can use stabilizating feature in Google Photos - yeah, it works, but it looks bad and super unnatural.
 

Marcyvee

Senior Member
Oct 9, 2015
295
28
Is it possible with the last build, to improve Google gestures with some actions when I hold swipe omg left or right? Such as it was in the >12 version?
 

devsk

Senior Member
Dec 14, 2008
2,052
763
Are you sure? For me, it starts to collect a bug report and then, just reboots the system without completing the bug report. Tried it from both command line and from the System->Developer Options
@AnierinB Another user did this as well and his phone rebooted as well. Do you have an idea about what's going on? Google Fi support really needs the bug report to debug the issue I am facing with mobile data.
 

Marcyvee

Senior Member
Oct 9, 2015
295
28
I updated to the last version yesterday.
I installed as OTA update after flash the new recovery from fastboot and sideloaded copipartition.zip. I haven't wipe any partition, anyway no problem at all. Every app seems to work fine.
I can't change the theme color, but is not a big problem. The rom looks great! No reason to not update.
 

vacs03

Senior Member
Aug 28, 2010
259
78
OnePlus 8T
Exactly that. For OnePlus 8 series, (I don't know about other OnePlus devices, I don't own them) videos taken from anything but OOS cam are basically not usable, because they are shaky af. For the rest - GCam is godlike, that's obvious. But still, cringe fanboys will say that "GCam is the best, and they see no difference in video stabilization", etc, etc. You basically have to not take any videos at all to say that.
Also someone will also cite an argument, that you can use stabilizating feature in Google Photos - yeah, it works, but it looks bad and super unnatural.
For the time being I'm using warp stabilizier in adobe premiere pro on pc to stabilize videos taken with gcam, it isn't perfect but it's currently the best option
 

parcou

Senior Member
Jun 7, 2008
1,397
176
TN
I cannot access the DATA folder
Internal storage > Android > Data

OP8P is rooted with Magisk, unlike on Android 12, I cannot access the DATA folder on A13. Using the FILES folder in the rom shows nothing.

I have used and the paid app for years Solid Explorer, which cannot grant access to \Data folder on A13. None of these file explorer apps can access this folder. I need access to the folders for apps like Swift Backup to back up to the cloud.

Is there a way to get rom access to the Android\Data folder?

Thx
 
Last edited:

devsk

Senior Member
Dec 14, 2008
2,052
763
@AnierinB my man! Google Fi support is bugging me about the bug report. I need to respond to them to get my mobile data fixed. Please help.

Is there anything that clicks in the output below:

Code:
09-30 19:27:34.916 10309 10404 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14 in tid 10404 (IrisHWC), pid 10309
 (composer-servic)
...
09-30 19:27:35.372 22450 22450 F DEBUG   : uid: 1000
09-30 19:27:35.372 22450 22450 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000014
09-30 19:27:35.372 22450 22450 F DEBUG   : Cause: null pointer dereference
09-30 19:27:35.372 22450 22450 F DEBUG   :     x0  0000000000000000  x1  0000000000000000  x2  b400007723445558  x3  00000000ffffffff
09-30 19:27:35.372 22450 22450 F DEBUG   :     x4  0000000000000000  x5  0000000000000008  x6  0000000000000001  x7  0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x12 fff4000000000000  x13 0000000000000001  x14 0000000000000028  x15 000000000000000e
09-30 19:27:35.373 22450 22450 F DEBUG   :     x16 0000000000000001  x17 00000077aab86854  x18 000000770f442000  x19 b400007723445540
09-30 19:27:35.373 22450 22450 F DEBUG   :     x20 b400007723445610  x21 b400007723445558  x22 00000000ffffffff  x23 0000000000000000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x24 0000000000000030  x25 0000007712fdecb0  x26 0000007712fdf000  x27 00000000000fc000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x28 00000000000fe000  x29 0000007712fdeb30
09-30 19:27:35.373 22450 22450 F DEBUG   :     lr  00000077a9e67780  sp  0000007712fde9c0  pc  00000077a9e67780  pst 0000000080001000
09-30 19:27:35.373 22450 22450 F DEBUG   : backtrace:
09-30 19:27:35.373 22450 22450 F DEBUG   :       #00 pc 0000000000017780  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollInner(int)+1016) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #01 pc 0000000000017c14  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollAll(int, int*, int*, void**)+296) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #02 pc 00000000000482b0  /odm/lib64/libpwirisservice.so (pxlw::DelayThread::threadLoop()+28) (BuildId: e6460e0a66759feb30484eb0f544afe4)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #03 pc 0000000000012f18  /apex/com.android.vndk.v33/lib64/libutils.so (android::Thread::_threadLoop(void*)+416) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #04 pc 00000000000f1478  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #05 pc 000000000008cdec  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.404 10451 12116 W NativeCrashListener: Couldn't find ProcessRecord for pid 10309
09-30 19:27:35.408 10451 11943 E NativeTombstoneManager: Tombstone's UID (1000) not an app, ignoring
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417124]@2 init: Untracked pid 22450 exited with status 0
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417160]@2 init: Untracked pid 22450 did not have an associated service entry and will not be reaped
 

AnierinB

Recognized Developer
@AnierinB my man! Google Fi support is bugging me about the bug report. I need to respond to them to get my mobile data fixed. Please help.

Is there anything that clicks in the output below:

Code:
09-30 19:27:34.916 10309 10404 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x14 in tid 10404 (IrisHWC), pid 10309
 (composer-servic)
...
09-30 19:27:35.372 22450 22450 F DEBUG   : uid: 1000
09-30 19:27:35.372 22450 22450 F DEBUG   : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0000000000000014
09-30 19:27:35.372 22450 22450 F DEBUG   : Cause: null pointer dereference
09-30 19:27:35.372 22450 22450 F DEBUG   :     x0  0000000000000000  x1  0000000000000000  x2  b400007723445558  x3  00000000ffffffff
09-30 19:27:35.372 22450 22450 F DEBUG   :     x4  0000000000000000  x5  0000000000000008  x6  0000000000000001  x7  0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x8  0000000000000000  x9  0000000000000000  x10 0000000000000000  x11 0000000000000000
09-30 19:27:35.372 22450 22450 F DEBUG   :     x12 fff4000000000000  x13 0000000000000001  x14 0000000000000028  x15 000000000000000e
09-30 19:27:35.373 22450 22450 F DEBUG   :     x16 0000000000000001  x17 00000077aab86854  x18 000000770f442000  x19 b400007723445540
09-30 19:27:35.373 22450 22450 F DEBUG   :     x20 b400007723445610  x21 b400007723445558  x22 00000000ffffffff  x23 0000000000000000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x24 0000000000000030  x25 0000007712fdecb0  x26 0000007712fdf000  x27 00000000000fc000
09-30 19:27:35.373 22450 22450 F DEBUG   :     x28 00000000000fe000  x29 0000007712fdeb30
09-30 19:27:35.373 22450 22450 F DEBUG   :     lr  00000077a9e67780  sp  0000007712fde9c0  pc  00000077a9e67780  pst 0000000080001000
09-30 19:27:35.373 22450 22450 F DEBUG   : backtrace:
09-30 19:27:35.373 22450 22450 F DEBUG   :       #00 pc 0000000000017780  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollInner(int)+1016) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #01 pc 0000000000017c14  /apex/com.android.vndk.v33/lib64/libutils.so (android::Looper::pollAll(int, int*, int*, void**)+296) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #02 pc 00000000000482b0  /odm/lib64/libpwirisservice.so (pxlw::DelayThread::threadLoop()+28) (BuildId: e6460e0a66759feb30484eb0f544afe4)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #03 pc 0000000000012f18  /apex/com.android.vndk.v33/lib64/libutils.so (android::Thread::_threadLoop(void*)+416) (BuildId: c200e9a85d2415f28f0687a94e6b8643)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #04 pc 00000000000f1478  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+208) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.373 22450 22450 F DEBUG   :       #05 pc 000000000008cdec  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 657a7c5a0c0be56f6df7f00bc776b77a)
09-30 19:27:35.404 10451 12116 W NativeCrashListener: Couldn't find ProcessRecord for pid 10309
09-30 19:27:35.408 10451 11943 E NativeTombstoneManager: Tombstone's UID (1000) not an app, ignoring
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417124]@2 init: Untracked pid 22450 exited with status 0
09-30 19:27:35.425     1     1 I (2)[1:init][20220930_19:27:35.417160]@2 init: Untracked pid 22450 did not have an associated service entry and will not be reaped

It looks like it's a segfault due to me disabling softiris in kernel, which I'm not reverting until the reason why I disabled it is fixed

P.s GoogleFi support isn't going to do be able to do anything If you're running a custom ROM. I've already asked you to check if it's working on stock, although you don't want to, so why should I help?

P.s I can send a boot.img with softiris re enabled so you can take your bug report although I'd still like an answer to what I just said.
 

devsk

Senior Member
Dec 14, 2008
2,052
763
It looks like it's a segfault due to me disabling softiris in kernel, which I'm not reverting until the reason why I disabled it is fixed

P.s GoogleFi support isn't going to do be able to do anything If you're running a custom ROM. I've already asked you to check if it's working on stock, although you don't want to, so why should I help?

P.s I can send a boot.img with softiris re enabled so you can take your bug report although I'd still like an answer to what I just said.
Its some weird interaction between Google Fi app and mobile data, where when the app is disabled or uninstalled, the data works. I would gladly disable the app but then, the MMS stops working.

Now, whether that interaction is because of Android 13 or not, we don't know. But I would like Google to try to see if they can debug that.

If you can pls give me a boot.img with the revert on softirs, I get Fi support off my back.
 

DrDominate

Senior Member
I cannot access the DATA folder
Internal storage > Android > Data

OP8P is rooted with Magisk, unlike on Android 12, I cannot access the DATA folder on A13. Using the FILES folder in the rom shows nothing.

I have used and the paid app for years Solid Explorer, which cannot grant access to \Data folder on A13. None of these file explorer apps can access this folder. I need access to the folders for apps like Swift Backup to back up to the cloud.

Is there a way to get rom access to the Android\Data folder?

Thx
Using FX file explorer with the root add-on I'm able to access the Android/Data folder.
 
  • Like
Reactions: parcou

ciku720

Senior Member
Apr 12, 2011
103
40
Xiaomi Redmi 3S
OnePlus 8T
Has anyone succeeded using a custom kernel on this Rom? I know that the blu_spark does not support the new partition system we have on the EvolutionX. I also searched few other kernels on XDA but none seem to work with Android 13 in general. Did I miss something, are there some alpha versions to try maybe?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Anyone having issues with pixel launcher since last update. The weather widget is not opening to full forecast and the search bar isn't working-only searching installed apps.
    Issues with pixel launcher have already been fixed. Will be available on the next release.
    3
    The latest build does not work OTA.
    My version: evolution_instantnoodle-ota-td1a.221105.001-11191405-unsigned.

    I have some problem even on op8p

    Same here OP8.
    Verification failed after download OTA

    Lmao

    OTA failed verification, decided to sideload. Phone now bootloops in recovery mode.

    See if I can't sort this out after work I guess...

    On instancenoodle and instantnoodlep, this new update requires data format.
    It's been announced on Telegram but not on xda apprently....
    3
    Would you mind explaining a little further how to get magisk and root with evolution x just installed?? i dont want to get my phone bricked

    Sideload (using with Evolution custom rom provided Recovery) and the
    ADB sideload command

    Once in Recovery and using Sideload as OP lays out in the same way to flash this rom.
    • Boot the phone in recovery and connected to a computer using the ADB commands
    • Once in Recovery go to Sideload option
    • adb devices (verify device is connected) from the computer
    • adb sideload Magisk-v25.2.zip (keep root) from the computer

    The Magisk file is the same as the apk file just changing the extension to .zip

    Once done reboot and install the Magisk app
    2
    Hi all. I'm confused and not following the post

    I am still on 11/19 for my OP8P. I see there is an OTA update available on my phone if I download and install as normal and run Magisk to keep root.

    I have not done anything since there is some post here about needing to wipe data or reformat.

    In newbie language, if I want to update what do I do from here? Same as normal, or am I forced to wipe data?

    Thx
    You're gonna have to start from scratch here.
    Follow the instructions as if you're coming from OOS12 (no need to flash C33 firmware though, because you already on it).
    You'll have to adb sideload and wipe data in the recovery.
    Can I flash this while being on OOS with A13?
    No, you have to be on OOS 12 firmware (C33-C35). If you're on OOS13 firmware you will most definitely face bugs.
    1
    i was wondering if the 48MP camera works now ... or if i missed something to get it working again in a13 because its not mentioned in issues...
    Yes it is.
    There's Camera Unlocker Magisk Module, but I don't know if it work on this ROM because it's not OOS based.
    The patch for this is already included in the ROM.
  • 50
    Evolution X 7.3 for the OnePlus 8, 8 Pro, 8T & 9R [Instantnoodle][Instantnoodlep][Kebab][lemonades]

    Banner.png


    Living, Breaking, Keep Evolving.
    Pixel UI, customization and more, we are Evolution X!

    - Team Evolution X -
    @joeyhuab (Founder/Lead Developer)
    @peaktogoo (Project Manager/Co-Founder)
    @
    AnierinB (Project Specialist/Co-Founder)

    Reach us on Twitter! @EvolutionXROM

    Check out our website!

    wjBJ2Hk.png


    Code:
    Themes
    - Monet Engine
    - Vivid Theme (Black theme/Vibrant monet)
    - Dark Theme Schedules
    - System Fonts (53 Styles)
    - SB Icon Packs (10 Styles)
    - SB Signal Icon Packs (14 Styles)
    - SB WiFi Icon Packs (10 Styles)
    - System Icon Packs (16 Styles)
    - 3 Button Navbar Styles (10 Styles)
    
    Statusbar
    - Clock Styles (Right, Center, Left)
    - Clock & Date Configs (Auto Hide, Seconds, AM/PM, Date Postion/Case/Format)
    - SB Logo Pack (28 Styles)
    - Network Traffic Indicators
    - Battery Icon (10 Styles, 3 Percentage Options)
    - System SB UI Tuner
    - Data Disabled Icon (On/Off)
    - Old Style Mobile Data
    - 4G Instead Of LTE
    - Roaming Indicator
    - Colored Icons
    - Bluetooth Battery Status
    - Mic/Camera Privacy Inidicator
    - Location Privacy Inidicator
    - Media Projection Privacy Inidicator
    
    Notifications
    - ReTicker
    - Heads Up
    - Heads Up Time Out
    - Less Boring Heads Up
    - Heads Up StopList/Blacklist
    - App Colored Background For Reticker
    - Heads Up
    - Notification Sound If Active
    - Kill App Button
    - Blink Flashlight For Incoming Call
    - In-Call-Vibrations (Connect, Waiting, Disconnect)
    
    Quick Settings
    - Clock
    - Clock Font Size
    - Date
    - Secure QS
    - Battery Style (11 Styles)
    - Battery Percent Location (3 Locations)
    - Secure QS Requires Unlock
    - Quick QS Pulldown
    - Smart Pulldown
    - When To Show Brightness Slider
    - Brightness Slider Position (2 Postions)
    - Brightness Slider Icon
    - QS Tile Animation Style (3 Styles)
    - QS Tile Animation Druations (3 Speeds)
    - QS Tile Animation Interpolator (8 Styles)
    - QS Vibration
    - QS Vibration Druation
    - QS Footer Warnings
    - User Account
    - Edit Icon
    - Power Menu Shortcut
    - Running Services Shortcut
    - Settings Shortcut
    - Clear All Button (10 Styles, 5 Backgrounds)
    
    Power Menu
    - System Settings (Hold PWR Assistant + Hold Duration)
    - Disable Power Menu On LS
    - Power
    - Restart
    - Advanced Reboot Options
    - Screenshot
    - Flashlight
    - Settings
    - Lock Down
    - Emergency
    - Users
    - Logout
    - Bug Report
    
    Gestures
    - System Settings
    - Quick Tap
    - Volume Button Platback Control
    - Swipe To Screenshot
    - Brightness Control
    - PWR Button Torch
    - Double Tap To Sleep Status Bar
    - Double Tap to Sleep Lockscreen
    - AOSP Gestures
    - Pill Length
    - Pill Radius
    - IME Space
    - Back Gesture Animation
    
    Lockscreen
    - Edge Light
    - Screen Off UDFPS
    - UDFPS Icon Picker (54 Styles)
    - UDFPS Animation Picker (36 Styles)
    - LS Charging Info
    - Hide SB
    - Hide QS During Secure LS
    - Media Cover Art
    - Ripple Effect
    
    Buttons
    - Show Vol Panel On Left
    - Per App Vol Control
    - On-Screen NavBar
    - Arrow Keys While Typing On 3 Button Layout
    - Compact 3 Button Layout
    - Invert 3 Button Layout
    - Volume Steps Configs (8 Sources)
    - Volume Rocker Wake
    - Keyboard Cursor Control
    - Alert Slider Notifications
    - Alert Slider Pulse
    - Block Alert Slider In Pocket Mode
    - Click To Partial Screenshot
    
    Animations
    - Screen Off Animation (3 Styles)
    
    Miscellaneous
    - AOD Display Schedule
    - Game Space
    - App Lock
    - Hidden Apps
    - Launch Music App On Headset Connect
    - Unlimited Photos Storage
    - Unlock Higher FPS In Games
    - Jitter Test
    - Ignore Secure Window Flags
    - Show Tempature Warning
    - Toast App Icon
    - Sensor Block Per Package
    - Default USB Configuration
    - Radio Info
    Code:
    My signature Universal OPlusExtras application:
    - Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer/Notification & Ringer/Refresh rate)
    - Ambient display gestures (raise2wake)
    - Kcal
    - Per-app refresh rate
    - DC-Dimming toggle
    - HBM toggle
    - Auto HBM toggle (with lux adjustment preference)
    - Power efficient Workqueue toggle
    - MSM touchboost toggle
    - fsync toggle
    - Adrenoboost preference (off, light, medium, aggressive
    - FPS overlay (9 Positions, 11 Colors & accent, 9 Sizes
    - Powershare toggle
    - Game mode toggle (240hz touch sampling rate)
    - TP edge limit toggle (disable edge detection)
    - USB-OTG toggle
    - USB2.0 Fastcharge toggle
    - System Vibration Strength preference

    sxs3pbW.png


    1. HDMI out
    2. Idk, you tell me

    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png


    First Time Install / Clean Flash (8 & 8 Pro)
    1. Be on any version of OOS12 (required firmware is shipped with Evolution X for these devices)
    2. Download vbmeta, recovery, and rom for your device from here (please make sure that you don't flash instantnoodlep (8 Pro) on instantnoodle (8) else you will hardbrick your device)
    3. Reboot to bootloader
    4. fastboot flash vbmeta vbmeta.img
    fastboot flash recovery recovery.img
    fastboot reboot recovery
    5. While in recovery, navigate to Apply update -> Apply from ADB (if you experience no touch in recovery, then use the vol & pwr keys. This is a sign of you being on an early version of OOS12. The required firmware will be flashed during installation of the ROM.)
    6. adb sideload rom.zip (replace "rom" with actual filename)
    7. Format data, reboot to system & #KeepEvolving

    First Time Install / Clean Flash (8T & 9R)
    1. Be on the latest OOS 12 (C36)
    2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
    3. Reboot to bootloader
    4. fastboot flash recovery recovery.img
    fastboot flash vbmeta vbmeta.img
    fastboot reboot recovery
    5. While in recovery, navigate to Apply update -> Apply from ADB
    6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
    7. Repeat step 5 and then adb sideload rom.zip (replace "rom" with actual filename)
    8. Format data, reboot to system & #KeepEvolving

    Update / Dirty Flash
    1. Reboot to recovery
    2. While in recovery, navigate to Apply update -> Apply from ADB
    3. adb sideload rom.zip (replace "rom" with actual filename)
    4. Reboot to system & #KeepEvolving

    OTA

    1. Check for update. If available, select "Download and install" (approx 10-15 min)
    2. Reboot & #KeepEvolving






    S2t0kJ9.png
    18



    17
    Updates are out!

    If coming from the previous 09/16/2022 release, OTA will work. For anyone who hasn't updated to that build, you will need to use the new recovery with support for erofs as pointed out here in order to flash the latest build.

    Changelog:
    • kernel: Enable wireguard kernel backend
    • sm8250-common: Fix disabling A2DP offload
    • sm8250-common: Import audio policy configurations from audio HAL
    • Instantnoodlep: Use 1080p resolution by default
    • base: Save user preferred resolution into persistent data store (restores user set resolution on boot)
    • AlertSlider: Allow UI to work with multiple resolutions
    • SystemUI: Use max Display.Mode in AuthController as well
    • Catch IllegalArgumentException for invalid phone id
    • Fix action bar font family on material themes
    • Fix crash occurred due to null pointer exception
    • KeyguardIndication: Fix glitchy charging info on lock screen
    • Settings: Allow Configuring Navbar Radius
    • StatusBarIconController: Guard yet another function from cast exception
    • SystemUI: Allow using tuner API for Global settings
    • SystemUI: Clean up and fix status bar logo feature
    • SystemUI: More rounded corners
    • SystemUI: Tiny expanding improvement
    • ThemeOverlayController: Remove repeated monet check
    • Use alphaoptimized layout for icons on left
    • base: use a double click effect for charging if there is no amplitude control support
    • core: Fix menu popup ripple
    • core: Fix NPE
    • fixup! frameworks: Add support for clock auto-hiding
    • Reland "Don't enable jdwp by default on userdebug builds"
    • SystemUI: Re-inflate keyguard status bar on theme change
    • SystemUI: Set heap tracking default also with a property like all the other flags
    • base: AudioService: bail out if ringer mode is not recognized
    • apns: Clean up Austrian carriers
    • Evolver: Bring back HeadsUp snooze and timeout options
    • Evolver: Bring back HeadsUp blocklist/stoplist
    • Fix Dark Theme "TURN ON UNTIL SUNRISE" not retained after reboot
    • Fixes crash/race condition when destroyActivity
    • Improve PendingIntent security check compatibility
    • Settings: Add charging vibration settings

    #KeepEvolving
    11
    Hey everyone,

    Just dropping by here to clean the thread and remind everyone to remain calm and respect the developers. Developers do the development in their free time and are not committed to anything. Let's appreciate the work done and help each other as a community. Also, take some time to read and follow the forum rules, especially:

    2.1 Language: XDA is a worldwide community. As a result, what may be OK to say in your part of the world, may not be OK elsewhere. Please don't direct profanity, sexually explicit language or other offensive content toward Members or their work. Conversely, while reading posts from other members, remember that the word you find offensive may not be offensive to the writer. Tolerance is a two-way street.

    2.3 Flaming / Lack of respect: XDA is about sharing and this does not involve virtual yelling (flaming) or rudeness. Flaming or posting with a lack of respect is unacceptable. Treat new members in the manner in which you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instructions when you can, showing them respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.

    2.4 Personal attacks, racial, political and / or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive and therefore, none of these types of discussions are permitted on XDA.

    Regards,
    theimpulson,
    Senior Moderator | Developer Relations | Recognized Developer
    11
    OPlusExtras are back :)
    Screenshot_20220817-192303.pngScreenshot_20220817-192148.pngScreenshot_20220817-192151.pngScreenshot_20220817-192205.pngScreenshot_20220817-192208.pngScreenshot_20220817-192211.pngScreenshot_20220817-192218.pngScreenshot_20220817-192226.pngScreenshot_20220817-192239.pngScreenshot_20220817-192244.png