Let me just start off with a tiny bit of background. The first thought that many people will have when reading that headline is that I must be some kind of Apple fan-boy. I would counter that with some personal history.
I love Linux. Or rather, I love Linux in certain situations. I've used it quite extensively for years, both in desktop and server functions. I've built web servers, mail servers, DNS servers, and file storage. I've waded through the dependency tangles on the desktop and fought to get the wireless working on many many laptops. (Remember the Broadcom wrapper installation procedure? I do.) When I had a web design studio, I used Linux exclusively on my machines for roughly a year.
However, I found that when it came to daily functional use, I was spending more time making the system work than I was working at the system. With Linux, I always had some issue for which I would have to find a workaround. Ultimately, I decided that unless I was putting together a purpose-built server, I was wasting too much time tinkering with the OS.
When Android surfaced, I saw a brilliant opportunity for purpose-built devices on open-source software to excel and kick some serious butt. I ran out and bought a Nook Color and rooted it. After a week or two of playing with it, I was again finding that I spent more time getting it to work than I did actually getting to use it.
I figured it was probably just because this device wasn't intended to be used with stock Android. I had rooted it, after all. On top of that, I found the applications for the device to be all over the place in terms of quality or function, or even resolution (more on this later). I found very similar experiences with the handful of Android devices I had to support while I was an IT administrator for several years.
Around this time, I bought a first generation, used iPad for my kids to play with. It has functioned completely flawlessly and still does to this day. Every "app" I buy for it functions as advertised, and they are all designed for this exact piece of hardware, though I understand it is possible to run iPhone apps on the device. I have had zero hardware bugs.
I recently found myself in need of a portable system for writing while I travel, so I started shopping around. I was immediately drawn to the the Nexus7 v2. This thing is a piece of beauty with its amazingly high-resolution screen, thin and light construction, and fantastic battery. Google has put a lot of work into the Play store in the last couple years, which really gave me hope for the application issues. I bought one and did it happily. That part of me that hates being mainstream rejoiced in the ability to figuratively give the finger to the big evil corporation of Apple.
Today, I'm returning it and getting an iPad. No single issue has led me to this point, but rather, a collection of small annoyances has outweighed my desire to have an Android device.
1. Bluetooth is broken.
My intention was to buy a tablet for writing while I travel. I imagined myself propping this thing up in an airport or hotel room, connecting my Bluetooth keyboard, and typing away happily. Unfortunately, what I found was that Android 4.3 (what comes on the Nexus7), has an issue rendering most Bluetooth keyboards completely incapable of functioning.
I couldn't believe it. This seems like it would be a really big deal, but it is yet unresolved. A quick Google search finds that I'm not alone in this. You begin typing and the keyboard goes nuts repeating characters until it decides to stop.
2. Applications suffering from hardware fragmentation.
Google has worked really hard on the play store. I booted it up and it looked fantastic. Things were clearly labelled and buying things was fantastically easy. However, I still found that some applications were just the cellphone versions scaled up. While it doesn't take much effort to uninstall a cruddy app and hunt down another, it is still incredibly annoying. I also downloaded a couple games that crashed when I attempted to run them. I understand that this is because tons of Android devices are out there and it is impossible to build software that will work flawlessly on all of them.
3. Bugginess in both the OS and the applications
This is the biggest annoyance. The touchscreen has decided to become unresponsive at least once a day since I bought it. It will be working fine, but then suddenly finger touches don't count. I have to hold my finger in place for a second for it to register, then sometimes it will register it as multiple touches. A quick reboot fixes the problem, but that is a pain in the butt when you're trying to carry out a task.
When the tablet reboots, it goes through the process of bringing up the lock screen. I don't know about the others out there, but mine does not cleanly transition from boot sequence to lock screen, there is a flickery mess that happens. This is in no way hindering me from carrying out a task, but rather is just another notch in the "this doesn't feel completed" column.
I realize that this isn't necessarily the fault of Android, but my Netflix application has become completely unresponsive several times in the past two weeks. I have uninstalled it and re-installed it, which fixed the issue (twice). Again, not a show stopper, but a pain in the butt. Did I mention that you can't watch Amazon streaming video on it? Well, theoretically you can if you root it and install some unsupported software (which still didn't work on mine), but out of the box you can'y.
I am hoping that I got a lemon. I've owned this thing roughly two weeks and I now have a nasty dead column in the middle of my screen. It isn't completely dead, it inverts colors from elsewhere. If it had worked flawlessly for a year I could almost overlook something like this, but it is two weeks old and already carrying the baggage of the annoyances listed above.
I actually want to love this thing. It is sleek, feels good in my hand, and has a vivid and colorful screen. The sound quality is good, the battery is good, and Android is so close to being something I would hand to my grandmother with confidence. When applications work they are fast, and there's no lag in navigation at all. If I were one of those guys who had to write a review after an hour of hands-on time, I'd be gushing over this thing.
However, I'm faced with the following issues right now:
I can't work on it (I'm not writing a 1,000 word article with the admittedly nice on screen keyboard).
I can't count on it to work correctly when I pick it up.
I really hope that Google digs in and refines this product. I would love to see even half of these problems worked out. I've decided that I'm not in the market for a "fixer upper" right now. I need a device that will actually just do these things. I'll get an iPad and just accept that maybe I'm not one of the cool kids (in my crowd at least).
Over the weekend, I connencted my wife's Samsung Android phone the my computer, which has Samsung Kies software, over USB. My intent was to simply copy some photos and the address book to my PC. I did that, then I was told that a new version of firmware was available and do I want to install it. I made the mistake of clicking "yes."
The download and install took about 30 minutes. But, when the phone started, it locked up and would not boot. It just frize at the AT&T Rethink possible screen. About then, I was thinking about the likely, not the possible.
I tried pulling the battery, but that didn;t help so I called Samsung. They recommended doing a hard reset. I really hesitiated because the phone was unlocked and it runs on T-Mobile. I feared that the phone would one again lock in AT&T. The hard reset worked and didn't lock the phone back on AT&T, but many settings and all the apps got blown away. Fortunately, I was able to restore the most important part, the contacts. I then had to reinstall all the apps, but only a few.
Now, I'll spend the next few weeks tweaking the settings because hte phone beeps a times she doesn't want, like in meetings. Every time I make a change now, I connect to Kies and back up the phone.
I had similar problems once with an iOS upgrade, though not with iOS7.
I've had a Nexus 7 for about 2 years now and have not experienced the screen flicker, unresponsive touchscreen or any other hardware problem. I haven't used Bluetooth much with it, so I can't speak to that. You got bad hardware and should have returned it instantly for exchange or refund.
Android apps are just software and the quality varies a lot because the barriers to entry are much lower than in the iThing universe. That is both a good and a bad thing, but I'll take the freedom and diversity that comes with it.
Two years ago, I changed companies and left my Blackberry behind to get a new smartphone, unwittingly falling into the Android app conundrum. I found that it took about $60 in apps to make my awful Droid Global 2 smartphone acceptable as a corporate device. Then came the hardware/software issues, lockups, slow dialup, and other irritations so numerous I became numb to them. Being an old PC guy, I'm not easily intimidated by glitches and bugs, but I was hoping that they would resolve themselves as I updated software and drivers. After nine months, they did not.
I'm convinced that it takes 6-9 months for most users to find out they really hate their Android devices. After my phone locked up coming into the SLC airport, causing me to get a speeding ticket, I determined that this phone would one day kill me (literally). Fortunately for me, it was time for an upgrade on my Verizon plan, so I took the plunge into iPhone world and haven't looked back. Yes, my geeky friends all bug me about getting a wimpy iPhone because I couldn't hack it in the Wild-West-like realm of Android software, but I'm comfortable in my own iPhone skin.
The primary problem with Android apps is that they are totally unverified by anyone but the developer. A friend of mine who write apps says that most smartphone app developers have a definite strategy -- develop your app for Android first, as they never reject anything. Then, submit your app to the iTunes store, expecting Apple to reject it a few times because it is touching areas of the OS that it shouldn't. Now my geeky software friends tell me that Android software all eventually resolve themselves by popular demand, but why should I waste my time doing all this just so it doesn't take 30 seconds for my smartphone to dial a contact? When I want to dial up a friend, I don't want the phone to run off check his Facebook status - just dial him up, and NOW!
There's no way you can tell me that bodacious processors alone with solve the problem of sorry software. If the Android community ever somehow gets a software-vetting process in place, then I might come back. For now, I'm an Apple guy.
This should really be updated with the new Nexus 7! All the ipad owners have to scowl at me as I have my keyboard/mouse combo RDPing my desktop and running Solidworks. Of course, the 7 inch screen means that for the 1900X1200 pixels, you really need a set of magnifiers to distinguish each and every pixel. there are no problems whatsoever with my $20 bluetooth keyboard. But I must admit, my PC bluetooth mouse is a bit finnicky. Don't understand why a company as big as Google can have issues with a 20 year old bluetooth protocol. But in the end, it is much more portable than an ipad, has more functionality, and is much less expensive...
I now have a nexus7 and an ipad. My kids generally prefer the ipad for the bigger screen but have used the nexus7 a few times too. The netflix app has locked up a couple times on them on the nexus7 but aside from that it has been uneventful. I don't think they really care.
I used my son as a lab rat and Galaxy Tab 10 won. A year ago I gave him an inexpensive Viewsonic Android tablet. At the age of 11 I figured he'd be a good judge of how it felt and worked. (I personally did not like it and would never use it, but I wanted to see if he could find a use for it).
After a few days he pretty much threw it aside (touch was unreliable, and other things, it just felt cheap.) I then did what I intended to do anyway: I bought him a Samsung Galaxy Tab 10 that was on sale in CostCo. He hasn't put it down since. (Be careful what you wish for, right?)
He uses it for games, staying in touch with friends, scout updates, exploring places to travel next, you name it. Not once has it let him down. I still get to use it myself, and the Play store is useful for what I need, tho I'm not a big apps user on it.
I could have rooted the Gtablet, as it has a great processing core and tons of memory, but did I really want to spend my time on that? The answer is yes, but I couldn't. Too much to do elsewhere. No time for optimizing, as satisfying as that would have been.
The Samsung Galaxy is my choice as I favor the 'open market', but it's all in how it's implemented, and Samsung doesn't mess around. They set the standard for any device that wants to compete with Apple.
Not all of us live in your fantasy world where we can just turn work off for weeks on end. That may be possible in large companies where every job is somewhat backed up by 3 other people, but in many companies, there is no one for things to fall back on .... and hence emails do get checked on vacation. Personally, when I do not work, I do not get paid, and customers (yourself included no doubt), do not like waiting ... no matter the reason.
David Patterson, known for his pioneering research that led to RAID, clusters and more, is part of a team at UC Berkeley that recently made its RISC-V processor architecture an open source hardware offering. We talk with Patterson and one of his colleagues behind the effort about the opportunities they see, what new kinds of designs they hope to enable and what it means for today’s commercial processor giants such as Intel, ARM and Imagination Technologies.