If your GPD Pocket 4 has stopped rotating the display automatically, the Rotation Lock option is missing, and the accelerometer shows “This device cannot start (Code 10)” in Device Manager, the problem may be caused by a recent AMD I2C controller driver update.
Recent affected systems were restored by rolling back the specific AMD I2C Controller used by the Pocket 4 accelerometer. Reinstalling the accelerometer driver or the complete GPD driver package may not work because Windows can retain the newer, higher-version AMD I2C driver.
Symptoms
- The display no longer rotates when the GPD Pocket 4 is turned.
- The Rotation Lock control is missing from Windows Settings or Quick Settings.
- The Memsic MXC6655 accelerometer appears in Device Manager with a yellow warning icon.
- The device status reports “This device cannot start (Code 10)”.
What causes the problem?
The GPD Pocket 4 uses a Memsic MXC6655 accelerometer, which communicates with Windows through an AMD I2C controller. Evidence from affected systems indicates a compatibility regression in the newer AMD I2C driver rather than a physical failure of the accelerometer.
AMD Ryzen Chipset Software 8.07.16.1035 includes AMD I2C driver version 1.2.0.131. The preceding 8.05.04.516 package includes version 1.2.0.126. Rolling the relevant controller back to the previous driver has restored the accelerometer and automatic rotation on affected devices.
This has not been formally confirmed by AMD or GPD as a universal defect, so check the installed driver version before making changes. Do not force an unrelated driver if your version or hardware differs.
Fix: roll back the AMD I2C Controller
- Right-click the Start button and select Device Manager.
- Open the View menu and select Devices by connection.
- Locate the failing Memsic MXC6655 accelerometer. Use the connection tree to identify the parent AMD I2C Controller.
- Right-click that AMD I2C Controller and select Properties.
- Open the Driver tab and note the current Driver Version. Taking a photo or screenshot is recommended.
- Select Roll Back Driver. If Windows asks for a reason, select the option explaining that the previous driver worked correctly.
- Restart the GPD Pocket 4.
If more than one AMD I2C Controller is listed, do not roll back controllers at random. Use Devices by connection to identify the controller associated with the accelerometer.
If Roll Back Driver is unavailable
- Open the affected AMD I2C Controller’s Properties window and select Update Driver.
- Select Browse my computer for drivers, followed by Let me pick from a list of available drivers on my computer.
- If AMD I2C driver 1.2.0.126 is listed for the same controller, select it and complete the installation.
- Restart the device.
If the previous driver is not stored on the PC, use AMD’s previous Ryzen Chipset Software release or the official GPD Pocket 4 driver package. Installing an older package normally may still leave the newer I2C driver in place, so verify the controller’s Driver Version afterwards. If you are unsure which controller or driver applies, contact support before forcing a manual driver installation.
Perform a cold reset
If Code 10 remains after the driver rollback:
- Shut down Windows completely.
- Disconnect the charger, USB devices, docks and other peripherals.
- With the Pocket 4 switched off, hold the power button for approximately 20 to 30 seconds.
- Reconnect the charger and start the device.
Confirm that the fix worked
- Open Device Manager and confirm that the warning icon and Code 10 error have disappeared from the MXC6655 accelerometer.
- Check that Rotation Lock is available again in Windows Settings or Quick Settings.
- Rotate the Pocket 4 through each supported orientation and allow a few seconds for Windows to respond.
Avoid reinstalling the problem driver
Windows Update or a later AMD chipset installation may offer the newer I2C driver again. Until AMD or GPD provides a confirmed corrected release, check the AMD I2C Controller’s version after chipset updates. Avoid registry rotation fixes, BIOS flashing or reinstalling Windows while the accelerometer still reports Code 10; those steps do not address a controller driver that cannot start the sensor.
Questions & answers