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] can't hear other side in conversation.

hey,
I bought the nexus s (9023) about two months ago, stock rom, not rooted, and for the last week or two, it started making problems.
about 1-5 times a day, i can't here the other side at all. as if it's on mute. not even the ringing tone, before I'm answered. the only thing that solves it, is to restart the phone.
in other forums i've read that it's a mess, and that i should use my warranty. the problem is i bought the phone abroad, and shipping it should take about 3 weeks.
is it a common issue?
can i solve it alone, mabye by switching to a non-stock rom?
i'll be very happy to read some good news here, but bad news is better than non.
thanks a lot,
tal
p.s, iv'e downloaded system info to monitor the temp, and it doesn't happen necessarily when the phone is hot.

I don't know... I am rooted, I have used 5 different roms since purchasing my phone.
Stock
CM 7
Savaged Zen
Oxygen
Soju
I have also used several kernels
CM Stock
Netarchy
Matrix
James Bond
Trinity
So far, on all roms and kernels I have experienced the same problem. You make a call and it connects, looking at the screen the time counter is going but there is no sound; it will sit there and hold the call for 30-55 seconds then ends call. A quick redial and bam it works. Some people have reported that they answered and there was nothing. I don't know, it's really obnoxious.
The other, more annoying problem is that randomly on calls throughout the day the phone will just reboot itself. Right in the middle of a call. AHHHH like 3-5 times daily!

help, anyone?
i'm stuck with this, and a bit clueless.

Well, somehow I discovered that the problem is related to the bluetooth. as long as it's turned of, nothing will happen, on the other hand, when I use my earphone (most of my conversations happen while driving) i need to restart my phone every 1-2 calls
any ideas?

just u can't hear other one while calling u?
thanks.

so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.

tal89 said:
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
Click to expand...
Click to collapse
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App

it's quite obvious, unfortunately it doesn't work.

cutiyar said:
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i can't hear, and he can't hear as well.

tal89 said:
i can't hear, and he can't hear as well.
Click to expand...
Click to collapse
hehee its problem ,
am really disappointing with nexus s , but i dont have enough money to buy HTC product again.

any solution?
Hi, did anybody have any solution to this problem?
I live this problem on almost half calls of specific numbers.
I am desparate...

Try setting discoverable timeout to never? Have you tried a different Bluetooth device?
Sent from my Nexus S 4G using xda premium

I have this problem too. This seem to happen on some Kangs and nightly, but not all of them. I can't hear when someone calls me. But when I call someone, I can hear them. I always have Bluetooth off (do not use them).

I live the same problem. No problem for outgoing calls. For incoming calls, I cannot hear caller's voice but they can hear me. It is not for all numbers.
I am on t-mobile and nexus s (cynagenmod nightlies). For all incoming calls from tmobile numbers no problem. But for almost all other carriers, it is just random.
I feel like I started having this problem after updating from CM 7.0.2 to 7.1 RC and thereafter(but not very sure on this).

If anybody still following this topic, I would suggest you to contact samsung if you still have warranty. On the second attempt they sent me a brand new phone with box and accessories.
Sent from my SGH-T989 using XDA

Or, you might give it a try with a different radio for your model:
http://forum.xda-developers.com/showthread.php?t=1116884
If you go this road, make sure you backup your EFS folder.

What i would do is if it is still in warranty just give it back to them and they'll probably give you a new phone. Since you said it takes 3 weeks to ship, just wait for it and use another phone if possible. Its not like your life is going to end. I think the problem is, not every phone is the same so there will be problems especielly when flashing a rom. For example unstable roms might not allow you to use this app or have serious effects on your phone.
Best to give it back to samsung and get a replacement.

[Q] NS i9020 weird call issue

Hello,
I've been a user of the xda ROMs for quite some time and i appreaciate all the work that's been put into the community.
Sadly, i have stumbled onto an issue i cannot solve myself, so i am seeking your help.
Description: When receiving a call and answering it (phone vibrates and rings), i cannot hear the other person, but they can hear me. (Speaker on/off doesn't do a thing, volume rocker up/down either). If the person calls back within a few minutes, i can almost always hear them and have a normal conversation. This does not happen in 100% of the cases, but in more than 50%. I have switched ROMs, kernels and radios (ATM i have CM7.1 RC, mar1x bfs v4,5, and XXKB3)
Is there any hope?

same issue on i9020t
I been having the same issue, but not quite as frequent, on my I9020T. I've experienced it with Cyanogenmod 7.1RC1 and NSCOLLAB (also based on CM71). I think I had it with CM7.0.2 and CM7.0.3, but can't remember for sure. The problem does not occur when I revert back to stock 2.3.4 rooted.
A somewhat related post in this forum, http://forum.xda-developers.com/showthread.php?t=1188264, got me thinking. The OP had a similar problem on an I9023 when bluetooth was enabled. I've noticed on NSCOLLAB that DSPManager is running a "Headset" service. I do not have DSPManager installed on my stock install.
Can someone more knowledgeable tell if its possible this service could be related to the problem with callers not being able to hear me. FYI, my bluetooth is normally off and I don't use a headset. I'm back to running NSCOLLAB 1.3.8, but I've disabled the Headset service. If the problem doesn't occur for a couple days, I think I may have something.
dinuvali, is the Headset service running on your build?

Removed DSPManager earlier. Just answered a call where they hear me but I can't hear them. They called me back, all normal.
Oh well, rolling back to stock for now.
Sent from my Nexus S using XDA App

Thank you for the reply,
Yes my CM 7.1 is running the DSPManager service.
Also, my neighbour who has the exact device as me, but stock unrooted, has never experienced this problem.
Along with this problem of not hearing the other person on the first call, i also get the dropped call once in a while (not only after 3 mins of talking, but also while the phone is ringing and they still haven't picked up yet)
From all the posts i've read concerning this issue, i think it's mainly a hardware issue, but maybe it can be bypassed with some sort of tweak.

Major breakthrough imo
Pressing Hold (left upper corner) and then unholding will render me able to hear the other person!

dinuvali said:
Major breakthrough imo
Pressing Hold (left upper corner) and then unholding will render me able to hear the other person!
Click to expand...
Click to collapse
Great find! Come to think of it, I never had it happen when I answered someone and immediately hit speakerphone, something I do alot when in my car mount.
I think I'll reload NSCollab, new version just came out today. When it happens again (unless they fixed it) I'll try this out. Thanks!

[Q] Loud static in call

I've been reading up on this and I'm to the point where I'm contemplating having Verizon send me a nightmare... I mean refurbished device.
How many people are having loud static in calls (randomly)? I'm not talking about a bad signal or something that's only happened to you once. I'm saying a straight up 90% of your calls your ear drum is about to explode because the static just suddenly pops up and is 5x louder than the conversation you're having with the person on the other line.
If you're experiencing this, have you been able to fix it?
I read/tried
-New radio
-New 4G SIM card
-Min CPU to 200mhz
-and more that I cant even remember off the top of my head
Basically I'm trying to see if people are experiencing this across the board, or if I might get lucky with a refurb from Verizon (as this is my absolute LAST resort, seeing as I've never received a working Verizon refurb).

I too have this problem. No solution yet.

Yeap, known issue with the phone. I recently contacted Vzw about the issue and they told me that Samsung knows about the issue and there currently isn't a fix available.
They offered me a completely different replacement device.

I voted no. I have heard it before, but it's not a common occurance, and I haven't had it at all in the last two or three leaks.

Never once had it
Sent from my SCH-I510 using xda premium

I have it. I'm currently on humble 5.0. Although its not as often as other gb leaks, it does happen. I find it to occur when screen dimms during call or if I pull the phone away from my ear and the screen turns on. The only setup the static noise did not occur is stock froyo.
I think many of us with this issue are waiting for the official update. If the static noise continues then I will contact Verizon for a replacement.
Oh and this charge is a refurbished phone that was exchanged for my crappy fascinate.
Sent from my SCH-I510 using XDA App

I had never thought of the screen turning off being the issue. My Touchpad has an issue with sound when the screen goes off. Hrmm... Maybe something to force the screen to stay on would resolve it.

I've narrowed this problem down.
Using GB Roms prior to EP4 this always happened, even with EE4 Radio. It also happened with EP4 radio but EP1/2/3 Base.
Therefore the problem is isolated to the EP1/2/3 base software.
I then isolated it to the dialer application itself. The fault occurs in Dialertabactivity or phone.apk.
If you pull the phone.apk or dialertabactivity.apk from stock EP4, this will go away for most phones.

Hmm want to see if anyone else has tried this.

Umm if you do this you will not be able to dial and utilize the phone. So yeah it will get rid of static because you won't be able to make a call hahab
cmdrfrog said:
I've narrowed this problem down.
Using GB Roms prior to EP4 this always happened, even with EE4 Radio. It also happened with EP4 radio but EP1/2/3 Base.
Therefore the problem is isolated to the EP1/2/3 base software.
I then isolated it to the dialer application itself. The fault occurs in Dialertabactivity or phone.apk.
If you pull the phone.apk or dialertabactivity.apk from stock EP4, this will go away for most phones.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App

Incorrect. You can push the ep4 versions of the apks using adb and it will work. I've tested.
Sent from my SCH-I510 using Tapatalk

I think there must be a bunch of defective phones out there doing this. I have never once had this happen to me, but I do way more texting than actual talking on the phone.
The business owner where I work is the exact opposite however. He is one of those guys who walks around with his phone constantly glued to his ear (he has 4 Gorilla batteries) & it has never happened to him either.
I asked him about it yesterday & he had no clue what I was even talking about.
~John

What I've noticed isnt so much a blaring of static as the other person im talking to sounding like they are trying to talk through a muffled microphone. Something like they have the microphone on their phone wrapped in a sweater and they are trying to talk through it. I cant understand half of the people I talk to.

I had this problem but the recent leaked OTA update: http://forum.xda-developers.com/showthread.php?t=1364298 fixed it for me. It's the first time anything gingerbread has been on my phone without the issue. A 15min call to my gf after the update produced a clean call with no deafening static/popping/crackling. I was worried for a second though cause she started unwrapping xmas decorations that were wrapped in tissue paper. There's a full odin of the EP4D release here: http://forum.xda-developers.com/showthread.php?t=1365376 should resolve the issue for those not running stock EE4 (though I haven't tested this yet, if you do use it report back if it works).

Also check out this thread for not only a cwm version of the OTA ep4d but also a modem updater file that can patch your modems to EP4D - they just need to be EE4 prior to flashing.

So I used the odin of the debloated/deodexed/rooted ep4d (the one I posted in my original response above, created by danalo) last night, first call I make today I get the static.

Sucks!!
mhemu said:
So I used the odin of the debloated/deodexed/rooted ep4d (the one I posted in my original response above, created by danalo) last night, first call I make today I get the static.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App

I went back to stock, going to see if the over the air works. So far the only resolution is to go back to stock and the manually run the update to ep4d.
Sent from my SCH-I510 using XDA App

mhemu said:
I went back to stock, going to see if the over the air works. So far the only resolution is to go back to stock and the manually run the update to ep4d.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
So, got the static after going to stock and doing the manual update...wtf. Decided to go back to stock and see if the OTA was ready...it was...got static...wtf.
Looks like I will be getting in touch with Verizon and see what my options are, sounds like some other people with the issue have had verizon admit there's an issue and have been compensated. I won't go into the details of what others have done, but I will say I don't plan on giving them more money than I already did for this phone. I'll report back when I have a resolution.

Ya its allot better but definitely still there. I was really hopping this would get fixed and at first it seemed good but after a few calls I got the static. I'm not sure what to do with it now. I've gone back to completely stock and took the update and it's still there.
Sent from my SCH-I510 using xda premium

Static noise since FP1

I had the static noise once in a while one ep4 but since I updated to FP1 all around and latest eclipse rom I hear it in every call any advice
for me,by me and I love you

I have the same thing. I did a full ass wipe and let it update from ee4. Seems better now.
Mine also started doing ghost key strokes and force closes.
Might be time for a replacement soon.

Agreed I was going to go back to a tbolt but the the other guy backed out
for me,by me and I love you

I reflashed and still getting crap call quality and the phone has a lot of glitchy moments. Says "charging" on lock screen even though I am not plugged in but battery is almost dead.

I just flashed 2.0 eclipse final and will see if anything changes
for me,by me and I love you

I've never had any noise during phone calls until I updated to FP1. I'm running the stock FP1, and experience intermittant electronic glitch type noises during calls. The volume of these noises is significantly louder than the call volume. I'm going to go deaf if I keep using this phone

I agree I see that if the call lasts longer than 15 seconds the sound starts
for me,by me and I love you

I also got the crazy loud static once with stock FP1 and never had it before. I also still get robot voice and occasionally lose outgoing voice connection. I see no voice improvements in FP1. If I wasn't so mature I would start to get mad right now.
Sent from my SCH-I510 using XDA

themortalwombat said:
I've never had any noise during phone calls until I updated to FP1. I'm running the stock FP1, and experience intermittant electronic glitch type noises during calls. The volume of these noises is significantly louder than the call volume. I'm going to go deaf if I keep using this phone
Click to expand...
Click to collapse
I was holding out for Tweakstock but decided last night since I was bored that I would just go all the way back to ED2 and do all the OTA's. since then I have used my phone darn close to 75 times and on all 75 calls (and I am not exaggerating this) I got either static, or one of those old timey modem noises after a minute or so.
Guess who is getting a call tonight? BTW on EP4D In the same situation I *might* have heard the static on 2 of those 75 calls. This really stinks.....

Same problem for me.. i'm on DC #3. today i spoke with a tech, and instead of troubleshooting the phone again, she offered me a factory reconditioned Nexus.. it will be here tomorrow.. not new but better than a 4th DC... what's funny is, just 2 weeks ago they said i couldn't get another type of phone.. i also have the insurance so if that messes up i can get that replaced too.. FYI.. she also said there was no reports of problems with that phone after the new update, i strongly suggest calling and reporting it. if it helps my tech was named Jenifer..

102mm said:
Same problem for me.. i'm on DC #3. today i spoke with a tech, and instead of troubleshooting the phone again, she offered me a factory reconditioned Nexus.. it will be here tomorrow.. not new but better than a 4th DC... what's funny is, just 2 weeks ago they said i couldn't get another type of phone.. i also have the insurance so if that messes up i can get that replaced too.. FYI.. she also said there was no reports of problems with that phone after the new update, i strongly suggest calling and reporting it. if it helps my tech was named Jenifer..
Click to expand...
Click to collapse
I guess I should do the same what number do I call to talk to a tech for a replacement
for me,by me and I love you

i just called the CS 800 number. got the new phone today! good bye Droid Charge!

102mm said:
i just called the CS 800 number. got the new phone today! good bye Droid Charge!
Click to expand...
Click to collapse
What phone did you get and was it your first replacement
for me,by me and I love you

Bump to get some answers
for me,by me and I love you

I'm trying to get a different phone as a replacement but all support wants me to do is to try safe mode to see if an app is causing the issue, which we all know isn't the problem. Anyone ever tried it?
Sent from my SCH-I510 using xda premium

mefloump said:
I'm trying to get a different phone as a replacement but all support wants me to do is to try safe mode to see if an app is causing the issue, which we all know isn't the problem. Anyone ever tried it?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
You should just tell them it isn't working so ask what they will do and most people threaten to cancel their contracts
for me,by me and I love you