Tuesday, May 20, 2014

Stable Channel Update for Chrome OS

Update (Fri May 30th, 2014):
  • 35.0.1916.116 / 5712.61.1 has been updated to ASUS Chromebox and Samsung Series 3 Chromebox.
  • 35.0.1916.116 / 5712.61.2 has been updated to Samsung Series 5 550 Chromebook, HP Chromebook 14, Acer C720, HP Chromebook 11, Toshiba CB30-A. This update contains fix for touch pad issue (378427, 377165)

The Stable channel has been updated to 35.0.1916.116 (Platform version: 5712.61.0) for all Chrome OS devices except ASUS Chromebox and Samsung Series 3 Chromebox. This build contains a number of bug fixes, security updates and feature enhancements. Systems will be receiving updates over the next several days.

Some highlights of these changes are:
  • The Chrome OS Launcher now supports folders - you can sort all of your apps exactly the way you want.
  • We updated the window controls based on the feedback of our users - the minimize button is back and the left/right tiling of windows can be done via long-press on the maximize button.
  • Hotwording (or "Ok Google") is now available on New Tab Page and Google.com for English (US) users.
  • We’ve implemented captive portal detection during a signed-in session, which will help you get online in cafes, hotels, airports, and other locations which provide internet connectivity via a captive portal.
If you find new issues, please let us know by visiting our forum or filing a bug. Interested in switching channels? Find out how. You can submit feedback using ‘Report an issue...’ in the Chrome menu (3 horizontal bars in the upper right corner of the browser).

Dharani Govindan
Google Chrome

22 comments:

Zak said...

Is there any reason the chromeboxes aren't included?

kyle winder said...

ya, what's the deal? i just got my chromebox tonight, is it already outdated, and not receiving updates? i was looking forward to the folder organization for apps.

let me know, thanks!

Jonathan Chartrand said...

I would also rely like an answer as to why the Asus Chromebox is not receiving the update. Will it receive the update at a future time?

David Andrade said...

It may be that the Chromebox and Samsung 3 Chromebook just haven't gotten it yet, not that they won't ever get it. Neither one is end of life yet, so they should get the update eventually.
http://www.google.com/intl/en/chrome/devices/eol.html

Joel Criger said...

The Asus Chromebox came out 2 months ago and has the same chipset and processor as all the new Haswell Chromebooks. Unbelievable they can't get the update to it at the same time....

kyle winder said...

Engadget says this: "Unfortunately, not all Chrome OS devices will get this -- namely, the ASUS Chromebox and Samsung Series 3 Chromebox. Google didn't say whether the update will ever come to the omitted Chromeboxes, but we'll let you know if anything changes."
What's the answer Google? i literally just got the box last night...Now i'm thinking i should return it.

Weaky6 said...

Whiners! Chill out. Just because your chromebook won't have 3 features someone else's does doesn't mean it sucks for goodness sakes. You know what, return that thing please. Then we don't have to hear your whiny self drivel on forums. ;-)

Joel Criger said...

What a short-sited thought. If the updates stop now for the Asus Chromebox then it will miss out on ALL future updates...next time try to add something to the discussion instead of making ignorant remarks.

iron2000 said...

Working experimental DirectWrite has arrived!

Tried it and it still has quite a lot of problems compared to the rendering of IE11 and Firefox. (Thus experimental :P)

Trever said...

The current update described here changes portions of the firmware and/or early boot. I saw this when my peppy updated last night. Presumably, that is for captive portal compatibility changes as described.

A chromebox is always on a network- i.e. doesn't need the captive portal changes. That probably means: it will get the changes soon enough, but it's not as much of a priority as it is for the Chromebooks, and there are presumably related reasons for the delay in updating the Chromeboxes (i.e. that Google hasn't just pushed the same updates to the Chromeboxes).

The notion that Chromeboxes are no longer supported or that you need to return your recently purchased Chromebox because it's not updating is just silly. Chromeboxes are officially supported for several more years. Patience. Worst case they will get updated in 6 weeks, but probably long before that.

Stephane Tremblay said...

I have two devices with Chrome OS: Samsung Serie 3 and a Asus Chromebox.
I will be very upset if I will not receive an update... I believe in ChromeOS but it could change.

Stephane Tremblay said...

It's strange, I just validate and I received the update on my Samsung Series 3 includes new features.

Good new !

Brian Ward said...

We use Samsung Series 3 Chromeboxes at work and none of them received the ChromeOS version 34 or 35 updates either. This is the second major update to ChromeOS that the Samsung Chromebox has not received. Also it has not received any of the security patches recently provide including the ones for flash. From my way of thinking, it looks like Chromeboxes are not being supported - can someone from Google comment of this?

upi said...

My Samsung Series 3 Chromebook (ARM chipset) got the update (Chromebook= daisy).
The Samsung Series 3 Chromebox (stumpy) has another chipset (x86) and didn't get it now!
The ASUS Chromebox (panther) has a celeron chip !
Do you got the difference?

brunes said...

Blah.... if this feature worked just constantly in the background it would be great, allowing you to use "OK Google" from your whole desktop would be awesome. But having it only work when you manually open a tab and go to Google.com makes it basically useless, since I (like most Chrome users) do that essentially never, we use the Omnibox, because that is what you guys have trained us to do!

kyle winder said...

patience is different than faith. you're asking us to have faith...not be patience. i want to know if it will happen or not, then i can wait. ANYWAY...i have another question: If i enable these features from chrome://flags, is it the same as the update or is it not the "final" stable version?

Trever said...

Google's official update policy is in writing:

https://www.google.com/intl/en/chrome/devices/eol.html

Trever said...
This comment has been removed by the author.
Trever said...

I should have added:

Devices are supported for 5 years, MINIMUM.

Since it's just Linux, I wouldn't be surprised if many devices see support beyond that. I strongly suspect firmware updates are likely to be the primary maintenance burden for Google. If firmwares don't need updates, your device (I suspect) will get support beyond 5 years.

I have three chromeboxes myself. The policy shows that Chromeboxes are supported until 2018 & 2019 depending on which Chromebox it is.

Raymond Coolidge III said...

Guys, not sure if you're aware of this but just because some devices aren't included in every releases doesn't mean that they won't get the update eventually. Obviously they will. There have been times where the Pixel hasn't gotten the latest release for almost two weeks but eventually it did. So just be patient.

David Paul said...
This comment has been removed by the author.
David Paul said...

My Chrombook 3 just updated this morning....