Fix the time position recording bug on MTK65xx processors
I had a Wiko Cink Slim and now I own an Acer Liquid E2. On both devices the player is not able to restart a reading on the correct timemark after pausing for a period of time. It seems that this bug is specific to MTK65xx devices.
It would be great to find a way to bypass this bug on a software basis in order to not depend on hardware anymore
I might have found a workaround for this issue thanks to a user that helped me do a LOT of testing.
For those having this issue the workaround will have to be enabled from Settings/Player/Resume Playback Workaround
Edit: delivered in v2.4
@Milan you can try switching the player built-in engine in the device developer settings. Toggling the 'Awesome player' might help with this issue
Unfortunetly this problem appears on my Lenovo P70, which has MT6752. Workaround does't work.
What I can add is, that this problem was not there on Android 4.4. I appeared after update to Android 5.1.
Any help would be great!
Hi Xavier. Still have the issue in my Motorola Razr D3 - XT920. It is a lot better but not 100%. I can help you testing it if you want. I think your app is the best and don't wanna change for another, even if you don't wanna fix it in my device. Thank you anyway.
Malheureusement pour moi et mon wiko Cink slim, cette solution de contournement ne fonctionne que partiellement. En effet, le podcast ne reprend toujours pas à l'endroit où je l'ai stoppé, mais au lieu des reprises aux alentours des 9 minutes, il reprend à présent à environ 40 minutes. Un progrès donc ;-)
Merci malgré tout pour cette excellente application
Yes. Now all I need is resume on headphone plug in and this app will be perfect!
Stefanos Chatz commented
Great job! I was using doggcatcher because of this, now I'm back, loving it and off to donate :)
That's because it's not available on the play store ;)
It will be available in the next version
Michael DA COSTA commented
Ok thanks but I can't tick that options, tell us how ton unlock that please :)
I'm looking for someone that can help me build a workaround to fix this issue.
If you are Ok to test some beta version please send me a mail (firstname.lastname@example.org)
Same problem on wiko cink slim...
Mikel Muga commented
I have this problem in two mtk 6589 devices. Only doggcatcher has a option to fix it.
It can be an option to difference your app from others
As explained this is a known bug for those specific processors. So if your previous device had a different hardware then it's normal it was working fine
Michael DA COSTA commented
I have this issue too on my wiko cink five, i don't understand it worked on my xperia u before