-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AARD 2 doesn't start #108
Comments
You can look at the logs on device with https://developer.android.com/studio/command-line/logcat . |
Here is what I got with logcat:
I still can't launch the AARD2 app from my launcher (never had such problem before with any other apps), but I was able to open it via the adb command: |
After launching the app with adb and adding dictionaries I closed the app. Now it starts just fine from the launcher. When using the search box on a device with e-Ink screen both background and text are black. It would be nice to have an e-Ink friendly mode. Also when the word is found in multiple dictionaries it is great to see all the entries on one page. The MDict app allows to expand several entries from different dictionaries or only one of them. It is very convenient, so I highly recommend to take a look at this approach. |
Interesting. I don't see this above, but in the GH email notification log also has these lines:
I wonder if despite PackageManager claiming unavailable shared library will be ignored it actually results in force stopping the package... Also if you don't filter with grep perhaps there's more relevant context from the os side... |
Search box is actually built-in OS component, unfortunately long neglected and unmaintained. The app doesn't control how it looks. Perhaps it will be replaced since after recent system updates it stopped working altogether - see #107. Note that .apk I build won't work for you as is though, because Google now requires minimum target version of 26 if I'm not mistaken for the app to be published in Play Store, and Android 4.2 is 15. |
This has been discussed before. In short, this approach would require a significant rewrite and doesn't work well for long content such as Wikipedia/Wiktionary. It's not going to happen (although people are free to write new UIs for the app if they feel so inclined). |
Here is the the full log
|
I don't know how it works, but, unlike many other apps that don't work on my Likebook Plus with Android 4.2, Google Play still shows that AARD 2 is compatible with all my devices. And I can install it. I was also able to launch it from within the CoolReader and it translates just fine. The only problem so far was with launching it. May be it is somehow related to the first log I posted above and then edited it above: |
I get "The requested URL was not found on this server." |
You mention versions 0.38 and 0.39. Minimum target version was bumped in 0.40 (Play Store requirements) so you don't see it or later ones (latest is 0.43) and you won't see any updates that might be pushed to the Play store because it is not possible to publish to the Play store anything targeting Android < 8 (even if technically it is still compatible with those older versions) |
Please copy the URL with the underscore |
Tried to install version 0.43 with adb install and it worked. Tried to re-install from Google Play and in the about section I see the same version - 0.43. p.s. But after re-installing I can only start it with adb untill I add a dictionary and close the app.
|
I was reading this, because I also observe Aard2 0.43 not starting on AOSP 4.1.2 (API level 16) and AOSP 4.4.4 (API level 19), while v0.41 (and older versions) works fine on both devices. All these versions are / were installed from F-Droid (which states that the minimum Android version is 4.0.3 for Aard2 0.4{1,3,4}) per F-Droid client app. I will try v0.44 (first the version compiled at F-Droid, then the one from the releases here) this weekend. If Aard 0.44 still shows this issue, I might provide logs from a these devices. |
I didn't have any problem installing AARD 2 onto Likebook Plus (with Android 4.2 only). But when I tap the AARD 2 icon from a launcher, it doesn't start. Tried version 0.38 and 0.39, but the result was the same. Is there any debugging information that can be analyzed to try to fix the problem?
The text was updated successfully, but these errors were encountered: