05-15-2023, 08:50 AM
Quote:1) I originally noticed the # sign doesn't work for the phone, but actually the issue appears to be it doesn't register text input commands. An example is checking voicemail which requires typing in the phone number and hitting a button below the touch pad to initiate the call. It then asks for your PIN and to press #. Normally when you start typing, the audio message to type in your PIN number stops. However, it keeps going implying it's not registering the typing. Curious if this also occurs for the browser if anyone can think of a site that triggers something when text is typed into an input, but no button is hit afterward.
Thank you for providing this background. The dial tones during a call are actually handled by modem commands that are unrelated to dialing. The current Sculpt image does not issue these commands. So the dial pad has currently no effect during a call. We should definitely implement the in-call dial tones until the August release.
Regarding the # button, it is missing only because I had no good place to put it, since one button position is taken by the delete button (currently labeled "C"). Down the road, I think we could place the clear button below the dial pad (where the current-call info is displayed during a call) and put the # button where it belongs.
