AOSP isn't dead, but Google just landed a huge blow to custom ROM developers
Technology
93
Beiträge
66
Kommentatoren
0
Aufrufe
-
Or in other words, cuck licenses.
Haha, great name, thanks for the link!
-
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.
If Pine64 can spec out a reasonably decent prototype of a phone and Purism can sell theirs for 2 grand (not worth it), then somebody else can legit come out with something just the same. Pine64 project and Purism cannot be the only communities that can somehow come out with these kinds of tech. Better yet, more people should be jumping to help out these guys to be free from Google and Apple dominance.
-
-
Now more than ever we need more work on PostmarketOS, Mobian, Gnome Mobile etc...
Bummer that it's still so hard to find a somewhat modern, affordable phone that is Linux compatible
Why can't we install it on a Samsung Galaxy A06 A065F DS ?
They are like, less than 200$ new without contracts -
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.
I want a phone with only cellular data, no calling, no sms, just an open source browser capable of webasm and webrtc
-
or a brand whose phones support their requirements other than google.
Wasn't Graphene's "selling point" for long being that nothing but Pixels can match their reqs? I don't see why any current band would want to make it easier for them, and I also don't see new brand significantly entering the market.
Graphene boiled themselves in their own frogpan.
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.
-
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.
I am running GOS on a Pixel 7, which means I've had this device for ~2.5 years at this point, and back when I transitioned to this setup I was aware they were talking about being beholden to Pixels due to the hardware security module not being available on other devices.
It has been a known issue. I understand it is a very difficult and costly undertaking to develop new hardware and new entrants would be competing against the big guys for fab space, manufacturing and assembly etc.
We need some kind of nonprofit or independently financed group to advance this cause. Could it be FUTO, Framework, or some other company/organization like this?
There would be market incentive to solve these problems - There has got to be a lot of demand for a neutral hardware platform that meets the hardware security module and other requirements for bootloader security, custom ROMs, etc.
-
-
I want a phone with only cellular data, no calling, no sms, just an open source browser capable of webasm and webrtc
Sounds like a tablet, and that very well could be easier for someone to build than a phone.
-
Why eSim? Does your carrier not support physical sim?
For traveling I find it much easier to just buy an esim
-
I am running GOS on a Pixel 7, which means I've had this device for ~2.5 years at this point, and back when I transitioned to this setup I was aware they were talking about being beholden to Pixels due to the hardware security module not being available on other devices.
It has been a known issue. I understand it is a very difficult and costly undertaking to develop new hardware and new entrants would be competing against the big guys for fab space, manufacturing and assembly etc.
We need some kind of nonprofit or independently financed group to advance this cause. Could it be FUTO, Framework, or some other company/organization like this?
There would be market incentive to solve these problems - There has got to be a lot of demand for a neutral hardware platform that meets the hardware security module and other requirements for bootloader security, custom ROMs, etc.
Would fairphone be a good choice?
-
You must be ignoring the Motorola bloat that makes it's performance beyond subpar somehow
People who use stock ROMs choose to suffer, just like people who choose to buy a Pixel that will either come unglued, push components through the display, or just constantly overheat.
-
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.
That was bound to happen at some point. Buying a Google device to then "degoogle" it never sit quite right with me.
-
-
Yeah, just that this has shit to do with the stated reasons. Google hasn't been an open source ally for quite some time now
Do you think it may be related to the monopoly issues they are currently facing?
-
I really want to give furios phone a shot. It's apparently close to supporting my carrier.
That and a sailfish phone. The community one though didn't support my carrier (think it's mainly EU specced only.)
What I find missing most of the time though is any esim support. Makes me wonder if the hardware one that you can program an esim on works.
I plan on buying one when my current phone is no longer usable.
-
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.
So I installed LineageOS recently. Now that I've transferred my passwords and account info I'm quite happy. What will happen from here? Will some apps stop working? If not, is there a problem with just continuing to use the phone as is until I need a new phone (security, eg)?
-
-
one less reason to buy a Pixel, well done Google!
How badly would this affect graphine os?
-
Would fairphone be a good choice?
No. Sadly they lack the security requirements of GOS.
Source -
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
