[Android-development] [Development] Help needed to test Ministro 10.3, needed for Qt 5.4!

Harri Pasanen harri at mpaja.com
Thu Nov 27 10:53:03 CET 2014 

My comment was not very clear, I meant the Qt Creator deployment 
options, not Ministro.    Both seem to be affected by security motivated 
changes in Android file access policy.


On 27/11/2014 08:38, BogDan wrote:
> Hi,
>
>    Ministro is *NOT* downloading the Qt libs & resources in a temporary folder, nor on SD card! It downloads them into its own private folder (which is a safe place) then it changes the file permissions to 0644 (MODE_WORLD_READABLE), this way any application can read them, but only Ministro can change them.
>
> Cheers,
> BogDan.
>
>
> ----- Original Message -----
> From: Harri Pasanen <harri at mpaja.com>
> To: android-development at qt-project.org
> Cc:
> Sent: Wednesday, November 26, 2014 10:27 PM
> Subject: Re: [Android-development] [Development] Help needed to test Ministro 10.3, needed for Qt 5.4!
>
> I don't know for sure, but it is likely related.
>
> Already now with KitKat 4.4.2 I've been unable use local libs deployed
> to temporary directory due to various errors.
>
> I've been wondering is it not possible to deploy the Qt libraries to an
> app specific directory and then just update the apk in place, rather
> than using a temp directory?   A related question is that can an app
> write its own shared libs?   If it can, then I assume for development
> purposes that could work so that app copies the libs it uses from some
> common area.   That might be faster than over the usb deployment.
>
> Harri
>
> On 26/11/2014 19:55, md at rpzdesign.com wrote:
>> Oops, I meant to say non-rooted devices.
>>
>> Rooted devices can likely put the QT5 libraries permanently in an area
>> where any app can get to them.
>>
>> md
>>
>> On 11/26/2014 1:53 PM, md at rpzdesign.com wrote:
>>> Does this also kill Rooted devices used for development that allow us to
>>> compile a minimal executable for upload to the device and shorten the
>>> compile-upload-debug cycle times?
>>>
>>> I like the idea of having a quick dev cycle time so I don't spend the
>>> rest of my days waiting for USB ADB executable uploads and debugger running.
>>>
>>> md
>>>
>>> On 11/26/2014 1:08 PM, Harri Pasanen wrote:
>>>> Hmm... looking at the issue it seems to me that it is not going to be
>>>> fixed, it is an intentional change.   They are tightening the platform
>>>> from security point of view, and this change is similar to change that
>>>> made removable SD cards much less useful in KitKat:
>>>> https://plus.google.com/+TodLiebeck/posts/gjnmuaDM8sn
>>>>
>>>> http://developer.android.com/reference/android/content/Context.html#MODE_WORLD_READABLE
>>>> says it has been deprecated since API level 17, so I doubt they'll bring
>>>> it back.
>>>>
>>>> Ministro has had a good run, but unless I'm mistaken this basically
>>>> kills it?
>>>>
>>>> Harri
>>>>
>>>>
>>>> On 26/11/2014 13:28, Cristian Adam wrote:
>>>>> Please "star" the android issue so that Google developers understand
>>>>> the severity of the problem.
>>>>>
>>>>> It's not like only six people are affected by this.
>>>>>
>>>>> Cheers,
>>>>> Cristian.
>>>>>
>>>>> On 26 Nov 2014 12:45, "BogDan" <bog_dan_ro at yahoo.com
>>>>> <mailto:bog_dan_ro at yahoo.com>> wrote:
>>>>>
>>>>>       Hello folks,
>>>>>
>>>>>       I have some bad news about Ministro on Android 5.0. Due to a
>>>>>       bug https://code.google.com/p/android/issues/detail?id=79478 introduced
>>>>>       by Google in Android 5.0 final release apps that are using
>>>>>       Ministro are not working anymore, on Android L preview it worked
>>>>>       just fine. I hope in the next Android version Google will fix this
>>>>>       problem.
>>>>>
>>>>>       New stuff added to Ministro 10.
>>>>>       - application startup up speed improvement, I've cuted +150ms from the
>>>>>       time that your application needs to wait for Ministro's response, now
>>>>>       your application waits 2-4ms (of course if Ministro doesn't need to
>>>>>       download/extract anything).
>>>>>       - extract Qt 5.4 QuickControls style info
>>>>>       - speed up the theme extraction (now it needs 2/3 of the previous
>>>>>       time).
>>>>>       - extract InsetDrawable. On Android 4.4.4 it seems this Drawable is
>>>>>       used and will crash QWidget based apps if is not extracted.
>>>>>
>>>>>       New stuff added to 10.1
>>>>>        - bumped MINISTRO_MAX_API_LEVEL
>>>>>
>>>>>       New stuff added to 10.3
>>>>>        - for more exceptions on Android 5.0
>>>>>        - extract default palette & fonts, needed by Qt 5.4
>>>>>        - extract some Android 5.0 specific look and style info.
>>>>>
>>>>>       What happen with 10.2?
>>>>>        - I bumped the version to 10.3 by mistake and I pushed it, so
>>>>>       there was no 10.2 :).
>>>>>
>>>>>       How to test it:
>>>>>       - make sure the previous version is installed and your apps are
>>>>>       using it.
>>>>>       - install over the previous version ($ adb install -r Ministro\
>>>>>       II\ v10.3.apk).
>>>>>         * Ministro will extract again *ONCE* the style.
>>>>>         * Trying your existing apps should *NOT* trigger any new downloads.
>>>>>       - after you test your applications with Ministro installed on top of
>>>>>       previous Ministro version, please test in on a clean installation. So,
>>>>>       go to settings -> apps and remove Ministro, then install it again ($
>>>>>       adb install Ministro\ II\ v10.3.apk).
>>>>>         * Ministro should extract style info and certificates and it should
>>>>>       download again all needed libs.
>>>>>         * Your application should work without any recompilation.
>>>>>
>>>>>
>>>>>       Please download and test Ministro from here:
>>>>>       https://files.kde.org/necessitas/installer/test/Ministro%20II%20v10.3.apk
>>>>>
>>>>>       Thank you!
>>>>>
>>>>>       Cheers,
>>>>>       BogDan.
>>>>>
>>>>>
>>>>>       _______________________________________________
>>>>>       Development mailing list
>>>>>       Development at qt-project.org <mailto:Development at qt-project.org>
>>>>>       http://lists.qt-project.org/mailman/listinfo/development
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Necessitas-devel mailing list
>>>>> Necessitas-devel at kde.org
>>>>> https://mail.kde.org/mailman/listinfo/necessitas-devel
>>>>
>>>> _______________________________________________
>>>> Android-development mailing list
>>>> Android-development at qt-project.org
>>>> http://lists.qt-project.org/mailman/listinfo/android-development
>>> _______________________________________________
>>> Android-development mailing list
>>> Android-development at qt-project.org
>>> http://lists.qt-project.org/mailman/listinfo/android-development
>>>
>> _______________________________________________
>> Android-development mailing list
>> Android-development at qt-project.org
>> http://lists.qt-project.org/mailman/listinfo/android-development
> _______________________________________________
> Android-development mailing list
> Android-development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/android-development

More information about the Android-development mailing list