GrapheneOS version 2022111000 released: https://grapheneos.org/releases#2022111000.
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS version 2022111000 released: https://grapheneos.org/releases#2022111000.
See the linked release notes for a summary of the improvements over the previous release.
GrapheneOS providing EARLY UPDATES again...
• kernel (Pixel 4, Pixel 4 XL, Pixel 4a, Pixel 4a (5G), Pixel 5, Pixel 5a): update base kernel to Android 13 QPR1 Beta 3 to SHIP THE DECEMBER SECURITY UPDATE EARLY
MetropleX couple questions/concerns
1) Why no Pixel 6/6P/6a/7/7P. Is it because it will be a feature release time too? Pixel 5/5a should still get those
2) there's a reason these security updates haven't been officially released yet. They aren't fully tested. There could be new bugs or zero days introduced.
I noticed my Pixel 3a got this update SP2A.220505.008.2022111100 but I thought obsolete meant no more updates, so I am a bit confused. Is Google still updating the Pixel 3a and this is downstream from that?
We only publish release notes for the main branch at https://grapheneos.org/releases#changelog used for all devices that are considered officially supported. 3rd generation Pixels are supported via a legacy branch. We just updated them to update Vanadium, apply the lockscreen bypass fix, etc.
They're close to dead. 3rd generation Pixels are insecure and we don't want to maintain a 12.1 branch separately so they aren't getting the GrapheneOS changes anymore. Moving them to Android 13 would provide current AOSP / GrapheneOS changes but would cause many regressions.
gosrox Why no Pixel 6/6P/6a/7/7P.
Google Tensor Pixels use a different Kernel. Read https://grapheneos.org/features#more-complete-patching
gosrox there's a reason these security updates haven't been officially released yet.
Yes but not for the reason you think, the security patches are locked in when published. The reason stock doesn't get them as fast is because their testing includes the rest of their stock OS featureset. If they found an issue in the non security patch elements unrelated to the security patch of their update package, it could/would delay the release of the security patch for 3+ weeks as the whole package would require further testing and validation etc again for their entire update package.
The delay stock has over us is inconsequential to the security patch itself.
This update broke something in the pedomater app from fdroids step calculations. The steps counter are doubling when I log in and out from my user or restart my phone. Very inconvenient since I rely on that app to track my steps for my health. Today I thought I only walked 2k but when I restart my phone it said I actually walked 4k. Which makes sense since it felt lot longer than usual lmao. I was opening the app every once in a while to check my distance and it did seem slow to update or was not counting all of my steps.
It was working perfectly fine in the 2022110800 release and is now acting weird in 2022111000. The Pedometer itself has NOT had an update (and has not in 3 years) so it should not be that. The only other updates I did was grapheneOS to 2022111000.
None of those few changes seem like they should have an impact on counting steps.
gosrox I just tried this app and it didn't seem to double my step count after a reboot. However it did feel fairly inconsistent. Regardless of whether there's been a regression here (I'm personally unsure as I haven't used this app before), I feel like I have to note that you probably shouldn't be using an app that's out of date.
Not only has it not had an update for years, but it's also stuck on target SDK 26. That's ancient. For context, we're currently at SDK 33. The SDK level brings privacy and security improvements which are often very substantial, and you should try your best to use apps which keep up with that.
matchboxbananasynergy I was able to reproduce it again today and so did a friend who never used it before.
Open app
Walk 100 steps
It says 100 steps
Restart phone
All of sudden it is 200 or more
Restart phone again and it keeps adding more with each restart.
It definitly did not behave like this prior to Nov 11 update.
gosrox Could you please check whether other pedometer apps behave in the same manner?