Photo: Qagon / Shutterstock.com
Google released a complex solution to fix the issue where Pixel users were locked out of their phone’s local storage due to a storage bug after the January 2024 Google Play system update.
The bug affected Google Pixel 5, 6, 6a, 7, 7a, 8, and 8 Pro models. While the Pixel users were relieved by Google’s acknowledgement and subsequent fix release, the fix doesn’t look user-friendly.
Google’s automatic update system was the perpetrator, and the solution demands a manual intervention that involves downloading developer tools, installing drivers, adjusting settings, connecting the phone, and executing commands via a command-line interface.
“We are aware of a storage issue occurring on a few Pixel phones that have received the January Google Play system update, causing some devices to behave incorrectly. If your device was impacted, you might notice multiple apps crashing, screenshots not saving, and external storage working inconsistently,” said Google’s post.
According to Ars Technica, the silver lining is that users following these intricate steps won’t lose any data, even if their phones have been in a non-functional state for the past week or two.
Nevertheless, many users expressed frustration over the lengthy downtime, and some resorted to wiping their devices, leading to data loss.
Enabling Android’s Developer Options involves a secret action, and the subsequent steps require downloading developer-centric tools like SDK Platform Tools intended for app developers. The reliance on the Android Debug Bridge (ADB) tool, designed for command-line access, adds another layer of complexity.
These two ADB commands and restarting your Pixel device may work:
- ./adb uninstall com.google.android.media.swcodec
- ./adb uninstall com.google.android.media
These modules control Android’s media rendering and processing, including support for formats like HEIF and AV1.
The absence of a user-friendly solution for a problem triggered by an automatic update raises questions about Google’s approach. Most users lack the technical expertise to navigate command-line instructions and developer tools.
Google maintains that only a small number of consumer devices, primarily those with multiple user accounts or work profiles, were affected by the bug.
” We are working on a fix for the root system update issue and we will update this thread when we have more details,” said the Google representative. This means that this is only a temporary solution and users may see a more permanent solution soon.
In the News: US authorities removed the Chinese KV botnet from SOHO routers
