Quote:
|
Originally Posted by JBabey
Quote:
|
Originally Posted by helmi_c
Simple, Microsoft bt stack is suck, and crappy bluetooth stack, Broadcomm is way way better and advance stack then ms bluetooth stack... The Speed (data transmission), A2DP (real A2DP experience), advance bt profile, File transfer, etc..
but for now, there's might be some issue with broadcomm stack since it was not design spesifically for Apache device (I hack/port it from Fujitsu Siemens T830 device), specialy the headset profile might still hv an issue... this is happens to all ported/hacked broadcomm stack for some device..
|
Helmi, is this something I can directly add as an OEM package... or do i need to go in and remove the MS bluetooth stack completely before integrating?
and of course, I appreciate the effort on getting this ported to apache! |
I think Make an OEM pack for Broadcomm is better if we not activated it by default, but if we do need to activated it as a default then we need to modify/disable ms stack.
this is how to disable MS bt stack by OEM style:
Code:
[HKEY_LOCAL_MACHINE\ControlPanel\Bluetooth]
"Redirect"=""
or
[HKEY_LOCAL_MACHINE\ControlPanel\Bluetooth]
"Redirect"="BTConfigCE.cpl"
[-HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth]
[-HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dcn]
[-HKEY_LOCAL_MACHINE\ExtModems\bluetooth_dun]
remove A2DP OEM pack, and apply the registry from the installer.. this is all will be more simple with new kitchen method...
the minus sign (-) is to delete the registry, in this situation the MS Bluetooth part.
or we can disable it by proxml file, by extended_rom style or any app that will choose wich stack to use, if such a app is available (app for parser an XML file will do fine I think), it will make the APACHE device that will hv two switchable workin bluetooth stack just by softreset it to switch between them... Isn't cool?
btw it also can simply done by a XML file for switching it.. U might study my DisableBroadcom.cab contain... the mechanism of remove/add/modify a file or registry is there..
talkin about this issue is need a new thread I think.. cos Broadcomm oem is kinda complicated but fun think to complish...