I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
mredmond2012 said:
I am having a problem where all vibration/haptic feedback will just randomly stop working completely. Then a few hours (and sometimes days) later it will randomly start working again. It will keep working again for a few hours or maybe days, and then randomly stop again. There seems to be no pattern to it.
I have no idea what is causing this. Has anyone else experienced this, or does anyone have any idea how to fix it?
This is extremely frustrating as I am someone who never uses the ringer; I just always have my phone on vibrate.
I'm running the latest stable release of CM 7.1 for the Evo 4G, but I had this happen before on stock Sense as well.
Click to expand...
Click to collapse
I am having this same issue as well. It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly. I've had that happen where I have my hands in my pockets and next thing I know I've accidentally got my Facebook up and running and typed half a book in the status field.
Again, I know that sounds silly but I ask because it's happened to me before.
Concordium said:
Does the phone ever always (or never) vibrate under a certain circumstance? i.e. incoming text, email, incoming/outgoing call, typing, etc.? Also, do you have any toggle widgets that could affect vibrate/ringer status?
I ask this because, and this may sound silly, it may be that you are modifying settings unknowingly.
Click to expand...
Click to collapse
That's fine, its an important clarification to make. But no, I am absolutely sure I have not changed any of the options unknowingly. As I said in the OP, ALL vibration/haptic feedback will cease to function entirely. I've often had it happen that in the middle of typing something, the haptic feedback for the keyboard will just go away. Immediately after this if I check the soft key buttons or test the vibration for notifications, none of these will produce any sort of vibration response either. Then randomly a few minutes, hours, or days later, all haptic feedback will just return. Its been an extremely strange and frustrating issue.
4nth0ny said:
It must be software related because the vibrate function works just fine when the phone rings. I am running CM 7.1 stable on an Evo 4G. I noticed the issue as well on CM 7.0.3.1 or whatever the latest stable build was on CM.
Click to expand...
Click to collapse
For me, when the vibration stops working, it stops working for everything, even when the phone rings. But that's what I can't figure out: if it is a software or hardware related issue. I was having this problem on stock Sense, and I figured if it was software related, perhaps flashing a new ROM (in my case, CM7), would fix it. However it hasn't, so I'm beginning to think if it is indeed a software issue, it must be a bug somewhere very deep within the code, otherwise it has to be a hardware issue. But if its a hardware issue, I can't figure out why it would randomly stop/start working like it does, and the thing is, most (75%) of the time, it is working. Its just the other 25% that annoys the hell out of me. That's why I thought I'd ask and see if anyone else had experienced it or found any solutions.
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
infamousteeboy said:
Its a CM7 thing...Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
Well like I said before, I was having this problem on my stock Sense ROM.....
infamousteeboy said:
Its a CM7 thing I've noticed it on Xplod, Decks, and CM7 I don't really mind it cuz my ringers are loud as hell but yeah its pretty weird :shrugs:
Usually AOSP ROMs for some reason have that problem cuz on sense ROMs it never happens
Click to expand...
Click to collapse
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Concordium said:
I've never had that problem on CM and I've been using many different versions of it for a long time. I don't know if I am lucky or what but people complain about a lot of issues that are claimed to be CM issues....yet I've never had a single one of them.
Click to expand...
Click to collapse
Well I kinda had the same problem that he's run into on CM but I figured it out but I figured since he's had the problem on a sense ROM also then maybe its not the ROM but I jus went into everything that had the option to vibrate and turned them all on cuz I've flashed a couple ROMs and the vibration would be off I try not complain about anything about any ROM its a person hard work they've done for free I try to figure things out on my own as much as possible before I create a thread not bad talkin the OP but jus sayin you know?
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it. I think it's just a crappy vibrator. (If there's a better name than "vibrator", please someone tell me.)
I had vibration problems on my first Evo as well, it was never rooted. My second Evo was a HW004 and the haptic feedback was perfect - it was softer instead of the shock-like haptic feedback I've experienced with my 003s. My current and third Evo is also a 003, so I assumed it had something to do with the motor used in 003s.
I've just turned haptic feedback off. I thought I'd miss it, but I've gotten used to it. I still use have my phone set to vibrate for notifications and calls and I've seen fewer issues.
If you think you can go without, I'd suggest turning haptic feedback off. Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Sent from my Evo + MIUI using Tapatalk!
plainjane said:
I don't think that it's rom related. I've been having issues with my haptic feedback since I got the phone, even before rooting it...
...Otherwise, unroot and take it into Sprint. You may have more luck calling, because if you can't replicate the issue in front of them then they can't do much.
Click to expand...
Click to collapse
Yeah, its definitely not ROM related...I don't know if people aren't reading the posts, but I've said several times that this occasionally happened on stock Sense, both before and after rooting.
Dang. I didn't want to have to bring it in to get it fixed, but I guess that's what I'm gonna have to do if its a hardware problem...I was really hoping it was software related or if someone would know of a way to fix it so that I could avoid dealing with warranty services...I got suckered into the Best Buy warranty, and it turns out that even though they either give you a new or refurbished model, they make you turn yours in and wait 5-7 days for the replacement to come in instead of ordering the replacement and then doing a trade with you when it comes in. I already experienced it once before when my USB port broke... :/
Not being able to replicate the issue is my main concern since sometimes it works and sometimes it doesn't. Trying to get it to stop working at a time when I can actually run out to the store is gonna be a pain...And I really don't want to waste a trip to the Best Buy store only to have it start working again with me trying to tell the GeekSquad Agent, "I promise, I promise! It was broken just 5 minutes ago!!" I can't imagine how many of those they have to deal with....
Related
(Info: currently running Myn's Synergy with Godmode and the Chop Suey 0.7 kernel, at least I'm pretty sure that's the version.)
The title sums it up -- I can't answer phone calls from my phone. Whenever I get a call, I get my phone out of my pocket, and then move the little phone icon to the circle (sense 3.0 lock screen), and then the phone dismisses the call. Sometimes it does so before I even get to touch the phone icon.
It also takes far longer than usual before it will let me call back, like it's not responding. I can get into the phone application, then I hit the number to call them back, and nothing will happen for like 30-45 seconds, then it will finally call.
Anyone else experiencing this? Any suggestions on fixes?
It's happened on-and-off since I started using Gingerbread ROMs, but recently it's been far more regular. I haven't been able to actually answer a phone call in almost a week.
I've never seen an issue like this.
You may want to try re-flashing your ROM/Kernel.
After wiping everything, that usually clears up "odd" issues.
[Not to sound insulting] have you restarted your phone since this issue started?
mattykinsx said:
I've never seen an issue like this.
You may want to try re-flashing your ROM/Kernel.
After wiping everything, that usually clears up "odd" issues.
Click to expand...
Click to collapse
I'm going to try flashing the non-Godmode Synergy ROM. It seems to be happening more on this one than on others in the past.
mattykinsx said:
[Not to sound insulting] have you restarted your phone since this issue started?
Click to expand...
Click to collapse
I have, yes.
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Naturesretard said:
I've seen a similar post to this way back in the day when I first rooted my phone, but since then have been unable to relocate said post, so I'll just post here as I've noticed this to be a constant problem, perhaps GB related.
Days where I don't make any phone calls I get decent battery life, about 1% every 2 hours and that's listening to music. But god forbid I have to make a phone call because then Dialer remains on consuming my sensor in spare parts. I've disabled just about everything in call settings related to sensors and even tried turning my BT on as I read it might fix it, no dice. The only way to fix atm is to restart or perform a hot reboot.
Anybody else experiencing this or have found a fix? Currently running Decks 1.3d and thinking of going back to a Sense rom cuz I never dealt with this crap before I tried AOSP, even though I love and prefer AOSP over Sense.
Click to expand...
Click to collapse
I would look for the topic about wake lock, there is a possible fix in there if I remember right. Also could try to reflash decks, I've never had a problem.
Sent from my PC36100 using xda premium
I agree with the guy above me, you should check the thread of whatever ROM your using as well, and for a quick fix you could always just push the Power/Screen Lock button
http://forum.xda-developers.com/showthread.php?p=14814224
Sent from my PC36100 using xda premium
Hello xda members! I have been experiencing a strange problem with my "T-Mobile G2"'s microphone and would like to share it with you in case you had any insight on it:
My phone's microphone is not working - I cannot use voice input, music recognition services, etc. all it picks up is silence. What makes it a "strange" problem? Well, the microphone will work during calls, but ONLY IF I first snap out the keyboard and then snap it back in! Sometimes the microphone will fade out and then go silent again, at which point I'll open/close the keyboard again so that the other party can hear me again.
I thought it was software at first, but then I flashed it to stock and still had the same issue. Now I'm worried it might be a problem with the ribbon cable that connects the two halves. Have any of you ever heard of a similar problem? Any suggestions as to how I might fix it?
If it is intermittent and you reflashed then my guess would be hardware like you suggested.
Most likely you mic is loose. Does it behave the same as opening and closing if you just hit it or shake it?
Sent from my ghdudsjihfr using dhhcdfhuf.
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
jervill said:
Thanks for the replies, I honestly didn't expect any! Interesting thing.. I flashed MIUI yesterday and now it feels like the problem is fixed. I've noticed a slight lag before the mic responds the first few times but now it's spot on. I don't see why flashing to stock didn't fix it while flashing to MIUI did so I think it's just a coincidence and that this is still a hardware issue.
I'll try and poke around explore this more when I get more time.
Click to expand...
Click to collapse
Do you superwipe?
killj0y said:
Do you superwipe?
Click to expand...
Click to collapse
Yup I did use superwipe.
Incidentally, the issue returned after 2 days of working perfectly. Doing a wipe and then installing that same ROM fresh (not a backup) did not fix it so that new most likely ROM had nothing to do with it. I'm giving up then and calling this a hardware issue, period. I guess it's a good thing that the HTC One phones are are coming out soon!
So i installed 7.2.0RC1 on my desire and it worked perfectly for 2 days but i've noticed this morning that when im getting calls or messages the phone isn't making a noise and notifying me of this.
I checked that I wasnt accidently on silent and I wasnt, so checked volumes, all ok, and then I decided to look at the ringtones and select a different one and where each one is supposed to give you a little preview of the tone im getting nothing.
Im really at a loss, has anyone else had this problem or knows how to solve it, its handy being made aware when someones trying to contact me
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
stankyou said:
I had this on the nightly prior to the RC1. Reboot and the ringtones should be back but you have to re-assign them I think.. and yeah it will probably happen again.
Click to expand...
Click to collapse
Tried rebooting and still nothing off previews or anything, its just kinda weird for a RC for this to happen, might have to go back down to 7.1.0 until the bugs are ironed out, thank god for nandroid.
Still might have a solution pop up here before i get round to doing that
Did you modify the rom? Change or remove ringtone files you don't need?
Even I had same problem various times. Rebooting solves the issue everytime.
I didn't modify the rom at all and rebooting doesnt solve it, come to think about it, its happening since i used a pair of headphones for the first time
Do you use any Bluetooth headset? Usually when I use mine it happens what you have described and the only quick fix was to make a reboot. I didn't tested it yet on CM7.2 RC1 but the issue was present in CM7.1 Stable.
I use Rings Extended, it`s perfect
Today I tested the CM7.2 RC1 ROM with my Bluetooth headset and so far it is working with no problems (no sound issues like you mentioned). Now I just have to see if it would also stay this way in the few days.
I also found that some users had the problem described in the first post when they were using usual cord headphones but so far I hadn't experienced any problems with them although I'm suing them almost every day since the CM7.2 RC1 ROM release day.
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2451 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Edited: Fat fingered the model #. Fixed.
simplicityy said:
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2541 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Click to expand...
Click to collapse
This might be obvious to you, so just ignore if you know this.
When holding your phone in your hand like you're texting in portrait mode, there's a switch top right and on side of phone.
Adjust the switch so it's down.
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
kevp75 said:
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
Click to expand...
Click to collapse
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
simplicityy said:
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
Click to expand...
Click to collapse
don't know if they are aware. just to add to the weirdness of it... for me... after the second time, the setting sticks...
i have this problem with my 8 pro, the phone doesn't ring and i think it goes straight to VM? seems like something broke with one of the latest OP updates?
There's no such version as CPH2541.
And here it works perfectly. Factory reset and try again.