Pixel Props
The detectability of LSPosed by third-party apps raises privacy and security concerns, reflecting unprofessionalism. This issue arises as developers created a native detection project, removed it later, and witnessed the emergence of forks of the original…
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.
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.
Telegram
LSPosed
LSPosed 内部测试开始
LSPosed internal testing begins
echo aHR0cHM6Ly90Lm1lLytOZkh6dGZ5TkJaczJaRGxs | base64 -d
如果对内测群被封禁踢出有疑问,在讨论群询问管理员,不要私聊。
If you have any questions about being banned or kicked out of the internal testing group, please ask the admin in discussion…
LSPosed internal testing begins
echo aHR0cHM6Ly90Lm1lLytOZkh6dGZ5TkJaczJaRGxs | base64 -d
如果对内测群被封禁踢出有疑问,在讨论群询问管理员,不要私聊。
If you have any questions about being banned or kicked out of the internal testing group, please ask the admin in discussion…
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!
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!
Pling
PixelProps Beta
Welcome to the official PixelProps Pling page! This is where you can download the latest Pixel Beta props. These props are designed with a focus on functionality and compatibility.One of the key...
Pixel Props
Photo
Google banned the Pixel 9 Pro XL (komodo) fingerprint. I will be adding more in a couple of hours.
Pixel Props
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.
This media is not supported in your browser
VIEW IN TELEGRAM
Quick showcase of the upcoming pif scalping feature for non beta 😎
Edit: Available on Pling
Edit: Available on Pling
Redfin_UP1A.231105.001.B2.zip
24.7 KB
Pixel 5 - Redfin
redfin-user 14 UP1A.231105.001.B2 11260668 release-keys
redfin-user 14 UP1A.231105.001.B2 11260668 release-keys
Raven_AP3A.241105.007.zip
26.1 KB
Pixel 6 Pro - Raven
raven-user 15 AP3A.241105.007 12470370 release-keys
raven-user 15 AP3A.241105.007 12470370 release-keys
Shiba_AP3A.241105.007.zip
28 KB
Pixel 8 - Shiba
shiba-user 15 AP3A.241105.007 12470370 release-keys
shiba-user 15 AP3A.241105.007 12470370 release-keys
Husky_AP3A.241105.007.zip
28 KB
Pixel 8 Pro - Husky
husky-user 15 AP3A.241105.007 12470370 release-keys
husky-user 15 AP3A.241105.007 12470370 release-keys
Comet_AP3A.241105.008.zip
29 KB
Pixel 9 Pro Fold - Comet
comet-user 15 AP3A.241105.008 12485168 release-keys
comet-user 15 AP3A.241105.008 12485168 release-keys
Cheetah_AP3A.241105.007.zip
27.1 KB
Pixel 7 Pro - Cheetah
cheetah-user 15 AP3A.241105.007 12470370 release-keys
cheetah-user 15 AP3A.241105.007 12470370 release-keys
Tokay_AP3A.241105.008.zip
29 KB
Pixel 9 - Tokay
tokay-user 15 AP3A.241105.008 12485168 release-keys
tokay-user 15 AP3A.241105.008 12485168 release-keys
Komodo_AP3A.241105.008.zip
29.1 KB
Pixel 9 Pro XL - Komodo
komodo-user 15 AP3A.241105.008 12485168 release-keys
komodo-user 15 AP3A.241105.008 12485168 release-keys
Akita_AP3A.241105.007.zip
28.5 KB
Pixel 8a - Akita
akita-user 15 AP3A.241105.007 12470370 release-keys
akita-user 15 AP3A.241105.007 12470370 release-keys
Caiman_AP3A.241105.008.zip
29 KB
Pixel 9 Pro - Caiman
caiman-user 15 AP3A.241105.008 12485168 release-keys
caiman-user 15 AP3A.241105.008 12485168 release-keys
Were you able to pass Play Integrity and CTS Profile checks with the latest modules?
Final Results
33%
Yes (share it)
17%
No
49%
Haven't tried
Pixel Props
Were you able to pass Play Integrity and CTS Profile checks with the latest modules?
Alright this poll did summarize the current status of our solution, in order to pass the Device integrity you must match with the module SDK for non Beta. In a few days Google will be able to ban/revoke most if not all shared keyboxes (online), That will mean the only solution will be the same as it was years ago. Spoofing system properties and relying on Basic or Device integrity. Remember that when Pixel Beta releases will be closed you might only be able to pass Basic. To pass Basic you need to have a working SElinux status. Otherwise there is still a possibility for PIF to be used and pass Device but no Strong. The same goes for TrickyStore, only with broken TEE status it could be semi-useful.