Pages: 1
Exact picture sizes for the SCP-5300 (with an explanation)
(Click here to view the original thread with full colors/images)
Posted by: martianviking
Do you want to know the exact sizes that you should be cropping/resizing your pictures to for uploading to your Sanyo SCP-5300?
I've seen a few threads that had a number of answers for this, but I've never seen a definitive answer (with an explanation). That is what I'm going to try to provide here. In case you're wondering, I've tried these tests using both PCSpix.com and my own server using my own .GCD files, so this should all work for you no matter what method you use to get pictures onto your phone.
It's a bit complicated, but here is the shortest, easiest, most correct answer I could come up with:
Background pictures: It will only display an area of 132x129 for background (or "screensaver") pictures, but the full image needs to be 132x176 (the full screen size) in order to get the phone to center the image correctly within the viewable area. Size your picture to 132x129, then add 16 pixels of blank space to the top of the image and 31 pixels of blank space to the bottom (16 + 129 + 31 = 176).
Caller ID pictures: It will only display an area of 132x144 for caller ID pictures. You can use a picture that is just 132x144; you don't need to add any extra space to the top/bottom of the image, but you can add 16 pixels to both the top and bottom to make it a full 132x176 if you want.** (It will display the same either way when used as a caller ID picture.) If you want to know more about what parts of a caller ID picture are covered by the name and number of your caller, read the next post.
** If you would like to be able to use your caller ID pictures for backgrounds (or "screensavers") as well as for caller ID, then you should always add the 16 pixels to both the top and bottom (since background pictures need to be the full 132x176 and they need the 16 pixels at the top). Just remember that the very bottom (the bottom 31 pixels, 16 of which are blank space and 15 of which are the bottom of your caller ID picture) will not be seen when used as a background picture.
Follow this key to the image below to see exactly what I mean:
GREY (each is 132x16) = Never displayed.
GREEN (132x129) = Entire area displayed when used as a background (or "screensaver") picture.
BLUE (132x15) = Not displayed when used as a background picture, but is displayed when used as a caller ID picture.
GREEN+BLUE (132x144) = Entire area displayed when used as a caller ID picture.
Posted by: martianviking
As for what parts of the caller ID picture get covered up by the incoming caller's name and phone number, it is as follows.
The caller's name and an letter showing the type of number (M, H, W, etc.) are placed over the picture (but you can see between the letters) using the top 15 pixels. The caller's phone number does a similar thing (you can see between the numbers), but it is placed over an area 20 pixels tall that starts two pixels above the very bottom of the picture. After you miss a call, the phone number goes away (but the name stays at the top of the screen) and a white bar is placed at the bottom of the screen. It completely covers the bottom 16 pixels of the picture. This bar contains a "View" label for the left soft-button.
This image should help show what I mean:
GREY (each is 132x16) = Never displayed.
LIGHT BLUE (132x144) = Entire area displayed when used as a caller ID picture.
SHADED GREEN (132x15) = Caller's name and type of number (M, H, W, etc.) are put over the picture here.
SHADED PURPLE (132x20) = Caller's phone number is put over the picture here.**
SHADED DARK BLUE (132x16) = This is completely covered up by a white bar with a soft-button label in it after you miss a call.**
** The purple and blue shaded areas extend all the way across the picture, but I only showed each one on half of the screen to make the picture easier to read (otherwise they would overlap and it would look very messy). Just imagine that they go all the way across.
Posted by: martianviking
In case you're wondering how I figured all this out, here's what I did. (As I said, I used both PCSpix.com and my own server to try all this.)
First, I uploaded the picture shown below. It's a full 132x176 picture with borders and rulers to help me count pixels. I observed that when set as the background image it cut off the top 16 pixels and the bottom 31 pixels (so it only showed a section of the middle that was 132x129 pixels). So, I made a new picture that was only 129 pixels tall, loaded it to my phone, and set it as a background. It didn't do it right; there was extra whitespace at the top and it cut off the bottom. I found that adding 16 pixels to the top and 31 pixels to the bottom ended up working just right.
I followed a similar procedure for the caller ID picture, except that there were a few more steps that included adding extra markers to count exactly where the callers name, phone number, and white bar were showing up.
If you want to retrace my steps, you can start with this image:
Posted by: martianviking
You can use this image to help show how the caller ID picture works. The greenish coloring at the top and bottom should not show up at all when set as a caller ID picture (the red borders should be the last line you see all around the picture, just before the white at the top and bottom of the screen).
When you receive a call with this picture set as the ID, the white border around the letters of the caller's name should go all the way to the top of the screen (overlapping the red border) and come down just enough to touch the green line marked "A" (but not overlap it). The caller's number should be between the purple lines marked "C" with the white borders of the numbers just overlapping the purple lines. If the caller hangs up before you answer, a white bar should appear that covers the bottom of the screen, and the blue line marked "B" should be on the last line of pixels still visible at the bottom of the picture just above the white bar.
Here it is:
Posted by: kinless
Wow, what intuition! I'm sure some people are going to tell you that you've got too much time on your hands. But heck I've always wanted the exact 5300 dimensions so I could have perfect pictures for wallpapers and IDs, but was too lazy to do them myself. This will help me out greatly! Thanks, Mr. Viking! I'm going to save this as a web archive and put it away for future reference.
Now all you have to do is the pixel dimensions and internal:external ratios for the external display, and you've become an official top elite nerd.
Posted by: thunderboom01
That is an excellent post martianviking. That helps me and probably lots of others. Great job!
Posted by: martianviking
Heh... glad it's going to some use besides my own.
As far as the external LCD goes, that thing is just a pain. The problem is, it does some automatic resizing so it's very hard to tell exactly where it crops the background pics. I can give you a general idea, though. It looks like it crops about 20 pixels off of the top and about 10 pixels off of the bottom. This is from the 129 pixels you're working with after you've cropped for the background, not the full 176. (It may be more like 22 or 23 off of the top, but it's right close to 10 off of the bottom.) Unfortunately, it really is hard to tell exactly (since we can't put a non-blurry picture on the external display).
It doesn't seem to crop the caller ID pics much, if at all. Any cropping that is done seems to happen at the very bottom of the picture and is probably negligible, though it still leaves those ugly spaces to the sides of the image.
I have to say that am really disappointed with the external display. Yes, it's color. Yes, it looks pretty crisp if you turn the contrast up. So why am I disappointed? Because we can't individually assign tailored pictures to the external display, so there is always space to the sides and the pictures always look blurry and pixelated. Very unprofessional/unfinished looking.
Other than that (and the fact that the time readout on the external display is so small, specifically during standby when large white digits would really help), I really can't find much to complain about on this phone. It's a wonderful machine, and Sanyo is to be applauded. Now I'm wondering if these two things could be addressed through a firmware update.
So does that qualify me for "elite nerd" status?
Posted by: JuNacy
Wow, what a very informative thread. I was wondering about this very thing a little while ago. Thanks for the heads up
Posted by: thunderboom01
Quote:
Originally posted by martianviking
So does that qualify me for "elite nerd" status?
|
I'll nominate you 
Posted by: exmike
can you post some of your backgrounds for us to see?
Posted by: the digitel
Mr. Viking, you are a pimp. Let's get this over to the sprint developer's forum and hopefully eventually to the 'genuises' at Sanyo.
Posted by: nancito
just saw this post, you did an amazing job! keep up the good work!
Posted by: sbono13
actually, the external lcd will display images that are wider than the 132 pixels. if you upload a picture with around 144 pixels wide, the bars on the left and right go away from the subLCD. These parts of the image get truncated on the normal LCD. For instance, when you download a picture stored on your pictures.sprintpcs.com website, you get an overcompressed jpg that is bigger than the screen (pixel wise). that picture fills the external LCD (as much as it can be filled).
The other thing i noticed is that you can shift the image around a bit to recenter it when assigning an image to wallpaper or picture ID. that way, you don't have to add blank pixels to the top and bottom of the 132x129 jpgs intended for wallpaper. It doesn;t recenter for the subLCD though...
Posted by: martianviking
Wow... I didn't even think of making the pictures wider to fill the sub LCD. Excellent tip. Perhaps we can do some experimenting and get some better, more exact numbers for the external LCD.
Thank you!
Posted by: CEGiven
Sprint has this for the 5300:
Phone Model: PCS Phone by Sanyoฎ (5300): Last Modified: 10/14/02
General Specifications:
Dimensions:
Browser: Netfront 3.0/Access
Vibrating Ringer: Yes
Display:
Pixel Dimension: 176 x 132
Pixel Size (ex .25mm x .25mm): 0.252W x 0.256H
Usable Pixel dimensions: 132 x 128
Color:
Color Depth: 16 bit 65535 color
Class image have transparency: No
Java:
J2ME: Yes
Restriction on JAR size: 100K
Java Heap size: 812K
Usable Pixel dimensions for J2ME: 132 x 60
Sound:
Ringer Type: CMX-MIDI
Posted by: martianviking
Addendum: External LCD
Well, sbono13 was absolutely right. 144 pixels is the perfect screen width to fill up the external LCD (horizonally, anyway).
Everything I said above about picture sizes for the internal LCD is still true, but in order for your pixtures to fill up the sides of the external LCD you should add 6 pixels to each side in order to fill in the space to the sides of the image. I also figured out the external LCD's cropping behavior (through the same system of trial and error).
Background pictures: Starting from the 129 vertical pixels used for internal background images, the 5300 will crop 23 pixels off of the top and 11 pixels off of the bottom before resizing. This leaves 95 effective pixels (vertically) to build the image displayed on the external LCD (23 + 95 + 11 = 129). So, the final picture displayed on the external LCD for background (or "screensaver") images is an automatically resized version of a 144x95 pixel image.
Caller ID pictures: Caller ID images are more complicated. Starting from the 144 vertical pixels used for internal caller ID images, the 5300 will crop two pixels off of the bottom but it will add one pixel to the top before resizing. That is to say, the bottom two pixels from the internally displayed 144 (vertical) pixels will be excluded from the external LCD, but it will include the single row of pixels located at 16 pixels from the top (starting from top of the full 176 pixels). This new line of pixels is never shown on the internal LCD. This would mean that if you used the very first picture at the top of this thread (the grey, green and blue one) for a Caller ID picture, it would never display any grey on the internal LCD, but when resizing for the external LCD it would include one line of grey at the top. This means that there are 143 effective pixels (vertically) used to build the image displayed on the external LCD (144 shown on internal LCD - 2 cropped from bottom + 1 added at the top = 143). You should still use 144 pixels for the width of caller ID pictures (the original 132 plus 6 pixels added to each side). So, the final picture displayed on the external LCD for caller ID images is an automatically resized version of a 144x143 pixel image.
Follow this key to the 144x176 image below to see exactly what I mean:
GREY (132x15) = Never displayed on either LCD.
BLACK (132x16) = Never displayed on either LCD.
YELLOW (each is 6x2) = Never displayed on either LCD.
LIGHT GREEN + DARK GREEN (132x129) = Entire area displayed on internal LCD when used as a background (or "screensaver") picture.
DARK GREEN + LIGHT PURPLE (144x95) = Entire area used as a base to create resized image that is displayed on external LCD when used as a background (or "screensaver") picture.
LIGHT BLUE + DARK BLUE + LIGHT GREEN + DARK GREEN (132x144) = Entire area displayed on internal LCD when used as a caller ID picture.
LIGHT BLUE + LIGHT GREEN + DARK GREEN + LIGHT PURPLE + DARK PURPLE + RED (144x143) = Entire area used as a base to create resized image that is displayed on external LCD when used as a caller ID picture.
Posted by: martianviking
So, we've solved the "blank edges" issue. It isn't perfect; the external LCD still doesn't look as good as it could, since the pictures are resized by some internal mechanism of the 5300 (instead of us being able to resize them manually with a nice image editing program).
Another thing to note is that pop-up notes (such as the "ringer off" message) were designed by Sanyo with the assumption that only 132 pixel wide images were used as backgrounds. This message in particular has white at the edges, which cover up the screen (something like the attached picture).
(I did all my testing with firmware version 1.035SP so other versions may have slightly different results. I doubt it, but it's a possibility.)
vBulletin Copyright ©2000 - 2008,
Jelsoft Enterprises Limited.
vB Easy Archive Final ©2000 - 2008
- Created by Stefan "Xenon" Kaeser