Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

AOSP project is coming to an end

old.reddit.com

Post reply on HN
Print view View original

81–90 of 135 posts

Re: AOSP project is coming to an end

#81

Post by alfiedotwtf »

bubblethink wrote: post #49
flanbiscuit wrote: post #30

Earlier quoted context omitted.

I'm moving away from Pixel Phones for my next Android. Going to switch back to Samsung. I currently have a Pixel 8 and my screen went completely green and glitchy yesterday (Google "android green screen", it's a hardware issue). It freaked me out because Im in the beginning of a long vacation with tickets held digitally in various apps and email. Thankfully I eventually figured out the solution which is ridiculous, w…

You need to manage your expectations with Pixel devices. They are often on sale. Buy the A series for ~$300, which is also what the Nexus phones used to be priced at. They easily last 3+ years, and if they die after that it's no big deal. Dying early, bootlooping, overheating, etc. have been a part of these devices since they have existed.

The worst but I’ve ever had with early Android was they never kept time properly! Set an alarm to wake you up, and when you eventually woke up, clock skew was out over an hour!

Re: AOSP project is coming to an end

#82

Post by alfiedotwtf »

onli wrote: post #31
DidYaWipe wrote: post #21

Can you even use the Play store on AOSP? I was interested in trying it (I don't use Android currently) but from what I gathered it seemed like a bit of a fraud (on Google's part) because it was fundamentally gimped.

You can on ROMs like LineageOS. The Play Store is part of the Gapps package some users install during the installation of the system. Alternatively there is microG and the Aurora Store, so the play store itself isn't needed. I assume that is the same situation on raw AOSP.

It’s been a while, but is LineageOS still going strong? I’ve been thinking of switching back to non-iPhones for a while

Re: AOSP project is coming to an end

#83

Post by nabogh »

zeech wrote: post #3

From https://calyxos.org/news/2025/06/11/android-16-plans/ - > Google did not publish any device-specific source code for supported, modern Pixel devices. > In previous years, Google released full device trees alongside new Android versions. This allowed developers to build and boot AOSP on Pixel hardware relatively easily. > With Android 16, only the platform/framework code has been released. The device trees are mi…

That's awful. I bought a pixel because the ecosystem around alternative android roms was healthy. This seems to change that.

Why can't I just get a general purpose computer in my pocket? Why is everything so hostile? I am willing to pay!

Re: AOSP project is coming to an end

#84

Post by onli »

alfiedotwtf wrote: post #82
onli wrote: post #31

Earlier quoted context omitted.

You can on ROMs like LineageOS. The Play Store is part of the Gapps package some users install during the installation of the system. Alternatively there is microG and the Aurora Store, so the play store itself isn't needed. I assume that is the same situation on raw AOSP.

It’s been a while, but is LineageOS still going strong? I’ve been thinking of switching back to non-iPhones for a while

I get the impression, yes. They still have a big list of supported devices, which means many maintainers, and they managed well to port their system to new android versions, even if a recent point release killed many devices. Have a look at https://wiki.lineageos.org/devices/, or alternatively my ROM finder https://www.sustaphones.com/.

However, I personally switched to CalyxOS. I was a bit unhappy with LineageOS pushing users towards the Gapps, by blocking microG from working properly (they blocked signature spoofing, a problem during the pandemic) and by forbidding discussions about microG on their subreddit, together with forbidding to even talk about issues with VoLTE or anything that touches rooting the system. They course corrected only a little bit with the signature spoofing, but still project user hostility otherwise via those rules. CalyxOS gave me a more usable system out of the box, while having a bigger focus on security (locking the boot loader) and presenting the project nicer. Vastly less devices supported though, and if pixels go closed now the Calyx project would have to implement big changes, those were their main devices.

Re: AOSP project is coming to an end

#85

Post by pwdisswordfishz »

raffael_de wrote: post #52

On a tangential: I recently found out that using Kagi it is possible to configure RegEx replacements in the search results (this makes it possible to replace "[www.]reddit.com" with "old.reddit.com").

Unfortunately the old.reddit.com frontend does not support /s/ links.

Re: AOSP project is coming to an end

#86

Post by AJRF »

transpute wrote: post #75
alerighi wrote: post #72

Earlier quoted context omitted.

It's not about security. Apple doesn't want to open on external applications, including the one run in VM/emulators, because it wants every software to pass from the AppStore. Not because security, but for the fee it has on app store purchases. If it opens to having VM, you could just run another OS in a VM (Windows, for example) and install normal software on it (like the desktop version of most programs) and not pa…

https://lapcatsoftware.com/articles/2025/6/1.html > For more than 90 percent of the billings and sales facilitated by the App Store ecosystem, developers did not pay any commission to Apple. Would the remaining 10 percent of App Store sales have meaningful competition from a CLI (no GUI) terminal VM that enables development workflows on iPad?

> developers did not pay any commission to Apple

That's certainly a take. The developer fee is $99 a year, that HAS to be paid to put something on the App Store.

Sure they are not getting commision on the download, but they ARE getting their pound of flesh from the developer fee.

Re: AOSP project is coming to an end

#87

Post by bubblethink »

I don't get the motivation behind this RedHatification. Hasn't Google already won in the Android space ? Nobody that matters is forking or using AOSP without Google's blessings anyway due to the stranglehold of Google Play Services. Why the sudden dick move ? I see some mention of the impending antitrust cases, but I don't quite see how that fits.

Re: AOSP project is coming to an end

#88

Post by raffael_de »

pwdisswordfishz wrote: post #85
raffael_de wrote: post #52

On a tangential: I recently found out that using Kagi it is possible to configure RegEx replacements in the search results (this makes it possible to replace "[www.]reddit.com" with "old.reddit.com").

Unfortunately the old.reddit.com frontend does not support /s/ links.

I've no idea what that even is. For me old.reddit is about accessibility while using a VPN and 18+ content (comparison of vaporizers, for example).

I don't want to have an account there, as this just lures me into using it more and engaging in pointless discussions.

Re: AOSP project is coming to an end

#89

Post by maxloh »

bubblethink wrote: post #87

I don't get the motivation behind this RedHatification. Hasn't Google already won in the Android space ? Nobody that matters is forking or using AOSP without Google's blessings anyway due to the stranglehold of Google Play Services. Why the sudden dick move ? I see some mention of the impending antitrust cases, but I don't quite see how that fits.

> Nobody that matters is forking or using AOSP without Google's blessings anyway due to the stranglehold of Google Play Services.

What about Amazon's tablets?

Re: AOSP project is coming to an end

#90

Post by safety1st »

jampekka wrote: post #61
safety1st wrote: post #55

Earlier quoted context omitted.

Wait what? This is a screenshot of 9 short lines of text from the Reddit image server. What is actually going on? Android source is still Apache licensed right? How are these things becoming closed source? What is happening?

Apache is not copyleft so new versions can become closed source.

You're right, but I am seeing other random Reddit posts that say Google has simply changed their development workflow/branching strategy, and that the claim from the OP is inaccurate.

At the moment we have 200+ upvotes on something that is very light on information, but heavy on confusion. I am just trying to understand what is going on.

Post reply on HN