Known issues

Here are some known issues with Chromeboxes and Chromebases as well as Google Meet hardware. If available, we list a workaround to help troubleshoot the issue.

Calendar and time zone

Delay in assigning calendar resources

After you’re granted administrator access, it takes up to 24 hours before you can assign a resource to Google Meet hardware. If you still have an issue after 24 hours, contact support.

Time zone setting changes after initial setup

Some Google Meet hardware doesn't retain the user-defined time zone setting after the initial setup, and return to the default time zone.

To resolve this issue, change the time zone using the following method:

Changing the time zone using the Google Admin console

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Devicesand thenGoogle Meet hardware and on the right, click Settings"".

    Some features require the Chrome devices for meetings with Calendar privilege.

  3. Scroll down to the Time Zone field and select the correct time zone.
  4. Click Save.

Meetings

Meetings created on a Chromebox don't show dial-in options
When you tap or click Start a new meeting on a Chromebox, the dial-in options aren't available.
Avoid this by taking one of the following actions:
  • Schedule the meeting through Google Calendar. 
  • Create the meeting on a personal device.
Email addresses in meeting invitations

Gmail ignores the dot within usernames. For example, test.email@gmail.com and testemail@gmail.com are delivered to the same inbox. For more information, see Getting someone else's mail.

If a user's email username has one or more dots, meeting invitations sent from a Chromebox must match the exact address, with the dots included. Otherwise, invitations won't let the invitee in and the user sees the error This party is over.

HDMI

Mimo touchscreen error: Sorry, this room isn't configured properly to support HDMI 

When connecting the HDMI cable, if the message Sorry, this room isn't configured properly to support HDMI shows on the Mimo or the external display, try these approaches: 

  • Ensure that the USB cable connecting to the Mimo is seated properly.
  • If you’re using a USB hub, connect the cable directly to the USB port on the Chromebox. If it works without the hub, make sure the hub has the latest firmware.
  • If the steps above fail, the problem could relate to a bad cable or cabling misconfiguration, such as the USB cable to the Mimo, the HDMI cable to the computer that is presenting, or an HDMI converter. Replace these with Qualified peripherals.
Presenting to a room can fail  

When presenting to a room using HDMI, the presentation stream might not start, or it starts without audio. 

  • Make sure the Mimo touchscreen is connected to power correctly and uses qualified USB 3.0 cables. For more information, see our configuration guide
  • Sometimes, this issue occurs even if the cables are set up correctly. So that we can investigate, file a support ticket.

Peripherals

Audio settings reset after every meeting

To ensure the best experience, set Google-approved peripherals as default. That way, after each meeting, the device resets to these peripherals. 

To use a different peripheral, see Set a default peripheral.

If another peripheral has the default setting, you can manually set the peripheral before the meeting:

  1. On the device, click Settings ""and thenAudio.
  2. Find and select your peripheral.
  3. Unplug all other peripherals before you start the next meeting.
The Huddly GO camera disconnects during meetings
If Chromebox unexpectedly loses the connection to the Huddly GO camera, try to disable the camera auto-zoom feature. Switch the:
  • USB connector from the Chromebox front port to the rear port.
  • Switch the USB 3.0 cable to a USB 2.0 cable.
Camera flickering 

Google Meet hardware users in Japan might experience camera flickering during calls as a result of the device overwriting the anti-flickering setting from 50 Hz to 60 Hz. To resolve this issue:

  1. Set the device to GMT +09:00 Eastern Indonesia Time (Jayapura Time) to change the power frequency setting while staying in the same time zone.
  2. Restart the device.

Hardware & power outages

Chromebox error message: Chrome OS is missing or damaged

If you see the error message Chrome OS is missing or damaged, try to:

  • Wipe and re-enroll the device. For details, see Re-enroll a device.
  • Recover the Chromebox with a USB stick and the Chromebook Recovery Utility extension. Learn to Recover a Chrome OS device.
    Note: You can use the utility to create a recovery USB for Chromeboxes or Chromebooks.

If these steps do not fix the issue, please file a support ticket.

Chromebox might crash or fail to start

If your Chromebox crashes repeatedly or fails to start, it might have a defective component. So that we can investigate, file a support ticket.

Chromebox resets when it loses power

If your Chromebox has a Kingston solid-state drive (SSD), it might unenroll and reset to the initial setup screen when there is a loss of power.

Check if your device has a Kingston SSD

  1. Connect a USB keyboard to the device.
  2. Restart the Chromebox.
    As the device is starting, press Ctrl+Alt+s.
  3. At the bottom of the screen, click Browse as guest
  4. In the Chrome browser window, enter chrome://system.
  5. Scroll to the storage_info section and click Expand
  6. Confirm the model number of the Advanced Technology Attachment (ATA) device is Kingston RBU-SNS4151S316GG2.

If your device is affected by this issue, request a hardware replacement by contacting Hardware support

Still need help?

Related topics


Google, Google Workspace, and related marks and logos are trademarks of Google LLC. All other company and product names are trademarks of the companies with which they are associated.

Was this helpful?
How can we improve it?