What you need to know
- Xiaomi's entry-level Redmi 9A and 9C smartphones are now official.
- The Redmi 9A comes with a MediaTek Helio G25 chipset, a single 13MP rear camera, and a 5000mAh battery.
- Redmi 9C features a slightly more powerful Helio G35 chipset and a rear-mounted fingerprint sensor.
Xiaomi Malaysia today quietly announced the Redmi 9A and Redmi 9C entry-level phones. Both phones are powered by MediaTek chipsets and promise excellent battery life.
The new Redmi 9C comes with a 6.53-inch HD+ display featuring a waterdrop notch cutout with a 5MP selfie camera. It is powered by a MediaTek Helio G35 octa-core chipset, paired with 2GB RAM and 32GB storage. The phone has a triple-camera on the back with a 13MP main sensor. It also comes with a rear-mounted fingerprint sensor and a massive 5,000mAh battery.
Redmi 9A, on the other hand, runs on a slightly less powerful MediaTek Helio G25 chipset, clubbed with 2GB of RAM and 32GB storage. It also has a single 13MP camera at the rear. Like the Redmi 9C, the Redmi 9A has a 6.53-inch HD+ display with a 5MP selfie camera housed within the waterdrop notch at the top. The rest of the phone's key specs are also identical to the Redmi 9C. The only notable difference is the omission of the fingerprint sensor.
The Redmi 9A has been priced at RM359 ($85) in Malaysia and will be available through Lazada (opens in new tab) starting July 7. Redmi 9C will be going on sale in the country by the end of July for RM429 ($100). While Redmi hasn't confirmed any details yet, the Redmi 9A and Redmi 9C are expected to soon make their way to a few other markets such as Europe and India.
The infographic for the 9C shows 13MP AI triple rear camera, contrary to the text of the article.
Two new affordable smartphones with new Mediatek gaming chipsets is a good news for customers looking for powerful phones without burning a hole in their pockets
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.