maemo.org Bugzilla – Bug 5603
Vertical photos from other devices should fill more space when shown in portrait.
Last modified: 2010-01-14 12:27:42 UTC
You need to
before you can comment on or make changes to this bug.
Maemo 5: 1.2009.41-10
STEPS TO REPRODUCE THE PROBLEM:
N900's camera photo:
1) Open the camera application in the N900.
2) Change the orientation of the device to portrait (the camera UI doesn't
3) Grab a vertical photo.
4) Open the photo with the Images application, and go to fullscreen.
5) Move the N900 to portrait orientation.
Other device's photo:
6) Copy a vertical photo made with other device to the N900 (for example with a
7) Open the copied image with the Images application, and go to fullscreen.
8) Move the N900 to portrait orientation.
The vertical photos made with other devices should fill more from the available
space in the screen if they are bigger than 480x800 (width x height).
Vertical photos bigger than 480x800 are shown with black borders for the 2
Photos made with the N900 are using all the available space from the screen, so
they are working correctly.
Always: I tried with photos from a Nokia N95, Sony DSC-P72 and a cheaper Benq.
I'll attach two example photos.
Created an attachment (id=1462) [details]
Photo made with the N900
This is a photo made with the N900, it's working as it should.
Created an attachment (id=1463) [details]
Photo made with the Nokia N95
Vertical photo made with the Nokia N95.
This photo triggers the bug.
Have you tried to make 5Mpix photo with N900? It should behave the same way as
with N95's photos.
The reason for that is aspect ratio of the image. Default 3.5Mpix resolution in
N900 camera is close to N900's screen aspect ratio, thus almost no black space
5Mpix image is 4:3 aspect ratio and your N95's photos have similar aspect
In order words, image viewer is preserving aspect ratio when showing images in
full screen mode.
(In reply to comment #3)
> Have you tried to make 5Mpix photo with N900? It should behave the same way as
> with N95's photos.
> The reason for that is aspect ratio of the image. Default 3.5Mpix resolution in
> N900 camera is close to N900's screen aspect ratio, thus almost no black space
> 5Mpix image is 4:3 aspect ratio and your N95's photos have similar aspect
> In order words, image viewer is preserving aspect ratio when showing images in
> full screen mode.
Yes, I know about the aspect ratio, using a 5MP photo made with the N900 also
Sorry if I don't have explained well the problem. Let me attach two screenshots
taking as examples a 5MP photo from the N900 and one from the N95.
Created an attachment (id=1464) [details]
Screenshot with the N95 photo
This screenshot is with the N95 5MP photo. Note the black borders are in both
Created an attachment (id=1465) [details]
Screenshot with the N900 photo
This is the case with the 5MP photo from the N900. It uses all space available
in the Y direction, so it hasn't black borders in both directions like it's the
case with the N95 photo.
Yes, I see the same with this image -- it looks like it is centered as some
multiple of 320x240 image (ImageViewer also claims in properties that this
image has a thumbnail embedded size of 320x240).
If you look at it with tracker-info (tracker-info /path/to/file.jpg) then you
can see that dimensions are reported properly.
Let me check something on this internally. I'll come back in few days.
Created an attachment (id=1473) [details]
Screenshot on N900
Must admit I still don't get the issue here.
Using the picture from comment 2 this is how it looks on the N900, no black
What am I missing?
(In reply to comment #8)
> Created an attachment (id=1473) [details] [details]
> Screenshot on N900
> Must admit I still don't get the issue here.
> Using the picture from comment 2 this is how it looks on the N900, no black
> What am I missing?
Perhaps I'm missing an update to the latest and greatest software?
Comment #5 is my screenshot from the N900, compare it with yours ;-)
Heh. Probably FIXED in the meantime, as I'm not sure though I close as
It is actually fixed and will be available in next software update. Andre,
please update alias to include proper internal bug number for it: int-132907.
Oh, even better. Thanks!
This has been fixed in package
which is part of the internal build version
(Note that 2009 is the year and the number after is the week.)
Any public update released with or after this build version will include the
Please verify that the new version fixes the bug by marking this bug report as
VERIFIED after the public update has been released and if you have some time.
Verified in non-public PR1.1 version (2.2009.51-1). Thanks!
The problem reported here should be fixed in the update released today for
public: The Maemo5 update version 2.2009.51-1 (also called "PR1.1" sometimes).
Please leave a comment if the problem is not fixed for you in this update