At Flint we believe the future of computing is web based. Web based technologies have improved dramatically in recent years. It is now possible to stream games, produce complex documents, collaborate with co-workers, basically anything from a web browser!
That is why Flint OS is built on the Chromium OS project. We aim to support a range of PC’s and popular Single-Board-Computers such as the Raspberry Pi and t-firefly, providing a simple , safe and secure way of getting things done via the web.
At the moment we have 2 release streams for Flint OS, namely Flint OS for Pi and Flint OS for PC.
Flint OS for Pi supports Raspberry Pi 2 and 3, other Raspberry Pi models are currently unsupported. Head over to https://flintos.io/instructions-rpi/ for instructions on how to run Flint OS for the Raspberry Pi.
For the PC, Flint OS has to be booted via a USB storage drive. Please head to https://flintos.io/instructions-pc/ for detailed instructions.
It is possible to install Flint OS for PC onto your hard drive so that you don’t need to boot Flint OS every time from a USB drive. However, at the moment we can only support Flint OS to occupy your entire hard drive. In other words, if you wish to install Flint OS onto your hard drive, you will lose every piece of data on this hard drive. If you are prepared to do this, please visit this link for the instruction.
Flint OS for PC is currently in early development, this means Flint OS is not supposed to work well at this stage and it does not work on every machine. You will also find bugs, glitches and crashes.
Our aim is to support as many PC’s as possible both 32bit and 64bit. Currently we support a wide variety of Intel, Nvidia and AMD/ATI graphics setups running 64bit Processors. 32bit system support will follow soon.
If for any reason Flint OS does not boot on your PC, please let us know with your detailed setup and error symptoms via /r/flintos, we (and the community) will try our best to help you.
We are always working to improve Wi-Fi compatibility. If you find that Wi-Fi can not work on your computer after installation, you can try to run
switch2wl on the command line to utilise alternative Broadcom firmware.
To enter the command line, press
Fn+Ctrl+Alt+F2 on some computers) after the login prompt appears. If you are not familiar with the command line, you can use the more friendly Crosh, just press the
Ctrl+Alt+t in the browser interface.
Once at the command line type sudo su and follow the prompts to set your own password. Then type
switch2wl The system may require a manual reboot, after this Wi-Fi networks should start to appear.
If you still cannot access Wi-Fi, please tell us your computer Wi-Fi chipset and we will try to fit in the future release of the chip.
Flash requires a licence to distribute which we are looking to obtain, for inclusion in future builds.
Previously the default password was
chronos but going forward all Flint OS builds will not have a default password set due to security concerns.
There are two options available depending on your requirements:
If you want to set a password for developer access and SSH use the command
sudo passwd chronosreplace
chronos with your own preferred password.
If you would just like developer access use the command
chomeos-setdevpasswd and then set your preferred password.
Netflix and Amazon Instant video require the DRM plugin called Widevine.
We are currently working on Widevine implementation into Flint OS, this is more of a licensing issue than a technical task so we can’t give any timelines unfortunately.
Support for Android apps is still in an experimental stage with Flint OS therefore it’s not yet included in our public releases. Once we believe it’s ready we will include this support for you to test.
For the time being, if you believe Flint OS + Android can be part of a business solution that can help your company or your product, please let us know.
We have had many questions regarding the Google Play Store in Flint OS. The Google Play Store and Android despite the obvious similarities are separate.
Android is an open source operating system much like Chromium OS and has been forked by many companies such as Amazon with their Fire tablets. The Google Play Store requires authorisation from Google to be included within a distribution based on a set of criteria. Apps distributed through the Play store usually rely on Google Services Framework for functions within the App and without authorisation from Google to include these in the operating system the apps will usually fail to function as expected.
At the moment Flint OS does not have any intention in shipping the Google Play store and we’re not allowed to do so. We may add ways for our users at a later point which allows easy distribution of Android applications more suited Flint OS.
Not yet, but it is a feature we are looking into. Currently we are ensuring the OS will fit onto a 8GB SD card for the Pi or 8GB USB stick for the PC builds.
Note we have done some OS performance tests and found there to be no noticeable difference between using a 8GB image or a 32GB image, there is however a big difference depending on which USB or SD card your using.
In all the testing we have been doing we have found that the storage media you are using has a huge effect on the user experience.
There will be other SD cards or USB sticks that work well but in our testing the following have performed well:
As fantastic a machine the Pi is, the HDMI settings can be a bit tricky. If you can please try the Pi with Flint OS on a few different screens before getting in contact we will be able to see if it is an issue with the config.txt file.
We are looking into enabling users ability to edit the config.txt file as with other Raspberry Pi operating systems.
This is a work in progress, and a feature we are very keen to get working.
Currently we haven’t made any specific adjustments to Flint OS for Kiosks but have seen a lot of uses for Flint OS in a kiosk environment and will be working on this across the platforms.
When using etcher on Windows 10 to burn OS images to an SD card or USB we have found running the program in administrator mode is a lot more reliable. (Thanks for the tip Greg!)