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

121–130 of 658 posts

Re: Android Oreo

#121

Post by ocdtrekkie »

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?

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.

Re: Android Oreo

#122

Post by dcomp »

pjmlp wrote: post #72
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 "…

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.

Re: Android Oreo

#123

Post by ringaroundthetx »

rukenshia wrote: post #68
fenwick67 wrote: post #22

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

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

Re: Android Oreo

#124

Post by kevincox »

pjmlp wrote: post #72
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 "…

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.

Re: Android Oreo

#125

Post by MBCook »

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.

Re: Android Oreo

#126

Post by MBCook »

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

I've only ever seen them inside Google hangouts, but I will say that I thought they were kind of cute.

I don't know where they could keep them since I agree it would be a good idea to have something very similar to other oasis.

Re: Android Oreo

#128

Post by ocdtrekkie »

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.

Google has rebranded viruses as "PHAs" or "potentially-harmful applications". They don't want anyone to know that Android devices get viruses. ;)

Re: Android Oreo

#129

Post by kevincox »

sarnowski wrote: post #98

Wondering if the following feature is enabled by default: "Wi-Fi Assistant Auto-connects you to high quality open WiFi and secures your connection with a VPN back to Google." I really do not want to tunnel my whole traffic through Google's servers.

I don't know if it is on by default but if enabled it will connect to "High Quality" open networks. If it does this it connects the VPN.

So the VPN is "required" by this feature but you can turn it off globally, or manually connect to networks where you don't want to use the VPN.

Re: Android Oreo

#130

Post by thinbeige »

ocdtrekkie wrote: post #121
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?

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 the broken camera, so you create a totally different urgency.

But Android is an odd OS, we will never see a proper update policy from them.

Post reply on HN