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

251–260 of 658 posts

Re: Android Oreo

#251

Post by drampelt »

rdsubhas wrote: post #141

Not saying that everything else is bad, but one thing that strikes me is how much they have run out of interesting things now that they had to use fillers[1] like: Tooltips Support for tooltips (small popup windows with descriptive text) for views and menu items. Normally, this would be relegated to a git changelog in the support library. But this is on the global marketing landing page. I like to imagine a fictional…

I think a lot of major changes are in Google's apps, not Android itself. For example a big update to the Photos app would be part of a major OS update in iOS but just another regular app update on Android.

Re: Android Oreo

#252

Post by ngcazz »

BinaryIdiot wrote: post #2

This seemed like the best choice in name and yet I wonder if they'll draw the same ire from the community as they did when choosing Kit Kat. Honestly I like it; it was better than basically all the other alternatives.

No, it wasn't :) [1]

[1] https://en.wikipedia.org/wiki/Ovos_Moles_de_Aveiro

Re: Android Oreo

#253

Post by tapoxi »

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.

My Moto X Pure (2015) has no carrier relationship and a very lightweight Android skin. It's still running Android 6.0.

I can't imagine them putting in development resources when they could just sell you a new phone.

Re: Android Oreo

#254

Post by mixedCase »

renox wrote: post #245
mixedCase wrote: post #146

Android has been improving so much in the performance department I think the phone that will replace my aging S3 will be... another S3 if I can find one. Seriously. Software has improved so much but the hardware nowadays is trash for my needs at least.

Uh? I replaced my S3 by a S7 and the hardware changes are huge: better CPU obviously but also much better screen (the S3 was unreadable during sunny days..)

Can you replace the battery with an extended one?

That's a deal-breaker for me, and battery cases are not a good replacement since I can't rely on the phone's own battery indicator, have to manually turn on/off and looking at ZeroLemon's case for the S7, it seems to require a headphone extender.

As for the S3's screen I have no complaints. It's readable in the sun with max brightness, I keep it at minimum the rest of the time.

Finally, the S7's native screen resolution is 1440p, meaning it will munch on battery much faster for no perceptible gain (at the distance I hold my phone). And manually lowering the resolution will render a blurrier image than native 720p so that's out.

Re: Android Oreo

#255

Post by dragonwriter »

euyyn wrote: post #189
dragonwriter wrote: post #58

Earlier quoted context omitted.

> "new emoji" is an OS-level feature now. System fonts have been an OS-level feature since the advent of OS with bundled GUI. Support of a larger part of the Unicode space in system fonts has been an OS-level feature since Unicode. New emoji has been a visible aspect of that, especially on mobile, for quite some time.

Why is it tied to the OS version, though? I would (naively) think it's a matter of just sending the new font as an OTA update?

Given that it's apparently a fairly compelling feature for many consumer end users, maybe it's a way of convincing OEMs and carriers and to actually deliver updates.

Re: Android Oreo

#256

Post by Zarel »

tombrossman wrote: post #120
pwg wrote: post #19

Earlier quoted context omitted.

Browsing with NoScript in default deny JS mode, I just had to turn of style sheets to be able to read the whole article, unimpeded by any scroll hijacking.

NoScript definitely improves most sites, but scroll can be hijacked with CSS alone: https://developer.mozilla.org/en-US/docs/Web/CSS/scroll-beha... Firefox users can set "layout.css.scroll-behavior.enabled = false" in about:config and never have to worry about this nonsense again.

Did you read the article you link to? It says that it only applies to CSSOM (JavaScript) and navigation (presumably clicking links). Not scrolling by the user.

Re: Android Oreo

#258

Post by vacri »

rdsubhas wrote: post #141

Not saying that everything else is bad, but one thing that strikes me is how much they have run out of interesting things now that they had to use fillers[1] like: Tooltips Support for tooltips (small popup windows with descriptive text) for views and menu items. Normally, this would be relegated to a git changelog in the support library. But this is on the global marketing landing page. I like to imagine a fictional…

You had to scroll past quite a few animated announcements and read past several lines of other updates in order to find this 'also-ran' item in the footnote.

Re: Android Oreo

#259

Post by dcow »

avar wrote: post #105
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…

What part of that page indicates that you can't use the platform like that? They just say "more control over how apps run in the background". Presumably you can still give your users a good reason for why you need to run uninterrupted in the background and they can approve it similarly to how they now approve other permissions.

The way this is implemented is that the system will kill any background services your app has after a grace period, just like iOS. In order to have a background service that "good reason" equates to a persistent notification in the tray and icon in the status bar--which nobody agrees is a good product experience.

Re: Android Oreo

#260

Post by gambiting »

Has google forgotten how to do great marketing?

You open the page. Scroll down. What should be the first thing you see? Obviously it should be the greatest, the best feature of the new OS. What is it instead? "Quick boot up time". Really? That's the best thing in Android Oreo? That when I reboot my phone once every 4 months, it's going to start quicker? Surely they could have picked literally anything else as the first thing to mention?

Post reply on HN