FreeCalypso > hg > fc-magnetite
view src/g23m-aci/aci/dcm_state.h @ 660:293c7db5f10f
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.
author | Mychaela Falconia <falcon@freecalypso.org> |
---|---|
date | Thu, 14 May 2020 02:50:41 +0000 |
parents | 53929b40109c |
children |
line wrap: on
line source
/* +----------------------------------------------------------------------------- | Project : GSM-F&D (8411) | Modul : ACI +----------------------------------------------------------------------------- | Copyright 2002 Texas Instruments Berlin, AG | All rights reserved. | | This file is confidential and a trade secret of Texas | Instruments Berlin, AG | The receipt of or possession of this file does not convey | any rights to reproduce or disclose its contents or to | manufacture, use, or sell anything it may describe, in | whole, or in part, without the specific written consent of | Texas Instruments Berlin, AG. +----------------------------------------------------------------------------- | Description : DCM instance is a state machine with several possible states. | Based on the current state, DCM handle different kind of messages/events. | States are listed in the order they should normally be sequenced. +----------------------------------------------------------------------------- */ #ifndef __DCMSTATE_H__ #define __DCMSTATE_H__ /** * DCM states. * * DCM instance is a state machine with several possible states. * Based on the current state, DCM handle different kind of messages/events. * States are listed in the order they should normally be sequenced. * * See the Readme file for a description of the state machine. */ typedef enum { DCM_OFF, DCM_IDLE, DCM_ACTIVATING_CONN, DCM_CONN_ACTIVATED, DCM_CLOSING_CONN } T_DCM_INTERNAL_STATE; /** * DCM substates. * * DCM instance is a state machine with several possible states. * Substates are included in some states. */ typedef enum { DCM_SUB_NO_ACTION = 0, /* ALL */ DCM_SUB_WAIT_CGATT_CNF, /* DCM_ACTIVATING_CONN */ DCM_SUB_WAIT_CGACT_CNF, /* DCM_ACTIVATING_CONN */ DCM_SUB_WAIT_SATDN_CNF, /* DCM_ACTIVATING_CONN */ DCM_SUB_WAIT_SATH_CNF, /* DCM_CLOSING_CONN */ DCM_SUB_WAIT_CGDEATT_CNF, /* DCM_CLOSING_CONN */ DCM_SUB_WAIT_CGDEACT_CNF /* DCM_CLOSING_CONN */ } T_DCM_INTERNAL_SUBSTATE; T_DCM_RET dcm_idle (T_DCM_HDR * msg_p); T_DCM_RET dcm_activating_conn(T_DCM_HDR * msg_p); T_DCM_RET dcm_conn_activated(T_DCM_HDR * msg_p); T_DCM_RET dcm_closing_conn(T_DCM_HDR * msg_p ); T_DCM_RET dcm_new_state(U8 state, U8 substate); T_DCM_RET dcm_save_state(void); T_DCM_RET dcm_restore_state(void); void dcm_dispay_state(U8 state, U8 substate); void dcm_dispay_sub_state(U8 substate_1, U8 substate_2); #endif