Hi
Just thought I would give you the heads up that the Smartphone Client works on WM5 pocket PC devices. I have tested it successfully on the HTC wizard (MDA Vario) and the HTC Charmer (T-Mobile MDA Compact II).
You will notice that in the portrait mode the administrative interface may appear slight shortened due to the length of the screen, other than that the application works fine.
rgds
Jim
do you have a copy of the Smartphone version all I have is the pocket pc one.
im eating an apple.
Related
Does'nt it have a stylus...i want one so I can run BB connect but bbconnect does not exist for smartphones just PPCs.
robdes said:
Does'nt it have a stylus...i want one so I can run BB connect but bbconnect does not exist for smartphones just PPCs.
Click to expand...
Click to collapse
The 750, like all Treo's is a PDA phone, not a smartphone, even though they call them smartphones.
http://euro.palm.com/uk/en/products/treo750v/specs.html
I understand that...
There are 2 versions of WM5 a smartphone version and a pocket pc version (with touch screen)...They have the treo 750 listed in the smartphone section (here) but I thought it was a PPC version of WM5
That's what I was trying to say. The 750v like all Windows Mobile Treo's use WM5 PPC Phone Edition OS. Yes you are correct that it should not be in the smartphone section.
Gotcha....thanks
i have the 8125(mda) and i just got the SP5M(SDA), i have a whole bunch of programs for 8125(mda). Can i use the same programs on the sda????
for example: 1) spb pocket plus
2) microsoft voice command
3)omap clock
4)nesterj
and i would like to know, what is the story, what program do i look for? can i use programs for "windows mobile pocket pc" on "for smartphone". or will the sda blow up??
Unfortunately you can't. Your 8125 is based a Pocket PC based version of WM5, and the SP5M is based on the smartphone version of WM5. The two OS's are very different in how they operate, and for this reason the software is not interchangable.
The software for the SP5M must be made for the "Smartphone edition of WM5", smartphone being the key word.
Hi
I have installed Activesync 4.5.0 (Build 5096) because it is necessary to keep my HTC S710 in sync.
I have noticed however that I have frequent and repeated program crashes when i try to sync older devices such as my i-mate JAM and HP nw6515 (to my knowledge, both run Windows Mobile 2003 SE).
Did anybody have similar experiences and managed a way around it?
Thank you and best regards
Stefan
I had no problems with my WM6 device + ipaq 4150 (wm2003).
i also have no problems syncing both my xda mini (wm2003se) and my ipaq hx 2495 (WM5) with Acivesync 4.5. both work fine. if it doesn't, i've heard of other people using Activesync 4.2 successfully as well.
He has WM6 on his s710 so 4.5 is mandatory.
hey guys (and girls where aplicable),
i got a question (a sorta dumb one). If a smartphone lik the iPAQ 514 Voice Messenger or the HTC Vox have windows mobile 6 standard does that mean they run regular windows mobile programs or smartphone versions? See the Cheeta/treo 750 has windows mobile standard ed. and is called a smartphone but it uses regular PPC programs, the other two mentioned before have the same wm6 but no touch screen. so i was wondering if that made a diference in the phones capabilities to use PPC Progs? I appreciate any answers as i am greatly puzzled and intregued buy this.
With WM6 they dispensed with the term "smartphone" in favour of WM 6 Standard. Too many non Windows Mobile phones were being called "smart phones" as well as PPC phones.
WM Standard has no support for touch screens and many PPC apps will not run on it.
WM Pro has touchscreens.
understanding versions...
so lemmie go over this... a ppc with a touch screen is said to run WM6 pro, a ppc without a touch screen is said to run wm6 standard the "smartphone" version. so what of the vox? it has all the capabilities of a full sized PPC without the touch screen so where would it and the ipaq 514 fit in? Because correct me if i'm wrong but dont they offer features like MS Office editing and production verus the others whose ability is limited to viewing or is it the WM6 platform that actually enables this?
You're right, its just a functionality of WM6. Any smartphone (i.e. non-Touch screen device) running WM6 has those same office capabilities and will be running WM6 Standard, not Professional.
As far as I know the two WM6 are one same core of the same OS but..
In the PPC version there is more advanced setup in the menus wich setup is locked in the Srtandard by default.
For example in the Standard there is no way to change the IP of the wi-fi manually.
And in the pocket pc there is some dll's, responsible for touchscreen operation .
yes but....
i do believe you might be correct on everything but the I.P setup for standard. i have an sda running wm6 and i can manually setup my wifi and change certain settings in the network config. Also the HP ipaq 514 that i've been researching also has the same features. see my big thing is i love he compact size of the smart phone but need the capabilities of the PPC. It wold be great if i could get the best of both. i know the O2 XDA stealth has that exact combo but they are hard to find and kinda pricey for thier age.
There are separate SDKs for Standard and Pro, so I think the differences run a little deeper.
well what to do?
well i guess my final questions then wuld be what kind of phone are:-
1/ O2's xda stealth
2/ HP's Ipaq 514
Upon my fellow blogger Tim Hillebrand’s report and because I’ll need to quickly enter a lot of info at MWC (and I don’t want to lug around my desktop replacement and, therefore, pretty heavy IBM Thinkpad a31p just for inputting text), I’ve installed the latest StowAway / iGo Bluetooth drivers on all my mobile devices (even non-Windows Mobile ones) to find out whether the drivers available HERE are (still) compatible with the latest operating system / firmware versions. I’ve found out the following:
Windows Mobile
Pocket PC’s (a.k.a. WM6 Classic / Professional):
HP iPAQ hx4700 (WM5 AKU 3.5.2; selecting & using the Widcomm driver, NOT the MS one); HTC Universal (WM6), Dell Axim x51v (WM5 official A12 (AKU 2.3) ROM with the MS BT stack), HTC Wizard (mfrazzz’ XDA Mobile 6 Release 5 FINAL) and the WM2003 HP iPAQ 2210: all work OK with the factory, default driver.
(Note that, as far as mfrazzz’ XDA Mobile 6 releases are concerned, version 3 was a no-go at all: it didn’t even try to connect. Pressing the Disable built-in HID support doesn’t help at all – unlike with all my other test devices or the same Wizard running Release 5.)
Smartphones (a.k.a. WM6 Standard)
HTC Vox / s710 (factory WM6 Smartphone ROM); no native driver; therefore, I tested it with the s620 / Excalibur / MteoR driver (they’re the same – actually, it seems ALL HTC Smartphones have the same drivers, unlike with WM5 and pre-WM5 Pocket PC’s): OK
HTC Oxygen / s310 with the above MS SP drivers (no native driver): the config app doesn’t even load (“Keyboard driver not functioning!”); then, after closing it, I started to get system errors about the keyboard driver DLL not responding.
Blackberry:
BB 8800 (4.2.1.101 / 2.3.0.80, T-Mobile): Works OK; program invocation hotkeys also work as expected.
Palm OS:
Palm T3: Works OK, albeit some of the program invocation shortcuts (apart from the most basic calendar/ contacts / inbox) take you to some other program, not the default one (unlike with the WM or the BB version). Otherwise, it’s OK.
Symbian:
Nokia N95 (firmware version v20): No native N95 (or any new – the latest ones are dated from 03/2007; the Palm / WinMo / BB drivers have been released a bit later; for example, the BB one in 07/2007) drivers from ThinkOutside; however, the N92 driver works just great on the N95. All the shortcuts work (as opposed to the built-in drivers). Note that the green Fn + Backspace terminates the connection (unlike on WinMo), which, then, must be re-enabled by just re-invoking the wireless keyboard applet. Also note that, unlike with Windows Mobile, Alt+keys directly enters accented characters, which are a bit more cumbersome to bring up under WinMo.
Note that the built-in Tools / Connectivity / Wlss Keyboard works without the need to install any third-party driver – apart from the complete lack of program / task switcher shortcuts and the lack of the English Pound, Japanese Yen and Euro entry.
Conclusion
All in all, the drivers are fully compatible with even the latest devices / firmware versions on all mobile platforms. On Windows Mobile, all the tested WM6 devices, Smartphones and Pocket PC’s alike, worked just great.
That is, you don’t need to be afraid of purchasing the keyboard – it WILL (almost surely) work. The only device not compatible was the HTC Oxygen / s310 low-end MS Smartphone. This doesn’t mean there aren’t other WinMo devices incompatible with the existing drivers, though - it's just that I haven't found one.