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

Search This thread

Nuke1999

Member
Jun 20, 2018
7
3
Hello, how long does the "Pixel is starting" last upon first reboot after flashing via Magisk? Mine has been stuck there for a while.. (about 10 minutes now)
Edit: Yeah, it's not going past "Pixel is starting". I have Android 11 with a rooted boot.img (obviously). Flashed V4 Pixel 4a exclusive via Magisk (latest build as of typing this). ****.

Edit #2: Okay, so since I had no choice but to flash a stock image, I proceeded to do that and flash this module as cleanly as possible, AKA I flashed new image, made a rooted boot.img with Magisk Canary. After rooting the phone, I followed OP's procedure for flashing the module, and I am no longer getting stuck on "Pixel is starting". Phone booted up successfully. I will report back the stability of the app/any further problems I come across.

Edit #3: Yeah, no. Ever since flashing the module, I do not have a status bar, no way of accessing the drop down menu at all, and no navigation keys (or gesture navigation). Flashing another stock image...
 
Last edited:
  • Like
Reactions: DiamondJohn

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,084
4,508
Sydney
Hello, how long does the "Pixel is starting" last upon first reboot after flashing via Magisk? Mine has been stuck there for a while.. (about 10 minutes now)
Edit: Yeah, it's not going past "Pixel is starting". I have Android 11 with a rooted boot.img (obviously). Flashed V4 Pixel 4a exclusive via Magisk (latest build as of typing this). ****.

Edit #2: Okay, so since I had no choice but to flash a stock image, I proceeded to do that and flash this module as cleanly as possible, AKA I flashed new image, made a rooted boot.img with Magisk Canary. After rooting the phone, I followed OP's procedure for flashing the module, and I am no longer getting stuck on "Pixel is starting". Phone booted up successfully. I will report back the stability of the app/any further problems I come across.

Edit #3: Yeah, no. Ever since flashing the module, I do not have a status bar, no way of accessing the drop down menu at all, and no navigation keys (or gesture navigation). Flashing another stock image...
I have been very interested in this module, but it does sound at the higher end risk for a boot-loop, or in your case a failed boot; with great power comes.... You may be interested in my recent discussions regarding recovering from a failed magisk module at:
There is a few posts after this one as well.

As for accessing / navigating. I use the pie style controls of an app called fooView (its free on the playstore). Actually just realised, my custom launcher has the gesture of pulling down anywhere on my home page, to show the quick tiles.
 
  • Like
Reactions: Nuke1999

Typhus_

Senior Member
  • Jan 9, 2013
    1,201
    1,352
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    Hello, how long does the "Pixel is starting" last upon first reboot after flashing via Magisk? Mine has been stuck there for a while.. (about 10 minutes now)
    Edit: Yeah, it's not going past "Pixel is starting". I have Android 11 with a rooted boot.img (obviously). Flashed V4 Pixel 4a exclusive via Magisk (latest build as of typing this). ****.

    Edit #2: Okay, so since I had no choice but to flash a stock image, I proceeded to do that and flash this module as cleanly as possible, AKA I flashed new image, made a rooted boot.img with Magisk Canary. After rooting the phone, I followed OP's procedure for flashing the module, and I am no longer getting stuck on "Pixel is starting". Phone booted up successfully. I will report back the stability of the app/any further problems I come across.

    Edit #3: Yeah, no. Ever since flashing the module, I do not have a status bar, no way of accessing the drop down menu at all, and no navigation keys (or gesture navigation). Flashing another stock image...
    Please provide logcats so that I may try to figure out what went wrong at your end.

    On a side note, yesterday I was making some tests on a new version and suddenly something went terrible wrong without me doing nothing special on the module. I had no choice but to completely factory reset my device. After that, rooted the phone again, flash the module again and had no issues whatsoever. Weird, really weird. Logcat showed me something about missing permissions, which made no sense at all.

    Anyway, without logcats I can't understand what could be wrong, so if you could share yours I can try to make sense of what's wrong.

    Cheers!

    Edit - Forgot to mention that you can use latest stable Magisk version, we no longer need Canary version, not even for S.
     
    • Like
    Reactions: Nuke1999

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,201
    1,352
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    Hello!

    Ok so, after adding de QS Rows x Columns options I've realized that, at least on sunfish (the screen size is just too small), we get a really ugly QS panel if we add more Columns and keep the tiles labels.

    So I had to do something about it. Unfortunately, on Android 11 we cannot use the feature already included on S so I had to go into smali business once more to get it done for sunfish.

    The QS Rows x Columns "suffered" an overall and I've added the hide labels feature. Unfortunately, I cannot add (or, better yet, don't know how to add...) a similar feature to the "universal" mod for other Pixels running on R. I've tried to come up with an overlay but, R "does not compute" overlays where we have to mess with layouts, so, I could only make it for sunfish since it really needs SystemUI changes.


    OP has been updated with this new version exclusive for Pixel 4a.


    Cheers!
     

    Attachments

    • Hide_QS_Labels.jpg
      Hide_QS_Labels.jpg
      56 KB · Views: 25
    • Rows_x_Columns.jpg
      Rows_x_Columns.jpg
      29.6 KB · Views: 29
    • QS_Panel.jpg
      QS_Panel.jpg
      48.2 KB · Views: 26

    Nuke1999

    Member
    Jun 20, 2018
    7
    3
    I have been very interested in this module, but it does sound at the higher end risk for a boot-loop, or in your case a failed boot; with great power comes.... You may be interested in my recent discussions regarding recovering from a failed magisk module at:
    There is a few posts after this one as well.

    As for accessing / navigating. I use the pie style controls of an app called fooView (its free on the playstore). Actually just realised, my custom launcher has the gesture of pulling down anywhere on my home page, to show the quick tiles.
    Thanks, wish I would've done a little more digging yesterday! Will definitely use this from now on, until we can get TWRP running on A11.
     

    Nuke1999

    Member
    Jun 20, 2018
    7
    3
    Please provide logcats so that I may try to figure out what went wrong at your end.

    On a side note, yesterday I was making some tests on a new version and suddenly something went terrible wrong without me doing nothing special on the module. I had no choice but to completely factory reset my device. After that, rooted the phone again, flash the module again and had no issues whatsoever. Weird, really weird. Logcat showed me something about missing permissions, which made no sense at all.

    Anyway, without logcats I can't understand what could be wrong, so if you could share yours I can try to make sense of what's wrong.

    Cheers!

    Edit - Forgot to mention that you can use latest stable Magisk version, we no longer need Canary version, not even for S.
    So from a very quick search, it appears that the only way to obtain Android logcats is through Android Studio; do you know if there is a "lighter" option, or something that isn't such a big overall file size? I have the crappiest internet where I'm at right now, so downloading Android Studio would be a pain, but am willing to provide if there is another way of obtaining logcats.

    Edit: If I run the command adb logcat through cmd for like ~2 minutes after booting up with the module, would that give you enough information to determine the problem?
     
    Last edited:

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,201
    1,352
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    So from a very quick search, it appears that the only way to obtain Android logcats is through Android Studio; do you know if there is a "lighter" option, or something that isn't such a big overall file size? I have the crappiest internet where I'm at right now, so downloading Android Studio would be a pain, but am willing to provide if there is another way of obtaining logcats.

    Edit: If I run the command adb logcat through cmd for like ~2 minutes after booting up with the module, would that give you enough information to determine the problem?

    Well, I use Android studio but since we're able to run adb during boot, you can get the logcat at boot time and keep it going until you want to. I've included an option on the module so that, if it fails to boot it won't go to rescue mode keeping it alive but with a black screen. That way, not only you can get the logcat but, also, gives you time to run the command, I've shared on the OP, to remove the module in case something goes south.

    Cheers!
     

    DiamondJohn

    Recognized Contributor
    Aug 31, 2013
    5,084
    4,508
    Sydney
    Well, I use Android studio but since we're able to run adb during boot, you can get the logcat at boot time and keep it going until you want to. I've included an option on the module so that, if it fails to boot it won't go to rescue mode keeping it alive but with a black screen. That way, not only you can get the logcat but, also, gives you time to run the command, I've shared on the OP, to remove the module in case something goes south.
    I have read about another magisk module, where if a specific file is found in the root of the SDCard, that module will uninstall itself. Something like this may be a good option to get out of a bootloop without flashing stock. And there is always

    Also Magisk has its boot-logging, as well as last_kmsg. Would last kmsg be of any value?
     

    DiamondJohn

    Recognized Contributor
    Aug 31, 2013
    5,084
    4,508
    Sydney
    Hello!

    Ok so, after adding de QS Rows x Columns options I've realized that, at least on sunfish (the screen size is just too small), we get a really ugly QS panel if we add more Columns and keep the tiles labels.

    So I had to do something about it. Unfortunately, on Android 11 we cannot use the feature already included on S so I had to go into smali business once more to get it done for sunfish.

    The QS Rows x Columns "suffered" an overall and I've added the hide labels feature. Unfortunately, I cannot add (or, better yet, don't know how to add...) a similar feature to the "universal" mod for other Pixels running on R. I've tried to come up with an overlay but, R "does not compute" overlays where we have to mess with layouts, so, I could only make it for sunfish since it really needs SystemUI changes.


    OP has been updated with this new version exclusive for Pixel 4a.
    I havent installed this module yet, but the QS rows and columns are one of the most interesting features, as on previous phones and ROMs I had a 5x3 grid, and that was with a much smaller screen. I was therefore a little surprise to read the above. Attached is a full size screenshot of my other phone
    Screenshot_Ruthless_Launcher_20210228-101008.png
    Its now a test/backup phone, so the actual tiles are unimportant. Actually, looking at it now, if the tiles were drawn closer together vertically, another row could fit comfortably .
     

    Mike808James

    Member
    Feb 13, 2016
    16
    2
    I enabled this Magisk Module, but now when I plug in my Pixel 4a to the charging cable (original cable and power brick) it no longer shows "rapidly charging" on the lock screen, it just says Charging, and tells me about how much longer until full. Does this module disable fast charging on pixel 4a?
     

    Mike808James

    Member
    Feb 13, 2016
    16
    2
    Oops. I found out that I wasn't using the original cable and charging brick when I thought I was (I have so many that look so similar!) When I actually made sure and used original charging brick and cable with my pixel 4a, rapidly charging does appear on lock screen while charging with this Magisk Module active. I love how you made it possible for us to hide the stupid pill line in gestures! Thank you so much for this awesome module!
     
    • Like
    Reactions: Typhus_

    Mike808James

    Member
    Feb 13, 2016
    16
    2
    Please, try to uninstall the Device Personalization Services app update. Then, having the module installed, reboot and wait for, like, 2 minutes tops. Check if the option appears or not.
    I have the same problem with no adaptive sound option. I had deleted Device Personalization Services app on my pixel 4a using Debloater (Terminal Emulator) Magisk module with Termux before I about a week or two before I even found your module here. However, I figured I need to have it (Device Personalization Services) for the Adaptive Sound Option to appear in the settings of my Pixel 4a, so I downloaded the update in Google play store, then disabled the app and restarted my pixel 4a. Still no luck. Please help me figure this out Typhus_. Thank you.
     

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,201
    1,352
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    I have the same problem with no adaptive sound option. I had deleted Device Personalization Services app on my pixel 4a using Debloater (Terminal Emulator) Magisk module with Termux before I about a week or two before I even found your module here. However, I figured I need to have it (Device Personalization Services) for the Adaptive Sound Option to appear in the settings of my Pixel 4a, so I downloaded the update in Google play store, then disabled the app and restarted my pixel 4a. Still no luck. Please help me figure this out Typhus_. Thank you.
    If you removed it there's no problem. My module adds the Pixel 5 version. All you need is to let it update to latest version (clear play store app cache and data if needed). After the update is installed, just toggle off/on the adaptive sound service option on Rom Control.
     

    kkjb

    Senior Member
    May 3, 2017
    332
    113
    You the Man ! Thanks for the FAST heads up on March. Thank You for all your hard work on this simple but (for me) Perfect add on, just the right amount of modifications to Factory.
     

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,201
    1,352
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    Hello!

    OP has been updated once again...

    Changes:

    • Added option to show more notification icons on status bar (on both module versions for March builds)
    • Corrected Carrier text size on lock screen (exclusive module version for sunfish only)
    • Fixed the QS header clock left padding to match the padding on status bar (exclusive module version for sunfish only)

    Cheers!
     

    Natakranta

    Senior Member
    Mar 19, 2013
    3,212
    6,151
    Dublin
    Hello!

    OP has been updated once again...

    Changes:

    • Added option to show more notification icons on status bar (on both module versions for March builds)
    • Corrected Carrier text size on lock screen (exclusive module version for sunfish only)
    • Fixed the QS header clock left padding to match the padding on status bar (exclusive module version for sunfish only)

    Cheers!
    V.6 in the evening and v.7 now working fine on my Pixel 4a5G stock Mar.2021 rooted Magisk 22.0
    Thanks for quick update!
     

    Typhus_

    Senior Member
  • Jan 9, 2013
    1,201
    1,352
    41
    Lisbon
    www.facebook.com
    Xiaomi Mi A1
    Xiaomi Mi A3
    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!
     

    Attachments

    • 01.png
      01.png
      752 KB · Views: 24
    • 00.png
      00.png
      95.7 KB · Views: 23
    • 02.png
      02.png
      372.6 KB · Views: 24
    • 03.png
      03.png
      356.1 KB · Views: 16
    • 04.png
      04.png
      381.2 KB · Views: 16
    • 05.png
      05.png
      355.7 KB · Views: 16
    • 06.png
      06.png
      359.2 KB · Views: 15
    • 07.png
      07.png
      357.2 KB · Views: 14
    • 08.png
      08.png
      394.7 KB · Views: 14

    Top Liked Posts

    • There are no posts matching your filters.
    • 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
      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!
      2
      Latest May 2021 Build is now available ! Can you check if this is compatible with SystemUI MOD V7?
      I'm going to test soon and report back.
      1
      Missing a features that known as Smart charging which available on custom ROM! Hope you will add this on that Addon so that we can use this on Stock ROM.
      These are UI adjustments and features. I doubt smart charging would happen cos that would require kernel level adjustments
      1
      It also comes off as impatient considering the update was just released. I never said don't ask him but maybe just give it a day or two before doing so
      I just informed him ! Nothing else.
    • 27
      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.

      Android_11_SystemUI_for_Addon_Features_V8.zip -> Use this version if you're already using 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!

      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!
      5
      OP has been updated.

      Both modules for March builds are now available.


      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