Fwiw, as a general rule, I would hope that a device that has a high resolution screen is correspondingly beefier in power. Even ignoring that, though, you can expect HVGA devices to have varying performance characteristics.
On thought I have is to view Android more like the desktop world, where if needed you give the user some ability to adjust the rendering features of the app to improve its performance on their device. And longer-term, I imagine that having built-in knowledge about various existing devices to automatically select those options will be used, again like on the desktop with graphics cards. (I do realize that this is more problematic in the mobile space since getting access to particular devices is more difficult than getting different graphics cards.) Another interesting wrinkle is that in density compatibility mode, the Surface behind a SurfaceView is kept at the HVGA resolution and scaled up (or down) by the compositor as it is drawn to the screen. So if you are doing rendering in that, you are still dealing with an HVGA size buffer. We have actually seen this have better performance than an app that is running in non-compatibility, since the scaling is likely less work than rendering all of the complicated scene inside of the surface view. I believe you can do the same thing outside of compatibility mode by setting the SurfaceView's surface to a fixed size that is smaller than the actual view itself, giving you something equivalent to the desktop approach of running at a lower resolution than the user has set for their normal screen. On Fri, Oct 2, 2009 at 12:43 PM, Warren <[email protected]> wrote: > > I have developed a game for android that really needs to have a > 480x320 resolution. I have considered trying to alter the game to > work with different resolutions, but this would be very difficult if > even feasible. I know of at least one phone from Motorola that will > have a WVGA screen. I loaded my game in the new 1.6 emulator with a > WVGA screen and the game was scaled up to fill the screen with a black > bar of unfilled space on the right. > > I'm happy to see that the application scaled up, but I wish it didn't > have a black bar on the side. I am also anxious to see how the scaling > performs. My game needs every bit of CPU it can get. > > I assume others of you have apps that rely on 320x480 screens. They > might rely on them for a reason, like mine, or it may be that you > haven't gotten around to designing for multiple screens yet. At any > rate, how do you plan to deal with other screen sizes? (There are QVGA > phones coming soon too.) I'm trying to decide the best way forward. > > Thanks, > Warren > > > -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
