[MOD][MAGISK][ANDROID 11] Addon Features for Pixel Devices - Pixel 5 Thread
- Thread starter Typhus_
- Start date
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!
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!
For the life of me I can not seem to get this working. What am I doing wrong? If someone could shed some light on the matter it would greatly appreciated.
My Steps:
I flashed (through magisk) V12 with system UI v8 and I get stuck in a boot loop at the G with the loading bar. Same happens with V12+V9 combo
i also flashed (through magisk) V13 with system UI v8 same results (boot loops). V13+V9 combo as well
i always flash the add-on first, then reboot. Both versions work fine giving me the rom control app. The problem is whenever I flash either of the system ui's regardless of the add-on version I end up in the same boot loop.
I am running Android 11 on a stock (rooted) Pixel 5. I have flashed everything doing a complete data erase and factory reset each time, it was the only way to get stuck out of the first boot loop that occurred.
Any CONSTRUCTIVE advise to guide me further?
My Steps:
I flashed (through magisk) V12 with system UI v8 and I get stuck in a boot loop at the G with the loading bar. Same happens with V12+V9 combo
i also flashed (through magisk) V13 with system UI v8 same results (boot loops). V13+V9 combo as well
i always flash the add-on first, then reboot. Both versions work fine giving me the rom control app. The problem is whenever I flash either of the system ui's regardless of the add-on version I end up in the same boot loop.
I am running Android 11 on a stock (rooted) Pixel 5. I have flashed everything doing a complete data erase and factory reset each time, it was the only way to get stuck out of the first boot loop that occurred.
Any CONSTRUCTIVE advise to guide me further?
Attachments
Your device is still on the January security update. You should be on the most recent stock ROM to continue. (June build).
You have to manually install all android updates once you have rooted your device. To do that you must uninstall all Magisk Module's and unroot your phone by flashing the boot.img of the Android rom version that you are currently on in your case it would be the January boot.img.
Okay thanks for the responses. I will look into how to flash the update then try this again once I do.
Not sure if anyone else has this issue with Android_11_Addon_Features_For_Pixel_V13.zip + Android_11_SystemUI_for_Addon_Features_V9_redfin_workaround.zip
The feature in the ROM Control app that automatically restarts/refreshed the SystemUI causes a complete System UI crash that requires a reboot to recover from. For example, when you change the QS Tile theme or the fonts. 80% of the settings cause this crash the moment you make a selection, making it almost impossible to set things up properly
I'm using the stock Pixel 5 June 2021 update (using Gesture Navigation), with Magisk 23.0 and only these two modules.
The feature in the ROM Control app that automatically restarts/refreshed the SystemUI causes a complete System UI crash that requires a reboot to recover from. For example, when you change the QS Tile theme or the fonts. 80% of the settings cause this crash the moment you make a selection, making it almost impossible to set things up properly
I'm using the stock Pixel 5 June 2021 update (using Gesture Navigation), with Magisk 23.0 and only these two modules.
Code:
06-18 11:52:53.154 13599 13599 D AndroidRuntime: Shutting down VM
06-18 11:52:53.156 13599 13599 E AndroidRuntime: FATAL EXCEPTION: main
06-18 11:52:53.156 13599 13599 E AndroidRuntime: Process: com.android.systemui, PID: 13599
06-18 11:52:53.156 13599 13599 E AndroidRuntime: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.ImageView.setVisibility(int)' on a null object reference
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.StatusBarMobileView.updateDisplayType(StatusBarMobileView.java:382)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.updateOldStyleMobileDataIcons(StatusBarIconController.java:478)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.onTuningChanged(StatusBarIconController.java:467)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.tuner.TunerServiceImpl.addTunable(TunerServiceImpl.java:196)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.tuner.TunerServiceImpl.addTunable(TunerServiceImpl.java:175)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.addMobileIcon(StatusBarIconController.java:315)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$IconManager.addHolder(StatusBarIconController.java:274)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconController$DarkIconManager.onIconAdded(StatusBarIconController.java:123)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.StatusBarIconControllerImpl.addIconGroup(StatusBarIconControllerImpl.java:97)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.systemui.statusbar.phone.CollapsedStatusBarFragment.onViewCreated(CollapsedStatusBarFragment.java:157)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1313)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.FragmentManagerImpl.addAddedFragments(FragmentManager.java:2431)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.FragmentManagerImpl.executeOpsTogether(FragmentManager.java:2210)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManager.java:2166)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.FragmentManagerImpl.execPendingActions(FragmentManager.java:2067)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.FragmentManagerImpl$1.run(FragmentManager.java:742)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.os.Looper.loop(Looper.java:223)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7664)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
06-18 11:52:53.156 13599 13599 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
06-18 11:52:53.160 1905 13679 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
06-18 11:52:53.161 1905 7437 W ActivityManager: Process com.android.systemui has crashed too many times: killing!
06-18 11:52:53.162 13599 13599 I Process : Sending signal. PID: 13599 SIG: 9
06-18 11:52:53.164 1905 1939 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
06-18 11:52:53.164 1905 1939 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
06-18 11:52:53.169 910 966 I [email protected]: skin-therm-monitor: 38.923
06-18 11:52:53.206 1905 2058 W InputDispatcher: channel '4b47910 ScreenDecorOverlayBottom (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-18 11:52:53.207 1905 2058 E InputDispatcher: channel '4b47910 ScreenDecorOverlayBottom (server)' ~ Channel is unrecoverably broken and will be disposed!
06-18 11:52:53.207 1905 2058 W InputDispatcher: channel 'bcf1ae5 ScreenDecorOverlay (server)' ~ Consumer closed input channel or an error occurred. events=0x9
06-18 11:52:53.207 1905 2058 E InputDispatcher: channel 'bcf1ae5 ScreenDecorOverlay (server)' ~ Channel is unrecoverably broken and will be disposed!
06-18 11:52:53.207 1131 2369 D BufferPoolAccessor2.0: Destruction - bufferpool2 0xb400007ad827b978 cached: 0/0M, 0/0% in use; allocs: 15, 80% recycled; transfers: 14, 79% unfetched
06-18 11:52:53.207 1131 2368 D BufferPoolAccessor2.0: Destruction - bufferpool2 0xb400007ad8287278 cached: 0/0M, 0/0% in use; allocs: 7, 57% recycled; transfers: 6, 50% unfetched
06-18 11:52:53.208 1905 8662 D WifiExternalCallbackTracker: Binder died [email protected]
06-18 11:52:53.208 1905 4042 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=289, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247 AdministratorUids: [] RequestorUid: 10247 RequestorPackageName: com.android.systemui] ], [email protected])
06-18 11:52:53.208 1905 4043 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ TRACK_DEFAULT id=290, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247 AdministratorUids: [] RequestorUid: 10247 RequestorPackageName: com.android.systemui] ], [email protected])
06-18 11:52:53.208 1905 4043 W AS.AudioService: Current remote volume controller died, unregistering
06-18 11:52:53.208 1905 2376 I StatusBarManagerService: binder died for pkg=com.android.systemui
06-18 11:52:53.209 1905 4043 W VolumeController: Error calling dismiss
06-18 11:52:53.209 1905 4043 W VolumeController: android.os.DeadObjectException
06-18 11:52:53.209 1905 4043 W VolumeController: at android.os.BinderProxy.transactNative(Native Method)
06-18 11:52:53.209 1905 4043 W VolumeController: at android.os.BinderProxy.transact(BinderProxy.java:550)
06-18 11:52:53.209 1905 4043 W VolumeController: at android.media.IVolumeController$Stub$Proxy.dismiss(IVolumeController.java:260)
06-18 11:52:53.209 1905 4043 W VolumeController: at com.android.server.audio.AudioService$VolumeController.postDismiss(AudioService.java:7844)
06-18 11:52:53.209 1905 4043 W VolumeController: at com.android.server.audio.AudioService.setVolumeController(AudioService.java:7670)
06-18 11:52:53.209 1905 4043 W VolumeController: at com.android.server.audio.AudioService$4.binderDied(AudioService.java:7679)
06-18 11:52:53.209 1905 4043 W VolumeController: at android.os.IBinder$DeathRecipient.binderDied(IBinder.java:305)
06-18 11:52:53.209 1905 4043 W VolumeController: at android.os.BinderProxy.sendDeathNotice(BinderProxy.java:664)
06-18 11:52:53.209 1905 4047 E BiometricService: Enabled callback binder died
06-18 11:52:53.209 1905 2094 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=289, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247 AdministratorUids: [] RequestorUid: 10247 RequestorPackageName: com.android.systemui] ] (release request)
06-18 11:52:53.209 1905 4047 E FingerprintService: Lockout reset callback binder died
06-18 11:52:53.209 1905 6489 I ActivityManager: Process com.android.systemui (pid 13599) has died: pers BFGS
06-18 11:52:53.210 1905 3110 W AudioService.RecordingActivityMonitor: client died
06-18 11:52:53.210 1905 1928 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=288, [ Transports: WIFI Capabilities: NOT_VPN AdministratorUids: [] RequestorUid: 10247 RequestorPackageName: com.android.systemui] ], [email protected])
06-18 11:52:53.210 1905 3110 D NotificationListeners: Removing active service ComponentInfo{com.android.systemui/com.android.systemui.statusbar.NotificationListener}
06-18 11:52:53.210 1905 1928 D WifiExternalCallbackTracker: Binder died [email protected]
06-18 11:52:53.210 1905 3110 D ConnectivityService: ConnectivityService NetworkRequestInfo binderDied(NetworkRequest [ LISTEN id=291, [ AdministratorUids: [] RequestorUid: 10247 RequestorPackageName: com.android.systemui] ], [email protected])
06-18 11:52:53.210 1905 2082 D WifiExternalCallbackTracker: Remove external callback on death 19681013
06-18 11:52:53.211 1905 1905 W WallpaperManagerService: Wallpaper service gone: ComponentInfo{com.android.systemui/com.android.systemui.ImageWallpaper}
06-18 11:52:53.211 1905 2094 D ConnectivityService: releasing NetworkRequest [ TRACK_DEFAULT id=290, [ Capabilities: INTERNET&NOT_RESTRICTED&TRUSTED Uid: 10247 AdministratorUids: [] RequestorUid: 10247 RequestorPackageName: com.android.systemui] ] (release request)
06-18 11:52:53.211 1905 1941 I libprocessgroup: Successfully killed process cgroup uid 10247 pid 13599 in 0ms
06-18 11:52:53.211 1905 2083 D WifiExternalCallbackTracker: Remove external callback on death 1874276
06-18 11:52:53.211 1131 2368 D BufferPoolAccessor2.0: Destruction - bufferpool2 0xb400007ad8285da8 cached: 0/0M, 0/0% in use; allocs: 14, 79% recycled; transfers: 13, 77% unfetched
06-18 11:52:53.211 1743 1743 I Zygote : Process 13599 exited due to signal 9 (Killed)
06-18 11:52:53.212 1905 2104 I WindowManager: WIN DEATH: Window{bbd2ea7 u0 NotificationShade}
06-18 11:52:53.212 1905 2104 W InputDispatcher: Attempted to unregister already unregistered input channel 'bbd2ea7 NotificationShade (server)'
06-18 11:52:53.215 1905 4041 I WindowManager: WIN DEATH: Window{9493f19 u0 AssistPreviewPanel}
06-18 11:52:53.215 1905 4041 W InputDispatcher: Attempted to unregister already unregistered input channel '9493f19 AssistPreviewPanel (server)'
06-18 11:52:53.216 1905 2378 I WindowManager: WIN DEATH: Window{f96a7ea u0 NavigationBar0}
06-18 11:52:53.216 1905 2378 W InputDispatcher: Attempted to unregister already unregistered input channel 'f96a7ea NavigationBar0 (server)'
06-18 11:52:53.217 1905 2378 V WindowManager: Orientation start waiting for draw, mDrawState=DRAW_PENDING in Window{4b47910 u0 ScreenDecorOverlayBottom}, surfaceController Surface(name=ScreenDecorOverlayBottom)/@0xef06572
06-18 11:52:53.218 1905 2378 W WindowManager: Failed to report 'resized' to Window{4b47910 u0 ScreenDecorOverlayBottom} due to android.os.DeadObjectException
06-18 11:52:53.218 1905 4042 I WindowManager: WIN DEATH: Window{4803df9 u0 StatusBar}
06-18 11:52:53.218 1905 4042 W InputDispatcher: Attempted to unregister already unregistered input channel '4803df9 StatusBar (server)'
06-18 11:52:53.218 1905 4042 V WindowManager: Orientation start waiting for draw, mDrawState=DRAW_PENDING in Window{bcf1ae5 u0 ScreenDecorOverlay}, surfaceController Surface(name=ScreenDecorOverlay)/@0xebe4a0
06-18 11:52:53.219 1905 4042 W WindowManager: Failed to report 'resized' to Window{bcf1ae5 u0 ScreenDecorOverlay} due to android.os.DeadObjectException
06-18 11:52:53.220 1905 4024 I WindowManager: WIN DEATH: Window{bcf1ae5 u0 ScreenDecorOverlay}
06-18 11:52:53.220 1905 4024 W InputDispatcher: Attempted to unregister already unregistered input channel 'bcf1ae5 ScreenDecorOverlay (server)'
06-18 11:52:53.221 1905 1928 I WindowManager: WIN DEATH: Window{4b47910 u0 ScreenDecorOverlayBottom}
06-18 11:52:53.221 1905 1928 W InputDispatcher: Attempted to unregister already unregistered input channel '4b47910 ScreenDecorOverlayBottom (server)'
Last edited:
all i can say is my setup is the same as yours stock june update with magisk and addon v13 UI v9 and no issues or crashes with any settings changes.
Same here! Working great!
However, I will say that when using Font-Manager to change the system fonts it put me into a "pixel phone is starting" loop that I had to ADB my way out of by disabling all modules.
I was curious, though....will this be compatable with substranium theme engine since it's just an overlay?
Someone on the 4a5g thread said it works.... At your own risk!
It's working for me on my 5, but as you said... At your own risk.
I just disabled it in Magisk, updated/rooted, and re-enabled it.
Hello!
Addon Features V13 and SystemUI V9 modules are working with JULY build update.
Just tested it right now.
Cheers and enjoy!
Addon Features V13 and SystemUI V9 modules are working with JULY build update.
Just tested it right now.
Cheers and enjoy!
Sweet! Lol I'm normally ok with playing guinea pig for these things but I guess this time I don't have to
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
29
So what is this? This is a Magisk module that adds the following features to any Pixel 3, 4 or 5 device running on Android 11:
- Forces Google Sans font system wide
- 63Accent colors
- 12Icon shapes
- 22Fonts
- Wallpapers Breel 2019; 2020 & 2020a
- 9 different Dark Styles
- Adds 2 button mode navigation (it was removed on Android 11 but I think some users like that navigation mode, so I add it)
- Background Blur options
- Blur Intensity options
- Adaptive sound options
- Navigation bar options (hide pill, reduce keyboard bottom space size, hide assist handles)
- SystemUI Tuner options
- Rounded corner options
- QS Rows x Columns options
- QS Footer Drag Handle options (Default, Accent based, Hidden)
- Option to show more icon notifications on staus bar
- Forces Basic Attestation thus making ctsProfile true by just enabling Magisk Hide
- Rom Control app (to setup all options available that you cannot using just Styles & Wallpapers)
Everything can be controlled using Styles & Wallpapers and also Rom Control app.
This MOD will probably work on any AOSP, or close to it, ROMs.
Get it here: Android_11_Addon_Features_for_Pixel_V8.zip
Just a note, this module already includes a SafetyNet fix, so if you're using another module for SafetyNet, please remove it since I don't know if that couldn't cause issues.
For all users already running Android 12 please go to THIS THREAD.
Addon Features EXCLUSIVE for Pixel Devices running on STOCK Android 11 ROM:
These exclusive and specific for Pixel Devices running on STOCK Android 11 ROM Magisk modules that you'll see next adds all of the features stated above but with extra goodies!
"Exclusive features" included:
- Battery Bar
- Battery Styles
- Clock Customization
- Corrected lock screen icons not changing after applying different theme
- "Disco Dingo" the QS (just a funny name for the option to apply random colors on QS toggles)
- Hide QS Labels
- Lock screen album art customization
- Lock screen camera shortcut (enable/disable)
- Lock screen custom clock faces
- Network Traffic Indicators (unfortunately, on redfin, it only works on QS Header and not on status bar)
- QS Battery percentage independent options
- QS Header opacity level control
- QS Headers styles
- QS Panel opacity level control
- QS Tiles styles
- QS Data usage info
- QS Rows x Columns options (both on portrait and landscape modes)
- Reduce Status bar height (and correct left padding on devices with the notch on the left)
- Removed side assist handles from lock screen
- Status bar Quick Pulldown (Never, Right pulldown, Left pulldown, Always)
- Switch styles
- Touch QS Labels to add or remove on QS customize panel (just didn't bothered to translate "Tap or Drag Tiles..." strings, so you'll continue to see "Drag Tiles..." but the feature is there, try it.)
Exclusive features downloads:
Android_11_Addon_Features_For_Pixel_V13.zip -> "Harmless" module that works on any Pixel device running on STOCK ROM, much like the "universal mod" shared above, but with a Rom Control app version that has more options. The "exclusive features" options won't do anything if the SystemUI module, shared next, isn't installed. If your going to try these exclusive features module, install this one and not the one shared above. The SaftetyNet is also included on this module, so once again, don't try to use any other SafetyNet module since it could break things.
Android_11_SystemUI_redfin_workaround_for_Addon_Features_V10.zip -> This is "THE" module! This module adds all xml and smali changes into SystemUI. Without this module the "exclusive features" won't work. Also, this module could be responsible for breaking boot if it fails to work at your end. I've ran several tests on my device (a Pixel 4a) and didn't face any issues but, since this module replaces stock SystemUI for a modded SystemUI, you could run into problems if some other module tries to do the same or it's simply incompatible with it. This module was updated to match latest Android 11 October 2021 build.
Android_11_SystemUI_redfin_workaround_for_Addon_Features_V9.zip -> Use this version ONLY if you're still running any Android 11 build between June and September 2021!
Notes regarding the "exclusive version" for Pixel devices:
- DO NOT, I'll repeat, DO NOT flash "SystemUI module" zip on any other ROM besides stock. It won't work! If you want those extra features on your current ROM you will have to port them yourself. I explain how to later on this post.
- Make sure that you're able to run adb shell as root before rebooting your device.
- If something goes wrong after flashing "SystemUI module", like if your device doesn't boot or something stupid, connect your phone to your PC during boot and run this:
Code:adb shellCode:suCode: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 shellCode:magisk --remove-modules- If none of the above methods work to get your device booting, then you have to boot into safe mode. By doing so, Magisk will disable all modules for you (it doesn't uninstall them, just disables them). To force a boot into safe mode all you need to do is to keep pressing volume down button during boot animation. After the system boots into safe mode you can reboot your device to boot up normally (since all modules will be disabled). If you get stuck during boot animation again, just force another reboot (I've had to do that during my tests).
- The "SystemUI module" requires that your device is already updated to March build!
- When a new OTA update comes please don't flash the "SystemUI module" until I say it's ok to do so. I mean, me or any other member who may have tested it. Why? Because Google may change things on stock SystemUI between builds. When that happens, I have to recreate the module again to adapt those changes. For instance, March build was not compatible with the module that was built on top of February build SystemUI. Rest assured that I'll always test the module with new builds and update as necessary.
- In case your device gets caught in a bootloop, please provide me a logcat so I may try and look if anything can be done about it. To do so, during boot connect your device to your PC and grab a logcat with this adb command:
Code:adb logcat > log.txt
Requirements:
- Unlocked bootloader
- Magisk Root | Magisk Manager
Suggestion:
- Uninstall all other modules you may have installed IF you're going for the "exclusive features". They could be incompatible with the "SystemUI module" thus making the device get caught in a bootloop. You may install them afterwards, one by one, just to make sure everything is ok.
- If you're up to it, instead of disabling/removing modules, just flash latest stock build through fastboot. If you want to retain your data, remove the "-w" flag from the update command on flash-all script.
How to install? (If you're running a Pixel 5, just install the module...you don't need all these next steps)
- Uninstall Device Personalization Services updates
- Clear Google Play Store app data and cache
- Flash the Magisk Module(s)
- Reboot device
- Open Google Play Store and update Device Personalization services (or any other Pixel exclusive app you see it needs to update).
- Profit!
Video:
Check all Rom Control (with exclusive features) options HERE.
How's these "exclusive features" even possible?
All (well, not all but almost...) features that you see on Pixel Devices "SystemUI module" were reverse engineered from Evolution X ROM source code. The source code is available on the link bellow shown on the credits. This means that I've been practicing some hard core "old school" Android smali edition in order to get this working. So, yes, I have some credits about this but, if it weren't for the original developers and it's public source code, none of this would be possible. Thank them for this!
Smali, and xml, edition wasn't enough to get this working. After decompiling, changing/adapt the code and recompiling everything again, I had to find a way to make it bootable without messing with the original apk signature. And here is where VR Theme logic came in handy. So thanks for the original dev who brought us this feature.
As for ROM Control app....this was/is a project created by daxgirl and wubydax back in 2015! So yeah, I'm not bringing anything new here, I just followed their instructions in order to get the features working after editing smali/xml with the source code taken from Evolution X. The original app source code is also available on the link shared on the credits.
I've just combined all of the above into a Magisk Module and shared here so that we can get the best of both worlds....a stock ROM with custom features included.
Rom Control with "exclusive features" source code:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a
Want to port the "exclusive features" to your Pixel device running on other ROM? Here's how:
https://github.com/ElTifo/CustomSettingsForDevs/tree/Pixel4a/app/src/mods
Credits:
EvolutionX ROM team, specially @joeyhuab
@daxgirl and @Wuby986 for ROM Control project and source code.
@Tulsadiver for showing me how to adapt VR Theme logic originally used on 3Minit Battery Mod by @gharrington.
@Ticklefish for Tickle My Android
@topjohnwu for Magisk
@kdrag0n for Safetynet-fix.
@Freak07 for Adaptive Audio
Cheers and enjoy!13
Hello.
It's impossible to do that since the only "Universal" version of the MOD, that is, a version that should work on any phone running an Android 11 close to AOSP ROM is V8 as shared on the OP. That's why it has a separate download link.
The other addon features suffered changes from Google changes throughout the monthly updates, besides, those versions require the SystemUI module as well, otherwise, the Exclusive features won't work. And that other module only works on Pixel devices.
I've explained everything carefully on the OP, if you read it you'll understand that the changes made are at smali code level, thus, it cannot be installed on other devices rather then Pixel ones.
I've also shared an "how-to" port this exclusive features to any other device (including older Pixels).
------------------------- " " ---------------------------------
Now, regarding all of you that are using these MODs...I've came to understand that Google hasn't changed anything regarding SystemUI since June, which makes me believe that google is now more focused on bringing a stable Android 12 instead of tweaking Android 11 SystemUI (which means that I no longer have to stick around Android 11 just to update these MODs when needed).
Having this in mind, I've decided to move on to Android 12. This means that I won't be updating these MODs for Android 11 any longer, since I believe the next update (if not the next it will probably be the other next one) will be an update to stable Android 12. Therefore, I really think this is the end of line for Android 11 and for these MODs as well. You can still use them if you want to stick to 11, of course.
Obviously, and since I miss these features on Android 12, I'll try to make a similar module(s) for Android 12 when it's possible.
As soon as something cool comes up, I'll share with all of you.
Cheers!8Well, SystemUI MOD is really not compatible with June update.
Google introduced some changes that requires some lame edition (mainly the IDs are different...which sucks).
It's going to be a dull procedure but I'll try to do it as fast as possible.
Please wait for a new update. As soon as I do it, I'll share.
Cheers!
