How to send feedback to help ChromeOS developers (and why you should)

3 minutes, 41 seconds Read


chromebook-plus-x360-keyboard

Caesar Cadenus/Zdnet

A few years ago, I switched to the beta channel for my Chromebook because I like to get the latest, greatest features before they are released to the stable channel. This switch not only allows me to keep readers informed of what’s coming, but it also gives me a chance to experience what Google has in store for ChromeOS.

There is another reason I choose to use this channel to offer my input. You see, when using the beta channel, you are given the option to send feedback to the developers on your experience. This feedback can be about bugs/issues you’ve run into or even suggestions on how to improve something.

Also: How to Enable Linux on Your Chromebook (And Why You Should)

One thing to keep in mind, however, is that you’ll want to include relevant information in your report, which could be:

  • Screenshot of the problem (if applicable)
  • What were you doing when the problem occurred?
  • Steps on how to reproduce the problem
  • Which version of ChromeOS are you using?
  • You can even attach system logs (more on this a bit later).
  • Your contact information

Adding this information may seem a little difficult, but the support you provide to the developer could be the very thing that makes it possible to solve a problem that is causing problems with your Chromebook. But remember, you don’t have to use the beta channel to report issues. Even the stable version, which you’re probably using, allows you to report bugs.

Also: 5 Reasons Why Chromebooks Are the Perfect Laptop for Most People

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 reports.

How to access the feedback window

What you will need: All you need for this task is a Chromebook As usual, I recommend that you make sure that ChromeOS is updated, a process that may solve your problem. That’s it. Now, let’s get to that feedback window.

The first thing is to log in to your Chromebook. Once logged in, you don’t need to open any apps to access the feedback window.

The easiest way to open the React window is the Alt+Shift+i keyboard combination. This action will open a small window, where you will first be asked to describe your problem. After you add a description, click continue.

The first window of the ChromeOS Feedback Wizard.

From this window, you can access top help content, which can help you solve your problem.

Screenshot by Jack Wallen/ZdNet

Before you continue, you may want to attach the system logs, which can be of great help to those examining your report. To access system logs, open Chrome on your Chromebook and type the following text in the address bar:

chrome://network/#logs​

On the results page, click Save the system log And wait for the OS to finish. System logs will be saved in your download file as system_logs_DATE.txt.zip (where the DATE is the date the logs were created).

ChromeOS Log File Generation window.

Here you can choose to include the policy configuration and separate log files collected by debugd as a separate file.

Screenshot by Jack Wallen/ZdNet

Click Next Page in the feedback window Add documents And then, when File Manager opens, navigate to System Log to attach it.

Also: How to quickly create a Google Task from an email in Gmail

You can also select the email address to associate with the response, add a screenshot, and allow Google to contact you about the issue. Once you take care of that, click send And feedback report will be sent.

The final window of the ChromeOS feedback window.

You have many options to help make your feedback report more helpful.

Screenshot by Jack Wallen/ZdNet

And that’s it for sending feedback to ChromeOS developers. By doing this, you’re not only helping the development team fix a potential problem you might have, but also allowing them to improve ChromeOS for everyone.





Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *