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

51–60 of 135 posts

Re: AOSP project is coming to an end

#51

Post by fsflover »

transpute wrote: post #13

Hopefully AOSP Pixel device support is merely delayed, not ended, since Pixel is the only way to get Debian Linux ("Terminal") VM + desktop mode support, https://news.ycombinator.com/item?id=43973395 . With Apple's ongoing refusal to enable VM/JIT support on iOS and iPad, Google Pixel + GrapheneOS + Debian is a very competitive 2025 offering.

> since Pixel is the only way to get Debian Linux ("Terminal") VM + desktop mode support

My Librem 5 also offers the desktop mode, since it just runs a desktop OS based on Debian (PureOS).

Re: AOSP project is coming to an end

#53

Post by swiftcoder »

Aachen wrote: post #39
charcircuit wrote: post #24

Earlier quoted context omitted.

Looking at how it works for Wear OS. Qualcomm still only hosts the repos for the BSP and not the whole OS. It's expected to still get those from Google, from the partner portal.

> (BSP) is the layer of software containing hardware-specific boot loaders, device drivers, in sometimes operating system kernels, and other routines https://en.wikipedia.org/wiki/Board_support_package presumably. Never heard that TLA in my life and it's not like I've not gotten my hands dirty in Android

Unless you are actually shipping a custom device running Android, there's very little reason for most developers to poke that far down the stack

Re: AOSP project is coming to an end

#54

Post by lipowitz »

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.

They've raised the prices so one is looking at a 1 year old a-series to pay $300. Meanwhile they are even further behind the curve hardware wise.

It would be very nice (but a tremendous effort) if Graphene OS took this opportunity to switch hardware preference right before Google's August release. Maybe to someone who could make a modern tablet too.

Re: AOSP project is coming to an end

#55

Post by safety1st »

transpute wrote: post #13

Hopefully AOSP Pixel device support is merely delayed, not ended, since Pixel is the only way to get Debian Linux ("Terminal") VM + desktop mode support, https://news.ycombinator.com/item?id=43973395 . With Apple's ongoing refusal to enable VM/JIT support on iOS and iPad, Google Pixel + GrapheneOS + Debian is a very competitive 2025 offering.

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?

Re: AOSP project is coming to an end

#56

Post by raffael_de »

transpute wrote: post #13

Hopefully AOSP Pixel device support is merely delayed, not ended, since Pixel is the only way to get Debian Linux ("Terminal") VM + desktop mode support, https://news.ycombinator.com/item?id=43973395 . With Apple's ongoing refusal to enable VM/JIT support on iOS and iPad, Google Pixel + GrapheneOS + Debian is a very competitive 2025 offering.

After years of being stuck with iPhones I'm also eager to soon switch back to Android. iOS always just felt like a polished compromise. Have been a happy customer of LOS using OnePlus devices. But LOS always also seemed a little opaque and casual. Hence I set my eyes on GrapheneOS and in consequence on a device from the Pixel lineup.

Re: AOSP project is coming to an end

#57

Post by jampekka »

misnome wrote: post #48
fc417fc802 wrote: post #34

Earlier quoted context omitted.

If it was really about security (in the sense of that which benefits the end user) they'd just stick it behind a toggle and be done with it. I just think it's important to call out the misalignment - security can refer to the interests of the end user, or alternatively to the vendor. The ambiguity is convenient for PR statements.

We’ve decades of examples of simple toggles not working. Bad actors will just explain to the target the necessity of switching it on.

Put it in the bootloader then.

The pretence that Apple makes these things for security reasons and there's absolutely no way in the world to make it possible is a bit ridiculous.

Re: AOSP project is coming to an end

#58

Post by vbezhenar »

pzo wrote: post #7

sad, was thinking to switch from iPhone to pixel 10 in few months once released exactly for the reason that is clean android and gives and escape hatch to use grapheneOS or lineageOS or calysOS. Any other android phone manufacturer that is supported by any of those projects? Most devices supported except pixel devices are few years old.

I tried to switch from iPhone to Pixel and switched back. Modern Pixel is absolutely not clean android. It's a mess of misfeatures. There's no clean android. iPhone is lean and compact compared to Android. GrapheneOS is solid, but built by security freaks, so unless you're a fan of OpenBSD, it makes little sense to use it. And any custom ROM locks you out of many important apps, like banks apps, NFC payments, etc (unless you want to actively combat integrity system).

Re: AOSP project is coming to an end

#59

Post by bluebarbet »

SlowTao wrote: post #33

While the title is jumping the gun a little, it is only a matter of time until I suspect this will be real. Give it maybe 5 years Max. That said, first rule of predictions, don't provide a time frame.

This is my take, too. I'm surprised by all the skepticism here, it looks to me like another case of techies not being able to see the wood for the trees.

These companies believe that AI puts them in an existential battle for survival. They're battening down the hatches. Concepts like open source and community collaboration can only look like unaffordable luxuries in such a context. Quaint, even.

IMO the last remaining hope for free software is going to be an entirely separate hardware-OS ecosystem, plus funding and lobbying to ensure that the web platform remains competitive.

Re: AOSP project is coming to an end

#60

Post by Teever »

misnome wrote: post #48
fc417fc802 wrote: post #34

Earlier quoted context omitted.

If it was really about security (in the sense of that which benefits the end user) they'd just stick it behind a toggle and be done with it. I just think it's important to call out the misalignment - security can refer to the interests of the end user, or alternatively to the vendor. The ambiguity is convenient for PR statements.

We’ve decades of examples of simple toggles not working. Bad actors will just explain to the target the necessity of switching it on.

But we have another example to look at. Why isn't this a big problem on Apple laptops?
Post reply on HN