Last month, a mysterious Honor smartphone with model number LRA-AL00 has been certified by the Chinese 3C authority. This device, according to reports out of China, is believed to be the upcoming Honor Note smartphone which will make it’s debut alongside the Honor V30 and V30 Pro. However, there are also recent indication that this device could be the upcoming Honor 20 Youth Edition or Honor 20 SE, due to it’s relatively smaller screen size.
Today, the Honor LRA-AL00 has also been certified by the Chinese TENAA authority. As usual, the device’s listing had revealed most of it’s key specs which most of us are interested in.
First and foremost, the upcoming Honor LRA-AL00 smartphone will feature a 6.3-inch OLED display with 2400 x 1080 pixels screen resolution. It has an overall footprint measuring 157.2×73.2×7.65 mm and weighs approximately 172.5 grams.
The device seems to be driven by an octa-core Kirin 810 SoC, paired with up to 8GB RAM and as much as 256GB onboard storage space. If that’s insufficient to you, the internal storage can be further expanded by up to 256GB with the use of microSD card.
Moving on to it’s camera, the device will arrive with a 48MP+8MP+2MP triple-camera setup on it’s back panel. Initially, the device is said to have a 64 megapixels main snapper which doesn’t seems to be the case according to it’s TENAA record. At the front, there will also be a 16 megapixels selfie camera.
The Honor LRA-AL00 will be fueled by a 3,900mAh battery which will support 20W fast-charging. For those who’re interested, there are two color options available for the device including Black and Green.
As usual, the upcoming Honor LRA-AL00 smartphone will not be shipped with Google Play apps and services out of the box. Similar to the case of the Mate 30 smartphones, it will make use of Huawei Mobile Services (HMS) instead of the typical Google Mobile Services (GMS).
Initially, an easy workaround for installing Google apps on Huawei and Honor smartphones using LZ Play was discovered. However, reports have claimed that this workaround is no longer working.
