LG has unveiled its new G Pro 2 smartphone, promising that the Android handset's 13MP rear imaging sensor will outperform those on rival smartphones and standalone compact cameras.
The camera features LG's custom Optical Image Stabilizer Plus (OIS+) technology, Magic Focus and Natural Flash custom shot options.
Magic focus is a custom option that lets users select their preferred depth of focus before saving an image. The shot mode also features an ‘All in Focus' option that tells the G Pro 2's camera to make every object in the frame as sharp as possible.
Natural Flash is similar to the custom dual-LED flash seen on the iPhone S. The mode is designed to improve the camera's flash to make colours look more balanced and realistic.
The LG G Pro 2 will run using a powerful 2.26GHz quad-core Qualcomm Snapdragon 800 processor, boast 3GB of RAM and run using an altered version of Google's latest Android 4.4 KitKat operating system (OS).
LG's loaded the OS with advanced Content Lock and Dual Browser features to boost the G Pro 2's enterprise appeal. Content Lock lets users lock files, photos, videos and memos with a unique password, while Dual Browser splits the G Pro 2's 5.9in full HD, in-plane switching (IPS), 1920x1080 screen to display two separate web browser windows.
The G Pro 2 will also include a custom Knock Code feature. Knock Code lets users set the G Pro 2 to unlock to one of 86,367 screen tap combinations.
The G Pro 2 will measure 158x82x8.3mm and will be powered by a removable 3,200mAh battery. The G Pro 2 is currently only confirmed for release in Korea, though LG promised to announce further details about launching the smartphone in other territories at Mobile World Congress (MWC).
Check back with V3 from 24 February for live coverage of MWC 2014.
ZenFone 5 Pro appears to boast a Snapdragon 845 SOC, an Adreno 630 GPU and 6GB of RAM
Pilot project will serve 300 homes to start with
The IoT faces significant compatibility challenges, which could be avoided for blockchain by adopting Hyperledger
Software engineers found the data writing bug via sparse disk images