Database Info

Anybody having reboots/freezes, have you tried this?

Don't ask why but try doing the following:
- Settings -> Sound -> Haptic Feedback. UNCHECK (turning it off)
- Settings -> Language and Keyboard -> Android Keyboard Settings -> Vibrate on KeyPress. UNCHECK (turning it off)
I've had good results since doing this without changing anything else, phone has been more stable and no random reboots or freezes yet. Theory is due to the custom driver/vibrator used in the LG G2X (per CM7 team) there's a memory leak or some bug that over time causes the phone to reboot/freeze.
Why I think this:
- A few times in the last few weeks it froze was when a notification came in (GMail, SMS, etc.) that would have caused the phone to vibrate but instead of doing so it just did the SOD. Know this because I have a XOOM with me (3G) and emails come to both XOOM and G2X same time
- If I leave everything on, after about 2-3 days of use the vibrations start getting wonky with some lasting longer than they should or just not doing it properly
- Had a similar issue with CM7 on my Verizon Incredible where vibration issues would eventually lead to a reboot/freeze
NO GUARANTEES THIS WORKS. But I wanted to share and get more feedback. Please make these changes and then restart so its fresh. You don't need to disable vibration alerts, just the haptic feedback and keyboard vibrate.
Please post your feedback. Thanks.

I dont have reboots and never have those on...I'm gonna turn em on and see what happens..

I just turned mine off as suggested... I am on my 2nd G2x and am experiencing reboot issues already. I will keep you posted after a couple days on the results.
Thanks for posting this potential fix.

Had these off ever since I got the phone, haptic feedback gets really annoying. Will put them on and see what I find

I have had those on and had no reboots.
Sent from my LG-P999 using XDA App

witeboy07 said:
I have had those on and had no reboots.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Might be related to hw. The vibrator in the phone is a piece of hw so maybe some versions have problems and some don't. I know while my Incredible had vibration problems on CM7 others didn't with same exact software.
I wanted to see more if people getting reboots benefitted at all from these or not. It you don't have reboots at all this post is irrelevant.

mobilehavoc said:
Might be related to hw. The vibrator in the phone is a piece of hw so maybe some versions have problems and some don't. I know while my Incredible had vibration problems on CM7 others didn't with same exact software.
I wanted to see more if people getting reboots benefitted at all from these or not. It you don't have reboots at all this post is irrelevant.
Click to expand...
Click to collapse
It might have more to do with the software. I've used the stock ROM, the leaked 2.3.3, and Cyanogenmod, and all three use different vibration models. The 2.3.3 was particularly bad, CM7 is probably the best.

Bought my G2x on the 9th( So, hello! I'm new ) and everything was great until... yesterday actually. Had a bootloop and had to factory reset, then it locked up later. Then today it locked up and I pulled the battery and just now it didn't come on when I tried to unlock it.
So... I'm trying this. Hopefully it works. D:
If not, I'm gonna have to get a replacement or something. I'll be back with a follow up, some time.

For those of you who try this, please update here after a day or two. I am likely to let T-Mobile switch my phone out to a Sensation today so I may not have a G2x to play with any more. I really like it and if there is a simple fix I'd be willing to give it another go.

Trying it now
I haven't had it reboot on me since I did a factory reset last week...
I'm going to turn off the vibrate settings as described in the first post. I'll come back in a few days to respond if I've had any reboots, freezes, etc.
EDIT: I'm also going to reboot after changing these settings just to make sure they "stick" and the phone is "fresh".

Day 1, no freezes.
I charged the phone and it didn't freeze either...
It's Day 2 now and I'll let you know how this goes down as well.

I haven't had either of these options checked since I first got the phone. I have a reboot approx every 1-2 days and a freeze every 3rd time.

Another strange thing
It's been over a day and a half after I've turned off the haptic feedback settings described by OP and no reboots or freezes yet. Even while using wifi calling and heavy camera use and very heavy picture uploading directly from phone to picasaweb.
Something else strange that happened to me before that could be related to the vibrate software/hardware is when some one called me it would vibrate and ring like normal but after sliding the green arrow over to answer it stopped ringing, answered the call just fine, but the whole time while talking the motor continued to vibrate in the two pulse way it normally does! Has anyone else had this happen!?

harleyxlc said:
I haven't had either of these options checked since I first got the phone. I have a reboot approx every 1-2 days and a freeze every 3rd time.
Click to expand...
Click to collapse
Try wiping your dalvik cache as I've posted in a separate thread.

worked for me. 2 days no problems

day/charge 2 and 3... everything is going well.

[Q] Haptic feedback problem

Hey everyone, so I just flashed Cyanogen 260 nightly and got everything running when something odd happened. I tried opening Astro, but it force closed. Since then, my haptic feedback hasn't been working. I've rebooted and checked all the settings for it to no anvil. The only time my phone vibrates now is when booting up to the splash screen, right before the boot animation. Does anyone have any ideas?

Have you checked in cyanogenmod settings under input. There are options for haptic feedback there.
Sent from my Desire HD using xda premium

Yeah. I've checked that already. Just a little update, I banged my phone against my palm to see of that would do anything. The first time I did it the phone vibrated quite a few times. After that I was unable to rereplicate that event.. I'm not sure if this is a hardware or software problem.

OverCaffeinatedHobo said:
Yeah. I've checked that already. Just a little update, I banged my phone against my palm to see of that would do anything. The first time I did it the phone vibrated quite a few times. After that I was unable to rereplicate that event.. I'm not sure if this is a hardware or software problem.
Click to expand...
Click to collapse
haha, well I would say banging your phone on your palm is not going be the best thing for your phone's life but and I know this is gonna be a huge pain in the ass if you have a lot of stuff, you can always reflash and see if that brings back your haptic feedback..at least then if it doesn't your one step closer to diagnosing it as a hardware problem..

Haha. When i woke up this morning the haptic feedback was working like usual. It was an odd problem, it could possibly be battery related because my phone was charging all last night.well anyways thanks for all the help!!

Haptic feedback suddenly stopped working

Just noticed it. No idea why. I turned the tablet off/on a couple of times but that didn't do anything. Any ideas?

The motor might be dead. Have you tried toggling it under sound?
The 700 I got from Best Buy, a C7, haptic was dead out of the box. Had to take it back.

Factory reset didn't fix it either. I'm hesitant to exchange it because I don't have any of the other issues people are complaining about with this one but might with another. What a pain in the ass.

Does it vibrate when you power on or off? It should at least do that, if it does, its working. If you don't feel anything its toast.
Makes me mad too cause the one I had, everything was great except haptic. I didn't want to wait for another one so just took the refund

NeoMagus said:
Does it vibrate when you power on or off? It should at least do that, if it does, its working. If you don't feel anything its toast.
Makes me mad too cause the one I had, everything was great except haptic. I didn't want to wait for another one so just took the refund
Click to expand...
Click to collapse
Yeah, it vibrates when turning on/off. The tablet has been set to 'vibrate on touch' since day 1. Mysteriously that doesn't seem to work anymore.

after seeing this thread i just checked mine out. The haptic feedback is really really weak. I cant really feel it unless i am paying really close attention. On my prime it is noticeable, for sure.
I powered down and back up as suggested and got the standard 1/2 second buzz associated with those actions.
Maybe something in the update neutered the feedback? Is anyone's really pronounced?

stunya said:
after seeing this thread i just checked mine out. The haptic feedback is really really weak. I cant really feel it unless i am paying really close attention. On my prime it is noticeable, for sure.
I powered down and back up as suggested and got the standard 1/2 second buzz associated with those actions.
Maybe something in the update neutered the feedback? Is anyone's really pronounced?
Click to expand...
Click to collapse
Mine was totally fine, pre and post update, until I think late yesterday? The only thing I can think of, and I really hope this has ZERO to do with my issue, is that I had left my stylus laying across the screen for a short period of time. I think while it was resting on the screen it was registering touches repeatedly and maybe this screwed up the feedback mechanism? I know it was registering because the webpage that was showing was zooming in and out frenetically until I picked the stylus back up.

stunya said:
after seeing this thread i just checked mine out. The haptic feedback is really really weak. I cant really feel it unless i am paying really close attention. On my prime it is noticeable, for sure.
I powered down and back up as suggested and got the standard 1/2 second buzz associated with those actions.
Maybe something in the update neutered the feedback? Is anyone's really pronounced?
Click to expand...
Click to collapse
IMO this tablet is considerably more hefty than the prime. I think its because of the form factor that doesn't transit vibrations as well.
Sent from my PG86100 using Tapatalk 2

I'm just going to live with the broken haptic feedback. None in stock locally to make an exchange, and I really don't want to go thru the rigamarole of shipping it back, waiting who knows how long for a replacement, and then possibly getting one with other issues.

I got no haptic feedback at all since I got the Infinity. There's no screen locking sound either. I guess there should be one anyway?! The settings for these aren't affecting to anything at all.

jdeoxys said:
IMO this tablet is considerably more hefty than the prime. I think its because of the form factor that doesn't transit vibrations as well.
Sent from my PG86100 using Tapatalk 2
Click to expand...
Click to collapse
i messed with mine all day. i am on the fence about sending it back (though prob not). it transmits a decent amount of feedback every 2-3 times, then 1-2 time where it is barely noticeable. I did the same set of testing with the prime...it too has a weak signal every 2nd or 3rd time, but it is still stronger than "regular" on my infinity.
I am going to see what others say, but i might have to agree with you on the transmission of vibration. If i hold it up to my ear, its definitely trying to do something...just not communicating it well.

Where is this "vibrate on touch" option? I can't find it anywhere. Are you talking about "Vibrate on keypress" for the Android keyboard? As long as you get buzz during the turning off and on, you at least have it functional.

alienedd said:
Where is this "vibrate on touch" option? I can't find it anywhere. Are you talking about "Vibrate on keypress" for the Android keyboard? As long as you get buzz during the turning off and on, you at least have it functional.
Click to expand...
Click to collapse
settings/sound/system - vibrate on touch.
its more for say a long press when adding a widget or icon...etc

stunya said:
settings/sound/system - vibrate on touch.
its more for say a long press when adding a widget or icon...etc
Click to expand...
Click to collapse
Hmmm. I don't get any feedback from that. Messed with some widgets and icons - nothing. Maybe its one of those things that didn't get checked by QC?

Ooookk...after reading this thread went to check my. Also no haptic feedback even if I check it from the settings...this is strange.

I never noticed haptic feedback.
After reading this thread I checked all the settings and I didn't get anything.
Except the one when you switch it off....
I'm using swiftkey.
So I checked the settings there.
It was activated but no haptic feedback.
But in swiftkey you can change the duration as well.
I set it to 60 and now I get haptic feedback.
So the hardware seems to be OK in my case.

I was getting decent haptic feedback when typing, backspacing, hitting the home key, arrow key, home screen, whatever, before it stopped working. I also tested out swiftkey from the app store and was able to turn up the haptic feedback setting when typing, but still nothing from screen touches etc. This has to be a hardware issue, right? Then again, why would this function work, then stop working, but then sort of work (at least on the keyboard side) when using another app?
I made an assumption that this problem manifested when I left my stylus on the screen causing the screen to bug out as if it were be touched rapidly and repeatedly. Because store exchanges are impossible at this time and I'm ~1.5 weeks from my 30 day return window I decided to order another one, and then set up an RMA for this one to go back and be credited; assuming that my replacement doesn't have any other issues. I couldn't justify letting this go considering the cost of this thing and the fact I've only had it a couple of weeks.

How about the screen locking sound? Should there be one?
Actually there is a very very faint audio feedback for touch that I'm able to hear with headphones in a totally quiet place. It disappears when unchecking the setting.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

Jack Daniel's said:
I never noticed haptic feedback.
After reading this thread I checked all the settings and I didn't get anything.
Except the one when you switch it off....
I'm using swiftkey.
So I checked the settings there.
It was activated but no haptic feedback.
But in swiftkey you can change the duration as well.
I set it to 60 and now I get haptic feedback.
So the hardware seems to be OK in my case.
Click to expand...
Click to collapse
If you change the duration of the regular Android Keyboard under its "Advanced Settings" you can get the vibrate on keypress to work. The duration is initially set too short for the vibrate mechanism to fully buzz. I changed it from 1 ms to 100 ms and I get definite (but not powerful) jiggle.
johannesr said:
How about the screen locking sound? Should there be one?
Actually there is a very very faint audio feedback for touch that I'm able to hear with headphones in a totally quiet place. It disappears when unchecking the setting.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app
Click to expand...
Click to collapse
I can get a faint locking sound. Can't hear anything for interactions outside of typing though.
stray_pube said:
I was getting decent haptic feedback when typing, backspacing, hitting the home key, arrow key, home screen, whatever, before it stopped working. I also tested out swiftkey from the app store and was able to turn up the haptic feedback setting when typing, but still nothing from screen touches etc. This has to be a hardware issue, right? Then again, why would this function work, then stop working, but then sort of work (at least on the keyboard side) when using another app?
Click to expand...
Click to collapse
I just checked all of the boxes under the sound feedbacks. I can get some haptic from the back and home buttons but still nothing for widgets and such. Can't really notice any sounds from those though. Perhaps an update lowered the values for the feedback and that's why your initial problem happened? Dunno.

alienedd said:
I just checked all of the boxes under the sound feedbacks. I can get some haptic from the back and home buttons but still nothing for widgets and such. Can't really notice any sounds from those though. Perhaps an update lowered the values for the feedback and that's why your initial problem happened? Dunno.
Click to expand...
Click to collapse
The problem didn't start happening until 2 days ago. The update has nothing to do with it. The last fix I tried to do was a 'cold boot'. I can't get that to work and yes, I followed the instructions posted on another forum and in YouTube videos. I hold down power and volume simultaneousy for up to a minute and nothing happens, other than locking it up and I have to stick a paper clip to reset it.

[Q] Touchscreen Issues

I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've never experienced any issues like this. Contact Nvidia Customer care.

This screen is very responsive!! Make sure you are all up to date with your ota and make sure you have a look in a settings / SHIELD POWER CONTROL/ OPTIMIZED

ttxcsabby said:
I purchased my NVIDIA tablet yesterday but having problems with the responsiveness coming from sleep. About 1/5 of the time, my tablet will not respond to my finger/stylus. I always have to press the power button a few times to get it to work.
I have all the updates, including the recent update from yesterday. Is this defective?
Thanks in advance
Click to expand...
Click to collapse
I've had that many times during one single day. Had to literally reboot the thing 5 or 6 times that day. COMPLETELY NO RESPONSE FROM THE SCREEN, ONLY BUTTONS. Still have to clue what the deal was. Hasn't done it since, but the issue DOES exist. And yes, I bought from the very first batch, straight from Nvidia.

I've had this problem since day one. Also the tab crashes at random times and it getting ****ing annoying. Thinking of returning the thing. It's worse than useless. Turn the screen off and you can bet that i'll have to reboot to get the touchscreen working again.
Idk why this helped but it did. I switched from using philz touch recovery to cwm recovery...now screen works less than half the time I turn it back on. That's still better than never.
Sent from my SHIELD Tablet

I've never experienced this on Stock, Only on Pac-Man ROM and CM11. Either way it is very annoying.
This is a reaaallllllyy ghetto work around until the issue is solved, but the way I worked around it on CM11 is to have Tasker and Secure settings wake the device for a few seconds every 45 mins - 1 hour. Ever since I've had Tasker performing that task I've had no issues with the screen being unresponsive.

I have figured out how to fix the touchscreen issues. All you have to do is go under Settings>Apps>All Apps and find anything that ranges from Google Taiwanese or any Google foreign language app and disable it. There should be two of them. I haven't had any problems since I disabled them. :good:

I found something that has worked so far. I always use Nova launcher since it's my fav. I didn't think much of leaving the launcher that came with the rom. I went to titanium backup and froze the other launcher and it solved the touchscreen issue. This also fixed the app crashing problems most of the time. Still if I run more than two applications at the same time everything on the tab starts crashing. Seems to be a ram problem. I checked max backround processes and it's at "normal" which usually is fine. If anyone has a solution to the crash problem please let me know. Meanwhile i'll keep trying stuff.
Sent from my SHIELD Tablet

Same problem here... Funnily enough I just wanted to try a custom rom to see whether this issue will be fixed and a new official upgrade to 7.0 came up - https://shield.nvidia.com/support/shield-tablet-k1/release-notes/1
Will see whether ithe problem is gone.

There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.

2kool2Bcruel said:
There was a time when my screen became a bit unresponsive. Very random. Calibrating the touch sensor fixed it up. Its a bit hidden but you'll find it by going into Settings>About Tablet (device)>Click on Model Number 3 times>The calibrating settings will pop up hit Touch then hit Start. It'll do it's thing and reboot. Hopefully it helps.
Click to expand...
Click to collapse
I had a similar issue with touchpoints not working near the corners, calibration fixed things for me also. It's pretty quick and easy to do so I urge you to try that before doing a factory reset.

So far so good... Android N seems to fix the problem
Sent from my Pixel using Tapatalk

[Q] Vibrate motor randomly stops. Any ideas?

My Nexus 5 vibrate motor seems to randomly stop. Usually, it stops working for just a few seconds at a time, but sometimes it stops for more than just a few seconds. It started randomly one day, and I haven't been able to tie it to a specific app yet, and it didn't coincide with the installation of a kernel or ROM.
I'm running rooted stock Lollipop with elementalX kernel (2.03).
I've tried pushing on the back, since some people have issues with the vibration motor not making good contact with the rest of the phone, but it seems that doesn't really do anything for me. It seems to help occasionally, but not necessarily.
Sometimes turning the screen off and back on helps, but sometimes not either.
Unfortunately, the inconsistency is making it difficult for me to figure out what the problem is. Could it just be a dying motor?

You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.

bblzd said:
You can open it up and reseat the vibration motor on its sticky pad if you're not worried about the warranty. Alternatively, some of those with the issue have reported success giving the phone a good smack.
Click to expand...
Click to collapse
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket

And it happens with stock kernel as well, correct? If it has been less than 1 year you could RMA.

chronostorm said:
Thanks for the ideas
I did try reseating the motor, and I thought it was going well, but after about a full day or so, I was hit with a non-vibrating motor again Turning the phone off and back on didn't help, but shaking it a bit seemed to do well
I have tried giving the phone a good smack, but it seems like a temporary thing. I'm mostly afraid I might miss a call, message, or vibrate alarm if I run into this problem with the phone in my pocket
Click to expand...
Click to collapse
I had this problem as well and still encountering it sometimes. Don't worry about a missed call though. My vibration completely stopped working and a reboot didn't help, however a call made the vibration work again lol and it has been working since. Fingers crossed same **** doesn't happen again.