[ROM][13.0_r49][OFFICIAL] Evolution X 7.9.2 [06/02/2023]

Search This thread
By:
Advanced…
B

Bennedict 929

New member
Apr 14, 2018
2
0
joshua3001 said:
Anyone else seen this happened:

When you switch between apps (on recents manager) and you tap on another app, it freezes for about 2-3 secs and then im able to scroll or keep using the app ...is this something I can configure or is the default behaviour? Thanks in advance
Click to expand...
Click to collapse
I'm on nameless and found this exact behavior as well
 
efx7n

efx7n

Senior Member
Jun 18, 2016
941
310
IMG_20230208_075336_368.jpg


Is there a feature to block application internet access in the rom? or can you add this? Ty so much very nice rom
 
I

iplop

Member
Jul 23, 2018
8
1
Hi everyone. I'm using version 230205.002-02070839 on OnePlus 8T. I can't use GPay anymore (it used to work in every other versions I tested). Error message is "your device doesn(t meet security requirements".
What can I do to be able to use Google Pay ?

Screenshot_20230208-084424_Yet_Another_SafetyNet_Attestation_Checker.png


Thanks in advance for your help !
 
Last edited:
AnierinB

AnierinB

Recognized Developer
Dec 7, 2015
1,517
4,904
25
United States
Evolution-X.org
Google Pixel 3 XL
OnePlus 8 Pro
iplop said:
Hi everyone. I'm using version 230205.002-02070839 on OnePlus 8T. I can't use GPay anymore (it used to work in every other versions I tested). Error message is "your device doesn(t meet security requirements".
What can I do to be able to use Google Pay ?

View attachment 5830719

Thanks in advance for your help !
Click to expand...
Click to collapse
It's a server side issue on googles end regarding CTS since this morning on multiple device, not just op8 series running customs.
 
  • Like
Reactions: cix18
AnierinB

AnierinB

Recognized Developer
Dec 7, 2015
1,517
4,904
25
United States
Evolution-X.org
Google Pixel 3 XL
OnePlus 8 Pro
BrickL0rd said:
always on still not always on.
Click to expand...
Click to collapse
This will be resolved on the next build for 8T & 9R. Please don't continuously report things and instead allow me time to address them. I'm working on 17 different devices and I can't get to everything all at once.

github.com

arm64: dts: 19805/20809/20828: Don't blank screen as part of LP1 cmd · Evolution-X-Devices/[email protected]

We send the LP1 command as part of entering Always-On Display mode, but we don't want that command to blank the screen. After all, the point of AoD mode is to keep the screen on to display the ...
github.com github.com

If you can't wait for the upcoming builds, then download the dtbo image attached in this comment, reboot to bootloader and flash it via the following cmd:

fastboot flash dtbo dtbo.img

Reboot and it will be fixed.
 

Attachments

  • dtbo.img
    24 MB · Views: 17
Last edited:
  • Like
Reactions: BrickL0rd, efx7n and YousifG7
Staff9643

Staff9643

New member
Feb 7, 2023
2
0
AnierinB said:
This will be resolved on the next build for 8T & 9R. Please don't continuously report things and instead allow me time to address them. I'm working on 17 different devices and I can't get to everything all at once.

github.com

arm64: dts: 19805/20809/20828: Don't blank screen as part of LP1 cmd · Evolution-X-Devices/[email protected]

We send the LP1 command as part of entering Always-On Display mode, but we don't want that command to blank the screen. After all, the point of AoD mode is to keep the screen on to display the ...
github.com github.com

If you can't wait for the upcoming builds, then download the dtbo image attached in this comment, reboot to bootloader and flash it via the following cmd:

fastboot flash dtbo dtbo.img

Reboot and it will be fixed.
Click to expand...
Click to collapse
Thank you! This solves the problem on 9R. When a new assembly is released, does this file interfere with the update?
 
I

iplop

Member
Jul 23, 2018
8
1
AnierinB said:
It's a server side issue on googles end regarding CTS since this morning on multiple device, not just op8 series running customs.
Click to expand...
Click to collapse
So even if I didn't upgrade, I would have the issue ?

scorpio76r said:
Don't hold your breath, I don't think that this was done by an error. Google does not really like us rooted people. They even have the magisk creater employeed by them.
Click to expand...
Click to collapse
I don't understand what changed that lead Google to flag my device. Maybe if I go back to a previous version ?
 
scorpio76r

scorpio76r

Senior Member
Jan 10, 2016
1,561
572
All over like street lights
iplop said:
So even if I didn't upgrade, I would have the issue ?


I don't understand what changed that lead Google to flag my device. Maybe if I go back to a previous version ?
Click to expand...
Click to collapse
Edit *
iplop said:
So even if I didn't upgrade, I would have the issue ?


I don't understand what changed that lead Google to flag my device. Maybe if I go back to a previous version ?
Click to expand...
Click to collapse
Are you running anything else besides the rom? I used the Pixify magisk module last week on my phone and, I thought all was good until I got banned from the Pennsylvania online lottery when I tried to make a purchase. I assumed that it was the module. I'm still on the rom build before the latest Feb build.
 
K

KrazyKlutt

Senior Member
Jul 30, 2014
153
28
AnierinB said:
This will be resolved on the next build for 8T & 9R. Please don't continuously report things and instead allow me time to address them. I'm working on 17 different devices and I can't get to everything all at once.

github.com

arm64: dts: 19805/20809/20828: Don't blank screen as part of LP1 cmd · Evolution-X-Devices/[email protected]

We send the LP1 command as part of entering Always-On Display mode, but we don't want that command to blank the screen. After all, the point of AoD mode is to keep the screen on to display the ...
github.com github.com

If you can't wait for the upcoming builds, then download the dtbo image attached in this comment, reboot to bootloader and flash it via the following cmd:

fastboot flash dtbo dtbo.img

Reboot and it will be fixed.
Click to expand...
Click to collapse
Thanks for the early fix, this works good.

The brightness flash in the recent build/builds is a shame, it's less jarring when disabling raise to wake when using AoD always on.
 
AnierinB

AnierinB

Recognized Developer
Dec 7, 2015
1,517
4,904
25
United States
Evolution-X.org
Google Pixel 3 XL
OnePlus 8 Pro
iplop said:
Hi everyone. I'm using version 230205.002-02070839 on OnePlus 8T. I can't use GPay anymore (it used to work in every other versions I tested). Error message is "your device doesn(t meet security requirements".
What can I do to be able to use Google Pay ?

View attachment 5830719

Thanks in advance for your help !
Click to expand...
Click to collapse

AnierinB said:
It's a server side issue on googles end regarding CTS since this morning on multiple device, not just op8 series running customs.
Click to expand...
Click to collapse

scorpio76r said:
Don't hold your breath, I don't think that this was done by an error. Google does not really like us rooted people. They even have the magisk creater employeed by them.
Click to expand...
Click to collapse

New builds are out which resolves issues with Google's new update to CTS. Enjoy
 
Last edited:
  • Like
Reactions: TheDevil259, Natakranta, scorpio76r and 2 others
B

bigbang09

New member
Aug 8, 2017
3
0
Hello everyone,
So I have a issue with my phone (oneplus 8pro IN 2023), it's freezing 1-3 times a day and after this I have to force restart my phone. I made clean flashing many times with EVOLUTION and after that I tried with different custom ROMS (LINEAGEOS AND CRDROID) to try fix this problem, but the problem is still there... I was thinking the problem was with my hardware issues, I flashed stock ROMS and I used it for a week with no problems.
Does anyone has any idea why it's happening and how to fix it because i tried so many times asking different people in chats but none of them told me any solution about it and I hope I will find answer here
 
You must log in or register to reply here.

Similar threads

AnierinB
  • Locked
[CLOSED][ROM][12.1_r22][EOL][OFFICIAL] Evolution X 6.7 [08/14/2022]
Replies
3K
Views
298K
shadowstep
shadowstep
1249131356
[ROM][11.0] Havoc-OS 4.2 [OFFICIAL] [2021-02-24]
Replies
279
Views
62K
vacs03
vacs03
deepongi
[TWRP][3.7.0-13][instantnoodle]TWRP for OnePlus 8/8Pro ][OFFICIAL][BETA 3]
Replies
1K
Views
141K
M
Marcyvee
xXx
[Magisk ROM] xXx NoLimits 12.4 [OP8/OP8pro] ☆ Speed/RAM optimized ☆ [OOS/H2OS v10/11]
Replies
1K
Views
267K
rodken
rodken
FoxyDrew
[ROM][12.0] Evolution X [1/11/2022][UNOFFICIAL]
Replies
238
Views
33K
E
ewong3

Top Liked Posts

24 Hours 30 Days All time
  • 1
    A
    Agimax
    mchalakov2 said:
    Can someone confirm if the random shut down is fixed in the latest update?
    Click to expand...
    Click to collapse
    After running 7.9.2 update all week, no more black screens or reboots so far :)

    @AnierinB this version seems very stable, fluid and responsive - much appreciation
    View
  • 2
    N
    Nords99
    M_Power01 said:
    Same thing happened to me using Waze with Evo 7.8 last week.
    I haven't had this problem yet with version 7.9.
    Click to expand...
    Click to collapse
    I also haven't had this since updating to 7.9, which is typically longer than I went prior to updating before having the issues. I'll keep a lookout for this, but based on what I can see it seems like 7.9 may have fixed the issue! Awesome and thank you Anierin!
    View
    2
    A
    Agimax
    M_Power01 said:
    As I said above, I had this problem with EvoX 7.8.
    I tried the latest build of LineageOS 20 for a few days and surprise .... yesterday my OnePlus 8T shut down the same way.

    I wonder if it could be a battery issue?

    Since last night, my OnePlus 8T has been running on EvoX 7.9
    No problem but it's too early to see if it will turn off again..
    Click to expand...
    Click to collapse
    Unfortunately, I have this same issue to,o found my phone off twice sitting by itself now (v7.9). If this happened to you on Lineage, must be something in the shared code. Unfortunately i'm rooted (no modules) so can't blame rom. Wonder, are you also rooted?
    View
    2
    N
    Nords99
    Baron1971 said:
    Is ist possible to reset the QR-Code-Scanner Settings to get it work again?
    Click to expand...
    Click to collapse
    I cannot say for sure what's causing your problem, I never had problems with the QR code scanner, but when I open it up, it seems that the quick settings QR code scanner is part of the "Google Play services" app. I'd make sure that that's updated for you - mine is currently on version 23.17.15 (190400-534251769) (231715044). Alternatively, you could fiddle around with things in app info, such as if you go to app info > top right 3 dots button > uninstall updates, then reinstall to see if that fixes your issue or clearing the cache/storage. Or maybe just updating to the latest would fix it :) Good luck!
    View
    1
    arslanejaz33
    arslanejaz33
    ChitralVerma said:
    were you able to find a fix for this netflix issue?
    Click to expand...
    Click to collapse
    unfortunately no , i tried various methods that my L1 certification will remain intact and certain ID number should be 5 digits but it always show 8 digits so i stopped trying. not worth the effort
    View
    1
    A
    Agimax
    mchalakov2 said:
    Can someone confirm if the random shut down is fixed in the latest update?
    Click to expand...
    Click to collapse
    After running 7.9.2 update all week, no more black screens or reboots so far :)

    @AnierinB this version seems very stable, fluid and responsive - much appreciation
    View
  • 67
    AnierinB
    AnierinB
    Evolution X 7.9.2 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

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

    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.63 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.63 for 8T & F.22 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)​

    View
    24
    AnierinB
    AnierinB
    rom:

    recovery:

    vbmeta:

    rom:

    recovery:

    vbmeta:

    rom:

    recovery:

    vbmeta:

    copy_partitions:

    rom:

    recovery:

    vbmeta:

    copy_partitions:
    View
    17
    AnierinB
    AnierinB
    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
    View
    13
    AnierinB
    AnierinB
    enjoy_life said:
    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.
    Click to expand...
    Click to collapse
    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".
    View
    12
    AnierinB
    AnierinB
    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?

    Use the official Google USB driver

    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?
    Set up udev rules

    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.
    8 (instantnoodle)
    8 Pro (instantnoodlep)
    8T (kebab)
    9R (lemonades)

    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!
    View

New posts