Archive

Posts Tagged ‘Windows Mobile’

Google Voice Web App for Windows Mobile

January 31st, 2010 1 comment
This entry is part 9 of 10 in the series Google Voice

The other day it was announced all over the web that Google Voice was finally available again for the iPhone, only as a web app instead of a true app. Google created a web page at http://m.google.com/voice rather than trying to get another app approved n the App Store. I checked it out on my iPhone (yes, I have one too — for work) and it is a great app. Although it doesn’t integrate fully with the iPhone contacts and dialer, it does present a decent dialer of its own and works very quickly and cleanly, initiating calls via the web and calling the handset back to complete the call.

Google says on the mobile web page that the m.google.com/voice page works for the iphone and for BlackBerries; the page identifies the phone type when you get to the page and directs you appropriately. So I wondered what would happen if I went there with a Windows Mobile browser like Opera.

Google Voice Mobile Screen

The result is a useful if ugly web page. The interface is limited to simple links, but all the necessary functionality is available. You can initiate a call by simply adding the number or selecting something from your Google contacts (it doesn’t integrate with your phone contacts). You can also see and manage any voicemail messages that you have.

By assigning Opera to a speed dial key on the phone and then assigning the Google page to a numbered bookmark, the page is only three clicks from any page on the phone. It isn’t quite iPhone convenient, but it works.

The downside to this implementation is that it’s dependent on a data connection, so you can’t use it where you have phone only service. This probably isn’t an issue for Verizon customers, but us T-Mobile and AT&T folks need to worry about these things.

Google Voice Mobile Connect Screen

Initiating a quick call is pretty simple and it does integrate with your contacts. It uses the callback method, so once you input a number or select a contact to call, you are presented with a list of your registered phones and the option to select the one to connect with the call. The iPhone app recognizes that it’s your iPhone, and once set up will always ring back to that number.

Please note that I have captured these screens from my Dash 3G with its tiny QVGA screen. I’m willing to bet that this app will look and work better on a larger touchscreen device. But at least those of us with non-touchscreen Windows Mobile smartphones finally have a workable Google Voice method besides GVoice Dialer. At the very least, it will give me another option to overcome the problems I’ve been having with GVoice Dialer connecting, particularly in noisy environments.

Another Dash 3G Update – Upgrading the Radio

January 7th, 2010 1 comment
This entry is part 9 of 11 in the series Dash 3G

The other day I flashed my phone to the latest version of the 3Volution ROM which Ookba had released on XDA-Developers. It’s been three days now and I’m very happy with it. It’s stable and fast and, so far, everything woks as expected. Even the Skyfire ALT key bug has been fixed.

There was really only one last thing to tackle on this device: the cellular radio itself. In a cellphone, there are really two sets of code that make things work, The Phone’s Operating System (OS) and the radio software. The OS controls all of the functions that you can see, while the radio software controls the way the phone communicates with the network. The OS and the radio can be installed separately.

Users on various message boards have reported that their phones seem to drop their 3G data connection back to EDGE speeds whenever they end a phone call. And a few people have complained that their ability to capture a 3G signal in the first place is suspect. Some people hope that an upgraded radio software package from the manufacturer will address some of these issues. In fact, it probably won’t, since connection speed decisions are made by the network and not the phone, but at any rate I figure that if HTC released a newer version of the radio software, there must be some improvement in it….

My Dash 3G originally shipped with radio version 3.44.25.30 (check yours by going to START/SETTINGS/ABOUT). The manufacturer (HTC) released a Windows Mobile 6.5 upgrade separately from the T-Mobile upgrade, and the HTC version had some updated radio code in it. Ookba managed to extract this package and build it into a stand-alone update, with version 3.47.25.29 in it. And that’s what I installed.

The Verdict

Well … the flash worked perfectly and everything installed in about a minute of work. Did it change the way my phone behaves? Not that much that I can see. It certainly doesn’t seem to have hurt anything, but there is no dramatic improvement either. I think that I am able to get better signal on my normal commute, but this could also very well be the result of T-Mobile’s ongoing network upgrades too. I don’t get any faster speeds when my laptop is tethered. I’m not sure yet whether actual phone performance is enhanced (I haven’t made enough calls).

So my recommendation is this: if you are comfortable flashing your phone, go for it. You might see some marginal improvements. But if flashing makes you nervous, then there’s no reason to suffer through this – the improvements aren’t dramatic.

Upgrading the 3Volution ROM on my Dash 3G

January 3rd, 2010 1 comment
This entry is part 5 of 5 in the series 3volution ROM

I’ve been running a custom ROM on my Dash 3G since its creator, Ookba, released it on XDA-Developers.com. I had been running his version 3VO.1.60.090209 since it was first released.

Since then a couple of supposedly improved versions have been released, and although the 090209 version had only one major flaw as far as my use was concerned (a weird bug where the ALT key didn’t function correctly when the SkyFire browser was launched from an e-mail link – it worked fine everywhere else) I thought I’d upgrade anyway to take advantage of any additional fixes Ookba built in.

I downloaded the latest version posted (3VO.2.50.112509) and installed it following the same procedure I used initially. The install worked flawlessly.

Although I initially had a problem where it seemed that the keyboard map was wrong and the SHIFT and ALT keys wouldn’t work, I believe that I had a corrupted download. Because I re-downloaded the file and flashed again and everything seemed to work.

So far, this release solved my major problem — the keyboard now works in Skyfire. I’m sure there are many more things to cover and I’ll write about them soon.

I just wish I could say the same thing for the ROM. The 112509 version had a major bug in it that left me dead in the water: It appears that the English keyboard maps are totally corrupted in this version and the SHIFT and ALT keys don’t work properly. And unlike before, where it only affected Skyfire, in this version they were broken everywhere. So the 3VO.2.50.112509 version was a total bust for me — and I cannot recommend that anyone use it — at least until the keyboard map issue is fixed.

For what it’s worth, I did switch the keyboard map and tried not only the stock Dash 3G map but a British version and the map for the Sprint Snap. Neither fixed the issue.

So – rather than rolling all the way back to the 3VO.1.60.090209 version, I rolled back to a version between that and the 3VO.2.50.112509 version. I am currently running the 3VO.2.00.101009 version. After 15 minutes of configuring my mail and getting my apps set back up it seems like a good successor to the 090209 version. There are some cosmetic changes to the START menu — I don’t know what else was supposedly fixed or tweaked. I’ll write about anything that comes up.

Another Google Voice Option for Win Mo and My GVoice Dialer Issue

November 3rd, 2009 1 comment
This entry is part 7 of 10 in the series Google Voice

As I posted before, my current Dash 3G is a non-touchscreen, Windows Mobile Standard phone, so I don’t get to enjoy the really cool stuff made for the Windows Mobile Professional, touchscreen crowd. Like iDialer. And like another Google Voice dialer I ran across,One Dialer, which appears to be a full-featured Google Voice dialer with SMS and address book support. If anyone checks it out and cares to tell me how great it is, please do!

GVoice Dialer Issue

GVoice Dialer is a decent application, and probably the best bet for Windows Mobile Smartphone users. If it integrated better with the native dialer and address book and supported Google SMS I’d be completely sold. But there is one problem I’m having. About the only parameter you can configure on GVoice Dialer is the delay between when it initiates a call and when it begins dialing the string of numbers that tells Google that you want to dial a call. The help suggests that a delay of six to eight seconds is usually sufficient. But lately I’ve been having a terrible time getting the Google menu to recognize my calls and I’ve had to extend this delay to as long as ten seconds to make it work.

I believe that this is primarily related to T-Mobile and slow call connecting. But … I never had this problem when I was using the GV Dialer trial. If I listen when GVoice Dialer is trying to call, it sounds like it’s simply dialing all the numbers too fast, but additional delay seems to help. I just wish someone would make a decent Google Voice client for us smartphone users …

Another Windows Mobile Dialing Option for Google Voice

October 31st, 2009 No comments
This entry is part 6 of 10 in the series Google Voice

Credit CardsSince making calls via Google Voice requires nothing more than entering a series of digits on your dialpad, there is a whole class of programs available for Windows Mobile, which I skipped in my software review, but which can be adapted for this purpose. Calling Card or Credit Card dialers. Think about it – using a calling card requires essentially the same functions as using Google Voice: dial a phone number, enter a PIN or other ID number, navigate a menu, and finally, dial the number you want to call.

So, if none of the Google Voice software that I identified for Windows Mobile works for you, you can always try to adapt a calling card dialer like Sunnysoft Calling Card or another freeware program. I haven’t tried this yet since I’m still trying to work through the bugs in GVoice Dialer, but it might be worth a shot if Calling Card gives better integration with the built-in address book. There’s a good post from an early Google Voice (Grand Central) adopter at http://technologyinmind.com/?p=107 who uses the Calling Card strategy and likes it.

Google Voice Clients for Windows Mobile

October 24th, 2009 No comments
This entry is part 3 of 10 in the series Google Voice

My Dash 3G is currently running Windows Mobile 6.5. The smartphone version — it’s not a touchscreen device. Since I’ve been using Google Voice I wanted a client or dialer on the phone that would seamlessly integrate with the phone’s normal calling function. I’ve tried several to this point and none is really satisfactory.

Making Google Voice Calls

There are really two ways to initiate a Google Voice call — via telephone or via the internet. In the phone-based method, you call your own Google Voice number and then enter your PIN and elect to make a call. You enter the number to dial and Google connects the call. In the internet version, you navigate to the Google Voice web page, log in, enter the number to dial and tell Google which of your phone numbers you wish to use for the call. Google completes the call and then rings your designated phone.

All of the Windows Mobile programs out there use one or a combination of these methods to make Google Voice calls.

GV Dialer

Confirmed 10/26/2009: the GV Dialer author has abandoned the project and left current users hanging out to dry. See this blog post and this screen:

F' You GV Dialer Users!

F' You GV Dialer Users!

It’s a shame too, because GV Dialer was probably the best Windows Mobile client out there.
Google doesn’t offer a dialing app for Windows Mobile yet so I was forced to look for 3rd party apps. The first that I found and tried was GV Dialer. And frankly I liked it. GV Dialer was simple: it inserted itself in the native Windows dialer so that whenever you initiated a phone call via any of the normal methods, you would be prompted whether you wanted to use your normal phone or Google Voice (it could also be set to always use one or the other). GV Dialer would then call your Google voice number and automatically enter the digits to work through the Google menu and initiate your call. It was very simple and it worked seamlessly. I liked it. The problem? It seems like the author stopped development abruptly before my trial expired and I can’t activate it to a full license. When you go to their website now, all you get is this:

No GV Dialer For You!!

No GV Dialer For You!!

Based on the blog on the site, I’ll bet that having the iPhone version pulled from the App Store killed any hope of actually making money so the author abandoned it. But it’s a pretty shitty thing to do to not even let people activate versions they already have. So I’m, stuck with a no longer functioning version of a program I liked and I had to start all over again.

iDialer

iDialer is a popular dialer replacement for Windows Mobile, originating (like so many things) on XDA-Developers, but now hosted on its own page. Upgraded or hacked dialers are popular with the touchscreen smartphone people (for reasons totally lost on me — I’ve never seen a single one that really offers much more than the standard dialer, with the exception of the Google Voice Support in iDialer) and iDialer is one of the more popular ones available. The new integrated Google Voice support is particularly cool. The problem of course is that the author wrote it for touchscreen devices only, so it works poorly at best on the Dash 3G. And, like most hacked dialers, it doesn’t replace the native dialer, so you have to start the dialer separately to use it which seems ridiculous to me. Nonetheless, a few users swear by it, even for non-touchscreen phones (see the second post of  this thread for example).

The main advantage of iDialer is that it can use both the dial-up and internet methods of initiating a Google Voice call. In some cases, the internet method is faster since there are fewer digits to input. But that isn’t nearly enough to overcome the limitations of trying to use this touchscreen app on my non-touchscreen device. So I gave up after only one day.

GVoice Dialer

That leaves GVoice Dialer as the client I am currently using. It works similarly to GV Dialer only not as seamlessly. For GVoice Dialer you need to initiate a call by starting the app first. Then you can select a number from your address book and initiate a Google Voice call. This is one extra step than GV Dialer required, but I guess it’s better than nothing. To speed up the process I assigned GVoice Dialer to a speed dial key on my phone so I can start the app quickly and then quickly jump to my address book.

The Ideal Program

What would be the ideal Google Voice client for me? First and foremost it would integrate with the native dialing functionality. That means absolutely no starting of any extra programs before initiating a call. One should be able to browse the native address book or type a number as normal and then be prompted whether to make a normal call of a Google Voice call. The program should also have a blacklist and whitelist, so you could designate numbers to always use Google Voice or never use Google Voice. If someone could do that I’d pay good money for it.

Updated List of My Windows Mobile Software

October 1st, 2009 No comments
This entry is part 8 of 11 in the series Dash 3G

Here’s a quick list of the software I’m running since upgrading to ookba’s ROM. Links are provided where possible:

  1. Opera Mini (included with 3volution ROM)
  2. Skyfire (included with 3volution ROM)
  3. Bing Search for Mobile
  4. Facebook App (from Microsoft)
  5. Garmin Mobile XT (modified to run from my own SD card, see this post)
  6. Google Maps
  7. GPS Test
  8. GPSed
  9. GV Dialer
  10. Midomi
  11. Nimbuzz
  12. OggSync
  13. Pandora (I got the CAB from xda-developers, but official page is here),
  14. PocketTwit
  15. Ilium Screen Capture
  16. Skype
  17. TCPMP (part of the 3volutioin ROM)

Dash 3G – Quick Impressions of 3volution ROM

September 7th, 2009 No comments
This entry is part 3 of 5 in the series 3volution ROM

It’s been one day since I flashed my phone with a “cooked” (custom) ROM that I found on XDA-Developers. And so far I have no regrets.

3volution Homescreen

3volution Homescreen

ROM chef “ookba” did an excellent job on this package, including some very clean and tasteful themes for the phone. I normally find most phone themes so cluttered and distracting that the first thing I do is set the background to a simple, plain black. But the default “Islands” wallpaper on this ROM is actually so nice I want to keep it. And it passed the ultimate test … my wife saw it and said that she’d like to flash to this ROM just for the look of it. And, perhaps greatest of all, as you can see in the homescreen picture to the right, there are some decent colored battery, signal, and other icons baked right in! I don’t have to spend another day with those shitty white icons that ship with the default Windows Mobile ROMs.

Once installed, it only took me about an hour to reinstall all my software and get my mail accounts set back up. I have to say, using an Exchange server at work for my primary contacts manager is a blessing, as is Google Apps’ support of IMAP4. Long gone are the days of losing mail that was saved to your handheld. It takes only 5 minutes to completely rebuild my mailboxes from the server. Add to that my Google Apps Calendar for personal use and my Exchange calendar, and my life is back under control within 15 minutes of wiping my phone.

Cool Tools

Cool Tools

Windows Mobile 6.5 added some nice features, and chef ookba made sure that critical system things were accessible. Like putting Internet Connection Sharing right on the main app list (it works — one of the first things I checked). He has also added several tools to allow easy management of the look of the ROM as well as several useful 3rd party apps that you would normally need to add separately to a default WinMo installation. Eight of them are shown on this capture of the Tools menu. Especially nice is the implementation of the “Titanium” homescreen architecture, which really advances the look and feel of the phone light years beyond the standard Windows Mobile homescreen and well beyond even the sliding panels in WinMo 6.5.

So, the bottom line after 1 day – the phone works perfectly after flashing, the ROM looks and works well, and I am very happy I took the plunge. More information as I dig deeper into the ROM and use it for daily work.

Flashing ookba’s 3volution ROM Part 2 – Flashing the ROM

September 6th, 2009 2 comments
This entry is part 2 of 5 in the series 3volution ROM

Windows Mobile 6.5 … er, excuse me, Windows Phone 6.5 … here I come.

In Part 1, I successfully installed the HardSPL security fix on my phone. The process and instructions worked like a charm. So I’m, willing to try part 2. Here it goes.

As before, I created a dedicated working directory on my PC and downloaded the file from http://forum.xda-developers.com/showthread.php?t=551642. The file is in a RAR archive (as opposed to a ZIP archive) so you will need to uncompress it before you can use it. I use 7Zip, but WinRAR and other programs work for this too.

Please see Part 1 of this series to see the parameters of my Dash 3G and the computer I am using to flash.

As before, here are the steps.

  1. Read, re-read, and re-re-read the flashing tutorial and the entire thread about this ROM (yes, all 266 posts at the time of this writing).
  2. Fully charge phone battery.
  3. Remove SIM and MicroSD from phone.
  4. Prepare computer by disabling firewall/virus software.
  5. Connect phone and allow ActiveSync to connect.
  6. Run ROM Update Utility (my ohone was HardSPL’d in Part 1)
  7. Follow prompts … Hit OK
  8. ActiveSync connection drops … bootloader screen starts.
  9. Wait. Progress bar on phone and screen. The progress bar on phone and screen moved steadily for about 90 seconds to 100%.
  10. Computer shows Rom Update Utility completion.
  11. Phone booted to 3volution/HTC start screen and hung there for about a minute. Then booted to WinMo 6.5 screen with “Preparing Device” message.
  12. After 2 minutes moved to SIM Failure screen.
  13. Phone rebooted again to 3volution/HTC screen then to WinMo6.5 screen.
  14. Clicked OK on Sim screen and saw 3volution homescreen! Success!

All in all — a pretty painless process. And at first glance, the 3volution ROM looks awesome! I will be reviewing after I get my mail accounts etc. set back up!

Flashing ookba’s 3volution ROM Part 1 – Installing HardSPL Fix

September 6th, 2009 No comments
This entry is part 1 of 5 in the series 3volution ROM

OK … I could be spending Labor Day shopping at T-Mobile to replace my $350 brick if this goes horribly wrong. But, I think ookba’s ROM has reached the point of reasonable stability. So I’m willing to give it a shot. This will be a play-by-play — you can live or die along with me!

Why Am I Flashing?

This is an incomplete answer. Partly, just because I can. There really isn’t that much wrong with the stock WM 6.1 ROM. Unlike my previous Wing, there is no major memory leak affecting performance. The T-Mobile ROM also doesn’t have too much bloatware which can’t be turned off — dumping the MyFaves display is pretty simple for example.

I guess part of me wants to move to WM 6.5 simply because I expected it to be released by now and I expected that new phones released during the summer would have it. Also since Microsoft has finally confirmed that 6.5 will be released this month, I expect that most 3rd-party programs will support it so there shouldn’t be that much risk in switching. So — we’ll see how it goes.

Background Parameters

Phone Info:

  • Windows Mobile 6.1 Standard
  • OS Rev: 5.2.21048 (Build 21048.1.6.3)
  • Radio Version 61.25t.25.19U_3.44.25.30
  • RIL Version 2.002
  • ROM Version: 1.17.531.5 (50264)
  • ROM Date: 06/03/09
  • Protocol Version: 61.25t.25.19U

Flashing Computer Info:

  • Model: Dell Studio 1735
  • OS: Windows Vista Home Premium (SP1)

If your system parameters differ by much, good luck.

Flashing Steps

  1. Read, re-read, and re-re-read ookba’s tutorial about flashing and unbricking your phone: http://forum.xda-developers.com/showthread.php?t=551959
  2. Read, re-read, and re-re-read the HardSPL flashing instructions at http://forum.xda-developers.com/showthread.php?t=550620
  3. Fully charge phone battery over night!
  4. Remove SIM and SD cards.
  5. Power device on.
  6. Bypass missing SIM error screen (hit DONE).
  7. Connect to PC and allow ActiveSync to connect (I actually don’t sync my phone via ActiveSync, so I always choose “Connect without setting up device” . Allow any additional programs to finish communicating (for example, one of my PC Corel photo programs “sees” the pictures on the device when it’s connected. Let this finish.)
  8. Download and unzip 1.17 Hard SPL patch. (I created a folder on the desktop to hold the files.)
  9. Disable firewall software on PC! It’s bad enough that the Vista User Access Control pops up as programs run … having more warnings or possible interruptions due to virus/firewall programs just makes this worse.
  10. Execute ‘auto.bat’ and follow directions on PC screen — hit any key as requested.
  11. Screen on phone pops up warning about untrusted software. Hit Yes and then click trackball on the next screen (there is an OK button that is partly obscured on our screen — you need to hit OK to continue).
  12. Phone goes blank for about 30 seconds.
  13. ROM Update Start Screen

    ROM Update Start Screen

  14. Rom Update Utility pops up on PC.
  15. Check box and hit next:
  16. Second update screen appears. Verify that you have the device connected, etc. and hit NEXT.
  17. You’ll see the progress screen warning that the update might take 10 minutes … it won’t (we’re not installing a complete ROM, just the SPL fix). After just a few seconds, the bar is at 100% and you are done.
  18. Install Complete

    Install Complete

After this step is complete you should verify that the SPL version is correct before you continue trying to flash a custom ROM. To do this, enter the bootloader (with phone off, hold Volume Up on side and power on) and see what’s listed on the tri-colored bootloader screen.

The text you want to see flashes by in less than a second, and is the first line in yellow at the top of the screen. You can enter the bootloader without continuing and wiping your phone clean, so don’t worry too much about this step. What you want to see is the string: “1.17.HARD” at the end of this line. If you don’t want to go through the process of actually setting your phone back to the factory default, then hit any key to exit the bootloader without continuing. I needed to start it twice before I read the line correctly and verified that my phone said “1.17.HARD.” Excellent it worked ….

In part 2, I flash the cooked ROM!