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.

#ifndef __L1SW_CFG__
#define __L1SW_CFG__
#define AMR 1
#define CUST 0
#define DCO_ALGO 0
#define IDS 1
#define L1_12NEIGH 1
#define L1_EOTD 0
#define L1_EOTD_QBIT_ACC 0
#define L1_GPRS 0
#define L1_GTT 0
#define L1_MIDI 0
#define L1_VOICE_MEMO_AMR 1
#define MELODY_E2 1
#define OP_L1_STANDALONE 0
#define OP_RIV_AUDIO 1
#define ORDER2_TX_TEMP_CAL 1
#define RAZ_VULSWITCH_REGAUDIO 0
#define SECURITY 0
#define SPEECH_RECO 1
#define TESTMODE 1
#define TRACE_TYPE 4
#define VCXO_ALGO 1
#endif /* __L1SW_CFG__ */