Development [ROM][13.0_r43][OFFICIAL] Evolution X 7.9 [05/10/2023]

Search This thread

dmbardal

Senior Member
I've had the same issues as several here, but on the newest build.

- Bluetooth does not work until i turn airplanemode on/off.

These two big issues:
- Screen won't rotate at all
- Auto-brightness does not work

(can anyone confirm this? Will try a reflash later tonight.)

Edit: I just realized I dont even have working sound at all
This must be some error that a reflash will fix.
Will update.

Edit2: A reflash did it. No idea what happened.
 
Last edited:

thomas.raines

Recognized Developer
Jun 23, 2011
2,162
3,899
Hutto
@AnierinB
Is source code broken or am I misssing something?

Code:
FAILED:
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
build/make/core/main.mk:1120: error: exiting from previous errors.
06:18:02 ckati failed with: exit status 1
 

chxei

Senior Member
Jun 26, 2015
498
129
tbilisi
Is anyone experiencing missing quick settings options? I had battery percentage and increased row count number but they are gone. I did OTA upgrade. Can someone with a clean flash confirm their non/existence?
 

Schnedi

Senior Member
Oct 27, 2011
983
2,489
@AnierinB
Is source code broken or am I misssing something?

Code:
FAILED:
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
build/make/core/main.mk:1120: error: exiting from previous errors.
06:18:02 ckati failed with: exit status 1
Need this commit

 

Schnedi

Senior Member
Oct 27, 2011
983
2,489
Is anyone experiencing missing quick settings options? I had battery percentage and increased row count number but they are gone. I did OTA upgrade. Can someone with a clean flash confirm their non/existence?
March update was huge, some code need to be re-written, those options have been removed for now

 
  • Like
Reactions: chxei

thomas.raines

Recognized Developer
Jun 23, 2011
2,162
3,899
Hutto
Need this commit

Got past previous error but now I have

Code:
hardware/google/graphics/common/libhwc2.1/libdrmresource/drm/drmeventlistener.cpp:21:10: fatal error
: 'drm/samsung_drm.h' file not found
#include <drm/samsung_drm.h>
 

thomas.raines

Recognized Developer
Jun 23, 2011
2,162
3,899
Hutto
March update was huge, some code need to be re-written, those options have been removed for now

And this is why I prefer to build myself. I can add things like battery percentage back...
 

AnierinB

Recognized Developer
@AnierinB
Is source code broken or am I misssing something?

Code:
FAILED:
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
external/android-nn-driver/Android.mk: error: "[email protected] (EXECUTABLES android-
arm64) missing libGLES_mali (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real proble
ms until later in the build.
build/make/core/main.mk:1120: error: exiting from previous errors.
06:18:02 ckati failed with: exit status 1
[/QUOTE]
[QUOTE="thomas.raines, post: 88360289, member: 4145127"]
You synced the wrong branch of our manifest. You need to sync tiramisu-pixel, not base tiramisu. There are reasons other than this specific error as well, so even if you manually solved it, then you will still encounter other issues in the resulting build if you do not compile using tiramisu-pixel.
Got past previous error but now I have

Code:
hardware/google/graphics/common/libhwc2.1/libdrmresource/drm/drmeventlistener.cpp:21:10: fatal error
: 'drm/samsung_drm.h' file not found
#include <drm/samsung_drm.h>
sudo apt-get install libdrm-dev
 
Last edited:
  • Like
Reactions: kkjb

jake.99x3

Senior Member
Jul 7, 2013
383
91
Richmond
Is anybody able to link me the steps I should take before flashing this ROM? I have not updated my pixel since buying in early November. It's Rooted and bl unlocked...
 

Homeboy76

Recognized Contributor
Aug 24, 2012
3,865
2,309
Google Pixel XL
Google Pixel 7 Pro
Is anybody able to link me the steps I should take before flashing this ROM? I have not updated my pixel since buying in early November. It's Rooted and bl unlocked...
Did you réad the Installation instructions in the OP (post #1).

VvzRh0K.png

Please note that the Required March firmware images are shipped/flashed with these builds!

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). DO NOT FLASH GAPPS, ALREADY INCLUDED.
  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). DO NOT FLASH GAPPS, ALREADY INCLUDED.
  5. Reboot to system & #KeepEvolving
OTA
  1. Check for update. If available, select "Download and install" (approx 10-15 min)
  2. Reboot & #KeepEvolving
 
Last edited:
  • Like
Reactions: kkjb

jake.99x3

Senior Member
Jul 7, 2013
383
91
Richmond
Did you réad the Installation instructions in the OP (post #1).

VvzRh0K.png

Please note that the Required March firmware images are shipped/flashed with these builds!

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). DO NOT FLASH GAPPS, ALREADY INCLUDED.
  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). DO NOT FLASH GAPPS, ALREADY INCLUDED.
  5. Reboot to system & #KeepEvolving
OTA
  1. Check for update. If available, select "Download and install" (approx 10-15 min)
  2. Reboot & #KeepEvolving
Yes but I am unsure if it's as simple as factory resetting then following the first time install instructions. Is it safe to flash after factory reset on November update or should I go to February then March
 

dmbardal

Senior Member
So, you have to flash the March stock bootloader and radio before doing a factory reset and flashing this ROM. I didn't know that. You sir have learnt me something. :)
Well no, but its always best to clean flash just in case.
I never dirty-flash anymore (many dirty-flash after flashing bootloader and radio manually).

Pixel flasher via web to stock -> flash custom ROM.
Best way to avoid issues.
 

jake.99x3

Senior Member
Jul 7, 2013
383
91
Richmond
Well no, but its always best to clean flash just in case.
I never dirty-flash anymore (many dirty-flash after flashing bootloader and radio manually).

Pixel flasher via web to stock -> flash custom ROM.
Best way to avoid issues.
Cheers. I appreciate the help, my last rooted device was a galaxy s4 haha. I didn't even know about the web flasher
 

Top Liked Posts

  • 1
    Do you take requests for the UDFPS icons?
    You can import custom one's in the system already, make sure to not apply them using gphotos however as that will most likely not work.
  • 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
    OP says to be sure you're on April firmware.


    There are no differences between April/May firmware.
    2
    So far, I really like the Evo X. But one thing caught me... What do I have to install or do to have live wallpapers again?

    You mean the pixel live wallpapers? Google limits the ability to expose them to Pixels wallpaper/theme picker only. However, there are ports of the wallpapers scattered across the internet, including xda. Though most of those packages do not include all the wallpapers. Just something you'll have to cope with when running a ROM that doesn't use pixels wallpaper/theme picker.
    2
    This is the first custom I've ever flashed on my Pixel 7 Pro due to being very content with stock rooted and ASOP Mods to fulfil my customisation needs.

    I must say I am very impressed! Installation was smooth and I didn't even need to 'faff' around with patching Magisk due to the simplicity of adb sideloading Magisk (note: for some reason the apk renamed to having a .zip extension didn't work, I needed to simplify it's name to "magisk.zip" which flashed perfectly. I was able to flash Kiri kernel via FKM (either perhaps because May stock had the relevant disabled flags or maybe EvoX just allows custom kernels to be flashed out of the box?).

    There is a wealth of features which is great to have and everything just works! With the Kiri kernel everything is super smooth and even on the first overnight settling it was pulling 0.5% p/h battery, which I presume may only but improve over time.

    Highly recommended, a big thanks to all involved in this rom :)
  • 55
    Evolution X 7.9 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.