Hi,
    
      it seems that Kindle kills Aedict Popup in spite of Popup having a
    service defined. You can verify in your device settings that when
    the Popup stops responding, the Popup service is stopped. The
    service is stopped by the Android system, even though there is a
    promise by Android to only stop services when the system is really
    really low on memory. I guess Kindle is somewhat special in this
    regard, maybe it stops Services to save battery/go into deep
    sleep/some other reason.
    
    The thing is that when Popup is killed by Android, the clipboard
    listener is removed by Android and there's not much Aedict Popup can
    do about it. The only thing is to add an alarm timer which wakes up
    Popup every 1 second and re-registers the clipboard listener. The
    trouble with this solution is that it would kill your battery really
    fast, that's why the AlarmService actually only allows wake-up calls
    once every 60 seconds or so. That would mean that the Popup is
    basically randomly dead for 1..59 seconds until the alarm service
    ticks.
    
      I have created a question regarding this:
    
https://stackoverflow.com/questions/49727040 
    Don't hold your breath though - Android is a piece of crap and this
    limitation is probably not solvable.
    
    I imagine that the Google Translate service suffers from the very
    same issue. It would be interesting to test this assumption.
    
    Best,
    Martin