AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Technology
99
Beiträge
66
Kommentatoren
365
Aufrufe
-
I want a phone with only cellular data, no calling, no sms, just an open source browser capable of webasm and webrtc
We had those, they were called Pocket PCs. I too want them back. I loved the Dell Axim x51v. A tablet does the job, but it's the same shitty OS.
-
Sounds like a tablet, and that very well could be easier for someone to build than a phone.
Can we have one of those that fit in my pocket, like 6.5" max ?
-
That was bound to happen at some point. Buying a Google device to then "degoogle" it never sit quite right with me.
I bought mine secondhand because I had a bad feeling about giving google money just to degoogle as well but still really wanted to use GrapheneOS
-
More like A-no-SP
It's Nopen Source
-
Yes, but that shouldn't explicitly opt in, and they shouldn't marry that product to Gmail and Google Drive if they are going to push it to enable by default.
Again, it's really insidious. They push it so aggressively I had to disable it on my personal device twice, and I can't just not use Google Photos app because it's tied to the camera itself on pixel phones.
I agree with you, it's insidious.
Given you've got a Pixel phone, you can save at least yourself from this problem by running Graphene or Calyx on it.
-
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.
This fucking sucks. Cyberpunk dystopia
-
-
Like, I understand the more the merrier, and so I don't hate on the whole Pixel, ROM development thingy, but I just don't understand the appeal of Pixel phones. If you want to be a photographer, get a camera. Other than that, you really don't need that great of a camera on your phone. Given the condition of America and the police state and corporate surveillance, I don't know why anybody with a damn look of sense would put their information on these major platforms, let alone even on the outskirts. Some people make money on social media, but a lot don't. I stick to my guns and I'm on the internet and computers to learn to educate myself, not to dick around with stupid shit. We need something other than Android. And we have to be weary of open source, especially when it's sponsored by Google. Google is a terrorist organization.
If you want to be a photographer, get a camera.
️Even professional photographers don't have their cameras on them at all times, nor are they as convenient for just whipping out and taking a picture within 1.5s.
Plus, cameras are expensive and they're another thing to carry around (idk about you but I don't have infinite pocket space) and they're another thing to keep charged, whereas you have a phone with you at pretty much all times anyway, because they're effectively required for modern society.
You may as well be saying you don't understand why phones can play music when you can get an MP3 player, that you don't understand why they play videos because TVs exist, that you don't understand why they have web browsers and plenty of apps, because PCs exist.
I stick to my guns and I'm on the internet and computers to learn to educate myself, not to dick around with stupid shit.
He said, on this Lemmy thread.
And we have to be weary of open source
Ah yes, that nefarious Open Source software. Tell me more about the evils of FOSS, Mr Balmer.
-
That was bound to happen at some point. Buying a Google device to then "degoogle" it never sit quite right with me.
Amen but here we are
-
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.
Damn, I've just switched to Pixel 3a XL I got for $100 and then installed Evolution OS.
-
-
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.
Long time coming, Play Integrity (or whatever's called nowadays) restrictions have effectively killed any alternative distributions.
-
-
Like, I understand the more the merrier, and so I don't hate on the whole Pixel, ROM development thingy, but I just don't understand the appeal of Pixel phones. If you want to be a photographer, get a camera. Other than that, you really don't need that great of a camera on your phone. Given the condition of America and the police state and corporate surveillance, I don't know why anybody with a damn look of sense would put their information on these major platforms, let alone even on the outskirts. Some people make money on social media, but a lot don't. I stick to my guns and I'm on the internet and computers to learn to educate myself, not to dick around with stupid shit. We need something other than Android. And we have to be weary of open source, especially when it's sponsored by Google. Google is a terrorist organization.
Being weary of open source is like being afraid to eat food that you watched somebody cook for you.
-
This would be sad if Pixel phones were worth buying, instead of being far inferior to midrange Motorola devices in battery life and performance while costing well over twice as much.
I mean, you're getting a lot of downvotes, but I've gone Motorola -> Motorola -> Motorola -> Pixel -> Pixel -> Motorola.
Both my Pixels died in less than a year. Each had battery life which, while it did improve over a few weeks as Pixel's optimization stuff took hold, never reached an entire day. Both were unacceptably fragile. Both failed randomly, just out of warranty.
And the Motorola I'm using now has none of those problems, was cheaper, is faster, has a better battery, has a better screen, and in some ways is more customizable (fuck that unmovable search bar).
Like, really. Motorola is a sleeper brand. Not perfect, but damn good.
-
You must be ignoring the Motorola bloat that makes it's performance beyond subpar somehow
All of which can be disabled.
-
Can we have one of those that fit in my pocket, like 6.5" max ?
There are some 7-8" tablets that could probably fit in a pocket, but finding the perfect mix of Linux compatibility and cell chip is going to be difficult.
However, I see a few Linux tablets out there that have to be all runs, because Linux tablets are a pretty small niche, so it might not be that expensive to build one yourself.
-
I mean, you're getting a lot of downvotes, but I've gone Motorola -> Motorola -> Motorola -> Pixel -> Pixel -> Motorola.
Both my Pixels died in less than a year. Each had battery life which, while it did improve over a few weeks as Pixel's optimization stuff took hold, never reached an entire day. Both were unacceptably fragile. Both failed randomly, just out of warranty.
And the Motorola I'm using now has none of those problems, was cheaper, is faster, has a better battery, has a better screen, and in some ways is more customizable (fuck that unmovable search bar).
Like, really. Motorola is a sleeper brand. Not perfect, but damn good.
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.
-
This fucking sucks. Cyberpunk dystopia
In cyberpunk dystopia you could buy normal things, just most wasn't it.
-
Do you think it may be related to the monopoly issues they are currently facing?
Quite possibly, the GrapheneOS team seems to think so:
GrapheneOS (@GrapheneOS@grapheneos.social)
Google seems to be in the process of splitting up Android and Pixels along with moving towards treating other Android-based platforms as their competitors instead of their partners. Pixels retain first class alternate OS support with Android 16 firmware so it's not about that.
GrapheneOS Mastodon (grapheneos.social)
GrapheneOS (@GrapheneOS@grapheneos.social)
Our speculation about this is that a result of Google losing a US antitrust case and likely losing several more soon, they're preparing for Android and Chrome being split into separate companies. If Android gets split off, they want to retain Pixels. https://www.nytimes.com/2025/04/21/technology/google-search-remedies-hearing.html
GrapheneOS Mastodon (grapheneos.social)
-
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.
huh, look at that. the thing people were warned about when buying pixel phones happened.
-
-
Yeah, I'd totally buy a phone running one of those provided it does all the phone things properly: SMS/MMS, reliable calls, all day battery, etc. I don't need fancy apps, I just need a working phone.
If I can get that, I could probably donate some time porting apps.
It's so crazy (technically understandable, but still crazy) to me that reliably receiving calls is still such a major issue
-
Does this mean Graphene is dead? Probably the real reason they would do this is to kill Graphene.
This fits into Google tying Android closer to them, same with the recent move of only making release source publicly available.
They're regretting having started Android as an "open" platform and want to gain control fast, maybe preparing for the current anti-trust trials they are facing in the US.
