One issue though. Looks like if one audio HAL implements master volume control then audio flinger expects all other HAL's to do the same as there is only one mMasterVolume in audio flinger. Is my understanding correct?
On Tuesday, April 15, 2014 9:54:19 AM UTC-7, Uday Gupta wrote: > > Thanks for the hint. Our primary audio HAL implemented a get_master_volume > function but did not update the volume value and thus the uninitialized > value. We don't do volume control in the HAL so removed it now and > everything is working now. > > On Tuesday, April 15, 2014 7:39:35 AM UTC-7, Glenn Kasten wrote: >> >> This seems like an uninitialized value, not a valid value. >> >> I suggest that you find a known working reference device >> (e.g. Nexus family) running the same OS version, and then >> start comparing logs, volumes at various places etc., to >> see where the difference first appears in the pipeline. >> >> On Monday, April 14, 2014 4:10:24 PM UTC-7, Uday Gupta wrote: >>> >>> Hi, >>> >>> On our development platform on KK, A2DP playback has no sound. Data dump >>> in the A2DP HAL shows all zeros. >>> >>> Enabling and adding some logs in AudioFlinger.cpp and threads.cpp shows >>> the master volume as -0.000002. >>> >>> Has sometime changed in KK compared to JB and some configuration >>> parameters need to be set to set the master volume to 1.0f. >>> >>> Thanks >>> >> -- -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-porting+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
