yashsingh1/xdaforums huggingface dataset:
[Nexus 7 (2013) Q&A] sauofee:
Hello Guys,

I'm experiencing issue with touch screen on my N7 (2013) 32gb, Build number: JSS15R , Unrooted

When I put my N7 on the pillow, or sofa (Not wood or metal surface) , the touch screen NOT responding in some area on screen (on the picture below), otherwise, when I hold my N7 in both hands or just one hand it seems to work just fine!

Do you have this issue or only me ?

Note: I used Multi-Touch test app (by TPYXA software) also for this test, and I did factory reset with no any apps install (only Multi-touch app)
[Nexus 7 (2013) Q&A] lespaulman67:
I was the first to post this. People think we are crazy. But you are right mine works perfect unless its on a pillow or couch or cloth. On the table it works perfect.

http://xdaforums.com/showthread.php?t=2448015&page=13
[Nexus 7 (2013) Q&A] fuser-invent:
Same here. Thought my Nexus 7 was fine for a couple weeks. I have no clue what could cause this but I've tested it a lot and it is definitely fine in my hands or on a hard surface and always really bad on a soft fabric surface. It makes no sense, maybe a hard case on the back would help? Has anyone with this problem tried that, are you using it with or without a case?
[Nexus 7 (2013) Q&A] sauofee:
What you think, is that hardware or software problem?
[Nexus 7 (2013) Q&A] roytse:
will this be caused by statics on certain fabric? (really wild guess):eek:
[Nexus 7 (2013) Q&A] lespaulman67:
I will tell you what I think. I think it has to do with the wireless charging coils in the back of the tablet.

I am using a slimline Moko case. I tried it out of the case and it still did same on couch and pillow. On solid surface works great.Is there anyone out there that has taken the Nexus 7 apart. Unplug the wireless charging see if it fixes the screen issues.
[Nexus 7 (2013) Q&A] Skinnysloth:
This problem is also known as the grounding issue, although some say that's not an accurate description. Regardless, I had this issue and this thread fixed it. http://xdaforums.com/showthread.php?t=2428133

Take a look and see if one of the files will fix your problem.
[Nexus 7 (2013) Q&A] Coronado is dead:
The ts10 file fixed this issue for me.
[Nexus 7 (2013) Q&A] Tim4:
Wow, just tried it and seems like you right.

Screen going nuts when placed on my bed.

When i touching it with all ten fingers, screen automatically turns off and on, endlessly sometimes.

Seems like thats a hardware problem, i dont think any app able to wake up the screen.

Just made a video. Sorry for quality, my dorm roommate havent back yet, so i were filming alone with power of my ankle.
[Nexus 7 (2013) Q&A] bokoy:
Google or asus or both should begin talking about this and what is the answer/solution they are going to give us. Mine is going to asus tomorrow, let's see what thy do. I know they have change screen, front and gps to another user, and did not even talk about gps problems at all, so they may know something.
[Nexus 7 (2013) Q&A] lespaulman67:
Wireless charging coils. Its causing a magnetic field on the back of the tablet. causing something like a grounding issue but really not.

If you take your USB cable and plug it in to your Nexus 7 and run the cord around the screen it will go nuts. It should not do that. Same with head phone plugged in to Nexus 7 and the head phone wire touches the screen it causes issues. There is a shielding problem. or its the wireless charging coils needing taken out.

Electromagnetic Interference

Large power lines, electric motors, kitchen appliances, and other devices may directly interfere with a display picture. Many devices are not properly shielded and their electromagnetic fields can cause disruption. Most modern display devices have sufficient shielding to prevent interference, but damage to the shielding may allow for signals to penetrate. Older displays and economy brands may have minimal shielding, leaving these devices vulnerable. Cables and audio/video equipment are also vulnerable to electromagnetic interference.

Read this guys

http://www.silabs.com/Support Documents/TechnicalDocs/Minimizing-Touchscreen-EMI.pdf
[Nexus 7 (2013) Q&A] sauofee:
@ lespaulman67

I agree with you :good:.

For me , when I plug my headphone into my N7 the problem with touch screen disappear even if I put it on Fabric ground.

Also, I have Galaxy Note II with QI wireless charging (QI wireless charger with the coil purchased from ebay 6 months ago), until now I don't have any issue with touch screen or charging itself.

Yes, I think the wireless coil caused touch issue.

Thank you all for the information , hope Google and Asus fix this very soon
[Nexus 7 (2013) Q&A] Tim4:
Here is a logcat for touchscreen fail and sudden screen off/on turning.

Not sure if i did it right though

Note that NFC turning on/off by itself as well.
[Nexus 7 (2013) Q&A] fuser-invent:
I have a couple of other tablets that I do amateur Dev work on, so I decided I can do without the nexus for a while and send it in for "repair" to see what happens. I'm curious to find out if they will change out any hardware or just flash a different firmware version and then send it back. I've tried every stock version if firmware with no luck, it seems to work fine for a couple if hour up to a day and the goes back to sucking. I'll report back in this thread when it gets mailed back and let everyone know what turn around time is like and if it actually helps. I have mentioned the ASUS customer service rep on live chat was excellent and its really easy to RMA it back.
[Nexus 7 (2013) Q&A] fuser-invent:
I got my tablet back from he service center. It was a pain, they shipped it to the wrong address and then fedex delivered it to a neighbor, had to retrieve it and re-deliver it. Turnaround time at the service center was only one day but shipping in both directions was about a week total.

Even though I requested it, there was no notes on what they did so I contacted customer service. They looked up the notes and told me they had to open the tablet to re-calibrate the touchscreen and also loaded a "newer driver" to fix the issue. They also said it was safe to update the firmware if a new version is released.

So far the tablet is fine but I'll report back after using it for longer to see if the issue really is fixed. If they had to open the tablet, that sounds like people with this particular issue do have to send it in for repair because no firmware update can fix it.
[Nexus 7 (2013) Q&A] sfhub:
Could you do me a favor?

assuming you are rooted, reboot your tablet

then type

su

dmesg | grep "ektf3k" | grep "firmware"

PM or post the output.
[Nexus 7 (2013) Q&A] fuser-invent:
What do you need from the output? That command doesn't work together but I can grep them separately. I'm not nearly set-up enough to copy/paste the dmesg, so I'll have to type it out for now. Relevant parts, let me know if you need more:

grep for firmware:

firmware version: 0xa042

firmware id: 0x3029

grep for ektf3k:

x resolution: 0x007e

y resolution: 0x00d2

boot code id: 0x6047

Max X=2239, Max Y=1343

Don't know if you need the rest but I'm guessing not.
[Nexus 7 (2013) Q&A] bokoy:
Mine got back from asus one week ago, they replaced screen, front and gps. Nothing was fixed, multitouch is still going mad, single touch is a bit improve, as before it works nearly well grounded but over a table or a sofa it works worst.

One friend got it back for a second time, the first time they did the same they have done to mine, now they changed main bd-2g, rear camera, screen, front and gps, 24hrs later he is reporting me that problems are back. Do you know what main bd -2g is? Motherboard?

Where did you type those commands?
[Nexus 7 (2013) Q&A] fuser-invent:
Just download any terminal emulator from the play store. I use this one.

As for the touch issues, mines obviously still got the multi-touch thing going on when you get several close fingers together. In my opinion that really has nothing to do with the Nexus 7. I've owned 8 tablets, not including the this Nexus and they all do the same thing if you put a bunch of fingers on the screen and then group them in close together. I'm pretty sure if you were to go to a Best Buy or something and play with all their tablets you would be able to reproduce the same thing on every single one.

The whole "only works when I'm holding it" thing was new to me though. It literally didn't work on any surface or even suspended on a stand. I've been playing around with it more since I got it back and putting it on various things, so far it works on every hard and soft surface, it also works whiles charging via USB and wireless charging. Another thing to note is that it came back with JSS15Q loaded. I haven't updated and don't plan on doing that for a while, even though the customer service people "guaranteed" me that it would be fine.

No clue about the bd-2g though.
[Nexus 7 (2013) Q&A] sfhub:
Ok, you didn't get any "newer" touchscreen firmware. This is the standard one that came with JSS15Q/R.

So it is possible you have a screen that now behaves best with the latest touchscreen firmware.
[Nexus 7 (2013) Q&A] fuser-invent:
I asked for confirmation and they said that no parts were replaced but the tablet was opened and the existing touchscreen was re-calibrated. I had previously tried all version of the firmware and the files from the touchscreen fix thread.
[Nexus 7 (2013) Q&A] fuser-invent:
Well I have more info. Applying the stock update broke the tablet again. So last time this happened I re-flashed the old firmware and it was still messed up. I will report back after I try that again and see if it works this time around :p

I have owned a ton (8+) Chinese tablets including Amlogic and Rockchip based stuff and haven't had this much trouble. I'm definitely kind of pissed that I decided to by a Nexus because I thought it would be better and it's actually much worse. If I didn't have so much experience with Android and was a 'noob' I couldn't even imagine how frustrating this would be.
[Nexus 7 (2013) Q&A] bokoy:
The problem is not android, is just this nexus devices made by asus in China. All the phones in my house are android but they are all samsung, here is the difference, all of them work like charm from day one. We also have a xperia z tablet that works perfect, this is just a problem from asus/goggle.

In Spain we ever receibe the devices from the rma with the JSS15J running on them and with the updates waiting to be done. My friend says that it works for him till he update or update and root the device, for me it was the best working compilation but still failing at multitouch, 15R is not much worst.
[Nexus 7 (2013) Q&A] jiangheng:
I've done this test, the problem is still there.

Is there a way to mod the hardware to fix this problem?
[Nexus 7 (2013) Q&A] robocopvn:
update to 4.4 still not to fix this problem ... is it permanent ?? software issue or hardware issue ??
[Nexus 7 (2013) Q&A] danvee:
No, sfhub has a fix that works on about 80% of effected devices.

Both software and hardware, apparently, but don't expect any admission either way from Google/ASUS.

Otherwise send it to ASUS for repair.
[Nexus 7 (2013) Q&A] Wonderstruck80:
I am still within my return period and am experiencing the same issues. When I place the device on a soft surface, the screen is unresponsive. Should I exchange the device or do all have this same issue?
[Nexus 7 (2013) Q&A] bokoy:
Hi, got mine back from asus for second time, they just reset and reinstall software, no hardware change this time. At least till now is behaving best than ever, I sent it with kikat and got back with the 15R, is this right? Or I did somthing wrong, no info...??

Thanks in advanced.
[Nexus 7 (2013) Q&A] sfhub:
Put a space after the "p" in both grep commands.
[Nexus 7 (2013) Q&A] bokoy:
Ok, did it. A bit different, kitkat drivers maybe?
[Nexus 7 (2013) Q&A] sfhub:
You have the touchscreen software that came with Kit Kat.
[Nexus 7 (2013) Q&A] bokoy:
Thanks, that was my guessing.

It is usual for me that when I do a factory restore it works whithout an issue for 1, 2 or 3 days, after that everything is back, multitouch problems mainly, I don't have complains about single touch in general after first rma. But is something really extrange that I cannot understand, like degradation from something or better said something getting saturated, because if it is fixed, at least temporary, and just with an image restore or a factory reset it can't be a component degradating.

So now i will try that connector, that some people is also reporting to work, and your ts's and see what I can do.

Again thanks for this and your great job with ts's.
[Nexus 7 (2013) Q&A] bokoy:
Told ya, 36 hours and multitouch problems are back. Tried the connector with no luck.
[Samsung Galaxy Fit GT 5670] ssn12:
guys blackberry messenger is now leaked

ANd is working fine for me

​

Link:http://wikisend.com/download/810296/BBM-release.apk

Note:Will work only in and above ICS

Hit thanks if i helped you !!
[Samsung Galaxy Fit GT 5670] sartrejp:
Thats the 1.0.0.42?

This one made things go wrong and will be disabled. Thats what blackberry said.
[Samsung Galaxy Fit GT 5670] ceonuke:
I don't think it will work. :rolleyes:
[Samsung Galaxy Fit GT 5670] abizerl123:
how to make it work on 2.3.6??
[Samsung Galaxy Fit GT 5670] zhu_zhu:
work on cm10? what device u use? galaxy fit?
[Samsung Galaxy Fit GT 5670] AleksaSavic:
You can't. It works only on Android 4 and above.
[HTC One X] pinbacninh_city:
Hello everyone!

I have a HTC One X after installing 4.2.2 & Sense rom cook 5 can not use Camera.

Although I have tried installing the rom different, but still did not improve.

Still having the same error with the camera Camera.Moi it back out.

Sorry people english is not my main language
[HTC One X] arun6106:
Is your G-sensor working (auto-rotation)?

It happens due to g-sensor issue :(

Not working on mine either, but works on 4.1.1 since its camera app doesn't require g-sensor

on 4.2.2 you can download an app camera jb which works perfectly fine.
[HTC One X] virgolib:
HTC had delivered app update for camera problem in Sense 5 (4.2.2), but pls note that is for fixing camera only not for G-Sensor.

Download: Camera APK - http://d-h.st/PUd
[HTC One X] 1boredchump:
How did this 4.2.2 software pass QA?

This phone would be awesome but it such a pos.

1st wifi and bluetooth signal not working properly, then home buttons failing to light, auto rotate failing and now the camera cuts out before you can take a picture.

Reseting phone at times has allowed the home buttons and auto rotate to work in the past so i assumed it was a software glitch, now i know for sure that htc are completely useless at QA and dont care about the customer.

Completely stock phone except the wifi mod to add a piece of wire which worked for wifi but bluetooth is still poor.

10 months to go til replacement time :)
[G2 Q&A, Help & Troubleshooting] cor_mann:
Hello,

I'm thinking about upgrading from my Galaxy Nexus to the G2. I'd get the N5, but that doesn't seem like a possibility on Verizon. Naturally, I'm accustomed to strong Dev support. Based on past Dev support for LG phones (aside from the N4), what can we expect as far as support? Will there be regularly updated custom ROMs, particularly AOSP based? How long can we expect for CM 10.2 support - and then for CM upgrades to new Android versions?

I appreciate everyone's knowledge in this matter - it will play a big part in my decision whether to get the G2.
[G2 Q&A, Help & Troubleshooting] lumpysherman:
Devs are working but I think it's to early to tell. The phone had only been out just over a week.

I came from a GNex as well but I'm happy with just rooting at this point, don't mind UX.
[G2 Q&A, Help & Troubleshooting] paradisewaits:
I'm running cm 10.1 alpha rt now on Verizon
[T-Mobile, Samsung Galaxy SIII] steelred:
Hey guys, :)

This is a possible fix for anyone who is experiencing all of the following issues. If you are NOT experiencing all of these issues then my fix is most likely not the cause of your problem.

1) Can't boot into ROM (phone will get no farther than GALAXY S III logo)

2) Can't boot into RECOVERY (phone will try to boot into recovery but will never make it)

3) Can't boot into DOWNLOAD (you may get as far as the caution screen but phone will turn off)

4) Phone starts, then turns off after about 3 seconds.

The solution that worked for me involves the power switch. It turns out that the reason you are unable to boot is because your power button is constantly being pressed due to a "sticky" button. This is a hardware flaw with only a temporary solution.

Steps to FIX issue.

1. Use fingernail to gently remove POWER BUTTON from phone. Notice that the bumps in the middle of the button are a little off-center.

2. Use a pair of fine tip tweezers to gently PULL on the yellowish/white POWER SWITCH inside the phone.

3. Test the fix by reinserting the battery. If the phone doesn't auto boot then press the POWER SWITCH with the end of your tweezers.

4A. If phone continues to power cycle then return to step 2.

4B. If phone properly boots then reinsert the POWER BUTTON with bumps in the middle aligned with the POWER SWITCH. If you don't align the bumps then the button will not function properly.

Once again, if this fix did not work for you then your problem is most likely in software (bootloader) and not hardware. ;)

Hope this helps someone. Cheers! :highfive:
[Verizon HTC One (M7)] TheAppleAndroidGuy:
I don't want to sound impatient or anything because I'm not I love my htc one as is but am just curious if any devs are getting closer to a unlock or root without the s-off tool. I've seen that there is a large bounty right now so I feel there should be devs at least trying to figure out something but it seems like I'm not seeing much info. anywhere and am only seeing people using s-off cards and stuff and I can't send my phone off. Any ideas?
[Verizon HTC One (M7)] cstrife999:
It has barely been a month. It's going to take awhile. If you aren't happy running stock on a phone don't buy it brotha.
[Verizon HTC One (M7)] TheAppleAndroidGuy:
Like I said I'm just curious, it's great stock! :)
[Verizon HTC One (M7)] adrenalinemotion:
There are multiple posts scattered here and there that hint/speculate that an exploit has been found and the devs are waiting on 4.3.

If you don't want to wait then send your phone off for S-Off, but please don't rush the devs. The exploit will come when it comes.

Can we lock this yet?
[Verizon HTC One (M7)] GrayBoltWolf:
Just hold on tight, it will be here soon!

There is an exploit floating around, but it needs work.
[Verizon HTC One (M7)] 123421342:
You know this how?
[Verizon HTC One (M7)] GrayBoltWolf:
I am not allowed to say, but trust me; and exploit is being worked on.
[Verizon HTC One (M7)] TheAppleAndroidGuy:
Alright thanks for the info.!
[Verizon HTC One (M7)] dspcap:
The OP is not rushing the devs, he's just curious if they are getting close.
[Verizon HTC One (M7)] cstrife999:
Yea but in all reality there are multiple threads about this... A simple search would provide the answers.
[Verizon HTC One (M7)] andybones:
Why would DEVs who are in a race to get a bounty TELL anyone how far they are? :confused::confused:
[Verizon HTC One (M7)] xHausx:
Exactly why bounties are a horrible idea IMHO. Donating for people's efforts is one thing, but bounties are almost always counterproductive unless someone already has an exploit that they don't want to burn.
[Verizon HTC One (M7)] AllenConder:
Its so funny after leaving iOS for my Gnex almost 2 years ago, I never thought I would be reading about "burning exploits" and "waiting for updates to release tools".

Oh well, the good thing about Android is, even "locked down" android is still amazing! The sexy hardware and looks of the phone take the sting out of waiting also haha
[Verizon HTC One (M7)] 123421342:
Why? Not "burning" exploits is a damn good idea. What happens when, lets say, the exploit was released now and then HTC took an extra week to patch it? Like getting insurance or warranty replacements? Too bad we wasted the exploit. Look what happened with the DNA and 2.04. It is literally the best idea to wait until the OTA comes out. This way, the majority of users get s-off and HTC will have a harder time patching it.
[Verizon HTC One (M7)] megaorange1:
My previous phone was the iPhone 4S and I never thought I would have to worry about exploits and etc ever again lol
[Verizon HTC One (M7)] abrego47:
i remember picking the dna up in april and it immediatly took the update for 2.04 then it took the 2.06 one. only a couple months went by and they came out with moonshine on linux then a window's version came out. i returned my phone back to stock to get 4g back and then i used the window's way. it is great to wait for the ota like you said so many more android's can get unlocked or s-off!!! :good:
[Verizon HTC One (M7)] AllenConder:
I think you misunderstood me. I was just making the comparison from iOS to carrier locked Android.

I completely understand why and how this is all done, but thanks for explaining to those that don't :)
[Verizon HTC One (M7)] kayone73:
Welcome to VZW asshattery, it's amazing how the AT&T and TMo owners don't have to deal with this nonsense

Sent from my HTC One Sinless ver 4.1 Google Edition rom
[Verizon HTC One (M7)] 123421342:
Att locks most boot loaders anyway
[Verizon HTC One (M7)] kayone73:
Of course, but at least there is a ready unlock solution, hopefully the devs will figure out the VZW obstacle soon

Sent from my HTC One Sinless ver 4.0 Google Edition rom
[Galaxy S 4 Q&A, Help & Troubleshooting] exxi:
Dear Friends,

I have done some serious criss cross flashing /modem/rom/recovery etc. (Rom upon rom) over the last months. I've recently had a soft brick and had to reinstall stock. I want a fresh start.

I feel like my phone's memory has been rewritten many times by now and that there are some resedues (crap files) in the system that I can't get out and that are slowing the system down. I'd like to do a full blown erase and restore to factory settings and then set up my custom roms again.

What is the best way to do this?

I am familiar with the use of Odin etc.

It would be delicious to get full instructions from you.

Best,

Thomas
[Galaxy S 4 Q&A, Help & Troubleshooting] Obagleyfreer:
Install a custom recovery like PhilZ and go to mounts and storage and then format system, cache, data, preload and SD card.

You will now have a totally clean system and can boot I to download mode and flash firmware in Odin.

Sent from my GT-I9505
[Galaxy S 4 Q&A, Help & Troubleshooting] exxi:
Thanks for the Help bro
[8125, K-JAM, P4300, MDA Vario General] valheru:
Hi Everyone. Long time user here but been absent since I got my Audiovox ppc4100 as someone stole my Siemens. EEEKKKK! I know don't say it. Of course I'm looking to upgrade and was previously looking at the PDA2K except for the horrible reports of BT being so poor. For me to upgrade I'd need to have a good BT hands free experience.

So for all you lucky souls who have one of these devices can you please report in as to how your BT experience has been on the K-Jam and which BT headset you are using? Thanks very much
[8125, K-JAM, P4300, MDA Vario General] robinton:
I don't get mine until tomorrow morning at 10:30, but I'll post a report on BT function once I get it.

Robert Harrold

Houston, TX
[8125, K-JAM, P4300, MDA Vario General] wardy:
Oh you are in for a treat 8) I use a SE HBH and the tomtom 700 . The headset works via voice command !!!!!!!!!
[8125, K-JAM, P4300, MDA Vario General] valheru:
Wardy, can you elaborate on which BT headset you use? I just don't get the acronym. Thanks for the responses though!

Though according to your signature, you are using Windows Mobile 2nd Edition which would mean you don't have an Imate K-Jam or just haven't updated your signature yet. Please advise and thanks again.