fix(android): onPlayerStateChanged is not called when audio has completed playing

[fzyzcjy]

Description

Close #1522

I am not sure whether this is the best way, but I can confirm it fixes the bug I see, and IMHO there are not infinitely many handler callbacks, so skipping this cancelation does not cause harm.

Checklist

• The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs:, chore: etc).
• I have read the Contributor Guide and followed the process outlined for submitting PRs.
• I have updated/added tests for ALL new/updated/fixed functionality.
• I have updated/added relevant documentation and added dartdoc comments with ///, where necessary.
• I have updated/added relevant examples in example.

Breaking Change

• Yes, this is a breaking change.
• No, this is not a breaking change.

Related Issues

[Gustl22]

Nice catch!

Do you think updateRunnable?.let { handler.removeCallbacks(it) } would do the trick?

But I'm a bit confused about the comment below this, but it should't make a big difference, as the runnable (and it's loop) will end after one update circle. We may should test this once anyway :)

[fzyzcjy]

Do you think updateRunnable?.let { handler.removeCallbacks(it) } would do the trick?

I am not sure. If it only removes that one specific runnable then maybe yes?

[fzyzcjy]

Btw this is partially why I do hope to implement #1527 - then there is no such callbacks, runnables, threads, etc!

[Gustl22]

@fzyzcjy Is it ok for you to merge it like this (after my changes)?

[fzyzcjy]

LGTM! (not tested yet though)