Android’s notorious January 2024 replace is mounted and rolling out once more

Google HQ.

We’re a 3rd of the way in which by way of February, however Android’s January 2024 Google Play System replace is simply now rolling out. The now-infamous replace initially rolled out firstly of January however was pulled after it began locking customers out of their telephone’s native storage. Apparently, the replace has been mounted and is rolling again out to units. We have been capable of get it to put in this morning.

The primary time this replace went out, some units with a number of person accounts or work profiles skilled what Google described as “a number of apps crashing, screenshots not saving, and exterior storage working inconsistently.” Customers described telephones affected by the difficulty as “unusable.” Google finally posted directions for a guide repair on February 1, about two weeks after the replace first began rolling out. These directions have been difficult, although, involving a guide course of the place you needed to allow developer mode, obtain the developer instruments, plug in your telephone, and kind in the fitting command prompts to delete buggy packages manually. As a part of that February 1 submit, Google appeared to vow to launch an automatic repair sometime, nevertheless it has been 9 days now.

Google skipped the December Play System replace as a result of vacation break, so this “January” replace in February is the primary Play System replace since November. Play System updates, if you happen to aren’t conscious, are a reasonably new Android replace format that’s separate from the OS-level system and safety updates. Google created a brand new, super-privileged code bundle referred to as an APEX Module that may home core system elements just like the Android RunTime or media subsystem. Google distributes these by way of the Play Retailer, permitting it to replace core Android elements straight with no need third-party producers to do any work. It sounds nice on paper, offered the updates work.

The replace was the second time in 4 months that an automated Android replace broke some Pixel telephones (for the file, one was a full OS replace, the opposite was a Play System replace). Each points resulted in downtimes measured in weeks and “fixes” that demanded both developer-level command line work from novice customers or brought on knowledge loss. Google’s observe file these final 4 months suggests 1) it does not have a dependable rollback technique for buggy updates, 2) it does not have ample testing for its updates, and three) it may’t shortly cease or restore injury brought on by buggy updates. These points all make updating a Pixel telephone a scary proposition currently.

Leave a Comment