Hi Dario, Well, we're still stalled on this problem. We're experiencing this issue with our Android music engine. The previous programmer observations I mentioned came from our UI team. Our engine team spent a couple hours investigating and weighed in on this. This is what they sent to me today: -------------------- Hi, Doc. Here is my current thoughts: BeamzEngine is not using MediaExtractor. We decoding MP3 in native C++ code by using minimp3 library. minimp3 is provided in source code and it is platform independent, so I don't think that it uses MediaExtractor (at least I don't see it in minimp3 sources). To work with mp3 files we using simple fopen/fclose/mmap/munmap functions, they are definitelly exists on any Android system. So I think problem in another place, mp3 decoding is not the reason of this problem. Java part of BeamzEngine uses android.media.AudioManager to query system audio params. Here is its usage: // "_context" here is activity, passed to BeamzEngineFactory.createEngine or BeamzEngineFactory.createEngine2 Object audManObj = _context.getSystemService(Context.AUDIO_SERVICE); AudioManager audMan = (AudioManager) audManObj; String fpb = audMan.getProperty(AudioManager.PROPERTY_OUTPUT_FRAMES_PER_BUFFER); String sr = audMan.getProperty(AudioManager.PROPERTY_OUTPUT_SAMPLE_RATE); Another possible place: for mp3 recording we are using OpenSL ES. Maybe it is uses MediaExtractor in its implementation. But you are saying that changing of song files from mp3 to wav fixes the problem, so it is doent't looks like what file recording or quering of system audio params is the reason. But maybe I am wrong. -------------- To recap, Our Android engine runs perfectly on other Android systems. This issue only shows up on the Focus Android device, so it's something unique to the Focus. Our engine programmers will continue to debug this but, we will also be relying on your assistance. Thanks Doc
... View more