If you belong to the early Jelly Bean 4.3 adopters and is now dealing with funky Nexus 4 behaviours, help appears to be on the way, at least for users located in the United States.
U.S. telco T-Mobile will soon dispatch a Nexus 4 firmware update that will alter the handset's current build of JWR66V to JWR66Y, Gotta Be Mobile said in a report. However, the 1.8MB update file is too light to be considered a major jump from what Google has unleashed in late July 2013.
T-Mobile has explicitly described as the file as security patch, the same report said, adding that Nexus 4 on other networks as well as the unlocked versions will eventually chew in the corrective measure. No time frame was given though on when exactly the update process will go live.
That would be the good news.
The bad news is, Nexus 4 users should not expect any dramatic Android changes. In short, the file is not the Jelly Bean 4.3.1 that Android watchers have been waiting for since the latest Jelly Bean caused multiple erratic functions on the 2012 Nexus edition, per reports by numerous device owners.
Reports have been widespread that the smartphone suffers boot screen freezes, delayed interface reactions, shorter battery life and pairing issued with Bluetooth accessories. All these glitches will not be solved by the T-Mobile-authored update, the GM report said.
Most likely, these hiccups, also reportedly plaguing the newly-minted Nexus 7 2013 build, will only disappear by the time the next Jelly Bean hit the update pipeline, it arrival unfortunately remains a mystery.
Google has yet to officially comment on the matter.
Now the bigger question is: Will Google send out a quick cure or will it simply advance the Key Lime Pie debut, which reports said is programmed to debut on early October via the rumoured Nexus 5 launch?
On all these concerns, nothing is definite yet. In fact, Google has routinely refused to provide details on when KLP is coming out or will it actually be released this year. Also, the Nexus 5 builder remains under wraps though analysts believe that the contest for the project has been narrowed down to LG and Motorola.
LG is a strong contender due to its previous works on the Nexus 4 while Motorola has an edge owing to Google's ownership of the company.
If ever, LG is supposed to pattern the Nexus 5 on either the LG G2 or the LG Optimus L II. Motorola, on the other hand, is likely using its 2013 flagship, the Jelly Bean 4.2.2-powered Moto X, as the base model for its take on the Nexus 4 successor.
To contact the editor, e-mail: