OK, I just spent $12,000 on a new home entertainment system at the Sony Style store. I'm still waiting for it to be delivered, but they did give a Sony Tablet S to take home and play with.
My first experience with Android was my Motorola Milestone phone. I was amazed at how simple it was to set up and how well it worked.
My experience with the Sony Tablet S has been much the opposite, and left me wondering:
One of the common symptoms is I keep getting messages like "cannot connect to server" or "server unavailable" from a variety of applications. It took over an hour to configure 3 of my 4 e-mail accounts because of these problems, and I still cannot get the last one configured.
Another problem I had was trying to apply the Android 3.2 update. The connection was impossibly slow and kept cutting out. Only later did I find that the default WiFi setting is to disable WiFi when the screen blanks. Who ever decided on that default deserves a kick in the bum. The default should be disable the WiFi when charger in not plugged in and the screen blanks. In particular, the system upgrade application should be smart enough to do this or warn you to do this. As it was it took me two days to finally perform a successful 3.2 upgrade.
I remember the iPhone 4 had antenna problems which lead to a lot of misery for many people. Does the Sony Tablet S have a pathological antenna design/implementation, or is it just my particular device?
Overall my experience with Android 3.2 and Sony's other features is abysmal compared to my phone. There are many design flaws in many of the user interfaces, in particular insufficient feedback when you are waiting for something - and I seem to spend most of my time waiting for this device to start and/or finish something. I'm a Software Architect and I design and implement graphical user interfaces (among other things) - so dealing with these problems is particularly frustrating because most of the solutions are so simple I can only assume the designers/implementers were too dumb or lazy to care about making this product easy to use with minimal user frustration.
- Eric
My first experience with Android was my Motorola Milestone phone. I was amazed at how simple it was to set up and how well it worked.
My experience with the Sony Tablet S has been much the opposite, and left me wondering:
- Is my particular device malfunctioning?
- Does the Sony Tablet S just suffer from bad design/implementation?
- Does the tablet version of Android just suck in general?
One of the common symptoms is I keep getting messages like "cannot connect to server" or "server unavailable" from a variety of applications. It took over an hour to configure 3 of my 4 e-mail accounts because of these problems, and I still cannot get the last one configured.
Another problem I had was trying to apply the Android 3.2 update. The connection was impossibly slow and kept cutting out. Only later did I find that the default WiFi setting is to disable WiFi when the screen blanks. Who ever decided on that default deserves a kick in the bum. The default should be disable the WiFi when charger in not plugged in and the screen blanks. In particular, the system upgrade application should be smart enough to do this or warn you to do this. As it was it took me two days to finally perform a successful 3.2 upgrade.
I remember the iPhone 4 had antenna problems which lead to a lot of misery for many people. Does the Sony Tablet S have a pathological antenna design/implementation, or is it just my particular device?
Overall my experience with Android 3.2 and Sony's other features is abysmal compared to my phone. There are many design flaws in many of the user interfaces, in particular insufficient feedback when you are waiting for something - and I seem to spend most of my time waiting for this device to start and/or finish something. I'm a Software Architect and I design and implement graphical user interfaces (among other things) - so dealing with these problems is particularly frustrating because most of the solutions are so simple I can only assume the designers/implementers were too dumb or lazy to care about making this product easy to use with minimal user frustration.
- Eric