Category Windows Mobile

Earlier this week, Nokia’s CEO came out and admitted something had to drastically change at Nokia, or they would basically be done…

“We poured gasoline on our own burning platform. I believe we have lacked accountability and leadership to align and direct the company through these disruptive times. We had a series of misses. We haven’t been delivering innovation fast enough. We’re not collaborating internally. Nokia, our platform is burning.” – Nokia CEO, Stephen Elop

Well, Stephen, the former head of Microsoft’s business division, revealed his master plan to reinvent Nokia… and his answer?  Windows Phone 7.

Seriously.  That’s his answer.  To move from one failing platform to another.  Excuse me while I catch my breath from laughing so hard and wipe the tears away from my face.  This is golden.

During Nokia’s presentation, he presented this ridiculously optimistic graphic, showing what Nokia thinks will happen to phone OS market share:

Read More

Two years ago I wrote about what Microsoft needed to do to turn their platform around.  Now with Windows Phone 7 only months away, it would appear Microsoft has failed in every way imaginable.

Windows Phone 7 will be a miserable failure.  There are many countless reasons why it is going to epic fail, but here are some of the most important:

1) Microsoft doesn’t know mobile phones from a hole in the ground.  Just look at the current state of Windows Mobile.  It’s built on the Windows CE platform, created in 1996.  Yes.  Let me repeat.  Windows Mobile is based on a platform created in 1996.  Sure, the platform has seen updates, but it’s still based on a world created 13 years ago.  Back when Windows 98 was nothing but a dream.   Windows Phone 7 is based on Windows CE.  Yup.  Microsoft’s newest “cutting edge” Phone OS is STILL based on Windows CE.  They just couldn’t get rid of it.  Thanks Microsoft.  The same bullshit you’ve been jamming down our throats for the past how many years that has NEVER worked right is your platform for the next Windows Phone?  EPIC FAIL.

2) The Kin is a disgusting failure.  The Kin is running a hacked down version of Windows Phone 7.  Don’t believe me it sucks?  Here are a few quotes regarding the Kin and it’s abilities:

“…Lofty goals indeed for a product like this, and unfortunately for everyone, Microsoft misses the mark by a long shot. It’s not even close.”

“…we also take issue with the browser, which is abysmally slow and buggy (it consistently crashed while trying to load any complex web pages like Engadget), and the email client, which seemed to have trouble displaying even the most rudimentary HTML messages”

“While using the One and Two we found ourselves consistently confused or surprised by how many bad little interface problems there are. Not only does the phone make it hard to do simple tasks — and not only are the social networking features poorly implemented — but the handsets are often sluggish, hiccupy, and downright crash-prone. We were told by the devices on more than one occasion that we needed to restart (while performing basic tasks), and often it would just throw us a blank screen while we waited for the device to come back from whatever tragic internal situation was occurring”

That’s enough of that.  If you want to read more though, you can head over to Engadget’s review of the Kin One and Two.

Read More

No, this post is not about my Fuze.  My Fuze has actually been a very good phone.  It has yet to really piss me off, especially like the 8525 did on a daily basis to me.

Today I got the urge to play with some different Windows Mobile builds, and since I have had my 8525 laying around not doing anything, I figured it would be the perfect little test platform.

As a side note; from what I saw from Windows Mobile 6.5 I didn’t care for it.  I like what HTC is doing with their TouchFlo interface MUCH better then the stock WM 6.5 scrolly interface.

Aside from that the OS seemed fine… but the hardware…. oh how the hardware pissed me off so badly I wanted to throw it against the wall again and again.  With in the hour I played with it, the phone randomly locked up on me… and when I reset it, the device acted like it was a HARD reset.  All the stuff I had done (thankfully not much really) was gone?!  WTF?!

I am thoroughly convinced this was not a ROM issue as there are hundreds of other people using this ROM with out issue.  I am positive that this is a hardware issue.  I believe that there is something very wrong in the land of the 8525.  Who knows what it is… I want to blame it on the Samsung processor and accompanying chipset, but I have absolutely zero proof to back that up… it’s just a theory.

The 8125, which I loved, had a Texas Instruments processor.  The 8525 had a Samsung, and my Fuze has a Qualcomm.  I have also seen other Windows Mobile (Verizon) phones with Qualcomms, and they always felt so much faster then the Samsung and even TI counterparts.  I think that the Fuze is really benefitting from the Qualcomm as it always feels snappy, and can go for a week or more with out a reboot.  That is iPhone-stability-level right there.

I’m not really sure where I’m going with this.  I am just posting up some experiences I had today which further push me to believe that the 8525 line of HTC devices had a lot more problems then just underpowered hardware.

I’m thinking of a fitting way to destroy the 8525.  Perhaps some shotgun blasts?  God forsaken hardware…

Note:  I’ve had this written since last week, just hadn’t posted it yet.  I kept going between posting it, or splitting this article up in to 2, 1 comparing hardware, 1 comparing software, because I feel like this article kind of meanders all over the place.  But I decided for my little blog site, this 1 massive post will do just fine.

Well, here it is.  The article thousands of people have been waiting for!  Ok, well probably no one… but here it is any way, my Fuze vs. iPhone comparison.  I wrote previously about why I went with another Windows Mobile phone over the iPhone, and now here is the comparison.

I’ve had the Fuze for over a week now and had time to get used to it and play with all of its features.

The iPhone is running 2.2 Firmware and has been Jailbroken.

The Fuze is running a custom Firmware.  Basically I’m running the AT&T leaked rom that is been modified.  The rom is the official AT&T update that is coming soon, but it was leaked out and people already have it.  I’m running a customized version that removes AT&T’s bullshit from it, an XDA-Developers member NotATreoFan (NATF) created.  It’s version 4.5 of his rom, which is Windows Mobile 6.1

My general feelings on the Fuze as of right now:  I LOVE IT.  This is one seriously kick ass phone.  It finally feels like a Windows Mobile device should be.  It is very fast, you can multi-task like crazy on it and it has a very nice, easy to use interface utilizing HTC’s TouchFlo 3D (which comes on the device, stock).

Read More

I recently bought an AT&T Fuze, the latest Windows Mobile powered device in the US.  It is in the mail right now and should be here next week some time.  When I get it I plan on doing a full on Fuze vs. iPhone comparison.  But before I get it, I just wanted to give a look at the history of the WM powered phones I’ve been using for the last 4-5 years and what made me decide to get another, even while around a year ago I wrote that it is broken beyond repair.

My first was the Cingular 8125 (HTC Wizard).  It came with Windows Mobile 5 and I loved it at the time.  It did everything and did it decently.  When Windows Mobile 6 came out it was an excitting time, getting the latest hacked WM6 roms for the Wizard and all that entailed.  Over all I really liked the 8125 and I still believe that it was a BETTER device then the 8525 is.

The only issue I ever had with my 8125 is the screen drift issue, where you had to align the screen about every 2-3 days.  I eventually cracked the screen on it due to my own stupidity/anger at the drift issue.

I bought an AT&T 8525 (HTC Hermes) after that…. and this device has really turned me off of windows mobile in the last year or so.  Couple that with the fact that my work phone is an iPhone, I really had a hatred growing inside of me for WM.  I still believe in the post I wrote and that Windows Mobile is broken beyond repair.  What I mean by this is that if Microsoft wants to compete seriously with the iPhone, all WM base needs to be thrown out and they need to start over.

I don’t know what went wrong during the hardware design phase of the 8525 but someone some where really screwed the pooch.  This phone has really been nothing but problems with me since I first got it.  The device has always seemed to run SLOWER then my 8125 did, and it always seems to be having issues, ESPECIALLY lately.  Most recently the phone is locking up ALL the time on me and some days I’ll miss multiple calls and text messages because of this.

I believe part of the issues with the 8525 compared to the 8125 are due to the 8525’s under powered single processor.  The 8125 actually had 2 processors in it.  1 for the OS related tasks, and 1 that managed all the phone’s radio related tasks, like calls, data, and text messaging.  The 8525 does both OS and radio tasks on 1 400 mghz Samsung processor, and I believe this is where the 8525’s shit-factor really comes in to play.

Read More

I have been using WM for nearly 2 years now. I started on WM5 and have been using WM6 for over a year now. I have had 2 different devices, both are PDA/Phone combination devices. The first was an HTC Wizard, and the second (and current) is an HTC Hermes.

I have loved these lil phones. They do literally anything and everything. Besides a phone and contact manager, you can surf the web, play games, emulate NES games, keep up to date on Weather, sports scores, RSS feeds, navigate using GPS, calculate anything you can imagine, take notes, photos, Exchange sync email, calendar, surf via Wifi, stream music and tv shows, or watch tv shows saved to your storage card…. etc… any way, you get the point.

These devices can do it all. If you want to do it, chances are some one out there has written a program that will allow you to do it.

But that’s where the glamor ends. Sure it may do all of these things, some of them well, some of them not so well, but it does not do them gracefully, or with ANY amount of style or intuition. The interface is a clunky disaster and navigating option menus and configurations is all but impossible at times.

Read More