Mastodawn

@thestrangelet RCS messaging is indeed a bit problematic right now. It used to work for the most part and then Google made some poorly documented changes to how they implement RCS which made it lose compatability and difficult to restore it. RCS works for many, but is still broken for some. Note though that there are also reports of RCS not working for some people on the stock PixelOS, so it isn't entirely related to GrapheneOS. The project has said that it's a priority of them to restore this compatability, so they are aware and working on it. To be sure though whether you have configured it in the way that makes it work for most at this moment, can you verify that you have set it up according to the instructions in the release notes of release 2025092700 ( https://grapheneos.org/releases#2025092700)?

Regarding Android Auto you are correct. It has downsides, which GrapheneOS just can't workaround. So it's there for compatability and people can then make an informed choice about the trade-offs. If I owned a car, I would do the same as you and opt to not use it.

GrapheneOS releases

Official releases of GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.

GrapheneOS

Show thread

tranquil_cassowary Feb 6

@rzeta0 @alberto

> I like that you can completely disable an app - not sure if main android does this.

Disabling apps is part of AOSP, so you can also do it on other Android OSes. But, GrapheneOS enables you to update an app when it's disabled and keeps it disabled while doing that.

> I use it to disable "loyalty shopping apps" until they are needed, so they don't constantly run in the background spying on you

I understand why you would do this but this is not needed most of the time. For time-sensitive permissions, like location, camera, microphone, there are grandular permissions that allow you to only grant it once or while in use (focused app). Other permissions aren't really time sensitive. For example, if an app has access to storage, it doesn't really matter if you only enable it from time to time, it can extract the data very quickly if it would want to. So disabling an app is most of the time not a good approach to preventing data exfiltration of any kind. I don't know what the loyallty apps you are referring to request specifically, that make you concerned about keeping the enabled, though. Curious about that.

> I'm currently having bugs with Android Auto for listening to books in the car but not sure whose fault that is.

Does it give you a bug report? Or is it just not functioning in the way you expect, and if so, in what way? Which app are you using for audiobooks specifically?

> note I don't use the NFC thing at all, never have, some say it is problematic on grapheneOS

The NFC hardware works and is completely supported by the OS. The reason many people have problem with NFC is because many want to use it for Google tap to pay. Google tap to pay implements the Play Integrity API, restricting its usage to OSes certified by Google. So, it won't work on GrapheneOS. But other apps using NFC for payment normally should work. If you are located in the US though, many banks rely on Google and Apple for payment and alternatives currently aren't really usable. If you are not located in the US, I recommend checking out Curve Pay. For the US, using a smartwatch from Garmin with Garmin Pay works, though.

tranquil_cassowary Feb 6

@thestrangelet
What was your reason for moving back and forth? Was there something missing from GrapheneOS from your POV? Was there something which could be improved? Bugs you encountered? Questions you didn't find the answer for? Would be happy to help in such cases, have been using it for 2 years.

Show thread

tranquil_cassowary Feb 6

@leopold
Quels sont vos buts? Si votre but est d'améliorer votre securité et du respect de votre vie privée, le choix est clair, GrapheneOS est la seule solution entre les alternatives que vous avez listées. Je peux vous expliquer pourqoi mais mon français n'est pas très bon donc vous devriez me permettre de répondre en anglais.

Show thread

tranquil_cassowary Feb 6

@frank
They won't release "their own phones". They have partnered with an OEM since June 2025. They are in active talks, which are going well, to help them meet the hardware requirements for a subset of their future devices. So, it will be a next generation of a phone from an existing Android OEM which will meet the security requirements, so GrapheneOS can support it. Still very exciting though. The OEM is not yet disclosed but it is a top 10 Android OEM and the phone will feature a flagship Snapdragon SoC.

Show thread

tranquil_cassowary Feb 6

@kgw
Well, it is better to stick with Vanadium from a privacy and security stand point, but maybe you have other consideration that push you towards Vivaldi?

Show thread

tranquil_cassowary Feb 6

@alberto
Yes. I'm using it for two years. Don't have any problems with it. For me, everything works. Recommend using the WebInstaller: https://grapheneos.org/install/web. Make sure the read the prerequisites properly. Tip: If you have another Android phone, use that to flash the Pixel, it's easier compared to using a desktop/laptop. Also, don't forget the post installation steps. If you have any questions regarding installation, you can visit the official community chat rooms or just ask here in the thread. The former is easier for help in real time though, evidently.

GrapheneOS web installer

Web-based installer for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.

GrapheneOS

Show thread

tranquil_cassowary Feb 5

@DL6PL
It will be supported normally in case it allows installing third-party OSes with all security features intact. In 2027, the OEM who partnered with GrapheneOS will release a phone which GrapheneOS will support, if all goes well. But, that will come to late for you, given that your Pixel 6 will be EoL soon.

tranquil_cassowary Feb 4

@pea
For Molly, this could be due to database lock. If the database is locked, you can't get notifications when you are using WebSockets for notifications. You can also use Molly with UnifiedPush (UP) or Firebase Cloud Messaging (FCM), and those normally allow you to receive notifications with a locked database and when your phone is in BFU (before first unlock) mode. That will be a general notification, telling you there is a new message in Molly, because the encryption can't give you contact or message content information. You can change the notification provider in the Molly settings. If you use FCM (which uses Google Play Services) or if you use UP (which uses a provider app like SunUp or ntfy), make sure to give Play Services and your UP provider app unrestricted battery.

For Deltachat, it also uses FCM: https://delta.chat/en/help#instant-delivery
So, make sure you have Play Services installed in the profile you are using Deltachat in and give Play Services unrestricted battery.

Delta Chat: FAQ

What is Delta Chat? Delta Chat is a reliable, decentralized and secure instant messaging app, available for mobile and desktop platforms. Instant creation of private chat profiles with secure and i...

Show thread

tranquil_cassowary Feb 4

@Schnack @kuketzblog

Hi, I follow the GrapheneOS hashtag and your post passed by. I translated it to English.

What do you mean with "direkt platt zu machen"? It translates to "flattening the Pixel" in English (lol).

Just wondering if there is some concern or question you have that I could help with. I'm a user for 2 years.

Mobile OS	GrapheneOS
Desktop OS	MacOS + ChromeOS