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?
Related
I have am issue where my blueant q2 headset says its connected but calls are not routed through the headset if my phone is left idle (no calls) for 5 min or more. Anyone else having the same issue?
I can toggle Bluetooth off and on and do the same on my headset and reconnect, it just never works if I'm not on a call and the phone has been sitting. Not very practical while driving.
Sent from my LG-P999 using Tapatalk
I have a Q2 and it works fine, great actually. Have you downloaded the BlueAnt Android app? See if it helps.
http://www.mediafire.com/?mijqgkknore
P.S. - It says Q1 but recognizes the headset as a Q2
I've been encountering the same thing with my z9i. Sometimes it will last a while and I'll be able to pick up and use it but most of the time it will "lock up" and I'll have to toggle the bluetooth on the phone. It's definitely an annoyance.
I will try the app and see if it helps. Anyone else having this issue?
matyou98 said:
I will try the app and see if it helps. Anyone else having this issue?
Click to expand...
Click to collapse
I can't get the Q2 to connect any calls whatsoever, OP did you solve the problem, I'm just about to return this thing if it won't work.
mr mystery said:
I can't get the Q2 to connect any calls whatsoever, OP did you solve the problem, I'm just about to return this thing if it won't work.
Click to expand...
Click to collapse
For me, it wasn't the Q2 it was the flaky Bluetooth in the ROM. It would work great with my headset and in the car and then, with nothing changed on either side, would stop working. Rebooting helped sometimes but it never stayed working consistently without some type of intervention.
I have the q2 as well and g2x connects and works but the problem here is the g2x Bluetooth driver itself. If they release GB and still not get this working i will never buy another lg phone. My next phone will definitely be a nexus with all these manufacturer's not getting their act together
Sent from my LG-P999 using XDA Premium App
cenwesi said:
I have the q2 as well and g2x connects and works but the problem here is the g2x Bluetooth driver itself. If they release GB and still not get this working i will never buy another lg phone. My next phone will definitely be a nexus with all these manufacturer's not getting their act together
Sent from my LG-P999 using XDA Premium App
Click to expand...
Click to collapse
LG is definitely making a case with me to go Nexus too, Google needs to get it together and force action with these companies, "no updates, no android for you".
Sent from my iPad using Tapatalk
I have made up my mind. Next year it will be a Nexus device. Done with all these company starting with Sony. First was the Xperia X1. Paid top dollar for that phone and sony lied and never gave it an update. Next was Nokia N900 and just as usually one or two update (can't remmember anymore) and the drop the device and left everyone in the dark. No i come over to LG and all we get from them is soon, this summer.... I have had it with all these companies. I would have had the Nexus S if not for the fact that i needed external SD card. The sensation is looking better more and more everyday to me even with its issues atleast we will get support from HTC. If they don't release this damn update before July is over then we all are really screwed. Now if they release GB and we still have Bluetooth issues and phone reboot or other issues that we currently have, then LG will go down big time. If they release GB and CM7 can not get their new driver working on it then WE ARE REALLY screwed and i for sure will really quickly look into getting rid of the G2x asap.
PS: all their top end devices that just came out all have Froyo. LG what are you guys really thinking. Seriously my suspicion is this. If we get GB i think that will be that LAST update we get from LG. I really hope CM7 can get the new driver to work with GB.
cenwesi said:
I have made up my mind. Next year it will be a Nexus device. Done with all these company starting with Sony. First was the Xperia X1. Paid top dollar for that phone and sony lied and never gave it an update. Next was Nokia N900 and just as usually one or two update (can't remmember anymore) and the drop the device and left everyone in the dark. No i come over to LG and all we get from them is soon, this summer.... I have had it with all these companies. I would have had the Nexus S if not for the fact that i needed external SD card. The sensation is looking better more and more everyday to me even with its issues atleast we will get support from HTC. If they don't release this damn update before July is over then we all are really screwed. Now if they release GB and we still have Bluetooth issues and phone reboot or other issues that we currently have, then LG will go down big time. If they release GB and CM7 can not get their new driver working on it then WE ARE REALLY screwed and i for sure will really quickly look into getting rid of the G2x asap.
PS: all their top end devices that just came out all have Froyo. LG what are you guys really thinking. Seriously my suspicion is this. If we get GB i think that will be that LAST update we get from LG. I really hope CM7 can get the new driver to work with GB.
Click to expand...
Click to collapse
Seriously with all their to devices launching with froyo we can see lgs commitment to the latest software.lg should get out of the game it's obvious they don't know how to play.
Sent from somewhere with something using tapatalk
mr mystery said:
I can't get the Q2 to connect any calls whatsoever, OP did you solve the problem, I'm just about to return this thing if it won't work.
Click to expand...
Click to collapse
Yes I fixed it. The buggy gingerbread leak and cm7 roms both fix the issue for calls. No more disconnects after it sits do a while. There definitely is an issue with the stock froyo and froyo based roms. Hope that helps.
Sent from my LG-P999 using Tapatalk
I flashed EB 1.05 GB 2.3.3 last night and spent the day driving using my Q2 without any problems at all. It even played music and I could make and receive calls with it.
Squid6290 said:
I flashed EB 1.05 GB 2.3.3 last night and spent the day driving using my Q2 without any problems at all. It even played music and I could make and receive calls with it.
Click to expand...
Click to collapse
thats cool, I'm on that rom too but still had that q2 issue, my jawbone ERA seems to work much better in this case. doesn't flake as severely or as often (once in 24hrs)
Squid6290 said:
I flashed EB 1.05 GB 2.3.3 last night and spent the day driving using my Q2 without any problems at all. It even played music and I could make and receive calls with it.
Click to expand...
Click to collapse
How long did you test this? have the phone and BT connected for couple hours and see if it looses sound? mine looses sound in less than 2hrs. The new one i picked up today did it in less than 30mins. I am just about to give up on the G2x.
cenwesi said:
How long did you test this? have the phone and BT connected for couple hours and see if it looses sound? mine looses sound in less than 2hrs. The new one i picked up today did it in less than 30mins. I am just about to give up on the G2x.
Click to expand...
Click to collapse
I used it for over an hour listening to my siriusxm apparently and making calls. No issues.
Sent from my LG-P999 using XDA Premium App
No, not long enough.... Leave BT on and Q2 on. You don't have to listen to music or make calls. Keep checking it by playing a music every 30mins or so and see if it works. During all my test it seems like 2hrs and 30min in, it will lock up. I ended up giving up on G2x because i know it is where the problem is and do not trust WE will ever see another update from LG. I don't want what happened to me with my Nokia N900 to repeat itself. I got the Sensation and boy, it just works. Battery life is unbelievable.
PS: BT worked like it is suppose to.
After about one day of this GB update, what can we tell? Still any issues? Some people bricked their phones, so is there any idea why? Can we recap on what has been achieved this far? Are there any flashable ROMs with all good stuff?
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
aowendoff said:
The phone is still buggy. I have been having issue with BT and the phone locked up on a call once.
Basically, sometimes when I turn my BT headset off, it will still say it is connected on the phone. I will need to turn the BT off and then back on to get it to work correctly again.
As for the phone locking up. I was on BT and switched over to the speaker phone and the phone just died. I had to do a battery pull to get it to turn back on.
So it really just sounds like they need to work on BT more because I never had these issues on Froyo.
Click to expand...
Click to collapse
Did you update the baseband?
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
For those who are still having problems after the update it might be wise just to do a factory reset because froyo and gbread is very different...
* GPS locks much faster now, often instantly, and indoors.
* Switching between 2G/4G seems to be smoother; doesn't lose the connection for a few seconds like it used to
htc2364 said:
I'm curious about this too! I was about to start a tread, but this one shall do.
Questions -
1. (People having reboots before update)
*Did it fix the reboot issue?
2. (People with signal problems before update)
*Did the new baseband fix this/ do you get better signal now??
3. Another problem I have is that wifi and 4G constantly battle each other to see which one gets the signal. So I have to turn wifi on and off until 2G/4G go away.
(For people that have this)
*Did this get solved?
4. * Does GPS lock faster/work better?
I've had three different phones and I've had same issues with all three and even trying different roms. A different rom might fix one issue, but not the others for me.
My main concern is the reboot and signal issues!
These are questions for people that have same or similar issues.
NOT for people with no issues before update.
So please NO "There is nothing wrong with my phone!" People.
Thanks!!
....
Click to expand...
Click to collapse
I had reboot issues before and so far haven't had any, but to make a proper conclusion I'll have to wait, as even before the update sometimes I would make it days between reboots/shut offs and sometimes only hours.
GPS appears to be very good now, as for wifi/4g/2g I always turn off 2g and use only wcdma setting, and haven't had any issues with it, I leave my wifi and BT on at all times too even when not connected and don't have too bad battery strain.
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had, but there are a lot of camera apps (I love vignette) so that's not a huge issue, if anyone has the lg app I would love it back though.
I did have some sluggishness especially this morning, I downloaded some widgets though so it might be more of what I added than the update itself.
one surprise was that I thought it was supposed to wipe all data etc. from the phone, but everything was set up the same as I had it before with launcher pro, so I was happy I didn't have to start from scratch. Also I have been getting occasional force closes with launcher pro that I didn't have before.
as far as quadrant scores go I'm getting consistant 2600+ so that is good, I had Faux's kernal and OC to 1300 w/ pimpmycpu and was getting 2800-3000 so without OC I'm more than happy with 2600. Now if only netflix will make it's way to this phone as is, and hopefully we can root soon as i really want ROM Manager, pimpmycpu and a few other root only apps to work again! Love this community, everyone is so helpful and creative, keep up the good work.
GPS locks Faster
Google Music Beta offline feature does NOT work, won't download.
Android Market did not restore my previous apps.
Touch screen is still dodgy, sometimes requiring multiple touches.
Email, specifically @Live.com mail will not display junk mail. Other folders, yes, but not junk.
More frequent messages about Cannot connect to Server
Has anyone figured out why some people have bricks trying to update? To be honest I still hesitate to do the update because I still don't know why this happens
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
I think it's worth waiting for a rooted flashable version a day or two and to avoid any risks.
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
<nods head and ducks>
mmapcpro said:
MOST of the situations seem to be because they didn't want to follow directions, and insisted on doing it their way...then, "OMG! LG BRICKZORD MY PHONE!!!"
I'm sure there were a minority few that had some other difficulty, but from what I read, almost every "brick" post I read had failed to list "nvflashed stock recovery" as one of the prerequisite steps.
Click to expand...
Click to collapse
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
dmartin1976 said:
GPS appears to be very good now...
Click to expand...
Click to collapse
I wish that were true for me. As I've mentioned in other threads, I'm still getting 90-180 second TTFFs, which is about where I was with stock Froyo. I hope someone will reply to my question in the other thread about the system settings they have that give them such good results. I've fiddled with all of the ones in the hidden menu GPS Test section and haven't found a good combination (and I don't know what the factory settings are supposed to be any more); it's hard because of having to wait a few hours between tests to let the ephemeris data expire in the receiver so I won't just be getting a carryover hot fix.
dmartin1976 said:
some things I noticed, in the gallery now when I hit share I don't see the gmail option, the camera reverted back to stock, which is a shame because I loved the things the LG cam app had...
Click to expand...
Click to collapse
Hmm, that's strange; I still have Gmail in the list of options for "Share" in the gallery.
As for the camera, I think I actually like this one better. At least, it seems to do a better job of taking close-ups with the flash. With the original LG camera, close-up flash photos were always blown-out and overexposed. I took a couple of test shots in a dark room with the flash, and they look great, about as good as you can get with an LED flash, I think.
JHaste said:
this ^^
even so, i had latest cwm running and i didnt brick **** lol people get so damn worried when the updating bar doesnt move consistently so they start fiddling with **** and boom! brick!
Click to expand...
Click to collapse
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
alodar1 said:
If I recall, once you reach the % range....the install range, it tells you, do NOT disconnect. Some of the pictures people were showing were in the Analyze area, before the actual download and install. I think if you get past the analyze phase you can install. I don't believe you can get past it with CWR installed.
Even still, the anticipated failure rate of an update like this (Bricked), is like 8 digits to the right of the decimal point. Even with the problems MS had with the NODO update on the Samsungs, the total # of failures was like 8 World wide. (or just over half their sales. )
So the process is pretty well tested and known.
Click to expand...
Click to collapse
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
JHaste said:
I promise you that I did it with CWM installed... I literally restored my stock nandroid, booted into that and then ran the update tool... I only had one hiccup where after i got to the S/W screen (after I had already downloaded but before the update) it said that I did not have the phone connected so i unplugged and plugged back in and that didnt work... so I unplugged, pulled the battery, put it back in, plugged in and everything went smoothly
Click to expand...
Click to collapse
So it seems some folks just had bad luck
krekabl said:
So it seems some folks just had bad luck
Click to expand...
Click to collapse
or the file they downloaded was corrupt? its not like we had an md5 to match...
JHaste said:
or the file they downloaded was corrupt? its not like we had an md5 to match...
Click to expand...
Click to collapse
well everybody updated the same source didn't they?
GPS locks on a lot faster...but still loses accuracy in middle of route.
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
Hey guys, I'm sure a lot of you are already on one of the ICS roms already. First of all hail all devs who have made our life better before official releases!
However I have seen posts talking about them experiencing Bluetooth problems just like I am right now and mostly mentioning the Music player stuttering and similar issues like that.
My problem is a little different. My aftermarket car deck worked perfectly with all the phones I have connected to, including my GB i727. However after I flashed the ICS my bluetooth connection kept dropping out randomly. Starting with the deck not auto connecting when I get in the car. Then after I manually connect "Phone" in the menu, it will MOST LIKELY disconnect after (on average) 2 minutes with the "Media" still checked (although the connection is not shown on either the icon in the status bar or the display of the deck). Weirdest thing is, sometimes it actually keeps on working after it connects.
I didn't think that would be a problem for me because I don't use Bluetooth earphones and I use my iPod instead of my phone to play music in my car. So I even disabled my Holo Music and my Google Play... I'm on Sean's SKY ICS 4.2D
I am just wondering if bluetooth misfunctioning is a common problem on all current ICS roms for our i727 or is it just the rom I am on right now? Because I drive a Manual car, the hand free in the car is actually very needed for me. So spread your wisdom on the bluetooth issues please!
Thank you!
my jvc car radio doesn't work at all with bluetooth sense updating to sky I c s. The stock I c s leak seemed to work pretty well however. Now the phone vibrates as if it's going to force close then disconnects the bluetooth within seconds of connecting every time.
Strangely, the radio does continue to play for a few minutes even though the radio and phone both say the device is disconnected. All kinds of weirdness going on here! I am going back to the stock leak as soon as I have time to reinstall all my apps for the millionth time.
On a side note, my monster bluetooth speakers seem to work flawlessly with all the roms i have tried. Seems I need an exterminator as I am over run with bluetooth bugs!
I am a programer. I wish I had the time to work on these and help develop these roms. The developers here are some truly talented and generous folks! After finals next week, I will try to devote some of my time to helping out this community which I gain so much from. Thanks to all of you guys! I can't wait until cm9 is in beta/release stage! That will be a dream come true!
Sent from my SAMSUNG-SGH-I727 using XDA
JERM^ said:
Hey guys, I'm sure a lot of you are already on one of the ICS roms already. First of all hail all devs who have made our life better before official releases!
However I have seen posts talking about them experiencing Bluetooth problems just like I am right now and mostly mentioning the Music player stuttering and similar issues like that.
My problem is a little different. My aftermarket car deck worked perfectly with all the phones I have connected to, including my GB i727. However after I flashed the ICS my bluetooth connection kept dropping out randomly. Starting with the deck not auto connecting when I get in the car. Then after I manually connect "Phone" in the menu, it will MOST LIKELY disconnect after (on average) 2 minutes with the "Media" still checked (although the connection is not shown on either the icon in the status bar or the display of the deck). Weirdest thing is, sometimes it actually keeps on working after it connects.
I didn't think that would be a problem for me because I don't use Bluetooth earphones and I use my iPod instead of my phone to play music in my car. So I even disabled my Holo Music and my Google Play... I'm on Sean's SKY ICS 4.2D
I am just wondering if bluetooth misfunctioning is a common problem on all current ICS roms for our i727 or is it just the rom I am on right now? Because I drive a Manual car, the hand free in the car is actually very needed for me. So spread your wisdom on the bluetooth issues please!
Thank you!
Click to expand...
Click to collapse
You should try his bluetooth fixes in the op. I had about the same problem and bluetooth fix 2 resolved it. YMMV
toothpick5 said:
my jvc car radio doesn't work at all with bluetooth sense updating to sky I c s. The stock I c s leak seemed to work pretty well however. Now the phone vibrates as if it's going to force close then disconnects the bluetooth within seconds of connecting every time.
Strangely, the radio does continue to play for a few minutes even though the radio and phone both say the device is disconnected. All kinds of weirdness going on here! I am going back to the stock leak as soon as I have time to reinstall all my apps for the millionth time.
On a side note, my monster bluetooth speakers seem to work flawlessly with all the roms i have tried. Seems I need an exterminator as I am over run with bluetooth bugs!
I am a programer. I wish I had the time to work on these and help develop these roms. The developers here are some truly talented and generous folks! After finals next week, I will try to devote some of my time to helping out this community which I gain so much from. Thanks to all of you guys! I can't wait until cm9 is in beta/release stage! That will be a dream come true!
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
hi-5 on JVC deck... damn... and yea I tried both fixes and no fix. exact same issue
JERM^ said:
hi-5 on JVC deck... damn... and yea I tried both fixes and no fix. exact same issue
Click to expand...
Click to collapse
+1
Sent from my SGS 2 LTE running SkyICS
Yep, same isdues.
Tried many things but nothing.
It worked, still does only on sky ice update 6, but the phone does not deep sleep, that's the problem so can't keep using that.
Hope official rogers will fix it.
odeccacccp said:
Yep, same isdues.
Tried many things but nothing.
It worked, still does only on sky ice update 6, but the phone does not deep sleep, that's the problem so can't keep using that.
Hope official rogers will fix it.
Click to expand...
Click to collapse
yea waiting for the Rogers release too. And sucks how both of you up top are all fellow Rogers users... could it be anything to do with our i727"R"?
toothpick5 said:
my jvc car radio doesn't work at all with bluetooth sense updating to sky I c s. The stock I c s leak seemed to work pretty well however. Now the phone vibrates as if it's going to force close then disconnects the bluetooth within seconds of connecting every time.
Click to expand...
Click to collapse
Same here.
JVC KW-XR810 car stereo running updated firmware.
Bluetooth crashes almost immediately and the phone buzzes.
I use bluetooth for playing pandora or internet radio.
UCALC worked perfectly.
UCLD2 is where problems started for me.
I've tried both fixes listed in the SkyICS thread.
http://forum.xda-developers.com/showthread.php?t=1630021
Hi
My problem with Bluetooth is pairing to the car auduo. The phone can see the device, recognizes the type and tries to pair, but after putting a code I get a connection refused error. Previously worked with stock and custom 2.x.x rooms. From is now a 4.0.4 one.
Any ideas/suggestions?
Solved by replacing Bluetooth.apk to 4.0.1 found at androidforums
Works fine in my Cayman S
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Bluetooth is finally fixed for me in CM10.1. No more Bluetooth Keep Awake. No more hassle of disconnects.
VW RNS 510
Hi guys,
I have found in other forum, and it's working for me.
Break connection between car and S3, and delete devices both in car and phone.
Now try to pair them again but don't let car system to access contact and data in phone.
After I did this my connection is stable.
Guy who suggested this believes that Samsung sends too much data ( all accounts data)and car system freezes).
Hope this works for you too
Sent from my SGH-T999 using Tapatalk 2
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
sounds familiar....
hey there,
I'm down here in New Zealand with a both versions of device, X & XL
my XL has the problem you speak about.
When i leave my house, it takes for ever to disconnect, pain of course because the 3G or 4G wont flip on while it thinks it is still on wifi.
When i return to my home/SSID the device takes for ever to reconnect, if it even does. i go to the wifi settings, and the connection initiation is just cycling, end attempts to connect, over and over.
I've thought i had fix it once before, by installing a new RUU. I was on RUU 1.77.708.3 Asia, could only find 1.77.708.2.
this seemed to fix disconnection on departure problem, but the cycling and hunting continued when i returned.
I have since found that this must be linked to the bluetooth. I say this because while the wifi is hunting/cycling i flip off the bluetooth and the wifi reconnects within seconds. I tested this more and with bluetooth disabled i have no wifi problems at all, but with bluetooth on, its gives my problems.
The second issue is the bluetooth its self. unlike my flawless desireHD, i can only stream music to my car head-deck, when i get a phone call, the music cuts out like it should, but the phone audio doesn't happen, been like that from the get go. wifi was a problem all the time because this dodgy bluetooth was on all the time so i could listen to music in the car and hopefully one day take calls in the car also.
well i have good news for me, today i flashed CleanROM.3.Standard .
http://forum.xda-developers.com/showthread.php?t=1655011
Today for the first time I can take calls over bluetooth in the car. this is good news because i was certain this was a hardware issue, even it it is, i am confident it can be resolved in the software now.
I'll do a few drive-by's my house tonight to test this wifi, see if that got resolved also. I'll let you know the result later.
I tell you all this in-case our issues are the same, it might save you some time... maybe.
good luck with, and check that bluetooth theory because i'm dying to know if its a common problem.
Cheers
Thank you for that very detailed post.
I also have bluetooth running (connected) to my car and it works flawlessly but it may be a cause for the WiFI staying connected as well. I will turn it off and see how it goes as the week progresses and keep this updated as well.
I would also like to flash clean rom but I am using the Rogers variant so I am worried it might not be compatible.
an_xda said:
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
Click to expand...
Click to collapse
This has been a known problem since the HOX has been released.
an_xda said:
As title says, I went to the theatre today and realized I still had 5 bars of WiFi when I was 20KM away from home, was this a one time glitch or is it a known problem?
Click to expand...
Click to collapse
First reaction: It's not a glitch, that's just really good WiFi...
Sent from my HTC One X using xda premium
I did those drive-by's......
Me again...
I did those drive-by's of my house, unfortunately there is no joy for me, still the WiFi behaves the same as before.
Its funny, down here we have assumed that the X is the same as the XL apart from the cpu. But in reality they are two completely different machines.
So I turned off Bluetooth and the problem does not occur anymore, WiFi disconnects as needed but it is obviously not a permanent fix. Another problem is the WiFi being on and off with 5 bars swapping between 4G and WiFi...
CleanROM again......
OK, I was doing some more reading and have since found that the developer of CleanROM has released a GSM patch so the hotspot on his ROMs now work.
You might remember i said earlier in this thread that CleanROM.3 worked best for me but the hotspot didn't work so i couldn't use it.
Now i have CleanROM installed again, Hotspot works, bluetooth both Audio & Phone work, and the WiFi at this stage seems to be doing what it should without having to manually toggle the bluetooth on and off. No apparent bugs to report at this stage.
Software Info on phone says this version is built around 1.29.728.12. I don't know if that means all ICS version of that number are good or not, but again its a place to start. Its looking like some versions have the issue and some don't, this re-assures me that it can be resolved within the software. I don't mind testing this stuff, as long as the developers don't mind developing it, and its a good learning curve.... its all good.
Check this CleanROM work out, it could be your answer.
http://forum.xda-developers.com/showthread.php?t=1655011
I'll check back in in a day or so and update you on my WiFi situation.
Cheers!
Thanks again for all your research and assistance.
I have the Rogers variant, should be no problem flashing it to CleanROM correct? Also, for each new CleanROM update, I would have to wipe and flash again? Seems troublesome.
Can you advise on the process required to flash the ROM? I am new to Android and the steps in the thread is not as comprehensive.
Many thanks.
hi there, show you how to load roms, thats a big job for me....
...I'm new to this myself, but i know a tutorial that will save me a ton of typing.
you need to do 2 things first, before flashing roms.
1,Unlock your bootloader
2,Install clockworkmod
have a look at this ,
http://forum.xda-developers.com/showthread.php?t=1647272
Study this thread, very helpfull. He explains how to install clockworkmod on your device, once you have that done you are 80% there, and you only have to do this process once, once done, flashing roms will always be the last 20%, you never do this again.
Infact flashing roms and backing up your own rom is a very simply task. the commands are on a list, just choose them as you go. To backup, wipe, and flash a new rom takes me less than 10 minutes.
Go to you tube and look at this, this shows you how Clockworkmod works.
http://www.youtube.com/watch?v=XOQEmQYFEeY
dont be freaked out, take it step by step, you'll be fine.
I also started this thread, regarding working roms for this wifi issue
http://forum.xda-developers.com/showthread.php?p=27585586#post27585586
no one has replyed yet, but it might yeild helpfull info later on perhaps
Thanks, I will do this shortly. Will unlocking the bootloader or doing any of the aforementioned steps give me the tampered signature?
Yes
yes, your phone will be marked.
Boot loader will be marked "Unlocked" , even if you relock it, its just gonna say "relocked" . nothing you can do about that.
The boot loader will also say "tampered" if you update the rom, but that msg dissappears completely if you update the phone via an RUU.exe
Can this hurt me with regards to warranty requests? I know I can remove the tampered status by flashing a stock ROM but I am concerned re: bootloader.