Related
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?
We switched from T-Mobile to ATT and got 2 Inspire 4g's and one Infuse.
Now my wife is hating her Inspire because she says the call quality is terrible. She can barely understand the person she is talking to, and if she turns the volume up it gets worse and worse.
She does not think it is the ATT network because it happens no matter where she is, and is not sudden or sporadic. She says it is every call all the time.
Any ideas before we take the 2 Inspires back?
You have a couple of options. The first would be to divorce her. (Just kidding.) The call quality is good on these phones. It is possible that you may have received a defective unit. The second option would be to exchange the phone for another and check the quality on the second unit, which is what I would recommend you try. It should not be happening on every call. There is nothing you could really try until you root your phone and test different fixes, but you should not need anything right now on a phone you have not changed yet.
I am in agreeance with the above poster, it sounds like you may have a defective handset, in all likelihood you should be able to exchange it, sooner than later and see if it works better. The other issue could be your area just has horrendous service for AT&T as that can happen as well.
Thanks guys, I agree we need to exchange it sooner than later, I am just worried because both Inspires we have have the same issue. I dont think it is the service because my Infuse is fine, and we have an iPhone 3gs that is fine in the same areas.
If both Inspires have the same issue it is possible they may have come from a bad batch. It is known to have very good call quality, and on certain roms you just have to apply a patch to fix sound issues. Normally, HTC build quality surpasses Samsung build quality. It may be worth it to go to a different store and try an exchange there to see how that goes. If your Infuse is working well, so should the Inspires.
Wolf_2 said:
If both Inspires have the same issue it is possible they may have come from a bad batch. It is known to have very good call quality, and on certain roms you just have to apply a patch to fix sound issues. Normally, HTC build quality surpasses Samsung build quality. It may be worth it to go to a different store and try an exchange there to see how that goes. If your Infuse is working well, so should the Inspires.
Click to expand...
Click to collapse
Well just because my son really likes his Inspire I went ahead and rooted his and installed the Android Revolution HD ROM. Here is what I tested/noticed:
With the downgraded ROM that is installed during the Rooting process the problem remains, and I was unable to use wifi. It would connect to the wifi, but could not browse the internet.
Once I installed Android Revolution HD I could connect and wifi was fine, but the phone signal was weak. So I installed the linked radio from the first page of the ROM and it went back to a strong signal, but not really any different than stock.
I am convinced that the issue is the radio, not the physical device, so I think I just need to find the right one.
If you are using the M2 radio that is recommended for the AR rom, then you should already have the correct Ril files that match that radio because they are included in the rom. The downgrade rom that is used during rooting needs to have a newer radio flashed in order to get it working. If you are getting any kind of tinny audio quality then there is a patch in the first post that fixes sound quality issues that a lot of people get. These patches are used for most of the European based DHD roms.
sgrant said:
Well just because my son really likes his Inspire I went ahead and rooted his and installed the Android Revolution HD ROM. Here is what I tested/noticed:
With the downgraded ROM that is installed during the Rooting process the problem remains, and I was unable to use wifi. It would connect to the wifi, but could not browse the internet.
Once I installed Android Revolution HD I could connect and wifi was fine, but the phone signal was weak. So I installed the linked radio from the first page of the ROM and it went back to a strong signal, but not really any different than stock.
I am convinced that the issue is the radio, not the physical device, so I think I just need to find the right one.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1106324
I have owned many AT&T phones, and the Inspire has one of the best sounding calls I have ever had. I would agree that it is probably a bad batch of phones, or something damaged the phones when they were shipped to the store. I have rooted/M2 Radio, and am running LeeDrOiD. This is by far the best phone I have owned. I am sorry that your wife is having issues, but i would definately try exchanging it for another Inspire before giving up.
i have no problems with call quality except for speaker
when i put phone on speaker the other end could never hear me
i would suggest putting ur sons phone back to stock, and taking them both to ATT and reproduce the issue for one of the reps and say see listen the phone sounds like total crap please fix this and have them replace both phones. do not leave the store until both of ur phones are working correctly
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!
So my thunderbolt has been overall great but i have this problem where if someone calls me they cant hear me but i can hear them and i can hear myself in my own speaker. is it a setting problem? i also flashed the latest radio for GB on the Infected Synergy Rom.
mistersikee said:
So my thunderbolt has been overall great but i have this problem where if someone calls me they cant hear me but i can hear them and i can hear myself in my own speaker. is it a setting problem? i also flashed the latest radio for GB on the Infected Synergy Rom.
Click to expand...
Click to collapse
I've literally had that same issue on almost every device I've used on Verizon and Alltel at some point. Some areas it's happened a lot in, other almost never. I'm hesitant to say it's the device because of my experience. I think it's something quirky with the network. For me, if I just call them back it works fine. It used to happen almost every time I called my Mom. Second call was a charm though. Then it mostly stopped... about the time she got off that damn Motorola and onto a BlackBerry... but it still happens occasionally.
yeah =[ ive never had this problem though and its constantly doing it because i was originally on cm7 but it started to i flashed another rom and it worked for a couple of calls at first but now no calls go through and im afraid to call verizon since im rooted but idk what to do =[ thanked you btw
mistersikee said:
yeah =[ ive never had this problem though and its constantly doing it because i was originally on cm7 but it started to i flashed another rom and it worked for a couple of calls at first but now no calls go through and im afraid to call verizon since im rooted but idk what to do =[ thanked you btw
Click to expand...
Click to collapse
eh.... I've called them with issues on both my rooted HTCs. It's never been a problem. I've talked to guys there about their rooted Androids. If they tell you to do this or that, either play super-stupid or BS your way through it and get them to put a work order out to check out things on their end. If that doesn't solve it, then it's time to go back to stock and exchange some hardware or something.
i was just experimenting and it turns out after like 25 secs they could hear me but im still lost on why
I recently got my MyTouch4g Slide. I used Revolutionary tool to S-OFF the device, and all was well.
After a day of usage, I began using the Bluetooth hands free in my 2010 Chevy Equinox. The connection synchronizes, no problem. All the hands free buttons work, and everything appears functional. However -- I have no audio, either mic. or speakers, from the bluetooth. I have to activate the handset to have a conversation, rendering the bluetooth useless.
Before I reached out to anyone, I performed the RUU installation from http://forum.xda-developers.com/showthread.php?t=1178082. It reverted my hboot, system, etc back to stock. However -- it is still S-OFF. So how do we get S-ON back on this phone?
Regarding the bluetooth -- I began escalating to Tmobile and GM. GM said there's nothing wrong with my Bluetooth (it works with all my previous 3 phones OK). Tmobile says this is not a known issue.
I called HTC support, and they said it sounds like a phone hardware issue with the phone.
I would like to know two things, which I cannot find searching the MT4G Slide forums:
* How can S-ON be restored? (I thought the RUU would handle this). I want to know in case I have to send it back to HTC.
* Has anyone had these bluetooth problems, before I send it in for a replacement?
Thanks!
I just got my 4G Slide yesterday, and haven't yet paired it with my '10 Equinox.
I'll do that tomorrow and let you know if it works or not.
I haven't had any issues with bluetooth on my JVC deck, but there is no problem sending back an S-OFF'd device, I've sent back several with no issues. Some devices are factory S-OFF, plus they never check returns.
Thank you both for the feedback.
jonnycat26, Please let me know what happens when you pair with your '10 Equinox. It's great to have someone with the same device and car make to test, to confirm if it is in fact my device.
I was able to successfully make a call without any issues. Or at least, I had audio when I did (call went to VM, and I did not leave a message).
jonnycat26 said:
I was able to successfully make a call without any issues. Or at least, I had audio when I did (call went to VM, and I did not leave a message).
Click to expand...
Click to collapse
jonnycat26,
You were able to hear audio and use the mic in your 2010 Equinox?
I guess this confirms I have a hardware issue. Sucks.
Thanks again!
Seeing as the Bluetooth worked for you & GM believes it's a phone defect, I am getting a replacement from Tmobile.
I know you already said you are getting a replacement, and for as expensive as this piece of hardware is - I wouldn't do anything different.
Figured i'd chime in though, have no issues pairing and using my bluetooth headset. Lets me do voice and listen through the headset.
My hands free (genius) mode works, though I don't use it.
I have a bluetooth game controller coming, somewhere in the mail. I know that's a whole other animal with it's own set of issues, but i'll let you know how that goes.
Thanks for posting about this, though, and it's lucky you found someone with the same stuff to test and compare. Bluetooth is going to be the next focus of my attention, I think, so i'm soaking up everything I hear about it now.
If anyone has found a way to make it S-ON, i'd love to know just to know, but it shouldn't be a problem with warranty issues if it was S-OFF.
The worst part of this for me is I have only had this phone since Friday. Further, it was a replacement for a faulty LG G2X, which I had RMA'd three times, and was about to cancel my service before they finally offered me a different phone.
So this will make my fourth return to Tmobile (three G2x, now a MT4G Slide) in the past three weeks. I have also spent about 30hours on the phone with them in the past three weeks.
I am truly exhausted dealing with this, but I really like this phone (the G2X sucked). So I am giving it one more shot.
They are sending me a new phone again, and not a refurb, so that's nice.
It's worth it.
I'm on my second one, I returned my first one. They took it back without hesitation, so even if you have to go through one or two at the beginning it's worth it.
You have the first few days after you get it, to exchange a defect for a working model. With this phone, it's absolutely worth it. Too expensive to walk around with a damaged one - especially from the door.
Your patience will be rewarded with an awesome piece of tech in your hands, it's amazing what you can do with this device.
foodogg said:
jonnycat26,
You were able to hear audio and use the mic in your 2010 Equinox?
I guess this confirms I have a hardware issue. Sucks.
Thanks again!
Click to expand...
Click to collapse
I was able to hear the audio without any issue. My call went to VM, and I didn't leave a message, so I can't say for sure the mic was working, but I have to believe it would.
arcticwolf8 said:
I haven't had any issues with bluetooth on my JVC deck, but there is no problem sending back an S-OFF'd device, I've sent back several with no issues. Some devices are factory S-OFF, plus they never check returns.
Click to expand...
Click to collapse
Weird, I have a JVC KW-NT1 that worked AWESOME with my TouchPro2 but this MT4GS has a bunch of static issues which pisses off my callers...does anyone know of a fix or a BT radio software update perhaps? It sucks that the phone is LIGHTYEARS ahead of my ancient TP2 but the BT might make me return it
btw
I'm working on a full unroot script with s on on the Dev page.... Expect it released next week
xmc wildchild22 said:
I'm working on a full unroot script with s on on the Dev page.... Expect it released next week
Click to expand...
Click to collapse
That would be handy indeed.
sent from my RuBiX infused MT4G Slide using xda premium