yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] bobafuzz:
Just got another N7, fired up YAMTT no issue, spent 15 minute drawing circles and square, no ghost touches. Decided that I should update to the newest firmware, I need to know if this is related to the latest build. No problem so far. I'm in the process of restoring all my backup and try out some games with multitouch, I'll report back if anything changes.

Update edit: Been playing around with multitouch and noticed that I'm getting an extra touch when doing 2 point multitouch at the X axis and the tablet is laid flat on a table, it's not as bad as before, no issue when I'm holding it in my hand though. I guess I can live with that.
[Nexus 7 (2013) Q&A] Rod3:
I am in the same boat. Had a perfect 16 GB, decided I would return it for the 32 GB, and that device was just like in your video. Multi touch app would continue well after removing your fingers. Returned again for another 32, and so far so good. Holding off on the update until it can be confirmed as not causing problems.
[Nexus 7 (2013) Q&A] canoo:
Are you running it on battery or plugged in?
[Nexus 7 (2013) Q&A] bobafuzz:
Battery.
[Nexus 7 (2013) Q&A] i486:
Well, my before perfect capacitive panel, started now showing some issues. Let's hope Google doesn't make us wait to long for the fix.
[Nexus 7 (2013) Q&A] JayBomb999:
Without a doubt, JSS15J is a problem.

I ran JMR66V build for a little over 48 hours straight without a hiccup. I decided to take the plunge and finally update to build JSS15J and... it's back. :(:( Erratic multitouch is undeniably back and linked to the latest update.

At this point, I am 100% convinced that software is at least partially a factor. I say "partially" because the jumpiness is equivalent to my 3rd device, though my 1st and 2nd were much more erratic. (None were as bad as bobafuzz's video however.)

So for me, that settle's it. 2 days on JMR66V, perfect. 5 minutes on JSS15J, erratic jank. The software is, at least partially, borked.
[Nexus 7 (2013) Q&A] metal571:
Same problem here with a play store N7. I never tried the older update though. Can we get a system dump from someone with JWR66V ASAP?
[Nexus 7 (2013) Q&A] canoo:
Someone did create a system dump. I have too few posts to put a link here but it's on page 13.

It was made from a 32GB model though. Don't know if it'll work on a 16GB model.
[Nexus 7 (2013) Q&A] metal571:
Oh yeah saw that. Was looking for a 16 GB one then.
[Nexus 7 (2013) Q&A] ShadowEO:
Noticed that the 4.3 Stock system that came on my model was a bit over-sensitive, however it seems that my batch will force you to update. I couldn't skip the first update and then it asked me to install a second. I didn't think to check on stock but YAMTT on PA 3.91 didn't have the issue at all.
[Nexus 7 (2013) Q&A] Obveron:
I experienced my first erratic touch symptom today. I was single pressing the view button in es file manager and it was instead selecting the exit button. Also I was trying to highlight a file by pressing and holding but it was instead selecting the Android notification buttons.

Nothing was working right in other apps, all was unusable, but the locations of the errors were consistent.

It's worth noting, this happened while I was in direct and very hot sunlight.... And it seemed to go away when as soon as I found some cool windy shade.

Just a one time occurance so far, so I don't know if they are connected.
[Nexus 7 (2013) Q&A] mcguinness89:
The problem completely disappeared once I unrooted my Nexus 7. Must have something to do with root in some cases considering I factory reset into 3 different Roms, including stock, and it still didn't disappear until I unrooted and locked the bootloader.
[Nexus 7 (2013) Q&A] JayBomb999:
I personally have never rooted this device.

I just don't know what to think anymore.
[Nexus 7 (2013) Q&A] boykomac:
So you are saying it is temperature dependent? Can anyone else who has a "bad" unit verify this please? Will be an interesting finding if confirmed.
[Nexus 7 (2013) Q&A] Rod3:
Took the plunge and updated my replaced 32 GB, and so far no touch issues like I had on the device that was replaced.
[Nexus 7 (2013) Q&A] mcguinness89:
If you haven't tried factory resetting your Nexus yet I would do that. But before you do that, since this problem was a grounding issue on some 1st generation Nexi, try holding onto the back and squeezing while typing. One of those methods should tell you what your real problem is.
[Nexus 7 (2013) Q&A] JayBomb999:
For the lucky folks without issues, would you mine doing a slow push to expand (opposite of pinch to zoom) in a browser? I'm curious if people are just dismissing small jumps as "android being android".

I may just be very sensitive to the slightest hiccup. Especially when I know they need not be there.

Thanks.
[Nexus 7 (2013) Q&A] canoo:
This is very interesting. I just tried crossing X/Y axes in YAMTT with my thumbs (using a bit more force than normal) while tightly gripping the device in the back with my hands. The issue seems to be much less severe. It acted very similar to how it does while plugged in.

As soon as I lightly hold the device in one hand and try crossing X/Y axes with my thumb and index finger with my other hand, the problem appears again.

Interested to see if this is the case with anyone else who is also having multitouch issues.
[Nexus 7 (2013) Q&A] rafa3L:
You're right. More pressure and I experience less erratic behavior. A noticeable difference. In my opinion this is not a good sign and leaning towards hardware. I could be wrong, I'm not sure if there is software calibration regarding sensitivity.
[Nexus 7 (2013) Q&A] Lolento:
Erratic multitouch only happens in portrait mode for me so this must be software issue.
[Nexus 7 (2013) Q&A] rafa3L:
Put it in landscape mode and spread your two fingers out wider (left right) instead of taller (top bottom). Now do you have the issue?
[Nexus 7 (2013) Q&A] metal571:
I have thee issue in landscape mode very clearly.
[Nexus 7 (2013) Q&A] Stanlehh:
is it safe to update to JSS15J from JWR66N?
[Nexus 7 (2013) Q&A] delfin2003:
Just wanted to say that I'm in the same boat with all of you who have erratic touches. I actually didn't know about this until i started playing with google maps and noticed that it was almost impossible pinch to zoom, zoom out etc. without having maps screen go crazy. Downloaded the multi-touch test app and realized that with two finger touches I actually see a third random touch on the screen go in and out! Googled and found this thread instantly! WOW. I am hoping this is software related and will give google another 10 days to fix this until I go and exchange it for another one...
[Nexus 7 (2013) Q&A] JayBomb999:
I asked a colleague to bring in his N7. He claimed to have no issues and I wanted to actually SEE a device on the latest build without touch problems.

His device works perfectly. The latest build, bought the same day, at the same store and he has no problems that I can see.

Curiouser and curiouser.
[Nexus 7 (2013) Q&A] canoo:
There was a post on the Google groups thread that seems to make the most sense to me. I can't link (too few posts so i'll just quote it).

This could explain why the problem is worse for some people and non existent for others. Google might have played with the voltage to the digitizer in the JSS15J update who knows. If this is the actual problem it should be fixable in an update. I was going to try exchanging mine today but it doesn't seem like much use. I'll hang onto it for now. still have about 10 days. c'mon Google...
[Nexus 7 (2013) Q&A] iorikun:
My first N7 which I got on the launch day had the same issue (vertical multi touch broken) which only happens when not plugged in.

I was waiting for a fix, but decided to replace it @ the store and stick with 66N for now (which seems to work perfectly fine). I'm thinking it's more grounding issue rather than voltage level.
[Nexus 7 (2013) Q&A] canoo:
If if were a grounding issue I would think that a software update wouldn't affect the tablet. The problem should be present no matter what right? ¯\_(ツ)_/¯ I'm just completely speculating...
[Nexus 7 (2013) Q&A] iorikun:
I think it all depends on how the digitizer is configured. It's possible to have the sensitivity just a tad bit high to trip over the stable ground point which your holding hands (or just static air) could provide (thus problem more problematic when laying flat on the surface without a hand holding it). I would think the digitizer driver could be configured to filter out any erratic samples when the digitizer is not grounded properly (at the price of losing some sensitivity).

But I'm on the same boat as you are. Just completely speculating at this point.
[Nexus 7 (2013) Q&A] mcguinness89:
The problem most definitely is a grounding issue. Squeeze the device from the front and back and you will notice that the touch screen functions properly for a little while, but once the pressure goes away most of the touches will not work. Just returned my Nexus 7 to Best Buy and they told me lots of people having the same issue and are returning. I guess I'll wait for the next Galaxy Note to come out, or until the problem is fixed.
[Nexus 7 (2013) Q&A] delfin2003:
Called google nexus support. A young lady on the other end was not aware of the issue but she said she will forward it to her supervisor.
[Nexus 7 (2013) Q&A] kentondb:
I'm an all Apple guy (2011 iMac/2012 MacBook Air/3rd gen iPad/iPhone 5) and I can't tell you guys HOW MUCH I DON'T WANT TO RETURN THIS TABLET.

I love this thing but damn the touch screen....
[Nexus 7 (2013) Q&A] :
I couldn't play games like Shadowgun or Absolute RC Heli and didn't dare bind the tablet to my Parrot A.R. Drone. I returned mine today, they had none left in store so I took my money back. I had decided to wait for a fix on a previous tablet that shall remain nameless, the fix never came and my warrant expired. So I will wait for stock to get in and see how this turns out. Back to the old N7 2012 for now.
[Nexus 7 (2013) Q&A] stimr2:
I agree it's a grounding issue. Never noticed it untilI got a tablet stand. Also have the issue when I place it on certain flat surfaces. Works fine when I'm actually holding it or plugged it.

I remeber my Galaxy Nexus had mutli-touch issues when it first came out.
[Nexus 7 (2013) Q&A] parmend:
So do you guys think its a wide spread issue or just a few bad ones? Some people say they have no issues . just curious because I will buy one if these in a few days .
[Nexus 7 (2013) Q&A] stimr2:
I think its pretty wide spread. The op is on his third one and it still has the issue. There a lot complaints on the google products forum as well. Digital Trends has a article listing the various problems with the new Nexus 7 and the multi touch is one of them. http://www.digitaltrends.com/mobile/google-nexus-7-problems/?redirect_override=true#comments
[Nexus 7 (2013) Q&A] kentondb:
Why did none of the reviewers (Ars, Anandtech, etc) not see this issue?

Can someone with better English inform them for assistance?
[Sony Xperia T, TL, TX, V] Warrior1988:
Just copy the Mms.apk to system/apps and fix permissions then reboot you might have to rename your other messaging apps to mms.bak or conversations.bak depending on Rom This is 4.1.2 version. If you want newer version and awesome Rom check out this Rom made by Peetr_ http://xdaforums.com/showthread.php?t=2240485
[Sony Xperia T, TL, TX, V] dully79:
As opposed to?
[Sony Xperia T, TL, TX, V] Warrior1988:
It's totally customizable.
[Sony Xperia T, TL, TX, V] dully79:
How?
[Sony Xperia T, TL, TX, V] Warrior1988:
You have can setup your colors for text background in the settings etc.
[Sony Xperia T, TL, TX, V] exeon:
Screenshot please.
[Sony Xperia T, TL, TX, V] dully79:
So i take it you cant do that with normal AOSP Mms.apk?

Why didnt you say that in the OP with screenshots?
[Sony Xperia T, TL, TX, V] Warrior1988:
Updating op soon yes fully working all around.
[Sony Xperia T, TL, TX, V] Warrior1988:
Added keep in mind you can customize the colors.
[Google Chromecast] Chugworth:
I want to something that should be quite simple and line up perfectly with what the Chromecast is designed to do:

I want to play an MP4 video from a URL.

Yet so far I have not seen a good way to do this. I wonder how much trouble it would be to write a simple app that does nothing but blast a URL to the device.
[Google Chromecast] bengadget:
A ton of people are doing this exact thing. What methods are you using? Are you talking about blasting a URL from a phone to the CC? Bypassing the need to cast a tab from a PC? I'm not sure that's possible yet.
[Google Chromecast] Chugworth:
Yes, I don't want to use Chrome extension at all. I just want to connect to the device and send it a URL. Is that so much to ask?

So, for example, I could just have a small command... Let's say "chromecast.exe". I would open a command window and type something like:

chromecast deviceIP videoURL

chromecast deviceIP pause

chromecast deviceIP play

That basic functionality would lead to greater things.

I wonder, is the Chromecast listening on a specific port that I could send some sort of command to? In a quick skim of the Cast API, I'm not seeing what I'm looking for.
[Google Chromecast] orionshock:
I predict a simple "sharing app" that allows you to do just that. Although I suspect it will be in fused with bloat and be called a media player :\
[Google Chromecast] moocow1452:
Could you tear down the call API, and use a bookmarklet or something?
[One (M7) Android Development] xdracco:
Aloha Forum,

Nothing revolutionary here but in cooking my ROM, I created a small script to enable/disable the persistent power notification in the notification drawer. This could be used during and post install. So here you go, enjoy....

Usage:

To enable: $ power-notification enable

To disable: $ power-notification

#!/system/bin/sh

state="disable";
if [ $1 == "enable" ];
then
state="enable";
fi;

pm ${state} com.htc.htcpowermanager/.powersaver.PowerSaverNotificationReceiver;

##
## EOF
##

I just got tired of having to hunt down the command (yea yea yea, i could have bookmarked it) with each rom install.

XDA Mods: If this has already been posted, please close it with link to duplicate thread please.

Aloha!
[One (M7) Android Development] mielnoir:
Where and how to insert or activate the script?
[One (M7) Android Development] andybones:
From what I can see, this seems to be an init.d script

It basically just allows you to edit the init.d script to enable/disable the notification, rather than having to adb shell, su, and then do the adb command to either enable or disable, or by using a terminal app from the play store, this seems much easier to just change out the word disable.

I think anyway..
[One (M7) Android Development] Magpir:
can u do something like modifying the htc power saver to reduce the time it goes into sleep mode?
[Nexus 4 Android Development] jlink38:
Reserved for KK kernel when released.
[Nexus 4 Android Development] jlink38:
Nexus 4 Stock (JWR66Y) and AOSP 4.3 Kernels
[Nexus 4 Android Development] jlink38:
Ladies and Gentlemen,

I requested this thread be moved here from the General section for better exposure. Hopefully more people can take advantage of it in between kernel flashes. Enjoy!
[Nexus 4 Android Development] Deleted member 4229013:
Exactly what I was searching for. Thanks a lot.
[Nexus 4 Android Development] priyam1309:
I am already running the 4.3 JWR66V kernel on Nex4, but want to change to JSS15J instead. Will just flashing the mentioned Kernel help me get this done??? Do I have to do a Wipe after flashing?
[Nexus 4 Android Development] hughfollett:
Nope.. You have to flash the entire rom if you want jss.. Flashing jss kernel on jw will cause problems..

Inviato dal mio Nexus 4
[Nexus 4 Android Development] priyam1309:
Can you help me out with a link to JSS15J based stock ROM?
[Nexus 4 Android Development] Holcomb227:
Here you go.

It already includes the stock JSS kernel.
[Nexus 4 Android Development] Jamal Ahmed:
@OP

Thanks a million for the stock kernels! We have so many custom kernels but rarely do we have completely stock ROM/kernel/radio/boot oader as flashable zips!

I appreciate your efforts a lot :)

I wanted to ask you a favour...

These seems to be no TOTALLY STOCK JSS ROM available atm.

Can you be so kind to compile for us a stock (flashable zip) of totally stock JSS with NO improvements at all? :) totally stock.

Each of JSS ROMs here seem to have this or that improvements or tweaks in them, which me (and most people I know) don't want. We just want a totally stock Google experience.

If you would kindly include such in the OP, it would be a gracious effort. Thanks :)
[Nexus 4 Android Development] kicksilver:
Thanks for providing this!
[Nexus 4 Android Development] philipepi:
I was about to ask something like that

thans man!!
[Nexus 4 Android Development] jlink38:
I am currently on vacation until Friday, and when I get back I'll give it a shot!
[Nexus 4 Android Development] C4SCA:
+1 for that idea.

U could make a thread somewhat like: "Everything stock JSS from top to bottom" or "Everything stock JSS inside out'

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Android Development] Sukhi:
Here it is : https://plus.google.com/u/0/1082629...CmkHa#108262968419038009038/posts/VoqdRjCmkHa

Credits : show-p1984
[Nexus 4 Android Development] jlink38:
Looks good! I was thinking of doing a minimalist build with the bare essential addons but every idea I've had was in other minimalist ROMs.
[Nexus 4 Android Development] pnut22r:
This is the equivalent of a kernel reset, correct? It replaces the ramdisk as well, correct?
[Nexus 4 Android Development] C4SCA:
Yep

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Android Development] jlink38:
Yes, which is important to flash when moving between two kernels with nonstock ramdisks.
[Nexus 4 Android Development] C4SCA:
[MENTION=3414783]jlink38[/MENTION] could u make a zip with JWR66Y kernel zip?

Some say there is some changes in the branch (read it on google +)

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Android Development] jlink38:
I'll take a look at the full update zip. The OTA doesn't have a boot.img included. I'm on my phone so I'll have to wait til I get home to check the full image.
[Nexus 4 Android Development] jlink38:
Just ran a hash check on the boot.img from both JWR66Y and JWR66V and they are identical. My zip is safe to flash with either! :good:
[Nexus 4 Android Development] apatal:
^

Nice to know I don't need to download it again. Cheers.
[Nexus 4 Android Development] C4SCA:
+1 here, thanks

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3).
[Nexus 4 Android Development] pixine786:
this is what i was exactly looking for.. thank you so much!!

had some problems with accepting call with Franco Kernel +
[Nexus 4 Android Development] ninosaxo:
great job!for try other custom kernel and revert to stock

little thinks make difference..thanks a lot!
[Nexus 4 Android Development] pikachukaki:
The stock JWR has root or its pure stock?
[Nexus 4 Android Development] apatal:
The OP shared stock kernels, not a ROM, so your question doesn't apply. :)
[Nexus 4 Android Development] pikachukaki:
With or without secure=0?i need to flash stock kernel but not lose root after that!!
[Nexus 4 Android Development] apatal:
Oh that! Yes, I believe these kernels are already insecure. :)
[Nexus 4 Android Development] pikachukaki:
Ok thanks for that....
[Nexus 4 Android Development] garth719:
I love you
[Nexus 4 Android Development] MaNFr3:
Can I use this on an AOSP 4.3 rom? in specifically for PA 3.99, i'm using faux kernel but i want to revert and stock PA kernel has colours that I don't like.

Thanks
[Nexus 4 Android Development] OhDae-su:
You can. Use the jwr one for PA.
[Nexus 4 Android Development] MaNFr3:
But it removes robot privileges it's right?

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Android Development] OhDae-su:
What privileges?! ;)

flashing a kernel doesn't effect root access if you mean that...

just flash the kernel in your custom recovery (without wiping anything) and you're good to go.
[Nexus 4 Android Development] MaNFr3:
Sorry but I can say that this flash remove my root access I don't know why! I had first disappoint when I start the device after flash and trickstermod (configurated for booting at start for previus kernel) say no root found. I've installed robot checker and it has confirmed that my device seems no rooted.

Inviato dal mio Nexus 4 con Tapatalk 4
[Nexus 4 Android Development] apatal:
How did you go about flashing this? My theory is that something from your previous kernel has caused havoc after flashing this one. I've used this kernel multiple times without encountering issues, as is expected from stock kernel. Try dirty flashing your ROM (and gapps) then this kernel and see if you still have issues.
[Nexus 4 Android Development] MaNFr3:
Nothing. I've just get root access using toolkits was the only way, thanks a lot either
[Nexus 4 Android Development] genkralyz:
is this the latest build for stock? tia

Sent from my N⁴
[Nexus 4 Android Development] C4SCA:
Yes!

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (stock 4.3). now Free
[Nexus 4 Android Development] jlink38:
I love you too. :highfive:

And yes, for stock, this is the most up to date.

I imagine my next update will be for the 4.4 update. Let's hope so!! :cool:
[Nexus 4 Android Development] jlink38:
Just flash the SuperSU or Superuser zip flash if your root disappears. No biggie.
[Nexus 4 Android Development] genkralyz:
I flashed the mako stock, and the latest build is jun 17? correct? tia ;)

Sent from my N⁴
[Nexus 4 Android Development] OhDae-su:
One page back you asked that already and still the answer is yes...
[Nexus 4 Android Development] genkralyz:
my bad. ;) I forgot.

Sent from my N⁴
[Nexus 4 Android Development] RohanM:
I flashed it JWR one & my device was in boot loop.,\. again flash the franko, device booted.
[Nexus 4 Android Development] C4SCA:
Be more specific....

What rom u running? U sure that ur rom isnt JSS and that franco is booting since there is a JSS version of it

sent from my NEXUS 4 tasting a revamped cooking recipe of Jellybeans (4.3).
[Nexus 4 Android Development] RohanM:
I am on carbon rom, JWR, never used any jss - I even dont know what jss is...
[Nexus 4 Android Development] jlink38:
Carbon is a JSS ROM so using a JWR kernel may have undesired results.
[Nexus 4 Android Development] RohanM:
Carbon is JWR since last 5 or 6 nightlys...
[Nexus 4 Android Development] apatal:
Franco's kernels modifies your system ramdisk. Make sure you dirty flash your ROM (and gapps, if needed) before flashing a new kernel on top of your current setup. Hope this helps. :)
[Nexus 4 Android Development] jlink38:
Had no idea. Just flashed it on my Nexus 4 and 7! It's so fast.
[Nexus 4 Android Development] jlink38:
OP updated with 4.4 Kit Kat kernel! Enjoy!
[Nexus 4 Android Development] Ostatni:
@UP

3.8 kernel?
[Nexus 4 Android Development] k0lega:
nope, the 3.4 from oct-18 that have been in all builds so far
[Nexus 4 Android Development] misterk267:
Can I ask if the 4.4 stock kernel has the fixed touch boost for mp-decision? I'm running the nexus 5 port and its great, but the kernel doesn't have touch boost.
[Nexus 4 Android Development] seven7xiaoyang:
+1

I want to use the touch control

---------- Post added at 02:21 AM ---------- Previous post was at 02:21 AM ----------

+1

I want to use the touch control:crying:
[Nexus 4 Android Development] misterk267:
If you're +1ing my post, I think you misunderstood. I'm not referring to touch control, I'm talkng about the touch boost feature of the interactive governor that boosts CPU to a certain frequency when the screen is touched.
[Nexus 4 Android Development] jlink38:
I don't know what to tell you buddy.
[Nexus 4 Android Development] jlink38:
I don't think it does. The showp1984 ROM has a fixed version of the kernel with touch boost working, as does AK100 kernel I believe.
[Nexus 4 Android Development] barome:
Do you have github to this ?