I meant 0.10.3 of course... On Thursday, May 22, 2014 9:50:00 PM UTC-7, Jerome Dochez wrote: > > I checked in a fix that enforce the order of application putting it last > which should fix your issue. I believe we will be publishing 0.10.2 soonish. > > thanks for the report, jerome > > On Thu May 22 2014 at 3:22:11 PM, Mateusz Grzechociński < > mateusz.grzechocin...@gmail.com> wrote: > >> Ok, so waiting for your feedback. >> >> Thx! >> >> M. >> >> W dniu czwartek, 22 maja 2014 17:22:02 UTC+2 użytkownik Jerome Dochez >> napisał: >>> >>> it may very well be. >>> I will dig on my side, don't spend more time on this until I report. >>> >>> thx, jerome >>> >> >>> >>> On Thu, May 22, 2014 at 3:04 AM, Mateusz Grzechociński < >>> mateusz.gr...@gmail.com> wrote: >>> >>>> At first sight, I see the main difference is that with old merger >>>> <uses-sdk> is BEFORE <application> whereas in new merger it's placed after >>>> <application>. Maybe that's the cause? >>>> >>>> I'll prepare small project and share it with you around today/tomorrow >>>> >>>> M. >>>> >>>> W dniu czwartek, 22 maja 2014 06:07:00 UTC+2 użytkownik Jerome Dochez >>>> napisał: >>>>> >>>>> umh, I fail to see what could be wrong. Another thing to try is to >>>>> generate the merged file with both the old and new manifest merger and >>>>> send >>>>> me the diffs if that's not too much trouble. >>>>> >>>>> Thanks a lot, Jerome >>>>> >>>>> On Wed May 21 2014 at 4:07:13 PM, Mateusz Grzechociński < >>>>> mateusz.gr...@gmail.com> wrote: >>>>> >>>>>> Sure, >>>>>> >>>>>> so here is my merged, final AndroidManifest.xml file when no >>>>>> "android:hardwareAccelerated="true" is present in >>>>>> src/main/AndroidManifest.xml: >>>>>> >>>>>> >>>>>> <?xml version="1.0" encoding="utf-8"?> >>>>>> <manifest xmlns:android="http://schemas.android.com/apk/res/android" >>>>>> package="com.mypackage" >>>>>> android:versionCode="1" >>>>>> android:versionName="unspecified" > >>>>>> >>>>>> <application >>>>>> android:name="com.mypackage.MyApp" >>>>>> android:icon="@drawable/my_ic_launcher" >>>>>> android:label="@string/my_app_name" >>>>>> android:theme="@style/Theme.my_actionbar" > >>>>>> .... >>>>>> </application> >>>>>> <uses-sdk >>>>>> android:minSdkVersion="9" >>>>>> android:targetSdkVersion="19" /> >>>>>> </manifest> >>>>>> >>>>>> What might be useful, I'm building debug variant, and in src/debug I >>>>>> have another manifest file, to be merged and it's like this: >>>>>> >>>>>> <?xml version="1.0" encoding="utf-8"?> >>>>>> <manifest xmlns:android="http://schemas.android.com/apk/res/android" >>>>>> package="com.mypackage"> >>>>>> >>>>>> <application> >>>>>> <activity android:name=".devopts.DevOptionsActivity" >>>>>> android:screenOrientation="portrait"/> >>>>>> </application> >>>>>> </manifest> >>>>>> >>>>>> Please notice I don't have redundant <uses-sdk> tag in >>>>>> src/debug/AndroidManifest.xml file - only values which should be added >>>>>> to >>>>>> src/main/AndroidManifest.xml file, treated as a template. See our >>>>>> previous >>>>>> discussion around this topic under https://groups.google.co >>>>>> m/forum/#!searchin/adt-dev/uses-sdk/adt-dev/aKPgAXreGFo/k59O5P_-iz0J. >>>>>> Seems like you fixed it in 10.0.1. >>>>>> >>>>>> Let me know in case of any other feedback >>>>>> >>>>>> M. >>>>>> >>>>>> W dniu czwartek, 22 maja 2014 00:57:29 UTC+2 użytkownik Jerome Dochez >>>>>> napisał: >>>>>>> >>>>>>> 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.gr...@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+u...@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+u...@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+u...@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. >> >
-- 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.