Hi Mateusz Without adding the "android:hardwareAccelerated="true" workaround, would it be possible to send what is the resulting <uses-sdk> and <application> elements in the merged manifest file ? I am curious to see what versions the application is running under or if there is an explicit android:hardwareAccelerated="false" added by the manifest file. On Wed May 21 2014 at 3:45:49 PM, Mateusz Grzechociński < mateusz.grzechocin...@gmail.com> wrote:
> Hi, > > Android gradle plugin v0.10 introduced new manifest merger. I've been > using it for few weeks without any noticeable failures, but today I think I > found one. > > It seems that after switching to new manifest merger, default hardware > acceleration flag is no longer added to AndroidManifest. > > As documentation says ( > http://developer.android.com/guide/topics/graphics/hardware-accel.html): > *"Hardware acceleration is enabled by default if your Target API level is > >=14"* > > In my src/main/AndroidManifest.xml I have: > <uses-sdk android:minSdkVersion="9" android:targetSdkVersion="18" /> > > When building APK, it's performance is much lower than before enabling new > merger. > Is it possible that new merger makes my app targeted for API 19 not using > hardware acceleration by default? > After explicit "android:hardwareAccelerated="true"", it works fine. > > M. > > -- > You received this message because you are subscribed to the Google Groups > "adt-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to adt-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to adt-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
