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.
Related
Hello all,
Recently got my Tp2 and loving it. Initially I got a like new Tilt2 and Hard-SPL and installed latest radio and custom ROM. All is well since then. The problem then arised when I'm incall, suddenly the other party can't hear me and I can hear them perfectly clear. Signal bar shows full 3G signal. I have to end the call and call again. This problem happens everyday and there's no fixed time pattern.
So I thought i got a defective phone from the seller, I sold it and got a new one. It had the AT&T stock rom and stuff on it. I hard-SPL and Security unlocked the phone. All was fine for a day or so leading me to believe my first handset was defective. But to my dismay, my current phone started to exhibit the same characteristics again and I was shocked.
I tried various ROM's even the stock one and different Radio builds still no luck. I'm stumped as I canot believe I received two devices with same problem? It can't be software as no matter which Chef rom i try, the other party suddenly stops hearing me ( sometimes my voice goes very low and then dies out). Here's a key thing I have to do for it to get temp. fixed. I have to blow hard at the microphone and then the opposite party can hear me crystal clear.
I have tried disabling 3G and roaming on Edge, I have tried different locations of my city thinking its related to cell tower, No luck
I am out of ideas and can't figure whats going on. What I can conclude is, during the call, something times out and goes to "sleep" and when i blow hard to the mic, it awakes the mic input. Just talking hard to the mic won't work either...has to be blown hard. My dad say's before he stops hearing me, he hears some "tuck-tuck" sound as if i am brushing the phone against some surface or sometimes he hears the sound as if I just dropped the phone, followed by dead silence on his end untill I blow through the mic. In both instances, i am just casually sitting on the coach.
At this moment I'm dumbfounded and think I'm cursed by HTC lol
I would appreciate any help from this community!
Thanks!
You could try toggling the "Auto Volume Control" setting.
It's under Settings Tab > All Settings > System > Auto Volume Control
Thanks, I will try that..Altough when i checked that, it's usually disabled by default in most Rom's
swatcho said:
Thanks, I will try that..Altough when i checked that, it's usually disabled by default in most Rom's
Click to expand...
Click to collapse
Yeah it's a bit of a long shot. The only source I can cite is a review at WMExperts for the Telus Touch Pro 2:
When holding the phone up to my ear to talk, some callers did note that I sounded far away until I enabled the Auto Volume Control in the phone settings.
Click to expand...
Click to collapse
Source: http://www.wmexperts.com/review-telus-touch-pro-2
Good luck!
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've been having a weird issue with my phone muting the mic during calls. This mute seems to be independent of the mute softkey on the phone (when it gets muted, the softkey is not lit, nor does toggling the softkey unmute the mic). This is incredibly annoying as once it mutes, the only way to continue the conversation is to hang up and redial. This issue occurs both using the phone normally (phone to ear), with a wired headset (so no possibility of cheek activating softkey), and with a bluetooth headset. In all 3 scenarios the mute will toggle on its own, seemingly randomly. I can go through a 40 minute call with no problems, yet sometimes it seems to mute right after I make the call.
Has anyone else had this issue?
This is what I have done to troubleshoot the issue:
1) With the original phone that I bought, I reset that phone back to factory settings and set it back up. Issue still persists.
2) Had the phone swapped out at the same Verizon store that I bought it at. Issue still persists.
3) Reset the new phone back to factory defaults. Issue still persists.
I will try the following:
Reset phone back to factory defaults and not install any apps whatsoever (running only apps that came with the phone, won't disable anything such as VZW Backup Assistant, etc either). Something tells me that this won't fix the problem either.
Does anybody know what I can do? This is a great phone but I'm a little miffed about not actually being able to make calls with it. I called VZW tech support and they are willing to replace the phone, but I basically have to go from a NEW phone to a certified like-new device (which VZW allows up to a maximum of 2 blemishes on the back, which I am not ok with) through no fault of my own.
See this thread on the Google Code bugtracker: (Hm.. I can't seem to post a link as a new forum member.. well its bug ID 24019 on the android bugtracker off of code.google.com) Don't want to munge up a link and piss off a mod or anything.. sorry guys :/
That im affraid is a nasty bug that is yet to be fixed.
Have you experienced this bug? I'd like to hear from members of this forum on if they have this issue, and how they resolved it (if at all). I was surprised that something so blaring isn't on the list of known GNex/ICS bugs (at least not on the one I saw on androidforums.com). I'm just uncomfortable with how the Verizon reps are pretending to not know about this issue...
//Edit: Oops. Found the other thread in this forum on this issue. It seems that I'm describing this as a mic muting issue, whereas other people are describing it with "mic cutting out" so I can never find their posts. Post ID 1403051 in Galaxy Nexus General.
Have AT&T Note 4 since launch. Stock, not rooted or anything like that. Not sure when this problem started because I don't regularly make calls, but I think within the last week or two, possibly after I got the update to COC6 (the update seemed to complete normally, though).
Every time I place or receive a phone call and attempt to use the phone normally (hold it to your head), the person on the other end cannot hear me at all. If I switch to speakerphone, they can hear me and it behaves normally, and if I connect to a Bluetooth device like my car, it also works fine, but if I try to use the phone normally, they cannot hear me. I can always hear them perfectly.
For what it's worth, Google won't pick up my "Ok Google" from the home screen anymore either. Also, I had previously had the option to wake the phone with "Ok Google" disabled, but when I try to enable it now, it hangs on listening to me say "OK Google" 3 times... as if it never hears me say it.
The microphone appears to be working completely normal for everything else I've tried, it's just acting like it's on mute when I'm in a call and not on speakerphone or Bluetooth, and the OK Google stuff isn't working either.
Any ideas? I'm trying not to factory reset... I've searched a lot and not found anything where anyone has solved the issue.
FWIW I had the same issue randomly with my rooted Note 2, and I believe I either fixed permissions or reinstalled the ROM to get it working (can't remember). I wish I could just reinstall the ROM or latest update (COC6) again so I don't have to factory reset. Is this an option at all?
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
pj_rage said:
Of course right after I post I solve it myself, but I'll share the fix for my case in the event that it helps anyone. The left hand bottom mic hole next to the USB port was plugged with some gunk (I could clearly see it plugged up completely). I used a safety pin to carefully clear it out and that fixed it. Works normally now. I had originally ruled out this kind of thing being a problem because everything was fine with speakerphone so I thought the mic was ok, but I guess maybe it only uses one mic or something? I suppose I was also swayed by the fact that my previous Note did have a software problem causing the same thing, so I figured this was probably software too. But nope, good to go after checking the mic hole!
Click to expand...
Click to collapse
Not gonna lie, I checked my mic hole as soon as I read this. XD
I tend to always put my pinky finger over that mic subconsciously. I don't mean to, but it's just how my hands want to hold the phone during a call. I constantly get people saying that they can't hear me though. Then I always notice that my stupid pinky is on the darn mic. Grrrrrr.
Sent from my SAMSUNG-SM-N910A using Tapatalk
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
So does anyone know? Is this simply not a feature of this phone?
Thank you.
bcsteeve said:
This has been annoying since I got the phone 7 months ago.
It doesn't turn off the screen when I take/make a call. I'm constantly putting my caller on hold or even hanging up with my ear or cheek. I've Googled the crap out of this and I've found MANY different settings to check/change - NONE of which exist on this phone.
Click to expand...
Click to collapse
I thought it was just me! I haven't looked for a solution as yet, but if you find one please post back here and share.
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
bcsteeve said:
Actually I did resolve it finally! I installed a different dialer app and it worked with it. I hated the app though, so I uninstalled it. Before I had a chance to find a different app, a call came in (using the default app again) and it worked as it should. I can't explain why, but for me... installing a different app and then removing it got the default dialer to behave correctly.
Now that it works "correctly", I have noticed a quirk with it. I have to wait for an outgoing call to actually be ringing (which can take some time with some calls) before I put it up to my ear or the screen won't shut off until I bring the phone down and then back up. Now, it is *possible* that this was always the issue and I just never figured it out. So maybe the whole app install/uninstall thing is unnecessary. Not sure.
Click to expand...
Click to collapse
I had a same problem too, but did resolved after factory reset. But I don't know where is the problem located, maybe the proximity sensor is very sensitive even with dust.
Sorry, bad English.
Your English is fine
I think you might be right, because my problem now seems to come and go. The screen definitely shuts off, but there's some times when my face will put the call on mute or other strangeness. I've even accidentally sent an email to my Mom, all with my cheek while on the phone with someone else! I had to click the back button 6 or 7 times to get back to the phone screen.
This phone was good value, but I do regret the purchase.
The proximity sensor is very sensitive, even with a very small string. I just test this when I call my second phone. And moving around my finger, and boom! My screen is turned off, but did turned on again after I moving away my finger. This is surprising me when I call my mom, and I force to turn off my device, and it's rebooted. After my device is successfully booted, I tried to call my Dad, and surprisingly the screen is not turned off. So I'll try to find the problem, and I founded them:
The proximity sensor is very sensitive, so be sure to wipe the proximity sensor until it gets clean completely.
That's it, so no matter if you use a different dialer or default dialer for your device, just keep in mind that I mentioned there.
Thank you. As always, sorry for my bad English.?