Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid ViewPager performance on Galaxy Tab 2
    primarykey
    data
    text
    <p>I have an application which uses Android ViewPager (7 views, pretty complex with images and animations). This application runs fantastically on my Asus Eee Pad. It is just gorgeous.</p> <p>I also have a Galaxy Tab 2 10.1 which almost can not run the app... despite it's brand new and theoretically more powerfull than my EEE Pad. I would like to mention both terminals run Android 4.0.3 and their screen size is identical (1280x800). Application runs in landscape mode.</p> <p>The application does not use sql, or internet access, just animations on different views and the swipe effect of the ViewPager.</p> <p>I checked I think everything, from heap, from lint, from basically all the available tools for profiling but nothing seems to improve my UI performance on the Galaxy Tab 2... I wonder if there isn't some difference in the hardware finally, where the ASUS will use GPU to render the UI and the Galaxy Tab 2 its CPU...</p> <p>I was wondering finally, if any of you, noticed some similar issues on Galaxy Tab or other tablets when comparing your app behaviors on multiple targets...</p> <p>Cheers! Paul</p> <p><strong>--- added September 6th ---</strong></p> <p>Well, it seems that, despite the Galaxy tablet should use hardware acceleration, it does not. When I am forcing each xml layout with <code>android:layerType="hardware"</code> and</p> <pre><code>v.setLayerType(View.LAYER_TYPE_HARDWARE, null);     ObjectAnimator oaAlpha = ObjectAnimator.ofFloat(v, "alpha",0f, 1f); </code></pre> <p>it works finally better... even if it is not as smooth as on the Asus one</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload