I’ve been playing around with an SGS3 for a couple weeks now, and I must admit that I’m pretty impressed with this device.
I’m one of those early android adopters that bought an HTC Hero and I’ve been using it for around 4.5 years. I know that it has really old hardware and it’s many Android versions older than this SGS3 device, but I was using it primarily as a phone (making calls/SMS) and as an application tester, so it worked well and had good battery life.
I’m not going to do here a device review (because I’m sure that you can find a lot of those), and I’m just going to point out what for me is this device killer feature:
When you have a screen as big as this, you don’t scroll pages as often as you would on a device with a smaller one. Without this feature, I believe that it would be really annoying having to touch the screen every 30s just so it wouldn’t go to sleep.
I believe that Samsung got it right, and I believe that this feature should be in all tablet devices too!
One thing maybe (or maybe not) you’ve noticed is that you can’t delete an entire directory using DDMS on eclipse.
To be able to delete a directory on simulator sd card you can use the ADB command and connect to device via shell.
The first thing to do, is to go to “<android-sdk-PATH>/platform-tools” and from there type:
Then connect via shell to the device that you want:
./adb -s emulator-5554 shell
Now you’ve connected to the device “emulator-5554″ and now you can remove the files or directories that you want!
I’m an ASUS Transformer proudly owner, and even though I still didn’t receive the most promised ICS update for my Transformer (is due to March), I’m already a bit disappointed at Google Design decision to maintain its fixed bottom Status Bar.
The Honeycomb was the first Android version for tablets and the idea of removing all the hardware buttons and use only software buttons looked really the best way to go but now with almost a year of using it, I start to realize it’s disadvantages.
First it will reduce the available screen height and second it’s prone to miss touching on those buttons when what you really want is to tap on some button that is on the bottom of the application.
This limitation is already addressed in this issue http://code.google.com/p/android/issues/detail?id=15408 but it’s marked as WorkingAsIntended. If you are one of us that think that this is a huge design limitation, please express your thoughts in there!