Motorola CEO Blames Open Android Store For Phone Performance Ills
angry tapir writes "Motorola's CEO blamed the open Android app store for performance issues on some phones. Of all the Motorola Android devices that are returned, 70 percent come back because applications affect performance, Sanjay Jha, CEO of Motorola Mobility, said during a webcast presentation at the Bank of America Merrill Lynch Global Technology conference."
A company passing blame on another company for its failings...
God made the Idiot for practice, and then He made the School Board -- Mark Twain Look for http://Thebar.steelbeachca
Because of the black box nature of smart phone, developers of smart phone applications are never held accountable for the resources their application consume. It should be standard to be able to see the amount of CPU, RAM and network I/O each application is generating so that hogs which cause performance, battery life or network overages can easily be spotted. As far as I can tell, neither Apple, Google or Microsoft has taken seriously exposing this type of data as a standard part of their phone software stack. Hence, we are left in situation similar to when the food industry was not required to put a break down of the nutritional information of the food The smart phone users have apps contributing "fat" and "sugar" into the smart phone's diet without any hard numbers to evaluate that impact.
The people that care about openness are an insignificant share of the market. Android is ahead because of increased hardware choice and cheaper handsets. That's it.
Does he mean things like motoblur?
Yep, the original Droid/Milestone was lighing fast running 2.1 and 2.2. When moto started to shoehorn in Motoblur they all of a sudden got really slow.
Same with HTC Sense but HTC are at least smart enough to chuck in lots of extra RAM to handle their bloated interface. I've been running Cyanogenmod on my Desire Z since 3 days after I got it and I've been more then pleased with how fast it is, Cyanogenmod uses ADW launcher which has a crapload of features (so much so it suffers from Kitchen Sink-itis) but is still very very fast.
I used to be a fan of Android on Moto, but between locked bootloaders and crappy social network based interfaces that slow everything down have completely changed my opinion on Moto. They are floundering because of bad design decision in using Motoblur, not because of Androids openness.
After HTC and Samsung, I'd rather buy a Huawei phone simply because they used the vanilla interface.
Calling someone a "hater" only means you can not rationally rebut their argument.
Only problem is, Motoblur is the application that will drain 35 percent of the phone's power and you can't get rid of it. Its sluggish and a power hog.
Attention... all grammer nazi"s! Is they're anything; wrong with: my post,
"Top" needs to be standard on smart phones
I cannot emphasize strongly enough the horror and despair for humanity I see in this single phrase.
It's like saying back in the caveman days that what we really needed was a better rock to carve . No, we needed to move on from the cave and invent fire and dwellings.
We need to move BEYOND what we have have, what we know. We cannot keep producing computing devices for humanity that require as standard anything like Top. We need to have systems that actually exhibit some of the AI we've been working for decades on, and not have to have every user know what a process is, or indeed manage anything.
Sorry, but our baby cannot stay a baby forever, because a 50-year old baby you still have to treat like a baby is mentally damaged. We have to let computing be usable by everyone, not working fully only for the anointed and requiring mothering because we cannot tear ourselves loose from that model.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
How about getting RID of MotoBlur...it was one of the problems causing the performance issues to BEGIN WITH.
I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
Shocking, the same third party issues that caused MS so many headaches for so many years also applies to phones. The difference is people can tolerate some complexity on their desktop. Apple figured out the vertical integration thing when it came to phones. People don't want a PC in their hand, they want a well-running appliance. The failure to grasp that will be Android's undoing.
The Motorola CEO, while I disagree with the concern about the open market, is spot on about the performance issues. I don't want to pay for a more powerful phone, and I don't think I should have to. My Moto Droid with its 300MHz processor has actually had very good battery life -- several days outside the US in airplane mode, and two days with basic 3G use. I don't think a phone should need a 1GHz processor, and indeed the original iPhone had a "slow" processor and the UI is more responsive for basic UI tasks than my friend's Droid X (aside from the smooth home screen scrolling which is just a GPU hack anyway).
The battery issues I have dealt with are almost exclusively issues with the built-in OS, leaving no solution aside from restarting the phone. For example, "android.process.media" taking 100% CPU after rescanning the SD card or playing a song, and no visible feedback aside from the phone getting hot; or MediaService taking hours to update the list of photos in the Gallery app.
Aside from a couple apps that run as a service, I've almost never had issues with applications eating up battery life unless I'm using them -- and I'm fine with using battery in that case, because I want to use those apps. However, unlike iPhone, Android allows applications to run in the background, and with background tasks, Android has the responsibility to keep the Phone functioning when those apps are running.
Android should always have a usable UI (10 seconds to answer a phone call when CPU is busy is absurd), in addition to a way to learn about CPU usage and disable faulty background apps. A message like "Service X is consuming excessive battery life. Disable / Ignore / Don't notify me again about X" would probably solve half of the issues I have had. I put the blame on Android itself for not having put any thought into this problem--Every android release adds dozens of useless features but no innovation on solving these basic usability issues.
Nice, I missed that.
The sad thing is the average slashdotter will still think Android has surpassed iOS, as far too many have been saying here for over a year now. Android isn't even *close* to iOS's market share, and as Android's growth has settled down, it's not certain that it ever will.
That won't stop the endless postings that somehow people are flocking to Android because of "freedom", as though the average phone buyer gives two shits.