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!!
Related
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.
Ok so i picked up my new skyrocket 2 days ago and I put CWM on it, made a back up and installed the ICS flavor ROM from the development forum. Everything went fine, and i didnt use the phone much yesterday, but today i noticed that i am having annoying touchscreen problems. It basically makes Swype unusable. I have restored back to stock and it was still doing it. I have reinstalled the ICS rom, double flashing it, and it still does it. Is anybody else having issues like this? Its noticable on lists. This video is just an example but it does it in the market, on web pages, etc..
http://youtu.be/x__jdlGXyjk
I have never had these problems. Maybe take it back and exchange it.
Sent from my SAMSUNG-SGH-I727 using xda premium
Update:
I used odin and i reset everything to stock with no CWM and no Root and the issue has stopped as far as i can tell. Maybe i just had a bad download. Ill redownload it again and flash it tonight and see if it persists.
Ok so ive been using stock and it started again. I used an app called Touch Test to see what the screen is seeing. It is a really intermittent issue. There is a "ghost touch" that is happening. near the top of the screen and at the bottom of the screen. A touch in the middle causes it to jump to the top and then back to the bottom causing touches to jump all over the place. It is very intermittent. I didnt buy the phone from ATT so there could be 2 reasons for the this.
A) It was sold to me like this
B) The people at ghost armor put to much liquid on my phone when applying the screen protector and messed up my phone.
I didnt notice any issues before i got it ghost armored, but i only had the phone 2 days before i got it wrapped.
Any ideas on how to recalibrate the screen or any other options i may have?
Found the culprit... Kind of embarrassed it took me this long. Ended up being the wall charger. Its a cheap knock off but it had the same input and output. I was sitting at my desk on the touch test app seeing it spaz out and unplugged it to show my friend what was happening and it stopped. Used the same cable to plug into the pc and no problem. Well that is a relief.
jason.hamilton said:
Found the culprit... Kind of embarrassed it took me this long. Ended up being the wall charger. Its a cheap knock off but it had the same input and output. I was sitting at my desk on the touch test app seeing it spaz out and unplugged it to show my friend what was happening and it stopped. Used the same cable to plug into the pc and no problem. Well that is a relief.
Click to expand...
Click to collapse
Wow, thanks a lot for this info man! You really saved my life.
I also got a new charger and started experiencing these weird jitters. If it wasn't for this post I would never have figure it out.
My new charger was an Original one from Samsung, but it was obviously made for a different model as the output voltage and current were higher = caused jitters.
I then went back to using my old charger which came with the phone and the issue is gone.
Using Samsung Galaxy S5 NEO (SM-G903F).
Thanks again!!!
My first thought is that it's a hardware problem on my phone. No haptic feedback on the capacitive buttons, keyboard, ringer, etc. I checked that haptic feedback is turned on in the settings and it is. I've restarted a few times and still nothing. I'm going to factory reset to see if that helps, but I wanted to check here first to see if anyone else is experiencing this. It happened pretty much right after updating SwiftKey 3 yesterday, but uninstalling Swiftkey does nothing, so maybe it's just a coincidence.
Thanks!
jakemg said:
My first thought is that it's a hardware problem on my phone. No haptic feedback on the capacitive buttons, keyboard, ringer, etc. I checked that haptic feedback is turned on in the settings and it is. I've restarted a few times and still nothing. I'm going to factory reset to see if that helps, but I wanted to check here first to see if anyone else is experiencing this. It happened pretty much right after updating SwiftKey 3 yesterday, but uninstalling Swiftkey does nothing, so maybe it's just a coincidence.
Thanks!
Click to expand...
Click to collapse
Are you on stock?
Sent from my One S
Yep, unrooted stock.
I'm 99.9% sure it's a hardware failure of my vibrator motor. If I slap the phone (lightly) against my hand, it works for a few seconds, then stops.
jakemg said:
Yep, unrooted stock.
I'm 99.9% sure it's a hardware failure of my vibrator motor. If I slap the phone (lightly) against my hand, it works for a few seconds, then stops.
Click to expand...
Click to collapse
Hmm weird.. two days after I bought my phone the audio stopped working and I was afraid it was a hardware fault but it was solved after a full wipe, so try that first.
Sent from my One S
Hi all. I'm having an issue with a 727R. I replaced a broken screen and now can't get the screen to stay on. Its a non rooted, factory 2.3.5 phone. When I turn it on, the sghi-727r screen pops up for several seconds and then dissappears, phone vibrates once, notification sounds appear shortly and all touch functions appear to work (by sound and haptic feedback). For all intents and purposes, this phone is on and working perfectly...if you're blind lol. I know the replacement screen works because it works perfectly if I go into download (odin) mode. I've been searching threads and haven't been able to come up with a solution, as most of the other blank screens are from bad flashes. Keep in mind that I am also testing this with the casing removed as it is a repair for a friend (if that makes any difference). Any help or ideas would be greatly appreciated and thanks in advance.
Is the brightness maybe turned ALL the way down? When it finishes booting shine a flashlite on the screen and tell me if u can see text, icons etc...
I'll do that as soon as I get home this afternoon. I could only hope that's all it is, but i'm a little skeptical that I could be so lucky. forgot to mention that I have also odin flashed the stock rom back on just in case of software corruption. I would also think that I would get full boot logo's during the boot sequence, but hey!....its definately worth a shot! I've seen stranger things . Thanks for the quick response.
norm182 said:
I'll do that as soon as I get home this afternoon. I could only hope that's all it is, but i'm a little skeptical that I could be so lucky. forgot to mention that I have also odin flashed the stock rom back on just in case of software corruption. I would also think that I would get full boot logo's during the boot sequence, but hey!....its definately worth a shot! I've seen stranger things . Thanks for the quick response.
Click to expand...
Click to collapse
No worries, keep us informed. I didn't even bother to ask because I just assumed someone at your level who can change a screen would intuitively know to Odin stock... I was right :good:
It a ribbon cable issue when I swap dismantling my SR's I ran into that twice swapped out screen and no issues after
Sent from my SGH-I727 using Tapatalk 2
crashpsycho said:
It a ribbon cable issue when I swap dismantling my SR's I ran into that twice swapped out screen and no issues after
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
So you had display for start of boot and d/l mode? If so, then I'll go no farther until I get another replacement screen.:crying:. Come to think of it, when plugged in and off, the charge symbol shows up for a second and its discoloured (almost like its made of vertical lines that are pinks and grays). You may have just saved me a lot of time. I was leaning toward trying to adb error logs in hopes of finding something. Other than that it was going to be a reflow on the gpu since the phone did do a leap of faith from 6 ft up....and lost lol.
icenight89 said:
Is the brightness maybe turned ALL the way down? When it finishes booting shine a flashlite on the screen and tell me if u can see text, icons etc...
Click to expand...
Click to collapse
No dice icenight. Tried out of hope but its completely black. I was really hoping for maybe a fault that could be fixed with a flash.....whoa is me....looks like I may be sending screen back and getting another. I cant send it out for another day so if anyone has any other ideas, or wishes to guinea pig this unit until one comes in, feel free to chime in. And thanks for the responses so far!
crashpsycho said:
It a ribbon cable issue when I swap dismantling my SR's I ran into that twice swapped out screen and no issues after
Sent from my SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
And the winner is....Crashpsycho! After months of trying to find a replacement, i finally got my hands on two of them for a decent price. Popped one in, odin'd jb stock and voila! perfect phone again. Thanks Crash!
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