• We are moving to xdaforums.com!

    Posts made between now and when the migration is complete will not be carried over.
    You will be automatically redirected once the migration is complete.

Development [ROM][13.0_r82][OFFICIAL] Evolution X 7.9.8 [09/19/2023]

Search This thread

kodabmx

Senior Member
Dec 28, 2010
167
44
Toronto
Google Pixel 7 Pro
Ok. So after a few years of running Samsung phones with stock ROM (didn't want to blow the e-fuse and F*** knox), I smashed it (fold 3) into many pieces because it pissed me off one final time.

Now I'm using a Pixel 7 Pro.
With the stock ROM, I had several apps that just didn't work. Smart Life would take 2 minutes to load if it ever did, SofaBaton app for a remote would only load on the first run, then you had to wipe the cache and data for the app to get it to work again.
Chromecast didn't work on the stock ROM while trying to pair with a Nvidia Shield Pro.
This and many other little quirks were bothering me so I installed this ROM.
All those things work now. Battery life was kinda crap until I found out that this ROM keeps the data connection alive while using WI-FI by default. Turned it off in Dev settings, and now the ROM has great battery life.
I even got Magisk and LSPosed installed with working Google Pay and banking apps.
I'm not using WI-FI calling (what the hell for? I live in a city with excellent cell coverage) so I couldn't tell you if that works.
I particularly like the slider control for animations in dev settings. 0.1x scaling makes the phone fast without totally getting rid of the anims.
OH and the damned fingerprint scanner actually WORKS with this ROM.
With the stock ROM, I found myself having to lick my finger and wipe it off before it would recognize it.

ADB is kind of a pain in the butt sometimes (it'll take a few minutes after booting to "see" the device using a USB cable, but wireless ADB works right away if you want to screw with pairing codes.

I flashed it using Manjaro GNOME (Linux).

A question for the devs: Will there be support for video over the USB connection or is that a HW limitation?
 
Last edited:
  • Like
Reactions: Shihabus Sakib Rad

vkass

Senior Member
Jan 8, 2011
600
195
OnePlus 6
Ok. So after a few years of running Samsung phones with stock ROM (didn't want to blow the e-fuse and F*** knox), I smashed it (fold 3) into many pieces because it pissed me off one final time.

Now I'm using a Pixel 7 Pro.
With the stock ROM, I had several apps that just didn't work. Smart Life would take 2 minutes to load if it ever did, SofaBaton app for a remote would only load on the first run, then you had to wipe the cache and data for the app to get it to work again.
Chromecast didn't work on the stock ROM while trying to pair with a Nvidia Shield Pro.
This and many other little quirks were bothering me so I installed this ROM.
All those things work now. Battery life was kinda crap until I found out that this ROM keeps the data connection alive while using WI-FI by default. Turned it off in Dev settings, and now the ROM has great battery life.
I even got Magisk and LSPosed installed with working Google Pay and banking apps.
I'm not using WI-FI calling (what the hell for? I live in a city with excellent cell coverage) so I couldn't tell you if that works.
I particularly like the slider control for animations in dev settings. 0.1x scaling makes the phone fast without totally getting rid of the anims.
OH and the damned fingerprint scanner actually WORKS with this ROM.
With the stock ROM, I found myself having to lick my finger and wipe it off before it would recognize it.

ADB is kind of a pain in the butt sometimes (it'll take a few minutes after booting to "see" the device using a USB cable, but wireless ADB works right away if you want to screw with pairing codes.

I flashed it using Manjaro GNOME (Linux).

A question for the devs: Will there be support for video over the USB connection or is that a HW limitation?
Adb shell
settings put global window_animation_scale 0.1
settings put global transition_animation_scale 0.1
settings put global animator_duration_scale 0.1
 
  • Like
Reactions: kodabmx

MultiCulti

Senior Member
Not a bug, intended behavior.
hoi, i just tried on other phone again to be sure 😅

on stock and also with different pixel launcher it is like this if i turn off (pause) the workspace!

Screenshot_20230203-075200_Lawnchair.png

So there no apps visible!
 

AnierinB

Recognized Developer
hoi, i just tried on other phone again to be sure 😅

on stock and also with different pixel launcher it is like this if i turn off (pause) the workspace!

View attachment 5826627

So there no apps visible!
Keywords:
> Stock
> Pixel launcher

Evo:
> Not stock
> Doesn't use pixel launcher
> intended behavior

Not quite sure the point you're trying to make, they're different launchers and ROMs. Saying something is a bug just because it behaves slightly different yet retains the same underlying functionality is inaccurate.
 
Last edited:

wgrant

Senior Member
Sep 23, 2011
1,547
522
I'm trying to install the rom but still at 0% after 10 minutes, how can I stop the process? Thanks
I had the same issue over and over again. Eventually it worked but I think it was just luck. I flashed stock January to both slots, wiping data then followed instructions for this ROM till it worked. If it got stuck (usually at 6%) I would cancel the side load command, reboot my phone to recovery, wipe again then attempt install.
 

Bestiole222

Senior Member
Aug 24, 2016
62
24
I had the same issue over and over again. Eventually it worked but I think it was just luck. I flashed stock January to both slots, wiping data then followed instructions for this ROM till it worked. If it got stuck (usually at 6%) I would cancel the side load command, reboot my phone to recovery, wipe again then attempt install.
I can't remember how to stop the adb command line so I do a alt+F4, the second time the installation was ok but I did a dirty flash coming from unofficial evo, and this brought me to bootloop. So I had to stop the phone, went back to recovery and wipe data. After that the phone booted, but I had to install all my app again.
 

t-ryder

Senior Member
Feb 23, 2011
1,533
1,224
www.t-ryder.de
Google Pixel 6
Thanks for the ROM.

Bug description: when using a shortcut (nova launcher widget or 3rd party app to lock / via the accessibility + device admin functions) to lock the device (which is IMO the most elegant and convenient way to do so) the screen does not turn off, it first shows the lockscreen for a second and then turns off. Feels like some annoying flickering every time locking. Other ROMs (Graphene OS, Statix OS, Stock ROM) don't do this.

How to reproduce: use shortcut to lock screen of Pixel 7

Logcat: s.a.

Screenshots: not needed

.:.

EDIT: to get rid of the effect I activated the old school CRT-off animation
 

Attachments

  • 2023-02-05_01.02.zip
    3.9 KB · Views: 19
Last edited:

t-ryder

Senior Member
Feb 23, 2011
1,533
1,224
www.t-ryder.de
Google Pixel 6
I had the same issue over and over again. Eventually it worked but I think it was just luck. I flashed stock January to both slots, wiping data then followed instructions for this ROM till it worked. If it got stuck (usually at 6%) I would cancel the side load command, reboot my phone to recovery, wipe again then attempt install.
Do you guys flash using a proper data cable? Some time ago I was using a not that good cable for sideloading ROMs on my Pixel 6 and it got stuck again and again until I used the original cable. By now I got me a high quality pretty long cable and all works. Seems like the newer Pixels in combination with some USB hubs/controllers don't like every cable.
 
  • Like
Reactions: Lughnasadh

AnierinB

Recognized Developer
Thanks for the ROM.

Bug description: when using a shortcut (nova launcher widget or 3rd party app to lock / via the accessibility + device admin functions) to lock the device (which is IMO the most elegant and convenient way to do so) the screen does not turn off, it first shows the lockscreen for a second and then turns off. Feels like some annoying flickering every time locking. Other ROMs (Graphene OS, Statix OS, Stock ROM) don't do this.

How to reproduce: use shortcut to lock screen of Pixel 7

Logcat: s.a.

Screenshots: not needed

I'll look into this. Thanks for following post #3 by providing logs and an accurate description of the issue.
 
Last edited:

Bestiole222

Senior Member
Aug 24, 2016
62
24
Do you guys flash using a proper data cable? Some time ago I was using a not that good cable for sideloading ROMs on my Pixel 6 and it got stuck again and again until I used the original cable. By now I got me a high quality pretty long cable and all works. Seems like the newer Pixels in combination with some USB hubs/controllers don't like every cable.
Yes I use the original cable, I install unofficial and official evol with sideload command, and I had to do the install twice for the two roms. Don't know why.
 

manban10

Member
Nov 9, 2015
36
9
Thank you for the rom. It's so smooth and everything just works. Battery life has been great, better than the stock rom. I haven't had any issues so far and it's been a week. I will update if I find anything wrong.
 

Crazyiain

Member
May 16, 2019
14
1
Amazing ROM running perfect on my pixel 7 pro thank you to everyone.

Any help i followed the steps to patch the .img boot for magisk everything installed but magisk is still showing installed N/A
Do I need to download the original firmware boot?.

Cheers
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I'm form Mexico, and thanks so much in advance if you are able to give it a try.
    Those 2 apps are the only reason why i prefer to run rootless but honestly i wish i could root and so that way i can have the volte magisk module for the Pixel always there instead of having to use shizuku and PIxelIMS.
    The apps almost intermediately crash when open, just sometimes you are able to see the logo for a split second.
    Good news, possibly. I had to download the apk's from 3rd party websites as Gplaystore kept saying not compatible even though I used a VPN to Mexico. So, the Hey banco app was a bit outdated, but the CFE was current. Both apps, after hidng in Magisk Alpha, load fine. Whether they'll continue to function beyond the login pages is anyones guess. But they both open at least.
    Here's my MEGA folder with the files you'll need - Latest Magisk alpha, USNF and Shamiko modules. See screenshots, which I'll upload in a bit, for how I'm configured etc... Plus, obviously, magisk hide (both app and installed apps) Good luck.

    BTW, I used a vpn on mobile before opening apps

    After hiding Google Play stuff as per screenshot, you might wanna clear cache and data of those items
    2
    Good news, possibly. I had to download the apk's from 3rd party websites as Gplaystore kept saying not compatible even though I used a VPN to Mexico. So, the Hey banco app was a bit outdated, but the CFE was current. Both apps, after hidng in Magisk Alpha, load fine. Whether they'll continue to function beyond the login pages is anyones guess. But they both open at least.
    Here's my MEGA folder with the files you'll need - Latest Magisk alpha, USNF and Shamiko modules. See screenshots, which I'll upload in a bit, for how I'm configured etc... Plus, obviously, magisk hide (both app and installed apps) Good luck.

    BTW, I used a vpn on mobile before opening apps

    After hiding Google Play stuff as per screenshot, you might wanna clear cache and data of those items
    Wow I did try with shamiko and hiding the app but it didn't work.
    I remember it used to work before but they updated the apps at some point and then I couldn't find any workaround.
    Thanks for testing all this, you didn't have to do it but you did, I'm gonna give it a try now :)

    EDIT: Its working! you are legend, thanks again
    2
    i think i break my device i followed your instructions for cheetah and then rebooted my device by mistake without installing the rom and now there's an infinite loopboot and cant access fastboot nor recovery :C
    Sounds like a you problem. Can't say you followed the instructions when you literally just said you accidentally did X. Pass

    I second this, the Pixel 7a version has the 90hz slider missing. Any ideas?

    Also, the OTA section is missing for the Pixel 7a as well. Other that that it works great 👍
    90hz will be fixed on the next release. You can access it via QS for the time being. And the OTA updater has been intentionally removed for preparation for A14. Not a bug.
    2
    I'm loving the sneaky Easter egg, keep tapping build number after unlocking dev options. Good laugh.
    Screenshot_20230927-105526_Settings.png
    2
    I didn't want to mess with kernel installation etc. since I am not a techie person. I mostly work from home and on WIFI so my battery drain is minimal. Could you link me up? At least I can take a look. Thnx

    I am actually enjoying the rooted Evox ROM. I had always had rooted Note 4 thru N20. Switched to Pixel only because of ability to root.
    Ok dude... 1st thing you need to check is whether verity and verification are disabled. Now, most roms require you do this at 1st clean flash but for me, using EvoX, it seems it's disabled from the start automatically because I can't recall disabling myself at 1st flash.




    So, if you want to check whether verity and verification is disabled for you...
    1. flash this module (avbctl-module-android-13.0.0_r11-panther.zip) in magisk. Have you flashed modules, are you familiar? I'll assume you are.
    2. Download a terminal emulator from playstore... such as this one
    3. Open [Material Terminal] and type 'su' + enter/return and grant su rights when prompted by magisk. That'll give you root access.
    4. Run 2 CMDs once root has been granted... 'avbctl get-verity' (+enter), followed by 'avbctl get-verification'.
    Both should be disabled in order to flash some kernels. Doing the above CMDs doesn't change anything, it just checks the current status.

    Providing both are disabled, you can go ahead and flash a kernel, such as Kiri or Radioactive

    Currently I'm using Kernel flasher to backup existing kernel and flash new.
    Install the app, backup existing kernel (tap 'view' on active slot, tap 'backup' and check all img options, tap 'backup')
    Go back to active slot and tap 'flash', then 'Flash AK3 Zip' and navigate to your downloaded RadioactiveKernel_PANTAH_v1.1.2.zip (ASSUMING YOU ARE RUNNING LATEST EvoX ROM VERSION - AUGUST BUILD). Then tap 'flash' and reboot. That's it.




    I know that's a lot of instruction for some fairly simple steps, but I wanted to be clear as poss. Good luck if you do decide to go ahead and enjoy.

    When updating via OTA (or flashing updates) it'll overwrite your custom kernel, so you'll need to check verity/verification again and reflash the corresponding kernel version - ie If you update to Sept build of EvoX, wait for kernel release and then flash Sept build of custom kernel. Don't flash a newer kernel on an older rom or you may have issues (I think, iirc)
  • 75
    Evolution X 7.9.8 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


    First Time Install
    1. Download boot, dtbo, vendor_kernel_boot, vendor_boot & rom for your device from here
    2. Reboot to bootloader
    3. fastboot flash boot boot.img
    fastboot flash dtbo dtbo.img
    fastboot flash vendor_kernel_boot vendor_kernel_boot.img
    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 (fully) 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

    39
    Latest downloads
    P7.png




    23
    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.img" 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.