Here are some known issues with Google Meet hardware, as well as Chromeboxes and Chromebases. Where available, we list a workaround to help troubleshoot the issue. If you're still having trouble, a workaround helps you to troubleshoot the issue.
- Issues with Admin console
- Issues with calendar & time zone
- Issues with provisioning & setup
- Issues with meetings
- Issues with HDMI
- Issues with peripherals
- Issues with hardware & power outages
- Still need help?
Issues with Admin console
Custom Home screen not displayingWhen you upload a custom wallpaper, make sure that the organizational unit where the device using the wallpaper is, has the GCP service turned on.
CrOS M126 has a known issue affecting customers using Logitech (Logi) devices. In Google Admin, the speaker/microphone sources for Logitech peripheral might show up twice, requiring Admins to manually change the default microphone and speaker selection. This change needs to be done individually for each device. The system currently defaults unpredictably and may select the Logitech device with the new name or the audio component of an attached display leading to an impacted user experience. We recognize the urgency of this issue and are actively working on a mitigation strategy to resolve it as quickly as possible.
Issues with calendar & time zone
After you’re granted administrator access, it takes up to 24 hours before you can assign a resource to Google Meet hardware.
Some Google Meet hardware doesn't retain the user-defined time zone setting after the initial setup and returns 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
-
Sign in to your Google Admin console.
Sign in using your administrator account (does not end in @gmail.com).
-
Go to Menu
Devices
Google Meet hardware
- Scroll down to the Time Zone field and select the correct time zone.
- Click Save.
Issues with provisioning & setup
- If the device displays an error screen after enrollment, wait a few hours for the update to apply.
- Once the update has been applied, reboot your system.
If you need an immediate fix, you can attempt to carry out a manual recovery on the device. Go to Recover your Google Meet compute system.
Issues with meetings
- Schedule the meeting through Google Calendar.
- Create the meeting on a personal device.
Gmail ignores the dot within usernames. For example, [email protected] and [email protected] are delivered to the same inbox. For more information, go to 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.
Issues with HDMI
When using 2 displays with the Lenovo Meet Compute System - Series One, or the Lenovo Meet Compute System - Series One (Intel 13th Gen), "HDMI- Out 2" is primary and "HDMI- Out 1" is the secondary screen.
If you unplug the HDMI adapter during a presentation, the camera will become undetected for a few seconds and will then mute itself. You should then be able to unmute the camera.
When connecting the HDMI cable, if this message displays, 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 previous steps 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 Approved peripherals for Meet hardware.
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, go to the configuration guide.
Issues with peripherals
Certain Samsung displays behave inconsistently when responding to Consumer Electronics Control (CEC) commands. Even though a Meet hardware device is powered on and sending a signal to the display to wake up, the display may remain powered off or in standby mode. This can result in the Meet hardware device showing a "Meet Could Not Start" error on the touch controller screen.
In order to fix this, you will need to manually power the display on, using the onboard power or a remote. Rebooting the Meet hardware device might also fix the issue.
Due to memory size limitations, our Intel 8th gen Kaby Lake Chromeboxes (Asus Chromebox3 CN65, CTL Chromebox CBx1, Lenovo Series One Meet Compute System (1st Gen) will not be able to download Rally Bar firmware packages. These may not update past the factory version.
Series One Room Kit cameras occasionally drop frames during meetings. This appears as a video stutter.
Series One Room Kit cameras occasionally disconnect. Reboot the system.
To ensure the best experience, set Google-approved peripherals as the default. After each meeting, the device resets to these peripherals.
To use a different peripheral, go to Approved peripherals for Meet hardware.
If another peripheral has the default setting, you can manually set the peripheral before the meeting:
- On the device, click Settings
- Find and select your peripheral.
- Unplug all other peripherals before you start the next meeting.
Google Meet hardware users in Japan might experience camera flickering during video meetings as a result of the device overwriting the anti-flickering setting from 50 Hz to 60 Hz. To resolve this issue:
- 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.
- Restart the device.
Issues with hardware & power outages
When using the Series One audio bar, the speaker and microphone can sometimes take a few minutes to connect after the device is restarted.
If you see the error message ChromeOS is missing or damaged, try to:
- Wipe and re-enroll the device. For details, go to Re-enroll a device.
- Recover the Chromebox with a USB stick and the Chromebook Recovery Utility extension. Learn to Learn to recover your Chromebook..
Note: You can use the utility to create a recovery USB for Chromeboxes or Chromebooks.
If your Chromebox crashes repeatedly or fails to start, it might have a defective component.
Still need help?
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.
