Comment by jordand
6 days ago
Makes sense for them to support this given their scale. I wouldn't be surprised if GrapheneOS secures another big Android OEM vendor (after Motorola Mobility) and the user base of the OS quickly grows from its current 400k+ to millions.
> after Motorola Mobility
Does anyone know anymore on that front? For months, I've regularly looked up whether there were any news, only to find nothing besides the original announcement. No ETA, no upcoming devices to be supported, heck, on the Graphene side, their own webpages make nary a mention. Would buy a Razr 70 Ultra + Clicks the second that is confirmed, but for something that was so publicly announced months ago, this seems very shaky...
I don't think we'll see it before CES in January.
At the time of writing, within ~12 months, in 2027, the 2027 Signature, Razr fold, and Razr flip will meet the hardware security requirements and should have official GrapheneOS support.
Motorola is currently porting GrapheneOS to their devices.
They're too busy pushing malware on the rest of their lineup in system updates left, right, and center.
silently re-enables com.glance.lockscreenM one more time on you...
I've been looking into GrapheneOS as a longtime Pixel user who is thinking of becoming a bit more security conscious. But, looking around at its current state RE: RCS and camera apps, I think it makes the most sense to stick with stock Android.
I also have a really niche feature I rely on daily (letting me "wifi call" from one sim over the data line of the other sim), and it's really hard to tell if GrapheneOS supports it.
If I can grab my old pixel that's stored in a box at my parents' house on another continent I might give it a try, but GrapheneOS really doesn't seem ready to be a daily driver.
What's the issue with RCS and camera apps? RCS works (from what i've heard) and you get the same image quality as on stock if you install the pixel camera app.
Not sure about that other feature you mentioned, but you can always revert back to stock if you don't like GOS. Restoring a backup is easier than it's ever been nowadays :-).
My understanding was that you have to install google messages to get RCS to work and on google's end it gets finicky about device ids. I read a couple blogs where people found RCS to be really unstable on GrapheneOS even with a couple workarounds.
If I'm going to have to install a bunch of google products onto my phone anyways, I don't buy the benefits as much.
I also had a recent experience being shaken down by a border guard entering Australia, and if he'd asked to go through my phone, explaining that I'm running a weird privacy focused OS he's never seen before seems like it would be a great way to increase my chances of spending a night in airport jail and being put on the next flight to North America. I don't really have anything to hide and appearing like I have things to hide could seriously inconvenience my life. Barring a tourist from entering a country has a very low bar of evidence.
Edit: Also the backup restoration is a bit more of a mess for me right now for the same reason I need the dual sim feature. I've got an American esim that's difficult to reactivate without being in America.
18 replies →
RCS is fully functional on GrapheneOS. Google Messages is the only RCS available for Android in practice and is fully supported by the sandboxed Google Play compatibility layer. It provides a special for granting ICC authentication access to Play services for it.
Camera features and quality are the same as the stock OS within the same app. Pixel Camera works fine on GrapheneOS.
Cross-SIM calling is better supported on GrapheneOS than the stock OS due to our carrier overrides features for force enabling features which aren't otherwise available.
Yeah I use rcs and you can use the pixel camera app if you want??
Rcs had a bug that was fixed recently though
RCS is fully functional on GrapheneOS with an app supporting it. Google Messages is the only RCS app for Android available in practice. It fully works on GrapheneOS via the official sandboxed Google Play compatibility layer support for it.
Camera features and quality on GrapheneOS are the same as the stock Pixel OS within the same app. Pixel Camera fully works on GrapheneOS even without sandboxed Google Play in the same profile.
GrapheneOS fully supports dual SIM and cross-SIM calling. It has much better support for it than the stock Pixel OS because cross-SIM calling is one of the features which can be force enabled for carriers not usually supporting it with the GrapheneOS carrier overrides. That also applies to 5G, VoLTE, Vo5G and VoWiFi where those can be used on carriers where those aren't available with the stock Pixel OS.
> but GrapheneOS really doesn't seem ready to be a daily driver
GrapheneOS is a daily driver for many people. The 3 things you've listed as concerns work at least as well in GrapheneOS as the stock OS. You're assuming functionality that's available is missing.
I did have RCS issues with GrapheneOS (on T-Mobile in the US) for a while, but at some point that was fixed and it works flawlessly now.
As for camera apps, the stock GrapheneOS camera app is a bit clunky, I just download the stock Android "Camera" off of the Play Store...
> I just download the stock Android "Camera"
The "stock Android camera" (the one in AOSP) is absolutely horrible. You're probably using Google's Pixel camera app.
3 replies →
> GrapheneOS really doesn't seem ready to be a daily driver.
As someone who has used it exclusively as their mobile OS for three years, it is absolutely ready. Does that mean it's perfect or bug-free? No, but nothing is.
Been using GrapheneOS as daily driver for 4 years on three pixels. Problems only start when banking apps start actively sabotaging it by pretending the phone is rooted etc. Normal apps work normally and you get way more control over them. I'll never go back to stock or worse than stock (Samsung) as long as GrapheneOS is around even if they get rid of all security aspects (which of course they won't, I'm just saying security is not the only selling point, de-googling is a big one too.. I didn't de-google but I sure like having the option)
If it become to big, it will go the same way as CyanogenMod, Google will send some people to pressure the manufacturers to drop them off
Google is the only one supporting them currently.
Well, also expect the next Pixel bootloader to be locked out if they become too big.
[flagged]
They've doubled their users in 2 years
Why are you being so aggressive?
Pathetic.