AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Technology
99
Beiträge
66
Kommentatoren
15
Aufrufe
-
I swear to god how many time it has to pass until developers realize open source is just a facade only Free Software licences are free as in freedom
Sorry how would have a GPL`d aosp helped here? Google would and could still have not published their drivers for the pixel. You'd need pixel drivers licenced by someone different from google to make them publish their changes to the drivers
-
huh, look at that. the thing people were warned about when buying pixel phones happened.
Google doing something bad? SAY IT ISN'T SO
-
TL;DR
-
Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release.
-
The company says this is because it’s shifting its AOSP reference target from Pixel hardware to a virtual device called “Cuttlefish” to be more neutral.
-
While Google insists AOSP isn’t going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult.
AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Google has confirmed it isn't discontinuing AOSP, but it's making a change that makes it harder for devs to build Android for Pixel phones.
Android Authority (www.androidauthority.com)
apple and google are doing their best to promote linux phones at this point.
dont buy american
-
-
TL;DR
-
Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release.
-
The company says this is because it’s shifting its AOSP reference target from Pixel hardware to a virtual device called “Cuttlefish” to be more neutral.
-
While Google insists AOSP isn’t going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult.
AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Google has confirmed it isn't discontinuing AOSP, but it's making a change that makes it harder for devs to build Android for Pixel phones.
Android Authority (www.androidauthority.com)
It's the year of the linux phone. /s
-
-
This is not a selling point but rather a unfortunate but comprehensible circumstance. Nexus and later Pixel phones have not been anything more than reference hardware without significant sales until the Pixel 6. Google has been a software company that has greatly benefited by android being an "open" platform you could contribute to and use their services on.
The App / Cloud ecosystem has gained a lot of competitors, so Google is doing their best to reverse this course of action by pulling more and more functionality out of AOSP into Play services and now into Cuttlefish. We can only wait and see how other phone manufacturers react to this.
We can only wait and see how other phone manufacturers react to this.
Honestly, it's obvious how they will react. After all, they'd have to pass a certification process if they want to be able to ship Google stuff.
-
Nah, you have it backwards. GrapheneOS didn't choose Pixels for any reason other than they're the only acceptably secure devices out there. I can't imagine they want this to be the case.
That still sounds like choosing to me. Like, if your project requirements are so strict that it only works on the mornings of a Tuesday that falls in a prime number day that has a blue moon and where there are no ATP tennis matches going on (all pre-existing things you have no vote on), maybe you should re-evaluate if you actually want your proyect to have a viable audience.
-
That still sounds like choosing to me. Like, if your project requirements are so strict that it only works on the mornings of a Tuesday that falls in a prime number day that has a blue moon and where there are no ATP tennis matches going on (all pre-existing things you have no vote on), maybe you should re-evaluate if you actually want your proyect to have a viable audience.
Is it really so outlandish to want my phone to be unbreakable by cops?
-
Which motorola?
I had a model I can't remember which was an emergency replacement from my OnePlus 3T years ago, then two G Powers of... Some years, then my Pixel 5a and then 8, and now a Razr 2024.
-
See? Pixel devices are nothing but a trip to the lemon grove, but people with debilitating chronic ass pain tearfully refuse to accept that they wasted their money on GETBRAND. I take those downvotes as an unofficial census confirming how many people don't know ball.
You might be a tad zealous, but you're not wrong.
-
Is it really so outlandish to want my phone to be unbreakable by cops?
In this year of 2025? No. But it still is basically setting oneself for failure from the perspective of Graphene, IMO. Like, the strongest protection in the world (assuming Graphene even is, which is quite a tall order statement) is useless if it only works on the mornings of a Tuesday that falls in a prime number day that has a blue moon and where there are no ATP tennis matches going on. Everyone else is, like, living in the real world, and the uniqueness of your scenario is going to go down the drain once your users get presented with a $5 wrench, or even cheaper: a waterboard. Because cops, let alone ICE, are not going to stop to ask you if they can make you more comfortable with your privacy being violated.
-
-
-
With a Trump-driven reduction of nearly 2,000 employees, F.D.A. will Use A.I. in Drug Approvals to ‘Radically Increase Efficiency’
Technology
1
-
-
-
-
Keep the Future Human: How Unchecked Development of Smarter-Than-Human, Autonomous, General-Purpose AI Systems Will Almost Inevitably Lead to Human Replacement. But it Doesn't Have to.
Technology
1
-
