Skip to main content

Samsung Galaxy Tablet 2 Review

Recently, through sheer blind luck, I was able to get a hold of one of these excellent little devices. A friend sent it down (he prefers his iPad) so I was able to play with it a bit before handing over to the wife for her amusement. The Galaxy Tablet is a 7" tablet, much like the Google Nexus I recently reviewed and use almost continually. At first blush here are the differences I noted:

  • the user interface is different (naturally). I feel that the Galaxy's is more polished, looks crisper but is a lot more busy. The QWERTY keyboard interface for example has the numbers above it and the keys are smaller on screen than the Nexus.
  • SD Card slot - upgradeable storage is a nice thing indeed.
Weight, size and battery life appear comparable. My wife loves it. She wasn't convinced initially about a tablet and didn't think she could find a use for it. As a non-technical person it seemed like another gadget to her. Now though she uses it for Pinterest, Facebook, eBay, email and generally web searching.

The Galaxy Tablet is a fine piece of hardware, but I have to criticize the interface. It is not as user friendly as the Nexus and this was actually a factor that led me to purchase a HTC One X over the Samsung Galaxy SIII recently. Navigating through some of the menus has been a pain, and initially finding in the Yahoo Mail app the Create Email option was not straightforward at all. That being said, now I've played more with it it's quite good.

I recommend the Galaxy Tablet to anyone who needs 3G or LTE connectivity as the Nexus doesn't appear to offer this. WiFi connectivity is very good on both devices and the Galaxy has a bright easy to read screen. Occasionally the light sensitivity gets a bit annoying as it dims the screen unnecessarily, or makes it too dark, but otherwise it's very good.


Popular posts from this blog

Plone - the open source Content Management System - a review

One of my clients, a non-profit, has a lot of files on it's clients. They need a way to digitally store these files, securely and with availability for certain people. They also need these files to expire and be deleted after a given length of time - usually about 7 years. These were the parameters I was given to search for a Document Management System (DMS) or more commonly a Content Management System (CMS). There are quite a lot of them, but most are designed for front facing information delivery - that is, to write something, put it up for review, have it reviewed and then published. We do not want this data published ever - and some CMS's make that a bit tricky to manage. So at the end of the day, I looked into several CMS systems that looked like they could be useful. The first one to be reviewed was OpenKM ( ). It looked OK, was open source which is preferable and seemed to have solid security and publishing options. Backing up the database and upgradin

Musings on System Administration

I was reading an article discussing forensic preparation for computer systems. Some of the stuff in there I knew the general theory of, but not the specifics of how to perform. As I thought about it, it occurred to me that Systems Administration is such a vast field. There is no way I can know all of this stuff. I made a list of the software and operating systems I currently manage. They include: - Windows Server 2003, Standard and Enterprise - Exchange 2003 - Windows XP - Windows Vista - Windows 2000 - Ubuntu Linux - OpenSuSE Linux - Mac OSX (10.3 and 10.4) - Solaris 8 - SQL 2005 - Various specialised software for the transport industry I have specific knowledge on some of this, broad knowledge on all of it, and always think "There's so much I *don't* know". It gets a bit down heartening sometimes. For one thing - I have no clue about SQL 2005 and I need to make it work with another bit of software. All complicated and nothing straightforward. Irritating doesn&

Traffic Monitoring using Ubuntu Linux, ntop, iftop and bridging

This is an update of an older post, as the utilities change, so has this concept of a cheap network spike - I use it to troubleshoot network issues, usually between a router and the network to understand what traffic is going where. The concept involves a transparent bridge between two network interface cards, and then looking at that traffic with a variety of tools to determine network traffic specifics. Most recently I used one to determine if a 4MB SDSL connection was saturated or not. It turned out the router was incorrectly configured and the connection had a maximum usage under 100Kb/s (!) At $1600 / month it's probably important to get this right - especially when the client was considering upgrading to a faster (and more expensive) link based on their DSL provider's advice. Hardware requirements: I'm using an old Dell Vostro desktop PC with a dual gigabit NIC in it - low profile and fits into the box nicely. Added a bit of extra RAM and a decent disk and that&