Google is quite simply deliberately leaving Pixel and even Android users (from other manufacturers) vulnerable to security attacks.
Google’s Pixel smartphones are specifically taken care of, in terms of security updates via
Pixel Update Bulletins, e.g. for September 2026, in the following listing:
https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01
Other Android users, e.g. Samsung, Sony, Motorola, etc obtain their security patches according to the listings within a link called Android Security Bulletins, in this case for September 2026 under the address:
https://source.android.com/docs/security/bulletin/2026/2026-09-01
Currently THE privacy and security gold standard smartphone operating system is GrapheneOS, which is only available for Pixel smartphones at this moment, where it will be also available initially on the 2027 Signature Series flagship Motorola phone at some point in time in the future.
Information has been leaked, that Cellebrite’s (smartphone hacking) hardware cannot obtain data from an up to date GrapheneOS supported Pixel phone in a BFU (Before First Unlock) state, that is encrypted and with a strong passcode.
A key component of the security of the smartphone is something called MTE (Memory Tagging Extension), where it was concluded that Google did not incorporate or disabled this hardware function in the new Pixel 11 series smartphone.
Therefore it can be deduced that Google is ‘deliberately’ weakening the security of their smartphones, in order for the 5 Eyes authorities (and Israel) to gain access to the phones (?), where after all, it is subservient within the domain of the 5 Eyes ‘Anglo Sphere’ global surveillance network.
In order to further weaken the security of Android, Google does not release security patches in a timely manner as it did once before.
‘Luckily’ for GrapheneOS users, the small developer team can produce better security patches than a multi-billion dollar corporation.
People running corporations in this manner know full well that the law takes a while to catch up to their ‘shenanigans’ and exploit this fact.
See GrapheneOS' post in relation to this problem
within the link:
No comments:
Post a Comment