question

Microleaks avatar image
Microleaks asked

setLooping audio bug on HD

The new HD versions of the Kindle are based on Android 4.0, which is a version that is affected by the setLooping audio bug ( http://code.google.com/p/android/issues/detail?id=18756) which I reported to the Google bug tracker about a year and a half ago. The code to test this bug is very simple... // someValidPath would be an audio file that is designed to be seemlessly looped, in my case an ogg vorbis file Media Player mediaPlayer = MediaPlayer.create(this, Uri.parse(someValidPath)); mediaPlayer.setLooping(true); mediaPlayer.start(); Since android 2.3.x this bug doesn't allow for the seemless looping of audio which worked fine is all android versions prior (and thus on the original Fire). There is a noticeable gap in the looping now which many users are complaining about on the HD devices. Starting with Android 4.1 a work-around was introduced that allows for seemless looping of audio. Here is my question and it is really intended for a Amazon engineer, but I would take anyone's input. My app is currently in the top 100 paid apps but is taking a beating by this bug. Is there any hopes of ever seeing the HD devices updated to the upstream Android 4.1 or higher codebase? If not, is there any chance of seeing setNextMediaPlayer(MediaPlayer next) back ported to the HD devices? Is there even a bug tracker that I could report this bug to? Thanks, Chuck
fire tablet
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

3 Answers

Sachin@Amazon avatar image
Sachin@Amazon answered
Hi Chuck, The Kindle Fire Tablet detail pages at www.amazon.com provide all of the information we have made available about Kindle Fire Tablet features and specifications. We cannot speculate on future availability of features and functionality. That being said, we will continue to monitor the setLooping audio bug as per the link you provided. There were a couple of comments that stated the issue still persists w/ OS 4.1.1. Thanks, Sachin
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Microleaks avatar image
Microleaks answered
The bug has been worked around in 4.1+, code modifications are required, but you can use: MediaPlayer.setNextMediaPlayer Before this, there was no work around as it was added in API level 16. I seeing many negative reviews because of this bug on my product page and I wish there was more that I could do. I would love to see this method (setNextMediaPlayer) backported. http://www.amazon.com/CWS-Software-LLC-Sleepy-Time/dp/B004V5QWU2/ref=sr_1_1?s=mobile-apps&ie=UTF8&qid=1356363122&sr=1-1&keywords=sleepy+time
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Sachin@Amazon avatar image
Sachin@Amazon answered
Hi Chuck, We understand your concern and have forwarded your issue to the concerned team. Thanks Sachin
10 |5000
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.