The Apple iPhone 6s and iPhone 6s Plus Review • Hacker News Board

Re: The Apple iPhone 6s and iPhone 6s Plus Review

#171

Post by willtim » Fri, Nov 06, 2015, 7:07 PM UTC

fernandotakai wrote: post #101

tw04 wrote: post #9

Earlier quoted context omitted.

I agree, the battery life is shockingly poor. I blame touchwiz as much as anything else. I would take a slightly thicker phone for a battery that consistently lasts all day.

i have my s6 rooted and with a custom rom. battery is not as bad, but not amazing. if i'm on a place with good mobile signal and on wifi, i can get a day[0] of battery life with ~2h of SOT (with my pebble connected and syncing all day long). but at the same time it's kind of worth it, because it's easily the best camera on a cellphone i've ever used. [0] http://i.imgur.com/J7Xe2FV.jpg

I see Google Services at the top consuming 22% of your battery. It must be Lollipop. Under KitKat, the screen is almost always at the top of the list.

Re: The Apple iPhone 6s and iPhone 6s Plus Review

#172

Post by willtim » Fri, Nov 06, 2015, 7:11 PM UTC

MichaelGG wrote: post #98

willtim wrote: post #37

Earlier quoted context omitted.

Samsung TouchWiz with KitKat 4.4.4 had awesome performance and battery life on my Note4, then they destroyed it with a Lollipop update (after constant update nags) and forced me to downgrade probably voiding my warranty in the process, anyone sane would have returned the phone. I don't know if Samsung or Google is to blame for the serious battery and performance regressions, but I do blame Samsung for pushing it out…

How about the silly OEMs that ship tiny batteries? The Huawei Mate 2 lasts 30-40 hours easily. The Blu Energy Studio lasts around 3 days.

Well we shouldn't need huge batteries if Android was fixed. Have you seen the batteries Apple put inside iPhones? iOS is great for their hardware margins.

Re: The Apple iPhone 6s and iPhone 6s Plus Review

#173

Post by chillacy » Mon, Nov 09, 2015, 9:08 AM UTC

applecore wrote: post #133

chillacy wrote: post #125

Earlier quoted context omitted.

Think about it from the company/engineer's point of view: would you want to maintain the old version of the code (adding security fixes and the like) for years after it's current, for probably less than 1000 people per version? Remember that the old versions of code probably build with old versions of the compiler, old trains, etc. And you can't not maintain this code, since there will be bugs found, jailbreaks, etc.…

It's a near-universal practice for several versions of important system software (like operating systems and databases) to be maintained and supported simultaneously. It's unusual for updates to stop entirely as soon as the next major version is released.

I see this as a necessity mainly for server software which you don't want to change too often. Ubuntu does a great job at this with their LTS releases.

But in the consumer mobile OS space, there are really only a few big players. It looks like google does patch old versions of the OS, albeit up to a limit: http://blogs.wsj.com/digits/2015/01/12/google-not-fixing-som...

But on the other hand with the way the android adoption curve looks, that's still a lot of people. I just checked wikipedia right now, something like 35% of users are running a version which google stopped patching. So to have the same coverage of security updates, google has to support more OS versions. And even then, they're leaving a lot of people in the dust.

I'm sure google would like people to upgrade too, less versions for them to maintain, but they've got the whole carrier situation to deal with in that ecosystem.