Events do not trigger unless 'refresh' is pressed about easer

[renyuneyun]

Whoops, thanks for reporting!

I haven't really tested, but I think it is possible that I used the wrong / incomplete intent filters for BatteryEventPlugin (so Easer didn't receive that Broadcast and won't perform actions).
Unfortunately, I don't think there is a way to get this information because we can't know if the code missed something (not catching an Intent / Broadcast) (unless we can know which Broadcast is on the way in Android system's view). Appreciate a lot for your willing to help :)

p.s. As of battery status, waiting for a while shouldn't be needed unless the device is extremely slow :P

Indeed, the second problem is annoying. I'm planning to get rid of that (by implementing #19), but unfortunately that behavior is going to be changed only after #19 is done. (Though it is possible to get rid of that now, it requires external storage or an extra dedicated component, and they will be dropped/removed when #19 is done.)

[renyuneyun]

707f988 (v0.3.3.2) should have fixed the first issue.

Please report back after you have a try :P

[craftyguy]

Cool, thank you! I will not be able to test this until the new version is picked up by f-droid.

…

On July 10, 2017 9:21:15 AM MDT, renyuneyun ***@***.***> wrote: 707f988 should have fixed the first issue. Please report back after you have a try :P -- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: #20 (comment)

[craftyguy]

This appears to be resolved now, thank you!