Aard2 0.54 fails to start on AOSP 4.4.4 …
Olf0 opened this issue · 4 comments
… while v0.53 works fine. All aard2 APKs were obtained from F-Droid.
I see that v0.54 still has minSDK=19 defined (and its APK installs fine), but there were extensive changes in the build configuration and scripts.
P.S.: I am still running such ancient Android, because it is actually the "Alien Dalvik" Android Runtime environment under Sailfish OS (a Linux distribution) on an Xperia X. Jolla Oy, which provides Sailfish OS and Alien Dalvik unfortunately only releases newer versions of Alien Dalvik for later Sony Xperia models, though Jolla still provides recent Sailfish OS releases for the original Xperia X.
P.P.S.: It was a bit complicated to obtain logs for this AOSP derivate running in a LXC container, and the old documentation is gone (only maintained for recent Alien Dalvik versions with AOPS ≥ 9), but I can invest some time to retrace how this is achieved, if logs are strictly necessary.
P.P.P.S.: Thank you very much for providing and maintaining aard2 for such a long time, @itkach. I am using it irregularly, but each time I do, I appreciate this fine piece of software a lot!
Sorry to hear 0.54 is broken for you. It would be interesting to know if .apk from Github releases also doesn't work. I don't know how F-droid builds the apk and i don't use it. One possibility is that it's just F-droid apk that's broken, another is that Android tooling broke compatibility with the really old runtimes. Or could be something else entirely, but without the logs no way to tell. In any case, try the .apk from Github.
@itkach, thank you for your reply.
It would be interesting to know if .apk from Github releases also doesn't work.
O.K., I will try that first, because it is easier than rediscovering how to access a Android log. As I am travelling this week, this will be on the upcoming weekend, earliest.
Or could be something else entirely, but without the logs no way to tell.
This is what I expected. Well, when trying hard to remember I achieved that years ago (when the documentation was still online), plus digging deep in the two SailfishOS forums I will likely be able retrace this information.
O.K., I found the old forum entries ([1], [2]) and the current, proper documentation for using logcat on Alien Dalvik (aka "Android App Support (AAS)").
But I fail to record anything relevant!
As I faintly remember, that one must have root privileges to access logs from other applications since Android 4, I did not try to record logs from within Android (i.e., in a terminal app), hence used:
[root@phone aard-logcat]# /usr/libexec/droid-hybris/system/bin/logcat -v threadtime -b main -b system -b crash -b events -f aard-0.54.catlog.txt -d *:V
And before that the same with Aard 0.53 installed:
[root@phone aard-logcat]# /usr/libexec/droid-hybris/system/bin/logcat -v threadtime -b main -b system -b crash -b events -f aard-0.53.catlog.txt -d *:V
Both logs do not show anything related to Aard, even though Aard 0.53 did start correctly and Aard 0.54 crashed, as always: aard-0.54.catlog.txt and aard-0.53.catlog.txt
Any idea, what I am doing wrong?
linked docs says
There are two ways to use logcat: a) from Sailfish OS b) from Android App Support (see the next chapters). The resulting logs differ. Choose a) or b) depending on the problem you want to look at.
Perhaps you're doing a) but need to do b)?