A new bug prevents access to the internal storage of Pixels


Image: Max Buondonno/ZDNET.

Three months ago, when Android 14 was released, a bug affected many Pixels, preventing their owners from accessing their device’s internal storage. In addition to limiting access to internal storage, this bug caused other issues, including application crashes (especially the camera), File Explorer not showing any files, and various messages error: “storage is full”, “system user interface is not responding”, or “Android system is corrupt”.

Ultimately, the bug was due to the presence of multiple profiles on the same device and Google deployed a fix a few weeks later.

But the problem seems to be back with the Play update of January 2024. For several days, users have been reporting problems accessing the internal storage of their device, screenshots that do not save , or even files that disappear.

Check your Google Play version

Fortunately, the issues caused by this update appear to only affect a minority of devices.

To check which version of Google Play you are using, go to Settings > Security & Privacy > System & Updates. If you already have the January version and you don’t have any bugs, everything is fine. If you’re still using the November version, on the other hand, wait for the green light from Google before installing the new update – especially if your device has multiple profiles.

Various Pixel devices are affected by the issues caused by this update, including the Pixel Fold, Pixel 8 Pro, Pixel 7, Pixel 6, and Pixel 5.

We do not yet know if the problem is linked, like last time, to the presence of several profiles on a device, or if the reason is completely different.

Waiting for the fix

The bug caused by the installation of Android 14 had simply been resolved by a patch published by Google. However, there is no fix for this bug yet.

Some people have managed to resolve the issue by resetting their device to factory settings. However, this is a last resort solution, which will erase all data from your device.

Google has acknowledged the existence of this bug and indicated that it is looking into it on 9to5Google.

Source: ZDNet.com



Source link -97