Hi I have the following issue when cooking both WM6.1 and WM6.5 ROM.
If I use a donor ROM with MS bluetooth stack, when I am trying the pair my WinXP netbook which is running Widcomm/Broadcom stack, my netbook can see the following service from my WM phone:
- ActiveSync
- Network Access Point (NAP)
- Dial-up Networking (DUN)
- OBEX Object Push
- Voice Gateway
If I use a donor ROM without MS bluetooth stack, but supplement the missing SYS part (SYS/Bluetooth and SYS/Bluetooth_0409) from another donor ROM which has MS bluetooth stack, then my netbook can only see the following service from my WM phone:
- ActiveSync
- OBEX object push
- Voice Gateway
The major show-stopper here is the missing of NAP. This is stopping me from moving to the latest shipped ROM I can get my hand on, as most recent WM shipped ROM all have been using Widcomm/Broadcom stack.
I am cooking for HTC Diamond. Due to the above issue, the best ROM I can get for HTC Diamond are:
- WM 6.1 build 21042 (donor from Topaz)
- WM 6.5 build 21887 (donor from Topaz) with native NK + OEMDrivers from pine ROM.
If someone has any solution to this issue, please help. Thanks.
I am impressed you have managed to get that far transplanting the MS BT Stack back into a device that natively has the Broadcom/Widcomm stack. I am keen to know what files/modules and registry entries you removed/added/changed from the OEMDrivers folder to get this far? I have a BT carkit and it simply doesn't get on well with the Broadcom stack on my custom-ROM'd LEO. With the same WM build and native drivers on my old Blackstone it works perfectly (with my BT carkit..).
Cheers
Andy
No, I am not. I am cooking for HTC Diamond, so my base ROM always has MS bluetooth stack. It's the donor ROMs that I am porting from that have Widcomm/Broadcom stack, because all the recent HTC WM builds always come with Widcomm/Broadcom stack.
Ah sorry, misunderstood. I thought the Diamond had the Broadcom stack natively.
If you have the MS BT stack natively then I'd have thought the MS BT components in the latest MS builds would work? I always use the 'full' MS Builds that are kindly packaged by DFT and not builds extracted from 'donor' ROMs.
Andy
I have always been sourcing donor ROMs from official ROMs releases. This way, I don't have to worry about beta OS, stability, time-bomb etc. Call me un-adventurous, but this is my preferred way of cooking and the source is legitimate, sort of ...
I would refrain from using unofficial/leaked MS build drops for the mean time if this issues can be resolved through other means.
Solved
I have found the answer to my own question.
It was caused by the DSM order in package.sof. For donor ROMs which don't have MS bluetooth stack, the package.sof will not contain the DSM UUID for SYS/Bluetooth and SYS/Bluetooth_0409. When the missing SYS are supplemented from another ROM, BuildOS will append their DSM UUIDs at the end, and so their RGUs will override the RGU from SYS/INTERNETSHARE and setup BT communication as PANU instead of NAP.
I analyzed packages.sof from Topaz ROM and SYS/INTERNETSHARE comes after SYS/Bluetooth.
As a result, I am now running my Diamond with WM6.5 Build 21913 ported from Leo 3.14.
Related
Maybe somebody can help me:
I try to install diffrent keyboards on my device (for Japanese Input, Large Button Input and so on).
I can see them all after installation, but I can not select one of them, when I try to select them it switch back to default Keyboard.
Any Idea how I could fix that problem?
Thanks
PS: I tryed SIPChange, but it did not work.
Another one hit the driver memory problem, brought to you by M$. Trinity is in particular vulnerable to this problem amongst other WM5 devices. I thought M$ fixed it many years ago with the introduction of WM2003 device - but I was wrong.
What OS you are using? WM5 or WM6?
i'm running wm5. today I managed in the safe mode to start one of SIP but thats no way to work. do you think it would change if I upgrade to wm6? to bad there is no official uprade... and, is wm6 fully supported by the Trinity? some where I read that the gps module is not supported by wm6 ..
Heard someone talked about that driver problem is less prominant in WM6 - but I am not sure - since I still don't find a reason to upgrade.
There ARE official WM6 for Trinity - for those Dopod machines. They said the official ROM from HTC is also coming at the end of the month.
The current official WM6 roms support GPS without problems - as with all latest cooked roms.
I'd suggest you go for WM6 to see if it fixes your SIP problem.
hi, I have made a small application to retreive nmea information from my bluetooth GPS on my HTC Tytn phone ( wm6 )
I developped it using microsoft visual studio 2008 pro avec wm6 pro sdk.
I would like to include a button to activate/desactivate the bluetooth from my application, any idear how I could do that plz ?
You'll find native functions and description in the SDK-Help.
Anyway, bluetooth is not simple to handle.
I'd recommend to use a freeware called 32feet to use bluetooth functions in .NET.
I's a library which does the wrapping of native DLL-functions to .NET.
You can find it on codeplex.com.
But keep in mind that it is not guaranteed to work properly, because there are 3-4 different bluetooth stacks on the market and the library does not work with all of them.
Hi,
if I good remeber someone on XDA have made some library to enable/disable BT/Wifi/Phone, and it was make in C# or VB... and there was near 1 or 2 month ago.
I don't know how to find his post but the good users could help you...
Sorry for this little help Hope you'll find !
I've been messing around with the 32Feet libraries (6.1 Touch Cruise with MS stack) and found them to be very useful and reliable so far. But the may be overkill for simply turning Bluetooth on and off. VJVolubilis (http://www.vijay555.com/?Releases:VJVolubilis) may give you what you want but it looks to be only compatible with the MS stack too.
SoftCoder
donzeze said:
hi, I have made a small application to retreive nmea information from my bluetooth GPS on my HTC Tytn phone ( wm6 )
I developped it using microsoft visual studio 2008 pro avec wm6 pro sdk.
I would like to include a button to activate/desactivate the bluetooth from my application, any idear how I could do that plz ?
Click to expand...
Click to collapse
Would like to help, but I like to work on your code. So if you can post it then I will see if I could put these buttons on
Did some research on my device/rom and found there are many dlls i dont have a use for like:
Drivers
- ircomm.dll (IR COM3)
- gpsid.dll (GPS)
- scard.dll (smartcard ????)
- bta2dpsnd.dll (a2dp)
Services
- bthidsvc.dll (BT HID)
- btagsvc (again BT a2dp)
- enroll.svc (certificates ?????)
This is just an example to probe my point as there should be more i dont know the use of and some dependent dlls.This could mean a little more ram and responsiveness since there could be fewer events for the Os to attend. I dont have a GPS, nor wireless headphones, had never used the IR...
Question: Its there a way of simply stop these dlls from loading into memory like we do in windows? pls im not going to cook a rom just to do that ...i dont care about the storage just need ram.
Thanks to any answer
HTC Tytn
ROM: Shamanix WM6 Ultimate v2 Final
RADIO: 1.48.00.10
History: VPA Compact (HTC Magician), Jornada 720
Hi,
I am learning to cook for legacy device HTC Prophet. I want to have my own base ROM, so I started with official WM 6.1 ROM from Kaiser (19214) and Elfin (19772). The OEM/Drivers was derived from the last official WM5 AKU 2.2 from Qtek S200.
Thanks to the wonderful community here, I was able to successfully port the XIP over and get my 1st booter. Everything seemed to work OK, bluetooth, GSM data/phone, Wifi, IR etc.
The only issue I have is Windows Live won't connect. I tried other SW, and they were OK with both EDGE data and Wifi (IE, SJPhone, OperaMini native, Jbed with OperaMini J2ME, PocketOutlook with Yahoo! emails etc.)
This happens with both donor ROMs, and it happens with both the Windows Live comes with the donor ROMs, or the CAB I downloaded from MS website. (to rule out RGU related porting issue.) Marketplace for WM6.1 won't connect, too.
I had tried searching for solution and there seemed to be similiar issue, but I wasn't able to get a solid solution.
I use BuildOS/PKGTool-based toolchain in my own commandline-based kitchen.
The last official WWE ROM which has Microsoft Bluetooth stack is Topaz ROM, both for WM6.1 (21042) and WM6.5 (21887). HTC Tachi also has MS bluetooth stack but this is not WWE. Thereafter all I can see that HTC shipped with Broadcom bluetooth stack.
Anyone know if there are more ROM with MS bluetooth stack? I haven't looked at Omnia2 and Sony Xperia ROMs.
Wowser, are you saying that the Topaz actually can use both the MS stack and the Broadcomm stack? Man, I've been trying to put the Broadcomm stack onto my Touch Pro, I think it really is possible now. Thanks!
It is not that easy as moving few files (I know, too bad ). I want MS bluetooth stack on my HD2, as it supports Bluetooth Mouse profile and with proper software it can show you cursor . Plus it has better A2DP sound and less c*aps out.
I have here also HP HX4700 that supports it and uses Widcomm /Broadcomm?/ BT stack, it has some kind of plugin for that. But I doubt it is compatible anyway, as this one is rather old (4 - 6 years).
OndraSter said:
It is not that easy as moving few files (I know, too bad ). I want MS bluetooth stack on my HD2, as it supports Bluetooth Mouse profile and with proper software it can show you cursor . Plus it has better A2DP sound and less c*aps out.
Click to expand...
Click to collapse
I actually think it's easier to put the MS stack onto another device than the Widcomm one. What you need is a device like the Topaz with the registry settings for OEMDrivers (for example Serial_btur**.dll) as well as a WM build that has the MS stack, and it should work. Of course what I'm trying to do is add the widcomm stack, so it might not be as easy as it sounds ^_^;
Xperia X1 is one of devices with ms stack.
as well as a WM build that has the MS stack
Click to expand...
Click to collapse
SYS build doesn't matter btw (if you don't delete anything from it).
ultrashot said:
SYS build doesn't matter btw (if you don't delete anything from it).
Click to expand...
Click to collapse
For a complete bluetooth experience, it's crucial to have the original "bluetooth" in the "Common" folder (OSKitchen). For example, I've worked with HTC builds that did not include that folder, thus breaking stuff like PAN visibility (because Broadcomm controlled that).
So, I've been looking through some Topaz ROMs, but I can't seem to find any with the Broadcomm stack. These are the ones I have tried:
Code:
RUU_Topaz_hTC_Asia_WWE_1.40.707.1_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship
RUU_Topaz_S2_hTC_Asia_WWE_2.53.707.4_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship
HTCPUREATTOriginalShipROM
I don't have a legendary connection speed, and thus I don't have the capacity to try them all, but which ones include the Broadcomm stack?
The list of ROMs I am able to get:
Code:
xda-diamond2-v2-16-207-3.exe
RUU_Topaz_HTC_RUS_1.39.411.1_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.exe
RUU_Topaz_S2_HTC_SPA_2.53.412.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Citrine_TMO_DE_2.13.111.3_radio_sign_topaz_61.42tc.25.31_4.49.25.05_ship.exe
RUU_Topaz_S2_HTC_WWE_2.53.405.5_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_PTG_2.53.410.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
HTC_Touch Diamond2_RUU_Topaz_S2_HTC_SPA_2.53.412.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_FRA_2.53.406.4_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
Topaz_HTC_WWE_EastEurope_1.39.479.1_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.rar
RUU_Topaz_S2_HTC_NLD_2.53.404.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
mda_compact_v.exe
RUU_Topaz_S_HTC_SPA_2.16.412.1_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe
RUU_Topaz_S2_HTC_SVE_2.53.413.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
HTCPUREATTOriginalShipROM.exe
RUU_Topaz_HTC_SPA_1.39.412.0_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.exe
RUU_Topaz_S_Vodafone_DE_2.16.162.3_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe
RUU_Topaz_S2_HTC_DAN_2.53.403.5_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_HTC_FRA_1.39.406.0_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.exe
RUU_Topaz_S_Telstra_WWE_2.31.841.6_Radio_Sign_Topaz_61.39tc.25.30_4.48.25.20_Ship.exe
RUU_Topaz_HTC_ITA_1.39.408.1_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.exe
RUU_Topaz_S2_HTC_NOR_2.53.409.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S_HTC_Asia_WWE_2.17.707.1_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe
RUU_Topaz_S2_HTC_ITA_2.53.408.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_WWE_EastEurope_2.53.479.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_HTC_WWE_1.39.405.2_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.exe
RUU_Topaz_Dopod_CHS_1.75.706.4_Radio_Sign_Topaz_61.27t.25.23_3.45.25.21_Ship_R1.exe
RUU_Topaz_S2_HTC_TUR_2.53.468.2_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_RUS_2.53.411.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_WWE-AFK_2.53.421.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
HTC Touch Diamond2_RUU_Topaz_S2_HTC_SPA_2.53.412.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S_Vodafone_DE_2.16.162.1_Radio_Sign_Topaz_61.44tc.25.32_4.49.25.17_Ship.exe
RUU_Topaz_HTC_GER_1.39.407.1_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19DE_Ship.exe
RUU_Topaz_S2_HKCSL_CHT_2.53.832.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_ELL_2.53.482.4_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HTC_GER_2.53.407.6_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_hTC_Asia_TW_2.53.709.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_hTC_Asia_India_de3G_WWE_2.54.1300.2_Radio_Signed_Topaz_61.44c.25.33_2.49.25.204_ESM7206A_Ship.exe
RUU_Topaz_S2_hTC_Asia_WWE_2.53.707.4_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_S2_HKCSL_WWE_2.53.831.3_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe
RUU_Topaz_hTC_Asia_WWE_1.40.707.1_Radio_Signed_Topaz_61.20t.25.10_3.43.25.19_Ship.exe
I can't delete posts? >_>
If its possible to get the MS stack working on the HD2 I would be a very happy bunny. I moved from a Blackstone to a HD2 and although the speed increase was fantastic there are some annoying issues and Bluetooth is the biggest. Other than the speed I was really happy with the Blackstone and everything just worked - slowly but worked...
Andy
ultrashot said:
Xperia X1 is one of devices with ms stack.
Click to expand...
Click to collapse
Do Xperia X1 official ROMs have higher build number then offical Topaz ROMs? I am trying to salvage the missing SYS parts for ROM cooking.
SYS/Bluetooth
SYS/Bluetooth_0409