yashsingh1/xdaforums huggingface dataset:
[HTC Desire C] vega509:
very nice rom. I have 2 issues,

1. Wifi will turn itself off after roughly 2 hours, turning it back on repeats the process. Reboot makes no difference.

2. Voice input for typing or search fails with a triangle with an ! mark in it, no message, just brings up a keyboard.
[HTC Desire C] LaputaCake:
Did u flash gapps
[HTC Desire C] vega509:
yes, the one linked to by addictz10. I used the NOPE 700 kernel.
[HTC Desire C] Sertico:
i just flash this rom following the instructions and my device just stock on HTC starting screen

so i havent see this rom yen

P.S i used the boot.img that comes with the rom
[HTC Desire C] nemanjsb:
"USE N.O.P.E or Prometheus Kernels.." :)
[HTC Desire C] Sertico:
Try both... And got the same results
[Nexus 7 (2013) General] wintermute000:
Google guy paulw has specifically said JSS15Q alleviates the touch issues

". 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."

Gah and I just unlocked/customed my N7..... guess I gotta wait till the chefs rebase or pull the pin, roll back to stock
[Nexus 7 (2013) General] sfhub:
Thanks, apparently he posted that right after I hit submit :)

Of course the big question now is how it is working out for people who had the multi-touch issues and whether this does anything to address the gps and random reboot issues.
[Nexus 7 (2013) General] blackhand1001:
Screw stock. Custom is so much better lol.
[Nexus 7 (2013) General] GuestK00190:
We need someone on XDA to get that OTA ASAP. We definitely need as many people as possible reporting about whether this fixes their N7 issues.

Here's hoping this'll all be good by tomorrow morning!
[Nexus 7 (2013) General] wintermute000:
Yeah but depends who arrives faster ROFL ROFL

I am very surprised by the lack of stock flashable ZIP roms (I know I can fastboot push the factory image but flashing a zip in CWM/TWRP is easier for the lazy!)
[Nexus 7 (2013) General] notoriouspk:
flash it someone

I would flash it but running a custom Rom... me wants to know if touch is fixed
[Nexus 7 (2013) General] wintermute000:
Yah thats my problem too, theoretically a ROM based on this new OTA would incorporate the fix but the only way to 'experience' it 100% is to flash it as stock as who knows how the changes interact with the custom ROM changes
[Nexus 7 (2013) General] GuestK00190:
I'm impatiently waiting to see the OTA notification on my fully stock N7... Here's hoping good things happen! :D
[Nexus 7 (2013) General] Anthonok:
Here's to hoping this fixes the bootloop issue
[Nexus 7 (2013) General] sfhub:
Btw given how JSS15J was apparently pulled, I am guessing they will produce 2 ota updates

JWR66N -> JSS15Q

and

JSS15J -> JSS15Q

Given how the feedback from initial users was worded on google forums we probably only have confirmation of the JSS15J to JSS15Q ota update. The one from JWR66N might also be available, just haven't seen confirmation of someone downloading.

Normally they don't pull updates so your path would have been

JWR66N -> JSS15J -> JSS15Q

But in this case since they seem to have pulled JSS15J it may work a little differently
[Nexus 7 (2013) General] windmark:
I'm also waiting on the OTA on my fully stock device, but I am one who have not been able to reproduce the touch issues on my n7. Will neither the less report back when I get it.
[Nexus 7 (2013) General] chiikko561:
I too am full stock jss15j and waiting hoping this solves my problems...

Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
[Nexus 7 (2013) General] spmode:
If I get the OTA update, where would I find the file so I can upload?
[Nexus 7 (2013) General] gunnyman:
Excellent post, bravo. Custom firmware not based on 15q will have the same issues as stock
[Nexus 7 (2013) General] MattDN93:
Also fully stock unrooted here, suffering from the mutitouch issues brought with JSS15J, no OTA here, I read in the other thread Google is phasing in the update by picking random device IDs to ease server load. Either way its good for the reputation of the N7 2013 that this update will ease customer (and my) tension about this being a hardware issue. It's not crippling my N7 like it seems to be doing for some other but it's definitely an issue. Will report back and possibly forage around my /cache partition when the OTA arrives to let you all know.
[Nexus 7 (2013) General] Deleted member 2879886:
It will pop up in your notification box as with JSS15J
[Nexus 7 (2013) General] Markdek:
Yeah, after hundreds maybe thousands of returns.

Had Google just communicated, that would have prevented so much waste w/ hundreds, maybe thousands, of returns.
[Nexus 7 (2013) General] Coronado is dead:
I think he is asking where it downloads to so that he can share it with the rest of us. But I am unsure where it downloads and cannot help here.
[Nexus 7 (2013) General] spmode:
Yea, I was wondering where the update file would be so I could share. If anyone knows...
[Nexus 7 (2013) General] sfhub:
You just have dead spots on you screen. Usually the are found in upper 1/3rd of screen in portrait mode.

They are not completely dead of course as it works when you hold the tablet, but when on a table there are dead spots.

There are units that have no dead spots.
[Nexus 7 (2013) General] RedDevils88:
Successfully updated the latest firmware without wipe. :)

Here are the steps that i used to flash mine without a wipe

WARNING FLASH IN YOUR OWN RISK!

Follow the steps from this website.

http://www.androidpolice.com/2013/08/10/ho...ge-and-root-it/

Summary:

1. Download the latest official image from google development website : https://developers.google.com/android/nexus/images#razor

2. Download Android SDK development tools from this website: http://developer.android.com/sdk/index.html

upon finishing the downloads:

1. extract the image file (.tgz) and place it on C drive or D drive (anywhere on the computer will do)

2. on Android SDK folder, navigate to sdk ---> platform-tools and copy

(a) AdbWinApi.dll

(b) AdbWinUsbApi.dll

(c ) fastboot.exe

then paste these into the extracted image folder.

3. to keep your data from being wiped : Proceed with this step if you want to keep your data intact. If you skip this step, your data will be wiped. With your favorite text editor, edit (be careful not to run it by accident instead of editing) flash-all.bat (if you're on Windows) or flash-all.sh (Mac, Linux) and remove "-w" from the fastboot update command. For example, if the line reads fastboot -w update image-razor-jss15q.zip, it should now read fastboot update image-razor-jss15q.zip. The -w option instructs fastboot to wipe data.

4. Reboot into the bootloader and click on the flash-all.bat that you have just edited and saved.

the tablet will now be flashing the new firmware version

This method worked for me, i am just trying to help so flash at your own risk!!

(this will disable your root privilege and requires you to reroot the device)
[Nexus 7 (2013) General] gti8:
I just did the factory flash of JSS15Q and my multi touch problems are gone :good:. Previously I ran the YAMTT test program and I had problems when the tablet was flat on a table and not connected to the charger. I was able to replicate the problem every time. Now it's gone and I'm happy :victory:
[Nexus 7 (2013) General] Melodycd:
I am going to update the FLO today. But i am not sure if it will help, cause my tablet have dead zones, its a line of 0,5 inch maybe from botom to almost top. What is strange, when i run tochscreen test, some time this zone is absolutely irresponsible, but some times it registers my toch there. Thats strange.

I can't return it, Amazon already refused to help me with it, i am not in US currently. :crying:

I'll do it as soon as i get home from work. Will post feedback after.
[Nexus 7 (2013) General] stringy2010:
Just flashed teshxx/scrosler deodexed version and all working well.

Didn't have any problems to start with but its just nice to know I'm up to date :)
[Nexus 7 (2013) General] TP_NC_USER:
Don't you have to also delete userdata.img and recovery.img from image-razor-jss15q.zip to avoid overwriting your custom recovery and user data?

After updating, I had to reflash SuperSU using TWRP and re-install BusyBox. I'm using the SecureSettings plugin for Tasker so I had to re-install the Helper app too. Managed to keep all my apps and data though and even my Google account privacy settings survived.
[Nexus 7 (2013) General] roy827:
JSS15Q OTA file

hello, guys,

I got the OTA and because i'm rooted, i was able to reach the OTA file from the Cache folder. (hey,OK i know, file uploaded to mega.co.nz/#!FZVTRZrQ!UorLeTYEpmTGWsOoMUnJpmJeMAxILSzK8LDGBnlb50Y)

Now i'm JSS15Q, with OTA upgrade succeeded. [MENTION=1299673]sfhub[/MENTION]

Have fun guys~~
[Nexus 7 (2013) General] Hnk1:
I DOWNLOADED THE IMAGE AND IT HAS NO FLASH-ALL FILES. JUST SYSTEM (only 1 file)

I need

flash all.bat

bootloader

flash base.sh

flash all.sh

EDIT SOLVED IT MYSELF

RENAMED MY FILE THAT I EXTRACTED FROM .TAR to .BZ

A new folder came and there was everything there.

Should have used another programme for unzipping
[Nexus 7 (2013) General] maopr16:
Thanks! Used teshxx's rom & just wiped dalvic & cache,updated to SuperSU 1.51, flashed from TWRP (no verification) Everything flashed fine for the deodexed ver. i have the update!

http://xdaforums.com/showthread.php?t=2416438
[Nexus 7 (2013) General] ScottPV:
Downloaded but did not work on my rooted with TWRP. Do I shorten file name?

Scott
[Nexus 7 (2013) General] ScOULaris:
So, to anybody who has gotten the update who previously had random reboots... has the update resolved that problem?

My Nexus 7 was doing fine for weeks with no reboots until last night. I hadn't recently installed any new apps or anything. Once it did it the first time, it would start randomly rebooting pretty frequently after that. I'd say it has rebooted four times in the last hour or so of usage.

The only thing that I did recently before this started happening was flash stock recovery back on there to get ready for the OTA. I doubt that could have anything to do with it, though.
[Nexus 7 (2013) General] chocowilliam:
How to update to JSS15Q without losing data and root? The instructions on the previous posts never worked for me. Do I need to revert to a stock kernel?
[Nexus 7 (2013) General] kenyee:
That's not good. I was hoping this update fixed the reboots which honestly bothered me more than the other issues. I returned my N7 which didn't have the multi-touch issues, but it did random lockup/watchdog timer reboots...
[Nexus 7 (2013) General] chaco81:
hey bud, thanks for the download... i just tried with TWRP and it failed at the end. which recovery you used to flash it??
[Nexus 7 (2013) General] ScottPV:
This works great:

http://xdaforums.com/showthread.php?t=2416438
[Nexus 7 (2013) General] acdcking12345:
Confirmed. Did the same thing and all is well. Went smoothly and my tablet seems to be fantastic. Let's see if it stays that way.
[Nexus 7 (2013) General] roy827:
You can only use this ota update, when 1) unrooted , 2) no system file modifications, 3)no kernel change 4) original recovery

use stock recovery to abd/sideload the ota file to update.

---------- Post added at 03:13 PM ---------- Previous post was at 03:06 PM ----------

You can only use this ota update, when 1) unrooted , 2) no system file modifications, 3)no kernel change 4) original recovery

Use

stock recovery

to abd/sideload the ota file to update.
[Nexus 7 (2013) General] RedDevils88:
It seems that this have solved my gps issue. Hope that it stays this way. :)
[Nexus 7 (2013) General] Melodycd:
I cant sideload OTA. When i enter "adb reboot recovery" it loads into the black screen with android logo and exclamation mark, and it is written - "no command". (( I have nothing more on the screen, so i can't choose "With Volume Down, highlight “apply update from ADB.”". What am i doing wrong? I am fully stock, bootloader is locked.
[Nexus 7 (2013) General] bozzykid:
Huh? You can apply an OTA update on a rooted Nexus 7.
[Nexus 7 (2013) General] chrismast:
If I understand well, yes you can, whereas should you have modified system files and/or custom recovery it will most likely fail.
[Nexus 7 (2013) General] roy827:
it seems that after 4.3 i cant update when rooted... my trial was a failure...

通过 Nexus 4 发表
[Nexus 7 (2013) General] AnarchoXen:
Yes..just do this. Takes a few secs and works via TWRP. :good:
[Nexus 7 (2013) General] Melodycd:
I can't update on stock. Did you manage to do it? I don't know why, after entering recovery mode, i dont have menu to choose - sideload. Only andrid-robot with exclamation mark. Sorry for double post! Just need to pass Nexus to my mom soon, she is waiting for me to fix multitouch issue.
[Nexus 7 (2013) General] poisike:
OTA link > http://android.clients.google.com/p....signed-razor-JSS15Q-from-JSS15J.7533fcdf.zip
[Nexus 7 (2013) General] Zylograth:
OTA URL:

http://android.clients.google.com/p....signed-razor-JSS15Q-from-JSS15J.7533fcdf.zip
[Nexus 7 (2013) General] chiikko561:
So if I don't want to unlock or root I just need to wait right ...

Sent 4rm my Paranoid Nexus 4.3 LTE...
[Nexus 7 (2013) General] poisike:
You don't need to be unlocked or rooted to sideload the update.
[Nexus 7 (2013) General] Origin8:
I have applied the JSS15Q update and I'm proud to say the multi-touch issues have vanished on my Nexus 7! I did a YAMTT test and tried the same test I did that would make my screen glitch and it doesn't do it anymore. GPS always worked on my N7 but I tested it again and it works flawlessly. So far so good!

Quick question, if I unlocked my bootloader, can I still receive OTAs?
[Nexus 7 (2013) General] Melodycd:
So i found a solution for those like me who have "no device" message after entering command "adb sideload...".

The problem is:

1. If you have only android logo and exclamation mark only, you are not in recovery yet. Press POWER + VOL UP until you see menu with different commands.

After that Windows will find new device and will ask for drivers.

2. Download drivers from this link http://xdaforums.com/showthread.php?t=2391236 . Download the one that is attached to the post. ADB_driver.zip

After installing those drivers, you will be able to sideload.
[Nexus 7 (2013) General] odobo:
mind to elaborate how this work on a rooted nexus 7? :D
[Nexus 7 (2013) General] Melodycd:
So after update i still have issues with touchscreen. Everything almost the same. There is a "dead" area, when i touch it, the touches becomes really mad )) Nothing is fixed for me. First experiense with Pure Google devices. ((
[Nexus 7 (2013) General] ScOULaris:
Correct me if I'm wrong, but can't you just download the update.zip to your root directory and then apply it from the stock recovery?

That's what I used to do when I didn't feel like waiting to receive OTA's on my old Nexus S. I believe there's an Apply Update option in stock recovery that looks for an update.zip in the root directory.
[Nexus 7 (2013) General] sfhub:
Thanks, Update #2 in first post now includes

JSS15J -> JSS15Q update url

Credit given

We STILL NEED

JWR66N -> JSS15Q OTA url
[Nexus 7 (2013) General] sfhub:
Thanks, credit given, see Update #2
[Nexus 7 (2013) General] :
Couldn't the people on JWR66N (as a workaround) sideload the update to JSS15J and then from there sideload to JSS15Q?

Just used ADB Sideload to flash the JSS15Q.

Update successful, but multitouch issues still linger.

Unfortunately, this tablet is going to be returned very soon.

Haven't tested GPS yet, here's hoping at least that works.
[Nexus 7 (2013) General] sfhub:
Yes, unlocked bootloader can receive otas

However if you deviate from stock by modifying or removing files from the ROM, future OTAs will likely fail. Adding files is normally ok.
[Nexus 7 (2013) General] hawkye:
It sounds like you have a hardware issue and need a replacement. I have zero touchscreen issues and finally the GPS is working properly.
[Nexus 7 (2013) General] SubMatrix:
Based on what I'm hearing it sounds like there are two scenarios for how the OTA affects people who had touch issues:

1. You had no multitouch issues pre-OTA, only single touch issues. In other words, when you are not holding the tablet and it is unplugged, sometimes/often single touches are not registered. I would classify the digitizer as being not sensitive enough. After the OTA, these issues remain.

2. You had crazy multitouch issues manifesting as either phantom touches or severe jittering, especially when having two touch points cross axes (easily visualized in YAMTT). I would classify the digitizer as being over sensitive. After the OTA, many report their issues are fixed, though some still have problems.

I am in the former camp, unfortunately. I am curious if the people who are in the latter camp, who "have no problems" indeed also have no single touch problems when not holding the tablet after the OTA.
[Nexus 7 (2013) General] sfhub:
I didn't write in immense detail but Update #5 in the first post has a mini guide that addresses your issues

The reason you don't have a menu is it is hidden by fallen android

You need to press/hold Power, then press/release VolUp, then release Power, in that exact sequence to display the recovery menu.

You will likely also need to install adb drivers which have been fixed to work in recovery (also in the mini guide)
[Nexus 7 (2013) General] sfhub:
The second category is further broken up into those that had noticeable multi-touch issues in JWR66N and those that only noticed multi-touch starting in JSS15J.

The latter appear to be resolved in this update while the former appear to have nod improvement, which makes sense if what they did was to rollback multi-touch to JWR66N

In my experience dead spots are not always accompanied by multi-touch issues, so they might be separate issues. Often you might have both but not always.
[Nexus 7 (2013) General] SubMatrix:
I have another N7 which is still on JWR66N, and has multitouch issues, but no dead spots. I'll be curious to see how JSS15Q affects it.
[Nexus 7 (2013) General] sfhub:
See Update #3 in first post
[Nexus 7 (2013) General] chiikko561:
Is the update file Only 10.71 mb

Sent 4rm my Nexus 7 FLO... Only thing missing is O.G. N7's development...
[Nexus 7 (2013) General] sfhub:
See Update #3 of first post for why it failed at end and a fix.
[Nexus 7 (2013) General] Summit1:
Just flashed the odex version from http://xdaforums.com/showthread.php?t=2416438 using TWRP. I didn't have bad touch issues before, but the new version touch points are liquid smooth and more sensitive . . . on par with the original Nexus 7 running 4.2.2.
[Nexus 7 (2013) General] sfhub:
The JSS15J -> JSS15Q ota update is 10.71 mb

The JWR66N -> JSS15Q ota update (which we don't have a link for) will likely be around 50 - 60 mb
[Nexus 7 (2013) General] dkb218:
Wait so 10 billion post say its a software issue and because you interpret one post to mean a hardware issue, you follow that one?

Is your N7 still having problems after the update because it's in a case? On a table? Is it possible you may not be apply the same pressure to the screen you would if it were held in your hand? I can't think of one conceivable reason why just putting the N7 in a case or on a table would change the touch input. Is the table or case grounding out the device is some way? Is laying it flat somehow causing the digitizer to separate from the screen? Is gravity the culprit?

I have zero issue with my N7. Not trying to clown anyone.
[Nexus 7 (2013) General] Hnk1:
After installing the new update on my Nexus 32 GB , June build with no multi touch issues, one speaker dead (no sound comes n it was like that as bought) showed no relative change in touch issues but I guess sound has improved on my only working speaker.

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.)

All google apps updated even when i had switched off auto updates.

In sleep, nothing is downloaded from google play but works if the screen is turned on.

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 I forced update manually.

Other than that I guess there is no difference.
[Nexus 7 (2013) General] sfhub:
IMO there are hardware variances which are affected by software/driver controllable parameters but there are some variances that are too great to be resolved by the current "fix"

Whether these variances can be resolved with further tweaking or should be considered defective is not known at this point.

Capacitative touch screen don't really work by pressure. They pass small current through your finger resulting in voltage drop that is recorded.
[Nexus 7 (2013) General] ch0mch0m:
Anyone able to sideload JSS15J -> JSS15Q patch? Keep failing for me.
[Nexus 7 (2013) General] sfhub:
If your issue is unknown device named flo see sideload miniguide in Update #5 of the first post for drivers to use adb in recovery

If your issue is it gets near the end and fails on permissions, you are probably rooted, see Update #3
[Nexus 7 (2013) General] Coronado is dead:
This isn't necessarily directed at you: I wish people who said that they had no issues with their touch screens were as quick to post videos as those who do. I've yet to see somebody post a video using their tablet on a table or on a bed or on the couch doing single swipes back and forth showing that all swipes register on the home screen. Or even doing single swipes/touches and yet another multitouch test to show that all swipes/touches register.

I've tried multiple devices from multiple sellers, and they all had the issue after the J update.
[Nexus 7 (2013) General] ch0mch0m:
My error is none of the above, it's in TWRP actually. I'm rooted with TWRP installed, that's why I didn't do the OTA update, nothing show up for update check, and tried to do the sideload manually.

I rebooted into recovery, TWRP in this case, and put it into ADB sideload mode, do the sideload command from adb on PC to send the file over.
[Nexus 7 (2013) General] bracketologist:
I'm in the first camp. I just posted in the Google forum on this. Like sfhub said, the single touch problems are very apparent in the top third of the screen when in portrait. I had these problems before and after the update. I used the JSS15Q factory image.
[Nexus 7 (2013) General] lespaulman67:
So what ver. was you on before updating to the JSS15Q.
[Nexus 7 (2013) General] sfhub:
Are you on JSS15J OR JWR66N?

the ota link we have so far only patches against JSS15J base

If you are on JSS15J have you installed anything custom? The install is complaining that file is different from what is in stock JSS15J
[Nexus 7 (2013) General] ScOULaris:
Anybody know if the update fixes the random reboot issue?
[Nexus 7 (2013) General] boykomac:
Looks like I need the stock JSS15J kernel. Tried sideloading the OTA from JSS15J to JSS15Q - it complains about some file in boot. Only thing besides supersu is the custom kernel I'm running, need to revert to stock kernel and try sideloading again.
[Nexus 7 (2013) General] Melodycd:
Yes, I should replace it, but Amazon refuse to issue prepayed not from US. :mad:

I wanted to try Nexus devices for last 2 years. But now I am really upset because of hardware issues. My Kindle Fire HD is much better in terms of build quality. :cool:
[Nexus 7 (2013) General] iGoogleNexus:
Hmmm I'm trying to enter recovery mode but I can't seem to boot into it... Its still holding "Power, Vol. Up + Vol. Dwn" right?

Haven't unlocked boot loader or anything...
[Nexus 7 (2013) General] timrock:
power and volume down.
[Nexus 7 (2013) General] iGoogleNexus:
Thank you! Lol
[Nexus 7 (2013) General] sfhub:
Yes, definitely it will fail because of custom kernel because new kernel is shipped as patch of old JSS15J kernel.
[Nexus 7 (2013) General] boykomac:
Thanks, I'm now downloading the stock JSS15J images, any pointer on how to flash boot.img is appreciated :)