Generally, I report bugs but I afraid from openly revealing all the information and details, I don't know why it just doesn't feel comfortable on public group.

So yea, I'm gonna write everything freely today as a feedback

1. The misunderstanding problem

Long ago I reported that the QS jitters because of Device Health Services
The solution implemented was removal of Health Intelligence Prebuilt 😭😭
Device Health Services is TurboPrebuilt
This problem still exists, read below for detailed information

Once again few days ago, I reported about sysconfig and suggested an asi fix, which also resolves magic eraser functioning, my suggestion was to shift to Pixel6 spoofing and import 2021, 2021 midyear sysconfigs only.
But Pixel8 spoofing continued and 2021, 2022, 2023 all sysconfigs were imported into the gms repo 😭😭
Also not blacklisted these newly imported configs on PiHooks
I've already tested this and it causes problems
even pixys dev did tests on this specific situation iirc
and now pixys gms only includes 2021 sysconfigs

2. My Problem with Pixel8 Spoof

gms loads tensor bloat flags, configs
breaks magic eraser, as pixel8 uses different procedure to provide that functionality (my theory*)
other issues which I can't recall right now

3. We don't need to spoof ASI/Turbo [tested*]

ASI loads features ondemand, whenever required, if we have the right sysconfig, proper asi package installed, It just works
Whenever a Pixel app tries to utilize ASI service it loads up.
For eg. Cinematic Walls trigger resource download if we have proper device config overrides and proper asi package loaded

Turbo (DeviceHealthServices) is no longer a pixel-exclusive package, infact it's now found on non pixel devices.
As per my testing battery estimates outputs faster if we don't spoof the package
Also better adaptive brightness management

4. The problem with Device Health Services

https://github.com/PixelOS-AOSP/frameworks_base/commit/6a8994eb66bd69388a579bf85161078c0f50d06a
This change makes a request to fetch the battery estimates.
My problem is that it creates a very minor qs jitter, and my theory is that it makes request to Turbo on pulling QS
If we build with and without this commit, record videos, slow-mo them, the difference is noticeable
Suggestion: Either get rid of it OR use hardcoded workaround to fetch the data and replace the text whenever the mini qs is pulled, then there will be no request made on pulling the full qs which might fix the jitter.

5. We don't need AiCore GMS Package

The package right now just sits idle and do nothing, required to be spoofed as P8-Pro in order to work
We don't need it because it eats a lot of RAM and creates weird problems while multitasking (also confirmed by Pixys dev)
As per my testing I keep 7-10 apps in background all the time minimized, after the functioning of this, I could only keep 3-5 apps, and the initial app opening time was increased
The value it delivers in return is not worth the effort
Since small features are already covered by ASI, for eg. ASI is already able to suggest GBoard replies on PixelOS from long time now

6. We don't need tons of device configs overrides

Image description

This one creates annoying bubbles at top even when system apps utilize location, and the location bubble gets static all the time, when you use rules feature, it's damn annoying
In order to get this resolved, we can completely remove this and rely on old statusbar icon that aosp still includes ig, or we can create blacklist to fix issues with specific system applications
and also YES the that last second config obviously didn't worked in my testing

After this

We also don't require smartspace device configs, gms is smart enough to enable them when required and I tested it, there's no difference
Same for Live Captions, this feature is now rolled out to non pixels, ASI loads it by default, but yes we still need this one "Captions__enable_augmented_music" ig.

7. Some issues gets no coverage

The Pixel Launcher crashes on opening settings pages from search results
There's a temporary workaround, which I suggested
I accept that such workarounds are not production ready, but until we find out the right way to do it, we can utilize it.
Let's face it and accept it, we already use hacks/workarounds to get the Pixel thing work :)

Thank you for reading whoever you are, I really wanted to convey these points to the team for once, please no offence to anyone, just a general feedback and write-up.