Nokia E65 Issues

There are just a few things I don’t like so much about the Nokia E65.

Firstly, and foremostly, there is a noticeable delay when doing particular actions. For instance, pressing the Address Book key and then typing a name in means you invariably miss the first couple of letters. And it only sorts by the start of the name, not text within the name.

Secondly, and at times more annoyingly, if I happen to close the slide at the same time as another action happens, like someone hanging up on the other end of the phone, it turns off.

That’s right, the phone goes dead. I then need to wait (minutes, it feels like) for the phone to finish starting up again.

The camera is badly placed, too. Not that I want to do video calls, but I can’t see the caller and them see me at the same time. because there is only one camera, and it is on the back.

Another annoyance is that address book entries don’t have a default number by default. And it takes ages to go through (delays each time) to setup the defaults. And these don’t sync properly with Apple’s Address Book, so if you reset your phone (for instance, to see if you can fix the shutdown bug), you lose all of the defaults you have carefully set up.

There is no autolock. It prompts you to lock when you close the slide. You can install software to automatically lock after a period of time, but if you close the slide at the same time as when the autolock kicks in, the phone turns off.

Bluetooth appears a bit dodgy at times. Sometimes it no longer connects to my computer, and I need to restart my phone. I think it is more to do with the phone than the computer, but I’m not sure.

Battery life is crap. I didn’t want to have to charge my phone every night, but if I use WiFi, then I do. If I just use Bluetooth, which I need to have for synching, then it’s every second day.

Salling Clicker is awesome. I have an addon script that synchs my phone every day, and it displays incoming and outgoing caller information via Growl. It also fades my system volume, and pauses iTunes when I am on the phone. This is the sort of thing that computers should do. All of the time.

Scheme/UC Berkeley

While I’m in the “learning a new language” mode, I thought I may as well start listening to the podcasts I’d downloaded from UC Berkeley, from the well-regarded CS61A course, and the associated textbook The Structure and Interpretation of Computer Programs.

The textbook is also freely available, including in a handy PDF version, and I’m working through that too.

The language used is Scheme, which is a Lisp derivative. It actually looks a bit like Objective-C in the way functions are called. Thus you see stuff a bit like:

(+ 5 6)

(solve 4 65 3)

That is, a prefix notation is used. The function (and operators, such as +-/* are also functions) comes first, followed by the argument(s). Compare this to Objective C:

[celsiusTextField setTextColor: [NSColor blueColor]];

In Objective C, the object comes first, then the method, then the argument(s). A different structure appears where there are multiple arguments:

[object methodName: argument1 secondArgName: argument2]];

I’m still struggling to think back to my C days, but there are lots of things about every language I’ve used since python that I don’t like. Memory management, pointers, static typing, there just doesn’t seem to be any reason to have to worry about this shit.

Probably the biggest thing for me is that it is exciting me about study next year. Even if it will be learning Java, and putting up with rubbish all over again…


Back in 1970, the French Government tested a heap of Nuclear weapons on atolls in the pacific. This photograph is allegedly one test on the island of Licorne.

This photograph looks so much like a painting it is amazing.

(From Licorne (Monoscope))