yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) General] dgm9sf:
Bluetooth Keyboard Works Fine on Android 4.2.2

Just replaced the N7.2 that I sent back a month ago with another (now that the keyboard problem appears to be software related). It came with Android 4.1 which worked perfectly with my Logitech bluetooth keyboard. Upgraded to Android 4.2.2 and everything still works perfectly.

Apparently, the "download updates automatically" switch is on because I have a persistent message that tells me the an Android update has been downloaded and is ready to install that I am concerned will update to 4.3 (the message doesn't say which version) that will break the bluetooth keyboard functionality.

Any comments on this 4.2 vs 4.3 difference with bluetooth keyboards?

Any suggestions on how to delete the version update and block the message so I won't inadvertently "upgrade" to a broken version?
[Nexus 7 (2013) General] chocowilliam:
TS10 didnt work for me. Lots of freezes, both app and touch. Though ghost touches are gone. Im trying TS20 now.
[Nexus 7 (2013) General] lpachuong:
It is just me or everyone has this problem? On TS10, with usb cable plugged in, the ghost issue disappeared and 10 fingers touch works perfectly fine. With usb cable unplugged, the ghost is back.
[Nexus 7 (2013) General] faizo:
And that's the part that worries me and makes me think there is a hardware side to this as well.

Bought N7 2nd gen few days ago and returned it prior to finding this fix on XDA. I'll be monitoring this and Google/Asus to see what final resolution, if any, will happen.

Otherwise, this is an amazing tablet!
[Nexus 7 (2013) General] DowntownJeffBrown:
Its cause the cable is grounding the tablet. The same way where you won't get touch screen issues while holding the device because its grounded. Also no not everyone has this problem.

Sent from my Nexus 7 using Xparent BlueTapatalk 2
[Nexus 7 (2013) General] sfhub:
reboot

su

dmesg | grep panel

From my experience I've only seen JDI panels, even though the source code is set up to handle other types.

Panel is different from touchscreen digitizer, we all have elan touchscreen
[Nexus 7 (2013) General] desmondso99:
JSS15Q

issues: part of the screen wasnt very responsive, freezes when typing and ghost touches

i have tried boot-ts10-lock.img and most of them no longer exist. Ghost touches occasionally happen but it is bearable

i really appreciate it
[Nexus 7 (2013) General] jak3z:
Anyone found a way to test for touchscreen issues that can be replicated 100%?

I saw some youtube videos and tried to replicate some issues but I never had such issues, but sometimes I feel like the touchscreen didn't work perfectly, but not sure if it's app related or touchscreen related.
[Nexus 7 (2013) General] Oliv3:
Try Yet Another Multi Touch Test. Landscape mode it, run one finger along the right side of the screen from top to bottom (back and forth) at a normal usage speed.
[Nexus 7 (2013) General] jak3z:
Just with 1 finger? Nothing happens O_o All normal.

Looks like everything is ok, I tried moving with 1 finger on the left and one on the right up and down close to eachother, and sometimes very randomly the Touch 2 swap to a Touch 3 event, and after some seconds goes back to Touch 2, but it never jumps around or goes wild, just acts as if I had lifted the finger for a millisecond.
[Nexus 7 (2013) General] Oliv3:
I never had Multi touch issues. I went through 3 tablets, 2 were July/models and 1 Aug/Model. I was able to produce 1 finger ghost/phantom touches on the right side of the screen in landscape mode every time, and also sometimes dead spots.

If yours seems fine to you then that's a good thing. because once you find that spot/area that is wrong, it's just gonna bug you.
[Nexus 7 (2013) General] jak3z:
Yeah thought so that it was fine, I even used TWRP knowing the risk of breaking my touchscreen, but looks like I got lucky, I will keep doing some tests, since sometimes I don't if I accidentally push a wrong key or it's a undesired input.
[Nexus 7 (2013) General] sfhub:
Either you are confused or bought the wrong tablet, those version #s don't match the N7.2
[Nexus 7 (2013) General] sfhub:
It shouldn't freeze.

If you haven't done so try ts10 or ts20 overnight sprinkling in a healthy amount of reboot fairy dust.
[Nexus 7 (2013) General] chocowilliam:
After a couple of reboots should the instabilities will be gone?
[Nexus 7 (2013) General] AHomelessGuy:
ts10 was working nicely for about a week, now it's becoming wonky again... looks like I'm going to revert to Stock soon and relock my bootloader so I can exchange for another one at Walmart.
[Nexus 7 (2013) General] lomonic:
seems to work better

I never had major issues to begin with, and yamtt tool tested, with no ghosting etc. Google maps and earth rotates and zoom alright for me. But sometimes in chrome, something just seemed a little cookoo. Such as missed touches or simply not very responsive overall. I also find the edge and bottom of the screen highly sensitive where touches on the bezel triggers an action in the system itself.

I did not observe any difference using it in the hands or on a flat surface. Nevertheless I installed ts10 just for the sake of testing and the fact that I am rooted. I'm beginning to notice some degree of improvement, definitely in the department of responsiveness:cool:. Gonna keep it for a while and see how it works on a longer term.

That said, is the ts-unlock equivalent to the 15Q update?
[Nexus 7 (2013) General] gorgeri:
Hi sfhub!

Thanks for the images. The ts10 and the unlocked image works normally most of the time with very rare touchscreen issues.

However, I have noticed that when the tablet gets warm, like after playing 15 minutes of Max Payne, the touch sensing becomes very bad.

After I quit Max Payne, on the left side where the tab is warm, when I swipe up and down, ocassionally a second touch appears making Chrome unusable with left thumb.

I have also wrote it to the Nexus 7 touch screen issue google group.

Thanks,

Geri
[Nexus 7 (2013) General] sfhub:
After ts-unlock, you'll have whichever version came with your ROM. If you are on JSS15Q ROM, then that is what you'll have, JSS15J would get that version, and so on. That is for stock. For custom ROMs, it depends what kernel the ROM creator used to put their ROM together.
[Nexus 7 (2013) General] sfhub:
Yes, they should. If not, then your touchscreen is probably just too out of spec to be dealt with currently and I'd exchange or return it if you find it still unusable.
[Nexus 7 (2013) General] sfhub:
Voltage and current properties can change as things heat up placing the values the touchscreen software is processing out of spec. Ideally they should be able to handle many situations, but in reality some screens may be too out of spec to be dealt with.
[Nexus 7 (2013) General] lomonic:
Sounds good. Thank you. An update after trialling ts-10 for a day, i've reverted back to default. Ts-10 is more responsive, and works very well with single touches. but with multitouches, it is starting to exhibit some weird behaviours and especially so in YAMTT. i'm getting squiggly lines near bottom right of the tablet with 2 fingers, and sensitivity with multitouch cross-over of axis.

Overall it's a good solution for those having problems, but i don't think it will benefit much to those who didnt have major issues to begin with.
[Nexus 7 (2013) General] neonlite:
i have the exact same issue, bottom right seems like a deadspot. after a reboot everything seems fine. but after a while it starts again. but its way better than the original.
[Nexus 7 (2013) General] bandit_knight:
I can see reports about new OTA update (JSS15R) being released. It's rumored to provide further fix to the touch issues. How could it affect me if I use ts10 on my device and I am pretty happy with it. Shall I revert to stock before applying the new update?
[Nexus 7 (2013) General] sfhub:
You will keep ts10 unless you want that to change.

If you want the touchscreen software in JSS15R, you can boot ts-unlock before or after the update, doesn't matter. Of course, until you unlock, you'll still be running ts10.

My advice if you are happy with ts10, just keep running it. Wait until reports come in on new touchscreen software. If reports are good, then boot ts-unlock.
[Nexus 7 (2013) General] roy827:
Updated

Hello, Sfhub my star.

I updated the JSS15R and found everything completely smooth (was using your TS10, which works fine but sometimes the screen overreacts...)

The update file (that is, from JSS15Q to Jss15R) in Cache folder is attached, try it with sideload. Also i used boot-ts-unlock.img before update.

hugs!:)
[Nexus 7 (2013) General] lespaulman67:
Can you tell me how to side load this new update. I was wondering if you can do it with boot loader locked. Seems like I did the JSS15Q on a previous N7 i had without unlocking boot loader. It worked but forgot how to. lol
[Nexus 7 (2013) General] sfhub:
there is a mini guide to refresh your memory in the download section of this post

http://xdaforums.com/showthread.php?t=2448015
[Nexus 7 (2013) General] lespaulman67:
Thanks I found it. Well the new update screwed my Nexus 7 2013 up again dead spots on screen. Had to load Ts10 fix again.
[Nexus 7 (2013) General] Skinnysloth:
The 15R update did not fix my touch issues. It was better than 15Q, but I still had some dead spots. I went back to TS11 and all is well again.
[Nexus 7 (2013) General] sfhub:
It was verified on the JSS15R thread that the touchscreen software in JSS15R is unchanged from JSS15Q
[Nexus 7 (2013) General] Nbsss:
Do you need to flash TS etc after changing kernels or flashing boot.img?
[Nexus 7 (2013) General] NekroWolfen:
That happened to me, but I'm late for a return anyways... I've been with it for over month now.
[Nexus 7 (2013) General] sfhub:
Once you find one that works OK for you, it will stay in place unless you flash ts-unlock.

You can flash different kernels, boot.img, etc, the ts touchscreen software will remain.
[Nexus 7 (2013) General] thunderger:
Tried all three boot images but don't have luck. Bought my N7 yesterday at local german distributor 'Media Markt', updated it to JSS15Q (OTA) and got some ghosting and mad responsive using three or more fingers creating "overlapping" lines.

TS-10 same behaviour as original. TS-20 more strange with some ghostings. TS-30 madness.

Today I'll return my N7 to my local distributor and get another one. They've left around 15 N7 in stock. :D
[Nexus 7 (2013) General] bandit_knight:
I am afraid this kind of behavior you will get with a new one too. I can observe a similar level of jumpiness when placing 3 or more fingers on overlaping axes on my Gnex and S3 (with SuperNexus ROM). I haven't noticed these issues for more than a year before reading about them on this forum and checking the screen in YAMTT :) I guess that may just be normal. Do you see any problem with it in apps? For instance can you easily rotate map in GMaps? Do you test when holding your device in your hand or on a table/bed/flat surface. In the later case the behavior will problably get even worse because of lack of grounding.

With my N7 I had only noticeable problems with stuck touches and freezes. Those were fixed by sfhub's ts10.
[Nexus 7 (2013) General] iCEION:
This is my touch problem.

Same behavior on JSS15Q and JSS15R and the one before.

It seems to not register touch properly in the top right corner depending on where I place the tablet... any comments on that?
[Nexus 7 (2013) General] thunderger:
Thanks for your hint. I tested it holding the N7 in one hand and using my other five fingers, with charger plugged in and laying on my table. Only with plugged in cable I don't have any issues. If I hold it in one hand, I can notice that sometimes a three-finger-input is recognized as a wrong two-finger-input showing a diagonal line. Drawing with three or four fingers will sometimes lead to a mad responsive, e.g. showing randomly and rapidly changing from one up to six or seven touches.

I tried with my N4 as reference and there aren't such strange behaviours. For me, it's okay that the touchscreen gets in trouble if my fingers are very close to each other but overlapping axis, disappearing touch points, etc. are a no go.

I hope that I get a better device.
[Nexus 7 (2013) General] gogol:
Why don't Google learn from this thread to fix the touch issue!
[Nexus 7 (2013) General] DowntownJeffBrown:
Looks to me like you are on JSS15Q not JSS15R

Sent from my HTC One using Xparent Red Tapatalk 2
[Nexus 7 (2013) General] iCEION:
I was on JSS15Q when I recorded the video, but that really isn't the point! I'm on JSS15R now and the problem persists. I just didn't record a new video just for that. If the problem was solved with JSS15R i wouldn't ask for input.
[Nexus 7 (2013) General] player911:
Once you flash 15Q, the touchscreen gets updated to the buggy driver. At that point, you will have issues no matter what rom you use. I tried flashing back to 15R and it was too late. It only UPGRADES and doesn't allow downgrades unless you force flash one of the tweaked files from this thread.

ts10 is working pretty good for me. It still gets goofy occasionally when typing alot. It starts to get "sloppy" and inserting lots of extra characters. I find that I can just turn off the screen and turn it back on, it clears it all up and I can go about typing accurately.

It rarely happens. Maybe once every 4-5 days.
[Nexus 7 (2013) General] chocowilliam:
I too experience missed touches, will they get fixed too? Multi touch problems are now gone.
[Nexus 7 (2013) General] Nbsss:
Which TS is the one that corresponds to the build just before jss15q?

I had no issues out of the box and the 2 immediate OTAs. The ota that was meant to fix the GPS gave me stuck touches. TS10 is really responsive and fixed the stuck touches but is a bit glitchy at times, though has settled down lately eg. The rare multiple touches that appear when swiping in a straight line. (I have dev options set to show them touch inputs)

So yeah, if anyone knows what I'm talking about I'd appreciate the help :)
[Nexus 7 (2013) General] sfhub:
Try ts20
[Nexus 7 (2013) General] undercover:
Last update fixed multi touch for me. Also, haven't noticed any missed touches, grounded or not. Yay.
[Nexus 7 (2013) General] bandit_knight:
Please let me know if you do. If there are better devices out there I will send mine for repair :) Unfortunately I am out of replacement option.
[Nexus 7 (2013) General] thunderger:
I was lucky. :) Yesterday I got my new N7 and it has no touch issues running JSS15J build. No issues after upgrading to JSS15Q and still no issues after installing newest CM10.2 nightlys.

I saw that a "batch" number on its packaging was increased from 8 to 9 but I don't know if there are more than the inital batch out in the wild. It can be fortune.
[Nexus 7 (2013) General] cocchiararo:
Since the 15R update was available, i installed the ts-unlock, rebooted twice, applied the 15Q factory image without wipe (i needed to get back the stock kernel and recovery, just in case), and applied the 15R update.

I played some Jetpack Joyride and noticed 1 sticky touch in 20 minutes of gameplay.

It seems better than 15Q, but ts-10 is still the best.
[Nexus 7 (2013) General] PJ Clifford:
Interesting! I did not have touch problems until 15q. After the upgrade, my TS got flaky like a lot of other people have reported. I tried ts10, but found it ridiculously sensitive. [sidebar] When playing with ts10, I found that that I could register a touch on the screen with a finger about a 1/16-inch ABOVE the touch screen. This was incredibly annoying as I seldom touch from a precise 90° angle to the tablet and was getting touches registered at other locations other than the one that I was going for. [/sidebar] I put on ts20 and everything seemed to go back to "normal". Fascinating that ts20 equates to the update prior to 15q, where I didn't have problems!
[Nexus 7 (2013) General] furou:
This is awesome! I'm on jss15r, stock everything.. just flashed ts10 and multi touch has been improved by so much.

My main benchmark is using google maps. Before, while placing the nexus on my bed I couldn't use maps because of all the ghost touches. Trying to rotate the maps would drive it crazy. Now it actually works, although once in a while it still double taps if my fingers are too close. Multi touch looks better in YAMTT as well.. I'm really happy, thank you sfhub! :good:

Should I try ts20 to see if I can completely eliminate the ghost touches? There's no issue trying ts20 and then going back to ts10, yes?
[Nexus 7 (2013) General] PJ Clifford:
None at all. I switched back and forth between those two several times and everything held together!
[Nexus 7 (2013) General] player911:
ts10 works great but still getting occasional freakouts. I don't know what causes it and it seems to last about 30seconds where any tap goes crazy. I can cycle the screen off/on and it will fix it or I can wait and it will correct itself.

It isn't apparent during regular use but noticeable when doing heavy typing or game playing.

Pretty complicated trying to play Terraria.

I might try ts20 tomorrow to see if that helps anything. ts10 feels perfect except for the occasional quirks.

I hope Google has a solid fix for everyone sooner then later.
[Nexus 7 (2013) General] trvbone:
Just wanted to come in and say R update seems to be a winner here!
[Nexus 7 (2013) General] psylock:
Hi,

When I bought my nexus, it updated the first time I booted, to JSS15Q I didn't have any problem with the touchscreen at all, some random reboots (using bittorrent app). I checked the touch with 'Multi-Touch test' and all worked properly.

Two days ago I updated to JSS15R by sideload (no wipes at all), and I started experiencing some problems with the touch screen, maps app went crazy when the tablet was lying horizontally and I had a lot of reboots. Maybe caused to the non-clean update. But, when it is usb-hooked to my laptop it works perfect.

Now, I just try all ts-images and the touchscreen is working the same, even worse it cannot detect the 10 fingers, but 7-8 fingers. Otherwise what I'm gonna do it's to flash JSS15Q and stay there until Google pronounces themselves about this problem.

Reading some other boards, I believe that some tablet stock are faulty either because a hardware problem and also a software problem (with the touchscreen driver).

As a matter of fact, my screen is a JDI panel.

Regards!
[Nexus 7 (2013) General] Jester Minute:
Sadly for me versions 10,20, 30 and the new 'R' firmware all have touch issues.

(i'm using Nexus 7 II tester to spot ghost touches).

Third one i've had now sadly, the curse of the early adopter :)

Ant
[Nexus 7 (2013) General] dgm9sf:
Yep, Wrong N7

Ordered "like new N7 (2013)". Recieved N7 (2012) with scratched screen.

Another poor result from Amazon.

Thanks for the quick diagnosis.
[Nexus 7 (2013) General] mi7chy:
My history.

Q OTA introduced sticky touches. J was still relatively new but don't recall any annoyances.

ts10 with Q OTA didn't experience sticky touches but had other issues like difficulty of hold pressing to open a link in a new browser tab, browser seems to sometimes register input elsewhere, etc. (4th best of everything tried)

ts-unlock with R OTA reintroduced sticky touches but everything else seem fine. (3rd best)

ts11 with R OTA only had minor issues such as requiring very precise touches and ~15 second pause while playing Great Big Wargame. (2nd best)

Still looking for 1st best and will try ts20.

Too bad this touch annoyance and Modern Combat 3 exiting game on level 10 possibly from overheat tarnish an otherwise nice tablet.
[Nexus 7 (2013) General] Skinnysloth:
Those of you who are not getting satisfactory results with ts10, 20, or 30 should try out the experimental builds, the ts11, 12, 14, 16, 18, 25. Ts10 initially worked well for me, but had occasional dead bands/spots. Tried ts11 and the dead bands went away. I still get ghost touches, but only when I use three or more touches that are lined up. Since I rarely ever use more than two fingers all aligned in a row, this is a non-issue for me.
[Nexus 7 (2013) General] player911:
Finally updated to ts-20 (from ts-10) and the occasional freak out seems to be fixed. I've been playing Terraria for about 2 hours and not one problem. I've been playing with YAMMT and while it still freaks out when you palm rest the screen with 10+ touches, it seems just fine for 9 fingers. This, in the real world, is not a problem for me.

I haven't flashed the new 15R software yet, but really no need. I'll put ts-20 through its paces but if it can play a touch-heavy game for 2 hours without any hiccups, then I'm happy.
[Nexus 7 (2013) General] brashmadcap:
32GB Deb bootloop

Any of these sent my 32gb deb/LTE into a bootloop on carbon rom

Will try with stock

update: flashed back to stock on deb and it just bootloops basically even on a completely stock rom
[Nexus 7 (2013) General] sfhub:
I am not understanding the bootloop part. By design, you are NOT flashing these onto your persistent storage, just doing temporary boot, then you reboot and are back to using your original software,
[Nexus 7 (2013) General] brashmadcap:
So for instance I'll:

#fastboot boot boot-ts20-lock.img

Then the device will reboot, and just hang for like 5 minutes. Just the splash screen. Then I wait and wait and wait some more. Then I finally did an "adb reboot" and it rebooted to the GUI. So if I'm not "flashing" this onto persistent storage, what exactly is happening. And when you say "back to using your original software" what do you mean? I doubt this is actually the case but the way you put that indicates that we may have to flash this every time despite the original post saying that this is survivable.
[Nexus 7 (2013) General] sfhub:
Let me be clearer.

fastboot boot boot-ts20-lock.img will temporarily boot into the included kernel. This will load the touchscreen software.

Once you do a reboot, you will be back to using your original kernel (but the touchscreen software is loaded and won't change)

The boot-ts kernel's job is just to load the touchscreen software. The boot-ts kernel is not required once the touchscreen software is loaded. Once you get past the Google splash screen, the touchscreen software is loaded and won't change (unless you want it to)

When you say it hangs on the splash screen, do you mean the Google splash or the X splash? If the X splash, everything will still work, just reboot and you will be running your original software, which shouldn't hang. The touchscreen software already loaded if you got past the Google screen, so even though you are using your original software, boot-ts already did its job and you will be using the ts[10,20,30] touchscreen software.

If you are hanging at the Google screen, then I'd need to investigate further.
[Nexus 7 (2013) General] Coronado is dead:
Hey guys, I keep my booloader unlocked and my N7 rooted.

My father in law however also has a N7 and wants this fix. I can install the ts10 file for him and then RELOCK the bootloader, yes? And it will stick even thorough official Google updates? He will be keeping the stock recovery as well.

Just making sure I understand this for his device. Mine I am a bit fmore free with since I keep it open.

Thanks!
[Nexus 7 (2013) General] sfhub:
Yes and Yes
[Nexus 7 (2013) General] Coronado is dead:
sfhub, you rock. His touchscreen is perfect again, and not to relock and let him take R :)
[Nexus 7 (2013) General] brashmadcap:
Don't worry it's hanging at the X not the Google screen. Not to worry I think all is good right now

Worst part is I think my device is defective I've tried them all ;[ so back to Google mine goes! Thanks for all your help!
[Nexus 7 (2013) General] gizmik:
Thank you google, you really trying hard to make my device useless, with every update :/

Out of the box touchscreen worked perfect, without flaws, after first update (JSS15Q) I experienced problems with touchscreen, then I flashed ts20 and everything worked fine after that again. Now I was stupid enough to update to newest JSS15R and now I have problems with touchscreen again, but now none of the images correct it completely. Thank you google, one more time -_-