DTMF code wait and pause

Feature Requests
#1

REPRODUCIBILITY: 100%
OS VERSION: 4.4.0.72
HARDWARE: Xperia 10
UI LANGUAGE:PL
REGRESSION: Nope

DESCRIPTION:

Unable to type DTMF wait code from the dialpad

PRECONDITIONS:

nothing

STEPS TO REPRODUCE:

Open the dialpad
try to type wait

EXPECTED RESULT:

nothing happens when holding # for longer time or tripple pressing it

ACTUAL RESULT:

there must be a way to enter DTMF wait code.

MODIFICATIONS:

Patchmanager: VolumeKeys

ADDITIONAL INFORMATION:

Actually, this is something old I asked in 2018
and itā€™s a basic phone functionality. Tbh itā€™s even more basic than SMS support.
Pause is there, a little bit cumbersome to type especially on 10 because of itā€™s touch nuances but itā€™s there. Wait is still missing.

#2

I think you confused actual with expected result.
Googling for DTMF wait comes up surprisingly short, and several hits mentions just doing a longer pauseā€¦ It also does not really seem these are codes/tones in DTMF you enter, but features in the respective implementations. I.e. it is not really default functionality left on the table as you seem to imply. (Making this even more clearly a feature-request)

#3

I never read that a ā€˜pauseā€™ DTMF tone exists in all my life. There is 0-9, *, # and, on some DTMF tone transmitters, A-D. Pause is a feature of the DTMF transmitter, e.g. the telephone, dialing automat or analog modem. There was a ā€˜pauseā€™ command in the AT codes of ancient analog telephone modems.

Itā€™s a good idea to implement a ā€˜pauseā€™ command into the addressbook phone number entry. Iā€™m testing just now and find here: Numbers 0-9, a + where the * should be, #, and *p that generates a simple * in the number field, further on, backspace and enter. Thats all. Long pressing any button does nothing.

Is the +/* mess worth a bug report or does this have a higher sense?

#4

Iā€™m using pause commands for a while now.
ā†’ long press ā€œ*ā€ on your dialpad
I suggest doing it twice in a row (single pause is ~3sek. and often to short).
In the dialpad itā€™s displayed as ā€œ,ā€.
In your dialhistory then itā€™s ā€œpā€.

1 Like
#5

Got it, thank you @tobset !

Longpress * - edit: in the phonebook app - does nothing, but doubletap * really generates p when entering a number into phonebook. On tapping *p , the appearing * is underlined for 2 seconds. On tapping *p again while it is underlined, it changes to p.

On dialling in the phone app, itā€™s exactly as you wrote. Long pressing * generates a , (comma) and this will surely be a pause but I didnā€™t check nowā€¦

2 Likes
#6

@Seven.of.nine @tobset @attah no no no, there are two types of this and I know cause I was using it and sometimes still does.
One is just pause which is waiting 3 seconds. Second is wait for user interaction. So example:
222222w32p2p2131p23123
this means that: call 222222 wait for user action (some auto dial systems wonā€™t allow you to instantly enter internal number so you need to wait till the hello ends), confirm the invitation is done, then call 32, wait 3 seconds, enter 2131 wait 3 seconds, enter 23123.
This is how it should work.

So please donā€™t tell me such thing doesnā€™t exists, here on other phones:
iOS Android

1 Like
#7

That does not make it part of any standard, nor a bug report.

#8

what? Then why iOS and Android, BlackBerry, WindowsPhone, and older phones does support it? Please explain this.

#9

Because it is a feature they have?

#10

and suddenly all companies, that compete with each other, made this decision?

#11

Please can some Admin change this thread from bug report to feature request? Imho the feature request is very appropriate.