Skip to main content
  1. Home
  2. Phones
  3. Android
  4. Mobile
  5. Photography
  6. News

Huawei implied photo shot on 5DMIII was captured with its P9 smartphone

Add as a preferred source on Google

One of the keystone features of Huawei’s P9 smartphone is its dual-camera system. Huawei pushed hard to market the photography aspect of the camera, claiming it was going to “change smartphone photography forever.”

In our own experience with the P9, Digital Trends writer Andy Boxall said the cameras inside the P9 — which were co-developed with Leica — were some of the “finest we’ve used on any smartphone.” And the photos he shared backed up this statement.

Recommended Videos

So you would think that Huawei would have no need to falsify information and inaccurately portray the capabilities of the P9’s camera system. But that doesn’t seem to be the case.

Back on March 8, 2016, Huawei shared a post on its Google Plus page that has since been deleted. In it, the Chinese manufacturer shared an example photo with text that implied the image was captured with the P9 smartphone.

P9 Camera
Image used with permission by copyright holder

As inspiring as the text might have sounded, the data behind the image didn’t seem to line up with it. As the EXIF data tools built into Google Plus showed, the photograph was instead taken on a Canon EOS 5D Mark III camera with an EF 70–200mm f/2.8L IS II lens attached; a $4,500 setup that’s a far cry from the P9 and its Leica-branded camera system.

A closer look at the EXIF data.
A closer look at the EXIF data. (Click to expand.) Image used with permission by copyright holder

Technically, Huawei never explicitly stated that the image was captured with its P9 smartphone. But it does seem highly irresponsible to word the caption in a manner that implied it was.

In speaking to Android Police, Huawei admitted to the misrepresentation and apologized, saying, “The photo, which was professionally taken while filming a Huawei P9 advert, was shared to inspire our community. We recognize though that we should have been clearer with the captions for this image. It was never our intention to mislead. We apologize for this and we have removed the image.”

We’ll leave it up to you to decide whether this was an honest mistake or deceptive marketing.

Gannon Burgett
Former Editor
TSMC might set up a price hike that could come straight for your next phone, laptop, or tablet
Here's what TSMC's rumored 10% chip price increase actually means in dollar terms, and why your next phone or laptop could end up costing more.
TSMC Fab

My wallet flinched the second I saw the words "TSMC" and "price increase" in the same headline, and honestly, yours should too.

Turns out the company behind the silicon powering basically every flagship device out there, including Apple’s A-series and Qualcomm’s Snapdragon processors, is reportedly about to make all of it a little pricier.

Read more
Samsung’s free storage doubling for preorders is gone in Austria, and the replacement isn’t as sweet
Samsung's free storage doubling deal might just be history.
The back of the Galaxy Z Fold 7

If you've pre-ordered a Samsung foldable purely for the free storage bump, tomorrow's Unpacked event might sting a little.

For years, pre-ordering a new Galaxy meant automatically getting double the storage at no additional charge. Buy the 128GB model, walk away with 256GB for the same price. The same applied to the 256GB and 512GB models. However, that might change at the upcoming Galaxy Unpacked event. 

Read more
Apple fixes Hide My Email bug that exposed users’ real email addresses
Here's how Apple's Hide My Email flaw leaked real addresses for over a year, and why it only got fixed once the story went public.
apple-merging-sign-in-with-apple-hide-my-email-icloud+

Turns out the "Hide" part of Hide My Email wasn't doing its job quite as advertised, something that I covered early in July. Security researcher Tyler Murphy reported the flaw in June 2025, but despite Apple claiming it was resolved in March 2026, independent tests confirmed it remained exploitable, at least until July 3, 2026.

So how did this bug actually work?

Read more