yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] bpear96:
Yeah, ADB Sideload :)

Also what did I win :confused: lol
[Nexus 7 (2013) General] Aerys:
Yes. adb sideload will do the job.
[Nexus 7 (2013) General] jiggytom:
What if we are on a ROM like Minimus from the Android Dev forum..do we have to wait for the developer to release an update? Maybe we can dirty flash to a different rom if another rom comes out with it first.
[Nexus 7 (2013) General] :
+1. Here's an adb sideload guide for those of you who are new to it: http://www.droid-life.com/2013/02/12/guide-how-to-use-adb-sideload-to-update-a-nexus-without-root-or-custom-recovery/
[Nexus 7 (2013) General] sfhub:
Simplified a little for nexus 7

This sideload guide is for

stock recovery

.

If you are using TWRP, copy the update.zip to your virtual sdcard, then boot to recovery, choose Install, select the OTA-update.zip file, then swipe to install. Prior to reboot install SuperSU to preserve root and TWRP recovery.

Simple guide to adb sideload:

adb reboot recovery

Alternatively, power down tablet and press/hold Power+VolUp until you see Google

You'll see fallen down android, press/hold Power, then press/release VolUp, then release Power, you will then see Recovery menu

Select "Apply update from ADB" using VolDown

Press Power to select

adb sideload update.zip

Suggest renaming long OTA update filename to update.zip for convenience

update should begin loading

If you have trouble with an unknown device named Flo, see this post for adb drivers that will work in recovery:

http://xdaforums.com/showthread.php?t=2391236

Alternate try the naked adb drivers:

http://xdaforums.com/showthread.php?t=1161769
[Nexus 7 (2013) General] SubMatrix:
sfhub can you add/link instructions to reverting to stock recovery from custom recovery like TWRP?
[Nexus 7 (2013) General] SalTNutz:
Can you sideload this into a CM10 rom?
[Nexus 7 (2013) General] phazerorg:
No.
[Nexus 7 (2013) General] Macmee:
Stock rooted, no OTA yet but even if I got it, it wouldn't work because I'm custom recovery and rooted so it looks like I'm waiting for a fix.
[Nexus 7 (2013) General] madquack:
Download the factory image package (search for it on google...)

Reboot to bootloader

in cmd prompt/terminal

fastboot erase recovery

fastboot flash recovery NAMEOFSTOCKRECOVERY.img

fastboot reboot
[Nexus 7 (2013) General] aerdely:
No not the case, I always use my tablet in landscape mode, I iffy typing happen whether it on left or right of screen while in landscape, mostly while trying to tap the space key but others as well, the screen acting strange maybe the case but as said always use tablet in landscape, even since day one, I don't live the portrait mode. As well I might of not noticed it but I also did a factory reset which seems it might have taken care of it, this never happened on other tablets which is the reason I'm noticing it. Maybe normal for the new n7 and doesn't really effect anything just something noticed. They type issue though is quite annoying whether typing on left or right in landscape like said never use portrait, and especially while trying to tap space key it just doesn't register. It s completely random and you just have to keep going back to retype the letter or space some times even twice. Is little annoying but tolerable, not as bad as some of the other issues I've seen reported. This only started after latest update, had no issues what so ever when was on last update which was 15j.

Update just did a reboot to Check, the screen flickering on startup seems to be gone which haven't checked since I did a factory reset an hour ago gonna try one more time later just to see but the missed key tapping you would almost think is personal error while trying to type fast, not really the case though, I've slowed down and typed which it is more obvious when it happens but also they keys getting stuck is still there which I thought went away after the factory reset. You tap a letter and it stay lit blue till you tap somewhere else on the screen. Even happens when typing pin on lock screen to unlock the tablet. If you happens when tapping back space it will stay lit and keep erasing letters on its own. Also with the letter it'll stay lit and the accented letter will pop up like if you were holding the key. As said none of this happened on 15j.
[Nexus 7 (2013) General] sfhub:
Sorry to hear that it got worse.

It does seem like they are tweaking parameters in the touchscreen firmware to account for hardware variances and this is making things better for some, no change for others, and worse for a few. Unscientifically it is looking like most are reporting better or no change but there are a few reporting it got worse.
[Nexus 7 (2013) General] ramsrdebest:
Update completely broke my gps

On the previous version of 4.3 J I would get gps signal for a considerable amount of time before eventually it would go out. With the Q update my GPS is completely broken it just sits on searching for gps and never actually connects.
[Nexus 7 (2013) General] sfhub:
Have you tried clearing agps and rebooting?

If that doesn't work have you tried factory reset?
[Nexus 7 (2013) General] aerdely:
Honestly it's not that bad, can deal with it. I came from the Asus transformer which had ghost touch issue which made the screen go nuts at time, always had to reboot and clean the screen. If this is all I have to deal with on n7 or at least I hope its all no worries. Can deal with it. It'll probably be taken care of in future update, like said it a new issue with latest update so sure there'll be a fix. Just figured I'd report it in case anyone experiences the same thing. Thanks though and nice talking.
[Nexus 7 (2013) General] ramsrdebest:
I tried clearing agps and rebooting with no success and I did a factory reset earlier to no avail.
[Nexus 7 (2013) General] aimfire72:
Agreed - this is freakin' BS with these "staggered roll outs".

I'm 100℅ stock and no OTA as of 8/25. If it's a server load issue, that's pretty sad, there's not exactly a huge installed base of stock Android devices out there. I mean, Apple manages to pull it off with their iOS updates, why can't Google do it? What am I missing here?
[Nexus 7 (2013) General] :
Yah it kill my gps to or the hardware just gave up after OTA. I tried clearing everything and even reflashing 15J but GPS will no longer turn on on any version...guess its RMA for me...:(
[Nexus 7 (2013) General] aimfire72:
Same here, nothing!

Sent from my Nexus 4
[Nexus 7 (2013) General] nikosssb:
When i open maps it keeps saying searching for gps. It was like this since I bought it. Im still on JWR66N.
[Nexus 7 (2013) General] danvee:
No issues after the 15Q update. No issues before, though.
[Nexus 7 (2013) General] rxnelson:
I don't think it is server load. I think they are scared of pushing updates or something in case it bricks a bunch of devices. However, when I turned on the tablet when I first got it I immediately got 2 updates as I assume everyone else did. They didn't worry about it then. Maybe they are just screwing with us.
[Nexus 7 (2013) General] soju59:
Got the update this evening (25 Aug) in NC. No issues for me, but none before either.
[Nexus 7 (2013) General] berardi:
I updated... but same as before I don't even get a blinking GPS icon at the top.

Anyone have an idea what to do? I don't even get the blinking gps icon at top
[Nexus 7 (2013) General] nikosssb:
Edit : updated to JSS15Q using the trick above ( clearing google framework data) and gps works fine now. I had no issues with touch neither before and nor now.
[Nexus 7 (2013) General] sfhub:
For me, turning on wifi assistance for that first lock helped, then afterwards could turn it off.
[Nexus 7 (2013) General] Bob Smith42:
Used adb sideload update.zip command to get jss15q.

Big difference on GPS. My GPS application on jwr66n was useless, not working even slightly. Now it works normally with jss15q.

Thanks all for info in this thread.

---------- Post added at 05:28 AM ---------- Previous post was at 05:23 AM ----------

The jss15q update fixed it for me. Before I had same problem.

I use GPS Status app from Play store. Before update it registered nothing at all. Not a single satellite in open field. After update to jss15q it works great. I get the icon in top status bar, too.

Good luck.
[Nexus 7 (2013) General] sfhub:
Can you verify your update went through and you are running JSS15Q? I know it is a silly question, but sometimes when the #s are very similar our eyes play tricks on us.
[Nexus 7 (2013) General] avink:
Clearing Google services framework worked! :)
[Nexus 7 (2013) General] sfhub:
In case anyone needs it, I added a link to the download section of the first post for the old JSS15J factory image.

JSS15J
[Nexus 7 (2013) General] sfhub:
Some of you have perfectly acceptable tablets except for GPS, are worried JSS15Q could introduce more (multi-touch, etc) issues, and just want the GPS fixed. You might be interested in this:

Help test GPS fix that does NOT require OS upgrade, stay on JWR66N/JSS15J
[Nexus 7 (2013) General] aerdely:
Here's something I've noticed, not really an issue but while I was on previous build 15j, in the equalizer setting in Google play. The bass boost option used to be available to change. Now on the 15q build its no longer available, just set in a fixed position again like in 4.2, any one else notice this or is there a way to change it.
[Nexus 7 (2013) General] jrwingate6:
Glad I didn't get this OTA. I'm on JWR66N and my Nexus works perfectly. No multi touch issues and it registers every touch perfectly when not grounded. I can't really comment about the GPS though since I don't use it. That's what I have a phone for.
[Nexus 7 (2013) General] shinkinrui:
Just want to add my report to the mix. I was one of the lucky ones that did not have any issues, touchscreen or otherwise, before the update came out. I threw a cheap dollar store screen protector on as a stopgap while waiting for my Poetic slimline case. A few days ago, I got the jss15q update and was dismayed to discover I now had touchscreen issues with single-finger taps just not registering or sometimes sticking after the finger is removed. Someone else who reported this said they took off their screen protector and it started working, so I waited until my poetic case arrived and did just that. I am now typing this with my new case on and my screen protector removed and the touchscreen issue is greatly reduced but not completely gone. Hopefully more software tweaking is on the way, but for now I can live with it. I've got another screen protector on the way.
[Nexus 7 (2013) General] jyams:
Used OP instructions to go from JWR66N->JSS15Q. Everything went smooth without error. Had no issues before update and no issues since. GPS and touch functions seem to be accurate and dependable. Happy camper!!
[Nexus 7 (2013) General] MattDN93:
Confirming the JSS15Q fixed my multi touch problems (tested in YAMTT on a desk, in hand,unplugged, plugged in) and I walked a good 3km with the GPS staying locked the whole time. For those still awaiting the update:

Till today I wasn't getting the update but here's honestly how I got it to work, literally from one minute to the next I got the update to show :

*Go to settings>apps and find "Google Services Framework" (NOT Google Play Services)

*In the app settings page tap "clear data" but DO NOT FC the app.

*Check for updates again. This probably won't change anything so REPEAT the above process

*For myself I had to repeat 4 times. After this, the update appeared and installed fine.
[Nexus 7 (2013) General] rxnelson:
Got the update today. GPS worked for the most part. It was weird because it acted like it lost signal for a few minutes "waiting for location" however it was still tracking my progress on the map? About 5 minutes later it resumed navigation.
[Nexus 7 (2013) General] sfhub:
Some nav apps deal with temporarily lost signals by using your most recent heading/speed until GPS comes back. Eventually if GPS doesn't come back, they will say lost signal but if it comes back fast enough, then they continue as if nothing happened.
[Nexus 7 (2013) General] matafact:
lost root with new update...

My touchscreen was fine. today the update lit up, so installed it, was rooted with Wugs Toolkit, now have lost root :(... Sure WUG will get it sorted, but annoying for sure...
[Nexus 7 (2013) General] cocchiararo:
So... a friend and i just got a pair of Nexus 7 (2013).

After seeing it had JWR66N, we both allowed google play to install some stuff, and were amazed at how good it ran while installing apps.

for different reasons, we both updated to JSS15Q.

Now i reinstalled (i used thefactory image) many apps, and the tablet slowed down to a crawl while doing it.

I guess this is related to all the "downgrades" to IO introduced in both JSS updates meant for preventing data corruption ?

I had made a complete nandroid of JWR66N... but beeing the genius that i am, i forgot to take it out before using the factory image T_T

On JWR i did not try swiftkey, but on JSS15Q i am using it, and i feel like typing on it is... choppy, or something
[Nexus 7 (2013) General] sfhub:
I doubt you'd notice more than a 5% difference in performance from those changes. I think your are experiencing something else.

I would try factory reset, then verify how things work on pure stock before slowly adding back a few apps at a time.
[Nexus 7 (2013) General] rxnelson:
This was Google navigation. It kept tracking me though. I stopped it stopped. I got back in car and drove it tracked all while saying waiting on location. The GPS icon showed lock the whole time as well.
[Nexus 7 (2013) General] sfhub:
Retrieved the whole sordid history of our touchscreen firmware here:

http://xdaforums.com/showthread.php?p=44954563#post44954563
[Nexus 7 (2013) General] cocchiararo:
well, it was pure stock, i believe, just signed into my google account and allowed the play store to update the base apps :P

(same thing as in JWR).

I now flashed a custom kernel and have not noticed the swiftkey thing again.
[Nexus 7 (2013) General] molo88:
After adb reboot recovery, My Nexus come to TWRP interface. It seems a lot difference from the instruction.

What should I do next?

-----------

OK, IN TWRP, IN Advance to enable sideload.

I don't know if I should check "Wipe Dalvik Cache" and "Wipe Cache".
[Nexus 7 (2013) General] sfhub:
Sorry, I should have stated the sideload is for stock recovery.

In TWRP, you can just copy the OTA update.zip to your virtual scard, boot to TWRP, choose install, and select the OTA update.zip.
[Nexus 7 (2013) General] molo88:
Do I need to reboot or Do something else before I install the 2 SuperSu files?
[Nexus 7 (2013) General] sfhub:
You can install right after the OTA if you wish, no need to reboot.

On the other hand, if you install them before the OTA, the OTA will undo the root, so just do it anytime after the OTA.
[Nexus 7 (2013) General] molo88:
Venice Yaeven

Failed.

Assert failed: apply_patch_check(/system/app/Keep.odex". "6sf9asf8a9ds8fa85d8ada4a8asdi9239", "b3e2dE:Error executing updater binary in zip "/scard/OTA-update.zip'

Error flashing zip '/sdcard/OTA-update.zip'.

I remember I did something to the Keep.

So? Do I have to flash the JSS15Q Factory Image ? (Since I have Titanium Backup my system).
[Nexus 7 (2013) General] cyberprodigy:
I don't know about anyone else but I am getting touches that 'stick' especially when typing.
[Nexus 7 (2013) General] sfhub:
Confirmed we have the PRNG fix for the Bitcoin heist in JSS15Q.
[Nexus 7 (2013) General] sfhub:
It is probably easier if you install the factory image.

If you follow this post, you can choose flash-all-nowipe to keep your data or flash-all to wipe your data.

http://xdaforums.com/showthread.php?p=44888268#post44888268

If you know Google Keep is the *only* thing you modified, I can give you an update.zip to revert you back (tell me what version you were running before, JWR66N or JSS15J), but then if you had any other changes, it would just repeat the above complaining about a different file.
[Nexus 7 (2013) General] molo88:
At last, I upgraded nexus 7 to JSS15Q with flash-all-nowipe the factory image. I found TWRP lost and flashed it back.

UPDATE-SuperSU-v1.51.zip and UPDATE-SuperSU-ota.zip FAILD, But I used UPDATE-SuperSU-v1.43.zip to acquire root again.

Thank you sfhub so much.
[Nexus 7 (2013) General] sfhub:
If you don't mind me asking how did it fail? What was the error message?
[Nexus 7 (2013) General] sfhub:
I think we have 43 pages of that, no?
[Nexus 7 (2013) General] DowntownJeffBrown:
That guy spams with old posts that people made. He will then add a link to Oakley knockoffs in a bit. Look at post 5

>^.^< Sent from meow HTC One which is like catnip to me atm
[Nexus 7 (2013) General] sfhub:
I was taken. Now I have 100 fake Oakleys I don't know what to do with. :)
[Nexus 7 (2013) General] thenrik:
Hi:

Ditto for me.

Tom
[Nexus 7 (2013) General] sfhub:
This is pretty hilarious (at least to me)

Our touchscreen is made by Elan Microelectronics.

See their Youtube video demonstrating their amazing capabilities using of all things, YAMTT!

Notice on over half their tests, the unit is sitting on the table with no hands touching the case and no usb cables connected? Just like we are testing. To add insult to injury, they even spray water on their touchscreen.

Yeah, right, I wish our touchscreen performed like their Youtube video.

So for all those people who think YAMTT is buggy, this is what the manufacturer is using to demonstrate their capabilities.
[Nexus 7 (2013) General] The111:
Somewhat related question: do you know how to check what version of stock recovery I have? It doesn't show it obviously like CWM or TWRP does.

I did a full unroot to accept OTA to JSS15Q, so I'm assuming it updated my stock recovery too. I notice a tiny update to the dead android screen, it now says "no command" next to the dead android which I'm pretty sure it did not before, but it also says <3e> as the version (?) which is same as it was before... but that doesn't mean it didn't rev from 15J to 15Q. Just wondering how I can check for sure that I have the 15Q recovery. Thanks.
[Nexus 7 (2013) General] sfhub:
The easiest way to know for sure which version is to flash a known version of stock recovery.

If you run this command I can probably tell you what you are running:

md5 /dev/block/mmcblk0p25

The "no command" thing I believe comes out when the system has downloaded an OTA update and you rebooted into recovery without giving it a command to install the OTA, but that is just a guess.
[Nexus 7 (2013) General] The111:
Thanks. The MD5 is

d7e08392ff252c5bf16f4af1ec52ceb5
[Nexus 7 (2013) General] sfhub:
stock JSS15Q recovery.
[Nexus 7 (2013) General] The111:
Thanks for checking. :)
[Nexus 7 (2013) General] molo88:
I did not capture the screen,sorry. when i swiped UPDATE-SuperSU-v1.51.zip in twrp, there was some file copy error. UPDATE-SuperSU-ota.zip is ok.

I failed to gain root access when i returned to system.

So I SWIPED UPDATE-SuperSU-v1.43.zip again in TWRP, It works. Then I check it in system, The version was v1.51. I don't understand why.
[Nexus 7 (2013) General] i486:
The test with the USB cable pretty much resumes the cause to grounding problems. No touch firmware tweak will fix that.

And what saddens me the most is that Google knows this and they are purposely not informing us, their clients. I think that by this time there is no probability of a recall. Instead they are throwing out "software fixes" so people believe in them and keep theirs nexus until the faulty batch ends and a new fixed one is released to the market, minimizing possible returning costs. By that time the "believers" had already long passed their return deadline, and would need to deal with Asus warranty which is not Google responsibility.
[Nexus 7 (2013) General] sfhub:
I suggest you look over the comments for the touchscreen firmware checkins to get an idea what they can do in firmware.

It is actually pretty complex the stuff they can handle.

http://xdaforums.com/showthread.php?p=44954563#post44954563
[Nexus 7 (2013) General] i486:
I saw the post, and it mainly concerns interference and noise free signal. Capacitive panels need proper grounding to be able to correctly detect the touch inputs, if the device's own grounding is deficient there is no amount of filtering that you can apply to the controller that can correct this issue since the inputs cannot be accurately detected in the first place.

You can see that the grounding issue remains even with the "software fixes" of this newer Q build.
[Nexus 7 (2013) General] DowntownJeffBrown:
Noooooooooooooooooooooooooooo :(

>^.^< Sent from meow HTC One which is like catnip to me atm
[Nexus 7 (2013) General] zlyons:
Just adding my experience for whatever it's worth... I had GPS issues before my Nexus updated today, the touchscreen was perfect. After OTA JSS15Q, GPS is perfect, but the touchscreen is slightly buggy. Very minor, but a bit less accurate on single taps sometimes, and Swype often thinks I picked my finger up in the middle of a word. Overall I'm happy and I think Google and Asus will get it fixed soon. If yours is realy buggy, try to get working one before a refund. This tablet is great!

-Z
[Nexus 7 (2013) General] Jashafi:
Nexus 7 Touch screen issues persit

Even after the JSS15Q, my touch screen is still having issues. The update did seem to reduce the amount of issues but certainly did not omit the problem. If you guys want can you check out my video on Youtube and let me know if you have similar experiences to what I am facing.

http://www.youtube.com/watch?v=68Le3yBGJbE
[Nexus 7 (2013) General] berardi:
My first unit had no GPS icon before nor after update.

Second unit had GPS icon before and after but could not hold lock. Update did nothing to resolve the issue.

These were my 10th and 11th units.
[Nexus 7 (2013) General] molo88:
New update JSS15Q is in use for one day, I found Google service use too much battery even than the screen. This never happen in old version JSS15J.

Any help?
[Nexus 7 (2013) General] reza_1803:
do not get jss15q

salaam,

I have google nexus 7 2, 32 gig wifi version,

my build number is jss15j and I have not get jss15q yet. Noticeably, my device has official firmware and did not root. So I do not know why my device did not get update (jss15q ). I checked several times software update and it showed " your system is up to date " !!!!!!!!!!!!!!!

Please give me your advice that how can I get OTA update !!
[Nexus 7 (2013) General] sfhub:
Only thing I can suggest is do a factory reset, don't sign into your google account, then see if the drain is still there. If not, slowly add stuff back until you notice the drain.
[Nexus 7 (2013) General] lespaulman67:
For me I just did a restore and bam it was there after setting up. You can try it.
[Nexus 7 (2013) General] reza_1803:
if your meant is factory reset, I did it before using it. and it also do shows me " your system is up to date "

:((

my kernel versionis :

3.4.0-g365a6e0
[Nexus 7 (2013) General] Tony_YYZ:
You just have to wait until your devices is queued up for the OTA. I received the notification just last night that it was available for me. I'm afraid to install it since my touchscreen works fine. I'm on JWR66N.
[Nexus 7 (2013) General] cocchiararo:
if you have no issues on JWR66N, i would keep that, since there is no going back
[Nexus 7 (2013) General] Tony_YYZ:
Problem with that is, I can't install Netflix. It requires a newer build. Part of the reason I bought this tablet was for media consumption. I either accept the OTA, wait who knows ho long for another OTA to be pushed or install a custom ROM which I didn't want to do until they became more stable.

Woe is me.
[Nexus 7 (2013) General] rsfinsrq:
Not sure if this will work for our tablet, but while waiting for updates on my Note 1&2, I would go to settings, time and date, select manual and set the date ahead one to two weeks (reboot after setting date) and the update would then be available. Might be worth a shot for those still waiting.
[Nexus 7 (2013) General] berardi:
Can you take the update and then use CM 10.2 nightly which is based on the new kernel or will that not work?