I am one of the priviledged few people in the world to own and use the exclusive and elusive Nokia N9. This is the wonder device with an amazing OS embedded in one of the most amazing hardware on mobile ever.

That OS has been branded MeeGo. However, the N9 does not really run MeeGo, because MeeGo wasn’t quite ready.

The N9 Is Not MeeGo

The Nokia N9 runs Maemo/Harmattan. Maemo was Nokia’s purpose built OS for tablets. It has powered a number of iterations of Nokia touchscreen tablets for years, the last being the N900, which I also reviewed here some time ago.

The N9 does not run MeeGo.

So, note: MeeGo wasn’t ready. On that, Nokia CEO Stephen Elop was right. Let us settle that once and for all. I have used the N9 till today, and I am convinced of that.

Even Maemo/Harmattan Isn’t Quite Ready

So, Nokia came up with an amazing device that runs Maemo/Harmattan branded as MeeGo. Problem solved. Who cares; right?

If you have been reading Mobility blog for a few months, you will have read my raving reviews and commentaries on the N9. All those positives remain valid. But here are the kind of issues that suggest to me that Maemo/Harmattan is not quite ready for mainstream consumers.

Take a look at these instructions:

Activate “Developer mode” by going to: Settings > Security > Developer mode. It’s OFF by default. Turn it ON.

After having it activated, you will find a “Terminal” app button under application menu.

Open it and you need to execute these commands (one command per line):

gconftool –recursive-unset /system/http_proxy
gconftool –recursive-unset /system/proxy
gconftool –recursive-unset /system/osso

I am betting my salary that if you are not a computer gizmo, you have no clue what those instructions are. I am betting that you have no interest in typing those Linux commands on your phone, except you live on command line instructions.

Well, those instructions are the only known way to solve a problem with the built-in Twitter app not working on the N9. Go figure.

For a long time, everything worked fine on my N9, then suddenly Twitter stopped connecting. Nothing I did worked. I restarted the device, checked my connections and even spoke to it (who knows?). Nada.

Finally, I got on the internet, and found that the only solution was the above steps. Now, I am more computer and mobile savvy than most people, but I can assure you that I didn’t feel any happier that I had found a solution. This solution sucks for the average consumer. It sucks for me too. Honest.

There are users with similar issues with the built-in Facebook app as well. There are some indications that adding multiple Google accounts on the N9 seems to corrupt the something somewhere (I’m deliberately avoiding geek-speak here).

Maemo, MeeGo, Mini, Mo

I love the Swipe UI of the Nokia N9, and thankfully Nokia say that they are implementing that on other devices. The N9 works well in almost every other way. But do ask yourself, “Do I want to become a Linux enthusiast in order to troubleshoot my smartphone?”

I’m betting that your answer is a big No – at least for most of you.

Troubleshooting Maemo/MeeGo devices will thrill geeks and nerds. But not the mainstream consumer. I am finally believing that Nokia made a good call dumping this platform.

Windows Phone, Anyone?

Windows Phone has a sleek, elegant user interface, but lacks too many functionality that Nokia fans have been used to. Too many.

as such, Nokia fans are caught in a tough place – Maemo/MeeGo not quite ready, Symbian has been pronounced dead (though it has stubbornly refused to die, the developer apathy to the platform is serious), and Windows Phone is so, so different.

Get Over It

Let’s get over it, guys: while the Nokia N9 is an amazing device and gets the job done, if and when you have issues, you know you don’t want to do the gobbledegook that is required to solve those problems.

Oh, plus, there are just too few apps available for the platform. It simply would be an uphill task getting apps to flood the market for it.

Running with Maemo/MeeGo simply would have been a strenous, uphill task for Nokia.

Still, I must commend the great job done by the small team that came up with the N9. Pulling this off in a matter of months, even after your CEO had declared your work as destined for the labs was amazing. Hat tip, guys.

But truth be told, this baby is not ready for mainstream consumerism yet.

Should You Get The N9?

Sure; it just depends on who you are. If you are a hardcore mobile enthusiast; yes do get it. If you love to use an exclusive device and stand out like I do, yes; do get one.

If you are also not an app junkie, by all means do get one.

Fortunately, I am both a hardcore mobile person and a lover of the finest in exclusivity. Plus, I use the barest minimum of 3rd party apps on my mobiles. As such, I am covered on all ends.

Now, do excuse me while I [grudgingly] go do the gobbledegook instructions required to get my Twitter account working on my N9 again. Don’t beef.

Comments please!

We put the matter to test in the public, and you have responded with over 70 comments and 39 votes on that article. The fight was a neck-to-neck battle between the venerable Symbian flagship, Nokia N8 (released in October 2010), and Samsung’s more recent Android flagship, the Galaxy S 2 (released February 2011). Eventually, the Galaxy S 2 edged the N8 back by just four (4) votes to clinch the title.

A summary of the votes cast:

1. Samsung Galaxy S 2: 13 votes
2. Nokia N8: 9 votes
3. Nokia N9: 3 votes
4. Nokia E7: 2 votes
5. iPhone 4S: 2 votes
6. Samsung Galaxy S: 1 vote
7. Nokia 5800: 1 vote
8. Samsung Galaxy Nexus: 1 vote
9. Motorola Droid Razr: 1 vote
10. HTC EVO 3D: 1 vote
11. LG Optimus 3D: 1 vote
12. Nokia X2-01: 1 vote
13. Samsung Galaxy Gio: 1 vote
14. Nokia 701: 1 vote

Ladies and gentlemen, I present you Mobility blog’s phone of the year 2011, the Samsung Galaxy S II:

Having had a BlackBerry 9360 with me for review for the last two weeks, it is now time for it to go. I have found it an interesting device to use – like all others, it has its strengths and its flaws.

However, one flaw that bugs me now when I have to let it go is the fact that the unique PIN that I have used for communicating with other BB users on Blackberry Messenger (BBM) also has to go.

You see, the BB PIN is tied to each specific device. When the device goes, your PIN goes. See the consequent problems?

The problem of retaining your BBM contacts is easilly solved. always backup your BBM contacts on a regular basis. Back them up to your microSD card and make suire that you retain that when changing BlackBerry devices. Slot the card in your new device and restore your BBM contacts. done.

Or use BlackBerry Desktop Manager to switch devices. Your BBM contacts will be automatically transfered to your new device.

The Unsolved Problem

If, however, you have printed your PIN on your business card, letterhead or other literature, or posted it online like I recently did….. errrr… you have to print new materials or go modify your webpage/s. Gross.

The Solution

It is more expedient that the BBM PIN be attached to users’ Blackberry IDs or accounts, so that its a permanent contact that one needs not worry about. I hope that RIM effects a change to reflect this.

At the moment, this device-specific PIN is a clog in having people adopt their BlackBerry PINs as important contact information.

PS: If you added me to your BBM contact list, I’m off BBM till I have to review another BlackBerry device. I do have your details backed up, and I will show up as soon as I am BB active again.

For now, that PIN now belongs to someone else. Yes; shame.

But the Mobility BBM Group is still active, and I have granted Admin privileges to a few trusted individuals, so do keep having fun!

Our own regular here, Lord Banks, has put up a rejoinder to Ibukun Olaoya’s recent article, Why I Have Refused To Jump Off Symbian. The rejoinder, titled Symbian Will Die – Long Live The User Experience, is a well written piece that addresses issues I also had with a number of EyeBeeKay’s reasons.

Here are the key points:

1. The quality of the user experience should never be dependent on the user’s willingness to customise it
2. Normal people generally don’t enjoy spending lots of time under the hood of their cars (or in this case, smartphones), messing around with the innards
3. Symbian has AIDS – Apps Incentive Deficiency Syndrome

I pointed out some of these issues in response to EyeBeeKay earlier. For example, the need to customise the user experience in order for it to be acceptable has been taken care of in Nokia Belle. Belle is a complete transformation into a modern user experience.

If you have used a Symbian device in the last three years, I recommend that you pick up and use a Nokia Belle device for a few weeks to see how good it really is. If you haven’t used Belle, any comments that you make about the Symbian user experience are likely to be 99.9% outdated and no more valid.

This is part of why it is my position that Nokia needs to stop putting outdated Symbian software in new devices. If users keep running into older, less-supported software (S60 3rd Edition & S60 5th Edition) on their smartphones, it is counter-productive to the experience of the different beast that Belle is.

Like I said to Ibukun, he needs to throw away that S60 5th Edition Nokia 5800 and get himself one of the new Belle devices.

However, I am not sure that much can be done about the Apps Incentive Deficiency Syndrome at this point. Belle seems to be coming after many developers had decided that it wasn’t worth the trouble anymore.

New apps are showing up for Belle on a regular basis, but not at a fantastic rate or anything comparable to what obtains on iOS and Android. If Nokia are able to somehow turn the tides on developer churn, then there is a fighting chance for Belle.

In the meantime, you will want to read Lord Bank’s complete article: Symbian Will Die – Long Live The User Experience

I am often amused when pure touchscreen aficionados assert that hardware QWERTY devices are history. Like people who assert that Blackberry has taken over Nigeria, they speak from what they observe in their limited circle of friends and acquaintances.

Of course, such a limited viewpoint does not portray the full picture – the true picture – of things.

The Statistics

At the time of writing this, there are over 170 modern mobile phone models with hardware QWERTY keyboards in the market. This includes feature phones, as well as smartphones from all platforms except iOS – Bada, Android, Symbian, MeeGo, WebOS, BlackBerry and Windows Phone.

These manufacturers know that there exists a market for hardware QWERTY devices, and wisely ensure that this market is not neglected in their line-ups.

All these manufacturers are releasing hardware QWERTY devices for all classes – low-end, mid-tier, and high-end. They are releasing candy-bar QWERTY devices and slider QWERTY devices alike too.

Around this time last year, I wrote an article on how it looked like QWERTY bars had been left in the hands of RIM/BlackBerry. Apparently, other manufacturers have wizened up to reality and are now pushing QWERTY bars with more vigour.

Pros And Cons

There are arguments for and against hardware QWERTY keyboards. We can argue the pros and cons all we like, but here is the most powerful factor – people will use what they want (or like), regardless of the pros and the cons.

Here is an excerpt from an article on Android Authority on the Best QWERTY Android Phones in 2011:

We happen to believe that QWERTY smartphones are craved for by mobile enthusiasts. An Admob report in 2010 showed that 54% of Android traffic was driven by devices that feature a full QWERTY keyboard. It’s hard to deny that a huge amount of people still want a powerful smartphone with a physical QWERTY keyboard.

This is interesting, as the Admob report echoes my observations on the subject – QWERTY devices are not going anywhere.

Yes; its hard to deny that a huge amount of people still want physical QWERTY keyboards. Yet, somehow, some still flat-out deny it.

Choice. Preference. Taste

SWYPE is awesome; yes. Onscreen QWERTY keyboards have improved tremendously; yes. But there are those who want hardware QWERTY and nothing is going to change that. This phenomenon is called choice. Preference. Taste. The last time I checked, it was a good thing.

Those who think that speed is all there is to the argument are wrong. If that were true, nobody would buy trucks or SUVs or city cars. Everyone would buy sports cars and roadsters instead.

Some men like their women lean and trim. Others prefer them with some extra flesh. Same goes for the women-folk.

In the end, a lot boils down to taste. That’s the way the world works. That’s the way humans are.

Personally, by default I will take a hardware QWERTY device over a touchscreen-only device. Not that I think the latter is inferior. In the same way, there are those who won’t touch a hardware QWERTY smartphone either.

If Apple were to release an iPhone with a hardware QWERTY, chances are that I would purchase one. Yes; I am hardware QWERTY like that.

In their line-up of best QWERTY Android smartphones of 2011, the Android Authority guys added, and I firmly agree:

QWERTY smartphones aren’t dead as some claim. It’s a booming ecosystem, in fact.

Those who claim that the hardware QWERTY on mobile is dead are seriously mistaken or comfortable in their denial. It is actually alive and well. The figures speak clearly.

Wake up, guys; the hardware QWERTY is alive and well. Comments welcome!

We know that not all our readers believe in or celebrate Christmas. Still, it doesn’t hurt to wish you all peace, love, joy and all good things this season and beyond.

Do kick back, relax, spend time with your loved ones, and have a fun-filled Christmas time!

Phone Of The Year?

To spice this season up, we are giving you all the opportunity to vote for your phone of the year 2011. You can only mention one device. One. It doesn’t matter when it was released. Tell us one device that has so impressed you this year that you’d like it to wear the crown of the “Mobility Blog Phone Of The Year 2011″.

We will collate the results before the year runs out and announce it here on Mobility blog. So, give it a shot now!

Ho ho ho!

Recently, I wrote about Blackberry BlackBerry Messenger As A Social Network.

One of the responses that I got to that article was from a gentleman who referred to BBM as the 3rd social network after Facebook and Twitter. he also added that he did more social networking via BBM than via the fore-mentioned two.

In addition, we now have an active Mobility blog BBM Group with 21 members. That number was achieved within four (4) days.

Recently, I found the display picture of one of my BBM contacts to my liking, but I didn’t feel like saying anything though I really wanted to appreciate it in some way. I found myself wishing for a “Like” button similar to what obtains on Facebook. That way, a user can like a Display Picture or Personal Message belonging to any BBM contact.

Any others?

It is possible that BBM can be further enhanced as a social network. Do you have any other ideas?

PS: In the meantime, if you want to hookup on BBM, here’s my PIN: 285A12BB (PIN no longer valid).

In a previous article of mine titled Change Is In The Air: Goodbye to Symbian?, I said this of BadaOS:

Bada? I don’t know. Bada is a poor copy of Android. If I want Android, I go buy Android.

Perhaps that was a bit too unflattering.

Every major mobile OS besides Android has slipped in market share since 3rd quarter 2010. The list includes Symbian, iOS, BlackBerry, and Windows Phone. The only platform other than Android with numbers on the rise is Samsung’s Bada OS, up to 2.2% from 1.1% last year. According to Gartner, that means Bada has a higher market share than Windows Phone (1.5%) right now.

Perhaps we are wrong ignoring it because its marketshare is still small. If it is growing, it shouldn’t be ignored. Consider that with all the buzz about Windows Phone, BadaOS is bigger.

From Samsung Jet To Bada 1.0

Back in January 2010, I reviewed the Samsung Jet, a non-smartphone that Samsung promoted as “smarter than a smartphone”. It was not too long after the release of the Jet that Samsung announced BadaOS.

In my informed opinion, the Jet was a fore-runner of BadaOS. I have had a brief hands-on with a first generation BadaOS device, and the similarities are too clear through and through.

A long-time regular on Mobility blog, SpacyZuma, also gave us a review of his Samsung S8500 Wave, so you can check that up.

Enter Bada 2.0

Of course, BadaOS 1.0 was unfinished and not quite polished. However, the latest iteration, Bada OS 2.0, has been re-worked. By how much, we are yet to see.

But in my opinion, perhaps BadaOS can be a viable alternative to Android OS. They are similar in functionality and UI. However, the apps ecosystem on Bada is not as robust. Still, it is growing.

Perhaps time will tell by how much.

Eyes On The Samsung S8600 Wave 3

There have been about ten (10) BadaOS devices released till date, and the Samsung S8600 Wave 3 is the flagship device. I will have my eyes on that baby in 2012 and lay my hands on it in the shortest possible time for a detailed review.

What do you think? Does BadaOS stand a chance? Is the growing marketshare an indication of anything? If someone is looking for functionality similar to what Symbian and Android offer, can Bada become a platform to run to?

The Co-Creation Hub Christmas Party for the Nigerian Tech Community held on Friday 16th December 2011. It turned out to be an awesome time.

I don’t know about you, but 2011 has been fairly stressful for me, so when I heard “party”, all my adrenaline went into full gear. Here was an opportunity to unwind and have fun, and I wasn’t going to miss it for the world.

Below are some pictures that I believe captured the essence and drama of the night. There are many more pictures than these, and I have provided links to the full albums at the end of this article.

I have included my commentary, and I hope that you have some fun going through this brief pictorial account.

I suspect that we might be getting more phone calls than usual at Mobility Towers from now. Omon seemed to have more than her fair share of admirers. Trust me. However, if you quote me on this, I will deny it vehemently. Thank you.

I was selected to pop a bottle of champagne. Lawd knows I had no idea how to go about that. In the above pic, I was trying to coax Emeka into doing it. Thankfully, Bosun rescued me when the time came. Phew!

It needs also be said that Gbenga Sesan did all his dancing that night by mouth. We suspect that he did that to protect his future political career from embarrassment. Yes, Gbenga; call your lawyers.

And, yes; I’m just beefing that he had all the ladies’ attention and I didn’t.

And Now, Some Honourable mentions

There were some individuals who stood out on the dance floor that night. Here they are:

Unfortunately, the above are not exhaustive. Lots more people showed dance floor talent that night that are not included above.

One thing is for sure, techies know how to party. Thanks to C0-Creation Hub and Opera Africa for an awesome event.

More Pictures

There are in all a total of 315 pictures published. There are certainly more exciting pictures than those selected for this report, so if you are game, head for the albums below on CcHub’s Facebook page.

You can view the full albums here:
1. Christmas Party for the Nigerian Tech Community

2. Christmas Party for the Nigerian Tech Community – Continuation

The primary reason why users are jumping off the ‘burning platform’ – i.e. Symbian-powered devices – is the unintuitive interface.

Compared to the other modern Operating Systems (OS), the Symbian User Experience (UX) is not as exciting and productive. Symbian lacks very little apart from this. Symbian is resource efficient, does multitasking well, and generally gets the job done.

Note that this un-intuitiveness obtains mainly on pre-Belle Symbian versions – Editor

I have often contended that no matter how wonderful an OS Interface is, or how much capable it is out-of-the-box, there will always be some lapses. This is where third-party applications fill the gap.

Hauling a smartphone around without making full use of the power of third-party applications is like permanently driving a V8-powered special Utility Vehicle (SUV) at a maximum of 40Km/hour on macadamized expressway. Hardly what it is built to handle!

Occasionally, I have been tempted to purchase a device powered by iOS/Android (Fruit & Robot). After all, variety is the spice of life. But that temptation is usually momentary. I end up asking myself, What UX can Fruit & Robot furnish that my Symbian-powered touchscreen device can not?

I am still struggling to discover this. Conversely, are there certain functionality available on Symbian that the Fruit & Robot lack? I know of a few.

I employ mercenaries (third party apps) to supercharge my aged Symbian-powered (s60 version 5th) Nokia 5800. Using these, I have not been able to justify being unfaithful to Symbian.

There are activities that we performance frequently on our devices. These activities should be accessible from ANY application. I attempt to highlight a few elegant applications that I employ on my Nokia 5800 to enhance my user experience, and mimic the Fruit & Robot OSes. This is not exhaustive.

With ‘DzSoft SettingBar’ installed, I can drag down from the top of the display. A screen pops up, allowing the following activities:
- Tweak profile settings
- activate silent and Offline mode,
- Turn bluetooth setting,
- Directly adjust screen brightness,
- Engage WLAN,
- juggle the music controls
- show the current time and battery status.

More interestingly, I am able to specify a maximum of five (5) applications/functions which can be invoked at any time – from any screen.

On my device, I have set those 5 slots to :
- ‘Home Screen’,
- ‘Settings’,
- ‘Messages’,
- ‘Contacts’
- ‘PhoneRotate’ (allows changing the phone screen orientation – at any point – without turning on the orientation sensor, which wastes battery power)

FIVE IS NOT ENOUGH
Of course, you are probably thinking: Just five application slots? That is not adequate! Enter ‘SmartPhoneWare Instant Menu’.

The applications I have assigned to ‘InstantMenu’ are the following: MsDict Viewer – (multi_dictionary application from MobiSystems Inc).

Kylom Project (outline application).

EpocWare ‘Handy Calendar’ (Appointments, reminders, etc).

Sticky Notes – ubiquitous electronics stick-it notes.

To further embellish instantaneous accessibility to my phone applications, I make use of JBak TaskMan.

The last software that I utilize is Usanov-Kornilov Nikolay’s QuickLaunch. This application allows you to specify five (5) application icons that popup on your touchscreen – in the usually anytime, anywhere fashion.

The apps I have assigned to QuickLaunch are:

- UC Mobile Browser (surprised?)
- LonelyCatGames X-plorer
- Opera Mini – better known than ‘money’!
- Quick Office – a versatile office application

LOCKING MADE EASY
We often need to (un)lock our device several times during the day. I have avoided using any of the physical keys on my Nokia 5800 – they will eventually fail. I prefer instead to use software solutions.

The camera, powerOff, (Un)Lock, Call (Green), Terminate (Red) and Menu (white) buttons have been permanently on holidays on my device. I do not use them (does that remind you of the buttonless Nokia N9?).

The ‘dzSoft DzLock’ application provides a variety of methods to (un)lock my phone. Swipe, double tap proximity sensor, cover the sensor for 3 seconds – are examples. You can (un)lock anytime, from
anywhere.

I urge people who spend good money on smartphones to get good Return On their Investment (ROI) by making use of software that brings out the power of their device.

Are you really making use of that smartphone?

So, you know why Symbian has me by the Jugular, and I am not complaining !

If you think I am ‘missing something’, please elaborate!

RIM have had a hard year in 2011. There were a number of server failures. The BlackBerry PlayBook has had dismal sales. RIM also had to rename their next generation OS version from BBX to BlackBerry 10. And now, their financial value is down over 70% in a year. A bad year indeed.

Mobility blog has a fast-thriving BBM group. Someone asked this question there yesterday: “Does RIM really need the American market to survive?”

The answer, in my opinion, is a No, and I will state why. First take a look at the following:

• There are a number of mobile manufacturers who build exclusively for the Japanese market and are doing fine. One market, yet healthy and profitable.
• Huawei has slugged its way up to the top 5 manufacturers list without being able to win the U.S. market.
• Market advisers have often said that it makes sense to focus on where one has comparative advantage or where you have a ready market.
• Motivational speakers will also tell you to go where you are celebrated. For RIM, that should mean that they focus their most energies elsewhere, if only for now.

RIM Needs To Go Radical – In A Different Way

Here is a saying of mine. For the records, I made it all up, and it reflects my often non-conformist, adventurous and radical nature:

Doing and saying what is popular may indicate a lack of creativity, courage or intelligence. Possibly all.

Every manufacturer is copying the iPhone, though they won’t admit it. In my opinion, they all lack either courage to be different or creative. Possibly both.

Some so lack this creativity that they copy its weaknesses too – hook, line, and sinker! Bummer!

Interesting enough, the iPhone didn’t become so popular by copying anyone. Go figure.

RIM, Stand Out

RIM, stick with your strengths – those great keyboards, that excellent form factor, and your security. But be creative.

For example, provide the option to choose to use a BIS plan or not for internet access on your devices.

By all means stick primarily with QWERTY keyboards. Add a Communicator form factor (side-sliding QWERTY). Keep one full touchscreen range. But let your mainstream devices be those great candy QWERTYs that people so love.

Full touchscreen slabs may be popular, but it doesn’t mean that the QWERTY market is not sustainable. It is! And for now, RIM is king there.

Stand out! Don’t conform!!

Go Where You Are Celebrated

RIM has the strongest following anywhere but the US market and need to wake up to this reality. In the UK, BlackBerry devices are still some of the most desirable smartphones. There’s also the Netherlands, Brazil, and Nigeria, among several others.

RIM needs to focus their energies in these places.

If RIM is waiting for BlackBerry 10 to turn things around for them in the U.S. and in the eyes of the U.S. media, they are probably in for a surprise. On the contrary in the markets where RIM has good mindshare, both users and the media are constantly singing the praise of BlackBerry and talking about how awesome it is. RIM needs to focus on the markets where it needs the least energy to sell.

RIM will continue to sell to their die-hard customers in the U.S. too, but that is not where they are celebrated now.

Africa, South America, Asia

RIM needs to ride on the wave and hype that BlackBerry already has in these regions. The hype is much, though Blackberry devices are not really as popular.

So many people in Nigeria think that Blackberry is the most popular phone in Nigeria right now. Even media houses and tech people (who should know better) help spread this impression though it is very untrue! That’s tremendous market advantage.

Young and mid-age people in several countries across the world are going Blackberry-gaga. That’s where RIM should be looking.

My almost 70-year old dad wants a Blackberry. His business partner has one. Almost every university undergraduate wants one. My kids want one each too.

They know a BlackBerry when they see one. Think about that. I can’t say the same for most other brands.

Come on, guys! Come and ride on this! Get on TV, in newspapers, on blogs, and on buses – and push this thing!

Push it, or go the way of the dinosaurs.

Conclusions

RIM did not achieve its great successes because of the American market. They achieved it when they started selling their BlackBerry phones elsewhere on the planet. That is exactly what they need to keep doing and pushing harder.

If you know anyone in RIM who can pass this article up, please refer them to it. I would hate to have to refer to this article a year from now with regrets.

I rest my case.

I use the Nokia E71, and on this device, Opera Mini is my browser of choice. I also do a lot of chatting via Yahoo Messenger’s mobile site right on Opera Mini.

I have noticed that from time to time, Opera Mini and Yahoo Messenger just have a ‘fight’. As the saying goes, when two elephants fight, the grass suffers. I really do suffer during those periods, as I’m paralyzed instant messaging-wise.

Every attempt to sign in would tell me, “Problem encountered while processing your last request. Error code 200″.

Given some time, they seem to be able to sort out their differences and life goes back to normal.

Recently, these two systems had such a ‘fight’ and this was really bad because it went for three days stretch. Now you can imagine my frustration during that period.

While things have since gone back to normal, I have to ask: Is this issue peculiar to just me or do others have similar experiences?

If you have ever experienced such, did you do anything to solve the issue? What did you do?

Thanks in advance!