That's a real shame! Just to clarify / for the record, is the following a result of MODE_WORLD_READABLE not working any more:
D/AndroidRuntime( 9159): Shutting down VM E/AndroidRuntime( 9159): FATAL EXCEPTION: main E/AndroidRuntime( 9159): Process: org.qtproject.example.foo, PID: 9159 E/AndroidRuntime( 9159): java.lang.UnsatisfiedLinkError: JNI_ERR returned from JNI_OnLoad in "/data/app/org.qtproject.example.foo-1/lib/arm/foo.so" E/AndroidRuntime( 9159): at java.lang.Runtime.loadLibrary(Runtime.java:371) E/AndroidRuntime( 9159): at java.lang.System.loadLibrary(System.java:989) E/AndroidRuntime( 9159): at org.qtproject.qt5.android.bindings.QtActivity.loadApplication(QtActivity.java:252) E/AndroidRuntime( 9159): at org.qtproject.qt5.android.bindings.QtActivity.access$400(QtActivity.java:94) ... or is it (as I first though) about a the deployment folder mismatch? (within the apk it's lib/armeabi-v7a, but the device looks for it in lib/arm/) Greets Thomas On 11/26/2014 07: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...@yahoo.com >> <mailto:bog_dan...@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@qt-project.org <mailto:Development@qt-project.org> >> http://lists.qt-project.org/mailman/listinfo/development >> >> >> >> _______________________________________________ >> Necessitas-devel mailing list >> necessitas-de...@kde.org >> https://mail.kde.org/mailman/listinfo/necessitas-devel > > > > _______________________________________________ > Necessitas-devel mailing list > necessitas-de...@kde.org > https://mail.kde.org/mailman/listinfo/necessitas-devel > _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development