I have having issues with the haptic feedback. It will work most of the time when I first unlock the phone, but it will randomly stop working as I am using it. An example is when I am typing a text message. the haptic feedback will work for the first couple of words and then it will just stop. Then all of the buttons on the bottom will not give haptic feedback also. Sometimes when I lock it and leave it alone for a minute it will work again. I do have it enabled in the settings. I have tasker installed and I thought that could have been messing up so I uninstalled it and it is doing the same thing. I even did a factory wipe and left everything uninstalled to make sure it wasnt any of my apps messing it up and it still did it. Is anyone else having issues? I am trying to see if there is something wrong and if i need to try and get it replaced. It is rooted and I have the telsa rom on it right now so I want to make sure I am the only one having issues before I unroot it and take it to Verizon. I have also tried it on different roms and kernels and it does the same thing. Thanks
If you are using any kernel other than stock you will have this issue, they all do. Same happens with me on the TB and happened to me on the Incredible, don't know why or what causes it, but it happens.
yukongt300ex, you have just described exactly what I have been experiencing with my Thunderbolt (in fact it has just done it while typing this post) and I'm running stock Sense..
Does anyone have a fix for this?
That is strange. I figured more people would be complaining and we would be hearing more about it if it is that common.
Yet another reason I cant wait for cm7!
yukongt300ex said:
That is strange. I figured more people would be complaining and we would be hearing more about it if it is that common.
Yet another reason I cant wait for cm7!
Click to expand...
Click to collapse
I think most of TBolt owners have the haptic feedback turned off
And soon as I get use to it not providing any feedback, it comes back... it's just teasing me lol
the same exact thing happens to me. in the middle of texting, the haptic feedback will just shut off throughout the whole device, including the soft keys on the front on my thunderbolt. i've found the stopping if usually triggered by me typing too fast for the thunderbolt to handle. for instance i'll type 3-4 words it won't register, then all the haptic feedback with come at once in one super long vibrate, and then it just shuts off for good, until i put the device to sleep for 5-10 minutes. then repeat -__________-
Related
I've had this occur three times when using my phone if i lock my phone and someone calls me or texts etc notice... my phone locks and will not respond to touch/unluck phone is not froze as the time changes. But there is no way aside from rebooting to fix this. anyone experience similar? is this a 1.5 issue or just a eris issue?
i've run into this quite a bit too and usually end up having to reboot with send+end+vol_up no idea as to what is causing it tho
I have read around its from the OTA Update and you must *288 on the phone to reprogram it. its rumored to solve it also a hard reset is rumored. Im trying the *288 and will report back.
If worse comes to worses, just run the RUU posted in the Desire Dev forum. It'll do a full reinstall of the phone's software and wipe your data, but it might fix your problems.
Yup I feel I may be doing that, seen that posted as well and commented the same. I just cant wait for 2.0/2.1, Root id like but its not itching me as much as the 2.0/2.1 i want.
I have been having the same problems that it sounds like many are having. My screen freezes when I have an incoming call causing me to miss the call. Very annoying. I basically have to have the phone at stock settings for it to work correctly. Also when I have a reminder from my calendar go off it freezes so I cant slide it down to turn it off immediately. It takes about 15-30 seconds for the slider to work in both cases.
I've had this issue since the update. I've run the ruu and did a factory reset. Nothing has helped. After several hours on the phone with tech support- the new Eris is in the mail.
so far since ive done *288 to reprogram the phone i have not had the lockup issue occur.
Don't you mean *228, or is that a new one?
yes *228 sorry
I tried *228 numerous times. The new phone just froze on me this morning at the lockscreen. I figured it had to be software related.
i had the same problem it happen to me 3 time had to restart my phone i think there is a bug in the software it happen after update
Lately my tab has been turning off by itself and it takes me a long time to turn it back on by holding the power button. Has a fix been found for this problem yet? I'm a little worried that one day the thing won't turn on again. Sometimes the tab is charged when it turns off, and I'm never using the thing when it does, so battery isn't really the issue. Any suggestions?
Gja88 said:
Lately my tab has been turning off by itself and it takes me a long time to turn it back on by holding the power button. Has a fix been found for this problem yet? I'm a little worried that one day the thing won't turn on again. Sometimes the tab is charged when it turns off, and I'm never using the thing when it does, so battery isn't really the issue. Any suggestions?
Click to expand...
Click to collapse
Are you rooted? Running a custom ROM? Running any extra mods at all?
No, I'm fully stock,never been rooted. Willing to root if the problem can be fixed though through a rom or something
i've made good strides in combating this.
But, you must have CWM installed in order to flash.
When you are ready to do this, then head over to the dev section, kernel thread.
In the meantime, set wifi to never sleep, and see if that cures some of it.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
To be honest if you have a completely stock machine I would call samsung and get them to check it, it sounds faulty. I work for a large computer retailler and haven't seen a single one behaving like yours out of hundreds.
Brian
Brian-UK said:
To be honest if you have a completely stock machine I would call samsung and get them to check it, it sounds faulty. I work for a large computer retailler and haven't seen a single one behaving like yours out of hundreds.
Brian
Click to expand...
Click to collapse
Mine also does and I have seen posts in other forums of others complaining of smae thing.
Ian
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
I googled vibration not working galaxy s2.
Found this but I didn't watch it as I am not on wifi.
http://www.youtube.com/watch?v=3JA3PXNYjJM
gerbs said:
After searching and trying to fix this for a few weeks, I'm finally reaching out for help, I really don't know what else to do.
My vibrate function seems to be completely dead.
I rooted the phone a while back when I first got it and everything was perfect on the first ROM I was using. I then flashed to a different ROM and lost haptic feedback but kept the other vibrate functionality (alarms, texts, etc.) Sorry I don't have specifics on the ROMs but I know the issues may be have been due to the i9100 porting stuff causing haptic issues
My vibrate functionality kind of slowly stopped working.. Sometimes when the headphones were in it would work fine, then I'd take them out it would stop.. and Vice versa.
It does SOUND like it's a hardware error.. But that seems a little silly since there have been multiple issues floating around w/ ROMs and haptic/vibrate problems.
Before I take any further action, anyone have any suggestions? I'm thinking to re-stock the phone entirely (unroot, stock kernel, stock rom) and see if that does it.. I'd rather not send it in to get replaced but I guess that would be an easy option if I can't fix it via software.
Click to expand...
Click to collapse
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
jcordova23 said:
Same happened to the last phone I had, the HTC Aria. I ended up just taking it to an AT&T store for replacement. I even tried going back to stock. Nothing worked on mine.
Sent from my GT-I9100 using XDA
Click to expand...
Click to collapse
Yeah, already called att for a replacement and its on the way. Finally decided to give up after getting it back to 100% stock (kernel rom bl etc).
I literally tried everything. But in the end it makes sense that it is a hw problem since so many others have run into it too. Poop.
i watched the video you showed. i started to mess around with my settings while i inserted my headphones on. Somehow, everything is fixed but the vibration is not as strong as before.
Furthermore, my aux does not work with this phone sometimes. It would need to be connected a certain in order for it to work.
I probably dropped my phone while I was working out while i have my headphones on. The connector probably got messed up in the process.
I might need to send my phone in for a replacement. Since i'm not under warrenty, i might send my phone to a lab. I'm pretty sure they can do something about it.
iichrisphamii said:
I might need to send my phone in for a replacement.
Click to expand...
Click to collapse
The vibrator turned out to be a hardware issue for me as expected, fyi.
This thread started off as a mod request because I thought it was my proximity sensor causing the issue. After further investigation I'm completely stumped as, disabling my proximity sensor didn't work (or the disable wasn't effective, not sure). Highly modified original post to make the thread relevant to the direction that its going.
Issue details - screen will not stay on while in call unless enabling speakerphone mode. After call initiates, screen promptly turns off. Pressing power key wakes the screen up but the second a finger is touched ANYWHERE on the screen it turns off again forcing one to wait for the call to disconnect itself or pull the battery to hard reset the device (whichever comes first). The issue seems to be somewhat inconsistent, as some calls I get more responsiveness out of the screen than others. It DOES seem to be software related as this issue is very, very specific. It only happens while a call is active. The screen and standby functions work 100% of the time otherwise.
Facts:
-issue was not present before obtaining s off and upgrading to ICS
-issue is present when doing a clean install of the Rom (energy, though I'm inclined to think its not Rom related for obvious reasons)
-issue persisted even when restoring an old back up of a gingerbread state from days prior to obtaining s off and flashing ics.
I know I'm not the only one experiencing this issue. I've spoken with several others who are having the same problem. Hoping an xda elite on here might be able to figure out what might be causing this to happen. Any help would be greatly appreciated.
----------------------------
(Original post) -
My proximity sensor is on the fritz and making it impossible to multitask anything while on a call (so much to the point where sometimes I can't even hang up and have to pull my battery). It's killing the screen the second I touch the screen anywhere while on a call.
Can someone tell me how to, or would someone even be able to put something together that'd allow me to disable my proximity sensor entirely? I don't really need it anyways since I can just manually hit standby before I hold my phone up to my ear. Any help anyone could provide would be greatly appreciated =)
Sent from my HTC_Amaze_4G using xda premium
Too tricky? No one? I know I'm not the only one encountering issues with their proximity sensor freaking out while on a call.
I guess ill just have to live with the inability to do anything on my phone while on a call unless I activate the speaker. Not the end of the world.
But if anyone can write a script/throw something together that'd turn it off you could save ne a lot of trouble and help others that are having this issue as well. Nbd ::shrugs::
Sent from my HTC_Amaze_4G using xda premium
would a piece of tape work? just tape it over the sensor.
No cuz then itd just stay off. The problem is that the screen won't stay on while in a call. If I touch the screen anywhere while on a call the screen shuts off immediately. =( very annoying. Can't even hang up sometimes.
Sent from my HTC_Amaze_4G using xda premium
Should work even though it's a different device, but haven't tried myself so no guarantees
How to/Solution to disable proximity sensor incall
Just a quick search found that
I tried to find the file in sys/class/optical-sensors/proximity .... But I didn't know which of the other files needed to be edited.
Wait....I sent this with Tapatalk?
Nativedude said:
Should work even though it's a different device, but haven't tried myself so no guarantees
How to/Solution to disable proximity sensor incall
Just a quick search found that
Click to expand...
Click to collapse
Totally worked. My proximity sensor seems to be off but oddly the screen still won't stay on while in call unless I have speakerphone enabled lol.
I figured it HAS to be related to the proximity sensor cuz the screen shuts off the instant my finger touches it... But apparently the problem is related to something else entirely. Thanks though =)
Just a slightly annoying glitch I can live with. Guess I'm gonna have to lol
Sent from my HTC_Amaze_4G using xda premium
AndroidAutobot said:
Totally worked. My proximity sensor seems to be off but oddly the screen still won't stay on while in call unless I have speakerphone enabled lol.
I figured it HAS to be related to the proximity sensor cuz the screen shuts off the instant my finger touches it... But apparently the problem is related to something else entirely. Thanks though =)
Just a slightly annoying glitch I can live with. Guess I'm gonna have to lol
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Totally reflash your rom, leak, whatever.. that bug sounds like something didn't take fully on initial setup. Can't hurt to try. I say this because it sounds VERY similar to the problem I had with my Vibrant.. and many of the issues I keep reading people having make me think that the install methods aren't perfect and fool proof.
If you're on the leak you'd have to make a nandroid, but if on a rom that doesn't wipe data partition you can just wipe the system and reinstall- or worse case restore a nandroid of data partition.
Silentbtdeadly said:
Totally reflash your rom, leak, whatever.. that bug sounds like something didn't take fully on initial setup. Can't hurt to try. I say this because it sounds VERY similar to the problem I had with my Vibrant.. and many of the issues I keep reading people having make me think that the install methods aren't perfect and fool proof.
If you're on the leak you'd have to make a nandroid, but if on a rom that doesn't wipe data partition you can just wipe the system and reinstall- or worse case restore a nandroid of data partition.
Click to expand...
Click to collapse
Yeah. That was my first suspicion. Sadly it persisted even when I restored a backup of when I was running nrg's gingerbread Rom. Think it might be some kind of weird hardware failure since it persists no matter what I do (clean install from scratch with everything wiped/cleared).
Nit a huge deal. If j ever have to look something up while on a call all I gotta do is throw the speaker on which is normally do in that situation anyways he he. Just bothersome when there's an issue you haven't been able to fix no matter what you've tried ya know? =)
Sent from my HTC_Amaze_4G using xda premium
AndroidAutobot said:
No cuz then itd just stay off. The problem is that the screen won't stay on while in a call. If I touch the screen anywhere while on a call the screen shuts off immediately. =( very annoying. Can't even hang up sometimes.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I have the same issue, I thought it was just my phone. It's such an annoying issue, can't even hang up half the time. I love the phone but that one issue is really irking me. I never had this issue til I updated to ICS.
Sent from my HTC_Amaze_4G using xda premium
Headshots4life said:
I have the same issue, I thought it was just my phone. It's such an annoying issue, can't even hang up half the time. I love the phone but that one issue is really irking me. I never had this issue til I updated to ICS.
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
That's the really strange thing of it is that I never had the issue till I flashed ICS as well, but then the issue persisted when I restored an old gingerbread backup. Hopefully someone might see this that might have a better understanding and be able to figure out what's causing this to happen. =L. I'll change the subject of the thread to hopefully draw attention to it.
Question for you (let's compare) are you s off? And what Rom are you currently running? I'm inclined to think its not Rom related since the issue persists even when restoring a nandroid back up from days before I ever obtained s off and flashed ics. It'd be nice to confirm this is happening on Roms other than energy. Don't feel like going through all the steps to flash revolutionary or any of the other ics roms at this moment just to confirm what I already suspect.
Sent from my HTC_Amaze_4G using xda premium
So I recently got my old bricked evolte replaced by Sprint. The one I was given worked fine the entire time the device was powered on. However, once turned off and back on, its screen would not work. It stayed like this for hours, until I finally started playing with it and realized it would come back on after playing with it for a little bit. I also found out that with this error the home screen pops up for a second when powering on your device, and that's exactly what I had. I read up on the error and found out it was a software error, and to reset to factory settings. So, this fixed it, I thought.
So now, after it is apparently fixed, it still does this to some extent. It will do this if the phone has been powered on for a while, and the screen won't stay off for more than like 2 or 3 minutes. Also the home screen doesn't pop up any more like it used to with the other error.
So what should I do? I was thinking of going to Sprint, but my problem is hardly reproducible. It only happens when it's been powered on for a long time, and won't do it twice in a quick succession. I feel that even if I could show them the problem, they might think they've fixed it when they haven't because it won't do it twice. I would like to root my device, but I'm afraid they're going to say that I'm the cause of the problem if I do that. If it's just a software problem though, maybe flashing a custom rom would fix the problem.
What do you guys think? What do you think is the best course of action? Any advice would be greatly appreciated. Thank you.
Never mind, I didn't know Sprint would order you a new phone if it was a minor problem like that. I thought they would only repair yours. So feel free to close this thread.