Closed Bug 719950 Opened 13 years ago Closed 13 years ago

B2G SMS: SMS Received but not appearing in Gaia SMS GUI

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jhammink, Unassigned)

References

Details

Attachments

(1 file)

commit dd4ecd1ebd2ccbfb90cfdcc654addccfce695c7e Merge: d107247 dfb0d51 from https://github.com/jonallengriffin/B2G pulled approx 7 p.m. p.s.t 1/18/2012 Samsung Galaxy S2 with working SIM card installed. To repro: 1. Send an SMS to your b2g phone 2. run adb logcat to verify that message is received 3. Watch SMS app to verify that received message is presented According to logcat, the message is received: I/Gecko ( 2587): -*- TelephonyWorker component: Received message: {"SMSC":"+12085978928","reference":null,"sender":"+12163393297","body":"Ggcffcc","validity":null,"timestamp":1326940036000,"type":"sms-received"} I/Gecko ( 2587): RIL Worker: Outgoing parcel: 0,0,0,20,37,0,0,0,76,0,0,0,2,0,0,0,1,0,0,0,0,0,0,0 But the incoming message never appears in SMS application. **Actual behavior:** Call forever goes into "calling" mode forever, but the call never actually connects. Hitting big red "hangup" button doesn't stop the call attempt; you must actually $adb reboot the phone to get out of this state. Desired behavior: Call connects; or indicates reasonable failure if cannot connect. Hitting big red "hangup" terminates the operation.
~Sorry *cloned bug* pls omit the last two paragraphs of description.~
The SMS received event fires in the DOM, so this is a Gaia bug. Please file this here: https://github.com/andreasgal/gaia/issues
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INVALID
(Also, please don't clone a bug unless you're actually splitting a bug into two.)
No longer depends on: 719331
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: