Skip to main content

Resolution

8 replies [Last post]
hallenberg
Offline
Joined: 2007-01-05
Points: 0

I haven't got around to compiling my own binary yet, but I have noticed that the resolution on the windows binary is greater than that of the linux arm-binary. Since it's using the framebuffer you would imagine that the whole framebuffer would be used for graphics, but currently only a portion is used. Is there any way to change this in the binary release, or do I have to compile my own from source?

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Gary

If you are targetting a desktop screen, then there will be many things
you will want to customize. The defaults are targetted for mobile
handset platform.

phonemefeatures@mobileandembedded.org wrote:
> I haven't got around to compiling my own binary yet, but I have noticed that the resolution on the windows binary is greater than that of the linux arm-binary. Since it's using the framebuffer you would imagine that the whole framebuffer would be used for graphics, but currently only a portion is used. Is there any way to change this in the binary release, or do I have to compile my own from source?
> [Message sent by forum member 'hallenberg' (hallenberg)]
>
> http://forums.java.net/jive/thread.jspa?messageID=193268
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: feature-unsubscribe@phoneme.dev.java.net
> For additional commands, e-mail: feature-help@phoneme.dev.java.net
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: feature-unsubscribe@phoneme.dev.java.net
For additional commands, e-mail: feature-help@phoneme.dev.java.net

hallenberg
Offline
Joined: 2007-01-05
Points: 0

I am targeting a device (not a mobile phone, but close enough) with a 240x320 screen. It seems a bit odd to me that the resolution of the GUI is hard coded to 176x210 (or at least seems to be) by default when the framebuffer supplies you with the actual resolution.

selenau
Offline
Joined: 2006-10-11
Points: 0

I manage to get 320x240 and 640x480 resolution (google mobile maps looks great) . It is not that hard, but you have to build it.

hallenberg
Offline
Joined: 2007-01-05
Points: 0

Yes, I found the xml-files so changing the resolution shouldn't be a problem. My only question is why the resolution is a hardcoded constant. Since you need to ask the framebuffer device for it's resolution anyhow to be able to draw, why not just use that resolution instead? That way the whole screen would be utilized no matter what hardware (as long as it's linux/fb of course).

aap031
Offline
Joined: 2006-10-18
Points: 0

Hi!

I believe this was chosen for the sake of graphics performance. Knowing screen dimensions at compile time allows you to use more efficient graphics routines (e.g. multi-register copy) as well as allows compilers (both java and C) to optimize the code

On the other hand there were no reason for phoneME Feature to be able to determine screen dimension at run time as it's primarily targeted for being ported to *particular* device.

Regards,
Andrey

hallenberg
Offline
Joined: 2007-01-05
Points: 0

Thanks. I thought that might have been the case, even if I personally imagine that the gains in performance are slim on modern (mobile) CPUs (please correct me if I'm wrong). I do however remember the good old mode 13h days where replacing y*320 with (y<<6)+(y<<8) gave an incredible boost in performance... But that's a completely different story.

I'm compiling my own port as we speak, so we'll see how it works out soon enough =)

/ Tomas

selenau
Offline
Joined: 2006-10-11
Points: 0

I think color depth is even more hard-coded. :) It is fixed as 16 bit everywhere.

aap031
Offline
Joined: 2006-10-18
Points: 0

Which gives quite noticeable performance boost indeed

Regards,
Andrey