During its press event at IFA, Honor unveiled its next flagship smartphone — the Honor Magic 2.
This "announcement" was really more of a tease than anything else, but even so, it would appear that Honor's got something exciting up its sleeves.
Following up on the first Honor Magic that was released in 2016, the Magic 2 features a nearly bezel-less display with no notch in sight. Similar to the Oppo Find X from earlier this year, the Honor Magic 2 has a slide-up design that houses its cameras and allows for its "nearly 100% screen-to-body ratio."
Honor's calling this its "intelligent Magic Slide system", and once it's activated, you'll have access to some sort of AI features — a big theme that was present with the first Magic.
It's been confirmed that the Honor Magic 2 supports 40W charging and is the first Honor phone to be powered by the Kirin 980 processor, but aside from those two tidbits, everything else about the phone is still up in the air — including pricing and availability info.
The first Honor Magic was focused on the Chinese market and never came to the U.S., so don't get your hopes up just yet about owning the phone yourself.
I still think I like Vivo implementation of the hidden camera but I'm glad to see phones with no notches, even though they never bothered me except for the PXL3 camel toe. Some will argue the pop up camera which I do agree. I still think that a phone with full screen front and small display on back for "selfie" for those who care would be the best thing I would like to see. Something like the Meizu Pro 7 did. A small back screen to me is better than a mechanical pop up anything.
And for video calling?
Can't please everyone.
Between slide-up cameras, huge notches, and fragile glass, I can't decide which I hate more.
Yay to a manual slider, just like the sliding keyboard of the open days. Those lasted as long as the phone itself.
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.