Related
QuickSwitch - Quickstep enabler for supported launchers
QuickSwitch is a Magisk module which systemlessly allows supported launchers to access the recents (QuickStep) APIs. It's future proof, detects which launchers are capable of being a recents provider, and is fairly simple to use.
Requirements:
- Android Pie+
- The latest version of Magisk
- A launcher which can be used as a recents provider on your specific android version.
Installation:
To use the module, simply follow the instructions:
1. Install the latest QuickSwitch apk from the Telegram channel or GitHub releases.
2. Open the QuickSwitch app that was installed.
3. Select a different launcher as your recents provider.
4. Reboot.
5. Verify your new recents provider is correct.
6. Set the new recents provider as the default launcher.
7. Profit.
After switching providers and rebooting, make sure the current provider is the default home app.
To switch providers after the initial install just open the app, select a new provider and reboot.
Updating:
To update, just update the app when a new release is published, or check the Magisk app as it should fetch updates too.
Uninstallation:
To uninstall the module, use the bin icon in magisk manager. Your recents provider will go back to default and your launcher will return to being a user app, after that, just uninstall the quickswitch app
Logging:
QuickSwitch saves all its logs to /data/adb/modules/quickswitch/logs/ and /sdcard/Documents/quickswitch/ all logs belonging to QuickSwitch begin with quickswitch. If you have any issues with the module send all log files in a compressed archive.
Compatibility:
As stated earlier, the QuickSwitch app auto-detects which launchers are compatible so it's going to be difficult to say a definitive list. But for an easy explanation, I'll just say that almost all stock Pie+ launchers will work as long as they are either ported to other devices or are installed by default on your device.
As for custom launchers, you'll have to install them and see if they appear in the QuickSwitch app.
Notes:
- QuickSwitch doesn't add support for launchers, launchers need to support QuickSwitch. Because of this, a full list of compatible launchers will not be provided as the app autodetects which launchers are compatible.
- Nova Launcher is NOT compatible with QuickSwitch and never will be unless they decide to add support for the Razer Phone natively.
Misc:
- You can grab the source for the module here
The SystemUI option (removed in Android 10+) will grant you Oreo style recents.
Credits:
- @paphonb for the QuickSwitch app and the initial concept and idea of a universal Quickstep enabler.
- @osm0sis for assistance with getting 3.x.x to work without having to go permissive, and for his and @topjohnwu's zipsigner
- The Lawnchair and Hyperion team's for initial testing of the module.
Download:
Download the latest version here.
Donations:
- If you wish to donate to @paphonb for creating the QuickSwitch app you can do so here.
- Or if you wish to sponsor me on GitHub for making the module, scripts, and handling support you can do so here.
Release details:
Current version: 3.3.1
Last updated: 19-06-2022
Created: 28-12-2018
FAQ
What does this module do?
The only thing this module does is changes which launcher controls your recents
Can I get app actions, or recents text/picture selection with this module?
This module doesn't control what features a launcher has. All it does is grant the launcher more permissions and enable a launchers access to recents.
How to get Oreo/Oreo Grid recents?
For Oreo recents simply set your recents provider to SystemUI and reboot.
If the SystemUI option doesn't show up it's because you're on Android 10 and the Oreo recents fallback has been removed from AOSP.
For grid recents follow these instructions:
1. Set the recents provider to SystemUI
2. Tap the three dot menu and toggle "Enable grid recents" to on
3. Reboot.
The FAQ will grow as more questions come to mind.
Common Issues & How To Fix
Launcher is constantly crashing
This generally means you are using a launcher port and didn't follow the instructions correctly. Here is a refresher:
1. Install QuickSwitch.
2. Install the launcher, don't set it as your default launcher.
3. With any other launcher, open QuickSwitch.
4. Set your desired launcher as your recents provider.
5. Reboot.
6. Verify the new launcher is now your recents provider in QuickSwitch.
7. Set the selected as your default launcher.
8. Profit.
If the launcher still crashes afterward get the module logs and a crash log using https://github.com/tacothedank/scoop
Setting the provider is successful but it still didn't work after a reboot
type this command in a terminal
Code:
su -c cmd overlay dump xyz.paphonb.quickswitch.overlay
If you see this line:
Code:
mState.................: STATE_NO_IDMAP
You need to ask your rom maintainer to add this commit. only for your device, it will cause issues on other devices.
Another fix you can do yourself if that happens is enter this command in a root environment (If stuffs breaks after doing this delete the .replace file through ADB).
Code:
mkdir -p /data/adb/modules/quickswitch/system/vendor/overlay && touch /data/adb/modules/quickswitch/system/vendor/overlay/.replace
Great!
Works well on this setup:
OnePlus 6
Pixel Experience ROM
Lawnchair Alpha 721
Quickstep 1.0.6
Just one issue that I've had before. I use Fluid NG to get access to navigation gestures on Pixel software. It removes the navbar by moving it to the invisible area "under" your display or something. In HTML world, this would have to do with margins and padding.
The result is this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With the navbar on, it looks alright:
Is it possible for you to fix this or provide an option to do so? Maybe by doing a reverse-padding for the app previews or something like that? ? I'll be happy to assist further.
schwarzerfleck said:
Great!
Works well on this setup:
OnePlus 6
Pixel Experience ROM
Lawnchair Alpha 721
Quickstep 1.0.6
Just one issue that I've had before. I use Fluid NG to get access to navigation gestures on Pixel software. It removes the navbar by moving it to the invisible area "under" your display or something. In HTML world, this would have to do with margins and padding.
The result is this:
With the navbar on, it looks alright:
Is it possible for you to fix this or provide an option to do so? Maybe by doing a reverse-padding for the app previews or something like that? ? I'll be happy to assist further.
Click to expand...
Click to collapse
Yea that's a lawnchair issue. We are aware of it and it will be worked on in a later update.
Sent from my LGE Nexus 5X using XDA Labs
Nice:laugh: working great on (oneplus 6t - oos 9.0.10), o used horizontal old style and Lawnchair and booth of them works great,
Thanks a lot..
I hope someone support the (grid recent) soon
Skittles9823 said:
Yea that's a lawnchair issue. We are aware of it and it will be worked on in a later update.
Click to expand...
Click to collapse
Thanks a lot for the heads-up. Enjoy your holidays!
Qutayba Khader said:
Nice:laugh: working great on (oneplus 6t - oos 9.0.10), o used horizontal old style and Lawnchair and booth of them works great,
Thanks a lot..
I hope someone support the (grid recent) soon
Click to expand...
Click to collapse
Grid recents might still be able to be enabled via a build.prop value but I'm not sure.
Sent from my LGE Nexus 5X using XDA Labs
I tried flashing quickstep through magisk and twrp and got a failed to install error. I'm on stock pie.
Gordietm said:
I tried flashing quickstep through magisk and twrp and got a failed to install error. I'm on stock pie.
Click to expand...
Click to collapse
Would you mind sending a recovery log so I could see the error?
Sent from my LGE Nexus 5X using XDA Labs
Skittles9823 said:
Would you mind sending a recovery log so I could see the error?
Click to expand...
Click to collapse
I'm sorry, but how do I get a recovery log?
Gordietm said:
I'm sorry, but how do I get a recovery log?
Click to expand...
Click to collapse
I found it:
Love this! Thank you for this awesome mod. Anyway to add a clear all button in the bottom right or bottom center? Thank you so much again for this development
stu5797 said:
Love this! Thank you for this awesome mod. Anyway to add a clear all button in the bottom right or bottom center? Thank you so much again for this development
Click to expand...
Click to collapse
All UI for Pie recents is launcher side.
Sent from my LGE Nexus 5X using XDA Labs
Gordietm said:
I found it:
Click to expand...
Click to collapse
Thanks will look over this in a day or two once I'm sober lol.
Sent from my LGE Nexus 5X using XDA Labs
Gordietm said:
I found it:
Click to expand...
Click to collapse
I don't see anything about a failed installation in there. You need to save the log right after the incident you want to report about...
More info on reporting bugs and different logs:
https://www.didgeridoohan.com/magisk/MagiskHelp
Updated to 1.0.7 and fixed the uninstallation of Lawnstep. (Kinda forgot the file was named "replace" and not ".replace".)
Sent from my LGE Nexus 5X using XDA Labs
Skittles9823 said:
Updated to 1.0.7 and fixed the uninstallation of Lawnstep. (Kinda forgot the file was named "replace" and not ".replace".)
Click to expand...
Click to collapse
Still get install failed, invalid zip.
I did the log right afterwards.
Gordietm said:
Still get install failed, invalid zip.
I did the log right afterwards.
Click to expand...
Click to collapse
That's weird. The zips I post are the zips magisk gives me when I use the download option. It should definitely work in recovery.
Sent from my LGE Nexus 5X using XDA Labs
Skittles9823 said:
That's weird. The zips I post are the zips magisk gives me when I use the download option. It should definitely work in recovery.
Click to expand...
Click to collapse
I tried 1.0.7 in magisk and in recovery and both ways it was a no go.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME TO THE FLUENCE FUHD PATCH
MODULE DESCRIPTION
Work in Progress / BETA. Android System Optimization Patch for non GSI/QSSI Snapdragons. Enables various Features and Functions on Hardware and Software Level. Also adding exclusive System Content like LWPs, UI Sounds and init.d Scripts.
MODULE DEPENDENCIES
Snapdragon SoC from 2017 or newer (ARM64). Android 9.0+ / SDK Level 28+ (Non GSI/QSSI).
Busybox for Magisk. Pix3lfy for Magisk For non Pixel Devices. Quickswitch for grid Recents.
INCLUDED FEATURES
* FULLY SYSTEMLESS ROM/PATCH MODULE
* FULLY BLACK/WHITE THEMED AROMA INSTALLER
* FULLY BLACK/WHITE THEMED AROMA FILEMANAGER
* BASED ON LATEST UNITY/MAGISK MODULE TEMPLATES
* BATTERY CALIBRATION AFTER CHARGING
* FILESYSTEM TRIMMING BASED ON TIMERS
* SYSTEM WIDE NETWORK OPTIMIZATIONS
* SQLITE3 DATABASE OPTIMIZATIONS
* INTELLIGENT ZIPALIGNMENT
* MADE AND TESTED WITH/FOR PIXEL DEVICES
* ALL DEVICE CONFIGS ARE AIMING ON QUALITY
* ALL RELEASES AND CHANGES ARE TESTED AND WORKING FINE
* INCLUDING CUSTOM UI SOUNDS AND LIVE WALLPAPERS
* ENABLES LATEST PIXEL FEATURES
* ENABLES VOLTE / VOWIFI + VIDEO CALLING
* ENABLES HIGH QUALITY AUDIO PLAYBACK
* ENABLES 4K HDR VIDEO PLAYBACK
* ENABLES MANY HIDDEN ANDROID FUNCTIONS
* ENABLES MANY HIDDEN ANDROID SERVICES
* ENABLES SMOOTHER AND MORE FLUID RENDERING
* ENABLES DISPLAY ROTATION FOR THE WHOLE OS
* ENABLES SETUP WIZARD EXTRA FUNCTIONS (WIP)
* ENABLES "ANDROID FOR WORK / ENTERPRISE" FEATURES
* ADVANCED AUDIO RECORDING SERVICES / FEATURES
* ADVANCED NETWORK SERVICES / FEATURES
* ADVANCED APP FUNCTIONALITY / FEATURES
* ADVANCED GRID RECENTS WITH MULTI/SPLIT SUPPORT
* BETTER OVERALL PERFORMANCE (UI, APPS, GAMES...)
* EXTRA DISPLAY TECH CONFIGS FOR SUPPORTED DEVICES
* DEFAULT DPI IS 480 FOR 1440P+ DISPLAYS (PIXEL, HTC, SONY ETC.)
* MUCH MORE AND MADE WITH <3
XDA:DevDB Information
FLUENCE FUHD, Tool/Utility for the XDA Community Apps
Contributors
Miustone, Miustone, Miustone, Miustone
Source Code: https://github.com/Miustone/FFUHD
Version Information
Status: Beta
Current Beta Version: 2
Beta Release Date: 2019-03-25
Created 2019-03-24
Last Updated 2019-03-25
SOURCES:
Download and Repack from:
https://github.com/Miustone/FFUHD
(LINK)
OR
Download and just flash from:
https://sites.google.com/view/miustone/RELEASES
(LINK)
(Note that GitHub Versions may be unstable, faulty or misleading)
Instructions
New Install
Download and/or repack the Patch from one of the Sources
Boot and Setup Your Device and install Magisk
Reboot to TWRP and flash the Patch (You can't use Magisk to install)
Start the AROMA Installer and do the Install of the Patch
Install other Modules if needed (Busybox and Pix3lfy)
Reboot to System and Enjoy
Updating the Module:
Start the installer and do the Install to uninstall the Module
After the uninstall choose to go back to the main menu of the Patch
Do the Install again to flash the new Patch
Reboot to System and Enjoy
PLEASE DO NOT UPDATE WITH BETA RELEASES SINCE IT MAY CAUSE CONFLICTS
Fluid Navigation
Before You start browsing thru the System do this...
Open the Fluid Navigation Gestures App from the Home Launcher
Allow Root Rights to the App
Press on activate (The Toggle)
Give Permissions and go back to the OS Settings
(The App doesn't works yet. Workaround Time!)
Open the "Apps and Notifications" Option in the OS Settings
Tap on Google Chrome, Expand the Settings and scroll down
Open the App in the Play Store over "App-Details"
Go to Your Apps and Games and Open the FNG App again
Now You can activate the Service over the Toggle
(Optional) Restore My Settings for the App from here:
https://drive.google.com/file/d/1pnkU5UefbA91ZBUe3AOd45mvm0Hg3kRA/view?usp=sharing
You can save it on Your Google Drive too, to restore it from anywhere You are...
If You don't use My Backup: Make sure You disable "Navigationbar hider" within the App.
..
Beta 1 Release uploaded and ready for download! Enjoy
@Miustone thanks for this mod. Do I need Pix3lfy for the best experience, or can I run without it?
Also, is it OK to run this with other tweaks/scripts I may already have installed?
Portrait mode crashes the camera app.
Maverick Jester said:
@Miustone thanks for this mod. Do I need Pix3lfy for the best experience, or can I run without it?
Also, is it OK to run this with other tweaks/scripts I may already have installed?
Click to expand...
Click to collapse
I wouldn't call it a mod since it's something more than that. But yes, you should install Pix3lfy if You are on a non Pixel Device and yes, you can install it together with Mods. Hope You like the Patch
dnp77 said:
Portrait mode crashes the camera app.
Click to expand...
Click to collapse
I will notice that somewhere. It's simply because of the Google Camera App that thinks that the Pixel 2 has 2 front Cameras for the Portrait Effect. The Media Profile Configs tells that there is only 1 which lets it crash. You are on a Pixel 2!?
I will take a look for a modded Camera Apk which works better / without Problems on our Devices. Any suggestions are welcome...
Beta 2 is uploading. First Release Candidate, but there are still things to solve... Don't wonder about the Size, there is a big Set of nice LWP / Wallpapers included
I really like the old AOSP Livewallpapers btw. i always removed them in the Past from the System but our Devices are so powerful and efficient nowadays that it don't hurts to have and run them. The Static wallpapers which you can access over the SONY Home Launcher are also pretty nice... Just saying
Aroma installer crashes the OnePlus 6t
Miustone said:
I wouldn't call it a mod since it's something more than that. But yes, you should install Pix3lfy if You are on a non Pixel Device and yes, you can install it together with Mods. Hope You like the Patch
I will notice that somewhere. It's simply because of the Google Camera App that thinks that the Pixel 2 has 2 front Cameras for the Portrait Effect. The Media Profile Configs tells that there is only 1 which lets it crash. You are on a Pixel 2!?
I will take a look for a modded Camera Apk which works better / without Problems on our Devices. Any suggestions are welcome...
Click to expand...
Click to collapse
My phone is the 2xl.
I have downloaded the beta 2. It did not show any configuration options in AROMA installer. Home button and back button are gone after installing the patch. I'm using Pixel 2 xl with stock rom and custom kernel. Thank you.
Same problem, I can't see option.
Now my Xiaomi can't boot.
How can i uninstall the patch ?
shadowikr said:
Aroma installer crashes the OnePlus 6t
Click to expand...
Click to collapse
Have other AROMA Installers ever worked on Your Device? Possible that TWRP is buggy on the 6T and needs to be fixed...
dnp77 said:
My phone is the 2xl.
Click to expand...
Click to collapse
Looks like we with the Pixel 2 Devices are the only ones facing this Problem. I'm on it
robertchiang said:
I have downloaded the beta 2. It did not show any configuration options in AROMA installer. Home button and back button are gone after installing the patch. I'm using Pixel 2 xl with stock rom and custom kernel. Thank you.
Click to expand...
Click to collapse
That because there are no Options yet. I'm working pretty hard on the System itself before i add Options. Stay tuned...
The Navbar is gone for Fluid Nav Gestures. Check it out, and sorry for the uncomfortable Start!
blamp1 said:
Same problem, I can't see option.
Now my Xiaomi can't boot.
How can i uninstall the patch ?
Click to expand...
Click to collapse
Which Xiaomi? Mi 5? Android 6 Miui?
Made some nice Progress over Night. Looks like i push another Release soon...
Which Xiaomi? Mi 5? Android 6 Miui?
Click to expand...
Click to collapse
sorry, it's MiMax 3 (nitrogen) with mi-globe rom (MIUI10 9.3.21)
Thanks for your help
Miustone said:
Have other AROMA Installers ever worked on Your Device? Possible that TWRP is buggy on the 6T and needs to be fixed...
Looks like we with the Pixel 2 Devices are the only ones facing this Problem. I'm on it
That because there are no Options yet. I'm working pretty hard on the System itself before i add Options. Stay tuned...
The Navbar is gone for Fluid Nav Gestures. Check it out, and sorry for the uncomfortable Start!
Which Xiaomi? Mi 5? Android 6 Miui?
Made some nice Progress over Night. Looks like i push another Release soon...
Click to expand...
Click to collapse
Thanks for the hard work, I'm waiting for your next release.:good:
blamp1 said:
sorry, it's MiMax 3 (nitrogen) with mi-globe rom (MIUI10 9.3.21)
Thanks for your help
Click to expand...
Click to collapse
Could You share the default build.prop from /system and /vendor with Me? You can additionally try to remove the system.prop from /common in the Patch Module and try if it will boot. I think there are conflicts over there...
robertchiang said:
Thanks for the hard work, I'm waiting for your next release.:good:
Click to expand...
Click to collapse
You're Welcome!
Miustone said:
Could You share the default build.prop from /system and /vendor with Me? You can additionally try to remove the system.prop from /common in the Patch Module and try if it will boot. I think there are conflicts over there...
Click to expand...
Click to collapse
I have no build.prop and no system.prop
After reinstall the rom, i have a build.prop (link)
I can't boot to the OS.
The rom boot but never finish
Miustone said:
Have other AROMA Installers ever worked on Your Device? Possible that TWRP is buggy on the 6T and needs to be fixed...
Looks like we with the Pixel 2 Devices are the only ones facing this Problem. I'm on it
That because there are no Options yet. I'm working pretty hard on the System itself before i add Options. Stay tuned...
The Navbar is gone for Fluid Nav Gestures. Check it out, and sorry for the uncomfortable Start!
Which Xiaomi? Mi 5? Android 6 Miui?
Made some nice Progress over Night. Looks like i push another Release soon...
Click to expand...
Click to collapse
No I tried to install aroma gapps but it never worked, there's a magisk ROM that is flashed thought twrp called xXx no limits hat uses a editable profile to install certain objects from the ROM possibly to go around the aroma installer
Download link for the the profile if you wanna see it
https://forum.xda-developers.com/devdb/project/dl/?id=31348&task=get
Can Havoc-OS or other AOSP/LineageOS based ROM use this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11:
Forces Google Sans font system wide
63Accent colors
12Icon shapes
22Fonts
Wallpapers Breel 2019; 2020 & 2020a
9 different Dark Styles
Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
Background Blur options
Blur Intensity options
Adaptive sound options
Navigation bar options (hide pill, reduce keyboard bottom space size, hide assist handles)
SystemUI Tuner options
Rounded corner options
QS Rows x Columns options
QS Footer Drag Handle options (Default, Accent based, Hidden)
Option to show more icon notifications on staus bar
Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide
Rom Control app (to setup all options available that you cannot using just Styles & Wallpapers)
Everything can be controlled using Styles & Wallpapers and also Rom Control app.
This MOD will probably work on any AOSP, or close to it, ROMs.
Get it here: Android_11_Addon_Features_for_Pixel_V8.zip
Just a note, this module already includes a SafetyNet fix, so if you're using another module for SafetyNet, please remove it since I don't know if that couldn't cause issues.
For all users already running Android 12 please go to THIS THREAD.
Addon Features EXCLUSIVE for Pixel Devices running on STOCK Android 11 ROM:
These exclusive and specific for Pixel Devices running on STOCK Android 11 ROM Magisk modules that you'll see next adds all of the features stated above but with extra goodies!
"Exclusive features" included:
Battery Bar
Battery Styles
Clock Customization
Corrected lock screen icons not changing after applying different theme
"Disco Dingo" the QS (just a funny name for the option to apply random colors on QS toggles)
Hide QS Labels
Lock screen album art customization
Lock screen camera shortcut (enable/disable)
Lock screen custom clock faces
Network Traffic Indicators (unfortunately, on redfin, it only works on QS Header and not on status bar)
QS Battery percentage independent options
QS Header opacity level control
QS Headers styles
QS Panel opacity level control
QS Tiles styles
QS Data usage info
QS Rows x Columns options (both on portrait and landscape modes)
Reduce Status bar height (and correct left padding on devices with the notch on the left)
Removed side assist handles from lock screen
Status bar Quick Pulldown (Never, Right pulldown, Left pulldown, Always)
Switch styles
Touch QS Labels to add or remove on QS customize panel (just didn't bothered to translate "Tap or Drag Tiles..." strings, so you'll continue to see "Drag Tiles..." but the feature is there, try it.)
Exclusive features downloads:
Android_11_Addon_Features_For_Pixel_V13.zip -> "Harmless" module that works on any Pixel device running on STOCK ROM, much like the "universal mod" shared above, but with a Rom Control app version that has more options. The "exclusive features" options won't do anything if the SystemUI module, shared next, isn't installed. If your going to try these exclusive features module, install this one and not the one shared above. The SaftetyNet is also included on this module, so once again, don't try to use any other SafetyNet module since it could break things.
Android_11_SystemUI_redfin_workaround_for_Addon_Features_V10.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI. Without this module the "exclusive features" won't work. Also, this module could be responsible for breaking boot if it fails to work at your end. I've ran several tests on my device (a Pixel 4a) and didn't face any issues but, since this module replaces stock SystemUI for a modded SystemUI, you could run into problems if some other module tries to do the same or it's simply incompatible with it. This module was updated to match latest Android 11 October 2021 build.
Android_11_SystemUI_redfin_workaround_for_Addon_Features_V9.zip -> Use this version ONLY if you're still running any Android 11 build between June and September 2021!
Notes regarding the "exclusive version" for Pixel devices:
DO NOT, I'll repeat, DO NOT flash "SystemUI module" zip on any other ROM besides stock. It won't work! If you want those extra features on your current ROM you will have to port them yourself. I explain how to later on this post.
Make sure that you're able to run adb shell as root before rebooting your device.
If something goes wrong after flashing "SystemUI module", like if your device doesn't boot or something stupid, connect your phone to your PC during boot and run this:
Code:
adb shell
Code:
su
Code:
rm -rf /data/adb/modules/Modded_SystemUI && reboot
If you forgot to enable the ability to run adb shell as root, and if your device is on a "non-boot" state, the only way you can fix that is to remove all Magisk modules you have installed. That can be achieved by running the following commands during boot:
Code:
adb shell
Code:
magisk --remove-modules
If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).
The "SystemUI module" requires that your device is already updated to March build!
When a new OTA update comes please don't flash the "SystemUI module" until I say it's ok to do so. I mean, me or any other member who may have tested it. Why? Because Google may change things on stock SystemUI between builds. When that happens, I have to recreate the module again to adapt those changes. For instance, March build was not compatible with the module that was built on top of February build SystemUI. Rest assured that I'll always test the module with new builds and update as necessary.
In case your device gets caught in a bootloop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:
Code:
adb logcat > log.txt
Requirements:
Unlocked bootloader
Magisk Root | Magisk Manager
Suggestion:
Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.
If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.
How to install? (If you're running a Pixel 5, just install the module...you don't need all these next steps)
Uninstall Device Personalization Services updates
Clear Google Play Store app data and cache
Flash the Magisk Module(s)
Reboot device
Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
Profit!
Video:
Check all Rom Control (with exclusive features) options HERE.
How's these "exclusive features" even possible?
All (well, not all but almost...) features that you see on Pixel Devices "SystemUI module" were reverse engineered from Evolution X ROM source code. The source code is available on the link bellow shown on the credits. This means that I've been practicing some hard core "old school" Android smali edition in order to get this working. So, yes, I have some credits about this but, if it weren't for the original developers and it's public source code, none of this would be possible. Thank them for this!
Smali, and xml, edition wasn't enough to get this working. After decompiling, changing/adapt the code and recompiling everything again, I had to find a way to make it bootable without messing with the original apk signature. And here is where VR Theme logic came in handy. So thanks for the original dev who brought us this feature.
As for ROM Control app....this was/is a project created by daxgirl and wubydax back in 2015! So yeah, I'm not bringing anything new here, I just followed their instructions in order to get the features working after editing smali/xml with the source code taken from Evolution X. The original app source code is also available on the link shared on the credits.
I've just combined all of the above into a Magisk Module and shared here so that we can get the best of both worlds....a stock ROM with custom features included.
Rom Control with "exclusive features" source code:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a
Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a/app/src/mods
Credits:
EvolutionX ROM team, specially @joeyhuab
@daxgirl and @Wuby986 for ROM Control project and source code.
@Tulsadiver for showing me how to adapt VR Theme logic originally used on 3Minit Battery Mod by @gharrington.
@Ticklefish for Tickle My Android
@topjohnwu for Magisk
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers and enjoy!
Is the first link down or is it just me?
Edit: nevermindnd it's working
shooterlgk said:
Is the first link down or is it just me?
Edit: nevermindnd it's working
Click to expand...
Click to collapse
How did you get it too work. It seems to be down for me.
Eudeferrer said:
How did you get it too work. It seems to be down for me.
Click to expand...
Click to collapse
Idk I guess I just clicked on it and it took me to browser but then I tried opening it thru app again and it worked
I am on stock march build and I flashed both zips but I can't get qs tiles to change, any ideas?
shooterlgk said:
I am on stock march build and I flashed both zips but I can't get qs tiles to change, any ideas?
Click to expand...
Click to collapse
Which zips did you flash? "V9" and "SystemUI"?
Typhus_ said:
Which zips did you flash? "V9" and "SystemUI"?
Click to expand...
Click to collapse
Is that correct?
shooterlgk said:
Is that correct?
Click to expand...
Click to collapse
I can't get the name of the 1st zip on that screen. Is it V8 or V9?
Typhus_ said:
I can't get the name of the 1st zip on that screen. Is it V8 or V9?
Click to expand...
Click to collapse
V9
shooterlgk said:
V9
Click to expand...
Click to collapse
Ok, and you've installed both modules with Magisk, correct? When you open Rom Control App and you choose your desired QS Tile nothing happens? Like you don't even see the icons disappearing on status bar and appearing again?
Typhus_ said:
Ok, and you've installed both modules with Magisk, correct? When you open Rom Control App and you choose your desired QS Tile nothing happens? Like you don't even see the icons disappearing on status bar and appearing again?
Click to expand...
Click to collapse
Correct. After I select the ones I want, it acts like it does switch them, but upon bring down the panel, it remains stock
shooterlgk said:
Correct. After I select the ones I want, it acts like it does switch them, but upon bring down the panel, it remains stock
Click to expand...
Click to collapse
Try to set the default. On Styles & Wallpapers set the default style as well. Afterwards try to change it again.
You could try as well to restart SystemUI to see if it applies the changes.
You can, as well, open terminal and run:
Code:
cmd overlay list | grep qstile
See if the checkbox is enabled on the qstile style you've chosen.
By the way, do you have any other modules installed?
Is that the only feature that isn't working?
Typhus_ said:
Try to set the default. On Styles & Wallpapers set the default style as well. Afterwards try to change it again.
You could try as well to restart SystemUI to see if it applies the changes.
You can, as well, open terminal and run:
Code:
cmd overlay list | grep qstile
See if the checkbox is enabled on the qstile style you've chosen.
By the way, do you have any other modules installed?
Is that the only feature that isn't working?
Click to expand...
Click to collapse
I'll try that right now. No it was a fresh install, and only installed those. So far that's the only thing I've tried
I have v8 installed and everything I've tested in rom control works. I have not tested v9. I will also like to say that there are some differences between the Pixel 5 SystemUIGoogle.apk and the other pixel devices. Pixel 3-4 have different lib files in them. However the res folder and smali folder are identical. I have not checked how your mod flashes (VR vs replacing entire apk), but if VR is used then there should be no issues on the Pixel 5. I was working on adding SystemUI mods to my mod, but this mod makes most of them useless, lol. And I don't like my mod to clash with this one as I'm using it as well. So I might either abandon the ideas in my end or if you allow, incorporate your changes to SystemUI to my mod so that users can use both of them.
eg1122 said:
I have v8 installed and everything I've tested in rom control works. I have not tested v9. I will also like to say that there are some differences between the Pixel 5 SystemUIGoogle.apk and the other pixel devices. Pixel 3-4 have different lib files in them. However the res folder and smali folder are identical. I have not checked how your mod flashes (VR vs replacing entire apk), but if VR is used then there should be no issues on the Pixel 5. I was working on adding SystemUI mods to my mod, but this mod makes most of them useless, lol. And I don't like my mod to clash with this one as I'm using it as well. So I might either abandon the ideas in my end or if you allow, incorporate your changes to SystemUI to my mod so that users can use both of them.
Click to expand...
Click to collapse
I've used VR Theme on SystemUI mod. Didn't touch any libs. The libs I've added are on both V8 and V9 Addon Features modules zip and they are only for SafetyNet fix.
I don't mind at all if you can merge your ideas into the module or create a new and better one. In fact, and as you may have noticed, I've shared everything I've changed on GitHub. The link is on the OP. If you know your way around smali you won't get any trouble on making it work.
Keep me posted. I've shared this exact same thread on all Pixel 3 and 4 models sub forum threads. If the changes you're thinking on adding works we could share everything for every Pixels.
Cheers!
Typhus_ said:
I've used VR Theme on SystemUI mod. Didn't touch any libs. The libs I've added are on both V8 and V9 Addon Features modules zip and they are only for SafetyNet fix.
I don't mind at all if you can merge your ideas into the module or create a new and better one. In fact, and as you may have noticed, I've shared everything I've changed on GitHub. The link is on the OP. If you know your way around smali you won't get any trouble on making it work.
Keep me posted. I've shared this exact same thread on all Pixel 3 and 4 models sub forum threads. If the changes you're thinking on adding works we could share everything for every Pixels.
Cheers!
Click to expand...
Click to collapse
Thanks man, I'll look into incorporating my edits into your mod. My edits mostly edit colors to give users control of icon, text, and background colors. I'll keep you posted.
eg1122 said:
Thanks man, I'll look into incorporating my edits into your mod. My edits mostly edit colors to give users over control of icon, text, and background colors. I'll keep you posted.
Click to expand...
Click to collapse
Sure. Go ahead then.
Typhus_ said:
Try to set the default. On Styles & Wallpapers set the default style as well. Afterwards try to change it again.
You could try as well to restart SystemUI to see if it applies the changes.
You can, as well, open terminal and run:
Code:
cmd overlay list | grep qstile
See if the checkbox is enabled on the qstile style you've chosen.
By the way, do you have any other modules installed?
Is that the only feature that isn't working?
Click to expand...
Click to collapse
shooterlgk said:
View attachment 5249141
Click to expand...
Click to collapse
The overlay is there and it's indeed activated. Are you absolutely sure you've got SystemUI module installed? Like, for instance, can you change the battery icon?
Typhus_ said:
The overlay is there and it's indeed activated. Are you absolutely sure you've got SystemUI module installed? Like, for instance, can you change the battery icon?
Click to expand...
Click to collapse
Sir I apologize, I had flashed it buT it was inactive. After activating it, it went to bootloop
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11:
Forces Google Sans font system wide
63 Accent colors
12 Icon shapes
22 Fonts
Wallpapers Breel 2019; 2020 & 2020a
9 different Dark Styles
Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
Background Blur options
Blur Intensity options
Adaptive sound options
Navigation bar options (hide pill, reduce keyboard bottom space size, hide assist handles)
SystemUI Tuner options
Rounded corner options
QS Rows x Columns options
QS Footer Drag Handle options (Default, Accent based, Hidden)
Option to show more icon notifications on staus bar
Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide
Rom Control app (to setup all options available that you cannot using just Styles & Wallpapers)
Everything can be controlled using Styles & Wallpapers and also Rom Control app.
This MOD will probably work on any AOSP, or close to it, ROMs.
Get it here: Android_11_Addon_Features_for_Pixel_V8.zip
Just a note, this module already includes a SafetyNet fix, so if you're using another module for SafetyNet, please remove it since I don't know if that couldn't cause issues.
For all users already running Android 12 please go to THIS THREAD.
Addon Features EXCLUSIVE for Pixel Devices running on STOCK Android 11 ROM:
These exclusive and specific for Pixel Devices running on STOCK Android 11 ROM Magisk modules that you'll see next adds all of the features stated above but with extra goodies!
"Exclusive features" included:
Battery Bar
Battery Styles
Clock Customization
Corrected lock screen icons not changing after applying different theme
"Disco Dingo" the QS (just a funny name for the option to apply random colors on QS toggles)
Hide QS Labels
Lock screen album art customization
Lock screen camera shortcut (enable/disable)
Lock screen custom clock faces
Network Traffic Indicators (unfortunately, on redfin, it only works on QS Header and not on status bar)
QS Battery percentage independent options
QS Header opacity level control
QS Headers styles
QS Panel opacity level control
QS Tiles styles
QS Data usage info
QS Rows x Columns options (both on portrait and landscape modes)
Reduce Status bar height (and correct left padding on devices with the notch on the left)
Removed side assist handles from lock screen
Status bar Quick Pulldown (Never, Right pulldown, Left pulldown, Always)
Switch styles
Touch QS Labels to add or remove on QS customize panel (just didn't bothered to translate "Tap or Drag Tiles..." strings, so you'll continue to see "Drag Tiles..." but the feature is there, try it.)
Exclusive features downloads:
Android_11_Addon_Features_For_Pixel_V13.zip -> "Harmless" module that works on any Pixel device running on STOCK ROM, much like the "universal mod" shared above, but with a Rom Control app version that has more options. The "exclusive features" options won't do anything if the SystemUI module, shared next, isn't installed. If your going to try these exclusive features module, install this one and not the one shared above. The SaftetyNet is also included on this module, so once again, don't try to use any other SafetyNet module since it could break things.
Android_11_SystemUI_for_Addon_Features_V10.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI. Without this module the "exclusive features" won't work. Also, this module could be responsible for breaking boot if it fails to work at your end. I've ran several tests on my device (a Pixel 4a) and didn't face any issues but, since this module replaces stock SystemUI for a modded SystemUI, you could run into problems if some other module tries to do the same or it's simply incompatible with it. This module was updated to match latest Android 11 October 2021 build.
Android_11_SystemUI_for_Addon_Features_V9.zip -> Use this version ONLY if you're still running any Android 11 build between June and September 2021!
Notes regarding the "exclusive version" for Pixel devices:
DO NOT, I'll repeat, DO NOT flash "SystemUI module" zip on any other ROM besides stock. It won't work! If you want those extra features on your current ROM you will have to port them yourself. I explain how to later on this post.
Make sure that you're able to run adb shell as root before rebooting your device.
If something goes wrong after flashing "SystemUI module", like if your device doesn't boot or something stupid, connect your phone to your PC during boot and run this:
Code:
adb shell
Code:
su
Code:
rm -rf /data/adb/modules/Modded_SystemUI && reboot
If you forgot to enable the ability to run adb shell as root, and if your device is on a "non-boot" state, the only way you can fix that is to remove all Magisk modules you have installed. That can be achieved by running the following commands during boot:
Code:
adb shell
Code:
magisk --remove-modules
If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).
The "SystemUI module" requires that your device is already updated to March build!
When a new OTA update comes please don't flash the "SystemUI module" until I say it's ok to do so. I mean, me or any other member who may have tested it. Why? Because Google may change things on stock SystemUI between builds. When that happens, I have to recreate the module again to adapt those changes. For instance, March build was not compatible with the module that was built on top of February build SystemUI. Rest assured that I'll always test the module with new builds and update as necessary.
In case your device gets caught in a bootloop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:
Code:
adb logcat > log.txt
Requirements:
Unlocked bootloader
Magisk Root | Magisk Manager
Suggestion:
Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.
If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.
How to install? (If you're running a Pixel 5, just install the module...you don't need all these next steps)
Uninstall Device Personalization Services updates
Clear Google Play Store app data and cache
Flash the Magisk Module(s)
Reboot device
Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
Profit!
Video:
Check all Rom Control (with exclusive features) options HERE.
How's these "exclusive features" even possible?
All (well, not all but almost...) features that you see on Pixel Devices "SystemUI module" were reverse engineered from Evolution X ROM source code. The source code is available on the link bellow shown on the credits. This means that I've been practicing some hard core "old school" Android smali edition in order to get this working. So, yes, I have some credits about this but, if it weren't for the original developers and it's public source code, none of this would be possible. Thank them for this!
Smali, and xml, edition wasn't enough to get this working. After decompiling, changing/adapt the code and recompiling everything again, I had to find a way to make it bootable without messing with the original apk signature. And here is where VR Theme logic came in handy. So thanks for the original dev who brought us this feature.
As for ROM Control app....this was/is a project created by daxgirl and wubydax back in 2015! So yeah, I'm not bringing anything new here, I just followed their instructions in order to get the features working after editing smali/xml with the source code taken from Evolution X. The original app source code is also available on the link shared on the credits.
I've just combined all of the above into a Magisk Module and shared here so that we can get the best of both worlds....a stock ROM with custom features included.
Rom Control with "exclusive features" source code:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a
Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a/app/src/mods
Credits:
EvolutionX ROM team, specially @joeyhuab
@daxgirl and @Wuby986 for ROM Control project and source code.
@Tulsadiver for showing me how to adapt VR Theme logic originally used on 3Minit Battery Mod by @gharrington.
@Ticklefish for Tickle My Android
@topjohnwu for Magisk
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers and enjoy!
Thanks, will try soon
Works fine here.
Wow it's amazing, thanks for your work.
@Typhus_
This module is/ these modules are amazing, well done! A small psa tho, with the modified systemui the currently playing song does no show on the aod. If you want to see the song just use the single "non-exclusive" module
OP has been updated!
New "exclusive features" added:
"Disco Dingo the QS" (just a funny name for the option to apply random colors on QS toggles)
Lock Screen Camera Shortcut (enable/disable)
Status bar reduce height (and option to correct left padding on devices with the notch on the left)
Status bar quick QS pulldown (Never, Right pulldown, Left pulldown, Always)
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V10" and "SystemUI V5" modules to be flashed.
Cheers!
OP has been updated!
New "exclusive features" added:
Status bar reduce height options (Default, Small, Medium)
Lock Screen Fluid Custom Clock
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V11" and "SystemUI V6" modules to be flashed.
Cheers!
OP has been updated!
New "exclusive features" added:
Bring back status bar footer drag handle (and it's options | Default; Accent based; Hidden)
Added option to completely remove the nav bar (it gets removed on any navigation mode but stock gestures will continue to work)
Center clock position fix option (it's needed for devices with a left notch using default status bar height)
Added Switch styles
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V12" and "SystemUI V7" modules to be flashed.
Notes:
The "center clock position fix" is somewhat related to the status bar height and "fix left side padding" options. You may encounter a few weird behaviors if you try to enable/disable/change those 3 features several times on Rom Control. I ran into a weird situation when testing all possible combo options....at the end I choose default status bar height and left clock. To my surprise, the clock ended up behind the notch...WTF!? So, if that, by any chance, happens to you, just try to set on/off all to default values, close ROM Control, open it again and choose your desired combo.
The "completely remove navigation bar" option has a warning dialog. I've added a "warning" so that people read it and understand what that option does. Since the text is somewhat long, I've added a timer that only enables the overlay, that removes the nav bar, after 10 secs (so that people have time to read the warning). And so, if you see the warning and just decide to immediately touch OK, you'll notice that the nav bar will only disappear after 10 secs... Having this said, the first a**hole that comes here stating something like "hey man I touch the remove nav bar option and it doesn't disappear...wtf!?...plzzz, halp. I've tried to enable disable several times...it dasn't wark!!!"... will be rewarded with a very nice "F**K *ff!" answer.
Cheers!
Hello!
SystemUI MOD V7 is compatible with April update, I'm using it already and it's working ok.
Tested it on sunfish (Pixel 4a) but I think it's the same for all models.
Thought you'd like to know.
Cheers!
I've successfully installed it on my pixel 4 (april update), But I couldn't find the adaptive audio settings option, all the rom control stuff works fine. I've installed both addon + modded sys ui.
danielaniq28 said:
I've successfully installed it on my pixel 4 (april update), But I couldn't find the adaptive audio settings option, all the rom control stuff works fine. I've installed both addon + modded sys ui.
Click to expand...
Click to collapse
That option only appears if Device Personalization Services are properly updated to last Pixel 5 version. Make sure to uninstall you current Device Personalization Services update, check that on app settings, afterwards clear Play Store App data and cache and reboot. Upon reboot, go to Play Store and check for updates. You should now see an update to Device Personalization Services. Do it, afterwards go to Rom Control and toggle off/on the adaptive sound service option. The feature should now appear on sound settings.
Cheers!
can I remove lockscreen charging / unlock info with this module?
ryandxter said:
can I remove lockscreen charging / unlock info with this module?
Click to expand...
Click to collapse
No. Those features don't exist...at least yet.
..
Installed in Pixel 4 and working 100%.
I have a question tho
Is there a way to disable the blur when going to homescreen from an app? Is a little time before the homescreen shows correctly, but no blur setup changed that.
I love this module, I missed so much the Album Cover in lockscreen. Thanks for the work!!!!
Guinis said:
Installed in Pixel 4 and working 100%.
I have a question tho
Is there a way to disable the blur when going to homescreen from an app? Is a little time before the homescreen shows correctly, but no blur setup changed that.
I love this module, I missed so much the Album Cover in lockscreen. Thanks for the work!!!!
Click to expand...
Click to collapse
No, the module only enables/disables default Android 11 blur that's implemented by Google. Not much else I can do besides that.
Glad you liked the mod.
Cheers!
Typhus_ said:
No, the module only enables/disables default Android 11 blur that's implemented by Google. Not much else I can do besides that.
Glad you liked the mod.
Cheers!
Click to expand...
Click to collapse
After a reboot I managed to restore the stock animation (It seems like when I played with the blur settings of notification/album cover and after rebooting the SystemUI the animation to homescreen bugged), I write if someone got the same experience.
thanks again for the module and the quick answer
Hello, I guess I'm the first idiot who's managed to break a phone with this mod, and I need some help.
Yesterday, I tried to flash a module named P5Props after flashing both Addon modules (SysUI v7 and v12), to see if that'd work.
But, these two modules don't seem to go together very well, and I got stuck on "Pixel is starting".
So, I removed P5Props using the same rm -rf command you mentioned in your first post, but that just made the phone boot to a black screen.
Then I tried booting into Safe Mode, but that just threw my phone into a reboot loop, where the phone boots up, and the Power off screen shows up immediately.
That was on a March 2021 update. After that, I updated to the April 2021 update, and that fixed the problem. But then I did it again.
I didn't flash P5Props this time, just updated the phone, and re-enabled my Magisk modules (they got disabled when I booted into Safe Mode before updating). Everything was fine, until I used the quick reboot option in Rom Control. That restarted my phone without launching SystemUI, but Pixel launcher worked. So I went to Rom Control again, and restarted SystemUI again.
And that's when my phone started booting to a black screen for the 2nd time. This time, I removed the SystemUI addon, and once again, my phone is now stuck in a reboot loop. I also tried removing all Magisk modules, but that didn't seem to help.
Trying to boot the phone without root doesn't work. It crashes and reboots into fastboot with an error saying "no valid boot slot". Reflashing the factory image doesn't work either, because it's not actually updating Android.
A new update might fix the phone again, but I'd have to wait until next week's Wednesday for that.
I have a logcat log, but I don't know if it has too much, or not enough info.
Thanks for your time and help. I'll attach a video of the reboot loop when it finishes uploading.
(also, the attached logcat doesn't show up for some reason)
Edit: since the phone I'm talking about is my daily driver (Pixel 4), and I couldn't afford to wait 9 more days, I updated it to Android 12 DP3. But could you still look into it? I wanna know what caused all this havoc and it might be helpful for other people as well.
Also, the Android 12 Addon module doesn't work on DP3
The current SystemUI V7 module isn't compatible with May update.
The phone boots but SystemUI just gets FC.
I'll have to fix the module and upload a new version.
Please be patient.
Cheers!
Hello!
SystemUI V8 module has been added on the OP.
It's already working with May build update.
Please do not get confused with "Addon features V8", it's SYSTEMUI V8!
Cheers and enjoy!
Well, SystemUI MOD is really not compatible with June update.
Google introduced some changes that requires some lame edition (mainly the IDs are different...which sucks).
It's going to be a dull procedure but I'll try to do it as fast as possible.
Please wait for a new update. As soon as I do it, I'll share.
Cheers!
Hello!
Addon Features V13 and SystemUI V9 modules have been added on the OP.
These MODs are now working with June build update.
No other features were added, only make them compatible with June update (sorry, I don't have much free time lately).
Cheers and enjoy!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11:
Forces Google Sans font system wide
63 Accent colors
12 Icon shapes
22 Fonts
Wallpapers Breel 2019; 2020 & 2020a
9 different Dark Styles
Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
Background Blur options
Blur Intensity options
Adaptive sound options
Navigation bar options (hide pill, reduce keyboard bottom space size, hide assist handles)
SystemUI Tuner options
Rounded corner options
QS Rows x Columns options
QS Footer Drag Handle options (Default, Accent based, Hidden)
Option to show more icon notifications on staus bar
Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide
Rom Control app (to setup all options available that you cannot using just Styles & Wallpapers)
Everything can be controlled using Styles & Wallpapers and also Rom Control app.
This MOD will probably work on any AOSP, or close to it, ROMs.
Get it here: Android_11_Addon_Features_for_Pixel_V8.zip
Just a note, this module already includes a SafetyNet fix, so if you're using another module for SafetyNet, please remove it since I don't know if that couldn't cause issues.
For all users already running Android 12 please go to THIS THREAD.
Addon Features EXCLUSIVE for Pixel Devices running on STOCK Android 11 ROM:
These exclusive and specific for Pixel Devices running on STOCK Android 11 ROM Magisk modules that you'll see next adds all of the features stated above but with extra goodies!
"Exclusive features" included:
Battery Bar
Battery Styles
Clock Customization
Corrected lock screen icons not changing after applying different theme
"Disco Dingo" the QS (just a funny name for the option to apply random colors on QS toggles)
Hide QS Labels
Lock screen album art customization
Lock screen camera shortcut (enable/disable)
Lock screen custom clock faces
Network Traffic Indicators (unfortunately, on redfin, it only works on QS Header and not on status bar)
QS Battery percentage independent options
QS Header opacity level control
QS Headers styles
QS Panel opacity level control
QS Tiles styles
QS Data usage info
QS Rows x Columns options (both on portrait and landscape modes)
Reduce Status bar height (and correct left padding on devices with the notch on the left)
Removed side assist handles from lock screen
Status bar Quick Pulldown (Never, Right pulldown, Left pulldown, Always)
Switch styles
Touch QS Labels to add or remove on QS customize panel (just didn't bothered to translate "Tap or Drag Tiles..." strings, so you'll continue to see "Drag Tiles..." but the feature is there, try it.)
Exclusive features downloads:
Android_11_Addon_Features_For_Pixel_V13.zip -> "Harmless" module that works on any Pixel device running on STOCK ROM, much like the "universal mod" shared above, but with a Rom Control app version that has more options. The "exclusive features" options won't do anything if the SystemUI module, shared next, isn't installed. If your going to try these exclusive features module, install this one and not the one shared above. The SaftetyNet is also included on this module, so once again, don't try to use any other SafetyNet module since it could break things.
Android_11_SystemUI_for_Addon_Features_V10.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI. Without this module the "exclusive features" won't work. Also, this module could be responsible for breaking boot if it fails to work at your end. I've ran several tests on my device (a Pixel 4a) and didn't face any issues but, since this module replaces stock SystemUI for a modded SystemUI, you could run into problems if some other module tries to do the same or it's simply incompatible with it. This module was updated to match latest Android 11 October 2021 build.
Android_11_SystemUI_for_Addon_Features_V9.zip -> Use this version ONLY if you're still running any Android 11 build between June and September 2021!
Notes regarding the "exclusive version" for Pixel devices:
DO NOT, I'll repeat, DO NOT flash "SystemUI module" zip on any other ROM besides stock. It won't work! If you want those extra features on your current ROM you will have to port them yourself. I explain how to later on this post.
Make sure that you're able to run adb shell as root before rebooting your device.
If something goes wrong after flashing "SystemUI module", like if your device doesn't boot or something stupid, connect your phone to your PC during boot and run this:
Code:
adb shell
Code:
su
Code:
rm -rf /data/adb/modules/Modded_SystemUI && reboot
If you forgot to enable the ability to run adb shell as root, and if your device is on a "non-boot" state, the only way you can fix that is to remove all Magisk modules you have installed. That can be achieved by running the following commands during boot:
Code:
adb shell
Code:
magisk --remove-modules
If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).
The "SystemUI module" requires that your device is already updated to March build!
When a new OTA update comes please don't flash the "SystemUI module" until I say it's ok to do so. I mean, me or any other member who may have tested it. Why? Because Google may change things on stock SystemUI between builds. When that happens, I have to recreate the module again to adapt those changes. For instance, March build was not compatible with the module that was built on top of February build SystemUI. Rest assured that I'll always test the module with new builds and update as necessary.
In case your device gets caught in a bootloop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:
Code:
adb logcat > log.txt
Requirements:
Unlocked bootloader
Magisk Root | Magisk Manager
Suggestion:
Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.
If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.
How to install? (If you're running a Pixel 5, just install the module...you don't need all these next steps)
Uninstall Device Personalization Services updates
Clear Google Play Store app data and cache
Flash the Magisk Module(s)
Reboot device
Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
Profit!
Video:
Check all Rom Control (with exclusive features) options HERE.
How's these "exclusive features" even possible?
All (well, not all but almost...) features that you see on Pixel Devices "SystemUI module" were reverse engineered from Evolution X ROM source code. The source code is available on the link bellow shown on the credits. This means that I've been practicing some hard core "old school" Android smali edition in order to get this working. So, yes, I have some credits about this but, if it weren't for the original developers and it's public source code, none of this would be possible. Thank them for this!
Smali, and xml, edition wasn't enough to get this working. After decompiling, changing/adapt the code and recompiling everything again, I had to find a way to make it bootable without messing with the original apk signature. And here is where VR Theme logic came in handy. So thanks for the original dev who brought us this feature.
As for ROM Control app....this was/is a project created by daxgirl and wubydax back in 2015! So yeah, I'm not bringing anything new here, I just followed their instructions in order to get the features working after editing smali/xml with the source code taken from Evolution X. The original app source code is also available on the link shared on the credits.
I've just combined all of the above into a Magisk Module and shared here so that we can get the best of both worlds....a stock ROM with custom features included.
Rom Control with "exclusive features" source code:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a
Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a/app/src/mods
Credits:
EvolutionX ROM team, specially @joeyhuab
@daxgirl and @Wuby986 for ROM Control project and source code.
@Tulsadiver for showing me how to adapt VR Theme logic originally used on 3Minit Battery Mod by @gharrington.
@Ticklefish for Tickle My Android
@topjohnwu for Magisk
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers and enjoy!
OP has been updated!
New "exclusive features" added:
"Disco Dingo the QS" (just a funny name for the option to apply random colors on QS toggles)
Lock Screen Camera Shortcut (enable/disable)
Status bar reduce height (and option to correct left padding on devices with the notch on the left)
Status bar quick QS pulldown (Never, Right pulldown, Left pulldown, Always)
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V10" and "SystemUI V5" modules to be flashed.
Cheers!
OP has been updated!
New "exclusive features" added:
Status bar reduce height options (Default, Small, Medium)
Lock Screen Fluid Custom Clock
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V11" and "SystemUI V6" modules to be flashed.
Cheers!
OP has been updated!
New "exclusive features" added:
Bring back status bar footer drag handle (and it's options | Default; Accent based; Hidden)
Added option to completely remove the nav bar (it gets removed on any navigation mode but stock gestures will continue to work)
Center clock position fix option (it's needed for devices with a left notch using default status bar height)
Added Switch styles
Hope you may enjoy these new features.
Remember, these features needs both "Addon features V12" and "SystemUI V7" modules to be flashed.
Notes:
The "center clock position fix" is somewhat related to the status bar height and "fix left side padding" options. You may encounter a few weird behaviors if you try to enable/disable/change those 3 features several times on Rom Control. I ran into a weird situation when testing all possible combo options....at the end I choose default status bar height and left clock. To my surprise, the clock ended up behind the notch...WTF!? So, if that, by any chance, happens to you, just try to set on/off all to default values, close ROM Control, open it again and choose your desired combo.
The "completely remove navigation bar" option has a warning dialog. I've added a "warning" so that people read it and understand what that option does. Since the text is somewhat long, I've added a timer that only enables the overlay, that removes the nav bar, after 10 secs (so that people have time to read the warning). And so, if you see the warning and just decide to immediately touch OK, you'll notice that the nav bar will only disappear after 10 secs... Having this said, the first a**hole that comes here stating something like "hey man I touch the remove nav bar option and it doesn't disappear...wtf!?...plzzz, halp. I've tried to enable disable several times...it dasn't wark!!!"... will be rewarded with a very nice "F**K *ff!" answer.
Cheers!
Thanks for this, may give it a shot this weekend!
Hello!
SystemUI MOD V7 is compatible with April update, I'm using it already and it's working ok.
Tested it on sunfish (Pixel 4a) but I think it's the same for all models.
Thought you'd like to know.
Cheers!
Had to stay on stock for a bit so I gave this a shot on the latest April update and it works just fine! Banking apps pass Safety net and all that jazz. Thank you for your work @Typhus_ !
I followed instructions exactly and after I install the new SystemUI Module, my phone restarts and gives me "System UI has stopped" and then a black screen. I'm on stock Android 11 rooted with the latest Magisk and no other modules installed. Any idea what the problem could be?
eragon1452 said:
I followed instructions exactly and after I install the new SystemUI Module, my phone restarts and gives me "System UI has stopped" and then a black screen. I'm on stock Android 11 rooted with the latest Magisk and no other modules installed. Any idea what the problem could be?
Click to expand...
Click to collapse
Is your phone running latest official build?
Anyway, without a logcat I can't really find out what went wrong.
The current SystemUI V7 module isn't compatible with May update.
The phone boots but SystemUI just gets FC.
I'll have to fix the module and upload a new version.
Please be patient.
Cheers!
Hello!
SystemUI V8 module has been added on the OP.
It's already working with May build update.
Please do not get confused with "Addon features V8", it's SYSTEMUI V8!
Cheers and enjoy!
So just to confirm I've got this right, add-on features V12, and system UI V8 for May patch?
purgy said:
So just to confirm I've got this right, add-on features V12, and system UI V8 for May patch?
Click to expand...
Click to collapse
Yup
amazing work. also for those wondering it does work with swift installer. you just have to disable your themes first and then install the mod and systemui stuff. after that reboot you just reinstall the themes and it works fine.
this seems to have stopped the current song title from being shown on the AOD. is there a way to get that back?
__init__ said:
this seems to have stopped the current song title from being shown on the AOD. is there a way to get that back?
Click to expand...
Click to collapse
Not that I know of. Can't quite understand why that happens....sorry.
Would this clash with gravity box?
With edge sense plus?
If anyone uses those in combination with this mod would be great to hear
I somehow ended up with an unresponsive black screen after flashing first addon v8, rebooting, then installing systemiu v12 on next reboot. don't do this
gonna try now with systemui 1st then addon in the one go
edit - nope, that just left me booting into a black screen even when holding down volume during boot for safe mode, which saved me the 1st time.
Only other mods were busybox ndk, detach, quickswitch.
Magisk 22.1, may patch.
purgy said:
I somehow ended up with an unresponsive black screen after flashing first addon v8, rebooting, then installing systemiu v12 on next reboot. don't do this
gonna try now with systemui 1st then addon in the one go
edit - nope, that just left me booting into a black screen even when holding down volume during boot for safe mode, which saved me the 1st time.
Only other mods were busybox ndk, detach, quickswitch.
Magisk 22.1, may patch.
Click to expand...
Click to collapse
SystemUI MOD is "the mod" as I've explained on the OP.
It doesn't matter the order you flash them, what matters is that SystemUI MOD completely injects all smali and xml modifications into your current SystemUI and, this, can be a critical operation if, by any chance, something else is trying to inject or change or whatever, your current SystemUI,
It will only work on stock ROM and, most likely, something else installed on your device is not playing nice with this. That's why I've sated on the OP:
Typhus_ said:
Suggestion:
Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.
If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.
Click to expand...
Click to collapse
So I suggest you do that, if you want to use this MOD, of course.
One other thing, without logcats, I cannot possibly guess what could be wrong. So, next time, if you want me to help you "the right way", please provide logs.
Cheers!
Would it be possible to add the option to use volume as media keys with screen off. I know most roms have the feature but stock doesn't.