CrazyTB's blog

I have a Nokia 6120 classic mobile phone, as well as a Sony Ericsson K750i. I've already posted a review of K750i. I also wanted to write a review about this Nokia phone, but the lack of time and motivation prevented me. In one sentence, Nokia 6120 classic (or any Nokia S60 phone) is very powerful, has lot of nice features, but also has an awfully bad interface. Sometimes it is so bad that it felt like Windows.

Right now, however, I'm not talking about the interface, but about a mis-feature that Windows also has: hard-coded daylight saving time settings.

God damn it, Nokia! Why do you have a hard-coded DST setting? Why? And again... Why?!?

Thanks to you, Nokia, I'm now awake 1 hour earlier than I should.

I use this Nokia 6120 classic phone as my alarm clock. Its flexible alarm allows me to set different alarm times for different days. Basically, I can set as many alarms as I want. It's very flexible and useful.

But it loses the usefulness when coupled with hard-coded daylight saving time dates.

Windows always had this very same issue. Not sure if it's fixed by now, but it was very irritating in the past.


So, how Nokia could have implemented it? Basically, the same way as Sony Ericsson did. On my good and not-so-old SE K750i, there is a small setting where the user says if DST is currently active or not. Just that, nothing else. Okay, the user must manually set that, at least you do it once and it works. In Nokia with its hard-coded DST, the user must fix the time once, and then fix the time again when Nokia automatically (de)activates DST.

And there is more! Now I'm pretty sure that it will happen again next year, whenever DST ends. So, next year, I might wake up 1 hour later than I should. (or maybe 1 hour earlier, it depends if actual DST ends before or after the hard-coded date)

Damn you, Nokia. Damn you.