Camera - Stills and Video

I sound like a broken record here with how many similarities there are between the Bionic and the Droid 3, but camera is another of them. The Bionic has a rear facing 8 MP camera with single LED flash and autofocus, and captures stills at a maximum resolution of 3264 x 2448.

The rear sensor is based on an Omnivision OV8820 CMOS sensor which is backside illuminated, 1/3.2" in size, and has 1.4µm square pixels. This is a very modern sensor behind an optical system with F/2.8 optics and a 4.6mm focal length. If that sounds familiar, it’s because this is exactly what’s inside the Motorola Droid 3 as well.

The front facing camera is home to a rather less interesting VGA (0.3 MP) fixed focus CMOS sensor. In this case, it’s an Omnivision OV7739 with 3.0µm square pixels which is 1/7.5" in size. I’ve found all of these drivers and configuration files again lurking deep inside /system on the Bionic.

The Bionic also has the same exact camera application, though subjectively it seems a lot more finicky on the Droid Bionic. In still image shooting mode, one can toggle between widescreen 16:9 aspect ratio 6 MP or the sensor’s native aspect ratio 8 MP, there aren’t any other options for lower resolutions. The other options are for toggling storage location, shutter noise, and video capture resolution. There are the usual assortment of other toggles on a ribbon down at the bottom - effects, scenes, modes, brightness, and flash settings.

The Droid Bionic shoots pretty decent photos, the problem that I have with this is the software. It takes a while to get into the camera application, and there’s a lot of shot to shot variance in speed. The other problem is that the Bionic seems to miss focus a lot more than I remember the Droid 3 doing - occasionally it’ll just blow off the long press on capture button and take the picture before AF finishes. This is maddening at times and downright frustrating at others since you’ll need to capture two or three to get one where AF has settled down, you can see this behavior below for yourself.

We’ve taken photos with the Bionic at the usual test location, and in the lightbox, with the lights on and off. Just like the Droid 3, the Bionic doesn’t illuminate the scene when running AF in the dark, so often it’ll expose perfectly but capture a blurry image. I’ll let you be the judge of image quality, it’s just like I saw on the Droid 3.

In video mode, you get the same layout, however instead the new options are audio scenes, video shooting duration, and an on/off toggle for LED lighting. Options for video shooting are pretty simple - 1080p30 at 15 Mbps, 720p30 at 10 Mbps, and a few others. For both of these, high profile features are used like we talked about in the Droid 3 review. You can actually see all of these configured from build.prop on the Bionic:

ro.media.camcorder.1080p=mp4,h264,30,15000000,aac,128000,44100,2 ro.media.camcorder.720p=mp4,h264,30,10000000,aac,128000,44100,2 ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2 ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2 ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2 ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2 ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1

Resolution, extension, video compression standard, framerate, video bitrate, audio codec, sampling rate, and number of channels. It’s all right there in that order presented nicely in build.prop just like so many other Android devices.

 

I’ve also captured sample video at the usual place from the front and rear facing cameras. Video quality is very good, though the Bionic does run that AF routine a lot on the rear facing camera while shooting 1080p video. Again OMAP4’s encoder implements some nice high profile feature, but still only uses 1 reference frame where 2–4 would ensure better encoder efficiency. I’ve also uploaded native samples from the Bionic to our server for you to watch without YouTube’s transcoding.

Display - Same as the Droid X2 Performance - OMAP 4430
Comments Locked

64 Comments

View All Comments

  • steven75 - Tuesday, October 11, 2011 - link

    Except for the waiting for your battery to charge, as proven in the tests above.
  • Omega215D - Tuesday, October 11, 2011 - link

    Not all of us have that issue with LTE. Granted the battery life isn't something worth writing home about but it's sufficient, especially after receiving Gingerbread on my Thunderbolt. On my original Droid and my brother's iPhone 4 there were times when the system would be pegging the EVDO constantly when loading some web pages thus putting more strain on the battery.
  • kepler - Tuesday, October 11, 2011 - link

    I would be interesting to see how much data is consumed during the tests. If the LTE phone is consuming 4x the data, but lasting half the time, that is arguably 2x increase in possible productivity.
  • Aikouka - Tuesday, October 11, 2011 - link

    I'm assuming that there isn't much difference between the data. LTE modems simply seem to be power hungry, so running a constant stream of data will show pretty high battery use.

    This knowledge is good for some users, because for people that like to stream things like Pandora, they may consider turning off LTE (LTE isn't really required for streaming music). But what came to my mind while reading the article is that **constant data use tests** don't necessarily mimic the actions that all users take.

    It'd be interesting if we could see power characteristics related to a single action. For example, how many YouTube videos could I load throughout a single charge of the battery? If the LTE-equipped phones can load 200 vs. 50 on EVDO (completely made-up numbers) simply because LTE provides significantly faster speeds, then that shows a rather large multimedia advantage.

    Even without such a test, I think it's pretty easy to see that while LTE is pretty amazing to see in a phone... there's a lot of micro-managing that you may have to consider doing to see the sort of battery life that we've come to expect out of a phone.
  • secretmanofagent - Tuesday, October 11, 2011 - link

    One thing that I would like to point out (and I think it's specific to Blur and worth mentioning) is the ability to dismiss individual notifications instead of having to open each individual notification or clearing all of them. I love that feature on the Bionic.

    I have seen some data connectivity issues with it where I will randomly lose all data and be unable to recover it until I reboot the phone (airplane mode doesn't fix it). This can happen at any point in the day or night, and I'm having my phone exchanged.
  • anandtech pirate - Tuesday, October 11, 2011 - link

    nah, that's okay. we don't wanna see your face.... :-p

    almost all phone reviews only show the phone which is what people are watching to see.
  • LordConrad - Tuesday, October 11, 2011 - link

    My Thunderbolt is rooted and running Andriod 2.3.4, courtesy of Das BAMF 3.0 RC4.9 rom.
    I've overclocked it from 1.0GHz to 1.2GHz

    A few benchmark results:

    Sunspider = 3092ms
    GUImark 2 (fullscreen) = 48.32
    LinPack (single-thread) = 44.831
    GLbench 2.1 Egypt = 18.2

    I'll stay with this until Qualcomm Krait gets here. Besides, I would much rather have a TFT screen at WVGA than a Pentile screen at qHD.
  • Omega215D - Tuesday, October 11, 2011 - link

    Let's see what the Samsung Prime and the HTC Vigor have in store for us now that they are using HD screens.

    I have the OTA Gingerbread on my Thunderbolt. I get similar results without rooting or overclock. Battery life is longer as well. I just have to avoid downloading useless apps from the market though (thanks to a certain APK).
  • LordConrad - Tuesday, October 11, 2011 - link

    I'm looking forward to the HTC Vigor also. I don't care for Samsung devices, the screens are nice but they feel cheap and are not as easy to root as newer HTC phones. The Thunderbolt was annoying to root and I'm not doing that again.

    I forgot to mention that I got the 3200mah extended battery from Seidio Online shortly after buying the phone. Also, the main purpose of rooting was to enable programs such as WiFi Tether. I refuse to pay an extra $30 for tethering since I never exceed my phone's 2GB data plan (tethering is only occasional).
  • jeepdinger - Tuesday, October 11, 2011 - link

    I would be curious to see the number of times each page loads when the battery test is run. It was stated that several pages load continuously during the test. The new LTE speeds versus the slower 3G speeds should manage the same or more page loads for the same or less battery life. If this were true then there is a definite advantage to the LTE speeds even though the battery life seems less when the pages are continuously loaded. Is this something that could be added to the graphic, maybe as 2 bars per phone listed. Thanks.

Log in

Don't have an account? Sign up now