search

joecks / clipboard-actions-community

A issue tracker for the Clipboard Actions Project
http://joecks.github.io/clipboard-actions/
Other
85 stars 21 forks source link

Service is not starting at boot. Manually started service gets killed. #26

Open bagarwa opened 8 years ago

bagarwa commented 8 years ago

Whenever I reboot my phone, Clipboard Action doesn't start with it. I have to manually launch the app to get its service running. Even after that, looks like the service gets killed pretty often. Because, after sometime, copying any text doesn't trigger CA notification.

I have a Nexus 6P, running stock Android 6.0.1, Rooted.

joecks commented 8 years ago

Hmm that sounds like a serious issue, could you please upgrade to the lastet version and let me know if this was fixed. Btw. BOOT_COMPLETE is an event which is fired sequentially to all registered apps and thus can hit Clipboard Actions late after the device is booted, then it will not start, I guess in your case very late.

joecks commented 8 years ago

Thanks for this question. Could you check if the latest updates helps with your issue?

Cheers Simon

On Thu, Mar 3, 2016, 17:43 bagarwa notifications@github.com wrote:

Whenever I reboot my phone, Clipboard Action doesn't start with it. I have to manually launch the app to get its service running. Even after that, looks like the service gets killed pretty often. Because, after sometime, copying any text doesn't trigger CA notification.

I have a Nexus 6P, running stock Android 6.0.1, Rooted.

— Reply to this email directly or view it on GitHub https://github.com/joecks/clipboard-actions-community/issues/26.

bagarwa commented 8 years ago

It is still failing to start at boot. I've waited an hour. I'm having to manually launch the app to get it started. And now I've enabled the foreground service via its sticky notification so it doesn't get killed.