(grapheneos.social)
> Google simply regrets android being open source.
But they won't learn that on their own. They are breaking the deals. So we move. We force their hand
I think they're fully aware of this. They just don't care, because the goal of "get market share super high" has been reached, so now they have no need for it to continue being open.
I don't disagree about what that means we should do; I just don't think we should assume they're being naive here. It's like writing a program to play chess; you should select your move assuming the opponent is smart and will make the optimal counterplay rather than assuming weakness, and then if they end up being less smart than that, you're still in a good place.
So yes, I do think they are being naïve. The stance is myopic. It is only a good move in the short term, and barely even that. It is under the false belief that we operate in a zero sum game.
Also in the last century most software was commercial, and thanks to business friendly licenses we are back to demos, PD, Shareware and co, only with new names for a younger generation.
Google will do just fine.
I’ve seen many open source contributors deflated because they wanted to share their code/solutions with other individuals and the world to learn from only to have their work sold as a service by a big cloud vendor without seeing something back for it. Or maybe even getting more work back to support the cloud vendor for free.
So I’m not surprised at all that licenses that allow commercial use up to a point and above that require seperate license or contributions back. It is still open source in a lot of ways. Can still be part of other open source distributions that themselves make no profit etc. And only companies that are more than able to pay must pay something.
Granted, we know Android would not be where it is today without open source contributions.
Google needs to be broken up.
If the goal of a hard fork is "the community will invest equal resources that Google does today" then you wildly underestimate how many engineers work on Chrome.
If AMZN couldnt make their fire whatever it was called fork of Android really grow, what chance has the community got ?
Difficulties maintaining a sufficient number of contributors to keep the project viable have persisted for several years. In January 2015, the project reported a lack of active developers and code contributions.[49] There have been continual problems providing timely fixes to security vulnerabilities since 2015.[50][51][52][53] In September 2016, OpenOffice's project management committee chair Dennis Hamilton began a discussion of possibly discontinuing the project, after the Apache board had put them on monthly reporting due to the project's ongoing problems handling security issues.[54][55][56]
Sounds like AOO is effectively dead, so this example is a fail to my challenge.
OpenSearch & ElasticSearch both seem alive, as well as OC & NC.
Neither https://github.com/privacyidea/privacyidea or https://github.com/eduMFA/eduMFA say either is a fork of the other.
I think you failed to share 3, 2 seem to valid examples of my challenge but the other 2 are questionable.
It is completely insane how many people work on Chrome. It seems like it is time to deprecate web browsers and do something different. Like you get a frame-buffer to draw on with something like a wasm vm. Web pages get replaced by programs (which they essentially are anyway). Get rid of 99.9% of the cruft that has accumulated over the decades in browsers. If you want to have some of that cruft, that is a library you have to send.
It should be the users choice how their browser renders, it's their damn browser. Instead, browsers are built to follow standards that mostly favor the developers preferences above those of the person who actually own the device rendering it.
The modern web is user hostile by design.
The biggest thing standing in the way of this is actually Apple, since they don't allow competing browser engines or equivalent so you can't make something like this for iOS whatsoever.
Not at first. Yet over time the work increases as one must differ more and more from Chrome. I believe that's why so many forks are giving up on Manifest V2.
Playing at their table is a losing game, the house always wins.
Android is even more of tragedy, given how all relevant NDK game development APIs are also available on GNU/Linux.
The reason why no one runs AOSP is because the phone market rewards differentiation. Each phone manufacture wants to build their own experience and building on top of AOSP is how they do so.
Is it really a losing game? Building a new OS from scratch is not worth it. Why throw away an entire app catalog for your device? Consumers want access to existing app catalogs when buying a phone. If anything is a losing game it's building a new mobile operating system over forking Android as a base.
This is what empire-building middle managers say to rationalize their boondoggles, but in actual fact most customers can't even tell the difference between two different vendors' Android skins, definitely can't tell the difference before they buy one, and the way they actually differentiate phones is on real hardware differences that show up in the specs like the camera or performance.
The hardware company's idiosyncratic fork of the software is irrelevant at best and annoyingly irregular in the common case.
No, the reason is that AOSP doesn't even include a functional keyboard nor a functional call manager nowadays.
AOSP apps were abandonned around Android 11, you can't just keep them as is for real users, it looks amateur.
Even the open-source ROMs came to the same conclusion eventually and developed their own.
No one was using those apps so it didn't make sense to spend time on them.
AI generating code changes the game significantly, though there are issues with that. A new OS would have taken several millions and multiple teams, but can now be done for far less. The problem is hardware to run it on. Who'd pay $2,000 for a shittier phone with less features when a $500 used one with GrapheneOS is right there? So the market, (in)efficiently, hasn't come up with a new phone OS. Not because it isn't warranted, but because the free market isn't a perfect system.
Technologists need to aggressively reject solutions which don't spread freedom to ordinary users as well.
Actually, use it now.
Because of their enshitification we do have alternatives that were developed.
At this point the their only services I'm using are Maps, Translate and Keep Notes and it is mostly due to lazyiness as all of those already have alternatives.
Edit: forgot about YouTube, which is ironic, because that one is a toughest one because the value comes from creators, but I'm doing my part and using GrayJay[1] so I can follow them if they switch their platform.
Yes, and now that they've achieved market saturation, it's time to pull up the ladder.
Thanks for all the free work, suckers!
I mean, FOSDEM full of Apple laptops on the corridors, the message was really lost.
Remember this upcoming Christmas that the ye oldie tradition of fixing PCs clearing awful exploiting phone apps (and cancelling subscriptions) should also include the "fix my browser" again, instead of Internet Explorer being replaced by Chrome, our collective duties is to replace Chrome with Firefox, plus its useful extensions to block ads and improve the web experience removing trackers etc.
Your call to arms today is to ensure all your tech colleagues join the movement, and then we can see Google's management views on "market growth"; they forget they made Chrome, we sold it - its our fault we forgot the "infinite growth of shareholder value"...
Implying I ever left Firefox in the first place.
With the way Firefox is heading, that might not be the best idea. Nowadays Mozilla seem more focused on riding the AI-hype wave than actually making an excellent browser people want to actually use.
What would be the point of a browser compatibility matrix then?
Which for the large majority of companies means Chrome and Safari nowadays.
Thanks to Apple's stance on iOS, otherwise it would be only Chrome, as younger generations apparently never got the IE history lesson.
As for the excellent browser that people want, that raises the question of what people want. There are likely as many answers as people.
Very puzzled why there isn't more love for Firefox, even on HN.
My biggest pain point at the moment (entirely subjective mind you) is not even the AI nonsense, but how disjointed and alien the Firefox UX and general feel is to Apple platforms (what I use, at the moment). I don’t want Firefox to mirror Safari 1:1 but I do want the Firefox UI and UX to feel polished, well thought out and thoroughly in line with system HIG specs—given that I spend a lot of time in a browser, it shouldn’t feel like a stranger in a strange land amidst my other desktop applications.
Aggressive UI improvements would go a long way to restore some faith in the incandescent fox‘ mission—at least for me.
Maybe you’re too preoccupied trying to discredit valid criticism as “fanboyism” to realise how important UI and UX are for products such as browsers.
Besides, Chrome itself is already an absolute mess of conflicting and downright distasteful UX choices and patterns. Firefox seems to be stuck in the past but Chrome seems to actively DESPISE being available on Mac.
And despite what many people here like to think: these things matter. UX improvements compound exponentially, and so do UX problems. Firefox has an opportunity here to be a first-class citizen on every OS it runs on. It has the opportunity to be the browser that respects your OS choices no matter what, but alas, Firefox seems rather content carrying its “ah yeah I remember using it back in ‘06” reputation.
Firefox is not a bad browser by any means, but it feels like Firefox is the browser equivalent of the “how do you do fellow kids” meme. An out-of-time experience pretending to blend in under the guise of “AI”.
Every other browser aren’t using macOS native UI therefore are wrong in this environment. But right on their own in being the same everywhere.
If my OS says windows and tabs close on the left, then I expect every single app to be a good platform citizen and not make me relearn default controls just to operate simple functions. Windows and tabs close on the left. End of story.
Mentioned as "one customer" in the PDF.
Edit: spelling
If your competition is attracting the worst kind of users, do you really want to get in their way?
So we move. We force their hand
Advocating for chromium to do what?
What do you have in mind?
This is the message that Firefox needs to push: Hate ads? Use Firefox.
Also, switching browsers is trivial. I do it on my parents' machines and they don't notice
- https://nitter.example/awesomekling/status/19693500085383702... (archive: https://web.archive.org/web/20250920103645/https://twitter.c...)
- https://nitter.example/awesomekling/status/18745182953508374... (archive: https://web.archive.org/web/20250101180923/https://twitter.c...)
- https://nitter.example/awesomekling/status/19712877382689095... (archive: https://web.archive.org/web/20250925185636/https://twitter.c...)
- https://nitter.example/awesomekling/status/19671787088520972... (archive: https://web.archive.org/web/20250914104847/https://twitter.c...)
With something like a browser (engine), I'm totally okay with someone saying "I'm an expert and I'm trying something with my own vision/priorities. I don't want input from random people that I have to spend time evaluating."
The GPL is worth nothing if nobody is enforcing it aggressively.
Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
Many people argued that 'customarily used for software interchange' is worded-as is to always be relevant to the times when the license is applied and that providing access to a Git repository is customary nowadays. In fact:
- The upstream Linux tree is distributed through Git.
- The relevant Pixel kernel sources used to be distributed through Git.
IANAL, so I am not sure how this part of the license will hold up in court, but the spirit is clear. Providing a Google Drive link is not customarily used for software interchange.
Also, I think it is fairly clear that the procedure is put in place to make everyone's life difficult, given that the relevant source used to be distributed through Git.
Just point out how that hurts security or privacy and we’re with you!
IOW:
Don’t threaten to stop using Google Chrome if they do one more evil thing. Start now.
I've been using it for more than 20 years.
I don't know why either of use loled though
I’m not doubting they added some ai junk somewhere. But whatever they did seems very easy to ignore.
A simpler, better time. I miss it :(
Now that the chromebooks are also Android, it feels like the slide is only going to grow ever more fearsome.
> Google simply regrets android being open source.
GrapheneOS is often around 4 to 6 months ahead on merging Linux kernel LTS releases. We used to handle this ourselves but switched to the Android GKI LTS branch maintained by Greg KH. Unfortunately, it was often struggling to keep up even before the absolutely massive increase in Linux kernel security patches this year. AI models have rapidly accelerated vulnerability discovery and it's an ongoing crisis for the Linux kernel. We want to be on the latest LTS revision within days and want to be using the latest LTS branch within months of it being released. We're not at all happy with how Android is handling things and plan to fix that ourselves. We'll get things back to how they should be.
We also ship all the AOSP userspace patches months before Pixels due to shipping all of the security preview patches as soon as possible. There are sometimes minor regressions but we find and fix them ourselves downstream. The security preview system has a terrible design especially considering that frontier AI models can reverse engineer the patches. There should at least only be a source embargo for around 24 to 72 hours rather than pretending as if it can work with the patches available 2 to 6 months in advance.
Perfect is the enemy of good. What's better for privacy, an old but inexpensive smartphone running Android 11, or the same smartphone running an up-to-date third-party rebuild of Android 16 or newer with as many privacy-improving bells and whistles as the hardware can support?
> Soon there will be two different phone brands which you can install it on.
...will they be available in my country (Brazil)? I don't think I've ever seen a Google Pixel phone in person.
I see your point, but it would be very misleading, since the phone would still have a lot of known holes. Only the OS would get updated, typically not the drivers, driver firmware, possibly not the kernel. The phone would still be easily compromised through all the known RCEs. So you tie up non-profit projects in a lot of extra work to get an improvement that does not really matter.
This is a mess created by the OEMs and they will continue to create this mess until people will stop buying from OEMs that only give lip service to security updates (roll out Android Security Bulletins to show a high patch level, while in reality the phone the phone has many known CVEs).
Not sure if you have any experience with eBay. I looked it up and people had problems selling to Brazil [1] but there are various listings that offer to ship. So maybe not a great option.
KaBuM!, Intec Store, Performance Solutions all charge significantly more with a 10a being more than double than from Google.
Motorola officially sells the Signature in Brazil [2] at the same price or cheaper than in the UK. It will be supported by GrapheneOS in 2027 on the 2027 version. From then on, hopefully Qualcomm brings MTE to the non-flagship chips and Motorola and GrapheneOS support budget or midrange devices.
>perfect is the enemy of good
I don't consider that relevant when users deserve ≥ security than an iPhone. GrapheneOS is not purpose-built to avoid big-tech's services although it does that more completely than any other alternative mobile operating system, the focus is privacy.
GrapheneOS on the state of privacy and security for their ethos: https://x.com/GrapheneOS/status/2044440381803069778
[0] https://www.ebay.com/sch/i.html?_nkw=google+pixel+9
[1] https://reddit.com/r/Ebay/comments/1d92pyn/
https://community.ebay.com/forum/shipping-57923/topic/diffic...
[2] https://www.motorola.com.br/smartphone-motorola-signature/p?...
Do these phones have ANATEL certification? Because if they don't, they will be rejected by customs. It's not simply a case of the item being held until you pay a 60% import tax.
Edit: September update for 8a has a kernel build from July. I believe it's still vulnerable but the exploit will need its offsets adjusting etc.
It'd be interesting to see which one is happening here.
Intel used to do the same with their anti theft technology aka Intel theft deterrent on their classmate PCs, so students had to enter unlock codes from an IT admin every 3 months or every say 200 boots to prevent the computer from being locked at the bios level preventing it from booting an OS, and there was an update which disabled that functionality permanently. And you would be warned when you had around 50 boots left to get the unlock code.
Android is not a Linux desktop or server distro. It is not about you getting to put what you want on the hardware you bought for free.
Operating systems are hellaciously expensive to maintain and that only gets worse in markets with rapid hardware improvements, as the smartphone market was up until maybe the late 2010s. Google is not a charity. SV did not come into national prominence for making investors $0. There is no money in giving maybe one in one-hundred smartphone users (and that's being generous) a bunch of code, for free, so that they can put it on their gizmo and talk to their nerd friends at their hacker meetup.
When they pitched Android as "open", they meant that carriers and device makers could load it up with all of the revenue-enhancing bloat that they wanted. In return, Google got a device that would let them hoover up all of the data they could ever want in order to build better ad service profiles for those using the devices. That is, after all, their business.
For a while, this could coexist with us screwing around with a real-life tricorder. At some point, though, the free stuff turned into a revenue opportunity that had to be exploited. And so, it will be.
Wish I could upvote you twice for that line alone. It perfectly sums up what I always wanted Android to be. Alas, the closer we are to this in hardware, the further away we are getting in software.
Pre-7 was just not an operating system that anyone except the geekiest of geeks wanted to use.
Windows Phone is a case study of missed opportunity.
Android won because it was available "right now" and easy to hack. Vendors could get a BSP (Board Support Package) from a chip manufacturer, slap Android userspace on top of it, and ship a phone within half a year. It was a glorious mess for a while.
Google then slowly tightened the reins and made the ecosystem more ordered.
I'm interested and wishing to see a future mobile OS that does not pander to the "attention economy" like Android/iOS are, but with billions now addicted and trapped by it, I'm realistic that it won't be an overnight success.
I think we're all more surprised by how long it took for Google to make these bad moves. For a period of time in the 2010s we actually started thinking maybe Google was alright.
This is to extent that some carriers still insist that they design phones and phone manufacturers are just factories. People need to understand that power dynamic before blaming those "mere factories" for not making Linux phones.
There has to be like an SVP of SoandSo Wireless pushing like three pillar approach of iOS, Android and Linux. Otherwise the pitch decks for any alternative phones just go straight to trash(or into a motorized shredder if it is still physical).
Only in the USA.
When Patrick Pichette left and Sundar became CEO both led to massive culture shifts.
What? Google is advertisement business. Not a software house. They sell ads. It all makes sense to build a walled garden. They are effectively a monopoly for half of the personal devices _in the world_. And they _will_ return their investments into the opensource. By locking Android and Chrome and showing ads to everyone.
Like the old days shitty TV, full of ads.
Google is a lawn mower, stop anthropologizing them. This goes the same with Apple, Microsoft, Meta, Amazon, ...
Could Google backtrack on this if they wanted? If they suddenly decided to stop releasing public code updates, what would they be violating? I can guess: Anti-trust maybe. probable at least contractual commitments Or is there some stronger forcing function?
They're not treating GrapheneOS very differently from other vendors, except that Graphene isn't relevant enough to sign a contract with because they don't make phones (or money, really).
Google should be putting out the code and patches like they used to, but the constant badgering of Google on this issue feels off. I don't see anyone complaining that Samsung isn't supporting their security-focused fork enough, or complain that Apple is delaying the bootloader unlock process by a day.
Despite their very worst, selfish intentions, Google is the very best vendor of commercial open source software. While Google's open source project collapses, there's plenty of space for other vendors to step in.
We should bemoan Google's fall from grace, but only because they're on the way to becoming just as bad as every vendor but Librem if they keep this up another decade.
https://source.puri.sm/Librem5/fw/firmware-librem5-nonfree
https://source.puri.sm/Librem5/arm-trusted-firmware
I hope I'm looking in the wrong place.
It only doesn’t make sense if you’re assuming conspiracy.
It makes a lot more sense if you assume they just don’t give a shit.
Of course, it does. Google is no longer afraid to spit on open source. People happy to use Chromium features better remember this. You are renting everything and your landlord will soon come demanding it back.
Can we just stop saying "Google" as if it's same faceless org? No, it's not Google, one or two asshole execs are behind this policy.
Bigger problem is HarmonyOS and similar devices, compatible with Android. Opensource threat from china!
And no NSA backdoors or honeypots!
Otherwise there's no need for NSA backdoors (as Cellebrite matrix shows) :)
Not particularly relevant but the lawful spying implemented in the telecommunications system by our own government has been abused by Chinese hackers as well.
lmao
* Google drop "real" Android source-code updates to OEMs _and_ the public every half.
* But they ship four Pixel updates, including documentation + SDKs.
* Now they added new APIs in a Pixel-only update.
* Google also drop security update backports to "trusted" OEMs monthly (which GrapheneOS have had access to for years).
So, there are now Pixel-exclusive app features on the Pixel SDK version which isn't available to OEMs - but, it's highly unlikely any app developer would actually depend on these new APIs, since Pixel marketshare is tiny to begin with. This in essence just makes Pixels a weird beta-testing device for what will come out a quarter later to "normal" devices, which is sort of an odd business decision, but also a weird thing to get really mad about, in my opinion (I do see what GrapheneOS are trying to do, with having OEMs saber-rattle about not getting features on the same cadence as Pixels, it just doesn't resonate very loudly for me).
However, the API headline seems to bury a deeper lede; in the thread, GrapheneOS also claim that the quarterly Pixel releases contain security content which is not appearing in the monthly backports. This is quite bad and very sloppy if true, since the Pixel releases can easily be patch-diffed and exploits backed out of them. I'd be interested in seeing this enumerated in more depth.
All of the major OEM shave access to the internal source with a _very_ small delay. OEMs don't ship these intermediate releases because they choose not to, not because Google witholds the source for them.
So now everybody is off worse. Not only are OEMs still slow with security updates, while CVEs float around for months among those within the know (or reverse engineering skills) for months.
Nobody buys a Pixel because of this minute software advantage.
Maybe get Motorola or Samsung to support security updates for six years and get back to Pixel users.
There are currently around 400k to 600k active Pixels with GrapheneOS. There have been far more than that when including the past devices our users have purchased. Pixels are a small segment of the overall market and that's substantial. If you add in people on other operating systems such as LineageOS then there are even more people using Pixels with another OS. A significant portion of people who bought Pixels did so because they were AOSP reference devices.
Samsung provides 7 years of support with monthly updates for their flagship devices. Unlike the Pixel OS, Samsung ships a lot of the security preview patches early.
Motorola Signature (2026) has 7 years of support. The upcoming successor to it is the first non-Pixel meeting all of the update and hardware security feature requirements for GrapheneOS.
Pixel 11 currently doesn't meet our security requirements due to at least temporary lack of MTE support which may get added in Android 17 QPR2. The upcoming Motorola device is also going to be using a 6.18 kernel at launch rather than 6.12. We would have launched Pixel 11 series support already if they met our security requirements. It's likely they will down the road but it's not clear why they omitted firmware and software support for a major security feature at launch. It's the firmware part which impacts us.
Did they though? Or is this just conjecture? Because, honestly, Pixels are not even available worldwide so a few AOSP enthusiasts dropping off and going to Graphene hardly seems concerning for the mighty G.
AOSP reference was a tagline for a few nerds that still wanted the Nexus devices of yore, but it was clear from day one that Google wanted their Pixel phones to be their iPhones.
> I did
Precisely my point.
My first phone was a Motorola that shipped with Eclair. Froyo had already been released and Motorola had a release date for Froyo scheduled in their website. They changed their mind. I don't trust Motorola one iota. Google has never lied to me they way they Motorola has. Good luck.
GrapheneOS has the bootable AOSP and will have Google-alternative device support.
We probably need an equivalent to Play Services, app signing/porting/publishing tools.
With these in hand could we talk Valve into providing the scalable alternative to the play store?
They have replacement portions for Play Services already (attestation, an app store, and location), but it'd be interesting if they also offered something for push notifications.
If you have it to give you can spend your budget on a donation and fund the effort directly.
But to be honest, many banking apps randomly stop working with GrapheneOS anyway. So if you see this...
https://privsec.dev/posts/android/banking-applications-compa...
https://github.com/PrivSec-dev/banking-apps-compat-report
And check the issues, it's unpredictable whether a bank will continue to work with GrapheneOS
So.. if you accept GrapheneOS might not be reliable for this use case, and decide have two phones (one just for banking stuff, another for.. using), then degoogling is fine.
Only thing is that the banking device probably needs to be a phone (or tablet I guess), I don't think you can emulate a real device good enough for it to work on something like Waydroid
Things will keep as is for as long as they keep making these OSs FOR the tech nerds.
Downvote me all you want. You know it’s true. An OS made for nerds and by nerds will never reach mainstream and will not, ever, move the needle anywhere. Tech is no longer a hobbyist’s game.
But Graphene doesn’t mean anything to the general public. People aren’t buying “an iOS device”, they are buying iPhones. People aren’t buying “an Android phone”, they are buying “a Samsung/Galaxy” or a “Pixel”.
Mind you, when I say people, I mean the general population. Not those actually interested in these subjects.
My point is: people don’t care about these specifics, people care about having a frictionless experience (or as close to frictionless as possible). Having to explain what Graphene even is is friction enough for most people to not even bother listening to your explanation.
As a personal device it works pretty well. For ssh terminal and reading markdown, it has by far best display.
Huawei made a big mistake by not fully open sourcing HarmonyOS, you can't flash OpenHarmony so it doesn't count.
I feel like Huawei missed a gigantic opportunity there: forking AOSP may have gotten them traction. I would totally buy a Huawei device if it could run GrapheneOS, and I wouldn't mind if GrapheneOS was based on Huawei's fork rather than Google's.
Regulate them! that is the only way.
Their should be a path for an AOSP build to be just as privileged as a google signed build.
So it seems like the problem isn't that the new API is Pixel exclusive, but that the first and third quarterly release patches each year are Pixel exclusive?
No, these are standard Android APIs included since Android 17 QPR1. These will be available through AOSP and other OEMs via Android 17 QPR2 in December 2026. It's currently exclusive to Pixels because it was released as part of Android 17 QPR1 since QPR1 and QPR3 releases are now Pixel exclusive since Android 16.
This is simply the first time they've added APIs in a QPR1 or QPR3 release following no longer releasing QPR1 and QPR3 to AOSP after the release of Android 16.https://grapheneos.social/@GrapheneOS/117282190165630051
> It would be interesting to know if Google's legal team is aware they're giving Pixels months of early access to new Android features and bug fixes including certain important security patches. Pixels being given this competitive edge over Google's OEM partners is very dubious.
Fixes/updates the modem firmware.
I've a feeling companies like Meta, Amazon, Steam are well placed to do this (esp. Meta and Steam). But not sure it will be helpful to them in any way, besides they'd want to ensure their own control and locks.
By the time the product becomes "popular", it's then just one more platform that needs to follow investor interest and laws.
But at least we can get updated internals for the Q20 (and soon the Passport). It'll be the closest we can get to carrying a BlackBerry for some time, if ever, and I'm happy enough with mine that I picked up a spare mainboard
You're probably asking if they're able contribute anymore?
in terms of accepting, unless it's stuff like bugfixes to core mechanisms, not really.
Go bankrupt, Alphabet!
We live in a time, if you want to build an android app, you easily can, but installing will be harder due to google concerns.
Respect for the GrapheneOS for pushing through regardless, even if they have to reverse engineer stuff. Can't wait to buy their phone.
Good phrasing. It's certainly not _your_ phone, you're just an untrusted user who is extended the privilege of using it.
Oh, the possibilities are endless and they're just getting started. Besides stopping releases of AOSP completely they could also mandate that any "certified" Android device should not allow bootloader unlocking (albeit OEMs will disallow that anyway)..
Nothing will happen, as it never does.
I'm going to start donating to a few free android distros I guess, I'm probably going to be trying them sooner rather than later, and without AOSP support the dev burden is going to be much higher, and it probably means they'll end up diverging and incompatible at some point (not in both directions, lineage will probably always have to have Android app support)
It’s closed too, sure, but at least it’s more consistent.
Google may just want to kill us and Apple don't even let this kind of software exist without massive hurdles...
However at this point, as a GrapheneOS user if I couldn't use it for any reason I'll go to iOS (even though I used it for a couple of years and I've been fed up).
Governments are paid out to not intervene. They should have stepped in decades ago. They should have made Google to release source code and interoperate with public services. They already make profit from their services.
Of course it's not great for their business model. Not to mention, no more trustworthy app distribution.
I don't see the EU really being able to forcing them to de-google android phones.
I am also curious how much those phones would cost, BTW, since the cost calculation to release such an OS would be a bit complicated.
So yeah, don't expect EU to defend you here.
https://digital-markets-act.ec.europa.eu/developer-portal/in...
Side note, that API here is HID. USB HID is so cool. There's so much stuff in this spec! Chargers and batteries can both communicate all kinds of status, which, well, afaik no one does, there's all kinds of sensors. It's this ancient spec that has so much, and weirdly is just so far ahead of where we are. More HID on Android will be great. Wish they'd played with others to make this so though!
This whole topic is basically people demanding that Google continues giving them their code for free for their operating system.
If it's really such a cancer, why whine and demand the continued work then?
Google is trying to take from the community potluck without giving anything back.
The community potluck has been replaced with a Google Play-shaped stock exchange over a decade ago.
Capitalism is transforming to feudalism.
Graphene is reaching that status for me every day and i'm looking forward to switching to it as my daily driver.
The short is that yes the GNOME/KDE apps do often look more impressive, but they suffer the same sort of malaise which seems to have infected Linux desktops sometime since Eternal September, and between the sporadic crashing and "this doesn't feel right", it's really hard for me to accept "It's more polished than AOSP!".
pmOS's installation page opening with a warning:
Make sure you read state of postmarketOS before installing postmarketOS.
The goal is to make postmarketOS usable for everyone, but we are not there yet. Usability and most importantly stability issues need to be worked out first. If you are looking for an OS that is as usable as iOS or Android, this project is currently not for you.
there is clearly no future for android for anyone wanting an open and spyware free platform. its time to invest out efforts elsewhere.
Anyone is free to fork, add the desired hardware support and flash.
(that's aside of some Moto flagships in 2027)
You say they can. How?
This is a real threat, but the reality is that the average person is more likely to be hacked/spied on from the software side, which Graphene would protect you from as effectively as it does on Pixel.
[0]: https://www.claimsjournal.com/news/national/2024/03/15/32248...
Not to mention to reach GOS’ requirements the cost of the phone would have to significantly increase which I imagine only hurts Android phones even more for no real gain since GOS users are minuscule overall.
And the long term support is definitely not the norm yeah. It’s pretty much just Apple and Google doing it for their own devices. Motorola will be a newcomer to this concept with GOS. But we can only wait and see if they actually stick to it, given their track record prior to the collaboration.
Google probably got away with it cause they made the chips and security chips themselves. I read something like Tensor costing $70 vs. a Qualcomm chip with MTE costing $250.
But even with of all this, it wouldn’t make sense for GOS to spend it’s limited resources developing for a less secure platform when appropriate target devices exist (they mentioned something to this effect a few days ago on reddit too): https://www.reddit.com/r/GrapheneOS/comments/1wifsiq/comment...
Back then the primary goal was checkboxes for the carrier to advertise and UI/UX was a distant second priority at most. Sometimes an advertised feature would just flat out be unusable (such as MP3 players), but good luck waiting for any kind of update because by then those developers had already been reassigned to the next handset model they promised to carriers.
Also, Samsung extensively customizes their OneUI fork of Android, with its own UI look and feel that evolves independently from Android based on their own priorities. Plus Samsung's Android maintains hundreds of features that either don't exist at all on AOSP/Pixels or later get folded into mainline Android.
(Including the little known killer app suite "Good Lock" available on Samsung's Galaxy store which gives power users an almost obscene amount of additional niche options and customizations that would give UX minimalist designers at Google or Apple a heart attack)
But despite how different Pixel vs. OneUI look and feel, I can use the exact same apps whether on a Pixel or Galaxy or $100 trash phone. Interoperability is very easy to take for granted and Android app ecosystem is (still) paradise compared to the lowest common denominator J2ME "app" era of the 2000s.
Oracle was a mighty powerhouse when it bought MySQL, StarOffice, and more. It lost defacto control of all of them, due to its stupidity. In the world of open source, the tighter you hold on, the less likely you'll retain control.
And yet, here we are, with Google playing games.
Google, a note: there are far more relying upon Android than you, and now there are forced alternative stores in the mix. If Samsung and everyone else said "sorry Google', or even a large majority, you're out. Gone. Nada.
They can now fork, and force old Android to have their new fancy pants 'Play' store too.
Google is also getting more and more pushy with Chrome. What if everyone depending upon that backend, shrugs and says "Sorry Google, we're hard-forking Chrome and we'll all maintain it".
The OEMs are incapable of writing a competent operating system, and don't particularly care to.
> Google is also getting more and more pushy with Chrome. What if everyone depending upon that backend, shrugs and says "Sorry Google, we're hard-forking Chrome and we'll all maintain it".
With what maintainers?
https://chrome-commit-tracker.arthursonzogni.com/organizatio...
It definitly still is. We run Postgres when we host our banking / financial stuff, but when we talk with banks and say that, they demand Oracle not that 'open source amateur stuff'. We have a version of our software for Oracle (and MSSQL) as well so no biggy, but still, we always try if we know it's not a complete immediate kill (which it will be if we put it in our documentation as only option). Oracle is still everywhere at the big guys.
Our Oracle license licensing went up so dramatically that the team I work with is moving some very large databases to postgres from Oracle because it doesn’t make financial sense anymore.
now, if we could only stop eating at the trough of Broadcom…
Postgres ftw. Long may it eat their lunch.
Oracle used to be a must-have because it was one of the few products that could handle transactions on a scale of a bank, with all the requirements for backups, redundancy, etc.
A fun anecdote. Back in 2000, I was present at negotiations (as a note-taker) where database vendors were bidding for a project for a factory control system. Vendors submitted benchmark results for various DB sizes up to 40Gb, and Oracle's rep hautingly said something like: "Our minimal size for benchmarks is 80Gb, so here are our results for that size".
And this was a _lot_ for that time. Now? It's so ridiculously tiny that you can host it on a smartwatch. So why would you pay Oracle?
They have their private own agreements with Google to secure whatever access they need to maintain their OneUI fork and are not the one making any public complaints. Samsung did have a love/hate relationship with Google that was openly simmering with resentment during the early years of Android but those days are long past.
Samsung already includes their own Galaxy store alongside the Play Store on all their devices, and have for 10+ years. But during that time have actually moved the opposite direction from your hypothetical fork scenario and both companies clearly view their current relationship as mutually beneficial.
Even though GrapheneOS and Samsung both maintain their own Android fork their views on AOSP/Google are not aligned.
Anything Oracle doesn't have much relevance. They were not really interested in growing any marketshare of those products for anyone.
Who will step up to maintain it? Keep in mind that it has to be somebody that every other OEM trust. In other words it would likely have to be an alliance of manufacturers. And they'd inevitably treat OEMs outside the alliance poorly and we'd be back to the current situation, but worse.