• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

BrokenBee

Senior Member
Dec 20, 2016
269
42
  • 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!
I did exactly that man. With clean flashes on the latest ROM. Still the same problem
 

48SnowBalls

Member
Jan 11, 2018
6
0
Google Pixel 4a
I'm having the same problem, have you managed to find a fix yet? This occur everytime systemUI needed a restart. And some changes such as remove navigation bar crashes it entirely. Even changing to dark mode and changing style require a reboot because of the black screen
Ok i managed to bootloop my device and get a corruption message again. But after a clean wipe, completely uninstalling magisk, remove any module/xposed related files and switching boot slot. It's working! This time without any of the previous isssues
 

48SnowBalls

Member
Jan 11, 2018
6
0
Google Pixel 4a
I did exactly that man. With clean flashes on the latest ROM. Still the same problem
you should def check if there were any files or configurations left from Gravity Box xposed module. I tested by installing GB again and as soon as i touched any of the SystemUI related setting, the black screen appears. I checked the adb folder from my lastest wipe and lxposed files were still there.
 

48SnowBalls

Member
Jan 11, 2018
6
0
Google Pixel 4a
It took me another clean wipe, but i found the actual issue on my device
08-28 13:27:26.604 12881 12881 E AndroidRuntime: FATAL EXCEPTION: main
08-28 13:27:26.604 12881 12881 E AndroidRuntime: Process: com.android.systemui, PID: 12881
08-28 13:27:26.604 12881 12881 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.ImageView.setVisibility(int)' on a null object reference
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.StatusBarMobileView.updateDisplayType(StatusBarMobileView.java:382)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.updateOldStyleMobileDataIcons(StatusBarIconController.java:478)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.onTuningChanged(StatusBarIconController.java:467)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.tuner.TunerServiceImpl.addTunable(TunerServiceImpl.java:196)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.tuner.TunerServiceImpl.addTunable(TunerServiceImpl.java:175)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.addMobileIcon(StatusBarIconController.java:315)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.addHolder(StatusBarIconController.java:274)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$DarkIconManager.onIconAdded(StatusBarIconController.java:123)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconControllerImpl.addIconGroup(StatusBarIconControllerImpl.java:97)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.systemui.statusbar.phone.CollapsedStatusBarFragment.onViewCreated(CollapsedStatusBarFragment.java:157)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1313)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2431)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2210)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2166)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2067)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.FragmentManagerImpl$1.run(FragmentManager.java:742)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
08-28 13:27:26.604 12881 12881 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
08-28 13:27:26.606 1542 12959 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
08-28 13:27:26.608 1542 3881 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
Ignore my previous comment, there's no conflict with Gravity Box. My previous wipe simply remove my eSim. Logcat points to an exception in the mobile icon. Which, happens because i was using dual sim at the time. The only fix i can think of for the module to works properly is to disable one of the sim. So if any of you encounter the same issues as i do. Try to delete the eSim. In the meantime we wait for @Typhus_ to look in to the issues when he has free time !!
 

Typhus_

Senior Member
It took me another clean wipe, but i found the actual issue on my device

Ignore my previous comment, there's no conflict with Gravity Box. My previous wipe simply remove my eSim. Logcat points to an exception in the mobile icon. Which, happens because i was using dual sim at the time. The only fix i can think of for the module to works properly is to disable one of the sim. So if any of you encounter the same issues as i do. Try to delete the eSim. In the meantime we wait for @Typhus_ to look in to the issues when he has free time !!

I'm sorry guys...I really can't help you guys right now since I've moved on to Android 12.

I've tested the module on latest August build before moving on to Android 12 and nothing bad or weird happened.

Either way, something could be wrong since I've faced a similar issue when I was abroad this summer. When on Roaming network the module just stopped working as it should causing SystemUI crashes...really don't know what went wrong but it seems that something related with the StatusBarIconController$IconManager is just not ok.

Couldn't find out what it was since, when I came back home, everything worked as it should....so don't really know what was that.

Try to follow @48SnowBalls suggestion.


Cheers!
 
  • Like
Reactions: kkjb

barramas

Senior Member
Jan 19, 2013
170
33
hello my friends,sorry for my bad english
root and magisk it ok
I can not install.....
i'me not twrp
how to install it differently
please help

sorry install ok directly magisk apk.thanks for your work
 
Last edited:

kkjb

Senior Member
May 3, 2017
340
117
Some things work on clean Sept flash, but yep there are changes compared to Aug.
Factory build date was only 15 days after Aug, so looks like developers are in Housekeeping mode with a12 arrival?
Staying on Aug.
Excellent work, thank you for the goodness :)
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,614
5,390
Sydney
Some things work on clean Sept flash, but yep there are changes compared to Aug.
Factory build date was only 15 days after Aug, so looks like developers are in Housekeeping mode with a12 arrival?
Staying on Aug.
Excellent work, thank you for the goodness :)
I skipped the Aug build as there were no new features. The Sept build has some minor feature updates.

If I am reading you right, you are saying that this mod does work with the September build (I would assume you tested?), but you are staying with August?
 

kkjb

Senior Member
May 3, 2017
340
117
Sept factory flash clean wipe, install. The clock, date, qs "make colorful" options are partial problems. Wifi traffic enabled works after a restart... QS color pallette was odd. So yes, some things worked. Those are my favorites for mod. moved that 4a to beta 5. This one is still on Aug, its the phone... Phone :)
Edit 1. May not have been flashing, but play store was up to date. Then doing proper stop, clear, restart.. play service reverted to may 1. Would not update towards current. (Aug 1 on August theme mods) on this 4a..
 
Last edited:
  • Like
Reactions: DiamondJohn

koreyb

Member
Jun 25, 2009
37
4
Google Pixel 4a
Hello!

Addon Features V13 and SystemUI V9 modules are working with JULY build update.

Just tested it right now.

Cheers and enjoy!
Are you still doing updates on this? I have fallen in love with the gesture nav after realizing how much it easier is to 'go back' by swiping from the side of the screen instead of pressing all the way at the bottom.

Running Dirty unicorn on 4a and it has feature to program an action when you swipe from the side basically all the way to the center (instead of long pressing like you would on 3 button nav). Using it currently to kill foreground app, like I normally do by long pressing back on 3b nav.

Hopefully you understand what I mean and if you do, is this feature included? Or possible to be added? Maybe grabbing the code from DU?
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,614
5,390
Sydney
Are you still doing updates on this? I have fallen in love with the gesture nav after realizing how much it easier is to 'go back' by swiping from the side of the screen instead of pressing all the way at the bottom.

Running Dirty unicorn on 4a and it has feature to program an action when you swipe from the side basically all the way to the center (instead of long pressing like you would on 3 button nav). Using it currently to kill foreground app, like I normally do by long pressing back on 3b nav.

Hopefully you understand what I mean and if you do, is this feature included? Or possible to be added? Maybe grabbing the code from DU?
Although never say never, I think the OP's previous post (only a few posts above yours!) already answers your question
I'm sorry guys...I really can't help you guys right now since I've moved on to Android 12.

I've tested the module on latest August build before moving on to Android 12 and nothing bad or weird happened.

Either way, something could be wrong since I've faced a similar issue when I was abroad this summer. When on Roaming network the module just stopped working as it should causing SystemUI crashes...really don't know what went wrong but it seems that something related with the StatusBarIconController$IconManager is just not ok.

Couldn't find out what it was since, when I came back home, everything worked as it should....so don't really know what was that.

Try to follow @48SnowBalls suggestion.
 
  • Like
Reactions: kkjb

BrokenBee

Senior Member
Dec 20, 2016
269
42
Are you still doing updates on this? I have fallen in love with the gesture nav after realizing how much it easier is to 'go back' by swiping from the side of the screen instead of pressing all the way at the bottom.

Running Dirty unicorn on 4a and it has feature to program an action when you swipe from the side basically all the way to the center (instead of long pressing like you would on 3 button nav). Using it currently to kill foreground app, like I normally do by long pressing back on 3b nav.

Hopefully you understand what I mean and if you do, is this feature included? Or possible to be added? Maybe grabbing the code from DU?
You’re running the old DU build?
 

Masern

Member
Dec 29, 2012
6
0
thanks for this great mod.

is there a possibility to remove a specific feature? i want to swap the navbar buttons but i guess the interaction with another mod only makes one of the two working. is there a possible workaround for me?

thank you
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,614
5,390
Sydney

Top Liked Posts

  • 1
    Since I want to keep one A11, have two 4a's. One will stay on Last A11 release, and was surprised and happy that last mods release which had troubles on Aug works great for the few mods I want on October (last A11) Was surprised so twice tested, a complete factory flash, mod's install and was very happy worked fine.
  • 1
    Since I want to keep one A11, have two 4a's. One will stay on Last A11 release, and was surprised and happy that last mods release which had troubles on Aug works great for the few mods I want on October (last A11) Was surprised so twice tested, a complete factory flash, mod's install and was very happy worked fine.
  • 29
    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_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_V9.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.

    Android_11_SystemUI_for_Addon_Features_V8.zip -> Use this version ONLY if you're still running May Android 11 build update!


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