comparison doc/Current_Status @ 35:23dbd942aa56

doc/Current_Status: update for the latest fixes
author Mychaela Falconia <falcon@freecalypso.org>
date Sat, 15 Oct 2016 05:15:23 +0000
parents cb00b90edaff
children
comparison
equal deleted inserted replaced
34:2fc925048350 35:23dbd942aa56
56 make and receive voice calls, and send and receive SMS. 56 make and receive voice calls, and send and receive SMS.
57 57
58 * In the case of voice calls, the call downlink audio is routed to the phone's 58 * In the case of voice calls, the call downlink audio is routed to the phone's
59 earpiece speaker and the phone's microphone serves as the source for the 59 earpiece speaker and the phone's microphone serves as the source for the
60 uplink audio, i.e., even though the LCD and keypad are dead with our fw, the 60 uplink audio, i.e., even though the LCD and keypad are dead with our fw, the
61 earpiece and mic continue to function as in a conventional phone. FR and EFR 61 earpiece and mic continue to function as in a conventional phone. FR, EFR
62 codecs work correctly (EFR was broken until recently), but AMR does not work 62 and AMR codecs all work correctly (EFR and AMR were broken until recently),
63 with this fw for some not-yet-understood reason, hence by default our fw 63 but our default build configuration has AMR disabled (the fw advertises to
64 currently advertises to the GSM network that the MS only supports FR, HR and 64 the GSM network that the MS only supports FR, HR and EFR codecs) to err on
65 EFR codecs. 65 the side of safety: we are having some reliability issues with the
66 L1_DYN_DSP_DWNLD feature (which is also disabled by default), and AMR is
67 believed to depend on one of these dynamically downloaded DSP patches.
66 68
67 There is also a highly experimental and minimally tested alternative mode 69 There is also a highly experimental and minimally tested alternative mode
68 of operation in which the traffic channel carrying FR codec bits (260 bits 70 of operation in which the traffic channel carrying FR or EFR codec bits
69 every 20 ms; it is not known whether or not this feature will also work with 71 (260 bits every 20 ms) is rerouted away from the internal vocoder to the
70 EFR) is rerouted away from the internal vocoder to the external host, 72 external host, such that you can receive the downlink voice bits digitally
71 such that you can receive the downlink voice bits digitally instead of 73 instead of listening to them in the earpiece speaker, and you can substitute
72 listening to them in the earpiece speaker, and you can substitute your own 74 your own uplink bits instead of the microphone-fed internal vocoder output.
73 uplink bits instead of the microphone-fed internal vocoder output. See the 75 See the TCH-special-feature write-up for more information.
74 TCH-special-feature write-up for more information.
75
76 There are also two known bugs which manifest only intermittently, but the
77 misbehaviour does occur often enough that you will likely encounter it:
78
79 * Sometimes something gets messed up in the voice uplink path such that the
80 downlink audio sounds just fine in the earpiece speaker of the phone running
81 FC Citrine, but the far end of the call hears only silence. Other times the
82 voice audio passes just fine in both directions. It is not currently
83 understood what factors determine whether it will work or not.
84
85 * Sometimes the L1A task in the firmware (see the Firmware_Architecture
86 write-up) appears to stop running; the externally visible behaviour is that
87 the debug trace output from L1 suddenly stops while the rest of the firmware
88 keeps running. GSM firmware without working L1 is unusable, hence when the
89 fw gets into this state, the only remedy is a power cycle reboot. It is not
90 currently understood exactly what happens and under what conditions.
91
92 Going forward, the current plan is to wait until our FCDEV3B hardware gets built
93 before any attempts will be made to go after the above-listed bugs. I, the
94 principal developer, am sick and tired of limping along with Compal, Pirelli
95 and Openmoko hardware when we have a design for our own FreeCalypso development
96 board which, when built, will be a much more convenient platform for firmware
97 development.
98 76
99 Target-specific usage instructions 77 Target-specific usage instructions
100 ================================== 78 ==================================
101 79
102 If you would like to play with our work-in-progress firmware and check it out 80 If you would like to play with our work-in-progress firmware and check it out