這裏有一個報告的問題https://code.google.com/p/android/issues/detail?id=77860
Reported by [email protected], Oct 21, 2014
Description:
I noticed MediaPlayer.OnCompletionListener callback behavior seems to be changed since Lollipop.
[KitKat]
- setLooping(false), setNextMediaPlayer(null)
-> onCompletion() is fired
- setLooping(true), setNextMediaPlayer(null)
-> onCompletion() is not fired
- setLooping(false), setNextMediaPlayer(other valid instance)
-> onCompletion() is not fired
- setLooping(true), setNextMediaPlayer(other valid instance)
-> onCompletion() is not fired
[Lollipop (when using AwesomePlayer)]
- setLooping(false), setNextMediaPlayer(null)
-> onCompletion() is fired : OK
- setLooping(true), setNextMediaPlayer(null)
-> onCompletion() is not fired : OK
- setLooping(false), setNextMediaPlayer(other valid instance)
-> onCompletion() is fired : ???
- setLooping(true), setNextMediaPlayer(other valid instance)
-> onCompletion() is not fired : OK
[Lollipop (when using NuPlayer)]
- setLooping(false), setNextMediaPlayer(null)
-> onCompletion() is fired : OK
- setLooping(true), setNextMediaPlayer(null)
-> onCompletion() is fired : ???
- setLooping(false), setNextMediaPlayer(other valid instance)
-> onCompletion() is fired : ???
- setLooping(true), setNextMediaPlayer(other valid instance)
-> onCompletion() is fired : ???
Tested environment:
- Nexus 7 2013
- Android 5.0 (LPX13D)
bugreport.txt.tar.gz
740 KB Download
Oct 22, 2014 Project Member #1 [email protected]
Thank you for reporting this issue. We have passed this on to the development team and will update this issue with more information as it becomes available.
Status: Accepted
Owner: [email protected]
Labels: 18080636
剛剛檢查官方android棒棒糖,仍然無法正常工作。 – Alex 2014-11-16 08:26:07