yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] Lexord:
Oh okay, I don't live here in US, so I really hope the first one i get is perfect :\ Or even better, i hope this is software related (which i highly doubt) .. thanks
[Nexus 7 (2013) Q&A] l1nuxguy:
Just really, really sensitive keyboard for me

Actually, funny thing is that I did/do *not* have a screen protector on the other Android device (a Galaxy S3) and it *does* have way, *way* lower sensitivity. I know it makes no sense and I'm sure is totally unrelated, but I did find that doing a clear dalvik cache when I was having the jumpy multi-touch problem went away (fingers crossed).

I'd love to think it's a software issue too, but really no idea other than how it sounds like at least some reports of the touch getting worse after one of the software updates. Right now I think it's just the keyboard seems really really sensitive. I really, really don't want to have to go risk exchanges after the horror stories from others.
[Nexus 7 (2013) Q&A] husker91:
Flashing a ROM won't fix the problem until a fix is found (if there is indeed a fix)... No one can be sure of what the cause is. So many people with the same problem is usually indicative of a software issue, unless Asus has had major manufacturing issues.
[Nexus 7 (2013) Q&A] aimfire72:
I find it hard to believe they had no clue that there was gonna a problem. If so, they must've only tested one device for a few hours, lol.

Sent from my Nexus 4
[Nexus 7 (2013) Q&A] DowntownJeffBrown:
Agreed

>^.^< sent from meow n7 v2
[Nexus 7 (2013) Q&A] slyr114:
ive read that most people have this issue after updating, i was wondering if there was a way to downgrade before the OTA without having had made a backup?
[Nexus 7 (2013) Q&A] LoopDoGG79:
I tried YAMTT, the app that was used in the video demonstrating the problem on my S3 and note 10.1. No issues what's so ever. Get the app yourself and try on another phone or tablet. Most likely, it won't have any issues.
[Nexus 7 (2013) Q&A] highfigh:
I would agree that it is a grounding issue not software. If I lay the n7 down and tap with one finger there are certain spots on the screen that refuse to register. But if I touch the metal inside the USB port with my other hand all taps register.

Makes me wonder if it could be fixed with some thin wire leads inside the shell? One to some ground, other end tied into ground on screen. Anyone brave enough to try?
[Nexus 7 (2013) Q&A] cyberprodigy:
It's obviously repairable via software because the issues only arise after applying the software update right out of the box.

Just be patient, there will be a fix eventually.
[Nexus 7 (2013) Q&A] wintermute000:
Not to mention (at least on mine) a reboot will make things great for an undetermined amount of time .e.g last night it suddenly manifested even with single swipes not registering, rebooted, up to 5 minutes ago absolutely perfect (when held) can't even reproduce the crossing axis issue and even when placed flat on a desk its all but unnoticeable unless you're really trying to mess it up
[Nexus 7 (2013) Q&A] highfigh:
Yeah I hope so! Heard some saying the kernel controls screen voltage. If so why can't it be changed to test? Wonder if a kernel dev could verify this? Actually I'll go ask one.
[Nexus 7 (2013) Q&A] bckrupps:
my second one was great out of the box and even after flashing pa. a few days later which was today it started going nuts again so I took it back and got the note 8 on sale. I must say the screen on the note 8 is really nice and the extra inch makes a huge difference. im not a samsung guy far from it but its a nice tablet. I tried twice and my mom loves her original nexus tablet but honestly I got tired of fighting the screen all the time I guess. I hope it works out for everyone cause its a nice tablet otherwise
[Nexus 7 (2013) Q&A] kentondb:
I, too, have noticed that a lock/unlock or a reboot will sometimes help the issue, but also does bending the tablet with my thumbs to increase connection.

So.... :confused:
[Nexus 7 (2013) Q&A] fax11:
hi, still no communication from google, it has been lasting for more than 3 weeks now...

I think I'm going to cancel my order (France).
[Nexus 7 (2013) Q&A] DowntownJeffBrown:
Yea you will be able to order from the UK soon anyways. Maybe by then we will has have an answer for those of you that are having these issues.

>^.^< sent from meow n7 v2
[Nexus 7 (2013) Q&A] phazerorg:
Except for all the people in this thread who say they have the issue even before the update. I've read and followed this whole thread and the general feeling is that if you don't have the problem at all before the update, you won't have it after. If you have it before the update (even if it's very very minor), you'll have it worse after the update... but the problem was there from the start.

People are going back and forth on whether it's hardware or software, talking about grounding and voltages and drivers and everything... but none of us are Asus engineers and we can really only speculate and make guesses (although sometimes educated guesses, from people who have background in these areas). The fact that some tablets are perfectly fine makes it seem like the hardware in others. It reminds me of the Galaxy Nexus volume button issue... which was at its root a hardware problem, but was able to be fixed through software. Maybe the software currently isn't tolerant enough of varying hardware, or maybe the hardware is broken in many. We just don't know.

The reality is that until Google or Asus make any sort of official statement, all we're doing is throwing out ideas, reporting our experiences, collecting information, and sharing our misery. All of that most definitely serves a purpose, and could lead ROM developers to coming up with their own fix, but nobody here works for Asus or Google QA, nobody here that I've seen is replacing digitizers or other related hardware, nobody is debugging drivers or recompiling them with potential fixes.

I say all this only because statements such as "obviously repairable via software" are misleading and "the issues only arise after applying the software update" is just plain incorrect.
[Nexus 7 (2013) Q&A] :
+1
[Nexus 7 (2013) Q&A] sfhub:
Actually I believe we all work for Asus and Google QA, we just aren't being paid. :)
[Nexus 7 (2013) Q&A] picachux:
On second exchange from Amazon I got one that no longer exhibits the jumpy touch. :fingers-crossed:
[Nexus 7 (2013) Q&A] Liquidretro:
Google has acknowledged the bug on their groups. Several of the android blogs have speculated that this is calibration of the digitizer and will be fixed via a software update. This is not the first time an issue like this has happened to a new device. There are several other bugs in 4.3 and I would have to expect an update pretty soon to squish most of them. I see no reason why this should cause someone to cancel an order. The hardware has a warranty for a year, if there was a massive hardware problem this wide spread (unlikely) then it would be fixed under this free of charge.
[Nexus 7 (2013) Q&A] texnnyc:
Well, I for one would like to turn on a device and have little to no problems (but no, I will never buy an Apple!) - I've waited this long and I can wait a little longer - plus, with the LG G-Pad coming out, that could give a possible alternative. But ... I would let that simmer for a month or so any release bugs get fixed.
[Nexus 7 (2013) Q&A] BESS667:
Mine works perfect, even with ten fingers at the same time
[Nexus 7 (2013) Q&A] Coronado is dead:
About to go try my 4th device :/

Decided to live-with/wait-for-fix on the multi touch and GPS issue, and this morning it boots up with a dead pixel and backlight bleed. Both were NOT there before, lol. The dead pixel is in the middle of the screen and very noticeable at all times.

4th times a charm?
[Nexus 7 (2013) Q&A] highfigh:
The nexus community is gonna get huge before long...with the market flooded with cheap open-box and refurbished units. xD
[Nexus 7 (2013) Q&A] viralbug:
I just received my 32GB N7 2013 today. At first I thought there were no problems at all.

However, after updating the firmware and more checking, I do see a little weird multi touch issue. However, it rarely happens and that too very minor. I'll see if it gets worse. I knew I shouldn't have rushed to update.
[Nexus 7 (2013) Q&A] eggman89:
Same issue here.

Nothing that I can show on video, but definitely something I can feel.
[Nexus 7 (2013) Q&A] Coronado is dead:
Well instead of exchanging mine for a 4th the guy at Staples was kind enough to let me return my Nexus 7 16GB on day 18 of the 4 day return policy.

Will wait for an update or nay news from Google. $35 in the hole for accessories right now, lol.
[Nexus 7 (2013) Q&A] JayBomb999:
That is how I'd describe my last couple attempts to find a perfect N7. It's "something I can feel".

I personally believe that most N7s have this issue, but people are just used to Android being janky. They think it's normal. If you're anything like me, you're probably extra sensitive to stuttering or the slightest erratic behavior (especially after dealing with a couple very bad N7s).

I've personally experienced iPad like fluidity on 2 pre-update N7s. Once I updated though, the herky jerky dance commenced.
[Nexus 7 (2013) Q&A] spmode:
Is it not possible to undo the update by flashing a previous ROM?
[Nexus 7 (2013) Q&A] JayBomb999:
I've heard conflicting reports, but if you can revert to a previous build, that will probably help. However...

Netflix requires the latest build to work. If you want Netflix (as I do), this is not a good work around.
[Nexus 7 (2013) Q&A] spmode:
I can only find the JSS15J image, can you link the previous image?
[Nexus 7 (2013) Q&A] Nevlever:
My first Nexus 7 (2013) had the erratic multi-touch behavior. Reverting to 66N build, rebooting, nothing had any effect except plugging it in.

Exchanged for a new one and it sometimes also has the issue. Except on this one plugging it in does not fix it. The only way I can figure to fix it is to reboot the tablet, which seems to fix it for about a day. Makes me wonder if there's two separate issues.
[Nexus 7 (2013) Q&A] JayBomb999:
Sorry. There isn't an official image for that build (as far as I know). Your best bet is to root and see if someone else in the forums has a TWRP backup for you to use. Otherwise, wait for Google and Asus to come through.
[Nexus 7 (2013) Q&A] LoopDoGG79:
I thought they released the binaries a few weeks ago?
[Nexus 7 (2013) Q&A] JayBomb999:
They did. However, they only released the latest build(JSS15J). He wants the JWR66N build.
[Nexus 7 (2013) Q&A] SubMatrix:
I just picked up a 16GB for my dad yesterday, and have yet to let it update to JSS15J. I can report that it has 0 touch issues, single or multi (even my 32gb doesn't register all single touches when laying flat on a table, unplugged).

I plan to update the 16GB to JSS15J soon and see if any touch problems show up.
[Nexus 7 (2013) Q&A] spmode:
It would probably help a lot of people if you could upload a nandroid of the 66N before you update.
[Nexus 7 (2013) Q&A] SubMatrix:
I'm pretty sure someone already posted that somewhere, I remember coming across it reading one of the threads. It might even be earlier in this thread.
[Nexus 7 (2013) Q&A] Coronado is dead:
Someone on the Google problems group is saying they just got update JSS15Q and the problem is gone. Anyone want to manually check for an update and report back (mine was returned and I am waiting for a fix).
[Nexus 7 (2013) Q&A] :
Nada

Not received the update yet after manually checking on my Nexus 7 V2; I have a feeling that this is actually rolling out because of the lack of an official response from ASUS/Google thus far.
[Nexus 7 (2013) Q&A] Coronado is dead:
Gotcha. Droid-life is reporting updates to other Nexus devices rolling out as well.
[Nexus 7 (2013) Q&A] :
A fellow DLer! I thought that was N4 specific, and that was a JWR build. May as well update them all at once, I guess. :)
[Nexus 7 (2013) Q&A] Coronado is dead:
Haha, nope, sorry, just got the news form a Google search ;)

http://www.droid-life.com/2013/08/2...ta-updates-for-the-nexus-7-hspa-galaxy-nexus/
[Nexus 7 (2013) Q&A] sfhub:
If someone gets a JSS15Q update please go into /cache and grab the ota zip file BEFORE updating so you can share with the rest of us.
[Nexus 7 (2013) Q&A] milan_gondor:
Someone already got an update but facing issues with Chrome

https://code.google.com/p/chromium/issues/detail?id=276693
[Nexus 7 (2013) Q&A] :
Will do. Noob here so wouldn't have thought of that myself.
[Nexus 7 (2013) Q&A] sfhub:
Also if you'd potentially like to share please oem unlock your bootloader right now before you even get notice of an update.

It will factory reset in the process but won't affect your ability to download or use the ota.

Then if you get the ota I can help you retrieve it.
[Nexus 7 (2013) Q&A] :
Cannot retrieve it with a locked bootloader? I need to keep mine locked because if this update does not fix my problems, my N7 is getting returned.
[Nexus 7 (2013) Q&A] Coronado is dead:
Just a note: one guy said it fixed his. Another guy now says it did not fix it. So it could be nothing, don't get your hopes up.
[Nexus 7 (2013) Q&A] :
Yeah I just saw that and died a little inside... :(
[Nexus 7 (2013) Q&A] sfhub:
/cache is a restricted filesystem

You don't need to root but unlocked bootloader will give you access to /cache indirectly

It is completely reversable. All it does is set a flag. The factory wipe is what the unlock does to secure your data. The relock takes one second and doesn't involve a wipe.

If it is too much, I understand. I just have visions of people constantly pressing check for update only to find out it isn't their turn.
[Nexus 7 (2013) Q&A] :
Yeah I hate that feeling as well.

Hopefully I am not one of the first to get it and find myself making that decision.

Thanks for the insight.
[Nexus 7 (2013) Q&A] sfhub:
Just to be clear you would ideally unlock your bootloader prior to getting the update, as the factory wipe that happens as part of unlock would wipe your cache and the ota update you just downloaded and it isn't clear whether you'd get to redownload.

If one unlocks now before they download the update then they will be all set up to pull the ota once it is downloaded since they won't need a factory wipe for the unlocking.

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

Other guy took it back and now says the update does improve but doesn't completely fix.
[Nexus 7 (2013) Q&A] :
Hmm okay... Is there any way to unlock the BL and then restore back to a locked BL with the exact same app placement, apps, data, settings, etc. as what I have now?
[Nexus 7 (2013) Q&A] sfhub:
There is a procedure to do an adb backup but i've never tried it with restoring after bootloader unlock so couldn't say for sure whether it would work in this situation.
[Nexus 7 (2013) Q&A] :
Okay, thanks for the suggestion. I'll be sure to look into it ASAP.
[Nexus 7 (2013) Q&A] sfhub:
3rd report that JSS15Q alleviates multi-touch issues.

Also JSS15J appears to be pulled. Folks on JWR66N who used to have notification for update no longer have it.
[Nexus 7 (2013) Q&A] :
(Update): Official word from Google that this update should fix multitouch issues:

https://productforums.google.com/forum/m/#!category-topic/mobile/other-google-products/W0Hfkq8hf-c

paulw (Google staff):

"Hi everyone,

As a couple of you have mentioned, there's a new system update that's started rolling out for your Nexus 7s. This update does address the touchscreen issues discussed in this thread. If you're one of the people experiencing touchscreen issues, please let us know how it's going after you've received and installed the update."
[Nexus 7 (2013) Q&A] SubMatrix:
Can you get notices of OTA updates if you're running a custom recovery? My impression was you couldn't.
[Nexus 7 (2013) Q&A] cowabunga:
Don't think you get notification on the updates unless you are on stock. At the minimum I know you cannot install the update if you don't have stock recovery.
[Nexus 7 (2013) Q&A] sfhub:
For the notifications, recovery doesn't matter, only the rom. Stock rom will definitely notify, custom roms, it depends, but obviously the ota would only install successfully over stock.

Installation of ota is best done using stock recovery, but I believe JSS15J was successfully installed using twrp. Obviously you cannot modify or remove the stock rom files or there is a high probability the ota will fail.

If you root using SuperSU the ota technically shouldn't fail but it does because of a flag SuperSU sets on a file used to support ota survival mode. There is a simple fix for that in one of my posts which I'll try looking up.

Here is the fix to allow ota updates to work with root, it was tested on rooted JWR66N ota updating to JSS15J

http://xdaforums.com/showthread.php?p=44597339#post44597339
[Nexus 7 (2013) Q&A] LoopDoGG79:
So fellas, has JSS15Q start rolling out yet?
[Nexus 7 (2013) Q&A] wintermute000:
Yeah (or the users in the google forums are goog employees lol)

need the OTA stat! Hoping someone puts the zip up on XDA!
[Nexus 7 (2013) Q&A] :
Nothing in Canada yet
[Nexus 7 (2013) Q&A] g3omanser:
Will the new update be available for JWR66N or only for JSS15Q?
[Nexus 7 (2013) Q&A] :
The new update is JSS15Q and should be for everyone its an OTA update.
[Nexus 7 (2013) Q&A] g3omanser:
Cool! I hope it'll fix all the bugs esp. the multi touch. It drove me crazy the second day.

PS srry if it's a dumb question. I'm a noob :P
[Nexus 7 (2013) Q&A] wintermute000:
It had better, I blew away my custom ROM/kernel and did a full wipe/restore to stock just for it :p

getting withdrawal without root lol

interestingly after I unlocked the BL the first time, my multitouch has definitely worsened from stock. Yet now after a full factory restore and wipe its still noticeably worse than out of hte box, yet I'm running the same goddamned build, no root, stock recovery, only difference is BL unlocked.
[Nexus 7 (2013) Q&A] eyecon82:
see..told you guys it was a software issue

http://androidcommunity.com/nexus-7-software-update-jss15q-brings-a-fix-for-multitouch-20130822/
[Nexus 7 (2013) Q&A] trvbone:
Anyone get update yet
[Nexus 7 (2013) Q&A] :
I'm glad if the new firmware fix it however don't jump to conclusion so quickly lets see how many people it helps first...since no reports are coming in of anyone getting this update yet except the two that posted on the google site.
[Nexus 7 (2013) Q&A] :
If anyone receives the OTA and has an unlocked bootloader, please contact sfhub immediately so he can help you retrieve and share the ZIP file for all to use. DO NOT install the update if you have an unlocked bootloader, as after installation the ZIP file cannot be grabbed.

If this file becomes available, there are a couple options as to how you can flash it. Hit up this link and ignore everything except the instructions at the end of the post: http://www.droid-life.com/2013/08/21/download-android-4-3-jwr66y-ota-updates-for-the-nexus-7-hspa-galaxy-nexus/#more-117742
[Nexus 7 (2013) Q&A] Tony_YYZ:
I've been trying all day to get the OTA notification. I'm running JWR66N at the moment. Will post up if I get the notice.
[Nexus 7 (2013) Q&A] :
Please do! I'm in the US with a 32GB model and no luck so far...
[Nexus 7 (2013) Q&A] trvbone:
Same here no luck yet
[Nexus 7 (2013) Q&A] :
Do you have the 32?

I wonder how they are selecting devices to receive the update, usually seems like the people who have received the update have nothing in common.
[Nexus 7 (2013) Q&A] trvbone:
Yes I do
[Nexus 7 (2013) Q&A] :
So I guess we are in the same boat.

sfhub, do you have any intel on how Google conducts their rolling OTA rollouts? I have a feeling they just have a program randomly giving people access to the OTA.
[Nexus 7 (2013) Q&A] DowntownJeffBrown:
I have a 16gb and still haven't gotten it.

>^.^< Sent from meow HTC One which is like catnip to me atm
[Nexus 7 (2013) Q&A] :
Thanks. This update is just moving way too slow for me! :(
[Nexus 7 (2013) Q&A] DowntownJeffBrown:
I agree bro. I'm thinking it's just random. I know that if I get it I will be posting it for u all.

>^.^< Sent from meow HTC One which is like catnip to me atm
[Nexus 7 (2013) Q&A] :
Yay!

Hopefully someone willing to share it receives it soon.

In other news, the JSS15Q factory image has been posted:

https://developers.google.com/android/nexus/images#razor
[Nexus 7 (2013) Q&A] DowntownJeffBrown:
Yea I'm pretty sure that got posted lady night. You could flash that if you wanted but you will lose all you data.

>^.^< Sent from meow HTC One which is like catnip to me atm
[Nexus 7 (2013) Q&A] :
No, I checked earlier today and it wasn't there.

Yeah, I'm still waiting on someone to share the OTA.
[Nexus 7 (2013) Q&A] Nevlever:
You don't lose your data if you just take the '-w' out of the 'fastboot update' command in the bat file.
[Nexus 7 (2013) Q&A] DowntownJeffBrown:
Ah OK I misread a post earlier today then. I just got home and checked mine and still no ota. I don't have the multi touch issues so it's not really a huge deal to me but I would like to get it so I can post it for you guys.

>^.^< sent from meow n7 v2
[Nexus 7 (2013) Q&A] :
We've got a nice guy here! :P

I have both multitouch and GPS issues.
[Nexus 7 (2013) Q&A] A.Abdalgalil:
Official factory image is now available at Google Developers site.
[Nexus 7 (2013) Q&A] highfigh:
Post 659 beat ya to it ;)

I'm going to flash back to stock and see if I can get it. Maybe they roll it out by city/state and Ohio is first on the list :sly:

Anyways the more unlocked n7's waiting the quicker we can get it up!
[Nexus 7 (2013) Q&A] :
You took the words from my mouth. :)

Except they should start in CA, cause the west coast is the best coast.

It's not like the rollout is random or anything :P
[Nexus 7 (2013) Q&A] sfhub:
The link for the factory image was updated in the last 2hrs, have a window opened on it and checked periodically
[Nexus 7 (2013) Q&A] phazerorg:
I just installed the new factory images, wiping in the process to start completely fresh.

It has NOT resolved the touch issues for me, at all. There is no noticeable difference at all as far as touch goes. YAMTT still shows touches being missed and extra touches appearing when I'm using the tablet flat on a table. I haven't done much other testing besides that yet, but so far for me the update does nothing for this problem.
[Nexus 7 (2013) Q&A] Coronado is dead:
This is disappointing to hear. Please report this on the Google group page people have been posting so that Google knows as well.
[Nexus 7 (2013) Q&A] wintermute000:
It partially works, apparently some apps can exclude themselves from adb backup and do so, when I restored I got maybe 3/4 of my apps back. Better than nothing.

ALso apparently some apps can bork the restore but it didn't happen to me/my set of apps.

---------- Post added at 09:00 AM ---------- Previous post was at 08:59 AM ----------

It partially works, apparently some apps can exclude themselves from adb backup and do so, when I restored I got maybe 3/4 of my apps back. Better than nothing.

ALso apparently some apps can brk the restore but it didn't happen to me/my set of apps.

This is one of the biggest failings in stock android IMO
[Nexus 7 (2013) Q&A] phazerorg:
Done, and I included a few details I've tested since posting here. A guy right before me says the update fixed the touch problems for him... wish I had his luck :(
[Nexus 7 (2013) Q&A] :
Yeah, using Helium to back up right now and it flat out told me that a couple of my apps will not be backed up.

Sucks for those apps.

---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------

How bad were your touch problems before the update?