Samsung launches Galaxy J3(6) in China
And it’s unclear whether Samsung is planning to bring the SM-W2016 to the European or U.S. markets but let’s hope so, because I’m excited at the prospect of playing a businessman circa 2002.
The company has been releasing several hundred phones with each phone aimed towards a different price point.
The smartphone was officially introduced in China and carries model number “SM-J3109”. But it looks like the internet’s nostalgia boner may soon be relieved, as multiple sources have confirmed that Samsung is getting ready to launch a bonafide, high-tech clamshell phone.
The J series of smartphones have paved the way for Samsung to offer entry level devices, especially in developing markets such as India.
The Android 6.0 upgrade status for a slew of Samsung handsets such as Galaxy Alpha, A5, A3, E7, E5, J7, J5, and J2 are shown as “waiting approval”.
After a stint at the FCC, and then at the FCC-equivalent in China, the Samsung Galaxy J3(6) is now official. The third variant is expected to be a surprise and is expected to be power packed with many high end features. It should feature two 3.9-inch Super AMOLED displays each with 1280 x 768 resolution. Under the hood, there is a 1.2GHz quad-core processor along with 1.5GB of RAM and 8GB storage. It runs on Lollipop 5.0.2 out of the box, but it will most likely receive the Marshmallow update in the near future. There’s also a secondary 5-megapixel selfies camera in the front. Overall, the smartphone measures 142.3 x 71 x 7.9 mm, and weighs 138 grams. We’ve been hearing various claims in this regard so far, but we don’t really have any concrete information about the full picture of what Samsung are planning.
Talking about the connectivity options, the device does support 4G LTE network and few other sets of options such as Wi-Fi, Bluetooth, and Global Positioning System.
What’s more astonishing is that Samsung has added the fast wired or wireless charging support on his handset, which tells that the small 2000mAh battery might not be an issue here.