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....
Hey guys, my galaxy nexus has started acting up. If I make a call to someone I can hear the person talk, but they can not hear me. Now the person I call when they try talking, they just hear there own voice back when they talk. If they said hi, they would hear themselves say hi back. Now the strange part, if I turn my phone to speakerphone everything works fine?!? Can anyone make anything out on what's going on with this? Suggestions? Thank you
Snake42490 said:
Hey guys, my galaxy nexus has started acting up. If I make a call to someone I can hear the person talk, but they can not hear me. Now the person I call when they try talking, they just hear there own voice back when they talk. If they said hi, they would hear themselves say hi back. Now the strange part, if I turn my phone to speakerphone everything works fine?!? Can anyone make anything out on what's going on with this? Suggestions? Thank you
Click to expand...
Click to collapse
What ROM do you use?
I'm using winners00 build of CM10 JB rom. I have been using the same rom for the past three to four weeks roughly. No problems until now
Snake42490 said:
I'm using winners00 build of CM10 JB rom. I have been using the same rom for the past three to four weeks roughly. No problems until now
Click to expand...
Click to collapse
I'd check with the dev of that ROM (or a forum support thread for it) if this problem has been encountered before. If not, I'd try flashing stock factory images for your device to see if the problem persists. If it does, it's likely to be a HW issue.
Hi,
I have a S4 Mini Duos (I-9192), stock ROM, baseband version: I9192UBUAMH1
The problem is:
While I am talking, after some time, the other people is no longer able to hear me.
I can hear him as normal, but he cannot hear me.
That happens randomly --- at least it seems so at present, I haven't found any patterns yet.
That happens no matter I use the phone or a earphone(headset).
That happens no only when using the build-in phone app, but also when I use Skype.
Thanks!
Holding the phone with your left hand and your little finger covers the mike, yes?
Vierko said:
Holding the phone with your left hand and your little finger covers the mike, yes?
Click to expand...
Click to collapse
Sorry for the delayed reply.
As I said, it happens even when I am using earphones. So I don't think it is because I cover the mic.
Thanks for the response though.
ccsasuke said:
Hi,
I have a S4 Mini Duos (I-9192), stock ROM, baseband version: I9192UBUAMH1
The problem is:
While I am talking, after some time, the other people is no longer able to hear me.
I can hear him as normal, but he cannot hear me.
That happens randomly --- at least it seems so at present, I haven't found any patterns yet.
That happens no matter I use the phone or a earphone(headset).
That happens no only when using the build-in phone app, but also when I use Skype.
Thanks!
Click to expand...
Click to collapse
Hi boys
I have the same problem andon the same phone and I don't know how to solve it. Anybody can help please...
Hello everyone, as my title states. I am having a problem with my proximity sensor when in a call. I have a sprint galaxy note 2 (L900) and am currently running CarbonROM's nightlies (4.4.2). Before I was using the 4/10/14 nightlie and when I was in a call the sensor was stuck and kept my phone dark until the call ended. But now with the 4/17/14 nightlie, the phone is constantly on while in a call. Has anyone else have this issue using CarbonROM? If there's a fix please let me know. Much appreciated.
thaittnguyen said:
Hello everyone, as my title states. I am having a problem with my proximity sensor when in a call. I have a sprint galaxy note 2 (L900) and am currently running CarbonROM's nightlies (4.4.2). Before I was using the 4/10/14 nightlie and when I was in a call the sensor was stuck and kept my phone dark until the call ended. But now with the 4/17/14 nightlie, the phone is constantly on while in a call. Has anyone else have this issue using CarbonROM? If there's a fix please let me know. Much appreciated.
Click to expand...
Click to collapse
I'm currently on Carbon ROM nightly version 4-17 and I have the same issue. Did you find any info on this bug in the Carbon ROM forum? I think this needs to be looked into because I don't like face dialing while talking on the phone. lol
tx_dbs_tx said:
I'm currently on Carbon ROM nightly version 4-17 and I have the same issue. Did you find any info on this bug in the Carbon ROM forum? I think this needs to be looked into because I don't like face dialing while talking on the phone. lol
Click to expand...
Click to collapse
No I didn't find any fixes for it. I talked to one of the developers and they are looking into it BC when I entered the live chat I asked the same question and they responded with "let me guess, note 2?"they're not sure what's going on with the notes that is causing the bug. But I've been looking at the change logs hoping they fix it and my phone volume is really low when I'm talking to someone as well. Sometimes I can't even hear the caller so I have to switch to speaker :/
Thanks for the reply. As for the low volume during calls. You may already know this but try lowering the volume then raise it back up and that should increase the volume a lot. It's a bug in some AOSP ROMS.
I have tried that and sometimes it works and sometimes it doesn't, unfortunately.
Sent from my SPH-L900 using xda app-developers app
The proximity sensor issue has been fixed in the latest nightly build 4-23. Although now I can't sync my browser in Google account sync settings. All others seem to sync except browser. Could be another bug...
This is happening to me and I've seen other users report this in some custom roms. I'm currently on Aosip, are you guys not experiencing this or somehow fixed it?
Royalfox said:
This is happening to me and I've seen other users report this in some custom roms. I'm currently on Aosip, are you guys not experiencing this or somehow fixed it?
Click to expand...
Click to collapse
Yes I have this issue as well, send me the fix please when you find it.. Thanks
WHATSAPP HAS some tricky thing going on! in all custom roms
1. voice call volume is too low
2. whenever audio note is played, screen goes off for couple of secont
3. you cannot sent voice note less than 1 sec!