Hi Dianne, Thanks for the insights you have been providing regarding supporting larger/mini screen size devices.
Is there any doc or guideline available which lists the modifications that needs to be done at the App F/W and App layers of the Android to support large screen UI. Thanks, Mike On Jan 18, 2:59 am, Dianne Hackborn <[email protected]> wrote: > Ah yes, QVGA medium (or high) density screens are not supported. If at some > point the platform does add support for them, it will mean doing the same > thing we did for QVGA low density: introducing a new way for applications to > say they support them, and requiring they explicitly do so, so no existing > applications will be compatible with such devices until they are updated. > > At this point we have no plans to add support for such screens, since these > are significantly different than existing screens in the amount of available > space and it is not something we want to impose on developers. > > You can certainly modify the platform and built-in apps to run on such a > device, but it doubt it will be running Market any time soon. Sorry. > > > > > > On Sun, Jan 17, 2010 at 2:14 AM, Motty <[email protected]> wrote: > > Hi Dianne, > > > Thanks for your answer! > > > I can do the work of adjusting the built-in applications (Dialer, > > Messaging, Contacts, etc') to a small 2.2" QVGA screen myself, but > > what about the non built-in applications? > > > I think that the problem is that the framework auto-scales application > > resources according to the screen size (small, normal, large) and > > density (low, medium, high) in order to preserve the same physical > > size of the element across different screens sizes, aspect-ratios and > > densities. In addition, on the Supporting Multiple Screens page on > > Android Developers site (http://developer.android.com/guide/practices/ > > screens_support.html) there is a table that states small screens as > > 2.6"-3.0". Can I overcome the fact that application developers have > > built their applications to be run on a small screen 2.6"-3.0" and not > > a 2.2"? > > > Please note that QVGA resolution on a small screen device, actually > > derived a medium-high density graphic. For example, QVGA 2.2" screen > > derived 180dpi density. I did not see an option of small screen and > > medium-high density in the table. Can you please confirm that this is > > not an issue? > > > Thanks, > > Motty > > > On Jan 17, 3:33 am, Dianne Hackborn <[email protected]> wrote: > > > QVGA screens are officially supported by the platform (there are Android > > > devices with such screens shipping, even); however, nobody has yet > > > contributed code to the open source project to make all applications and > > UI > > > elements work on such screens. In particular, tweaks (or less ideally > > > small-screen-specific variations) for layouts that don't fit and low > > density > > > graphics. You will need to do this work yourself. > > > > On Sat, Jan 16, 2010 at 2:07 AM, Motty <[email protected]> wrote: > > > > Hi, > > > > > I want to port Android on a QVGA 2.2" screen device. > > > > From what I read on android developers site (http:// > > > > developer.android.com/guide/practices/screens_support.html) and from > > > > playing a bit with the emulator, it seems that there might be some > > > > problem in porting it to such a small screen. > > > > > Q: > > > > 1. Can you please confirm the minimum supported diagonal for a QVGA > > > > screen? 2.6"? > > > > > 2. If there is no "out of the box" support for such a small screen, > > > > are there any changes that I can easily do in the framework in order > > > > to support it? Or, is my only choice to go over all the applications > > > > and change them accordingly? > > > > > 3. What are the implications on apps downloaded from the Android > > > > Market? Is declaring small screen and medium density enough? > > > > > 4. Will I encounter a problem in getting Google permission to put the > > > > Android Market application on such a small screen device? > > > > > 5. Does Google plan to extend the small screen support in future > > > > Android releases? > > > > > Thanks, > > > > Motty > > > > > -- > > > > unsubscribe: > > > > [email protected]<android-porting%2bunsubscr...@googlegroups.com> > > <android-porting%2bunsubscr...@googlegroups.com> > > > > website:http://groups.google.com/group/android-porting > > > > -- > > > 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.- Hide quoted text - > > > > - Show quoted text - > > > -- > > unsubscribe: > > [email protected]<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting > > -- > 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.- Hide quoted text - > > - Show quoted text - -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
