My Motorola Droid has been sent away for repair (requiring a part from China, a two week wait and a cost of over £50.) As I am therefore without a phone, I thought that I would try to install XDAndroid on my old HTC Touch Pro. I tried it once before about 3 years ago and it worked well enough to convince me that Android was a better phone operating system than Windows Mobile 6.1, but not well enough to be usable as an everyday phone.
This time I hoped that there would have been some updates to make Android more stable. The installation process seemed easier than I remembered. I thought I would document it, not just for others but for my own benefit in case I want to repeat the procedure for a third time.
You will need a blank microSD card. 4GB is plenty big enough. Then download the XDAndroid package from the repository at http://htcandroid.xland.cz/. I chose GBX0C_Full_Bundle_2012.04.24.zip because it was the newest.
Unzip the package to a temporary folder. The result is a folder named after the bundle,containing the files. Copy all the files (but not the folder itself) to the root directory of the microSD card.
The next step is to identify your model of phone. There is a long string of letters and numbers under the battery near the serial number stickers in tiny print. It will be 4 letters and a number. Mine said RAPH100: Raphael is the code name for the Touch Pro.
Having determined the code name, look in the files you unzipped for a folder named Startups. It contains several folders with names to match the phone. In the RAPH folder was another folder named RAPH100. That folder contains a file named startup.txt. Copy this to the root directory of the microSD card along with the other files. Now you can put the microSD card in the phone, replace the battery and switch it on.
Using the WinMo file manager look in the root of the storage card. There should be a file named Haret.exe. This is a Windows program. Run it. You should see a window that says "Booting Linux" which quickly changes to a console screen with tiny writing scrolling up the screen (I needed the extra strength reading glasses I use for fine electronic work.)
Watch the boot process carefully. It should stop at one point and ask you to perform the screen calibration. When I did this before, I recall that the the script displayed boxes on the screen that I had to tap with the stylus. This time there were no boxes displayed, so I had to guess the positions. The first time I guessed wrong: the result was an installation of Android that was insensitive to my touches.
I tried again after watching a YouTube video of the process which showed the screen calibration and saw that the tap points were: top left, top right, screen centre, bottom left and bottom right. After you have tapped the five points the boot process then carries on for several more minutes after which you should see an Android opening screen. Swipe the lock to the right and away you go!
In Windows Mobile you can create a shortcut to the program Haret.exe in your Start Menu which will make it easier to start Android next time. Do be certain that you create a shortcut not a copy because Haret has to be run from the root of the microSD card.
This version of XDAndroid seems a bit more stable than the one I installed three years ago. It's good enough for an emergency phone, which this is, but it runs slowly and functions like Bluetooth and GPS don't work reliably. Development of this Android port ceased a year or so ago so there won't be any updates. Interest in running Android on HTC Windows Mobile devices ebbed away as the users got themselves real Android phones. But it will do for now. It whiled away an afternoon and resulted in something I can use until my Droid returns from repair.
Showing posts with label Android. Show all posts
Showing posts with label Android. Show all posts
Sunday, July 07, 2013
Wednesday, January 30, 2013
First ham app for Android
![]() |
| My first Android app |
Because NGR and WAB only cover the UK, my app will not be very useful if you are outside of Great Britain. Indeed the app will probably blow up if you try it outside the UK as I haven't included any test that the user is within these sceptred isles.
I'd rather not say how long the app took me to complete, but it was far longer than expected given that I had already written code to convert from lat/long to grid locator in VOAProp. That code was in Pascal, and the trouble was caused by the fact that Basic4Android does not have equivalent functions to those in Pascal, or even Visual Basic, so I could not just do a copy and paste. In the end I found a conversion routine written in C++ and converted that to B4A's dialect of Basic. From there on it was easy, as there is a user-written library in B4A to handle conversions to/from National Grid references, upon which the WAB programme is based.
If I don't try something else I might have a go at displaying a Google Map centred on my location, as one of the examples that come with B4A does just that.
I don't plan on publishing any of the apps I create in Google Market (or Google Play as I think they now call it). I am doing this just for fun. Think of this as the programming equivalent of those radio projects knocked together on a breadboard or built Manhattan style, with no expectation that they will get put into a nice box.
If there is any interest I will make available the B4A project files as a zip file so that folks can play with them, hack them about or use them as a starting point for something better.
Wednesday, January 23, 2013
Basic Android Programming
Up until I got an Android smartphone, there has not been a single programmable device that I've owned and not tried to write my own programs for it. However, programming for Android devices seemed to be fiendishly difficult, requiring a good knowledge of Java (which I haven't got) so I didn't attempt it. The other week I saw an article in a computer magazine that went through describing how to create programs using a tool called Basic4Android. It seemed similar enough to other development tools I have used such as Visual Basic, Delphi and Lazarus. So I thought I would download the trial version and have a play.
I soon discovered that the trial version is pretty limiting. It's enough to get a feel for the environment and the development process by creating "hello world" apps and suchlike, but in order to do anything interesting you need to use libraries and these are only accessible using the full paid-for version.
There are two full versions of Basic4Android you can buy: the Standard version which costs $49 and includes support and free upgrades for two months, and the Enterprise version which costs $99 and includes support and free upgrades for two years. As I'm not an Enterprise, only a dabbler (and a cheapskate one at that) I bought the Standard version. With hindsight that was not such a good idea, as I discovered after purchasing that only current paid-up users get access to the download links for additional libraries, even user-written ones, and access to the support forum. So after two months I'm on my own. A false economy, I think.
Basic4Android is a very powerful development tool and I don't think there is much you couldn't do with it if you're clever enough. The language is object oriented like any modern Basic, and objects exist to let you access the internet, draw charts, access SQL databases and much more. You can access the Android device's GPS via a fully featured GPS library. There is even code to work with Google Maps. I have no intention of developing an Android version of APRSISCE (as if I could!) but Basic4Android looks powerful enough to make that possible.
So far I haven't learned much about Basic4Android programming that's worth sharing with people, but here are a few things I wish I had known prior to buying.
There is no need to pay the full prices I mentioned earlier. Once Google finds out you are interested in Basic4Android, ads to buy Basic4Android with 30% off will follow you around the web. To get the deal, click on one of them.
There are two options you can use to pay for Basic4Android, PayPal and Plimus. If you are in Europe then be sure to use the PayPal purchase buttons. If you use Plimus then you'll get stung for VAT which will bump up the price 20%.
Better still you can get Basic4Android Enterprise version with two years' updates and support at half price by using the coupon code dnxyif. Unfortunately this is only valid if you use the Plimus payment option so there is no avoiding VAT if you are in Europe. But even with VAT it's still the best deal I think. I hope that helps someone.
![]() |
| The Basic4Android development environment, |
There are two full versions of Basic4Android you can buy: the Standard version which costs $49 and includes support and free upgrades for two months, and the Enterprise version which costs $99 and includes support and free upgrades for two years. As I'm not an Enterprise, only a dabbler (and a cheapskate one at that) I bought the Standard version. With hindsight that was not such a good idea, as I discovered after purchasing that only current paid-up users get access to the download links for additional libraries, even user-written ones, and access to the support forum. So after two months I'm on my own. A false economy, I think.
![]() |
| Sophisticated GPS apps can be developed |
So far I haven't learned much about Basic4Android programming that's worth sharing with people, but here are a few things I wish I had known prior to buying.
There is no need to pay the full prices I mentioned earlier. Once Google finds out you are interested in Basic4Android, ads to buy Basic4Android with 30% off will follow you around the web. To get the deal, click on one of them.
There are two options you can use to pay for Basic4Android, PayPal and Plimus. If you are in Europe then be sure to use the PayPal purchase buttons. If you use Plimus then you'll get stung for VAT which will bump up the price 20%.
Better still you can get Basic4Android Enterprise version with two years' updates and support at half price by using the coupon code dnxyif. Unfortunately this is only valid if you use the Plimus payment option so there is no avoiding VAT if you are in Europe. But even with VAT it's still the best deal I think. I hope that helps someone.
Saturday, March 17, 2012
Taking a tablet
A month or so ago I solicited the advice of my readers on the selection of a device for reading e-publications. I learned that the Kindle - my original choice - would not meet all of my needs, but I received some strong endorsements for the Apple iPad.
As someone who pays full price for SIM-free mobile phones just so as not to be tied to one provider, the idea of a device that only let you use what Apple approves and insists on being tethered to iTunes did not, unfortunately, appeal to me. My online activities are very Google-centric, I'm a fan of open source and I already have an Android smartphone so inevitably my thoughts turned to Android tablets. Someone mentioned that Maplin had some cheap tablet computers in their sale - the Archos Arnova 10 G2. Maplin is rarely the cheapest source of anything even in a sale so I visited a price comparison site and found that Carphone Warehouse had the Arnova for £10 cheaper and with free shipping. I checked some reviews and the majority were very positive, even though many qualified their comments with "for the price." The tablet was in my hands 24 hours and £139 later.
As a tablet virgin my impressions probably aren't worth much but even I can tell that the Archos is not Apple build quality. The plastic case is more reminiscent of something that came out of a Christmas cracker. £11 on eBay got me a leatherette case/stand for the tablet so I don't see the case anyway. But as many reviewers said, it's a lot of tablet for the money. I haven't got around to trying any e-book readers yet but I've used it for email and web surfing and I love it already. Battery life is great, the tablet is silent as there is no fan inside and no Intel Pentium giving you a hot lap so it's a much better laptop device than a laptop.
One problem was that there was no Gmail app as I use on my smartphone. The Arnova doesn't come with the standard Android Market so the choice of apps is rather limited. I found some instructions for installing Android Market on the Arnova but as usual whenever I attempt something technical with computers I got error messages that aren't mentioned in the description. After trying a few things at random and on the point of giving up I noticed that Gmail had been installed and I had the full Market, except that it has been renamed Google Play. That probably confused me into thinking it was something to do with games, which I have no interest in.
The one thing I haven't managed to do yet is find an app for my blogging activities. On the PC I use Blogger Dashboard in a browser (Firefox, of course) but on Android Dashboard is no good for keeping up with the blogs I follow because the list of posts is in an iframe and the Android browser doesn't support scrolling in an iframe. Nor does the Dolphin browser, which I was led to believe would be the solution. I'll probably have to use gReader, as I do on the smartphone, but I'd hoped the tablet would let me use something a bit more sophisticated.
We watched a TV show on the Arnova using the BBC iPlayer and I was impressed by the quality. Until then I could never understand why anyone would want to watch TV on a computer but in fact the angular size of the Arnova screen in my lap is larger than that of the TV when I'm sitting in my armchair, so it's actually better. As you may gather, I'm pleased with my new gadget!
As someone who pays full price for SIM-free mobile phones just so as not to be tied to one provider, the idea of a device that only let you use what Apple approves and insists on being tethered to iTunes did not, unfortunately, appeal to me. My online activities are very Google-centric, I'm a fan of open source and I already have an Android smartphone so inevitably my thoughts turned to Android tablets. Someone mentioned that Maplin had some cheap tablet computers in their sale - the Archos Arnova 10 G2. Maplin is rarely the cheapest source of anything even in a sale so I visited a price comparison site and found that Carphone Warehouse had the Arnova for £10 cheaper and with free shipping. I checked some reviews and the majority were very positive, even though many qualified their comments with "for the price." The tablet was in my hands 24 hours and £139 later.
![]() |
| Archos Arnova 10 G2 |
One problem was that there was no Gmail app as I use on my smartphone. The Arnova doesn't come with the standard Android Market so the choice of apps is rather limited. I found some instructions for installing Android Market on the Arnova but as usual whenever I attempt something technical with computers I got error messages that aren't mentioned in the description. After trying a few things at random and on the point of giving up I noticed that Gmail had been installed and I had the full Market, except that it has been renamed Google Play. That probably confused me into thinking it was something to do with games, which I have no interest in.
The one thing I haven't managed to do yet is find an app for my blogging activities. On the PC I use Blogger Dashboard in a browser (Firefox, of course) but on Android Dashboard is no good for keeping up with the blogs I follow because the list of posts is in an iframe and the Android browser doesn't support scrolling in an iframe. Nor does the Dolphin browser, which I was led to believe would be the solution. I'll probably have to use gReader, as I do on the smartphone, but I'd hoped the tablet would let me use something a bit more sophisticated.
We watched a TV show on the Arnova using the BBC iPlayer and I was impressed by the quality. Until then I could never understand why anyone would want to watch TV on a computer but in fact the angular size of the Arnova screen in my lap is larger than that of the TV when I'm sitting in my armchair, so it's actually better. As you may gather, I'm pleased with my new gadget!
Saturday, August 20, 2011
Motorola Millstone
This weekend I had planned to write about my Android smartphone, a Motorola Milestone 2, which I bought in early July soon after I came out of hospital. It was a fantastic phone with a big, clear screen and a really usable slide-out keyboard. It became my main method of electronic communication. The Android user interface is great - far, far superior to Windows Mobile. It is well integrated with Gmail as you would expect and it has an excellent web browser that can display almost any website, unlike the IE browser in Windows Mobile which is just a piece of s***. I was also intending to write about an Android APRS application called U2APRS. Unfortunately, last night my Milestone turned into a brick.
The one thing I hadn't got round to doing was install a good app to read the various blogs that I follow. Blogger Dashboard is one of the few sites that doesn't work well in the Android browser. I decided to install Feedly, found that I liked it, and spent some time going through all the blogs marking all the posts as read. Having done that I was trying to figure out how to get back to the list of blogs now that there were no new posts when the screen froze and refused to respond to touch input.
Thinking that this was just a software crash, I pulled the battery. But when the phone started up again the screen still refused to respond to finger movements. And now I couldn't get past the lock. This situation persisted after several attempts.
Time to go online. A Google search revealed that problems with the Motorola Milestone 2 touch screen were not uncommon and that the only diagnostic to try was to perform a factory reset to make sure that the trouble was not due to a software glitch. This would, of course, remove all my apps and settings. But there was no alternative. Except that the instructions for performing a hard reset - press and hold the Camera button while powering up the phone - didn't work. Every time, the phone booted into its normal screen, which was still locked.
After wasting quite a lot of time making several attempts at this I found another forum post that suggested holding the X key on the keyboard whilst powering on the phone. This got me a step nearer to where I was trying to be - a screen with a warning triangle and an Android icon on it - but the instructions to bring up the menu - press and hold the Volume Up button and then the Camera button - did nothing. Again, a lot of time was wasted trying this several times, including different permutations of pressing and holding, and trying both of the Volume buttons since I couldn't be sure which was Up and which was Down, to no avail. Deep frustration was setting in.
Olga found a forum post which suggested that pressing the keyboard Search button from the Android warning screen would bring up the reset menu. That didn't work either. Then she found another one that said to use the the @ key. At last, the menu! I was finally able to format the system and wipe all my apps and data. When the phone rebooted it entered the initial configuration sequence, asking what language I wanted it to use. Which I was unable to select because the touch screen still didn't work.
So my Milestone is currently as much use as a lump of rock. I'm missing it already. It will probably take several days to send it for repair and have it returned, which I can't even start to do until Monday. But I'd rather do without a phone than go back to Windows Mobile, which may be a very good platform for running apps but is absolutely loathsome as a telephone and is totally useless for Gmail.
Deep frustration. Not to mention irritation over the valuable time I'll have to spend reinstalling and reconfiguring everything once it's back. And to add to my annoyance I've lost U2APRS because the developer JA7UDE's web site has been offline for the last couple of weeks for reasons unknown and there is no longer any way to obtain it.
I'm not a happy bunny.
The one thing I hadn't got round to doing was install a good app to read the various blogs that I follow. Blogger Dashboard is one of the few sites that doesn't work well in the Android browser. I decided to install Feedly, found that I liked it, and spent some time going through all the blogs marking all the posts as read. Having done that I was trying to figure out how to get back to the list of blogs now that there were no new posts when the screen froze and refused to respond to touch input.
Thinking that this was just a software crash, I pulled the battery. But when the phone started up again the screen still refused to respond to finger movements. And now I couldn't get past the lock. This situation persisted after several attempts.
Time to go online. A Google search revealed that problems with the Motorola Milestone 2 touch screen were not uncommon and that the only diagnostic to try was to perform a factory reset to make sure that the trouble was not due to a software glitch. This would, of course, remove all my apps and settings. But there was no alternative. Except that the instructions for performing a hard reset - press and hold the Camera button while powering up the phone - didn't work. Every time, the phone booted into its normal screen, which was still locked.
After wasting quite a lot of time making several attempts at this I found another forum post that suggested holding the X key on the keyboard whilst powering on the phone. This got me a step nearer to where I was trying to be - a screen with a warning triangle and an Android icon on it - but the instructions to bring up the menu - press and hold the Volume Up button and then the Camera button - did nothing. Again, a lot of time was wasted trying this several times, including different permutations of pressing and holding, and trying both of the Volume buttons since I couldn't be sure which was Up and which was Down, to no avail. Deep frustration was setting in.
Olga found a forum post which suggested that pressing the keyboard Search button from the Android warning screen would bring up the reset menu. That didn't work either. Then she found another one that said to use the the @ key. At last, the menu! I was finally able to format the system and wipe all my apps and data. When the phone rebooted it entered the initial configuration sequence, asking what language I wanted it to use. Which I was unable to select because the touch screen still didn't work.
So my Milestone is currently as much use as a lump of rock. I'm missing it already. It will probably take several days to send it for repair and have it returned, which I can't even start to do until Monday. But I'd rather do without a phone than go back to Windows Mobile, which may be a very good platform for running apps but is absolutely loathsome as a telephone and is totally useless for Gmail.
Deep frustration. Not to mention irritation over the valuable time I'll have to spend reinstalling and reconfiguring everything once it's back. And to add to my annoyance I've lost U2APRS because the developer JA7UDE's web site has been offline for the last couple of weeks for reasons unknown and there is no longer any way to obtain it.
I'm not a happy bunny.
Tuesday, September 14, 2010
Experiences with Android
The Micro SD card I ordered arrived on Monday so I was eventually able to try installing the Google Android OS on my HTC Touch Pro. The delay turned out to be a benefit as I was able to take the advice of Eric SA5BKE who commented to my earlier post that he had found a better set of installation instructions to the ones I mentioned.
Still, as usual when I try to do anything with computers, if something can go wrong it will. First, the phone could not see the new SD Card. I had to format it with a utility from the SD Card Association. Then I messed up the screen calibration where you have to click, when prompted, on the corners of the screen, and wasted some time trying to recover from my mess-up. But eventually I was rewarded with the sight of the Android home screen on my HTC Touch Pro.
The effort was worthwhile. I really like the Android OS. It is so much better a smartphone operating system than Windows Mobile 6.1. You still feel that you are using a phone, not a Windows PC that has an annoyingly small screen. Making phone calls and sending text messages is really simple, as it should be. And once you have found out how the new OS is supposed to be used (since the download doesn't come with a user guide) it's easy to use.
I am a huge fan of Google - I have five GMail accounts and probably make hundreds of Google searches a week - and what I really like about Android is the way Google features are integrated into the OS. Until now I could never understand why people liked smartphones and would actually want to use them to answer email because my experience was based on trying to access GMail using one of the two awful web browsers on my Windows phone. But now I get a notification whenever a new email comes into any of my inboxes and I can either clear it or click on the email to read it in full or reply on a display designed to make full use of the small screen. I guess that's how other smartphones work if you have a corporate mail server running Microsoft Exchange, but I've never had one.
I was also very impressed with the Google search widget on one of the virtual desktops of the home screen. It had a microphone icon so, out of curiosity, I clicked it and was invited to speak. A moment later it typed what I had said into the search box and was performing a search on it. Fortunately I hadn't said something rude! I then had some fun composing emails and text messages without using the keyboard. Unfortunately the speech engine doesn't recognize words like "comma", "full stop" or "newline" as punctuation and formatting, nor does it recognize commands like "send." But I was very impressed with the accuracy with which it understood what I said - the last time I tried voice input was at least a decade ago on a PC and I found it ultimately frustrating.
One of the applications I was keen to try out was Navigation, Google's free satnav program based on Google Maps which is not available for Windows Mobile. I haven't had a chance to test it in the car, but it seems like the full works, with a text to speech engine that barks directions at you. The optional but probably rather unnecessary satellite view looks rather cool, though I was rather less impressed by the route it suggested from home to Keswick, south-east of here, which involved turning right at the end of the cul-de-sac and going north, then west for a mile to reach the A66 before going east, instead of turning left and heading east which would save best part of two miles. My old satnav does that too, but that's because the estate hadn't been completed when the maps were made and it believes the top of the estate is still a building site.
The Android Market contains thousands of apps that you can download, either free or for a modest charge. However, sorting the wheat from the chaff seems like one of those things life's too short for. It reminds me a bit of the early Windows "shareware" market when anyone who had taught themselves Visual Basic thought they would be the next Bill Gates by releasing some flaky software that did very little and usually crashed as soon as it experienced some condition the programmer hadn't thought of.
There seem to be very few ham radio applications, though, and almost no really good ones. I saw quite a few apps to do with Morse, giving the lie to the idea that code is dead, but nothing that looked worth trying. The only professional quality radio application I could find is the new EchoLink client for Android.
My feelings about this have mellowed a bit since I wrote about it just over a week ago. Last Friday just before dinner I received a call through my EchoLink node from Practical Wireless VHF columnist and fellow blogger Tim Kirby, G4VXE, who was on his way home from work by train and called me using the EchoLink client for his iPhone. Though we've exchanged blog comments a few times it was very pleasant to speak with Tim for the first time. This was a contact we would be unlikely to make over radio and certainly not in that particular situation. Only EchoLink made it possible.
In the interests of research I had a conversation with myself using the EchoTest server and found the audio quality to be just as good as when I use my Kenwood TH-F7E to make contacts via my RF node. However the cellphone client has one disappointing limitation. You can't make a direct connection using the cellular network. You have to use a communication option called "Relay" which only allows you to call other non-cellphone EchoLink users. It doesn't allow other EchoLink users to call you. It's a bit like having a radio and not being able to call CQ.
I was somewhat unimpressed by the Android APRS app, APRSdroid, not just in comparison with Lynn, KJ4ERJ's APRSISCE for Windows Mobile, but even with the iBCNU app for the iPhone. The user interface is basically a console window: you can see position packets going out, and if you wish you can see raw packets of other users within a selected radius of your location. There is no support for messaging at all in the present version.
Tracking doesn't seem to work very well either, unless you are also running another application such as Navigation that keeps the GPS on all the time. I think the problem is that the app tries to save power by turning on the GPS, waiting for a fix and then turning it off again until the next time interval. It didn't work too badly when the phone was sitting in its charger cradle on my desktop, but getting a GPS fix when you are moving can take a very long time. There is a need for a simple APRS tracking and messaging application for Android but this has a way to go before it gets there.
The HTC port of Android OS is not an official release and has quite a few bugs and things that are still To Be Done. I've had the phone lock up and fail to respond to anything and have had to pull the battery a few times. There is no support for the built-in camera and the battery charge indication is completely fictitious. It's also best not to use wi-fi as it warms up the phone and consumes a lot more power than under Windows Mobile.
Unlike most people I bought my HTC Touch Pro SIM-free and unlocked because I don't like to be tied to a network. As a consequence I'm not going to be offered an upgrade for no extra cost when my contract runs out. I need to keep the phone for a while but I'd be more than happy to dump Windows Mobile because as a phone it's too much hassle, even though it does allow me to run some pretty powerful applications. I hope that the issues with the HTC Android port will be resolved in order that it becomes stable enough and functional enough for me to use it on my phone all the time.
Still, as usual when I try to do anything with computers, if something can go wrong it will. First, the phone could not see the new SD Card. I had to format it with a utility from the SD Card Association. Then I messed up the screen calibration where you have to click, when prompted, on the corners of the screen, and wasted some time trying to recover from my mess-up. But eventually I was rewarded with the sight of the Android home screen on my HTC Touch Pro.
The effort was worthwhile. I really like the Android OS. It is so much better a smartphone operating system than Windows Mobile 6.1. You still feel that you are using a phone, not a Windows PC that has an annoyingly small screen. Making phone calls and sending text messages is really simple, as it should be. And once you have found out how the new OS is supposed to be used (since the download doesn't come with a user guide) it's easy to use.
I am a huge fan of Google - I have five GMail accounts and probably make hundreds of Google searches a week - and what I really like about Android is the way Google features are integrated into the OS. Until now I could never understand why people liked smartphones and would actually want to use them to answer email because my experience was based on trying to access GMail using one of the two awful web browsers on my Windows phone. But now I get a notification whenever a new email comes into any of my inboxes and I can either clear it or click on the email to read it in full or reply on a display designed to make full use of the small screen. I guess that's how other smartphones work if you have a corporate mail server running Microsoft Exchange, but I've never had one.
I was also very impressed with the Google search widget on one of the virtual desktops of the home screen. It had a microphone icon so, out of curiosity, I clicked it and was invited to speak. A moment later it typed what I had said into the search box and was performing a search on it. Fortunately I hadn't said something rude! I then had some fun composing emails and text messages without using the keyboard. Unfortunately the speech engine doesn't recognize words like "comma", "full stop" or "newline" as punctuation and formatting, nor does it recognize commands like "send." But I was very impressed with the accuracy with which it understood what I said - the last time I tried voice input was at least a decade ago on a PC and I found it ultimately frustrating.
One of the applications I was keen to try out was Navigation, Google's free satnav program based on Google Maps which is not available for Windows Mobile. I haven't had a chance to test it in the car, but it seems like the full works, with a text to speech engine that barks directions at you. The optional but probably rather unnecessary satellite view looks rather cool, though I was rather less impressed by the route it suggested from home to Keswick, south-east of here, which involved turning right at the end of the cul-de-sac and going north, then west for a mile to reach the A66 before going east, instead of turning left and heading east which would save best part of two miles. My old satnav does that too, but that's because the estate hadn't been completed when the maps were made and it believes the top of the estate is still a building site.
The Android Market contains thousands of apps that you can download, either free or for a modest charge. However, sorting the wheat from the chaff seems like one of those things life's too short for. It reminds me a bit of the early Windows "shareware" market when anyone who had taught themselves Visual Basic thought they would be the next Bill Gates by releasing some flaky software that did very little and usually crashed as soon as it experienced some condition the programmer hadn't thought of.
There seem to be very few ham radio applications, though, and almost no really good ones. I saw quite a few apps to do with Morse, giving the lie to the idea that code is dead, but nothing that looked worth trying. The only professional quality radio application I could find is the new EchoLink client for Android.
My feelings about this have mellowed a bit since I wrote about it just over a week ago. Last Friday just before dinner I received a call through my EchoLink node from Practical Wireless VHF columnist and fellow blogger Tim Kirby, G4VXE, who was on his way home from work by train and called me using the EchoLink client for his iPhone. Though we've exchanged blog comments a few times it was very pleasant to speak with Tim for the first time. This was a contact we would be unlikely to make over radio and certainly not in that particular situation. Only EchoLink made it possible.
In the interests of research I had a conversation with myself using the EchoTest server and found the audio quality to be just as good as when I use my Kenwood TH-F7E to make contacts via my RF node. However the cellphone client has one disappointing limitation. You can't make a direct connection using the cellular network. You have to use a communication option called "Relay" which only allows you to call other non-cellphone EchoLink users. It doesn't allow other EchoLink users to call you. It's a bit like having a radio and not being able to call CQ.
I was somewhat unimpressed by the Android APRS app, APRSdroid, not just in comparison with Lynn, KJ4ERJ's APRSISCE for Windows Mobile, but even with the iBCNU app for the iPhone. The user interface is basically a console window: you can see position packets going out, and if you wish you can see raw packets of other users within a selected radius of your location. There is no support for messaging at all in the present version.
Tracking doesn't seem to work very well either, unless you are also running another application such as Navigation that keeps the GPS on all the time. I think the problem is that the app tries to save power by turning on the GPS, waiting for a fix and then turning it off again until the next time interval. It didn't work too badly when the phone was sitting in its charger cradle on my desktop, but getting a GPS fix when you are moving can take a very long time. There is a need for a simple APRS tracking and messaging application for Android but this has a way to go before it gets there.
The HTC port of Android OS is not an official release and has quite a few bugs and things that are still To Be Done. I've had the phone lock up and fail to respond to anything and have had to pull the battery a few times. There is no support for the built-in camera and the battery charge indication is completely fictitious. It's also best not to use wi-fi as it warms up the phone and consumes a lot more power than under Windows Mobile.
Unlike most people I bought my HTC Touch Pro SIM-free and unlocked because I don't like to be tied to a network. As a consequence I'm not going to be offered an upgrade for no extra cost when my contract runs out. I need to keep the phone for a while but I'd be more than happy to dump Windows Mobile because as a phone it's too much hassle, even though it does allow me to run some pretty powerful applications. I hope that the issues with the HTC Android port will be resolved in order that it becomes stable enough and functional enough for me to use it on my phone all the time.
Friday, September 10, 2010
Becoming an Android
A few days ago I came across a forum thread discussing ham radio applications for smartphones in which someone claimed that they were using an HTC Touch Pro (the phone I have) dual booting into Windows Mobile and Google Android. I was interested, but imagined that achieving it would require the ability to follow exactly a lengthy sequence of obscure commands with a high probability of turning the phone into a brick. However I was unable to resist looking into it further and discovered that it should be easier than that. It should be simply a matter of extracting an image of the HTC Android port on to an SD card, copying a configuration file that matches your model of phone into the root folder and then running a program (under Windows Mobile) that reboots the phone into Android. Unfortunately I don't have an SD card of the type used by the Touch Pro so I haven't been able to try it yet.
I originally bought a smartphone running Windows Mobile specifically because it would run Lynn KJ4ERJ's APRSISCE, which is undoubtedly the best APRS client on any smartphone by several hundred miles. However, for me that is really about the only good reason for using that platform. I don't need the ability to sync with Outlook or use Pocket Office as I don't use any Microsoft applications on my PCs, and I find Windows Mobile to be too much like Windows itself - complicated to use - and not enough like a phone - easy to make phone calls and text messages. Plus, the fact that running APRSISCE all the time drains the battery in a couple of hours leaving you without a working phone has been a big disincentive to using it in the way I originally envisaged.
Whilst Windows Mobile 6.x is an undoubtedly powerful platform, as you can tell from the range of full-featured applications (not just "apps") available for it, it is also a dead end. I was surprised to find that Windows Mobile currently has just 5% of the market. Microsoft is hoping to reclaim some of its market share with the upcoming Windows Mobile 7. Personally I think it's too late and Microsoft has missed the boat on this one. I think Microsoft has an over-inflated opinion of the Windows "brand". People use Windows on PCs because they don't have much of an alternative, not because they think it's great. Smartphone users have lots of choices. People love Google because they are always giving us stuff for free, while Microsoft always makes you pay (and then keeps checking your receipt afterwards). So I think Windows Mobile 7 is doomed even if Microsoft hadn't decided to make it incompatible with earlier versions so that it won't run any legacy applications - including APRSISCE.
I really wished in the end I had bought an Android phone. Now this dual boot trick will allow me to try the Google OS out and see whether it is really is as good as the hype. More when I receive the SD card I ordered and am able to try it.
(Update: Just checked the status of my order placed on Wednesday with option for first class next day delivery and it is still shown as Pending. Grr! Clearly it wasn't a good idea to order from MyMemory.)
I originally bought a smartphone running Windows Mobile specifically because it would run Lynn KJ4ERJ's APRSISCE, which is undoubtedly the best APRS client on any smartphone by several hundred miles. However, for me that is really about the only good reason for using that platform. I don't need the ability to sync with Outlook or use Pocket Office as I don't use any Microsoft applications on my PCs, and I find Windows Mobile to be too much like Windows itself - complicated to use - and not enough like a phone - easy to make phone calls and text messages. Plus, the fact that running APRSISCE all the time drains the battery in a couple of hours leaving you without a working phone has been a big disincentive to using it in the way I originally envisaged.
Whilst Windows Mobile 6.x is an undoubtedly powerful platform, as you can tell from the range of full-featured applications (not just "apps") available for it, it is also a dead end. I was surprised to find that Windows Mobile currently has just 5% of the market. Microsoft is hoping to reclaim some of its market share with the upcoming Windows Mobile 7. Personally I think it's too late and Microsoft has missed the boat on this one. I think Microsoft has an over-inflated opinion of the Windows "brand". People use Windows on PCs because they don't have much of an alternative, not because they think it's great. Smartphone users have lots of choices. People love Google because they are always giving us stuff for free, while Microsoft always makes you pay (and then keeps checking your receipt afterwards). So I think Windows Mobile 7 is doomed even if Microsoft hadn't decided to make it incompatible with earlier versions so that it won't run any legacy applications - including APRSISCE.
I really wished in the end I had bought an Android phone. Now this dual boot trick will allow me to try the Google OS out and see whether it is really is as good as the hype. More when I receive the SD card I ordered and am able to try it.
(Update: Just checked the status of my order placed on Wednesday with option for first class next day delivery and it is still shown as Pending. Grr! Clearly it wasn't a good idea to order from MyMemory.)
Subscribe to:
Posts (Atom)








