REVIEW: TSMobiles: Terminal Service Client for Mobiles - General Topics

I’ve long been promising a review of a multiplatform (Java-based) RDP client, TSMobiles (as of version 2.3.14) for quite a long time. Now that I’ve tested its brother, Remote Desktop for Mobiles (RDM+), I’ve decided to give a try to this app as well.
Note that this is a terse, technical, comparative quick review requiring you to understand the contents of my Windows Mobile Remote Desktop Controller Bible. Therefore, I won’t elaborate on, say, the RDP protocol itself, its advantages and disadvantages when compared to other protocols etc.
I’ve tested it on both QVGA and VGA Pocket PC’s and MS Smartphones. It should, essentially, work on Symbian S60 devices exactly like on the MS Smartphone platform; therefore, I didn’t separately test it on my Nokia N95. I haven’t run tests on my Blackberry either – essentially, the BB client must be far less different from its generic (non-BB-specific) Java brother than in the case with RDM+.
As it’s strictly Java-based, you’ll need a MIDlet manager to run it. See my MIDlet Bible for more info. I’ve tested it under the latest, most recommended Jbed version, JRebeiro_EsmertecJbed_20071119.3.1, reviewed HERE.
First, some benchmarks.
Benchmarks
As opposed to the official TSC (pre-WM6) RDM (WM6) client developed by Microsoft, it’s quite sensitive to smooth scrolling and other types of animations. Benchmark results:
Smooth scrolling (1sec): 2.8k/5.6M (!!!)
No smooth scroll (0.5 sec): 2.8k/1.1M
It’s still way better than NetOp Remote Control 9.0 by Danware and the RDP4-only Mocha Remote Client 1.2 by MochaSoft in this respect, though.
As opposed to RDM+:
Here, the mouse pointer does hover
It uses the entire screen estate (no visible menu / operating system bars)
There’s no context menu by click-and-holding the screen. However, you can bring it up any time by clicking the (relocatable) menu icon; it’s in the center right area in THIS screenshot (the shot also displays the menu)
As can also be seen in the above shot of the menu, only the usual keyboard shortcuts are available in the menu. Their list is HERE
you can send over function keys and the like by enabling Direct input. Then, thumbboard character (but NOT special character, including Enter and delete! Cursor keys and Space do work) input will be handled as textual, direct input. Clicking the screen brings up a quick selector band at the bottom, which lets for sending special keys
No configuration capabilities – for example, you can’t configure it not to use 8-bit color depth. In this respect, it’s different from the RDM client too.
There are (numeric) dialpad shortcuts, making work (for example, left/ double left / right clicks, zooming in/out, bringing up menu etc.) much easier. It works just great!
No file transfer capabilities
Also see the advantages (no need to install another server on the desktop) and disadvantages (resized desktop, locking the user out, pretty much limited usability in a corporate environment because of the lack of HTTPS encapsulation compatible with mobile clients etc.) of the RDP protocol itself
Compared to the built-in RDP client (Remote Desktop Mobile (RDM) – not to be mistaken with SHAPE’s own, commercial RDM+ controller!) of (most) WM6 touchscreen-enabled phones,
Cons
impossible to use higher color depths than 8 bit (unlike with RDM)
much worse keyboard support (should you need to enter a lot of text, this can be an issue – then, stick with RDM). With RDM, all thumbboard keys work as expected (Enter, Del etc.); in TSMobiles, they don’t. Tested on both the HTC Universal and the HTC Wizard (Pocket PC’s) and the HTC Vox / s710 (MS Smartphone). Incidentally, on the latter, you can’t use the multifunction keys (for both alphabetic and numeric input) - a very common problem with Smartphone apps running on the Vox.
no sound support (RDM screenshot)
very sensitive to smooth scrolling and animations (huge bandwidth usage & major slowdown)– make sure you disable them all
no copy/paste (automatic clipboard synchronization) between the remote desktop and the mobile client
Pros
it has a built-in traffic meter
has a dedicated console mode. In this respect, in theory, it’s WAY better than RDM (let alone TSC). In order to make it work, make sure you tick in “console section” in the account setup dialog as can be seen in HERE
Note that you need at least Windows Server 2003 (Version 5.2 of the underlying RDP protocol) or Vista (6.0) for this to work; regular Windows XP doesn’t support this. If you need console mode on XP, go for, for example, RDM+, which does offer it. Also note that, with Vista, console mode didn’t work for me for some reason.
Able to send over any special keys (including function keys), unlike RDM
QVGA compliance
(The above screenshots are all VGA; therefore, let’s see how TSMobiles behaves on QVGA devices):
On QVGA devices (as opposed to VGA ones, where, due to the remote desktop’s also being VGA, there’s no need at all for zooming in), the menu also contains a “Zoom in” item:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the zoomed-in state, you can both use the on-screen arrows (as with the PPC / touchscreen Symbian / Palm / iPhone(?) version of RDM+) and the D-pad for quick scrolling.
Also, as with the non-Pocket PC clients of RDM+, you can redefine the D-pad-based scrolling by switching to the “Scroll mode”:
As you can see, the touchscreen is utilized by default by the program.
(QVGA) MS Smartphone compliance
Works OK on MS Smartphones. You’ll need to use the “5” key to bring up the menu:
The other keypad shortcuts are as follows (note that they’re usable even on a Pocket PC – if it has a dialpad or a full QWERTY keyboard; tested this on the HTC Universal and worked OK):
[1] - Left mouse click
[2] - Left double click
[3] - Right click
[6] - Left click and hold
[4] - Selecting and sending keyboard shortcut from list
[8] - Zoom In
[9] - Zoom Out
[*] - Turning on scroll mode
[0] - Selecting and sending keys sequence (entering text string)
[#] - Opening/Closing Control keys menu
All in all, it works OK and pretty fast on the MS Smartphone platform as well.
Note that, on the MS Smartphone platform, it isn’t affected by the screen bug of all Jbed versions – unlike, say, the Gmail MIDlet. That is, you won’t need to try to use the full screen Jbed 3D hack explained HERE.

Important Vista note: you MUST log off before logging in with TSMobiles!
At first, I had severe problems with connecting to Vista and the FAQ of TSMobiles didn’t help either (other than starting it has become Vista-compliant as of version 2.3.11). After trying to connect, it just announced it can’t: it displayed a “Received disconnect” error message. (Incidentally, I’ve also tested the heavily outdated and in no way recommended Mocha RDP client (version 1.2); it didn’t work either – but, of course, I didn’t even expect it to work, it being based on RDP4 only (dunno if RDP4 is phased out in Vista – I think it already is).
Of course, RDM worked (just like XP’s / Vista’s built-in RD client) just great with exactly the same remote Vista desktops. So did TSC in WM5. I’ve tested this on two different remote Vista desktops, one of them running Vista Business, the other running Vista Ultimate, with both firewalls and virus protection apps enabled and disabled – no success, while, again, the RDM client worked just great.
Fortunately, finally, I found out what the problem was: you MUST log off your Vista account so that TSMobiles can log in. Then, it works just great:
This is, in my opinion, a major problem with TSMobiles, which should be addressed promptly.
Note that the console mode didn’t seem to work with Vista.
Verdict
While it’s certainly way better than the pre-WM6 TSC’s (unless you use the well-known vijay555 full screen hack to fix one of its major problems: the lack of a full screen mode), it has little advantage over the built-in WM6 client, RDM, in the new version. If you already have RDM, you might want to stick to it unless you really need the special features of it (console mode – if it does work, that is -, special characters, ability to send more sophisticated mouse actions etc.). In generic use, I’d stick with the default RDM, particularly if you count in the VERY high price ($35) of TSMobiles.
On touchscreen-less phones (including MS Smartphones, Symbian and BlackBerry phones), the situation is pretty much different: on them, it’s already a decent alternative if and only if you MUST use RDP to access a remote desktop. If sticking to RDP isn’t a must, I’d go for RDM+ instead because of the vastly superior feature set (file transfer, less data usage, usable through firewalls, not that restrictive a protocol etc.)

Related

REVIEW: Teksoft's brand new Pocket PC utility suite Smart Bar

Teksoft, developer of the excellent BlueMusic application (see for example this article & the links), has just come out with a brand new suite, Smart Bar, of system management applications. I decided to give it a try as it’s a pretty capable suite of utilities with some really excellent modules.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
They even promise an application capable of recording both (!) parties in a phone conversation (so far, this has been impossible with all Pocket PC Phone Edition devices of both HTC and ASUSTeK (Fujitsu-Siemens T8x0)); I think it’ll work by directly “tapping into” the Bluetooth unit as can be seen for example in here.
Availability, price
The suite is available here. To review the (pretty good and recommended) manual, visit this link. There is a(n unfortunately, pretty restricted) trial version too.
The “price” of the suite is 200 credits; that is, between 20 and 25 euros (depending on the amount of money you transfer to your online credit account). The registration is a one-device only (that is, CPU ID- and not PPC owner name-based); licenses can be transferred to other devices in case of a device change (for example, when the previous one bites the dust and gets exchanged).
Install
Use smartbar_setup.exe for pre-WM5 and the CAB files for WM5; see install.en.txt for the latter case.
Compatibility
It’s stated to be compatible with strictly QVGA devices with at least the WM2003 operating system. (I’ve also tested it on Pocket PC 2002; it indeed doesn’t work.)
You can, of course, try to install it on VGA devices, but I don’t think you should give it a go. I’ve tested it on three different VGA devices (Dell Axim x51v A12, WM5 iPAQ hx4700 2.01, WM2003SE Pocket Loox 720). On the hx4700, the PowerPlugin Today screen plug-in was absolutely useless; on the two other devices, it was shown, but not anything else. On the Dell Axim x51v, I’ve received frequent gwes.exe crashes after a reboot, because of which I had to entirely disable PowerPlugin.
Of the PowerPlugin, few features were accessible on these VGA devices; in the following chart, I’ve summarized all this (note that it also contains HTC Wizard-related info):
Note that, as far as the Wizard is concerned, I’ve listed two ROM’s: the O2 2.21.4.1 WWE (3/9/0) ROM and the “cooked”, widely known AKU3.2 one by KTamas / bepe. This means there are differences between different ROM versions / builds – all icons may work with your particular ROM version. The developer has promised they would test the suite with other ROM versions.
As can clearly be seen, the majority of the features PowerPlugin has can’t be used - not even on the QVGA HTC Wizard (with some ROM versions).
One of the central features of the application, Smartbar, wasn’t accessible either on any of my VGA devices. Self-standing apps like the screen capture, the network troubleshooter and the task manager applications, however, did work on VGA devices.
Also, it’s very important that you BACKUP (see the Backup Bible if you’re unsure) your device before installing the application. My absolutely clean, freshly hard reset WM2003 HP iPAQ 2210, after the install, couldn’t boot in at all and I ended up having to hard reset the PDA (I’ve tested this two times). I haven’t tried to boot into Safe Mode (read this roundup & tutorial if interested in Safe Mode on the Pocket PC); it may have helped .
Today plug-in (PowerPlugin)
It’s a simple plug-in with shortcuts to en/disable wireless units, suspend the device, show whether it's connected to the Net (IMHO, this is pretty useless on a WM2003+ device - after all, the Connectivity icon is always visible on the taskbar) and a backlight slider. It doesn’t contain for example battery or memory meters, unlike most other Today launchers (please see this iLauncher review and the links to earlier reviews to find out what a decent Today launcher should offer.)
Unfortunately, the majority of the functionality it’s supposed to offer didn’t work on my test devices. For example, as far as en/disabling wireless functionality is concerned, it was only on the x51v that it was able to both en- and disable Wi-Fi; on the Wizard, it was only able to enable it and on the PL720, wasn’t able to do anything. As far as Bluetooth is concerned, it didn’t work on any of my test devices in any direction. The backlight slider only worked on the PL720. (See the chart at the top, in the Compatibility section for more info.) The only exception is the HTC Wizard with the O2 ROM, where everything worked. (Again, more information on the compliance with other HTC Wizard ROM versions will be published / announced later.)
Also note that, while it has, in addition to the backlight slider, a backlight icon. It, now, doesn’t do anything. Hope the Teksoft folks wire it to the backlight / brightness applet of the device as is the case with all the other, similar Today plug-ins.
Task manager
This is one of the best features of the suite.
Pretty cool. Better than the built-in task manager: it lists the memory used, whether it’s a windowed app/process and if yes, is it visible; the title and the window class name. However, it doesn’t display other advanced & useful stuff like CPU usage and has no “Stop all processes”. Also, it’s not possible to “hide” system processes either – that is, for a newbie, this task manager can prove pretty dangerous.
Ultra Keyboard
This is probably the most unique feature of this suite: it allows for controlling some functionality using the keyboard. The most important of this is text insert macroing capabilities, which has always been missing from Pocket PC’s (except for some, not very capable Software Input Panels (SIP's) like Resco Keyboard Pro and Biomobility’s CopyText Pro; also see this thread for more info if interested).
When you use text insert macroing and assign a macro to, say, the series of characters “bye”, Smart Bar will constantly monitor the keys you press on the built-in (or external) keyboard of your PDA and when it sees the keys b, y and e pressed in order, it’ll delete back the three characters and insert the replacement text.
It's really cool but, unfortunately, only works with built-in keyboards or external ones (like those of desktop-based PDA controllers; see this roundup for more information on them.) Even in this case it can prove useful - most built-in thumb boards are pretty awkward to enter text on them.
You can initiate the following functionality from the keyboard: Replace with phrase; Execute a file; Turn device off; Reset device; Call number and Screen Capture. Note that if your keyboard has a different layout than your current ROM language, the default layout will be used. For example, if you have a German MDA Vario (= HTC Wizard) with English ROM but use the keyboard in German mode so that you find all keys at once, you will need to enter ‘bze’ instead of ‘bye’ for the ‘bye’ script to be executed. Also, note that not even in this case will everything execute – that is, try not to use anything that have relocated letters.
In my tests, all these functions worked OK.
Smartbar
This is a shortcut bar at the bottom of the Today screen for accessing active apps (closing / activating them) and activating other built-in apps (and the Desktop mode) of the Smart Bar suite. Unfortunately, task control-wise, it is probably the worst module in the entire suite; hope this will be greatly enhanced in subsequent releases.
Compared to (better) task managers like iLauncher, Magic Button or Spb Pocket Plus, its disadvantages are as follows:
It can only be accessed on the Today screen, not on the taskbar (and / or the Close / Minimize icon itself)
It supports no mass operations like “close all but this one”, “close all”, unlike with Magic Button or the built-in iTask of Compaq / HP iPAQ’s
It doesn’t override the Minimize / Close (x) icon
Hope these disadvantages will be soon be fixed and the task management functionalities of the application greatly enhanced.
Note that while it doesn’t have explicit scrolling icons / menus (unlike Magic Button as can be seen in here but NOT iLauncher 3, which is suffering from the complete lack of scrollbars as can be seen in this and this screenshots), you can scroll the active task icon list if there are more than five (Portrait) / seven (Landscape) of them.
I’ve also tested the CPU usage of smart.exe to see whether it causes any CPU load, particularly with more than a handful programs active. (For example, Magic Button causes a constant CPU usage of about 1-3% all the time.) The results are acceptable and not much worse than those of Magic Button:
Desktop
Yes, a WisBar Advance Desktop (WAD) clone! It’s in no way so advanced as WAD; still, if you like these kinds of applications, you may find the one in Smart Bar suitable.
Screen capture
Smart bar also contains built-in screen capturing capabilities. Please see the Screen Capture Bible for more information; in the following pros/cons list, I build on the information and explanations of that guide.
Compared to other screen capturer applications,
Pros
Uses a 3-second delay by default; that is, it can be used to make menu screenshots (without using the periodic screenshot capabilities)
Able to capture images periodically (albeit with some limitations, particularly when it comes to the frequency of taking shots). Note that it’s the “Stop interval” drop-down list that lets you fine-tune the interval it’ll take screenshots (between 10 seconds and 10 minutes as can be seen here and here)
If you use it on a device with a built-in thumb/keyboard and you enable screen capturing through Ultra Keyboard, you will be able to capture almost any game screen any time (!) by just entering the Ultra Keyboard shortcut (“CAP” by default). In this respect, the suite is unbeatable and unrivalled.
Periodic screenshot capturing is fast and, therefore, gaming-friendly (unlike, say, BeniSoft ScreenShotCE)
Both BMP and JPG output; the latter with settable quality
Can save files to anywhere, not just the main storage
Can capture images, in addition to the original (100%) size, at double and triple (200% / 300%) size – very useful on QVGA devices to avoid further enlargement and unique among all the screen capturer applications
Landscape & VGA compliant even in SE VGA mode
Cons
Multishot (periodic) capabilities are a bit limited – you can’t instruct the app to make shots less frequently than every two second
While the screenshot utility is a self-standing app, it cannot be invoked from a custom-written nScriptm script to fine-tune periodic screenshot making parameters
(Trial version useless: it inserts a message in the captured images)
All in all, the screenshot capabilities of the app are excellent, especially when you take the price of the suite into account and the only problem with this module are the too frequent screenshots in auto mode. Also, as has already been pointed out, the ability to make hardware keyboard-based screenshots of games is unbeatable and unique.
Network Tools
The suite also contains a simple (it’s in no way as advanced as, say, vxUtil) network troubleshooting utility, Network Tools.
It’s able to ping and traceroute to find out possible networking problems. It also uses DNS lookups; that is, if you for example enter www.yahoo.com, the contents of the input field will revert to 209.73.186.238 (or something very similar, with a different ending), showing the IP address of the given computer (it doesn’t do the reverse).
It also exports the traceroute results to a file. (Note that I didn’t have a “real” wireless connection during the tests and the utility had problems accessing the net via USB (in both WM5 AKU2+ networking modes); I could only access the desktop computer my PDA was hooked up to; this is why there is only one entry in the tracelog.)
It’s pretty cool to have if you don’t happen to have Windows Mobile Network Analyzer PowerToy or vxUtil around.
Verdict
This app is certainly promising. Hope subsequent builds / versions will fix the issues / implement the missing functionality (most importantly, overridden Close / Minimize button) I’ve elaborated on. Then, I’ll recommend it heartily, without conditions. Now, in the present state, I do recommend it too – but conditionally.
First, the bad. It does have compatibility issues. If it does work on your PDA model, it won’t likely to support all the features of the Today plug-in (PowerPlugin) and has no for example storage meters. Also, the task management functionalities / program shutdown capabilities of Smartbar are certainly inferior to most similar apps like iLauncher, Magic Button or Spb Pocket Plus. I find this the biggest stumbling block of the application.
Second, the good. It’s, as an all-in-one application, is really good. That is, if you don’t want to struggle with installing many applications (say, WAD + Magic Button + some advanced (!) screenshot app + vxUtil) to achieve the same (or even better! See for example the screenshot utility) functionality (without keyboard macros, of course), give it a go. Also, if you need keyboard macroing (again, it won’t work with on-screen keyboards, only hardware ones!), this is the application to go.
The same stands for taking screenshots: this application clearly excels in this area (except for the too frequent screenshot taking in repetitive mode – hope the developer fixes this too), particularly when it comes to making screenshots of anything (most importantly, games) that inhibits hardware button access and, therefore, renders hotkey-based screen grabbing impossible. Then, Ultra Keyboard’s excellent keyboard-based shortcuts will prove highly useful.
All in all, if you still don’t have any application to implement the above-listed functionalities or, for example, losing the excellent task management functionalities of other task managers isn’t a problem, definitely give it a go. Remember, however, that
do NOT get it if you are a VGA user; wait for the soon-to-be-released VGA-specific / compliant version
do backup your device before installing or, at least, make sure you have an active Safe Mode application

REVIEW: brand new SOTi Pocket Controller Professional 6.0

We all know the, without doubt, BEST “let’s control a Windows Mobile device from a desktop PC” solution, SOTi Pocket Controller Professional capable of controlling both Pocket PC's and Smartphones. Now that they have just released a brand new, 6.0 version, I’ve given it a very thorough test ride (current, tested version: 6.01 build 1256). Read on to find out whether it’s worth upgrading!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note that the excellent Windows Mobile site Just Another Mobile Monday has already published an excellent review. Please make sure you read it. In the current article, I “only” show what has changed over the last, 5.07 build 966 version (and, for SP users, I give you some genuine registry hacks to hide the icon of the old Pocket Controller from the task bar). I also provide you with some benchmark so that you will know everything to decide whether the new version is worth upgrading. You may also want to read my all-in-one roundup of all the comparable solutions HERE.
Availability
It’s available HERE. A single-device license costs $35.95. If you have purchased Pocket Controller-Pro during the last 10 months, you are eligible for a free upgrade. Otherwise, you get a 20% discount if you've purchased Pocket Controller earlier.
Should you have more than one Windows Mobile devices, you need to purchase a license for each of them, should you want to access them via Pocket Controller. This isn't an issue with the vast majority of the Windows Mobile users out there, having only one handheld, "only" supergeeks and gadget fans having more than one device.
Compared to the old, 5.x series,
The pros
Fully fledged registry editor – currently, the only one registry editor to flawlessly work with WM5+ devices, as opposed to the free Mobile Registry Editor 1.1 (of which, the long-promised, new, 1.2 version doesn’t seem to be released). It supports everything a decent registry editor should support: import / export (using version 5 compatible with Resco Registry Explorer), search and is way faster than MRE. (See the Windows Mobile Registry Editor Bible for more info.)
Image snapshot capabilities are vastly enhanced: PNG is supported and GIF are saved compressed. No need to save your images to BMP files and, then, in a separate session, convert them to PNG’s (or, probably, GIF’s). Not that the latter would be THAT complicated: I’ve, for example, created a simple batch file just calling ImageMagick to make this stuff automatic.
The video capture capabilities have also been enhanced: now, it’s also able to record into WMV files (not only AVI ones), should you prefer the former to the latter.
On MS Smartphone (Windows Mobile 6 Standard) models, the Soti icon isn’t any more displayed on the task bar (in addition to the above screenshots, HERE is an Oxygen screenshot; compare all these screenshots to my previous Smartphone shots).
Note that , with previous versions, you could also do the same with importing THIS registry file and restarting your phone (results visible HERE). This hack has been, as usual, discovered by me; it just involves setting HKEY_LOCAL_MACHINE\ SOFTWARE\Apps\ SOTI\ PocketController\ enabletray to OFF.
The client CPU usage is a TAD lower, 32-33% as opposed to 33-34%, under exactly the same circumstances. In the screenshot, the first 3-4 minutes have been taken using the new (another screenshot of this case HERE; as can be seen, it lacks the PocketController icon in the top right corner, also showing it’s the new version), the last 3-4 minutes with the old version, quickly swapping the two versions in between. Note that if there is no remote controlling session, the CPU will not be used.
The User Interface is far prettier now: the new Vista style UI, which also now has a New Skin Display Mode (i.e. Skin in Window) that was not possible in v5.07.
The Skin Catalog has also been completely redesigned; for example skin downloads are much faster now, you can also do things like download all skins for a manufacturer with a single mouse click and preview all skins without having to download each skin one at a time and then click on each skin to look at it. Also added is the capability of showing the specifications for a device in the Skin Catalog in addition to its picture. At present, however, the data of a few devices data is populated. As an example, look at the Intermec CN3 device in the Skin Catalog.
Now, for some other stuff I don’t actively use / need: it supports advanced security options (for example, remote wipe), advanced printing and a lot more; see THIS for more info on new / enhanced functionality.
Still not changed / enhanced
You still can’t use the keyboard / mouse with the HTC Vox – as opposed to the HTC Oxygen
The Task Manager module hasn’t changed at all. This means you can’t expect anything like acbTaskMan or any, more advanced task / process manager / monitor tool. (See THIS for a complete review of these tools.)
The draw mode isn’t enhanced: it only supports hand drawing (shot of the older version HERE) – there are no ways of using for example circles / ellipses (to emphasize something) or making some text (for example, e-mail addresses, names etc. in a contact list) illegible. This means you will still need to post-process a LOT of images to make a lot of personal information unreadable.
On the other hand, you don’t need to keep Ctrl depressed on the keyboard any more to continue drawing, which was a definite problem with the earlier version (which just deleted handmade drawings upon releasing the Ctrl button; this also means, with the old version, you can’t use the Ctrl-D shortcut to quickly bring up the screenshot window, unlike with the new one).
The remote console is as simple as before; it only knows very few commands. Not that it should be a complete reimplementation of the file system tools of the venerable MS-DOS, anyway.
About 100k more (built-in - as before, being a service started at startup, it can't be installed to storage cards) storage usage (understandable if you think of for example the brand new functionality like remote wipe)
Note that Intel 2700G (3D accelerator in the Dell Axim x50v / x51v; see the Screen Capture Bible for more info on the related problems) screen capture-wise, I haven’t found any differences. The problems are mostly based on the fact that a given game’s hating ActiveSync. As is pointed out in the Bible, you can be successful at making a game run with Pocket Controller being active; for example, with Call of Duty 2, to do this, you need to only activate Pocket Controller after you’ve started a new game or loaded a previous one, not before (otherwise, the game may hang in the menus).
Verdict
If you can get a free update (that is, you’ve purchased your copy in the last ten months), go get it. If you need Smartphone screenshots without the SOTI icon and are afraid (you shouldn’t be!) of importing my registry script, it’s a must. Also, if you need a decent and, as opposed to anything else currently available, working and fully fledged desktop-side registry editor, go get it. The same stands for the brand new functionality like enhanced security / remote wipe – if your particular model / carrier doesn’t support it, you may want to go for alternate means; one of them may be the new Pocket Controller version.
If, on the other hand, you already have the 5.x series, it’s working great with you, don’t need any of the new functionality and you aren’t eligible for the free, new version (because you’ve purchased your copy more than 10 months ago and, therefore, you could only use the 20% rebate), I’d think twice before going for the new version: the underlying engine is only (very) slightly better / faster than the last, 5.07 version (see for example the CPU usage results). It's only at low-speed, for example, GPRS connections (as opposed to the high-speed direct USB connection) that there is a certainly visible communication speed improvement: the data traffic during remote control sessions is a little more efficient (SOTi have switched to using the same technology for their enterprise solution, MobiControl, which can manage devices over slow GPRS connections, so sending less data really matters in this case) I’m not sure whether it’ll worth the $28.76 for a 5.0x user – again, unless you desperately need the new features (remote wipe, desktop-side registry editor etc).
Finally, if you’re a newcomer to Windows Mobile and have NOT ever purchased any version of this tool, go get it – it’ll pay off in everything; most importantly, speed (no other tool remote controller tool supports so high a speed). You will LOVE it, I’m absolutely sure – just don’t waste your time with the other, in most respects, vastly inferior solutions. What you gain by not paying anything for a free remote controller tool, you will easily lose by, for example, having to waste a LOT more time waiting for screen refreshes because of the far worse communication protocol used.
UPDATE (07/20/2007): PPCT frontpage; SPT frontpage; minor (mostly GUI-related) changes.

New Java-based browser Teashark: really a competitor to Opera Mini 4? Not (yet?)

Thanks to XDA-Developers forum member TalynOne, I was directed to the new Java MIDlet-based browser Teashark. It is also mentioned in THIS blog post too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Availability
You can download the JAR file HERE. Just deploy it under either the Jeodek or Jbed MIDlet Manager. (Do NOT try to deploy it under TAO Intent because the browser is entirely incompatible with all TAO Intent versions!)
Please note that, if the words Jeodek, Jbed, TAO Intent and MIDlet Manager sound Chinese to you, don’t despair: just wait for my long-promised MIDlet Manager Bible, where I explain everything you’ll ever need to know about these programs. In the meantime, feel free to follow the links in the above-linked MIDlet Manager Bible announcement for forum posts and other remarks.
Compatibility, problems, bugs
As I just love Opera Mini 4 (OM4 for short; see review HERE), which I use almost exclusively for Web browsing, I’ve tested the new browser at once to see whether it’s, as mentioned in the above-linked blog post, indeed a decent alternative to Opera Mobile.
I’ve tested the browser with the three most common MIDlet managers out there: TAO Intent (both the 10 and the 11 series), Esmertec Jeodek and Esmertec Jbed. (Haven’t tested it with IBM J9.)
TAO Intent (tested on the HTC Wizard Pocket PC (TAO version 11.1.7.1029 default), the HTC Universal Pocket PC (11.1.7.1036 Risidoro) and the HTC s310 / Oxygen Smartphone (10.1.7.680 default)): absolutely useless. The menus aren’t accessible (neither the hardware nor the software, on-screen keys work) and there’s no way of even navigating on the page – neither the D-pad nor the on-screen / hardware 2/8 or up/down buttons work. Finally, as with the other MIDlet managers, the touch screen can’t be used on Pocket PC’s.
Esmertec Jbed (tested on the HTC Universal): a bit more usable. While it still doesn’t support any kind of touch screen operation, at least it allows for accessing the menu (via a hardware key only). It has the following pros / cons (under Jbed):
Pros
Upon entering an already-entered URL, it has an automatic address completion feature, unlike OM4b2
It displays both italic and bold characters, unlike OM4b2 (OM is totally unable to render italic text and, depending on the actual font size used, it may refuse to render bold too).
The in-page text search works just great (examples: 1 2 3) – I wish Opera Mini had the same feature!
Cons
The rendering of the text is VERY bad: wherever there is a style / color change, the text overlaps as can clearly be seen in THIS screenshot
Scrolling (in full page view mode) is FAR better thought-out in Opera Mini 4 - it takes far less D-pad presses to navigate to a link without annoying screen scrolls.
There is only one character size, unlike with OM4 – no font size setting capabilities as can be seen in this screenshot taken under Esmertec Jeodek on the s710. This is REALLY bad: Java MIDlets have access to, in general, three different font sizes by default.
The default mode is a no-one-column (that is, showing the original layout) mode. On VGA devices, this, in most cases (there are exceptions; for example, the page HERE is rendered almost unreadable because of the need for horizontal scrolling – for comparison, HERE is the same under Opera Mobile 4 beta 2 without using the one-column mode and with Extra large fonts (!) – see the difference? OM4 is WAY better in this respect too), isn’t a problem. In order to enable the default one-column mode, there’s a “page start with mini view” checkbox in Preferences, I couldn’t check it in under Esmertec Jeodek v20070115.1.1 on my s710 (while it worked under Esmertec Jbed v20070802.2.1).
Again, it doesn’t make use of the touch screen in ANY way – not even at selecting from the menus
History doesn’t work at all, unlike with OM4, where you can quickly switch between the visited (and still in-memory!) pages
Generally, it loads pages definitely slower than OM4, while it uses more bandwidth
It doesn’t let for scrolling through the links of the main (home) page: it only scrolls down to the third or fourth (depending on the actual screen orientation) and, then, start from the beginning. On other pages (including the “Visited” page list), there’re no similar problems. Note that this seems to be only a problem with Jbed; with the (older) Esmertec Jeodek (the one, v20070115.1.1, coming with the HTC s710 / Vox Smartphone), I could scroll through all the homepage items
It uses its own text entering method when entering the URL to navigate to or the search expression for text search. (Fortunately, this is NOT the case with in-page text fields/ areas like the Google textfield at the top, where the default one is used. That is, if you absolutely must use punctuations in the URL you need to enter, fire up Google so that you have access to the default, MIDlet manager-provided text input area; there, you’ll already be able to use all the punctuation marks – including the ones on hardware keyboards OR phone dialpads; for example, the one on the HTC s710 / Vox). This means the following:
if you have a built-in hardware keyboard to enter text you will only be able to enter alphanumeric characters but nothing else – not punctuation marks only accessible via a Symbol key (fortunately, the dot, “.”, isn’t one of them – at least on the Universal) or “/”! Think of it: you can’t even directly enter URL’s like www.pocketpcmag.com/blogs because of the inability to enter /! This GREATLY reduces the usability of the app, particularly if used together with Jbed (which, being run always in full-screen and, consequently, hiding the SIP icon) doesn’t allow for bringing up the SIP and entering special characters on it. Note that I don’t know if entering “special” characters (like /) works on a SIP as Teashark is completely useless with the TAO Intent Manager (one of the MIDlet managers to support bringing up the SIP any time).
On Smartphones, the dialpad works in the standard mode (without xB9; the # and * buttons, however, just can’t be used to enter anything else. That is, even if you keep # depressed, you won’t be presented a list of the usable punctuation marks (including for example /), only the # will be repeatedly included.
Still as far as Smartphones are concerned, it’s absolutely unable to make use of the slide-out keyboard of the HTC s710 / Vox.
Verdict
While this browser certainly has some advantages over Opera Mini 4 beta 2 (the in-page text search and the ability to render italic / bold being the most important), in general, this browser is, currently, in no way recommended for Windows Mobile users because of the really bad bugs. That is, just stay away from it.
I let you know as soon as a usable version is released.
UPDATE (09/14/2007 14:15 CET): I've also tested the browser under IBM J9 6.1.1 on a Dell Axim x51v. While, unlike with TAO Intent, you can move around with the D-pad (and click links), the softkeys don't work (not even with hardware buttons), which means you don't have access to the menus at all. That is, it's useless under IBM J9 too.
Hmm... will try. Is it for PPC Phone or SP?
Minimo v0.2, I find that it is very slow.
CWKJ said:
Hmm... will try. Is it for PPC Phone or SP?
Click to expand...
Click to collapse
Both as it's a MIDlet.
CWKJ said:
Minimo v0.2, I find that it is very slow.
Click to expand...
Click to collapse
Yeah, it's VERY slow. Use for example OM4 b2 instead, if you absolutely must use a free browser.
Cross-posting this from a post I made on the Opera Mini forums, since this community is more likely to understand my issues with this browser...
There is something fishy with Teashark.
THINK ABOUT IT.
1) They appeared out of no where with a Java app.
2) There is NO linkable parent company on their site. Can't look up domain registration, can't find out ANY other information AT ALL about them and who they are.
3) They have absolutely NO way to relate back to the community. They have a "blog" run on a wordpress backend. That right there should throw up some red flags. Why would a "company" or WHATEVER they are that is developing a Java browser (with no ads in it mind you), use Wordpress as a blog backend? That just makes no sense to me
4) How exactly does this company make their money? Something tells me you don't want to know if you've been using their browser. They have no advertisements on their site or in the browser. They have to be making money somewhere, because they wouldn't have these proxy servers serving up loads of bandwidth for free. Where is their money coming from? A parent company? Who?
5) Their whole website is fishy. Aside from complete lack of information, why do all links on their site link you to port 8080 on their server? Why aren't they running over standard port 80? Something is odd about that alone.
6) The vendor tag in the app is labeled as "Vendor". Ummmm... what?
Their website traces back to: "IP 69.72.142.98 is from United States(US) in region North America"
That is about the only traceable information I can figure out.
It creeps me out that this mysterious company pops up out of no where and throws this "browser" app out there, with absolutely no effort to disseminate who they are. What is even creepier is that people have downloaded this app and are using it with ZERO knowledge of who this company is or who is behind them!
A review of the latest version has just been published: http://forum.xda-developers.com/showthread.php?p=3571856#post3571856

Web Browsing News as of 10/18/2007: new Opera Mobile, Picsel, Spb Pocket Plus

A lot has happened in the last month on the Web browser scene. Let’s go over the news!
1. Opera Mobile 8.65 Final released!
Since this March, there have been two beta versions of Opera Mobile, without doubt the BEST, fastest and most standards compliant Web browser for the Windows Mobile platform. Now, almost half a year after the release of the first Beta, the final version has, finally, been released, of which I was also a (closed) betatester, working closely together with the developers and decision makers of Opera.
Compared to the 8.65 betas, which I thoroughly elaborated on in the Web Browsing Bible (and, therefore, in here, I don’t elaborate on these new features – make sure you read my roundup above), there are only few changes. There, on the other hand, have been several bugfixes; for example, the really annoying DEFBROWSER bug I’ve, independent of some other people doing the same, discovered and reported HERE).
Design decisions
Single column layout removed. This is a design decision I don’t really agree with. Particularly if you have a VGA device, you MAY find the lack of the single column mode annoying, particularly with sites / pages that, otherwise, would work much better with a well-working One Column mode. An example: a Wikipedia article in PIE’s One Column mode on a VGA device in Landscape mode (Largest charsize, High Resolution enabled) (the same with Fit to screen – as can be seen, it’s pretty much useless) and the same in Opera Mobile (Minimum font size: 8; Zoom: 100%). As can clearly be seen, One Column modes will ALWAYS be able to present more information. You can, of course, use zoom facilities so that the horizontal screen estate is fully filled in but, then, the character size will also grow and, what is worse, the images will also become pixelizated. (Also see THIS thread for more info / discussion.)
Desktop view, which has been made the default (!) viewing mode, has been made much friendlier. Now, it’s using a bit smaller characters than before. Should you still find them too big, switch to the default (fit to screen) viewing mode because setting Menu / Tools / Settings / Minimum font size to even 8 doesn’t seem to do the trick. Thanks to the, most of the time, excellently working new wrapping functionality, makes it possible to live without having to scroll around. This is shown in the following (VGA Landscape) screenshot with the View menu shown:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, the cache is stored on the same drive as the executable program itself. While this is what many people have been asked for (particularly with devices only having 64 Mbytes of Flash ROM, meaning only 10-11 Mbytes of it available to the users – for example, the HTC Oxygen / s310 Smartphone is one of them –, you will definitely like this.
Note that, however, this approach might have negative consequences. As has been explained in my Web Browsing Bible, storing the browser cache on a slow-to-create-files-on storage card (most non-high-end cards are like this) may result in the slowdown of the page loading. If this is a concern to you (because you visit pages that contain a LOT of different images, which are all cached), make sure you manually (!) relocate the cache to somewhere else – or, for that matter, completely disable it in Menu / Tools / Settings / History / Cache Size as can be seen in HERE. To relocate it back to the main storage (or even a RAMdisk, if its being completely deleted each reset and the decrease of RAM memory isn’t a problem either because, for example, you use a 128M RAM model), just follow my previous Opera cache relocation tutorial.
Problems I’ve discovered and/or fixed in the meantime
On MS Smartphone (Windows Mobile Standard) phones, when you have really low RAM memory (you’re running out of it), problems may occur with keyboard shortcuts. Namely, no matter what hardware shortcut button you press, the same functionality (in general, Reload and / or Back) will be executed. This can lead to confusion – at first, it caused me a lot of headache too until I’ve understood how this all works.
All in all, if your hardware dialpad buttons don’t do what they’re supposed to do, you may want to shut down (some) other apps and / or Opera Mobile tabs. This will free up some RAM, which will result in the buttons working again.
There’s still no hardware application button support (you can only tie button shortcuts to dialpad / keyboard buttons), but now that I’ve published a FULL tutorial and explanation of all decent Windows Mobile button enhancers, including how you can configure your hardware buttons to simulate the pressing of numeric (dialpad) buttons, this isn’t that big an issue. Just make sure you read the Button Enhancer Bible and do what’s there.
There had been a problem with non-English operating systems because of the wired-in (English) directory names with the initial release. This, along with manually fixing it, has been fixed in the meantime; that is, current builds no longer have this problem.
Verdict
Opera Mobile is and, as it seems, definitely remaining the best browser for both Pocket PC’s and MS Smartphones. While there still are some glitches (the worst of them, the lack for hardware app buttons, having been fixed by me), these problems are nothing compared to the generic sluggishness and/or Web standards incompatibility with (most of) the other browsers. Make sure you get at least the trial version.
2. New (1.0.5) Picsel version released!
There is (see THIS) also a new version of the Picsel Web browser.
As opposed to some XDA-Dev folks, I haven’t found much improvement. For example, the CSS compliance is still very bad (the result of the Acid2 test is HERE; that of the CSS1 test is HERE). The Ajax compliance isn’t a tad better either (tested with THIS and THIS test suite).
All in all, there isn’t much improvement. You may still want to give it a try if you are a big fan of the GUI. I, myself, would still stick to either Opera Mini or Mobile. Don’t necessarily believe the hype
3. New Spb Pocket Plus
Spb Pocket Plus has always been one of the best Pocket PC (Windows Mobile Pro / Classic) system enhancers. The brand new, just released 4.0 version boasts, in addition to a lot of new functionalities, a, compared to the much less significant changes during the 2.x-3.x version jump, considerable
(screenshot showing the four tabs, all populated, and the drop-down list (now, only having one element) of the invisible tabs in the upper right corner. For comparison: a screenshot of the context menu of the old, 3.x-series version HERE, also showing there haven’t been any new buttons / any tabs in it.)
It has received the following niceties:
screen dragging mode; note that the autoscroll can be a bit of a pain in the back; it’s sometimes the best to disable it
tabs (with a pretty welcome context menu – very few other products have the same, as can also be seen in the “Tab context menu (if any)” row of the chart of the Web Browsing Bible)
adding the ability to switch off / on keyboard dragging in the context menu
a separate quick access button, next to the “Action” button of the address bar; note that “Search” here makes a quick Google search with the text you enter in the address field.
The settings screen has remained similarly simple – as you can see, there isn’t much to choose from. The same stands for Menu / Spb Pocket Plus, which didn’t change either as can be seen in HERE. As far as saving Web pages is concerned, you can still only save them as simple HTML files – no MHT or full HTML page saving is possible. Incidentally, as can also be seen in the last screenshot, the new SPP version has a system-level (not only available when saving pages, but from every app that would, otherwise, use the system-level, default, very dumb file dialog) file dialog box like that of Mad Programmer, whose FileDialogChanger I’ve often recommended. HERE’s a screenshot of the Setup program where you can en or disable it. (note that, as opposed to Mad Programmer’s FileDialogChanger, you can’t define exceptions – there’re no configuration capabilities of the new “File Open/Save Dialog”).
Compare this to the immense setting / menu options of PIEPlus or even MultiIE and you understand why I still recommend either of these for the serious Internet Explorer Mobile user, as opposed to Spb Pocket Plus. Not that SPP would be THAT bad any more.
It also has some bugs, but, knowing how great the Spb folks at bugfixing are, I’m pretty sure they’ll be fixed VERY soon:
clicking the cross in the upper right corner (to close the IE window) doesn’t work if there are more than one tabs open. You MUST manually bring up the Start menu and switch (in cases, re-run so that the execution is switched to it) to the program you want to. Of course, if you use a third-party task switcher (for example, the highly recommended Magic Button, PHM’s Alt-Tab or almost all the hardware app button enhancers reviewed HERE)
the smooth scrolling mode isn’t really doing what it’s supposed to: in Landscape mode, it’s, in general, scrolling more than it should or even scrolls multiple pages. Some people have also reported other problems with it; see for example THIS.
4. New version of jb5
In the MS Smartphone Web Browsing Bible, I’ve elaborated on the brand new web browser jb5, which, back then, only had a Smartphone version. Late August, a brand new, 5.0.79 version has been released for both the Smartphone and, now, the WM5+ Pocket PC’s. While it’s still having problems and I still consider it much inferior to Opera Mobile / Mini, if you need the special features (for example, in-page text search, which, on the Windows Mobile platform, is only supported by the currently unavailable NetFront and the memory hog & on several handheld models super-slow Minimo) jb5 offers, you might want to check it out. I’ll let you know as soon as it receives a really useful and recommended version.
5. Web Viewer for WM5
There is a brand new multitab IEM plug-in, “Web Viewer for WM5”, HERE.
Unfortunately, this title still has a lot of problems and, consequently, I don’t recommend it. As with jb5, I’ll announce when a useful, bug-free version is released. I also recommend the comments HERE.
6. Other stuff
In some of my earlier articles, I’ve already elaborated on two not really recommended newcomers: TeaShark and UCWEB. IMHO, it’s, currently, pretty useless to bother about these browsers. I’ll let you know when a considerably better version is released.

REVIEW: Another great, multiplatform instant messenger client: Palringo

Instant Messaging is, as with, for example, Web browsers, is a constantly improved area of mobile platforms. This means we’re getting newer and newer instant messenger apps all the time.
Palringo is the newest application to enter the Windows Mobile / Symbian instant messaging world. It, despite of being new, is already is a decent contender really worth paying attention to. Their free (!), multiplatform IM client, Palringo, is certainly worth paying attention to because it has some goodies not present in (most) other instant messenger clients.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(VGA Pocket PC)
(Symbian s60v3)
(176*220 MS Smartphone)
(Current, tested versions: Windows Mobile: 10/25/2007; Symbian s60v3: 0.96 (11) 10/08/2007. Test devices: Pocket PC (HTC Universal, HTC Wizard), MS Smartphone (HTC s310, s710) and Symbian s60v3 (Nokia N95).)
Getting, using
You can download it HERE. Enter your e-mail address twice. It can be arbitrary – that is, on any other server; it must, however, be an existing one so that you can activate the account. Also, create the password you’d like to use with the client. After submitting the info (and signing in with this), you’re taken to the Download page, where just click the “Download” button or buttons, if you select clients for multiple operating systems. Currently, three operating systems are supported: Windows Mobile (Smartphone and Pocket PC), desktop Windows and Symbian S60v3. They also promise a MIDlet (Java) version of their client, bringing IM support to even “dumb” phones, Blackberries and Palm OS-based devices.
Alternatively, if you don’t want to use desktop download / installation, you can fill in your phone number if you want a direct installation link to be sent to you per SMS.
After installing and starting the client, select Menu / Palringo / Online. Enter the e-mail / password pair you’ve registered yourself first at Palringo.
Then, you’ll need to add services to your account. You may want to do this on your desktop computer (with the desktop version if you don’t have a remote controller tool like the excellent Pocket Controller) if you don’t have a decent keyboard for your phone. If you do this on the desktop, the added service accounts will be immediately synchronized to your mobile (and vice versa – and, of course, between mobile phones as well).
Palringo is interoperable with MSN, Yahoo, AIM, GG (Gadu-Gadu), ICQ and XMPP (Jabber). That is, after selecting Menu / Add Service, select the one you’d like to use from the list and, then, just fill in the service login / password as can be seen in HERE. Now, you’ll be logged in. Note that you can add other service accounts any time; you’ll be able to switch between them on the main dialog.
You’ll soon notice Palringo supports multiple logins. Very few IM clients allow the user to log in with multiple accounts into a given IM network: currently, only the, otherwise, not very good Causerie and the band new, beta version of Shape Services’ well-known IM+ for MS Smartphones. (See THIS and THIS threads; their Smartphone homepage is HERE; note that the current (4.45 and 6.15, respectively) PPC and Symbian S60v3 versions still don’t support multiple logins). In THIS screenshot (the same made on a 176*220 Smartphone is HERE and you can see I’ve already logged in with three MSN accounts, and I can still add more MSN accounts by selecting Add Service.
In this respect, therefore, Palringo is without doubt the best.
In addition, it supports groups (pretty much like on the IRC), which is a great way to meet friends or people and is increasingly used by some user communities like that of the infamous XDA-Developers. You can, of course, both create a new or join an existing group. Some screenshots of joining a group: 1 2 3 4 – it’s certainly worth giving a try!
Voice clips, camera stills, clickable links, copy/paste
As with several other clients, it supports sending voice clips. As opposed to, say, Fring (which is without doubt the best IM app in this respect), and just like with Microsoft’s Live Messenger on Windows Mobile (but not on the desktop, where full voice chat is supported), you can only use voice clips, not real-time VoIP. (And, of course, this only works in one direction with non-native Palringo receivers like MSN.) The voice codec is Speex-based, which means it works with acceptable upload speed even over GPRS, while maintaining pretty good sound quality.
Links are clickable on all platforms - certainly good news.
You can paste into the text input field and you can also copy the contents of individual messages (Pocket PC – a HTC Wizard – screenshot HERE). This is good news for Symbian S60 / MS Smartphone (platforms lacking a touchscreen and its mass-selecting capabilities) users but not very good for Pocket PC users, which may want to make mass selection upon wanting to, say, save an entire conversation to a file in one step.
Logging, history
Unfortunately, it doesn’t seem to log conversations on Windows Mobile at all. On Symbian, however, there’s a separate menu item in the chat window, Options / View Older Messages (or, alternatively, activating the thin bar at the top – in the screenshot, it’s purple-colored). This will retrieve the message from the server, which may take some time, particularly if you retrieve a voice clip or an image.
(Windows Mobile users, see the point in providing Symbian info in my articles? The previous paragraph was one of the tidbits that REALLY make it worth discussing multiple operating system versions at the same time. It’s certainly worth knowing the Symbian version is better in this respect – then, you can “push” the developers to implement the same functionality in the Windows Mobile port as well.)
The problem with this kind of logging is that you must retrieve all older messages one by one by either selecting Options / View Older Messages all the time or, better, pressing the bar. In addition, as the old messages / images / voice clips are all stored on the server, it may take some time to retrieve them. However, it’s still better than nothing at all. Still, in this respect, there’re much more advanced IM clients; most importantly, mov Messenger (for both platforms under Windows Mobile).
Notification, vibration, Pocket PC suspended state, Unicode
It seems to support system-level settings on all Windows Mobile devices (as opposed to Symbian); for example, it had no problems with vibration on the HTC Universal and HTC Wizard PPC. I’ve encountered no vibration and/or system-level audio / vibration switching problems with the HTC Oxygen (s310) and HTC Vox (s710) MS Smartphones either. Notification bubbles / taskbar icons are supported on Pocket PC’s; a taskbar icon is supported on the Smartphone platform; they’re all animated. Notification LED’s are also used.
No such icons under Symbian (for example, on the Standby screen), though.
I haven’t had any problems with receiving notifications on Pocket PC’s in suspended state (tested on the HTC Wizard and Universal), which is certainly very good news, battery life-wise. Of course, always-on platforms not using a suspended state (Symbian, MS Smartphone) have worked all the time.
It has no problems with Unicode chars in either direction (tested with MSN).
Symbian issues (and goodies)
While I had no problems with vibrating alarm (in “Meeting” mode) on ALL of my Windows Mobile devices, it didn’t work on my Nokia N95.
The camera interface is inaccessible under Symbian as can be seen in HERE (before capturing – as can be seen, no interface is accessible, unlike under WM – I’ve tested this on all the three WM test devices), HERE (after capturing) and HERE (transferring the resulting shot) but NOT under WM (example screenshot, taken on the Oxygen, HERE and HERE – incidentally, they show my Universal and N95, both running Palringo), where the real interface is used. This means for example the inability to manually switch to macro mode, switch off the flash etc.
Fortunately, under Symbian, you can set a default access point so that the client can automatically reconnect as can be seen in THIS screenshot. Incidentally, this shot also shows that under Symbian, you can independently set the notification volume, unlike under WM.
Also, on Symbian, it isn’t shut down when the free RAM decreases. This is a definite plus on RAM-lacking models like the Nokia N95.
Windows Mobile issues, CPU / memory benchmarks
I’ve had no problems at all. It worked on all my test devices I’ve installed it on (HTC Universal VGA Pocket PC, HTC Oxygen / s310 WM5 176*220 and HTC Vox / s710 QVGA Smartphones) in both Portrait and Landscape orientations. There were no keyboard problems at all and no orientation change flaws; not even on the Vox (which, before the latest version of mov Messenger, had caused problems to the latter.)
CPU / memory usage while actively waiting for incoming messages: 0% and 300…700kbytes on WM, independent of the “Power/Data Saving Mode” checkbox in Settings. That is, very good.
Some other screenshots
Contact list (on a 176*220 MS Smartphone)
Adding a contact: 1 2
Chatting interface on Symbian
Photo, clickable and voice clip sending works from Palringo to MSN – but, of course, not in the other direction.
Verdict
This is an excellent IM client all supported mobile platforms (Windows Mobile Smartphones and Pocket PC’s and Symbian), particularly if you look for a client capable of joining pre-existing IRC-like groups like that of XDA-Devs and/or want a messenger application capable of multiple logins to the same network. It’s only the lack of logging and copying large blocks (not just one row) of text on touchscreen-enabled platforms (Pocket PC) that I really miss.
Related (Windows Mobile-only) articles
The MS Smartphone Instant Messaging Bible
The Pocket PC Instant Messaging Bible (Cross-posts: PPCT, MobilitySite, AximSite, XDA-Developers - 1, XDA-Developers - 2, FirstLoox, BrightHand, HowardForums, TheSmallPicture)
A pretty nice list & quick comparison of the brand new (year 2007) IM apps (that is, Octro, Mundu and Palringo.)
Great article, this is by far my favourite IM client out there.
You should add to the review the fact that it works on http only connections (XMPP over Bosh, probably) and that they have a battery friendly setting (¿HTTP Binding?).
Those last facts are on my own, but I'm pretty sure I'm right
stickman said:
Great article, this is by far my favourite IM client out there.
You should add to the review the fact that it works on http only connections (XMPP over Bosh, probably) and that they have a battery friendly setting (¿HTTP Binding?).
Those last facts are on my own, but I'm pretty sure I'm right
Click to expand...
Click to collapse
Does it support proxy configuration?
I still haven't seen *ANY* IM clients out there supporting (or 'inheriting' wm's) proxy configurations.
My dataplan doesn't allow proxyless connections, everything must go through their proxy - otherwise it won't work.
So im stuck without no IM client. anyone has any suggestions?
Good but...
Sound input from the Sprint Mogul and Touch does not function properly in Palringo. It has horrid clicking and choppiness, and although Palringo has been aware of the problem for some time, no solution yet. (Fingers crossed though). I think there are 3 main problems other than the sound bug.
1: Battery life is absolutely atrocious with palringo open. My mogul burned through 50% of a fresh 1500mAh battery in 3 hours.
2: No way to add new contacts
3: Whenever you close a conversation, like to return to the contact list, next time it opens there is absolutely no history...so this is definitely not for ADD people or anybody messaging more than 1-2 people at a time.
Crash after installing Fring
Here's my story I wanna share in case others encounter the same difficulties:
My Hermes is crashed right after installing the latest Fring (cab over the air). The device now blocks seconds after restarting. The screen remains normal, but it is completely frozen, and no command is possible.
I regret not having made a backup beforehand I'm still trying, but I think the only way out at this stage is to hard reset.
another issue is you have to sign in to parlingo, to use a service.
e.g. i cant use my own IM server in my own network if i can not reach parlingo server.
Never seems to connect to their network for me.
Could be that it's somehow blocked by my school's firewall (I'm on their wifi and don't get cell signal in the building). Anything with HTTP binding usually gets through but I can't find an option for enabling HTTP binding. If only Talkonaut wasn't a java app...
UPDATE (02/27/2008): there's a great review of the app HERE. There's some user feedback worth checking out HERE and HERE. Also note that MoDaCo also has a Palringo usergroup.

Categories

Resources