Punkt. MC02 phone doesn't run GrapheneOS. It still runs a fork of Android 13 while GrapheneOS is solely based on Android 15. MC02 is clearly using the LineageOS update client, not the GrapheneOS update client. It's problematic that some people think it's a way to get GrapheneOS.

nostr:npub1q8w7u2ymrghfpp6v5dpg57jpgaj2djk340a2npwzq8n64ksk6wxq8aw95u Definitely no for the most part since this only shipped on October 28th in iOS 18.1 and there are much older versions included in the screenshots such as iOS 16. It is possible a small portion of it was because of this. It appears they reboot the default 4 days after it was locked in iOS 18.1.

Can you see the rest of the thread over the bridge?

https://grapheneos.social/@GrapheneOS/113450097776800819

nostr:npub193pcsgj0mn2s7f898j4eh2j2kczlpplg93zcwq6swf5s7venzz5sgmm5gn That one wasn't written by them and it's not yet clear what they're going to do with it. If they could change the license, they probably would.

nostr:npub193pcsgj0mn2s7f898j4eh2j2kczlpplg93zcwq6swf5s7venzz5sgmm5gn It's not possible to change from a pre-existing copyleft license without permission from every contributor or somehow removing all their code and all code based on it which is not practical since who knows what got based on it elsewhere. AGPL also prevents them introducing code under their own heavily restricted non-commercial usage license. They could theoretically pay the contributors and relicense the code though.

iOS 18.1 was released on October 28, 2024. This has nothing to do with recent news coverage where cops are blaming imaginary features for devices not staying in After First Unlock state. Devices likely crashed due to one of many bugs which exist, including already patched ones.

iOS 18.1 added an implementation of the auto-reboot timer for locked devices we've been using in GrapheneOS since June 2021:

https://chaos.social/@jiska/113447894119816217

This was one of our early generation protections against forensic data extraction. We added a lot more protections this year.

It's not hyperbole to say that FUTO has caused millions of dollars of damage to GrapheneOS with the fabrications and spin they're still actively spreading about us. Any developer offered money by them should be aware of what happens if you don't promote them and tolerate abuse.

FUTO made a $40k donation to GrapheneOS supposedly with no strings attached. They ended up being unhappy with us not making content with them and promoting them. They began supporting attacks on us and tried to destroy the GrapheneOS project. Recommend not taking money from them.

FUTO apps aren't open source but rather source available with heavy restrictions on usage:

https://github.com/futo-org/android-keyboard/blob/master/LICENSE.md

They're taking the place of real open source apps and making it less likely for viable options to emerge since people are going to use and contribute to these.

GmsCompatConfig version 148 released:

https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-148

See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.

Forum discussion thread:

https://discuss.grapheneos.org/d/17141-gmscompatconfig-version-148-released

#GrapheneOS #privacy #security #gmscompat

GrapheneOS version 2024110400 released:

https://grapheneos.org/releases#2024110400

See the linked release notes for a summary of the improvements over the previous release.

Forum discussion thread:

https://discuss.grapheneos.org/d/17094-grapheneos-version-2024110400-released

#GrapheneOS #privacy #security

nostr:npub1ak5kewf6anwkrt0qc8ua907ljkn7wm83e2ycyrpcumjvaf2upszs8r0gwg This sounds like an app bug causing a compatibility with Android 15. It's very unlikely that it has to do with GrapheneOS unless you have the Network permission disabled for the app.

We're working on fixing a regression in the GrapheneOS releases based on Android 15 which resulted in a subset of users having a subset of their Network and Sensors toggle settings not migrated over from the Android 14 permission database to the Android 15 permission database.

nostr:npub1rcr8h76csgzhdhea4a7tq5w5gydcpg9clgf0cffu6z45rnc6yp5sj7cfuz nostr:npub1hxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3q4sg75y It should reach the Stable channel later today. All known important regressions are fixed.

GrapheneOS version 2024102100 released:

https://grapheneos.org/releases#2024102100

See the linked release notes for a summary of the improvements over the previous release.

Forum discussion thread:

https://discuss.grapheneos.org/d/16637-grapheneos-version-2024102100-released

#GrapheneOS #privacy #security

GrapheneOS based on Android 15 will reach the Stable channel later today. It's very stable already and we've fixed a bunch of upstream bugs including several impacting the stock Pixel OS. We've made 7 official releases based on 15 already and the 8th is going to reach Stable.

GrapheneOS version 2024101701 released:

https://grapheneos.org/releases#2024101701

See the linked release notes for a summary of the improvements over the previous release.

Forum discussion thread:

https://discuss.grapheneos.org/d/16537-grapheneos-version-2024101701-released

#GrapheneOS #privacy #security

We're preparing the changes for a new release of GrapheneOS based on Android 15. We've implemented over a dozen fixes, largely for new upstream issues impacting the Android Open Source Project. We also added a workaround for the new stock OS Android 15 factory reset protection.

Android 15 is being released today and we should be ready to quickly ship a release based on it as if this is a monthly update, not even a quarterly one.

We already put together builds working well across all supported devices based on the Android 15 Beta and September sources.

There's a highly inaccurate article about Pixels from Cybernews making the rounds everywhere in privacy communities. It gets the details nearly completely wrong and thoroughly misrepresents things like the optional network-based location used nearly everywhere as Pixel specific.