Recent content by shider

@spewak what version of chrome do You have? Bug is fixed in chrome 33.0.1750.166

Good news for everyone. Google has released new version of Chrome today - 33.0.1750.166. Problem seems to be finally solved.

Good news for everyone. Google has released new version of Chrome today - 33.0.1750.166. Problem seems to be finally solved.

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.

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

This bug is certainly specific to current version of chrome (beta works fine). But it is also system related. This is because it occurs in only a few manufacturers of smartphones. I have done little research and problems occur in HTC, Sony and LG. Samsung users do not report it. Small update...

@smartmove. Did you disable Chrome? If not, it is possible that You got latest Chrome again because of automatic updates.

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...

There is a new version of Google Chrome - 33.0.1750.136. Unfortunately, the problem still occurs.

Just uninstall Google Chrome updates in Google Play and turn off auto update. I have same issue on HTC One X.

Reset will not help you. Uninstall the latest update of Chrome and disable auto updating. Chrome contains a bug that turns on the speakerphone.

Hello. This problem is not related to KitKat update but latest Chrome update (33). I have the same issue on HTC One X. It appears after Chrome start. Killing and starting Chrome results in turning on loudspeaker on first call. Problem can be solved by uninstalling Chrome updates (and disabling...