Category: Smartphone

Windows Mobile Smartphone

  • Back to Basics: Jumping Bluetooth Com Ports

    One of the two RAM DIMM sticks in my main PC went bad last week. So, I had to unplug the cables from the back, take the case cover off, replace the bad DIMM (lucky to have guessed on the first try which of the two DIMMs was bad), replace the cover, and plug all the cables back in. Simple, right? One would think so. But, not really.

    My Bluetooth USB dongle is on a USB hub. When I plugged the hub and other USB cables back in, I didn’t plug them back in to the same USB ports they were in before I took the PC’s case cover off. After I turned on the now repaired PC, I tried to Sync my Windows Mobile smartphone over Bluetooth. Didn’t work. When, I checked ActiveSync, it showed grayed out options. A bit of digging around revealed that the pseudo COM port Windows XP assigned to the Bluetooth dongle had jumped from COM4 to COM6. A bit of fiddling around fixed this and got things working as expected.

    So, if you need to pull cables from your PC, be sure to note which physical port the Bluetooth dongle is assigned to. FYI: This is an issue for the USB sync cable too. Although it does not suffer from the jumping pseudo COM port issue, Windows will not recognize your Windows Mobile device hardware and will have to re-recognize it. This should not require any intervention on your part. But, it does take a bit of time and may be anxiety causing the first time you see this. This has been like this for years. So, I don’t expect it to change anything soon.

  • Mailbag Q&A/Back to Basics: ActiveSync and Bluetooth

    Having used Windows Mobile devices since 1997 when the Handheld PCs running Windows CE (still the core engine underneath the Windows Mobile shell) had been out for just a few months, I sometimes forget that things that seem obvious to Windows Mobile enthusiasts may not be obvious to other people. So, I’ll pontificate 🙂 talk about some real basic type topics here now and then to try to help people who haven’t spent the past decade playing with these things.

    Back in May I posted a short video to YouTube titled T-Mobile Dash WM6 Bluetooth ActiveSync demonstrating syncing with my PC using BT. I received an email from viewer ZTT asking:

    hello, so on active sync you just have to turn bluetooth on and how does it connect to the computer? does the computer have to be bluetooth??

    Oy! Good question. Microsoft ActiveSync and Bluetooth (BT) are two of the most problematic basic tech items I know of. They shouldn’t be. But, they are.

    First, yes, your desktop or notebook computer must have a Bluetooth radio in order to sync with a Windows Mobile device over Bluetooth. Unlike Apple Macs (which all have BT these days), very few desktop and notebook Windows PCs come with an intergrated Bluetooth radio. Some notebooks have the option have adding an integrated BT radio at the time of purchase. If your Windows PC does not have BT, BT dongles are fairly inexpensive these days.

    You need to partner your Windows Mobile device with the PC using a USB cable the first time. If all goes well, you should be able to configure ActiveSync and the WiMo device to sync over BT. I have an earlier blog entry that details this process. It can be found at…

    Tips for ActiveSync With Bluetooth

  • Mailbag Q&A: Using a Mobile Phone for Heart Attack Care

    Reader D.S. has an interesting question. I usually post interesting questions because I think the question and my response might be of general interest. This time, however, I’m posting it because I think the question needs a better response than I can provide. D.S. asks…

    We are in the midst of setting up a system to improve the care for patients who are suffering a heart attack in the city and county of […]

    One significant issue is how to to allow the cardiologist to see the electrocardiogram. This is important for the cardiologist to make a decision as to whether an emergent cardiac catheterization should take place.

    Obviously if it is during business hours or if the cardiologist is at home and has a fax machine, this is not as much of an issue.

    However, we need to address the possibility that the cardiologist on call is out and about. Hence the question about how a cardiologist might be able to view the electrocardiogram in the field.

    One thought is for the cardiologists to have mobile devices. In my research of the topic, there do appear to be ways for a fax of the electrocardiogram to be sent to a mobile device. However, the worry is that there is still a delay, especially with a fax to email solution. In acute heart attack care, seconds and minutes count, so the image would need to be available in real time.

    In your experience, what would you recommend as a way to get an image of the electrocardiogram to the cardiologist. Some way for the emergency room to send a fax of the electrocardiogram to the phone? Could it be send via MMS messenging?

    First, here’s a caveat/disclaimer: My response here should not be considered as advice, recommendation, or consultation. It is merely a response to an interesting question. (Sorry for the weasel words :-).

    Couple of thoughts…

    1. First, before starting on the technical aspects of the project, be sure to consult with an authority in the Health Insurance Portability and Accountability Act (HIPAA). You may need to encrypt the electrocardiogram image for transmission.

    2. As you point out both SMS and email are subject to potential delays. And, sending images may be problematic depending on how email is configured, the storage capacity of the receiver’s mail server, and other factors. It may be worth investigating the possibility of keeping multiple resolutions of individual images (low, medium, high) on the server and sending alerts to the cardiologist via simultaneous multiple channels: E.g., automated voice call, SMS, email. This message would point the receiver to a password protected site where the image could be called up on a mobile device for viewing.

    3. Don’t rule out the possibility of an old-style client-server application where coded alphanumeric data is sent from the server to the client (mobile device) instead of a graphic image. An electrocardiogram image could be rebuilt from this smaller coded data. This could greatly reduce the amount of data that is sent compared to an image file and thus speed up the process of receiving and viewing the electrocardiogram image.

    Here are links to two mobile technology sites that may provide more information than I can provide.

    MedicalPocketPC.com

    Smartphone & Pocket PC Magazine has an M.D. as a regular contributing author

    Finally, if anyone has other information links that might be useful to D.S., please post it in a comment to this blog entry.

  • Google Gmail IMAP4 Works Fine with Windows Mobile

    My Google Gmail IMAP4 feature was turned on earlier today (Oct. 25, Thursday). The first thing I did was test it with a T-Mobile Dash (Smartphone AKA Standard Edition) running Windows Mobile 6. And, yep, WiMo’s Messaging (email) works fine with the new Gmail feature.

    Google provides step-by-step instructions to configure Windows Mobile 6 to work with Gmail and IMAP4.

    Google Mail Help IMAP Windows Mobile 6

    However, experienced WiMo users may find the less eye-glazing generic help page faster to go through.

    Google Mail Help IMAP Configuring Other Mail Clients

    Google’s IMAP service seems a lot slower than service on other IMAP servers I use. However, it may simply be because of all the new clients being configured and downloading email. I’m hoping this will clear up (speed up) within a couple of days or weeks.

    Addendum: Hey, I just noticed my Gmail storage is up to 4.3GB. When did that happen?

  • Issues With Recurring Meetings in Windows Mobile

    Microsoft’s Jason Langridge wrote an interesting blog item related to recurring meetings earlier this week…

    Having Problems With a Calendar With Lots of Recurring Meetings?

    The problem, it turns out, occurs because Microsoft creates recurring meetings out to 400 years if no end date is set. Um, who was the big brain who decided on that I wonder? I suspect many of us set recurring events that go on forever even if we don’t expect to live for another 400 years. And, I wonder if birthdays and anniversaries are set using the same recurrence algorithm? That might explain some of the bizarre behavior there. Many WiMo users have seen birthday events multiply inexplicably. Some have even seen birthdates split across two days after Microsoft issued a patch to deal with the fact that Daylight Savings’ start and end dates were changed in the US this year. And, then, there is the problem of changing just a single occurrence of a recurring event that I’ve described earlier…

    Here’s the scenario for that problem: Set a recurring appointment (e.g., weekly staff meeting) with no end date in Outlook on the PC. Sync the PC with a WiMo device. Detach the WiMo device from the PC. Change just one of the meetings in the series on the WiMo device while leaving the other recurring events in place. Sync the WiMo device with the PC. When I do this, the single event changed on my WiMo device reverts back to the original date/time after syncing with the PC. It does not happen 100% of the time. But, I would say it happens at least 50% of the time for me.

  • The Have and Have Nots: Windows Mobile vs. iPhone Sites

    Weather.com Mobile

    The screen shot on the left is of the Weather.com site on a Windows Mobile 6 Pocket PC (Professional Edition). The screen shot on the left is the same site tweaked for the iPhone on an iPod touch. Although it takes a lot longer to load on the iPod touch (both devices were on the same WiFi network although the Pocket PC was limited to 802.11b vs. the 802.11g for the iPod touch), the iPhone version sure looks a lot nicer and provides a lot of functionality without scrolling up and down.

    Microsoft has a lot of work to do to bring the Windows Mobile Internet Explorer browser into the 21st century. The iPhone has clearly inspired a lot of firms and their web designers to maximize web-impact for the iPhone’s Safari browser in a way that we have not seen previously for other web-enabled mobile devices.

    Microsoft’s announcements of more enterprise mobile-enabling products for 2008 is good for the enterprise. But, again, that is clearly not where most of us are these days even if we work for a large organization. Microsoft really needs to focus on the basics and fix the broken stories at that level: Internet Explorer, ActiveSync and Windows Mobile Device Center, and alarms are just a few of the basics that need fixing.