Only this time the problem is more perwasive. With PC an average user did not get botherd by all this trash, the machine was good enough for surfing and email, which is what they used it for. Only advanced users and techies would get frustrated. However, with smartphones it seems to be a real problem even for an everyday user.
What I don't understand though, is all this fat that providers pile on the phones and PC really worth it for them. They spend time and money to develop all these custom themes and apps, than users remove them. Even if users don't remove them and find them good enough to use, where is the profit to the provider? Branding and recognition?
http://m.gizmodo.com/5439590/best-buys-optimization-is-offic...
For wireless companies, the custom branding is how they hope to be considered more than just a dumb pipe by providing additional "value" to users. This is why Verizon bundles their Vcast music store, and AT&T includes their custom Navigation and Yellow Pages apps. They desperately want to be seen as content companies. This is not a reasonable business strategy though, because the more they frustrate their customers with this nonsense, the more those users will flock to the pristine shores of iOS, where carriers have even less control, thereby cementing their position as a simple utility.
So the PC experience has gotten a lot better in recent years. I don't know why though, perhaps the industry learned? Perhaps it's not worth it to pre-load it with crap anymore?
The crappy first use experience was ruining Microsoft's image, because people associated the cruft with them.
I agree that unremoveable and unkillable apps are a huge problem with Android. This is why I switched to Linux in the first place and Google needs to fix it, ASAP.
Maybe it's different now?
It still absolutely amazes me that you guys usually pay for incoming SMS messages.
I mean come on. W T F? If the carriers started charging each time you charge your battery the US public would just bend over and take it.
Contrary to most the promises politicians make, this one costs no money and simply involves signing the right bills into law. It will even be good for the economy. Of course, they would have to withstand the rich and powerful lobby of said behemoths, which is of course why such a politician will be very hard to find.
What? I've never seen a carrier charge for incoming SMS.
Many people have a plan addon that includes receiving some SMS for free, but the basic stock plans do not.
For the last few years, texting to the US had always been at the same rate as Canada (and covered by texting plans). Rogers decided to switch that on me when I wasn't paying attention... although I'm pretty sure I asked, and the Sales guy lied.
In either case. One complaint to the FCC in the USA, or CCTS in Canada will get things your way. Both countries, from my experience, has pretty terrible customer service. I can barely understand half of Verizon's CS team, and one guy at Roger's CS actually told me I should just do nothing, even though I felt cheated, because "if you sue, our company has more money than you, and you'll lose for sure". Sigh.
I called Bell to have them block all incoming text messages and they said that they could not do it because it was somehow tied to their emergency 911 location determination service. After much prodding they said they could turn off incoming texts (but I should hope that I never have to call 911 with my mobile) but came back with a $3/month plan for like 500 text messages so I just took that instead.
I switched to Rogers and am now on an iPhone plan which has text messaging but I would love to be able to block incoming texts again if iOS 5 and Google+ gets serious traction.
Verizon: "20¢ per text sent (per recipient) or received (including Canada, Mexico, Puerto Rico and the U.S. Virgin Islands)"
AT&T: "All AT&T customers with Text Messaging-capable phones are pre-activated to send and receive messages at $0.20 per message with no monthly charge."
Straight from their websites.
Also it could quite possibly be that I am indeed living under a rock as I am very satisfied with my carrier so I don't actively look at plans of others.
https://encrypted.google.com/search?q=incoming+text+message+...
the problem is CTS tests API consistency with the goal of preventing platform fragmentation for app developers. there is also a separate set of tests that specify minimum hardware requirements for each version of android, and specs such as battery life, etc.
compatibility and android brand licensing also requires a certain set of minimum apps, such as the phone dialer, calendar, contacts, music player, etc. but (and quote[3]):
> The Android upstream project defines a number of core applications, such as a phone dialer, calendar, contacts book, music player, and so on. Device implementers MAY replace these applications with alternative versions.
and further -- the gmail, chat etc. apps are proprietary Google apps, and there are various licensing reasons why they can not be enforced as part of 'compatibility'.
API compatibility is good, but UI and app compatibility is very flexible - and given such flexibility, carriers will almost always go the crawpware route.
[1] http://source.android.com/compatibility/android-cts-manual-r...
[2] http://source.android.com/compatibility/index.html
[3] http://source.android.com/compatibility/2.3/android-2.3.3-cd...
Clearly this phone is one example, if the battery is discharging itself so quickly (and generating so much heat) in an hour.
How about the only sane option is to not buy a phone with crapware on it? This is what markets are for - so that crappy products can die. If Verizon sells phones with crapware and T-Mobile sells phones without, choose T-Mobile.
Even better, if the US market finally wakes up to buying unlocked phones from electronics vendors rather than locked phones from carriers, you can actually choose between handset brands like consumer electronics is meant to work.
If I buy a digital camera, I have to do a bit of research to find out which one is good. If I'm not that demanding, then the extent of the research can be asking my friend who just bought a camera which one she bought. It would be an easier choice if only two companies made decent cameras and I just had to choose one or the other, but that's not how it is, and I suspect the camera market would also stagnate in that situation.
Sorta gives me a bit of hope on capitalism. I stay with them on principle.
Give me a break. Just get a phone "with Google" and use the pure Google experience and it's a breeze. All of this spinning and complaining about what OEMs are doing to an open source OS is like complaining about the DIY boxcar racer you bought and put together turned out like shit. (and you want your money back.)
The "with Google" branding meaning nothing in terms of actual phone experience, and Samsung isn't the only vendor at fault here. After my experience, and dozens of similar accounts like this blog post, I don't recommend anyone buy an Android phone that isn't a "by Google", like the Nexus line, and even then, only if they have some strong objection to getting the iPhone, which I would recommend over any current Android device.
I really, really, really wanted to like Android, but you can damn-near put an 18 month countdown on the majority of the Android phones before the manufacturer abandons it and you're stuck using XDA developers or the like for updates, patches and improvements, or just to fix the stock crap they ship. On a 24 month contract cycle, that's just unacceptable.
Somewhat broad generalization ahead...
About once a year, Apple comes out with ONE new phone, an iPhone. If the phone is bad, Apple goes out of business. Apple bets the company every year on that new iPhone, and to make that a reasonable bet, they spend tons and tons of marketing on design, engineering, quality, and customer support. Apples knows a bad iPhone makes WSJ / New York Times front pages. Apple knows that to make a bad iPhone loses them iPad, iPod, Macbook,... customers.
And so ... by and large, Apple does not make bad iPhones.
In contrast
Four times a year, each, HTC, Samsung, Motorola, LG, Kyocera, Huawei, Sony, and others, come out with a new Android phone. This phone is one of many many products made by each of these companies. The success or failure of any of these phones means almost nothing to the company. And so, the product development and rollout of any of these phones is not a bet-the-company gamble. Accordingly, very little effort is made on design, engineering, and customer support. None of these companies have terribly loyal customers, most seem to buy a given phone based on carrier affiliation, or based on costs. Losing a customer here is bad, but does not carry the long term cost as losing a customer at Apple does.
And so there is very little incentive to make anything but competitive (in all the wrong meanings) phones here. There is a race to the bottom mentality going on.
"We think the phone we make is good, at least as good as the phone they make. Let's get some more marketing dollars from our partners for it and we will all be happy"
I then went to look at Creative's website, and looked through their list of products. They had 16 separate models, many of which were very subtle variations (e.g. the 316 vs. the 316z). There was no breakdown page that would show you the differences or help you decide. Some of them had LCD screens, some of them played WMA, some of them had more space, some came in multiple colours, but you didn't know which had what or what it cost until you clicked on the page. Making a completely informed decision would take hours of clicking links, making notes, hitting the back button, and then clicking the next link.
I marvelled that not only was Creative competing against Apple, they were competing against themselves. They produced 16 different models, which requires 16 different manufacturing processes, 16 different packagings, 16 different manuals (each in a variety of languages), 16 different QA processes.
The same thing is happening here. Manufacturers are largely unwilling to challenge Apple in the high-end of the market (where the Galaxy S, Nexus S, iPhone 4, etc. all live), so they work in the smaller end. The lower prices mean lower margins and lesser quality parts. This also leads to less testing and QA, meaning a lower quality finished product.
As a result of these lower margins, they need to sell more phones, which means producing more models of phones and shortening the lifetimes of the phones in order to encourage people to turn them over faster. It's becoming a race to the bottom.
People compare Android and iOS to Windows and Mac, but it feels like the better comparison is Mac vs. PC hardware, not software. Apple makes very few models of computer (Macbook Air, Macbook Pro, iMac, Mac Pro), which they refresh lately. There are lots of variations, but you have four base models which are simple to understand. In comparison, if you go to Dell's website, there are a dozen models you can buy, each with subtle variations, and even with different prices depending on which business unit you buy from. Other PC manufacturers all do the same thing, and because they don't control the software they ship (other than crapware), they can only really differentiate on price.
It's become a race to the bottom, trying to slash costs and increase volumes at the same time, and PC manufacturers have realized that they're fighting over a huge chunk of the market and leaving Apple to actually make the profits. Android certainly has the potential to surpass Apple in market share, but they're going to be fighting over a much smaller chunk of profits, fragmenting their efforts over multiple products and competing against other manufacturers' multiple products.
It just doesn't make a lot of sense to me.
Google needs to create a new platform that curates as well as Apple does. Or sit and watch while Amazon builds one on top of Android.
In the long run, Google needs to do something about this, or face it doing severe damage to the image of their platform.
I bought the MyTouch3G (2nd Android phone ever), the G2, the Nexus S and recently the Galaxy Tab. Overall, I'm very happy with the experience of each of these phones. There are other phones out there that have great experiences as well. As a consumer, I will research these purchases which matter and will pay with my time to get exactly what I want. If you want to, instead, pay for one company to handle quality end-to-end for you, then you will pay for that, too.
For me, the pluses in Android outweigh the (few) minuses (that remain).
For anyone else, it's great that they have the choice to make. :)
If years of market research prowess fails me and I consistently see similar stories crop up every month or two where other technically inclined people regret purchasing some other Android device, it says to me that I didn't simply get a lemon or make a huge mistake in my decision making but the market itself has a problem, whatever issues and loopholes allowed it before have remained unfixed. Since the price difference between iPhones and top end Android phones are basically the same ($100 variance or so on a >$2k total cost...big deal), and that I can mindlessly buy whatever the next iPhone release will be and have pretty good assurance Apple has my back, I'm completely unwilling to waste time researching Android devices and still possibly get bit in the ass for my efforts.
Most consumers don't know the difference between Google-made Android phones and the others. You're missing the core point which is that the Android platform is fragmented and regular people are being given a phone full of advertising and apps built for up selling.
Regardless, the intention of my point was that manufacturers were given "blueprints" and "tools" and they built a shitty product. Even though Android is Google's product, the end result is not and to point fingers at Android is wrong. Is it the fault of Google if people are using the tools improperly? If anything, Google should've better managed the Android trademark so as to not associate their toolbox/blueprints with sub-par implementations.
I'll be downvoted, but here goes: This shows the Linux heritage. All of Linux's problems on the desktop aren't really problems with Linux. It turns out that Android's problems aren't Android's either.
Solved!
All of Linux's problems on the desktop aren't really
problems with Linux.
Errr, what?The reality is that Linux-the-umbrella will be judged by any specific distro's user experience. People more familiar with the situation will know that in many cases bad experiences are caused by choices specific to distros or even the packages they bundle, but the true average user's perception is not that nuanced.
The same argument largely works for Android. In some ways worse because there is a certification process that allows you to use the Android name, but does very little to ensure someone didn't wreck the user experience with their customizations.
In other words, "Hey, let's make it somewhat exclusive to use our brand, but do nothing to ensure quality from the end-user's perspective!" All the disadvantages of exclusivity, with none of the advantages.
For example Ubuntu has made great strides in this regard, but some would say the continual, sometimes drastic changes in the shipped apps and modifications of the interface make it hard for users.
The technophiles are right about the point they make about the latter, but it's the former that will make or break it in the marketplace.
In this case, instead of addressing (usability?) issues, the perceived problem, rather than being addressed head on, is redefined as being at the feet of the user, thus transferring responsibility and absolving oneself. (I.e "It works for me"!)
I think that's what they were saying.
But the fact that some hardware producer doesn't want to give up the specs so that we can support it? Not Linux problem.
They may be a problem for you, if you want to run Linux but it isn't Linux problem.
This case is the same. I would prefer it was some problem with Android, since we could then solve it but crap-ware on carriers isn't a software issue.
MS understood this and they are doing the same with WP7. Google knows it is a problem so they release the Google Experience phones, but they can’t disallow it completely.
Battery life was terrible on every Android phone I used. I could not get through an 8-9 hour work day with moderate use (an hour or two of streaming, maybe a few web pages, some texting and a brief call or two). I can absolutely confirm the weird battery issues this user experienced. On multiple phones. At times, the phone would get warm (not scorching hot in my case) and the battery would go from close to a full charge to nearly dead in the span of an hour or so. I kept spare chargers everywhere. Five freakin' phones.
I finally gave in and switched to an iPhone. Now I'm kicking myself for not doing it sooner. Maybe this is a little dramatic, but after using iOS for several weeks I have come to the realization that Android is flat out trash in comparison. I like having an "end call" button that is actually responsive and, you know... ends a call. On Android I would press it several times before the call would end. Just about every time. On too many occasions I had to pull the battery off.
The unresponsive button thing isn't isolated either. Push a button. Wait. Wait. Push it a couple more times. The whole thing is agonizingly slow. Try to unlock the screen. Crap. I have to push the button 3 or 4 times. Arrgghhh!
Don't even get me started on typing. The keyboard would lag on a regular basis, to the point where it was just not practical to use it for texting. I would start to type, the keyboard froze up and then a bunch of special accented characters would show up. Turning off basically every feature of the keyboard like haptic feedback and auto-correction would help, but the typing experience was still the worst of any phone I have used since T9 predictive text has been available.
Apps crashed left and right. I'm not even talking about random stuff from the Android market. I'm talking about the built in ones. I had a task killer installed. It was my most frequently used app. Let that sink in. My task killer was my most frequently used app. I was constantly killing things that were slowing down the phone or eating up battery for no good reason. Search the Android market for task killers. There are tons of them. Some of them run in the background and automatically kill stuff in an attempt to improve performance.
I could go on, but I'd rather not. I'm just glad I don't have to use those Android phones anymore. It will be a very long time before I would consider buying one again.
I've had 4 Android devices, all the ways back to cupcake on the G1. In the early years I absolutely saw the issues that the GP observed, tolerating the platform for secondary reasons while hoping it would get better. I, too, had to pull my battery to end a call more than once. Until Froyo I never recommended Android to non-tech friends or peers. With a modern Gingerbread device I would recommend it in a heartbeat.
But...wow...reading their post is like a blast from the past. jm4 seems to have a really bad sense of timing "buy high sell low!" because Android today is a slick, smooth, reliable platform.
Oh. You probably weren't aware of this, but task killers can cause every problem you list -- app crashing, UI lag, etc.
As soon as I got rid of mine, my phone was much more responsive and had about twice the battery life!
Is that true with current devices? Absolutely not. Gingerbread suffers from zero of the complaints that you mentioned.
"I had a task killer installed. It was my most frequently used app."
You should probably remove this from your post because it betrays that you are an ignorant user. All else follows from that.
While you have edited your post here to temper the zeal, comments like "Android just replaces feature phones" are, well, "fanboy" type comments. Tell my Galaxy S II that.
You're angry about something and are taking it out on Android. No one should draw much from your dated observations.
This story is about a bad device, possibly even a defective handset. Call the press, someone got a lemon!
The GP post originally contained a claim that Android is "garbage", would persist on "feature phones", among other nonse belonging in Engadget comments.
I do wish having an idle skype didn't send packets constantly, though.
Me thinks the better experience saves me at least 93 seconds of pain per day, possible even 2 whole minutes worth.
The touch on my Nexus One (HTC Passion) is horrible the slightest smudge and that's it no touch. I bought my mother an iPod touch a couple of years ago and the touch is fantastic. Actually anyone I know with HTC seems to have problems but not those I know with Android but not HTC hardware.
I played around with a Samsung Galaxy II on display in a store and even after hundreds of people were poking at it and smudged it the touch was flawless.
I've had a few crash on Android OS (v2.3.4 GRJ22) but I prefer it over iOS I find the iPod Touch's GUI suffocating after using Android.
It's definitely Google's problem. Experiences like this tremendously hurt the Android brand. What if you bought a "BMW" but it turned out to be a piece of crap because BMW had licensed their engines and logo but exercised no quality-control over the final products? You'd never buy another BMW, regardless of whose fault it really was.
I'm glad the author's mom found a smartphone she likes, but this isn't an Android problem. It may very well be a Google problem, since Apple was indeed successful in keeping the kruft off the iPhone, but Android devices come to market in a completely different way than iPhones, and as long as we sign over our rights in exchange for a $400 device discount we're going to have to deal with some of it.