That Swype beta, on my Nexus One at least, expired a couple of days ago, with a message to update to the latest [beta] version.  I’d been meaning to check for an update anyway, so I sought out the latest version.

It turns out that an Android beta registration process is now in operation, which is good, since it should include notifications of Swype updates.

The page to head for is https://beta.swype.com/

Some details from the Swype registration page:

Swype is pleased to offer an Android Beta!

Here are the details:

• Initially we will have a limited number of participants – we’ll expand it soon
• In English and Spanish – more languages to come
• Limited Features – some key features of Swype require OEM integration
• HVGA and WVGA Resolutions – don’t worry we’ll detect this automatically
• Limited End User Support – mostly via our forum
• If your phone came pre-installed with Swype DO NOT download this beta (it won’t work)

How will this work?

You register with an email address you can access via your mobile and we send you a link to download Swype. That’s it!

On my N1 the download (using WiFi) and install process went very smoothly.  There was a friendly message asking me to uninstall the earlier [unofficial] beta app first: I had to do this manually (using Astro) which is fair enough, since it was a manual install in the first place.

I’ve been using the updated beta for a couple of days now and it is an improvement over the earlier one.  It seems more responsive.  The previously learned words are still there, which is nice.  Significantly, I no longer get Swype warning me of a screen size problem.

If you haven’t tried Swype yet, and you have a compatible phone, I really do recommend it.  Text entry is a pleasure.

If your phone isn’t supported in the current beta version, take a look at SlideIT, a similar product.  Personally, I prefer Swype because it has a better keyboard format and offers greater control over punctuation and capitalization; Swype is much better at entering oddly spelled user IDs and passwords with mixed letters and digits, for example.

I look forward to Swype coming out of beta and being available for purchase in the Market.

On my Android phone (formerly a Hero and now a Nexus One) I have likewise settled on Twidroid as the ultimate Twitter app.  That may be about to change…

HootSuite for Android is here.  They’re not calling it Hootdroid, though the HootSuite guys do now have a Twitter account by that name, @Hootdroid, with a clever twist on the Android robot.

The Android app has been on the Market since 1pm UK, so as I write this I’ve had all of 30 minutes to explore.  On this basis, I am impressed.  The UI is rich and the familiar HS tabs and stats are all there.  The implementation on Android is very slick, learning some tricks from the iPhone app, no doubt.  For a new Android Market app, it is excellent quality.

If you’re a HootSuite user, or even if you’re not, give this new Android app a whirl… you may like it.  A lot of thought has gone into the app.  This is bound to pay off for the HootSuite guys, since it could attract a lot of new users to their Twitter platform.

I’ll be using HootSuite for Android instead of Twidroid for a few days at least.  Who knows, I may stick with it.

Today, my thanks go to @thheinen for letting me know of a similar app, SlideIT, which is available on the Android Market for any Android phone.  This is similar to Swype but goes further in providing a Palm-like “graffiti” mode and, importantly for the European market,  separately installable language packs for many languages.

I’ve now installed SlideIt on my dear old Hero (which had languished somewhat, of late, serving as an eReader by my bedside) and I’m impressed.  Given the Hero’s slower processor, SlideIT’s word prediction and recognition is excellent.  Swype wins on good looks and in some aspects of punctuation control.  That said, I really need to use these two keyboard apps for a while before arriving at any firm conclusions.

Since my Nexus One is my main phone, I’m going to install SlideIT on the N1, alongside Swype, so I can try them both.  It’ll be interesting.

Either way, these two apps make on-screen text entry a real pleasure.  I reckon I can get words into the phone about three times quicker than using a tap-entry keyboard.

If you haven’t tried SlideIT, I recommend giving it a go.  It’s FREE, by the way   (as are the language packs)

It’s amazing.  Watch the video.

So much nicer than tapping the screen.  I’ve used other keyboards from the Android Market, but Swype has the edge over them for ease of use and quality, even in its beta release.

Sadly for anyone without a Droid or Nexus One, the Swype beta is not for you at present.  Apparently, it’s a screen size issue, although even on my N1 I get the occasional warning from Swype saying that the screen is not of the required dimensions.  On that basis, I guess you could try Swype on other phones… ?

The Android Swype beta is not available on the Market… you need to download it and transfer it to your phone.

Here’s how to do it:

http://www.androidcentral.com/download-beta-version-swype-android

It’s very easy to enter text using Swype; you just need to know a few things about how to use it.  Be sure to watch the tutorial videos at http://www.swypeinc.com/tips-tricks.html They are all very short and to the point.  Recommended viewing.

Enjoy the non-tapping’ness.  :)

In this context, tethering a smartphone to a computer allows that computer to get onto the Internet using the phone’s data service.  It’s a bit like using a mobile phone as a modem, something I remember doing before broadband took off.  The connection between computer and phone may be USB or Bluetooth, depending on the solution you opt for.

Why tether your phone?

For me, the main reason is to have a fall-back option in the event of my usual broadband access going off-line.

In other situations tethering can get a laptop computer online where there is no WiFi but there is a 3G (2G, even) signal.

Options for Android

Tethering is not just available for Android but that’s the platform I am interested in.  In fact, the solution I have opted for is also available for iPhone, BlackBerry, Windows Mobile and Palm.  It also works for Windows and Mac.

Doing a web search I came up with three ways to achieve a tethered phone:

1. Root the phone and run a few command line commands on the PC.  I’ve never been keen on the idea of rooting my phone, so this option is out.
2. Proxoid.  As you’ll see if you follow the link to the Proxoid web site, this does not need a rooted Android phone.  Proxoid makes the phone act as a proxy server for the client computer.  There is, however, quite a lot of messing around with Windows network setting, and this put me off this solution.  It is FREE, though, and this is a good reason to give it a try if your budget is limited.
3. PdaNet. This software is not free; the Android version is currently US$ 23.95 on the Market.  As mentioned, there are other versions for other mobile platforms.  The nice thing about PdaNet is that no manual changes are required on the client computer.  This is achieved by installing a piece of Windows (or Mac) software to provide a device driver to make the USB connected phone appear as a dial-up modem.

Getting the software

The Android software for PdaNet is available from the Market, in the usual way.  There is just one version and it is free… after one month it restricts access to non-HTTPS sites only.  When you buy a license this unlocks the full functionality of the software… there is no new version to install.

The Windows or Mac software is available from the PdaNet (June Fabrics Technology) web site.

Installing PdaNet

My first Android phone was an HTC Hero (I still have it) and I had installed HTC Sync on my laptop because, well, it seemed a good idea at the time.  In fact, I never really found Ineeded HTC Sync, since I use Google Mail, Google Contacts and Google Calendar, but I’d left the software there just in case it is needed when HTC finally roll out Eclair for the Hero (expected in March).

“What has this to do with PdaNet?”, you ask.  Well, during the install of the Windows software (I’m running WinXP SP3) a message popped up saying that HTC Sync had been detected and that the software would try to coexist, but that there may be connection issues, in which case I should uninstall HTC Sync.

In retrospect I should have known better, but I left my phone (a Nexus One) connected by USB to my laptop (from an earlier unrelated activity) when I ran the install of the PdaNet Windows software.  The upshot of this was that the Windows “New Hardware” wizard failed to install the new USB device driver.

Deciding to play safe, and because I’d been meaning to get rid of HTC Sync anyway, I uninstalled it now and then reinstalled PdaNet, this time ensuring that the phone was not connected to the laptop.  Strangely, this time around there was a message dialog warning against having the phone connected… something I did not see the first time… perhaps a bug in the HTC Sync detection routine?

During the installation process, the software asks you to enable USB Debugging on the Android phone.  This is required for PdaNet to function and is easily done.  Once enabled, you’ll see a new item in the notification bar of the phone, from which you can disable USB debugging if need be.

Anyway, it all went smoothly the second time around, ending with brief instructions on how to start using the tethering software.

PdaNet in action

The software is simplicity itself to use.  First start the Android software and tap the button to “Enable USB Tether”.  Then, on the computer, right-click the PdaNet icon in the Windows System Tray and select “Connect”.  The connection is established within one or two seconds.

Windows sees the connection as a dial-up service:

After disabling the laptop’s usual network connections I tried the tethered link.

With my phone connected to WiFi, I found web browsing on the laptop as quick as it normally is over WiFi.  I guess this is to be expected.

After turning the phone’s WiFi off, so it switched to 3G, the laptop was still very usable.  I wouldn’t use it to watch videos, though, but then, who would?

If you have the PdaNet software visible on the phone, you can see network traffic counts, in and out.

Conclusion

In the short time that I have used the software, I found the PdaNet tethering solution extremely usable and have no hesitation in recommending it.

In fact, I decided to skip the 30-day free trial and have purchased my license.  For the functionality provided and the security it gives for something as important as web access, I’d say it’s money well-spent.

If you’ve used PdaNet, I’d be interested in hearing your views.

There’s a convenient Twitter hash-tag for this movement: #BuzzOff…  it could even start trending.

Intrusive and Noisy

Rather than offer an opt-in, Google have assumed Gmail users will want Buzz.  For those that choose not to partake, there is no simple opt-out button in the Gmail settings.  It can be turned off via a link at the foot of the Gmail page, but this does not get rid of any Buzzes automatically generated from your Picasa and Reader activities.  Nor does it remove you from the follow lists of other Buzzers or remove others from your following list (kindly generated by Google on your behalf).

Mistakes

It’s amazing that Google did not exercise their usual caution by rolling Buzz out initially to a smaller set of Gmail users.  This would surely have generated a lot of useful and less public feedback.  Perhaps Google had its reasons to act in haste, but it seems to have been handled quite poorly.

Google are taking note of the [mainly] negative feedback, and I’m sure there is a huge effort now to improve the way Buzz works and undo the bad publicity.

Don’t want Buzz?

Here’s a link to instructions to comprehensively turn off Buzz for your Google account:

http://news.cnet.com/8301-17939_109-10451703-2.html

Nice try, Google.  Better luck next time.

The new one is called “Steira” and is the work of Made By Elephant.

How do you like the new look?

At the time of writing this, I’ve had my Nexus One for five short days.  I find myself slightly troubled: while the Nexus One is a truly beautiful device, I don’t have the same emotional attachment to it as I have to my Hero.  This may be because it’s too soon… the Hero is still there on my desk, as a WiFi device… it’s hard to let go.

The GoogleNexusOne channel on YouTube has some vidoes (embedded below) that may encourage that emotional attachment.  They’re certainly nice to watch.

Episode 1, Concept & Design

Episode 2, Display & 3D Framework

Episode 3, Testing

Episode 4, Manufacturing

Added, 8 Feb 2010…

Episode 5, Day One

I was one of around 70 devs at Google’s London offices for the Android Developer Lab session.  After the check-in and half an hour for coffee and a light breakfast, we were ushered into the “St James Park” room and took our seats.

About ten minutes into the presentation there was a knock at the door: some important packages had arrived for the presenter.  Apologising for the interruption, he left the room, quickly returning with a fellow Googler carrying the first of two large boxes.  Already there was an air of excitement in the room, as the two Googlers opened one of the boxes.  After looking at the contents for a moment in mock surprise, the question to the devs: “Who would like a Nexus One?”.  Oh, joy!

Ten minutes later each dev in the room had a Nexus One.  Geeky enthusiasm was thick in the air as the room filled with the excited sounds of joyous devs unpacking their new hardware.

Tweeting was the obvious thing to do and we were asked to include #ADL2010.  On the presentation display the tweets began to roll in.

Pictures were taken by Googlers, Nexus Ones (Nexii ?) were waved and smiles were wide.

On with the presentation, covering the APIs and features of Android 2.1 and the potential for great apps on devices like the Nexus One.  No mention of tablets, but this has to be a target platform that offers, perhaps, even greater creative scope.   It’s another reason Google wants devs to get on board and produce some head-turning apps.

We then had a freestyle lab, with devs given the opportunity to see how their apps run on a range of Android phones provided by Google.

The lab concluded in time for lunch, with the usual exchange of Twitter and email details.  I came away inspired by the presentation, the Nexus One and, not least, by the other devs that I’d met.

This event was just one of many Android Developer Labs that Google are holding over the next few weeks in cities around the world.  If my own experience is anything to go by, there will be a lot of very enthusiastic Android devs out there.  We can expect great things in the Android Market.

The Nexus One makes a great Android dev platform, and I look forward to making full use of it.

Like Woody when Buzz Lightyear arrived on the scene, I’m not about to abandon my faithful HTC Hero.  There’s something about the Hero that makes me just a little unsure I really want to move to the Nexus One.  More on this later…

A nice feature is its ability to generate a QR Code for a range of textual data types on your phone.  This can then be scanned by someone else’s phone as a way of sharing information.

• Contact
• Bookmark
• Clipboard
• Application

I had seen QR Codes occasionally but never knew that they were so useful.

Google have a web site, ZXing (“Zebra Crossing”), with a Java code library that can be used for bar code applications.

The possible uses of QR Codes are almost endless.  Google recently announced a Favorite Places initiative, whereby restaurant and shop owners receive a QR Code to put in their windows linked to Google Maps localised data.  This would allow, for instance, the menu of a restaurant to be viewed by scanning the QR code in the window, perhaps with a special discount voucher deal.

Nerdy idea: How about having a QR Code party, where the guests have QR Code tags which tell something about themselves… it could be interesting.   In fact, it wouldn’t surprise me if someone at Microsoft has already done this for those massively popular Windows 7 Launch Parties… if they didn’t, they should have.  What a missed opportunity.

Another use could be a kind of treasure hunt, where QR Codes have to be collected, and each code provides a clue to the next one.  This could actually be fun.

I wanted to do a QR Code for myself, as an alternative to the traditional business card.  Well sort of.  I found a web site that has this as an online tool, Kaywa QR Code.  Their web app will create a QR Code from any text you enter (up to 250 chars).

So, here I am, in a QR Code… perhaps I should put it on a T-shirt.  Already been done, no doubt.

Scan me  :)