The Stable channel has been updated to 53.0.2785.103 (Platform version: 8530.81.0) for all Chrome OS devices except Google Chromebook Pixel (2015), Acer Chromebook R11, ASUS Chromebook Flip C100PA, HP Chromebox CB1, and Acer C7 Chromebook. 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:

Material design overview mode

SAML SSO for Chrome Apps

Highlights - Accessibility feature

New app API to enable watchdog behavior in kiosk apps

Security Fixes:

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed

If you find new issues, please let us know by visiting ourforum orfiling a bug. Interested in switching channels?Find out how. You can submit feedback using ‘Report an issue...’ in the Chrome menu (3 vertical dots in the upper right corner of the browser).

So far so good. Thank you for the update. But honestly, I was looking forward to receiving Android app support for my Acer Chromebook 14 with release 53. When and how will this important feature be deployed?

I am pretty frustrated to notice that Android apps are not "working" with my Acer Chromebook C720. The Acer C740 is on the famous list, and it is the exact same device as my laptop. What is the logic in here? To prove you i works, I installed two apps on my Chromebook and it works perfectly! Plus, I have a touchscreen on my laptop. AGAIN, what is the logic?

I deleted my comment as clearly no one is reading these concerns. Perhaps the powers that be have not picked up on the level of frustration waiting all this time for the promised upgrade allowing Android Apps to actually happen instead of just a lot of fanfare. Not everyone is comfortable with the Dev channel or Beta, and I can't be the only one loathe to switch to either one knowing if you want to go back to Stable you lose everything. If you are waiting for some momentous occasion to put the update in place, consider we have already been waiting for months. Any day now would be just fine, it doesn't have to be Christmas. (seriously, don't wait until Christmas or you'll have a riot on your hands_

Android apps are being delayed until they can finish working out all the kinks. The Flip, R11, and Pixel should still be the first to get Android apps but until they do another update (most likely still Chrome OS 53 so you won't have to wait 6 weeks for it to be released in 54), the apps will not be available. I'd give it a week or two before they make it available. With something as big as this, they want to make sure that its as close to perfect as it can be before they release it. If you really want to download the apps, you can always switch over to the beta channel until it gets released to the stable channel.

I'm with Aunt Gina. I've got an Asus Flip (which I love), and I've been waiting eagerly for 53 to hit the stable channel since June. Been checking the release blog and Googling for "android apps on chromebook" every day. Lots of articles about new Chromebooks, running Windows programs on Chromebooks, and how Android on Chromebooks is going to save the world, but no actual news.

I've resisted the temptation to switch to the dev or beta channels because I don't want to risk having an experimental version of the OS corrupting my data, and I don't want to have to re-enter all the WiFi access passwords for the many hotspots I use. I keep telling myself, just a few more weeks, just wait a few more days...

And now I find that my poor little inner Chromebook enthusiast has been tricked again. At this point she's screaming at the top of her lungs, "I want my Android apps!"

I, of course, being a mature, sensible adult, am sitting quietly, not screaming at all, just carefully, rationally typing this post. No rioting here at all. Yet.

I promise not to join my inner child in screaming for at least another day. Maybe two...

ok cody parker i get that and it takes time for these things lots google has to do to convert android to chrome.my opinion is it was said months back the 3 yes 3 chromebooks to get android. ok later june nothing then sometime in july it was avalible on dev. channel. then while later on bata. ok now the headline for this page says its on stable channel for other chromebooks now aint this a tale i mean a little white tale if the 3 that was to get first then those 3 should have been the ones listed for stable channel i do know i have went back and forward to dev. channel now back and forward on bata last week i went from bata to stable and boy that was a mistake it continued to close out come back on close out with this chrome didnt shut down properly i contacted acer and woman said has virus send in for repair at my cost tho its under warranty after a long time i got it back to bata channel and it works fine mabey it was do to getting android or version 53 on stable not sure but google needs to tell us a time or close to time 53 on stable instead of this bata dev. channel and this and that gee

Everybody just relax. Google said Android apps would be coming "later in the year and early 2017".

The first models for testing were the Chromebook Flip, followed by the R11 and the Pixel shortly after, along with everything else afterwards.

When they finish testing in the beta channel, they'll roll it out to stable. It's a 6-week cycle in between channel releases. Unless they've started testing in the dev channel for any model, it'll be at least 12 weeks before your model is added. The initial 3 models have a few last minute bugs that have to be ironed out before the stable channel gets the update. It'll be a few days or maybe a week or two - hopefully. If it can't be rolled out in a timely measure, the additions will be rolled back and those models will get Chrome 53 without Google Play just like the other models, and it'll go back into testing phases for another 6-week wait to get it right.

The models listed in the compatibility list are coming, but there are no definite dates on anything because they want this to be stable and reliable, not half-arsed. The stuff that goes into bringing the whole Android environment to Chrome OS is new and a big change and requires some new updates to the core parts of Chrome OS to support it, and each Chrome device needs specialized code to support it, which is why it'll take time to update each model, and why older models aren't getting it.

Sure, get excited, but be patient too. Your Chrome device still works as it always has - simple, stable, and secure. Google doesn't want to change that just because this big new add-on is being put into the OS.

OK lol baby baby I didn't intend to have anyone thinking I was mad Ect.just asking what I couldn't find online one thing says this another that.again like I said it takes time but my frown is it states on this page that Android version 53 is on stable channel but not on the first 3 yet OK fine no prob. Just makes no sense is why but no big deal thanks to all the feed back.

Can no longer block, copy and paste from a web site I use frequently. NO problem at all when I used on Microsoft. Trying to figure if this google update is also the reason why when I open a "NEW" word document, the formatting is all messed up.

I'll have to weigh in on the side of non-exclusion of 3 machines that were the testbed for development and beta-testing. It just seems non-sensical to me to blow a trumpet announcing, as Google/Alphabet did in the Spring that Android apps on Chrome OS was a real thing; and have more than one presentation at Google I/O this summer on how close they were to putting it out...everybody "knows" that Google only takes 6 weeks from one release to the next. It sure seemed to me that those who had the 3 machines "readiest" for Android apps should get that functionality as "scheduled".

They built up expectation in everyone, and now they are reaping the downside of high expectations: people who were very excited and are growing in disappointment and frustration.

I really think that the folks working on this project should officially announce on the blog that the project has hit unforeseen roadblocks, and put out a schedule and deadline that is realistic given what they know.

Everyone understands that things change--but when you create expectations, you have to manage the ire that missing those shipping dates causes. Better to ship "early" on a longer deadline than to be "late" on an unreasonably early one. (imho)