[ROM][14.0_r25][OFFICIAL] Evolution X 8.3 [03/04/24]

Search This thread

parcou

Senior Member
Jun 7, 2008
1,462
196
TN
Mods let me know if I need to unlink the zip but if you want dolby and a camera:
LMC8.4_8.4_R15_apkcombo.com.apk and the attached Dolby Magisk Module.

Anyways Long time evox oos11 user here and this rom is basically perfection out of the box. Super easy to migrate from evox oos11 with swiftbackup and I now have dual sim thanks to another thread on TMO OP8 conversion.

Regarding all the rather nasty commentary about the exclusion of dolby and OOS camera, you're frankly looking a gift horse in the mouth.

I'd much rather the rom to feel fast and unbloated and spend a few minutes looking for what's omitted than have it fully intact yet bloated and slow on first load. As much as I loved evo OOS11 I always had an unresponsive/slow camera which I personally couldn't address. And although I didn't have issues per se with Dolby I understand the omission in favor of less necessary apps.

Now I have the best of both worlds. An Incredible, super slick OOS which I have full confidence to flash over my aging parent's OP8 stock as well as the ability to add back the apps I need which still work flawlessly.

If you couldn't be bothered to google the dolby and camera addons in spite of the fact you're likely fiddling with MSM, rooting and custom roms, I really have no idea what to tell you.
Thank you!!!
 
  • Like
Reactions: ferreinf

parcou

Senior Member
Jun 7, 2008
1,462
196
TN
How do I get the clock back on my home screen and make the weather alert and Flashlight on/off go away?

Annoying, and it stays there all day. After some time, the clock returns, but then it can return to the two messages. Reboot does not fix or restart the launcher. I only want the CLOCK/Date no messages

umHbUI7g6Uppj5Z5YO7NTsh02skz1UTzwRpH4ghh4-F4Ykz5dxit7cK8g28qJMS_jDH76lc4hz_aiEGTumTskFoAz9wjO-mcc3lwK3C4jOtJYtIGB81ncfOio97sUWPGhTrG2me4o2vi0OZ9gyEfdpkhhgOJI82SewfUTUn7vhV8v24i2PzL8_phFHcs7T3RMH2kPgskkBLH21922OLKyUmVRZRWe8lKvMdIdbWc8wJHBTlLuo6bMcnLFFVBAOMRyIOacntbw4TOwNfvxVQRj6APJTgNcVY7Gap-NJL75AvTYFovsC13h6LKKEx8YkoVuPIdZ9ra0Xcy7koCbHtHzAF7KMfgSzAQ-IT40NZGr_Mn1arcnc1laVfRHeY_SN5dogS5kSRuA0EZhCp3trnyQbRy-9bYOCwv8RF7jkzdVv03G_9v-oLKBYYCPatoFvef0xGIKmCEMzoCcrOSjwbSKpKwmjfn-CuvT1oj53om_1NxScKhN9pYJ-7Xk8GPDtC3cIt-7klHQBalJvXbneGwVeL3BKALI0fHoMzIuABHM5hyqlbrgve5rfhkBt2G60Jic9DNZ9Yu1C4nuJIs6W0wXBLKd2rh_YxscxAuJAShREzfEThW2fH0HmyMtbnOojarJkNxdrAgE82HTvxvC6o8cySxoxYNaIlh_dkcRSb10jUej13V1vIfKqJ9hHKVx2G0G97WWnPMJArV26eyX647fKRpTuHidSuy1eYYxVQLKaJcxD1oxh_EgfBTjyhNFnNOCJ3IBwJ6VfZGa-5pCxr4QMB4tMmvIYJE1lEvxtsULkymGaRe6sPYjErbfGYOREpgozI6leQO8ojci2QqjNMp7KkT23xx-V-CjhBZL4KAIAm1Lic2BW8k-WERW82TRv1zBboO7PXg_kvCTlIhAzkhZ_yypzKY2Z1rU7CNPeYVXBkp-p233w=w606-h1329-no
 
Does anyone know if Google Fi works? This is another area where I know LineageOS excels, but Pixel Experience doesn't.

For anyone interested, Pixel Experience spoofs the model and various other properties, causing Google Fi to not work with the original SIM.
 
This isn't pixel experience.
That's a good answer, but it's not the one I was looking for. This isn't Pixel Experience, but the file for EvolutionX still can't be read by ADB like LineageOS can be.

Yes, everything has their differences, but it's your responsibility to list if Google Fi works or not, as it's already expected that most major carriers will. All that doesn't work on Pixel Experience is activation through the application, service is fine.
 

AnierinB

Retired Recognized Developer
That's a good answer, but it's not the one I was looking for. This isn't Pixel Experience, but the file for EvolutionX still can't be read by ADB like LineageOS can be.

Yes, everything has their differences, but it's your responsibility to list if Google Fi works or not, as it's already expected that most major carriers will. All that doesn't work on Pixel Experience is activation through the application, service is fine.
How do you expect me to know if it works when I don't even have Google Fi myself? Your expectations for free software are way too high, how about you check if it works and I'll go from there.

Also that file you're referring to isn't my problem to deal with whatsoever. I don't support third party modifications such as magisk, exposed, custom kernels, etc. So whatever you attempt installing on your device that doesn't work and isn't provided by me is not my responsibility.
 
Last edited:

apophis9283

Forum Moderator / Recognized Developer
Staff member
That's a good answer, but it's not the one I was looking for. This isn't Pixel Experience, but the file for EvolutionX still can't be read by ADB like LineageOS can be.

Yes, everything has their differences, but it's your responsibility to list if Google Fi works or not, as it's already expected that most major carriers will. All that doesn't work on Pixel Experience is activation through the application, service is fine.
I understand where you are coming from, however, to ask a dev to make sure it works on every network, is a tall task. If said dev uses T-Mobile then how would you expect him to know about Google-FI? Generally how it works, is you find out it doesn't work and you provide logs and devs see what they can do.
 
I understand where you are coming from, however, to ask a dev to make sure it works on every network, is a tall task. If said dev uses T-Mobile then how would you expect him to know about Google-FI? Generally how it works, is you find out it doesn't work and you provide logs and devs see what they can do.
I can't find out if it doesn't work, or if it does, if ADB (the latest version provided by the Android SDK) is unable to sideload a file.


For clarification, as I didn't seem to provide it in my previous posts, I was mainly trying to ask if EvolutionX will spoof a different device for the Google Fi application, as it must remain unspoofed to be able to activate. Sorry if my question was misunderstood.
 

Locutus99

New member
Mar 6, 2011
3
3
Thank you very much for the great rom.
This is for me the best rom for the OnePlus 8 Pro, significantly better than the original rom. Good battery life, very fast, very stable and it looks good too. In addition, OTA updates. Perfect!

Thanks again for your time and patience with us.

Greetings
Andreas
 
  • Like
Reactions: parcou and AnierinB

ItsmeeVishal

Member
Jan 27, 2023
20
7
Hi, is there any firmware update required for connecting to Jio 5g network? I have been invited to the Jio 5g program, but my oneplus 8t 5g is unable to connect to the 5g network while using this rom.
Hey bro.... I'm planning to install this rom.
My main concern is Jio 5g support.
Will you tell me it works on oneplus 8 on this rom or not?
 

Tins790

Member
Aug 1, 2016
12
1
In oneplus 8t i have a bug... When open a site internet and use the camera with chrome, is in black and white and not the principal camera
 

KrazyKlutt

Senior Member
Jul 30, 2014
210
80
Really awesome to see such amazing development!

Some questions:

AoD / Ambient display have issues?

Fingerprint is still slower than OOS?

Do Adaptive brightness have major issues so it's better not to use?
 
  • Like
Reactions: Soerdroid

Tins790

Member
Aug 1, 2016
12
1
Any browser recognizes me as the main camera in black and white
 

Attachments

  • Screenshot_20230205-083148_Camera2_Probe.png
    Screenshot_20230205-083148_Camera2_Probe.png
    222.8 KB · Views: 56
  • Screenshot_20230205-083232_Chrome.png
    Screenshot_20230205-083232_Chrome.png
    2 MB · Views: 56

AnierinB

Retired Recognized Developer
In oneplus 8t i have a bug... When open a site internet and use the camera with chrome, is in black and white and not the principal camera

Any browser recognizes me as the main camera in black and white
This will be fixed on the upcoming releases. What's happening is the browser is defaulting to one of the auxiliary cameras

I can't respond to every post right away, please don't submit duplicate reports next time and wait for me to respond.
 

Tins790

Member
Aug 1, 2016
12
1
This will be fixed on the upcoming releases. What's happening is the browser is defaulting to one of the auxiliary cameras

I can't respond to every post right away, please don't submit duplicate reports next time and wait for me to respond.
Sorry but i have mistake to upload a photo for the example. Thank for the answere
 
  • Like
Reactions: AnierinB

KrazyKlutt

Senior Member
Jul 30, 2014
210
80
Choosing "system font" or "google sans" (yeah those are the same) doesnt apply for me on the EvoX launcher or apps like Nekogram, Google Keep etc.

But all the other I've tested do. Is this some issue on my end?
 

parcou

Senior Member
Jun 7, 2008
1,462
196
TN
Really awesome to see such amazing development!

Some questions:

AoD / Ambient display have issues?

Fingerprint is still slower than OOS?

Do Adaptive brightness have major issues so it's better not to use?
Great rom I've enjoy using it...

My findings:

AOD works well for me when I use it. But I do not since it is well known that Pixel has an issue with the Adaptive brightness and seems to be too bright at night and too dim during the day... Works right at times, then it does not. Many posts on the Pixel devices, so my guess is this Rom carries it over since it is Pixel based. I just turn it off

The finger reader is the same with AOD it will not always pick up the finger, although it tells me to press firmly. So there is a Pixel issue with the finger reader. So I turn it off. My screen unlocks each time with a blank screen, but I wish I could keep using the AOD.

This is my on/off experience I am NOT saying this is for all users and their experience
 
  • Like
Reactions: moccor

Staff9643

New member
Feb 7, 2023
2
0
Hello. Why does the AOD go out 3-4 seconds after the screen is locked?
OnePlus 9R
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    to install additional packages,you need to reboot recovery first do you want to reboot to recovery now? NO YES, on my device this comes and cmd stuck at 47% from last 30 minutes. i pressed NO and it is installed. if someone have the same issue.
    Having the adb sideload command show 47% complete is normal (happens on all custom ROM installs). As long as you get to the reboot to recovery option as you described, you should be fine.
    1
    Is this ROM discontinued?
  • 75
    Evolution X 8.1 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)

    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

    • Google restore isn't functioning at this time.
    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.

    First Time Install (8 & 8 Pro)
    1. Be on any version of OOS12 or OOS13 (OOS 13.1.0.582(EX01) 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 (OOS 13.1.0.582(EX01) for 8T & OOS 13.1.0.583(EX01) 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

    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)

    28



    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
    5ac2ab61387ede01016f92acfa122a08338.png
    Commonly asked questions & answers:

    Q: Why am I getting "error cannot read" while attempting to sideload the ROM
    Well, you should be using the latest platform-tools and have it added to PATH. A lot of unofficial drivers floating around on the internet install outdated adb/fastboot along with the drivers. Please refrain from installing these as well as minimal adb & fastboot; Use the official google driver and official platform-tools instead.

    Alternatively you can prefix each adb/fastboot cmd with ./ while in the platform-tools folder via powershell or bash, etc.

    For example:
    ./adb sideload ./rom.zip

    This basically tells the shell "Hey, I want to execute this local binary rather than the one in PATH".

    Q: I'm a windows user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?


    Q: I'm a linux user and my device is not being listed when I run adb/fastboot devices. I'm using the latest platform-tools, what could be the reason for this?

    Q: Why is MTP and/or Android Auto not working?
    Set the default USB configuration in Settings > The Evolver > Miscellaneous > USB Configuration

    Don't see your question? Well, feel free to post a comment in this thread, we will reply as soon as we can. We'd appreciate if users used XDA FIRST and the telegram group as a LAST RESORT.

    To be continued (I'm sure).

    Firmware update:

    FLASHING THE WRONG DDR TYPE 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!!
    1. Check your DDR type using the following command:
    adb shell getprop ro.boot.ddr_type

    0 = ddr4
    1 = ddr5

    if getprop returns an empty value, use the following commands instead (requires root):
    adb shell su cat /proc/devinfo/ddr_type
    DDR4 = DDR4
    DDR5 = DDR5

    1. Download and flash the firmware zip that matches your device and DDR type:
    8 (instantnoodle)
    8 Pro (instantnoodlep)
    8T (kebab)
    9R (lemonades)

    2. Reboot to recovery and then sideload the ROM.

    Custom Kernels:

    Custom kernels may be flashed at YOUR OWN RISK. However, we will not provide extended support regarding such and it is up to YOU, the end user to make your reports in the appropriate thread for X kernel, not in this thread.

    Obtaining root:
    Let it be known that we will not assist anyone with bug reports until they have disabled all modules and restored to the default, unpatched kernel that is shipped with the ROM!

    Root can be obtained by either one of the following methods.

    1. Download the Magisk.apk on your pc (you can change the file extension to .zip if you wish, though it is not required).
    2. Reboot to recovery
    3. Navigate to Apply update -> Apply from ADB
    4. adb sideload magisk.apk (replace "magisk" with actual filename)
    1. Download the full rom.zip from post #2 of this thread
    2. Download payload-dumper-go that corresponds to the architecture of your pc
    3. Run payload-dumper-go against the rom.zip
    4. Grab boot.img from the extracted folder and transfer it to your device
    5. Patch the boot.img with the magisk application and transfer the patched image to your pc
    6. Reboot to bootloader
    7. fastboot flash boot boot.img (replace "boot" with actual filename)

    Retaining root across OTA updates:
    When an OTA update is available, let it download and install. Before rebooting simply open Magisk Manager and click on the first "install" button and select "install to inactive slot". Once it's done, reboot and enjoy.

    Reporting bugs and submitting logs:

    In most cases logs should be provided when reporting bugs. This can be done by enabling USB debugging in developer options of the device, connecting it to your PC and running one of the following cmds depending on the type of bug/issue while reproducing it:

    General system log
    adb logcat > logcat.txt

    Kernel log
    adb shell su -c dmesg > dmesg.log

    Please provide a detailed description of the bug/issue as well as link/upload the log you had taken.
    There are exceptions to this as some issues are unable to be caught in logs. In this case, it is expected that users provide clear and accurate steps to reproduce the issue.

    Getting involved in the development:

    We've set everything up in such a way where all you need to do is install AOSP build dependencies, initialize a repo client, init the tiramisu branch of our manifest, sync the code and lunch your device (e.g lunch evolution_instantnoodlep-userdebug); Roomservice will automatically sync all device specific dependencies for you to compile without error. There is no need to manually clone anything due to this and applies to OnePlus 6, 6T, 7, 7 Pro, 7T, 7T Pro, 8, 8 Pro, 8T, 9R, 9 & 9 Pro (enchilada, fajita, guacamoleb, guacamole, hotdogb, hotdog, instantnoodle, instantnoodlep, kebab, lemonades, lemonade & lemonadep).

    Device and ROM source changes can be submitted on github to the appropriate repositories by making pull requests via comparing forks. Please follow the google patch format for commits and triple check your changes by compile testing and verifying they're correct. Please retain proper authorship if you are not the author!
    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".