yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] viralbug:
I flashed the Google firmware JSS15Q. Unfortunately, I still have the same multi touch issue. :( However, my issue is much lesser compared to what many of the users here are facing, even on JSS15J. I don't have any single touch problems. I only see slight jittering when trying to bring 2 touches along the same axis.

EDIT: I seem to have single touch issues as well when laid flat on a surface. :/
[Nexus 7 (2013) General] sfhub:
Power+VolUp until you see Google, then let go

Fallen android, press/hold Power, then press/release VolUp, then release Power

Power+VolDown will get you bootloader screen from which you can also enter recovery
[Nexus 7 (2013) General] ch0mch0m:
I am on JSS15J, rooted, stock rom. The only thing I've added is the APM (http://xdaforums.com/showthread.php?t=2383059 ).
[Nexus 7 (2013) General] sfhub:
Most likely apm made the change, check the apm update.zip and you should see what was modified

It is probably easier to just flash the factory image than figure out how to get everything set up for the ota by reverting to files you may no longer have
[Nexus 7 (2013) General] sfhub:
Boot into bootloader using Power+VolDown

fastboot flash boot boot.img

You can find the boot.img in the image zip file in the JSS15J factory restore

You can even use the JSS15Q boot.img if you can't find JSS15J
[Nexus 7 (2013) General] boykomac:
Thanks mate, flashed stock boot.img and updated to 15Q successfully :)
[Nexus 7 (2013) General] timrock:
so after flashing the update, i will lose root. yes? so how do i go about getting it back a) without using a pc and b) without losing the stuff i have on the device? Anyone?
[Nexus 7 (2013) General] sfhub:
If you use the factory image you root will be overwritten. If you use the ota, your root will be disabled. There are many guides to put root back, but I don't know of any which do not involve a pc if you are on stock recovery

The ota will not cause you to lose data and you can modify the factory image restore to not wipe data.
[Nexus 7 (2013) General] timrock:
thank you. so is there a non pc method to put root back if am on TWRP, which i plan to install after i get the OTA
[Nexus 7 (2013) General] sfhub:
Update #8:

Factory JSS15Q repackaged as TWRP flashable update.zip available

(these are rooted and come with unsecured boot, so are not pure stock, but may be what you are looking for)

http://xdaforums.com/showthread.php?t=2416438
[Nexus 7 (2013) General] boykomac:
Well the new update does not fix my touchscreen - still missing to register single touches now and then when flat and unplugged, pinch to zoom sometimes generates ghost touch (happens rarely but it still happens)
[Nexus 7 (2013) General] sfhub:
Yes, twrp will automatically ask you if you want to root when you exit

Or if you want latest SuperSU place the SuperSU update.zip on your virtual sdcardband boot to twrp and choose install
[Nexus 7 (2013) General] boykomac:
GPS looks perfectly fine :)
[Nexus 7 (2013) General] Lookatthemonkeys:
Thanks for this. I really wasnt sure about all the other methods, but I guess because I had not received the update on my Nexus yet this was my only option. I started to put stock recovery back on and tried to adb sideload but it didnt work. Luckily I just re-flashed twrp and then installed the zip, and also superSU and the SuperSU-ota for next time. Thanks.
[Nexus 7 (2013) General] Zylograth:
JWR66N -> JSS15Q

http://android.clients.google.com/p....signed-razor-JSS15Q-from-JWR66N.35d9b692.zip
[Nexus 7 (2013) General] aerdely:
Question, is the ota still in initial implementing stage or is it all devices yet. See couple people have gotten it but not sure if every one has. Just asking as I haven't yet. Thanks.
[Nexus 7 (2013) General] The Holocron:
I have not received it at my device as of yet. I suspect this is being rolled out--and this is a pure guess on my part--based on hardware revision. That's likely coded in the serial/device number.

I had a 16GB N7 that flaked out on me. I returned it and got a 32GB N7 to replace it and haven't had a problem. My 14-day return period just passed. When going to the bootloader, I notice the "Hardware: rev_e".

again, just a guess...
[Nexus 7 (2013) General] aerdely:
Yea was just wondering. Just got mine last week, haven't checked the hardware revision but as of now that haven't experience any issues as others have reported so that could be the case. We'll see If we get it in next couple days I guess but no biggie other wise if it only fixes devices with the issues we've seen reported. Thanks.

You were right about that but also as I don't know if it matter but mine is also rev_e but 16gb. Just checked it, gonna have to wait and see but other wise no hurry as like said only seems to help the devices with the issues.
[Nexus 7 (2013) General] milliman:
I received my up update an hour ago and promptly installed it. My tablet is still very responsive and the multi-touch issues are gone.
[Nexus 7 (2013) General] SubMatrix:
Personally, I'm still waiting to see video proof of someone who had single touch problems when flat on a table unplugged no longer have any issues under JSS15Q.
[Nexus 7 (2013) General] Pulga89:
Issues gone!

Well, I have a 32GB Nexus 7 (2013) rooted and with unlocked bootloader, and the multi-touch issue was unbearable on stock Android. I switched to CyanogenMod 10.2, but it was even worse. So I decided to take the plunge and followed this guide to restore everything from the newest factory image (JSS15Q), and IT WORKED! All multi-touch and sluggishness issues are completely gone and I'm rooted again! I wiped everything and started with a clean factory image. Most people who have problems with this update are probably doing a dirty installation or leaving some files behind.

The guide is great and fairly easy to follow. I'm very new to Android in general, but I've been tinkering with computers and devices for over 12 years; So if I could do it, I think most of you can :D.
[Nexus 7 (2013) General] Geese1:
I'm getting an error message when sideloading the update package:

E:signature verification failed

Anyone know what this is and how to fix it? I thought at first it had to do with having the SuperSU on the device, but I ran the fix listed in this thread and I'm still getting the error.
[Nexus 7 (2013) General] ejkeebler:
na

me
[Nexus 7 (2013) General] foodude1:
Just wondering, I've been watching impatiently for a few days now and haven't received the update. My OG nexus 7 got them almost immediately after I learned about them. How long am I going to have to wait!!
[Nexus 7 (2013) General] odobo:
did the same and its working fine on my nexus 7 :cyclops:

just tested GPS and it was staying strong for the whole hour
[Nexus 7 (2013) General] stealthj:
are u using CWM? isng there an option to disable signiture verification?
[Nexus 7 (2013) General] lespaulman67:
Well everyone its 6:25 pm in IL. and I received the new update from the JWR66N. Guess what I have tons of keys not registering and double hitting on the keyboard.

This is Not good at all.Now what guys. I'm typing and my screen disappears.My GPS is working now.

I don't think this update is for the screen problem at all.

I will do a video later on this. Same problem as all my other ones I had.
[Nexus 7 (2013) General] Geese1:
No, I'm using the stock recovery as that's what most people recommend for OTA updates.
[Nexus 7 (2013) General] thenrik:
Hi:

My experience exactly. I got the Nexus 7 2012 yesterday but no love for my Nexus 7 2013. Who knows how Google rolls out updates--region, serial number, tarrot cards, the I-Ching??? Anyway, after reading about so many people getting the update, I was starting to wonder if maybe Google didn't like my pajamas or I forgot to use Brill Cream.. I read this post, from another forum, this morning and felt a little better after seeing folks east, west, north, south, international--all sans updates. The operational word is rolling out slowly.

Like it or not, there's nothing to do but wait:

androidforums.com/nexus-7/757234-still-waiting-update-4-3-a.html#post6088018

Tom
[Nexus 7 (2013) General] sfhub:
Thanks, updated first post, credit given
[Nexus 7 (2013) General] sfhub:
It usually means something changed or got corrupted in the ota update.zip file.

Do you have a virus checker running or anything that might affect downloaded zips?

Perhaps try redownloading?
[Nexus 7 (2013) General] church:
http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
[Nexus 7 (2013) General] maopr16:
http://xdaforums.com/showthread.php?t=241643
[Nexus 7 (2013) General] Geese1:
Just Microsoft Security Essentials, but I'll try redownloading and see if that fixes the issue.

Just had to update my wife's as she was stuck on JWR66N (used the fix that I found on the forums here) and as soon as I did that she got the OTA from Google to download JSS15Q. So now she's running the latest build while I'm still struggling here. :(

[Edit] Just tried it and still no luck. I even downloaded a different JSS15Q update file from another thread on the board here, but that one didn't work either.
[Nexus 7 (2013) General] maopr16:
http://xdaforums.com/showthread.php?t=2416438 sorry about the previous mis-paste
[Nexus 7 (2013) General] isketerol:
Success update with TWRP adb sideload

This ground has already been covered, I am sure, so this is more a confirmation than a revelation.

Was on TWRP with SuperSu

Grabbed the OTA update zipfile

Backedp using Titanium and adb backup methods just in case

Removed root with full unroot in SuperSu

Ran adb sideload using TWRP

Rebooted fine into the system

Back to fastboot, reloaded TWRP

Reinstalled SuperSU

Back to rooted tablet with the latest build. No issues.

By the eway, tablet is encrypted as well. No issues there.

Iskie
[Nexus 7 (2013) General] rhinosaurus:
Two tablets in my house. Within 1 hour of getting 15J both tablets suffered reboots for no reason. Mine had 2. Hope this isn't a recurring problem.
[Nexus 7 (2013) General] TBon68:
JSS15Q update

After doing "adb sideload JSS15Q.zip" I received {set_perm: some changes failed, E: Error in /tmp/update.zip (Status 7) Installation aborted.} Need some assistance on how to proceed. Thanks,
[Nexus 7 (2013) General] church:
It has something to do with supersu changing permissions that the update can't change. There is a fix for the supersu issue but all I did was follow

http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/

I'm stock but rooted and this helped me get on jss15q from jss15j without losing user data
[Nexus 7 (2013) General] sfhub:
Flash UPDATE-SuperSU-ota.zip from this post:

http://xdaforums.com/showthread.php?p=44597339#post44597339

Then redo the adb sideload.

You actually already have 98% of JSS15Q flashed but the ROM will still say JSS15J.
[Nexus 7 (2013) General] TBon68:
Thanks, I will give that a try and feel a little bit better that it's not a big issue.
[Nexus 7 (2013) General] wakeboredb:
Has anyone with supersu pro that took the ota tried the protect root option?
[Nexus 7 (2013) General] sfhub:
Don't know what changed in these modules but they got patches.

Folks can concentrate on seeing if there are any changes in these areas vs JSS15J

system/app/FaceLock*

system/app/Settings*

system/bin/sensors.qcom

system/framework/core*

system/framework/ext*

system/framework/framework*

system/framework/framework-res*

system/framework/services*

system/lib/hw/nfc_nci.flo.so

system/lib/libchromium_net.so

system/lib/libfacelock_jni.so

system/lib/libLLVM.so

system/lib/libmdnssd.so

system/lib/libnfc_nci_jni.so

system/lib/libnfc-nci.so

system/lib/libpatts_engine_jni_api.so

system/lib/libsensor1.so

system/lib/libstagefright_soft_aacdec.so

system/lib/libstagefright_soft_aacenc.so

system/lib/libwebcore.so

system/lib/libwebrtc_audio_coding.so

system/lib/libwebrtc_audio_preprocessing.so

system/vendor/firmware/gss*

system/vendor/lib/mediadrm/libwvdrmengine.so

system/vendor/lib/libmmcamera2_iface_mdules.so

system/vendor/lib/libmmcamera2_imglib_modules.so

system/vendor/lib/libmmcamera2_isp_modules.so

system/vendor/lib/libmmcamera2_sensor_modules.so

system/vendor/lib/libmmcamera2_stats_modules.so

system/vendor/lib/liboemcamera.so​
[Nexus 7 (2013) General] angieri918:
Will there be a much easier way to do this soon? Like just taking it and flagging in recovery or will I need to try and learn how to do this? I would like to learn but am really strapped for free time here lately
[Nexus 7 (2013) General] wintermute000:
For all those with root.... why faff around?

- Titanium backup and copy to PC

- Flash factory JSS15Q image

- re-flash TWRP

- re-root and reinstall Titanium

- Copy Titanium backup back and restore

Foolproof
[Nexus 7 (2013) General] reggie14:
It sounds like I'm not the first person to say this, but I'm having trouble installing the JSS15J -> JSS15Q update within TWRP. I'm rooted with SuperSU, and I applied the OTA fix as suggested in Update 3. When I try to install the update zip, it fails with the message:

assert failed:apply_patch_check("/system/framework/android.policy.jar", "<some hex>
E:Error executing updater binary in zip '/sdcard/update.zip'
Error flashing zip '/sdcard/update.zip'

I just want to keep it simple. I don't want to reflash the stock recovery if I don't have to, and I certainly don't want to flash a factory image wiping user data. If I hose something up I'll just restore a nandroid backup and take it from there

Because a backup+clean flash+restore takes a long time. I'd rather avoid it. Most of it is just backing up and restoring the gigabytes of apps I have. It doesn't help that at least one app isn't properly backed up by Titanium Backup (PvZ). I have to restore that one by hand.
[Nexus 7 (2013) General] sfhub:
Did you install APM or some other modification of the ROM through an update.zip you ran in TWRP?

The install is complaining that android.policy.jar has been modified from what it expected to see.
[Nexus 7 (2013) General] reggie14:
Ahhh, yep, actually I did. I installed APM. I completely forgot that was a mod until you said it. Thanks for reminding me. At the time I didn't realize that would create problems with OTAs.

What are my options at this point? I really, really hate doing clean flashes, since reinstalling and restoring apps takes so long. Obviously if I have to do it I can, but even then I'd like to figure out how to avoid this in the future. I like APM, but I'd be willing to live without it if that's what it takes to make updates easier.
[Nexus 7 (2013) General] Melodycd:
So, after many hours testing, I still have touchscreen issues. With one or two fingers, on a table or in hands. Jss15q didn't helpe at all. But I made a deal with Amazon, they issued me some money to return to them(I am not in US). So I solved the touchscreen issue, just my way :) Was happy to be a part of Nexus community, but was not happy to be a Nexus owner. Going to switch to something else. Going to try Note 8.0 or will wait for KFHD 2013. Thank you all for help. :thumbup::thumbup::thumbup:
[Nexus 7 (2013) General] wintermute000:
Whatever floats your boat, but you've probably spent more time researching a way around having to backup than backing up + copying. Its not like you have to sit there staring at the progress meter :)

Though I've never had a single app that Titanium didn't handle properly, so I suppose you're in a unique situation
[Nexus 7 (2013) General] RickLyons74:
You can flash the factory image without wiping data
[Nexus 7 (2013) General] sfhub:
I am testing and uploading a fix just for you. Will take about 15 minutes. I'll attach to this post.

I don't know if it does everything APM does, but I use this:

https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
[Nexus 7 (2013) General] reggie14:
OK, I saw the instructions for that earlier in this thread. I can give that a try.

So I realize at this point I'm just sounding whiny, but moving forward I just want a nice, easy, fast way to install updates. Flashing the factory image without wiping data didn't look that hard, but it is still a much more involved process than just downloading a zip and installing it in TWRP. I'm happy with stock, so I don't have any particular desire to flash a third-party ROM. Do I just need to avoid flashing mods like APM in the future?

If you know of a way to backup PvZ using Titanium, I'd love to hear it.

---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------

That's awesome. Thanks so much!
[Nexus 7 (2013) General] RickLyons74:
Once you're super comfortable with adb, it'll literally take 45 seconds....
[Nexus 7 (2013) General] sfhub:
Let me know if it works. Just install it in TWRP, then re-run the OTA install.
[Nexus 7 (2013) General] reggie14:
It worked great. Thanks! It looks like your file just overwrote the UI files that APM changed. Right?

I really appreciate your help on this.
[Nexus 7 (2013) General] sfhub:
Yes, that is all it did.
[Nexus 7 (2013) General] ScOULaris:
Just got my first random reboot after the OTA update. I was really hoping that this update would have put a stop to these.

The only modification I have made to the stock ROM is installing Koush's superuser app, but the reboot occurs while I'm doing all sorts of things completely unrelated to that.

Am I the only one experiencing this? It just started happening to me recently before the update, and now it seems as though it's here to stay.
[Nexus 7 (2013) General] sfhub:
Attached following to first post:

stock-kernel-JWR66N.zip

stock-kernel-JSS15J.zip

stock-recovery-JSS15J.zip
[Nexus 7 (2013) General] sfhub:
Based on reports, I don't think this update really did anyting to alleviate random reboots.

Either your usage pattern triggers them or it doesn't.

For me the trigger was Chrome, so I stopped using it and the reboots went away.
[Nexus 7 (2013) General] bracketologist:
After some further reading, it was mentioned in one of the threads that a screen protector may cause issues with the touchscreen's sensitivity. This makes sense, but I didn't think about it a whole lot in the beginning because I've never run into this problem before. So, in a desperate move, I took off the SP (which was an Illumishield) and...it seems to work. The single touches appear to be registering on a consistent basis, whether it's lying on a table or on a bed/sofa and not being charged or held by me. Call me a happy camper...at least at this point.
[Nexus 7 (2013) General] sss2sssss:
I'm thinking whether I should wait OTA update or just direct flash the file...
[Nexus 7 (2013) General] wilsonlam97:
It fixes Google Play music shuffling as well.
[Nexus 7 (2013) General] THS1989:
Thanks Google ! Multi touch is perfect now :)
[Nexus 7 (2013) General] lowbo*:
I just got my new nexus and right when I got it I threw a screen protector on it. I do have touch issues like others have mentioned when the tablet is laying flat. And now when trying to use Swype, I'm getting skipping and it's not playing nice. I'm on the latest 4.3 and it hasn't done anything to fix the issue... I'm getting tempted to pull the screen protector off this mofo to see if it really is causing the problem. :-\
[Nexus 7 (2013) General] jakelights:
Sad to say, multitouch issue still exist after i update, gps working well though.
[Nexus 7 (2013) General] chiikko561:
Side loading seems to have fixed my problems

Sent 4rm my Paranoid Nexus 4.3 LTE...
[Nexus 7 (2013) General] cosimoss:
The 10.7MB OTA turned up last night:(UK):
[Nexus 7 (2013) General] AZKJS:
My issue with multi touch is worse with this update. Before i would get random letters while typing but now it just hangs and pulls up sub menues like i am long pressing the keys.

I think i am going to roll back to the old version atleast spell check fixed the misstyped words.
[Nexus 7 (2013) General] Melodycd:
So many problems can defenetly tell that this is a mix of hardware and software problems. My recommendation - if you want to keep Nexus, exchange it until you get a proper working tablet. Software updates can tune touchscreen but can't fix hardware issues.
[Nexus 7 (2013) General] sfhub:
I've tested a couple of units and it is all based on slight differences in sensitivity (voltages/currents) so it is quite possible a screen protector made enough of a difference to push it over the edge.

If there is a problem area, it is almost always the top 1/3 in portrait mode. All the units I tested didn't have a screen protector on them.

There are units that have good sensitivity all over the screen. There are units that have lots of dead spots. There are units just on the fence, where if you

touch very lightly

with the large part of your finger rather than the tip

switch to your other hand

switch to your thumb or pinky

it will register taps easier

This is all with the tablet sitting on a table of course. In your hand everything registers.

It almost feels like they should give you the option to calibrate the sensitivity on your own because the variances in hardware are great enough that some people will just miss lots of taps.
[Nexus 7 (2013) General] Coronado is dead:
I have illunishields and am picking up a 32gn today. This post makes me sad, lol. Although I kind if experienced it before with the 16gb I had. $8 wasted! Maybe its because they are too thick? I hate using anything without a screen protector, they have saved my devices many times.
[Nexus 7 (2013) General] ScOULaris:
I doubt that it's app-specific. I have had reboots while using Google Play Books, while Chromecasting, while browsing in both Chrome and Firefox, and even while simply uninstalling an app.

It's completely random, and it's definitely specific to 4.3.
[Nexus 7 (2013) General] sfhub:
Simplified flashing stock images, added option to keep user data.

Nothing to edit, don't need to download sdk, just unpack the razor-jss15q addon zip file (no stock factory files are modified).

http://xdaforums.com/showthread.php?p=44888268#post44888268
[Nexus 7 (2013) General] sfhub:
I am not saying it is app specific. Quite the contrary, the core problem is in the OS because it should never be rebooting even with offending apps.

I'm saying that in everyones' usage patterns, they have their own app that "triggers" the OS issue.

For my usage pattern, that trigger app is Chrome.

I am not even talking about the tablet rebooting while using Chrome.

The reboot will be random and somewhere else. The tablet might just be idling.

I can tell there will be a reboot within an hour once Chrome tabs start hanging and generally becoming sluggish.

Stop using Chrome and the reboots go away completely.

If I use Chrome very conservatively and only have one or two tabs open, it doesn't happen either. I generally am very aggressive with tabs, having 10-12 tabs open at any time.

This is just conjecture, but the core problem could be a network issue caused by a race condition that is more easily triggered with parallel network activity.

Separately I believe there are units that have a pure hardware problem. I tested one unit where the camera app would always crash within seconds of starting on JWR66N. This unit would crash no matter what you did, with the exact same image as the other unit by its side, running the same exact apps.

IMO the pure hardware problem affects fewer people, while the OS reboot issue POTENTIALLY affects everyone, but they might not have a usage pattern that triggers it.

This is all guesswork. I don't have access to enough units to really flesh these theories out.
[Nexus 7 (2013) General] sfhub:
How did it behave before JSS15Q?
[Nexus 7 (2013) General] bozzykid:
How is that even possible? The update didn't include a new Play Music app.
[Nexus 7 (2013) General] sfhub:
Well the update did include AAC encoding/decoding changes.

I was curious what the issue was before because it wasn't widely reported.
[Nexus 7 (2013) General] aerdely:
Wondering, has any one else not received the update. Figured I would of by now as it seems people in the UK are now receiving it. I'm fully stock so there should be no reason I shouldn't get updates, or I wouldn't think at least.