admin

Not a day goes by without some kind of rumor about the iPhone 4S/5, or what Nokia’s WM7 phones will be like, or some shots or videos of the new BlackBerry Bold 9900. Most of the time the manufactures themselves don’t create the buzz but the fact that these devices are on everyone’s lips is good advertising, it is good business. It creates a brand awareness and makes people hold off buying phones because they are waiting for that phone. All companies know that and act accordingly.

But not HP, they know better. According to HP the best thing to do is to fly under the radar of the media and public, to pass as unnoticed as possible. The last thing HP want to do is create excitement about their products. Because how can you otherwise explain the fact that even though the Pre 3 is slated for a July release we are not hearing anything about it, no images, no press release, no leaked devices, no nothing. If you go to PreCentral you will instead be able to read about Verizon’s pricing plans (wohoo!). I know, I had to take a few deep breaths myself just to calm down a little from the excitement.

It is not as if HP have several high selling devices that they do not want to stifle by leaking the Pre 3 (no, the HP Veer absolutely does not count!). On the contrary: given the launch of the TouchPad any day now the Pre 3 would the perfect combo to promote.

It is really sad how first Palm and now HP continuously manage to screw up with WebOS and all its potential.

At this point I don’t think anyone have not heard about the N9 that was presented by Nokia a couple of days ago. As expected, the excitement that was present at the N900′s presentation is still, if not more, very much alive and the general response has been thoroughly positive. In fact I think most people were surprised by the quality of MeeGo at this point after having read that article that contained the infamous “Oh shit”-moment and many are now asking themselves what that moment was all about. The overall impression after that article was that MeeGo is in an Alpha-stage, at best, but after having seen the N9 presentation many are genuinely perplexed about Elop’s decision to not pursue MeeGo more decisively.

But Nokia will of course eventually publish the number of N9/MeeGo units sold in a given quarter, so that begs the question, what will Nokia do if the new N9 sells by the millions? I.e. if the N9 sells well even without an ‘ecosystem’ what will that say about Elop’s decision to pursue WP7 instead of MeeGo and what would that mean for his argument that everything is about ecosystems these days? Obviously at this point it is all speculation, but if the reaction of the public is anything to go by then Nokia might very well be in for a surprise.

Now what constitutes good sales is obviously relative. If you compare it to Symbian volumes then the number will probably be “low”. But if, in absolute terms, the N9 sells better than, say, HP’s WebOS devices, what with all their ‘ecosystem’, then you really would not be able to talk about a MeeGo failure. Will that then be enough shift Nokia’s attention to MeeGo or will they continue to relegate it to that seemingly eternal beta status?

If the sales of the N9 closely correlates with the public’s reception of the device then I genuinely hope that Nokia will give MeeGo the time, attention, resources and money that the platform deserves. If not, then I might actually begin to believe all those conspiracy theories about MS and Stephen Elop in regards to Nokia….

UPDATE:
I just read Engadget’s editorial, stating exactly the same thing. I hadn’t come around to reading my RSS feeds before posting my own opinion only 3 hours earlier.

But, in the meantime, I also came across this news article from Finland, which claims that Elop is set on killing off MeeGo; if true then it is truly staggering and I think it raises several legitimate questions regarding Elop’s WP7 decision.

There is absolutely no doubt that the Samsung Galaxy S2 is the best phone on the planet right now. It really is as complete as you can expect from any phone currently. Sure, you could perhaps add a better camera to compete directly with the Nokia N8, and a notification LED is a something I always want in a phone. But in the grand scheme of things that is nitpicking, really.

The fact is that the Galaxy will still be one of the best phones in the market six months from now, if not the best. I would even argue that in a year from now it will still be a very competitive phone, hardware wise, and will be able to perfectly run anything you throw at it – the dual core processor and 1 GB of RAM will make sure of that.

But the important thing about the Galaxy, and what the other manufacturers should take note of, is that when you create a phone with the right hardware, when you don’t pull any stops, people will flock around that device. It will be talked about, it will get press, it will get attention regardless of the platform it is running on (whoever said that it is all about the software?); so the next time you manufacturers want to create the new iPhone killer, have a look at the Galaxy S2 and let it inspire your hardware decisions.

I haven’t heard the term ‘ecosystem’ as many times in my whole life as I have since Elop’s announcement on February 11. All of sudden it is all about the ‘ecosystem’, everyone is attributing everything to the ‘ecosystem’ – even when your phone stops working because it got crushed by a bus it apparently has something to do with the ‘ecosystem’ these days.

But you know what? I could not care less about an ‘ecosystem’. Honestly I don’t. And I am getting bored hearing about it everywhere, even more so because everyone seem to take at face value that an ecosystem is the way to go in the future. I have argued before that the concept of an ecosystem doesn’t exists on your PC, so why do I need it on my phone? I don’t need it on my PC, and I don’t want nor need it on my smartphone/mobile computer; the more tied you are an ecosystem the less flexibility and freedom you have to use your phone the way you want to, and if you do not agree with that then just have a look at this – that is a direct consequence of your beloved ‘ecosystem’. And you can be sure that we will see more of that if everyone, manufacturers and consumers alike, is set on jumping on the ‘ecosystem’ bandwagon. (And no, an appstore is not an ‘ecosystem’, appstores existed long before the iPhone no matter how hard Steve Jobs is trying to sell you that they were first, eg. google ‘Handango’ and ‘Palmgear’, both existed years before Apple’s appstore).

I am certain that the future will be about openness, so that you can connect to any cloud that you wish, and the lock-ins that we are see now will seem antiquated. It will about open services and open APIs, and those manufacturers who chose to continue the current path of lock-ins will disappear or be marginalized.

So instead of an ‘ecosystem’ what I want instead is a true mobile computer. I want the full experience in my pocket, with no compromises. I want to be able to carry around my phone and use it just as I would use a laptop. I want access to the whole web, be able to download any file or media and then consume it directly on my phone or my TV, no matter what kind of media it might be.

So who will be the first to throw ‘ecosystem’ in the bin where it belongs and instead focus on what we should be striving for: true mobile computers with complete freedom and unrestricted access to everything in the cloud? That is why I have such high hopes for MeeGo, as I would like to see it as being the stepping stone to something greater and better beyond where everyone are rushing right now.

And if not MeeGo, there is always Canonical of course….

No, it has nothing to do with the old ‘M$’. It has nothing to do with open source vs. commercial software either. My hope does not even have anything to do with my “disinterest” in WP7 right now.

The reason really is much more simple, and pragmatic, than that: whenever Microsoft has been the leader in any market they have all but stopped to innovate. Just to give a couple of examples, look no further than what happened after Microsoft came out victorious from the browser war between Internet Explorer and Netscape. They virtually stopped developing their browser and it was not until Firefox and later Chrome began to gain popularity that Microsoft finally put some effort into improving their browser again. And then of course there is the example of Windows Mobile: after Palm committed suicide by refusing to improve their hardware and software in their devices Microsoft had a window (no pun intended) of opportunity of 2-3 years to get a stronghold of the smartphone market. But instead, seemingly true to their modus operandi, they simply seemed happy that their largest competitor was out of the game and basically put their mobile OS in the drawer to collect dust. And look just how long it took Microsoft to react after that – even Steve Ballmer admitted they were late to the party.

Now I’m not saying that the other players would be any better if any of them became market leaders (just look at Nokia how complacent they became!). On the contrary, if I had to make a bet I would say that they would likely behave in the same way. But that is a supposition – with Microsoft it is a fact. They have proved that on more than one occasion.

Having said that, I really don’t expect either Microsoft nor any of the other players to become so dominant in the smartphone space that they can afford to just sit back and relax. But if one of them were to become the leader then, again, I sincerely hope that it will be Microsoft’s lot to be the chaser.

If you have read the smartphone news the last couple of days you will likely have come across various discussions regarding RIM’s dire situation in the smartphone arena. But when you follow a market long enough you begin to see patterns and trends, and I have already in two occasions seen the fall of two large, even dominant companies that you simply did not think could happen before it was a fact.

The pattern goes something like this:

1) The company is not keeping up with the latest trends, in software and/or hardware.

2) The company denies that there is any trouble and instead simply talks about how great they are doing and that they still have a large market share and are an important player.

3) The company is slipping financially, both in shares and sales.

Both Palm and Nokia fit this pattern. Palm stubbornly refused to come out with better hardware while, on top of that, they were trying to dictate what the users wanted, for example when their CEO stated that Palm’s users did not want to listen to music on their devices, they simply wanted a simple organizer. Add to that an outdated platform, Palm OS, and you can easily see how Palm’s demise was inevitable. And Nokia of course followed a similar pattern, though the big difference is that Nokia never restricted the features they offered in their phones (on the contrary), it was rather a question of implementation and execution, though the ideas were right.

So how is RIM doing if we compare it to that pattern? 2) and 3) certainly fits. And to some extent 1) could also be applied: up until now they have certainly trailed behind the rest, but their upcoming devices are not bad by any means hardware wise and are certainly competitive in today’s market, so they seem to be aware of that they need to come out with more competitive hardware. But I also think that the one thing that they have in their favor is that they know that they need a new and modern platform, hence their purchase of QNX. And as we know they are hard at work adapting QNX for their phones; without a doubt they would have benefited greatly if QNX was running on their BlackBerries already but I get the impression that they are very aware of that and are doing everything they possibly can to get it out as soon as possible (the Playbook, though incomplete feature wise, was developed and launched in an impressively short time). And that sense of urgency was something that I never saw in either Palm or Nokia.

So, in conclusion, I think RIM still has a good chance to remain one of the dominant players in mobile computing if they manage to get QNX on their smartphones relatively quickly, say H1 2012. At the same time, I would not be surprised if they offer their new QNX-based phones without the BIS/BES lock in; remember, you read it here first….

I had the last Pre, the Palm Pre 2, for only a week before I sold it. There were mainly two reasons for selling it.

First, it was the poor phone signal: when it lost the signal, for example while on the subway, it would take several minutes for the phone to grab the signal again which was very annoying as you could not take advantage of the brief moments when you did have a signal to text someone or to rapidly load up the web page.

The second issue, and this was a disappointment after having read opinions about the previous Pre-devices, was the battery life. All Pre-devices so far have been kind of notorious for having a rather poor battery life, and given this I was counting on that they had made rather drastic improvement in this area over previous phones. And based on all accounts (the Pre 2 was the first Pre I had owned) the Pre 2 did in fact have a longer battery life, but I expected more. If I pampered the phone it would barely last me a day, but if I used it more seriously I would not even get to late afternoon.

I have looked at the Pre 3′s specs and it seems that HP only gave it a very small boost in battery capacity compared to the Pre 2, going from 1150 mAh to 1240 mAh . Given the larger display, larger resolution and faster CPU on the Pre 3 I expect its battery life to be, at best, the same as on the Pre 2, which really wasn’t good enough. Unless, of course, they have made some serious optimizations in the OS, though I would not count on that.

So for all you prospective Pre 3 buyers out there: consider buying an extended battery for your Pre 3. Believe me, you will need it!

I remember when the N900 was released in late 2009. The blog sphere was abuzz and everyone was genuinely excited about this brand-new platform. The videos and published images were so cool. It had beautiful graphics and the multitasking was amazing, both as far as performance was concerned (i.e. the number of apps that you could run simultaneously) and the UI. Everyone wanted one even if it was being pitched primarily as a developer device. In fact, it seemed as if Nokia was taken by surprise by the interest that people were showing in their new device and platform, and as a result they repeatedly tried to downplay its relevance as a smartphone for the masses. I even recall one article saying so explicitly, that when they asked the Nokia sales rep about the N900 that it was quite odd and frustrating to see how the Nokia rep was trying to “cool down” the excitement of the article writer.

It was thus very clear that the N900 was not aimed at the masses, and as such that Nokia wasn’t prepared to completely back the phone up. It was as if they knew that the platform was not quite feature complete yet and as such would not be suited for everyone. Maybe it was because Nokia simply did not have the team in place that could fill the gaps in the platform and therefore did not want it to take off in a big way. I don’t know. But the fact is I have yet to read a single post by people who have owned the N900 that have not said that the N900 was a great device and that it is a shame and big mystery why Nokia did not put more effort into the trying to evolve the platform. Many of them still use it and I have read numerous times that the N900′s browser was the best mobile browser ever made so far. The opinions on the N900 make me regret that I didn’t pick one up when it was launched, even though I knew that certain features were missing.

I think everyone agrees that it could have been the next major mobile platform, that disruptive technology that Elop keeps referring to. So, given the rumors that Nokia will launch a MeeGo device on Tuesday the 21st, what can and should Nokia learn from the N900? It is very simple, really: if you see that people are genuinely excited about the it, if it receives a lot of press, if you see that it creates an group of devoted fans just like the N900 did, then back your phone and your device 110%! Don’t hold back, put any and all resources you have into the platform. Run with it as far as you can. And if it means that you have to steer away some resources from the Windows Phone 7 development, then do so, because at this point WP7 is just a plan, a wishful thinking, while the N9 is real and is here and is creating the buzz and the attention that you desperately need! Don’t downplay MeeGo only because you have bet all your chips on WP7 at this point. OK?

But to be honest, at this point my real and only wish is that, come Tuesday, that N9/MeeGo rumor turns out to be more than just a rumor!

Phandroid made an interesting affirmation yesterday, saying that iPhone users don’t really talk about smartphones with one another.

Not only do I agree with that, but I would even go further and say that vast majority of iPhone users are not interested in smartphones, let alone what the competition does. And as I have stated before I think that stems from the fact that the iPhone caught traction with the public when it was still a dumbphone, and thus most of its users were in reality dumbphone users. I have only met ONE single iPhone user who was supposedly interested in what is going on with the other platforms but you couldn’t expect much of any kind of decent and objective discussion with him, which wasn’t surprising given the statements from him of the kind “I love you Steve Jobs!” (yes, those were his exact words).

Whenever I try to engage in a conversation with “fellow” iPhone users about smartphones I am always met with either a sheepish expression (i.e. “I have no idea what you are talking about”) or simply disinterest. I sometimes even feel embarrassed when I use my iPhone in public as I don’t want to be labeled as that clueless, “just-another-iPhone-clone”, “follow-the-crowd” individual.

In contrast, my most interesting discussions have invariably been with Android users; so yes, I absolutely agree that Android users are much more prone to strike up conversation about smartphones and OSs then iPhone users. (But to fair, WebOS users have in even more in common, but that is simply because they are as rare as the Dodo….).

Continuing with my series on what I dislike the most with each OS or platform (see this and this), the turn has come to WebOS.

WebOS is a little different though in that there isn’t any single or major showstopper, which is a testament to how good the OS is. Sure there are some features that are poor such as the few supported video formats, and then you have that ‘Oreo-effect‘ in the slider mechanism, but these things are not features per se and can be fixed. The point of these “gripe-posts” is to get at more fundamental issues/features in each platform.

So what is my issue with WebOS then?

Answer: it is the card view when you switch between the running apps; though neat and pretty, I find it a chore to swipe several times to get from one end of the card view to the other. The new stacks feature in WebOS 2.0 is supposed to mitigate that somewhat, but it is rather clumsy to handle and it takes a long time to stack cards that are not right next to each other (and yes, I know that you can zoom out to see more cards, but that involves an extra step and still is not enough). I think that the “single” card view is poor usability and would like to see at least the option to view the running apps in a grid (think multitasking in Bada or Maemo), e.g. a 2×2, 2×3 or ideally 3×3 grid. And as the Nokia N900 proved each icon can be live just as in WebOS. But even if they aren’t I would still prefer a grid/row of static app icons (think Android) than the card view. In other words, I even prefer the iPhone’s row of 4 scrollable icons over the single card view.

The card view has of course been copied by RIM’s QNX and it will also be used in the Windows Phone 7 Mango update, and I really don’t think that is an attractive feature, which it why it was disappointing to see it implemented in exactly the same fashion on HP’s new TouchPad: with that screen you could easily have done something along the lines of Maemo/Nokia N900. And note that I complained about a similar thing in Symbian^3, but I would even rather have kinetic scrolling as well, even if I overshoot sometimes, than WebOS’s cards.

So my request to HP is: please add at least the option to be able to view the running apps in a grid view, even if that grid would not be live.

1) What was your planned strategy for Nokia while you were expecting to be elected the new CEO?
2) What is your opinion regarding Elop’s decision and strategy to go with Windows Phone 7?
3) If you were to replace Elop as CEO as of tomorrow, what would you do going forward given everything that has been done and happened so far?

I can’t but envy the person who has the opportunity to chat with Anssi by the water cooler every day….

I wrote in another post that I think/hope that the new buzzword ‘ecosystem’ is a just fad that will eventually be replaced by largely platform-independent services and an open OS.

I am aware of that there is little economical incentive for the current big players to go down that path (with Google possibly being the least one to resist as long as it generates traffic for them), something that was also mentioned in the comments of that post. So I have was thinking about it when I came across this article at The Register about Canonical. Since I use Ubuntu it should immediately have occurred to me that Canonical is one of the obvious candidates for coming up with that open solution I am hoping for: if I am not tied to or need nor want any ‘ecosystem’ on my desktop then why would I want it on my smartphone/mobile computer?

In the meanwhile I am crossing my fingers for that rumored MeeGo announcement on June 21!

OK, just for the record: I am completely and utterly unimpressed by Windows Phone 7, and that is putting it gently. I would be hard pressed to even classify it as a smartphone right now, what with the lack of multitasking.

I stated this before on some other site but I will repeat it here again: I would never, with a clean conscience, recommend a WP7 phone in its current incarnation to anyone I know. And I have tried it enough to know. I think that the live tiles are plain boring and very limited compared to widgets, and the Metro UI is appalling – it looks as if the design team came to a complete stop in the middle of the wireframe stage of the design process (wiki).

One of the sacred UI rules on a small screen is to take maximum advantage of the limited screen by displaying the maximum amount of useful information, but instead WP7 have these huge headers in most apps, with a font size that seems to be targeted at the visually impaired. But apparently the Windows Phone 7 team thought that was more important than always displaying the top status bar. How is that good usability?

And while I am at it: I have all but stopped reading comments on WP7 sites as the posters (=WP7 users) sound like they are in a state of as much denial and defensive regarding their platform as your typical iPhone user was, circa 2007, and I have little patience for that.

And for those who have not had the chance to make up their own minds yet, and if you actually are still in doubt about Windows Phone 7, have look at this and this video review of a couple of HTC phones.

Will I be able to look past Metro UI once Mango arrives? That remains to be seen.

Sometimes it is good to keep a perspective on how far we have come technology wise in just a few years. Thus, I thought it would be interesting to pitch the best phone currently in existence, the Samsung Galaxy S2, against one of the best and most desirable devices back in 2000, the Palm Pilot Vx, the king of the hill back then, and my first PDA and which ignited my passion for PDAs (which later of course would morph into the smartphones we all know and love).

So let’s rumble!

Samsung Galaxy S2 Palm Pilot Vx
Display Super AMOLED Plus capacitive touchscreen
4.3″
480 x 800 pixels
16M colors
LCD resistive touchscreen

3.2″
160 x 160 pixels
monochrome, 16-grayscale
CPU 1.2 Ghz Dual-core Exynos 20 Mhz Motorola Dragonball
I later overlocked mine to a whopping 28 Mhz!
RAM 1 GB 256 Kb (in the form of heap space where the actual programs ran; RAM memory referred to the storage capacity back then, i.e. what the ROM is today)
ROM 16/32 GB (expandable up to 32 GB) 8 MB
Phone Yes In my wet dreams!
Wifi Wi-Fi 802.11 a/b/g/n Huh?
Bluetooth v. 3.0 Bluewho??
GPS Yes Yeah right pal! Maybe in 2020 if we’re lucky!
Infrared No Yes
Camera 8MP + HD-video recording Why would I want to always carry a camera with me!?
Music playback Yes No
Though there was a hack that allowed you to transfer a mp3 file; I say “a” because with only 8 MB of storage, shared between apps and data…. you do the math! And then of course there was that piezo speaker and no headphone connector.
Oh, and does this count?
Video playback Yes Watching videos on a 160×160 pixel grayscale screen and a 20 Mhz CPU!??
Stop it, you’re killing me!
Browser Yes, including full Flash 10.3 support The closest thing was AvantGo.
I felt so vanguard reading news on my PDA during my daily commute!
Apps Yes Yes
I spent hours and hours playing Bejeweled!
Weight 116 g 114 g
Battery life 1,5 days 3-4 weeks!



To be fair, the comparison would have been slightly different if I would have compared the Samsung to a Psion Revo (which back then I looked long and hard at for a couple of weeks, before finally deciding on the Palm Vx mainly because of the size difference). And then of course there was Microsoft’s Palm PC and the Nokia Communicator.

But the Palm Vx was the sexiest of them all even though it was less capable in many was, but the things it did it did them very well (does that sound familiar??).

And if you wonder what happened to my Palm Vx, as I said above I overclocked it using some hack, and it was hot! And I mean that in a literal sense as well as it would heat up noticeably, but after a couple of months it died on me – the CPU had burned out. But I still keep around here, somewhere….

On my old site I wrote about my biggest gripe with Symbian, but my beef with BlackBerry has, no matter how odd it might seem given the bashing RIM’s OS is getting lately, nothing to do with the OS.

I also posed the question of the point of BlackBerry beyond push email, and that is related to my biggest issue with BlackBerry. I am talking about RIM’s BIS/BES server (for an excellent explanation of the two servers, read this); the idea of adding a whole other service layer on top of the operator is completely puts me off, and when you take into account the consequences of RIM’s extra layer it immediately becomes a non-option. We have all seen what happens when those servers are down: it means not only no e-mail but none of features you would expect on a smartphone, i.e. you BlackBerry turns into a dumb-phone which will only allow you to make phone calls and send texts. Another result of going through BIS/BES is that the download speeds depend on the server (as opposed to your network) and email attachments have a maximum size limit, which is again limited by the server.

It is a real shame because as an OS I actually like it (sans the infamous battery pulls) and the new Webkit browser is actually very good, with pinch-to-zoom text reflow! Add to that that I am a sucker for front-facing QWERTY keyboards – the upcoming Bold 9900 would be the ideal phone for me as far as design is concerned! – but alas….

Nokia has said that they will have some kind of VIP relationship with Microsoft, and as a result be able to tweak the OS and add their own exclusive features to the platform. That whole argument strikes me as odd for a couple of reasons.

1) Nokia looked for an OS outside the company in part because they supposedly wanted to be able to leave the OS development to someone else so that they could focus on other things they do better, such as hardware; unless adding Nokia’s own “flavor” to WP7 means simple tweaks like some exclusive live tiles or some skinning, it seems as if doing major changes/improvements to the platform (such as adding USB mass storage capability) would require much more of an effort on Nokia’s part and thus contradicting their stated goal.

Now it is fair to argue that adding a certain feature will probably take a significantly less effort than developing a complete OS, so there is nothing odd with that (if Nokia’s tweaks in fact will go that deep into WP7).

2) But assuming that Nokia actually will be allowed add significant, deep level features to the OS that they will not need to share with the other WP7 manufacturers, what is more difficult to grasp is why those other manufacturers (e.g. Samsung, HTC, LG) would want to continue to produce WP7 phones at all given that they would be in a permanent and default disadvantage against Nokia; for them it would be like being in an abusive relationship. I do not see any reason, no incentive, for them to license and manufacture WP7 phones under those conditions. For anyone wanting to buy a WP7 phone, and for the sellers, it would be a no-brainer: Nokia would be the brand to buy and recommend just for those added and exclusive features.

So again, why would the rest of the WP7 manufacturers bother at all with WP7 under that scenario? Obviously they wouldn’t.

And that could explain why both Microsoft and Nokia keep repeating that the other manufacturers are important in the WP ‘ecosystem’, i.e. it could be a false reassurance so that they stay in the game until Nokia starts producing their phones so that WP7 sales don’t stall completely in the meantime. It could also explain HTC’s recent announcement to wind down their WP7 efforts.

One of the first things (the second, to be precise) I look for in the specs of smartphone when I want to decide on the best performing device is RAM memory, both total and ideally how much is available to the user after a soft reset.

Having enough RAM is the difference between a pleasurable user experience and an exercise in frustration: I would much rather have a phone with a little slower CPU than a RAM-starved device (and I know that from my personal experience). Given this fact alone, and when you take into account the RAM specs for the Galaxy S2 and the Sensation, 1GB vs. 768MB respectively, the decision is obvious, even more so given some reports that Sense 3.0 on the Sensation uses up half the RAM on the phone! Yet most people only look at the CPU when they compare two phones for performance, seemingly unaware of the significant slowdowns that occur when the OS has to start closing down apps in the background and then run the garbage collector due to lack of RAM memory.

So in the case of the Galaxy S2 and the Sensation, comparing CPUs is virtually pointless as far as day-to-day performance and usage is concerned. Any bottlenecks will much sooner be a result the amount of RAM available. And with the Galaxy’s RAM you can also be much more certain that your phone will be able to run future versions of Android, as it invariably grows and requires more demanding hardware (look no further than the HTC Desire and Gingerbread-update debacle, where HTC claimed that the Desire does not have the required hardware to run Gingerbread well).

Add to that the superior battery life on the Galaxy S2 and there is nothing to think about, really. And no, not even the Sensation’s qHD display nor HTC’s Watch video streaming service can make up for this.

In all, the Galaxy S2 is almost the perfect phone right now as far as the hardware goes (the only thing I would *desperately* add is a notification light!), and the other manufacturers should learn from that.



UPDATE:
I had heard about the so-called “death grip” on the Sensation but since I had not seen any evidence of it I did not include it. But then I came across this where you will be able to see it firsthand; if you still were not convinced that the Galaxy is the right choice then you should be after watching that video.

NOTE: this is an older post from my previous site which I disabled. But due to the interest and large amount of feedback I got I have republished it here again (though unfortunately I wasn’t able to migrate the comments).
If you want to give some feedback then please do so here.

—————————————————————————————————————————–

As I wrote a while back now, a firmware update was provided by Nokia for the E72, which was available to me only a few days later and which I then immediately installed.

I have used the phone now for several weeks with the updated firmware, and I think that I can safely draw some definitive conclusions not only about the bugs that I reported here and the firmware update, but also provide some overall impressions of the E72.

I will start with the bugs that I reported.

  • I’m happy to report that the A2DP bug has been completely solved. Since I installed the update I haven’t had *any* problems with listening to music both through my BT headset and my BT stereo headphones, including after a phone call.
  • Unfortunately the phone still disconnects from the BT headset for no apparent reason, though possibly with less frequency than before. However, the phone doesn’t hang anymore as a result of a disconnection as it did before, and “all it takes” is to toggle the BT off and on and reconnect the headset.

    It is still very annoying, but a significant improvement over how it behaved before the update.

  • The speakerphone echo that I also reported has been resolved. I haven’t received any complaints of any kind since the update.
  • On a couple of occasions I have also discovered my BT headset to be completely out of battery only a few hours after a complete recharge, even though I’ve only used it briefly. It’s as if the phone leaves a connection open with the headset which consequently rapidly drains the battery.

That’s as far as the reported bugs goes.

Now for some general impressions of the phone.

  • I was on a business trip to London last week, as a result of which I put the E72 through its paces. During that trip I had several apps open constantly, including a large pdf file of the London tube network, Metro, the built in music player and CorePlayer. I would also use the GPS/Nokia maps and the camera extensively . With all these apps up and running, the limited RAM on the E72 reared its ugly head several times during my trip, silently closing apps in the background as a consequence. That, along with some hangups of the camera when I tried to take a “screen shot” of a computer display, made for a somewhat disappointing experience, and I was left with an overall impression of the phone not being entirely up to a “business critical” task.

    With the exception of Nokia, I am not aware of any manufacturer that produces high-end smartphones with only 128 MB of RAM (of which only 45 MB is free after a reset). This fact alone makes the whole RAM issue particularly disappointing, especially since Nokia could and should have easily predicted the impact of this.

  • Though not strictly E72 related, I just can’t adapt to how poorly alarms are handled on the Nokia/Symbian(?). It’s something that keeps annoying me every time an alarm goes off. Heck, even my fiancée has started to complain about how tiresome they are.

So what’s the overall verdict?

On the one hand I love the efficiency of this device: the things it does well it does really well, and during those moments I love it. On the other hand you have the BT issues, the low RAM, the alarms.

If you use the E72 “lightly” and don’t depend on its bluetooth, then it is a cracking phone which there really isn’t anything to complain about. But this phone wasn’t made to be used that way, and it is marketed as a business device. As such, I feel that the negatives are simply too prominent for me to be able to use the E72 reliably and in a consistent manner.

As a result I have decided to get rid of it. I will give it to my fiancée who won’t have any of these problems precisely because she doesn’t depend on the bluetooth and won’t “push” the phone . In fact, though she is well aware of the issues I have with the phone she still can’t wait to inherit it, knowing that she won’t experience these problems (and she hardly uses alarms).

So what will I buy next then?
That will be the topic of my next post.

I wrote yesterday what I was hoping to see in the next version of iOS. Well, it turns out I was overly optimistic, as the release only fixed the two most glaring issues (notifications and lock-screen) while leaving out everything else.

I was certainly expecting quite a lot more, and more so given the fact that it won’t be available for another few months while that the competition (read “Android”) keeps updating and improving at an astounding speed – Apple seems almost flippant in its perceived superiority over Android (and I think Android is the better OS at this point, with vastly superior hardware).

And as always Apple continues with the process to build even higher walls around their walled garden, or to use the current politically correct term ‘ecosystem‘ , what with their iMessage.

Add to that the lack of any new hardware (officially at least) and I see very little reason to wait to “upgrade” from my current iPhone 4 to an iPhone 4S/5; it’s time to look into those contingency plans….

—————————
UPDATE
According to the Business Insider, it seems as if there will be a couple of more of my requested features:
- FaceTime over 3G (though it is still crippled since it only works between iPhones, in typical Apple fashion)
- LED notification. According to the article you can use the camera LED, which seems odd since you would have to keep your phone face down in order for it to be useful; but maybe the iPhone 4S/5 will have an notification LED on the front….?

With only a few hours left before the announcement I’ll give a brief list of the features I would like to see in the updated iOS (some have been predicted, but regardless…). Some of them, not all, are actually critical if I am to consider upgrading to an iPhone 4S/5.

- Less strict rules for background apps. E.g. currently you cannot have an alarm app play a song instead of an alarm without leaving the app running which drains the battery at night.

- Improved soft-keyboard: I would like to see long presses to access numbers and other characters, instead of having to switch to a different mode (think Android on HTC phones).

- Customizable ring/sms/mail tones. ‘Nuff said.

- Much improved notifications.

- Quick access to the different radios, instead of having to dig down into the settings, in various places, only to toggle the radios.

- User accessible file storage. Let users manage part of the memory as file system where they can freely create files and folders and move them around, and also to allow to use the phone as a thumbdrive.

- Widgets. Doesn’t have to be anything fancy, but simply make the app-icons “live”, meaning that they update themselves with the relevant information. You could take it one step further and allow icons of different sizes as well in order to provide more information.

- Video calls over 3G as well instead of Wifi only. As it is now it’s virtually a useless “feature”.

- Active lock screen. Display some useful info on the lock screen as well.

- Text reflow in the browser when you pinch to zoom.



Regarding the hardware, despite the rumors of a delay, I would like to see:

- HD video recording (a given).

- A louder speaker, as the current one is ridiculously low, you are guaranteed to miss many calls and all messages/mails with the phone in the pocket right now.

- A notification LED! Having to wake up the phone only to see if you missed something the minute you have been away from the phone is a chore, and just awful usability. Apple should really know much better!

- Larger display. I think 3.8″ – 4.0″ would be ideal.

But in a short while we’ll see and I will know what my next phone will be, as I have several contingency plans…!

Tomi Ahonen has written an interesting post over at his blog – it is very long but relevant for anyone who is truly interested in smartphones, so much that it prompted me, after a looong break from posting (and after having moved to and back from abroad in the meantime), to start posting again and write about my own view of Elop’s decision to go with WP7.

Overall I agree with Tomi, though think that maybe he underestimates the perception of who are the market leaders. Also, one thing is units sold (where Nokia is still the undisputed champion), but another matter is the profit made regardless of the number units sold which (where Apple reigns), and I don’t think he gave that distinction any attention; at the end of the day, it is the profit that matters.

But one of my main issues with with Elop’s decision to go 100% with WP7, which he based on the term ‘ecosystem’ which he constantly keeps throwing around, is that I believe the idea of an ‘ecosystem’, and which obviously stems from Apple’s attempt to create one (i.e. “the walled garden“) is vastly overrated. It’s a buzzword, a fad, that will disappear.

Let me explain. On your PC you don’t have an ‘ecosystem’ nor does anyone think in those terms. What you do have is a platform (=OS) and all you want is simply the tools (=apps) that will allow you to do what you want/need, whether it be the browser or dedicated programs.

Why do people think that it is a good idea to treat smartphones any differently, and even more so when smartphones are becoming more like PCs? Why would I want to be tied to any ‘ecosystem’ to have access to and download my tools (=apps), or upload files, or participate in a social network?

What Apple got right, besides from the UI/usability, was the appstore, i.e. a simple way of finding and downloading the tools/apps that you want or need. But that is it. (Note that an appstore is not the same as an ‘ecosystem’).

Now some people make the case that people want to have a seamless experience on their phone, and that inevitably requires an ‘ecosystem’. But that is not true nor the solution, or at least not the ideal solution. What they *should* be focusing on instead is to create a solid API so that the app developers can provide that experience (if the platform creators haven’t already, that is).

Nokia had the clout to bring that open platform, with superior hardware, to the masses (probably in the shape of MeeGo) but, as Tomi notes, they failed miserably with the execution. But that doesn’t mean the idea was wrong.

So even though Elop is absolutely right about that drastic changes are needed in Nokia (especially note the last paragraph in the link), the solution is not to copy the other players, but rather to drastically change the organization in order to quickly get Nokia to execute on that broader, greater vision that goes beyond ‘ecosystems’ (think what Google did on the PC). Now that doesn’t happen overnight obviously and in the meantime they would have needed to do a lot of firefighting which could very well have included adopting WP7 or Android in some way, but certainly not to the extent and fashion that Elop executed it; e.g. imagine Nokia doing their very best to create the best speced Android phone on the market (aka. a Samsung G2 but with a better camera, perhaps a keyboard, etc.); Samsung will be selling millions of their high-end G2, with high profit margins, so why wouldn’t Nokia do equally well or better while they get their act together?

When I last wrote about my impressions of the original Palm Pre I noted that the main issue, besides from the build quality, was that it was quite slow. Fortunately, according to all acounts (and videos) all of that seems to changed with the new Palm Pre 2. Thus, as soon as the new Palm Pre 2 was on sale, unlocked, from Palm.uk I immediately placed an order for a unit.

I am really looking forward to receiving it as I have wished to have a Palm Pre device ever since WebOS was announced almost two years ago (!), and I have since openly complained about the fact that Palm didn’t sell them unlocked. But they (=HP) finally came around!

It should arrive in a day or two, and I will continuously post my impressions of  it for the next few weeks.

Nov 142010

I am in the progress of migrating my site from b2evolution to WordPress, which will hopefully be done in a few days.

In the meantime, you can continue reading the “old” site.

My fondness for Symbian is hardly a secret at this point, so when the Nokia C7 was announced I was looking forward to it more than the N8, so much in fact that I decided to wait for its release. I ordered the C7 as soon as it was available, but despite being excited to finally get my hands on a Symbian^3 device it was only with me for 24 hours before I returned it.

There were mainly three reasons for returning it.

Browser. If you have read any review of the N8 or C7 you will know that the browser has been widely criticized. To be honest, I think most reviewers have been too kind in their criticism because the browser is, by far, the worst browser on any smartphone platform out there right now. It is so bad it is borders on being unusable: it is extremely slow at loading pages, scrolling on desktop sites is choppy at best, it does not auto
fit the page to the screen width when you zoom in and it doesn’t have multiple tabs. In short, there is absolutely nothing positive that can be said about the browser.

Text input. With no portrait qwerty keyboard on board and the fact that entering text is done in “pop-up” mode, any text input is a chore.

Multitasking. No, it’s not what it sounds like. Rather, it’s a usability issue in S^3. The sliding of the horizontal list of open apps is fun for about oh 30 seconds. You then discover that you constantly overshoot the app you are looking for so you end up slowly dragging the list instead of swiping it. It’s definitely a step backward from the previous icon grid of open apps.

Then there were minor issues such as the threaded messaging: it looks nice but it’s rather slow, every time you send or receive a message it blacks out for second when it updates the list. And of course the old Symbian alarm “feature” is still there.

On a positive note though, the Bluetooth issue has been completely resolved.

In all the Nokia C7 was a rather disappointing experience, and one that left a dent in my faith in Symbian, not because Symbian doesn’t have the potential to be a great OS but rather because of Nokia and their inability for the last few years to rapidly execute plans. The next few months, what with Meego and the promised Symbian updates, will be crucial for Nokia.

The Nokia N8 was finally supposed to be released at the end of this month, but now Unwiredview.com reports that it has been delayed, once again, until October.

The reason is apparently that they are still fixing bugs!

Now, the fact that Nokia wants to release a device that is bug-free is all good and well. But Nokia’s competitors also strive to release devices that are without issues, and not only are they arguably more successful in doing so, but they also A) do not need to make a big fuss about it, but also B) manage to do so, and C) without any delays.

Case in point, you have the HTC Desire HD and HTC Desire Z, which were announced only a few days ago and will be available in less than a month.

The difference in productivity between the two companies is staggering. How many sales will Nokia lose as a result of this? Unless one is specifically interested in Symbian^3, the average consumer is not going to hold out for the N8; instead they will walk into a store, see the excellent new HTC phones (among many other options) and get that instead. By all accounts, even Windows 7 will be available by then. In other words, Nokia had an excellent window of opportunity right after the summer which they will now miss.

You would expect certain basic processes to be in place at Nokia, the largest smartphone manufacturer in the world. Yet their absence is painfully obvious, once again, with this last delay.

There is no doubt the Nokia N8 will be a very important device for Nokia, but not because of its specs and what it will bring to the smartphone market, not even because of Symbian^3, but because it will be Nokia’s opportunity to prove that they really can deliver when they set their mind to it. As such, it is arguably the most important device Nokia has ever released to date.

After the failure of Nokia’s last flagship device, the N97, (and to a lesser degree, and in my experience, the E72), they really need to show the world they can deliver a good user experience on a new device from day 1. This means making the right decisions in terms of hardware specs, software, and a thorough QA before the release.

Whether Nokia have learned from the past remains to be seen. On paper at least I would have liked to see more RAM than the announced 256MB. But regarding the software, Eldar Murtazin from Mobile-review.com doesn’t seem very optimistic, as evidenced in a very interesting interview with the Unwiredview.com.

The fact is that Nokia really will need to nail it this time in terms of user experience, otherwise they might very well permanently cement their reputation as the company that constantly “under-delivers” as a result of skimping on the hardware (CPU and/or RAM) and an awful (non-existent?) QA. I am sure the wish and the awareness of this is very present at Nokia; the question is if they can make necessary changes within the company and execute upon this awareness.

© 2011 MobileInfoPlanet Suffusion theme by Sayontan Sinha