There are other car connection threads but I thought I would post this thread to provide a search hit for anyone with a Ford Bluetooth Radio. It combines bits from a couple of threads and should enable you to successfully connect to your Ford car. Thanks to all of the other posts whose work I have cobbled together here. This is confirmed as working with the HTC 1.66 WWE ROM.
Out of the box the HD2 does not initiate auto connection with the Ford, refuses to pair with the Sony radio and hangs the radio at the end of a call so...
Using Resco or similar registry editor..
1. Modify the HandsFree plug-in: HKLM\Software\WIDCOMM\Plugin\HandsFree
i. Change DWORD SupportedFeatures to 45 (was 1379)
ii. Create binary value HFBDA , set to same value as LastConnectedBda
iii. Create DWORD HFDeviceType (Dec) 2
2. Modify the WIDCOMM bluetooth general settings: HKLM\Software\WIDCOMM\BtConfig\General
i. Change binary Value bdaddr to (no value) delete the existing key value, was 00 23 76 74 2c d5
ii. Change DWORD DisableReopenAudio to 0 (default is 1) I didn't have this registry key so I created it with DWORD value (dec)0
3. Reboot device (soft reset or long press off until power off option).
These above mods make the handshaking between car and HD2 much less prone to lockups!
Go to car, check that radio has bluetooth enabled.
HD2 wil find car (Ford Audio), send a random keycode - pairing fails but this will wake up radio which displays another keycode. Re-enter this correct keycode and pair device.
If a Ford built in radio then accept incoming connections and phonebook download when prompted.
If the Sony radio (Galaxy, S-Max etc) then you must also accept the stereo music connection else it will not work.
On HD2 go to settings, menu, all settings, bluetooth and 'add knickname' to your Ford Audio connection, check that 'accept all connections' box is ticked on this page.
Only bug so far is that by accepting the stereo audio connection the music player starts playing whenever you connect to the Sony radio. The music cannot be heard as the Sony does not accept incoming streams - however if you do not enable it at the connecting stage then the phone connection subsequently fails and refuses to work again. If anyone can get around this annoying problem then please post below.
Huge thanks for pulling this together
I'd about given up hope of getting the HD2 working with my S-Max. Still not perfect, but at least now usable.
Great stuff.
Interstingly the current S-Max seems to be generally less compatible than the one from a couple of years ago.
Related
I want to buy this headset but I have some doubts about it and I thought you may help. (I have HTC Universal)
1. Does this headset really show the CONTACT'S NAME on display or just the phone number? If so, can I upgrade ROM or install patch to make it show NAME? I use Pocket Informant, if it matters...
2. Does the remote really work? With all player's software (usually use TCPMP). With my laptop on standby and closed (screen faced inside) can I simply make it start playing and foward etc??
3. Can I see the song's info on display? Like artist, song's name and all?
4. As a simple headset (on car use), is it good enough? easy of use, good sound quality on recieving and mic good quality on talking? Or is it just like "Speeker on" effect on Universal that I have to have my mouth gludded on display to talk and other person listen clearly (laptop mode)?
5. As a headset (for music and movies purpouse) is it good quality sound (better than original HTC headphones/headset that came with Universal (wired ones)?
6. I've heard there was a problem reconnecting headset stereo after a call (recieving I think). I've also heard that had o reconnect on settings... Is it true? Happens with all PPCs and all Stereo BT headsets? Or just with some brands/models? If this happens, I dont know if its worth the money, since I recieve calls a lot (would be boring to restore settings or resets...).
Can be fixed with upgrade of ROM or patch (If there is this problem with Univ).
7. Is it worth to trade a normal BT headset (jabra b250v) and stereo headset (wired that came with Uni) for this one??? It's kinda expensive... Will I be pleased or its just problems... wireless stuff??
8. how do I know if my ROM has AD2P and AVRCP. If no, how do I upgrade to it?
Please help me decide if its worth the buy!
Thanks
Deiota
RE
Hi!
I'm using the SE HBH-DS970 bluetooth headset with QTEK 9000 aka Universal
1 - It shows contact names provided you've JETware Hands-free Extension installed otherwise you only have contact numbers on display
http://www.jetwaremobile.com/index.htm
2 - The remote works very well with Conduits Pocket Player v2.8's AVRCP
http://www.conduits.com/products/player/
3 - Didn't notice it can
4 - Not sure use in car (I don't drive) but it works well when use for talking
5 - Sound quality fairs vey well and its slightly strong on the bass side and not too strong on treble (comparing to BLUETAKE iPhono mini 450Rx). Did not try with Universal's wired headset
6 - This issue applies to many headsets too. Only way out is to exit the music program and re-start it and everything will be fine
7 - Why have 2 when you can have 1 integradted one?
8 - So far only the latest Universal, QTEK 9000, ROM has built-in A2DP and AVRCP.
Hope it helps
RE
Bro,
Your QTEK 9000 ROM
QTEK 9000 (Universal)
ROM Version: 1.30.77 WWE
Radio version: 1.09.00
ExtROM version: 1.30.176 WWE
has built-in A2DP and AVRCP
RE
Oh...and ,btw, add to your registry to have an improved A2DP performance with less stuttering/lag etc
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd
Add "Priority256 "=dword:60 (Use Dword Value)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway\Capability
Change Dword value to 69 (default is 37)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings\BitPool
Change Dword value to 40 (default is 30, recommended by other forumer is 60)
Re: RE
FOSA said:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway\Capability
Change Dword value to 69 (default is 37)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings\BitPool
Change Dword value to 40 (default is 30, recommended by other forumer is 60)
Click to expand...
Click to collapse
maybe i'm blind but i never find these two in the QTEK rom registry
RE
Sorry, what I meant was
change the Capability Dword value in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway\
to 77 (default is 37)
and the Bitpool Dword value in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings\
to 40 (default is 30, recommended by other forumer is 60)
All change values are in Decimal :lol:
Re: RE
FOSA said:
and the Bitpool Dword value in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings\
to 40 (default is 30, recommended by other forumer is 60)
Click to expand...
Click to collapse
Strange, I do not have the registry entry "Settings\". After "A2DP\", all I have is "Device1\", "Device2\" "Device3\", "Device4\".
I am using the tornado patch (not the Qtek ROM).
Anyway, I am using this Sony Ericsson headset:
- If I am playing music and a call comes in, the headset does not pick-up the music after the call. I have to shut everything down, and refresh the services of the headset.
- Usable range for stereo music is about 10-20 centimeters. So, if the Universal is on my belt, then the headset receives the music okay. Any further, and the headset does not receive the music. In other words, in my experience, the wired headset that came with the universal has longer range!!!
- The music title and contact names do not appear on the headset screen, but then I am not using JETware Hands-free Extension at the moment.
@FOSA: How is your experience, especially concerning:
- bt range (for music)?
- Resuming music after a call?
- I understand you are using the Qtek ROM (not the tornado patch)?
RE
Sorry, missed out one other important registry entry for smooth A2DP, here:-
HKEY_LOCAL_MACHINE\Drivers\BuiltIn\BtA2dpSnd
Add "Priority256 "=dword:60 (Use Dword Value)
Note :- All in there're 4 registry entries
RE
Hi BillB
Quote
"How is your experience, especially concerning:
- bt range (for music)?
- Resuming music after a call?
- I understand you are using the Qtek ROM (not the tornado patch)?"
- 5m of open space is not an issue
- Not possible to resume music after a call, however, I just exit Conduits Pocket Player v2.8 and re-start the player again and everything (including AVRCP cotrols) work fine. NO need to soft reset and re-pairing. My AVRCP controls even work with my QTEK 9000's lid closed. All these made possible with Concuits Pocket Player v2.8
- Yes, I'm using the QTEK 9000 with latest A2DP ROM + the 4 regsitry entries mentioned above for smooth music
Thanks for the info.
I will have to try Conduits Pocket player, and maybe even upgrade my JasJar to the Qtek ROM (I am guessing that i-mate will not release any new official ROM updates for JasJar).
Re: RE
BillB said:
FOSA said:
and the Bitpool Dword value in
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\A2DP\Settings\
to 40 (default is 30, recommended by other forumer is 60)
Click to expand...
Click to collapse
Strange, I do not have the registry entry "Settings\". After "A2DP\", all I have is "Device1\", "Device2\" "Device3\", "Device4\".
I am using the tornado patch (not the Qtek ROM).
Click to expand...
Click to collapse
i have the QTEK ROM with Device1-4 and none of the other settings that FOSA and other's speak of. just the opposite. which is which??
RE
Sorry all,
Only 3 entries needed
Hi skywriter,
The 3 registry entries are added using an improved A2DP patch available on this forum - can't remember where. However, if you know how to add these entries then there's no need for the said patch.
You can have different values after trying them out and get the minimum stutter/lag/hiss etc on your set
See the attached pictures
:lol:
RE
Sorry, one of the pictures was synching while its being snapped, here:-
Where to buy
Hello!
I want to know where is the best place to buy this headset (in Europe).
Thanks
Deiota
I don't know if this place is the "best", but I bought mine from this online store in Spain with very fast service/delivery:
http://www.bluezona.com/index.php?o...18&PHPSESSID=9b2d60858e02b1e75bc53faace6b690f
They have several other models available too.
FOSA,
You seem to know your DS 970 pretty well. I have the same model and I love it I must say. I am not experiencing any hiss or reception problems except when my 9000 is in a case where the magnet is messing around with it in general.
However... I have the following issues:
- Turn BT on 9000 on
- Turn DS 970 on
Although Wireless Stereo Option in the pairing is unchecked the phone streams all sound to the headset. I have to go in and check/save and uncheck/save to disable wireless stereo.
Also I cannot get Caller ID to work correctly with the Jetware. I emailed them and sent them a log and they determined that the headset is using extra commands which is what is causing the problem. Probably will be fixed in a future release but for now, it doesn't work.
Mind you, I have tested thoroughly and did go to the trouble to backu and hard reset. Both problems persist after hard reset with only one number in contacts for test purposes.
Any ideas? (the wireless stereo bit it killing me..)
Other than that I have to say, it's extremely well behaved, stylish, handy and reliable.
Joanna
Correction: I tried the new beta of Jetware and it works fine (so far) with the CallerID checked in the Advanced Options.
RE
Quote
"However... I have the following issues:
- Turn BT on 9000 on
- Turn DS 970 on
Although Wireless Stereo Option in the pairing is unchecked the phone streams all sound to the headset. I have to go in and check/save and uncheck/save to disable wireless stereo. "
I don't have this problem. Once paired my QTEK 9000 auto detects my HBH-DS970 the next time when I turned both on and 'Handsfree' and 'Wireless Stereo' options are always checked
RE
Aaaaaaa.............its not relaible
I uninstall and re-install JETware and now its not displaying name caller id
:roll:
FOSA my problem is not whether it's checked or not. I have chosen to uncheck the wireless stereo and use it only as a headset when I drive. It completely ignores the UNchecked wireless setting and still streams all sound (including incoming call ringtone) to the DS970 even though it shouldn't. Setting is unchecked and the minute I turn on the headset it acts as a wireless stereo. Have you tried this at all?
I have not tried uninstalling but 2 days later the beta still works. I have two more questions for you, well one really:
1. Does it scroll the whole name of the contact? Mine shows the number and then the name but not the whole name (which in Greece could be miles long). Just the first 10 characters. On the HBH660 I know it scrolls the name. I am not sure if this is a limitation of the headset or the software.
2. Uninstall and remove the settings from the registry. It leaves the settings behind in HKLM/Software/Jetware. Trying installing then and see what happens. I use the beta which will be released with the next week or so (or so they said).
Joanna
Re: RE
FOSA said:
Hi skywriter,
The 3 registry entries are added using an improved A2DP patch available on this forum - can't remember where. However, if you know how to add these entries then there's no need for the said patch.
Click to expand...
Click to collapse
thanks FOSA! i knew they came from somewhere... but i didn't know where. if i can just create them by hand that works too!
I am successfully using the Tornado A2DP hack on my Prophet in conjunction with my bluetooth enabled car stereo. I have written a mort script to make the two connect automatically when bluetooth is switched on but there are odd occassions when they disconnect, like if I switch to listen to the radio.
I can't find the registry setting that controls the state of the "set as wireless stereo" function to either 1 for on or 0 for off. Can anybody help?
My intention is for the script to re-connect the wireless stereo if it detects that the registry setting has changed to 0.
I have been busy trying to track down the issues I have been having on my apache with a2dp, try searchnig the registry for "stereo", you should get a few hits.
Otherwise try
HKLM\Software\Microsoft\Bluetooth\Device\[your devices mac address]\services\
There should be a few long strings (folders), most likely corresponding to one for "wireless stereo" and one for "handsfree", in one of those you may see the wireless stereo...
anyway thats what I got with a 3.5aku and moto headset.
shiggs,
I've already tried that path and it does have a "services" folder with Wireless Stereo and Hands Free folder but the Dword value is enabled (set to 1) in both permanently, evenwhen bluetooth is switched off.
If we can figure this out it would be beneficial for everyone with a wireless stereo device for automatic connection.
Surely someone must know what registry changes take effect once "set as wireless stereo" has been tapped?
neomagik said:
Surely someone must know what registry changes take effect once "set as wireless stereo" has been tapped?
Click to expand...
Click to collapse
use a little utility called ssnap to take a snapshot of registry before enabling that option and another snapshot after checking it. Then compare the two file with an hexeditor (for example) and see which key/value was changed/added
cheers
hey all
I cant seem to find a lot of info about this topic, so hoping you guys can help me out somehow.
is there any way of getting WM to join to handsfree bluetooth profile when i'm in my car (using pioneer headunit)?
reason being is pioneer head units require you to be connected to the phone in order to use the head unit to make calls, phonebook, etc
with my nokia back in the day, provided bluetooth was on, i would sit in my car and turn my ignition on. about 10-15 seconds later, the headunit joins with the phone. the phone says its connected to 'Pioneer BT unit' and the headunit shows the battery and signal level, and shows the correct phonebook.
with my jasjam (running blacksatin wm6 - although had the same problem on wm5), the pioneer unit doesn't join automatically... it is only after i receive or make a call using the phone, that it quickly joins to the headunit. even then, the person could have started talking before the audio fully comes through...
however this is not a problem there on, as once the bluetooth connection has been made, it remains, and everything works as it should.
so is there any registry hacks or programs i can run that will allow the headunit to make the connection to the handsfree profile once ignition is on in the car?
Cheers,
Bill
hi bcx7,
I had his problem too. It may depend on what head unit you are using, but perhaps the solution is the same.
my pioneer head unit is a DEH-P75BT. It looks for a smartphone, but doesn't recognize the hermes as it's classed as a pda phone.
Solution:
Change the COD (Class of Device) from a PDA device to a smartphone device.
1. First make sure you've got a backup, or remember all settings you change in the registry.
2. Edit with a registry editor the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SYS\COD
By default my T-Mobile Vario II has the value: 1048852 (decimal) for WM5 & 5374228 (decimal) for WM6. Change this to: 5374476 (decimal).
3. Soft restart your device
4. Your device should dentify itself as a smartphone, and my pioneer unit finds it without problems. Note that for my Vario II, I also have to discovery mode always on, so I also protect it with a PIN code.
On the head unit, scan for the devices, save it in one of the P1, P2 positions etc. Then when you switch on your ignition, the head unit should recognize it.
One final tip. My head unit doesn't see the Vario II unless the screen is on (device not in standby). If the screen is off (device in standby), and even though bluetooth is on and in discovery mode, the head unit won't see it. Once connected I put the device in standby and it stays connected just fine.
I found this information a while back on this forum, so credit to the original poster - sorry don't know who it was.
Hope thats helps.
Mike
For those frustrated by the lack of phone support for rSAP car phone kits from anyone other than Nokia. I have managed to get my SE Xperia X1 working with my VW Toureg, suspect it should work with Merc Benz, but you'll need to try it.
I downloaded Helmi's BTSAPSettings Cab from http://forum.xda-developers.com/showthread.php?t=273857&page=17 posting #166 and installed it. Works great connects to car, doesn't drop, quality great.
Only problem I have is that the car kit only sees the sim contacts to copy across and not my outlook contacts. I believe this is because it sees the phone as a Pocket PC and not a Phone/SmartPhone. Anyone have any ideas on how to fix? Any regedits needed?
Thanks
X1, SAP and Nokia 616
Hi!
i also installed Helmi's BTSAPSettings Cab and the X1 now shows SAP in bluetooth profiles.
But my Nokia 616 connects only as handsfree and not in sim acess mode.
Any ideas?
Thanks!
Greetings, Luggi
no working on my touareg
hi
I installed the file on my x1, and teh sap is visible in the list of bluetooth profile. But when i am in my car, it says that the phone is not comptatible.
Do you have any suggestion?
Thanks
This works
with the x1 and the Nokia 616:
http://forum.xda-developers.com/showthread.php?t=372529
Greetings, Luggi
I have tried installing both files.
SAP works, the car finds the phone, asks for the code, they pair.
But then, the car keeps saying "connecting..." the PDA (X1) loses the operator but the car doesn't access the SIM and even says cannot connect.
Any idea??? (The xperia has got the new R2 firmware)
My X1 works out of the box with my Kenwood 8041BT car radio. It shows all my Outlook contacts, i have no items on the sim-card. I have no software separately installed for this, the rom is the one in my signature.
Bluetooth devices identify themselves as a certain thing. Headsets as headsets, phones as phones...interestingly, XDA's identify themselves as PDA's not phones. This can be changed....
Taken from http://forum.xda-developers.com/showthread.php?t=282544&highlight=rsap
You need a registry editor. If you're not comfortable with editing the registry, don't do it. It can and will mess up your phone if done wrong!
First, you need to change the bluetooth identity to be a phone, or the accessory will not recognise it (funnily enough, bluetooth car kits don't look for pocket PCs). Here's how:
Download PHM RegEdit. Its a free, and simple registry editing program.
Next, edit the following value:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:52020C (hex)
Bear in mind the new dword is a Hex value, so be sure to select "Hexadecimal" from the Base menu.
For reference (in case something messes up), heres the original value (the Pocket PC identifier):
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:1048852 (decimal)
Now, soft reset the phone. If the device is already paired, delete the pairing, and start from scratch. This time it should work as the accessory is seeing the device as a phone, not a PDA. If it doesn't work, you haven't lost anything. The first thing I did with my XDA Stellar was change this and it still happily runs A2DP, file transfer, Activesync etc.
Hope that helps, but play at your own risk.....
Bluetooth devices identify themselves as a certain thing. Headsets as headsets, phones as phones...interestingly, XDA's identify themselves as PDA's not phones. This can be changed....
Taken from http://forum.xda-developers.com/showthread.php?t=282544&highlight=rsap
You need a registry editor. If you're not comfortable with editing the registry, don't do it. It can and will mess up your phone if done wrong!
First, you need to change the bluetooth identity to be a phone, or the accessory will not recognise it (funnily enough, bluetooth car kits don't look for pocket PCs). Here's how:
Download PHM RegEdit. Its a free, and simple registry editing program.
Next, edit the following value:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:52020C (hex)
Bear in mind the new dword is a Hex value, so be sure to select "Hexadecimal" from the Base menu.
For reference (in case something messes up), heres the original value (the Pocket PC identifier):
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\SY S]
"COD"=dword:1048852 (decimal)
Now, soft reset the phone. If the device is already paired, delete the pairing, and start from scratch. This time it should work as the accessory is seeing the device as a phone, not a PDA. If it doesn't work, you haven't lost anything. The first thing I did with my XDA Stellar was change this and it still happily runs A2DP, file transfer, Activesync etc.
Hope that helps, but play at your own risk.....
I use the FISCON Pro for Volkswagen RNS-510 and RCD-510 Bluetooth Hands-Free unit in my car. This Hands-Free unit uses a Parrot chipset and directly connects to the CAN-Bus of the Vehicle making it easy to install.
Up until a recent Firmware update everything worked fine.
After the Firmware Update to Release 1.83 I experienced that the Bluetooth Connection is dropped after every phonecall. And to establish it back on one has to Toggle Bluetooth on the Touch HD or power down the RNS headunit. Quite inconvenient for daily use on the road, and annoying.
I had conversations with the Producer Kufatec and the Distributor I bought the Fiscon unit from. Apparently there was a change in the Firmware that created this behaviour.
Now doing research on this I came across the Windows Mobile SDK Documentation and the documented registry entries allowing to control the behaviour of the Bluetooth Audio Gateway.
And these are now the settings that brought back the stability of the BT Connection inbetween calls:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"SupportCLI"=dword:00000001
"OutgoingCallOption"=dword:00000002
"PowerSave"=dword:00000000
"NoHandsFree"=dword:00000000
"BTAGExtModuleVersion"="2008.12.18.0"
"ConnectHFOnCall"=dword:00000001
"ConnectScoInAlways"=dword:00000001
"Capability"=dword:00000065
"BTAGExtModule"="OEMAGW.dll"
"BTAGPBModule"="\Windows\BthAGPhonebook.dll"
"NoRoleSwitch"=dword:00000001
I did not explicitly test each individual entry, however reading the documentation "PowerSave" might have had the most contribution. "PowerSave" allows to set if the BT Control Channel will stay alive between phone calls. It was disabled on default on my unit, and that would explain why the Fiscon unit lost connection after every call as Windows Mobile was putting the BT Control Channel to sleep.
You may read the full documentation on these Registry Settings here on the MSDN Website:
http://msdn.microsoft.com/en-us/library/aa915920.aspx
Just for completeness these are the settings for the AudioGateway Module and Extensions (Windows Mobile 6.5, cooked by XANNY):
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModuleVersion"="2008.12.18.0"
"BTAGExtModule"="OEMAGW.dll"
"BTAGPBModule"="\Windows\BthAGPhonebook.dll"
Then I discovered the settings for the BT AudioGateway Service, that also carry a "PowerSave" entry and which I set to (0) to disable any PowerSave for the Service (I assume):
Code:
[HKEY_LOCAL_MACHINE\Services\BTAGSVC]
"PowerSave"=dword:00000000
"IsEnabled"=dword:00000001
"Index"=dword:00000000
"Prefix"="BAG"
"Keep"=dword:00000001
"Order"=dword:00000009
"Dll"="BTAGSVC.Dll"
"FriendlyName"="Bluetooth Audio Gateway"
With these changes I performed to my Touch HD's Windows Mobile 6.5 it cooperates nicely again with the Hands-Free unit, keeping the BT Connection up.
I want to document and share this here, to help other Touch HD or Windows Mobile users that have similar trouble with their Bluetooth HandsFree unit.
Please perform any changes resulting from this post on your own Windows Mobile unit with your full self-responsibility.
Hi
I have the same Fiscon Pro on my Volkswagen Passat with the RCD-510. Unlike you I got a HTC Touch Diamond 2 (Topaz) with WM 6.5
I had the Problem you described prior to 1.83. Now all is fine but I cant access teh Phonebook from within the middle-console in my car. Does this work with you?
cheers
btw. my Registry has some interesting differences to yours:
Code:
[HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\AudioGateway]
"BTAGExtModuleVersion"="2008.12.18.0"
"BTAGExtModule"="\Programme\JETware\JetBTHFx.dll"
"BTAGPBModule"="OEMAGW.dll"
wtf?