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

411–420 of 658 posts

Re: Android Oreo

#411

Post by askafriend »

function_seven wrote: post #140
MBCook wrote: post #125

Earlier quoted context omitted.

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.

I love the invisible ink one the most. I use it pretty often actually. Yes it's dumb, but I'll be damned if I can't have some dumb fun.

Re: Android Oreo

#412

Post by yincrash »

saghm wrote: post #70
jampa wrote: post #36

I know this is a non-issue for many, but those emojis look really dated. Every update they get harder and harder to read in small form. One of the things I observe, mainly on Instagram Stories is only people with iOS post with emojis attached, I never see Android ones. Too bad there is no way to install custom emojis in any system (without rooting/registry tweaking), like we do with fonts.

Personally, I find it kind of ridiculous that new emojis are considered flagship features of mobile OS updates. I'd think that it would be possible to decouple emoji updates from kernel/security updates, so I imagine that Android/iOS tie them to the OS updates solely as a way to motivate non-technical users to update.

Android actually recently released a support library that apps can implement for this.

https://developer.android.com/guide/topics/ui/look-and-feel/...

Re: Android Oreo

#413

Post by Skunkleton »

khc wrote: post #299
mjevans wrote: post #148

Earlier quoted context omitted.

Reflect for a moment; what was the 'new' price of the Nexus 4 vs the 'new' price of the iPhone at the time? A Nexus 4 was a 2012 phone with 2GB ram, and 8GB storage (entry model) https://en.wikipedia.org/wiki/Nexus_4 An iPhone 5 is the comparable year device. https://en.wikipedia.org/wiki/IPhone_5 It had entry specs of only 1GB of RAM, but 16GB of storage. The apps would also be native binaries instead of 'java' apps…

not to diminish the rest of your argument, but my understanding is that java apps should be smaller than native apps (not significantly, since a huge part of apps' storage requirement is for assets, not code)

My experience around this time was that Android apps where much much smaller than similar iOS apps. Somewhere on the order of a 10x difference for apps without a lot of assets.

Re: Android Oreo

#414

Post by bootlooped »

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

Some of them did not match perfectly with their counterparts in other Emoji sets. I wouldn't call that "completely incompatible" though, and it doesn't imply that one or the other is wrong.

If the purpose of this was to bring them in line with other emoji sets, they could have just redone the few that show somewhat different expressions.

Re: Android Oreo

#415

Post by scott_karana »

cakedoggie wrote: post #325
saghm wrote: post #70

Earlier quoted context omitted.

Personally, I find it kind of ridiculous that new emojis are considered flagship features of mobile OS updates. I'd think that it would be possible to decouple emoji updates from kernel/security updates, so I imagine that Android/iOS tie them to the OS updates solely as a way to motivate non-technical users to update.

Mobile OS's aren't just for grumpy old people.

GP's point wasn't that emojis shouldn't be updated, but that it shouldn't require MAJOR/BREAKING VERSION updates (kernel, libraries, the works) to simply update a sprite font.

Re: Android Oreo

#417

Post by bootlooped »

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.

I plan to. The blob set was a real design triumph. I loved the flat simple style, and they were in line with Material Design guidelines. The new ones are a joke.

Re: Android Oreo

#418

Post by fulafel »

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.

How in practice would you go about putting AOSP on a device without the vendor cooperating? Is there some kind of secure boot system that always accepts AOSP images?

Re: Android Oreo

#419

Post by kalleboo »

ClassyJacket wrote: post #326
ksk wrote: post #93

Earlier quoted context omitted.

Probably because they have to test the ROMs on their network in different regions, with different frequency bands, with roaming, etc. That work is tedious given all of the phones they support.

The iPhone doesn't suffer from this problem. It should be up to the phone manufacturer (HTC, Samsung, etc.) to test their product. The carrier can still, of course, test the new firmware all they like - they just shouldn't be able to interfere with its release.

TBF, Apple did release one update that caused issues with the radio on the Verizon network[0]. Carrier testing should have caught that.

[0] https://www.theverge.com/2016/10/17/13306776/apple-iphone-7-...

Re: Android Oreo

#420

Post by fulafel »

sumeno wrote: post #188
on_and_off wrote: post #166

Earlier quoted context omitted.

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

That's a pretty unreasonable desire. Technology changes so much in 10 years that it wouldn't be feasible to support a generation of phones for that long. 10 years ago was the original iPhone. How much of a money sink would it have been for Apple to support the original iPhone until now?

There's no rocket science in maintenance support (eg security patches) for 10 years. That's the only thing that is necessary to keep the device usable.
Post reply on HN