Ok, first off, i am hoping someone somewhere has experience of using the sideshow for windows mobile on their touch pro II.
I am experiencing a lot of problems, mostly i cant get it working at all. The problems start when i pair the device over bluetooth!
When i pair vista installs all the drivers it needs but cant find the "Bluetooth Peripheral Device" drivers, and then when i explore the services vista finds for my touch pro 2 the sideshow box is there but un-checked, and then i check it and apply, and it has the same problem with not being able to find a peripheral device driver.
I then found the universal Bluetooth dotNet Sideshow drivers, and they installed successfully (i think). But now no device appears in the sideshow control panel in vista, even though in device manager is shows "HTC Touch Pro2 T7373" under the Windows Sideshow category.
Has anyone got this working? or has anyone encountered these problems? I would really like to see how sideshow is on my phone. Any help would be gratefully appreciated!
Ok, so i have solved it, even though over 45 of you lot looked and had no help, thanks for looking though. The solution was that the "Bluetooth Peripheral Device" that remains unfound needs the driver updating in the way outlined here:
http://www.computers.nepalesemap.com/index.php?topic=3.0
Then the sideshow application on the phone finds the vista machine. Then the wanted gadgets can be activated on the pc.
My hope of using this as an "inteligent" remote control and more is and was valid, apart from the limit of support and development for the mobile sideshow package. It works, but it crashes every time a large list is presented. I have no doubt this is because it is a preview release, but the date of the 0.01 version is dating back all the way too the 20th January 2009; and there seems to have been no updates to the mobile client since.
Does anyone in this vast comunity use sidebar and not have this crashing problem? and also is there anyone here with any news on the development of this product as i am still keen and interested!
Related
Dear All
Please help: I have an O2 XDA IIs which MS Activesync 4.1 does not detect, despite all my efforts during the last few days (I also have an old iPAQ 1940 which Activesync detects fine).
The XDA is from work, so could it be that it is somehow locked, and if so, how can I unlock it?
Also, as an alternative, can I sync the XDA with my PC via Bluetooth through the iPAQ's?
Any ideas will be gratefully received!
Many thanks in advance,
L
Hi there,
I've Looked through hundreds of forums and although I have seem similiar I haven't found a resolution to my exact problem.
Due to the fact that I've been trying to resolve this issue on and off all day it's probably something really simple... :roll:
HISTORY
PDA
Was running WM2003SE on a Xda IIS.
PC
ActiveSync 3.8 on Laptop with Windows 2000 SP4 and all updates. Laptop on a home LAN with router. No firewall software and have since removed all Spyware removal software, (after doing one last scan).
My Task \ Issue \ Problem
I wanted to to the upgrade to WM2005 and followed all the usual procedures. The one mistake I may have made was to install the very very latest 4.1 Activesync without removing 3.8. However at this stage my XDA was still on 2003SE and synced perfectly with 4.1 Activesync.
I performed the upgrade to WM2005 including patches and as far as the XDA is concerned everything appears to be working.
Activesync however doesn't work. Via the USB cradle Windows 2000 detected a device and under device properties it's was listed as Generic RNDIS, it's now listed as a windows mobile based-device. I don't have an entry in my network connections, although I think this only happens with Windows XP. I've tried uninstalling Activesync, removing the rapi.dll file, reinstalling etc, I even did the former and removed entries within the registry and running a registry fixer but to no avail.
I then decided the Bluetooth route but cannot sync via this method either. I can actually succesfully connect from PC to XDA and vice versa but cannot use these connections for Activesync.
I have another Hard Drive for this Laptop which I use for testing. I can simply shut down, swap drives and boot again to another build. The other build is also Windows 2000 with SP4 and pretty much nothing else. I've installed Activesync 4.1 onto this machine, plugged in the cradle and everything works fine.
So..... I know the XDA is fine, The cradle's okay and Activesync 4.1 actually works with my XDA OS. The problem is it doesn't work on one particular build. I believe this is actually a Activesync issue but due to some form of conflict with my build. It's currently out of the question for me to rebuild so my mission is to find out what's conflicting.
Just to summarise though..... Activesync 4.1 was working fine, I upgraded XDA to WM2003 to WM2005 and then it stopped. The other harddisk proves that Activesync does actually work with my XDA.
Pheeeew...... I hope somebody doesn't suggest lack of information.... :lol: :lol:
So the reason for the post?? Well if anybody else is having frustrations, (which I'm sure I'm not the only one judging my my searching), your not alone.
I think a lot of people's problems have actually been resolved by the latest version of Activesync, (4.1), and other people have resolved by sorting out the main culprit of firewalls.
For me though I'll keep searching..... if any of you can think of any other ideas I can use for diagnosing the problem I'll appreciate it.
Thanks in advance..... sorry for the waffle.....
RESOLVED
Okay.... During further searching I noticed people mentioning VPN clients interfering.
I did have SecureRemote VPN installed which I use for work purposes.
I uninstalled SecureRemote but had to uninstall & re-install Activesync again. This time it's working.....
I will, (but not tonight), re-install the VPN client and see what happens. If Activesync countinues to work then, apart from being happy, it's worth making a note of.
If it doesn't work then I'll start to investigate why...... I know the new active sync does some form of IP connection but I cannot accept that it won't work with VPN's installed.
use windows XP (SP2) ...
first install the activesyn and then restart your computer.
then attach your pocket pc with usb cable.
and try to connect.
its works for me...
Having been absent from the forum for a while (other handheld projects) I came back just in time to discover the renaissance period for Crossbow . I am completely in love with the Rom (despite the criticisms), its incredible how much faster it is than my last custom WM5 rom. Anyhow, my only issue is that I can't sync with my Vista RTM installation! I plug in my Exec, WMDC says connecting, and I briefly see the Make new partnership window morph in, then it disappears and the device is "disconnected" from wmdc, however there is still a usb connection. (Windows Media Player is also launched). Not sure what the issue is, I’m using Midget’s rom. Plenty of people in the forum seem to be using wm6 and vista fine together, so I wonder if there's something I’m not doing properly or if this is a known issue with a possible fix. Forum searching has yielded Nuclear pvt'ing a vista fix to someone. Appreciate any help/advice. Its not the end of the world, as I sync with an exchange server as well, but I would certainly like to have my laptop sync'ed with my Uni as well as be able to install apps off the PC instead of using a card reader or mailing cabs to myself.
take a look here :
http://forum.xda-developers.com/showthread.php?t=291268
install Windows Mobile Device Center Beta
appreciate the link, I went through that thread already too. First thing I did was install beta 3 so that I could sync my universal when I was using WM5. Since the upgrade, I can't sync. The initial connection screen pops up for a second, as I stated recognizing the pocketpc, but all of a sudden the connection terminates. I wonder if Its an old USB driver issue or something residual from being stuck at the bootloader until I ran the bootloaderfix.
Vista Sync Issues
Are you using the OneCare Beta Program for Vista? If so then you will need to edit the OneCare (not windows) firewall to use WMDC correctly, this is a known issue with OneCare.
see http://forums.microsoft.com/WindowsOneCare/ShowPost.aspx?PostID=815195&SiteID=2
Steps to enable WMDC for OneCare.
1 - Disconnect the device.
2- Launch the One Care Control Panel:
Click on "Change One Care Settings".
Click on the Firewall Tab.
3 - Open the following ports for all programs in the OneCare firewall:
port990: open inbound TCP
port999: open inbound TCP
port5678: open inbound TCP
port5679: open outbound UDP
port5721: open inbound TCP
port26675: open inbound TCP
4- Open the following programs in the OneCare firewall:
C:\Windows\WindowsMobile\wmdc.exe
C:\Windows\WindowsMobile\wmdHost.exe
C:\Windows\WindowsMobile\wmdsyncman.dll
5 - Reconnect the device.
I hope this helps, let us know if you still have issues.
-Jwrightmcps
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Poser said:
First let me apologize for spamming the forums with some similar threads... each time I overcame a hurdle and a new one presented itself, I just began a new thread to discuss that. From now on I will append the initial thread... thanks for your patience.
1. WM6.1 and WMDC 6.1 (vista x64) are not too friendly... as the interface, though designed to be intuitive.... is anything but. I am sure it will get worked out in the future... but now it is one tough SOB to conquer
2. From doing enough reading on the web, though recently updated (12-17-07)... the Toshiba BT stack also does not play nicely with WM6.1 ... as numerous smartphone and PPC users are experiencing issues across multiple mobile platforms.
3. In Vista x64 (this is my personal experience) the only way for me to sync via bluetooth is to drop the Toshiba BT stack and use the generic M$ drivers. However... doing so I lose the stereo and serial port services
4. For whatever reason, it seems that activesync locks up STK (R08). When I disable STK, I can establish a connection infintely quicker. Alternatively... when I have activesync disabled, STK is much snappier and its failure/crash rate drops substantially
If anyone has had similar and/or different/"better" experiences with similar hardware... I'd love to hear about it
OS: Vista ultimate x64
ROM: Kavana/Rickwyatt .18
BT adapter: Kensington Micro USB (toshiba rebadge)
HTC: s620
Click to expand...
Click to collapse
Never thought of STK being the culprit of activesync issues. Since i didnt have these issues with WM 6.0 . Now i also use the toshiba bluetooth stack but i use winXP and there was a way that i could get activesync to work. (not sure how this would translate to WMDC) here it goes. Basically i created another bluetooth COM port with the toshiba BT configurator. then made sure that COM port # was selected in connection settings under activesync then i opened activesnc on my phone searched for new bluetooth devices and when it found my PC and connected, activesync was one of the options. Trying to go the other way around by pairing the phone starting with toshibas program did not yield the same results, in fact i could never get it to paired the other way around.
very interesting...
I will try the technique with today... usually my issue comes about when the devices cant exchange passkeys... although they are identical.
pudge.... should I set the com port as server or client?
Poser said:
pudge.... should I set the com port as server or client?
Click to expand...
Click to collapse
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
pudgedaddy said:
Do what? the com port needs to be a serial COM port. not a bluetooth DUN or PAN com port
Click to expand...
Click to collapse
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Poser said:
I gotcha... when I use the BT com port utility it asks whether I want to create a client-side or server-side port
since its serial it needs to be "server" side...
I tried, but still no luck, it pairs.... lists stereo and activesync in the services, but then refuses to sync
I think this is a flaw in WMDC 6.1
Click to expand...
Click to collapse
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
pudgedaddy said:
the only other thing you might try is in bluetooth settings -->security on your device. disable (temporarily) the OBEX security option and try again.
You can also try and create a COM port on your device. When you're on the screen where you add a new bluetooth device. press right soft key and select COM ports. right soft key again and then select new outgoing port. then select your PC (or laptop) on the list of devices that shows up. then add a com port . and it will let you pick com 6 or com 7. Then try again
Click to expand...
Click to collapse
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Poser said:
already been down that road, trying to set up a new outgoing com port (6,7) no dice.
I think the deal is WMDC6.1 ... it makes me sad
Click to expand...
Click to collapse
sorry to hear that. Well since i have the same drivers, i will not be using vista anytime soon (not that i needed this as an excuse to begin with)
I was thinking of perhaps looking for some compatable drivers to replace the Toshiba stack. The generic MS drivers allow me to connect via activesync... but thats all, I lose all serial services (including object push, file transfer, stereo etc....)
I'll be honest though, I have been an XP guy for a long time... but after learning how to tweak, hack and optimize my vista install, I love it.
Hi,
I bought the Bluetooth Gamepad from Chanipus. There are some remainders, even though the manufacturer is gone bankrupt. But the drivers are undependable. On some devices they are working, and on others but same devices drivers doesn't work.
I tried it with my Touch HD and the Diamond of my wife. Both devices say "Sorry! We don't support this Bluetooth Gamepad." But according to some Forums, on some HD and Diamond this Gamepad works...WHY
So I thought about writing a new driver or frontend or whatever, but I never wrote a program for Windows Mobile. Not even a driver at all...
Maybe it is possible to do some kind of reverse engeneering of the latest driver and then do some changes to the program?!
I don't know...but this is a developer-forum
Kind regards,
Toby
Keep it up!
problem is that reverse engineering generally takes months of intense work
luck
and of cause the device itself for testing
Gentlemen,
I have searched the forums and found 1 thread about this but there wasn't a resolution. Hoping that bringing up an old topic someone will have found a fix.
I have Win7 X64 on my laptop. Wanting to pair my laptop and the phone for ... well everything. When I go through the pairing process I connect the two, put in the code and then the driver installation section starts.
It fails on "Bluetooth Peripheral Device" with driver not found. Has anyone else seen this and found a fix/workaround for it
I have the identical 'problem,' although there seems to be no consequence of this driver not being installed. Everything I've wanted to use bluetooth for so far is fine... activesync, hands free, stereo audio, etc. Perhaps I just haven't used a feature yet that requires the Bluetooth Peripheral Device driver.
Still, I'm anal retentive and I'd like to get the driver installed properly if possible.