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

111–120 of 135 posts

Re: AOSP project is coming to an end

#111

Post by lipowitz »

vbezhenar wrote: post #109
lipowitz wrote: post #71

Earlier quoted context omitted.

I don't see what OpenBSD has to do with it. Is this like liking reliability in a car meaning you are a Toyota fan? I've had no trouble with banks, brokers or payment networks on GrapheneOS but I don't use crap like company-X pay wallets..

GrapheneOS is not just AOSP rebuild. They do an astonishing amount of work to harden Android. They have a lot of security and privacy-related features. They built a custom layer over Google Services to contain them. I admire this effort. However I don't care that much about my privacy and I don't care about extended security. All I want is a basic Android system without any of added apps, without any AI. I want the m…

It takes a lot of work for them to push google apps into its own permissions system etc, but its not like you feel that as a user..

Its similar to what the Linux distributions that try to turn on a SeLinux like profile by default would feel like if they really put in the work. That's nothing like switching (from a Linux) to a BSD.

(I would love to just run my desktop Linux with a half baked touch UI and rely on browser versions of almost everything, but that would feel like a real switch between OSes instead of just seeing the same OS with a corrected security profile as the user. I also don't see why you compare it to an Abrams, I doubt an Abrams has a security model intentionally compromised by an ad company, GrapheneOS just makes it possible to catch the dumbest or laziest attacks on a system no one should run ever.)

Re: AOSP project is coming to an end

#112

Post by belowaverageiq »

xnx wrote: post #97

Not true. From the Android VPN and GM: "We're seeing some speculation that AOSP is being discontinued. To be clear, AOSP is NOT going away. AOSP was built on the foundation of being an open platform for device implementations, SoC vendors, and instruction set architectures. AOSP needs a reference target that is flexible, configurable, and affordable – independent of any particular hardware, including those from Googl…

Ready-made AOSP device trees for Pixels, which are needed to build custom ROMs, are the ones going away. This is a blow to GrapheneOS as they have been dedicating 100% of their time to improving their ROM itself in the past few years.

Since at this point they'll need to create device trees like LineageOS does with Snapdragon/MTK phones, so I hope they won't stick with the worst Android manufacturer on Earth. Especially now that the snapdragon 8 elite 2 will have the same security features as the Tensors.

Re: AOSP project is coming to an end

#113

Post by belowaverageiq »

belowaverageiq wrote: post #112
xnx wrote: post #97

Not true. From the Android VPN and GM: "We're seeing some speculation that AOSP is being discontinued. To be clear, AOSP is NOT going away. AOSP was built on the foundation of being an open platform for device implementations, SoC vendors, and instruction set architectures. AOSP needs a reference target that is flexible, configurable, and affordable – independent of any particular hardware, including those from Googl…

Ready-made AOSP device trees for Pixels, which are needed to build custom ROMs, are the ones going away. This is a blow to GrapheneOS as they have been dedicating 100% of their time to improving their ROM itself in the past few years. Since at this point they'll need to create device trees like LineageOS does with Snapdragon/MTK phones, so I hope they won't stick with the worst Android manufacturer on Earth. Especial…

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.

Re: AOSP project is coming to an end

#114

Post by microtonal »

bubblethink wrote: post #99
ThatMedicIsASpy wrote: post #96

Earlier quoted context omitted.

I use my monitors, TVs, PC hardware for 10 years+. Things dying after 3 years is a big fucking deal. WTF is wrong with you.

The software also used to be supported for only that long. Support cycles have been getting longer, but so has the price. Batteries also die in a few years.

There are many people who use 5 year old or older iPhones. My dad uses an iPhone 12 (2020), my mum an iPhone 11 (2019), someone else in my family still uses an XS (2018). In one of these cases a dying battery was replaced (which is still much cheaper than a new phone). They all still work very well and fast.

Also a lot of folks around still sporting Samsun S20 (though they should probably ditch them now due to the lack of security updates).

Getting only 2-3 years of life is very bad for most people.

Re: AOSP project is coming to an end

#115

Post by ranger_danger »

immibis wrote: post #92
fc417fc802 wrote: post #47

Earlier quoted context omitted.

I believe the device tree stuff is GPL due to the kernel. Might be mistaken though.

A device tree is probably counted as data, so not copyrightable. I am not a lawyer and this is not legal advice. But there's plenty else that is GPL, and in AVM vs Sebastian Steck, it seems that even LGPLv2 requires the manufacturer to give you all the stuff you need to install a modified version of the software, i.e. it seems that all GPL licenses imply anti-tivoization.

> AVM vs Sebastian Steck

That case was dismissed because they settled privately, so technically it does not prove anything about LGPLv2, and Germany is not as big on blindly following precedent in law as other countries anyway.

Re: AOSP project is coming to an end

#116

Post by [deleted] »

lipowitz wrote: post #54
bubblethink wrote: post #49

Earlier quoted context omitted.

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.

[deleted]

Re: AOSP project is coming to an end

#118

Post by xnx »

belowaverageiq wrote: post #113
belowaverageiq wrote: post #112

Earlier quoted context omitted.

Ready-made AOSP device trees for Pixels, which are needed to build custom ROMs, are the ones going away. This is a blow to GrapheneOS as they have been dedicating 100% of their time to improving their ROM itself in the past few years. Since at this point they'll need to create device trees like LineageOS does with Snapdragon/MTK phones, so I hope they won't stick with the worst Android manufacturer on Earth. Especial…

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

#119

Post by xnx »

belowaverageiq wrote: post #112
xnx wrote: post #97

Not true. From the Android VPN and GM: "We're seeing some speculation that AOSP is being discontinued. To be clear, AOSP is NOT going away. AOSP was built on the foundation of being an open platform for device implementations, SoC vendors, and instruction set architectures. AOSP needs a reference target that is flexible, configurable, and affordable – independent of any particular hardware, including those from Googl…

Ready-made AOSP device trees for Pixels, which are needed to build custom ROMs, are the ones going away. This is a blow to GrapheneOS as they have been dedicating 100% of their time to improving their ROM itself in the past few years. Since at this point they'll need to create device trees like LineageOS does with Snapdragon/MTK phones, so I hope they won't stick with the worst Android manufacturer on Earth. Especial…

The Pixel device trees going away is very disappointing, but he headline "AOSP project is coming to an end" is an exaggeration.

Re: AOSP project is coming to an end

#120

Post by palata »

transpute wrote: post #101
AJRF wrote: post #86

Earlier quoted context omitted.

> 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.

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.
Post reply on HN