|
Deobulakenyo apparently isn't the only one is running into issues with 4.32...
My Libra 2 has been running absolutely fine on 4.30, but now that I wanted to update to 4.32, it has been behaving quite oddly. When it's on 4.30, it detects that an update is available, downloads it and then asks whether to update immediately or update later. Either way, something about the update seems to go wrong - after a couple of 'three-dot screens', it boots back up and is still on 4.30. However, it won't connect to a PC via USB again, and nothing short of a factory reset will get it to do that again. Which doesn't stop it from happily announcing that an update is available, however...
I'm wondering - what are the odds of both of our devices having the same defect that only shows up in one specific update (since 4.28 -> 4.30 goes without a hitch)? Could it maybe be have something to do with affiliate or regional things rather than a hardware fault?
|