Crota360/Brya: Rotation/Tent Mode Not Working in Windows 11 26100.7623/.7705

[bookofchrome]

Redrix and Pantheon: Is rotation to tablet/tent mode supposed to work in Windows 11 26100?

Devices: Redrix (alderlake/brya family) and Pantheon (kabylake refresh/nami family) Firmware: Full UEFI ROM (MrChromebox-2512.2 on Redrix and MrChromebox-2503.0 on Pantheon) Both are convertible tablets with a 360º hinge. When rotating to tent or tablet mode in Windows, nothing happens at all, keyboard stays enabled, display doesn’t rotate, it continues behaving as a normal clamshell laptop. The Pantheon rotates correctly in Linux (Fedora 43), so it’s not a firmware limitation. The Redrix I d…

@Zidrewndacht

The Redrix… I decided to test on a Fedora 43 LiveCD and… it doesn’t rotate at all there as well.

Then I found this (DriverIdentifier)[ Google Redrix Drivers ] from someone’s different Redrix, which shows the “[ACPI\VEN_GOOG&DEV_0006] Chromebook EC Sensor Hub” showing this device as installed.

Yet mine doesn’t seem to have this device at all?

I also have a brya-based chromebook (Dell Latitude 5430 Chromebook 2-in-1, crota360/brya) that no longer has the Chromebook EC Sensor Hub appear in device manager, even after a clean installation of Windows 11 IoT Enterprise LTSC 2024 and trying to reinstall the crosec 2.0.6 driver package. Weirdly enough, across every distribution of Linux I have tried so far (assume latest for all listed: Linux Mint, Ubuntu, Pop!OS), rotation did not work there either.

Keep in mind… The sensors did work in Windows and all linux distros on the 11-30-2025 build of the mrchromebox firmware. After updating, the sensor hub appeared to stop being presented.

I don’t think this is an OS issue, it could be a problem with how the firmware exposes ACPI\VEN_GOOG&DEV_0006. I have all drivers installed including TB4/Audio and applicable chipset drivers installed.

[Zidrewndacht]

@bookofchrome Redrix is fixed: accelerometer is not working in redrix · Issue #879 · MrChromebox/firmware · GitHub . If what I proposed was indeed what fixed it, it should apply to all affected brya boards.

I suppose MrChromebox will have this fix included for all boards in the next build.