bmi3: fixed the mysterious "mute on first call" bug When UI-enabled fw boots on a previously blank (no /mmi/* files) FFS for the first time, the output_volume member of the persistent UI settings structure was left uninitialized, corresponding to the earpiece volume being set to mute, which is an invalid setting. Because of other quirks in the far-from-finished UI code, this volume setting takes effect only when the first call is answered, producing the odd behaviour seen at the user level. The current fix is to set the blank-FFS default for output_volume to volume level 4, which is the same -6 dB Iota volume as the ACI default.

#!/bin/sh

tmpfile=/tmp/fc_hg_id$$

hg id -in > $tmpfile 2> /dev/null
if [ $? != 0 ]
then
	rm -f $tmpfile
	echo unknown
	exit 0
fi

read global local < $tmpfile
rm -f $tmpfile

global_noplus=`echo $global | tr -d +`
local_noplus=`echo $local | tr -d +`

if [ "$global" = "$global_noplus" -a "$local" = "$local_noplus" ]
then
	dirty=
else
	dirty=-dirty
fi

echo $local_noplus:$global_noplus$dirty