Hi all,
I believe there's a lot of discussion generated on the merits and faults of the various Himalaya WM2003SE default Microsoft BT implementations.
I have looked at the 2.20 BT Registry and found the following settings:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\1]
"ProfileUsed"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Headset/Hands-Free"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\2]
"EventIndex"=dword:00000000
"SvcName"="Serial Port COM5"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\3]
"EventIndex"=dword:00000000
"SvcName"="ActiveSync"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\4]
"DUNsetup"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Dial-up Networking"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
"BTDUN.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
"BTSPP.dll"=dword:00000000
"Default"="Active Sync"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
"BTSPP.dll"=dword:00000000
"Default"="Serial Port"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000
I believe that the first 4 "CurAvailSvc" entries are used together with the BTBond_UI.exe that is called after BT pairing. For those who don't know what I am taking about, BTBond_UI.exe is called in 2.20 ROM after pairing to display a page with 4 checkboxes (Headset/Hands-Free, Serial, Dial-up Networking, ActiveSync). These 4 entries are missing from 2.02 and 2.06 registry.
In addition, comparing the registry against 2.02 and 2.06, you will find that 2.20 is using different BT files for enabling BT ActiveSync, Serial Port, Dial-up Networking and Headset/Handsfree:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
"btagsvc.dll"=dword:00000000
@="Handsfree"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"btagsvc.dll"=dword:00000000
"headset"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BthASPlugIn.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BthASPlugIn.dll"=dword:00000000
These particular registry entries are missing from 2.06 ROM but available in 2.02tl and 2.20 ROM:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAudioModule"="OEMExtDll.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Settings]
"IgnoreExternal"=dword:00000001
SIN has did his investigation and found that the second "AudioGateway" entry should not be updated as it prevents the mic from working when you paired your BT headset with "headset" mode instead of "handsfree" mode.
Under Magician BT registry, there is an additional entry:
[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001
You will find that this entry is not enabled in 2.02/2.06 or 2.20 ROM. Any ideas how it helps?
[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001
If I m not wrong
It is with 2.2 & 2.06 also
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAudioModule"="OEMExtDll.dll"
This above not in 2.2
& also in 2.2
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
@="Handsfree"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
"BTDUN.dll"=dword:00000000
About BTProfile...
darren_the said:
[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001
Click to expand...
Click to collapse
The entry is with 2.02/2.06, but my device with 2.06 has the entry as 0x0 instead of 0x1. I'm not sure what it does though.
Anyone has ideas why this is so?
darren_the said:
& also in 2.2
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
@="Handsfree"
"BTAGW.dll"=dword:00000000 (NOT btagsvc.dl)
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BTSPP.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
"BTDUN.dll"=dword:00000000
Click to expand...
Click to collapse
Yes, essentially the same thing that I found out. See the Services serial numbers, it's identical.
good job, this might help us, any recomendation for me? i have 2.02t the handsfree works to an extened but the mic as some of you know is not working, any recomendation for that? anyone think i should try ssomething from the above, i backup daily :lol:
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
henrylim said:
Hi all,
I believe there's a lot of discussion generated on the merits and faults of the various Himalaya WM2003SE default Microsoft BT implementations.
I have looked at the 2.20 BT Registry and found the following settings:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\1]
"ProfileUsed"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Headset/Hands-Free"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\2]
"EventIndex"=dword:00000000
"SvcName"="Serial Port COM5"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\3]
"EventIndex"=dword:00000000
"SvcName"="ActiveSync"
[HKEY_LOCAL_MACHINE\SOFTWARE\HTC\CurAvailSvc\4]
"DUNsetup"=dword:00000000
"EventIndex"=dword:00000000
"SvcName"="Dial-up Networking"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
"BTDUN.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
"BTSPP.dll"=dword:00000000
"Default"="Active Sync"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
"BTSPP.dll"=dword:00000000
"Default"="Serial Port"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
"BTAGW.dll"=dword:00000000
I believe that the first 4 "CurAvailSvc" entries are used together with the BTBond_UI.exe that is called after BT pairing. For those who don't know what I am taking about, BTBond_UI.exe is called in 2.20 ROM after pairing to display a page with 4 checkboxes (Headset/Hands-Free, Serial, Dial-up Networking, ActiveSync). These 4 entries are missing from 2.02 and 2.06 registry.
In addition, comparing the registry against 2.02 and 2.06, you will find that 2.20 is using different BT files for enabling BT ActiveSync, Serial Port, Dial-up Networking and Headset/Handsfree:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0000111E-0000-1000-8000-00805F9B34FB]
"btagsvc.dll"=dword:00000000
@="Handsfree"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001103-0000-1000-8000-00805F9B34FB]
@="Dialup Networking"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001108-0000-1000-8000-00805F9B34FB]
@="Headset"
"btagsvc.dll"=dword:00000000
"headset"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\00001101-0000-1000-8000-00805F9B34FB]
@="Serial Port"
"BthASPlugIn.dll"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Services\0350278F-3DCA-4e62-831D-A41165FF906C]
@="Active Sync"
"BthASPlugIn.dll"=dword:00000000
These particular registry entries are missing from 2.06 ROM but available in 2.02tl and 2.20 ROM:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\HandsfreeProfileOn]
@=""
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\AudioGateway]
"BTAudioModule"="OEMExtDll.dll"
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Bluetooth\Settings]
"IgnoreExternal"=dword:00000001
SIN has did his investigation and found that the second "AudioGateway" entry should not be updated as it prevents the mic from working when you paired your BT headset with "headset" mode instead of "handsfree" mode.
Under Magician BT registry, there is an additional entry:
[HKEY_CURRENT_USER\SOFTWARE\HTC\BTProfile]
"ON"=dword:00000001
You will find that this entry is not enabled in 2.02/2.06 or 2.20 ROM. Any ideas how it helps?
Click to expand...
Click to collapse
can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working
By the way, does anyone know about BlueTooth patch for BlueAngle ?
I still look around but found nothing.
Can we use that patch to make WM2003SE for XDA2 use Bluetooth more stable?
And thank for everyone who still work on this topic.
mmmmmmm
Is that why my active sync isnt working with BT?
I have upgraded my rom to the 2003SE and now i cant manage to sync by BT.
I can use my car BT though with the device without a problem, but i can activesyc by BT.
Also, when trying launch the destinator and use it with BT GPS it says the driver is occupied (or something).
Is the problem because of the 2003SE upgrade? should I downgrade and all will work just fine?
Please help me.
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
[quote="Rabia]
can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working[/quote]
Here it is.
problems with BT in all SE upgrades
I hve found the following problems with the BT stack on all the SE updates available
1) BT Headset reception is rubbish, tried the bluetrek G2 and Itech Clip and sound quality in the callers end is really quiet compare to the wm2003 original rom
2) BT Activesync does not work end of story
3) BT icon on today screen for headset keeps dissappearing
My opinion :-
Stick with 2003 and use SRS to rotate the screen to landscape until a fix is found for the SE os.
I have tried all versions of se 2.02, 2.06 (which really zapped my battery) and 2.20.07chs translated, all have they own lttle problems and none are 100% complete, however i have found 2.02 is probably the most stable.
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
henrylim said:
[quote="Rabia]
can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working
Click to expand...
Click to collapse
Here it is.[/quote]
thanks man but looks harder than i thought could you post your registery file, are you 2.20 chs?
Re: problems with BT in all SE upgrades
steverae said:
I hve found the following problems with the BT stack on all the SE updates available
1) BT Headset reception is rubbish, tried the bluetrek G2 and Itech Clip and sound quality in the callers end is really quiet compare to the wm2003 original rom
2) BT Activesync does not work end of story
3) BT icon on today screen for headset keeps dissappearing
My opinion :-
Stick with 2003 and use SRS to rotate the screen to landscape until a fix is found for the SE os.
I have tried all versions of se 2.02, 2.06 (which really zapped my battery) and 2.20.07chs translated, all have they own lttle problems and none are 100% complete, however i have found 2.02 is probably the most stable.
Click to expand...
Click to collapse
Your'e right, but....
ONLY SE really has a bare minimun support for handsfree devices.
No matter what you feel about WMP 10, ugly skins, or wrong keyboard maps, if you WANT or NEED handsfree your only choice is 2.XX
Not there yet...
Re: problems with BT in all SE upgrades
steverae said:
2) BT Activesync does not work end of story
Click to expand...
Click to collapse
I've got it working. I don't use to have BT USB dongle, but bought one since I've curious why so many thinks that BT ActiveSync is a gonna.
I did do some research on the Net, and found quite a number of gems from iPAQ users complaining about the same thingie.
Are u using XP SP2 or SP1?
Re: Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.
Rabia said:
henrylim said:
[quote="Rabia]
can some one post this file BTBond_UI.exe, i need to try mimicing everything on 2.20 version to see if its working
Click to expand...
Click to collapse
Here it is.
Click to expand...
Click to collapse
thanks man but looks harder than i thought could you post your registery file, are you 2.20 chs?[/quote]
I'm 2.06 base. I'm posting the 220 reg file, based on a conversion of default.fdf from the 220 ROM package. I do hope that I've the full reg converted since it appears that the file has a few things missing from the exported reg of an installed ROM.
Perhaps someone with 220 ROM installed can comment?
Re: problems with BT in all SE upgrades
henrylim said:
I've got it working. I don't use to have BT USB dongle, but bought one since I've curious why so many thinks that BT ActiveSync is a gonna.
I did do some research on the Net, and found quite a number of gems from iPAQ users complaining about the same thingie.
Are u using XP SP2 or SP1?
Click to expand...
Click to collapse
Would you be so kind and post here step by step config of Active Sync over BT, you did? There are probably more of us with this problem. :wink:
Thanks!
ACTIVESYNC BT WOES...
Hi Everybody!
I've noticed some increased troubles when, after having a BT equipped PC with Widcomm drivers, (the most usual) you upgrade to Win XP SP2.
Some of you are pointing to this, and it might be part of the trouble, but this is also true that versions 2.02 and 2.06 did permit me syncing via BT, and version 2.20 does not. So it looks like some kind of incompatibility among XP SP2 and some 2003 SE versions on our XDA.
Since I've been unable to upgrade my Widcomm BT drivers on my PC, I can't either assure this is only a Microsoft mess (Widcomm seems a bit guilty in my opinion)
Any guess or idea for getting BT ActiveSync back to work in 2.20?
This is a little OT, but the problem with XP SP2 and Widcomm drivers is that MS has added BT drivers to Windows that are digitally signed. As a result when you connect you BT device it will always install the MS drivers as default because the Widcomm ones aren't certificated. In order to get round this you have to remove the device from device manager and re-install it picking the drivers yourself.
widcomm drivers
Nice try, but, how did you get a workaround to the "license" message when reinstalling or upgrading the widcomm drivers? They don't even have SW upgrades in their web site!
PD I've been forced to restore my laptop hard disk to factory state when failing to get BT back to work after "upgrading" the widcomm drivers. This is crazy!
Re: widcomm drivers
Looking Glass said:
They don't even have SW upgrades in their web site!
Click to expand...
Click to collapse
Here's the Widcomm XP installation package extracted from the latest Logitech SetPoint 2.22 update for my diNovo KB & Mouse.
When installed as part of the Setpoint 2.22 upgrade, it provides the drivers for my Bluetooth wireless hub.
With 2.20XX, the BT ActiveSync won't initialise but I've had no problems using BT ActiveSync on 2.02.t1WWE, 2.06.00WWE & a merge of both.
:arrow: NOTE: I've only attached the Widcomm installation package, you'll still need to provide your own drivers for your BT Hub/Dongle.
Hope it helps: :wink:
Thanks
Thanks a lot Sin, will make another try.
In fact I tried installing the whole thing downloaded from the Logitech Site, but again it failed to install properly.
The BT in my laptop is factory built-in by Acer, and this is the annoying part, since Acer don't even provides an upgrade for it. In their site you can read: "Before installing XP SP 2, remove your BT drivers, and reinstall them after upgrading to SP 2", but the whole thing failed, and there were not way to get rid of the license message.
The Activesync problems only appeared after moving to 2.20.07 "translated", but it was the only way to solve the "dual-stereo" bug, so I feel mostly stuck: pick one of...
- No Hands free profile
- Dual Stero mic and earphone... or
- No BT Active Sync.
Take your bets ladies and gentlemen...
Will try with your drivers and help.
Regards.
:wink:
I used finalzero's 2.06.
Everything is working OK, but no handsfree BT profile?
ow can this be accessed?
To get handsfree to work in 2.06 you have to patch the os with a reg patch and some files, you can find these on the site here,
http://forum.xda-developers.com/viewtopic.php?t=13660&postdays=0&postorder=asc&start=50
Although when i tested this, my mic didn't work on the headset, so i reverted back to headset mode and everything is fine.
_________________
کíŋ
O2 XDA2
ROM: Merged 2.02.t1WWE & 2.06.00WWE
Radio Version : 1.18.00
ExtROM version : Sin.Merged.v1.0
1GB SD Card, WiFi, HBH-35 & Backpack
I'll try that.
Thanks
I have upgraded my OS from 1.23 to 2.06 (cingular OS only, no extROM).
Voice Command 1.5 installs properly but gives an error when launched
Voice Command 1.6 refuses to install at all
Both versions of VoiceCommand are French not US (though you would need to know that )
I have tried to do that just after a hard reset not to be polluted by my other apps, but I have the same result
I have tried with and without the "allow non-certified applications" flag from HTC tweak 2.0. Same result...
I got 1.5 to work on this os after a sprite restore with sbu from OS1.23, but the PIM database was corrupted. So I had to restore without it and get it back from ActivSynch. I do not think there should be a relationship between the 2 however...
1.5 was working after the twicks to remove Speed Dial as indicated on the Wiki (but with corruped PIM database)
But since I have a clean PIM database, no way to get Voice Command to work despite desinstall, clean any trace of it in the registeries and reinstall...
Any hints from the experts on the group?
That would be much appreciated as I am running out of ideas to try!
Odd,
It worked for me. Of course, knowing me I probably copied the CAB down to the device over USB and ran it there.
Of course, I'm using the english version since all the people I know have english names (joke).
Rob
I did try to install it thru a cab execution on the device as I do usualy (I like to keep all the cabs for easy reinstall if necessary)
Any hint why I get an exec error on 1.5? I would stick to it if it worked as I found some ways to get it to work with BT
Try setting all parameters in the regional settings to US. then reinstall. revert afterwards to French settings.
I have come across an other Microsoft product which needed US settings.
Simple.
Cingular OS2.06 is AKU3 = No VC1.5
MS Voice Command v1.5 will NOT work on AKU 3.x ROMs; VC v1.6 should work (does for me with Cingular 8500 w/OS 2.06)
Good Luck!
Cingular 8500
OS 2.06
Radio 1.27
drbowden said:
MS Voice Command v1.5 will NOT work on AKU 3.x ROMs; VC v1.6 should work (does for me with Cingular 8500 w/OS 2.06)
Good Luck!
Cingular 8500
OS 2.06
Radio 1.27
Click to expand...
Click to collapse
I second that! 1.5 would not work at all. Only 1.6 did on the latest Cingular AKU 3.3 ROM.
I have got SPV c550, I've changed windows from Wm 2003 to Wm 6 few times, I've used 3 versions of ROM, and I had the same problem on all of them:
I Can't send anything by bluetooth or irda. I can receive data but I can't send it.
I've tried Total Commander and file explorer, but it's just showing an error.
Is there any ROM of Wm6 or even Wm5 that will fix this errors?
p.s.
sorry for my english
nie wiem Pawle w czym tkwi problem. ja tez go mialem ale mi pomogl wlasnie total commander
Yeap
I've been having the same problem too! I'll let you know if I ever find a solution!
TC wysyła, ale tylko do "normalnych" telefonów. Nie mogę nic przez niego wysłać do żadnego SPV
I can send and receives ～
I used kingson's 1122 ROM.
But it's noly Chinese Language
U can link this :
http://www.ioicn.com.cn/forum/thread-243465-1-2.html
Click to expand...
Click to collapse
username : ming12
password : wmhmily3
It is my ioicn ID, I do not know if you can open that page. Whether or not to support Chinese characters
I am also sorry for my English.
I used googlr translator:
Code:
kingsen第三版自用版--豪华集成版:
Kingsen version of the third edition of their own - luxury integrated version:
Code:
http://www.isload.com.cn/store/zqa8pgjpggmcc/5x6_WM6_kingsen_V3_USED.rar/downlaod
I don't speak Chinese,are you talking about this ROM?
I used this bin.
But too many do not have access to integrated software, that comparison wasted space.
Try using moBlue, it works for me.
1) is BT working with all phones?
2) is IR working?
3) How can I get this moBlue rom?
4) Is bloetooth working in WM5 for c550?
Haven't tried BT with many phones - works with SE, HTC and Samsung.
Havent tried IR, but i suppose it works. Nobody had complaints.
MoBlue is software, not ROM.
I think there is no stable WM5 for Hurricane (C550)
So you can saend files by bluetooth to other smartphones?
My problem is that I can't send anything to other SPV, I can send files to "normal" phones by Total commander, but it's not working with smartphones.
I've installed moBlue and I don't think so it will help me:]
IR is not working at all in all the ROM's I tried, I,ve got error telling me something about "function socket"
p.s.
Again, sorry for my English
Problem sloved!
You've got to copy file manager from WM5, Bluetooth is working with all devices, even smartphones.
I'll upload files leater.
how did you do this?
is there any way to copy file manager or "album" from 2003 in WM6?
edit: i don't know the wm5 manager - but the wm6 haven't got some functions who the 2003er manager have!
Put files intu your /windows directory
http://rapidshare.com/files/77435167/Pulpit.rar.html
it worked for me!
p.s.
I don't know what functions WM6, WM5 or WM2003 have because I'm using Total commander
ok
is there any way to use 2003 File Manager and Album in WM6?
edit: you explorer work perfect
need album
pls - upload the album from Wm5