I got to say, this is pretty odd that it's a problem suddenly showing up like this. Same thing here, on sprint. It's bizarro world!
Posted via Android Central App
Posted via Android Central App
LG Optimus G: Speakerphone automatically on when calling and answering
- Thread starter scubaslim
- Start date
It's not a bug, it's a feature. 
In all the threads about this problem out there over the years and different phone models, it's obvious the "auto speakerphone" is something that can be set through software. I took a look in the Play store and there are a number of apps. I installed "Auto Speakerphone" (https://forums.androidcentral.com/e...s?id=org.malamber.speakerphone&token=MdMtsmEj). The first time I ran the app, the auto speakerphone option was already on. I turned it off and closed the app. Hopefully that does it. I'll report back if successful.
In all the threads about this problem out there over the years and different phone models, it's obvious the "auto speakerphone" is something that can be set through software. I took a look in the Play store and there are a number of apps. I installed "Auto Speakerphone" (https://forums.androidcentral.com/e...s?id=org.malamber.speakerphone&token=MdMtsmEj). The first time I ran the app, the auto speakerphone option was already on. I turned it off and closed the app. Hopefully that does it. I'll report back if successful.
Just to follow up - It doesn't happen with all phone calls now, some numbers and people it does turn it on and other times it does not.
For me it has never happened with all phone calls. I answer a call and it automatically goes to speakerphone, so while I'm on the call I turn off speakerphone with the bottom left option on the screen, and for a while I receive calls without the problem. I wonder if either bluetooth, which I keep on for my car, or my ringtone, AT&T Catch Me, could have anything to do with this. I've changed both to see.
I have a Sprint HTC Evo 4G LTE with this problem. I spent an hour on the phone with Sprint tech support this morning; they couldn't figure it out and suggested I take phone to service center. After phone call I dug some more and discovered that this isn't unique to Sprint, nor to HTC, nor to KitKat since I only have 4.1.1 on my phone. Checked when latest Chrome browser was released -- Feb 28 -- which was about the time the speaker started automatically turning on when I called someone. So... I uninstalled updates to Chrome, disabled it (ver 33.0.1750.136) and installed Chrome BETA (ver 34.0.1847.62) and the problem is fixed, for now at least.
Same problem here. Tried uninstalling chrome, didn't work. Restarting, resetting phone not works. I have changed my charger brick and charging cable recently, problem started to show up after that. I'm back using my old trusty goodie cable and brick but the problem is still there. It doesn't happen all the time, it only happens 3 of the 10 calls but it's annoying in any way. Downloaded "Auto Speakerphone" from Play Store, see if it works. I'm subscribing this topic, in case of source of the problem would be found.
I've had this problem for a while. Seems to relate to certain numbers you call. I find the Chrome theory a little hard to correlate. I've had HTC phones in the past do this crap too. I'm also on an LG Optimus G now. If anyone can find where this is set or if a bug...seems random...please post.
Thanks.
Posted via Android Central App
Thanks.
Posted via Android Central App
Although various hardware problems with the speakerphone appear from time to time in smartphones, the current problem is related to Google Chrome.
You can simply confirm this bug:
1. Kill Chrome (in settings / apps).
2. Open Chrome.
3. Press Home button.
4. Call somewhere. Is speakerphone on?
5. Call once more. Is speakerphone off?
6. Go to 1. and try again.
You can simply confirm this bug:
1. Kill Chrome (in settings / apps).
2. Open Chrome.
3. Press Home button.
4. Call somewhere. Is speakerphone on?
5. Call once more. Is speakerphone off?
6. Go to 1. and try again.
Last edited:
Update.
Same problem occurs when using latest Opera with Chromium 33. More info here https://code.google.com/p/chromium/issues/detail?id=351310 and here https://code.google.com/p/chromium/issues/detail?id=352111
Same problem occurs when using latest Opera with Chromium 33. More info here https://code.google.com/p/chromium/issues/detail?id=351310 and here https://code.google.com/p/chromium/issues/detail?id=352111
Followed the steps, i guess you're right but what about the solution? Is there anything else that could cause this problem? In theory, it should be solved by simply uninstalling Chrome, but it does not.
I have also been having this issue starting in March 2014. very lame. I love Chrome and don't want to reset it. Maybe if we get enough attention, LG will realize the issue and fix it.
This is not LG bug. Temporary You can install Chrome beta. It works fine.
@Hedehe. You must disable Chrome after uninstalling or turn off auto update.
@Hedehe. You must disable Chrome after uninstalling or turn off auto update.
@shider
Hmm. It worked, but it's really weird, I can't really connect Chrome with phone app. Thanks for the suggestion. Have a nice day sir.
Hmm. It worked, but it's really weird, I can't really connect Chrome with phone app. Thanks for the suggestion. Have a nice day sir.
Good news for everyone. Google has released new version of Chrome today - 33.0.1750.166. Problem seems to be finally solved.
Did you pick up the update for Chrome which seems to have completely fixed the issue?
the update fixed the issue, but now chrome has updated again and the problem is back.... wtf chrome?!?
Similar threads
- Question
Trending Posts
-
Pixel 8 Pro - No notifications for Messages on Android Auto
- Started by ArtieTheOneManParty
- Replies: 0
-
-
-
-
Facebook
Twitter
Instagram