AKU2 for T-Mobile MDA

Now that I’ve got the T-Mobile MDA in my hands, the next obvious question is whether the Messaging and Security Feature Pack for Windows Mobile (aka AKU2) will be offered by Tmo. AKU2 contains the update for Windows Mobile 5 that changes the behavior of “push email”. The change allows the push-mail functionality that shipped with Windows Mobile 5 to behave more like the BlackBerry.
The original implementation of push-mail in Windows Mobile 5 had the mail system send a specially formatted SMS message to the WM5 device. The SMS message instructed the device to initiate an ActiveSync session with the defined server. The ActiveSync session would then pull the email to the device during the synchronization process.
With the new update, the process has changed so that the system never uses SMS messages to do this. Many users were put off by the need for an SMS package on top of the data package, on top of the cell plan. In the new system, the WM5 device keeps synchronizes itself with the server over the air.
Once the sync is complete the device sends an HTTP request to the server asking for any changes since the last sync – the catch here is that the request has a time out of (I seem to remember) 30 minutes. If the server has an update to any of the synced data during that time, it will return the request to the device indicating new data. A new sync is done and a new HTTP request is sent to the server again waiting 30 minutes. If there are no new data updates and the request times out, the device simply re-issues the request. This sequence goes on unless either the device or server is taken offline, or the configuration is dismantled.
For the new system to work, the device will make enormous use of the data connection. While the device will be connected almost all the time, data transfer only happens during the request and sync periods. If you have an unlimited data plan, that really takes the concern out of the picture cost-wise. Also, this is fairly battery efficient as simply keeping the data pipe open doesn’t use much power, only when transmitting/receiving.
It’ll be interesting to see how well this system works out. T-Mobile just released the MDA a few weeks ago so I’m sure they don’t have the AKU2 update pending too soon, and I currently have my MDA simply polling my email accounts on a 15 minute cycle. There are real needs for push mail like the BlackBerry and Microsoft’s implementation, but it is not a requirement for me at this time. Neat stuff!

Where oh where is BlackBerry Connect…

RIM’s BlackBerry supposedly offers a BlackBerry Connect for Windows Mobile software component.  What I need to figure out is where do you find this elusive software?  Do you get the software along with BlackBerry Enterprise Server, a separate offering, free download, WalMart, at the bottom of my favorite cereal box – where?

The dissapointing thing for me on the BlackBerry front is that there are so few real sources of information and solutions on the Internet.  For Windows Mobile, there are thousands.  This is the difference between a closed system like BlackBerry, and an open environment like Windows Mobile.

I’m not going to debate the supiority of the BlackBerry push email system – that is obvious, but what I have trouble with is the lack of acceptance of customer choice.  The company I work for is planning on rolling out BlackBerry services, for a number of reasons.  But what I see is a true lack of choice for our users.  What do you tell a senior exec when they come back with a spiffy new Windows Mobile device and you tell them that they cannot use it with our new push email system?  With the rates charged for the support contracts, you would think they want to cover all the needs a corporate customer may need.
Come guys where is the customer choice?

Pocket PC Works!

Well, this is my first attempt to post frorm rry my iPaq, and I’m pleasentty pleasently surprised to find that WordPress works well with the older uerspon version of Pocket Internet Explorer.

Now lets hit the publish button and see what happens.

Update: It does work well – of course I was using “Transcriber” and made a few mistakes that I had to come back to correct. 🙂

RIM, NTP Settle Legal Dispute

So RIM finally broke down and paid off NTP…

RIM has paid NTP $612.5 million in full and final settlement of all claims against RIM, as well as for a perpetual, fully-paid up license going forward. This amount includes money already escrowed by RIM to date.

Since I did not follow the technical details of NTP’s claims or RIM’s arguments against patent infringement, I can’t comment on if I think this is a reasonable course of action for RIM.  However, now that the uncertainty that has surrounded a “possible” shutdown of the Blackberry service, maybe we can all start looking forward to future devices and services from both companies.

Via: RCR Wireless News, RIM Press Release

Complaints Against Mobile Operators in Decline

So, The Wireless Report has posted an article that talks about CTIA (Cellular Telecommunications Industry Association) announcing a drop in customer complaints against the mobile phone carriers.  They also express their doubts about its accuracy.  While I hope that the carriers have improved their customer service (T-Mobile & Verizon seem to be working at it), I also am concerned that the overall customer satisfaction is still not increasing.

Check out The Wireless Report & CTIA itself.

Pin It on Pinterest