Pixel 4, Pixel 4 XL and Pixel 4a are end-of-life and shouldn’t be used anymore due to lack of most security patches for firmware and drivers. We’re considering porting them to Android 14 to continue providing extended support longer than initially planned to keep them as a way to preview the current version of the OS despite them not being secure. It will be a significant effort to port them properly without lost functionality and we’re looking for a new developer to fund rather than reassigning any developers from their existing work on the OS.
Tags:
- 2023101300 (Pixel 4a (5G), Pixel 5, Pixel 5a, Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, emulator, generic, other targets)
Changes since the 2023101100 release:
- exempt non-app system packages from new package visibility restrictions to fix many APIs in secondary users
- Sandboxed Google Play compatibility layer: expand background activity launch shim to all the core Google Play apps to fix sandboxed Play Store compatibility issues with Android 14
- Sandboxed Google Play compatibility layer: fix “Don’t show again” notification action which broke after Android 14 port
- Pixel 5: add back support for battery share (reverse wireless charging) via the new infrastructure in Android 14 which we already adopted for 6th/7th/8th generation Pixels
- GmsCompatConfig: update to version 78
You must log in or # to comment.
…I really think these should show on the system update menu. A description of what’s your current version (not shown on system update section), the newer update number and date, and a summary of what it entails. I find the current process rather… Obscure…
I agree. I was impressed with Android 14 being out within a few days after public release, but I wish they would have taken their time. It doesn’t feel like I’m on a stable release channel, and I don’t think I actually am.
The OS is technically stable, I’m using it daily. These issues were likely edge cases. There’s a lot of variable when maintaining such a huge project like an Operating System, so edge cases like these were bound to happen eventually.
Hmm not so much of an edge case, if rebooting your phone inevitably leaves it useless for about 20min (depending on the amount of app), and wit a chunk taken of your battery. Acceptable for your average update, but not during any/every reboot :(
The slowness is during update not reboot. The other bugs were edge cases.
If you have a github account, may you please create an issue of this, so Project Members may see this? The issue tracker located here: https://github.com/GrapheneOS/os-issue-tracker
I do agree that having change logs shown in the OS for new updates would be nice.
Thanks…I just made a request there.
EDIT: Sigh…It was requested already on October last year. No work done on this I guess.I don’t see it. Where is it posted?
Thank you for posting
