PixelXpert-Next

Channel name was changed to «PixelXpert-Next»

canary-501 released in canary channel

Changelog:
- Allow magiskd to interact with priv-apps targetting API 36
- Stable release

6.0.0 released in stable channel

Changelog:
- Its PixelXpert-Next time!
- Support now for Android 17QPR1
- Resolve Android 17QPR1 background camera restrictions + power button detection
- xposed: Rectify scope list for Android system
- RecordingMessage: Suppress call-{recording,notes} TTS
- Fix lockscreen double tap to sleep gesture support

Hey everyone! The development of PixelXpert has been restarted on a fork. The basic principles of the project will remain the same and Siavash and the other devs will be around in whatever capacity they'd like to be. For now, the focus of the project is to get features that were broken in a17 past the shutdown announcement working and then proceed to re-add removed features (if its possible)
I'll still consider new feature ideas and as usual, builds are always going to be opensourced and built on GH!

To reflect that I'm going to be building it (and not Siavash), the project has been renamed to PixelXpert-Next (totally didn't steal the name from a joke)

Since all supported Pixels are GKI, there is now a change in supported root solutions to only KSU (and sane/reliable forks) and the README has also been updated to reflect that.
The latest canary supports Magisk but I haven't personally tested it so proceed with caution

A massive shoutout to Siavash for allowing me to continue it and obviously the legendary development he's done till now ❤️


- Anirudh

Hi again

Referring to https://t.me/PixelXpert_Discussion/89843, this channel is now transferred to @anirudh109

Hi everyone,

We started working on PixelXpert (formerly AOSPMods) back when Android 12 was the latest thing on Pixel devices—was it the Pixel 6? Honestly, I don't even remember anymore.

Back then, modding was done in a different way. We had to decompile Pixel's SystemUI code, modify it, recompile it, and ship it out. Every single month, a new update would release and we had to do the whole thing all over again.

Then we shifted to Xposed and LSPosed. It was widely available, the Android source code was easily accessible, and almost everything was standard Java. Because it was straightforward Object-Oriented code, we could easily use LSPosed to hook into running processes and change whatever we wanted. We knew exactly what to expect, and monthly updates or device differences didn't really complicate things.


Things changed:

First, Google pushed everyone toward Kotlin and Jetpack Compose. Kotlin introduces functional programming features that Java doesn't natively support, so during compilation, the compiler has to "invent" complex structures under the hood to make it work. This results in deeply nested code blocks and unpredictable runtime signatures. Jetpack Compose makes this even worse with endless layers of compiler-generated wrappers. It runs fine on your phone, but it's a total nightmare for Xposed modding. It makes reliably hooking into runtime processes incredibly difficult, and lately, some mods have become totally impossible.

Second, the LSPosed team stopped public development a while ago. While there are some forks and limited testing groups around, the framework just isn't as open, stable, or universally available as it used to be.

Finally, Google is dropping updates faster than ever —they even added a Canary channel— but they've limited releasing official Android source code to 2 or 3 times a year. That leaves us working with outdated sources. Our only option is reading decompiled code, which is heavily optimized and obfuscated at compile-time, making it incredibly hard to reverse-engineer.

To sum up: up-to-date source code is hard to get, Android has shifted to heavily optimized machine-generated code, and the Xposed infrastructure isn't reliable enough anymore to justify the massive time investment.

Because of all this:
we are shutting down the PixelXpert project indefinitely.

We just can't bear the pressure of reverse-engineering such highly complicated, hard-to-get code on a fragmenting framework anymore.

Over the past 5 years or so, a lot of brilliant developers contributed to PX. The list is way too long to write out here, and it would be unfair to leave anyone out, but you can see all of them in the contributors' section on our GitHub page. Huge thanks to every single one of them for the time and energy they gave to the modding community.

We also want to thank all the users who suggested features, shared ideas, and helped us test the canary versions. We really appreciate you.

It wasn't all for nothing, though. We had a great time modding Android together and made some awesome friends along the way, which is priceless.

Hopefully, the kind of features PX offered will just become standard in future Android versions.

Yours,
The PX Team

canary-499 released in canary channel

Changelog:
- Reverted some unintentional changes

canary-498 released in canary channel

Changelog:
- fixed compatibility with official LSposed. (For reasons unknown to me, they prefer to block remote activation. So, from now on, no automated activation for you: do it yourself. Do let me know if you managed to understand their mindset)

NOTICE: canary 497 only works on Lsposed Vector - Other users please don't install this update

canary-497 released in canary channel

Changelog:
- Fixed PX boot-looping in certain conditions

canary-496 released in canary channel

Changelog:
- A17qpr1b4: Fixed icon transparency (I couldn't make a fix, but Gemini could!)

canary-495 released in canary channel

Changelog:
- A17QPR1b3: Fixed statusbar gestures
- A17QPR1b3: Fixed Screen gestures and related system UI crash
- Added option to hide navigation bar insets (Thanks to eXtreames@Github)