Bluetooth headset register keys - MDA II, XDA II, 2060 ROM Development

I have a Qtek 2020, with a Jabra BT250v! My bluetooth stack is 3900 on a ROM version 2.06 WWE! I can pair it but the sound doesn't get through!
I have look through the forum but i can't find any settings and information of the register keys special to this headset!
This is the only thing that i a missing with the widcomm stack. I can run through the network, i can synchronize my PDAphone also!
Where could i check my configuration?
Does anyone has make it work with the same stack and headset?
It worked with the MS stack, but now that i have the network on the widcomm i want to keep the widcomm stack only!
almost everything works...
I will post tonight my register key when i'll get home!!
Thx for reading so far, and posting now on!

Bluetooth register keys!
Here are the register keys! May be a bit long but i would like to know if there is something wrong!Please let know and share your knowledge!
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connections]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connections\0003]
"PluginProfile"=""
"Shortcut"="ActiveSync with NERFIAUX"
"LocationBitMask"=dword:00000001
"DefaultConnection"=dword:00000000
"LocalDirectory"="\\My Documents"
"BDName"="NERFIAUX"
"BDDevClass"=hex:32,01,04
"BDAddress"=hex:00,0A,3A,54,98,71
"UserInstalled"=dword:0000000E
"ComPortNumber"=dword:0000000E
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Name"="ActiveSync"
"SecurityId"=dword:00000001
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"UUID"=dword:00001101
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connections\0001]
"PluginProfile"=""
"Shortcut"="Internet via NERFIAUX"
"LocationBitMask"=dword:00000001
"DefaultConnection"=dword:00000000
"LocalDirectory"="\\My Documents"
"BDName"="NERFIAUX"
"BDDevClass"=hex:32,01,04
"BDAddress"=hex:00,0A,3A,54,98,71
"RasConnection"=""
"Autoconnect"=dword:00000001
"Password"=""
"UserName"=""
"UserInstalled"=dword:0000000C
"ComPortNumber"=dword:0000000C
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"Name"="Accès réseau"
"SecurityId"=dword:00000002
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001102
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connections\0002]
"PluginProfile"="HandsFree"
"Shortcut"="Headset connection to Jabra BT 250v"
"LocationBitMask"=dword:00000001
"DefaultConnection"=dword:00000001
"LocalDirectory"="\\My Documents"
"BDName"="Jabra BT 250v"
"BDDevClass"=hex:20,04,08
"BDAddress"=hex:00,07,A4,0C,1E,AA
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001108-0000-1000-8000-00805F9B34FB}"
"Name"="Headset"
"SecurityId"=dword:00000000
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001108
"SpkGain"=dword:00000008
"MicVolume"=dword:00000008
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\HandsFree]
"ServiceMask"=dword:00000001
"AudioPreferences"=dword:00000000
"HFDeviceType"=dword:00000001
"HFBDA"=hex:00,07,A4,0C,1E,AA
"AudioSetupDll"="HTC_PCM_Routing.dll"
"SupportedFeatures"=dword:00000037
"AudioHandling"=dword:00000013
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\HandsFree\AutoLoadOnStackStartup]
"ActionType"=dword:00000001
"LoadPath"="hfpui.exe"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\HandsFree\ControlPanel]
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"Enabled"=dword:00000001
"Dll"="HfpControlPanel.dll"
"Name"="Hands-Free"
"UUID"=dword:0000111E
"Configurable"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\DUNServer]
"ModemInterface"="TAPI"
"SendPPPTerminate"=dword:00000001
"ServiceName"="Dial-up Networking"
"TapiLine"="Cellular Line"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\DUNServer\ControlPanel]
"Encryption"=dword:00000000
"Authentication"=dword:00000000
"Authorization"=dword:00000000
"Enabled"=dword:00000000
"Name"="Dial-up Networking Server"
"UUID"=dword:00001103
"Configurable"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\AV]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\AV\AutoLoadOnStackShutdown]
"ActionType"=dword:00000002
"LoadPath"="btavui.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\AV\AutoLoadOnStackStartup]
"ActionType"=dword:00000003
"LoadPath"="btavui.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\Hid]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\Hid\AutoLoadOnConnect]
"ActionType"=dword:00000002
"LoadPath"="bthidplugin.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\Hid\AutoLoadOnStackShutdown]
"ActionType"=dword:00000002
"LoadPath"="bthidplugin.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Plugin\Hid\AutoLoadOnStackStartup]
"ActionType"=dword:00000003
"LoadPath"="bthidplugin.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\AutoConnect]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\AutoConnect\0012]
"ClassID"=hex:02,11,00,00,00,00,00,10,80,00,00,80,5F,9B,34,FB
"MTU"=dword:000005F0
"SecurityLevel"=dword:00000030
"SecurityID"=dword:00000002
"UUID"=dword:00001102
"BDName"=hex:4E,45,52,46,49,41,55,58,00
"BDDevClass"=hex:32,01,04
"BDAddress"=hex:00,0A,3A,54,98,71
"ServiceName"=hex:41,63,63,C3,A8,73,20,72,C3,A9,73,65,61,75,00
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\AutoConnect\0014]
"ClassID"=hex:01,11,00,00,00,00,00,10,80,00,00,80,5F,9B,34,FB
"MTU"=dword:00000294
"SecurityLevel"=dword:00000000
"SecurityID"=dword:00000001
"UUID"=dword:00001101
"BDName"=hex:4E,45,52,46,49,41,55,58,00
"BDDevClass"=hex:32,01,04
"BDAddress"=hex:00,0A,3A,54,98,71
"ServiceName"=hex:41,63,74,69,76,65,53,79,6E,63,00
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Devices]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Devices\00:07:a4:0c:1e:aa]
"LinkKey"=hex:84,CF,1C,93,4F,74,0E,8B,F8,FF,A1,D6,30,34,56,2B
"TimeStamp"=dword:00000000
"Features"=hex:FC,FF,0B,00,00,00,00,00
"DevClass"=hex:20,04,08
"Name"=hex:4A,61,62,72,61,20,42,54,20,32,35,30,76,00
"TrustedMask"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Devices\00:0a:3a:54:98:71]
"LinkKey"=hex1,6F,B0,AD,C6,68,02,2A,F5,B2,9E,46,8B,94,3E,3F
"TimeStamp"=dword:00000000
"Features"=hex:FF,FF,0B,00,00,00,00,00
"DevClass"=hex:32,01,04
"Name"=hex:4E,45,52,46,49,41,55,58,00
"TrustedMask"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications\0001]
"Authentication"=dword:00000000
"ComPortNumber"=dword:00000007
"Encryption"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Name"="Generic Serial"
"SecurityId"=dword:00000001
"UUID"=dword:00001101
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications\0002]
"Authentication"=dword:00000000
"ComPortNumber"=dword:0000000C
"Encryption"=dword:00000000
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"Name"="LAN Access Using PPP"
"SecurityId"=dword:00000002
"UUID"=dword:00001102
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications\0003]
"Authentication"=dword:00000000
"ComPortNumber"=dword:0000000B
"Encryption"=dword:00000000
"GUID"="{00001103-0000-1000-8000-00805F9B34FB}"
"Name"="Dialup Networking"
"SecurityId"=dword:00000003
"UUID"=dword:00001103
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications\0004]
"Authentication"=dword:00000000
"Encryption"=dword:00000000
"GUID"="{00001105-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX Object Push"
"SecurityId"=dword:00000005
"UUID"=dword:00001105
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications\0005]
"Authentication"=dword:00000000
"Encryption"=dword:00000000
"GUID"="{00001106-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX File Transfer"
"SecurityId"=dword:00000006
"UUID"=dword:00001106
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Applications\0006]
"Authentication"=dword:00000000
"ComPortNumber"=dword:0000000E
"Encryption"=dword:00000000
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Name"="ActiveSync Serial Port"
"SecurityId"=dword:00000001
"UUID"=dword:00001101
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Debug]
"LogIPAddr"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Debug\Log]
"012"="2005/06/14 12:18:05:0000
Stack loaded OK"
"NextEntry"=dword:0000000D
"011"="2005/06/14 11:32:36:0000
Stack loaded OK"
"010"="2005/06/14 10:53:24:0000
Stack loaded OK"
"009"="2005/06/14 10:34:32:0000
Stack loaded OK"
"008"="2005/06/14 09:59:58:0000
Stack loaded OK"
"007"="2005/06/14 09:24:55:0000
Stack loaded OK"
"006"="2005/06/14 09:00:12:0000
Stack loaded OK"
"005"="2005/06/14 08:44:59:0000
Stack loaded OK"
"004"="2005/06/14 02:44:57:0000
Stack loaded OK"
"003"="2005/06/14 02:39:10:0000
Stack loaded OK"
"002"="2005/06/14 02:23:11:0000
Stack loaded OK"
"001"="2005/06/14 01:52:17:0000
Stack loaded OK"
"000"="2005/06/14 01:49:39:0000
Stack loaded OK"
"015"="2005/06/14 01:23:36:0000
Stack loaded OK"
"014"="2005/06/14 01:21:13:0000
Stack loaded OK"
"013"="2005/06/14 01:05:59:0000
Stack loaded OK"
"MaxEntries"=dword:00000010
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Filters]
"InquiryScanMode"=dword:00000002
"WhoAllowedToConnect"=dword:00000000
"AllowOthersToDiscover"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\General]
"UseIconView"=dword:00000001
"RadioInitRunMode"="Auto"
"StackMode"=dword:00000001
"DefaultPropertiesDll"=""
"DefaultStatusDll"=""
"UnnamedDeviceName"="<No Name>"
"NoSleepingWhileConnected"=dword:00000001
"MaxSimultConnections"=dword:00000007
"CountryCode"=dword:00000000
"SecurityType"=dword:00000002
"MinorClass"=dword:00000010
"UsePocketPCName"=dword:00000001
"DeviceName"="Qtek-2020"
"AutoDiscovery"=dword:00000000
"Bdaddr"=hex:00,00,00,00,00,00
"BtWLANCoexistance"=dword:00000000
"EnableAFH"=dword:00000001
"EnableModuleSecurity"=dword:00000001
"GetRemoteNameBeforeConnectionAccept"=dword:00000001
"LicenseKey"="E3E534E19B3E82141321561D913215633CC92760F687E82F"
"ModuleSecurity"=hex:00,00,00,00,00,00,00,00,00,00,00,00,00,00,00,00
"PnpId"=""
"PowerControlLibrary"="Auto"
"RadioInitLibrary"="TIBinaryParser.dll"
"RadioInitPostLoadScript"="Roadster_Init_Script211.bts"
"RadioWLANCoexDisableScript"=""
"RadioWLANCoexEnableScript"=""
"TransportLibrary"="BtCeBCSPTrans.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Platform]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Platform\PowerMode]
"ActiveProfileMask"=dword:00000000
"InactivityHandling"=dword:000000BE
"KeepPowerOnMask"=dword:E0000001
"PowerOffState"=dword:00000003
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\SerialTransport]
"BaudRate"=dword:000E1000
"ByteSize"=dword:00000008
"Device"="COM"
"FlowControl"=dword:00000000
"Parity"=dword:00000002
"Port"=dword:00000006
"StopBits"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services\0001]
"UserInstalled"=dword:00000000
"ComPortNumber"=dword:00000005
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001101-0000-1000-8000-00805F9B34FB}"
"Name"="Bluetooth Serial Port"
"SecurityId"=dword:00000001
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001101
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services\0002]
"SaveInPIM"=dword:00000001
"SendBusinessCardOnRequest"=dword:00000001
"AcceptNotes"=dword:00000001
"AcceptEmailMessages"=dword:00000001
"AcceptCalendarItems"=dword:00000001
"AcceptBusinessCards"=dword:00000001
"InboxDirectory"="My Documents"
"DefaultBusinessCard"=""
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001105-0000-1000-8000-00805F9B34FB}"
"Name"="OBEX Object Push"
"SecurityId"=dword:00000005
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001105
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services\0003]
"FlistFormat"=dword:00000000
"Root"="My Documents"
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001106-0000-1000-8000-00805F9B34FB}"
"Name"="File Transfer"
"SecurityId"=dword:00000006
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001106
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services\0004]
"Description"="Net"
"NetworkMode"=dword:00000001
"Auto"=dword:00000001
"PropertiesDll"=""
"StatusDll"=""
"GUID"="{00001102-0000-1000-8000-00805F9B34FB}"
"Name"="Network Access"
"SecurityId"=dword:00000002
"Encryption"=dword:00000001
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"UUID"=dword:00001102
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services\0005]
"Name"="Voice Gateway"
"GUID"="{00001112-0000-1000-8000-00805F9B34FB}"
"UUID"=dword:00001112
"Authentication"=dword:00000001
"Authorization"=dword:00000000
"Encryption"=dword:00000001
"SecurityID"=dword:0000000C
"Auto"=dword:00000001
"Enabled"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\Services\0006]
"UUID"=dword:00001103
"Authorization"=dword:00000001
"Authentication"=dword:00000001
"Encryption"=dword:00000001
"SecurityId"=dword:00000000
"GUID"="{00001103-0000-1000-8000-00805F9B34FB}"
"StatusDll"=""
"PropertiesDll"=""
"Auto"=dword:00000000
"ModemComPortNumber"=dword:00000001
"ModemComPortString"=""
"FlowControl"=dword:00000000
"Baudrate"=dword:0001C200
"SPPServiceName"=""
"Name"="Dialup Networking Server"
"SPPEnabled"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface]
"PhoneWizAllServices"=dword:00000001
"DefaultPANMode"=dword:00000001
"DeviceName"=""
"FarEastFonts"=dword:00000000
"TrayIcon"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\DeviceIcons]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ConnectionMenu]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ConnectionMenu\AddIns]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ConnectionMenu\AddIns\HfpSetDefault]
"Command"=dword:00000002
"Connected"=dword:00000000
"MenuItem"="Set as preferred hands-free"
"Plugin"="HandsFree"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ConnectionMenu\AddIns\HfpSettings]
"Command"=dword:00000001
"Connected"=dword:00000002
"MenuItem"="Hands-free Settings..."
"Plugin"="HandsFree"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ServiceIcons]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ServiceIcons\HandsFree]
"Icon"="btwizardhfp.dll,28132"
"IconConnected"="btwizardhfp.dll,28133"
"UUID"=dword:0000111E
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ServiceIcons\AV]
"Icon"="btwizardav.dll,32015"
"IconConnected"="btwizardav.dll,32014"
"UUID"=dword:0000110B
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\BtConfig\UserInterface\ServiceIcons\Hid]
"Icon"="btwizardhid.dll,25513"
"IconConnected"="btwizardhid.dll,25512"
"UUID"=dword:00001124
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard]
"ConnectTo"="ActiveSync with NERFIAUX"
"ConnectToName"="NERFIAUX"
"ConnectToBDA"=hex:00,0A,3A,54,98,71
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns]
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\ActiveSync via Bluetooth]
"Description"="btrez.dll,29026"
"Dll"="btwizardprofiles.dll,4"
"Icon"="btrez.dll,29083"
"Order"=dword:0000000B
"Title"="btrez.dll,29025"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\Bluetooth File Transfer]
"Description"="btrez.dll,29028"
"Dll"="btwizardprofiles.dll,5"
"Icon"="btrez.dll,29091"
"Order"=dword:00000014
"Title"="btrez.dll,29027"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\Business Card Exchange]
"Command"="WindowsBTBusinessCard.exe"
"Description"="btrez.dll,22763"
"Icon"="btrez.dll,22132"
"Order"=dword:0000003C
"Title"="btrez.dll,22762"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\Connect to the Internet]
"Description"="btrez.dll,29024"
"Dll"="btwizardprofiles.dll,1"
"Icon"="btrez.dll,29079"
"Order"=dword:00000028
"Title"="btrez.dll,29023"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\Explore a Bluetooth device]
"Description"="btrez.dll,29022"
"Dll"="btwizardprofiles.dll,0"
"Icon"="btrez.dll,29067"
"Order"=dword:00000046
"Title"="btrez.dll,29021"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\Hands Free]
"Description"="btrez.dll,28002"
"Dll"="btwizardhfp.dll"
"Icon"="btwizardhfp.dll,28129"
"Order"=dword:00000009
"Title"="btrez.dll,28001"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\PAN]
"Description"="btrez.dll,29084"
"Dll"="btwizardprofiles.dll,2"
"Icon"="btrez.dll,29097"
"Order"=dword:00000032
"Title"="btrez.dll,29082"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\AV]
"Description"="btrezav.dll,32002"
"Dll"="btwizardav.dll"
"Icon"="btwizardav.dll,32002"
"Order"=dword:00000005
"Title"="btrezav.dll,32001"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Connection Wizard\AddIns\Hid]
"Description"="btrezhid.dll,25501"
"Dll"="btwizardhid.dll"
"Icon"="btwizardhid.dll,25511"
"Order"=dword:000000FF
"Title"="btrezhid.dll,25500"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Locations]
"CurrentLocation"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Locations\0000]
"Name"="Default"
[HKEY_LOCAL_MACHINE\SOFTWARE\WIDCOMM\Version]
"RadioLmpSubVersion"=dword:000001E7
"RadioManufacturer"=dword:0000000A
"RadioLmpVersion"=dword:00000001
"RadioHciRevision"=dword:000001E7
"RadioHciVersion"=dword:00000001
"Software"="1.0.0.3900"
[HKEY_LOCAL_MACHINE\Services\HandsFree]
"Keep"=dword:00000001
"Description"="Hands Free Service"
"DisplayName"="HandsFree"
"Context"=dword:00000001
"Index"=dword:00000002
"Prefix"="APP"
"Order"=dword:00000008
"Dll"="HandsFree_Dll.dll"
Thx

hum doesnt read all that but
one thing i did find is that in my xda2 radio version 1.18 didnt work well with a jabra 250 (not the V one ) so i downgraded radio to 1.17 and the problem solved jabra250 works ok
i dont know if its related or not just it worked
you can try that for yourself and if doest work put 1.18 back aggain

can we hear music over bluetooth?
can we hear music through bluetooth by playing windows media player (like nokia phones)

can we hear music over bluetooth?
can we hear music over bluetooth headphone?

Audio over bluettoth
I'm looking into this same issue, and there's another post also..
http://forum.xda-developers.com/viewtopic.php?t=22817
is is possible that someone couold PM me the HTC_PCM_Routing.dll
I have almost the same registry values for te Widcomm branch, but the key with that DLL mentioned is missing.... I can add the key, but need the DLL.

Related

Hermes GPS - Technical Discussion, FACTS ONLY. W.I.P.

[V speaking: PLEASE do not use this thread for rumour or ideas. This thread is for FACT only. Use this thread for ideas etc. Thanks!]
i know its not common practice to do this, but....
i hope this will be the place for the technical discussion of our journey to implement the gps module.
please no non-technical posts, only research here. use the other thread for theories about missing antennas and crippled chips..
this will be a moderated thread.. (sleuth ? ) from Sleuth: I'll make sure of it. PM me with posts you don't think belong here dutty
if you want to participate:
the dumped rgu( reg files ) can be found here:
http://forum.xda-developers.com/attachment.php?attachmentid=33852&d=1170260634
both hive files (default reg files) converted to ascii human readable format can be found here:
http://forum.xda-developers.com/attachment.php?attachmentid=33847&d=1170257783
my last post with information was:
bobstarina said:
dutty
I'm using Radio ROM 1.22.01.01.
I'm affraid of using 1.29 because of 1.008 loader in it.
Sleuth255
The situation with drivers is not good. It seems to me that we will need all of radio related DLLs from Trinity but at this moment my Hermes is not working propertly with Trinity's RILGSM.DLL.
Click to expand...
Click to collapse
bobstarina.. i have replaced the following dlls successfully (can be loaded and working properly):
-unimodem.dll
-gpsid.dll
-gpschannel.dll
-gpsapi.dll
-rilgsm.dll
-serialusbfn.dll
-serialUSBFnModem.dll
i tried to replace:
-ril.dll ( phone is unable to start, alot of services need to be started manually: sound, gsm codec etc. - they work properly but the phone is not working, i assume it depends on another dll or service )
-serial_cmd.dll ( can be loaded manually, crashes the device after a few minutes, probably depends on the ril.dll )
-cellcore.dll ( contains the entire API/OS functions related to the telephone. error: OS won't bootup, i assume the reason is that the replaced cellcore.dll hasn't got the proper signing so it would require a manual load but at that time a manual load is not possible )
unfortunately i still cant get the gps to respond... damn..
i have compiled this gps c# application.. it's from the wm5.0 sdk, it makes use of the wm5.0 intermediate gps drivers.. can somebody please test it on the trinity so we have a proper application as testing ground.
usage: unzip both files ( the dll+the exe ) into a directory on your ppc.
goodcompany.. thanks for the offer, can you still read output on the screen or is the device totally broken?
--- we really need the help of a trinity user.. we need to trace the whole process of an application talking to the gps module..
my first question to those (gps'd)trinity users that want to help would be:
whats the bootloader gps nmea output on your device??
grabbing the output is very simple, you won't loose any data on your device:
-put your device into bootloader mode (on the hermes it's left ok, powerbutton + stylus reset)
-kill the activesync process on your windows xp computer ( kill wcsecomm.exe + rapimanager.exe via taskmanager )
-unzip mtty and start it, as connection select the usb driver.
-a terminal will open
-type: "rtask b" enter
-"ate1" enter
-"atv1" enter
then wait until you see output on your terminal. then type:
-"[email protected]" enter
grab some input, leave the device alone for a few minutes.. then save the output (file->save) from mtty and attach it to your post.
thank you!
edit:
second question, i really need a registry dump of a trinity gps device. could somebody please dump the whole registry - but please make sure that there is no personal information stored on the device.
---
okay i've just created my own registry dump from the *.hv files that are in the romdump thats floating around.. but it looks like this is from a test rom because the gps applet seems to be disabled:
"[HKEY_LOCAL_MACHINE\ControlPanel\GPS Settings]
"Hide"=dword:1
"
pof, was that dumped rom you pointed me to the current released dopod rom?
interesting, i have found those strings inside the rilgsm.dll using a hexeditor:
Code:
[D :: VIRSER_COM] [D :: SERIAL_CMD] [D :: FRONTLIGHT] [D :: LED] [D :: PSM ] [D :: GPS] [D :: RIL] [D :: SIR ] [D :: FIR] [D :: CF] [D :: SERIAL_BT] [D :: SERIAL] [D :: AUDIO] [D :: BACKPACK] [D :: WLAN] [D :: SD] [K :: KERNEL] [D :: SPI] [D :: BATTERY] [D :: TOUCHP] [D :: KEY] [D :: I2C] [D :: MISC] [D :: CAMERA] [D :: USB_HOST] [D :: USB_FUNCTION] [D :: Display]
this looks like devicedrivers and , i can find most of these in the registry i got
for example:
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\OEM_Misc]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\GPSChannel] (gps)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial] (serial_cmd.dll)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\CIF]
etc. but i cannot find anything that's close to "virser_com" sounds like "Virtual serial" -> gps port??
maybe the reason i cant find it is that this is a preproduction dump...
Sleuth255 said:
@dutty: Trinity bootloaders don't have access to the radio command interpreter. The "rtask b" command is missing....
it's never easy damnit....
Click to expand...
Click to collapse
damnit....
pof, i assume that's the rom the trinity users are flashing to enable gps on their device.. is there a gps tool included in the ext rom?
yesterday night i've played around with the at debug feature of the hermes with all trinity dlls in place.. looks like there's really only one link missing check it out:
the communication between GPSAPP->GPSCHANNEL.DLL->RILGSM.DLL->RIL.DLL works without any problems, but the commincation from the ril to the gpsapp doesn't seem to work.. i don't know why.. yet:
check it out:
Code:
1:44:0 Rx:+CSQ: 6,99\r\n0\r
1:44:0 Rx:@HTCCSQ: 2\r\n
1:44:4 Tx:[email protected]=1,44,3,2007,1,31\r
1:44:4 Rx:0\r
1:44:10 Tx:AT+CSQ\r
1:44:10 Rx:+CSQ: 7,99\r\n0\r
1:44:20 Tx:AT+CSQ\r
1:44:20 Rx:+CSQ: 7,99\r\n0\r
1:44:21 Tx:[email protected]\r
1:44:21 Rx:0\r
1:44:23 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:23 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:23 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:23 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:23 Rx:,,N,,K*4E\r\n
1:44:24 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:24 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:24 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:24 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:24 Rx:,,N,,K*4E\r\n
1:44:25 Rx:NMEA$GPGSV,1,1,00*79\r\n
1:44:25 Rx:NMEA$GPGGA,,,,,,0,,,,,,,,*66\r\nNME
1:44:25 Rx:A$GPRMC,,V,,,,,,,,,,N*53\r\nNMEA$GP
1:44:25 Rx:GSA,A,1,,,,,,,,,,,,,,,,*32\r\nNMEA$
1:44:25 Rx:GPVTG,,T,,M,,N,,K*4E\r\n
1:44:26 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:26 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:26 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:26 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:26 Rx:,,N,,K*4E\r\n
1:44:27 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:27 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:27 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:27 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M,,N,,K*4E\r\n
1:44:28 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:28 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:28 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,
1:44:28 Rx:M,,N,,K*4E\r\n
1:44:29 Tx:AT+CSQ\r
1:44:29 Rx:+CSQ: 7,99\r\n0\r
1:44:29 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:29 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:29 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:29 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:29 Rx:,,N,,K*4E\r\n
1:44:30 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:30 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:30 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:30 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:30 Rx:,,N,,K*4E\r\n
1:44:31 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:31 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:31 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:31 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:31 Rx:,,N,,K*4E\r\n
1:44:32 Tx:[email protected]\r
1:44:32 Rx:[WCDMA] GPS: END\r\n
1:44:32 Rx:0\r
1:44:32 Tx:[email protected]\r
1:44:32 Rx:0\r
1:44:34 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:34 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:34 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:34 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:34 Rx:,,N,,K*4E\r\n
1:44:35 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:35 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:35 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:35 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:35 Rx:,,N,,K*4E\r\n
1:44:36 Rx:NMEA$GPGSV,1,1,00*79\r\nNMEA$GPGGA,
1:44:36 Rx:,,,,,0,,,,,,,,*66\r\nNMEA$GPRMC,,V,
1:44:36 Rx:,,,,,,,,,N*53\r\nNMEA$GPGSA,A,1,,,,
1:44:36 Rx:,,,,,,,,,,,,*32\r\nNMEA$GPVTG,,T,,M
1:44:36 Rx:,,N,,K*4E\r\n
1:44:37 Tx:AT+CSQ\r
1:44:37 Rx:+CSQ: 7,99\r\n0\r
1:44:37 Tx:[email protected]\r
1:44:37 Rx:[WCDMA] GPS: END\r\n
1:44:37 Rx:0\r
1:44:47 Tx:AT+CSQ\r
1:44:47 Rx:+CSQ: 7,99\r\n0\r
1:44:57 Tx:AT+CSQ\r
1:44:57 Rx:+CSQ: 7,99\r\n0\r
1:45:3 Tx:[email protected]=1,45,3,2007,1,31\r
1:45:3 Rx:0\r
Click to expand...
Click to collapse
lets get back here..
i noticed that my device crashes when its low on battery and the rilgsm.dll is loaded... we really need to figure out all depending drivers, services and other dlls...
Temporarily stickied.
V
dutty
Now I'm deep inside the RGU files from Trinity.
Some interesting findings:
1. HKLM\Comm\Security\SystemCertificates\Privileged Execution Trust Authorities - maybe we can put needed certificates into this branch for an automatic start of Trinity DLLs (another choice is to find the differences between RGU file and Hermes registry - who knows maybe there are some special certificates in Trinity's testing ROM?) I will check it later.
2. In RGU file there is the registry branch HKLM\Drivers\RegisteredDevice\BTD_COM9. I cannot find it in registry of my Hermes. I will try to add it and will see what happens next.
Added: After adding this entry and soft reset I'm able to start COM9 manually (as you remember I was not able to start it during last 2 days) !!!
3. \HKLM\Drivers\BuiltIn\QCTUSB_PCD9
In Hermes registry I have this branch empty.
In Trinity RGU file there are some keys inside this branch:
Dll="QCTUSB.DLL"
Prefix="PCD"
Index=9
DeviceArrayIndex=5
Tsp="Unimodem.dll"
Order=3
DeviceType=0
FriendlyName="Virtual PCD9"
DevConfig=20,00,00,00,05,00,00,00,10,01,00,00,00,4B,00,00,00,00,08,00,00,00,00,00,00
And SOMETHING INTERESTING:
\HKLM\Software\Microsoft\RIL\DataPort="PCD9:"
(In Hermes registry this key refers to "PCD1:")
Maybe this is what we looking for?
It looks like "virser_port" that you are looking...
In the registry of my Herm200 (Vario II, T-Mobile radio ROM, no Trinity radio flashed),
HKLM\Drivers\RegisteredDevice\BTD_COM9 points to btd.dll, flags =0, index=9, pefix is COM.
On my Hermes, \HKLM\Drivers\BuiltIn\QCTUSB_PCD9 has the same values as you found in the Trinity RGU file.
\HKLM\Software\Microsoft\RIL\DataPort="PCD9:" is indeed pointing to PCD1 on my Hermes.
It seems to me that the first two reg keys are identical to the original ones on my Hermes, only the contents of the .dll files may or may not differ between Trinity and Hermes.
edit: I did a search in my registry and found this in HKLM\Drivers\Active\63
HND=Dword 305664 decimal
Key=System/CurrentControlset/GPSIntermediateDriver/Multiplexer/ActiveDevice. Does this key point to the GPS Driver that works between the GPS and the OS? How is this in the trinity reg dump? Hmmm, I looked at it, it points to the GPSID.dll file. not much help I am afraid. let me know if I can help in any way.
is there anyone with a trinity who can post more Registry data pertaining to the COM9 port?
particularly what's in their QCTUSB_PCD9
Olipro said:
is there anyone with a trinity who can post more Registry data pertaining to the COM9 port?
particularly what's in their QCTUSB_PCD9
Click to expand...
Click to collapse
From the dumped trinity reg from the other thread (post 390)
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\QCTUSB_PCD9]
"DevConfig"=hex:20,00,00,00,05,00,00,00,10,01,00,00,00,4B,00,00,00,00,08,00,00,00,00,00,00
"FriendlyName"="Virtual PCD9"
"DeviceType"=dword:0
"Order"=dword:3
"Tsp"="Unimodem.dll"
"DeviceArrayIndex"=dword:5
"Index"=dword:9
"Prefix"="PCD"
"Dll"="QCTUSB.DLL"
Click to expand...
Click to collapse
cheers, and also; is there anything about COM9 (or the GPS) in HKLM\Comm
Olipro said:
cheers, and also; is there anything about COM9 (or the GPS) in HKLM\Comm
Click to expand...
Click to collapse
Nothing specific to COM9, port 9, virtual ports, or GPS. Only mention of generic USB Serial linkage which must be for synching.
If you need to, you can see the reg dump file @ http://forum.xda-developers.com/showpost.php?p=1121468&postcount=390
just another mention; but I have installed the privileged developer certificates on my Hermes and have signed the rilgsm dll with that signature; after doing this, the dll starts *AUTOMATICALLY*!
UPDATE2: GPS DLL's are signed; GPS device now starts automatically
UPDATE3: signed unimodem.dll and cellcore.dll; phone still functions with these installed
UPDATE4: signed serial_cmd.dll; this makes my device white-out and die... can someone find out what DLL's this one depends on so I can load it without crashing
Dear Olipro,
Could you put these signed files in this topic?
All other people involved in research will be very much grateful to you.
Olipro said:
just another mention; but I have installed the privileged developer certificates on my Hermes and have signed the rilgsm dll with that signature; after doing this, the dll starts *AUTOMATICALLY*!
UPDATE2: GPS DLL's are signed; GPS device now starts automatically
UPDATE3: signed unimodem.dll and cellcore.dll; phone still functions with these installed
UPDATE4: signed serial_cmd.dll; this makes my device white-out and die... can someone find out what DLL's this one depends on so I can load it without crashing
Click to expand...
Click to collapse
can you explain how you have signed those files with the developer certificate?? i have tried it myself with several different method (sign package from mamaich) and security configuration manager.. i just can't sign those beasts..
i think serial_cmd.dll depends on ril.dll but there is another missing dll...
edit: I did a search in my registry and found this in HKLM\Drivers\Active\63
HND=Dword 305664 decimal
Key=System/CurrentControlset/GPSIntermediateDriver/Multiplexer/ActiveDevice. Does this key point to the GPS Driver that works between the GPS and the OS? How is this in the trinity reg dump? Hmmm, I looked at it, it points to the GPSID.dll file. not much help I am afraid. let me know if I can help in any way.
Click to expand...
Click to collapse
yes the hermes implements the gps intermediate driver, with some small adjustments you can keep those entries.. not sure what they were, i have to check.. gpsid is the driver that implements the microsoft gpsapis that oyu can use in .net for example (check the tool i compiled in c#)
from the looks of everything, it really looks like they just crippled out some functions to make the hermes a non gps device.. i'm sure there were some protoypes with gps enabled..
elementary my dear friend
You might recall I posted something that allows you to disable the security on your PDA; this application also allows you to provision developer certificates on your PDA as well.
Basically, I provisioned the certs onto it, and then used signtool.exe (if you go to the file menu on the security program then it'll show you what folder it needs to be in) to sign the DLL files and plopped them on my PDA with Resco.
seems to be a massive breakthrough since ril.dll (and pretty much everything else) works perfectly and automatically though this method.
P.S: get the signtool.exe off Google; there's a Codeproject website that has it.
Olipro said:
elementary my dear friend
You might recall I posted something that allows you to disable the security on your PDA; this application also allows you to provision developer certificates on your PDA as well.
Basically, I provisioned the certs onto it, and then used signtool.exe (if you go to the file menu on the security program then it'll show you what folder it needs to be in) to sign the DLL files and plopped them on my PDA with Resco.
seems to be a massive breakthrough since ril.dll (and pretty much everything else) works perfectly and automatically though this method.
P.S: get the signtool.exe off Google; there's a Codeproject website that has it.
Click to expand...
Click to collapse
yeah.. thats the "security configuration manager".. it just wont work for me .. weird..
i have attached a file package, can you check if you can sign files with this? it even contains the proper certificate, copy it to your wince device and execute the cert.
dutty said:
yeah.. thats the "security configuration manager".. it just wont work for me .. weird..
i have attached a file package, can you check if you can sign files with this? it even contains the proper certificate, copy it to your wince device and execute the cert.
Click to expand...
Click to collapse
Yeah... it won't work till you get the Signtool.exe
Olipro said:
Yeah... it won't work till you get the Signtool.exe
Click to expand...
Click to collapse
care to attach ? i couldn't the file besides on msdn.. can you attach signtool.exe + your dev certificate?
dutty
Your tool is working for me. Successfully signed files with warning message "No timestamp".
You could attach other files you got from Trinity rom If this tool is not working for you.
I will sign all of them and attach them back.
bobstarina said:
dutty
Your tool is working for me. Successfully signed files with warning message "No timestamp".
You could attach other files you got from Trinity rom If this tool is not working for you.
I will sign all of them and attach them back.
Click to expand...
Click to collapse
yes i can sign them with it too, same warning but WCE does not accept the files as signed
Checked it right now. The same problem with me.
I found a problem in your signing tool.
For an option "-spc" in the BAT file you should use SPC certificate (not CER).
There is a tool in MS SDK for converting CER to SPC:
"cert2spc cert1.cer [cert2.cer … certN.cer] outputSPCfile.spc"
Do you have this tool? Can you post it here?
bobstarina said:
Checked it right now. The same problem with me.
I found a problem in your signing tool.
For an option "-spc" in the BAT file you should use SPC certificate (not CER).
There is a tool in MS SDK for converting CER to SPC:
"cert2spc cert1.cer [cert2.cer … certN.cer] outputSPCfile.spc"
Do you have this tool? Can you post it here?
Click to expand...
Click to collapse
http://www.codeproject.com/useritems/signcode.asp
when you try and sign a file with the Security tool, it shows the path it's looking in to find Signtool.exe; put it in there
bobstarina said:
There is a tool in MS SDK for converting CER to SPC:
"cert2spc cert1.cer [cert2.cer … certN.cer] outputSPCfile.spc"
Do you have this tool? Can you post it here?
Click to expand...
Click to collapse
cert2spc.exe is included in Microsoft .NET Framework SDK 1.1
C:/Program Files/Microsoft.NET/SDK/v1.1/Bin/cert2spc.exe

Instabile bluetooth during navi

Dear all,
I have always problems using blue tooth mouse and MDA III. During navigation the contact between mouse and device is lost, then, some minutes or seconds comes back, sometimes nothing happens. The distance between device and mouse is 10 cm. I use ROM 1.42.01 GER, RADIO 1.13.00, ExtROM 1.42.122 and BT 1.0.0.3900. Can anyone help?
I have the same problem on my BA with helmis WM6 and ger lang applied. Any suggestions out there?
I've no problems with my BT GPS from NaviLock.
My MDA (spec. c below) is running with WM6 from HEMLI on Radio 1.50.00 and these settings:
Start | Settings | Connetions | Bluetooth
- Devices: [Devicename] -> Serial Port {activated}
- Modus: Bluetooth activate {activated} // This Device visible for other {activated}
- COM-Ports: [Devicename] -> Port {COM8} // Secure connection {activated}
- Security: Authentication (Passkey) required {activated}
Start | Settings | Connetions | External GPS
- Program: GPS-Programport {none}
- Hardware: GPS-Hardwareport {none} // Baudrate {9600}
- Access: Manage GPS automatically {activated}
TomTom (navigation software)
- GPS-Settings: Other Bluetooth Device {COM8}
The only problem I've is with my BT Headset where I only can get the phone but not the sound from the navi...
[Edit:] Have also a look here and here...
Greets Rossi

[HOW-TO] Bluetooth tethering - Internet - ROOT req.!

Hello guys this is my first HOW to so please be a lil bit patient.
Questions and comments are welcomed of course!
Because I sent my SGS 2 for repair I took my older blackberry from my box with old garbage and tried to think about internet connection.
BB doesn't have wifi hotspot or something like this so how can we dial up internet connection from android?
Here we go.
Some stuff which must be installed before procedure:
1) ROOTed device
2) Busybox installed
3) Linux in loop device - maybe this is not needed but I am lazy ass and this was the fastest solution.
Procedure:
First of all we need to determine what is your bluetooth address (blackberry in my case).
For this one you have two options.
1) Determine it on your PC (I don't have windows so I will describe linux method only)
Turn bluetooth on your PC on.
Turn bluetooth on your cellphone and enable device discovery (device needs to be visible!!)
Open terminal and write:
Code:
hcitool scan
You will get something like this: " f4:0b:93:08:a0:16 "
Write it down you will need it for later use.
2) How to determin a bluetooth address on android
Because standart busybox and asus rom don't have hcitool we will need to use it from Linux environment (from loop device).
So if you haven't installed linux distro in loop file do it! It's up to you which one you preffere. I made following steps in ubuntu 12.04.
After installing ubuntu to the loop device start it and write from command line:
Code:
sudo apt-get update && sudo apt-get install bluetooth
Ok now we have tools for bluetooth installed.
Now turn on bluetooth on your android, turn on bluetooth on cellphone (discovery enabled).
chroot into your linux in loop and write:
Code:
hcitool scan
Write down your address like in the example above.
Now we need to determine which number of channel is dialup networking
This command is included in android terminal with busybox so you don't have to write it in the loop linux distro.
So write in the terminal like SU:
Code:
sdptool browse f4:0b:93:08:a0:16 <--- here is YOUR address of bluetooth cellphone
You will get something like this:
Code:
Browsing F4:0B:93:08:A0:16 ...
Service Name: Dialup Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Profile Descriptor List:
"Dialup Networking" (0x1103)
Version: 0x0100
Service Name: Voice gateway
Service RecHandle: 0x10001
Service Class ID List:
"Headset Audio Gateway" (0x1112)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Headset" (0x1108)
Version: 0x0100
Service Name: Hands-free
Service RecHandle: 0x10002
Service Class ID List:
"Handsfree Audio Gateway" (0x111f)
"Generic Audio" (0x1203)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 3
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Handsfree" (0x111e)
Version: 0x0105
Service Name: Advanced Audio
Service Provider: BlackBerry
Service RecHandle: 0x10003
Service Class ID List:
"Audio Source" (0x110a)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 25
"AVDTP" (0x0019)
uint16: 0x102
Profile Descriptor List:
"Advanced Audio" (0x110d)
Version: 0x0102
Service Name: AVRCP Remote Control
Service Provider: BlackBerry
Service RecHandle: 0x10004
Service Class ID List:
"AV Remote" (0x110e)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103
Service Name: AVRCP Remote Control Target
Service Provider: BlackBerry
Service RecHandle: 0x10005
Service Class ID List:
"AV Remote Target" (0x110c)
Protocol Descriptor List:
"L2CAP" (0x0100)
PSM: 23
"AVCTP" (0x0017)
uint16: 0x102
Profile Descriptor List:
"AV Remote" (0x110e)
Version: 0x0103
Service Name: SIM Access
Service RecHandle: 0x10006
Service Class ID List:
"SIM Access" (0x112d)
"Generic Telephony" (0x1204)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 4
Profile Descriptor List:
"SIM Access" (0x112d)
Version: 0x0102
Service Name: Phonebook Access PSE
Service RecHandle: 0x10007
Service Class ID List:
"Phonebook Access - PSE" (0x112f)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 5
"OBEX" (0x0008)
Language Base Attr List:
code_ISO639: 0x656e
encoding: 0x6a
base_offset: 0x100
Profile Descriptor List:
"Phonebook Access" (0x1130)
Version: 0x0100
#
In the example above we need to find dialup networking (you can grep it of course but the name can be a little different).
When you locate in your output this sevice (once again Dialup networking), look for channel.
In my case channel is 1.
Code:
Service Name: Dialup Networking
Service RecHandle: 0x10000
Service Class ID List:
"Dialup Networking" (0x1103)
"Generic Networking" (0x1201)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Write the channel number down.
Now you have your address and we won't need linux distro anymore (in this case )
Now run android terminal and write:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p1 /system
This will remount system for read and write.
Now download latest package of berry from this address:
https://bitbucket.org/tcolar/berry4all/downloads
and save it unpacked to somewhere on sdcard.
These configurations file are for blackberry but with some modifications it can work for another cellphones !!!!!!!!!
We will use configuration files in the folder config.
I am from Czech republic and I use T-Mobile.
It unfortunately means that I didn't have right dial configuration file in the config folder. So I took tmobile and tmobile-bb-chat and rename it to tmobilecz and tmobilecz-chat. After that I created folder on the sdcard called chatscripts and moved tmobilecz-chat there.
File tmobilecz needs to be moved to the /etc/ppp/peers.
So here is how to do that from android terminal:
Code:
su
cp /sdcard/download/berry/config/tmobile /etc/ppp/peers/tmobilecz
mkdir /sdcard/chatscripts && cp /sdcard/download/berry/config/tmobile-bb-chat /sdcard/chatscripts/tmobilecz-chat
Here is output of my configs:
Code:
/ $ su
# cat /etc/ppp/peers/tmobilecz
# was tested as working by Me
#460800
115200
/dev/rfcomm1
## No detach = PPP dialing stays in foreground
nodetach
#noipdefault
defaultroute
#nomultilink
#ipcp-restart 7
#ipcp-accept-local
#ipcp-accept-remote
#lcp-echo-interval 0
#lcp-echo-failure 99
#nopcomp
#noaccomp
#noauth
nomagic
#noccp
#crtscts
#pap-timeout 20
#pap-restart 20
#lcp-restart 10
#novj
user "gprs"
password "gprs"
usepeerdns
#debug debug debug
# does not exist in all pppd versions (osx)
#replacedefaultroute
connect "/system/bin/chat -f /sdcard/chatscripts/tmobilecz-chat"
and chat file:
Code:
/ $ cat /sdcard/chatscripts/tmobilecz-chat
TIMEOUT 10
ABORT 'BUSY'
ABORT 'NO ANSWER'
ABORT 'ERROR'
ABORT "NO DIALTONE"
ABORT VOICE
ABORT RINGING
SAY 'Starting GPRS connect script\n'
'' 'BBT_OS'
'' 'ATZ'
OK 'AT+CGDCONT=1,"IP","internet.t-mobile.cz"'
ABORT 'NO CARRIER'
SAY 'Dialing...\n'
OK 'ATD*99#'
CONNECT
~p
/ $
Now we have configs on the place last thing is that we need initiate dun connection between android and phone.
You can imagine it like a tunnel for dialing, so it needs to be established before dialing (pppd daemon).
Now we will use our determined bluetooth address and chanel with rfcomm command.
Android terminal like SU:
Code:
su
rfcomm bind /dev/rfcomm1 f4:0b:93:08:a0:16 1
rfcomm is utility for creating connecting, bind option will create device under /dev/rfcomm1, after bind is bluetooth address and at the end is 1 this is number of channel.
THIS COMMAND NEEDS TO BE RUN AFTER EACH REBOOT when you want to dial internet from your phone.
During this commnd you can receive request for pairing, do it of course.
After this command run as root pppd daemon with your config file, in my case named tmobilecz:
Code:
su
pppd call tmobilecz
If you have nodetach option in the peers config file like me, dial process stays in the foreground. You can close it by ctrl+c or closing terminal window.
After pppd you should receive ip address by the phone and connectio to the internet!!
WOALA!
If it is not working or you want to check what is going on during dialing install application ALOGCAT from market and filter messages with pppd only.
If you have difficulties write it down and I will try to help you.
After this setup everytime when you want connect to the internet through phone you have to write this in terminal (i created script for myself but it's up to you)
EXAMPLE:
android terminal:
Code:
su
rfcomm bind /dev/rfcomm1 f4:0b:93:08:a0:16 1
pppd file /etc/ppp/peers/tmobilecz
That's all!
When I have a time I will better format and color this post.
Now I have to cut my grass in the garden sorry
placeholder for future use
deadlocked007 said:
You do know you could've just used pdanet tablet
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
Code:
This software allows you to get FULL Internet on an Android tablet if you have an Android phone.
I don't have android phone so answer is no it can't be used.

Parrot asteroid smart error "user interface resolution [736x442] is not supported..."

Parrot asteroid smart error "user interface resolution [736x442] is not supported..."
Hi
I tried install igo primo on parrot asteroid smart but i have error "user interface resolution [736x442] is not supported..."
I tried to modify file multimode.ini, its look like this
Code:
[modes]
; mx=WidthMin..WidthMax, HeightMin..HeightMax,Folder
; OR
; mx=Width, Height ,Folder
m3=700..960,400..600,"800_480"
m4=440..600,680..960,"800_480"
m5=1024..1280,552..800,"1024_768"
m6=600..800,976..1280,"1024_768"
sys.txt
Code:
[rawdisplay]
driver=engine
screen_xy="auto"
or
Code:
[rawdisplay]
driver=engine
screen_x=736
screen_y=442
screen_x2=442
screen_y2=736
for info.ini i add the following line
736_442,442_736
whats's wrong?

Enable Bluetooth on Android VM

Hi everybody,
I have installed Android-x86 on a Virtual Box VM. I'm trying now to activate bluetooth capability on it.
I plugged-in my usb bluetooth dongle, I mounted it in my VM. Everything is ok so far.
On Android side, I can detect my dongle through the hciconfig and scan with it with hcitool.
The problem appears when I try to enable it in the graphic interface. It always shows me Bluetooth as off.
When I try to move the button on the right to activate it - nothing happens... It completely ignores my attitude.
It is also not possible to enable it through the applications: when an app asks me for an authorization to allow bluetooth, I authorize it to do so but it doesn't succeed.
The error I observe through the adb logs is as follows:
723338-01-21 11:02:23.948 1378 2327 D BluetoothManagerService: enable(com.android.systemui): mBluetooth =null mBinding = false mState = OFF
723474-01-21 11:02:23.948 1378 2327 D BluetoothManagerService: enable returning
723549-01-21 11:02:23.949 1378 1415 D BluetoothManagerService: MESSAGE_ENABLE(0): mBluetooth = null
723644:01-21 11:02:23.949 1378 1415 E BluetoothManagerService: Fail to bind to: Intent { act=android.bluetooth.IBluetooth }
But it doesn't help me much...
Please, if you have any idea how to solve this issue or progress in locating the problem, it would be great.
Thanks in advance for your time!

Categories

Resources