wm2003se bluetooth problem - MDA II, XDA II, 2060 ROM Development

I have upgraded my spv m1000 into 2.06.00WWE rom wm2003de
Everything is runnig great,very stable exept the bluetooth stack.
While it bonds perfect with my gps receiver,i cant send or rceive files from other bt devices (cell phones)What could be the problem...it always produce an error.Can i upgrade to widcomm bt stack?where do i find it?
Thank you

babisgr said:
I have upgraded my spv m1000 into 2.06.00WWE rom wm2003de
Everything is runnig great,very stable exept the bluetooth stack.
While it bonds perfect with my gps receiver,i cant send or rceive files from other bt devices (cell phones)What could be the problem...it always produce an error.Can i upgrade to widcomm bt stack?where do i find it?
Thank you
Click to expand...
Click to collapse
What is the error you have?
Do you succeed to pair the devices?
Do you use OBEX to transfer files?

it gives me an error tha says
"Cannot connect to the OBEX device.It is either not accessible or does not support selected service" when i try to send something from my ppc and when i try to send something to it windows just give an error tha cannot send

Can anyone tell me which version of WM2003SE has the bluetooth working?
My brothers himalaya was upgraded to 2.02t rom and now has the ear speaker working along with the bluetooth headset. Any advice will be greatly appreciated.

babisgr said:
it gives me an error tha says
"Cannot connect to the OBEX device.It is either not accessible or does not support selected service" when i try to send something from my ppc and when i try to send something to it windows just give an error tha cannot send
Click to expand...
Click to collapse
You have to check if the OBEX service is running. If not you have to start it.
Just use this tool
http://forum.xda-developers.com/showthread.php?t=280104&highlight=Free+Task+Manager
Go on the service tab, look for the OBEX service and checks if the service is running, if not start it and try.
Cheers,
.Fred

ok,i can see tha OBEX service is Stopped as well as BTAGSSVC(BAG0).I cant start it,it says "the device is in use by an active process and cannot be disconnected"

babisgr said:
ok,i can see tha OBEX service is Stopped as well as BTAGSSVC(BAG0).I cant start it,it says "the device is in use by an active process and cannot be disconnected"
Click to expand...
Click to collapse
Ok, get the name of the dll of the OBEX service then go to the processes tab,
select services.exe process, show the context menu, and select details.
In modules, checks if the dll is in the list?

ok
in services.exe i can see the obexsrvr.dll
maybe there is a problem with the file.Can someone post the dll to replace and see?

Related

Microsoft BT for Himalaya WM2003SE - 2.20, 2.02tl and 2.06WW

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:

First impressions with Magneto.

Pleasant interface.
ActiveSync 4 works through USB.
I cannot accede to Storage and ExtendedROM.
All buttons correctly work including camera and record.
Backpack dont works (Some change in the registry to fix that?)
ExtendedROMunlocker dont work.
Resco file explorer works.
Cabinstl works.
I can install programs from PC to PPC through USB (ActiveSync), in PPC (not in PC) screen ask about install in "Device" or "Storage Card".
Internet Explorer works trough USB (ActiveSync)
I cannot make hard reset but I can put it in bootloader mode.
I only have been one hour proving it.
At the moment he is everything.
HDJ80 said:
Pleasant interface.
ActiveSync 4 works through USB.
I cannot accede to Storage and ExtendedROM.
All buttons correctly work including camera and record.
Backpack dont works (Some change in the registry to fix that?)
ExtendedROMunlocker dont work.
Resco file explorer works.
Cabinstl works.
I can install programs from PC to PPC through USB (ActiveSync), in PPC (not in PC) screen ask about install in "Device" or "Storage Card".
Internet Explorer works trough USB (ActiveSync)
I cannot make hard reset but I can put it in bootloader mode.
I only have been one hour proving it.
At the moment he is everything.
Click to expand...
Click to collapse
Tell us something about the speed of the system and the space it takes...
Regards,
Primoz
p.s. Hope it will be soon released a version for the magician :wink:
Some screen captures
I have few installed programs but I think that the speed is very similar.
I do not understand very well as Magneto uses the memory, you have 14,57MB of ROM (storage) to install programs but you cannot install them in the RAM.
You can see 24,35MB of RAM but I believe that Magneto uses all the RAM, only who deal with form different those 24.35 from the 100 rest that we cannot see.
Resco file explorer cannot accede to Windows or temp but microsoft file explorer if it can.
Parrot CK3000 works fine.
About backpack: battery and TV/monitor output works but CF slot dont works.
Is it still using the MS bluetooth stack ? Any improvement on bluetooth function ?
Yes, it is MS BT, but now it appears a new menu, "COM Ports"
IMPORTANT: I have upgrade to Magneto using himaupgradeut_197.exe and the original nk.nbf file (without patching)
It has worked to the first time and I have not had any error of identification.
Also I have left the Storage empty before beginning the update.
what does the "patch" do anyway?
where did you get this version can you upload your version? or share it?
I heard that it i impossible to downgrade to 2003se is that true?
what do you advice: try it or not try it until its officially released(It is beta right?)
thx
OMEGA_ReD said:
where did you get this version can you upload your version? or share it?
I heard that it i impossible to downgrade to 2003se is that true?
what do you advice: try it or not try it until its officially released(It is beta right?)
thx
Click to expand...
Click to collapse
should try, you can downgrade 2k3SE later if you don't like 2k5
witch version shuld i take?
and shuld i patch it or something like that to be able to downgrade it later?
thx m8!
ishtangli said:
what does the "patch" do anyway?
Click to expand...
Click to collapse
It changes the filename of file "DevAuth.exe" in a way that it can't be executed anymore before start.
This application checks the hardware in some way to determine if the device is allowed to use the software. Maybe some of you have a device that matches this "authentication".
What about BT voice call?
Hi
"Parrot CK3000 works fine."
Does it mean that you can originate a call from BT device? Voice dial or smth. like this?
Or it just receiving calls and you can hear and microphone is working?
Making of voce calling over BT is one reason for me to upgrade...
can you give met the link for witch i can download it?
I have used the file nk.nbf from Xda-developers ftp.
I have returned to wm2003SE with himaupgradeut_197.exe and nk.nbf file of version 2.06.
ParrotCK3000 works just as with 2,06 version and the change of the registry.
Magneto is very interesting but it specially has a great failure, when you install many programs the system becomes slower, particularly with programs like betaplayer.
If the problem of the RAM use and the access to CF slot were solved, it would be a great system.
2.06 works with AS 4.
More news:
Magneto can be reinstall again using himaupgradeut_197.exe in bootloader mode.
If we installed the programs in the SD and left frees the memory of the PDA, the system goes much more fast.
Some programs cannot be installed in the SD and they settle in the PDA. Some programs that work in wm2003 and wm2003se not admit magneto, aborts the installation.
SPB pocket plus does not settle because it says that it is being tried to install on ppc2000 and aborts the process.

[Help] Cant run DrYAR Bluetooth v1.6 on atom AKU3.3.3

On my original Atom black version with wm5 can use DrYAR Bluetooth v1.6
but after i flash my o2 atom black to AKU3.3.3 cant use DrYAR Bluetooth v1.6, if use will effect ur bluetooth cant receive any thing.
i need a software to see when bluetooth send file got show process bar...
u all can download to test on ur pda
below got provide DrYAR Bluetooth v1.6 software
You're using bluetooth to transfer large files?
davidw89 said:
You're using bluetooth to transfer large files?
Click to expand...
Click to collapse
nope, actually when i still using original version atom black (i duno wat version, but is provide by o2 ) i still can use DrYAR Bluetooth v1.6, so when i send something to others ppl , or others ppl send file to me by phone, got show a processing bar by %.
after i flash to AKU3.3.3 , cant use it ....
if install already , then open bluetooth, i cant even receive file
Luckyghost said:
nope, actually when i still using original version atom black (i duno wat version, but is provide by o2 ) i still can use DrYAR Bluetooth v1.6, so when i send something to others ppl , or others ppl send file to me by phone, got show a processing bar by %.
after i flash to AKU3.3.3 , cant use it ....
if install already , then open bluetooth, i cant even receive file
Click to expand...
Click to collapse
I think you need to enable OBEX first. It is disabled by default to save on battery power. Please look for it in the ATOM WM5 AKU3.3.3 thread.
i already download the OBEX Server.cab and installed in my atom black
then i open the Dr.Yar Bluetooth v1.6.1, is still same problem
below have the picture
Luckyghost said:
i already download the OBEX Server.cab and installed in my atom black
then i open the Dr.Yar Bluetooth v1.6.1, is still same problem
below have the picture
Click to expand...
Click to collapse
Could you try the new ROM Aku3.3 final edition?
yes, i also tried install the Final edition ...
but still like that ...
can u all try to install Dr.Yar Bluetooth v1.6.1 on u all pda?

Bluetooth problem; it send files, but don't receive anything, using wm6.5 build 21501

hi man im actually using wm6.5 build 21501 rom, and the bluetooth doesnt want to run... a mean, i can send file to other equipment or devices, but.. just cant receive... im trin to use, other soft like.. bluezard bt crawler, dryar bluetooth persian bluetooth ... and no,.. i cant receive nothing, in the other device that trys to send me anithing says something like obex error... help...
Same problem
I am also facing the same problem. Tried many options still other device is getting OBEX error. Please help!

[Q]Help needed - Bluetooth not working

G'Day All,
I have a T9193 that's about 3months old and have run into a Bluetooth issue.
When I start up the phone I get the message "BTTrayCE.exe is not a valid Pocket PC application"
When I try to turn on Bluetooth from Settings I get the message "Can't turn on Bluetooth"
I have had Bluettoth working before and the only thing that I think could have caused this is a failed installation of Tom Tom on the first go. I did eventually manage to successfully install Tom Tom but still can't get my Bluetooth function to work. I've tried a soft reset but that has made no difference.
Anyone have any ideas? Any assistance would be greatly appreciated.
Cheers,
Franz
I would suggest a hard reset. It looks like a system file corruption to me.
tomtom jacks up the bt files by replacing them with outdated ones. go to this post and unzip the bt files and put them in your windows folder (either by activesync or total commander).
http://forum.xda-developers.com/showpost.php?p=3900678&postcount=8

Categories

Resources