I don't know if this is a popular issue, but I wasn't sure what to call it in order to search for it.
I have an iPhone 3G running the latest software. I noticed this start to happen before 4.2.1, but only in the version before 4.2.1.
I listen to a short, daily podcast and this is where I first noticed the problem. For example, I'd select the podcast for Thursday, but then once the narrator of the podcast identified the date, I realized it was the podcast for Friday.
Eventually I thought to watch it, and when I would select the podcast (all previously unlistened to), it would automatically track to the very end of the podcast I selected, causing the app to go to the next day's podcast in my list.
I thought this was pretty annoying, but then I noticed on longer podcasts, like TWIT, I would select the unlistened episode and it would either start at the very end and then return to the podcast home screen, OR it would start randomly through--say 42 minutes into the 2 hour podcast.
I have now discovered the same thing in regular music files.
Anyone know if this is a known issue? I could try a restore that takes forever, but I wanted to check first. Thank you.
I have an iPhone 3G running the latest software. I noticed this start to happen before 4.2.1, but only in the version before 4.2.1.
I listen to a short, daily podcast and this is where I first noticed the problem. For example, I'd select the podcast for Thursday, but then once the narrator of the podcast identified the date, I realized it was the podcast for Friday.
Eventually I thought to watch it, and when I would select the podcast (all previously unlistened to), it would automatically track to the very end of the podcast I selected, causing the app to go to the next day's podcast in my list.
I thought this was pretty annoying, but then I noticed on longer podcasts, like TWIT, I would select the unlistened episode and it would either start at the very end and then return to the podcast home screen, OR it would start randomly through--say 42 minutes into the 2 hour podcast.
I have now discovered the same thing in regular music files.
Anyone know if this is a known issue? I could try a restore that takes forever, but I wanted to check first. Thank you.