The Camera on the Samsung Galaxy S does a good enough job.
And when I say ‘good’, i mean decent. In daylight. When there’s good enough lighting. Read on for a bit more about it.
The Galaxy S has the usual Camera UI that you’d expect in a touchscreen device nowadays. The whole screen acts as the viewfinder, and there are notifications for resolution, gps-lock (if you’ve chosen to geo-tag your images), Anti-Shake & Blink detection (if you’ve turned these features on), battery level, remaining shots left, etc at the top of the screen.
With the Galaxy S however, all you have to do is tap on the screen object you want it to focus on, and it’ll auto-focus on it.
This implementation couldnt get any simpler. That being said, I still missed having a dedicated camera key, since it does get clumsy sometimes. And dont even think of trying to take a landscape picture with one hand.
Tap on the little arrow head to the left side, and more options pop up in the UI.
Things like Shooting Mode.
Scene Mode.
Or more intricate settings like Focus Mode, Timer, etc.
You can also choose to review the image you’ve taken, or turn Geo-Tagging on.
Tap on the camera icon on the top right side of the screen and you’ll switch to Video recording mode. The UI here is pretty much exactly similar, as you’d expect.
Settings are also present, although in lesser variety. You can choose to record at an mms-friendly size.
Or tinker with your Exposure or Recoding Resolution. As I later found out, the default video recording resolution is not set at 720p, so make sure to change that once you get your Galaxy S.
You can also choose to record video without Audio, if you’d need to.
Here’s a quick video on the Camera UI. Just to give you a better idea.
Since the Galaxy S isnt supposed to be a Camera Feature phone, we’re not going to critique each Image. But here’s a couple Camera Samples just to let y’all know what this thing is capable of.
Close-Up Images:-
Image 1:
Image 2:
Image 3:
Image 4:
Image 5:
Image 6:
Image 7:
Image 8:
Image 9:
Image 10:
Image 11:
Image 12:
Image 13:
Mid Range Images:-
Image 1:
Image 2:
Image 3:
Image 4:
Image 5:
Image 6:
Image 7:
Image 8:
Image 9:
Image 10:
Far-away Images:-
Image 1:
Image 2:
Image 3:
Image 4:
Image 5:
Image 6:
Image 7:
Image 8:
Image 9:
Image 10:
Image 11:
Image 12:
Image 13:
Image 14:
Image 15:
Night and Low-Light:-
Image 1:
Image 2:
Image 3:
Image 4:
Image 5:
Image 6:
Image 7:
Image 8:
Image 9:
Image 10:
Video:-
High Definition 720p Daytime (Warning: Loud Noise):
High Definition 720p Low-Light (Warning: Loud Noise):
High Definition 720p Night (Warning: Loud Noise):
Standard Definition:
Standard Definition:
Standard Definition:
Conclusion:-
So as you can see, the Samsung Galaxy S has a pretty capable camera. It’s weakpoints would have to be how it handles too much light (the sky is too white in many cases). However it’s color reproduction is mostly spot on except for a couple cases here and there. And with functions like Blink detection and Anti-shake, and a couple camera effects, it does a good enough job.
Since it doesnt have a flash module of any kind, Night shots arnt very great. Something to note if you’re the kind of person to take a lot of pictures of you and your friends at the club, etc. I’d imagine Samsung decided to leave out flash on the Galaxy S, so as to attain the slim profile (it’s the slimmest Android phone to date). Some people might even argue that you might as well not have a flash present, instead of bothering with an LED flash module.
Video quality is pretty good, although frames do start to drop sometimes when recording at 720p High Definition. The audio recording during video mode is quite bad to be honest. For some reason it seems to amplify any high pitched noises, which results in very irritating audio.
For more camera samples, dont forget to check out our Samsung Galaxy S Camera Samples Album on Flickr.
What do you think about the Samsung Galaxy S and it’s Camera? Something we missed? Do let us know in the comments y’all.
Comments (7)
Audio recording sucks even on its own, not only during video capture.
This is because whoever integrated (wrote) the audio drivers was unable to
1) Set the microphone sensitivity to an appropriate level
2) Low pass (anti-alias) filter before (re)sampling