Live data from Hacker News

Android Oreo

android.com

631–640 of 658 posts

Re: Android Oreo

#631

Earlier quoted context omitted.

Demonstrating how much Microsoft bends over to maintain backwards compatibility. Something that for all their other flaws they should be applauded for.

You mean the APIs. But I wasn't talking about those, but rather the hardware - the only thing that you need there is ABI (or at least API) stability for drivers. So you can pull the same thing off with Linux, as well. Basically, modern desktop OSes can run on decade-old hardware, although they will have reduced functionality due to some missing features.

Which is why the sales have dropped more than 30% over the last couple of years.

Obviously, OEMs don't want this trend to continue.

Re: Android Oreo

#632
post #544

Earlier quoted context omitted.

>and Project Treble does not signficantly change this This hits the nail on the head. ProjectTreble thing will make no significant change in the long run. OEMs don't care about updating Android, they only care about selling hardware and developing shitty custom launchers. Google is the only one that could change this. They could "tie" the Android licensing (Play Store and their custom bits) to forcing the OEM to rele…

To be honest, I think Google has LG, HTC, Sony, Nokia, Lenovorola, and almost every other Android manufacturer in the pocket here. These companies don't have the capabilities to independently make a competitive OS and app ecosystem and will have to comply with Google wherever it goes. With the exception of LG, all of these companies have even significantly dialed down their efforts to customize Android from AOSP or "…

Honestly, I'm not sure it's any threat from Samsung that means Google won't do this. I think it's (justified) fear from their legal team that adding any additional licensing terms to the Play Store right now given the European Commission are about to come down on them like a ton of bricks under anti-competition law is suicidal.

Shame Google wasted a lot of capital they had trying to do some really silly things in Android for a few years, and didn't lance this boil while they still had the chance.

Re: Android Oreo

#633
post #426

Earlier quoted context omitted.

Actually since Google is still allowing customizations, it will hardly change anything.

They can impose whatever they want to OEMs who want to ship the Play Services and Google apps. That's pretty much all of them. If they say "install it this way or no Play Store for you", every manufacturer will follow.

They almost certainly cannot do that in Europe at the moment given the regulatory situation. Indeed, I expect to see far fewer restrictions going forward, not more.

Re: Android Oreo

#634
post #609

Earlier quoted context omitted.

The iPhone doesn't suffer from this problem. It should be up to the phone manufacturer (HTC, Samsung, etc.) to test their product. The carrier can still, of course, test the new firmware all they like - they just shouldn't be able to interfere with its release.

Apple makes products available to carriers pre-launch for testing IIRC. I don't think they skip the line.

They certainly have the market power to skip the line, but they still go in the line, unlike some suggestions here.

Re: Android Oreo

#635

Earlier quoted context omitted.

You've said this in a few different places, do you have a source for that? You are saying you could load AOSP on an S9 regardless of what Samsung does? If so, this is indeed huge, but I have some serious doubts about it, perhaps because I have felt so very burned by Android so many times in this respect on anything but Nexus devices.

Maybe - the bootloader must allow you to run that AOSP ROM, which only is possible if the bootloader isn't locked. Lots of OEM:s lock their bootloaders. But otherwise, yes, there's nothing else stopping you.

There are a bunch of things potentially stopping you in practice. The HAL isn't a total wall, and I expect to see many OEMs go around it in some places, either due to incompetence, the HAL being inflexible, or timescales.

So even in situations where you can install such a ROM, there's very little guarantee key bits of hardware will operate properly. Any non-standard hardware/hardware feature is also fairly likely to break.

Re: Android Oreo

#636

Earlier quoted context omitted.

Really OT but since you brought it up, I legit just started reading the book yesterday and this is my first DFW book. Looks kinda daunting, any advice?

keep an organized notebook while you read this book. of characters, ideas, events (which happen non-chronologically), etc. not being pretentious -- you will actually need it. I've been reading this book on and off for about four years now, and wish I had started with a notebook from the beginning. don't get discouraged if some passages are boring -- make a note of them and just power through them. it's so, so worth i…

I like to read but I don't challenge myself all that much so I'm afraid I'll be in over my head, would you recommend checking something out to sort of "prepare" myself?

Like watching Tarkovsky straight from Michael Bay is not something I'd recommend, I'd tell them to watch some Nolan for contemporary, then Kubrick and stuff before going for Solaris. Is there an equivalent?

Re: Android Oreo

#638

Earlier quoted context omitted.

I imagine there are plenty of instances where apps do not account for space well

Frankly i get the feel that most apps don't care. They develop for a certain size and resolution, maybe what is currently on the Samsung flagship, and if it also work outside of that box they are happy. And if not they simply flag it as not supported in the Play store. Android has had from day one all manner of capabilities for fitting a UI to different devices. But still i run into UIs that seems fixed in some manne…

> Photoshop designer with a chip on their shoulder.

I think you are attributing malice to something where laziness would be an easier explanation. As an occasional Android dev, I know the laziness problem all too well when trying to get UI to fit multiple devices.

Re: Android Oreo

#639
post #405

Earlier quoted context omitted.

Do you have any facts to back this up? Prior to the iPhone changing how phones were sold-- carriers meddled with everything so they could get their hands in media playback, app sales, feature upgrades etc. I don't think much has changed in this where anyone gives them an inch (which is nearly everyone but Apple). Note: I worked for T-Mobile for four years prior and a little after the originals iphone came out.

Before the iPhone, how prevalent were software updates to phones? I know of no one who ever got had an update. There is absolutely no reason for carriers to need to do anything at all, else it would not make sense that I can change the SIM card out and voila I’m on a new carrier. The manufacturer is the one doing the testing, and the carrier simply provides the infrastructure. I feel US perhaps has a different experi…

My Nokia 5800 went through several UI redesigns via OTA updates.

Re: Android Oreo

#640

Earlier quoted context omitted.

Most people don't think about such things when buying (renting) a new phone. If you do consider it, you're an exception to the rule.

What do you mean rent? I buy my phone. It's mine. I can put it on any network I like.

You certainly can't put whatever software on it that you like. They go well out of their way to ensure that.
Post reply on HN