[ROM][13.0_r20][OFFICIAL] Evolution X 7.5 [01/18/2023]

Search This thread

parcou

Senior Member
Jun 7, 2008
1,410
180
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
85
88
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
193
45
Tarnobrzeg
OnePlus 9 Pro
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
316
34
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,060
766
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
316
34
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
268
80
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,410
180
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,060
766
@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,060
766
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
105
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
    The OP8/OP8P twrp thread was updated yesterday with a13 compatibility.
    I haven't tried it yet, but I'll do asap.

    A question regarding the last update: "instantnoodlep: Update fw and libs to F.15" means that I have to flash the new firmware before to download and install the OTA? Or I can flash the OTA update as usually?
    Firmware is shipped with instantnoodle/p.

    Only kebab/lemonades users need to manually update firmware before flashing the ROM.
    3
    Thank you for your work. I have been using this rom for a few days and, it is awesome. I personally can't see why anyone who is running Android 13 would choose to be without this rom. This rom brings new life to the oneplus 8 (I'm coming from android 11,tried oxygenos 13 when released and went back to 11, never tried 12, and now I'm using this rom with no regrets. A complete daily driver out of the box. Thanks again. I will be supporting.

    I appreciate the kind words and I'm glad to see many are enjoying our work! There's definitely more to come so stay tuned and #KeepEvolving! If you do wish to support, donations can be made via the link in the OP as the "friends and family" option. :) Much appreciated and thank you in advance!
    3
    Im currently trying to figure out the issue. If i find a solution i will be sure to tell you what it is
    Bro found it, it was the version of the ADB, try this one:


    directly from google works tight away
    2
    Please add oos cam and dolby sir that's the least I need from this rom.

    its been mentioned lots that the developer is not adding OOS Cam or Dolby. It's not going to be added.
    2
    To note:

    -Rom has been working amazing, with great battery life and performance, love A13 animations, lot of props to the Dev
    -Using Greatness GCam mod and getting some AMAZING results

    System wise:

    -FP is working a little slower than OOS, (again, maybe just 1 seg longer to read)
    -When I choose the FPUDS animations, they play really fast, like 2.5x the regular speed, is this normal?
    -Warp suppose to charge at 30W but tops I've seen on several charges is 22W
    -Is there an option to lock apps on recents? Can't seem to find it xp

    Apps wise (just to mention):

    -Google Photos got stutter on all my videos when playing (new ones and old ones already uploaded)....but when I play them with other app (google files ie) they play just fine
    -When snap a photo on WhatsApp, it froozes the screen from 3-5 secs and then show the photo taken

    Always available for trying and testing stuff 😋
    Again thanks to the Dev for the awesome work, you revived my 8 Pro 🙏🏽

    Edit 1: G Photos just need an update, my bad!
  • 58
    Evolution X 7.5 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
    
    - Theming Settings (Style, Color Source, Accent Color, Accent Background, Background Color, Luminance, Chroma, Tint Background)
    - Custom Themes (Black, Clear, Vivid, Paint In The Snow, Espresso)
    - Dark Theme Schedules
    - Lock screen Clock Fonts (16 Fonts)
    - Headline/Body Fonts (53 Fonts)
    - SB Icon Packs (10 Styles)
    - SB Signal Icon Packs (14 Styles)
    - SB WiFi Icon Packs (10 Styles)
    - System Icon Shape Packs (16 Styles)
    - 3 Button Navbar Styles (10 Styles)
    
    Status bar
    
    - Status Bar Lyrics
    - Clock Styles (Right, Center, Left)
    - Clock & Date Configs (Auto Hide, Hide Duration, Show Duration, Seconds, AM/PM, Font Size, Date Position/Case/Format)
    - SB Logo Pack (20 Styles, Right/Left)
    - Network Traffic Indicators
    - Battery Icon Styles (19 Styles)
    - Battery Percent (Hidden, Inside Icon, Next To Icon)
    - Battery Bar (Thickness, Alignment, Blend Colors, Reverse Direction, Colors, Animation)
    - System SB UI Tuner
    - Data Disabled Icon (On/Off)
    - Old Style Mobile Data
    - 4G Instead Of LTE
    - Roaming Indicator
    - WiFi Type Icon
    - Colored Icons
    - Notification Count
    - Bluetooth Battery Status
    - Mic/Camera Privacy Indicator
    - Location Privacy Indicator
    - Media Projection Privacy Indicator
    
    Notifications
    
    - ReTicker
    - App Colored Background For Reticker
    - Heads Up (Time Out, Importance Threshold, Less Boring, Stoplist/BlockList)
    - Force Expand Notifications
    - Notification Sound If Active
    - Kill App Button
    - Blink Flashlight For Incoming Call (When Ringing, When Silent, When Entierly Silent, Always)
    - Blink Flashlight For Notifications
    - In-Call-Vibrations (Connect, Waiting, Disconnect)
    
    Quick Settings
    
    - Clock
    - Clock Font Size
    - Date
    - Battery Style (15 Styles)
    - Battery Percent Location (Hidden, Inside Icon, Next To Icon)
    - Battery Estimates
    - Secure QS Tiles Requires Unlocking
    - Quick QS Pulldown (Disabled, Right, Left, Always)
    - Brightness Slider (Never, Expanded, Always)
    - Brightness Slider Position (Top, Bottom)
    - Auto Brightness Icon
    - Hide Labels
    - Label Text Size
    - Smart Pulldown
    - Vertical Layout
    - Columns In Portrait (2-5)
    - Columns In Landscape (2-6)
    - QS Tile Animation Style (3 Styles)
    - QS Tile Animation Druations (3 Speeds)
    - QS Tile Animation Interpolator (8 Styles)
    - Vibration On Touch
    - Vibration On Touch Duration
    - QS Footer Warnings
    - Show Data Usage
    - User Account Icon
    - 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
    - On-The-Go Mode
    - Settings
    - Lock Down
    - Emergency
    - Device Controls
    - Users
    - Logout
    - Bug Report
    
    Gestures
    
    - System Settings
    - Quick Tap
    - Volume Button Playback Control
    - Swipe To Screenshot
    - Brightness Control
    - PWR Button Torch
    - Double Tap To Sleep Status Bar
    - Double Tap To Sleep Lock screen
    - AOSP Gestures
    - Pill Length
    - Pill Radius
    - Hide IME Button Space
    - Back Gesture Animation
    
    Lock screen
    
    - Edge Light
    - Always On Fingerprint
    - UDFPS Icon Picker (55 Styles)
    - UDFPS Animation Picker (38 Styles)
    - Lock screen Charging Info
    - Hide Status Bar
    - Hide QS During Secure Lock screen
    - Media Cover Art (5 Filters)
    - Ripple Effect
    - Fingerprint Authentication Vibration
    - Fingerprint Error Vibration
    
    Buttons
    
    - Navigation Bar
    - Compact Layout
    - Invert Layout
    - Show Vol Panel On Left
    - Per App Vol Control
    - On-Screen NavBar
    - Reorient Volume
    - 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)
    - Power Menu Animations (11 Styles)
    - Android P Animation Style
    
    Miscellaneous
    
    - AOD Display Schedule
    - Google Services
    - Parallel Space
    - Game Space
    - Smart Pixels
    - App Lock
    - Launch Music App On Headset Connection
    - Unlimited Photos Storage
    - Unlock Higher FPS In Games
    - Netflix Spoof
    - Pulse Music Visualizer (Navbar, LS, Ambient)
    - Volume Panel Timeout
    - Jitter Test
    - Ignore Secure Window Flags
    - Show CPU Info
    - Toast App Icon
    - Sensor Block Per Package
    - Wakelock Blocker
    - Alarm Blocker
    - Default USB Configuration
    - Radio Info
    
    Evolution X Launcher
    
    - Icon Packs
    - Notification Dots
    - Icon Size
    - Icon Font Size
    - Max Lines For App Label
    - Lock Layout
    - Add App Icons To Home
    - Dark Status Bar
    - Double Tap To Sleep
    - Wallpaper Scrolling
    - Wallpaper Zooming
    - At A Glance
    - Swipe To Access Google Feed
    - Hide/Show Status Bar
    - Top Shadow
    - Icon Labels On Desktop
    - Hotseat Background
    - Google Search bar
    - Themed Icons
    - Corner Radius
    - Themed Icons In App Drawer
    - App Drawer Search bar
    - Icon Labels In App Drawer
    - App Drawer Row Height
    - App Drawer Background Opacity
    - Recents Background Opacity
    - Recents Scroll Vibration
    - Recents Screenshot
    - Recents Google Lens
    - Recents Clear All
    - Suggestions In All Apps List
    - Suggestions On Home
    - Blocked Suggestions
    - Parallel Space
    - Taskbar
    - Rotation
    - Hidden & Protected Apps
    Code:
    My signature Universal OPlusExtras application:
    - Awesome alert slider (Notification/Flashlight/Brightness/Rotation/Ringer/Notification & Ringer/Refresh rate/ExtraDim/NightLight/ColorSpace)
    - Ambient display gestures (raise2wake)
    - Kcal
    - Per-app refresh rate
    - DC-Dimming 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)
    - USB-OTG toggle
    - USB2.0 Fastcharge toggle
    - System Vibration Strength preference

    sxs3pbW.png


    You tell me :cool:

    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png

    DO NOT flash instantnoodlep (8 Pro) on instantnoodle (8) or vice versa, else you will semi brick your device! The only way to recover from this is by purchasing an EDL DEEP FLASH cable and using it in-conjunction with msmtool.

    Please note that we ship OOS13 F.10 abl.img on 8, 8 Pro, 8T & 9R to bypass the BL unlocked warning!
    Please note that we ship a Custom logo.img on 8, 8 Pro, 8T & 9R to better match the ROM!


    First Time Install (8 & 8 Pro)
    1. Be on any version of OOS12 or OOS13 (F.15 firmware is included in these builds)
    2. Download vbmeta, recovery, and rom for your device from here
    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
    6. adb sideload rom.zip (replace "rom" with actual filename)
    7. Format data, reboot to system & #KeepEvolving

    First Time Install (8T & 9R)
    1. Be on the latest OOS13 (F.15 for 8T & F.19 for 9R)
    2. Download copy_partitions, vbmeta, recovery, and rom for your device from here
    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
    6. adb sideload copy_partitions.zip (press "yes" when signature verification fails) and then reboot to recovery
    7. Repeat step 5 and adb sideload rom.zip (replace "rom" with actual filename)
    8. Format data, reboot to system & #KeepEvolving

    Please note that if you are not on F.15 (kebab) or F.19 (lemonades) firmware, your proximity sensor will cease to function until you update to said firmware!!

    Update (8, 8 Pro, 8T & 9R)
    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

    Firmware Update (8, 8 Pro, 8T & 9R)​

    21



    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
    13
    Not sure why you sound so bitter. Everyone makes his own choices, however one can't deny the reality - the stock OS is better at this point of time than any other ROM.

    I've seen people updating to the latest build of Evo and their data wiped without warning. The developer didn't say a word of precaution in this forum that the users data would be wiped upon the update. That's a critical oversight and logcats will not help getting your data back.

    I won't say anything about other issues I encountered myself. I mentioned them earlier in this forum thread but never got any reply.

    While the sixth version of EvoX (Android 12), which was based on OOS 11 worked quite well (I was very happy with it at some point), everything went downhill when the base was changed to OOS 12, including the newly-introduced absence of OOS cam.

    OnePlus 8 Pro can make some beautiful videos with hyperstabilization, which no other camera applications are capable of. However, the developer straight up said he will never add the native camera back. I understand that quite a number of people couldn't care less about OOS cam, but for many that's something that would prevent from using this ROM.

    Some other Android 13-based custom ROMs for OnePlus 8 series do have OOS cam, which means that the absence of it in EvoX isn't a result of a technical limitation, but rather a result of the developer's unexplained reluctance to implement the feature.

    Everyone has their own views and this is mine. I do understand that all of these custom ROMs are provided for free and on "as is" basis. What I'm saying is that this one In particular isn't stable and feature-rich enough to be a daily driver.
    1. Those builds for OnePlus 8/8Pro were updated to use qcom wrapped key encryption changes (which was clearly in the changelog). It should be a given that any changes to encryption would result in having to format data. I also intentionally mismatched the hashes in our OTA updater system so OTA would fail due to such. You know, there's a "Device Support" link in the OP thread you also could have joined to ask.

    2. I've explained my stance on OOS cam multiple times. Just because "other ROMS" include it doesn't mean I have to. My ROM, my rules. Use something else if you have an issue with that as you're under no obligation to use my ROM, just as I am under no obligation to add anything I don't want to. Also, there are very impressive GCAM mods (with the appropriate XMLS) for OnePlus 8 series and we now ship Aperture from LOS, which just added support for OIS as well as 4k/60fps video recording on main lens + aux lenses.

    3. "What I'm saying is that this one In particular isn't stable and feature-rich enough to be a daily driver." The ROM is pretty stable and full of features, so I don't understand what made you come to that conclusion though you are entitled to your own opinion (emphasis on opinion, as it isn't factual). I believe my user count, the amount of work I put into squashing bugs & working directly with OnePlus LOS devs to fix issues in the base device trees, etc shows the complete opposite of your "opinion".
    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