Hey guys this thing thats been happening to me is absulotely mind boggling and if anyone can resolve this it would be greatly appreciated. it bugs me like theres no tomorrow.
so heres the issue.
i have a samsung galaxy s4 with all the latest updates provided Android Version 4.2.2
when im travelling along in the car or even randomly seated i would receive a call or even make a call and place my phone on loudspeaker now the funny thing here is that the phone after maybe 10-20 seconds will automatically switch back to normal speaker and it annoys me so i have to put it back on loudspeaker mode
ive had the occasional scene where it still showed that loudspeaker was activated but the caller was coming through the normal speaker so it forces me to tap loudspeaker to de-activate it and then tap it again to activate only to realise not long after it automatically switched back to the normal speaker all over again.
NOTE: the phone is laying flat on my lap or standing infront of me.
has anyone had this issue before and is there some sort of fix for it
PLEASE HELPPP !!!
Sent from my GT-I9505 using xda app-developers app
Related
Hey guys i currently upgraded from the nokia n900 to the nexus one. I had this great app on the n900 where it used the proximity sensor to switch the phone call to speaker when its away from your face and then switch back to the regular phone "ear" speaker when its against your face. I tried looking for something like it i downloaded "smart call" and it kinda works but it uses the accelermeter to determine the phones orientation. any help is appreciated THANKS!
This is a surprisingly good idea...
I really want this function also.
I had this in my Touch Pro2 but that used both proximity sensor and accelerometer so when i put the phone on a table with the screen down it started speakerphone. As soon as I picked it up it changed back.
Really good feature if you´re put in hold, waiting for someone to answer.
+1
Brilliant idea.
Ya its great! so basically when the screen turns on when you pull it away from your face so does the speaker lol i think its simple enough for the developers to create right?
nothing?
deng 200 views and no love.
You might want to try asking this in the Tasker thread. I'm not familiar with the program, but it might be able to do what you want.
+1 This is a great idea. I just spent 45 minutes on the phone with Time Warner and was on hold 5-6 times, this would have been handy.
I know for a fact this would suck on my n1. The only noticeable problem i have on my n1 is my prox. sensor sucks, alot of the time it thinks that my head is away from my phone and i end up muting myself and not realizing it and then getting hung up on. Very annoying
_-..zKiLLA..-_ said:
I know for a fact this would suck on my n1. The only noticeable problem i have on my n1 is my prox. sensor sucks, alot of the time it thinks that my head is away from my phone and i end up muting myself and not realizing it and then getting hung up on. Very annoying
Click to expand...
Click to collapse
Mine does the same thing, but like djstoffe had on his Touch Pro2 we should implement the accelerometer so we don't get any 'false alarms'.
After a 12 hours working day I needed to relax a bit...
I just decided to write the app as I like the idea but I'm not sure on the concept how to use it... have to sleep about it.
Anyway you can play with the attached apk and if you would post me a logcat, that would be nice and i can see on which devices/rom's it doesn't behave like on my Nexus with CM6...
Code:
adb logcat|grep SpeakerProximity
Just fire up the app and there is a preference view where you can set it on or off with a combobox.
It's working on my phone but as I'm sleepy I can't test it any further but if you like the app and think it could be usefull, just post your comments and I see that I turn it into a optimized app (this is just a quick afterwork writedown)
Before I forget, I will post the sourcecode after I cleaned up my mess and maybe also write a short tutorial on how I did write this app ;-)
Added a new Version in post #27 => http://forum.xda-developers.com/showpost.php?p=7972710&postcount=27
WORKS GREAT THANKS!!!
Sent from my Nexus One using XDA App
Thanks so much for stepping up and making this, rac2030. I just tested it on my phone and it works great!
Works like a charm!! Thumbs up!!!
Hmmm... scary that it's working without probs... did test it today a bit but expected bugs: because I was tired and just wrote out of my head.
Could you guys feed me some lolcat to see if the values are always right or as I asumed?
Ok came across a problem. Is there a way that the app keeps running but disables when the Bluetooth is connected to a headset? The other day I was using my jawbone and it kept switching from speaker to the jawbone.
Sent from my Nexus One using XDA App
k0shi said:
Ok came across a problem. Is there a way that the app keeps running but disables when the Bluetooth is connected to a headset? The other day I was using my jawbone and it kept switching from speaker to the jawbone.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I will take a look at it, sounds like a good idea...
Note to myself:
- Disabling the speaker switch if headset is connected (bluetootht and wired)
- proximity monitoring should be handled in a proper service that starts with the accept broadcast of the call and ends itself after the end call broadcast
- grabbing it upsodedown (based on G senseor) switch microphone on and off (as a second option in app)
I'm running into a couple problems with the app on my Nexus CM6.
It is functioning properly except for the screen and speaker button. I called myself from Gmail and answered like normal with the phone up to my ear, working so far, then I took the phone away from my head and the screen came on and switched to speaker perfectly, but after that if you put the phone back up to your face the screen doesn't turn off and the speaker button remains green (as if it were still on speaker phone).
Like I said, it switches back and forth from speaker to no speaker flawlessly, so that part is working great. Any one else experiencing this?
Also, it would be amazing if we could utilize the tilt sensor so that if you wanted to set the phone on the table, screen down, it won't switch back to in ear.
dailydR1ver said:
I'm running into a couple problems with the app on my Nexus CM6.
It is functioning properly except for the screen and speaker button. I called myself from Gmail and answered like normal with the phone up to my ear, working so far, then I took the phone away from my head and the screen came on and switched to speaker perfectly, but after that if you put the phone back up to your face the screen doesn't turn off and the speaker button remains green (as if it were still on speaker phone).
Like I said, it switches back and forth from speaker to no speaker flawlessly, so that part is working great. Any one else experiencing this?
Also, it would be amazing if we could utilize the tilt sensor so that if you wanted to set the phone on the table, screen down, it won't switch back to in ear.
Click to expand...
Click to collapse
Have to test this, thx for the info.
Note to myself:
- add tilt Sensor and dont switch back if in speaker and get flipped (make this optional in settings screen)
Hi all,
I bought an infuse last week for a family member and loaded cm7 on it without any issues.
Starting today, when the infuse is placed on a phone call no one can hear me but I can hear them.
I've checked the sim card for scratches and it looks perfectly fine.
After troubleshooting it a few more times, what I noticed is as soon as the screen goes black during a phone call the mic is muted, so I have to consistently light the screen back up for the person on the other end to hear me. This also happens when I use the sensor and place the phone next to my face, it will also mute me. I've made sure that I'm not accidentally hitting the mute button, but it's strange that the mic cuts out as soon as the screen goes black.
Does anyone have any fixes or inputs on this matter?
I have an infuse for myself as well, with the exact settings, modem, and rom and mine is working just fine.
The phone hasn't been dropped or anything.
I've browsed around and people have been suggesting to "uncheck background noise" setting, but I can't seem to find it. I tried pressing the menu button while on a call and there is nothing. Am I doing this wrong or is the setting nonexistent in cm7?
Thanks
chaosdmonik said:
Hi all,
I bought an infuse last week for a family member and loaded cm7 on it without any issues.
Starting today, when the infuse is placed on a phone call no one can hear me but I can hear them.
I've checked the sim card for scratches and it looks perfectly fine.
After troubleshooting it a few more times, what I noticed is as soon as the screen goes black during a phone call the mic is muted, so I have to consistently light the screen back up for the person on the other end to hear me. This also happens when I use the sensor and place the phone next to my face, it will also mute me. I've made sure that I'm not accidentally hitting the mute button, but it's strange that the mic cuts out as soon as the screen goes black.
Does anyone have any fixes or inputs on this matter?
I have an infuse for myself as well, with the exact settings, modem, and rom and mine is working just fine.
The phone hasn't been dropped or anything.
I've browsed around and people have been suggesting to "uncheck background noise" setting, but I can't seem to find it. I tried pressing the menu button while on a call and there is nothing. Am I doing this wrong or is the setting nonexistent in cm7?
Thanks
Click to expand...
Click to collapse
Might i suggest to try another ROM? =/ I dont really know much about cm7, still its not expected to work perfect since theres not a real build for our devices only unnofficial compilations.
Or try all the compilations available for instance i can post this 2 threads that you can find on android development section:
LinuxBozo build:
http://forum.xda-developers.com/showthread.php?t=1195525
uberamd build:
http://forum.xda-developers.com/showthread.php?t=1311960
If both have the same problem i guess using a smsung based rom would be the next step, theres a rom and rom port galore at our forum so you wont be short on options
Nope, the noise cancellation setting is not available in CM7. You would have to go back to a 'stock' based ROM to get that setting.
Thanks for the info guys. Unfortunately, it didn't work. I went ahead and exchanged for another one since I am within my 30 days.
Hi all,
Just wanted to put this out there to see if anyone else had experienced this. Using SGS2 skyrocket - stock 2.3.5 UCKK1 (rooted) and then updated UCLA3 everything (rooted) - When on a phone call after sometimes 1 minute and then other times 5 minutes my microphone stops working and the other person cannot hear me. I can hear them fine, but they cannot hear me.
Wired headphones work without an issue, but the internal mic seems to have an issue with my phone. a work around I read for the non LTE SGS2 works where you hit the speakerphone button and then they can hear you again and if you turn it off it buys you another 5 minutes or so on mic.
So frustrated with this that I am doing an exchange today on the phone.
Just wanted to see if anyone else had experienced and if there was a know n problem with the phone? Google and XDA returned very little.
Thanks!
MB
Hey I too also have this issue, I had a temporary fix which lasts longer than turning on the speaker but it's still temporary, I have the skyrocket on Rogers and I called them in about it, apparently it has something to do with the network, they did some reset and told me to restart my phone and it worked for about a week or so, hope this helps, if anyone has a fix to this please reply
I read another case like this awhile back, try searching it up. i believe it was rma'd though
I have a very similar problem, I go "in and out" a lot. The problem is the noise canceling mic on the top of the phone by the headset input, I left myself voice mail on my home phone and while talking moved my finger gently over the tiny microphone hole and that causes me to go in and out.
For most turning of Noise Suppression in settings will work, for me it does nothing as if it is perma on lol except on ICS where it actually turns off (dont ask me I have no idea why)
I've had 3 Nexus 5's so far due to one RMA and lastly because of a mistake on Google's part. But with all 3 Nexus 5's I have had two bugs that have been driving me nuts. I was curious to see how many people have had the same problems and if anyone knew of a fix. Bugs:
1) Keypad buttons being pressed while on a call. This happens almost every call. It seems that the screen is still active even if the proximity sensor turns off the screen. I haven't been able to reproduce it on purpose, but every single call I take I hear buttons being pressed. Sometimes it's like my notification bar get's pulled down, then the clock is clicked and I feel all these vibrations and ringing sounds and I look down at my phone and I'm in the date/time settings. This happens even if I don't have the dialer keys open. Weird.
2) Say I'm laying in bed and I answer a call. It seems as if there is some sort of setting for the accelerometer that if my head is tilted too much it's as if the microphone stops working... almost like the phone tries to switch to the second microphone (the one not normally used for phone calls). I can't tell you how many times I've been in bed and get a call from my wife (who works night shifts) calling to say goodnight and if I ever put my head back on my pillow she can't hear a word I say. As soon as I lean forward again she can hear me.
These are two problems that I have had with 3 different Nexus 5 phones. I've experienced the same problem with both Franco Kernel and the stock kernel. I don't know what else to do but it's driving me crazy. Anyone else seen these problems or know of a fix?
Thanks in advance.
Try turning your screen off during a phone call and see if there are still key presses being made. Depending how you hold the phone, the proximity sensor might switch the screen on during your call and could register key presses from your ear. The sensor is on the right side of the phone and will "miss" your head if it's behind it.
Unless you're leaving the digitizer enabled (tap2wake etc.) it shouldn't happen.
The mic issue while lying down seems to be common. Your head/pillow blocks the sound and noise cancelation wigs out. You could alter the way you hold the phone while lying down so the secondary mic at the top sticks out more. Personally, I just sit up and haven't had an issue with the noise cancelation since.
Sent from my Nexus 5 using Tapatalk
Hello everyone, i recently upgraded my mom's phone from an htc 610 to my old nexus 5 i had lying around so i took it up to the AT&T store and the rep tried to pull off the backing of the phone thinking it was a cover, got about halfway down, and disconnected / broke the top speaker (the one used just for phone calls). So she can't hear people on the other end of calls anymore and i'm trying to figure out a way to fix this (taking the phone apart being a last resort, but i'll do it if i have to) It's not a software bug (switched around various roms, kernels, audio settings) and the top speaker worked fine before so i'm trying to figure a workaround like routing all the audio for calls to the bottom speaker but i have no idea how i would go about doing that. If anyone has any ideas how i could do this or maybe any other suggestions i would really appreciate it. Thank you for your time! ^^
HourlySword said:
Hello everyone, i recently upgraded my mom's phone from an htc 610 to my old nexus 5 i had lying around so i took it up to the AT&T store and the rep tried to pull off the backing of the phone thinking it was a cover, got about halfway down, and disconnected / broke the top speaker (the one used just for phone calls). So she can't hear people on the other end of calls anymore and i'm trying to figure out a way to fix this (taking the phone apart being a last resort, but i'll do it if i have to) It's not a software bug (switched around various roms, kernels, audio settings) and the top speaker worked fine before so i'm trying to figure a workaround like routing all the audio for calls to the bottom speaker but i have no idea how i would go about doing that. If anyone has any ideas how i could do this or maybe any other suggestions i would really appreciate it. Thank you for your time! ^^
Click to expand...
Click to collapse
Try a Bluetooth headset/earpiece.
Sent from my SCH-I535 using Tapatalk