Development [ROM][13.0_r49][OFFICIAL] Evolution X 7.9.2 [05/31/2023]

Search This thread

norryhox

Senior Member
May 31, 2015
172
31
Wegberg
first of all thanks great rom.
After I changed the settings for the gesture control yesterday, my line at the bottom is gone, the back gesture no longer works and switching to three or 2 buttons no longer works either.
does anyone know and can help me?
 

tensux

Senior Member
Nov 18, 2011
1,069
294
boston
i'm getting decent battery life, have not rooted
 

Attachments

  • messages_0.jpeg
    messages_0.jpeg
    159.1 KB · Views: 140
  • Like
Reactions: Veiranx

norryhox

Senior Member
May 31, 2015
172
31
Wegberg
I found the error, I had switched off Show navigation bar at the bottom of the screen in the "Keys" settings. Apparently a small bug that shouldn't affect the gesture control.
 

AMDFenics

Senior Member
Oct 18, 2012
615
309
Just a question, don't punch me, if it's a stupid one... Didn't flash a custom rom for a long time...

The guide says, "don't relock the BL unless u are on stock rom".
What would happen, if i relock on custom rom without anything rooted.
Just like here - Evo ROM, with vendor_boot.img. Nothing else installed.

Thanks :)


Damn it, @AnierinB and the whole team, thank you so much for this ROM! This customization is epic...
 
Last edited:

Dopamin3

Senior Member
Dec 7, 2010
437
239
OnePlus 8T
Google Pixel 6a
Just a question, don't punch me, if it's a stupid one... Didn't flash a custom rom for a long time...

The guide says, "don't relock the BL unless u are on stock rom".
What would happen, if i relock on custom rom without anything rooted.
Just like here - Evo ROM, with vendor_boot.img. Nothing else installed.

Thanks :)


Damn it, @AnierinB and the whole team, thank you so much for this ROM! This customization is epic...
You'll brick your phone. Maybe not right away, but an OTA or something could mess it up.

Why do you even need to consider locking BL? Out of the box, Evo X passes all safety net checks, nothing can even tell you're using a rooted/custom ROM phone. If you do want to root then there are ways to hide it as well.

Older OnePlus phones like the 8 series had MSMTool available- basically an engineer utility that could always save a device as long as it booted into EDL mode regardless of bootloader lock status. Google is nice and provides the factory images and full OTAs, but you're not recovering from a brick if your bootloader is locked.
 
  • Like
Reactions: Veiranx

norryhox

Senior Member
May 31, 2015
172
31
Wegberg
Is there the function
Automatic switching from hands-free to handset with the proximity sensor?
If not I'd appreciate having it
 

Dopamin3

Senior Member
Dec 7, 2010
437
239
OnePlus 8T
Google Pixel 6a
So

so as a general definition, for all non pixel supporting countries root solutions will be required to enable VolTe and 5g?
Yes I think this is correct info. That is UNTIL Google releases QPR2 with official support for 5G/VoLTE in more countries and Evolution X merges it in. This will probably take a little bit of time in addition to when it finally comes out. (lol normally Pixel monthly updates come out Mondays, here we are Thursday and no word or updates from Google)
 

AMDFenics

Senior Member
Oct 18, 2012
615
309
You'll brick your phone. Maybe not right away, but an OTA or something could mess it up.

Why do you even need to consider locking BL? Out of the box, Evo X passes all safety net checks, nothing can even tell you're using a rooted/custom ROM phone. If you do want to root then there are ways to hide it as well.

Older OnePlus phones like the 8 series had MSMTool available- basically an engineer utility that could always save a device as long as it booted into EDL mode regardless of bootloader lock status. Google is nice and provides the factory images and full OTAs, but you're not recovering from a brick if your bootloader is locked.
Nah, i don't want to relock the BL, was just curious what exactly happen when do so. I'm aware of the chance to brick it... Is the any CRC check or something, that stops it from starting?
 

JohnTheFarm3r

Senior Member
Apr 29, 2016
1,648
844
Jupiter
OnePlus 9 Pro
Nah, i don't want to relock the BL, was just curious what exactly happen when do so. I'm aware of the chance to brick it... Is the any CRC check or something, that stops it from starting?
It won't boot, that's all. You'll just soft brick the phone.

To lock the bootloader on a custom ROM you would require a custom AVB key.

Feel free to check what AVB is and what it does, and you'll understand why you won't boot your phone if you try to lock the BL on a custom ROM.
 
  • Like
Reactions: AMDFenics

AMDFenics

Senior Member
Oct 18, 2012
615
309
It won't boot, that's all. You'll just soft brick the phone.

To lock the bootloader on a custom ROM you would require a custom AVB key.

Feel free to check what AVB is and what it does, and you'll understand why you won't boot your phone if you try to lock the BL on a custom ROM.
THX exactly what i asked for :)
 

Top Liked Posts

  • 1
    i have flashlight bug too. also random ui crashes after qs pulling down.
    1
    Yeah I flashed May Stock before flashing this.
    Should I try Beta stock?
    Nooo, not as far as I'm aware... Will have another read of OP but pretty sure it says to NOT use the beta builds. If you're gonna try another stock base rom, could try April.

    EDIT: this is from OP 'Please note that the required April/May firmware images are shipped with these builds. However, you will need to be on STOCK stable April/May prior to following these instructions, not QPR BETAS OR A14DP! This includes having custom kernels installed. STOCK MEANS STOCK!'
  • 5
    Day two running the latest build. I've been running this phone hard and messing with absolutely every mod and customization option possible. I cannot find a bug. I'm trying, and I just can't find any lol. If you're on the fence and coming from stock and your reading this, just go ahead and install!
    4
    Kernel can be flash after the EvoX? Also, what kernels are peeps using that they like?
    Screenshot_20230521-222550_Chrome.png
    3
    No doubt most are aware but a brief note for those of you rooted and want to keep root....

    Update via ota (settings/system/system update.
    DO NOT REBOOT once the install is finalised.
    Open magisk manager app, select install magisk (not app), choose 'install after ota'. Reboot.

    This will install magisk to inactive slot. Root will be maintained
    3
    OP says to be sure you're on April firmware.


    There are no differences between April/May firmware.
    2
    I flashed the evolution ROM twice now in the past 3 weeks. I gave up the first time cause the phone does not have a mobile connection. I tried it again now but with the same issue - no mobile network. Is anyone facing this issue on Pixel 7PRO?

    You're the only person I've had mention that so far, everyone else seems to be running the ROM just fine on 7, 7 Pro and 7a. Make sure you have the proper firmware installed prior to flashing the ROM, as the latest 7/7 Pro builds may not have it included.

    Also, please do not quote the entire original post (op) next time.
  • 56
    Evolution X 7.9.2 for the Google Pixel 7, 7 Pro & 7a [panther][cheetah][lynx]

    Banner.png


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

    - Team Evolution X -
    @joeyhuab (Founder/Lead Developer)
    @RealAkito (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

    sxs3pbW.png


    You tell me :cool:

    DO NOT FLASH GAPPS, ALREADY INCLUDED

    VvzRh0K.png

    Please note that the required April/May firmware images are shipped with these builds. However, you will need to be on STOCK stable April/May prior to following these instructions, not QPR BETAS OR A14DP! This includes having custom kernels installed. STOCK MEANS STOCK!

    First Time Install
    1. Download vendor_boot & rom for your device from here
    2. Reboot to bootloader
    3. fastboot flash vendor_boot vendor_boot.img
    fastboot reboot recovery
    4. While in recovery navigate to Factory reset -> Format data/factory reset and confim to format the device.
    5. When done formatting, go back to the main menu and then navigate to Apply update -> Apply from ADB
    6. adb sideload rom.zip (replace "rom" with actual filename)
    7 (optional). Reboot to recovery to sideload any add-ons (e.g magisk)
    8. Reboot to system & #KeepEvolving

    Update
    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 (optional). Reboot to recovery to sideload any add-ons (e.g magisk)
    5. Reboot to system & #KeepEvolving

    OTA

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






    S2t0kJ9.png


    17
    5ac2ab61387ede01016f92acfa122a08338.png
    Commonly asked questions & answers:

    Q: Why am I getting "error cannot read" while attempting to sideload the ROM or are unable to fastboot flash vendor_boot
    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: Will you release builds in the update.zip format?
    No, we will not be releasing builds in that format due to a handful of reasons; The main reason being that it is not able to be installed via OTA and is incompatible with our official devices infrastructure.

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

    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 init_boot.img from the extracted folder and transfer it to your device
    5. Patch init_boot.img with the magisk application and transfer the patched image to your pc
    6. Reboot to bootloader
    7. fastboot flash init_boot init_boot.img (replace "init_boot" with actual filename)

    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-pixel branch of our manifest, sync the code and lunch your device (e.g lunch evolution_cheetah-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 Pixel 6, 6 Pro, 6a, 7, 7 Pro & 7a (oriole, raven, bluejay, panther, cheetah & lynx).

    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!
    11
    It's a server side issue on googles end regarding CTS since this morning on multiple device, not just p7 series running customs. Please keep in mind this is separate from SN not passing by default without modules (which was already fixed, but now there's this).
    Anyways, this was resolved. Builds will be out sometime tomorrow.