Detailed specifications of two upcoming Samsung tablets have just surfaced. The third generation of the Galaxy Tab mid-range lineup will feature a couple of slates armed with a 10.1" and an 8" display, respectively. Interestingly, the picture that came along with the leak confirms the hardware home button, which is still unusual for Android slates.
Samsung Galaxy Tab 3 10.1
The Samsung Galaxy Tab 3 10.1 will run on Andrdoid 4.1 Jelly Bean and will be powered by a 1.5GHz dual-core CPU and will have 1GB of RAM. That might as well be a typo as the Galaxy Tab 3 8.0 is said to have 2 gigs of operating memory. Unfortunately, earlier reports of a 2560 x 1600 pixel display weren't confirmed and the new rumors point to a resolution of just 1280 x 800 pixels.
The Galaxy Tab 3 10.1 will reportedly have 16GB of internal memory, which will be expandable through the microSD card slot. Connectivity options will include Bluetooth 4.0, Wi-Fi, standard microUSB port and, depending on the version, HSPA or LTE. Power will be supplied by a 7,000 mAh battery, while imaging will be taken care of by a 3MP main camera and a 1.3MP front-facing snapper.
The larger of the two upcoming slates will reportedly measure 256.7 x 175.3 x 8.7 mm and weigh just 533g. That will make it both thinner and lighter than the Galaxy Note 10.1, which is the current Samsung flagship tablet.
Galaxy Tab 3 8.0
Moving on to the Samsung Galaxy Tab 3 8.0, we learn that it will feature the same CPU as its bigger brother. The 8" display will have a resolution of 1280 x 800 pixels and will be your window to Android 4.1 Jelly Bean at launch.
Connectivity options and cameras are the same as on the Galaxy Tab 3 10.1, while the battery has been trimmed down to 4,500 mAh capacity. If the rumors turn out true, the Galaxy Tab 3 8.0 will be impressively slim at 6.95mm, but will weigh 330g - about the same as the Galaxy Note 8.0.
The 3G versions of the Galaxy Tab 3 duo are expected to come to the market in May, while the 4G units will go on sale in June-July. Pricing of either device is unknown at this point.