My smartphone(s) were replaced and then summarily deprecated.

Well, after many months of having two silver paperweights on my desk, and many calls and emails to Everlink to get them serviced, I finally received an email from someone at Everlink to get them replaced.  So, I box up both phones, ship them off and a few days later, two shiny new Red E SC1100 Smartphones running Smartphone 2003.  One I turned on to make sure it worked and put back in the box.  The other, I used for a week or so before decided that the battery life just plain sucked (and I couldn't get the Internet connection working as I had on the previous SP's I had), so I want a new phone.  Well, I decided on the Nokia 6820 because of its cool flip-out keyboard and bluetooth.  It also has a camera, but that's just fluff for the most part.

Why you ask, did I get a non-SmartPhone and why am I blogging about it?  Well, first of all, to express my disappointment in the whole Everlink experience.  If you are going to pay $500US for a developer kit, the bloody thing needs to work as a cell phone.  That's the primary function.  A battery that lasts 15 minutes before it is dead is just not acceptable.  Yes, I know this is a pre-production phone and for “development purposes only”, but if I'm developing an app that uses GPRS and need to test it in the field, it needs to work for more than 15 minutes without having to plug it in.  I was *so* disappointed, I didn't even bother putting any .NET CF apps on the thing after waiting 8 months to get a copy on a real phone.  Secondly, I'm really impressed with the form factor and business-applicable use of the 6820.  I'm halfway thinking of seeing if I can get part of the CF to run on the 6820 somehow (maybe a ROTOR port or something??)  Lastly, if MS really expects to sell SP as a corporate enhancement, you have to be able to show something that a> works and b> has a wow factor.  The dev phones had some of the wow factor, but no where near the 6820 (which most exec's want because of the “promised” BlackBerry support - another issue for another blog), so in my book, that's a double loser. 

So moral of the story is - the support wasn't there when Everlink's own ROM upgrades broke both of the phones I paid for (although they were replaced for just the price of me shipping them back), the battery life was horrible and the wow factor just wasn't there for a phone that couldn't function as a phone.  I'm a staunch MS supporter and if I have ditched the product, imagine what the brand loyalty for the common folk are.


  • You should look at other phones within the Smartphone market. I'm using a Samsung i600 phone with Verizon and I love it. I also have a Xphone (AT&T GSM) that I got off of eBay that is application unlocked and developer ready for $400.

    The Xphone is everything you would want in a phone, my only issue is that GSM coverage in my area sucks.

    The Xphone has bluetooth, digital camera, Smartphone OS 2003, etc. The battery life is pretty good.

    Also, I would bet that your problem connecting to the Internet were proxy issues. When you have to setup a phone yourself, some of the Internet settings must be done manually.

    I'm a Smartphone user that will never turn back, never!

  • Otto: thanks for your comments:

    1> I will only deal with GSM phones, so the i600 will not work for me.

    2> I did not know that the XPhone was actually out. I'll check it out, but 400 bucks for a smartphone bit me twice.. it's not going to happen a third time more than likely.

    3> the internet connection wasn't proxy issues. It worked fine on the old version - the new browser just wouldn't connect 90% of the time - and in the odd chance it did, it was very slow. I tried it all over town, where I had no problems with the other phones.

    4> I said I would never turn back, and I did. First and foremost, it has to work as a phone, with the dev devices clearly did not do - which is my main beef.

  • Thanks for the link Otto - I am already familiar with Modaco. I typically frequent and - check those out if you haven't already.

    As far as the setup, I know how to set it up, it worked - it just did not work *reliably*. It is not a network issue - it was a phone issue. My provider uses no proxy, it's wide open HTTP/WPS on port 80. I had to make manual entries myself to get it to work - you have to do that with *every* phone you do not get from the provider that you use.

  • We're a group of volunteers and opening a new scheme in our community. Your site provided us with valuable info to work on. You've done an impressive job and our whole community will be thankful to you.

Comments have been disabled for this content.