Camera - Stills and Video

The Droid 3 includes a nicely improved rear-facing 8 MP camera. Without doing much more than looking at the back of the device, you can see that gone is the dual-LED flash system, and in its place is a single LED solution which seems to be equivalently bright. For comparison, recall that the Droid 2 had a 5 MP rear facing camera and no front facing camera.

I did some poking around and discovered that the Droid 3 uses an OmniVision OV8820 for its rear facing 8 MP camera, and an OmniVision OV7739 for its front-facing VGA camera. OV8820 is relatively par for smartphone 8 MP sensors, at 1/3.2” size and capable of delivering both 1080p30 and 720p60. Pixels on the OV8820 are 1.4 microns square and backside illuminated (thinned using OV’s back-grinding process) just like their other comparable sensors.

The front-facing OV7739 is again VGA, and designed with package thickness (just 3 mm) in mind. It can capture VGA at 30fps and QVGA at 60fps. Of course, the VGA sensor is correspondingly smaller at just 1/7.5” with 3 micron square pixels.

We did the usual thing and took photos with the Motorola Droid 3 at our test locations (which continue to be in a state of flux, with a few spots totally inaccessible - only 3, 4, 6 and 7 are left), in our lighbox with and without the LED flash for comparison, and some general everyday photos around town. Stills taken on the Droid 3 are much improved over the Droid 2. By comparison, the Droid 2’s lightbox photo looks noisy and lacks much dynamic range in the dark camera barrel. Note that I maintain the distance from camera to subject, and the difference in apparent size comes from a change in focal length from 4 mm on the Droid 2 to 4.6 mm on the Droid 3.

With the lights on, the Droid 3 is a definite improvement over the Droid 2 and other 8 MP smartphone cameras. However, with the lights off, it's often a crapshoot. The software doesn't pre-illuminate the scene for autofocus, instead only flashing a quick autoexpose test flash and then the photo. As a result, it took many, many attempts to get an even questionably focused shot in the dark. 

Stills on the Droid 3 are captured at 3264 x 2448 size when the 4:3 aspect ratio is selected, which I guess brings me to the next set of things that are changed - the camera application. With the camera shutter button gone, the Droid 3 camera UI now features a shutter button center on the right side of the UI instead of top right. There’s a button for toggling the front and rear facing camera, and down below between still and video.

Hit menu, and you can see what else is different. The menus have been consolidated into a single strip which goes along the bottom of the camera UI. The same core camera functionality remains - camera effects (filters), a few shooting modes (scenes), panorama, brightness, and flash modes. What’s changed is that the shooting resolutions and modes are now super simplified - what remains are a widescreen (6 MP) and non-widescreen (8 MP) capture mode, and nothing more.

It’s a very Apple-like approach (whose iOS camera has no resolution options), and I think it makes sense, since most of the time there really isn’t a reason to capture in anything but the highest resolution. Maybe a 2x2 binned-mode resolution for more light sensitivity would make sense, but nothing outside those two sets seems requisite considering it’s all just a software decimation at that point anyhow.

The Droid 3 allows for above average capture speed. I was able to mash the capture button on numerous occasions and capture as fast as the button appeared after the extremely short preview and shutter animation finished. The Droid 3 certainly seems faster than the Android paradigm of capture, preview (and covertly write out the buffer), then allow for another frame to be captured, which often takes 5 or more seconds. I show the Droid 3 shooting video pretty quickly in our video review overview.

Regardless, the Droid 3’s improved camera now is up to par and slightly better than the competition 8 MP cameras based on Samsung sensors in some of HTC’s phones in the right conditions. One thing is certain though, things have improved considerably since last year’s 5 MP and 8 MP cameras took stage.

The next subject is of course how video capture fares on the Droid 3. The two most interesting Droid 3 video shooting modes are 720p30 and 1080p30, which record at bitrates of 10 and 15 Mbps, respectively, with 128 Kbps, 44.1 KHz AAC stereo audio.

What’s impressive about the Droid 3’s OMAP4430 SoC is that it can encode high profile H.264 video. Though there’s still only 1 reference frame and no B-frames, that’s still much better coding than what Tegra 2 or Snapdragon have to offer with their baseline encoders. In addition, the OMAP4 video encoder implements 8x8 size macroblock partitions (8x8DCT), which enables considerably better quality and better encoding than the default 16x16 that other baseline encoders are using. According to further OMAP 4 documentation, it’s possible for the IVA-HD encoder in OMAP4430 to work at up to 20 Mbps 1080p30.

Samsung’s Exynos is the only other SoC I know of that does high profile H.264 encoding (17 Mbps, CABAC, 1 reference frame), every other SoC we’ve seen to date just does baseline. At this point, it looks like OMAP4’s video encoder is definitively better than both Tegra 2’s and Snapdragon’s.

 
 

I again did the usual thing and shot some videos with the Droid 3 at our test location, and zipped them up for your perusal, but per our media streamer and video guru Ganesh’s suggestion, decided to tweak things around for an even better comparison. In addition to the normal test location video, Ganesh suggested shooting video on the device-under-test alongside a reference camera for comparison. I grabbed a dual bracket camera mount, smartphone mount, and monopod and headed out to shoot some side by side video with the Droid 3 alongside a Canon Vixia HF11 I use.

Droid 3 Video

Vixia HF11 Video:

Originally I thought the Vixia HF11 I use was shooting 1080p30, however it turns out that even in 30p mode it actually is capturing 60i. Originally Ganesh and I were concerned that the Droid 3’s video looks juddery, it turns out that this shudder/jitter is just because of the difference in 30p (Droid 3) and 60i (Vixia). The Droid 3 is again impressive, easily capturing the top quality crown in our opinion for smartphone video quality. Well deserved kudos to Motorola and TI with the OMAP 4430 encoder. You can download the zip of the HF11 and Droid 3 videos shot on the same bracket and play them back on your own as well.

Display - 4" qHD with PenTile RGBW Cellular and WiFi Connectivity, GPS
Comments Locked

84 Comments

View All Comments

  • jigglywiggly - Saturday, July 30, 2011 - link

    i'd sell myself

    This phone lux nice, do want, I just wish it was on at&T
  • 7amood - Saturday, July 30, 2011 - link

    why don't I see any galaxy s2 in the comparison charts and where is the galaxy s2 review from anandtech?? :/ *waiting*
  • Brian Klug - Saturday, July 30, 2011 - link

    We actually just got an SGS2 in this week (international version) and I'm busily working on the review for that device ;)

    -Brian
  • Omega215D - Saturday, July 30, 2011 - link

    I got to spend some time with this phone and it is pretty nice but doesn't feel as solid as the Original Droid nor look as elegant. Thankfully the Droid 3 got it where it counts performance-wise. The phone crashed when activating the camera and required a battery pull but that was only once. If I didn't have my Thunderbolt (which is doing well on battery life now) the choices would be Droid Incredible 2 or Droid 3 as they are both international phone. That would change if Verizon decides to get more WP7 phones.

    I liked the review. It's very detailed and unbiased, unlike the sorry excuse for a review from PhoneArena which shows it's clear Apple bias.
  • Johnmcl7 - Saturday, July 30, 2011 - link

    I'm extremely disappointed there's not even one phone of this class and type for sale here, there's rumours of an HTC Doubleshot with a keyboard but still no sign of it. I've been trying the software keyboard on a Tab for a while but I can't stand it, I much prefer the N900's physical keyboard which leaves me stuck for the moment for an upgrade.

    John
  • Brian Klug - Sunday, July 31, 2011 - link

    I guess you could always spring for the Chinese version, but hopefully there's a Milestone international version equivalent coming soon.

    -Brian
  • piroroadkill - Saturday, July 30, 2011 - link

    Aw man, even my Desire HD has 768, and it actually gets put to use.
    Why cheap out, Motorola?

    That said, as much as this looks great, I'd never recommend it due to Motorola's anti-modding community stance. Oh well.
  • Ben - Saturday, July 30, 2011 - link

    I'm wondering if "The Droid 3 has excellent ambient noise cancellation during calls, again thanks to the two extra antennas which are no doubt used for processing. I’m not sure what IP is beyond the Droid 3’s noise rejection hardware, but clearly it does a good job."

    Should read as "The Droid 3 has excellent ambient noise cancellation during calls, again thanks to the two extra microphones which are no doubt used for processing. I’m not sure what IP is behind the Droid 3’s noise rejection hardware, but clearly it does a good job."
  • Brian Klug - Saturday, July 30, 2011 - link

    Yeah I got antennas and microphones sort of confused there, thanks! Fixed now!

    -Brian
  • Bob-o - Saturday, July 30, 2011 - link

    It's awesome they included a row of numbers at the top, I hate switching when entering mixed input. But why, oh why did they not put the usual secondary symbols on the number keys??! You know, !, @, #, $, etc. That's standard!!! What were they thinking??! Groan. . .

    Also:

    > What feels neglected is how anemic the hardware keyboard auto-replace engine is.
    > Compared with the gingerbread and even Motorola multi-touch keyboards, the hardware
    > keyboard has an almost non-existant auto-replace engine for fixing misspelled words.

    This makes me question Android's software stack. Why would each device (whether physical or virtual) have to implement this functionality? This should be a filter on input, no matter what device the user is using to enter data. . . and so it should work identically no matter what keyboard is being used. Stupid.

Log in

Don't have an account? Sign up now