27
Nov 09

Lost my life inside N900 – sudo’ing it back (with a blessing from Nokia)

Errata for my previous post: The Nokia Updater didn’t brick my N900 test unit. The gloomy morning greeting was caused just by a drained battery.

Nokia Software Updater isn’t supported on Windows 7. It just fails:

Nokia requires that I use either Windows XP or Windows Vista. Fortunately, I had a spare XP virtual machine lying on my disk, and managed to reinstall the system software.

Unfortunately, this didn’t clear the user data from the device. How… unexpected! Well, you could call this a feature, or a blessing, depending on your situation. Now you don’t have to hassle with backuping and restoring your Maemo device every time you do an OS upgrade.

But for me it’s a curse. I really, really want to erase every bit of personal data on this device. I synced it yesterday with my Outlook, and now it seems to contain every bit of both my personal and work life.

I sent Nokia guys several e-mails requesting assistance, but haven’t got any response yet. *

After trying out things by myself, I’ve figured out that there really isn’t a simple command to erase all the accounts, passwords, logs, pictures and what not.

Since I am fluent with Maemo, I’ve decided to install root access and SSH on the device, and start digging within the file system.

I so wished it wouldn’t get to this. I wished that Maemo 5 would be mature enough for the average user. I pretended to be one, until now.

rm -rf, here I come!

*) Got just official response back from Nokia. They confirmed my suspicion: there’s no GUI command for removing all personal data, and regretted that N900 is still a “hacker device” in some respects. I was instructed to use rm -r .*. Hint: choose your working directory carefully! :-)


27
Nov 09

N900 bricked by Nokia Software Updater?

In the morning, a very dark N900 was waiting on my desk. When I left it in the office yesterday, it was still very alive with the Nokia logo and a USB icon on the screen.

The instructions tell me not to disconnect or abort the process, or I’ll break the thing.

But I have to return it back to Nokia today – other reviewers are waiting for the unit.

I resorted to the manual for guidance: “Read the documentation stored on the device”. Well, that’s quite difficult now, but thank’s for saving some paper.

Quite a conundrum here.

(Errata & follow-up)


26
Nov 09

Stuck with the N900 review unit

The first Maemo phone has finally gone through our tests, and the critical review is done.

isani-and-n900

Tomorrow the unit goes back to Nokia, but first it has to be re-initialized. So, I launched the Nokia Software Updater and started the process as usual:

still-flashing

Alas, the progress bar seems to be stuck. The estimate “15 minutes left” hasn’t changed at all in 2 hours.

Oh well, I’ll leave it crunching for the night and disconnect it it the morning.


24
Nov 09

What you need to know about Chrome extensions

A browser action that shows unread messages.

A browser action that shows unread messages.

Extensions for Chrome are about to take off. The functionality has been in developer builds for a while, but Google is poised to bring it to all users.

1. Extensions are web apps

Extensions are ZIP packages with HTML, JavaScript, CSS and images inside. A JSON manifest tells Chrome what the extension does and what features it has.

2. What they can do

  • Edit page content (ad blocking!)
  • Use web APIs (through RSS, JSON etc.)
  • Add buttons and information to the toolbar
  • Open and close windows and tabs
  • Manage bookmarks

All access to tabs, windows and content is done through JavaScript APIs. Each extension is run isolated, and it cannot access other extensions or scripts that run on web pages.

3. What they can’t

  • Run arbitrary code
  • Add toolbars, sidebars, menu items etc.
  • Manage downloads, cookies, proxies etc.
  • Edit browser preferences

Note that future versions may have API hooks that do these. For now, extensions can’t touch the inner workings of the browser.

4. Browser and page actions

These are the two main types of UI for extensions. A browser action is a button that’s always visible. When clicked, it can open a new tab, show an info popup or do some other function. The button can change appearance and have an overlay badge like an unread count.

Page actions are the same, but the button only appears when necessary. This could be used for subscription buttons, for example.

5. Install without a restart

Click to install, enable/disable, update or uninstall. No restarts ever. For someone with a long Firefox background, this was quite the eye-opener.

6. Security model

Chrome isn’t a Firefox-like “extensions can do anything” system. Every extension must declare privileges it needs, like access to bookmarks or a specific domain. These are shown to the user when installing an extension.

7. Userscripts

Google provides a way to package existing Greasemonkey userscripts into Chrome extensions. In fact, userscripts are the way page content is manipulated in Chrome.

8. Background processes

If extensions are just JavaScript, how can you monitor ongoing events? An extension gets an invisible always-open page, where the JavaScript can keep on running.

9. Updates

Updates are fully automatic. An extension’s manifest contains an URL that Chrome listens to for future updates.

10. Gallery

Google already has a gallery for Chrome themes, and an extension one will open soon. Developers are invited to submit their extensions for the gallery.


24
Nov 09

As easy as copy and paste

How to copy text from a web page on the iPhone:

  1. Tap-and-hold on the text.
  2. Markers appear. Drag them to the beginning and end.
  3. Tap Copy.

How to copy text from a web page on the Nokia N900:

  1. Drag with the stylus from outside the left edge of the screen to the middle. (Note: This doesn’t work with a finger.)
  2. A cursor icon appears. Tap it quickly, before it disappears.
  3. Drag with the stylus across the text to select.
  4. Tap the menu.
  5. Tap Copy. (Note: This menu item may randomly not appear. Try again.)

Note that on the N900, this only applies to the browser. For other applications, the way to copy is either different or not available. You may need to use cursor keys instead of the stylus. Sometimes you need to hold down Shift, sometimes not. Selecting text can make it an unreadable blob of single color.

My point? Apple got no end of grief for not having copy-and-paste on early iPhones. A trivial feature, it was called. Implementable in a few lines of code.

On the new Nokia flagship model, the same feature is inconsistent, haphazard and a pain to use. Sometimes it feels downright accidental that it works at all.

All features are trivial if you don’t care about doing a good job.


24
Nov 09

Linkpost: iPhone malware, N900 and WinMo depression, Chrome extensions

Mainly mobile topics, with some Microsoft and Ruby filling:

  • Spotify now runs on Symbian in addition to iPhone. No news on Silverlight port for Symbian at last week’s PDC.
  • Nokia sent a batch of N900’s to the Finnish press just before PDC. Haven’t had a chance to play with our test unit yet personally, Ilari has – with mixed feelings. Perttu Pitkänen (Digitoday, It-viikko), thinks its “sturdy” and “beats iPhone in multitasking”, AfterDawn likes the performance but dislikes the apps and limitations.
  • Joe Wilcox writes in his PDC09 summary, that Microsoft “mobile phone strategy is a disaster”. Couldn’t agree more.
  • Expression Web Service Pack 1 has been released. Mostly bug fixes, improves PHP editing (not something you would expect in a Microsoft product).
  • Jailbroken iPhone and iPod touch users attacked by a new worm, this one sounds nasty.
  • Google Hacking is always fun. This times PDF files printed with IE leak path data. Doesn’t sound that serious, though.
  • WoW turned 5. Times flies!
  • iPhone and Android make up 75% of mobile browsing in the US, according to AdMob.
  • A new standard for content management systems is being prepared under OASIS. Seems quite enterprisey.
  • JRuby is making progress, also on Windows. Haven’t noticed much enthusiasm behind IronRuby, though. InfoWorld report from RubyConf.
  • And finally: Google opens Chrome to extension developers. Look out, Firefox.