Future supported screen sizes and resolutions

by RugBat » Tue, 03 Feb 2009 15:24:42 GMT

Sponsored Links

I'd love to get some information about the screen sizes Android is
planning to support in future, and what that might look like.  I'm
particularly interested in larger screens, like 8"-10" WVGA.

I see the roadmap says:

      Beyond Q1 2009 ... Support for WVGA and QVGA

but what kind of support is that?  If this is still phone-oriented,
then I might expect support for 3"-4" WVGA, with the existing UI -- so
the contacts list, for example, would still be a single column.  My
project is for a system with a larger screen, about 8"-10", and it
really needs a different UI layout to look good -- the contacts list
with one column but two rows per entry looks poor in the wide screen.
A two-column view would be much better.  Also more items per screen,
as my touch area is much larger.


* Will Android support this?  IOW will the standard apps have layouts
tailored to this kind of screen?
* Roughly when would that be?




Future supported screen sizes and resolutions

by Jean-Baptiste Queru » Tue, 03 Feb 2009 15:29:58 GMT

 At the moment the target is to support screens with a physical size
similar to the G1 (like you said, 3-4") and pixel counts ranging from


Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.


Sponsored Links

Other Threads

1. someone please explain this error and how to get rid of it

While trying to build the Yamba example code from "Learning Android",
I am getting the following error.  I suspect that it
may have something to do with the external jar file, jtwitter.jar (the
book version which has one error from the original

---------------------------  CUT HERE  ---------------------------

[2011-05-12 13:36:14 - Yamba] Dx
trouble processing "java/nio/CharBuffer.class":

Ill-advised or mistaken usage of a core class (java.* or javax.*)
when not building a core library.

This is often due to inadvertently including a core library file
in your application's project, when using an IDE (such as
Eclipse). If you are sure you're not intentionally defining a
core class, then this is the most likely explanation of what's
going on.

However, you might actually be trying to define a class in a core
namespace, the source of which you may have taken, for example,
from a non-Android virtual machine project. This will most
assuredly not work. At a minimum, it jeopardizes the
compatibility of your app with future versions of the platform.
It is also often of questionable legality.

If you really intend to build a core library -- which is only
appropriate as part of creating a full virtual machine
distribution, as opposed to compiling an application -- then use
the "--core-library" option to suppress this error message.

If you go ahead and use "--core-library" but are in fact
building an application, then be forewarned that your application
will still fail to build or run, at some point. Please be
prepared for angry customers who find, for example, that your
application ceases to function once they upgrade their operating
system. You will be to blame for this problem.

If you are legitimately using some code that happens to be in a
core package, then the easiest safe alternative you have is to
repackage that code. That is, move the classes in question into
your own package namespace. This means that they will never be in
conflict with core system classes. JarJar is a tool that may help
you in this endeavor. If you find that you cannot do this, then
that is an indication that the path you are on will ultimately
lead to pain, suffering, grief, and lamentation.

[2011-05-12 13:36:14 - Yamba] Dx 1 error; aborting
[2011-05-12 13:36:15 - Yamba] Conversion to Dalvik format failed with
error 1

---------------------------  CUT HERE  ---------------------------

Can anyone tell me what this means, and, more importantly, how I get
rid of it so the project will build?



2. Broadcast before shutting down

Hi there,

Does anyone knows what broadcast event gets launched before a device
is turned off (if any) - I want to be able to receive it on an app
that is installed on the sd card, which complicates things...



3. WebView

4. Scrollbar in AdapterView derived object

5. Use your Machine as ADK with libusb

6. AVD Emulator Opens Wrong Dpi

7. Gallery image should navigate with textview