PixelXpert-Next
3.56K subscribers
3 photos
500 files
42 links
[MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+

GitHub: https://github.com/anirudhgupta109/PixelXpert-Next
Download Telegram
6.0.6 released in stable channel

Changelog:
- Fix hiding statusbar icons (NOTE: some icons are now in jetpack compose and can not be hidden)
- Fix Quick QS Panel pulldown gesture
- Fix notification default expansion
URL: https://github.com/anirudhgupta109/PixelXpert-Next/releases/tag/v6.0.6
๐Ÿ”ฅ3
with these two releases, both canary and stable are on the same status and codebase and can be used interchangeably on anything (Android 17, QPR1, QPR2)

i would still prefer if you use canary only on android betas so that you don't update to a bootlooping/crashing build in the future

also the XDA post to farm some karma: https://xdaforums.com/t/mod-xposed-magisk-ksu-android-17-qpr1-compatible-pixelxpert-next-system-modifications-for-pixel6-11-phones.4800391/post-90748893
๐Ÿ”ฅ7๐Ÿ‘1
I guess i've neglected magisk users for too long (honestly though, why do people still use it)

build is to use the magisk sepolicy live patcher alongside the boot patcher to hopefully fix some magisk permission issues as well as bring back shuffle pin to QPR2 Beta (i dont know if it works on September Stable, ya'll can flash and report back if it does, p11 still doesn't have a build, I WILL NOT BE RESPONSIBLE FOR LOST DATA)


i risked losing my data thrice during this when i jumbled my pin and the device forgot which number is where ;-;
๐Ÿ‘7๐Ÿ”ฅ3
tldr: easy unlock fixes can wreck data if it's incompatible in future updates, say bye bye to fam pics

So since shuffle pin was fixed on compose keyguard, I was debating adding easy unlock fixes and found it was pretty heavy to add back
I really don't want to risk device decryption and possible loss of data on Android updates not being compatible (file-based encryption will wreck your data incase easy unlock glitches out) and so I'm not going to fix it for compose keyguards (the one on September stable and the QPR2 betas)
๐Ÿ‘8
Fixed EasyUnlock using the native android system method that @KieronQuinn told me the bypass to absolute GOAT โค๏ธ

we can now have a safe version of easy unlock!
๐Ÿ‘8๐Ÿ”ฅ4
IF YOU FLASHED CANARY-518 DO NOT REBOOT
FLASH CANARY-519 IMMEDIATELY!!!
๐Ÿ‘10๐Ÿ˜ก9๐Ÿ”ฅ1
6.0.7 released in stable channel

Changelog:
- Optimize Magisk install scripts and remove unnecessary files/functions for KSU/APatch
- Fix shuffle pin for compose keyguard (the one on android betas and the new September Stable)
- Use the inbuilt easy unlock for all pin lengths (system one restricts it for only >=6 digits)

URL: https://github.com/anirudhgupta109/PixelXpert-Next/releases/tag/v6.0.7
XDA: https://xdaforums.com/t/mod-xposed-magisk-ksu-android-17-qpr1-compatible-pixelxpert-next-system-modifications-for-pixel6-11-phones.4800391/post-90754709
๐Ÿ”ฅ5๐Ÿ‘2
The app has transitioned to user app instead of being in priv-app (system app), your preferences will carry forward to the new user app but granting lsposed permissions and root grant will be needed again after reboot followed by a reboot because hooking into Android system

(obviously only needed for this update, future updates will be handled automatically as usual)
๐Ÿ”ฅ8๐Ÿ˜ก1
6.0.8 released in stable channel

Changelog:
MANUAL FLASHING IS REQUIRED FOR THIS BUILD!!!!
RE-GRANTING ROOT + RE-ENABLING IN LSPOSED IS NEEDED ON BOOT UP FOLLOWED BY A REBOOT TO HOOK INTO SYSTEM!!!
READ MORE ON XDA Thread!!!!!
- Switch PX-N from a system priv-app to a user app
- Add caffeine QS tile

URL: https://github.com/anirudhgupta109/PixelXpert-Next/releases/tag/v6.0.8
XDA: https://xdaforums.com/t/mod-xposed-magisk-ksu-android-17-pixelxpert-next-system-modifications-for-pixel6-11-phones.4800391/post-90756850
๐Ÿ”ฅ2๐Ÿ˜ก1
theres a qs tile and theres an option to integrate it with the gestures in misc settings
๐Ÿ”ฅ5๐Ÿ‘2
^fixes an edge case where PX-N could cause multiple hooks into SystemUI and when there is an update to SystemUI, PX-N's modifications are sent to all hooks casuing excess resource usage
ive also checked other places in the app and this was the only instance
๐Ÿ”ฅ2๐Ÿ‘1