Hello, Same problem on my desire, it is quite anoying, my app rely on the mediaplayer, so I have maybe a quarter of people using my app having this problem, and there is nothing I can do...
On 9 juil, 15:11, k_day <[email protected]> wrote: > I am seeing this exact same thing on my Hero. Have you made any > progress? > > On Jun 30, 3:20 am, MobDev <[email protected]> wrote: > > > > > Hi there, > > I have installed the 2.1 update on my HTC Hero yesterday, and happy as > > a puppy I instaleld my streaming app... Just to discover that it won't > > stream decently... It has to stream an mp3 stream and it works on my > > ADP 1.6 device, on a Samsung Galaxy S test-device (with 2.1) and on > > the 2.1 emulator... > > Logcat is gettign the follwoing errors : > > > 06-30 10:14:18.360: INFO/AudioPolicyService(56):stopOutput(): before > > lock > > 06-30 10:14:21.259: DEBUG/dalvikvm(1906): GC freed 28 objects / 1944 > > bytes in 186ms > > 06-30 10:14:21.439: INFO/AudioHardwareMSM72XX(56): AudioHardware pcm > > playback is going to standby. > > 06-30 10:14:21.439: DEBUG/StreamProcess(56): > > OutputStreamProcess::ResetAOLC() > > 06-30 10:14:22.919: INFO/AudioPolicyService(56): startOutput(): before > > lock > > 06-30 10:14:22.987: INFO/AudioHardwareMSM72XX(56): AUDIO_START: start > > kernel pcm_out driver. > > 06-30 10:14:26.329: DEBUG/dalvikvm(287): GC freed 11 objects / 488 > > bytes in 268ms > > 06-30 10:14:47.789: INFO/AudioPolicyService(56):stopOutput(): before > > lock > > 06-30 10:14:50.879: INFO/AudioHardwareMSM72XX(56): AudioHardware pcm > > playback is going to standby. > > 06-30 10:14:50.879: DEBUG/StreamProcess(56): > > OutputStreamProcess::ResetAOLC() > > 06-30 10:14:53.911: INFO/AudioPolicyService(56): startOutput(): before > > lock > > 06-30 10:14:54.022: INFO/AudioHardwareMSM72XX(56): AUDIO_START: start > > kernel pcm_out driver. > > > The result is a playing player, which stops (pauzes) every 10 seconds, > > the restarts... This will work for about 8-10 restarts and then will > > simply stop without ever thrwoing an exception or something like > > that... Which makes it somewhat difficult (if not impossible) to catch > > for us developers... > > So has anyone been experiencing the same problem ? Does anyone have a > > clue if in this update another OpenCore lib has been used ? Does > > anyone have any solution ? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
