CyanogenMod 10.2 (ADDED on November 18, 2013) Audio: Fix Visualizer's get/set parameter methods not worked bug Root-Box/frameworks_av#1ĥ.stagefright: Fix size of metadata key LiquidSmooth-Old/android_frameworks_av#1.I fixed it on LiquidSmooth, RootBox and VanirAOSP ROM, but I'm afraid that there are other custom ROMs still have this bug. Some custom ROMs have bugs on visualizer implementation. Some custom ROMs (Old LiquidSmooth, RootBox and VanirAOSP) Use MediaPlayer class based player apps (*1).(I don't know that Galaxy Nexus has this issue, but it's interesting because the phone using OMAP SOC.) I think the difference came from base platform difference, Nexus 4 and 7 (2013) are using Qualcomm's Snapdragon SOC, on the other hand Nexus 10 uses Samsung's Exynos SOC. Nexus 10 also supports low-latency playback, but it doesn't have the issue. However this issue only occurs on certain Nexus devices. But it has a side-effect, visualizer doesn't work while music playing by Open SL APIs. The Google has introduced low-latency audio playback feature since Android 4.1. So sometimes they support new features earlier than vendor customized models. Nexus series devices are Google's reference model Android devices. Nexus 4, Nexus 5 and Nexus 7 (2013) (maybe Snapdragon based Nexus only) NOTE 2) Originally, the tunnel player seems to have been introduced by Code Aurora Forum's developer.ģ. NOTE 1) This issue is already reported on Samsung's developer forum. (Novemadded: I found that MediaPlayer.start() is not required on the dummy instance, only MediaPlayer.prepare() call is needed. Second MediaPlayer instance will fall back on standard audio playback mechanism. Occupy tunnel player instance by dummy silent MP3/AAC file playback.Put "code = false" in build.prop file (!!! root required).Use Open SL API instead of MediaPlayer class (*2). Only one instance is permitted (can't create multiple tunnel player instances).Audio playback by MediaPlayer class (*1).There are several conditions for the tunnel player to be used. As a result, visualizer does not work at all. If the tunnel player is used, audio capturing process is bypassed. It uses hardware acceleration playback mechanism called "Tunnel Player (Tunnel Playback)" when playing music files. I investigated this issue and found the reason. My Galaxy S4 (SC-0E, JP model) corresponds to this case. Snapdragon based Galaxy S4 have visualizer not working issue. Galaxy S3, S4, Note 3 and derived models (Snapdragon model only) But I got some feedback from Galaxy S3 users that my app doesn't work on it. I have Galaxy S2 (SC-02C, JP model), but visualizer works well on it. Sorry, I don't know about this issue on these phones. Galaxy devices (except for S4) and HTC Rezound There are several reasons that makes visualizer not working. My app also have the similar issues, so I know some causes of them.įirst, visualizer not working issue is not a single issue. I'm developing and publishing "Music Visualizer" app on Google Play store. It is right now the only visualizer on the market, where this works. It seems like it is possible to solve this problem, because external visualization works on the Morphyre Music Visualizer. If you have this problem, I apologize! Please email me and I will refund you."Īlmost all visualizer apps on the market have this problem and can’t visualize from external players on the new Galaxy and some HTC devices. Still looking for a work-around, but we'll probably have to wait for a future version of Android to fix it. This is a problem for all music visualizer apps on these phones, as evidenced by user reviews of other apps. "NOTE: To Galaxy S/S2/S3/S4, Galaxy Note 1/2, Galaxy Nexus and HTC Rezound owners: The visualizer will sporadically show a flatline with many music players, due to an Android bug related to the built-in DSP in these phones. Several visualizer apps have this warning message: This is caused by an Android code bug in the Digital Signal Processors, which are included in the new Galaxy and some HTC devices. The bytes in the updateVisualizerFFT are not 0 then, so the app has something to use for visualization, even when the visualizer is created with 0 as an argument. This results in no visualization, since there is no signal to use for visualization. The bytes in the updateVisualizerFFT method are always 0 for external players, when a visualizer is created with 0 as an argument. I have played music with external players, while debugging the visualizer apps. Visualization for external players does not work on the new Galaxy devices. It can also use the music from external music players( Winamp for instance). A visualizer can have an internal music player, which means that the app has its own built in player.
0 Comments
Leave a Reply. |