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
Help, I bought a hbh-600 bluetooth headset but am not be able to connect it to my Qtek 9090. I can find the device and authorise it, but I am not able to connect to the device. Everytim I will connect to the device my Qtek 9090 says: Connection failed...
Help what can I do...
Had this problem yesterday with my step uncle's Harrier, and the HBH-600.. Just took a lot of fiddling around by turning bluetooth on/off, re-pairing, and it eventually worked.
I haven't seen this with my Harrier/HBH-600.. but I have had some general bluetooth issues.. About to try an upgrade to the 3500 build.
Can you tell me specific what you have done? Because I have tried that repairing and Bluetooth on and off also a few times...
Is it the authentification? Or is it something else.
Tnx!
:wink:
Well, no, not really sorry.. I was just mucking around, because he was in a hurry to leave... It just worked in the end. It may well not be the same problem anyway.. sorry.
the range on HBH600 sucks - mount it on the ear, and put 9090 in your trousers pocket or extend your arm while holding PPC - you will have very poor sound instantly.
Tnx all for the info. I have found the BT-PPC build 3500 patch and my bluetooth headset is working!!!
what's your radio firmware version now ?
Radio: 1.06.00
Bluetooth: BT-PPC build 3500
Has anyone tried to edit the BT registry settings? There are two which look interesting:
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\sys\
DisableAutoSuspend: REG_DWORD
Determines whether or not suspend mode is enabled on the device.
1: AutoSuspend is disabled. If the Bluetooth device is currently connected the stack calls SystemIdleTimerReset periodically to ensure the device does not go to sleep.
0: AutoSuspend is not be disabled by the stack.
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway
PowerSave : REG_DWORD
Configures the audio gateway to conserve power when establishing audio connections.
0 - Keeps the service level connection active for the Hands-Free profile in between calls.
1 - Closes the service level connection between calls.
This page provides the BT registry keys under WM5:
http://msdn.microsoft.com/library/d...ecomm5/html/wce50constackregistrysettings.asp
BT disconnect
Do you know whic values should i change to prevent the bluetooth from turning off after a while speciall when the device is not connected to the cradel
I don't have WM5 loaded, but it looks like the first key prevents the device from going into autosuspend when the BT is connected. I checked with my M2000 and my MDA Compact, both running WM2003SE, and they have this key set to 1.
The 2nd key is not present in my WM2003SE devices. Of course my M2000 has the 3900 stack, and my Compact has the MS stack. Can you check to see if you currently have those keys on WM5, and what they are set to?
Yung said:
I don't have WM5 loaded, but it looks like the first key prevents the device from going into autosuspend when the BT is connected. I checked with my M2000 and my MDA Compact, both running WM2003SE, and they have this key set to 1.
The 2nd key is not present in my WM2003SE devices. Of course my M2000 has the 3900 stack, and my Compact has the MS stack. Can you check to see if you currently have those keys on WM5, and what they are set to?
Click to expand...
Click to collapse
It is also set to 1 in wm5 ...
ThExSenatoR said:
Yung said:
I don't have WM5 loaded, but it looks like the first key prevents the device from going into autosuspend when the BT is connected. I checked with my M2000 and my MDA Compact, both running WM2003SE, and they have this key set to 1.
The 2nd key is not present in my WM2003SE devices. Of course my M2000 has the 3900 stack, and my Compact has the MS stack. Can you check to see if you currently have those keys on WM5, and what they are set to?
Click to expand...
Click to collapse
It is also set to 1 in wm5 ...
Click to expand...
Click to collapse
Well then maybe we need to change the second value to 0 ? I would try it,but I had to downgrade to 2003SE again,as I need reliable b/t. Even a somewhat reliable b/t is better than the wm5 b/t for now.
Later..........
It looks like the 2nd key may keep the audio gateway active...
ThExSenatoR said:
Yung said:
I don't have WM5 loaded, but it looks like the first key prevents the device from going into autosuspend when the BT is connected. I checked with my M2000 and my MDA Compact, both running WM2003SE, and they have this key set to 1.
The 2nd key is not present in my WM2003SE devices. Of course my M2000 has the 3900 stack, and my Compact has the MS stack. Can you check to see if you currently have those keys on WM5, and what they are set to?
Click to expand...
Click to collapse
It is also set to 1 in wm5 ...
Click to expand...
Click to collapse
The first on is there and and is set to 1
The second one does not exist in my WM5 Registery. I would assume no REG_DWORD at all would be defaulted to Zero or not even used.
hdbueller said:
ThExSenatoR said:
Yung said:
I don't have WM5 loaded, but it looks like the first key prevents the device from going into autosuspend when the BT is connected. I checked with my M2000 and my MDA Compact, both running WM2003SE, and they have this key set to 1.
The 2nd key is not present in my WM2003SE devices. Of course my M2000 has the 3900 stack, and my Compact has the MS stack. Can you check to see if you currently have those keys on WM5, and what they are set to?
Click to expand...
Click to collapse
It is also set to 1 in wm5 ...
Click to expand...
Click to collapse
Well then maybe we need to change the second value to 0 ? I would try it,but I had to downgrade to 2003SE again,as I need reliable b/t. Even a somewhat reliable b/t is better than the wm5 b/t for now.
Later..........
Click to expand...
Click to collapse
The second value is on 0 if i remember well...
Back to WM2003SE
i think i will be back to wm2003se, as i tried the two switches but nothing happened.
So many new WM5 releases... Still no bluetooth fix?
Hi
Unfortunately - yes.
But good guys are working on it.
It's matter of short time when Ivan's ROM will have it.
It's the only thing that keeps me staying on WM2003...[/b]
Dont count on it being fixed, not with the MS stack anyway.
lets all cross our fingers and hope that widcomm 1.7 works
i doubt there would be a fix with MS Stack, unless we can get broadcom or widcomm stack running.. then everything, including A2DP should run just fine.
I'm currently testing the broadcom/widcomm 1.71 stack, result are still inconclusive, but its better than the M$ one
Everything apart from bluetooth voicedial.......
Hi
Most of you already know this, but:
The newest relase of Ivan's ROM has the BT disconnect issue resolved permanently.
Have fun with it
Yes it is a step in right direction, but still have nasty bug with most BT Headsets, no voce in call. I am sure that mamaich ivan and Midget_1990 will find a solution for this bug soon. We will just wait and see
any progress?
I have widcomm stack 1.7 in my ipaq 6965, and I can control audio input/output over bluetooth by press of button on the headset (press and hold for 2 sec it'll trigger a redial AT command I think) but it just can't trigger an application like voicecommand in the pda. What's fustrating is that there's no documentation of widcomm sdk, so there's no way to figure out what's required in the registry (plus what dll needs to be develop) in order to handle the AT+CPR200 (I think that's the AT command for bluetooth button press) event.
If somebody has some clue or progres, please share here and hopefully more brains can be put together and fix this once and for all!
I do not know what is the problem with your ipaq, but the bt bug is fixed now, you can search the forums for it
xplode said:
I do not know what is the problem with your ipaq, but the bt bug is fixed now, you can search the forums for it
Click to expand...
Click to collapse
hi, my problem is not about auto-disconnect or no sound. everything works perfectly fine with 1.7 widcomm stack except that I can't do voice dial. specifically, I can't activate a voice cmd application with the press of bluetooth button. When I press the button, the audio streaming is turned on (and mic is working over bluetooth) but it just doesn't start the voice cmd application, which I have to manually turn it on from the pda device.
if your BA's widcomm can enable the voice dial, I would like to request if you can share your registry and the necessary dLL
we dont use widcomm anymore because someone fixed the M$ stack.
Hi!
I've allready tried some ROMs on my BA (xplode wm6.1 and so on), but i have problems with bluetooth. I can't get my BA working with tomtom 6 and my Nokia LD-3W gps mouse. I also have problems sending stuff through bluetooth (for example contacts from my mobile phone). On wm2003 everything works fine. But I don't want the wm2003.
please help me!
try updating your bt stack to latest version. should be able to find it in the ba wiki
I've got the latest BT stack allready...
I had a similar problem with my Haicom BT GPS mouse when set up according to the instructions in the wiki.
Removing the "secure connection" to the mouse my problems with GPS went away.
As I normally don't use BT for anything else I can't comment on other bt problems.
When you install xplode rom install his all fixes cab files it will fix BT wifi contacts and beam
The xplode ROM is the one I love
(failing that I drop back to the o2 distribution 2003 ROM.