3D modeling library for Opengles in Android

by and.pradeep » Thu, 12 Mar 2009 18:12:13 GMT

Sponsored Links
     Is there any 3D modeling library for Opengles that can be used in


Other Threads

1. Layout issues with 2 specific devices

All -

Sorry for posting another layout topic, but I think all of my reading
of different layout concerns has confused me a bit, so I wanted to see
if someone could help with a specific case.

I have an urgent question regarding layouts across different android
devices.  I would greatly appreciate input as I am not quite sure if I
am handling things correctly.

Currently working with 2 devices using Android 1.6 (the highest I can
go as per the archos firmware support)

The archos specs:

        D/SYSTEM_INFO( 1923): running device stats
        D/SYSTEM_INFO( 1923): display width : 480
        D/SYSTEM_INFO( 1923): display height : 800
        D/SYSTEM_INFO( 1923): density : 1.125
        D/SYSTEM_INFO( 1923): density dpi : 180
        D/SYSTEM_INFO( 1923): physical pixels per inch (x) : 195.38441
        D/SYSTEM_INFO( 1923): physical pixels per inch (y) : 193.5226
        D/SYSTEM_INFO( 1923): scaled density (for fonts) : 1.125

The nexus specs:

        D/SYSTEM_INFO( 1499): running device stats
        D/SYSTEM_INFO( 1499): display width : 480
        D/SYSTEM_INFO( 1499): display height : 800
        D/SYSTEM_INFO( 1499): density : 1.5
        D/SYSTEM_INFO( 1499): density dpi : 240
        D/SYSTEM_INFO( 1499): physical pixels per inch (x) : 254.0
        D/SYSTEM_INFO( 1499): physical pixels per inch (y) : 254.0
        D/SYSTEM_INFO( 1499): scaled density (for fonts) : 1.5

This app was originally designed for the archos device, so the
currently base layouts are done, tested, and accurate for that.  There
is no AbsoluteLayout use, everything uses dip (tried sp as well), and
some things are manually sized, but again using dips and mostly
RelativeLayouts.  Things display fine here.  Yesterday I attempted to
run the app on the nexus.

On first pass, the images on the nexus were way too big.  Actually,
most everything was oversided. This seems odd to me, as a higher dpi
would seem to produce a smaller image.  However, I understand that
android must compensate for this by up-scaling the image.  I can get
around this by adding the following to the manifest :

android:anyDensity="true" />

Which treats the images correctly.  As well, I changed anywhere where
I manually use a BitmapFactory to load an image to not scale, and the
images seem to be behaving well.  I still have a problem with fonts in
TextViews, WebViews, and actually most layout objects.

Again, text is way too big on the nexus, as well as layouts.  For
example, I have a LinearLayout in one activity that has a layoutHeight
of 370dip.  This looks perfect on the archos, but way too big on the
archos. I have found that if I size it as around 210 dip in a layout-
hdpi xml file for the nexus, it looks correct.

My question is, am I doing something wrong here, or is this the way I
should approach, having different layouts for each dpi?  It seems like
basic dip sized components (as well as fonts should size correctly)  I
realize I specified manual density scaling myself, but even without
the supports or using android managed scaling, I still see everything
as too big.



2. Trouble: Windows XP detecting Nexus One by USB

Are you by any chance using XP-64?  If there is a way to make the
phone visible on that platform I haven't found it but I have no
problems on Windows 7.


3. adb can't list my attached device

4. No new shopping site cargo does not order .. Download and use

5. Current issues with ipv6

6. Add Columns inTableLayout dynamically

7. How to trigger phone touch lock