Years ago, I switched to the beta channel for my Chromebooks because I like getting the latest, greatest features before they are released to the stable channel. Not only does this switch allow me to keep readers informed of what’s coming, but it also gives me the chance to experience what Google has in store for ChromeOS.
There’s another reason I opt to use this channel…to offer my input. You see, when using the beta channel, you are given the option to send the developers feedback on your experiences. This feedback could be bugs/problems you’ve run into or even to make suggestions on how to improve something.
One thing to keep in mind, however, is that you’ll want to include relevant information in your report, which could be:
- Screenshots of the issue (if applicable)
- What you were doing when the issue happened
- Steps on how to re-create the issue
- What version of ChromeOS you are using
- You can even attach system logs (more on this in a bit)
- Your contact information
Adding this information might seem a bit daunting, but the help you offer the developer could be the thing that makes it possible to resolve an issue that’s causing you problems with your Chromebook. Keep in mind, however, that you do not have to use the beta channel to report issues. Even the stable version, which you’re probably using, allows you to report bugs.
First, I’m going to show you how to access the Send Feedback window, and then I’ll show you how to access your log files and attach them to the report.
How to access the feedback window
What you’ll need: The only thing you’ll need for this task is a Chromebook. As usual, I would suggest you make sure ChromeOS is updated, which is a process that could solve your issue. That’s it. Now, let’s get to that feedback window.
On the resulting page, click Store system logs and wait for the OS to finish. The system logs will be saved to your Downloads file in the form of system_logs_DATE.txt.zip (where DATE is the date on which the logs were generated).
And that’s all there is to sending feedback to the ChromeOS developers. By doing this work, you’re not only helping the development team resolve a possible issue you might have, but also allowing them to improve ChromeOS for everyone.