The issue seems to have gone away with a dictionary update, so that may be
a clue :)
Again, amazing program! I bought the stroke drawing program even though I
don't need it, so that I could pay you in some way since you refuse paypal
On Aug 23, 2015 4:31 PM, "Martin Vysny" email@example.com wrote:
Thank you for letting me know, and I apologize for this behavior. I will
try to reproduce the issue myself, please stay tuned.
Well, I do not reject donations per se ;) I will gladly accept the donations via PayPal, my mail address is firstname.lastname@example.org. Any support is highly appreciated. Let me look at this pesky issue. Meanwhile, it would be of tremendous help if you could obtain the stack trace information bound to that DeadObjectException. This would require you to install Android SDK - would you be interested in doing that? You can find more information here: http://aedict.eu/faq.html, the "Aedict 3 log" section.
Unfortunately I cannot reproduce this issue myself. I can try to perform a blind fix, but first I would perhaps try to reproduce the issue. Can you please describe in more depth, how exactly are you switching to Aedict from some other app? I tried both sharing selected text to Aedict and activating the persistent notification message, but I get no DeadObjectException. Perhaps the KanjiPadExt service is killed by your phone during the drawing lookup, because of low memory? What kind of phone do you have, and how much memory does it have?
In order to do the blind fix, I will need the stack-trace of the DeadObjectException exception though - can you please install the Android SDK, obtain the log and paste it here?
If you switch to Aedict from some other app (Anki in my case) while Aedict was already instantiated, the stroke kanji search fails with the following message: Failed to find kanjis, a
The text was updated successfully, but these errors were encountered: