Android Phones
Motorola CEO blames Android apps for phone quality issues, thinks Blur can fix that
June 3, 2011 | by Andrew Kameka
Motorola
Why does your Motorola phone freeze so much? How on Earth can you explain the lag or apps that work perfectly fine on other phones yet seem to crash on your Atrix 4G or Droid X? You would naturally assume that there’s something wrong with your Motorola phone, but the problem is actually those crappy apps developed by third-parties.
At least that’s what Motorola CEO Sanjay Jha would have you believe. In a webcast presentation yesterday, Jha downplayed the obvious failings of MOTOBLUR and pointed the blame squarely on poorly constructed Android Market apps that hinder performance. These apps eat battery life and lead to errors that, according to Jha, cause up to 70 percent of the returned Motorola Android phones.
While there are obviously a large number of Android apps that have problems and don’t deserve to be in the Android Market, it’s laughable that Motorola would pin its failings on those apps. I’ve tested several Motorola devices and each time, no matter how far the technology advances, I walk away hating MOTOBLUR even more. And many of the errors that I’ve experienced on those phones happened out-of-the-box before I even launched the Android Market. Perhaps Jha should look twice at the bloatware he and carriers place on Motorola devices and its tweaked versions of Android, that also never seem to get the advancements and improvements that Google offers to deal with some of these very performance issues, before blaming developers.
Jha is actually going in the opposite direction and painting MOTOBLUR as the very thing that will prevent poor performance by warning users about poor apps. More than 10 million MOTOBLUR phones send usage statistics to Motorola, so Jha believes that the company is close to developing a system that can analyze that data and build a list of faulty apps. So if an app performs poorly on Blur devices, users will get a warning before downloading that the app may affect performance.
I think this is probably true. That said, battery life with my Droid X is pretty manageable. And performance and force closes have never been much of an issue with me. Now I don't use Wifi and Navigation a lot. But when I do, they are battery hogs. Since Navigation is almost always used in my car, I simply keep my phone hooked to my charger. No big deal.
So why when I put an ASOP rom on my Droid X do I not have any of these problems?
Lol, I guess he never read this article -> http://android-simplicity.blogspot.com/2011/06/an… Shoulda bought an apple!
I agree 100% with this article. Considering just how bad Motoblur is, I don't think Mr. Jha needs to be commenting on anyone else's programming. The Droid X and Motoblur is a disaster. Between that mess, and the fact that Motoblur is downloading information about usage, locking down bootloaders, and will now act as a gatekeeper for apps on Motorola devices, etc. I won't be buying any more Motorola devices. My recent post About Simply Applied
Even my backflop is half decent with cm6 on it. It is definately motoblur that sucks not third party apps
What's even more annoying is that developers spend a lot of extra time dealing with issues/bugs because of all of these manufacturer customizations. By putting MotoBlur on their phones, they are creating issues which require the app developers to spend additional time testing and fixing problems which would be avoided if they'd just use stock Android. Maybe developers could make better apps f they had more time to spend on improving their apps and less time trying to figure out why their app works with HTC Sense but not Motoblur. On top of that, all of the phones would get updates in a timely manner, making it even easier for developers to ensure their apps work properly.