Sad news. I hope they remove the latest update so no more users run into these problems.
comments
Techspot is blocked by badblocks+ for some reason
It's tap to pay (or use the public transit) that's keeping me back.
Why Molly over the official client, may I ask? The official client is already OSS.
Didn't this one have the kernel regression with a memory leak?
And it seems to have fixed it, haven't had any issues since the update, I'm on a Pixel 9a
GrapheneOS released the update yesterday to revert that change https://discuss.grapheneos.org/d/42518-grapheneos-version-2026100200-released
Yes but it wasn't with its price nowadays itnis definetly not with 100 dollars more. Vying it now you get less support.
It's been a minute since I flashed a rom but I feel like I'm gonna need a cable and a laptop?
Good thought. Luckily all my critical folks are on Signal.
It's not Netflix. It's... analog...
I still use this thing daily. I installed moonlight and play my PC game on it too. It's great.
I was able to get RCS to work on Google Messages easily on GrapheneOS. The issue I had was trying to NOT use RCS. My messages have never been encrypted with iPhone users so I'm using Molly for people that matter anyways, and I was hoping to be able to recieve group texts even though I wasn't using Google Messages anymore. Nope, could never get it to work. I tried deregistering from RCS on Google's page, I tried contacting TMobile support, etc. Those group text just disappeared into the ether. So I'm back to Google Messages until Grapheme Messages adds RCS.
I'm talking about a hardware update not the firmware.
I thought that might have been the setting that did it. Unfortunately, a prompt to change that setting occurred only after about 16 hours of multiple rounds of switching, uninstalling, resetting permissions for, adding permissions to, and clearing data from the Messages app, multiple rounds of turning off RCS through Google, etc. I didn't see it mentioned anywhere in support posts or the extremely long release notes pages until after that prompt.
Admittedly, my ability to find anything useful through DDG or Google seems to get worse every week.
It's actually really easy nowadays. There's specific setting in the sandboxed Google play for ICC identification (needed for RCS) and activation/it getting it to work is trivial as long as you use Google messages.
The native RCS app is something they want to do but is far out.
I think graphene inherited this issue. It certainly inherited the memory bug in the latest update.
I did recently and its been better than I expected. The only real issue was RCS. After 2 years of me not having a Facebook account, my friends finally switched from Facebook's system to a group text... which broke utterly without RCS.
I had to install Google's Messages app and fiddle with the native app and Google's RCS settings and eventually it start working again. I am pretty competent but the support for this seemed to be digging through forum posts and trying a bunch of different solutions unsuccessfully and then having it suddenly work and not knowing why. I hope they manage to get a solution working in the native app.
Otherwise a great experience!
I dunno about them but my phone is only at 22% battery and I can't reach the cable from where I'm sitting.
I was joking. Also I run Graphene already.
Good news. You can switch from your couch.
You know how else you can get a more secure, convenient Pixel without having to put up with Google's shitnanigans?
Switch to GrapheneOS.
It may be inconvenient but it does make your phone more secure
Will be a good excuse to get off my ass and switch to Graphene