So I owned my BA since 2005 and tried all ROM/radio/BT upgrades and now am at xplode's ROM and 1.15 radio and 1.39 BT, still can't keep BA farther than a foot away from my headset. Static just kills any conversation on the street. I come to think it's the hardware, and as such, it's unfixable. This is so far the reason that I don't use my BA as a phone anymore -- I'd rather keep it in sync with my Mac, and also sync up my Nokia, via Missing Sync. If I happen to have a contact I need on the Nokia, I can beam it from the BA via BT. Of course, SMS is the main reason to prefer BA, but I'd rather have a solid headset connectivity. I also didn't like it under WM2003SE when the phone had to be rebooted during a call. Overall, I'm afraid, we'll just have to move on to WM Phones with more solid BT headset connections, or -- better yet -- to iPhone.
braver said:
So I owned my BA since 2005 and tried all ROM/radio/BT upgrades and now am at xplode's ROM and 1.15 radio and 1.39 BT, still can't keep BA farther than a foot away from my headset. Static just kills any conversation on the street. I come to think it's the hardware, and as such, it's unfixable. This is so far the reason that I don't use my BA as a phone anymore -- I'd rather keep it in sync with my Mac, and also sync up my Nokia, via Missing Sync. If I happen to have a contact I need on the Nokia, I can beam it from the BA via BT. Of course, SMS is the main reason to prefer BA, but I'd rather have a solid headset connectivity. I also didn't like it under WM2003SE when the phone had to be rebooted during a call. Overall, I'm afraid, we'll just have to move on to WM Phones with more solid BT headset connections, or -- better yet -- to iPhone.
Click to expand...
Click to collapse
I can some it up in one word.
BTONBASUCKSABIGONEANDTHEREISNOFIX.
Related
It is from an HP 6315 from 3/31/05
http://h18007.www1.hp.com/support/files/HandheldiPAQ/us/download/22539.html
I would love to see if we could get this stack and the settings on our XDAII and other HTC devices,,, THAT would be cool.
Bluetooth build 1.0.0.3701:
Corrects inaccurate display of headset icon when a call is in progress.
Adds a check to determine if Bluetooth stack is initialized before accepting messages from phone.
Adds a user interface (UI) change to enable a connected headset to automatically disconnect before attempting to connect to a different headset when the user chooses to connect to a second headset.
Corrects check for invalid device name.
Corrects issue where handheld could not reconnect to remote device after a page timeout.
Corrects Object push profile update so it sends all files.
Updates FTP connection wizard to correct service discovery issue.
Corrects issue with call waiting for incoming call handling while dialing out.
Corrects issue with headset connection icon so it is correctly displayed after power cycling.
Corrects audio to make it compatible with an in-car solution.
Corrects audio issue where the right channel for a headset was unavailable for playing audio and during calls.
Corrects issue where the LED and network status were not properly synchronized.
Corrects issue where the user could not send multimedia messaging (MMS) message.
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
2. This is not a HTC device, so I doubt the tools developed here will work on it.
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Well, even though I don't want to stop progress because I would like to have the ROM taken apart for my own personal reasons, the 6315 was actually made by Compal. Bad move on the part of HP in my opinion. However, the bluetooth stack that was taken from an iMate JAM worked on the 6315 and that is how most survived until the update was released. So it very well could work on the HTC's. On a side note, if someone could point me in the right direction, I will take the ROM apart, just don't know where to start.
mamaich said:
HappyGoat said:
2. This is not a HTC device, so I doubt the tools developed here will work on it.
Click to expand...
Click to collapse
This is an HTC device. All HPs are designed by HTC.
Click to expand...
Click to collapse
Oops....my bad....excuses!
no htc dont make ALL hp's pda's the H5400's was oem'd from LG
and even if the ipaq in question is made by HTC then that dont garentee that the xda tools work as they are not made by HTC
I can tell you now that the XDA tools do not work on that ROM as it stands. However, looking through the HEX, it is laid out a little differently than the XDA ROM's but have some of the same portions, just in different locations. Now if I knew more about what I was looking at, I could take it apart for you. The 6315 uses Widcomm BT and like I stated before the BT drivers ripped from a JAM worked great on the 6315 so I have a feeling the 6315 drivers will work on the XDA's.
I can also tell anyone looking at it that in the first header of the ROM the letters are shifted 13 characters. So when you see RAT it equals ENG and so on. It looks like they don't do that for very long though.
BT
HappyGoat said:
Hmmmm....a few remarks, correct me if I am wrong:
1. There is already a BT version 1.0.0.3900 available
Click to expand...
Click to collapse
BT 3900 and 3500 do not support Hands Free Profile or even Headset Profile on my XDAII.. This is important so people can use Caller ID on a BT device and OR a Car Kit with the Hands Free Profile....
Switching stacks is a pain in the but...
Even so, the only OS that even slightly works with Hands Free on the Himalaya, is 2.20 translated but even that has bugs that makes it very frustrating. The 2005 did have a fully functional BT, even having separate serial ports for each BT device, (like GPS), but the other bugs and the limited memory left over from the useless and unerasable Extended ROM from the other OS made it no good..
With this new ROM, I may be tempted to buy the HP again.. When I first bought one, it was DAM slow and the BT SUCKED!!!
Maybe now it is usable.
I love my Himalaya and it's 128 of built in..
http://www.expansys.com/product.asp?code=PDA2&asource=IMATE
http://www.expansys-usa.com/product.asp?code=PDA2&asource=IMATE
I will just have to keep waiting for one of the above unless someone finds a fix for the BT Hands Free.
I have a BlueAngel / SX66 on Cingular. I have been through every ROM upgrade you can imagine, all with the hopes that SOME DAY the bluetooth will work properly. More specifically, I have a stick BMW and it's impossible for me to talk on this thing and drive at the same time, not to mention really unsafe, but I absolutely need to talk in the car because I'm on the move a lot. There is a bluetooth headset interface in the car that I know is pretty damn good because it works so beautifully with Motorola devices (specifically the somewhat ancient V600 I have). My SX66 can barely get through 3 seconds of being connected to it before it just goes haywire and drops the connection, locks up my stereo, etc. It's a disaster. So every time a new ROM comes out I sit for hours upgrading just hoping that maybe this time it will work. I've tried a Motorola HS810, HS850, a Logitech Mobile Freedom, a Jabra BT800, and an Ericsson HBH600. Not one of them can consistently hold a connection without it dropping here and there and me having to go to the Bluetooth manager and "reconnect". These are all reputable headsets that work flawlessly with other devices.
Conclusion: The MS bluetooth stack is pathetic.
Problem: I want my SX66 to work with JUST ONE bluetooth device flawlessly. It doesn't need to be the car necessarily, but that would be really sweet if it did. I have recently upgraded to WM5 in another feeble attempt, but alas WM5 doesn't appear to be compatible with GoodLink, the messaging sync software that I'm tied to that makes me use this god awful device (I won't use a Treo because the Palm UI is garbage and it has its own host of problems I've seen). I'm going to have to downgrade back to 1.40 to get GoodLink to work again because its pretty vital to me.
Question: Does anyone know how to get Bluetooth to work consistently with any headset, paired with an SX66? I seriously have sank like $400 just in headsets trying to get this piece of crap to work. If there are any stack upgrades, firmware flashes, etc. WHATEVER I'm willing to try anything. This is the only Windows based device available on the market that is compatible with GoodLink and has a qwerty keyboard that's easy to use.
FYI, the BA uses the Broadcom/Widcomm BT stack, unless you've upgraded it to WM5.
I have read every post about MS bluetooth stack vs widcomm etc....
I know someone can build a cab file that will uninstall the MS one and replace with the newest widcomm stack.
I LOVE my universal but I carry TWO phones with me because the universal's connection via bluetooth is not PERFECT for phone calls like the blackberry (oh i fking hate the blackberry for everything else).
I REALLY REALLY REALLY want to use only my Universal but the static on bluetooth KILLS me because I am on the phone 10 hours a day.
PLEASE please help me. Fish
This file fix Blue Tooth
Bluetooth stack
I would second Fish's comments about the Univerasl and the Bluetooth stack. I have bluetooth in my car and it is great WHEN it works. When it doesn't work it takes a lot of tinkering to get the car to recognize the phone again. I'm of course not sure if the issue is on the Universal side, but Bluetooth turns it self off, so there is some kind of problem. I have tried different radios, currently 1.13 (tried 1.14 as well, but went back). I'm very interested in finding a solution (not using two phones), can you please provide some detail on what the CAB file does to Bluetooth?
Thanks,
Sven
Logout. said:
This file fix Blue Tooth
Click to expand...
Click to collapse
What exactly does this file fix/change ?
I've just installed the WM6 crossbow helmi_c version
do I still need this file ?
This is a Stack changer to change from MS BT stack to Cambridge Silicon Radio BT stack. Originally developed for Dell AXIM (about what I've found). Seems to work fine there, but need to uninstall/reinstall after every soft-reset because of a volume lock bug.
http://www.pocketpcmag.com/blogs/index.php?blog=3&p=392&more=1
http://www.aximsite.com/boards/showthread.php?t=108767&page=1
UPDATE
Do not install this patch yet. It is over a year old.
Follow the development/information on Widcomm BT Stack instead. Following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
SO this is a different BT stack then the original MS and the widecomm ?
Daelyn said:
UPDATE
Do not install this patch yet. It is over a year old.
Follow the development/information on Widcomm BT Stack instead. Following links
http://forum.xda-developers.com/showthread.php?t=279236
http://forum.xda-developers.com/showthread.php?t=285419
http://forum.xda-developers.com/showthread.php?t=285696
http://forum.xda-developers.com/showthread.php?p=1073003
Click to expand...
Click to collapse
True
reading the posts in the forum he linked:
12-12-05, 09:57 PM
I'd rather go with the widecomm BT
I installed the Hermes Widcomm BT stack on my Universal. Sound is great, but the rest is troublesome. We need a developer to fix the code for us so it works on the UNiversal .
Check my thread in UNiversal/accessories. Or move that thread over here please!
Daelyn said:
http://forum.xda-developers.com/showthread.php?t=285419&page=20
Tried out BT Stack change for Hermes patch/program.
TEST RESULTS ON UNIVERSAL WITH WM6 (Midget aka Helmi unreleased)
Sound IS great. But other than that, this program does not work very well on my device. Of course this is designed for Hermes but I gave it a shot.
Issues:
1:
Screen flickers (only when this BT is turned on).
Flickers really bad and unable to use device.
Fix: set the device to standby (power button) and wake it up again. Flickering gone
2:
Once BT is deactivated for a few minutes I can't start it again.
Fix: No fix found yet. Only a Soft-reset and directly activate BT works.
3:
I can't use my GSM/UMTS connection anymore. Trying endlessly. Even after soft-reset's I can't connect. WiFi works fine though.
Fix: No fix found yet.
4:
Unable to uninstall this program. Tried several times. I get to the "Soft Reset Device Yes/Cancel". I soft reset, program still there and working.
5:
Hard-Reset, complete setup with WAP, MMS, MAIL etc.
Installed Widcomm BT Stack again.
Soft-reset:
Screen flickering (fix)
No 3G/UMTS connection avalible anymore. Even when BT stack is completly shut down.
We need a specific one for our Universal. Who's up to fixing this for us?
KEEPING this post updated.
EDIT 06: 18:40 @ 21/01/07
Click to expand...
Click to collapse
Quoted from my A2DP/AVRCP thread in accessories.
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
try this link
it may help
http://www.pocketpctweaks.com/pocketpc_tweaks/increase_bluetooth_volume
frz
Thanks for the info
I changed the channel in the registry of the device to channel 5 as suggested on that webpage. It was the same quality. I then tried a few other channels and the same results - connection quality still staticy.
Thank you very much for trying to help me though. Fish
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
I'm also worried with the same issue, because I've exactly the same problem. But I don't think only altering of BT stack should fix the problem. My understanding is, something is also to be done in radio (rom) side itself. Because I was using a different radio rom last year at about May or June and my BT headset worked perfect. But I can't remember now about what build that was, because later on I've updated my radio to few other releases.
Radio rom has NOTHING to do with the Bluetooth or Wifi - It's ONLY the firmware for the GSM chip.
xixfishxix said:
Even with the new WM6 roms - I have tried ALLLLLLLLLL of them the bluetooth phone quality sucks.
I am using the new Pdaviet 2.0.03 (something like that) and i have tried
THREE different headsets
Jabra BT250v
Jabra BT500
Jabra BT500v
All have the same crackly sound issue. But with my blackberry (ass phone, i HATE it) the sound is PERFECT.
I am soooooooooooooooooooooooooooooooooooooo tired of carrying two phones with me - i can not live without my memory (or i mean the universal, which i use as my personal assistant). But my clients can not live with the quality of the phone call connection. Now if I do not use my bluetooth and hold the GIANT universal up to my head (kinda like a military field radio) then the clarity of the call is great.
It is the Bluetooth stack i am 100% sure of it.
OMG Helmi_c let me have your widcomm stack PLEASE I will even pay you for it.
Click to expand...
Click to collapse
We know the MS BT stack is crappy. I found out today that Helmi_c is developing one. But, still, this thread should be more about how to resolve the BT stack change (or just shut it until our friend Helmi_c finishes his school stuff and gets back to being the ROM-N3rd in need of more RAM that we all love so much) than bringing up more issues about the MS BT stack.
Thanks.
guys,tried almost all roms on my universal,some of them works a few days,after 3 months i flashed with the good old official rom,better and stable than all
anyway,the only reason for this waste of time was this a2dp issue,being not able to listen music to my motorokr(tested with 2 laptops and 2 htc,working great)
so i think is just some kind of incompatibility motorokr-universal(yes,i try all the a2dp hacks/registry editing found here
I have a sx66 with build 3900 and a jawbone. Can anyone get this to consistantly work with the sx66? When it works, it works decently but after I charge it via a sync cable, go out of range of the phone or answer a phone call via the phone itself it will "kind of" lose connection.
The reason I said "kind of" because the phone still sees the jawbone. It won't use it. I have the icon on the screen indicating that it is connected but I can't get the sound to transfer to the headset nor will it let me answer a call via the headset. I would then go through a series of disconnects and syncing to get it going again. Sometimes I would ultimately have to take out the battery. Any help would be appreciated. Thanks.
I have a sx66 too. maybe you shall do one upgrade.
currently I am on helmís wm5 rom release and way better than 2003se this phone had.
also, what is your current rom?
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"