Anyone have a problem with Samsung Focus, when receiving a call or dialing for someone, i can´t hear what people are saying, the sound is muted for a while.
Any fix for that?
This bug is very annoying
Thanks
I've always thought this was a network issue. I have a Focus on Rogers but my previous phone, a Sony Ericson dumbphone also had the same issue on Rogers.
No problems with my AT&T Focus. Maybe its a problem with Rogers?
I have the same problem. I thought it was because my phone was unlocked.
Any fix for this?>
This is not Rogers issue. I live in Brazil and have the same problem here. This is a phone issue or WP7 issue
lommez said:
This is not Rogers issue. I live in Brazil and have the same problem here. This is a phone issue or WP7 issue
Click to expand...
Click to collapse
I live in Buenos Aires and I have the exact same problem. My wife has the same phone (same company) without issues. I sent my to Samsung but they could not repro the issue so the bastards sent it back to me. The first call I did, it muted. Damn, they did not fix it and I'm pretty sure they did not test it correctly.
On the other hand, the only temporary fix that I found it works (but it sux) is to MUTE and UNMUTE the phone call when that happens. As simple as that, but it sux.
Damn Samsung Focus. It's incredible the amount of problems that this phone has.
Related
A few times now i've noticed that if i'm in the middle of trying to send a text or email and a phone call comes in (and I answer)..the person on the other end can barely hear me and any sound comes out all "robotic". I've been wondering if this is an issue or if it's just a "bug" on my phone. Anyone else noticed this?
Rickroller said:
A few times now i've noticed that if i'm in the middle of trying to send a text or email and a phone call comes in (and I answer)..the person on the other end can barely hear me and any sound comes out all "robotic". I've been wondering if this is an issue or if it's just a "bug" on my phone. Anyone else noticed this?
Click to expand...
Click to collapse
haveing the same problem on a bell dz they replaced the phone and sim and still same prob they say its a network problem....
666
After 30 minutes of going through posts in this forum trying to look for a solution, and apparently I couldn't find what I was looking for, I've decided to create this post.
Something really weird started happening to my arc recently. Whenever there's an incoming call (call waiting) while I'm talking on the phone, everything gets muted immediately. I cannot hear the other party, and vice versa. Even though I answer the call waiting call, we couldn't hear each other at all. I had to reject the call waiting call in order to be "connected" with the current call again. At first I thought it was some carrier, reception issues, but it's not. The bars were full and I've tried restarting the phone, but it didn't help. I was wondering if anyone has the same issue after upgrading to 2.3.3 and how did you fix this? I didn't notice anything like this before I upgraded. Any help is appreciated!
jerrytea said:
After 30 minutes of going through posts in this forum trying to look for a solution, and apparently I couldn't find what I was looking for, I've decided to create this post.
Something really weird started happening to my arc recently. Whenever there's an incoming call (call waiting) while I'm talking on the phone, everything gets muted immediately. I cannot hear the other party, and vice versa. Even though I answer the call waiting call, we couldn't hear each other at all. I had to reject the call waiting call in order to be "connected" with the current call again. At first I thought it was some carrier, reception issues, but it's not. The bars were full and I've tried restarting the phone, but it didn't help. I was wondering if anyone has the same issue after upgrading to 2.3.3 and how did you fix this? I didn't notice anything like this before I upgraded. Any help is appreciated!
Click to expand...
Click to collapse
I have the same problem. really annoying!
AmitPeri said:
I have the same problem. really annoying!
Click to expand...
Click to collapse
are we the only 2 that has this problem?!
Don't know if it helps but I just wanted to let you guys know I don't have the problem
( open bootloader, flashed prerooted global generic )
jerrytea said:
are we the only 2 that has this problem?!
Click to expand...
Click to collapse
Do you have the Viber app installed? I saw somewhere that some phones react like this because of Viber.
Sorry I don't seem to have noticed that either and I recieved a call waiting bleep while I was on a call just yesterday
I can confirm its the Viber app, I just uninstalled it and the problem is gone!
AmitPeri said:
I can confirm its the Viber app, I just uninstalled it and the problem is gone!
Click to expand...
Click to collapse
Yes, I can confirm this as well, but the problem is fixed on the latest version of Viber. Happy with regular call and Viber now. Thanks to everyone who tried to help
I just got a Galaxy W 2 days back, and I absolutely love it, but there is this one issue I am constantly facing.
Whenever I use my headphones, after removing them, the Music ( or whatever audio an app has ) gets routed through the top speaker
(Image Attached) . Although I found a workaround, i.e calling someone on handsfree mode does the trick, Can't find any permanent fix.
Would be glad if someone here could help me out with it. I can't figure out if its a hardware problem or a software bug.
Nope didn't happend to me.
try go to 2.3.6 via kies or auto apdate from the phones settings, maybe it will fix it.
It is already 2.3.6 I updated it as soon as I got it. Will go to service centre today.
But do you have the latest 2.3.6 version?
Does it always do this? You probably have installed an app that might have been messing with your phone's audio. This has never happened to me before.
I bought the phone hardly 4 days back, Yes, happened from the moment I bought it, with no apps installed. Tried ToggleHeadset, but that did not work either.
What is your version and the built date?
*#1234#
sound strange , it didnt happen to me.. maybe u should approach samsung customer service..
Assuming that you tried a different headset and it still doesn't work, I suggest returning the phone as well.
That would be a good idea!
Hey guys,
Just got it back from the Samsung Centre, they say it was a software issue. ( Though its still LA2) Anyways, its solved now.
And what they did with your phone? Factory defaults or what?
I've been having this same problem. I'm glad to hear it's a software problem. I toyed with the idea of sending my phone off to Samsung but I'm glad I didn't now. Especially as I'm planning on rooting soon once I've done a bit more reading up (it's my first android, feels strange to be a beginner with something again, takes a while to learn all the little tricks).
Anyway I posted the following to Android Forums a couple of weeks ago, with no reply (I can see this forum is much more active).
"A problem I've been having recently (not exactly sure when it first happened) is that I'll go to watch a video and instead of the sound coming out of the loudspeaker, it comes out of the handset/phone speaker (not sure what you call it, the one above the screen for putting your ear to). Needless to say it's way too quiet to hear anything properly. It's happened randomly now about 6 or 7 times. I've had to restart the phone every time to remedy the problem. It's getting kinda annoying.
Also I think my headphone volume may be playing up. Not sure if it's related, but there's been times where at full volume music has been pretty underwhelming (I know about the dreaded EU volume cap (which I hope to remedy with a forthcoming root once I've read more up on the subject), no - it seemed even quieter). I'm almost sure there's something wrong because all of a sudden earlier today while listening to some sounds the volume jumped up to what seemed more akin to a maximum volume.
Could these two problems be related? And if so could anyone suggest what I could do to sort this out? Perhaps a factory reset (which I understand I'll have to do if I want to root anyway)? I really don't want to have to send it off for repair. I dunno if I could part with my new favourite toy lol."
Anyway OP you're not alone. Glad to hear you got it sorted. Mine's an XXKK1 btw, although I don't really know what that means.
Sent from my GT-I8150 using Tapatalk
They updated firmware (try updating it) and then set it to factory default.
RSX....Hi
Are you 2.3.6 or 2.3.5??
The XXKK1......means in Sammy code
XX Region
Austria, Belgium, France,
Germany, Hungary, Italy, Spain,
United Kingdom
KK1 simply shows Year/Month/Revision....
1st K is 2011.....starts with A [2001]
2nd K is Nov. [Jan-Dec.....A-L]
So, your FW is Nov 2011, Ver 1
You prob due update......
Check with Kies or Check Fus App from Market
https://market.android.com/details?id=com.johnan.checkfus
Sent from my GT-I8150 on Lanzarote Canary Vacation using Tapatalk
Since moving to Jellybean (when it first got released) and attempting to use Google Now, I noticed that the it wasn't doing or understanding what I was saying. It appeared that there was a lot of static noise before it would recognise what I was trying to say.
I loaded some recording software to make sure it wasn't just Google Now, but it turns out that it just hisses for that first 5 seconds before it comes good. It does not happen in phone calls, just when recording/talking to Google Now. Changing ROMs, kernels and radios has not changed the problem. Even moving up to the new 4.1.1 hasn't rectified the problem.
Has anyone else had this problem? Has it ever been fixed?
Any help would be fantastic!
Bumping.
Still can't seem to find an answer anywhere for this.
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
galapogos01 said:
This is a real problem. It makes the new Voice Search unusable.
There's a bug on it but it hasn't had any real attention - http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=29092
Edit: interesting that yours is a Telstra phone too. Wonder if its build/baseband related?
Click to expand...
Click to collapse
I've tried different basebands, ROMs etc. Still suffers from the 2 seconds of hissing/not working microphone before it comes good and is usable.
Interesting. I too am on Telstra, tried few 4.1 and 4.1.1, CM10 and the same issue. Not to mention, even after the hiss is over, the volume is very low and rubbish in general.
Interesting that it affects a lot of Telstra phone owners.
Anyone reverted to the stock Telstra rom/baseband to test? Does it affect voice search in 4.0.x as well?
Same problem!
I have this exact problem!! I've had difficulty finding any others with this problem until I found this thread.
Grr, mine shows static for about 4 seconds and it struggles to understand anything at all! After those 4 seconds, it dies down, then I can speak and it is better but far from perfect with recognising my speech!
FYI mine is a yakjudv Telstra phone from Australia which I flashed to yakju 4.0.4 and then did a JB update OTA......
It was on the stock DVKK6 but am now on the XXLF1 radio that came with JB....
Argh, whats going on, i was so pumped for google now voice actions!!! Now its basically useless!!
Mines almost spot on 4 seconds every single time.....
Any solution to this would be greatly appreciated!
+1 again on my gnex
factory installed yakjudv i think, from vodafone.
I have had it since ICS, tried to record lectures in class, and the first few seconds is always static.
Now that you mention it, when I activate voice search in google now, i see the grey circle voice indicator spazzes out for a few seconds before it goes back to normal. Maybe that's why I have to speak loud for it to recognise my voice to make it distinct from the initial static, so it usually doesn't work that well.
Kinda weird that it appears to be Telstra gnex's. Still no luck in finding fixes yet.
Sent from my Galaxy Nexus
Any workaround or fix for this?
It seems like Santaria has already tried a variety of different radios with no luck.
Is this a case of sit and hope that Google fixes this?
So what exactly is the problem? There's 2 mics in the phone, but its picking up the wrong one?
Since when were there 2 mics? one for phone call and one for speakerphone? I didn't even know this. How could this happen and why is it only on Aussie phones? The hardware should be the same across the board?
I'm so confused
One is for noise reduction.
Cheers,
Jason
I wonder if there's a way to enable/disable the noise reduction mic?
Sent from my Galaxy Nexus
galapogos01 said:
One is for noise reduction.
Cheers,
Jason
Click to expand...
Click to collapse
One is for calls the other one is for recording videos and video calls...The Galaxy Nexus do not have a noise reduction software on board neither the required hardware so no noise canceling feature!
Sent from my Nexus 7
Err...
http://www.slashgear.com/galaxy-nexus-review-21196912/
http://en.wikipedia.org/wiki/Galaxy_Nexus
There seems to be some debate about its effectiveness - probably related to the above bug disabling it in some cases.
For the record, same problem on my telstra Gnex, google now only works if I hold the mic right to my mouth.
I'm having the exact same issue. I just bought a new gn that was locked to Vodafone Australia. I unlocked it and went to yakju then got the OTA and then started having the exact same problem that everyone else has described. I get massive static and so far nothing I've said has been recognised. It just times out with the message "recognising...".
I've recorded my voice using an app but everything sounded fine and I didn't get any static. I have the same problem if I use a hands free kit too.
Seems this happened with ICS also
http://forum.xda-developers.com/showthread.php?t=1602840
Star this issue
Hey guys, a few of us seem to be having this problem, please star this issue so that Google will be aware of it.
http://code.google.com/p/android/issues/detail?id=29092
SIMPLY CLICK HERE AND STAR THE ISSUE.
Starred
Starred a long time ago...
No luck, even with 4.2.2
I take it they're never going to fix this problem
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
try the replacement handset. I've had my G3 since it came out with no problems whatsoever.
steve.whisenhant said:
My T-mobile LG G3 has been working like a champ for many months. Now, call quality for person to whom I am speaking is very poor. It sounds like there is very faint speaking that drops in and out. This happens both on bluetooth and off, but is worse on bluetooth. There is no physical block to built-in or headset microphone. I know this because can record voice memo and do 'OK Google' dictation with ease. VOIP calls (Google hangout) are ok given my WiFi bandwidth.
T-mobile tier2 support tried to sell me on notion that lollipop might fix me (based on www_androidauthority_dot_com/lg-g3-problems-517832 ) but I'm skeptical and jumped at the offer of a handset replacement. Any other ideas out there?
Click to expand...
Click to collapse
Wow, my G3 just started doing this too. I've had it for 6 months and it's just been the past week that I've been having issues. It's hit or miss, but about 90% of the time I get complaints that the other person can't hear me or that I sound very faint. It's been driving me crazy. I've figured out that I can toggle speaker mode and it fixes it. Can you try that out see if it's the same for you?
I noticed this about a week ago, interesting. Wonder if it's something on tmobile's network.
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
---------- Post added at 09:48 AM ---------- Previous post was at 09:04 AM ----------
madmanjsm said:
This just happened to me as well on Tuesday, March 10th. I live in Los Angeles. A reboot seems to fix it for one call. This is kind of a big problem.
Click to expand...
Click to collapse
I'm now running in safe mode and a couple test calls to my Google Hangout sound fine. Don't think it's a hardware issue.
I've started to experience this too. It's really annoying. I hope it gets fixed soon. Though, I am glad to know it's not just me. I really didn't want to dig around in my apps to find the offender.
Question: Do any of you guys have the Nova Launcher Beta running? I think I started having issues around then.
Sent from my LG-D851 using Tapatalk
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
bryanwny said:
I'm on Verizon with a G3, but try reading my post @ http://forum.xda-developers.com/showpost.php?p=59423187&postcount=25 and maybe it'll help some of you
Click to expand...
Click to collapse
Thanks! I downgraded and installed Google App 4.1.29 here http://www.apkmirror.com/apk/google-inc/google-search/google-app-4-1-29-1706998-arm-android-apk-download/. Also disabled auto-update for Google Apps so it doesn't update to 4.2.16.87075793. I'll test it out and see what happens.
I also have had the same problem lately, just twice. A reboot fixed it
This is affecting me as well. I'm also in Los Angeles and the phone was fine until some time last week. I'm trying to the google apps downgrade now...
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Lookatthemonkeys said:
I also am having the same issue in my D851. My phone worked fine for 2 weeks and now 75% of the time the caller on the other end says they cant hear me and I sound like I am a mile away. This does not happen when I used VOIP such as hangouts. I am thinking about flashing a AOSP ROM until the t-mobile 5.0 build comes out.
Click to expand...
Click to collapse
Try downgrading the Google app. Worked fine for me.
Downgraded, seems better. Are people also recommending not to use voice activated Google now?
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
tippingvan said:
How do I downgrade the google app? I tried turning off the "OK Google" way, but still have the same problem.
Click to expand...
Click to collapse
In the play store for the Google search app click the uninstall button. That will return the app to it's factory version. Then just install the version that's linked earlier in this thread. Make sure you have automatic updates turned off for the app or it will keep updating.
Sent from my LG-D851 using Tapatalk
Same thing happens to me. I had my phone for about 2 months now and sometimes people cant hear me or i sound like a transformer. i restart my phone and it fixes the problem but still does it after a couple days. I'm not rooted or anything like that. I also have a problem when I'm on a call. my volume bare goes up and down if i wanna lower and or raise it and the volume sounds the same even on speaker phone it does it too..
I had the problem turn off ok google from any screen and reboot and problem with voice calls fixed
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
JohnnyDanger said:
I had this same problem. Maybe I should have came here first. I got a replacement in the mail a couple of days ago. New one seems to be working fine. Hopefully the problem doesnt start happening again.
Click to expand...
Click to collapse
I was gonna do a factory reset and if that didn't work i was gonna get a replacement . Hopefully this fixed the problem. The only issue I seem to be having is. when I'm on speaker phone or have it to my ear. and when i go to adjust the volume it doesn't change it. like i see the meter go up and down but the volume stays the same. its weird
I can confirm that after enabling voice activation for google now from any screen was the culprit of Mt audio issues. I was told I sounded far away or like a robot far away. Reset my device numerous times and reinstalled all apps and made calls. Once I enabled OK google from google now the issue came back. Disabled it and BOOM it worked fine. Haven't had an issue since.