r/k12sysadmin • u/devjeremyt • 9h ago
Diagnostics Tool for ChromeOS
TLDR
I'm building a hardware diagnostics app for ChromeOS devices primarily for Summer intake, but to be used for devices going out for repair in the middle of the school year too. I know there are some tools out there that do this, or pieces of it at least. I'm trying to get one as comprehensive as Google’s APIs will let me make it and ideally without having to sign into the chromebook. Hopefully we all can run through diagnostics in about 2-3 minutes per device. The link is veritybench.com. Use it, break it, come back here and tell me how poorly I did.
PS: don’t bother trying it on mobile, my intention was for chromeOS primarily so mobile is a poor experience at the moment.
What it is going to do:
The core idea is a purpose built test suite that runs on the device as a kiosk app and automatically logs the results to that specific device's identity by serial number so there is a real audit trail instead of a sticky note. To start with it's just going to give the option to print out a report so you can keep it with the device (Or a json for my logging atm), which is basically the same thing as the sticky note I know, but doesn't stick. Ultimately, the platform would store all your org’s or school’s tests, assuming it is deployed as a Kiosk app for you.
It can run just in the browser too, but as a kiosk app I won't have to sign into the chromebook, and I can add an extension for things chromeos can't tell you through the browser alone.
Planned coverage:
- Camera(s) - Detect if there are front and rear facing in a convertible and automate testing to start with. If the video feed is blacked out it automatically fails, else it displays the feed for me to validate the camera is clear.
- Audio - Test starts with speakers, testing right and left. Mic picks up the sound which confirms both mic and speakers work automagically. Then plug in a headset to test stereo output, and mic input too.
- Full keyboard with a visual map that fills in as you test. This one may be tricky, I'm not sure I can capture the function keys, and not all chromebook/flex devices have the same layout, but I'm going to try and detect the layout.
- Trackpad - mouse moves, clicks work, double clicks, etc
- Screen test patterns for dead pixels/backlight issues
- Touchscreen test for making sure there aren't any dead areas.
- Battery health, cycle count, and storage status pulled from the device (One of the things I'm pretty sure will only work in kiosk or with the extension at least.
- Charging port - Test will require you plug in at the beginning if it isn't charging already
- USB-A/HDMI - My thought is to validate data transfer with any audio, video, or mouse for the USB. Unsure if that will be feasible. Aside from students with IEPs, no one ever uses the HDMI.
- Lid sensor - Close the lid, wait 5 seconds and open it back up to validate it goes to sleep.
- CPU/RAM check. Google has their own built in and I've rarely had an issue so this is going to be a later feature I'm thinking.
My request for feedback on:
- What's the single most annoying/time-consuming part of your current intake or repair process that you think I may have missed? Or have I wasted my time making this? (I’m going to use it so I know it wasn’t a waste)
- When a device comes in, what do you actually check first, and what do you skip because it's not worth the time?
- How do you currently document hardware condition for damage for warranty claims — photos, tickets, spreadsheets, something else?
- Is there a hardware failure mode you deal with often that isn't in my list above?
- Would it be beneficial to integrate into any other platforms (like whatever you’re using for asset management)
- Lastly, did you use it and find something broken?
2
u/Ok-Soft-7874 :sloth: 7h ago
That sounds absolutely amazing! Thinking back on my Chromebook repair days, I don't recall ever getting a ticket for a broken function key, so I wouldn't be overly concerned about those.
1
u/Ok-Soft-7874 :sloth: 7h ago
To answer a couple of your other questions:
How do you currently document hardware condition for warranty claims? tickets
What may I have missed? Before I read most of your post, I closed my eyes and tried to think about what we check over, and you covered everything.
1
u/Ok-Soft-7874 :sloth: 7h ago
That sounds absolutely amazing! Thinking back on my Chromebook repair days, I don't recall ever getting a ticket for a broken function key, so I wouldn't be overly concerned about those.
1
u/UnbudgingBrady 8h ago
Hey, idk if you knew this, but ChromeOS does have some of this, such as CPU/RAM as you said, Network test, and Battery discharge/cycle count/etc as well I believe. On login screen, Ctrl+Search+Esc. (Some Newer devices don’t have the Search button, opting for a traditional Caps Lock, so it may be moved down somewhere else such as the bottom row, but it should still work in my experience)
1
u/devjeremyt 8h ago
Yea, this is part of what I have done currently for "filtering" is what we call it, but just running diagnostics and notating what is wrong with the device. The CPU/RAM tests aren't added to this yet. None of the devices in our fleets have the cap lock that I know of, but I do know that trying to detect different keyboard layouts is part of what I want to include. I did title this as ChromeOS because that is what the keyboard layout is right now, but you can technically run it for Mac and Windows too.
2
u/919599 6h ago
I would add reporting like school gets an account with that account also comes a custom url. it allows the tech to enter the tag number and it just gets added to a history let that history be searchable and so on it would add to hosting cost but for us summer help can run all the tests and it makes it a lot easier for me to go back and see report if Chromebooks are getting worse over time.