Back to Top

Forgets Audio Location

3 posts / 0 new
Last post
Stangs55
Offline
Last seen: 10 years 1 week ago
Joined: 11/14/2009 - 16:17
Forgets Audio Location

Sadly, this bug has existed for a while and is why I've been using Google Listen as my main player for a couple months now. I've been delaying coming and posting here out of laziness...but after seeing each update fail to fix this, I thought I'd pop my head in here again.

Whenever I'm listening through the headphone jack and I just unplug the headphones to stop the playback, it usually (~75% of the time) completely forgets where in the podcast it left off...so that the next time I insert the headphones and hit play, it picks up either at the previous start position before I last listened or about 5-10 minutes before the actual location it stopped. This results in my searching and scanning for the actual location that playback had stopped.

eric
Offline
Last seen: 4 months 5 days ago
Joined: 11/06/2008 - 22:02
Playback position

I have an old issue for this but it's been dormant because it stopped happening to me and I hadn't heard of anyone else experiencing it. I just moved the issue up in scheduling, hopefully I can gather enough info to figure out what's happening.

Is your seekbar updating while the audio is playing? The code that remembers the position is near the code that updates the seekbar so I would expect them both to work or fail at the same time.

I don't have any logging around that right now but I'll add some to the next release so I can get a better picture of what's happening.

http://mantis.snoggdoggler.com/view.php?id=307

eric
Offline
Last seen: 4 months 5 days ago
Joined: 11/06/2008 - 22:02
Found bug, probably what's happening to you.

If DC is not running and you start playing the audio by pressing the headset button or the widget play button (without starting the app first), then wherever the audio stops playing is forgotten.

You can workaround this by making sure DC is running before pressing on the widget play button or pressing the headset button.

I'll try to get a fix for this in the next release.

Thanks for posting.