The settings displayed probably/possibly won't stop it.

Presidential Alerts is likely the channel being used for this test⋮

GrapheneOS enables the toggle to turn off ALL alerts.

GrapheneOS.org

Casio Royale AE1200 FTW

Don't get an older phone, between the Pixel 6a and future 7a having such a low price to entry along with 5 years from release support it doesn't make sense to use a 5th Gen < device. Better ROI on current production devices.

6th Gen + recommended.

Our recommended devices from the FAQ:

https://grapheneos.org/faq#recommended-devices

Be sure to check https://endoflife.date/pixel too.

If you're gonna go out, do it with a bang!

#RapidUnscheduledDisassembly

Can't wait... #Starship

IVPN for Android is now available on Accrescent, an open-source app store focused on security and privacy. New updates will go live on the platform in sync with our Play Store releases. Note that Accrescent is in alpha, under development. https://accrescent.app

I dont find the search to be all that bad, the issue I have is interacting with a result and pressing/going back only to lose the search and where you were, being back at the general feed.

Or save yourself the hassle and move to #GrapheneOS on a Pixel 😉...

grapheneos.org

#[0]

I run a 6a purely because I preferred the Pixels for their smaller screen/size. 😁

I do, isolated to a secondary user. Owner profile stays 'clean'. Anything you want to know?

GrapheneOS user here 😉😜 daily driven since the Pixel 3.

Look forward to your questions if you have any, nice to connect with you both.

Thats great, good to connect. 👍

Thanks to GrapheneOS' Sandboxed Play Services you DO NOT need to sacrifice convenience or usability.

If you are thinking you'd need to stick to stock for this reason and removing Google completely isn't your focus then using our Sandboxed Play Services is all a plus.

Read more here:

https://grapheneos.org/usage#sandboxed-google-play

99% app compatibility with all the security and privacy improvements.

All funcionality of the TSU and GXP in the Tensor chips is retained. Google Camera works just the same allowing your use of the hardware you paid for without compromise.

The ONLY apps you can't use are Google Wallet due to Play Integrity API requiring the OS to be whitelisted and Android Auto due to it's awful invasive system level privilege requirements.

Yet where these can be securely enabled like Play Services through a fully researched and considered approach within the scope of the project the dev team always endeavours to do so.

Any questions, concerns etc you know where to find me.

MetropleX (GrapheneOS Community Moderator)

Let's hear that cheer... 😄

#[0]

Shorts on for the first time this year...

Not personally, however Google will often certify authorised third party repair centres. If you can find out if one exists in your locale ask them if they can help or recommend someone if it is out of scope for their operation.

If and it is a BIG if, you can find a competent repair specialist they will need to transfer the following to a new logic board...

Storage + Titan M + SoC + TEE and for them to all be paired up together.

If you can't due to the encrypted at rest nature of the storage it will be impossible to be recovered.

Bangles fan?

Have decided that:

Ende-zu-Ende-Verschlüsselung

Is better than:

End to End Encryption

Pleased you're considering GrapheneOS for your device.

While what you use is your perogative, if you are looking at the OSes due to being concerned about security/privacy and that being a focus of your decision making, the following should be taken into account.

GrapheneOS and CalyxOS are much different. GrapheneOS is a hardened OS with substantial privacy and security improvements:

https://grapheneos.org/features

CalyxOS is not a hardened OS. It substantially reduces security. It recently went 2 months not shipping standard security patches.

Compatibility with Android apps on GrapheneOS is also much different. GrapheneOS provides our sandboxed Google Play compatibility layer:

https://grapheneos.org/usage#sandboxed-google-play

Can run the vast majority of Play Store apps on GrapheneOS, but not CalyxOS with the problematic microG approach.

CalyxOS is closer to LineageOS they both share the same issue above and they both always use multiple Google services too while giving them privileged access even if users don't use microG. It would be wrong to imply they don't use Google services. microG is of course an implementation of Google services. GrapheneOS doesn't use Google services by default.

To clarify further they always use Google services even without microG. They use Google for connectivity checks, network time, attestation key provisioning, SUPL, DNS fallback (LineageOS only), PSDS (Pixel 6 and 7), eSIM activation and more enabled by default.

https://blog.privacyguides.org/2022/04/21/grapheneos-or-calyxos/ is a 3rd party article explaining some of the substantial differences between GrapheneOS and CalyxOS. It's a common misconception that they're similar. CalyxOS is far more similar to LineageOS than GrapheneOS. There are many other alternate OSes available.

https://privsec.dev/posts/android/choosing-your-android-based-operating-system/ is another article about privacy and security differences between alternative Android-based operating systems.

If you have any questions/feedback though you know where I am, always happy to help. I look forward to reading your conclusion. Take care.

Correct, regards the Pinephone:

Pinephone has no secure element. Lacks secure element features deeply integrated into Android Open Source Project such as the hardware keystore, disk encryption key derivation throttling and insider attack resistance for the secure element. GrapheneOS makes even more use of it.

Pinephone has almost none of the expected hardware security features. It has an insecure SoC configuration, no secure element, no capability of providing Wi-Fi anonymity, no possibility of providing proper security support due to the chosen components and further problems.

Pinephone is not open hardware and doesn't have open firmware despite many misleading claims about it. There's no open source baseband firmware available but rather an open source OS for loading proprietary baseband firmware.

The Pinephone baseband with the open firmware is really no more open source than a mainstream Android phone with an open source rild and other services in the OS. It's presented as a breakthrough and unique feature but what's being replaced doesn't exist on a mainstream phone.

GrapheneOS priority is avoiding the device being compromised in the first place. Pinephone has very poor hardware, firmware and software security. Radio firmware can't be kept properly updated. Operating systems for it lack modern security model with proper sandboxing and MAC/MLS, etc.

We're unwilling to make substantial security sacrifices to have broader hardware support which is why we focus on Pixels. Pixels offer far better security than other Android phones and the Pinephone offers far worse security than a typical Android phone which is why for example we can't support it.

Thats correct and anyone who wants to know more can check out https://grapheneos.org/usage#sandboxed-google-play