Devices
9 TopicsHow to change the keyboard layout in managed chromebooks?
We currently have around 100 Chromebooks that we use for exams. I have now been asked to make it possible for participants to change the keyboard layout. Most use the German keyboard, but a few want to write with an English or French layout. What do I need to set in the management console so that participants can change the layout on their devices?42Views0likes2CommentsThe ChromeOS "Developer Wall": Why is Pro-Grade Hardware so hard to find?
(Traduction en français à la suite) Hi everyone, I’m writing this to start a discussion about a major bottleneck for the ChromeOS ecosystem: the lack of high-performance hardware for developers. I’ve been a "ChromeOS-first" developer for a while now. I love the security, the simplicity, and how far Crostini (Linux) has come. However, I’ve hit a wall. I am currently using a machine with an **Intel i5, 16GB RAM, and a 1TB SSD**. On any "Consumer" list, this is a top-tier machine. But for professional development—compiling large C++ or Rust projects, running multiple Docker containers, and keeping a heavy IDE open—it is simply **under-dimensioned.** Compilation times are 2x to 3x slower than my peers on high-end macOS or Linux workstations. The Search for the "Unicorn" Chromebox I’ve been searching for a "Workstation Class" Chromebox. My target specs are: * **Processor:** Intel Core i7 (13th/14th Gen) or ideally an i9. * **RAM:** 32GB or 64GB (Crucial for virtualization and containers). * **Storage:** 1TB+ NVMe SSD. If you go to Amazon or Best Buy, the selection is disappointing. You are flooded with Celeron, i3, or low-power i5 machines. Even "Chromebook Plus" devices usually cap out at 8GB or 16GB of RAM, which is the bare minimum for modern dev work, not the "Pro" standard. #### Why is high-end hardware "Invisible"? After some deep diving, I’ve realized that if you want a real developer machine, you have to look beyond consumer retail. Here is the reality of the market right now: **1. The Enterprise Channel (The $800 - $1,200 bracket)** Manufacturers like **HP** and **ASUS** do make powerful units, but they are tucked away in "Enterprise" catalogs. * **HP Chromebox G4 (Enterprise Edition):** Can be found with an i7-1360P. Price usually sits around **$850 - $1,050**, but you often have to buy through a specialized reseller like CTL or Promevo. * **ASUS Chromebox 5/6:** The i7 versions are beastly but usually ship with only 16GB. Retail price: **$700 - $900**. **2. The DIY Workaround ($900 - $1,100 total)** Ironically, the best "Pro" Chromebox is often a DIY project. * **The Strategy:** Buy a base **ASUS Chromebox 5 (i7 version)** for approx. **$750**. * **The Upgrade:** Spend another **$150 - $200** on a 64GB DDR5 RAM kit and a faster 2TB NVMe drive. * **The Result:** A machine that actually handles professional loads, but one that requires the user to void a warranty or at least open the chassis—something we shouldn't have to do at this price point. **3. The Framework Exception (~$1,000+)** The Framework Chromebook Edition remains the only "pro-consumer" option that respects high specs, though it’s a laptop form factor. To get an i7 with 32GB+ RAM, you are looking at a **$1,100+** investment. #### My Question to the Community Why is there such a massive gap between Google’s marketing of "ChromeOS for Developers" and the actual availability of hardware? * Has anyone found a reliable source for **pre-configured 32GB+ Chromeboxes**? * Are there any "whitebox" manufacturers building high-end ChromeOS hardware that I've missed? * Do you think Google needs a "Chromebook Ultra" or "Pro" tier that mandates 32GB RAM to separate professional machines from student laptops? I’d love to hear how other devs are solving the hardware shortage. Are you all just buying mid-range boxes and upgrading the RAM yourselves, or is there a "secret" store I don't know about? Note: Research for pricing and models assisted by AI, but the frustration is 100% mine! Français: Le « Mur du Développeur » sous ChromeOS : Pourquoi le matériel de niveau « Pro » est-il si difficile à trouver ? Bonjour à tous, J'écris ce post pour lancer une discussion sur un goulot d'étranglement majeur de l'écosystème ChromeOS : le manque de matériel haute performance pour les développeurs. Je suis un développeur « ChromeOS-first » depuis un certain temps déjà. J'adore la sécurité, la simplicité et la maturité qu'a atteinte Crostini (Linux). Pourtant, j'ai atteint un mur. J'utilise actuellement une machine équipée d'un **Intel i5, 16 Go de RAM et un SSD de 1 To**. Sur n'importe quel site de vente grand public, c'est une machine haut de gamme. Mais pour du développement professionnel — compiler de gros projets en C++ ou Rust, faire tourner plusieurs conteneurs Docker et garder un IDE lourd ouvert — elle est tout simplement **sous-dimensionnée.** Mes temps de compilation sont 2 à 3 fois plus longs que ceux de mes collègues sur des stations de travail macOS ou Linux. #### La quête de la Chromebox « Licorne » Je recherche une Chromebox de classe « Workstation ». Mes spécifications cibles sont : * **Processeur :** Intel Core i7 (13e/14e génération) ou idéalement un i9. * **RAM :** 32 Go ou 64 Go (crucial pour la virtualisation et les conteneurs). * **Stockage :** SSD NVMe de 1 To ou plus. Si vous allez sur Amazon ou dans les grandes enseignes, la sélection est décevante. On est inondé de machines Celeron, i3 ou i5 basse consommation. Même les appareils « Chromebook Plus » plafonnent généralement à 8 ou 16 Go de RAM, ce qui est le strict minimum pour le développement moderne, et non un standard « Pro ». #### Pourquoi le matériel haut de gamme est-il « invisible » ? Après quelques recherches approfondies, j'ai réalisé que pour obtenir une vraie machine de développeur, il faut regarder au-delà de la vente au détail classique. Voici la réalité du marché actuel : **1. Le canal Entreprise (Tranche 800 $ - 1 200 $)** Des fabricants comme **HP** et **ASUS** fabriquent des unités puissantes, mais elles sont cachées dans les catalogues « Enterprise ». * **HP Chromebox G4 (Enterprise Edition) :** On peut la trouver avec un i7-1360P. Le prix se situe généralement autour de **850 $ - 1 050 $**, mais il faut souvent passer par un revendeur spécialisé comme CTL ou Promevo. * **ASUS Chromebox 5/6 :** Les versions i7 sont très performantes mais ne sont généralement livrées qu'avec 16 Go de RAM. Prix de vente : **700 $ - 900 $**. **2. La solution DIY (Total 900 $ - 1 100 $)** Ironiquement, la meilleure Chromebox « Pro » est souvent un projet à monter soi-même. * **La stratégie :** Acheter une **ASUS Chromebox 5 (version i7)** de base pour environ **750 $**. * **L'upgrade :** Dépenser **150 $ - 200 $** supplémentaires pour un kit RAM de 64 Go DDR5 et un drive NVMe de 2 To plus rapide. * **Le résultat :** Une machine qui encaisse enfin les charges professionnelles, mais qui oblige l'utilisateur à ouvrir le châssis (et potentiellement risquer la garantie), ce qu'on ne devrait pas avoir à faire à ce niveau de prix. **3. L'exception Framework (~1 000 $ +)** La version Chromebook de Framework reste la seule option « pro-consommateur » qui respecte les hautes spécifications, bien qu'il s'agisse d'un format ordinateur portable. Pour un i7 avec 32 Go de RAM ou plus, on dépasse les **1 100 $** d'investissement. #### Mes questions à la communauté Pourquoi y a-t-il un tel fossé entre le marketing de Google « ChromeOS pour les développeurs » et la disponibilité réelle du matériel ? * Quelqu'un a-t-il trouvé une source fiable pour des **Chromebox pré-configurées avec 32 Go+ de RAM** ? * Existe-t-il des fabricants « whitebox » (génériques) qui construisent du matériel ChromeOS haut de gamme que j'aurais ratés ? * Pensez-vous que Google ait besoin d'un palier « Chromebook Ultra » ou « Pro » qui imposerait 32 Go de RAM pour séparer les machines professionnelles des ordinateurs pour étudiants ? J'aimerais savoir comment les autres devs résolvent ce manque de matériel. Est-ce que vous achetez tous des boîtiers de milieu de gamme pour améliorer la RAM vous-mêmes, ou existe-t-il un magasin « secret » que je ne connais pas ? Note : Si l'IA a aidé pour les chiffres et les modèles, la frustration, elle, est 100 % d'origine humaine !12Views0likes0CommentsCustom Protocol Handler for Isolated Web App Not Working After ChromeOS Update (May be).
Hello, After my ChromeOS device updated on September 25, 2025 (though not certain this is the direct cause), custom protocol handlers (web+collab:// and collab://) for my Isolated Web App (IWA) stopped working. Triggering these links in Chrome no longer launches the app—they simply do nothing. This was functional until two days ago. App Type: Isolated Web App (IWA) Manifest excerpt: { "name": "someapp", "id": "/", "short_name": "some-app", "version": "0.1.0", "update_manifest_url": "https://github.com/--some-repo--/iwa-release/releases/latest/download/update.json", "icons": [ { "src": "/192x192.png", "sizes": "192x192", "type": "image/png", "purpose": "any maskable" }, { "src": "/144x144.png", "sizes": "144x144", "type": "image/png", "purpose": "any maskable" } ], "start_url": "/", "scope": "/", "display": "standalone", "display_override": ["borderless"], "background_color": "#ffffff", "theme_color": "#3B82F6", "isolated_storage": true, "permissions_policy": { "cross-origin-isolated": ["self"], "direct-sockets": ["self"], "controlled-frame": ["self"], "window-management": ["self"], "display-capture": ["self"], "all-screens-capture": ["self"] }, "protocol_handlers": [ { "protocol": "web+collab", "url": "/?data=%s" }, { "protocol": "collab", "url": "/?data=%s" } ], "launch_handler": { "client_mode": "navigate-existing" }, "window_controls_overlay": { "enabled": true } } Recent Changes Enrolled new users in Google enterprise Updated the app manifest (see above) ChromeOS device updated on 2025-09-25 Observed Behavior Protocol links for both my IWA (web+collab://) and the official ChromeOS IWA SINK app (web+cf://) no longer launch the installed apps No errors, warnings, or manifest validation issues Clicking protocol links does nothing (both in managed and unmanaged device states) What I've Tried Checked manifest and protocol handler registration Tested after app reinstall and in different device policy states Reviewed enterprise Admin Console for new/relevant policy changes Searched for protocol handler or IWA-related changelogs/updates Compared behavior with different protocol URLs and schemes Questions Is anyone else experiencing protocol handler breakages for IWAs since a recent Chrome/ChromeOS update? Have there been changes in policy, manifest format, or handler registration that could affect this? Any ideas or diagnostics for discovering if Chrome or policy is blocking/ignoring the protocol? Any leads, recent experiences, or possible workarounds would be greatly appreciatedSolved170Views1like5CommentsAny plan to certify MacBookAir8,1 or 8,2 for Chromeos Flex?
Hi, is there any plan to develop full Chrome OS Flex support for T2 Intel macbook airs from 2018-2019? I tried installed it on the that machine, but it has common Linux struggle with T2 security chip: keyboard, touchpad, wifi and bluetooth not worked. So, I wondering, if there will be some future support? I know that the non-working parts, i mentioned, is possible to have fully working with t2linux project. I am running Fedora 42 with t2linux patches without issues. Thanks Alv.Solved114Views0likes2CommentsChrome OS Flex AUE in Google Admin
Hey. The admin console has a fantastic feature where you can see the AUE of your devices pr year. It makes it easier to plan budget for replacing devices going out of support and planning execution. https://admin.google.com/ac/chrome/devices/?sf=2&so=2&tab=dashboard However - you can only see Chrome OS devices since the "Automatic updates until" field in Google Admin is not populated as in the example below. Obviously this information is available somewhere to be displayed, but it is currently not. I would really like to avoid exporting inventory to a spreadsheet, use the certified model list (https://support.google.com/chromeosflex/answer/11513094?hl=en) to populate the empty field in the spreadsheet and keep track of it there. How do others plan inventory replacements? Has anyone else tried to reach out to the Chrome OS team pointing out this flaw?Solved78Views0likes1CommentPoly Studio Video stopped working
After updating to most recent version iof Chrome OS Flex (138.0.7204.221) we are no longer able to use videosource using Google Meet. First it reports missing credentials. After a restart it claims that the video source could not be used as it might be in use by other apps (no other apps are running). Screenshot from settings In norwegian "Tillatelse kreves" => eng: "Permission is required" After a hard restart (power off/on) Chrome OS says the camera can not be used. I have tried the suggested solution of "disconnent the camera and connect it again". It worked with the prevous version of Chrome OS Flex ( like version 136.0.7103.158).124Views0likes5Comments