Live data from Hacker News

AOSP project is coming to an end

old.reddit.com

121–130 of 135 posts

Re: AOSP project is coming to an end

#121

Earlier quoted context omitted.

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

The copyright holder can change the license for new versions. Copyleft does not matter.

It does when there are many copyright holders, like famously in Linux.

Re: AOSP project is coming to an end

#122
Hypothetically, what would happen to the Android SDK and all those developer tools if Google was to go proprietary with AOSP?

One could fork AOSP, but the Android SDK is not open source, is it?

Re: AOSP project is coming to an end

#123
post #26

Earlier quoted context omitted.

> (Xiaomi, Motorola, OnePlus), none of which are even close to state-of-the-art hardware. Well, Pixel is arguably pretty shitty hardware as well

I truly hate how crappy their processors are, it's insane that their upcoming flagship will have the same performance as a three year old flagship. you don't need it, it's just a phone . Yeah maybe now, but in two years when the pixel is shitting itself you will understand. If GrapheneOS dies, that's probably it for me with pixels. The only advantage left is how cheap you can get a new flagship pixel on the gray mark…

The Pixel 10 ought to have a TSMC SoC (https://www.androidauthority.com/google-pixel-10-3470386)

Re: AOSP project is coming to an end

#124

Earlier quoted context omitted.

> Most devices supported except pixel devices are few years old. That pretty much sums it up, there's a reason all of those custom ROMs pivoted to supporting basically just Pixels. Apart from Pixels, your only options are Fairphone and a few years old Chinese models (Xiaomi, Motorola, OnePlus), none of which are even close to state-of-the-art hardware. Custom ROMs are pretty much dead, this just might be the final na…

this is not true at all. the 1yr old OP12 has LineageOS and so does the 6 months old 13R, with support for the 13 incoming.

I see only oneplus 11 in the officially supported phones list. I'm not interested in unofficial port - in the era of SGS2 I played many custom unofficial rooms but this days I don't have time for it

Re: AOSP project is coming to an end

#125
post #118

Earlier quoted context omitted.

Never mind, it seems like they're thinking of wasting their time with a custom ODM-built smartphone. I truly hope they won't choose this route. If they do someone should add "Will the GrapheneOS-Phone fail?" on Polymarket, I'll bet my parents' house on it.

> custom ODM-built smartphone I agree that this would be a crazy choice and doomed to fail.

could you elaborate why?

Re: AOSP project is coming to an end

#126
post #78

Earlier quoted context omitted.

Apple shipped hypervisor support back in iOS 16, then removed it! https://taoofmac.com/space/blog/2024/07/25/0900

This is a nice post of things that bothers me in the Apple ecosystem: arbitrary limitation after arbitrary limitation. I didn't know about the Apple Watch couldn't pair with an iPad, and I don't think even an Apple fanboy could make an excuse for that one.

> I don't think even an Apple fanboy could make an excuse for that one.

You're underestimating the strength of the reality distortion field.

Re: AOSP project is coming to an end

#127
post #39

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

This acronym is somewhat known in Android device hacking communities that try to replace Android with Linux or Windows, because these communities usually deal with understanding the bootloader and Qualcomm distributes bootloader sources from what I remember in their BSP.

Re: AOSP project is coming to an end

#128
post #120

Earlier quoted context omitted.

An estimated 3M iOS developers would generate $300M developer fee revenue. App store revenue is around $100B, or 300X estimated developer fees.

Still, "developers did not pay any commission to Apple" is wrong.

If the full sentence is referencing sales commission, then the fixed developer fee would not qualify, since it's not a percentage of revenue, https://www.collinsdictionary.com/dictionary/english/sales-c...

  Sales commission is the percentage of the value of a sale that a sales associate or sales representative may earn.

Re: AOSP project is coming to an end

#129

Correct title would be: Google is locking Google Pixel platform.

Sounds more like "Google Pixel is no longer the reference device for AOSP"

Indeed. Also remember that android supports multiple form factors and pixel at best served as. reference only for phones. Auto, watches, and tablets were ill served. Cuttlefish, the replacement, works for all form factors.

Re: AOSP project is coming to an end

#130

Earlier quoted context omitted.

Can’t you already do that? If you pay 99/year you can sign your own apps with whatever entitlements no? You just can’t submit them to the Apple Store for obvious reasons

It was removed, https://news.ycombinator.com/item?id=44255512

Hypervisor yeah but it’s still possible for code in debug mode - there is even an app that automates the process for you https://github.com/osy/Jitterbug (requires a paid dev account)
Post reply on HN