Chrome OS Dev: File manager displays media files from Android

Last year, Google started integrating the Play Store into Chrome OS, enabling Android apps to run on more and more devices. After the android apps are running quite a bit, the integration continues in the dev version of Chrome OS, the file manager can now also display the media files stored in the virtual Android.

Since the middle of 2016 the first Chromebooks have access to the Play Store and all devices presented this year will also be able to access the Play Store and run Android apps natively. However, with the download and running of these apps, now the next steps on the agenda is to bring together the file managers.

Chrome os dev android files

Originally, Chromebooks were conceived as pure Cloud devices and therefore have only a very minimal file management with very few functions since the beginning. In the normal case, all downloaded and saved data are stored in the ‘downloads folder’. This has worked very well so far and was quite sufficient for the needs of Chrome OS users, but with the arrival of Android it looks quite different.

In the current developer version of Chrome OS, the file manager also lists media files from Android and are displayed as virtual folders. There are the new entries “Images”, “Videos” and “Audio” which can also contain subfolders. All the apps stored by Android apps are in the same way as you are accustomed to by the various gallery apps of the operating system. Because the files are not officially available for Chrome OS, they are currently read-only and cannot be deleted or edited.

It is the developer version of Chrome OS, but still this implementation is not quite as successful. It does not really matter that these files are objects from Android. Images, videos and audio files from the actual Chrome OS are not listed there. Otherwise, the Android apps cannot easily access the files of Chrome OS, which further confuses the two worlds.

The file manager thus contains stored files for Chrome OS, the files from the virtual Android and also a link and listing of all folders and files from the Google Drive. This is handy, but it must be better separated visually so as not to confuse the user completely. Since the first new devices with Chrome OS and Android are already delivered, one should hurry with it.


  1. Google we need you to create a storage subsystem that is available via the containers. Allow us to add a second drive that we can use as we want with the containers. Do NOT allow containers to touch the ChromeOS system drive.

    Very similar to the persistence solution with the cloud and containers. Basically a backend service for the containers.

    When you then give me access to the containers I can basically run Crouton in a container without developer mode and with persistence across reboots but while staying completely safe.

    Then, please, please, allow me to download and install on my Windows boxes.

    Take a break and then give me SteamOS as a container on ChromeOS. Your engineers will see it and would assume already have.

    You are doing some of the most incredible stuff ever with the client and I am old. But keep at, and go faster.


Please enter your comment!
Please enter your name here