Nexus 7 (2013) JSS15Q OTA Update Rolling Out - Fixes GPS/GNSS and Multitouch Issuesby Brian Klug on August 22, 2013 5:46 PM EST
We published the full Nexus 7 (2013) review today, and liked it so much we gave it our Editors Choice Silver award. I'm a huge fan of the updated Nexus 7 and have been using it since launch without many issues, but a number of users ran into a few bugs that are being fixed today with an OTA update and build number JSS15Q. We've confirmed with Google that the JSS15Q resolves these issues and is slowly rolling out to all users. The bugs previously affected both GNSS (GPS+GLONASS) dropping out intermittently which Qualcomm provides through the APQ8064-1AA SoC, and some issues with touch recognition.
Although GPS and GNSS constellation lock would happen fast and signals were fine (Qualcomm's GNSS remains arguably best in class), the fix would periodically and randomly disappear and not come back until after a restart. I have to admit I ran into this particular bug once while testing the Nexus 7 for my initial mini review piece, but didn't think much of it since it didn't happen in subsequent testing. This issue is resolved with the update, and some quick testing with GNSS reveals no dropout issues.
The other issue was a touch controller related bug which affected taps along a shared axis causing the taps to disappear and then reappear and some other issues. I didn't see this issue on my Nexus 7, and neither did Anand, possibly due in part to multiple touch controller sourcing, but it also is fixed as of the update.
Users can either wait for the OTA update to hit their devices, or re-flash with the full factory image which Google has also updated via the link below.
Source: Factory Images for Nexus Devices
Post Your CommentPlease log in or sign up to comment.
View All Comments
noeldillabough - Thursday, August 22, 2013 - linkVery nice to see they're updating, I'll wait for the OTA.
dyc4ha - Thursday, August 22, 2013 - linkAn undeniable advantage of a Nexus device, timely updates
wintermute000 - Friday, August 23, 2013 - linkBzzzt wrong, this fixes glaring issues that should have been caught in round 1 of QA.... goog really dropped the ball on this one.
Nice to have a fix (yes mine's affected by the multitouch bug) but really sloppy and hurting sales/rep.
Orwelian84 - Friday, August 23, 2013 - linkPlease name one company that has consistently flawless releases with no bugs? I won't both holding my breath, because the fact of the matter is that bugs always creep in and the mark of a great company is its ability to rapidly respond to its customers, which is what Google has done. In less than 30 days they fixed this software problem and are rolling out to its customers a fix.
Their stock hasn't suffered and the tech punditsphere isn't lambasting them so I am not sure where you came up with the "hurting sales/rep" line. Sounds like you are butthurt because your tablet suffered from a bug. I am sure Google is sorry that this happened to you, but as I said they have rolled out a fix.
If it had been a Samsung tablet you would be waiting for a fix five months from now and if it was an Apple bug first they would have denied it, then issued a fix complete with a snarky remark about "not holding it right".
Transmitthis14 - Friday, August 23, 2013 - linkOrwelian84 - In less than 30 days they fixed this software problem and are rolling out to its customers a fix.
Here I and all the rest of the other 2012 Nexus 7 owners are, with this multi touch issue,
We have been trying everything, posting on Google's forums as well as androids, talking to support and even replacing products for OVER a year, to get this issue resolved or even acknowledged.
It took the media interest and possible loss of sales of a "new tablet" for them to put resources into action to fix the issue.
I love my Nexus7 (Despite the ongoing Bluetooth audio connection issues (which you won't hear about unless someone with a 2013 one has media clout)) and I expect bugs, but you really should understand the time frames involved before making a comment about 30day fix's
Orwelian84 - Friday, August 23, 2013 - linkThis post is about the 2013 version, and so far as I know, and all the reviews I have read, the issues you are describing with the 2012 version were much less widespread...e.g normal problems in the supply chain and not a specific bug in a significant proportion of the tablets shipped.
I highly doubt the "rest of" the 2012 owners had the problems you are describing because there would have been media coverage and the 2012 tablet was almost universally acclaimed as the best tablet money could buy.
And again I was posting a comment on a thread about an update to a brand new tablet, not last years version. I made no claims about the 2012 version and again so far as I know your experience with it is in no way generalizable to the whole.
misterv - Thursday, September 5, 2013 - linkFirst of all, you assumed the fix even worked (many are still reporting the issue despite the "fix" so they have yet to actually fix it in a timely manner). Second of all, Consumer Reports has said not to buy the Nexus 7 2013 tablet until they've addressed the multitude of issues with the 2013 version (again, which they haven't done yet fully) so I'm not sure how you can claim that there's been no reputation damage whatsoever. The Verge also has an article that not only outlines all the bugs of the current release but also of the 2012 release, many of them still unfixed as Transmitthis states. And I disagree with you. It's perfectly reasonable to question a company's commitment to support by their behavior with past products. It was YOU who made the generalized statement, "the mark of a great company is its ability to rapidly respond to its customers, which is what Google has done." He was bringing up a perfectly valid point, that just because they addressed an issue this time, doesn't make the company wonderful based on their past behavior...If someone slapped you every day last week but today they bought you an ice cream sandwich, it doesn't make them a nice guy either...if google releases one timely fix but fails to address numerous past problems, it doesn't make them a great company.
Then you summarily discount that his claims that there are issues with the original nexus 7 and even a cursory search on google itself brings up quite a number of people with complaints about the 2012 nexus 7.
But the most egregious thing you said is that the 2012 issues were less widespread and therefore normal problems in the supply chain. You have no basis or evidence to support that claim other than your survey of, what I'm sure, was the entire internet.
While I understand that there are always a few defective products that slip by, robust QC is supposed to catch a good deal of them. Something so basic as a number of consumers complaining that the device would not reliably turning on, or the casing coming loose (2012 version) or a touchscreen not correctly registering touches on a large percentage of devices (2013) is a QC failure, plain and simple. If you want to apologize for Google and Asus go right ahead, but basic functionality should be robustly tested and wasn't two devices in a row.
And look around more closely, neither then nor now is it just one or two people with the complaints.
Azurael - Friday, August 23, 2013 - linkQuite. I own many Android devices of various shapes and sizes and not one of them would be free from major bugs were it not for the hobbyist development community. I don't know of any modern, complex piece of technology that's released sans-bugs these days. At least Google not only bother to fix them, but do so in a timely manner.
Rob Sims - Monday, August 26, 2013 - linkThe "not holding it right" comment was based on rumour, not fact, from the late Steve Jobs in June 2010 (that's right, over 3 years ago). Despite the story of the supposed email/tweet/text message, no-one was ever able to find evidence it was ever said and most concluded later that it was probably fabricated for whatever reason at the time. Using such remarks invalidates much of what you might sensibly have said, whether that was your intention or not!
Impulses - Friday, August 23, 2013 - linkNice, I haven't even opened mine cause I've been away... Guess I might try updating it after rooted to see if root access survives (I'm not replacing the bootloader, just loading TWRP thru ADB after unlocking, precisely because I'd rather get Google's OTAs directly/immediately).