News for hackers. Stuff that matters.
Re:HP Chromebook 11 Review by rayiner on Tuesday October 15, 2013 @12:19PM (#6554202)
The dreadful battery life is interesting:

"Despite using relatively power efficient hardware and being paired with a 30Wh internal battery, the Chromebook 11 barely lasted 5.4 hours in our web browsing battery life test. Local video playback was even worse at 4.8 hours."

The "web browsing battery life test" in this article is the same one as in here: http://www.anandtech.com/show/7117/haswell-ult-investigation. Note how the iPad 4 gets 9.48 hours on both tests. On that test, the 11" MBA gets over 11 hours, despite having less than a 25% larger battery and using Core i5 processors. The 13" MBA gets over 14 hours, though it has an 80% larger battery (but has to drive a 30% larger screen).

This suggests that Samsung's Exynos 5 is extremely power-hungry or Chrome OS's power optimization is extremely bad.

As an aside, Apple/Intel's phenomenal battery life performance with the latest MBA signals to me the beginning of the end for ARM. If we're getting to the point where a current-generation Haswell laptop CPU is putting up light workload power draw comparable to a flagship A15 tablet chip, that's not a positive thing for ARM. Heck, even if you just compare the iPad 4 with the MBA 11", the writing seems to be on the wall. The iPad has a substantially bigger battery than the MBA, while driving a smaller (albeit more pixel-dense and power hungry) screen. And yet the MBA totally holds its own on the battery life test.

Re:HP Chromebook 11 Review by devx on Tuesday October 15, 2013 @12:28PM (#6554284)
Samsung's Chromebook had about the same battery life, if not a bit bigger, and achieved that with I think half the battery size. So whatever is going on now, is probably HP or Google's fault.

Also, I think you're confusing things. Are you referring to this?

http://anandtech.com/show/7085/the-2013-macbook-air-review-1...

That shows 11 hours in "light workload". Unfortunately, starting with this year, Apple stopped giving "real" numbers for its Macbook battery life, and started giving battery life for "minimum workloads" like the whole laptop industry has done for more than a decade. The "real" battery life is closer to that "medium workload" (Haswell gave about a 50 percent boost compared to last year's Macbooks).

With medium workload, it's 9 hours, with a 50Whr battery (according to you, I didn't check), so at 30Whr, that would normalize it at around 6.7 hours. Still good, but nowhere as impressive as you made it sound at first.

I'll grant you this. The decision to use a last-gen chip in this Chromebook wasn't a very smart one, and that's probably HP's fault. Mediocre companies like HP with mediocre employees and mediocre middle management tend to be very slow about adopting new technologies in their products, which is why you never see them come out with some cutting edge tech first.

Re:HP Chromebook 11 Review by blinkingled on Tuesday October 15, 2013 @12:38PM (#6554372)
The 13" Air has a 54Wh battery compared to the almost half capacity 30Wh battery of the ChromeBook. So that's almost half the battery life on almost half the battery capacity. Not exactly dreadful but could get better.

With Haswell Intel got the power draw at idle down to a very good level. So the major power sucker is still the screen. But given the Chromebook has a smaller screen and less powerful SoC the ChromeBook should in theory get little better battery life than it does. That one we can chalk up to the 3.4 Linux kernel that the ChromeBook is using and OS X / Safari generally always being ahead in power use department.

I think we'll see the battery life get better with the newer Haswell Chrome books when Google switches to a more recent Linux kernel.

Re:HP Chromebook 11 Review by TylerE on Tuesday October 15, 2013 @01:04PM (#6554594)
Interesting way to twist the numbers.

To be accurate:

The Chromebook gets 38.5% of the battery life with 55.5% of the battery capacity. That's quite a bit different than the 1:1 ratio you imply, more like 0.7:1.

Put yet another way, with the MBA13's battery, the Chromebook would last 9.7 hours. With the Chromebook's batter, the MBA would last 7.8 hours.

Re:HP Chromebook 11 Review by blinkingled on Tuesday October 15, 2013 @02:06PM (#6555137)
Twist? If I had implied 1:1 - why do you think I spent the next paragraph explaining the difference? Also 0.7:1 isn't exactly dreadful - so that point stands.
Re:HP Chromebook 11 Review by TylerE on Tuesday October 15, 2013 @02:23PM (#6555277)
"So that's almost half the battery life on almost half the battery capacity."

If that's not implying a 1:1 ratio I don't know what is.

Re:HP Chromebook 11 Review by blinkingled on Tuesday October 15, 2013 @02:36PM (#6555354)
Are the battery life tests the same between the Air and ChromeBook? The Air review from Anandtech tests the Air for Light, Medium and Heavy Workloads (whatever that means) in which it gets 11/8.9/5.53 hours respectively. The ChromeBook test on the other hand is labelled "Web Browsing Battery Life" which to me suggests that it isn't exactly the same as the one used with Air or for that matter which one of the Light/Medium/Heavy compares closely to it.
Re:HP Chromebook 11 Review by tedunangst on Tuesday October 15, 2013 @07:34PM (#6557063)
Did you not read rayiner's link? There's a big graph labelled "Tablet Web Browsing Battery Life" with the MBA in it.
Re:HP Chromebook 11 Review by blinkingled on Tuesday October 15, 2013 @07:51PM (#6557148)
Do you happen to know if "Tablet Web Browsing Battery Life" and "Web Browsing Battery Life (WiFi)" are one and the same thing though? Tablets don't load Flash. ChromeBook does by default. The tests may still be different in unknown ways.
Re:HP Chromebook 11 Review by kllrnohj on Tuesday October 15, 2013 @01:21PM (#6554727)
> This suggests that Samsung's Exynos 5 is extremely power-hungry or Chrome OS's power optimization is extremely bad.

I'm betting it's Chrome OS. The Nexus 10 also runs the Exynos 5, same exact chip, yet it gets 9+ hours of web browsing battery life and does it with a 2560x1600 screen.

Re:HP Chromebook 11 Review by taopao on Tuesday October 15, 2013 @02:06PM (#6555134)
Nexus 10: 9000 mAh HP Chromebook 11: 2300 mAh ^^ I'm betting it's this.
Re:HP Chromebook 11 Review by rayiner on Tuesday October 15, 2013 @02:14PM (#6555213)
You can't compare battery ratings in milliamp hours unless you know that the load voltage is the same for both.
Re:HP Chromebook 11 Review by bronson on Tuesday October 15, 2013 @02:56PM (#6555501)
Of course you can. If you read some datasheets you'll see that's how batteries are rated.
Re:HP Chromebook 11 Review by rayiner on Tuesday October 15, 2013 @03:10PM (#6555621)
Batteries are rated in milliamp hours at a given voltage. You can't directly compare ratings in milliamp hours without accounting for the voltage. Watt-hour ratings, in contrast, bake assumptions about the average battery voltage into the rating, and thus can be compared directly even between batteries having different voltages.

In this case, it's common sense. There is no way a Nexus 10 has a battery four times as large as an 11.6" notebook.

Re:HP Chromebook 11 Review by kllrnohj on Tuesday October 15, 2013 @06:15PM (#6556742)
Nexus 10 has a 22.75Wh battery, the HP Chromebook's is 30Wh.

Chromebook has a bigger battery than the N10, not a smaller one. Probably also a factor in why the Chromebook tips the scales at 2.3lbs vs. the N10's 1.3lbs.

Re:HP Chromebook 11 Review by Recoil42 on Tuesday October 15, 2013 @02:05PM (#6555131)
How big is the battery on the Nexus 10?
Re:HP Chromebook 11 Review by Touche on Tuesday October 15, 2013 @12:54PM (#6554519)
I bet ChromeOS is just not optimized for ARM. The original CR48 got incredible battery life (more than 10 hours), as did the Series 5 (the first for-sale Chromebook). Both of those used Atom processors. Since the majority of Chrome use is on the desktop with x86 computers, my guess is that this is the reason.
Re:HP Chromebook 11 Review by fromanator on Tuesday October 15, 2013 @12:30PM (#6554298)
The power drain could also be from poorly optimized supporting chips/shipsets like microcontrolers, WiFi Cards, and other periphery devices.