So.. i have had a weird problem for quite awhile now but have been putting up with it..
When on a voice call when the screen goes off it will mute the mic, leaving the other person asking if i am there.. i have to shake the phone or hit the power button a bunch. It also doesn't wake up instantly when that happens, almost like its in a deep sleep. I don't have any battery saver apps or anything installed....
I am using CM11 right now with FL24 modem, i have tried other modems.. same issue.. This issue also happened on other roms incluing vanir and others...
I did a search and found one other person with the same exact issue.. but no fix posted, was hoping someone might have an idea on how to figure this out.. thanks..
Experiencing Similar Problem
I've been experiencing a similar issue for a bit over a month, too. I'm not quite sure if it was when the screen went off, but certainly within 15 seconds of making or receiving a call my mic cuts off. It sometimes comes back after -- I don't know if that's because I shake the phone around or otherwise get the screen to come on, although the mic turning back on and the screen turning back on do not happen at the same time.
I'm also on CM11 with FL24 modem on a Samsung Epic 4G Touch, which makes me suspect it's the same problem. Do you have a link to the other forum post?
I suspect it's a relatively recent regression with CM, because I installed CM11 on the phone at the end of October and everything was fine. I first started experiencing the issue a few weeks thereafter. I can't recall if it happened after upgrading CM, or if It was after I installed Google Voice (since removed,) or if there was no particular prompt.
Related
I've had this issue happen a few times, so I disregarded it, but just a few minutes ago it happened 3 times in a row. Here is what happens:
I'm in the middle of a phone call, and suddenly I hear a beep, and I look at the phone and the call was disconnected (I'm back on the 'Phone' screen). I then realize that the phone becomes unresponsive (the screen doesn't respond, same thing goes for the Home/Menu/Back/Search buttons).
The only thing I can do is press the top 'Off/Lock' button to shut off the screen, then press it again, and everything goes back to normal.
This happened 3 times within 5 minutes.
Is anyone else experiencing this problem? If so, any advice/solutions?
My 30-day purchase window is up in about a week, so I'd like to get this resolved before then to avoid any headaches.
Thanks in advance.
Have you loaded any apps? Modified the phone at all?
I've never seen this type of behaviour before.
Thanks for the reply. No, I haven't rooted it, or loaded custom time or anything. The only thing I've done is just download/install some Apps from the Android Market, that's it.
What do you all think I should do?
*bump*
I think I may have fixed the issue -- I had the Google Voice installed on my phone, and when I uninstalled it, I haven't had the problem since (it's been about 3 days).
Has anyone else experienced any stability issues or glitches using the Google Voice app?
My mom has been having this issue with her stock 2.1 Inc... She says the screen suddenly stops working and all that will work is the power button and volume rocker. Says it usually happens mid call.
PS. she doesn't have google voice. And google voice doesn't cause this issue on my Inc.
Yeah, it just happened to me again, and I don't have Google Voice installed, so that's not the culprit.
Is anyone else having this problem? Please let us know in this thread - I am going to swap the phone out tonight at my local Verizon store.
It happens to me frequently. Before and after I rooted. Let me know what Verizon does about it.
Sent from my Incredible.
I got the phone replaced at the Verizon store a couple of days ago, and I have yet to see the problem. However, ill keep a close eye out and will post another update in the next several days.
Sent from my ADR6300 using XDA App
Hey all,
I was unable to find this same issue, so if it was posted already sorry, but i am having an odd one. My phone seems to be freezing randomly after phone calls, staying on a black screen. However the led light still blinks, if i have a message or whatever, and the hard keys on the front do light up. It doesn't happen all the time, just some times after a call, and only happens with phone calls, and i need to pop the batt out to get it working.
Any ideas?
Thanks
JC
I do have the overclocktool installed but don't think or know if that would cause it
Do you have oct V1.5? If you do that is the problem there are numerious complaints in that thread about V1.5 locking the phone up during or after calls. It has to do with the dynamic clocking. some people have had luck by turning the dynamic clocking off . It didn't work for me so I went back to V1.4.1. I'm sure the issue will be fixed in the next release.
Im not sure if maybe i dropped the phone and this happened, but everything was fine up until i flashed the teamfenix mod. That's when i started to notice that i could barely hear what people are saying unless i have my phone on speaker. Ive reflashed and just went back to cm 6.0.1 and the problem continues....anyone have any ideas or the same problem?
bump............
There's a few reports over in another part of the MyTouch forum where people are having similar problems. Either low call volume and high Skype volume or vice versa.
I'm not sure if they've found a fix yet, I haven't had these issues with CM 6.1 so I haven't checked the thread recently, but it seems to be a problem a few people are experiencing.
i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help
Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300
Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.
I know the proximity sensor is not functional with the Rhodium400. My wife and I are both running the newest version FRX 7.1 on the .27 kernel.
She had issues with Windows Mobile getting a data connection, and it would carry over to Android. So I dd a hard reset on Windows Mobile and started her Android from scratch (as it was having other slowness and issues also). Ever since then she tells me (and I have heard this in call) that every time she puts her cheek or face to the phone it will sound as if the call dropped but it doesn't drop really. She can't hear me and I can't hear her, but as soon as she takes her head away she and I can both hear again. This doesn't happen all the time, and is likely only happening when XDAndroid has not been rebooted in a few days.
I have not been able to confirm it by sitting right beside her and calling and confirming the problem, but I plan to do so tonight. At first I thought she was just muting me because she was ticked at me...don't ask , but she isn't smart enough to come up with something like this, because technically it sounds like the proximity sensor is mucking up the phone call which I thought was not possible from everything I have read. I even had her turn the power button off at the top to turn the screen off, to make sure she wasn't bumping any buttons. The way it looks, it almost sounds as if the phone is inadvertently trying to place another phone call and putting the first phone call on hold.
Has anyone else had this issue? Doe anyone think this is likely a proximity sensor issue, or have any advice for when I get home tonight and start playing with the phone?
Supposedly also this issue was going on with her in the car and the phone plugged into a car charger. She called me back with it not on the charger and it is not messing up anymore. I don't know if it is coincidence or not, since it wasn't always doing it to begin with.
Never heard of this, almost sounds like a hardware failure.
Run WinMo for a few days, see if you can recreate the problem there. If so, there's something going haywire with the physical hardware.
I get a situation kind of like this in Android, but not WinMo. Basically if I recieve a call it's about a 50/50 chance that this happens. I can't hear them and they can't hear me. There is no sound at all, like the speaker and mic don't even turn on. However, mine doesn't seem to have anything to do with the proximity sensor as it does it as soon as I hit the answer button and moving the phone away doesn't fix it. Also, it's only when recieving calls, outgoing calls work all the time.
I've had similar problems, but quite a bit in the past, making me think mine was software or settings. So don't discouraged!
My thinking is, since auto-mute to rear speaker/mic system is a 'feature', that maybe that system gets triggered. Check those settings, and that level/bubble calibration stuff.