Can anyone help me with this problem
it is as following.
The bluetooth doesn't work if i try to sent a file to another phone via bluetooth. When i do it just in the same way i did it in the past with my MDA2 this was selecting the file and then choosing beam file then it would find al bluetooth devices.
With the MDA3 i have to make a connection with the other device via bluetooth manager ->browse files on a remote device then i can send a file to another device.
I will be verry happy if someone could help me
no one??1
Hi
Does anyone know how to setup IGuidance to work with WM5? I dont know how to work the BT ports at all. In 2003se, i could use the "scan" for bt data and it'd find the itrek gps unit but now it results in "no gps found". alternatively, what other gps software will work other than tomtom? I dont have tomtom =(
I've got version 2.1 and it seems to work with WM5. I add the gps to the bluetooth and then I create an incoming and outgoing port. I set my gps to port 6. In IGuidance it won't detect the gps but if you manually choose port 6 it will work just fine.
Andy
iGuidance 2.1.3 locks up my Wizard after several minutes. Grrr...
I am having all sorts of trouble with my PDA2K (WM5) and iGuidance. Although I think it has more to do with my bluetooth than anything. When I first started trying to get it to work it gave me coordinates that I was in Africa... Anyway, I think I am going to go back to 2003SE.
I'm having a different problem with iGuidance v2.1.3 on WM5. It installs and runs just fine. I use BT over COM6 and it seems fine. The problem I have is that the coordinates are off. The strange thing is that when I run GPSInfo (a separate app) it shows the correct coordinates - iGudiance thinks they are different and thinks I'm in a different location ( a few miles away).
I gave up on it and decided to go back to 2003SE (iGuidace v2.1 that worked perfectly fine on that configuration a long time ago). I followed teh steps to format/clean hive and did the down grade but am having a different problem. I've seen other people running into similar issues but I've not been able to get around it
"BTTrayCE - bluetooth can no longer be used because the license has expired" - I have tried a number of things using different BT stacks, 2003SE builds, reset (soft+hard) etc. Same problem!!! Argh - I'm stuck. I really miss my GPS!
Hi krille,
I also had similar problems with my SX66 and iGuidance and finally decided to go back to win 2003 because it worked fine with it. In WM5 my BT GPS receiver was never able to make a connection with iGuidance. But now I am having a different problem. I cannot downgrade even though I followed all the instructions correctly posted on the BA_Downgrade page. The upgrade program ( MaUpgradeUt_noID.exe ) does not seem to identify the rom versions and though it gives me a successfully upgraded message nothing had happened. I cannot downgrade now and stuck with WM5. Did any of you experience this when downgrading and can offer me any help.
DEK.
I've been upgrading/downgrading with differnt ROMs without any problems
Make sure to disable activesync on the pc and copy the nbf files as described in http://wiki.xda-developers.com/index.php?pagename=BA_Downgrade_WM5. Sometimes the verion info update to/from doesn't show between WM5/2003SE...
What happens when you click Update to continue?
BaUpgradeUt.exe worked
Thanks for your reply. I followed all the steps as described in the link you have sent but MaUpgradeUt_noID.exe did not upgrade (downgrade to 2003SE) though I got a message saying it did. Then I tried the file BaUpgradeUt.exe in PH20B folder and it did work. My device data file says my SX66 is in fact PH20B1 though. I do not know why MaUpgradeUt_noID.exe cannot update my ROM. Anyway I am happy now with my WM2003SE and iGuidance and BT all work faster with ROM update to 1.40. Now I am planing to customize my ExtROM to have all my personal settings and programs so that I want feel bad not having WM2005. Thanks for your willingness to help.
DEK.
Has anyone sucessfully installed MS Voice Command 1.5 with the New ROM (Jasjar ROM 1.30.68 WWE, Radio 1.09.00, extROM 1.30.153)? It installs but when I run it I get an error message and it disables itself. Any suggestions?
Thanks,
Sven
I have VC working fine with the new ROM - installed and worked just the same as before, so does the reg hack to enable operation via BT headset...........maybe if you try it again (re-install?) it will work
works fine on mine.
@sbatxda I had the same issue, VC would just close itself...what worked was a simple soft reset, I only figured this out after pulling out all my nose hair but hey it's never to late to learn Just do a soft reset an it should work as normal.
sorry, i assumed a soft reset was a foregone obvious solution and would be done automatically by anybody that has any knowledge of any microsoft system.
if in doubt, reset
youmeus: it worked ok on the new ROM then? I'll try to upgrade soon I guess then..
V
MS Voice Command 1.5
Thanks for the suggestions. I have made the register modification to get it to work with my BT headset and I have made multiple soft resets. I have some issue with the Voice Command install in that I have to first install the 1.0 version and then the 1.5 version; if I go directly to 1.5 the install tells me that there is no previous version and stops. This may create some issue, but this is also how I did it with the previous ROM version. I'll try a re-install again.
Regard,
Sven
@vijay555, yes I tried it again and it works ok now...but this new rom has a few issues that I am not comfortable with so I am going back to old rom once I get home later
@sbatxda, the better way to install VC is vis the cab file...just look for the cab file on your desktop eg C:\Program Files\activesyne\voice command\...etc and drag the cab to your PPC.
MS Voice Command 1.5 installation
Thanks youmeus,
Installing the .cab worked better.
I'm now having difficulties installing the .cab file with my ISP settings. It will not install on my device or storage card. This worked fine with the old ROM.
Ideas anyone?
Regards,
Sven
BT hack reg
@adesonic
installed and worked just the same as before, so does the reg hack to enable operation via BT headset...
Click to expand...
Click to collapse
please tell me the issue about this or send a link in a thread. VC 1.5 doesn't work with my BT headset.
DTR - try this - copied from another thread on here
MS Voice Command activation from BT headset
Now this one is sweet and makes the JASJAR the daddy for voice commands.
Install Voice Command to the default location.
Fire up a registry editor
Go to: HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand
Modify the string marked "path" from the default \Windows\SDDialer.exe to \Program Files\Voice Command\VoiceCMD.exe
Now, when you press your BT headset connect button, MS Voice command will fire up and take commands through the headset. It's reponses will be played through the headset too.
regs
sonic
@adesonic
oh, thatone I shure did try. But, having a Magician, I obviously had no success.
Maybe the fault is with the i-tech headset, which probably doesn't support connection.
I also had no luck with streaming audio to that headset, which some posts in other threads say is possible.
Thanx neverteless for your fast reply.
regards
Why haven't MS upgraded this software to a proper WM5 version yet?
OR have they and I haven't been paying attention?
Question: Earlier I and others have had problems with showing of contacts displaying a blank page.. Are you guys able to show contacts using Voice Command properly?
@eman, you have to add one the files form the VGA hack in your windows folder for VC to display contacts...I can't remember the name of the file so do a search on the board!
Great to know there's a solution.
Installing VC now
with the previous ROM there was the issue where it didn't work in laptop mode with the lid closed. Does VC work in that mode now, or are you guys using it in portrait mode?
It would be great if it did.
the file needed is outres.96.dll
no VC doesnt work when the clam is closed.
even on the latest release.
I just upgraded to AKU3_2 Beta 8. I seemed to be the most stable from the threads for A2PK (bluetooth stero which is a MUST have). Now I get an error on soft reset.
"The file "sddaemon" cannot be operened. Either it is not signed with a trusted certificate, or one of its components cannot be found. You might need to reinstall or restore this file."
Does any one know what this is about? Any way to fix it? I don't seem to have any problems with the device.
Also, I am getting a bit confused from posts. Is it possible to have MS Voice Command (routed through bluetoothe) and the Bluetooth stero on the same device? I realize I may have to tell it which one to use when, that's OK.
Thanks,
Hey guys, searched for a while now but couldn't find a similar thread to this related to our phone.
Suddenly,
my Wlan stopped working.
The issue is well known, it starts up, says "unable to scan for networks" and shuts down.
Same goes for setting up a W-Lan hotspot, starts up and immediately after it stops trying.
Both worked flawlessly before.
Since then, i tried cache wipes, reboots etc.
I am on the newest dz radio, using Virtuous Sense 2.0.0 for sum time now.
I found a workaround for a galaxy s that implied deleting the configuration file. This file seems to be at a different location on the desire z. Additionally, it probably has a different filename.
I was only able to find the file with the information of my saved wlan connections (WTF, why are the passkeys writting in clear text, not crypted in any way??) - this was the only file in the /data/misc/wlan directory.
I actually only want to full wipe as a last consequence,
since my phone's a bit shaky. Last year I had a severe issue with my sd-card slot (maybe someone remembers), which somehow disappeared month later without any interaction - pure magic. I even replaced the slot before with no improvement - suddenly the functionality returned.
I actually don't want to lose sd-card functionality again, so i even fear flashing a new rom.
I hope there is someone who can give me some input - maybe some config files are missing or stuff - i only hope its not hardware related.
In the meantime I also tried reflashing my rom and flashing the radio again,
no success
EDIT:
Okay screw it, I wiped and flashed my rom again - same issues,
Sounds like a hardware issue...
any ideas?
Greetings