Related
I am struggling to use my SonyEricsson HBH 35 Headset with my Tmobile MDAIII. But after a while the BT Stack stops working and I have to turn BT on and off to be able to use the headset again. Tmobile Service Line told me that they are aware of the problem and they will post a fix for that but no time frame was giving. Therefore I was wondering whether the latest Imate PDA2k Rom was having the same BT problems. Which version of BT stack is on this rom? Is it possible to copy the necessary files onto the MDA III and make it work with the never version?
PDA2K has the same issues with the BT Stack. In fcat it is just awful.
Anonymous said:
PDA2K has the same issues with the BT Stack. In fcat it is just awful.
Click to expand...
Click to collapse
Hell, its worse than 'just awful'....
...The Bluetooth on the PDA2K is just downright unusable.....
...I am still holding my breath, praying to GOD they get a real fix out and not just a 'here ya go' patch with more problems in it......
BT version... MDA III new ROM
I would like to know which version of the BT you guys have = which is most current for MDA III. To verify this go to settings/connection/bluetooth an check in About .
I have heard some news that ROM 1.20 is being tested internally, and somebody promised me to provide it to me. I am really waiting.. as current one keeps turning on device every minute...
have a hcb-30 bluetooth carkit that worked great with my Qtek 2020, but i cannot seem to get it to work with my qtek 9090....it finds the qtek allright and pairs with it, but cannot connect....my bluetooth version is 1.0.0 build 2200...
hope they get a fix out soon...
Re: BT version... MDA III new ROM
lukasz said:
I would like to know which version of the BT you guys have = which is most current for MDA III. To verify this go to settings/connection/bluetooth an check in About .
I have heard some news that ROM 1.20 is being tested internally, and somebody promised me to provide it to me. I am really waiting.. as current one keeps turning on device every minute...
Click to expand...
Click to collapse
I'm running v1.0.0 Biuld 2200
Mine also likes to turn the unit on every minute or two and run the battery down VERY fast...........
onurd said:
I am struggling to use my SonyEricsson HBH 35 Headset with my Tmobile MDAIII. But after a while the BT Stack stops working and I have to turn BT on and off to be able to use the headset again. Tmobile Service Line told me that they are aware of the problem and they will post a fix for that but no time frame was giving. Therefore I was wondering whether the latest Imate PDA2k Rom was having the same BT problems. Which version of BT stack is on this rom? Is it possible to copy the necessary files onto the MDA III and make it work with the never version?
Click to expand...
Click to collapse
You may tried that DON'T PAIR the HBH35, Afterwards, use a Bluetooth connection wizard to add it. This may be OK to add HBH35.
I don't know how those incompetent idiots could release the blueangel with such a obvious bluetooth problem, HOW CAN THEY NOT see it! the error messeges pops up so frequently.
Go for it, version 1.5
http://forum.xda-developers.com/viewtopic.php?p=65548#65548
I couldnt get 1.5 to work on my pda2k, cant overwrite certain files... how did you do it?
I didn't do it as i don't have a BT headset yet. because of these treads I'm waiting before i get the headset, gps, and keyboard for bluetooth
I didn't do it as i don't have a BT headset yet. because of these treads I'm waiting before i get the headset, gps, and keyboard for bluetooth
you don't have it yet and you are telling other people to go for it! i dont think it works for the pda2k
Did you read or post first?????????????????
As you can see Guest and firebird say it worked to some degree for them on the PDA2K (MDAIII). Since I didn't have a BT headset to try myself I thought I would help you by pointing you to someone who had.
Read posts before blasting back.
*********************
Guest
Posted: Mon Nov 08, 2004 06:20
Subject: BlueTooth manually updated on PDA2k to 1.5.081
--------------------------------------------------------------------------------
http://forum.xda-developers.com/viewtopic.php?t=11729&highlight=widcomm
Since I didn't see in any thread about someone updating their PDA2k to the latest widcomm drivers... Just an FYI, I copied the files from the other thread onto my PDA2k. Seems to be working. Will test further to see if I'm still getting memory issues like before.
NOTE - I used Resco to copy the files over. There were several warnings that I was updating a file in ROM.. but I went ahead and did that anyway...figured I could hard reset the device if need be.
just a warning, the ROM files he was talking about overwriting, cannot be restored by doing a hard reset, it is permanent. if it messes up you will have to re-flash your pda with a new copy of the OS. that's what i had to do since i couldnt get it to work
Hi Guys,
Recent got an XDA IIi after being with the older XDA II for over 16 Months.
But I have recently run into problems with my BT Car kit :
Motorola Bluetooth Car Kit HFW-8000.
Basically the problem is that it does not always connect to the Car Kit and when it does it will only from time to time connect and let me have a handfree conversation.
I have also used the Broadcom Bluetooth Cab file here in order to extend what Bluetooth Profiles that can be used but seems not to have any great bearing to stablize the issue.
So I went down the Hard Reset Road but again still intermittent issues, I then upgraded the ROM to the New one on the O2 Website the v 1.11.169 ROM.
I also had similar issues with the XDA II but it was resolved by using the Pocket Bluetooth tools, which was great and never once after installing it did I have any issues with the Car Kit.
http://www.bluetooth.jazztel.es/
One of my questions is, is there a similar programme to to above Pocket Bluetooth tools for the XDA IIi as I have tried it with the XDA IIi but does not work.
Or does anyone know how you would revert to have the XDA II radio or is there a work around for it.
Thanks Guys
Woody
Hi Woody_XDA,
I have had my XDA2i for a couple of months now and recently got a O2 blue headset for it, I had simular problems with the headset disconnecting and having to manually connect every time I switched it on. After browsing this wonderfull forum I decided to do a corperate install and get rid of the O2 active interface, since then no problems at all. I now use Pugs modified ROM version 162 with radio 1.04 and have no stability problems at all with no twice weekly reset. Hope this helps you and many thanks to Pug for his ROM.
Mace
Ditto, I also use the custom firmware with 1.04 radio and bluetooth works a charm. It still eats battery like nothing else, but it works with no problems. Also like the fact that the XDA can cope with my GPS receiver and my handsfree kit simultaneously, that's handy for in the car.
Cheers Guys for the information, took it on board and works great, did a great deal of stress testing in order to confirm it and works excellent..Thanks to PUG again and guys thanks for the info much appreciated and this is by far a great forum
Mace - you mention some bluetooth issues being resolved since you applied the custom ROM... I posted in the Alpine Applications forum here the other day a list of issues with bluetooth that I was wondering had been addressed - so far no reply - are these the symptoms that were cured for you??
Hi Bewlay Brother sorry, I missed your other post on Bluetooth issues, my original problem was that every time I switched on my BT headset , which is a O2 Blue, I had to open the BT manager and make the connection, the phone would then occasionally lose the connection and sometimes whilst still showing a connection refuse to transfer the call. This was using the official 162 ROM with the O2 active UI. I have since installed Pugs 162 ROM with radio1.04 and done a corporate install and BT seems to work perfectly, switch on the headset, it connects, never loses pairing and transfers calls.
Hope this helps you, and thanks again to Pug,
Mace.
Mace - what you describe sounds similar - my problems were essentially the loss of pairing with my Motorola headset a lot of the times when the XDAIIi switched off its display and went into stand-by mode, also if I closed the boom bike on the headset (to temporarily turn off the headset) it would fail to re-pair when I next opened the boom mike... the other issue was that I had to make sure the phone keyboard was displayed on the XDA once I had paired up otherwise the last number redial function on the headset would not work - if I pressed the dial button on headset and the phone display was not on the screen it would simply open the phone display function but fail to then dial the number - really crap. Also reception was poor to headset even over relatively short distances from the XDA. IF these areas in particular could be cured by the upgrade then I am eager to do it - I must admit I have read that this upgrade has not been without problems for some people here so it is going to be a tough call.
Just a thought, but have you done a personal or corporate install as I think the main fix with Pugs ROM was the upgrade to radio 1.04, which I don’t think affects the BT, so a corporate install with your existing ROM may make a difference.
Did a corporate install when it was new out of the box...
whats the difference between the corporate and personal install?
Corporate doesn't install ANY of the branded O2 interface - so no gubbins, nothing to slow down the phone, you just get a bog standard Windows Mobile 2003 SE installation, aside from the O2 GPRS and SMS settings. Bosh.
hi
i've been reading the posts and i have the same problem where can i get hold of pug's ROM if it's possible cos this seems to get rid of the problem
And then today, headset will not automatically connect, needing Bluetooth manager to be opened to make the connection. AARRRGH!
BT car kit problems
I have the 1.04 Radio, but it still won't sync with my 2003 BMW 325xi bluetooh or with my 2005 Acura MDX bluetooth.
Help!
Unstable Bluetooth Signal Strength - Samsung WEP200 Bluetooth Headset
Hi, I just got a Samsung WEP200 Bluetooth Headset. It would pair with my O2 XDAIIi but I cannot hear any voice in both incoming and outgoing calls. When I check the BT Manager, it shows a totally unstable BT strength that varies from very strong to very weak. The same headset worked well with other BT phones. My ROM version is 1.11.00 WWE, Radio version 1.04.00.
Any help would be greatly appreciated.
Hello,
Just upgraded to WM6 using the official Palm upgrade (TREO750-2.23-RWE).
The Treo is unbranded and came with WM5, also an RWE ROM.
The most important issue I currently have is terrible bluetooth interaction with my car-kit. Pairing is OK, I can start or receive a call, but there is no sound. Before, with WM5 I had no issues.
Setup:
- Treo 750
- WM6 (TREO750-2.23-RWE)
- Pegeuot RD4 radio with integrated bluetooth
Any solution? Or should I downgrade to WM5? If so, how should I downgrade?
Your help is most welcome!
David
Odd... With both the Treo 750 running WM5, I had the same problem. Basically, the first 30-60 seconds of a call wouldn't sound on either the handset, or the speakers over the bluetooth connection. This was always for the first call after getting in the car. To get around it, I would get in, start up the car, and call my voicemail. Once I could hear the call on the speakers, usually 30 seconds later, I would hang up. I could then make and receive calls normally.
After upgrading to WM6, incoming calls would occasionally be very low volume. I would have to hang up and call the person back. This also happens with WM6 on my AT&T Tilt.
No fix for that one....
daupers said:
Hello,
Just upgraded to WM6 using the official Palm upgrade (TREO750-2.23-RWE).
The Treo is unbranded and came with WM5, also an RWE ROM.
The most important issue I currently have is terrible bluetooth interaction with my car-kit. Pairing is OK, I can start or receive a call, but there is no sound. Before, with WM5 I had no issues.
Setup:
- Treo 750
- WM6 (TREO750-2.23-RWE)
- Pegeuot RD4 radio with integrated bluetooth
Any solution? Or should I downgrade to WM5? If so, how should I downgrade?
Your help is most welcome!
David
Click to expand...
Click to collapse
daupers,
Just curious that this might be related. Can you post what radio version you ended up with after the upgrade to WM6?
Dropped the issue at Palm
Yesterday I sent an email to drop the issue at Palm, since I used the official upgrade on an official pristine Treo. I still have to receive an answer.
I'm wondering if I ever will receive an answer that will resolve my issue.
Did anybody else on this forum ever get help from Palm?
David
Im heaving simmilar problems with Treo 750 WM5 and Toyota original BT-HF. Repatedly the connection is established, but then lost (without warning) - and then you get no sound (or an odd "interferrence " sound). I switch the BT off, then on, connect it again and it (usually) works fine. I assume it has smthng to do with the BT firmware. No other solution so far.
Where can I find a download for the original RWE WM5 ROM?
Can anybody provide me with a link to an WM5 RWE ROM for the Treo 750 (Cheetah)?
Thanks
I did some searching and so far I discovered the following.
WM 5 supports bluetooth 1.2.
WM 6 supports bluetooth 2.0, which should be backwards compatible with 1.2.
The carkit supports 1.2, but I'm not sure if it supports 2.0.
It looks like a compatibility issue, caused by the upgrade.
Could this be the source of the problem?
D
The hardware in the 750 supports 1.2 only, WM6 is backwards compatible with 1.2. Any device that supports 2.0 will be backwards compatible with 1.2. I just upgraded to the AT&T official WM6 build and am still having the same problems as always with my Moto HF850, no voice command, only get one working connection before the bond fails and I get no audio. *sigh*
I have the same problems Treo 750V 2.18-VFE with WM6.
Car: Citroen C4 with integrated bluetooth radio.
My car connects fine to the Treo, however when I make a call or answer a call 9 out of 10 times I have no sound. Currently I have to use the wired headset.... While I have no sound the connection is intact and I cannot use the Treo itself without cancel bluotooth from the menu.
I can read the indexes of the phone, make calls by using car functionality but no sound. Also when I have sound most of the time it's after ten seconds.
Since yesterday I also have no ringer sound anymore. Palm Support gave me an update but it's not for my ROM version.
I'm affraid I have to ask Palm to swap the phone again. Currently this is number 3:-( within a few months
BT working after WM6 upgrade
Hi everybody, surprisingly, after upgrade to WM6, my BT connection with toyota original handsfree started to work, I haven´t had a single "lost connection" since. Why is that I don´t know... Just to let U know - More lucky than the others...
I Received my fourth Treo last week. I now have ringer sound again (for now).
However I still have the sound problems with using my carkit.
My car connects fine to the Treo, however when I make a call or answer a call 9 out of 10 times I have no sound.
I get the same problem with an Orange SPV M3100 (HTC TYTN) and by factory fitted bluetooth kit in my Citroen C4... It's fine using the latest Orange WM5 ROM, but upgrading to WM6 stops the car kit from working, (connects, but no sound). I asked my Citroen dealer and they advised it was a known issue with 'high end phones like Nokia running Symbian, etc'. They had no idea about when a fix might be available.
Delayed or Missing Sound
Install the sound fix. That's what is there for.
What sound fix? Can you post a link, or let me know where it is?
Support also advised me to install the sound fix.
However it only work for lower rom versions.
When you install WM6 You will have a higher rom version.
The sound fix should allready be in WM6.
I think I'll try to contact Citroen about this...
My previous phone HTC TyTN (Hermes) worked perfectly well with my car OEM Bluetooth HF (BMW X3 '05) using varios ROMs and Radios, starting from the original VM5 to many cooked VM6 editions which I tried.
Now I purchased a brand new HTC TyTN II (Kaiser), which seems to have serious problems with the car Bluetooth. It pairs ok, but immediately when the actual bluetooth communication starts, the phone always reboots itself.
I have made a log of the communication using JETware Hands-free Extension. In the attached log you can find a row with strange character causing immediate reboot to the phone. The problem is not caused by Jetware, because the phone behaves exactly the same without Jetware.
From another forum I have found out that this seems to be a common problem also with another phone model which is T-Mobile Dash (HTC S620).
http://www.jetwaremobile.com/forums/forums/thread/394.aspx
http://www.jetwaremobile.com/forums/forums/thread/282.aspx
Any ideas how to sort this out? Which component on Kaiser should I start flashing upgrade/downgrade?
--
Mika
Kaiser ROM 1.56.414.2 Radio 1.27.14.04 Protocol 22.45.88.07H
Update to my situation, tried so far:
- Flashed Sleuth's V3.0 with Radio 1.64.08.21. The problems persists, phone pairs ok with BMW HF, but reboots itself immediately when actually connected.
- Tried to install Widcomm Bluetooth Stack which is duscussed in this thread, but could not get it really work in my Kaiser. After solving low memory issue by changing bitrate to 115200 it started, but it was not able to find any bluetooth devices at all.
I just wonder if this could be a hardware issue not solveable by any software updates? What could be fundamentaly so different between Hermes and Kaiser bluetooth implementations, that one works fluently and the other keeps rebooting itself even with different roms and radios (WM6.0 and WM6.1)?
What might be going so badly wrong in a bluetooth conversation that Kaiser decides to reboot? The AT-commands conversations starts just fine, but ends to a long string with odd characters. (please see the attached log file in my previous post).
Anyone, any ideas, please? I have done so much searching on this subject lately that I probably can no longer see any trees in the wood.
--
Mika
ROM: 3.0 Sleuth WWE
Radio: 1.64.08.21
Protocol: 25.74.40.02H
Updated car software
Now I upgraded my car computer software to the newest version as adviced in the x5world site here, the problem persists.
Hello,
I wonder if somebody can help me get to the bottom of this.
Basically, I have a TyTN II (branded as a T-Mobile MDA Vario III). I also have a Parrot 3200+ LS Colour car hands free kit.
Initially, I had a TyTN (branded as a T-Mobile MDA Vario II) and this worked fine with the Parrot. Problems began when I upgraded it to Windows Mobile 6 after an update was released by T-Mobile. What would happen is as I started the engine and the Parrot connected to the phone, it would say I was in a call even though I wasn't. It could only be resolved by rebooting the phone.
When I got the TyTN II, the problem became more frequent to the point where it was just annoying to use.
Now, this is where it gets interesting. Parrot are blaming Microsoft for this problem and aparently the problem *may* or *may not* get fixed in 6.1 which is some time off yet. It is a Bluetooth Stack issue aparently but I am not sure I believe them on this nor their attitude to if it will actually get fixed.
I am wondering if anybody knows anything more about this or any fix for it.
Best Regards,
Craig Brass
craigbrass said:
I am wondering if anybody knows anything more about this or any fix for it.
Click to expand...
Click to collapse
Install one of the 6.1 ROMs here and see if it helps?
I have this with my TyTn II and parrot 3300. It also used to happen with my Orbit.
I noticed that it only does it when a data connection is active. If I press the red button on the Parrot it clears and all is good.
Not sure if yours is the same issue.
I have a Parrot 3100, and have loads of problems! It randomly crashes, it randomly decides to want to call random people, it randomly decides to route the call through the Tytn II rather than the Parrot, and it randomly works without a problem. I emailed Parrot and got this response:
--------------------------------------------------------------------------
The HTC TyTn II is still undergoing compatibility tests with our products, thus is not listed as being compatible at present. We are currently also working closely with HTC to improve compatibility and functionality with new PDA devices running Windows Mobile 6.
I would recommend dialing out from the Parrot as opposed to using your handset as from experience this works best.
I would also recommend updating the software on your Parrot, the latest version is 4.16. To update you will need a Bluetooth enabled PC (preferably a laptop) and our Parrot update tool software. http://www.parrot.com/usa/support/downloads
--------------------------------------------------------------------------
Just noticed tonight that a new version is available for download, (4.17) so I have upgraded the Parrot and will give it a try tomorrow.
Cheers
so, was the upgrade succesfull? did it solve ur issue?
I'm also having issues using my tytn ii with the parrot ck3100. (standard firmware in it)
No, it hasn't completely. It has solved most of the problems, but it now decides to (randomly) mute incoming calls, and route the audio through the handset instead. It also decided to route the TomTom audio via the parrot! I didn't think that was possible???
I'm having some of the same sorts of problems w/ the Parrot CK3100 and my Tilt. Of course, I just go it installed last nite, so I haven't had a ton of time to play with it. I DID, however, do a long road trip today and here's what I've found.
When initiating a call from the phone, there's about a 50/50 chance that it will go thru the handset or Parrot.
One time, the Parrot locked up to a point that I had to get off at an exit and restart the engine to reset it.
I had to re-pair the phone and Parrot once, because the lost one another.
I'm running the latest AT&T ROM on my phone and latest firmware on the CK3100. I never had ANY of these problems w/ my Nokia CK-7W, but it had a REALLY annoying echo on the other end when used w/ anything but a Nokia phone.
Dan
Today, things got even stranger. As of this morning, the kit would try to initiate a phantom call every time the car was started and it connected w/ the phone.
Then, it was muting the radio for 1-2 seconds every 3 to 5 minutes - very annoying when listening to an audiobook.
As of this afternoon, both problems magically stopped. I have e-mailed Parrot tech support, but I'm not hopeful that I'll get a useful reply.
I have had so many problems with the 3200 that ,due to anger, I have broken the bracket and front screen. It mutes the radio even after the call has finished. Crashes too often. I have no audio at least half of the calls I make.
I must add that it also did this with my Trinity running WM6 but worked flawlessly with my SP5 smartphone.
I read "HTC and Parrot Announce Strategic Alliance" on the Reuters website.
How I chuckle.