Closed
Bug 757773
Opened 13 years ago
Closed 13 years ago
B2G Telephony: Redial
Categories
(Core :: DOM: Device Interfaces, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: echou, Unassigned)
References
Details
Currently, we cannot do redial because there is no such interface. However, most Bluetooth headsets have this function, like double-click to redial. Furthermore, I can also redial on my HTC Sensation, only need to bring up dialer and click "dial" without entering numbers.
Redial is defined in Bluetooth HSP, clause 4.33.3, AT+BLDN (Bluetooth Last Dialed Number), Android implements this in Phone.apk [1]. So the question here is how should we expose those call log information, right? [1] http://source-android.frandroid.com/packages/apps/Phone/src/com/android/phone/BluetoothAtPhonebook.java
Updated•13 years ago
|
Blocks: b2g-telephony
Comment 2•13 years ago
|
||
(In reply to Eric Chou [:ericchou] [:echou] from comment #0) > Currently, we cannot do redial because there is no such interface. However, > most Bluetooth headsets have this function, like double-click to redial. > Furthermore, I can also redial on my HTC Sensation, only need to bring up > dialer and click "dial" without entering numbers. Sure. That's a dialer feature, though. Redial requires keeping a phone log so you know which number to redial. Gecko does not keep this log and IMHO shouldn't. This is entirely a content feature. Please file a bug against Gaia. (In reply to Yoshi Huang[:yoshi] from comment #1) > Redial is defined in Bluetooth HSP, clause 4.33.3, AT+BLDN (Bluetooth Last > Dialed Number), Android implements this in Phone.apk [1]. > > So the question here is how should we expose those call log information, > right? Exactly like Android: in the app, not in the system.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•