I'm so glad GrapheneOS is willing and able to pick up the pieces and polish Android into a usable product as Google continues to drive its clunker into the ground. The only question is if GOS can rescue Android before Google sends it off a cliff.
In the meanwhile you can try this temporary fix: Go to Developer Options->Apps>Background Process Limit and change the limit from Standard to "at most 4processes" [1]
Usually I am the one making fun of people who have been claiming that "the new update made everything buggy and slow and reduced battery life" with every update for the past 15 years, but this time this one's actually real and hitting my base Pixel 8 hard. Hopefully the October update fixes it.
I'll be interested to see if downstreams of AOSP ultimately weaponize updates against Google. For the kernel that's a minefield but Google made plenty of stuff Apache/MIT to keep its options open..
It's a post about google screwing up their process and also pushing a bad update to a ton of people, and other people cleaning up their mess. I'm glad "open source is working" but that's a small part of the picture and I don't see why that would remove the point of the blog post.
Software bugs happen. That's a given. If GOS thinks they are above bugs, they are a) either not doing anything significant b) lying.
Am I surprised that a bug happened in Pixel? Sure. Is there a cause to call for better processes? Yes. But saying "well well well, I fixed the bug" just comes across very amateur.
It's concerning to hear about the disarray within the internal workings of Android, they've spoken quite a lot about this recently such as getting access to the code and having to make manual requests.
I'm curious if there's any back up plan to an operating system used by billions. One would think, and hope, the EU would have an alternative ready to go at a moment's notice. Android is literally too big to fail, but I doubt the EU would be ready even though you could consider the failing of Android a national security emergency.
I would like to know more about what's going on at Google that are causing these issues.
I read a lot of comments like this, saying "we should have an alternative". And I agree that it would be really cool, BUT:
AOSP and the Android SDK are open source. GrapheneOS is exactly an alternative to Google Android. Sure, Google could shut down the Play Store (but alternative stores exist), or destroy the Play Services (but even then, there is microG).
I am happy that Google is still contributing to Android because they have a ton of money and many brilliant engineers, even though as a company it seems like it's somehow trying to burn it to the ground. But I am optimistic: it would be possible to build on top of the open source parts of Android if needed.
AOSP is open-source, but unlike Linux distros, AOSP per se doesn't really support any platform other than the Android emulator. To support real devices you need devicetree/firmware/drivers from a vendor. So it's concerning to see this move from Google, which is also the device vendor for all currently supported GrapheneOS devices.
I want GOS to succeed; I'm afraid their exceptional technical and developmental skills could be made mostly ineffective by their foot-gun conduct. Fanboys urging them on or defending everything they do are driving them toward a cliff.
GOS can just talk about the upside, their solution to this problem. That's great work. But they often choose to denigrate others, which is destructive, damages relationships (the most essential assets - especially when you have no money to offer!), and is myopic: GOS's sh-t stinks too; they f- things up too. Forgive us our trespasses as we forgive those who tresspass against us.
It seems especially dangerous being entirely dependant on Google's goodwill; Google has zero need for GOS. I'd think Motorola, who now has money and reputation depending on GOS's success, would tell GOS to zip it. If I were in that industry and looking to partner, I might love GOS's technology but their behavior would be hard to overcome. For example, I love OpenBSD, but who partners with them? And OpenBSD isn't dependant on someone else.
Just zip it, be professional, focus on what you are doing and not on others. Great job on this fix!
>Just zip it, be professional, focus on what you are doing and not on others.
How do you propose they "focus on what [they're] doing and not on others" when their entire project is dependent on other's (Google's) work that directly impacts their own users? There's nothing about this blog post that is unprofessional. GrapheneOS released a patch for a rather severe performance bug, which is outside the scope of their normal work, so they provided context into why they made the decision to do so.
wow, well said. This explains why I always felt a bit off about GOS. I'm reminded of Igalia, who does a ton of work on Safari but always comes across as professional and dependent.
There's a certain humility in how Igalia conducts business, and they contribute sooo much to the web ecosystem.
I'm so glad GrapheneOS is willing and able to pick up the pieces and polish Android into a usable product as Google continues to drive its clunker into the ground. The only question is if GOS can rescue Android before Google sends it off a cliff.
In the meanwhile you can try this temporary fix: Go to Developer Options->Apps>Background Process Limit and change the limit from Standard to "at most 4processes" [1]
1: https://redlib.catsarch.com/r/GooglePixel/comments/1wr1767/c...
Usually I am the one making fun of people who have been claiming that "the new update made everything buggy and slow and reduced battery life" with every update for the past 15 years, but this time this one's actually real and hitting my base Pixel 8 hard. Hopefully the October update fixes it.
Based on the timeframes in the linked post, it likely won’t
I was wondering what was wrong with my phone, i thought a reboot would fix it and forget to do it everytime.
The lags are actually quite unpleasant and noticable, i wonder how it wasn't caught before the release.
Gosh, I have noticed a number of my apps (Pixel 11 fold 'pro') simply halting under high workload. This is that I suppose.
I'll be interested to see if downstreams of AOSP ultimately weaponize updates against Google. For the kernel that's a minefield but Google made plenty of stuff Apache/MIT to keep its options open..
Why wont GOS contribute this to upstream?
Because Google is already picking patches from GOS ;-)
I'm confused, so if open source is working as expected then what's the point of the blogpost?
It's a post about google screwing up their process and also pushing a bad update to a ton of people, and other people cleaning up their mess. I'm glad "open source is working" but that's a small part of the picture and I don't see why that would remove the point of the blog post.
Software bugs happen. That's a given. If GOS thinks they are above bugs, they are a) either not doing anything significant b) lying.
Am I surprised that a bug happened in Pixel? Sure. Is there a cause to call for better processes? Yes. But saying "well well well, I fixed the bug" just comes across very amateur.
Major performance bugs don't sneak themselves into releases and then prevent followup fixes from being promptly released.
The point of the post is not that grapheneos made the fix, it's that they had to.
> We have rapidly growing resources and we'll handle it.
This is such a rarity to see in today's world. I'm glad GrapheneOS is getting the support it needs. I wish that happened more often.
It's concerning to hear about the disarray within the internal workings of Android, they've spoken quite a lot about this recently such as getting access to the code and having to make manual requests.
I'm curious if there's any back up plan to an operating system used by billions. One would think, and hope, the EU would have an alternative ready to go at a moment's notice. Android is literally too big to fail, but I doubt the EU would be ready even though you could consider the failing of Android a national security emergency.
I would like to know more about what's going on at Google that are causing these issues.
I read a lot of comments like this, saying "we should have an alternative". And I agree that it would be really cool, BUT:
AOSP and the Android SDK are open source. GrapheneOS is exactly an alternative to Google Android. Sure, Google could shut down the Play Store (but alternative stores exist), or destroy the Play Services (but even then, there is microG).
I am happy that Google is still contributing to Android because they have a ton of money and many brilliant engineers, even though as a company it seems like it's somehow trying to burn it to the ground. But I am optimistic: it would be possible to build on top of the open source parts of Android if needed.
AOSP is open-source, but unlike Linux distros, AOSP per se doesn't really support any platform other than the Android emulator. To support real devices you need devicetree/firmware/drivers from a vendor. So it's concerning to see this move from Google, which is also the device vendor for all currently supported GrapheneOS devices.
I love you, GrapheneOS. XOXOX
I want GOS to succeed; I'm afraid their exceptional technical and developmental skills could be made mostly ineffective by their foot-gun conduct. Fanboys urging them on or defending everything they do are driving them toward a cliff.
GOS can just talk about the upside, their solution to this problem. That's great work. But they often choose to denigrate others, which is destructive, damages relationships (the most essential assets - especially when you have no money to offer!), and is myopic: GOS's sh-t stinks too; they f- things up too. Forgive us our trespasses as we forgive those who tresspass against us.
It seems especially dangerous being entirely dependant on Google's goodwill; Google has zero need for GOS. I'd think Motorola, who now has money and reputation depending on GOS's success, would tell GOS to zip it. If I were in that industry and looking to partner, I might love GOS's technology but their behavior would be hard to overcome. For example, I love OpenBSD, but who partners with them? And OpenBSD isn't dependant on someone else.
Just zip it, be professional, focus on what you are doing and not on others. Great job on this fix!
>Just zip it, be professional, focus on what you are doing and not on others.
How do you propose they "focus on what [they're] doing and not on others" when their entire project is dependent on other's (Google's) work that directly impacts their own users? There's nothing about this blog post that is unprofessional. GrapheneOS released a patch for a rather severe performance bug, which is outside the scope of their normal work, so they provided context into why they made the decision to do so.
Look to "HugOps" as inspiration: when someone else is having a bad day, offer them a hug rather than running them down.
The article uses phrases like "completely broken", "awful", and "<delay> wouldn't be a surprise". Which might be true but it's not helping.
wow, well said. This explains why I always felt a bit off about GOS. I'm reminded of Igalia, who does a ton of work on Safari but always comes across as professional and dependent.
There's a certain humility in how Igalia conducts business, and they contribute sooo much to the web ecosystem.