Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Android Oreo

android.com

Post reply on HN
Print view View original

151–160 of 658 posts

Re: Android Oreo

#151

Post by sebojanko »

komali2 wrote: post #143

Going to take advantage of an Android thread here to ask something that has driven me crazy for ~3 years: How do I disable "pop-down" notifications? i.e. facebook messenger, on receiving a message, drops down a little message box from the top with that message. It stays there for about 2 seconds and then disappears... unless further messages in that chat appears. The only way I can disable this is by muting that chat…

In the Notifications settings, you can adjust every app's notification settings and disable this.

Re: Android Oreo

#152

Post by function_seven »

randyrand wrote: post #74
IkmoIkmo wrote: post #59

Earlier quoted context omitted.

Only they're marketing it with oreo cookie mascot, look at all the material. I highly doubt you can just do that. It's the same with kit kat, they probably couldn't just use that, either. But it's a win-win for both parties, I doubt either of them paid.

It seems like unnecessary legal risk for Google, and probably restricts how they can market it.

There's no risk. They talked to Nabisco, said, "Hey we wanna call the next OS 'Oreo', coo?" And Nabisco said, "Ok."

Maybe money was paid one way or the other. Or not.

What restrictions are you imagining?

Re: Android Oreo

#153

Post by [deleted] »

putlake wrote: post #110
izacus wrote: post #99

Earlier quoted context omitted.

Just like you have to buy an Apple phone to get Apple updates immediately, you need to buy a Google phone to get Google updates immediately. Pixel and Nexus rollout is starting nowish (and beta participants are already getting the OTAs). This is really not a secret at this time anymore and should be taken into account when you succumb to Samsung marketing. Everybody else will be probably 4-6 months late.

But Apple supports iPhones for 4-5 years. Google has said they will only support their flagship Nexus and Pixel phones for no more than 2 years. For a $700 device this is unacceptable.

[deleted]

Re: Android Oreo

#154

Post by semi-extrinsic »

nsriv wrote: post #131
JorgeGT wrote: post #118

Earlier quoted context omitted.

The catch is that you can buy an Apple phone everywhere, but for instance Google decided simply to not offer the Pixel in my country. Also, they stopped updating my Nexus 4 long time ago, something that Apple does not with their devices. Hence, I am not "succumbing to Google marketing" again. I have now updated to a Moto, which used to be a Google company. Let's see how long it takes to update...

This round of updates for Moto will be interesting, as it has a light skin. Completely dependent on Lenovo ownership, and they haven't been making the best choices lately.

FWIW, I still get security bugfix system updates on my 2015 Moto 3G, as recently as two months ago. Here's hoping they keep up this level of support.

Re: Android Oreo

#156

Post by chaz »

fenwick67 wrote: post #22

"new emoji" is an OS-level feature now. Welcome to 2017.

For a lot of people, new emoji are a great reason to upgrade and not miss out. Apple's been training customers to do this for years.

Re: Android Oreo

#157

Post by thinbeige »

ocdtrekkie wrote: post #136
thinbeige wrote: post #130

Earlier quoted context omitted.

I don't think that MS tests all hardware when updating Windows. Sometimes some hardware doesn't work after an Windows update and then you just head to the respective hardware manufacturer and try to get updated drivers. This model could work for phones too. Google updates and maybe my S8's camera is not working anymore but at least we have secure and patched phones. And the good thing is: Samsung has to quickly fix t…

It depends what we're talking about. Specifically with ARM processors, it isn't trivial to add drivers separate from your OS deployment. Microsoft DOES work with (and update) third party hardware directly for Windows 10 Mobile devices. And this is true for their third party phones from HP, Acer, etc. as well. (Note, I have a Windows Mobile device from 2014, and I still receive the latest security fix on Patch Tuesday…

> ARM processors, it isn't trivial

This is what they tell us for decades. You can just disable parts of an SoC if no driver is available. This is just an architectural decision Google is not willing to address.

And ARM reference designs from a handful of manufacturers are not that different.

Re: Android Oreo

#158

Post by bluGill »

zitterbewegung wrote: post #95
amrrs wrote: post #89

Has Google ever released a report on how much time it takes an average flagship device to get the latest android version? Even if you've paid $$$$ in getting Samsung Galaxy S8 just recently, you're not going to get Android O tomorrow morning. But that's definitely the case with iOS. That makes a huge difference in the world where Software updates play a huge role in performance and functionality than hardware update…

Vertical integration has its advantages. Also, due to people buying new phones every 6 months those seem to be the two things that disincentivze Android phone makers to not do those things.

You can change that: don't buy a new phone every six months, and buy from a maker that supports your phone longer. Maybe you cannot get the latest, but when you support the companies that support their phones for more than a few months you support that business model which in turn ensures that someone who updates their phones exists.

You might have to leave the major names behind, and might have to skip a few features. Do you need the latest and greatest anymore though? When Android was new (2008) CPUs were much slower and upgrades did help your experience. (I remember missing calls because my phone couldn't switch to the phone app quick enough).

Re: Android Oreo

#159

Post by thinbeige »

widdma wrote: post #114
thinbeige wrote: post #94

Nice Marketing coop for an OS where 50% of devices won't get updates. I don't get it. They bring frequent major updates with such important features like 60 new emijis or antivirus software instead of just doing their homework and implementing the number one feature for an OS: Direct OS updates from the OS vendor and nobody else. Don't tell me it's a problem and the driver situation is so difficult. This is just a ba…

This release introduces Project Treble with the goal, I believe, of fixing this exactly this problem.

I don't think it will solve the problem because they still want the hardware makes to distribute updates.

Re: Android Oreo

#160

Post by pedrocr »

dcomp wrote: post #108

The most interesting part is the way they are planning on tackling fragmentation in O onwards with Project Treble [0] If your device ships with O it should be running an immutable semantically versioned HAL. In essence you should be able to be able to flash AOSP on every new device. No matter what the vendor does. Edit: I can see it now, in the technical specs of each device you will see a list of HAL Versions. The n…

So you'll still be vulnerable to kernel bugs but most everything else will get regular updates? A bit better I suppose.
Post reply on HN