GrapheneOS version 2024011600 released

GrapheneOS

GrapheneOS version 2024011600 released:

https://grapheneos.org/releases#2024011600

See the linked release notes for a summary of the improvements over the previous release.

Eagle_Owl

GrapheneOS
I don't remember exactly whether it only happened with this version, but the energy consumption of the Pixel 8 Pro is much higher than that of its predecessor, the 7 Pro, with almost identical software and a completely identical system configuration.

P7P: 1 % energy consumption in pure standby with 5G mobile communications after 1:00 h (sometimes 1:30 h)
P8P: 1 % energy consumption in pure standby with 5G mobile communications after 25 min.

In previous versions, the Pixel 8 Pro usually took around 50 minutes in standby before the battery lost 1%.

– The only difference regarding mobile radio: Dual eSIM (both Telefónica) on P8P, one eSIM on P7P.
– The only difference regarding apps: Threema Libre is installed on the P8P and SimpleX Chat is installed on the P7P. However, as SimpleX Chat does not have such an efficient push system, I have not set its notifications to the highest priority. Nevertheless, the battery lasts much longer. So messengers are not the cause.

However, I can see under Settings/Battery/Battery usage (Filter by system) that mobile phone usage on the P8P is 72% (Total: 14 h 18 min.) and on the P7P it is only 57% (Total: 3 days 22 h 17 min.).

A slightly older modem software is installed on the P8P than on the P7P (Provider: Telefónica Germany)
Modem version details:
P7P: eplus_de-52000000018 2023-08-30
P8P: eplus_de-52000000006 2023-08-30

I have also tested Flight mode: then the P8P reaches normal energy consumption like 1% standby in 1 h or more.

BTW: Since day one of using the energy consumption at night with Flight and low-power mode the P8P is 3–4% and with my P7P 2% only.

Eagle_Owl

GrapheneOS
Now I guess I've found the power guzzler: Dual eSIM consumes much more energy than expected! At least in the current Android 14 version.
I hope that this can be optimised in the software (by Google or by GOS developers).

P. S.: My Pixel 7 Pro does not support Dual eSIM, for whatever reason. Supposedly, every Pixel phone from Pixel 6 onwards can support Dual eSIM (depending on the provider, of course), but although my provider Telefónica Germany supports it, Dual eSIM only works on my Pixel 8 Pro.

VAULT

[PROBLEM REPORT] Magic Earth (Sat Nav) can NOT open after this GOS update. App attempts to open and displays message: "App Encountered a Problem and needs to Close"

Running GOS on Alpha Channel on Pixel 8 Pro... app was perfect the day before on prior GOS version. NO other changes on my phone settings etc.

Stewart

I don't think the problem comes from GOS, but more from Magic Earth, an update problem.

VAULT

Stewart Oh... Well M.E. has been near faultless for the past year for me on my P7P then on my P8P... Then updated yesterday afternoon, and this am, M.E. wont open... I've NOT changed anything nor added other apps etc... ONLY change was the GOS update...

VAULT

Stewart

Stewart I don't think the problem comes from GOS, but more from Magic Earth, an update problem

Dam, I think you're right... I forgot a M.E. update arrived too via Aurora Store with some other apps. That's probably it... hmmmm...

Les_Norton

VAULT

I had the same problem.

[deleted]

hide specific system apps..

what apps became hidden?

matchboxbananasynergy

[deleted] Google Sevices Framework, Play Services, Play Store, eSIM firmware updater, eSIM activation app, Android Auto, Pixel Camera Services.

VAULT

Just did a full shutdown then power back up... problem persists...

Oggyo

The problem is in Magic Earth.
Magic Earth 7.1.24.3 (version code 2024051611) crashes.
But there is no problem with Magic Earth 7.1.23.51 (version code 2023161911) on GrapheneOS ver. 2024011600.

Stewart

I updated GOS yesterday and Magic Earth worked fine, until just now when I updated Magic Earth, it stopped working.
That's why I think the problem is with Magic Earth.

VAULT

Agreed. It would seem M.E. is the culprit... my most humble apologies to my best tech friend GOS :]

dregrinfuces

Anyone else seeing battery drain issues with this release? My Pixel 6 updated to it yesterday morning. By late afternoon the battery was down to about 70%. That's more usage than expected, so I booted it into Safe Mode and back, then swiped away all the open apps. Charged to full, pulled it off the charger when I went to bed, and this morning, it was down to about 65%. That's about twice my normal battery usage. According to the Battery Usage chart, the biggest draw was from the Google Play Store at 2% (two percent). Everything else was at 1%. If I switch the view to Systems, it shows Mobile Network used 87%, but total less than a minute. System (IDLE) at 6%, Ambient Display at 6% and everything else at less than 1%. It's odd that at an individual level, nothing seems to be using the battery. But, overall, the battery is draining about twice as fast as normal.

gosrox

dregrinfuces anyons know if gos/aosp also do thing like iOS where after update everything index/reindexes for a day or more? I also experience massive battery drain since updating to different gos/aosp 14 versions but goes away aftef few days. I'm not talking about the optimizing app pop up. On ios it used to do indexing in background and you could tell by phone being warm but back to normal afyer a day or so

dregrinfuces

gosrox It took 2 days, but my battery usage yesterday was back to normal. Perhaps, as you said, there is some kind of indexing happening in the background and it takes a while.

matchboxbananasynergy

Les_Norton This has been confirmed to be a Magic Earth issue.

spiral

Eagle_Owl

Pixel 6/7 do not support duel esim, they support "Duel SIM" meaning one psim and one esim. Pixel 8 can do this too, as well as duel esim.

Eagle_Owl

Eagle_Owl
Addendum:
Unfortunately, the energy consumption with one eSIM is now just as high as before with dual eSIM. :-(
The higher energy consumption of the P8P must have another reason than dual eSIM.

I therefore ordered a new eSIM for my P8P to have both phone numbers available on the main device again.

Eagle_Owl

spiral
No, I guess you are wrong.

it's name is Dual eSIM, aka MEP. But your typo is not the point. ;-)
Google itself announced Dual eSIM/MEP a long time ago for Android 13 and then released Dual eSIM as a feature drop, first for a beta version of Android 13 and later for the stable version.

And in another forum, people had written to me that they use dual eSIM with the Pixel 7 Pro and don't understand why it doesn't work for me.

Unfortunately, far too few people use eSIM or even Dual eSIM aka MEP, which is why there is almost no reliable, verified information on the Internet and no one shares his/her experience online.

Reference:
https://source.android.com/docs/core/connect/esim-mep

spiral

Eagle_Owl

Dual esim didn't work for me on multiple P6/P7 generation phones.

https://support.google.com/pixelphone/answer/9449293?hl=en#zippy=%2Cuse-esim-profiles

Perhaps the problem of dual esim not working for us was that our carrier didn't allow it. On my P8P phones, however, I am using the same carrier than I used when I unsuccessfully tried to use dual esim on the P6/7, but with P8 dual esim works.