Thanks Dianne. Can you please tell me where exactly this flag is getting set in the current build system? And also How to make the expanded status bar and the search dialog to cover entire screen when running emulator with 480x800 skin?
Thanks Thote On Nov 20, 6:12 am, Dianne Hackborn <[email protected]> wrote: > The build system automatically builds applications to target the current > version, if they haven't otherwise specified a version in their manifest. > It's just a matter of passing a flag to aapt when building an app. > > > > On Thu, Nov 19, 2009 at 1:34 AM, TG <[email protected]> wrote: > > Hi, > > > We are porting Donut (1.6r1) to a WVGA (480x800) device. When we > > install and run an application, which doesn't contain neither <uses- > > sdk> nor <supports-screens> tag, application covers only small area of > > the screen. if we use <uses-sdk> tag with value 4 in manifest file, it > > work fine. But All default applications (comes with Android source) > > works fine without any <uses-sdk> or <supports-screen> tag in their > > manifest file. > > > Where exactly is the difference between default android applications > > and sdk built applications? How can I make all applications to run in > > full screen without any <uses-sdk> tag in manifest file? > > > One more strange observation is that Status bar expanded view and > > Search dialog will not cover entire screen if you run emulator with > > 480x800 skin. why? > > > Thanks > > Thote > > > -- > > unsubscribe: > > [email protected]<android-porting%[email protected]> > > 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. -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
