[MOD][MAGISK][ANDROID 11] Addon Features for Pixel Devices - Pixel 4a Thread

Search This thread

motes

Senior Member
Dec 20, 2010
426
63
Yes, it is normal.

The font changes are not system wide since the overlays that changes fonts work like that. I was only able to force Google Sans as default system wide, instead of Roboto font, since I actually replace the Roboto font files with Google Sans files inside the module. Every other font is just an overlay that don't actually change the font everywhere. It's standard procedure for all default font overlays (the ones you have even without my module installed).

With CFI module (Custom Font Instaler) it changes almost all phone texts (except some webs and the chat titles on telegram)
 

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
With CFI module (Custom Font Instaler) it changes almost all phone texts (except some webs and the chat titles on telegram)
That module probably does what I've done just with Google Sans font, which is, replace Roboto font files with Google Sans font files. It's doable and I've tried that approach before with all fonts included on this module but I soon realized that some fonts just look really ugly, and I mean REALLY UGLY, if we choose to do so. Having this in mind, and if you want a specific font to be applied system wide you can just replace the Roboto font files you see inside this module zip on /system/fonts/ with the files from the font you want. Just don't forget to rename them to Roboto-"whatever". After modifying the zip, flash that new zip version and your system will be with that font all over the place.

If you choose to do this, don't unzip the module zip, just do all changes directly inside the zip using 7zip or WinRar on your PC.
 

motes

Senior Member
Dec 20, 2010
426
63
That module probably does what I've done just with Google Sans font, which is, replace Roboto font files with Google Sans font files. It's doable and I've tried that approach before with all fonts included on this module but I soon realized that some fonts just look really ugly, and I mean REALLY UGLY, if we choose to do so. Having this in mind, and if you want a specific font to be applied system wide you can just replace the Roboto font files you see inside this module zip on /system/fonts/ with the files from the font you want. Just don't forget to rename them to Roboto-"whatever". After modifying the zip, flash that new zip version and your system will be with that font all over the place.

If you choose to do this, don't unzip the module zip, just do all changes directly inside the zip using 7zip or WinRar on your PC.
Yes it is what cfi module do, you need to creat a folder with all the forms of your font (italic, bold, regular...) and it makes a backup and change the roboto font for the onr on the folder... Why it makes that complikated Google😞😞🤦🏽‍♂️🤦🏽‍♂️
 

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
I appreciate it but cross checking hundreds of public ID's is a lot more than I would like to take on.

I've just updated the "tuto" on GitHub and also provided a new MODs.zip to (try and) make things even easier.

For instance, all new needed IDs are now identified and isolated on the R$* files. I've also identified all smali files that have content resources values.

All one needs now is some patience and a "working brain".

Honestly, I think you could make this under 1 hour without any hiccup.


Cheers!
 

wrongway213

Recognized Developer / Recognized Contributor / Re
Jul 27, 2014
5,071
8,815
32
Canton, OH
I've just updated the "tuto" on GitHub and also provided a new MODs.zip to (try and) make things even easier.

For instance, all new needed IDs are now identified and isolated on the R$* files. I've also identified all smali files that have content resources values.

All one needs now is some patience and a "working brain".

Honestly, I think you could make this under 1 hour without any hiccup.


Cheers!

First time in my life I've ever wished I was a Windows user 🤣
 
  • Haha
Reactions: Typhus_

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
** WARNING - TESTERS NEEDED **


I've decided to compare SystemUIGoogle.apk from sunfish (Pixel 4a) with all SystemUIGoogle.apk from other Pixel devices that had a March build.

Just to make sure, these were the devices that I've checked:

  • redfin -> Pixel 5
  • bramble -> Pixel 4a 5G
  • sunfish -> Pixel 4a
  • coral -> Pixel 4 XL
  • flame -> Pixel 4
  • bonito -> Pixel 3a XL
  • sargo -> Pixel 3a
  • crosshatch -> Pixel 3 XL
  • blueline -> Pixel 3

To my surprise the only difference between them is the signature used to sign the apk and one lib!? I've compared all files, one by one, using WinMerge.

You know what this could mean?

It could mean that the "specific and exclusive module" for sunfish shown on the OP could actually work on any Pixel running on A11 stock March build with a simple modification on the module's logic.


Ok, so having this said, is anyone willing to test this?


For those who want to test this, you may download these 2 new modules:


Android_11_Addon_Features_For_Pixel_V9.zip -> "Harmless" module that works on any Pixel device, much like the "universal mod" that's on the OP but with a Rom Control app version that has all options that, until now, were only available on the "specific" version for sunfish. Most of the features won't do anything if the other module isn't installed and actually works...(let's hope so, my fingers are crossed). 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.

Android_11_SystemUI_for_Addon_Features_V2.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 thus making my theory go down the toilet (let's hope not....)


Now, this is important!


Please have in mind that, if I'm wrong, you need to know what to do in case your device don't boot while testing.....

Basically, you'll only need to be able to disable the "SystemUI Module" in case things go south during boot.


This can be done in 3 ways:

1 - Remove the module with adb shell running as root during boot animation:

Code:
adb shell

Code:
su

Code:
rm -rf /data/adb/modules/Modded_SystemUI && reboot


2 - Remove all modules running a special adb shell Magisk command also during boot animation:

Code:
adb shell

Code:
magisk --remove-modules


3 - Force booting into safe mode and Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To do so, 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 (with the modules disabled). If you get stuck during boot animation, just force a reboot again (I've had to do that during my tests).


Now the question is, who wants to test this?


I'm 99% confident that this could actually work for any Pixel running on latest stock Android 11 March build.

If anybody wants to test please uninstall my universal mod first (if using it obviously).

The best would be to just disable all your current modules installed, just to make sure that, if the system doesn't actually boot, it's not due to incompatibility with any other module.


Remember to enable adb shell as root before doing anything!


Testers, I don't want anyone to yell at me if things go south...yes, this "is risky", it has a chance that will break boot
.

Rather than that it won't brick your phone, that's for sure.


If "SystemUI" module breaks boot, then just forget about this....or provide logs and I'll try to see if anything can be done about it....



I could use some feedback from all Pixel owners running on stock Android 11 with March build.


Best of luck to all testers.

I really am hoping that this works.


Cheers!


P.S. - This obviously works on sunfish (Pixel 4a), I'm just looking for testers using other models....

P.S.2 - I've tested a version built with redfin (Pixel 5) files extracted from stock redfin ROM and it worked on sunfish. So I'm pretty confident that this should work the "other way around".
 
Last edited:

andybones

Recognized Contributor / Inactive Recognized Devel
May 18, 2010
14,502
14,676
Google Pixel 5
** WARNING - TESTERS NEEDED **


Yesterday I've decided to compare SystemUIGoogle.apk from sunfish (Pixel 4a) with SystemUIGoogle.apk from redfin (Pixel 5), both stock, March builds.

To my surprise the only difference between both is the signature used to sign them and one lib!? I've compared all files, one by one, using WinMerge.

You know what this could mean?

It could mean that the "specific and exclusive module" for sunfish could actually work on redfin (and hopefully other Pixels) running on A11 stock March build with a simple modification on the module's logic.


Ok, so having this said, is anyone willing to test this theory?


For those "brave of you out there", you may download these 2 new modules:


Android_11_Addon_Features_For_Pixel_V9.zip -> "Harmless" module that works on any Pixel device, much like the "universal mod" that's on the OP but with a Rom Control app version that has all options that, until now, were only available on the "specific" version for sunfish. Most of the features won't do anything if the other module isn't installed and actually works...(let's hope so, my fingers are crossed).

Android_11_SystemUI_for_Addon_Features.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 thus making my theory go down the toillet (let's hope not....)



Now, this is important!

Please have in mind that, if I'm wrong, you need to know what to do in case your device don't boot while testing.....

Basically, you'll only need to be able to disable the "SystemUI Module" in case things go south during boot.


This can be done in 3 ways:

1 - Remove the module with adb shell running as root during boot animation:

Code:
adb shell

Code:
su

Code:
rm -rf /data/adb/modules/Modded_SystemUI && reboot

2 - Remove all modules running a special adb shell Magisk command also during boot animation:

Code:
adb shell

Code:
magisk --remove-modules

3 - Force booting into safe mode and Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To do so, 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 (with the modules disabled). If you get stuck during boot animation, just force a reboot again (I've had to do that during my tests).


Now the question is, who wants to test this?


I'm 90% confident that this could actually work for redfin users on latest stock Android 11 March build. If other Pixels SystemUI are built using the same logic then it could work for more.

If anybody wants to test please uninstall my universal mod first (if using it obviously). The best would be to just disable all current modules installed, just to make sure that, if the system doesn't actually boot, it's not due to incompatibility with any other module.


Remember to enable adb shell as root before doing anything!


Testers, I don't want anyone to yell at me if things go south...yes, this "is risky", it has a chance that will break boot
.

Rather than that it won't brick your phone, that's for sure.


So first test the "SystemUI" module. If it boots normally, you'll be able to use Rom Control with all features enabled. All you'll need is just to flash the other module.


If SystemUI module breaks boot, then just forget about this....or provide logs and I'll try to see if anything can be done about it....


Please provide feedback.


I could use some feeback from all Pixel owners running on stock Android 11 with March build.


Best of luck to all testers.

I really am hoping that this works.


Cheers!


P.S. - This obviously works on sunfish (Pixel 4a), I'm just looking for testers using other models....

Hey, tried flashing the SystemUI Module. It sent me to a factory reset, which I canceled and adb removed magisk modules to get me back booted. I only had time to test quickly and give feedback, so I apologize for not having any logs.
Thanks for taking the time for us. Keep up the great work my friend.
 

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
Hey, tried flashing the SystemUI Module. It sent me to a factory reset, which I canceled and adb removed magisk modules to get me back booted. I only had time to test quickly and give feedback, so I apologize for not having any logs.
Thanks for taking the time for us. Keep up the great work my friend.
Ok, thanks for your feedback.

Which device did you test?
 

andybones

Recognized Contributor / Inactive Recognized Devel
May 18, 2010
14,502
14,676
Google Pixel 5
Ok, thank you.

I was really hoping that it would work... don't quite understand why not...but, anyway, thanks again.
Very welcome.
I was hoping as well. Was looking forward to date in Status Bar.
How'd you get to learning smali so well? stuff ain't easy!

What would it take to get these extras for the P5 now that this method didn't work? I do have other modules but nothing that touched SystemUI. (Busybox, JamesDSP, debloat, pixel launcher editor, uni doze, uni safetynet)
Editing your smali/xml changes into the P5 SystemUI and creating a separate SystemUI_AddOn Module?

Would it be possible to adjust just the QS tile font size in ROM Control?
Would go along nicely with the options for changing rows/columns.
Right now I like stock 2 rows with 4 columns, but could get away with 2x5 or even 2x6 with the smaller font.
 

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
Very welcome.
I was hoping as well. Was looking forward to date in Status Bar.
How'd you get to learning smali so well? stuff ain't easy!

What would it take to get these extras for the P5 now that this method didn't work? I do have other modules but nothing that touched SystemUI. (Busybox, JamesDSP, debloat, pixel launcher editor, uni doze, uni safetynet)
Editing your smali/xml changes into the P5 SystemUI and creating a separate SystemUI_AddOn Module?

Would it be possible to adjust just the QS tile font size in ROM Control?
Would go along nicely with the options for changing rows/columns.
Right now I like stock 2 rows with 4 columns, but could get away with 2x5 or even 2x6 with the smaller font.
I've shared on the OP a link to GitHub where all xml and smali files are available as well as a tutorial that everyone can try to follow in order to adapt all "exclusive features" for their own devices.

As for QS font, the only way would be an overlay that would change the text style on QS but that would, not only, change the labels but it would also change other text like alarm and such on QS. Not sure if it would look good to be honest. I've tried that approach when I was trying to create an overlay to hide QS labels on the "universal" mod.

As for learning smali, I'm no expert but I have a brain....what I did was to see the original code in java, available on GitHub source code. Then I've took a Evolution custom ROM and decompiled it. Afterwards it was just a matter of patience by comparing file by file, method by method, to see what changed at smali level and adapt everything on stock. Recompile back, see if it work and boom...

Lot's and lot's of trial and error before achieving the desired goals. Countless hours around this, sometimes quite frustrating but, in the end, the job got done and I'm quite satisfied. I just wish I could find a way to get this on several Pixels but, judging by your report, it seems it won't be "that" easy.

Anyway, and like I've said, the worst part is done, everything I've shared makes it possible for anyone to adapt everything for their own devices.

Cheers!
 
Last edited:

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
What would it take to get these extras for the P5 now that this method didn't work? I do have other modules but nothing that touched SystemUI. (Busybox, JamesDSP, debloat, pixel launcher editor, uni doze, uni safetynet)
Editing your smali/xml changes into the P5 SystemUI and creating a separate SystemUI_AddOn Module?

Forgot to answer about this...

Yes, you're correct, you would have to adapt all xml and smali changes into your SystemUI and replace the stuff present on the SystemUI module with the ones from your recompiled and modified SystemUI.

Now, as for safety net, tell me something, did you flash both modules I've shared or did you just try and flash the SystemUI module? I ask this because the "Addon_features" module already has a saftety net fix inside that could conflict with any other safety net module installed, and that could also cause a non boot sate....forgot to mention that.

I don't mean to be insistent but, could you please remove all modules you have installed, reboot the device and just try again both modules I've shared for testing purposes?

If you could share logs, in case things fail, it would help me to understand as well what could be wrong.

This request is also for everyone out there who may read this.


Cheers!

P.S. - You're with March build, correct?
 
Last edited:

andybones

Recognized Contributor / Inactive Recognized Devel
May 18, 2010
14,502
14,676
Google Pixel 5
I've shared on the OP a link to GitHub where all xml and smali files are available as well as a tutorial that everyone can try to follow in order to adapt all "exclusive features" for their own devices.

As for QS font, the only way would be an overlay that would change the text style on QS but that would, not only, change the labels but it would also change other text like alarm and such on QS. Not sure if it would look good to be honest. I've tried that approach when I was trying to create an overlay to hide QS labels on the "universal" mod.

As for learning smali, I'm no expert but I have a brain....what I did was to see the original code in java, available on GitHub source code. Then I've took a Evolution custom ROM and decompiled it. Afterwards it was just a matter of patience by comparing file by file, method by method, to see what changed at smali level and adapt everything on stock. Recompile back, see if it work and boom...

Lot's and lot's of trial and error before achieving the desired goals. Countless hours around this, sometimes quite frustrating but, in the end, it gets the job done and I'm quite satisfied. I just wish I could find a way to get this on several Pixels but it seems it won't be "that" easy.

Anyway, and like I've said, the worst part is done, everything I've shared makes it possible for anyone to adapt everything for their own devices.

Cheers!
Thanks for the input.
Forgot to answer about this...

Yes, you're correct, you would have to adapt all xml and smali changes into your SystemUI and replace the stuff present on the SystemUI module with the ones from your recompiled and modified SystemUI.

Now, as for safety net, tell me something, did you flash both modules I've shared or did you just try and flash the SystemUI module? I ask this because the "Addon_features" module already has a saftety net fix inside that could conflict with any other safety net module installed, and that could also cause a non boot sate....forgot to mention that.

I don't mean to be insistent but, could you please remove all modules you have installed, reboot the device and just try again both modules I've shared for testing purposes?

If you could share logs, in case things fail, it would help me to understand as well what could be wrong.

This request is also for everyone out there who may read this.


Cheers!

P.S. - You're with March build, correct?

Thanks for hard work man. It is appreciated.

Latest March build.

I had disabled all modules previous to flashing, but I only flashed your SystemUI_Addon Module. I never got around to flashing the Addon_Features_V9.
 

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
Hello!

This thing was confusing me and I had to continue my quest until I could find something that would explain why it didn't work.

So today I've decided to implement all changes I've done on sunfish (Pixel 4a) into redfin (Pixel 5) SystemUIGoogle.apk.

Afterwards I've created a "SystemUI" module with all those changes, having redfin SystemUI recompiled files as base, inside and flashed it on sunfish.

I was hoping to get a non boot state and catch the logs....

Couldn't catch any logs...SINCE IT WORKED!


Now, am I stupid or if something made entirely with redfin original files worked on sunfish, why wouldn't it work the other way around!?
 

Attachments

  • 400094600153_393218.jpg
    400094600153_393218.jpg
    84 KB · Views: 35
  • 400150200970_183383.jpg
    400150200970_183383.jpg
    34.7 KB · Views: 36
Last edited:
  • Like
Reactions: andybones

Typhus_

Senior Member
Jan 9, 2013
1,134
1,210
41
Lisbon
www.facebook.com
Xiaomi Mi A1
Xiaomi Mi A3
Hello,

I've just updated the "SystemUI" module that I've shared for testing on THIS post.

I believe it's more accurate now and it may fix a issue that was causing a non boot state on other devices.

If you have tested it before and if it failed, please test it again.

I'm counting on more feedback.


Cheers!
 
Last edited:

Cj719

Senior Member
Hello,

I've just updated the "SystemUI" module that I've shared for testing on THIS post.

I believe it's more accurate now and it may fix a issue that was causing a non boot state on other devices.

If you have tested it before and if it failed, please test it again.

I'm counting on more feedback.


Cheers!
Just wanted to confirm its working on my 4a 5g
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    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!
    4
    Hello!

    SystemUI MOD V7 is compatible with April update, I'm using it already and it's working ok.

    Thought you'd like to know.

    Cheers!
    4
    Yeah, on my Pixel 4a 5G the center clock is almost perfectly centered on latest update after enabling the padding option but it makes sense it's not going to be the same for different size devices.
    Tulsa had to blindly test many versions of his mod via trial and error for every device he supports, which is a lot. If you collaborate with his work you could find out the correct padding for each device but that would still be a lot more work on your part creating a different mod for each device and then keeping them all up to date. I guess if you're really ambitious...

    Really enjoying what you've done here though and looking forward to see what else is possible on stock. This is a game changer imo
    I don't mind at all to team up with @Tulsadiver or with any other member.

    If the goal is to achieve a "Pixel community AWESOME MOD" that everyone can enjoy, I'll need help.

    I've shared all source code on GitHub. Anyone can contribute to it, create different branches for different devices, etc.

    You are all more than welcome to give me a hand and boost this up to the best custom MOD for stock ROM ever built.


    Cheers!
    3
    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!
  • 24
    Addon_Features_For_Pixel_Devices.png


    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 users that may be testing Android S developer preview I've made a module that, not only, adds all above features, but also, adds the hidden Android S features that you can choose to test. That module is shared HERE. I've also shared, on that post, a PDF with all features explained as well as instructions. Feel free to try it.



    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_V12.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_V7.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.


    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)

    1. Uninstall Device Personalization Services updates
    2. Clear Google Play Store app data and cache
    3. Flash the Magisk Module(s)
    4. Reboot device
    5. Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
    6. 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!
    6
    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!
    5
    OP has been updated.

    Both modules for March builds are now available.


    Cheers!
    5
    Hello!

    Both modules on the OP have been updated.


    Changelog:

    • Added QS Rows x Columns options
    • Navigation bar assist handles options added on "universal" module version
    • Improved ctsProfile fix

    Cheers!
    4
    Hello!

    OP has been updated...again...

    Changes:

    • Added option to control Blur Intensity (on both module versions).

    Maybe with lesser intensity, the blur will be more compatible with devices who suffers "frame drops" while using it...


    Cheers!
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone