Aurich Lawson
Android 14 has a nasty storage bug that seems to be affecting customers of the “a number of profiles” function. The bug is about as dangerous as you may get, with customers having “unusable” gadgets because of getting locked out of machine storage. A number of customers are likening the expertise to getting hit with “ransomware.”
Earlier studies had this bug restricted to the Pixel 6, however Google appeared to disregard these studies, and now with a wider rollout, this doesn’t appear device-specific. Everything upgrading to Android 14 this early seems to be affected: Pixel 6, 6a, 7, 7a, Pixel Fold, and Pixel Tablet.
The Google concern tracker for that is now as much as over 350 replies and has had no response from Google. The bug is languishing at solely the medium “P2” precedence (P0 is the very best) and stays “unassigned,” which means, assuming the tracker is updated, nobody is trying into it.
Some customers have helpfully posted log information stuffed with worrying messages, like, “Failed to open listing /data/media/0: Structure wants cleansing.” Being locked out of your individual machine’s data partition causes all types of weird points. Some customers are boot looping, others are caught on a “Pixel is beginning…” message, whereas others can get into the cellphone. If your cellphone tries to proceed trucking with no native storage, you will be inundated with all types of error messages. The digital camera app claims to be “out of storage,” and you may’t take screenshots as a result of there’s nowhere to retailer the screenshots. The file supervisor lists 0 bytes for each sort of file and empty folder, and the information additionally aren’t viewable from a PC over USB. The System UI and Settings additionally preserve crashing. Basically, computer systems want storage to perform!
Android’s user-profile system permits for each a number of customers on a single machine (which is nice for tablets) and splitting up “residence” and “work” profiles to maintain your work data separate from your private data, by way of duplicate apps. It sounds just like the bug is simply hitting customers who reap the benefits of this not often used function, with a number of studies that the first profile—that is often the essential one—will get locked out.
Several customers are complaining in regards to the data misplaced from all of this, so it is a good time to remind folks to all the time have a backup of the whole lot on their telephones. Even straight out of the field, Android has choices for Google Photos automated backups, Play Games storage of your recreation data, and one million different cloud-based data options (it could be good if Android telephones had a complete whole-phone backup function, although). While it’s completely cheap to count on your OS to maintain operating after an replace, telephones are uniquely susceptible to getting misplaced/stolen/broken, so having the whole lot get saved some other place is a good concept. Shockingly, a number of customers report the cellphone is robotically doing a manufacturing facility reset, which deletes all of your data, shutting down any chance of data restoration. This function ought to in all probability not exist, but it surely’s one other signal that telephones aren’t a dependable storage medium for vital data.
What’s so unusual about how Google is dealing with this bug is that the corporate has instruments to cope with this. Google delivers software program on a gradual and infrequently irritating “roll out” technique, the place a small proportion of customers will get an replace at first, and because the days move, increasingly customers decide in to the replace. Google does this to see if any issues pop up by way of its intensive Android analytics system, and if an issue is detected, the replace rollout may be halted, limiting the issue to as few folks as potential.
Why did not that occur right here? Surely, a bug the place persons are locked out of their telephones and probably lose data is price halting a rollout, but it surely by no means occurred. Google’s complete response to this drawback has been missing. To our data, nobody from Google has formally addressed the difficulty within the 10-ish days it has been round. It hasn’t issued statements to the a number of websites which have already reported on this. No one is replying to the bug tracker, and the difficulty is unassigned. What’s up, Google?