yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] afremont:
Ok then, well I was hoping for something a little more detailed, but thanks for the reply. Now that I've found my way to ektf3k.c and the HOWTO for building ROMs and kernels, we'll see if I can't persuade it to just flash it whenever the kernel supplied firmware version is different and not just when it has increased. Provided I don't brick my tablet first. ;)

Do you know if any changes were made outside the firmware that would explain my wife's tablet working better after backing up to the JSS15J release? She was praising it last night, nary a complaint. She had plenty to say after the Q update though.
[Nexus 7 (2013) General] sfhub:
BTW I'm not disputing you (or your wife) are seeing something different in your restored JSS15J. I'm just saying it isn't because of the firmware. The firmware runs independent of the ROM and kernel and communicates with the kernel using interrupts.

There's an embedded system in there processing and filtering your touchscreen actions. If this was Motorola's exaggerated market-speak they might even call it a 5th "core" like they do for their other dedicated co-processors.

If the firmware isn't loaded onto the embedded controller, it isn't running and therefore cannot be the cause of what you are seeing. Your log proves that your earlier firmware wasn't loaded and you are still running the 42 firmware from JSS15Q.

Seeing as the firmware is the same now on your JSS15J build as it was on the JSS15Q build, but performing ok, you may actually want to go back into JSS15Q, do a factory reset, and try again, loading nothing at first and not even signing into your wife's google account. You might just find everything works fine even though before it didn't.
[Nexus 7 (2013) General] fergiet:
Same problem with mine, just got it on Friday. UK 32gb on latest OTA. Long presses often fail to respond and touching an app to open can take a few tries. May send it back and wait a couple of months to see if it's a software or hardware issue then reorder.

Google/Asus need to sort it quickly. :confused:
[Nexus 7 (2013) General] sfhub:
Try this post:

Take that multi-touch! Fix and lock in what works for YOU regardless of updates
[Nexus 7 (2013) General] bandit_knight:
I noticed today that my Macbook Pro can with 100% reproducibility trigger the multitouch issue. It's enough to place my N7 on the MBP keyboard and try to touch it with more than two fingers. Then the screen starts to act crazy.

See the video:

http://www.youtube.com/watch?v=H05N1P0dpTo

I tried the same with my Galaxy Nexus and IPad 3rd gen. None suffers from the same issue as the N7.

Apart from this my N7's touchscreen works pretty ok. It only suffers from very rare stuck touch issues that were introduced by the latest update. I can also see some "shaky" behavior in mutltouch test apps when trying to touch with more than two fingers on the same axis but this has never shown up for me in regular apps.

I do believe that this is really a hardware issue that Google is trying to mitigate with some software tricks.
[Nexus 7 (2013) General] player911:
I agree. I found a factory reset helped some.
[Nexus 7 (2013) General] cocchiararo:
would it make ANY sense for me to do a factory reset, even tho i loaded the factory image and started from scratch ?

I only have the sticky touch issue, and yesterday the tablet froze 3 times while playing JetPack Joyride (and came back to like and continued playing, all by itself)
[Nexus 7 (2013) General] afremont:
I assume that you have Google Apps installed. Make sure you have Location Reporting turned off. Plus the WiFi part of location services will make use of the WiFi "even when turned off", unless you uncheck that option as well.
[Nexus 7 (2013) General] Igorsep:
Will do that as soon as I get home! Till then I'll pray. Thanks!
[Nexus 7 (2013) General] afremont:
Following up with my firmware rollback attempts. I modified ektf3k.c to reflash the firmware whenever the version number is different. Here is some dmesg output showing apparent success:

<4>[ 0.249114] [ELAN] Touch dirver register

<4>[ 1.166351] [ektf3k]:[elan] elan_ktf3k_ts_init

<4>[ 1.166687] [ektf3k]:[ELAN] Start HW reset!

<4>[ 1.426879] [ektf3k]:[elan]detect intr=>Old FW

<4>[ 1.427093] [ektf3k]:The boot code is old!

<4>[ 1.457061] [ektf3k]:[elan] __hello_packet_handler: hello packet 55:55:55:55

<4>[ 1.457153] [ektf3k]:[elan] hello packet's rc = 0

<4>[ 1.669128] [ektf3k]:[elan] __fw_packet_handler: flashed firmware version: 0xa042

<4>[ 1.671264] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x007e

<4>[ 1.673309] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00d2

<4>[ 1.675415] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029

<4>[ 1.677459] [ektf3k]:[elan] __fw_packet_handler: boot code id: 0x6047

<4>[ 1.677673] [ektf3k]:[Elan] Max X=2239, Max Y=1343

<6>[ 1.677978] input: elan-touchscreen as /devices/virtual/input/input0

<4>[ 1.678405] [ektf3k]:[ELAN]Mike is looking at the firmware!!

<4>[ 1.678527] [ektf3k]:The firmware supplied in kernel is version 0xA038 and id:0x3029

<4>[ 1.678710] [ektf3k]:Start firmware update!

<4>[ 1.678833] [ektf3k]:[ELAN] Start HW reset!

<4>[ 1.706848] [ektf3k]:Send command into IAP mode

<4>[ 1.816955] [ektf3k]:pages_number=367

<4>[ 1.822723] [ektf3k]:sendI2CPacket send 132 bytes

<4>[ 1.856994] [ektf3k]:recvI2CPacket recv 2 bytes: aa aa

<4>[ 1.862792] [ektf3k]:sendI2CPacket send 132 bytes

<4>[ 1.897003] [ektf3k]:recvI2CPacket recv 2 bytes: aa aa

...... a bunch of lines of this for 15 of the longest seconds in my life

<4>[ 16.462829] [ektf3k]:sendI2CPacket send 132 bytes

<4>[ 16.497100] [ektf3k]:recvI2CPacket recv 2 bytes: aa aa

<4>[ 16.497192] [ektf3k]:[ELAN] Start HW reset!

<4>[ 16.999664] [ektf3k]:[elan] firmware_update_header: hello packet 55:55:55:55

<4>[ 17.001678] [ektf3k]:[elan] __fw_packet_handler: flashed firmware version: 0xa038

<4>[ 17.003784] [ektf3k]:[elan] __fw_packet_handler: X resolution: 0x007e

<4>[ 17.005798] [ektf3k]:[elan] __fw_packet_handler: Y resolution: 0x00d2

<4>[ 17.007812] [ektf3k]:[elan] __fw_packet_handler: firmware id: 0x3029

<4>[ 17.009918] [ektf3k]:[elan] __fw_packet_handler: boot code id: 0x6047

<4>[ 17.010040] [ektf3k]:Finish the touch firmware update!

<4>[ 17.010253] [ektf3k]: /proc/ektf_dbg created

<4>[ 17.010742] [ektf3k]:[elan] Start touchscreen elan-touchscreen in interrupt mode

<4>[ 17.011016] [ektf3k]:[ELAN]misc_register finished!!

<6>[ 17.011138] elan-ktf3k 3-0010: Update power source to 1

:victory:
[Nexus 7 (2013) General] Elvind Anderson:
You are lucky got a great hardware Nexus 7 :)
[Nexus 7 (2013) General] cocchiararo:
So... you can now change touchfirmware to any higher/lower version ?

How do you change it ? I would love to be able to try the ones that came with JWR66N and JSS15J. (i am on 15Q now, rooted of course)
[Nexus 7 (2013) General] afremont:
I had to modify the actual driver so it's a big hassle to do since you have to build a custom ROM. It was more of a let-me-see-if-I-can-do-this kind of thing.

sfhub has a technique that lets you try 3 different setting and then lock them in. I wish he'd tell us how he locks the changes in. ;)

Try here:

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) General] danvee:
Random guess?

As firmware flashes 'up', he might have chosen very high version numbers: higher than they would under normal naming convention.

Again, nothing but a wild, yet logical, guess.
[Nexus 7 (2013) General] cocchiararo:
i guessed the same.

I flashed ts-10 and sticky touches seem gone (ROM remains JSS15Q)
[Nexus 7 (2013) General] danvee:
Right, as he's only doing the digitizer firmware. It shouldn't change.
[Nexus 7 (2013) General] sfhub:
Looks like Google closed the mobile help subforum and consolidated everything under the Nexus subforums.

Apparently they consider multi-touch and random restarts ongoing issues as the topics were moved, while GPS was left on the old forum. Everything on the old forum is now marked read-only.

Anyway, updated the links in first post.
[Nexus 7 (2013) General] player911:
Yea this really helps. TS-10 made my N7 feel whole again.
[Nexus 7 (2013) General] Linuxslate:
I am now getting 1 or 2 random reboots a day since my N7(2013) got "infected" with JS15Q.

I don't think I ever had a spontaneous reboot on the prev. firmware.

(100% stock - never unlocked BL, never rooted, never installed a ROM other than official OTA's.)
[Nexus 7 (2013) General] sfhub:
It could be some app you are running (that you weren't running before) triggering a bug in the rom, causing the reboot.

There were some releases where Chrome would trigger reboots 30-60 mins after I last used, sometimes when the tablet was just idling. Chrome was the "trigger" in my usage pattern, but others have there own "trigger" apps. Once I stopped using Chrome, the reboots went away (again, for my usage pattern, others may be different)
[Nexus 7 (2013) General] ANGEL4RIM:
Guys I need help.

I can't update to ota via sideload . everytime i trying get this error

assert failed: apply-patch-check("/system/framework/android.policy.jar" , "380fxxxx

E: Error executing updater binary in zip

I've never flashed any Roms I just rooted with stock 15j. I did though flashed mode APM maybe that's the problem . I did follow every step in the op

Also when I try to flash factory images with adb I get error saying the system img is missing ,but its not I checked .

Any help ?
[Nexus 7 (2013) General] sfhub:
Yes, it was APM that is causing your issue.

I fixed this for someone else here. You can use the same if you want to use the ota.

http://xdaforums.com/showthread.php?p=44928915#post44928915

If you want to use the factory image, see this post:

http://xdaforums.com/showthread.php?p=44888268#post44888268
[Nexus 7 (2013) General] ANGEL4RIM:
O man thank you very much. I rally appreciate your help.

I'll flash that mode today in twrp and try again . by the way is having twrp while updating ota bad or good ? Should I flash stock recovery back to apply ota update ?

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

By the way I remember I flashed inverted dark theme Google play store in twrp . is that gonna make error in ota ?
[Nexus 7 (2013) General] sfhub:
Regarding recovery, stock recovery is safest. With custom recovery like twrp, it is best to wait until someone else has tried the version you plan to use. In this case, twrp 2.6.0.0 has definitely been tested to work ok. I don't know if 2.6.1.0 (2.6.1.1) has got as much testing. They switched from a stock kernel to using their own built kernel. Not that there is anything wrong with that, but the more changes you make the more chances for problems to be introduced.

If the thing you flashed required TWRP to install, chances are it changed something in the ROM which will then cause OTA error. Look in the zip you flashed. Look at any files in the system directory in the zip. If you find some, those will probably need to be reverted. .png/.jpg/etc probably will not cause issues, but .jar, .odex, .conf, lib*, etc. will all cause issues.
[Nexus 7 (2013) General] trvbone:
Hey guys what's APM?

Oh is it advanced power menu?
[Nexus 7 (2013) General] ANGEL4RIM:
Thank you very much. I have twrp 2.6.0.0 and I just flashed the update ota zip and everything an went smoothly with no error .

I noticed that root app supersu is no longer working . it says there's no binary . is there a fix ?

---------- Post added at 08:17 PM ---------- Previous post was at 08:16 PM ----------

Yes its advanced power menu.
[Nexus 7 (2013) General] sfhub:
Just reflash SuperSU from here:

http://download.chainfire.eu/supersu

Actually if you flashed SuperSU immediately after the OTA (before rebooting), then you wouldn't lose root nor have to reflash TWRP.
[Nexus 7 (2013) General] ANGEL4RIM:
Thanks all working good. :)

Yes after the update, twrp did ask me if I wanted to fix the root but didn't think it would be neccesary since I already update the app from play store.
[Nexus 7 (2013) General] elad1111:
PRNG fix

Can you elaborate where can I find the PRNG fixed code.

I am looking on 4.3 dev, or androidxref JB 4.3

Is this fix the problem for all applications using SecureRandom?

I supposed I will find it in engineGenerateSeed on the SecureRandom class (or lower), However I found nothing.

Thanks.
[Nexus 7 (2013) General] sfhub:
I'm on mobile right now so it is hard to research but just looking at what I posted in the past, I believe I might be mistaken.

The sample code appears to assume it is fixed in SDK versions > 18. For some reason I read that as "= 18" instead of "> 18"

http://xdaforums.com/showthread.php?p=44945937#post44945937

They code dropped SDK 18 into our release.

So it appears this might not be fixed until SDK 19 drops, however the randomness of Google play songs seems to have happened, but that might be at the application level.

When I have time I'll go back and see if I can figure out what is going on.
[Nexus 7 (2013) General] steenbt:
Rolled back to JSS15J

I got a system update last night. I was on JSS15Q now I am back to JSS15J!

Anybody else?
[Nexus 7 (2013) General] sfhub:
Did this really just happen? Sorry, my jaw is still on the ground. Must pick up before I can say anything.
[Nexus 7 (2013) General] danvee:
Still on Q here.

Forced a recheck and no updates shown.
[Nexus 7 (2013) General] jhuff83:
I have TWRP and did as you said but update still fails.
[Nexus 7 (2013) General] sfhub:
So you used TWRP, chose Install, then selected the OTA update.zip, correct?

What was the error from the install log? I just need the last few lines that indicate the error.
[Nexus 7 (2013) General] jhuff83:
Correct.

assert failed: apply_patch_check

E:Error executing updater binary in zip /sdcard/OTA update.zip

Error flashing zip /sdcard/OTA update.zip

I'm using TWRP 2.6.0.0 and supersu 1.6.5. Don't know if it matters but I'm using faux kernel as well.
[Nexus 7 (2013) General] sfhub:
Does it make a difference if you don't have a "space" in the filename?
[Nexus 7 (2013) General] jhuff83:
Changed it and it still failed.

gives a long error ("EMMC:dev/block/platform/msm_sdcc.1/by-name/boot:7045120:e809f9.............

Then when I reboot system it states root permissions appear to be lost. Fix root permissions now? I swipe to fix and it reboots for me.
[Nexus 7 (2013) General] sfhub:
Ok, your first error was caused by the filename.

The new error you listed here is because your kernel is not what the OTA update is expecting.

If you are running the JWR66N->JSS15Q update, then your kernel needs to be stock JWR66N.

If you are running the JSS15J->JSS15Q update, then your kernel needs to be stock JSS15J.

You can find the stock kernels in the download section of the first post. Install the correct one using

fastboot flash boot boot.img

You can also consider using the factory image restore, which doesn't care what versions you are running because it will just overwrite things.
[Nexus 7 (2013) General] jhuff83:
I went back to the toolkit and reflashed stock kernel. Update took after that. Thanks for the help. Reflashing faux kernel now.
[Nexus 7 (2013) General] cocchiararo:
You can also just get the 15R factory image :P

15R did not fix my sticky touch issues, went back to ts-10 fix.
[Nexus 7 (2013) General] karandevilocs:
hey guys i got the new nexus 7 today and i tested some stuff to see if they work properly !

when i set it up it was on JWR66N and i tested touch / gps / wifi by YAMTT / GPSTest / WifiAnalyzer and multi touch was ok and wi-fi was superb BUT gps didn't work at all didn't even received the gps signals ..

the i updated to JSS15R and tested stuff again this time MULTITOUCH bug appeared (jumpy multi-touch) / wi-fi was the same / and gps improved and received signals but it didn't lock on any of them ...

my question is that should i try some TRICKs or stuff to see if my multi-touch work on latest one OR should i download JWR66N and reinstall it?!

and the 3rd option to send it back...

PLEASE Help ...

UPDATE: i restarted the tablet and now the buggy touch is gone ... is this a temporary thing ?!

+ screenshot of YAMTT on Nexus 7 :

+ screenshot of YAMTT on S4 :

as you can see the "P" on my s4s is 1.000 and on nexus is something less ! what is that ?!
[Nexus 7 (2013) General] sfhub:
Buggy multi-touch could be temporary or it could be persistent. Depends on your screen. If it isn't bothering you right now, don't worry about it. If it starts misbehaving again, you need to look at this thread (downgrading to JWR66N very likely won't help)

http://xdaforums.com/showthread.php?t=2428133
[Nexus 7 (2013) General] karandevilocs:
FOR NOW everything work just fine gps worked again (i was testing it in door :P) and no reboots / freezes or screen flicks and i've never seen any touch bug after restart ...

i just fear that after REPLACE DEADLINE TIME (it's tomorrow) it start showing some weird stuff and bugs!

and are there some test that could push boundaries and make it work hard that may show the future bugs right now?!

like something that maybe make it buggy like installing an app or backup /restoring!
[Nexus 7 (2013) General] .MoHaMaD:
JWR66N->JSS15R OTA

https://docs.google.com/file/d/0B1A2pY6wsXejVU13ZDBJNllOM1U/edit?usp=sharing
[Nexus 7 (2013) General] onesolo:
Does this thread is the one to report/talk about the latests official images for N7II ?? Why the title remains with the previous image version?
[Nexus 7 (2013) General] sfhub:
JSS15R is discussed here:

http://xdaforums.com/showthread.php?t=2448015
[Nexus 7 (2013) General] geckocavemen:
There is already a fix for rooted with custom recovery in the first post...
[Nexus 7 (2013) General] sfhub:
To restore stock recovery:

adb reboot bootloader

You can also power down, then press/hold Power+VolDown until you see the bootloader screen

fastboot flash recovery recovery.img

You can grab stock recovery from this post. Unzip and place recovery.img in you adb/fastboot directory

http://xdaforums.com/showthread.php?p=44597339#post44597339
[Nexus 7 (2013) General] bailyc:
Does anyone know if I'll be able to apply the OTA update from JWR66N if my device is one that was experiencing the JSS15J update failure? I tried applying the fix in this thread and I still couldn't get it to work, so I just decided to wait for the next update. Thanks!
[Nexus 7 (2013) General] :
If you would like to, I believe you can flash an OTA with a custom recovery (see instructions at end of linked post):

http://www.droid-life.com/2013/08/21/download-android-4-3-jwr66y-ota-updates-for-the-nexus-7-hspa-galaxy-nexus/#more-117742

EDIT: If you want to switch, though, sfhub's post is making it sound easy!
[Nexus 7 (2013) General] sfhub:
See update #5 in first post
[Nexus 7 (2013) General] Aerys:
Google start pushing it to our devices please:crying:
[Nexus 7 (2013) General] :
+1.

This OTA rollout doesn't seem widespread at all, at this point.
[Nexus 7 (2013) General] Tony_YYZ:
It should work just fine. It has to because any new devices on the shelves right now have JWR66N and will need the update as well.
[Nexus 7 (2013) General] sfhub:
It will likely fail for the same reason as one or more of your stock files were somehow coming back with unexpected sha1 hash code(s)
[Nexus 7 (2013) General] bailyc:
Hm, that's what I was afraid of. What's the best course of action? I was a bit lazy after the fix from that thread failed to allow an OTA update, but I guess I just need to wait for the official, full factory image and flash that, then replace as much apps+data as possible?
[Nexus 7 (2013) General] sfhub:
You could

try figuring out what file is bad

try restoring jwr66n twrp/nandroid backup someone posted

flash google factory jss15j image

There are ways to do it w/o wiping data, but only if you are already unlocked
[Nexus 7 (2013) General] rhinosaurus:
At this point is it still recommended to only apply the first ota update then?
[Nexus 7 (2013) General] :
Out of the box? Not necessarily. Does not matter what build you are on at this point, you will receive the OTA and this should fix your problems.

That said, I advise you avoid JSS15J, which should have been pulled anyway.
[Nexus 7 (2013) General] sfhub:
If by "first" you mean the mandatory update that happens right after you enter wifi info, yes that is the only generally available update at the moment.

The second update JSS15J got pulled (though you could still manually install if you desired) For folks who never had multi-touch issues in JWR66N they will probably be ok with JSS15J and would be able to run netflix.

However the 3rd update (or the "new" second) JSS15Q has just started rolling out so if you are patient this is the one you should try even if you need to wait a day or two.
[Nexus 7 (2013) General] rhinosaurus:
Perfect thank you. My tab is in my mailbox... On my way to get it now :)
[Nexus 7 (2013) General] :
Have fun! You're going to love it!
[Nexus 7 (2013) General] cyberprodigy:
Damn it feels good to be right about the touchscreen issues being software. Sucks for all the impatient people who returned their tablets.
[Nexus 7 (2013) General] :
Lots of 14 day return periods were expiring... What if it was hardware? They would be stuck with a tablet that didn't work well AND was unreturnable.

And I reserve judgment on the issue being fully software until a large group of people try the OTA and verify that it solves their multitouch issues.
[Nexus 7 (2013) General] spmode:
If I download the update from a link, can I just adb sideload it or flash it through CWM, or do I have to restore the stock recovery and then adb sideload?
[Nexus 7 (2013) General] nexusisneecesary:
Didn't the multi-touch issue show up with the 4.2 update on the OG nexus 7?

sent through space time.
[Nexus 7 (2013) General] :
If I remember correctly some OG N7 devices has them on launch day and still do have them.
[Nexus 7 (2013) General] bailyc:
Thanks for the suggestions. I am unlocked and rooted now as well and can use Titanium Backup if needed, so I'll probably just go with the factory image route once it becomes available.
[Nexus 7 (2013) General] :
Look at my post here: http://xdaforums.com/showpost.php?p=44881791&postcount=649
[Nexus 7 (2013) General] nexusisneecesary:
Maybe, for some reason I always thought it was software issue.. Oh well. I could be wrong.

sent through space time.
[Nexus 7 (2013) General] cyberprodigy:
Two questions

1. Is it necessary to have stock recovery installed to get the OTA update?

2. What steps should I perform before installing?
[Nexus 7 (2013) General] :
I'm not sure, all I know is that a couple of my friends had issues long before 4.2 on their OG devices. I didn't own an OG myself, I boycott Tegra. :P

---------- Post added at 01:25 PM ---------- Previous post was at 01:23 PM ----------

1. Doesn't look like it.

2. Look at my post here: http://xdaforums.com/showpost.php?p=44881791&postcount=649
[Nexus 7 (2013) General] sfhub:
As the other poster mentioned, I would reserve judgment also. There are definitely hardware variances in the touchscreen (to be expected)

From my experience if you had no touch screen issues with JWR66N then you wouldn't have any issues with JSS15J. If you slight issues with JWR66N then they became more noticeable on JSS15J.

This update could potentially:

fix the problem for everyone

alleviate the problem to the point most will not notice it

alleviate the problem so the fewer notice it unless they had it real bad to start

make the problem better for some and worse for others

Hopefully it is the first or second situation.
[Nexus 7 (2013) General] sfhub:
I guess another option is to wait for them to eventually replace the JSS15J factory image with JSS15Q which seems logical, but may or may not happen.
[Nexus 7 (2013) General] :
The fact that this OTA should fix the multitouch issue definitely came as a real shocker to me, with all the proposed grounding solutions indicating it was probably hardware, or a mix of both hardware and software.
[Nexus 7 (2013) General] nexusisneecesary:
I am having an issue on build jss15j with it not properly recording my screen on time. It's been showing two and a half hours screen on time for the past 30 minutes anyone else experience this?

sent through space time.