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.
AOSP project is coming to an end
121–130 of 135 posts
Re: AOSP project is coming to an end
#122One could fork AOSP, but the Android SDK is not open source, is it?
Re: AOSP project is coming to an end
#123Earlier 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…
Re: AOSP project is coming to an end
#124Earlier 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.
Re: AOSP project is coming to an end
#125Earlier 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.
Re: AOSP project is coming to an end
#126Earlier 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.
You're underestimating the strength of the reality distortion field.
Re: AOSP project is coming to an end
#127Earlier 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
Re: AOSP project is coming to an end
#128Earlier 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.
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
#129Correct title would be: Google is locking Google Pixel platform.
Sounds more like "Google Pixel is no longer the reference device for AOSP"
Re: AOSP project is coming to an end
#130Earlier 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