Have a read of: http://developer.android.com/guide/practices/screens_support.html
But start by changeing all pixel (px) units to density-independent pixels (dp) units, dp units scale with the pixel density of the screen. On Aug 21, 3:49 am, Mystique <joven.ch...@gmail.com> wrote: > I read the Android resource and realize QVGA/WQVGA is using 120dpi, > HVGA is 160dpi while WVGA800/WVGA854 is 240dpi. > Is this the reason? What do I need to do to get my FrameLayout to > display right after the tab without manual adjustment? > Get some kind of environment reading for screen, do some maths and > modify it in the coding? What is the default tab size as in dpi?? Are > they all different in Android version? > > On Aug 21, 10:20 am, Mystique <joven.ch...@gmail.com> wrote: > > > Maybe it was the layout xml i'm doing it wrong? Are tab size all > > different for different android version/screen resolution? > > What best to do if I always want my fist textview to start right below > > the tab dynamically and not hardcoding using android:paddingTop? > > > <?xml version="1.0" encoding="utf-8"?> > > <TabHost xmlns:android="http://schemas.android.com/apk/res/android" > > android:id="@+id/my_tabhost" > > android:layout_width="fill_parent" > > android:layout_height="fill_parent"> > > <TabWidget > > android:id="@android:id/tabs" > > android:layout_height="fill_parent" > > android:layout_width="fill_parent"></TabWidget> > > <FrameLayout > > android:id="@android:id/tabcontent" > > android:paddingTop="95px" > > android:layout_height="fill_parent" > > android:layout_width="fill_parent"> > > <LinearLayout > > android:id="@+id/content1" > > android:orientation="vertical" > > android:layout_width="fill_parent" > > android:layout_height="fill_parent"> > > > On Aug 21, 3:18 am, RichardC <richard.crit...@googlemail.com> wrote: > > > > Beyond strange as your APK is signed (by you) so any changes would > > > have invalidated the signature and it would not install. > > > > Try and "adb install" the apk you uploaded to the market (you will > > > probably need to uninstall it first from your phone) and see what it > > > looks like. > > > > On Aug 20, 7:56 pm, Mystique <joven.ch...@gmail.com> wrote: > > > > > I was using 1.6 as emulator and then installed the apk in HTC Desire > > > > which has 480x800. > > > > Both shows the same result. When I published it, it doesn't look the > > > > same on my Desire when I install from Market. > > > > Isn't that strange? > > > > > On Aug 21, 2:15 am, RichardC <richard.crit...@googlemail.com> wrote: > > > > > > On the emulator did you try your app with all the difference screen > > > > > sizes / OS combinations ? > > > > > > I think you need about 5 emulators to hit 90% of devices: > > > > > 1.5 HVGA mdpi > > > > > 1.6 HVGA mdpi > > > > > 2.1 WVGA800 hdpi > > > > > 2.1 QVGA ldpi > > > > > 2.2 WVGA854 hdpi > > > > > > There are a few more combinations you could test with but I think the > > > > > above gets you to about 90% coverage. > > > > > > On Aug 20, 6:38 pm, Mystique <joven.ch...@gmail.com> wrote: > > > > > > > Hi, does publishing app in Android Market add something to the app? > > > > > > Why is my alignment off where where were ok in emulator and direct > > > > > > transfer to my phone? > > > > > > > How am I going to know what to adjust if Android Market causes it? > > > > > > > Anyone have this issue? > > > > > > > Regards. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en