Updated sensitive props v6.4.8.4, Changelog:

Moved boot.hash function to post-fs-data.sh
Project finally on GitHub :D
Other fixes..

Pling Download
GitHub ⚡️

Finally brought an update to build.prop (commit 1452c8a)
Check it out !

October Komodo Props updates are live on Pling!

What's new?:

- Automatic pif.json updates: Non-Beta builds now automatically grab the latest pif.json from chiteromans GitHub.
- Beta builds generate pif.json: Beta builds will try to create the pif.json file themselves.
- TrickyStore integration: Both Beta and non-Beta builds will add your package list to the TrickyStore target.txt file.
- Magisk Action Button: You will be able to do these actions on click.

I had updated the props once again, Now it should pass Strong. Still trying to figure out why exactly it cannot pass CTS profile meanwhile i am using the original Pixel Props... Google what are you doing?!

Has anyone else experienced issues with device CTS profile certification tests on the latest Android 15 beta releases? We're unable to pass them, which makes me wonder if Google is about to drop the official version and thus closing beta tests. 🤔

📦 New build.prop Update!
Commit: e662e476c

🔄 Changes in this update:

• Added SHA256 hash verification for module scripts
• Updated documentation for Android 15 Beta OTA links
• Improved module naming (*_Props)
• Optimized sysconfig file handling
• Removed unnecessary system properties
• Added planned support for Pixel.Features
• Enhanced module installation reliability

🛠 Technical improvements:

• Refactored directory processing
• Improved error handling
• Better module script verification

#Update #PixelProps #Magisk

📦 New Sensitive-Props update (v6.4.9-hexpatch)
Commit: 4a0cd7c26

🔄 Changes in this update:

• Added automatic busybox path detection
• Improved error messages and formatting
• Enhanced Magisk DenyList handling for Play Services
• Fixed path resolution issues
• Increased service interval to reduce system load
• Removed unsafe property modifications
• General code cleanup and stability improvements

⚠️ Remember to uninstall the module before dirty-flashing/updating your ROM!

📱 Requirements:
• Android 10+
• Magisk v26.3+
• KernelSU latest version
• APatch latest version

#SensitiveProps #Magisk #KernelSU #APatch #Update

Follow-up on LSPosed Team’s Actions and the Continuation of Their Project

28 Oct 2024:

Barely a year after my initial post on 15 Dec 2023, where I raised concerns regarding the detectability of LSPosed by third-party apps and highlighted the unprofessionalism surrounding it, significant developments have occurred. The LSPosed team, who had previously announced they would cease working on the project shortly after my post, has now reversed their decision and resumed development. This flip-flop move appears to be a calculated attempt to discredit my concerns and generate hate toward me, further exemplifying the lack of transparency and professionalism I initially pointed out.

Notably, this decision to continue development comes suspiciously right after the emergence of a popular fork of LSPosed called "LSPosed-Irena", which has gained traction in the community. It raises questions about whether the LSPosed team is trying to reclaim relevance by potentially basing their future work on this highly-regarded fork. The timing of these actions suggests a reactive, rather than proactive, approach to innovation and project management, continuing the pattern of questionable practices within the LSPosed team.

In light of these events, I reiterate the importance of discussing the implications this has on privacy and security. The detectability of LSPosed by third-party apps, which remains a core concern, continues to pose risks to users who rely on these tools for legitimate purposes. Additionally, the behavior of the LSPosed team in relation to the wider developer community — including spamming repositories, as I previously mentioned — reflects poorly on their commitment to fostering a healthy, collaborative development environment.

For those who may have missed the context, my initial post shed light on how the LSPosed team had, at one point, created a native detection project, only to remove it later after forks emerged. My attempts to address these issues were met with hostility, leading to my expulsion and banning from their group. This pattern of behavior, along with their recent actions, continues to highlight the need for accountability and professionalism in the development community.

As we move forward, it is crucial to remain vigilant and push for transparency, especially when projects like LSPosed have such widespread influence over user privacy and security. The emergence of alternatives like LSPosed-Irena is a reminder that there are better ways to govern these types of projects — ones that prioritize the community’s needs over personal agendas.

Let’s continue to advocate for a more open, secure, and professional development environment that upholds the values of transparency and user protection.

Thank you for your support and for continuing to engage in this important conversation.

I've added latest builds to Pling !

What changed?
From now on the PixelProps will have volume key selection by default on the Safe/Sensitive Modes. Else can be manually set on the module directory/config.prop

When using an older ROM make sure to set Safe SDK to true so that you don't break CTS Profile.

If you have bootloop issues set all of the Safe/Sensitive modes to true!

Google banned the Pixel 9 Pro XL (komodo) fingerprint. I will be adding more in a couple of hours.

Apparently the non beta can still pass strong as it downloads the pif.json from chiteroman GitHub.

Quick showcase of the upcoming pif scalping feature for non beta 😎
Edit: Available on Pling

Pixel 5 - Redfin
redfin-user 14 UP1A.231105.001.B2 11260668 release-keys