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

131–140 of 658 posts

Re: Android Oreo

#131

Post by nsriv »

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

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.

Re: Android Oreo

#132

Post by kevincox »

dcow wrote: post #60

Am I the only one who's really disappointed by the platform's shift in its stance on background execution? I was originally drawn to Android because it wasn't iOS. I wanted to develop on a platform where I could run a service in the background if the user wanted that. Apps that were bad stewards of battery life and phone resources were supposed to be scrutinized by users and removed if they were too poor. You can be…

You can disable "Battery Optimization" per app, so this isn't very restrictive. It just applies by default.

Re: Android Oreo

#133

Post by thinbeige »

klondike_ wrote: post #11

Project Treble is the most important thing in this release >The biggest change to the foundations of Android to date: a modular architecture that makes it easier and faster for hardware makers to deliver Android updates. With any luck, this will end the huge security/update problem Android has. Right now an update is dependent on the chip manufacturer's drivers, then the OEM adding them to the ROM with their custom "…

Why do you think so? On that page is just this sentence and nothing more. I don't believe in a significant improvment unless Google takes ownership of all OS updates themselves.

Re: Android Oreo

#134

Post by eitally »

hughes wrote: post #84

Really sad about the loss of the blob emojis. Will probably have to root my phone to use a third party emoji switcher app to preserve them.

And it's not that the new emojis are all necessarily bad. My issue is confusion over what the recipient will see when I select one of the new emojis. I'm still not 100% clear on the emoji set mapping between OEMs/OSes. :-/

Re: Android Oreo

#135

Post by kevincox »

pjmlp wrote: post #73

>Google Play Protect: > Working to keep your device and data safe from misbehaving apps by scanning over 50 billion apps per day, even the ones you haven't installed yet! Also known as anti-virus.

Yeah, also known as a feature that has been around for years but now is being shoved in my face whithout providing any additonal benifit. (I guess I am supposed to feel safer?)

Re: Android Oreo

#136

Post by ocdtrekkie »

thinbeige wrote: post #130
ocdtrekkie wrote: post #121

Earlier quoted context omitted.

Google doesn't want to bear the cost of testing and releasing updates for all of the hardware. Most Android manufacturers barely manage to break even (or outright lose money) trying to sell and support Android hardware. (Samsung makes money, most others don't.) Blaming the OEMs for your security issues is free.

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 around 1 PM, every month.)

Re: Android Oreo

#137

Post by MBCook »

thinbeige wrote: post #116

> that makes it easier and faster for hardware makers to deliver Android updates. They still don't get it. Google as the OS vendor should update all phones and NOT the hardware makers. Hardware manufacturers can still update their special features on the side after an OS update got deployed but I want that the OS and its core become updates directly and only from Google. Why is this so hard?

Devils advocate: why should google do that? That would be a pretty big outlay of money/time and they may not be getting paid at all by OEMs.

I agree it's probably the only way to actually fix this, I just don't think it will happen.

Re: Android Oreo

#139

Post by kevincox »

metalliqaz wrote: post #48
abol3z wrote: post #33

Finally Android will stop Facebook apps from sucking my RAM secretly!

I've found a fantastic solution that works on any phone! Uninstall facebook and facebook messenger. Then use Chrome and facebook's mobile site. Life changer, man.

I haven't had much problem with FB Messenger, and it's app is more useful then the mobile site.

However the main app is a total dog and the mobile site is quite complete. Would definitely remove it.

Re: Android Oreo

#140

Post by function_seven »

MBCook wrote: post #125
fenwick67 wrote: post #22

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

I remember that when Apple started announcing that they were new emoji's in the new iOS versions all of a sudden people updated WAY faster instead of waiting a few months. It really does seem to be something that drives adoption.

I'll admit it. The thing that got me to update iOS this last time were the iMessage effects (slam, confetti, invisible ink, etc.).

I rarely use those now, but I'm not immune to superficial hype. It's fun.

Post reply on HN