So I had the SE Mw600 for my nexus one and it worked like a charm but after pairing it with the sensation. No buttons work. I just the the audio and nothing else works. I did some digging and it seems to work for the desire I wonder what is the difference? Anyone have an idea of why it wont work? or have it working?
It is working here as it should.
Works fine here too. I finally see Caller ID with gingerbread powered Sensation
Works here as well. Paired up fine. I could adjust the volume and stop, play and forward like when I had it with my N1.
So its just me... maybe I should factory reset the phone and see if that helps thanks for the answers guys.
loloklo said:
So its just me... maybe I should factory reset the phone and see if that helps thanks for the answers guys.
Click to expand...
Click to collapse
Woah really? A factory reset for the phone just for a bluetooth pairing? Have you tried other options?
Like unpair and remove the headset from your phone and reboot. And for safe measure reset the MW600 as well.
To reset the MW600 headset
1 Make sure the headset is turned off.
2 Press and hold down POWER until the pairing indication appears.
3 Simultaneously press and hold down POWER and CALL button until the headset turns off.
Have you also tried other bluetooth headsets and do they work properly? I just don't want you to go through a full factory reset and have to restore everything in creation if you don't need to. GL
EDIT: And like with my n1, the tracks do not appear on the MW600 (but the caller ID function works) because it's a Sony Ericsson thing. But all the other buttons work without an issue.
kpjimmy said:
Woah really? A factory reset for the phone just for a bluetooth pairing? Have you tried other options?
Have you also tried other bluetooth headsets and do they work properly? I just don't want you to go through a full factory reset and have to restore everything in creation if you don't need to. GL
EDIT: And like with my n1, the tracks do not appear on the MW600 (but the caller ID function works) because it's a Sony Ericsson thing. But all the other buttons work without an issue.
Click to expand...
Click to collapse
Well I have tried everything. I reset the mw600 and unpaired it. I paired it again with my nexus and it works fine.
I haven't really tried other headsets because Well I don't have access to them. Except my bluetooth radio transmitter thing which works fine.
I searched around every other forum here and elsewhere trying to see if anyone had the same problem or similar but nothing. I've tried all the free players that they said worked and what not but really nothing works.
The really odd part is that the sounds comes out fine but none of the controllers work. which kinda make it useless in the gym.
I'll try to reset the mw600 again and pair it again and see if this time it all works this time. I know the factory reset seems a little bit too much for only the bluetooth thing but since I'm the only one having the problem I think it is the phone. Idk I'll wait a little bit more and do some more digging before I reset. Thanks for all the help.
loloklo said:
Well I have tried everything. I reset the mw600 and unpaired it. I paired it again with my nexus and it works fine.
I haven't really tried other headsets because Well I don't have access to them. Except my bluetooth radio transmitter thing which works fine.
I searched around every other forum here and elsewhere trying to see if anyone had the same problem or similar but nothing. I've tried all the free players that they said worked and what not but really nothing works.
The really odd part is that the sounds comes out fine but none of the controllers work. which kinda make it useless in the gym.
I'll try to reset the mw600 again and pair it again and see if this time it all works this time. I know the factory reset seems a little bit too much for only the bluetooth thing but since I'm the only one having the problem I think it is the phone. Idk I'll wait a little bit more and do some more digging before I reset. Thanks for all the help.
Click to expand...
Click to collapse
I am not sure if this applies in your case, but are you on a non-US Sensation? Not sure if the others are using the US tmobile sensation or not. But I am using the Tmobile branded version here. Again, I am not sure if it's relevant in your case.
yeah mine is a Tmobile US sensation. for my luck after struggling with this thing all day yesterday today... I dropped my phone and I cracked my screen. This isnt my week at all. Called HTC and they are saying it will be 160 dollars to fix... Well at least that will take off my mind from this for a while.
*UPDATE* after factory reset to send my phone for repairs... I tried to pair my phone again with the mw600 and it worked fine... I guess there was just something wrong with the phone settings.
I use my MW600 with my t-mobile branded sensation and all works fine. I use it with xiialive and can skip stations fine and everything. The names don't appear on the display, but again like kpj says, it's a se thing.
Actually its not a SE thing but its a Bluetooth stack problem android uses a 1.0 AVRP version called bluez and track name support is only in AVRCP 1.3/1.4.
I found all this by doing some more research on the topic. So when we get an upgraded Bluetooth stack we will be able to see the track names. SE payed for the upgrade to enable this feature apparently.
Can we get the new stack with a custom rom?
ツ
The_Biz said:
Can we get the new stack with a custom rom?
ツ
Click to expand...
Click to collapse
yes. However, I've gone from one version of a rom to another and lost the functionality...and the chef could not explain why.
AFAIK, any rom that is remotely based on a stock one will not support song info.
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?
i have a headset that i want to pair with my Charge, but for some reason when i try to pair it, it keeps telling me that the device returned a code that was incorrect,
first off the headset has no method of input, and second the phone never asked for a code, ive searched everywhere and cant find answers just people with the same issue that just decide to give up and get a new headset.
the Issue was there since EE4 (the version my phone had when i purchased it at the VZ store)
I now have EP4 with tweakstock, tried it with stock rom and still same issue
I know that the 2.1 should automatically exchange the codes is there a way to manually put in the code to the charge?
the head set works fine on a flip phone my brother uses, and im not sure if this is specific to the droid charge, or if this is Android in general as i dont have any way to test it.
any suggestions other than "buy a new one" would be great
oh come on! anyone?
See if another, newer headset has the same problem. If it happens again, it's the phone's bluetooth. If it pairs successfully then it's just an incompatible headset.
Really, there's no other way of testing. Just because one headset works with one phone, doesn't mean it'll work with another, but this isn't a common problem since Bluetooth headsets are mostly universal.
Sent from my SCH-I510 using xda premium
Is anyone else having trouble with keeping their Bluetooth headset connect to their HOX on 1.85? I have a Plantronics, which has worked great until I exchanged my HOX for a new one. I have unpaired and then paired again several times. It pairs and connects, but when I make a call it starts out where I can hear it ring and then disconnects after 2 seconds. Works fine with the Bluetooth connection in my Fusion. Any thoughts?
Same problem
I have the same problem with 1.85. If you disable WiFi the BT will work fine, but it seems like you'll have to decide if you want BT or WiFi....I'm on my 3rd handset and I"m about done with HTC
Tsalagi said:
I have the same problem with 1.85. If you disable WiFi the BT will work fine, but it seems like you'll have to decide if you want BT or WiFi....I'm on my 3rd handset and I"m about done with HTC
Click to expand...
Click to collapse
I finally figured that WiFi was causing trouble. Couldn't believe that was the issue. I am on my 4th and I can now use both. Keep bringing them back! Its the only thing you can do. The phone is sweet now that everything is working.
Ok, so I have an issue with my One X that I didn't have on my Galaxy Nexus. I was able to leave my bluetooth on (on the Gnex) all the time. When I got in the car, after a few seconds or so, it would connect. I never had to think about it. This was on AOSP, CM, or AOKP. No matter the build, it always worked this way.
With my One X, it never connects automatically. I feel like there's a setting I'm not seeing that I need to enable to allow it to act this way. If bluetooth is on, I have to manually tell it to connect to the stereo. Sometimes I have to shut off the bluetooth radio, turn it back one, etc etc.
This is on Sense Builds, AOKP, or CM.
Anyone have any insight? I feel like this shouldn't even be a thought. I should be able to just leave it on and never think about it.
Wrong section. Q's belong in Q&A. Let the mods know so they can move this thread.
Its not you, its the phone, or specifically the Bluetooth stack. Certain combinations of phones and Bluetooth devices (like your car stereo head unit) just don't play well together. Its the same on my car, which is a 2012 Subaru Impreza with factory head unit (which I understand is made by Kenwood). It work fine (mostly, sometimes the steering wheel controls to skip tracks won't work) once its connected. But it won't auto-connect and has to be connected manually every time I start the car. For other people's car stereos, it may work just fine.
There is nothing in Settings that will fix this. Further, I've messed with some of the system files to see if that would help (which some have pointed out has worked on other devices), but no good. I've also hoped that HTC would have fixed the problem with one of the firmware updates (as they sometimes update the BT stack when they update the firmware). But I've tried various builds, including the recent Sense JB firmware's, and the same problem persists.
I've reported the issue to HTC back when the phone was originally released in May. HTC support walked me though the usual steps of factory reset, update firmware, safe mode. But of course, none of this worked, and they logged the issue for further investigation. Aside from a change in the BT stack by HTC, I don't think there is much that can be done.
There are various apps and toggles and such that may make your life a bit easier (and others will likely suggest). And I'm using one now called Speed Enabled Bluetooth. But really, they are just half-a$$ed workarounds at best, and not a true fix. I wished the thing would just work like its supposed to.
My phone just auto connects to my car Bluetooth just fine. I'm on stock at&t 2.20
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
My phone just auto connects to my car Bluetooth just fine. I'm on stock at&t 2.20
Click to expand...
Click to collapse
As I already said, its dependent on the car stereo. Some will work, some won't. What make/model car, and is it the factory stereo or not?
My car is also a 2012 Subaru. its a wrx impreza, so we're in the same boat. guess its time to start looking into an aftermarket headunit.
Sent from my HTC One XL using Tapatalk 2
Hey guys,
I have a bluetooth headphone (Wearhaus Arc), which I had to sent in for repair recently. Since I have them I faced with connection issue, but sometimes it worked at the first go. Also because I wasn't able to update to firmware, the support told me to return it. Before doing so I unpaired the headphone from my phone (HTC One M8 running latest official stock unbranded Android 6.0).
Since I got headphone back, my phone isn't able to "see" the headphone. Bluetooth is on and the headphone as well, but for my phone it's like the headphone isn't there/switched on. I did some pairing testing with other phones (HTC Sensation, BlackBerry Q10, HTC HD2), which found the headphone immediately and worked fine. So my guess is, that only my M8 has a problem with it. Pairing, unpairing and "repairing" (pairing again) between my M8 and the other mentioned phones worked well, so there can't be an general bluetooth issue.
After doing a factory reset on my M8 I'm a step futher, because now the phone sees the headphone (somethimes), but it isn't able to establish a connection. In case my M8 sees it, I tap on the available devices, the phone tries to connect, but a second later I get the message: "unable to pair. Make sure your devices are on and discoverable, and then try pairing again". Rebooting the phone does not work. I also cleared the data and cache of the bluetooth share app and performed a network reset like described here: http://forum.xda-developers.com/htc-one-m8/help/htc-one-m8-bluetooth-wont-android-6-0-t3340279
My question to you guys is, what can I do, to get the headphones to work?
Is it possible, that the phone has is still a piece of information left about the former connection, which refuses any new connection?
Is there a file on the phone, which stores the bluetooth connections? if yes, maybe deleting or editing the file could help?
Thank you in advance!
@@RON
Are you sure that the Bluetooth antenna of your phone is working correctly? It sounds like its an issue of the phone.
akkudererste said:
Are you sure that the Bluetooth antenna of your phone is working correctly? It sounds like its an issue of the phone.
Click to expand...
Click to collapse
Maybe, but as I have written, my M8 can be paired in both directions with the other mentioned phones flawlessly. That's why it actually can't be a general issue, right?
Is there a possibility to test the Bluetooth antenna?
Sent from my HTC One_M8 using Tapatalk
Anyone some ideas?
Sent from my HTC One_M8 using Tapatalk
Recently a firmware update for my headphones was released. After updating the pairing with my M8 works fine