yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] sfhub:
In the early days of a rollout, there is a process that randomly selects unit ids to receive the update. No amount of checking for updates will make any difference until your unit id is selected.

Later on in the rollout, they turn the spigots on full and everyone is selected.
[Nexus 7 (2013) General] aerdely:
Yea, I got that. It seems the device checks by its self every couple of hours any way so I'm not worried about that but I guess when they say its rolling out slow they really mean it. After a couple days I would of just assumed it would be system wide by now but who knows. Just going to have to Wait but thanks for the info.
[Nexus 7 (2013) General] sfhub:
By two weeks usually everyone has it through the normal OTA distribution channel.

It is only slow if you haven't been chosen :) I have a couple of units that were all chosen, so it was "fast" for me :)

If you want it earlier, suggest you manually install.
[Nexus 7 (2013) General] aerdely:
Trust me i would of done that by now, or even been rooted by now if I had the choice but I don't own a PC to sideload it. Like said if were my choice I'd be rooted as I have all my other devices mostly phone which didn't require a PC to do it at first in the early days of android but now at days it seems a PC is required to root most devices now. Like said no biggie as there's not much I'm worried about with the new update, just like getting them, think most feel that way. Either way gonna root just have to wait till I get the chance to use a PC. Thanks.

I think there were only 2 I weren't able to root which were the droid eris in the early days of HTC locking they're bootloader and the the droid x. Two others required a PC which I eventually got access to do which were the og droid and og n7. Other than that I think I was able to root most others I've owned without one but also back then a had a computer which that has crapped out in recent months. No biggie anyways, just gonna have to wait and see.
[Nexus 7 (2013) General] wilsonlam97:
Before it kept playing the same songs over and over but now it's actually random songs being chosen. Simply they fixed the problem with Android not really generating random numbers.
[Nexus 7 (2013) General] sfhub:
Hmm, so they fixed this problem?

http://arstechnica.com/security/201...droid-crypto-flaw-used-in-5700-bitcoin-heist/

That is actually a far more serious and bigger problem than Google Play random songs.

Cryptographic private keys used on Android are potentially affected (and vulnerable to be stolen). Beyond that lots of cryptography depends on random numbers really being random.

UPDATE: I believe we have verified the PRNG fix for this security issue is included in this release.

According to the sample code from Alex Klyubin, Android Security Engineer

public final class PRNGFixes {

private static final int VERSION_CODE_JELLY_BEAN = 16;
private static final int [COLOR="Red"]VERSION_CODE_JELLY_BEAN_MR2 = 18[/COLOR];
private static final byte[] BUILD_FINGERPRINT_AND_DEVICE_SERIAL =
getBuildFingerprintAndDeviceSerial();

/** Hidden constructor to prevent instantiation. */
private PRNGFixes() {}

/**
* Applies all fixes.
*
* [MENTION=948141]Throw[/MENTION]s SecurityException if a fix is needed but could not be applied.
*/
public static void apply() {
applyOpenSSLFix();
installLinuxPRNGSecureRandom();
}

/**
* Applies the fix for OpenSSL PRNG having low entropy. Does nothing if the
* fix is not needed.
*
* [MENTION=948141]Throw[/MENTION]s SecurityException if the fix is needed but could not be applied.
*/
private static void applyOpenSSLFix() throws SecurityException {
if ((Build.VERSION.SDK_INT < VERSION_CODE_JELLY_BEAN)
|| [COLOR="Red"](Build.VERSION.SDK_INT > VERSION_CODE_JELLY_BEAN_MR2)[/COLOR]) {
[COLOR="Red"]// No need to apply the fix[/COLOR]
return;
}

The fix for not enough entropy (randomness) in the PRNG (PseudoRandomNumberGenerator) SecureRandom() was in API level 18 included in Jelly Bean MR2.

JSS15Q is MR2 for us and we see from this checkin log that we have API level 18 in our release. That plus the Google Play randomness mentioned above is pretty good assurances we have the PRNG fix.

http://funkyandroid.com/aosp-JSS15J-JSS15Q.html

Project: platform/prebuilts/sdk

a9fda16 : Drop official release of SDK 18.​

https://android.googlesource.com/platform/prebuilts/sdk/+/a9fda16

Drop official release of SDK 18.

The SDK is downloaded by the Eclipse SDK Manager.​
[Nexus 7 (2013) General] vcallas:
Since getting the OTA yesterday my GPS has greatly improved. I have been switching between Ingress and Waze for the past 6 hours and only lost lock once and that was because I was underground and it required my location in Ingress within 15 sec. I did have one random reboot this morning but I have not been able to make it happen again. I have never had any screen issues though before the update the longest I could keep GPS going was 30 min, though usually Ingress would only allow me to play for 5 min without needing a reboot.
[Nexus 7 (2013) General] wilsonlam97:
It very well seems like it.
[Nexus 7 (2013) General] matthewr87:
That's odd. On JSS15J my tablet had an up-time of close to 500 hours. Now only a day after installing JSS15Q I JUST had a random reboot...
[Nexus 7 (2013) General] sfhub:
If you did a dirty flash, you may want to factory reset and restore apps only.
[Nexus 7 (2013) General] matthewr87:
Thank you for the tip. I simply installed the OTA when it showed up. Do you think it is still a good idea to factory reset? Thanks!
[Nexus 7 (2013) General] NekroWolfen:
With the update everyone agrees that it definitely fixed the jumpy multi-touch issue?
[Nexus 7 (2013) General] scriptor:
nexus 7 update

I just updated my N7 and the issue continues with touch failure =[ I have a feeling this is going to be hardware failure....
[Nexus 7 (2013) General] xdatoast:
Quick early report: I updated to JSS15Q via adb today and no random rebooting yet. It had been happening frequently, particularly watching YouTube videos. Also, Netflix works now.
[Nexus 7 (2013) General] sfhub:
If you are not having troubles, no need to reset, but since you are, good idea to try.
[Nexus 7 (2013) General] wintermute000:
For most but not all
[Nexus 7 (2013) General] Caldair:
I just got my flo yesterday and knew about 15Q update beforehand, so the first thing I did was check for updates, but of course, I was told no updates were available.

So I did a little trick I learned while waiting for my turn to get the 4.3 update on my Nexus 4: went to Settings>Apps>All, selected Google Services Framework and cleared its Data, then back to About tablet>System updates and tapped to Check for update. It took 2 tries of the whole process, but I got my update.

After getting the update installed you will just want to remove your Google account and add it again, just to get all the permissions Google wants right again.

Hope this works for you. I have sucessfully done this twice on the Mako, and now once on Flo, so it seems to work consistently, if not always on the first try. Good luck.
[Nexus 7 (2013) General] aerdely:
Thanks, I'll give it a try. It seems most have received the update with the exception of a the few who did sideload method but when I do press check it actually doesn't seem to the time update but instantly does when I press check like it doesn't even check the server. On my transformer when had it if you check for an update after pressing the button it took a few seconds and you can see the progress line working, the blue line that signal its checking, but in the case of this one it doesn't seem to at all just instantly update time like said, so haven't check for most of yesterday or today because figured i'd just get it when it was available. I'll give that a try though maybe something got fouled up.

---------- Post added at 01:07 AM ---------- Previous post was at 12:51 AM ----------

Good info, it took 3 attempts of clearing Google services framework then checking for the update but it worked finally got the 10 mb download and it updated. Thanks for the help, good to know for the future.
[Nexus 7 (2013) General] danvee:
Bad news is that there have only been 123 people posting about this freezing, rebooting, etc issue in their product forums.

Need everyone effected to make it known by posting there....

https://productforums.google.com/forum/#!topic/mobile/mG4JXaT-SHs[351-375-false]
[Nexus 7 (2013) General] robk2544:
I was tired of waiting for 15Q because 15J broke GPS (didn't see previous post on how to induce) so I sideloaded it with ADB, after I learned to tap build 7 times for developer options, debug. It went fine, "About" shows update, but GPS lock is very slow. Is this normal? I'm a Win expert (my job) but new to Android. The device is stock, haven't done anything to it yet. Anyone else not pleased with GPS? Other than this, it seems to be much better than my Lenovo 2107 that I bought 8 months ago.

Rob
[Nexus 7 (2013) General] aerdely:
Although I wasn't experiencing many issues before other than slow GPS lock. No multi-touch or random reboots after getting the update it does seem the GPS is a little better, still a little slower than I've noticed on other devices but not bad. Can deal with it. Never tried the gps while in my apartment, usually its off for battery consumption but while in my apartment doesn't seem to lock to well, although its a basement apartment in a 3 family house so probably to be expected. Other than that everything else still seems to be OK after the update, considering like said weren't many issues to begin with for me but just figured I'd report it.
[Nexus 7 (2013) General] eecummings:
sfhub, you've attached stock-recovery-JSS15J.zip (8.18 MB), but under Update #3 you refer to stock-recovery-JSS15J.zip (7.70 MB). Can either be used?
[Nexus 7 (2013) General] GunninZombiesdown:
Has anyone else that did the update have their N7 get stuck in the boot screen? Any ideas for a quick fix without having to flash it?
[Nexus 7 (2013) General] NotARobot91:
Sadly even on the build 8 of CM. My multitouch issues have gotten even worse. A bit of a bummer.
[Nexus 7 (2013) General] sfhub:
Yes, either can be used. The smaller one is what it looks like before installation (from the factory images) and the larger one is what it looks like after installation.

I have both the factory and pulled (after install) images and since I was grabbing the stock JWR66N kernel (which had to be pulled since we never got JWR66N factory images) I was in the pulled section of my archives so I grabbed all pulled versions for the first post.

I always do binary compares on the factory and pulled versions to make sure the relevant sections are the same. The pulled versions are larger because they represent the whole partition.

The pulled versions are what it looks like when you do a TWRP or CWM nandroid backup.
[Nexus 7 (2013) General] sfhub:
Which boot screen? Google? X? Recovery? Bootloader?
[Nexus 7 (2013) General] jhom52:
Thanks for the trick. It worked on the second try. I'm now on Q. :good:
[Nexus 7 (2013) General] Hnk1:
Thank you so much for your updates and help mate.

However, I AM HAVING SOME TOUCH ISSUES(I never experienced them before) AFTER THE UPDATE WHICH WAS MANUAL.

I think this should be added that if your device doesn't receive the update, do not manually do it if you have no problem.

I did that to see if my speakers had hardware issue or software. I will be going back to old version.

DETAILS :

After installing the new update on my Nexus 32 GB NON ROOTED, STOCK, JUNE build with no multi touch issues, one speaker dead (no sound comes n it was like out of the box) showed no major change in touch issues but I guess sound has improved on my only working speaker. It could be due to sound settings changed a bit in Google Music maybe.

I have seen a bit of glitch with keyboard typing as a word is typed twice and sometimes keeps on holding when I have even let it go. (I have non of these issues before but they are very rare n with some typing practise it has improved and i am waiting for a glitch.)

Also while playing games, if I have to keep on holding on a specific location, sometimes the key keeps on being pressed even when I left it go.

And if two or three keys are stuck, You will hang your Nexus until the touch sensors feel the touch is gone and you game will resume.

I only have this on REAL STEEL and I am not sure if this is a GAME issue or software issue but I am not gaming much at the moment on it.

All Google apps updated even when I had switched off auto updates at PlayStore.

In sleep, nothing is downloaded from GooglePlay but works if the screen is turned on. However, other downloads work even with screen turned of.

I had one typing glitch while typing this all with one finger and non while typing with both thumbs.

I guess previous was more stable for me and forced update manually was not a good choice.

Other than that I guess there is no difference.

---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------

Cool trick
[Nexus 7 (2013) General] The111:
I have JSS15J stock rooted on my device. When I unlocked the bootloader and rooted, I flashed TWRP recovery.

I wanted to go back to stock recovery and tried flashing the JSS15J recovery from the OP here, but after doing so every time I try to boot to recovery I get the dead android symbol. If I flash TWRP again though it works fine.

I'm flashing the stock recovery via the same method I use to flash the TWRP (i.e. "adb reboot bootloader" followed by "fastboot flash recovery filename.img"). It appears to flash successfully, just won't ever boot to the newly flashed stock recovery.

Any ideas?

Interestingly enough, there is a "stock JSS15J recovery" in this thread which is a totally different file size. I've tried flashing that one also and same result (dead android).
[Nexus 7 (2013) General] Rollerdog:
I used the trick to get the ota update and it worked fine. However I am not sure how to remove my google account and then add it back again. I would prefer not to do a factory reset
[Nexus 7 (2013) General] chrismast:
Go into settings and into your Google account, just delete and re-add
[Nexus 7 (2013) General] Rollerdog:
Thanks Chris. I got confused by looking at some older examples of removing an account. It is evidently a lot simpler now.
[Nexus 7 (2013) General] GunninZombiesdown:
It was the X screen.I ended up just doing a factory reset anyway.
[Nexus 7 (2013) General] aiiee:
When I enter "flash-all-nowipe" I get "'flash-all-nowipe' is not recognized as an internal or external command,

operable program or batch file." in response. Did you leave something out?
[Nexus 7 (2013) General] lespaulman67:
Hi my Nexus 7 2013 build 7/2013 was perfect oout of the box on touch. It was on JWR66N now on JSS15Q from a OTA. It has really messed up my touch now it ghost all over the place when I swipe and I have tons of dead keys in landscape mode.

I was wondering if I can side load JWR66N back as stock right now. Google is got to fix this or its going back. I am on 5th right now. All from different stores. Same issue on everyone of them. Must be hardware.

Please let me know
[Nexus 7 (2013) General] sfhub:
The dead android symbol *IS* stock recovery.

Google has just hidden the stock recovery menu by default possibly so you don't mess things up by accident.

Anyway, to see the stock recovery menu you need to Press/Hold Power, then Press/Release VolUp, then Release Power, in that exact sequence.

Both of those are stock recovery. One is pre-flash from the factory image. One is post-flash pulled (ie the same as if you did a nandroid backup) I always do binary comparison on the two to make sure the relevant sections are the same. Both will pass future OTA check for updates.
[Nexus 7 (2013) General] sfhub:
If you have done a dirty flash (ie preserved your user data) first thing you should try if there are issues is to do a factory reset (backup apps and sdcard if necessary) and see if the problems persist.

This is the same for the OTA and for Factory Images.
[Nexus 7 (2013) General] sfhub:
Did you double unpack the factory image to get the razor-jss1q directory?

Did you unzip the attached razor-jss1q-addon.zip into the razaor-jss1q directory?

Is your command prompt in the razor-jss1q directory?
[Nexus 7 (2013) General] sfhub:
Google hasn't provided JWR66N factory images but someone has posted a JWR66N TWRP backup somewhere you can restore to. I don't have the link at the moment, I think it is in the erratic touch screen thread.
[Nexus 7 (2013) General] lespaulman67:
Well Google get us back to the JWR66N with a update of some type. Pull all the others from the OTA till we fix this issue. Lets try to get the JWR66N so we can side load it. If goes back in and works like it did I would say this issue is software. But whatever happened it was bad. Dead screen all the time in certain area.
[Nexus 7 (2013) General] rikai:
Well, i seem to have drawn the short straw, myself. JSS15J gave me no issues with my touchscreen at all, i did have issues with random reboots at one point on JSS15J, but a completely fresh install and updating the Google play apps one by one manually rather than just doing an 'update all' fixed those completely.

I decided to do the OTA update to JSS15Q anyway, because i was having occasional wifi issues, and now i'm seeing ghost touches and random long-presses even when i stop touching the screen (though i can not reproduce these in YAMTT, only notice it sometimes in various apps when using the keyboard) and disappearing touchpoints and touchpoints not staying under my finger(usually when doing 3 finger touch) when doing multitouch on the same axis. So JSS15Q seems to have in fact BROKEN multitouch for me, very annoying. For the record, this is all without a screen protector.

On the plus side, wifi issues do seem to be fixed, not sure if there's a difference in GPS as i haven't paid much attention to it. I may try to revert to JSS15J regardless to see if it fixes the touch issues again. Much less annoying to have occasional wi-fi issues than to have a erratic touchscreen.

Am i in a third camp of my own? :x
[Nexus 7 (2013) General] aiiee:
It was the addon file. While it was attached in the post, I missed it in the text so I didn't touch it :) Thanks for your help!
[Nexus 7 (2013) General] aerdely:
I used the same method and actually didn't have to, just reset Google location access and went to settings and hit sync, everything was fine after that. Account has been OK since.

---------- Post added at 07:18 PM ---------- Previous post was at 07:12 PM ----------

I have a funky issue since the new 15q update which I didn't have before. Getting miss types when trying to type in certain apps, mainly here in xda 4 app, also some keys seem to stick, you tap it and the letter stays lit for no reason. Also on start up the lock screen acts funky, half of it stay black for a little bit while the other flickers weirdly for a couple seconds till it eventually all shows up. Never noticed these things or had them till the latest update, the miss type and keys getting stuck is quit annoying, trying to type and you have to pause and either go back or wait for the key to release to continue typing.
[Nexus 7 (2013) General] crspang:
Simply genius! Thank You!
[Nexus 7 (2013) General] jrwingate6:
This didn't work for me. I tried it 10 times.
[Nexus 7 (2013) General] Caldair:
:( Bad luck I guess. A few others have reported success since I posted this yesterday, so I really do think it's more than just coincidence. You may not want this update anyway, as touch seems a little messed up. For instance, as i was typing this message at one point my "d" key on the keyboard lit up blue and stayed that way, as if I was holding the key down, until I touched somewhere else.:confused:
[Nexus 7 (2013) General] The111:
Haha, oh man I feel stupid. Talk about making assumptions. :o I just thought for sure that symbol was bad news and meant the partition was borked.

Thanks for the info. :good:
[Nexus 7 (2013) General] aerdely:
Yes, everything was fine up until this point and was experiencing the same thing but not only that, getting miss types especially with the space bar when typing, press a letter or the space key and it doesn't register. Just did a factory reset, it seems to have fix the issue with the key getting stuck lighting up blue but still getting miss type here and there while typing messages here in xda although not really noticing it any where else yet. This maybe the single touch issue which others have reported. While I wasn't experiencing it before, I am now after the latest update. Not using any screen protector or anything else. A factory reset seems to have alleviated the keys getting stuck though.
[Nexus 7 (2013) General] lespaulman67:
I wonder if Google has pulled that update also. Anyone that gets this update please post in here. Starting today. I have a feeling they pulled it. Well it did damage to everyone again. Should of stayed with JWR66N.
[Nexus 7 (2013) General] danvee:
I still haven't gotten it... Northern NJ.
[Nexus 7 (2013) General] SubMatrix:
Finally got this to work around the 10th time or so. I first tried 5 or so times, then didn't try again for a couple hours. On the 2nd set of tries, the 2nd attempt worked.
[Nexus 7 (2013) General] aerdely:
Try this, it usually works in most cases just takes deleted attempts. One person reported he tried over 10 time but eventually it worked, it worked for me on the 3 attempt.

http://xdaforums.com/showthread.php?p=44954063
[Nexus 7 (2013) General] lespaulman67:
Everyone listen up. I been doing some heavy testing. I have a Moko case and here is the weird thing if you fold the case back and lay the tablet on your palm without touching the tablet with your hand at all. It has 2 layers of somewhat leather between it and your hand it works perfect. It also works perfect setting it that way on my leg. hmmmmmmm

I been really flexing the screen on its back. Now its working perfect laying on the table without touching it. The tablet is running great now.

This is telling me that's its a internal issue going on guys. I think the cables are loose. Can we get brave people with the issue take it apart and check. Check back if it works. Has to be loose parts inside .Mine fixed itself. hmmmmmmmmmm

It does have that rattle by camera.upper left corner in landscape mode.
[Nexus 7 (2013) General] sfhub:
The start up lock screen acting funny, I think has always been the case, but only when you first boot up in landscape mode. That you never noticed it before makes me think you usually use it in portrait mode, but only recently started booting up in landscape mode.

If that is the case, I wonder if it also possible you didn't notice the iffy typing before because the problem area was mostly in the top 1/3 of the screen (in portrait orientation) which isn't in the typing area in portrait mode, but if you switch to landscape mode, it is the left side of the keyboard (or right side depending on how you rotate)
[Nexus 7 (2013) General] Aerys:
adb logcat > logcat.txt, check for update, download update, find link in logcat, upload to mega.co.nz, profit.
[Nexus 7 (2013) General] sfhub:
Updated first post, thanks
[Nexus 7 (2013) General] greyhulk:
I am stock, but rooted with TWRP. Can I simply run the OTA and then restore root with OTA Rootkeeper? I was able to do that on my Nexus 10.1 with no issue when 4.3 came out (although I did have to reroot manually) and I'd rather not unroot if I don't need to.
[Nexus 7 (2013) General] dscribe:
OTA Rootkeeper says it does not support JB 4.3. Check it out --> https://play.google.com/store/search?q=ota rootkeeper
[Nexus 7 (2013) General] macaumen:
Cannot find any update. Still on JSS15J
[Nexus 7 (2013) General] Tony_YYZ:
I'm still on JWR66N. No new OTA available for me as of yet.
[Nexus 7 (2013) General] sfhub:
See update #3 in first post
[Nexus 7 (2013) General] greyhulk:
VERY nice. Thanks!
[Nexus 7 (2013) General] chiikko561:
Patiently waiting but truly tired of being patient... Lol... I just want to play my multi touch games with out problem...

Sent 4rm my Paranoid Nexus 4.3 LTE...
[Nexus 7 (2013) General] player911:
Once we get the URL, we can just manually update. Correct?