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

641–650 of 658 posts

Re: Android Oreo

#641

Post by Eridrus »

DCKing wrote: post #597
irq-1 wrote: post #587

Earlier quoted context omitted.

Couldn't Google use an immutable HAL as a way to make updates themselves? Let users drop manufacturer customizations and get stock android on an older phone.

They might. In an edit above, I remarked that for such a system to exist indeed Project Treble is a necessity. But taking centralized control over the way Android updates will be a very ballsy political move by Google to make. Some smaller vendors might appreciate that these responsibilities are taken away from them. Sony, HMD/Nokia and Lenovo/Motorola are basically only adding some apps, themes and tweaks to AOSP at…

> Android's bad reputation in regards to updates doesn't really hit anyone that hard.

I think this is an issue for Google when they want to introduce new platform features for developers, e.g. Project Tango. If updates take years to get to users, it handicaps Google's ability to be innovative.

Re: Android Oreo

#642

Post by srcmap »

mariusmg wrote: post #539
DCKing wrote: post #536

Earlier quoted context omitted.

I'm very skeptical of the level of optimism that is thrown towards Project Treble. In the end it's just a way to make OEM's lives easier while developing updates. It will still require them to actually make updates for devices. Despite Project Treble they will still not have an economic incentive to update devices. And that is the core issue here, really. My expectation is that Project Treble will help speeding up An…

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

There might be another way.

I heard from "Security Now" podcast that there is a new law that require all government purchased IOT devices must be update-able to fix security issue.

Expand the law a bit:

Make all internet connected device makers (Include phone maker) liable for any loss of private consumer info, hack for 10 years from any internet connected devices release.

Anyone can file lawsuit against them easily or in class actions against the vendor if they don't provide security fixed/upgrade within 4-6 months of from being notify of the vulnerability.

Establish an ISO security standard for IOT (and all Phone): such as

1) Standardize SW/FW update requirement, method and audit. ssl, security hash, CA, etc.

2) Requires system to monitor and log all program/critical system components creation/execution/all internet connection and download for auditing by owner of device.

3) Require system vendors to have source code / tools chain / build system in place to rebuild and fix security issues.

Once the vendors are liable for hack. They will need Insurance. The Insurance Company can follow the ISO security standard to audit and estimate the potential cost.

Re: Android Oreo

#643

Post by H1Supreme »

> "Native C/C++ API for high-performance audio"

This is good to hear. But, this makes me wonder about Android's ability to prevent people from pirating apps. Due to the nature of Android, I've never wrote an app that wasn't free.

On iOS, there are a number of audio apps that do quite well. I'd be hard pressed to port an app to Android, if taking the apk was as easy as it's always been.

Re: Android Oreo

#644

Post by ksk »

josteink wrote: post #626
ksk wrote: post #610

Earlier quoted context omitted.

Resources are finite. I don't know what your point is? That they should simply give up and do nothing? >That carriers needs to do testing is a lie perpetuated to allow for customer-hostile business-practices. Stop repeating it. Other than your opinion, what evidence do you have that this is a lie?

All of Europe? Where GSM was invented? This kind of bullshit only happens in the US where carriers are free to bullshit as they like due to absolutely lacking regulation. In Europe we know better, we do better. I'd rather say the burden of evidence is on the other side of the argument: prove to me why do you need to do testing as a carrier.

>I'd rather say the burden of evidence is on the other side of the argument: prove to me why do you need to do testing as a carrier.

And yet you make absurd claims without evidence yourself. So because you're confused as to the reason, that makes them a liar.. Nice.

Re: Android Oreo

#645

Post by tomkarlo »

thaumasiotes wrote: post #611
tomkarlo wrote: post #603

Earlier quoted context omitted.

This doesn't make any sense. It assumes there's no competition between manufacturers, and that users don't switch. If older phones were actually "better", manufacturers would just make those and steal customers from anyone making the newer devices. The phones of today aren't "built with shorter lifespans in mind", but they are built with more tightly packed components, more energy-dense batteries (to support their po…

Did you mean to respond to me? It seems like we agree, but this is basically how I would have responded to throwaway613834.

You're right. mis-replied in the thread.

Re: Android Oreo

#646

Post by 2bitencryption »

suckerburg wrote: post #636
2bitencryption wrote: post #475

Earlier quoted context omitted.

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?

you could read some of DFW's short stories to understand his style a bit.

other than that, don't be too afraid -- Infinite Jest is intentionally complicated and convoluted, being a bit confused is part of the experience. even if you aren't quite sure what's going on in every chapter, the writing is gorgeous and funny even on a sentence-by-sentence basis.

You'll meet one character, then move on to another character, then return to the first character four hundred pages later. You'll read footnotes on footnotes that refer to other footnotes. There will be plays on words that appear on page 20 and then are reprised on page 600. Extended metaphors are introduced and return without warning.

Just start reading it, and if it gets too hard, put it down a bit. It's still a book for entertainment (the whole story is _about_ entertainment), so don't treat it too much like it's homework. just have fun with it :)

Re: Android Oreo

#647

Post by fulafel »

pjmlp wrote: post #630
dcow wrote: post #596

Earlier quoted context omitted.

Point being the delta between what a native app and what a browser app can do has all but disappeared. BT and Graphics are the last few notable things and both will be supported by browsers soon (webgl already is and webbt is incoming). I'm not saying go use JS.. I very much do not enjoy it. Im asking why we need to build native when there's increasingly less to justify the overhead.

WebGL is a poor cousin of OpenGL 4.6. Even comparing WebGL 2.0 to OpenGL ES 3.0, which it is based on, there are nice features like geometry shaders missing.

Nitpick: Geometry shaders came in GLES 3.2 (there was also a geometry shader extension for GLES 3.1).

In WebGL 2 you can still do geometry processing, and store results in buffers for subsequent draw calls, using transform feedback.

Re: Android Oreo

#648

Post by pjmlp »

fulafel wrote: post #647
pjmlp wrote: post #630

Earlier quoted context omitted.

WebGL is a poor cousin of OpenGL 4.6. Even comparing WebGL 2.0 to OpenGL ES 3.0, which it is based on, there are nice features like geometry shaders missing.

Nitpick: Geometry shaders came in GLES 3.2 (there was also a geometry shader extension for GLES 3.1). In WebGL 2 you can still do geometry processing, and store results in buffers for subsequent draw calls, using transform feedback.

You are right, I mixed it up.

Like that idea for WebGL 2.0, will have a look into it.

Re: Android Oreo

#649

Post by mlnj »

thanksgiving wrote: post #490
mlnj wrote: post #408

Earlier quoted context omitted.

Devices with a stylus (like the Galaxy Note series) can use it by hovering on the element.

Speaking of the note series, I wonder if the note 8 will ship with Oreo and if so how well it keeps the treble stuff.

:(

Re: Android Oreo

#650

Post by freech »

eloisant wrote: post #499
pjmlp wrote: 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.

Why would they do that? Isn't Play Store the way Google monetizes android?
Post reply on HN