Database Info

Possible Bluetooth Fix G2x - Works so far

Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot

fix the a2dp on gb and i'll give you your first donation.

What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!

donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.

crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..

Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.

The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.

jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.

So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium

ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?

crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.

I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).

mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium

All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.

SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?

No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?

[Q] SMS doubled and tripled - Help

My gf recently bought a Charge an has been getting doubles and sometimes tripled incoming messages. I thought it may just be an issue with the stock app so I installed Handcent and began playing with its settings to try and prevent the issue. So far there has been no luck on my end so I opened a ticket with Verizon which has also been unsuccessful. Thinking maybe it was a phone issue we swapped it for another charge , but have the same issue. Through my searching I've seen that there are alot of folks with this issue on both the Charge and the Thunderbolt, and folks have had varying degrees of success with multiple methods. I've tried every method I've seen so far with no luck. The issue appears to be intermittent since it does not happen with every message, however it does happen very frequently. If anyone has any suggestion I'd be very appreciative. I really don't want to have to spend $100 more to get the Bionic to remove this issue, since I do want to stay with a dual-core LTE device on VZW. Thanks.

skribbles505 said:
My gf recently bought a Charge an has been getting doubles and sometimes tripled incoming messages. I thought it may just be an issue with the stock app so I installed Handcent and began playing with its settings to try and prevent the issue. So far there has been no luck on my end so I opened a ticket with Verizon which has also been unsuccessful. Thinking maybe it was a phone issue we swapped it for another charge , but have the same issue. Through my searching I've seen that there are alot of folks with this issue on both the Charge and the Thunderbolt, and folks have had varying degrees of success with multiple methods. I've tried every method I've seen so far with no luck. The issue appears to be intermittent since it does not happen with every message, however it does happen very frequently. If anyone has any suggestion I'd be very appreciative. I really don't want to have to spend $100 more to get the Bionic to remove this issue, since I do want to stay with a dual-core LTE device on VZW. Thanks.
Click to expand...
Click to collapse
Sounds like a network issue. Does it happen with different senders?
Sent from my SCH-I510 using Tapatalk

Yes, so far it is happening with all senders at different times. I was thinking it was nnetworrelated myself. Now that you mention it though I wonder if it has to ddo with LTE not being up yet here. Its scheduled to launch in Nov. Which is why I want to stick with an LTE device. I'll try turning off the LTE and see if that helps.

Please use the Q&A Forum for questions Thanks
Moving to Q&A

[Q] Data just stops but stays connected.

This has been driving me crazy lately. It's most noticeable if I'm watching any kind of video or tethering with PDAnet. I'll be browsing or watching videos then suddenly the data just stops, but it still shows me connected to 4G with 4 bars of signal. The only way I can get the data back is cycling airplane mode.
Has this happened to anyone else and is there any way I can fix it? I'm running Humble 1.62 with EP1W radios and using PDAnet 3.0 to tether.

Bandin03 said:
This has been driving me crazy lately. It's most noticeable if I'm watching any kind of video or tethering with PDAnet. I'll be browsing or watching videos then suddenly the data just stops, but it still shows me connected to 4G with 4 bars of signal. The only way I can get the data back is cycling airplane mode.
Has this happened to anyone else and is there any way I can fix it? I'm running Humble 1.62 with EP1W radios and using PDAnet 3.0 to tether.
Click to expand...
Click to collapse
Yes and No!
Sent from my SCH-I510 using XDA App

i'm running gummy 2.1. 1.9RC up until yesterday. I've noticed for the past month that this has been happening. Talked to Verizon, they ask me to confirm that settings were well, set. reboot and watched it happen again. they confirmed that its an existing problem and they acknowledge it with all samsung products. they said they can do nothing about it as long as their is a known fix (reboot system or shut down data and start it up). They did say a new update is coming out very shortly which specifically fixes this from samsung.

orateam said:
i'm running gummy 2.1. 1.9RC up until yesterday. I've noticed for the past month that this has been happening. Talked to Verizon, they ask me to confirm that settings were well, set. reboot and watched it happen again. they confirmed that its an existing problem and they acknowledge it with all samsung products. they said they can do nothing about it as long as their is a known fix (reboot system or shut down data and start it up). They did say a new update is coming out very shortly which specifically fixes this from samsung.
Click to expand...
Click to collapse
Ill try to let you down easily. Thats a bunch of BULLISH! I called verizon and got the same line. Also those aren't known fixes. They are called work arounds.
I called samsung mobile US and was told they arnt aware of any issues with the samsung charge. They also took down my device/contact info and said they would be in touch! The only software update we MIGHT see soon is GB. As we all know, the issues are still present in the leaked GB build.
As a former fascinate owner I went thru this merry go round before. Verizon blames Samsung, Samsung says there is no issue. Verizon finally admits it and offers an upgrade. Thats the pattern that will play out here.
Just so everyone knows VZW is still replacing Fascinate s with Droid charges. The issues still exist!
Sent from my SCH-I510 using XDA App

Please use the Q&A Forum for questions Thanks
Moving to Q&A

Yep, this happens to me all the time. Interestingly, my data dropouts are always this way (4G icon still showing), not the usual way where people drop down to 3G/1X or fail to show the 4G icon.

Only happens when I'm streaming Pandora.
Sent from my Droid Charge running Infinity Beta

If you guys are tethering this WILL happen. It happens to me if I download a huge file or stream HD videos. I have to restart the phone and then it works again.

There are multiple data connectivity issues with the Droid Charge. I have spoken to many different techs at Verizon, some of them claim it is a known issue and that they are aware and a software update is "coming soon" I have had techs tell me it was announced on 10/19, i have also had techs tell me early november. However I had more techs, including several at Samsung, tell there is no known issue, and no upcoming software fix. Please see this other thread at XDA, and all the issues that people are having. http://forum.xda-developers.com/showthread.php?t=1309271

[Q] No sound when making calls or receiving calls

Dear All.
My samsung galaxy s2 skyrocket had been working with ParanoidAndorid (v 2.55) for 2 months without problems, but since a week ago I couldn't place regular calls. I can dial the numbers and receive calls, but in neither case I can hear any sound. The rest of the functions work just fine (youtube, chrome, etc). After checking for sound configurations, such as noise reduction, the problem persisted. I have to say that the problem goes away after rebooting the system, but is happens again at random times. I've change to Cyanogenmod 10, but the situation holds.
I noted that two apps seems to be producing this problem: Viber and Line. Immediately after I receive a Viber/Line call the problem arises. This is strange as I've been using Viber from the beginning, but the problem has been happening only from last week.
I would appreciate any suggestions. Thanks in advance

Contact the app DEV and provide him some logs. It's not the phone from what you're describing.

hechoen said:
Contact the app DEV and provide him some logs. It's not the phone from what you're describing.
Click to expand...
Click to collapse
I'll try using the phone without Viber/Line for a couples of days just to be sure that is a app-driven problem. Given the popularity of these apps, I would be surprised if this is only happening to me.

Did the app update recently? I'd unistall it then clear caches and reboot. If the problem goes away it's the app.

Hi @MarceloR -
I am a rep. of Viber here on XDA.
Thanks for sharing the details of the problem.
First, please note that Viber does not officially support your device, s2 skyrocket (here is the full list of fully compatible devices: http://bit.ly/Hm5k9p). Furthermore, we (Viber) don't claim to fully support devices with Custom ROMs, since it is impossible for us to adapt our app with all of the Custom ROMs out there.
Both these issues may be the sorurce of the problem you're experiencing. Have you tested this issue on Stock ROM on your device? (though it's not fully supported).
Having said that, the problem still sounds odd - Viber should not affect your ability to use your phone for regular calls.

Same problem, different software
I'm having the same issue - no mic, no sound on phone calls. I do not have either of the above-mentioned apps installed. I'm running CM10.1, though (Rogers). Tried installing the CLI3 modem, and the stock Rogers modems to see if that might help.
I did notice that the ear speaker was getting quite hot when I tried to use the phone, and the phone app itself is performing tremendously slow.
If anyone has thoughts / suggestions about how to fix this, I'd really appreciate it.

It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.

Update: pulled SIM card, battery. Reboot, shut down, insert SIM card. Everything works again. Using the same 3/3 nightly. No other changes.

lingowistico said:
It's a common issue and has nothing to do with Viber, i've never used it personally.
This has happened to me on all kinds of roms stock, custom and AOSP.
Usually, when it happens, it happens after or while i am running an app that uses audio. Like any video / audio player and games.
It's not that big of a bother since it doesn't happen too often, but just embarassing.. when you've payed some $300+ for a phone and it doesn't even make phone calls lol. Might as well have bought one for $20 that does.
My point is i want to know a reason or explanation for this if someone can offer one.
Click to expand...
Click to collapse
Common for whom I don't have these issues. I swear how do you guys have all of these crazy problems.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
http://forum.xda-developers.com/showthread.php?p=39678817

@lingowistico -
Thank you for sharing this valuable information, that will help us aide our users as well.
If you have any news in this matter, please do let us know

lingowistico said:
Common for some..
http://forum.xda-developers.com/showthread.php?t=2168656
Click to expand...
Click to collapse
I circumvented this problem by installing an old version of viber (one from Dec 2012). I found the old version here: http://www.androiddrawer.com/
So far, no problems. Everything seems to be back to normal.

Pixel 3 Speakerphone issues?

I got my Pixel 3 unlocked from Google a couple of days ago. I really love the phone, but oddly, every time that I call my wife and I'm on speaker, it always takes 8-10 seconds for her to be able to hear me. This happens with no one else, as I've called multiple people on speaker. Google offered to RMA the device, but I'm not convinced that it's a hardware issue. If it's a software issue that will likely be fixed in the future, I will just keep this one. I'm not entirely sure what to make of it, but I don't really want to go through the RMA process just for it to continue happening. Has anyone else had similar experiences? From what I can see on Reddit and elsewhere, it appears to be a rather commonplace issue. I just can't justify waiting for another device to solve a wide spread problem. If it was a fluke issue, then a factory replacement wouldn't make me nervous. I think that I am just going to return the device for a full refund and wait for something else to come out. Sucks though, because I otherwise loved this phone.

I have noticed this as well. I try to talk over the speaker and the person on the other end can't hear me for a little bit. I might try to RMA the phone. How'd you go about talked to Google Support about the issue? A phone call, chat or email?

norman1080 said:
I have noticed this as well. I try to talk over the speaker and the person on the other end can't hear me for a little bit. I might try to RMA the phone. How'd you go about talked to Google Support about the issue? A phone call, chat or email?
Click to expand...
Click to collapse
I was using the chat service, it worked fine. I haven't RMA'd the device. I went and got a new SIM card from AT&T and it seems better. I did tons of test calls to other people on different carriers and it only ever happened with my wife, who is in Verizon. For that reason, I don't think there is a hardware issue with my device, but I don't know what it might be.

norman1080 said:
I have noticed this as well. I try to talk over the speaker and the person on the other end can't hear me for a little bit. I might try to RMA the phone. How'd you go about talked to Google Support about the issue? A phone call, chat or email?
Click to expand...
Click to collapse
I figured it out while I was messing with it yesterday. Turn off HD voice. "enhanced LTE" in the network settings menu and that fixes it. I am on AT&T and had great connectivity with same carrier subscribers, Sprint, and others. I tried calling multiple friends with Verizon and had the issue every time. So I just turned it off.

Update: it looks like December update fix my issue. Will update again if something happen
---------------------------------------------------------------------------
This speakerphone issue is happening to me using TMobile and also using Whatsapp calls.
I noticed this issue because the phone is also not connecting to my Honda Civic 2016 Bluetooth and tried using the speakers.
I'll wait for December 2018 update and make lot of test before I contact Google.
I'm using the regular Pixel 3 white.

I have the same issue,,,when I first get a call and answer it with speakerphone no one can hear me for a few seconds then if I toggle speaker off then back on it works okay??

stl-fan said:
I figured it out while I was messing with it yesterday. Turn off HD voice. "enhanced LTE" in the network settings menu and that fixes it. I am on AT&T and had great connectivity with same carrier subscribers, Sprint, and others. I tried calling multiple friends with Verizon and had the issue every time. So I just turned it off.
Click to expand...
Click to collapse
Doesn't this remove the ability to use group chats?
I got my wife the Pixel 3 at launch and we're on the 3rd phone because of this issue and it's still happening. It only happens on speakerphone (not regular) and her speakers seem to be fine which makes me think it's software and not hardware.

deblas66 said:
Doesn't this remove the ability to use group chats?
I got my wife the Pixel 3 at launch and we're on the 3rd phone because of this issue and it's still happening. It only happens on speakerphone (not regular) and her speakers seem to be fine which makes me think it's software and not hardware.
Click to expand...
Click to collapse
I agree with you. I think I'm still having issues with it even without it on. My wife is still saying it sounds like I'm in a tunnel any time I'm on speaker. I hope they get this resolved, and ASAP.

stl-fan said:
I agree with you. I think I'm still having issues with it even without it on. My wife is still saying it sounds like I'm in a tunnel any time I'm on speaker. I hope they get this resolved, and ASAP.
Click to expand...
Click to collapse
Me too. I did some serious searching and it is a more major problem than I thought.
https://productforums.google.com/forum/#!topic/phone-by-google/YCbNdF9b1ts;context-place=forum/phone-by-google

I am wondering if anyone has tried turning off the wifi calling option? I havent tried that yet as it is the only thing I havent tried to see if my phone doesnt have problems when first answering a call with the phones speakerphone and people on the other end not being able to hear me for the first few seconds? I saw in a Google thread that there may be a problem with the handoff of wifi to actual LTE calling and it makes it difficult for the phones speaker to know where to apply the sound to? I dont have a sim in my phone currently so I am wondering anyone else tried this to see?

Archangel said:
I am wondering if anyone has tried turning off the wifi calling option? I havent tried that yet as it is the only thing I havent tried to see if my phone doesnt have problems when first answering a call with the phones speakerphone and people on the other end not being able to hear me for the first few seconds? I saw in a Google thread that there may be a problem with the handoff of wifi to actual LTE calling and it makes it difficult for the phones speaker to know where to apply the sound to? I dont have a sim in my phone currently so I am wondering anyone else tried this to see?
Click to expand...
Click to collapse
I've had WiFi Calling and VoLTE disabled for a while now - still garbage call quality on speakerphone.

Same here

I have WiFi calling off of mine.. still same issue

i have a new google pixel 3 after an ota update my speacker is not working anymore i tried to reboot the phone and even flashing it but nothing worke with me. can any one help please ?

hi,
i have same issue .. did you find how to solved this problem?

jon2jay said:
I may have found a fix for this. Need you guys to confirm.
Goto the permissions of Google play services, and disable MIC permission. During phone calls you will see a 'this app needs permissions to run blah blah' ignore it. Test speaker phone now. I stumbled upon someone who mentioned this (can't find the post now) and I have had 0 issues w/ straight speaker phone.
Click to expand...
Click to collapse
I can't even make calls with mic permission disabled

jon2jay said:
I may have found a fix for this. Need you guys to confirm.
Goto the permissions of Google play services, and disable MIC permission. During phone calls you will see a 'this app needs permissions to run blah blah' ignore it. Test speaker phone now. I stumbled upon someone who mentioned this (can't find the post now) and I have had 0 issues w/ straight speaker phone.
Click to expand...
Click to collapse
My wife has this issue with her new Pixel 3 - oddly not when calling me (I have an S8) but when calling 3 other confirmed people (who [co-incidentally] all have iphones?). Even talking to them over handset first which is obviously fine, when she switches to speaker mid-call they can't hear her.
We tried this but she still has the issue.

bwgooch said:
My wife has this issue with her new Pixel 3 - oddly not when calling me (I have an S8) but when calling 3 other confirmed people (who [co-incidentally] all have iphones?). Even talking to them over handset first which is obviously fine, when she switches to speaker mid-call they can't hear her.
We tried this but she still has the issue.
Click to expand...
Click to collapse
Newest update ending in C3 for my Pixel 3 has fixed my speakerphone problem, so far! Will keep you posted.

kperk said:
Newest update ending in C3 for my Pixel 3 has fixed my speakerphone problem, so far! Will keep you posted.
Click to expand...
Click to collapse
Yes, she just updated and tested speakerphone with one of the iPhone's she was having trouble with and no problem. Seems to be working for now!