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

161–170 of 658 posts

Re: Android Oreo

#161

Post by cmurf »

JorgeGT wrote: post #118
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.

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

My Moto G3 (2015) came with Android 5.1.1, and got an Android 6.0 upgrade. That's it. It has had two or three security updates since then, but it's still Android 6.0.

Despite that, it's been overwhelmingly the best phone I've had: cheap even unlocked, stable, no bloatware, waterproof.

Re: Android Oreo

#162

Post by fenwick67 »

ringaroundthetx wrote: post #123
rukenshia wrote: post #68

Earlier quoted context omitted.

I hoped they wouldn't follow through with the new emoji style. Going to miss the blobs a lot.

why? those expressions were completely incompatible with what other phone users were seeing or sending

You are correct in some cases but not in a majority.

Re: Android Oreo

#163

Post by izacus »

JorgeGT wrote: post #118
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.

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

Yes, the limited availability of Google Store and Google hardware in general is a huge failing of the company.

I really don't understand why they so commonly fail to bring best Android devices to markets with most Android penetration - they're practically giving the market share away to Apple's aggressive price cuts lately.

Re: Android Oreo

#164

Post by pjmlp »

dcomp wrote: post #122
pjmlp wrote: post #72

Earlier quoted context omitted.

As I commented in another HN story, I don't believe OEMs and telecom operators will release updates, if Google doesn't force them to do so. They already admitted on the ADB Podcast that they don't want to remove the ability for OEMs and mobile operators to customize their forks of Android. We will still be forced to buy new devices even if they are VTS certified.

> VTS certified If it passed VTS it should be able to run AOSP. The new CTS will be an AOSP System image running their VTS passing "drivers". Even if your vendor doesn't push any updates. At least you should be able to run a number of newer versions of AOSP as long as Android doesn't deprecate those VTS drivers.

Usually common users don't flash their devices and that is what matters for the Android dashboard.

Re: Android Oreo

#165

Post by zacmps »

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…

I'm pretty sure this is called 'peeking'. You can disable it specifically in the power notification controls. Level 2 is (iirc) what you want.

Re: Android Oreo

#166

Post by on_and_off »

JorgeGT wrote: post #118
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.

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

I would really like to see Google take Oreo as an opportunity to set an example and push the pixel 2 with something like 10 years of support.

I am not holding my breath though

Re: Android Oreo

#167

Post by zacmps »

zacmps wrote: post #165
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…

I'm pretty sure this is called 'peeking'. You can disable it specifically in the power notification controls. Level 2 is (iirc) what you want.

Level 3 actually.

Re: Android Oreo

#168

Post by pjmlp »

kevincox wrote: post #124
pjmlp wrote: post #72

Earlier quoted context omitted.

As I commented in another HN story, I don't believe OEMs and telecom operators will release updates, if Google doesn't force them to do so. They already admitted on the ADB Podcast that they don't want to remove the ability for OEMs and mobile operators to customize their forks of Android. We will still be forced to buy new devices even if they are VTS certified.

The sad thing is that it shouldn't be on Google to force them. It should be Google to enable them and the users to "force" them. They have argably been enabled for a while, but Treble is making it even easier. Hopefully this pushes the needle over the line for at least some OEMs/teclos.

In Germany there are quite a few stores still selling budget Android 4.4 and 5.1 devices, which people keep on buying.

Re: Android Oreo

#169

Post by izacus »

ringaroundthetx wrote: post #123
rukenshia wrote: post #68

Earlier quoted context omitted.

I hoped they wouldn't follow through with the new emoji style. Going to miss the blobs a lot.

why? those expressions were completely incompatible with what other phone users were seeing or sending

No they weren't.

Re: Android Oreo

#170

Post by peterjlee »

pervycreeper wrote: post #6
Freak_NL wrote: post #3

A non-generic brand name for their O-release? Did they strike a deal with Nabisco/Cadbury? I can't imagine Google doing this without some form of legal go-ahead from the trademark owner.

Of course. Would be interesting to know what the exact quid pro quo is for deals like this though (who pays whom, and how much, etc.).

When Kitkat came out, they decided it was mutually beneficial and didn't pay each other.
Post reply on HN