IT: Nokia E90 – The First Few Hours

 Computing  No Responses »
Jul 282007
 

I have been a PDA user for many years (since the Psion 3 although I’m no Psion groupie … I’ve been through Palm devices and the Sharp Zaurus on the way to the E90), and have carried a separate phone. This of course has disadvantages in that the PDA is not generally “connected” and it is all too often left behind when you don’t think it will be needed … for instance on the little 70 minute stroll I’ve just taken. I’ve always been intrigued by the Nokia Communicators not least because they had more or less evolved from the old Psion 5 (which had the best damn keyboard that a PDA has ever had and probably will ever have), but had always steered clear because I had always stuck with the phone provided by my mobile provider.

I eventually (early 2007) went SIM-free mostly because the free phones provided with a phone contract were getting nastier and nastier, and got myself a Nokia N80i. Then I heard about the E90 and kept thinking about ‘converging’ my PDA and phone, and when it became available hit the button to get one. It turned up yesterday afternoon (after a whole day of waiting in for it 🙁 ).

Opening The Box

After clearing away a few freebies provided by the phone seller … including a pointless piece of ribbon for dangling the phone around someone’s neck (not mine! Being a little more paranoid than most I don’t like providing an attacker with a ready made garrotte), and a mysterious 10cm circle of sticky silicon, I find the phone. Big and red.

Take a 3cm thick A5 pad and chop into three equal sized pads and you get something more or less the same size. Small enough that it will still fit in my front jeans pocket, but big enough that it is now difficult to take notes out … time to rethink how I organise my pockets or possibly get one of those quaint belt cases. Picking it up and you instantly realise that you are holding something that is not cheap and nasty.

The battery compartment cover is a bit fiddly, but not so much so that if you swap batteries regularly you will dread that time coming. The slot for the SIM is great … just slide it in rather than have some kind of nasty bracket in there to make things fiddly. Put the battery in and you’re ready to go … nice that the battery is provided with some juice in it unlike some high tech gadgets where you are supposed to charge the battery overnight before turning the device on.

Getting the 1Gb mSD card inserted is no more fiddly than any fiddling with mSD cards is. Who decided mSD was a good idea anyway ? SD cards themselves are small enough themselves, mSD is too small; accidentally drop it onto a shag-pile carpet and you’ll spend half an hour hunting for it. Not that I have such a carpet of course!

And no Nokia pop-tart connector! Instead you get a mini-USB connector and a 2.5mm headphone/microphone connector. That is a relief … the engineer who came up with the pop-port was obviously coming off a 10-day bender … ok concept, awful execution.

First Poweron

I plunged straight in … just opened the clamshell and started using the big screen and keyboard. Kind of a surprise seeing the old Nokia startup graphics on an 800-pixel wide screen. The screen itself is bright and sharp, and probably perfectly readable outside. The default font is kind of large on such a screen (but is tweakable so you can see more on screen). The keyboard is pretty good as well. Although not a particularly full travel each key does give positive feedback, better than the Zaurus! However it is kind of small and it is all too hard to miss the key you are aiming for and hit another by mistake (although I have noticed my accuracy towards the end of this ‘first few hours’ has improved). Odd because by reducing the over-sized ‘special’ keys at both sides of the qwerty pad it should be possible to make the main keys ever so slightly bigger.

Straight from the beginning, the E90 was perfectly functional as a phone; a quick delve into the “Data Mover” and my contacts from the N80i (and gallery contents, notes, etc) were flashed across bluetooth onto the E90. A quick bit of configuration and the phone is online using my WifI router. Following my own instructions and my calendar was synced to the corporate calendar. At this point I was effectively finished at setting things up with the exception of figuring out some way of getting my iqnotes data onto this phone (some hacking with Perl to import them into ActiveNotes).

Candybar Mode

Shut, the phone actually works better for receiving or making calls than an ordinary mobile; the size is more comfortable and unlike the N80i it doesn’t try to rip out my beard. The keys on the top are larger than modern phones and easier to use; with the exception of the “green” and “red” buttons which share space with a total of six buttons and the navikey. It makes it difficult to hit the right key and there is plenty of space for an additional row of keys. Kind of irritating as I can see myself using the “smartphone” functions in closed mode very rarely and the additional keys are only necessary when using the “smartphone” functions.

However the screen whilst relatively small for a smartphone (it is after all, effectively just a secondary screen) is pretty good and perfectly visible outside (I did test the small screen outside) although I have not had the opportunity to test it in bright sunlight (currently rather rare in the UK). It is even readable enough in powersave mode to read the time (something I sometimes found tricky on the N80).

VoIP (Truphone)

Following the instructions to ‘re-install’ Truphone (my VoIP provider of choice seeing as it is a UK company, and currently gives me free calls to UK landlines in addition to many other destinations) and it was on the phone and ready for testing. A quick phone call showed everything was working fine. The provided headset seems to be even better than the one provided with the N80i and would probably work perfectly well for listening to music.

Truphone itself is almost invisible disappearing seamlessly into the native interface, just allowing the “Internet” option to the “Call” menu to function via Truphone. I only use Truphone at home, but I see there are multiple profiles to allow Truphone to work in multiple locations with different Internet connections.

Web Browsing

I am not normally one for browsing the web on a small screen, but the Nokia web browser on the E90’s screen works well enough that I used it to visit my Del.icio.us bookmarks for the Nokia smartphones (mislabelled Nokia_N80) to download additional tools (well I also used the native “Download!” thing as well). Incidentally if you haven’t already tried it, using Del.icio.us for your bookmarks is quite useful when you have more than one computer to use them from … assuming you don’t mind your bookmarks being public of course!

The browser will “zoom out” to display an overview of the entire web page if you keep travelling around the page too long. Possibly more useful on a smaller screen than the E90’s where it does seem to get in the way. Another oddity is that the “Back” button we find in all browsers does not just go back to the previous page, but gives you a scrollable list of overviews so you can travel back more than one page easily. Perhaps it is just something one needs to get used to, but I frequently found myself going back further than I intended.

Summary

This one is definitely a keeper, and I’ll probably be keeping it for quite a long time. It does pretty much everything I need although a serial port would be nice for those odd occasions when I need something portable to connect to the console of a Sun E6900 (there is something oddly perverted about using a handheld computer for controlling an enterprise computer with more CPU cores than is easy to count and is the size of a full rack). Many of the “rough edges” I have noticed so far, are things I will get used to like the size of the keyboard, etc.

The only disappointment has been the GPS device which won’t work although that is probably because mostly I’ve been trying it indoors … not wise!

Now I’m off to throw that mysterious silicon circle against the wall for amusement … it sticks!

Why Rockbox Your iPod, iRiver, Gigabeat, or Archos Audio Player

 Computing  No Responses »
Jun 212007
 

I have been stimulated into writing this by a slashdot article (not worth linking to) where people were arguing about the merits of installing Rockbox onto a compatible audio player … such as the iPod. Some people seem to think that replacing the standard iPod software is heresy!!

Or at the very least are complaining that Rockbox does not work the same way as the standard firmware.

I am in a somewhat odd situation … I bought an iPod after I was aware that Rockbox supported the iPod (and specifically avoided the 80Gb Ipod as it wasn’t supported at the time) to replace a rockboxed iRiver iHP100 (more commonly known as an iHP110) that was suffering from a lack of battery “oomph” (and yes I had tried replacing the battery). I spent probably just a couple of minutes in the native firmware before switching to the Rockbox firmware because I did not want to re-encode several thousand OGG-encoded tracks.

Now obviously I cannot criticise Apple’s interface or functionality on the iPod because I have not really used it.

However I can say that the Rockbox firmware is a perfectly adequate interface to run on an iPod and is getting better every week. Some of the features the Rockbox has include :-

  • Multi-codec support to play MP3, OGG, FLAC, AAC, WAV, … encoded files. I haven’t pulled down the full list but you really cannot get an audio player offering more codec support on a portable device. Not everyone needs this of course, but it is nice to have the choice.
  • The default Rockbox interface is kind of ropy on the iPod, but it is “themable” and some of the themes are pretty good … just have a look at the Rockbox Themes website (I have linked to the iPod Video themes)
  • Numerous “plugins” for playing games, displaying photos and other miscellaneous things. I must admit I don’t use them too much, but being able to play Jewel whilst bored waiting somewhere does come in useful.
  • The standard mass storage method of storing audio tracks in a way that can be easily accessed outside of iTunes does mean it is easier to copy some tracks to another computer easily. Of course I mean the freely distributable tracks!

Rockbox does have some disadvantages … the battery life is relatively poor compared with the native firmware (but very much better than an iHP100 with a tired battery!), and if you have a lot of investment in iTunes you will suffer from the lack of support (although the Rockbox database will track down files stored on the iPod whether they were put there by iTunes or just copied).

The most sensible advice for an iPod user thinking about making the switch is just to try it out. You may like it or you may not, but you don’t have anything to lose as you can always go back to the standard firmware. In fact as you can easily switch from one to the other, you can try out Rockbox gradually over time … go back to the native firmware when you are lost, and go back when you are feeling adventurous.

Another advantage that the existent Rockbox provides, that many people miss is that it may just put some pressure on Apple to improve their native firmware. If Apple notices that many of their iPod customers install Rockbox, they may be inclined to take a look themselves and start implementing features in their native firmware to “keep” their customers … surely something that would be good for all iPod owners.

IT: The Spam Problem

 Computing  No Responses »
May 192007
 

Just fixed the scripts that create (and update) my spam report. I decided long ago not to block spam (previously it was difficult to block it properly because of how email was setup; I could properly block it now but it would ruin the report), so I could produce an archive of spam and do some basic analysis on the content. I’ve been running the report a few years now (the oldest spam in hand dates to roughly June 2003) and it now shows the expected trends … the number of spams is growing and the size of each spam message is growing (because many these days are image spams).

Apart from the existence of spammers themselves (if they were to vanish overnight, nobody would mourn), there are two major contributions to the spam problem :-

  • People unwittingly providing the spammers with massive supercomputer with an enormous amount of network bandwidth available. Almost every
    spam you and I get has been sent via someone’s infected computer. If you don’t have a router between your computer and the internet,
    buy one online in the next 15 minutes. Whilst there are other things you can (and should) do to make your computer more secure, a router is
    probably the biggest single thing you can do.
  • ISPs who don’t bother to deal with infected machines. In the old days, if you were to warn a network administrator that they had a machine
    with a possibly dangerous infection sending large quantities of network traffic, they would move heaven and earth to fix the problem. Today
    an unfortunate number of ISPs would rather let the spam go through than possibly annoy a customer.

IT: Software Patents and Microsoft Bullying Open Source Developers

 Computing  No Responses »
May 192007
 

Microsoft has recently claimed that open source software breaches exactly 235 software patents. Apparently open source developers “burn down the patents system”. Well my response to that is “well done open source developers”. Software patents are the biggest scam out there … bigger by far that all those scams we receive in our inbox every day. I quite happily say that companies trading on their portfolio of software patents are amongst the slimiest examples of capitalism and that even Microsoft were not that bad. Of course now they seem determined to join them.

A bit of tedious history … patents were first introduced as a mechanism to protect individual inventors from being ripped off by large companies. The 19th century is full of examples of individual inventors being ripped off by large companies. So patents for “hardware” inventions are not necessarily bad things.

Software is somewhat different. Software developers utilise software libraries written by others without inspecting the libraries for ‘patent violations’. When writing new code, they will come up with solutions to problems without realising that the solution they come up with has been used before. For instance one of the many algorithms for sorting is the insertion sort; it is not the most efficient sort, but is efficient enough (and probably more importantly is a stable algorithm) and is so simple that it has probably been re-invented many times. Certainly I thought of it back when I wrote a database engine for the BBC micro. There are many examples of software patents that are this simple.

For example, Microsoft holds a patent on a mechanism for navigating a web page in a graphical browser using the keyboard which requires that the ‘current link’ is highlighted in some way. Not only is there an example of a web browser using this mechanism before Microsoft’s patent (Lynx … a text browser that does exactly what is described in Microsoft’s patent), but it is a mechanism that is so obvious that it has been invented many times independently. Text editors on text terminals in the 1970s (and earlier!) used some sort of highlighting to indicate the current ‘active point’ on the screen and many of these editors were developed independently. So Microsoft’s patent here is a development of prior art (the only new thing is the graphical interface), and the basic concept of pointing where the ‘active point’ is, is one of those things that is obvious.

Back to Microsoft’s claim that open-source software is in breach of its patents … what exactly are these patents ? Well Microsoft doesn’t appear to be letting anyone know, which is kind of underhand as it stops open source developers from attempting to remove the problematic code. Linux Torvalds also points out that Microsoft hasn’t released their own source code to see how many patents they might be in breach of. Who knows ? Perhaps Microsoft has taken open source code and then patented concepts developed by open source developers … certainly it is known that Microsoft’s TCP/IP software is based on the BSD TCP/IP network software. Linux also points out that Microsoft has probably used many technologies developed by IBM such as demand paging and the like.

Most sensible people seem to believe that Microsoft’s tactic here is to spread FUD over the use of open source software to encourage people to use their own software. Perhaps they should spend more time on making their software better rather than indulge in dubious legal practices.

IT: A Rambling Look At Ubuntu Linux 7.04

 Computing  No Responses »
Apr 282007
 

This is intended to be quite a long piece and may be saved before it is fully completed. Some of the content will be more general ramblings on Linux in general rather than specific to Ubuntu 7.04

I recently installed Ubuntu 7.04 (not without a few problems that most people are unlikely to encounter) and thought it worth rambling through a few thoughts that occurred to me. Most of the ideas are related to how Ubuntu would come across to less experienced users although to be frank I find it difficult to put myself in their shoes. One point to make fairly early is that Linux distributions have conflicting goals … they need to appeal to the less experienced user without putting off the ones who have been running Linux for years, compiling their own kernels and generally getting used to the deeper levels of Linux. One idea here is to have two “sides” to every configuration screen … one for the easy options and one for the advanced options. This does not necessarily need to be implemented as a GUI window that can be turned over, although that is not a bad idea.

I installed using the “alternate” installation CD and did not bother with the “user-friendly” partitioning options, so I can’t say much about the normal installation CD or the partitioning experience. However it is worth noting that partitioning is a somewhat tricky concept to someone new to Linux who has not necessarily done much in the way of partitioning under Windows. Also selecting different filesystem types (ext2, reiserfs, xfs, jfs, etc.) is not something that the average user will be comfortable with.

Mind you Linux installation is not exactly difficult. Those who claim it is, are frequently overlooking just how difficult XP is to install. Either they are already used to it, or have never installed it in the past! Of course installing Linux is trickier than running the Windows that was installed in the factory on the average PC.

Incidentally, whilst I understand that setting up complex partitions and filesystems is inevitably going to take a while, my configuration took as long to setup as the rest of the installation! This is somewhat extreme!

So the ordinary user has managed to work their way through the installation routine and has rebooted the system. They are now faced with a blank screen with just a ‘username’ prompt in the middle. It would be nice here to have a one-off prompt in a seperate window here to explain that the user needs to login with the username and password they created during the installation and a brief explanation of why logging in is a wise mechanism

So the user logs in and is presented with a fairly typical GNOME screen which is quite blank. It would be quite nice to start a “What To Do Now” screen here. The GNOME help feature is quite useful when started, but it should be started for new users. However advanced users may prefer to “turn it over” to get a more complex default index with content that applies more to them. This could be nothing more than a single item on the help screen titled “Advanced Users” to give instructions on how to do it (something like dpk-reconfigure yelp advanced-view) … a command line command here is appropriate to indicate a barrier that should be climbed before it is appropriate to “turn this page over”.

One other thing on a series of documents explaining Linux to new users. It could explain some of the typically installed applications … which ones to use to do what, and where to find them in the menus. It could also explain the reason for the funny names … that many of the applications are created by programmers and named by them, and not to let their sometimes peculiar sense of humour be offputting.

Traditionally Ubuntu has avoided including proprietry codecs for common multimedia formats such as MP3. This is for genuinely legitimate reasons and I am not suggesting this changes, but the help screens should have a number of entries relating to this. “Playing Proprietry Encoded Music And Videos” should point to a help screen saying why these formats are not included by default and simple instructions in installing them. “Why Can’t I Play MP3s” and “Why Can’t I Play DVDs” should give a short explanation and point to the instructions on installing them. By all means make the point that priorietry formats are evil, but be helpful too.

Oh! And don’t lie in help screens. At one point Ubuntu claims that their package manager is the only way to install software. This is obviously not true to advanced users and could eventually be seen as not true to ordinary users too. Just say that it is strongly recommended to install software using the package manager as an obvious mistruth makes one wonder what else is wrong.

Ubuntu comes with a fairly easy way of enabling “desktop effect” with an appropriate warning about their stability. However it only enables compwiz and I wanted to have a quick look at beryl. This was acomplished fairly easily, and I suddenly had access to a great deal more desktop effects. Some very interesting eyecandy it was too, some of which I can see could be quite useful.

However the preferences screen was a little swamped with different configuration options. Whilst beryl is most definitely in an early phase of development, it would be wise to look at this. Not that all of the options should be removed, but going back to a phrase I used earlier, “turning over” the options screen to keep the advanced options hidden from most users should be considered. It also needs far more explanation of what all the options are. Perhaps a button to “grow” a simple explanation into a longer more detailed explanation.

What if things go wrong and the new user needs assistence ? Well there are two parts to this … problems during the installation that results in a system that cannot be booted, and problems that crop up after installation.

For the second, there needs to be a section in the help screens on obtaining assistence. This should assistence in obtaining information about the broken system (perhaps Linux needs a tool like “Sun Explorer” which generates a compressed archive containing the output of many different diagnostic commands such as fdisk -l, cat /proc/cpuinfo, etc). Also explaining how best to phrase support requests … anyone who has done technical support knows the problems that can come about because of badly expressed problem issues.

Ubuntu helpfully has pointers to sources for free online support, and to commercially available support. However it would be useful pointing out the basic difference between the two … free support can be of as high a quality as commercial support, but you cannot be certain of getting a response. Whereas commercial support has the downside that it costs money.

Finally (well … if you are lucky 🙂 ), Ubuntu comes with a fine graphical package manager called Synaptic; whilst as a crusty old Unix veteran I prefer the command-line equivalent, it does do a pretty good job. However a new user looking at Synaptic could be a little overwhelmed by the number of packages that are available. Synaptic has a series of ways of viewing the package repositories which can be helpful in finding what you want; why not add an additional default view (with a prominent button saying “See the rest”) that has just one (well perhaps up to five) “best of breed” package listed for each application.

A new user is less likely to be overwhelmed when installing software if they visit the package manager and see “3D Modeler” -> “Blender” instead of the current situation where “Blender” itself consists of half a dozen packages that they need to hunt through several hundred applications to find.

 Older Entries  Newer Entries