Log in

View Full Version : Connectivity Nirvana: We're Not Quite There Yet


Jason Dunn
02-20-2004, 06:30 PM
<i>This is an article written by a Pocket PC Thoughts reader named Andrew. It raises some very interesting points about mobility, connectivity, and some of the problems with the Pocket PC OS as it stands now. If you have suggestions on how to solve Andrew's connectivity issues, I'm sure he'd be glad to hear them!</i><br /><br />----------------<br /><br />Lately I've been spending far too many hours trying to figure out how to make my iPAQ 2200 + Bluetooth phone act like a Windows Mobile Smartphone. What do I mean by this? Allow me to explain.<br /> <br />Right now, I have a "Tanager" Smartphone in addition to my Pocket PC. I really like it, particularly as a complement to a laptop, because the one-hand integration makes it easy to use while on the move. The thing that is most addictive is Exchange ActiveSync on a regular schedule - since I have unlimited GPRS, I set it to sync every 5 minutes, so that I can be pretty sure that any time I have a second to pull the phone out and check my mail, I've got the latest without having to go and hit the server again. <br /> <br />However, there are times that I do prefer the larger screen and File Sync capabilities of my iPAQ + BT phone combo. And trying to make a non-Phone Edition Pocket PC embody the best traits of a Smartphone is...challenging. Maybe I should just give in and get a Phone Edition device, but then, the whole point of a Pocket "PC" is the ability to customize the device and make it do exactly what you want, right? So, I've been on a quest to see just how close I can come. It's been probably a month or so that I've been actively pushing the boundaries in this area, and I thought it would be interesting to catalog my findings so far.<!><br /> <br /><b><span>My Perfect World vs. The Real World</span></b><br />In my perfect world, I would like to turn on my Pocket PC, have it automatically dial a GPRS connection through my Bluetooth phone and have that connection persist until I turned off the Pocket PC. I would also like to be able to power-off my device instantly regardless of whether or not I have a connection open and not have any ill effects (since one of the huge advantages of a PPC is "instant on/off"). This is connectivity nirvana for me.<br /> <br />In the real world, there seem to be a few issues:<br /> <br />1.) Powering off the Pocket PC with a GPRS connection established via Bluetooth produces an error message the next time the device is powered on (minor but very irritating). But much worse, trying to reestablish the GPRS connection after dismissing the error won't work - a soft-reset of the Pocket PC is necessary before being able to use GPRS again. Perhaps this behavior is specific to the iPAQ 2200 but regardless it can be frustrating.<br /> <br />(Why don't I just disconnect prior to powering off? Because it requires 6-8 seconds and a stylus tap - inconvenient for quick browsing or e-mail sync while waiting in line for something, for example. Easy one-handed use is key!)<br /> <br />2.) There is no convenient way to establish a GPRS connection - that I'm aware of - that does not involve pulling the stylus out and tapping several small icons/buttons. An existing option that's map-able to a hardware button would be optimal, but I'd settle for being able to create a shortcut. Using a Smartphone has really spoiled me when it comes to easy one-hand access to functionality!<br /> <br />3.) I'm quite certain there's no way to auto-connect to GPRS on power-on using the default OS and apps. I've found one third-party application on Handango that claims to automatically redial a GPRS connection when you power on the device, but it's not optimal.<br /> <br />4.) Using ActiveSync I can manually initiate an EAS sync with no connection open, which will automatically dial a GPRS connection (good). However, when it's done syncing, it also automatically disconnects the GPRS connection (good for folks who pay by the MB; not so good for those of us blessed with unlimited GPRS). I tried to find a setting or registry key to change this behavior but was unsuccessful. I can use IE to similarly automatically dial a GPRS connection, but if I initiate an EAS sync while connected that way, the EAS will disconnect the connection when it's done. I'd love to know about a workaround for this.<br /> <br />5.) Following the Smartphone model, I've even tried using an application to turn off the Pocket PC's screen instead of powering off the device itself, since this would mean the connection would persist at the cost of battery life (the device in theory doesn't power off by itself while a connection is present). However, quite often when I've done this for more than about 45 minutes, I find that the device has powered itself off somehow. I don't think it's possible that the power button is being pressed accidentally (if it's in my pocket, for example) because I've never pulled the Pocket PC out of my pocket and discovered the screen on or that other applications were open due to pressure on the touchscreen. I guess I could just change the settings so that the device *never* turns off, but that seems risky in scenarios like the old "wake up at midnight with Media Player running, battery dead the next morning".<br /> <br />6.) After giving up on some of the "always connected" scenarios above, I tried setting my Pocket PC to Exchange ActiveSync using my phone's connection every 5 minutes during "peak hours", with the device dialing and disconnecting. Since the above has demonstrated that it is apparently impractical to maintain a constant GPRS connection all day, this means that my Pocket PC will dial into my phone via Bluetooth every five minutes in order to sync, and then disconnect when finished. Good enough. However, there is a problem when I am actually using the phone for voice calls. If I am talking with someone and the Pocket PC tries to initiate a connection to sync, it *hangs up* on my voice call and establishes a GPRS connection instead. Needless to say, this is not desired behavior. I verified that the "wait for dial tone" box is checked in my settings for the connection I'm using to dial; however, I suspect this is irrelevant to GPRS connections both from my limited understanding of the technology and also the fact that having the box checked doesn't fix the problem. My latest idea is to answer my phone when a call comes in and then quickly disable Bluetooth on the Pocket PC, which is not exactly optimal. : )<br /> <br />My hat's off to Microsoft for doing a great job with Pocket PC Phone Edition and Smartphone - but it would be great to see some of that same amazing experience for those of us who like to carry two devices.

spinedoc
02-20-2004, 06:53 PM
I have been trying to do the same thing for a very long time.

Currently I have an Ipaq 2215 paired with a SE T608 phone. Now you GSM guys have it real easy compared to the few of us with the only CDMA bluetooth phone!

I have tried mphone, running voice, pocket phonetools, and a few others I forget. The only one that works halfway decent is mphone, but its quite buggy.

I have the same hope, to make my 2215 into something close to a mobile phone. It is extremely frustrating. Based on the software solutions I have used it seems like it is really up to the 3rd party developer to come up with a good solution. Most of these solutions seem to be made in someones garage and dont really work very well. Take picture caller ID, is that really that hard to ask for? Only a few of the programs do text caller ID, and buggy at that. Don't even get me started on the issue of the Ipaq not supporting audio gateway/headset, even though it is a hidden fix in the registry.

Good luck on your quest, and please keep us informed. You are not alone!

dd-mj
02-20-2004, 07:12 PM
I know that I want in my next PDA/Phone. I want a PocketPC version of the Color RIM Blackberry with Phone capability. I want to recieve email and messaging without ever thinking about sync'ing. I want my Phone/PDA to vibrate when a new message or IM comes in.

I want a large screen with a thumb keyboard, because that is the only way I can really efficently reply to email and IM.

I would buy a color RIM with cell phone capability today, except I love the PPC platform and large suite of applications.

The recent pictures of the Moto MPx300 get me really excited. That looks close to what I want.

kendrick
02-20-2004, 07:18 PM
...the whole point of a Pocket "PC" is the ability to customize the device and make it do exactly what you want, right?

I haven't upgraded from my trusty old Casio yet, but as I remember the strict definition of the Pocket PC the point of it was to have an extension of your desktop. As written, the specs of the original Pocket PC were intended to give somebody a way of having their data available without having to be right next to the main workstation. That's why we have to do things like synchronizing and hard resets. :/

I don't mean to tell anybody what they can and can't do with the hardware that they buy and own. (In the interest of full disclosure, I don't use Activesync and use my device mostly for games, so I'm not exactly a representative Pocket PC user.) But to that point, has Microsoft's documented 'definition' of a Pocket PC changed with the 2002 and 2003 iterations? If a Pocket PC is intended to be a stand-alone device now, then Microsoft has a long way to in the areas of application support and portability. On the other hand, with people installing the .NET framework on everything (including toaster ovens) maybe we're closer to stand-alone Pocket PC's now than we were then.

-KKC, tired out after 45 minutes on the dance game, but that's a subject for a whole other discussion board.

fmcpherson
02-20-2004, 08:11 PM
I have been doing something similar. I have a SoneyEricsson T68i phone and an iPAQ 4155. For some reason the 4155 has a difficult time connecting to the T68i via Bluetooth unless the phone is in Discoverable mode. (I don't know why, my 2210 never has problems connecting.) Since there is no way to keep the T68i in Discoverable mode for more than 3 minutes, I would have to manually put the phone into discoverable mode every time I want to connect, which is hardly convenient.

My work around is to use Running Voice. In the morning I start Running Voice, turn on Bluetooth Discover on the T68i and establish a connection, and then use a hardware button to turn off the screen. Since Running Voice keeps the Bluetooth connection open, I can then just put my phone away in my pocket and fire up a GPRS connection from the phone whenever I want. Battery life doesn't seem to be too much of a problem when doing this, unless I am doing a lot of GPRS stuff. I have gone with long periods of time maintaining a GPRS connection and haven't run into the Pocket PC closing the GPRS connection, however I do tend to have problems GPRS goes away while the phone/Pocket PC thinks it's still connected.

(BTW, if all I wanted to do was turn the screen off I could just use Windows Media Player to do that. However, I also like the phone features that Running Voice provides, providing some of the Phone Edition functionality to my 4155.)

Scott R
02-20-2004, 08:37 PM
Andrew, I think #6 is about as good as you can expect to get. I don't think that having your PPC always connected to your phone via BT but with the screen off is going to be practical any time real soon due to battery life issues. I would imagine that it would drain your PPC's battery way too fast. What is reasonable to expect is for your PPC (or phone) to be smart enough not to hang up an existing call and, instead, wait xx minutes to try again (or just wait for the next scheduled interval). Now, I'm wondering whose fault this is? Is it...
a) The PPC blindly killing the phone connection so that it can do it's thing.
b) The phone not being smart enough to disregard the PPC's request to connect.
c) An inherent weakness of the Bluetooth protocol.
d) The application that you're using.

Hopefully, the answer is (d) as this could be addressed by the developer coding the app to ignore the scheduled interval if a phone call is in progress and try again later.

So, does anyone know the answer? I might be able to provide some insight later. In addition to my iPaq h4155, I also have a Tapwave Zodiac (Palm OS for those that don't know). I own a copy of SnapperMail for the Palm OS which can do scheduled interval checking of email. I'll simulate the example you provided and let you know what the results are.

Scott

Bandito
02-20-2004, 10:08 PM
What model is your Bluetooth phone? This is going to sound like a pretty weak workaround, but since we are restricted by limitations of these devices, it seems only fitting that you use one of these limitations to your advantage...

What I've discovered about most Bluetooth phones (actually, every one that I've tested, but I haven't tested 'em all) is that they can only have one active Bluetooth connection. That being said, here's my solution. When you're using your phone for voice, use a Bluetooth headset. That way your one active Bluetooth connection will be used up and your iPAQ will fail to connect. Also, you get to use a Bluetooth headset :)