diff options
| author | 2023-02-06 16:34:54 +0000 | |
|---|---|---|
| committer | 2023-02-06 18:13:03 +0000 | |
| commit | 2517d03c19ce5f9792eccca4018a64de131108ba (patch) | |
| tree | 94a568c93cc5992c2a71b5404d829331e56e42bb /libs/input/PointerController.cpp | |
| parent | 30a3877337a12520020fc1cfa079cdaa8c33abce (diff) | |
Clarify start/stop DTMF tone API documentation.
The API docs are not clear; they insinuate that a caller can issue any
number of "play" DTMF requests followed by a single "stop" request and
that the framework will interpret this as two digits in succession.
In reality, the documentation is referring to the fact that the local tone
will correctly stop if another tone is already playing. The API
requests are sent directly to the modem as the InCallService sends them,
and it is possible that some ConnectionService implementations (more
specifically some vendor IMS implementations) will get confused if
they receiver multiple starts and then a single stop.
Test: Docs only change
Bug: 262699364
Change-Id: I770008cc3b000f739d930ea899df5e98d1b17129
Diffstat (limited to 'libs/input/PointerController.cpp')
0 files changed, 0 insertions, 0 deletions