"Invalid Qt version" on Asus Tranformer

[Sebastian Diel]

Hi,

one of my testers reports an "invalid Qt version" problem on his Asus
transformer (Android 4.03).
Installing went through, Ministro was downloaded from Google Play Store.

But with each start he encounters the "Invalid Qt version" error.

We have tried:
- Configuration tool (neither stable, nor testing, nor unstable work)
- Clearing the data of Ministro
- Installing Ministro II v8.9.2.apk
- De- and reinstalling my App.

On other devices the app runs flawlessly.
I myself actually run out of ideas...

Sebastian

[Ray Donnelly]

You *could* be running into the armeabi/armeabi-v7a problem in Android
4.0.0 ... 4.0.3

Here's some reference:

http://code.google.com/p/android/issues/detail?id=25321

Did you try to install and use your APK on an API-14 AVD?

You need to get logcat output from the user if possible.

> --
> You received this message because you are subscribed to the Google Groups
> "android-qt" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to android-qt+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Sebastian Diel]

Am 16.02.2013 22:00, schrieb Ray Donnelly:
> You *could* be running into the armeabi/armeabi-v7a problem in Android
> 4.0.0 ... 4.0.3

Wouldn't that mean that the app just yields a poor performance? I've
read that
armeabi should work on all devices (albeit considerably slower without
hardware
floating point operations etc.) - but then again I am on a very
unfamiliar terrain
here and without much knowledge about what Necessitas actually does "under
the hood".

Looking into my apk I just realized that I only offer a lib/armeabi
folder, in it i find
a "gdbserver" and a "libclassInTouch.so". No armeabi-v7 folder.

In Necessitas the default kit is "Qt 4.8.2 for Android armv5 (default)

> http://code.google.com/p/android/issues/detail?id=25321
This seems to be a problem with choosing the right .so file (correct?) and
there is no choice in my apk. Perhaps this is the problem in the first
place?

> Did you try to install and use your APK on an API-14 AVD?

I've just tried that - the apk installs & works without problems.

> You need to get logcat output from the user if possible.

I'll try to come back with the log.
Best regards and thank you very much for your work and your support!

Sebastian

Thanky you for now!
Sebastian

[Sebastian Diel]

Hi,

thank you very much for the logcat hint, Ray!

With the log (saved via Android System Info) I've found the culprit:
02-17 14:24:44.064 W/System.err(1415)at
org.adblockplus.brazil.SSLConnectionHandler$ConnectionHandler.run(SSLConnectionHandler.java:165)

After that, recieving the files went down the drain, of course:
02-17 14:24:44.064 W/System.err(1415)Caused by:
libcore.io.ErrnoException: recvfrom failed: ECONNRESET (Connection reset
by peer)
02-17 14:24:44.064 W/System.err(1415)at
libcore.io.Posix.recvfromBytes(Native Method)
02-17 14:24:44.064 W/System.err(1415)at
libcore.io.Posix.recvfrom(Posix.java:131)
02-17 14:24:44.064 W/System.err(1415)at
libcore.io.BlockGuardOs.recvfrom(BlockGuardOs.java:164)
02-17 14:24:44.064 W/System.err(1415)at
libcore.io.IoBridge.recvfrom(IoBridge.java:503)
02-17 14:24:44.064 W/System.err(1415)... 4 more
02-17 14:24:44.064 I/https. (1415)SSL connection closed
02-17 14:24:44.064 I/ProxyService(1415)request done
02-17 14:24:44.064 D/ProxyService(1415)socket close
[...some freeing and stuff...]
02-17 14:24:44.884 E/MinistroService(19374)Invalid qt verson

[Solution]:
Just deactivating Adblock did the trick. It can probably be activated
again after retrieving the libs.

Thank you,
Sebastian

Am 16.02.2013 22:00, schrieb Ray Donnelly: