Quantcast
Channel: All About Symbian - S60 Content
Viewing all 1165 articles
Browse latest View live

Hands on with the DataTraveler, USB stick into Symbian microUSB

$
0
0

Guest writer Frank Bloise brings us a brief hands-on with the Kingston 32GB Micro USB 2.0 DataTraveler Flash Drive, providing an extra USB stick Symbian-compatible file store with no cables needed.

Frank writes (with some inline photo notes from me):

"Just to let you know I've been using this little accessory for a while, it works perfectly. It is a Kingston 32GB Micro USB 2.0 DataTraveler Flash Drive and is nothing more than a normal pen drive that also has a male microUSB end. It works basically on both PCs and in USB OTG enabled devices, such as the Nokia 808, N8, etc. 

DataTraveler

The gadget plugged into a Nokia 808 and showing its file system mounted....

I got it to test and play with the USB OTG functionality and to make it easier and quicker to transfer photos and videos off the 808 and to be able to share it to my PC or my other smartphone, a Blackberry Z30.

DataTraveler

The microUSB 'end'...

The speed seems adequate and I use it a lot, especially when travelling, to quickly share any photos between the 808 and my Z30.

DataTraveler

The USB 'end', for plugging into a desktop/laptop (etc.)

I got mine from Amazon UK here. There are other models (a bigger sized 64GB) and other brands (Sandisk has its own OTG) that I imagine work fine with the Nokia 808, N8, etc. "

DataTraveler screenDataTraveler screen

The storage mounted and in use on Symbian....

Thanks, Frank. Comments welcome if you've tried this gadget too!


Emulators and oddball games

$
0
0

'Another Guest' is a name from the past that cropped up again recently, along with the news that new emulators, updates of existing ones and new games altogether have been released for Symbian recently. See below for some highlights - if you like your retro gaming then maybe these are all worth a look?

From the Another Guest site - follow the title links for full post details and the download instructions:

OhBoy 1.00(0)

A gameboy emulator using the gnuboy emulation core.
Oh Boy is an SDL port of gnuboy and offers:
  • frame skipping
  • GUI menu for loading roms
  • GUI menu for some settings and saving them to gnuboy .rc files
  • FPS indicator (from SDL gnuboy port)
Screenshot

Then there's this update:

ScummVM 1.70(0)

ScummVM is a program which allows you to run certain classic graphical point-and-click adventure games, provided you already have their data files. The clever part about this: ScummVM just replaces the executables shipped with the games, allowing you to play them on systems for which they were never designed!

And then some games which were new to me:

Tile World 1.30(0)

Tile World is a reimplementation of the game "Chip's Challenge". The player controls Chip, navigating him through his challenges. The object of each level of the game is to find and reach the exit tile, which takes you to the next level. The levels contain many different kinds of obstacles, creatures both hostile and indifferent, tools, protective gear -- and, of course, chips.

...and...

Digger

Originally for the Nintendo, Digger is a game where you try to collect the diamonds and bags of gold while avoiding getting caught by your enemies. 

 

...and...

Xump 1.10(0)

Xump game consists of a 20 x 12 playfield, filled with different types of blocks.
The player must make the blue blocks disappear from the playfield by stepping on them. There are five main types of blocks, each of which behave differently.

...and, older, but still interesting...

Interlogic 1.00(0)

The game InterLOGIC is based on the old Amiga logic game "Balls". The object of the game is to move balls of different colors through a maze, connecting them with other balls of the same color. Two or more connected balls of the same color will disappear. The aim of the game is to clean the whole maze in this way. The balls are connected if they are right next to each other horizontally or vertically, but not diagonally. The current release contains 30 mind-breaking levels for you to solve.

Great stuff, and definitely showing that Symbian development hasn't stopped completely.

Major cuteRadio update, adds TuneIn, podcasts, and much more...

$
0
0

cuteRadio, only launched for Symbian a couple of weeks ago, is already developing apace, with this new version 0.2.x adding TuneIn integration, plus a lot more, as detailed below.

From the developer's blog post:

cuteRadio has now been updated to version 0.2.1. The Symbian version can be downloaded from here, the MeeGo-Harmatan version is available at OpenRepos.net, and the Maemo5 version can be obtained from the Extras-Devel repository.

Changelog:

  • Added TuneIn integration.
  • Added podcasts.
  • Added option to play a station/podcast direct from a URL.
  • Improved state-change notifications in the media player.
  • Added option to use an alternative media player.
  • Replaced ‘Now playing’ banner with a toolbutton. (Symbian/MeeGo-Harmattan)
  • New icon designed by Matthew Kuhl. (Symbian)

A couple of screens of the new version in action:

ScreenScreen

Great update, Stuart, keep it coming!

CountIt offers background proximity counting

$
0
0

New in the AppList Symbian Store is CountIt, a (wait for it) counter utility - it works via either touchscreen or - innovatively - via your Symbian phone's proximity sensor. And it works (via the latter) even when the phone is locked and the screen 'off' - try that on another mobile platform! See below for more...

From the official description:

CountIt is counter application based on QML.

You can count up or down directly via touch screen or use proximity sensor for more energy efficient non-touch way of control (can works in background or when is phone locked).

In every page is little information hidden in header. Just press it and you can get some information about page. Long press on header opens quick menu.

I gave CountIt a quick spin:

CountIt screenshotCountIt screenshot

A nice illustrated set of Settings, though the volume controls did seem a bit temperamental...

CountIt screenshotCountIt screenshot

Waving your hand over the proximity sensor is enough to trigger a count event - this works very well, even in the background or when the phone screen is locked! (right) you can count up or down, as needed.

You'll fnd CountIt in the new apps section of the AppList Store. Hopefully the Store is working out for you all. See here just in case you haven't already got this installed or if this is new to you. Also, if you have custom firmware installed, make sure you tick the option in settings to show 'unsigned' applications, you'll see extra applications!

Kaktus brings Netvibes to Symbian

$
0
0

Continuing the flow (ok, trickle!) of new applications for Symbian in 2014, Kaktus is an unofficial client for the Netvibes RSS feed reading system and includes a full offline mode, so you can read feeds on the underground (etc.)

From the AppList Store description:

An unofficial Netvibes feed reader, specially designed to work offline.

Kaktus is an unofficial client of Netvibes.com service. Using Kaktus you can fetch, browse and read your RSS feeds aggregated on Netvibes tabs and dashboards. The most significant feature is possibility to read articles in offline mode, so without a network usage. In such mode, previously downloaded content of web pages are displayed from local cache.

Good stuff. Some screens of Kaktus in action:

Screenshot, KaktusScreenshot, KaktusScreenshot, KaktusScreenshot, KaktusScreenshot, Kaktus

You can download Kaktus directly in the Symbian AppList Store clientHopefully the AppList Store is working out for you all. See here just in case you haven't already got this installed or if this is new to you. Also, if you have custom firmware installed, make sure you tick the option in settings to show 'unsigned' applications, you'll see extra applications!

Native Flickr sharing now broken for Symbian

$
0
0

Sharing images to Twitter, Facebook and Flickr has been part of Symbian and its Gallery for years, but changes at Flickr's end seem to have broken sharing to the latter. Such incompatibilities were inevitable, of course, as APIs change and services evolve and with Symbian frozen and effectively unsupported now. 

Yes, 'support until 2016' has been widely quoted, as something said by Nokia back in 2011, when the switch to Windows Phone was announced. But that was before the whole shooting match got bought up by Microsoft - which, clearly, has no incentive whatsoever to put resources behind such a relatively niche compatibility fix for a legacy platform.

Of course, it's possible that Accenture, still contracted to do low level Symbian support, might knock something up, but I think at this stage that it's unlikely. Please, someone in the know, get in touch if this is happening?

What happens at the moment is that you share to Flickr from Gallery and the upload starts... and then fails, though the only indication is that errors stack up in the notifications pane:

ScreenshotScreenshotScreenshotScreenshot

The process, from sharing to submitting the form, to seeing the notifications and the errors....

Gravity (beta) updated to encompass Foursquare API changes

$
0
0

I have no idea why Jan Ole Suhr doesn't just make the 'beta' version of Gravity the version, at this stage in Symbian's ecosystem history. Still, most people reading this will be on the 'beta' track, in which case note that there's a new version to be aware of. The good news? It fixes compatibility with changes made to Foursquare's APIs. The bad news? That's all that's different, so if you don't use Foursquare then don't bother!

Anyway, from the MobileWays beta page:

Version 2.85 Build 7305 - 03 Jul 2014

Download complete package for ALL phones

(DBG7305gravity.ALL.sisx, 3211 kB)

Smaller Installation Packages for Specific Symbian Platforms

Download for Belle, Anna, S^3 and S60v5 with Homescreen Widget Support

(DBG7305gravity.HSW.sisx, 885 kB - For Nokia N8, 808 PureView, E7, .. and Nokia N97, N97mini, C6-00)

Download for S60v5

(DBG7305gravity.V5.sisx, 839 kB - For Nokia 5800, 5230, ...)

Download for S60v3 FP2 with GPS Support

(DBG7305gravity.FP2.sisx, 809 kB - For Nokia E72, E5, E52, C5, N86, ...)

Download for S60v3

(DBG7305gravity.V3.sisx, 791 kB, 03 Jul 2014 - For Nokia E71, N95, E63, ...)

The Foursquare API change is all documented here, if you're interested.

It's pretty impressive that Gravity is still being updated for the old S60 3rd Edition/FP1 platform, dating back to 2006. It shows what can be done with some good old fashioned native Symbian C++ coding!

Some screenshot proof:

ScreenshotScreenshot

I always find it easier to download straight from the beta page and install in-place. The in-app updating doesn't work for the beta track immediately, etc.

AppList gets erroneous message bug-fix update

$
0
0

AppList, the (mainly freeware) Store for Symbian users for 2014, has been updated, with a Nokia Store-related bug fix. Version 1.0 Build 290 is available as an update if you just open AppList. It's also worth noting that the very latest Gravity build is also present (with the Flickr and Foursquare compatibility fixes).

Hopefully the AppList Store is working out for you all. See here just in case you haven't already got this installed or if this is new to you. Also, if you have custom firmware installed, make sure you tick the option in settings to show 'unsigned' applications, you'll see extra applications!

The problem this update fixes is when installing an application that used to be Nokia Store-hosted and now is stored elsewhere - erroneous messages would pop up, etc.

Here's the new (Build 290) update shown and working:

Screenshot, AppListScreenshot, AppList

Over the air updating of the AppList client and (right) the current 'What's new' page...

Screenshot, AppListScreenshot, AppList

One of the updates waiting for me was the very latest Gravity build (yay!), the other is Fahrplan, a public transport route planner.....


Star Browser for Symbian evolves, serious Web alternative?

$
0
0

Star Browser, last covered here on AAS, has now been signed it seems. Moreover, there's a major new version with a changelog as long as your arm. A serious competitor for Web and Opera/Opera Mini? Over to you, AAS and Symbian enthusiasts, let's evaluate it!

From the official description for Star Browser:

Star Browser is a colourful  and innovative QML/Qt powered browser, it comes with Unlimited Bookmarks, Customizable Homepage, User Sharing, a wide range of excellent user settings, Special Web search Area, 100% Fullscreen mode, Browsing History, ScreenShot Ability, Local File Access and last but not least the the UI can be changed in lots of ways from a large range of colours.

Here are the main changes, from the launch post for the new version (there are more listed, if you click through):

Much improved User Interface, 

  • Old browsing UI gone, now all features are accessible from the one big Menu (Slide Right for more options)
  • URL input available from Menu,
  • New Menu has some characteristics, Landscape/E6 shows all Items in one go, a Button with a white ring indicates that Button has a long press feature, A white fade over the Button indicates a enabled feature.
  • Symbian Qt Quick components replaced with darker backgrounds for better look and for less battery usage with in view.
  • VGA devices (E6, 702T) now support the UI better, massive shout out to Matthew kühl for all of his testing, helped me out a hell of a lot, Menu Button now shows page loading progress, and had long press features, Progress Bar is thinner and less intrusive.

Customisation

  • UI Colour customisation has being taken to yet another level

Search Area

  • The Search Area has undergone a complete revamp. You now have two ToolBars, Bottom consists of Close, Search History and Quick Search Engine changing. 
  • You can now also press the Enter key on your qwerty or keyboard to search. Search Suggestions have also being added, minimum 3 Characters.

Settings

  • I've re-organised Settings to make them easier to navigate, and faster to open. 
  • You are now told to press a Bottom Tab to begin since some users where confused about how to work it.
  • Added Private Browsing - Remove Browsing History on close

General Features

  • Background file downloading added (no progress indicators, just download started/completed banners, you can choose save location and file name)
  • Application now catches Red Key and Task Manager close events allowing the browser to fully utilise its function on close features.
  • Share Area now opens Choice in Star Browser itself
  • Open in default browser choices now launch in the user selected and not Nokia browser all the time.
  • RSS Feeds Area added, very basic at the moment, simple add and open, you can have as many as you like as well.
  • Simply click on a story to open the stories page.
  • Small update manager added (located in Settings-About- the Right ToolButton on the Toolbar
  • (This is only available to Belle Refresh, Belle Feature Pack 1 and 2 users, don't ask for lower support because even I don't know why it won't work on lower than Qt 4.8 builds)

The UI is certainly different, with the bottom pop-up control panel. Some screens of Star Browser in action:

Star Browser screenshotStar Browser screenshot

The browser opens to two help pages, showing the pop up main menu and what all the symbols mean....

Star Browser screenshotStar Browser screenshot

AAS and the full New York Times site rendered OK (though slow)

Star Browser screenshotStar Browser screenshot

Delving deep into Star Browser's settings - and tips pages...

In use, the browser seemed a bit sluggish on my test sites (I was using a 808 on Delight firmware, if that makes a difference?), but I suspect more data points are needed for the developer - hence the news post here on AAS. Please feedback below - or directly to the developer - in order to improve Star Browser further.

You can download Star Browser here in the web-based Store on Symbian Developers. Note that if you previously had the unsigned v1.5 installed, you'll have to remove this manually first.

The 'pro' music player QuasarMX moves on, updating and upgrading ex-Store...

$
0
0

Reviewed by me a year ago here, before the demise of the Nokia Store (in terms of updates or anything new), the 'pro' music player QuasarMX has been given a new lease of life by the developer, with a download path for the free version and an upgrade, license-transferring path for the paid version. See below for some quotes and links.

From my review intro:

However, real music afficionados might want to go further. Fancy gapless playback? Fancy playing back Ogg Vorbis and FLAC files as well? Fancy integrated, fully working cover art, lyrics, and artist bio downloading? Fancy a full 10 band parametric EQ with additional bass and treble customisations? Fancy comprehensive genre-based playlist construction? You'll be wanting QuasarMX then. 

From the developer post:

You may have read that upgrades via the Nokia/Ovi store are no longer possible.

For users of the Lite version of QuasarMX: Just uninstall the old version and download and install the free version.

For owners of the Full version of QuasarMX (now Pro) this unfortunately means that upgrading is a bit more involving because we do not have any record of who has bought the full version from Nokia. For a proof of ownership the new version of QuasarMX will scan your device for an older installed full version of QuasarMX.

Here are the upgrade steps for the Full/Pro version:

  1. Make sure you have the latest version of QuasarMX Full installed from the Nokia/Ovi store:
  2. Install the free version of QuasarMX from our website:

    Download QuasarMX free version

  3. Start the free version of QuasarMX (notice the new icon).

    NokiaQuasarMX

  4. The app will tell you that it has found an installed version of QuasarMX Full on your device. Please follow the instructions on the screen to create an account or login with an existing account. The license will be transferred to your account. Once this is done, you may either unlock the Pro features immediately in the app or download and install the package of the Pro version.
  5. You may now uninstall the old version of QuasarMX.

If you previously skipped the upgrade check, you can easily start the upgrade again via Main Menu > Help & AboutUnlock Pro features.

It's all worth it - I was very impressed by QuasarMX on Symbian:

ScreenshotScreen

ScreenScreen

Any problems with the update/upgrade, just see the developer's home page here. Any comments on QuasarMX in your life, a year on?

The future of the Lumia 1020 - another sidelined classic like the 808?

$
0
0

The clue is probably in the generic term 'camera-centric', really. However much people in the tech world like their phone cameras, having just a little too much emphasis placed on imaging - enough to warrant a significant bump on the back - seems to be the death knell for a device long term. In part though, this is more down to the time needed for R&D, but the end result is (yet again) a device which seems destined to be sidelined a little....

A little history

We saw this in action for Nokia's N93 - the original 'transformer' Symbian phone that could look like a regular T9 clamshell or a consumer camcorder at will. It tested well amongst geeks and camera phone enthusiasts but made no mark whatsoever in the consumer marketplace of the time (2006). The best-selling N95 escaped the 'camera-centric' tag because it had so many other innovations, of course, the integrated GPS, the GPU, the high quality stereo speakers, and so on.

The we run forward to the Nokia N82, from 2007/2008, the first smartphone with a Xenon flash, very definitely a 'camera phone' first and foremost. And still a device with just about the brightest Xenon illumination in the world, even after 7 years. But, despite appearing in High Street shops, it didn't sell in huge numbers.

Repeat the process with the N86, the first High Street smartphone with an 8MP camera and still unique in having variable aperture, the first to use intelligent digital zoom when capturing video and to use a digital microphone. So many innovations, yet the N86 also failed to set the sales charts alight, this time in 2009.

Nokia N86 camera

Next in line, the aluminium-bodied N8, at the end of 2010, with 12MP and Xenon flash and a, for the time, huge sensor. Sales started off well, using the new GPU-accelerated Symbian^3 platform, but then Nokia's Stephen Elop (prematurely) shot Symbian down on stage at MWC 2011 as part of the demonstration of support for Microsoft and Windows Phone, and the N8 never recovered.

Finally, on the Symbian front, we had the all-conquering Nokia 808 PureView, the result of five years of R&D, learning lessons from all the devices above, offering what's still (by far) the largest camera sensor in any phone, with 41MP sensor into which users could 'zoom', digitally, without losing light or quality, and with hardware oversampling producing noiseless, pure images at lower resolution by default. Released in spring 2012, a full year after Symbian's execution, it's clear that the only reason this still made it to market was that so much work had already been done on the hardware and it would have been criminal to not at least shown it off to the world. At least, not without a Windows Phone version ready, something which was still a year away. As a result, in the world of 2012, with Symbian's 360p screens seeming blocky compared to WVGA and 720p and with Android really taking off at the high end, and with Symbian utterly frowned on within High Street shops, the Nokia 808 PureView remained something of a cult hit only.

Lumia 1020 and 808 PureView

If there's a common thread in all the above, it's the inescapable conclusion that it takes time to create a really good phone camera. The space, weight and power constraints place extreme pressures on designers and in each case, by the time the phone hit the market, the underlying hardware was nearing the end of its relevance in the wider smartphone world. For example, the N82 was a full year after the N95 which had essentially the same internals, the N86 was a device and form factor from a bygone age even when launched, the N8 was legendarily delayed by up to a year, the 808 was borne into a completely hostile future.

And the same pattern applies to the Nokia Lumia 1020, headlined above. With ostensibly almost identical specifications to the mass market Lumia 920, it lagged the latter by almost a year. So, when eventually available, the chipset and internals were already nearing end-of-life, in terms of use in new devices. Again, the delay was almost certainly down to getting the camera working satisfactorily - again 41MP, like the 808, but this time doing everything in the main processor and an extra GB of RAM. The 1020 was well received by camera phone enthusiasts, and remains a benchmark device, though its shot to shot times are looking a little prehistoric in a world of 2.5GHz processors and monster GPUs.

Specs and the future

What, then, does the future hold for the Lumia 1020? There's no doubting that it fared better, in terms of sales, than its Xenon-equipped, large-sensored 41MP ancestor, the Nokia 808, but with quite a few new software releases from Nokia/Microsoft explicitly saying that they're only for the Lumia 1520 and 930, worries are starting to creep in for 1020 fans.

Let's look at the hardware across the Nokia's (now Microsoft's) Windows Phone range:

Chipset Devices Specification
Snapdragon S4 Lumia 520, 521, 620, 720 Dual-core 1GHz Krait, Adreno 305, 512MB RAM
Snapdragon S4 Lumia 625 Dual-core 1.2GHz Krait 200, Adreno 305, LTE, 512MB RAM
Snapdragon 400 Lumia 630, 635 (etc) Quad-core 1.2 GHz Cortex-A7, Adreno 305, 512MB RAM
Snapdragon S4 Lumia 820, 920, 925, 928 Dual-core 1.5GHz Krait, Adreno 225, LTE, 1GB RAM
Snapdragon S4 Lumia 1020 Dual-core 1.5GHz Krait, Adreno 225, LTE, 2GB RAM
Snapdragon S4 Lumia 1320 Dual-core 1.7GHz Krait 300, Adreno 305, LTE, 1GB RAM
Snapdragon 800 Lumia 1520, 930 Quad-core 2.2GHz Krait 400, Adreno 330, LTE, 2GB RAM

The Lumia 1020 does stand out a little, amidst its peers, by having the extra Gigabyte of RAM, needed to handle the processing of the (up to) 38MP full resolution bitmaps internally, but the RAM will hopefully come in handy in helping ensure that the 1020 is less likely to be left behind when it comes time to update the Windows Phone platform again.

So far we're seeing no device left behind by Microsoft, thanks in part to Windows Phone's comparatively low hardware requirements - most of the work is in finishing code, adding functions  and fixing issues and compatibility, all without adding much to 'bloat'. As a result, even the lowest Lumia 520 is getting the full Windows Phone 8.1, though some of the higher end camera-related functions are starting to come with some hardware requirements. Historically this has been done according to RAM, though with 2GB on board the Lumia 1020 should be good in this regard for another year or two at least.

Processor and GPU speed are more of an issue, with the latest features in Nokia Camera/Storyteller being limited to just the Lumia 1520 and 930 - at least in theory. 'Living Images' worked pretty well under the original Nokia Camera Betas on the 1020, so maybe these can be worked in again, in an update?

Certainly Nokia seems to have standardised on a 'good enough' 20MP cut down version of the PureView technology. Which is fair enough - and results are good - but it doesn't stop the cameraphone geek in me wanting a third in the 41MP series. Is it just me?

OS updates

What of the core OS though - at what point will Microsoft start lopping off device compatibility? Windows Phone 8.1 Update 1, rumoured to roll out to developers for early testing later this month (July), for eventual release over the air to consumers in November/December, is supposed to be a fairly minor update (by comparison to 8.0 to 8.1) and should also be available for all devices. 

Windows Phone 8.1 Update 2 is scheduled to be available for testing around the end of 2014 and is likely to include new features to support new hardware, and I'd expect much of the lower end of the current Lumia range to get this update but not the full feature set. 

Whatever comes after that is pure conjecture (Google 'Threshold' if you want more on the rumours) and depends very much on Microsoft's ongoing plans to unify its platforms, but it's a fair bet that Windows Phone 8.2 (or Windows Phone 9, or whatever it ends up being called) will be optimised for the Snapdragon 800 and higher. Will the Lumia 1020 be updated for this release? My guess is 'no', but with the extra RAM, who knows? It might go down to the wire and depend on how many 1020-owning enthusiasts there are in early 2015 at Microsoft!

Of course, it's not all about the operating system and there are other ways for a classic smartphone to get sidelined. It happened to the Nokia 808 and it's happening now to the Lumia 1020. First, sales of the device stop - it becomes harder and harder to find one for sale - perhaps to replace a broken or stolen device? And accessories become harder to find - in the 1020's case there's the Qi charging back shell and Camera grip. If you have a 1020 and want either of these, then you've probably already put things off too long. [In the 808's case it was mainly the BV-4D battery, original replacements for this were/are like gold dust.]

Lumia 1020 in Camera Grip

So - the Lumia 1020 stands a chance of being updated for longer than its older sister devices, the 920 and 925 - but only a slender one. Having said that, the 1020 will, by the time WP9/Threshold/whatever hits, be two years old and will have enjoyed updates freely throughout that time, adding significant extra general functionality that certainly wasn't there when customer bought the device.

Classic of tech engineering

The Lumia 1020, like the 808 before it, still has unique selling points (in terms of photo quality, reframing/zooming flexibility and low light shots of people), and it seems that we still have at least another year of updates ahead. So celebrate the 1020 and don't give up on it. 

And don't you dare sell the Lumia 1020. Those who sold on the Nokia 808 PureView have bitterly regretted it - these devices are classic of modern tech engineering.

1020 and 808, all in white!!

Dropbox login changes uncover showstopper QtWebKit bug in Symbian

$
0
0

One by one, service changes across the world do seem to be gradually dropping off Symbian's radar, sadly. Dropbox is the latest, with changes in its OAuth login system that are not only incompatible with Symbian Dropbox clients, they actually trigger a bug in Symbian's QtWebKit module and force the whole smartphone to spontaneously reboot. What's that? You want QtWebKit fixed? ROFL! [editorial coming]

The best summary of the issue is at the Delight blog (the people who do the great firmwares):

You may have noticed that some Symbian apps like cuteBoxDropian or FilesPlus can't login into Dropbox anymore.
I recently read multiple reports about this on Delight Blog, Symbian Forums or via Email. Most of them claimed a bug on Delight side, but that's not true:

Some users tested it on original firmware(s) or other custom firmwares like The One by Daniel or Mohican by Xeon, all have the same issues, the problem can be a:

a) reboot directly without of a usual shutdown (like a system application crash or stack overflow) 
b) like a) but with a reboot loop
c) simple app crash 
d) full freeze of the phone 

If you try to login with your Dropbox account inside of the apps. Thanks to the testers (like Allstar Software, Ade and Adan from Symbian FTW and Matthew from the comments below) for these informations! The mentioned applications are QtQuick based GUI apps which use QtWebKit to show the login page, so the issue must be there.
A reboot can mean a stack overflow, but we don't really know what's the problem without of debugging an own Qt build what's not possible on Symbian. It's not related to JavaScript because it happens even with disabled JavaScript, so it seems to be related to the HTML code.

My guess about this: It seems like it's a QtWebKit bug which was unknown before and recent updates on Dropbox's login page uncoverd it. It affects Symbian Belle Refresh and FP2 and Anna.

ScreenshotScreenshot

Starting any Qt-based Dropbox client (and hey, they all are!) and trying to authenticate presents a blank-ish screen, followed by a device reboot, in the case of my Nokia 808 PureView....

All of which is a major shame, though perhaps such showstoppers were inevitable, given how complex smartphone operating systems are - and with no one left to patch/support the guts of Symbian/Qt, we're rather.... err.... screwed.

Note that you can still log into Dropbox using Web or Opera Mobile (etc) - just as long as Qt isn't involved. So you can still grab that file in an emergency. But you can rule out all Dropbox clients for logging in.

As some people have pointed out, if you'd previously logged in with a client then you may have an authentication token which will work for a while. But not forever.

I'm mulling over a few editorials - watch this space.

C'est la vie - 'Support' expectations for Symbian 'until 2016' unrealistic

$
0
0

Look, I get it, there are plenty of Symbian enthusiasts here - I'm one of them. But every single time something breaks in terms of compatibility with a particular Internet service, we see the same comment from multiple people: "But Nokia promised us support until 2016!" That was indeed what was promised on stage at MWC 2011. But then you have to look at both what the word means and what's happened to the company itself since then. I'm not apologising for Nokia's multiple faux pas and for the current situation in 2014, but let's at least be realistic.

'Support until 2016'

First of all, what does a phone manufacturer mean by 'Support'? I'd venture, as a minimum:

  1. someone to pick up a phone when called, or respond in an online forum, to answer user questions
  2. hardware warranty, and repair facilities after that
  3. patches and fixes for OS and core application bugs and incompatibilities

Number 1 is still in place, at least, via Nokia Discussions, and number 2 is nominally still relevant, with a network of Care Points across the world, though the actual warranties will have run out now for just about every Symbian device, so we're only talking about repair facilities. However, in many cases, if spare parts are needed, they won't actually be available, since they're no longer made. It would be unrealistic to expect any company to keep a massive parts inventory for so many models years after their warranty ran out - but hey, you might still get lucky.

Number 3 is the controversial one, of course. The enthusiast's position is that bits are bits and bytes are bytes, and support was promised until 2016, so why can't this part, at least, be honoured?

Indeed. But honoured by whom? The original (massive) Symbian development teams at Nokia (and then Accenture) have been almost completely disbanded, the company itself officially abandoned all software development for the OS at some point in 2012, the application Store got frozen and the relevant part of Nokia itself was bought up, lock stock and barrel, by Microsoft over the last 12 months. So who exactly do users think is going to code such fixes and patches?

A good example is the recently discovered bug in QtWebKit, whereby changes on an OAuth web login screen were enough in Symbian Qt-based applications to crash the OS completely. It's a low level bug and probably fairly easy to fix - if there was anyone left with access to the code. And build tools. And update servers.

Elop and Ballmer strike an agreement

Symbian's death being signed and sealed. Elop has now moved jobs at least once and is back at Microsoft, where he started, now looking after Microsoft's device's division - otherwise known as er.... what was left of Nokia's handset division after the disastrous 2011/2013 period; Ballmer resigned this year - some point towards the Windows 8 fiasco as the main reason here. An infamous photograph?

When chatting to a Nokia staffer at the Lumia 1020 launch, I asked how morale was internally, what with Symbian being axed (a year before) etc. "Oh", the lady said, "Morale is great, anyone upset about the OS change left ages ago." Which is telling, really. Getting a patch or update out for any part of Symbian OS is now just about impossible, I'd say, there simply aren't any joined up resources left to accomplish such a thing.

Bit by bit, as the online world changes (APIs, OAuth, etc.), the greater the chance that more and more of Symbian's online 'hooks' will break. Some of these are down to the OS and can't be fixed anymore. Some are down to third party applications and may or may not be addressed, depending on the developer and whether they too have abandoned their Symbian developer toolchain/machine.

Status, mid-2014

Of course, all the standalone 'converged' functions that made Sumbian and its hardware great are still there and working as advertised - devices like the N8, 701 and 808 are still great phones - but in 2014 we live in a very different world and the chances are that most things you'll want to do involve the Internet to some degree. Even humble Gmail and Google PIM sync is now a pain unless you pay Nuevasync for the privilege.

In short, 'Support until 2016' was a laudable aim, but is only true in a rather tenuous fashion in 2014. And there's no one to shout at, since Microsoft won't be interested in the slightest. It's like buying a car from one manufacturer and then, two years after another company takes them over, complaining at the latter that the former had promised engine upgrades when you bought the vehicle. "Sorry, nothing to do with us, that was before our time" will come the reply.

What about custom firmware? Despite petitions for Nokia to release Symbian's last known source code, this never happened. Unsurprisingly, since a surprising amount of work is needed to clear 10 million lines of code for public release into a repository. Copyrighted modules, existing licenses, etc. It's a minefield. So CFW builders like the Delight team have to work from binaries, adding to the OS where they can, modding where they can, but ultimately just patching up an OS that's now fallen into disrepair. Still, it means that any Symbian enthusiasts can at least hobble along for the time being.

Update

Applying a post-flash update to Delight CFW on a Nokia 808 Symbian phone....

The future?

Perhaps the best approach for someone in love with their (e.g.) Nokia 808 or N8 is to think of the phone as a converged device circa 2008, i.e. telephony, superb photography, music playback and navigation, but only rudimentary online functions, and to use the Symbian device on conjunction with a small tablet powered by iOS or Android.

That approach has a lot of plus points, spoilt only by the patchy support for getting a tablet online using the Symbian device as a conduit, due to Wi-fi hotspot standards changing in recent years ('ad hoc' rather than 'infrastructure'). So you'd probably need at least a data SIM in the tablet, unless you'd be confident of external wi-fi when needed. There's no one easy answer.

What about moving away from Symbian? At least there's hardware in the mobile world that's roughly as capable and more modern. Samsung's Galaxy K Zoom is arguably a match for the Nokia 808 in a lot of ways and Android's flexibility and expansion mirror Symbian, while Nokia's Lumia 1020 is now dirt cheap (well under £300, SIM-free) and has the same 41MP sensor and oversampling, etc. And both options give you the Xenon flash. There IS life after Symbian, trust me. 

But please don't parrot the 'But Nokia promised us...' line anymore. Yes, you can be cross at Stephen Elop, at Microsoft, at Nokia's board, at Elop's predecessors, and all are to blame for Symbian's fall from grace. But, even if any of these were to hear your cries, there's almost nothing that can be done anymore. 

Sadly. Very sadly.

Delight fully in place!

Skype to stop working 'within a few weeks'

$
0
0

Back in February, I reported that Skype was being withdrawn from the Nokia Store 'for the last time', but that you could still sideload the Skype client and it would work 'for a while'. That 'while' seems to be drawing to a close, with some Skype users receiving the email quoted below. In summary, Skype for Symbian will stop working altogether 'within the next few weeks', however you managed to install it in the first place. Such service stoppages are perhaps expected, given the perilous state of 'Support' for the OS mid 2014.

Here's the email that was received from Skype support:

Skype apps for Symbian are permanently retiring

We've noticed that you are, or previously were, signed into Skype on a Symbian phone, and we're sorry to inform you that we are now permanently retiring all Skype apps for Symbian phones. As a result, within the next few weeks, you'll no longer be able to sign in and use Skype on any Symbian phone.

You can still stay in touch with friends and family using Skype on an Android device, Nokia Lumia phone or desktop computer. You can sign into them all using the same Skype account. The latest versions of Skype for all your devices are available at http://www.skype.com/download.

Hey, at least Skype didn't mention the iPhone!!

Any Symbian applications that access Internet-facing services should continue to expect the worst, of course, with zero support now from companies like Skype. While sad, given the installed base of older Symbian phones, in this case Skype was always a poor relation of the Android/iOS/WP versions, with no video calling support, so it's perhaps not a huge loss.

Still, another nail in the coffin for some people?

Skype in action

Frozen Nokia Store downloads/purchases will be unavailable after the end of 2015?

$
0
0

A couple of weeks ago, the official Nokia Developer Blog announced some changes to its support for Series 40 and Nokia's ill-fated 'X' platform - but the eagle eyed people at Symbian Developers have put two and two together and have drawn a very likely conclusion for Symbian users too....

From the Symbian Developers article:

You might have heard that Nokia X and Nokia Asha basically got killed off by Microsoft recently, or were put in “maintenance mode”, if you want to use the correct term. The plan is to replace these kind of devices with low-cost Windows Phone-devices instead. Sadly, this also means that Nokia Store will get affected. The Nokia Developer Team recently announced that developers can still publish new content for Nokia X and Nokia Asha devices, but that it will come to an end after March 31, 2015.

It was also announced that content in Nokia Store no longer will be available to download after the end of 2015. Although only Nokia X and Nokia Asha was mentioned, Symbian-devices will also get affected, as they all share the same store for apps, games and themes.

Nokia X and Nokia Asha is the reason why Nokia Store kept running for so long, and without them, the store most likely would have closed earlier. It’s sad to know that all content might disappear after 2015, but at least it’s not happening in 2014.

I've said for a while that Symbian enthusiasts should make sure they're as independent as possible from what remains of the old Nokia - using custom firmware, using an alternative application store, using freeware downloads, and more. Of course, there's still some content that is 'locked' in the (frozen) Nokia Store, not least a few commercial applications that were never formally released outside the Store. Maybe some kind geek, in the comments, can explain the procedure for a keen Symbian fan to 'grab'/intercept the SISx file for an application that they have legally purchased?

Before the downloads cease altogether, that is!


Whatsapp For Symbian updated, adds chat archive function

$
0
0

Whatsapp, despite being a pretty core Symbian application for many people, hasn't been (consistently) in the Nokia Store for many months, so the freezing of the latter didn't cause it to skip a beat. For complicated reasons (my SIM keeps switching devices, essentially), I can't really use Whatsapp at all, but I did get notified by Vedhas Patkar about a new version, v2.11.600, detailed below.

Vedhas writes:

I must admit that I was pleasantly surprised when I got a notification regarding a Whatsapp update earlier this week on my phone. This is the second (or maybe the third) update that Whatsapp for Symbian has received after Nokia announced that they won't be accepting any updates for Symbian apps in the Store. 

This new update brings with it the ability to archive chats, along with the usual bug-fixes that accompany every update. I am must admit that I am not aware about the exact changelogs, but who doesn't like an app update? 

ScreenScreen

The new version of the app can be downloaded from the official Whatsapp website, as will future versions, of course.

The supported Symbian UIs/platforms are the usual S60 3rd edition, S60 5th edition and Symbian^3, Anna and Belle.

I wonder which other Symbian applications you consider 'core' to your day to day life that should perhaps be kept updated outside the frozen Nokia Store and which perhaps aren't? Worth you dropping the developer a line and letting them know that a) you're still keen for updates, and b) the likes of AAS is still keen to give them publicity for such efforts?

Facebook image sharing from Symbian Belle FP2 now broken

$
0
0

Internet services, it seems, just can't resist fiddling with their APIs. And clearly something at Facebook's end has been tweaked just a little, since the social image sharing built into Gallery on Symbian Belle FP2 now doesn't work anymore. Symbian Developers does report that all still works for Belle FP1 and before though, 'thanks to Nokia Social' being used instead for the sharing bit. Now when was the last time you saw that phrase in print?(!)

It's true, I tried sharing an image from Gallery on my Nokia 808 and now get a couple of unsightly textual errors:

ScreenshotScreenshot

Thankfully, other means of posting images to Facebook still work, so the API change can't have been that huge. For example, ShareBoard (and, I'm sure, many other Facebook clients?) still works fine:

ScreenshotScreenshot

As with other news stories along these lines, we can (sadly) expect more and more services to gradually become incompatible with Symbian OS and its apps. It's just a question of whether we're talking months or years....

Comments welcome - what do you use to upload images to Facebook these days?

Tough questions: Microsoft, Nokia, Windows Phone, Symbian, Meego and more

$
0
0

As part of a continuing series of features taking a good long look at the state of mobile, and aiming to be as brutally honest as possible, here I use my experience in the mobile industry to tackle the really tough 'what if' questions that have probably been in your brain for the last three or four years, as 'All About' readers. Hopefully my answers will provoke debate in Disqus below, too - why not get involved?

Elop on stage at an evening 'clarification' in 2011 trying to answer the blogosphere's questions

Elop on stage in a follow-on evening event at MWC 2011, explaining in more detail some of Nokia's strategy and answering some of the criticisms of the original keynote statements...

Understandably, a lot of the 'what if?' discussion will revolve around a single date in history, the (infamous?) February 2011 public turnaround of Nokia's Stephen Elop on stage with Microsoft's Steve Ballmer, announcing Windows Phone as the way forward with Meego being cancelled and Symbian being wound down. The other date/news/link you perhaps need is the sale of Nokia's Devices division to Microsoft a couple of years later.

Right, on with the questions. And if you want to have your say, please see below. Also, please note that all opinions below are mine (Steve's) and don't necessarily reflect the views of other current or past contributors to AAS and AAWP.

________________________

What if Nokia had kept on with Symbian and Meego in 2011?

At the start of 2011, Nokia was on something of a roll, actually. The new Symbian^3 range of handsets, the N8, C7, E7 and C6-01 were all selling quite well, having been out for a few months. These were the first Symbian phones (from Nokia) with capacitive touchscreens and the user experience was a lot closer to what buyers were expecting after three or so years of Apple iPhone and then Android handsets. Could Nokia have succeeded by sticking with Symbian for the midrange and using its new next-gen Meego OS for top end devices?

Possibly. There were problems though, which even the most ardent Symbian and Meego fans will acknowledge.

Symbian logo

One of the graphics from days of Symbian's ill-fated move to open source - and then back again, wasting time and man power...

Firstly, Symbian's codebase, massively overhauled from the original non-touch S60 devices over the years and massively delayed by the whole 'take Symbian open source' fiasco, was a right mess. The OS itself was designed back in the days of GPRS and dial-up modems and almost everything had to be retrofitted over the next decade. The iPhone (and iOS) had been improving rapidly from its 'smartest feature phone' opening in 2007, and the hardware and components used in the iPhone and Android worlds were starting to get close to Nokia's prowess.

Competition was fierce and Symbian's legacy architecture was holding it back (plus the above mentioned delays). 2011 was the point, arguably, where Android and iOS started to match Symbian from a technical (OS) point of view. Yes, Symbian development could be continued, but there had already been so many false starts and unproductive blind alleys (Symbian Carla and Donna, anyone?) that the competition was sure to overtake in fairly short order.

Secondly, Nokia's Symbian development teams had become too large (thousands), too complex and fragmented - matching the OS itself, in a way. A fresh start was surely needed. Which brings me to...

Thirdly, Meego, a joint project with Intel, was progressing as a modern cloud-centric, swipe-driven, graphical OS, but was too immature to take on iOS and Android. Having used the Nokia N9 at length, I'd say that it was at least a year behind where it needed to be. [Of course, Windows Phone was no further along, but that had the integral backing of the mighty Microsoft rather than Meego's part time patronage from an ailing Nokia.]

Nokia N9

The radically styled Nokia N9 running Meego - the hardware got re-used for the Lumia 800, the swipe-based interface has been copied time and again by the likes of Blackberry OS 10, Jolla and even sometimes Android.... The N9 was somewhat stillborn and never really promoted. It needed to have been faster and higher resolution and more mature.

Cancelling Meego seemed harsh to fans of the OS, but it was too little, too late in the wider context. Nokia's mistake was not to wind Symbian up - that this had to happen at some point was obvious to all - but in announcing it so dramatically to the world before a successor was ready.

I've said many times privately that if I'd been a writer on Nokia's PR staff back in February 2011, I could have saved the company billions in stock value. All Elop had to say, on stage to the world, was "Windows Phone is the future, with Microsoft, but we're continuing with our new Symbian handsets until Windows Phone is ready".

As it is, there was a massive fall in sales of the fledgling Symbian^3 handsets through 2011, as networks understandably lost confidence in Nokia's commitment to the Symbian^3 handsets and stopped ordering, recommending and selling them. And a corresponding abandonment of Symbian as a viable platform/ecosystem, by developers and service providers, resulting in a situation by 2013 where compatibility with popular Internet-hosted services was already starting to drop away. Yes, we had Symbian Anna and Symbian Belle, but these were little more than UI polish at the end of the day.

Rafe's often said that Elop had to make the point about the switch dramatically and forcibly, in order to convince Microsoft that Nokia was serious about the new platform, but I'm not convinced. Elop was ex-Microsoft and had tight ties into his old company - there was no need to play public politics when his old friend Steve Ballmer was only a handshake away, on stage with him.

In short though, if Nokia had kept on with Symbian and Meego in 2011, it would ultimately have been doomed. The end of Symbian and Meego would have taken place later (maybe up to a couple of years at most), but the end was in sight. It's just the way it all panned out that rankles, both for Symbian/Meego fans and for (as it turned out, in the end) Nokia employees.

Elop and Ballmer

Was Stephen Elop a 'trojan horse' from Microsoft?

Ah yes, talking of Elop, above.... In a sense, of course he was (a trojan horse). Not explicitly, of course, but when Nokia's board hired Elop they knew full well that he was bringing close ties to Microsoft management with him, and the promise of hooking into Microsoft's fledgling new smartphone OS, backed by enormous financial reserves. Elop himself would always have had, in the back of his mind, the knowledge that exciting things were happening back in Redmond, and that if he didn't think Nokia's OSes were cutting it then he might be able to engineer a change. So, when Elop bounded up on stage at the end of Nokia World 2010, I was apprehensive, to say the least, speaking as a writer and editor for a Symbian-centric web site - what on earth was about to happen?

As it turned out, leaving aside the large and arguably unnecessary sales shortfall mentioned above, the change to Windows Phone went relatively quickly and smoothly, the production of the Lumia 800 just over six months later was impressive - even if the hardware did borrow hugely from the Meego-powered Nokia N9.

Has Windows Phone been a sales disaster all round?

Not really, I'd argue that it's a newer OS (2010) than iOS (2007) and Android (2008) and hasn't yet reached the peak of its potential (though with the availability of Windows Phone 8.1 and Lumia Cyan it just got a lot closer - we're now approaching the 'put up or shut up' phase for the OS). Moreover the smartphone market has been growing massively, largely on the strength of cheap Android handsets, the vast majority of which have little merit as works of engineering. Despite past examples like VHS vs Betamax video, quality should win out in the end, which is partly why Apple's iPhone sales have remained relatively stable despite the cheap Android onslaught.

Windows Phones have been selling at just less than 10 million per quarter, worldwide, but I fully expect this figure to be 15 million in Q3 and more in Q4, 2014. I know I'm biased, writing for AAWP, but in terms of numbers, the best of Windows Phone is still to come.

Would Microsoft have made such good progress with Windows Phone without Nokia's input?

No. Microsoft is large and slow - this has always been its way in other areas. Witness the slow growth and stagnation of Windows Mobile pre-2007. Windows Phone was a complete rewrite and had promise, but it took Nokia's hardware engineering prowess to create products based on Microsoft's OS that people actually wanted to buy. Through design, build quality, top components (screens, cameras, speakers).

In addition, Nokia's engineers (all used to what Symbian and Meego were capable of) had been pushing Microsoft very hard to try and get the rudiments of Windows Phone up to the level where they could say, hand on heart, that the new Lumias were an improvement on what had gone before. I firmly believe that Nokia's involvement with Windows Phone accelerated the OS to the point where it's now seen as 'a little late but catching up', as opposed to 'so late to the the smartphone party that it's irrelevant'. Niceties like Nokia Glance screen, all the imaging innovations and processing (seen in the existence of the Lumia 1020 below and its PureView successors), the HERE sat-nav suite, plus a lot more under the hood, have meant that Windows Phone is at least on the same lap as its competitors and, arguably, about to start catching up, in terms of sales and general ecosystem.

Lumia 1020 camera

What if Nokia had adopted Android as the way forward in 2011?

This question has been debated a lot over the last few years - somewhat fruitlessly, but it's still worth a mention here. On the positive side, it would have been quicker to develop Android handsets, since the OS was more mature, Android would have appealed more to Symbian users since there are a lot of similarities in terms of flexibility and multitasking, and - of course - Android was something of a sure success story. It's always good to back a winning horse.

On the negative side, Nokia was worried about Samsung and Chinese manufacturers swooping in to steal its lunch in the low and mid-range*. Would Nokia have stood out? I'm sure sales in the short term (2011-2015) would have been better, but as a decade-long strategy it seemed flawed. Elop's leaning was naturally towards his alma mater and the idea was that Windows Phone could be a long term (2015-2020) success story, tied into (the then upcoming) Windows 8 and Windows 9, into tablet ambitions and Xbox in the living room. Microsoft, it seemed, had the vision, the money to back it up, and Elop had all the right contacts to make the transition - and, eventually - the sale work. 

* We're only now just starting to see cheap Far East Windows Phones appear, by the way...

_______________________

The above notwithstanding, I do have a number of personal sadnesses - I'd have loved to have seen Nokia pour another year's worth of OS development behind Symbian to produce an 808 successor, with larger (4.5") and higher resolution qHD screen. I'd have loved to have seen what high end Nokia hardware running Android 4.x would look like. I'd have loved to have seen where Meego could have gone (again, larger screen, more horsepower).

Then there are the sadnesses of the Nokia layoffs and the sale of (most of) a once proud Finnish company. We're in a new era though, where everything happens at breakneck speed, yesterday's tech is old hat and sales of smartphones are measured in the billions. It's OK to look back and analyse (as here) with hindsight, but it's also time to look ahead - and as far as possible. 

Watch this space.

Smartphones and Beyond - 800 pages of core reading and a saga of an entire industry

$
0
0

Trailed here at the start of the year, David Wood's huge 800 page book on the rise and fall of Symbian and the transition of its licensees to other platforms, against a background of massive change in the smartphone industry, has now been published, in electronic form. I've only skimmed through it so far, it'll take weeks to get through properly, but there's such detail that everyone will find plenty of interest. Symbian old-timers and enthusiasts, especially those with a development background, will gobble up the mass of detail about how the OS got started and how it evolved. While newcomers will pounce on the last part of the book and the background and reaction to February 11th 2011 (and Nokia's adoption of Windows Phone). 

Book coverFrom my earlier trailer:

David Wood is something of a legend in the Symbian world, having been one of the architects of Symbian's predecessors, Psion's SIBO and then EPOC/32 operating systems, and then being intimately involved with the OS throughout the 2000s. If anyone was going to 'write the book' on Symbian then David's the man. 

...Peppered with quotes, press release extracts, internal meeting slides, and so on, 'Smartphones and Beyond' isn't a light read, but for anyone who's genuinely interested in what went right and what went wrong inside this industry, David's book is well worth looking out for...

The book is now out in electronic form, at least, for the Kindle, here on the UK site and International (US) site

Some extracts, to get you hooked:

On the subject of first getting going with Nokia and launching Symbian:

My first visit to Finland to meet Nokia coincided with a period of particularly cold weather. It was the evening of Monday 27th January, 1997. Along with Juha Christensen and Mark Gretton, I flew to Helsinki, where Juha had a hired car waiting for a two hour drive north to Tampere. Juha and Mark had suffered an uncomfortable flight from Helsinki to Tampere a few weeks earlier, on account of buffeting from turbulent weather, and preferred on this occasion to drive. When we finally arrived in Tampere, it was well after midnight. As we briefly walked outside, my face burned with the bitter frost of the night-time air. The temperature shock was a visceral reminder that I was in a very different environment from the one I had experienced in my nine previous years in software development at Psion.

During the car journey, Juha’s mobile phone had rung. It was a call from one of his industry acquaintances. The caller asked Juha, knowingly, “So, what are you doing in Finland? I wonder who you’re meeting there, eh?” Apparently he had called Juha earlier, and he had received a message from the network telling him the call could not be completed. The network message had made it clear that it was a Finnish mobile network. Woops.

This question caused us some consternation. Our trip to Finland was meant to be ultra-secret. I even wrote into my Psion Agenda, “Trip to Egypt”, making a play on the fact that we used the word “Nile” as the codename for Nokia. No one should know that we were talking to Nokia.

Things were very different, seventeen months later, on 24th June 1998. On that day, Pekka Ala-Pietilä, President of Nokia Mobile Phones, stood on a stage in central London alongside David Potter and Colly Myers of Psion, to convey Nokia’s public support for Psion’s EPOC software. 

On the subject of reaction to Apple's iPhone in 2007:

What was less obvious, however, was that Apple was capable of learning a great deal from its experience with Rokr. It’s a mistake to conclude, just because a company has failed to achieve its market targets with v1 of a project, that it will inevitably fail in the same way with v2 and later releases. After all, Symbian had walked the same path: initial releases of Symbian OS were late and had reduced functionality, but the company put in place learnings from these experiences, and eventually built a very powerful software creation engine. In the same way, Apple converted its disappointments with Rokr into insight that helped it make such a success with the iPhone.

Second, the Symbian world underestimated the extent to which:

  • Third party telephony modules were now available, that could be integrated reasonably straightforwardly into new smartphones
  • Users would accept second-rate telephony experience (with e.g. a greater proportion of dropped calls, or poorer quality voice audio), on account of better experience with other aspects of the device
  • Voice calls had diminishing significance, overall, compared with the greater significance for users of messaging, video, and browsing
  • Consumers would adopt the unexpected usage model of carrying both a smartphone and a “dumb phone”, with the latter (often a lower spec Nokia phone) being used for voice calls.

Further, Symbian was wrong to group Apple together with companies like Dell and Acer that were primarily manufacturers of computers; Apple was not only a manufacturer, but also the creator of a rich operating system (Mac OS). Critically, Apple had the ability to create a version of their desktop software (Mac OS) which could be used in smartphones (iOS).

[There's more, including a dramatic comparative encounter with one of Symbian's founders now fallen in love with the iPhone and its specced up Safari web browser.]

On the subject of February 11th and the Nokia strategy change:

Nokia’s announcements of February 11th, 2011, were the subject of avid attention within a group of Accenture Mobility personnel. A small number of us, including several ex-Symbian employees, had gathered for the day in Accenture’s Cambridge office on the Business Park, off Milton Road, to watch a live webcast of the announcements.

We did not yet know it, but the date of “February 11th” would come to be regarded as the blackest day in the history of Symbian – analogous (though in a much smaller setting) to the pivotal transformation in American public consciousness inflicted by the dreadful horrors of aircraft terrorism on September 11th, 2001.

However, Nokia boldly believed they could duck this dismal tide of failed relationships. They had a much closer hotline into Microsoft. And, it seemed, they had the special benefits of a new mobile platform from Microsoft – one which had learned from all its Redmond precursors.

However, even a cursory examination reveals a set of important ways in which Windows Phone 7 was uncompetitive as compared to Symbian, for deployment in mainstream smartphones:

  • There was limited support for languages such as Chinese
  • Options for “operator customisation” were few and far between
  • Hardware requirements were higher, implying more expensive devices.

If MeeGo was “not ready for prime-time use”, nor was Windows Phone. If Symbian needed lots of repair work, so did Windows Phone. Nokia’s judgement was that the required enhancements would come quickly enough to Windows Phone. That judgement turned out to be naïve. Not for the first –or last – time, a company underestimated the amount of effort required to improve a major smartphone platform.

Terrific stuff.

And yes, I'm quoted a few times in the text. Ahem. David, your cheque is in the post....(!)

You can buy Smartphones and Beyond here at Amazon. There's also David's mini-site about the book here, with extra extracts and full table of contents.

PS. The also prolific Andrew Orlowski has penned a lengthy review of the above book - also good reading, if only as an overview!

The Nokia 808 PureView meets... the 2014 Sony Xperia Z3

$
0
0

Reader Martin Roth has put up a neat little video showing what happened when his 2012 Nokia 808 PureView met the new Sony Xperia Z3 at IFA 2014.... Suffice it to say that Sony's made improvements - but the Z3's camera is still some way off matching the 808. See below....

Nicely done, and fair, too. You can see more of Martin's 808 work here, by the way.

Viewing all 1165 articles
Browse latest View live