GrapheneOS version 2026081300 released

mspbonn

Update on Pixel 7a and Tablet went fine. No issues so far.
Bubbles still not available on the Pixel Tablet.

Thanks to the dev-team 👍

gristle-cause

This update appears to have changed SMS messaging behavior from a secondary profile, though nothing in the changelog explicitly points to a change I can tie to this

Using the stock GOS messaging app in a secondary profile with SMS permission:

incoming messages are now automatically loaded, whereas previously the messaging app would need to get relaunched (awesome)
MMS messages cannot be sent (less awesome)

Kamika242

I have problems with the mobile network connection since today in the morning right after the update. The eSIM (silent.link) is jumping around between 3 networks, stays on german Telekom for a while then and jumps back to O2, until the connection is lost again. O2 and Vodafone can't be selected manually (network not available) and on automatic network selection the described scenario happens. Before the update the connection was always stable on O2 under automatic network selection, all networks were also selectable manually. Data connection is stable, when connected to any network.
I have to wait a few days to see if this happens due to network problems of O2 and Vodafone, the silent.link service or the problem is really caused by the update. It might just be a coincidence.
Everything else works perfectly.

xxx

Kamika242 I have to wait a few days to see if this happens due to network problems of O2 and Vodafone,

Bummer, please report back. Network works fine here since the update (with german sims).

de0u

Kamika242 Something to try at some point: Settings, System, Reset options, Reset Mobile Network Settings.

GrapheneOS

gristle-cause No, it didn't change anything about SMS or MMS in secondary users. It never worked well.

gristle-cause

GrapheneOS correlation v causation makes a fool of me once again... appreciate the confirmation

GrapheneOS

gristle-cause There may be a relevant change to MMS in the security preview releases but nothing that should make secondary user SMS work better.

GoSaM

gristle-cause correlation v causation

That's the way it is, so double checking is always needed to sort out strange coincidences that seem so convincing at first glance, a pitfall many fall into, me as well. So if we fall into such pitfall and recognize it, then we are never a fool but learn and made one more step to improve ...

See my check question w/o using your nice "correlation v causation" 🫣
https://discuss.grapheneos.org/d/41221-gmscompatconfig-version-173-released

Kamika242

xxx please report back.

I rebooted the device a few minutes before I went to bed, with this reboot the issue was apparently fixed and also today I've seen no network jumps anymore. What is surprising is, I already did a restart for some time after the app optimizing process, that's what I always do, because after optimizing not all background apps are starting automatically and this first reboot didn't already fix the issue.
All in all, yes, the issue was caused by the GrapheneOS update, but was fixed by a second (actually the third) reboot.

de0u Something to try at some point: Settings, System, Reset options, Reset Mobile Network Settings.

I know, but this can't be a permanent solution. I've never did so many network resets as under GrapheneOS. This time I did the "small network reset" (the small circular arrow symbol in the right corner on top in network settings), but it didn't help.

Kamika242

Forgot to mention, caused by this network work issue I also had an abnormal battery consumption, much higher than usual for a Sunday, this actually was the main reason to do a further reboot in the evening.

Sam57

GrapheneOS Well....so it is just coincidence that multiple users are reporting exactly same behaviour (here, in previous release as well...)? And how come it it related to carrier? The sim button should be there even without any sim whatsoever. Same issue reported in previous update, more same problems reported in https://discuss.grapheneos.org/d/36864-sims-greyed-out-since-android-17-multiple-devices. And as mentioned there, could be upstream problem, no specific to grapehenos itself...but I hope it will be resolved, because mobile phone without ability to use it as phone is...well just a nice handheld.

Granite

GrapheneOS
Unfortunately, whatever you are referring to regarding the security preview release, has broken something in mms for secondary users. I'm not alone in this. In my case, outgoing messages in group messaging fails. One-to-one messaging works.

The issue initially was, any out going text that included an emoji or other image failed to send from both owner and secondary. Image free messages were not affected, delivered normally. After multiple reboots and a network reset, messaging from the owner profile returned to normal, ditto one-to-one messages from the secondary. However, now ALL attempts to respond to group texts in the secondary, including image-free texts, fail. Incoming texts from group members arrive just fine, including images.

Never had this happen before. I've been using the same app on GOS for more than a year.

I'm using Textra, and reverted to stock GOS mms for testing, then installed Quik sms for another test. The problem is consistent across all three apps.

« Previous Page