Just got the Android 2.2.1 update on the Nexus one and this bug is still not fixed. What should I do now Google?
On Sep 20, 8:54 am, jdeslip <[email protected]> wrote: > Well, if you Google for "pandora froyo" you get a ton of pages with > people having this problem (at least I believe it to be the same). > One particularly insightful link is > here:http://forum.xda-developers.com/showthread.php?t=737111 > where they show you can fix the problem by reverting to the old > OpenCore engine instead of the new StageFright media engine used in > 2.2. This can only be done on rooted phones however... > > There is alos this > article:http://www.androidcentral.com/sirius-xm-app-updated-fix-froyo-bug > - Apparently sirius app had this problem and fixed it somehow. > Probably by changing the format to a lower bitrate on their server or > something which is not available to me in my emusic app. > > I wish someone from the Android team would comment here and let us > know what the appropriate route to take is. Is there a workaround we > can implement now? Is an updated froyo release on the way for affected > devices? > > On Sep 19, 11:07 pm, Ben Pellow <[email protected]> wrote: > > > > > > > > > I'm seeing this issue as well, and only with 2.2. I've seen it with > > the emulator, droid x, nexus one and moto droid. It happens lot more > > to me (10x+) with high bitrate streams than low ones (320 vs 120 kbps > > mp3). It seems intermittent and I can find nothing on the web posted > > about it other than this thread. > > > It is a real problem with media apps running in 2.2. The constant > > "-2147483648" always appears with this MediaPlayer error, and could > > probably be tracked down in the source. The problem is not with > > eMusic or the stream. I have seen the same issue with streams hosted > > by other services. > > > On Sep 18, 12:51 pm, jdeslip <[email protected]> wrote: > > > > Yes, it works fine on 2.1 and below. This is almost certainly related > > > to the problems the Pandora/Last.fm etc.. apps have on 2.2. I just > > > want to find out what the recommended tactic for developers with this > > > problem is. Is Google on verge of releasing an update 2.2? Or is > > > there an official workaround? > > > > On Sep 17, 11:58 pm, Indicator Veritatis <[email protected]> wrote: > > > > > If that were the problem, then why would it work under 1.5 and fail > > > > under 2.2? > > > > > On Sep 17, 8:50 pm, Doug <[email protected]> wrote: > > > > > > Have you considered that eMusic might be doing something on the server > > > > > side to prevent the stream from working? Many sites that stream > > > > > things will leave urls active for a limited time or require you to > > > > > preserve an HTTP session. -- 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
