Vibrate suddenly extremely low. - AT&T Samsung Galaxy S II SGH-I777

I have had my phone since the summer time and flashed multiple ROMS/kernels and never had an issue with the vibration. I was using Task650/ktoonsez 4.1.2 12.2.2012 with Fluxxi 4.3.3 for some months now.
Yesterday I lost almost all intensity to my vibrate. I can not feel it when typing in swype or touching the capacitive buttons. I downloaded a vibrate app and can feel it although it is very soft.
I have increased the intensity in Device options/Haptic and using extweaks.
I have cleared all cache/dalvik. I have flashed a new rom (Helly bean). Nothing works. Hopefully this is not a hardware issue but it is looking that way. Does anyone have any suggestions? Should I try flashing to stock?

That's what I would do,if only to eliminate the possibility of it being hardware related.
Sent from my GT-I9100 using Tapatalk 2

Same thing on stock. I have also noticed that auto-rotation is wonky. Will rotate from portrait to landscape but not from landscape to portrait. Guess I will have to contact samsung.

Just want to update for anyone else that has a similar issue. I was able to fix the problem with vibration by violently smacking the phone on its side against my hand a couple times. Vibration is much stronger now, almost as strong as it was before. Also re-calibrating my accelerometer after this fixed auto-rotation. Yay!

.....?.....violently smacking....seems legit

Related

[Q][FIXED] No more vibrate function!

My i9100 suddenly stopped vibrating. No haptic feed back, no sms vibrate, no call vibrate. No *#0*# vibration...
I had lighting rom, installed stock rom and nothing, wont vibrate again.
Anyone had this kind of trouble? Any other idea than sending it back? (I got this abroad...)
Thanks in advance
Factory reset will solve it had this happen to me once after flashing a rom and a factory reset bought haptic feedback back.
Sent from my GT-I9100 using Tapatalk
Didn't work, I had tried that.
But weird stuff:
After I installed a Brazilian stock rom, I was fully charging it so I could root it again. Accidentally it fell for about 2 feet high.
Vibration is back on. (probably a HARDWARE failure, a jam of some kind) Really weird. (I do use a silicon case, my i9100 is without a scratch, I wonder what will happen from now on...)
It was the first time I see a FALL fix a phone though.
Well. It went on and off again. Probably faulty hardware.
Sent from my GT-I9100 using XDA App

Razr touch screen randomly not responding

I had my razr for about 2 weeks, and this problem already happen to me a few times.
The touch screen will suddenly not responding to ANY touch, only the the buttons are still working(include the 4 buttons on the bottom).
I had to hard reboot my phone to get it working again.
Does anyone face the same issue?
Sent from my XT910 using XDA App
WongJames said:
I had my razr for about 2 weeks, and this problem already happen to me a few times.
The touch screen will suddenly not responding to ANY touch, only the the buttons are still working(include the 4 buttons on the bottom).
I had to hard reboot my phone to get it working again.
Does anyone face the same issue?
Sent from my XT910 using XDA App
Click to expand...
Click to collapse
Yes I also face this type of problem while playing games. Screen become unresponsive while playing but can solve by pressing power button(no need to reboot).Not on 2.3.5 base only on 2.3.6.
I also face this problem, after updating my rom to arctic 2.0 rom, which uses some stuff from 2.3.6.....power does not help, have to hard reboot. any idea why?
I've had this problem happen to me on my Droid RAZR (CDMA Verizon), can't remember if its before or after I was rooted... I just had to hard restart and its only happened once since then.
pswin09 said:
Yes I also face this type of problem while playing games. Screen become unresponsive while playing but can solve by pressing power button(no need to reboot).Not on 2.3.5 base only on 2.3.6.
Click to expand...
Click to collapse
The power button does not work for me
I had try to press the power button, but then the screen still not responding, so I cannot pass through the lock screen, and have to hard reboot......
I am on stock rom, 2.3.5, the Asian version.
But it seems it does not matter to different region's razr since the cdma one had the same issue
Sent from my XT910 using XDA App
I get this too. I had 3 razrs, first two had dead pixels so I had them replaced, all had this issue. Has not happened in awhile and I can't remember if it was always with a game, but at least one time it was with a game. Anyway, I don't think this has to do with rooting because my first one I never rooted and it did this. Don't remember if power button worked or not, but I had to reboot as well with power and volume down, or up, whatever it is, to get it to respond again.
No problems here.
I have had this happen about 4 or 5 times for me as well - got it day of launch. Mine says it is the XT912 though - is that right?
XT912 is the Verizon specific one, so yes.
Seems to be a fairly common issue. What is the chance that this is a software problem as opposed to a hardware one and so will be fixed with an update?
I had it happen for the first time yesterday after about 5 weeks or so, strange cause I wasn't doing anything. Battery was at about 15% though...
I only encounter this bug when I open Rom Toolbox for the first time and the superuser permissions screen shows up. My screen doesnt respond to touch anymore. I have to use the power button to make it work. Thats it. It happens nowhere else.
I've been using ROM Toolbox since day one, can't say it's the issue.
Sent from my XT910 using xda premium
opensourcefan said:
I've been using ROM Toolbox since day one, can't say it's the issue.
Sent from my XT910 using xda premium
Click to expand...
Click to collapse
Happened to me today...any need to panic?? On official Stock ROM 2.3.5...
Also, is this a hardware issue or software??
My problem is bit different, on a 4 month old unrooted razr.
Touch screen will start to fail recognizing my sywpe typing and start jumping all over the place, or it will end the word while I'm still sywping the word...
Sometimes it types in different letters (1/2 keyboard away) when I'm not sywping to avoid this BS when it happens.
Unfortunately, I cannot reproduce this result whenever I want to, I'm currently trying to reproduce the situation.
I believe this happens more often when my battery is low... or when I have been using it for an extensive time.
I go to draw program to test if it is the hardware problem and it is jumpy too, but not by much.
The problem does get better with reboot, but not 100% of the time, so I can't conclude it is SW problem
I also have issues with this. I think the problem is software side. It seems to be poorly responsive often after I unlock my phone and try to swipe screens.
Also while typing quickly with two hands it often does not input all the letters I type, although it flashes the keys and acknowledges that I touched them (this one might be a keyboard issues, not sure yet)
And ya, on an all black screen, I'm noticing some dead pixels- a lot of rectangular patches of dead pixels. I don't really notice it anytime else except when it's all black.
Been making me double think my choice, but I will wait for ICS update and possibly bootloader bypass. But.. I might be getting another phone shortly just because of the size (bezel mostly), these touch screen issues, and the performance isn't exactly where I anticipated it to be.
Razr XT910 touchscreen randomly jumping or not responding
I'm having all the problems mentioned earlier:
- touchscreen stops working randomly
- touch "jumps", like someone is touching it in random places
- some letters on the keybord stop working randomly
- phone gets quite hot at the top
My XT910 is not altered in any way, stock android 2.3.5, as updated as possible.
This happened when it was up-to-date and the very clean one.
This happens really irregularily. At first it happened when I played multitouch games - at some point the touchscreen just stopped responding and could only go back or lock the screen (but not unlock it, obviously).
Twice it happened when I was just going through messages or contacts.
I sent it to Motorola to fix it - they just reset it, benchmarked it for 45seconds and sent it back.
The very evening I got it back I tried to "heat" it myself - I installed a lot of apps, played a lot multitouch games on 3d graphic and voila! - it started freaking out like never before (vidoe in zip file attached).
My last idea is that it happens because of a low quality generic anti-scratch foil on the screen. So I threw it away and tried to "heat" the phone again - nothing.
I used a different foil - anti-reflecting + benchmarking apps - nothing.
If it happens again I'll send it with this video + the one I'll make then.
Hope it gets Motorola specialists off their ass and back to work .
Hey there, my maxx has this weird issue with it's screen too.
Take for example, a game with on screen controller like reckless racing. If i push the screen too long, it won't recognize my press anymore in the pressed area. I tried to go back home, thinking this is the game issue, but it's not, the home launcher button that coincidentally in the same location with game control button is unclickable. i tried with phone tester app and it show the same symptom, the pressed area indicator will disappear within 1-2 minutes.
The only solution is to turn off display and turn it on again. Should i bring it to service center?
Sent from my XT910 using xda app-developers app
Hello, I've recently having this exact same problems with my Motorola Droid Razr Maxx.
The screen sometimes doesn't respond as it should:
-Random touches.
-Not detecting swipes.
-Not detecting anything at all after long press.
-Detecting the touch location wrongly...
When this happens, sometimes a reboot fixes everything. Others, I just have to stop using the phone, and come back later.
Has anyone managed to find a possible cause and/or solution to this problem?
I've tried diferent roms, full reset, rsd flashes... But still the same problem

[Q] CM7 - I keep hanging up on people!

So since I've moved to CM7 I keep hanging up on people when I am trying to hold my phone between my ear and shoulder because my jaw bone hits the end button. I don't recall this happening ever with Blur. Is there a prox sensor that is supposed to disable the phone when it's up against your face? Where is this setting in CM7 or is it just an issue of buttons being in slightly different places w/ CM7 than with stock? If so, is there a phone replacement app that anyone could suggest?
Have you tried turning the screen off (via the power button) before holding it to your face? That was something I desperately wished I could do on my old Moment, because its proximity sensor sucked, but the power button served double duty as the end call button.
Interesting idea. I didn't consider trying that. I also noticed under Call Settings an option "always use proximity sensor" which I enabled and will try. Maybe my phone thinks it's horizontal when I hold it that way.
It is a vertical horizontal thing I believe. Phone needs to be pretty much vertical for the proximity sensor to come on. You can test this in a dark room. Call a number and watch the sensor illuminate. It should look like a red dot near the earpiece. Then move it towards horizontal. You should see it cut off.
Sent from my MoPho. All typos are the phones fault.
ypu may need to do another fresh clean install. completely wipe everything then flash the rom again?
The "always use proximity sensor " setting seems to have fixed it. I must have had my too horizontal.
Sent from my MB855 using XDA App
jeggen said:
The "always use proximity sensor " setting seems to have fixed it. I must have had my too horizontal.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I was just going to mention that. I found the setting while tooling around in the cm7 settings. Glad you got it fixed.
Sent from my MoPho. All typos are the phones fault.
will give that a try. im having same issue on cm7.2

[Q] Touchscreen wakeup issue

Hi everybody,
Recently I've been encountering a problem where my streak won't respond to any touches after I open the screen. Pressing the power button and waking the phone up again does not solve the problem. I've read about the static issue, but unfortunately it doesn't seem to be the case here as the problem still occurs even when my streak isn't in my pocket.
Oddly enough, rebooting the phone solves the issue temporarily. The touchscreen will work perfectly until I turn the screen off again, but when I turn the screen back on, the phone doesn't seem to register any touches. The phone itself works fine as it still receives notifications even when the touchscreen is unresponsive.
Is this a hardware or a software issue?
I'm currently on DSC 2.2 and baseband 366. I'm going to try a factory reset right now to see if any will improve.
Thanks!
Edit: did a factory reset, problem is still occurring
I have the same problem, does anyone know how to fix this? thanks
Sent from my Dell Streak using xda app-developers app
Have you tried recalibrating your touch screen from the dell menu?
Its option 3, worked for me a few days ago.
Loco007 said:
Have you tried recalibrating your touch screen from the dell menu?
Its option 3, worked for me a few days ago.
Click to expand...
Click to collapse
Yeah I have. I'm currently assuming it's a hardware issue since I've reverted back to a stock rom along with several other custom roms but the touchscreen still remained unresponsive after waking it up. I'm hypothesizing its a bad connection somewhere, especially if the display and touch sensor wake up separately. Does anybody know anything about this and whether it can be repaired?
On the other hand, I might be completely wrong...
I noticed that some bags for DS5 produce static electricity, such as the original Dell Bag (Futon bag - ?)
The Leather Bag (with red fissure) does not produce static electricity even when having the DS5 in trousers.
jlin5647 said:
Yeah I have. I'm currently assuming it's a hardware issue since I've reverted back to a stock rom along with several other custom roms but the touchscreen still remained unresponsive after waking it up. I'm hypothesizing its a bad connection somewhere, especially if the display and touch sensor wake up separately. Does anybody know anything about this and whether it can be repaired?
On the other hand, I might be completely wrong...
Click to expand...
Click to collapse
I had this problem once, pried and screwed the Streak open, checked connection ribbons, and cleaned it with (a little bit) electric contact spray. This has saved my irresponsive power button as well! Success:good:

2nd screen issues

Has anyone had this occur?
It's happened twice now and a factory reset fixes it but only temporarily. If the phone is left alone, the second screen will normally dim to roughly half it's brightness on its own. This is normal, however mine stays continually at full brightness and has stopped dimming, again. Also if the proximity sensor is covered by either placing the phone in your pocket or turning it screen down in the table. The screen will completely turn off. Once removed from the pocket or turning it face up, it will normally turn back on. Easily seen by testing this. However, mine has stopped turning off on either example. It stays on constantly no matter what. I have done a factory reset twice before and it fixes the issue but that is getting old. Does anyone have this issue or advice on how to fix this? I would be very grateful. I'm tired of resetting my phone.
Thank you
Sent from my LG-H901 using Tapatalk
No one knows eh? It's a mystery to me as well. Wondering if it's a proximity sensor problem. ?
Sent from my LG-H901 using Tapatalk
Hmm.. I installed a few applications to test the proximity sensor. Turns out it's not working. This in turn prompted me to search of the issue with regards to the proximity sensor malfunctioning. I discovered a couple threads declaring similar problems with the second screen after folks disabled system applications.
My phone is not rooted but I've disabled Instagram and Facebook through the applications settings on the phone. This was dinner sometime shortly before the recent malfunction. These of course on the v10 are system applicants, at least on T-Mobile.
Long story short, the only way to fix it sounds like what I've been doing, factory reset.
Sent from my LG-H901 using Tapatalk
The proximity sensor is definitely not working. It's pretty obvious during a phone call as well. I'm going to utilize LG bridge to back up tomorrow. Then I'll do a factory reset.
There's definitely a connection when disabling system apps through the normal application settings route. Not sure how many are affected by this. But if it ever effects someone else, remember this thread.
I'll post results tomorrow. At this point I'm convinced it's not hardware related and if things return to normal afterwards. That'll confirm my suspicions that there's a bad bug floating around to what degree I'm not sure.
Sent from my LG-H901 using Tapatalk

Categories

Resources