[MOD][Xposed+Magisk][13 Compatible] AOSP Mods - System modifications for AOSP-based Android 12+

[binoysankar]

Try rebooting?

Facing this issue from past few days and i would have restarted during this time more than once already...
Also i tried uninstalling and reinstalling the module again still not working. I know its an issue with me only but i don't know how to resolve it.
I wanted to try another wifi and see if this is issue with my wifi network. Except this wifi is working great actually.

 

[roirraW "edor" ehT]

Facing this issue from past few days and i would have restarted during this time more than once already...

I was on Canary 173, but I just updated to Canary 179 (still on the November 2022 Pixel 7 Pro firmware), and rebooted, but with build 179, I actually havie a more serious issue where the screen keeps blanking out on the lockscreen, and eventually reboots. I was able to use:

adb wait-for-device shell magisk --remove-modules

to remove all Magisk Modules. I repeated installing the Systemless Hosts and Universal SafetyNet Fix v2.3.1 MOD 2.0, and also again AOSP Mods Canary 179 using the same installer previously downloaded, and once I gave AOSP Mods root access, it once again started blanking the screen repeatedly until it reboot.

Occasionally if I let it reboot enough times, it would go to the Android Recovery screen, but just choosing "Try Again" instead of "Factory Data Reset" would reboot "normally" (albeit with the screen blanking and eventual crash, until I disable all Magisk Modules).

I'm back up on Canary 173 fine right now. If I had more time, I would try re-upgrading in case it was just a corrupted download, but I might do so in the morning unless someone else confirms the same issue in the meantime.

So I can't get far enough to be able to confirm your same issue on Canary 179. It is working fine on Canary 173, and the Stable 2.4.0 before that.

 

[SuchiruDoragon246]

P6 dec. Update & latest aospmod canary build, system ui crashes after taking a screenshot

Same issue here. P7P Decemebr build running latest aospmod stable build. Guess it wasn't the network indicator after all. Seems to have stopped if I turned off both "disable screenshot sound" and insecure screenshot settings.

Right now the only option I have enabled is the Google Sans system-wide font which isn't giving me problems at the moment.

 

[binoysankar]

Any help on this. With wifi on and wifi off (sim data on)

Finally i resolved my issue by adding private dns of google...

 

[Thebear j koss]

I was on Canary 173, but I just updated to Canary 179 (still on the November 2022 Pixel 7 Pro firmware), and rebooted, but with build 179, I actually havie a more serious issue where the screen keeps blanking out on the lockscreen, and eventually reboots. I was able to use:

adb wait-for-device shell magisk --remove-modules

to remove all Magisk Modules. I repeated installing the Systemless Hosts and Universal SafetyNet Fix v2.3.1 MOD 2.0, and also again AOSP Mods Canary 179 using the same installer previously downloaded, and once I gave AOSP Mods root access, it once again started blanking the screen repeatedly until it reboot.

Occasionally if I let it reboot enough times, it would go to the Android Recovery screen, but just choosing "Try Again" instead of "Factory Data Reset" would reboot "normally" (albeit with the screen blanking and eventual crash, until I disable all Magisk Modules).

I'm back up on Canary 173 fine right now. If I had more time, I would try re-upgrading in case it was just a corrupted download, but I might do so in the morning unless someone else confirms the same issue in the meantime.

So I can't get far enough to be able to confirm your same issue on Canary 179. It is working fine on Canary 173, and the Stable 2.4.0 before that.

179 is only compatible with December update. If using anything else stay on that build.

 

[roirraW "edor" ehT]

179 is only compatible with December update. If using anything else stay on that build.

Thanks much! I should've thought of that consideration. I appreciate it.

 

[Thebear j koss]

Thanks much! I should've thought of that consideration. I appreciate it.

It should be in the changelog in the app as obviously not everyone is in the telegram group. Just to keep everyone up on what I know from the group, it is going to take a week or more to sort out all the changes from Nov to Dec updates. Be patient and stay tuned...<--- From telegram channel

 

[Ghisy]

Thanks much! I should've thought of that consideration. I appreciate it.

If you're still on November (like me), you can use 177. 178 & up require the December update. I did the same mistake (because I didn't see the warning on the Telegram channel) by updating to 178 but was able to downgrade back to 177!

I'm waiting until the dev adds what's missing and I will update to December. He says the system framework has changed a lot from Nov so it will take a few days at least.

 

[swieder711]

haven’t seen it here yet, so -- not "important", just reporting: the battery bar feature seems to be out of order as well with the december update. using aosp latest canary (177), still .. worked until android november update.

Came here to report the same issue with the Battery Bar feature not working on the Dec update. I really like this feature and look forward to its return.

 

[ekeppel]

What a fantastic module. I've really missed Gravitybox since it stopped receiving updates, and this mod is a very comprehensive replacement (and then some!)

I just wanted to say Thanks for all of your hard work!

 

[miklat106]

If you're still on November (like me), you can use 177. 178 & up require the December update. I did the same mistake (because I didn't see the warning on the Telegram channel) by updating to 178 but was able to downgrade back to 177!

I'm waiting until the dev adds what's missing and I will update to December. He says the system framework has changed a lot from Nov so it will take a few days at least.

How did you downgrade? You just flashed November's file instead?

 

[Ghisy]

How did you downgrade? You just flashed November's file instead?

Despite the constant system framework FC, I managed to get into LSposed, disabled the module then rebooted. After that, I uninstalled the AOSPMods module in Magisk, rebooted again. Then flashed v177 in Magisk, rebooted, re-enabled in LSposed.

Since I had a back-up of AOSPMods settings, I restored it and bam! Back in business!

 

[siavash79]

I was on Canary 173, but I just updated to Canary 179 (still on the November 2022 Pixel 7 Pro firmware), and rebooted, but with build 179, I actually havie a more serious issue where the screen keeps blanking out on the lockscreen, and eventually reboots. I was able to use:

adb wait-for-device shell magisk --remove-modules

to remove all Magisk Modules. I repeated installing the Systemless Hosts and Universal SafetyNet Fix v2.3.1 MOD 2.0, and also again AOSP Mods Canary 179 using the same installer previously downloaded, and once I gave AOSP Mods root access, it once again started blanking the screen repeatedly until it reboot.

Occasionally if I let it reboot enough times, it would go to the Android Recovery screen, but just choosing "Try Again" instead of "Factory Data Reset" would reboot "normally" (albeit with the screen blanking and eventual crash, until I disable all Magisk Modules).

I'm back up on Canary 173 fine right now. If I had more time, I would try re-upgrading in case it was just a corrupted download, but I might do so in the morning unless someone else confirms the same issue in the meantime.

So I can't get far enough to be able to confirm your same issue on Canary 179. It is working fine on Canary 173, and the Stable 2.4.0 before that.

In the future try this

adb shell su -c "touch /data/adb/modules/zygisk_lsposed/disable"
adb reboot

 

[roirraW "edor" ehT]

In the future try this

adb shell su -c "touch /data/adb/modules/zygisk_lsposed/disable"
adb reboot

Thanks! I will note this.

 

[miklat106]

Despite the constant system framework FC, I managed to get into LSposed, disabled the module then rebooted. After that, I uninstalled the AOSPMods module in Magisk, rebooted again. Then flashed v177 in Magisk, rebooted, re-enabled in LSposed.

Since I had a back-up of AOSPMods settings, I restored it and bam! Back in business!

Sorry, I thought you meant that you downgraded the firmware, I misunderstood you.

 

[siavash79]

stable 2.4.x and canary 176 are the last versions for A12 and A13 up to Nov build.

Starting canary 177 and 2.5.0, the mod will only support A13 Dec+

 

[digger16309]

stable 2.4.x and canary 176 are the last versions for A12 and A13 up to Nov build.

Starting canary 177 and 2.5.0, the mod will only support A13 Dec+

Critical Info - hopefully placed in bold red text at the top of the OP.

I can see a lot of thread questions ahead about why the mod isn't working...

 

[AlkaliV2]

Hey Siavash79! I was doing some unrelated debugging in my logcat and I came across an error that was related to AOSP Mods. Wanted to provide the error in case it offered insight to anything. I have not activated any settings in the app yet, just have it installed.

Pixel 5
Stock Pixel December 13.0 Update
Activated with LSPosed 1.8.5 Zygisk (System Framework, Phone Services, Pixel Launcher and SystemUI)
Magisk 25.2

Spoiler

12-08 13:47:26.594  2674  2674 E LSPosed-Bridge: java.lang.ClassCastException: com.android.systemui.statusbar.phone.NotificationIconContainer cannot be cast to android.widget.FrameLayout
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at sh.siava.AOSPMods.utils.NotificationIconContainerOverride.calculateIconXTranslations(NotificationIconContainerOverride.java:129)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at sh.siava.AOSPMods.systemui.StatusbarMods$5.beforeHookedMethod(StatusbarMods.java:498)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at de.robv.android.xposed.XposedBridge$AdditionalHookInfo.callback(Unknown Source:79)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at LSPHooker_.calculateIconXTranslations(Unknown Source:8)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at com.android.systemui.statusbar.NotificationShelf.updateAppearance(NotificationShelf.java:913)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at com.android.systemui.statusbar.NotificationShelf$ShelfState.applyToView(NotificationShelf.java:26)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at com.android.systemui.statusbar.notification.stack.NotificationStackScrollLayout.applyCurrentState(NotificationStackScrollLayout.java:20)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at com.android.systemui.statusbar.notification.stack.NotificationStackScrollLayout$1.onPreDraw(NotificationStackScrollLayout.java:2493)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.ViewTreeObserver.dispatchOnPreDraw(ViewTreeObserver.java:1182)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3567)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2328)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:9080)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1231)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1239)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer.doCallbacks(Choreographer.java:899)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer.doFrame(Choreographer.java:832)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1214)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.os.Handler.handleCallback(Handler.java:942)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.os.Handler.dispatchMessage(Handler.java:99)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.os.Looper.loopOnce(Looper.java:201)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.os.Looper.loop(Looper.java:288)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at android.app.ActivityThread.main(ActivityThread.java:7872)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at java.lang.reflect.Method.invoke(Native Method)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
12-08 13:47:26.594  2674  2674 E LSPosed-Bridge:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Spoiler

12-08 13:49:17.826  2674  2674 E LSPosed-Bridge: java.lang.ClassCastException: com.android.systemui.statusbar.phone.NotificationIconContainer cannot be cast to android.widget.FrameLayout
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at sh.siava.AOSPMods.utils.NotificationIconContainerOverride.calculateIconXTranslations(NotificationIconContainerOverride.java:129)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at sh.siava.AOSPMods.systemui.StatusbarMods$5.beforeHookedMethod(StatusbarMods.java:498)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at de.robv.android.xposed.XposedBridge$AdditionalHookInfo.callback(Unknown Source:79)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at LSPHooker_.calculateIconXTranslations(Unknown Source:8)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at com.android.systemui.statusbar.phone.NotificationIconContainer.onLayout(NotificationIconContainer.java:63)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1891)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1729)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.LinearLayout.onLayout(LinearLayout.java:1638)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.RelativeLayout.onLayout(RelativeLayout.java:1103)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at com.android.keyguard.KeyguardClockSwitch.onLayout(KeyguardClockSwitch.java:0)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.LinearLayout.setChildFrame(LinearLayout.java:1891)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.LinearLayout.layoutVertical(LinearLayout.java:1729)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.LinearLayout.onLayout(LinearLayout.java:1638)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.GridLayout.onLayout(GridLayout.java:1219)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at androidx.constraintlayout.widget.ConstraintLayout.onLayout(ConstraintLayout.java:66)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.FrameLayout.layoutChildren(FrameLayout.java:332)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.widget.FrameLayout.onLayout(FrameLayout.java:270)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.View.layout(View.java:23700)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewGroup.layout(ViewGroup.java:6413)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl.performLayout(ViewRootImpl.java:3999)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:3372)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:2328)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:9080)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1231)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1239)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer.doCallbacks(Choreographer.java:899)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer.doFrame(Choreographer.java:832)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1214)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.os.Handler.handleCallback(Handler.java:942)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.os.Handler.dispatchMessage(Handler.java:99)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.os.Looper.loopOnce(Looper.java:201)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.os.Looper.loop(Looper.java:288)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at android.app.ActivityThread.main(ActivityThread.java:7872)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at java.lang.reflect.Method.invoke(Native Method)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
12-08 13:49:17.826  2674  2674 E LSPosed-Bridge:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:936)

Edit: Added additional log output I discovered further down.

 

[miklat106]

I had to reinstall the module and for some reason I can't find rhe option now to split the network tile. What am I missing?

Edit: Found it!

 

[totofe69]

hi everybody,
I tried to flash module on my sweet (redmi note 10 pro) but when i reboot, it stuck on screen "device starting"
I'm not only person with this issue.
Device : Sweet - redmi note 10 pro
Rom : Pixel Experience Plus
Android : 13
Magisk : 25.2 with zygisk and lsposed actived