view cdg211/prim/mmsms.pdf @ 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 56abf6cf8a0b
children
line wrap: on
line source

;********************************************************************************
;*** File           : mmsms.pdf
;*** Creation       : Fri Jun 08 13:57:55 CST 2007
;*** XSLT Processor : Apache Software Foundation / http://xml.apache.org/xalan-j / supports XSLT-Ver: 1
;*** Copyright      : (c) Texas Instruments AG, Berlin Germany 2002
;********************************************************************************
;*** Document Type  : Service Access Point Specification
;*** Document Name  : mmsms
;*** Document No.   : 6147.106.97.102
;*** Document Date  : 2002-07-19
;*** Document Status: BEING_PROCESSED
;*** Document Author: HM
;********************************************************************************



PRAGMA 	SRC_FILE_TIME 	"Mon Nov 24 15:51:10 2003"
PRAGMA 	LAST_MODIFIED 	"2002-07-19"
PRAGMA 	ID_AND_VERSION 	"6147.106.97.102"



CONST 	MAX_SDU_LEN 	1 	; maximum service data unit length



VALTAB 	VAL_ti
VAL 	0 - 6 	"ms originated transaction"
VAL 	8 - 14 	"ms originated transaction"
VAL 	7 	TI_RES_MO 	"reserved"
VAL 	15 	TI_RES_MT 	"reserved"




VAR 	cause 	"MM cause" 	S


VAR 	l_buf 	"length in bits" 	S


VAR 	o_buf 	"offset in bits" 	S


VAR 	buf 	"bit buffer" 	B


VAR 	ti 	"transaction identifier" 	B

VAL 	@p_mmsms - VAL_ti@ 	

VAR 	d1 	"dummy, not used" 	B


VAR 	d2 	"dummy, not used" 	B





COMP 	sdu 	 "Service Data Unit"
{
 	l_buf 	 ; length in bits
 	o_buf 	 ; offset in bits
 	buf 	[MAX_SDU_LEN] 	 ; bit buffer
}






; MMSMS_ESTABLISH_REQ 	0x80000009
; MMSMS_RELEASE_REQ 	0x80010009
; MMSMS_DATA_REQ 	0x80020009
; MMSMS_DATA_IND 	0x80004009
; MMSMS_ERROR_IND 	0x80014009
; MMSMS_ESTABLISH_CNF 	0x80024009
; MMSMS_ESTABLISH_IND 	0x80034009
; MMSMS_RELEASE_IND 	0x80044009
; MMSMS_UNITDATA_IND 	0x80054009



PRIM 	MMSMS_ESTABLISH_REQ 	0x80000009
{
 	ti 	 ; transaction identifier
}






PRIM 	MMSMS_RELEASE_REQ 	0x80010009
{
 	ti 	 ; transaction identifier
}






PRIM 	MMSMS_DATA_REQ 	0x80020009
{
 	d1 	 ; dummy
 	d2 	 ; dummy
 	sdu 	 ; service data unit
}






PRIM 	MMSMS_DATA_IND 	0x80004009
{
 	d1 	 ; dummy
 	d2 	 ; dummy
 	sdu 	 ; service data unit
}






PRIM 	MMSMS_ERROR_IND 	0x80014009
{
 	ti 	 ; transaction identifier
 	cause 	 ; error cause
}






PRIM 	MMSMS_ESTABLISH_CNF 	0x80024009
{
 	ti 	 ; transaction identifier
}






PRIM 	MMSMS_ESTABLISH_IND 	0x80034009
{
 	d1 	 ; dummy
 	d2 	 ; dummy
 	sdu 	 ; service data unit
}






PRIM 	MMSMS_RELEASE_IND 	0x80044009
{
 	ti 	 ; transaction identifier
 	cause 	 ; release cause
}






PRIM 	MMSMS_UNITDATA_IND 	0x80054009
{
 	d1 	 ; dummy
 	d2 	 ; dummy
 	sdu 	 ; service data unit
}