Android app won't play high bit rate MP3

[ralphchrisdavis]

I have two Android devices. My phone which is running Android 2.3.6 won't play high bit rate MP3's using the Subsonic Android app. This used to work fine. The web page interface still works fine with high bit rate MP3's. Also my pad running version 4 Android plays fine using the Subsonic Android app.

I have tried various transcoding settings, including no transcoding at all, with no success. Although I just noticed this problem, it must have failed with one of the Subsonic updates. Either the Subsonic PC software or the Subsonic Android software.

Does anyone have any suggestions how to fix this besides buying a new phone?

[ralphchrisdavis]

Any one? This got broken in the last few months by one of the updates.

[ralphchrisdavis]

I hope someone can help. I have since discovered that many other browsers also do not work with high bit rate, such as 320 kbs, MP3 files. Google Chrome under Windows XP, Internet Explorer under Windows XP, etc. The Subsonic Android app and the regular Android web browser don’t work either. The only thing it seems I can depend on are 128 kbs files.

I am lost to locate where the problem is. Is it the browser or the server? I have read about Java issues. Is it the version of Java I am using on the server? Where do I look? Has anyone else seen these problems? Everything used to work great and now practically nothing does. My server is running Windows Server 2003 and I am a paid Subsonic user.

[ralphchrisdavis]

Please help. At least let me know if I am asking obvious questions or if I have found a real problem.

I downloaded the latest version of FFmpeg and got some results. Chrome under XP now plays high bit rate files OK. IE8, the browser in my Samsung phone and the Android Subsonic app still will not play.

There don’t seem to be any hints in Subsonic’s log file. In fact the browsers and the Subsonic app that don’t play also don’t make any entries in the log file. Here are the last few lines. One of them does seem to show an error but the timing is wrong for it to be from my failed attempt at playing an MP3.

105734 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Looking for RMI registry at port '9412'
106719 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Could not detect RMI registry - creating new one
106812 [main] INFO org.springframework.remoting.rmi.RmiServiceExporter - Binding service 'SubsonicDeployerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[10.168.3.100:9412](local),objID:[0:0:0, 0]]]]
421937 [btpool0-5] INFO org.directwebremoting.log.startup - Starting: DwrServlet v3.0.0.116.rc1 on jetty-6.1.x / JDK 1.7.0_71 from Oracle Corporation at

[ralphchrisdavis]

Well, I may be getting farther. After replacing all of the instances of FFMPEG that I found with the latest version I am seeing some improvement. My Android Subsonic app started working after I uninstalled and then reinstalled it. Will see if it lasts. Also I noticed that Google Chrome under XP seems to work OK.

At this point what doesn’t work is the regular Android web browser, Chrome under Android and IE8 under XP. When I select an MP3 file to play under any of these browsers nothing happens. Nothing even shows up in Subsonic’s log files. More and more this is looking like a Flash failure and may well be unrelated to bit rate as previously thought. Got any ideas?