Related
I have the thing basically working. I am also getting a Vox 710s to try as well.
My primary concern at this point is auto connect. I am a consultant and get in an out of the car a lot. So it is pointless if I have to click the stereo 6 times each time I get in. I need the thing to just work. I may return the deck if I can't get it too work.
So I need to find out where the failure is. Then I can pursue it with the manufacturer. Why can't this stuff just work?
So if I find a bluetooth headset that does auto connect to the phone do you think that is enough I can't got to pioneer and say the problem is your deck?
If the head set doesn't auto connect which I find hard to believe then I can work with jetware or cingular to see what is up. I am guessing it is the deck.
Thoughts
opps
phone is a cingular 8125 up to date roms running the latest Jetware.
another poster on crutchfeild says tmobile dash does autoconnect
does this narrow down the cause?
I spent over a month working with Pioneer and Jetware with an AVIC Z2 GPS unit with Pioneer's ND-BT1 adapter. In the end, I had to pull the Z2 and installed a Kenwood. Pioneer tech Support finally admitted that they suffer problems with nearly all PDA type phones, especially when they 'sleep'. Seems the connection is dropped nearly as fast as it is made and the devices won't stay connected. Mine dropped EVERY call when the backlight went out after 60 seconds of non-pda use. If i set time timer up to 5 minutes, it dropped the call when the PDA went to sleep. Leaving the PDA on all of the time of course drained the battery.
My wife now has the HTC Touch in her car with the AVIC Z2 and the ND-BT1, however, the problem isn't there. Pioneer has come out with a 'Service' upgrade program for the Z2 and the Touch uses a newer WM6 version. The two seem to be compatible.
thanks for the insight
Having just read the mk6000 review I don't feel so bad. I was wondering how well as system between your speakers and you deck would work.
That said I ordered an unlocked 710 (vox) to test out with wm6 and bt 2.
I am hoping this will work. Do you think I will still need Jetware?
xophere said:
Having just read the mk6000 review I don't feel so bad. I was wondering how well as system between your speakers and you deck would work.
That said I ordered an unlocked 710 (vox) to test out with wm6 and bt 2.
I am hoping this will work. Do you think I will still need Jetware?
Click to expand...
Click to collapse
Try it first without Jetware. It is now with at 30 day free trial and limited features but good enough to test once you get your new unit. If you find out that you need it, then register it.
I have had a Pioneer DEH-P9800BT for many months now, and I am getting sick of having to click 6 times to connect the phone. You would think that the stupid thing could perform the same thing when you turned on the car/stereo. I wish I could get a firmware update or something to fix it.
Replace your Pioneer with the one of the Sonys (MEX-5000BT if you need preouts, MEX-2500BT if you don't). I've been using the 5000 since January -- once I did the initial pairing, it connects every time both in handsfree & A2DP.
My Atrix pairs up nicely with my '01 BMW's BT system, but will drop the connection after about 15sec, and then reconnect again, hold that connection for about 15sec, then drop it. Phone will show Paired but not connected, and the car will be in a similar state. Following other's suggestions, I cleaned out my Contacts-- even with no Contacts in the phone, the same thing happens.
Any idea what's going on? My iphone 3gs and 4 connected 100%, uploaded their Contacts, and never gave me a moment's problem, so I know the BT in the car is working OK.
Help!
Sorry to hear that. I have so far no problems with connecting my phone to my built in BT system. I have a Mazda 2010. I stream music and get incoming calls too.
I used a bt headset for an hour long conference call this morning. No lost connections yet. Reboot doesn't help?
Sent from my MB860 using XDA App
Nope, rebooting doesn't help. BT on the Atrix works just fine with my Panasonic house phone that has BT on it.
I had the same issue today in my 2010 Dodge Ram. Captivate worked great in it, but the Atrix dropped the BT/Call after 30-45 seconds or so. I haven't noticed it dropping connection when I'm not using the phone (I have an icon on my ent/nav headunit), only saw the icon disappear when on a call.
Exwoodchuck said:
My Atrix pairs up nicely with my '01 BMW's BT system, but will drop the connection after about 15sec, and then reconnect again, hold that connection for about 15sec, then drop it. Phone will show Paired but not connected, and the car will be in a similar state. Following other's suggestions, I cleaned out my Contacts-- even with no Contacts in the phone, the same thing happens.
Any idea what's going on? My iphone 3gs and 4 connected 100%, uploaded their Contacts, and never gave me a moment's problem, so I know the BT in the car is working OK.
Help!
Click to expand...
Click to collapse
OK, so I messed with it some more...
If I'm super-fast, I can dial from the car's BT system-- and the name of the phone does appear on the car's Nav. That is, until the phone and/or car drops the connection.
I've asked for help on Motorola's forum, and been tracking down a Product Manager @ ATT to get the word up the chain.
I have the same issue with my 04 3-Series. I posted about this in the Problem forum.
No bt issues here. I used it yesterday with a car kit/fm transmitter to stream Slacker and nav simultaneously to my stereo for a couple of hours and it worked great.
Ziuck said:
I have the same issue with my 04 3-Series. I posted about this in the Problem forum.
Click to expand...
Click to collapse
Think we've got the same BT ULF's in our car. Please let me know if you find a solution, and I'll do the same.
mgymnop said:
Sorry to hear that. I have so far no problems with connecting my phone to my built in BT system. I have a Mazda 2010. I stream music and get incoming calls too.
Click to expand...
Click to collapse
Can you skip forward and back and pause?
I could with the iphone but have not been able to get it to work with android.
The weirdest bit is that I got it to work for Pandora ONCE... then never again.
I think it has something to do with the way android treats certain devices... I have motorola BT stereo headphones that the controls worked for WinMo W7 and iphone, but do not work on any android device I've tried.
I also lose connection with the in car BT occaisionally but not very often and can usually get it to reconnect without much hassle.
2010 mazda 3.
Exwoodchuck said:
My Atrix pairs up nicely with my '01 BMW's BT system, but will drop the connection after about 15sec, and then reconnect again, hold that connection for about 15sec, then drop it. Phone will show Paired but not connected, and the car will be in a similar state. Following other's suggestions, I cleaned out my Contacts-- even with no Contacts in the phone, the same thing happens.
Any idea what's going on? My iphone 3gs and 4 connected 100%, uploaded their Contacts, and never gave me a moment's problem, so I know the BT in the car is working OK.
Help!
Click to expand...
Click to collapse
Just because it worked with your iPhones doesn't mean the BT module isn't faulty...it might just have trouble accepting connections from certain things. Not to say the phone's *not* at fault, but don't assume it's the phone when there's a chance it could still be the phone.
I have a kenwood bluetooth module in my receiver that worked perfectly with every phone until I got an iPhone 4 (even previous iPhones worked fine). It wouldn't connect and finally when I got it to work the sound quality was horrendous (most people couldn't understand a single word). I thought the phone was obviously bad until I contacted Kenwood and they sent me a beta driver for the bluetooth module in the receiver. Updated the driver and it worked perfectly.
I agree- the BT module *could* be fault, but given that it works with all iphones and my BB Bold, I'd have to say that it's more than likely something to do with the way the Atrix/Android handles the connection.
Others are now chiming in on the Motorola Forum about this issue- including someone who has a newer BMW BT module than I have - he's also got the same issue. There's also a Dodge owner earlier in this thread that's got the same problem.
On a whim, I copied 20 contacts to the SIM, thinking that might be the problem.
Same results.
i also had bt pairing problems with my ford sync, and it seems to be android related as it also happened with my n1.
couple things to try that should help: disable wireless and make sure you aren't using the power widget on one of your home screens. also, i used autostarts to unbind the media button pressed event, and between those three things, the bt works fine...
Tried an experiement-- copied some contacts to the SIM.
Same issue- phone connects/disconnect/connects/disconnects for good.
Exwoodchuck said:
I agree- the BT module *could* be fault, but given that it works with all iphones and my BB Bold, I'd have to say that it's more than likely something to do with the way the Atrix/Android handles the connection.
Others are now chiming in on the Motorola Forum about this issue- including someone who has a newer BMW BT module than I have - he's also got the same issue. There's also a Dodge owner earlier in this thread that's got the same problem.
Click to expand...
Click to collapse
Apparently you read my post...but didn't understand it completely.
My previous receiver worked *PERFECTLY* with all phones but the iPhone 4. I used about 20+ phones with it without a single problem...but the iPhone 4 wouldn't connect 3/4 of the time, and when it did it didn't transfer any contacts and when I made a call the sound quality was *very* bad. I obviously assumed it was the iPhone 4 until I tried another one with it...turned out it *WAS* the receiver having an older firmware that wasn't compatible with the iPhone 4.
The reason a lot of Audis and BMWs aren't working with a few Android phones (the Atrix being one of them) isn't because Android is designed poorly...it's because the firmware in the receivers doesn't handle the Android setup well. The reason most people can connect but can't get contacts is because the way BMW/Audis poll for Contact lists doesn't work with Android. The car manufacturers haven't spent the time required to realize this and put out a correction. You should be complaining to BMW or Audi about this (whichever type you own) and trying to get them to release an updated BT Stack for your receiver (they might say it's not possible but it is).
Thanks for the clarification.
I doubt that BMW is going to release a firmware upgrade for my BT module - its out of production, and it's already 'state of the art', circa 2006 when they stopped producing them. I've read of other issues with newer BMW and other cars still having issues with the Phonebook upload, which is where I think the problem lies. It doesn't seem to be isolated to older cars either- I've read of 2010 models having the same issue I've got, and not just from European makers.
Digging around, this is a common theme with Android and BT not playing nicely-- many other phone manufactures have released patches/updates to correct similar issues, and I'm hoping that with the Atrix being the 'biggest and baddest', that Motorola sees fit to do the same. I've got a $600 fully integrated factory BT system thats now useless, and I'd sure like to have it working again.
I sometimes forget that I've got another BT-enabled car to test on -- a 2010 Audi A3.
My Atrix paired with no issue, then popped up with a message in the Notification area about allowing access to the Contacts. Ahh-hah! When paired to my BMW, I never get that message. So... the BMW appears to be unable to complete the handshake for PBAP access, and when it fails, it drops.
After syncing with my BMW I do not get the PBAP confirmation.
I did not get the confirmation with my Inspire 4G either but that phone DID work just fine. Contacts and audio would work and never had a drop out when I had the phone.
So there is a way to "fix" this issue without updating the vehicles BT.
Tested with my car bluetooth with 2 calls for ~30 mins in all today morning. Worked fine. It stayed paired on all the time.
I know there are a variety of posts of many flavors in regards to OEM in car bluetooth handsfree systems. Some for unbranded i9100, some for the AT&T i777
For anyone out there with the knowledge: Is there anyway to find a task automater (like a macro) to lets say automatically activate the bluetooth button for the paired device, lets say 1 second after Bluetooth turns on. In connection with Auto Bluetooth app (like the ones which turns on when motion is detected) it could be automated. I would do it, except I don't know how to write program code.
I am thinking like "if bluetooth turned on, wait 1 second, trigger paired device input" . Because in that case it would connect (automatically) in most cases I though many many people posting around here.
Anybody any idea?
I am trying to connect my Galaxy S2 with they system in my 2011 Jaguar XJ. I never had a problem with my BlackBerrys. The BlackBerry autoconnects the moment I start the car and all functions work.
Absolutely not so with my S2. It seems that differnet car manufacturers differing systems which use BLuetooth differently. Some work, some don't .
Let me clearify the problem. Phone does NOT AUTOCONNECT and it drives me nuts. Before i just got in the car and never pulled the phone out of my pocket. Now I have to pull it out and manually connect.
I am posting as I may save some of you some time. I tried everything up and down the list. About every Bluetooth apps in the market place. Free or paid. Really pretty much all of them. Nothing worked. I upgraded to the (leaked) UCKJ1 and back to the original UCKH1. I rooted and unrooted.
To no avail. All I can do is use a shortcut widget to save me a few menues to navigate.
So for the ones with the same problem; you know all the things I tried. Don't waste your time.
It takes two devices to successfuly connect. If a connection doesn't happen, you can't blame just one device. My ISGS2 auto-connects to all of my devices (AV receiver, headset, PC, car, portable speaker, G-Tab) automatically every time. I get you're upset, but you can't single the phone out alone. As for cars, in the ISGS2 forum, non-iDrive (older) BMW's were the majority of the problem.
Same here. I have no problem auto connect to my BT devices. But when it comes to BT auto connections, problems are common. Both sides of the BT connection can be the cause.
Well depending on the year, make and model of the car with bluetooth. Really need more information. What Barry said is oh so true and usually anyone can tell you what their experience is. My experience with my daily driver's system *Alpine CDA 9887, Alpine KCE-BT400 made by parrot*, works flawlessly. The only time I ever had to manually connect was right after getting my sgs2 and even my captivate connected properly unless I was connected to my jawbone icon when I jumped in my truck.
HTH,
Charlie
Mine connects flawlessly in my 2010 Camaro SS.
Im in a 2011 Camry SE, and with stock ROM it connects automatically. With CM7.1, I just have to take it out of sleep, by turning on the screen, and it connects. Not a big deal.
Sent from my SGH-I777 using XDA App
Hi, Thanks to all for the responses. I completely agree that it takes two devices to do it right and I am fully keeping that in mind. I have 2 more cars I can try with. So I will check if it works with my wife's Lexus and with my Clarion system in another car I have.
It just is, that my BlackBerry (which I don't miss at all) simply did the job perfect. Obviously I can't tweak anything on the car side as that is next to impossible. There is no open source code and all is so proprietary.
So the only hope I have is to figure out a way to teach my SGSII.
Again thanks for the input. I do absolutely LOVE my Galaxy S2 (i777) therefore this is a simply irritating that I have to push buttons when I get in the car.
Hearing that it works for most of you is well, good for you and not so good for me.
Blaze9 said:
Im in a 2011 Camry SE, and with stock ROM it connects automatically. With CM7.1, I just have to take it out of sleep, by turning on the screen, and it connects. Not a big deal.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
dmnall said:
Well depending on the year, make and model of the car with bluetooth. Really need more information. What Barry said is oh so true and usually anyone can tell you what their experience is. My experience with my daily driver's system *Alpine CDA 9887, Alpine KCE-BT400 made by parrot*, works flawlessly. The only time I ever had to manually connect was right after getting my sgs2 and even my captivate connected properly unless I was connected to my jawbone icon when I jumped in my truck.
HTH,
Charlie
Click to expand...
Click to collapse
Well, I will experiment a bit more and I will share what I will find in case others have similar problems.
This reminds me of a blog post ages ago called "Bluetooth needs a dentist"
The state of Bluetooth compatibility is abysmal in general... What is exceptionally sad is that 4-5 years ago or so, one of the most relibale and compatible Bluetooth stacks around (BlueZ) got a bunch of nastygrams from the Bluetooth SIG regarding failure to run the "offficial" compatibility/interop tests.
The short summary: Bluetooth compatibility is an epic nightmare, on both sides of the coin (host and device).
Entropy512 said:
This reminds me of a blog post ages ago called "Bluetooth needs a dentist"
The state of Bluetooth compatibility is abysmal in general... What is exceptionally sad is that 4-5 years ago or so, one of the most relibale and compatible Bluetooth stacks around (BlueZ) got a bunch of nastygrams from the Bluetooth SIG regarding failure to run the "offficial" compatibility/interop tests.
The short summary: Bluetooth compatibility is an epic nightmare, on both sides of the coin (host and device).
Click to expand...
Click to collapse
Hello,
I have to fully agree with Entropy512. Bluetooth compatibility is a disaster. Especially after all the years around. Not sure who, what and where is deciding on BT specs, drafts and so forth.
I know that with car systems it is a hit and miss. But it doesn't have to be. We all know that. I was digging on my good old Jaguar forum. What I found confirms exactly what we are saying.
Earlier Samsung Androids barely could hold a connection on Jaguars systems. Just with later versions and Gingerbread that was resolved. And none of the Samsungs autoconnect to any Jaguar system. And that is the same for Audi, Merceds and Subaru and probably some others. According to the Jag forum Samsung knows about this and worked on it.
But here is the main problem. On my wife's Lexus and on my Clarion head unit in my van it works like a charm. Automatically connects without a hitch. I understand Samsung can fix that but than it may not work on other cars. But how come BlackBerry was able to do what the Samsung unit can't???
And yes, some features like phonebook, direct dial and so forth are totally hit and miss. How do car unit manufacturers test? With what? Just one phone from 3 years ago? Same with the phone manufacturers. Is anybody talking? Seriously, why can't car head units manufacturers and phone manufacturers not figure out how to get on the same page? Car BT is becoming a standard equipment. So do BT enabled phones, no matter smart phones or what have you. There are not that many head unit manufacturers. So they can't agree on a standard which then can be used by the devolpers for a decent BT stack for phones? Completely ridiculous. Can make phones talk to you like the Apple Siri but can't get a bluetooth connection.
OK, I got that off my chest. Now I will try to get to work. All I can do is working on the i777 side, because there is no acces to anything on the Jaguar side.
Funny thing is, my phone is always stating phonebook request when I get in the car. Eventhoug I turned phone book off in the car. So the phone "hears" the car. Just without hitting the profile for the car it won't connect.
Auto connect to my Mazda 6 no issues. Same with all my other phones.
Sent from my SAMSUNG-SGH-I777 using xda premium
cpcrazyfly said:
Auto connect to my Mazda 6 no issues. Same with all my other phones.
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
Do you have problems with the Mazda taking too long to switch from "Music" mode to "Headset" mode, thus the vlingo voice prompt timing out? My mazda has that issue and it makes vlingo in the car pretty much useless.
I don't typically use voice commands but ill try. It has no issues taking and making calls then going right back to google music streaming.
Sent from my SAMSUNG-SGH-I777 using xda premium
I am also experiencing sporadic problems with my SGS2 and 2011 VW Golf using BT. About 75% of the time, it auto-connects fine when I start up the car. The car lets me know it linked and I can make/receive calls through the car's BT system fine. Address book loads as well (though does require a secondary authorization on the phone the very first time you use it).
However, every once in a while it either can't "find" the phone, or goes into a continuing looping state of "paired/not-paired". Generally when I actually want to use it! When it can't find the phone, manually searching for it (on the car's system) usually rectifies it temporarily, but it may go to unpaired a few minutes later. And on occasion, it simply can't find it at all. When I reboot the phone, or disable/re-enable BT on the phone itself, this problem usually goes away. This makes me think it's more of an issue with the phone then the car.
I too came from a BlackBerry torch and never once had a single pairing problem with my car.
When paired, media streaming generally works well, but occasionally I have to stop/restart it a couple times in order for the car to 'see' the media stream and allow me to chose it as the input.
The problem that I have is that the sgs2 will not report signal level to the car, so the car always shows full signal, even if i have no signal.
And it doesn't connect to the car unless the phone is in the car when the car starts. If bluetooth is turned off, or if I leave the car and go out of range, I will have to open the settings and force a connection.
Problem Solved, Autoconnect now working
Problem solved, read on:
This seems to apply to a variety of other vehicles, namely Jaguar, Mercedes, Audi, some BMW, Nissan and Subaru.
You can get your phone bluetooth auto connect to your vehicle by trying the following:
Attention, I believe this works for rooted phones only.
Get a app such as Titanium Backup Pro or MyToolbox.
under System Apps freeze "Bluetooth Share".
Now my phone automatically connects to my Jaguar XJ and all features seem to work. Having gotten around to check the phonebook yet. But all recent number log show and all seems to work.
Attention: I believe that may only work for rooted phones.
metalco said:
Problem solved, read on:
This seems to apply to a variety of other vehicles, namely Jaguar, Mercedes, Audi, some BMW, Nissan and Subaru.
You can get your phone bluetooth auto connect to your vehicle by trying the following:
Attention, I believe this works for rooted phones only.
Get a app such as Titanium Backup Pro or MyToolbox.
under System Apps freeze "Bluetooth Share".
Now my phone automatically connects to my Jaguar XJ and all features seem to work. Having gotten around to check the phonebook yet. But all recent number log show and all seems to work.
Attention: I believe that may only work for rooted phones.
Click to expand...
Click to collapse
I'm going to try this...
I've been having trouble with it automatically connecting to my 2011 WRX. My iPhone 4 always connected immediately, no problem. But the GS2 has yet to automatically connect, ever. It is paired fine and if I go into the Bluetooth settings, it is paired OK and I can manually tell it to connect. I've tried deleting the connection both from my head unit and the phone and recreating everything multiple times. Still no luck.
I'll try this and report back.
Bluetooth is def one of those technologies that could be enormously awesome but often has so much "fussiness" with it (due to incompatibilities or quirky behavior between varying BT devices) that it can easily become a right-royal PITA, IMO.
I've had quite a few Android phones over the years, now, and tried running both stock OS and many different ROMs on them with one of the expected primary functions of my phone to be as my main music player, including streaming music via BT/A2DP to my car stereo and this one function has ALWAYS proven to be the most frustrating experience. So yeah, I'll fully agree that whomever is "calling the shots" with setting up guidelines and specifications for BT and BT-based devices needs to get themselves an iron fist and put an end to this crap of inconsistent behavior and general flakiness.
When I got my AT&T SGS2 I was shocked to see that Samsung had done something to enable their stock music app to be able to transmit song metadata via BT. Android thus far has only supported AVRCP 1.0 (AFAIK) while you need AVRCP 1.3 (or higher) to be able to have metadata transmit over BT. At first I was ecstatic that FINALLY I could see my song info from my phone displayed on my car stereo while connected via BT. But then I found out that with the SGS2 and the stock music app my car stereo could no longer successfully send play/pause/forward/reverse commands to my phone! D'oh!!!
So then I went back to Poweramp (what I had been using for my primary music app on my previous phone; a Nexus S) and of course it wouldn't display the song metadata. But the big shocker was that it also couldn't recognize control commands issues from my car stereo! Not cool!
I did much tinkering and research and finally found that the music app PlayerPro would successfully work with my head unit (but still no metadata, of course) and so that's where I'm at.
Ridiculous, IMO. Nobody should have to endure such frustrating behavior with BT devices. I really wish somebody could straighten this kind of mess out in regards to Bluetooth and get things to "just work".
No luck for me. Freezing the Bluetooth Share did not fix my auto-connect problem.
ack154 said:
No luck for me. Freezing the Bluetooth Share did not fix my auto-connect problem.
Click to expand...
Click to collapse
OK, you can try one more thing;
Freeze all of those files: BluetoothPBAP, BluetoothShare and BluetoothAvrcp. If you have any other entries you can try freezing them, too. Just everything EXCEPT anything with a name like Brcm or BrcmBluetoothServices.
Just try it. And MAKE SURE to wipe cache after freezing, or better reboot. Also you want to make check they are in a "frozen" state after rebooting. I used "MyToolbox" and it worked perfect.
I haven't checked if I can still stream music, but I never use that anyways. I froze all of those and started unfreezing one by one. The experiment showed that in my case I only had to freeze the BluetoothShare. You may have to freeze the others, too.
Let me know how ot works. I am curious now.
hello, I am running the current public release at the time of this post(v1.1). I have a Jabra SP700 bluetooth FM speaker for my car. I am uncertain if this is a fault of the rom or the hardware of my bluetooth speaker. I am leaning more towards the bluetooth but I figured I would ask the community.
I play music through this to my car stereo. Frequently the bluetooth drops the audio connection at random times. The phone and speaker say the X2 is connected, but the audio ceases. Within a minute the sound will play through the phone speaker not the bluetooth. Then the bluetooth will say "disconnected" and begin searching to reconnect. My X2 will state the bluetooth is still connected. In order for me to get the phone connected, I need to power off the bluetooth then disable and reenable bluetooth on the X2.
I believe this has happened with previous versions, ive been using eclipse since it started. Although I cannot remember if it works correctly with the bluetooth bone stock.
I am leaning towards the bluetooth since the bluetooth is about 2 years old now...but I was wondering if anybody used a similar bluetooth piece and experienced similar issues. Thanks!!
Ok guys. Let's try this thread over.
Anyone want to help this gentleman? We're not going to argue or derail. If you can't help this guy, don't respond.
OP, search while you wait for an answer.
There is a known issue with the bluetooth function on 1.1
I had heard people saying that with the newest ((1.2rc3)) that the issue had been fixed.
I don't use bluetooth do I cannot confirm but that might be the issue
I didn't think that older BTdevices would become "obsolete" . I thought any newer phones that support bluetooth would encompass all older BTdevices not exclude them. I can see an older phone not connecting to newer bluetooth but not older bluetooth not connect to newer phone.
Nitro tweeted that the new eclipse final should be out tomorrow. Hr has known about the bluetooth bug for a while so I am sure it was a priority fix.
It is possible tho that there is something faulty with your bluetooth device. Have you tried contacting the manufacturers of it to see if that is a known problem with that device? They may be able to help troubleshoot it also.
Thanks ash. As usual you are helpful and nice the speaker is way out of warranty. Ive owned it for 2 years. The battery os startong to go too. I never doubted the compatibility of the speaker...just the performance. It has acted odd in the past. I did not notice an issue initially with the X2. Since it started acting up i was pretty sure it was the bluetooth just showing its age and starting to malfunction. Well at least i do not have to buy anothee speaker just yet
Sent from my DROID X2 using XDA App
Thanks
Even if it is out pf warranty they may be the type of company who is willing to repair or help with problems just to keep your loyalty to their products. Who knows you may be able to talk them into a rebate on new product or a coupon or something . Might be worth a shot. Just be site you tell them you promote the product to people you know and in forums you post in. I have been looking for either a wired or bluetooth speaker for my x2 and not sure what to go with. . I saw one in the VZW store I
that looked nice but $199 is a bit steep for a speaker for me lol
And it seems like any other speaker I find (wired or bluetooth) is labeled do I ipod /iphone etc... im thinking the wired would work okay((headphones jack type)) but am not willing to shell out the 50$ that ill only get back in store credit for opened electronic in a store I barely shop at lol. Im sure ill find something sometime and ur post introduced me to a different one to look into. Curious if new eclipse final will fix your problems. Good luck.
Its odd that it will work for a while and then cut off. Wonder if it may be the "receiver " in the device not working correctly. Maybe something wiggled loose. Might be worth taking it apart((if possible) and checking where things connect to each other it giving it a wipe down and clean it up. Maybe dirt is interfering with something inside due to its age.
Or IT'S ALL YOUR FAULT. YOU USED IT TO MUCH FOR WHAT IT WAS DESIGNED FOR AND IT IS DEAD NOW ...lol j/k...im sure something can be done to fix it if it isn't eclipse that is causing the problem. ..its just a matter of is it worth the time to fix or buy a new one..
It is all my fault!!!! Haha. Well that is an idea....maybe i will try. If i can make a suggestion, the droid roadster is pretty cool. Works well and is user friendly! I tested it for a while and liked it.
Sent from my DROID X2 using XDA App
I have a bluetooth earpiece that I use with my old Razr and it works fine with my DX2 so I don't think age has much to do with compatibility. Wear and tear probably plays more of a factor.
I do pair my DX2 with my Touchpad (WebOS, not when booted in CM7) and I can make calls great on the TP but because the default bluetooth.dun is missing from Eclipse I can send sms with my TP. Not an issue but something to consider if you are shopping and comparing specs to see if you nifty new devices will work with your phone. The devs pull out the blur and bloat because that is what we want but it can change how devices talk to each other.
I have a set of moto rokr hd headphones that I use all the time and I have had this exact same issue with eclipse. The phone still says it has a connection but no audio is playing through my headphones. The only way to correct the issue is to turn off the headphones and turn off bluetooth on the phone and restart them both. It will happen completely at random times. Sometimes I will use them for a couple hours before it hours, but sometimes only 15 min. Its def eclipse, I don't think moto headphones have a compatability issue with a moto phone
1.) Has anyone with the "Bluetooth Problem" rooted their phone and found that it fixed the BT issue.
2.) Did the first OTA cause the BT problem on the Amaze.
I bought my HTC Amaze in January 2012. I didn't have my access to my Plantronic headsets at the time. Before I was able to test the Bluetooth on my Amaze, the first OTA came out. I did the update and all was good. Then my headsets came in and I tried them all (3 total -Voyager Pro HD and Explorer.) The range with the Voyager and Explorer was about 1-2 Ft. I basically had to hold the handset next to the Bluetooth headset. The Explorer had a better reception, but both headsets were distorted with the sound of static and would drop connection with a mere turn of the head. After ICS I now get about 8-10 Ft. with lots of static at anything over 3 feet.
My HD2 running CyanogenMod 7 still gets 30 ft. line of sight. And 15-20 through doors and walls.... I guess I'm spoiled.
Thanks for any answers guys.
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Maybe there's an issue with your BT antenna? It could be something as similar to the wifi fix (where you add a small piece of aluminum foil to the back of your case where the antenna is).
I have spent alot of time on the T-mo forum in the last few months. For the most part there seems to be a BT issue with at least "some" of the phones. When I updated to ICS the BT did without question get better. Not great.. but marked improvement. The fact that ICS made it better, along with a few posters stating that their phones BT worked fine prior to the first OTA but went bad after the update, led me to believe that the problem may be software related ...ergo the first OTA. The other people that are having this problem also saw a difference when they too updated to ICS.
One update "allegedly" messed up BT on the phone (some anyway) and another made the BT problem better. Strange....
hasoon2000 and kered424 are you guys running stock ROMs? I haven't rooted a custom ROM up to this point because I wasn't sure if it would actually fix the problem. That is why I was seeking a confimation or denial that rooting the phone would fix the problem. My dilemma is returning the phone. I have not unlocked the phone...but I did do the "Leaked ICS." But that is off topic...
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
kered424 said:
I've been running stock for the longest time, but recently switched to NRG's stock-look rom. I've never had an issue with bluetooth (gb, ics, or nrg). When I was running stock, I was rooted, but I doubt rooting will fix your problem.
Click to expand...
Click to collapse
Thanks for you reply kered424.
I guess what I am really looking for is someone that actually recognized they had the problem and notice a change when rooting a custom ROM onto the phone. I may not find that person here...most people here root without need. I'm all about rooting...I have an HD2 that I still root (my digitizer just went out.) I just do not want to go through the hassle of rooting only to find out that it was the hardware and not the software. I would not even post about this and root the phone...if it were not for the marked impovement when I updated to "Leaked ICS."
It leaves me going: "Hardware?..software?...hardware?...software?"
From your description, it sounds like hardware. Have you tried the aluminum foil trick? That's the only thing I can think of.
Solution to Amaze 4G Bluetooth Issues. Possibly.
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
Still Still No Adequate Solution to Amaze 4G Bluetooth Issues.
badgerdave said:
You are right...I could not find anything showing a diagram or pic of where the antenna is/are located. Hopefully somone will provide you with something. Have tried emailing HTC and outright asking for a diagram?
Click to expand...
Click to collapse
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
BlackeyedBandit: I once read that the very first OTA is what messed up the Bluetooth on the Amaze. Unfortunately I am unable to comfirm this, or deny it. When I purchased my Amaze in Janaury 2012 my BT devices were being shipped to me. Before these devices got to me, my Amaze prompted me to do an update. I did it. When my BT devices arrived none of them had a range of more than 1-3 Ft. without static and/or terminated BT connection. When the ICS update came out the range increased to about 8-10 Ft.
I want to revert back the ROM that was first released to see if in fact it is better. But....I don't want to go through all those changes to find out it doesn't work any better. My phone is still completely stock...because I want to be able to return it soon. I love the phone and only want the BT to work in a manner that I have become accustomed to with HTC products. And to get the video stereo sound quality fixed too.
This is my second HTC device. The first was the HD2. It was a nightmare with WinMo 6.5 on it. I returned that thing 5 times and never got one that worked right. I eventually...with the help of xda members and others, learned the art of rooting. Once I got that down and rooted Andriod onto it, I was in love. I thought that even with all it's faults, HTC made an awesome device. I just needed to figure out how to "tune it up."
So I believed that the Amaze would be super awesome and looked forward to getting it. I feel let down because BT is a must for me. I'm not sure I will buy another HTC product either. This is the second time I have been burned.
BlackeyedBandit said:
Me too. I asked them for a service manual as I am a PC technician to let me figure it out but just like Toshiba laptops. Not a chance.
Update: Unfortunately my Bluetooth antenna mod/fix seems to only have solved the connectivity issue indoors as my headset still cuts out every few seconds outside and drops calls like crazy. I feel as though we've all been suckered by HTC as they will neither let us exchange for a smartphone that works properly or provide a solution to those of us who purchased this factory defective off the shelf phone.
I will still continue my efforts to find a way to enhance the antenna but I will probably never buy anything from HTC again seeing as how they've chosen to not deal with and dodge this widespread problem. T-mobile is no longer selling the Amaze that was the Sales person's response when I told them they were selling a defective product today at one of their stores, However, on the T-mobile website they are giving them away for free with new contracts. Those poor unfortunates that take them up on that offer who know no better.
I am going to demand a refund from either T-mobile or HTC but I doubt I will get one.
The salesman at T-mobile said "Nothing beats a wired headset." jerk!
Again I am sorry for jumping the gun but I was certain I had made a significant breakthrough in solving the Bluetooth problem on the Amaze.
Click to expand...
Click to collapse
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
notperse said:
This Piece of S was offered as a replacement to FIVE HTC Sensations, followed by a Samsung Galaxy S Blaze?, followed by THREE HTC Amazes...all in 11 months. WiFi doesn't work right. Bluetooth is practically useless on the Amaze, and worse when combined with WiFi. I've used it with three different high-end Bluetooth devices (Plantronics (best-I forget the name), Samsung's best, and the Motorola Sliver Elite. All work find with friends' phones when I've tried to troubleshoot. I've used several WiFi routers, access points, repeaters,etc...still the signals fluctuate, the sound warbles, and the calls get disconnected.
I have LITERALLY spent 49:25 hours on the phone with T-Mobile, and 16:30 hours on the phone with HTC. There has been no resolution. T-Mobile...offered...me...the option (get this...) to pay MORE money and get a different phone. I've spent countless hours on websites (I'm a software developer and systems integrator, so I know my way around) and was unable to get anything working. I've had to hold the phone...in my hand...about 1-2ft from my Bluetooth devices to get them to work at all.
The device is FULL of known issues. Bluetooth & WiFi being the only ones about which I care.
I've also gone back to the T-Mobile store twice (which dialing 611 or the 800-number tells you not to do...but after the HTC Sensation, and then the HTC Amaze issues, I had to choice but to go to the face-to-face supervisors and beg for help.) The first supervisor left T-Mobile and the second one "Jodi" was INCREDIBLY rude to me.
T-Mobile's 611/800-number "customer service" has three times not documented anything - and I was on the phone for 1:30 hours/each.
Click to expand...
Click to collapse
Bro I think you have been extremely unlucky with the amaze. Although it does have some issues (capacitative light bleed, camera flash bleed, lower battery life than one would like, and slow development) most of these have been overcome to a great extent. If you are using a case you will have WiFi issues and possibly Bluetooth (I had WiFi issues with cover on, no BT issues) but that's fixible with a silver cigarette foil (or gold as well Iguess) placed in the battery back cover right beside the camera hole in the cover.
BlackeyedBandit said:
I've been reading XDA forums and modding my phones for years and now and at last I may actually have a contribution to make.
Alright all of you suffering with this enormous Bluetooth problem on the Amaze 4G that HTC pretty much refuses to acknowledge or address.
I too purchased an Amaze a couple months ago and was quite satisfied with its overall performance. That is until I received a Bluetooth ipad game controller and set of S9-HD Bluetooth headphones for my birthday. Then the nightmare began. Constant signal loss. If I were trying to text someone the sound would cut out on every key press. The ipad game controller would lose connection before getting through level one on Metal Slug Three played with NEO.emu (an awesome app by the way for its support of that controller). The in call signal quality was terrible and this was after trying multiple headsets. I read about a foil trick to correct this problem but never once found a tutorial on how to do it and the Bluetooth antenna prongs often spoke of were never actually pointed out anywhere. I looked all night for a diagram that would indicate which ones they are. I am guessing the they are the ones on the upper left. Not the top two immediately above the camera. If I am mistaken please make haste to correct me as it will determine the solution I detail. I had to guess I could find no real confirmation of this as they are both top left. Would someone send me a picture of the actual phone with the backing taken off and indicate which leads are to the Bluetooth antenna? As soon as I can confirm this I will post the fix.
I design and repair custom PC's in my free time for the elderly, disabled, and low income and I used that background to do a little experimenting the result was two more 4G bars in my basement and the the headset cutting out once during a three paragraph text. In game sounds were flawless and in call performance was perfect without a single cut out of signal.
As soon as someone discloses where those actual Bluetooth prongs are. I will post the how to and materials needed to perform this very successful solution. Not a 100% but 90% which is certainly better than the 20% us Amaze users have been putting up with.
I'd also like to thank all the developers for all knowledge and effort that goes into making all the cool enhancements and themes I had on my old HD2 and am now leaning how to apply on the Amaze. Hours of fun. You are all very much appreciated and Keep people like me learning new things.
Oh, I am running NRG's latest Aug 6, 2012 ICS Themed ROM release for the Amaze, Stock Kernel, 4EXT (the best!) S-ON, (Bricked my first Amaze with S-OFF).
As soon as I get confirmation of the antenna location and do a little more testing I will post the fix right here (next week or two). I don't want to look like an idiot or give misinformation if I have it incorrect or cause any damagage to anyones phone.
Click to expand...
Click to collapse
I too have the bluetooth connectivity issues. The only reference I could find to an "aluminum foil fix" was actually wifi antenna related. However, the thumbnail image is in this post by darll, 15th November 2011: (Wifi signal affected by phone case) in the Amaze 4g General forum.
BT MAC addresss
hasoon2000 said:
Nope. Mine works. I have a jawbone prime. No issues with connection.
Sent From My HTC Amaze 4G Via Someone's Room
Click to expand...
Click to collapse
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
chevycowboyusa said:
Where does the bluetooth get it's MAC address from? (the one under settings/ about/hardware info/ bluetooth address)
Click to expand...
Click to collapse
I think it is on the chip, but I'm not certain. It could also be programmed into the part of the phone firmware that is not touched when flashing.
I also want to report that I've had no issues with BT connectivity, and I have connected with about 8 headsets / handsfree over the past year.
My Amaze can get into a problem state with the BT, where the phone does not acknowledge a change in BT from off to on or vice versa. When this happens the phone starts to overheat, and I have to power completely down, and then power on again - at which point it will show the actual BT status. I've been on NRG almost from the start, so I don't know if this is a hardware issue or a ROM issue. I haven't had it happen in a while - I'm now more careful about turning on the BT (the problem seemed to happen when I was accidentally hitting the switch twice). Since I know how to avoid it, I haven't pursued any fixes.
Have you tried replacing the back cover? That seems like the most probable fix.
bluetooth
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
BT
artur-x said:
bluetooth problems?!
Hi, I have a rooted and s-off amaze with nightmare rom. everything is working but bluetooth. I can turn it on and switch to visibility but the problem is it can not find any devices and also it can not be found by others. I flashed some kernels but it did not work. please if u know a kernel that fixes bluetooth i can try it. thanks
Click to expand...
Click to collapse
This have anything to do with it?:
http://forum.xda-developers.com/showpost.php?p=54112028&postcount=6