Some Pixel 6 clients got a discourteous shock subsequent to refreshing their telephone to Android 14, as they were kept out of their telephone’s inner stockpiling. The issue essentially impacted Pixel clients who had numerous client or visitor profiles set up. Following a rising number of reports, Google recognized the bug and affirmed it was dealing with a fix. Toward the end of last week, the organization made the fix accessible for impacted clients through a test, noticing a more extensive delivery could begin in the following fourteen days. That fix is currently carrying out as a piece of the November 2023 security fix, with more knowledge likewise being accessible on what precisely turned out badly.
Google’s delivery notes for the November 2023 security fix notice the multi-client bug fix. This update went live recently and will carry out to all Pixel clients throughout the following week.
As Google recently uncovered, this arrangement will just help Pixel clients kept out of their telephone’s essential stockpiling. In the event that your telephone stalled out in a boot circle because of the bug, the November update will do nothing to fix that. You should production line reset your gadget to inspire it to work once more, losing all put away information all the while.
However, what prompted Android 14 keeping some Pixel clients out of their telephones? Android master Mishaal Rahman has revealed some insight into that. Purportedly, the issue was brought about by a bug during the F2FS document framework, which Pixel telephones use for their information segment. While more established Pixels additionally utilize a similar document framework, the bug is apparently found in bits in light of Linux 5.10, utilized by the Pixel 6 and 7 series.
Google didn’t uncover more insights concerning the flawed patches that made the bug decide the impacted Linux adaptations.
The bug is set off by a “corrupted xattr (extended attribute) entry that occurs when a secondary user is removed and the file system is F2FS,” according to Mishaal. Google’s fix for the bug runs a record framework consistency check (fsck) when the information parcel is mounted. This likewise makes sense of why impacted Pixels take strangely lengthy to boot subsequent to introducing the November security fix.
What’s amazing is the way Google didn’t discover the bug during testing, which at last prompted a little segment of Pixel clients being locked out from their telephones.
Strangely, Mishaal takes note of that since an issue with F2FS causes the bug, it could likewise influence other Android telephones utilizing a similar document framework. For instance, the Samsung Cosmic system S23 involves F2FS for its information segment. While the organization has proactively carried out the Android 14 update for the gadget, there have not been any reports from clients about being kept out of their telephone’s interior stockpiling.
This could be on the grounds that Samsung doesn’t offer the capacity to make an optional or visitor client profile as a piece of One UI. In any case, considering how serious the bug is, anticipate that all significant Android makers should consolidate the fix in the following update for their telephones.