The Samsung Galaxy Tab 10.1 was first revealed back in March and is the bigger brother to the original Galaxy Tab 7, with a much larger 10.1″ display running at 1280 x 800 px (WXGA), a 1Ghz Nvidia Tegra2 (Dual Cortex A9) processor and 1GB RAM. Android Honeycomb 3.1 is on board bringing the first version of Android with the new tablet enhanced features. Storage options are 16GB, 32GB or 64GB however there is no MicroSD slot for increasing it beyond this. Samsung uses the same proprietary 30 Pin connector from the original Tab so although there is no standardised Micro USB at least Samsung is staying consistent with their own cables and the 10.1 will work with many of the original 7’s accessories.
Measuring 256.7 x 175.3 x 8.6 mm the Tab 10.1 is actually 0.2mm thinner than the iPad2 and weighing 565g its also 36g lighter, so the larger screen real estate will actually feel lighter and easier to handle when compared to the iPad2 something Samsung has clearly targeted.
The usual connectivity options are present Bluetooth 3.0 and WiFi a/b/g/n on board, along with A-GPS, digital compass and gyroscope. The front facing camera is 2MP and the rear facing camera is a 3MP Auto Focus with LED flash for low-light capture.
Its the cameras that have given the Tab 10.1 has an interesting fan in photographer and blogger Fats Shariff also known as Fatsarazzi. In part of a series of videos on the Samsung Galaxy Tab YouTube channel – www.youtube.com/samsunguk – Fatsarazzi talks about how he uses his Galaxy Tab 10.1 in both his professional and personal life.
The large size of the device would make you think the Tab 10.1 is not ideal for photography, but Fatsarazzi makes a good case for using it in many situations, and the large screen makes reviewing the images in detail afterwards as easy as on a monitor. Also with the huge array of image editing software available in the Android Market Fats demonstrates the ease with which he can adjust the just-taken images to crop or add effects (not all image Apps will run full screen on the Tab yet, but this is a Honeycomb limitation and should be fixed in the 3.2 update).