Closed Bug 882069 Opened 12 years ago Closed 12 years ago

Some SMS cannot be sent (with 20130603202903 Geeksphone image)

Categories

(Firefox OS Graveyard :: Gaia::SMS, defect)

All
Gonk (Firefox OS)
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mcepl, Assigned: airpingu)

Details

Attachments

(1 file)

Attached file output of adb logcat
SMS messages are not sent reliably ... for some contacts everything works perfectly, but for some no message go through. I get an exclamation mark next to the message and when I click on it, I get the message "Zprávu se nepodařilo odeslat. Opakovat?" (Message couldn't be sent. Repeat?) and when I press "Repeat" phone tries to send the message again, but with the same results. Using http://downloads.geeksphone.com/peak/images-peak-2013-06-03.Gecko-08a0e76.Gaia-cf65cd8.zip (build ID 20130603202903) on Geeksphone Peak. Attaching output of adb logcat when trying to repeat sending, but I don't think there is anything interesting there (I have console switched on).
(In reply to Matěj Cepl from comment #0) > Attaching output of adb logcat when trying to repeat sending, but I don't > think there is anything interesting there (I have console switched on). This looks SMS related, so possibly the problem: E/GeckoConsole( 117): [JavaScript Error: "lastSegment is undefined" {file: "jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js" line: 2521}]
Hi, gene, Any idea?
Assignee: nobody → gene.lian
(In reply to Chris Double (:doublec) from comment #1) > (In reply to Matěj Cepl from comment #0) > > Attaching output of adb logcat when trying to repeat sending, but I don't > > think there is anything interesting there (I have console switched on). > > This looks SMS related, so possibly the problem: > > E/GeckoConsole( 117): [JavaScript Error: "lastSegment is undefined" {file: > "jar:file:///system/b2g/omni.ja!/components/RadioInterfaceLayer.js" line: > 2521}] Bug 872219 has already fixed exactly the above-mentioned issue and the patch has landed to both mozilla-central and mozilla-b2g18. However, I'm not really sure if this issue is related to that. Hi Matěj, could you please test this issue again with that patch included?
(In reply to Gene Lian [:gene] from comment #3) > Bug 872219 has already fixed exactly the above-mentioned issue and the patch > has landed to both mozilla-central and mozilla-b2g18. However, I'm not > really sure if this issue is related to that. > > Hi Matěj, could you please test this issue again with that patch included? What do I konw ... couldn't you ask somebody from Geeksphone about it?
Keywords: qawanted
Hi Matěj, since you were the reporter of the bug, so I was just asking could you please verify this issue again with the latest build? Anyway, let's ask for QA's support.
Tested on a Leo device with the following build information : Gecko http://hg.mozilla.org/releases/mozilla-b2g18/rev/a199b1109860 Gaia 3e9090894daaa1c7f894a1dcc1026b21f889eadc BuildID 20130618070211 Version 18.0 I was not able to send even a normal text message. I get an exclamation mark next to the message and when I tap on it I see, "Message couldn't be sent. Try Again?". Tapping on try again doesn't work any good(just like Comment 0).
(In reply to Gene Lian [:gene] from comment #5) > Hi Matěj, since you were the reporter of the bug, so I was just asking could > you please verify this issue again with the latest build? Anyway, let's ask > for QA's support. If you mean the latest Geeksphone's stable image, that I have (build ID 20130613185731). If you mean their latest nighly, I am a bit hesitant to switch to it, as this is my main phone, and I have loaded a plenty of data to it already. If you exercise just a little pressure, I may give in and upgrade to their latest nightly.
This issue is not reproducing. If it is, the world should explode but we're not aware of that. Temporally close this one.
Keywords: qawanted
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
(In reply to Gene Lian [:gene] from comment #8) > This issue is not reproducing. If it is, the world should explode but we're > not aware of that. Temporally close this one. Yeah, a good way how to get rid of just user. Who cares, right?
(In reply to Matěj Cepl from comment #9) > (In reply to Gene Lian [:gene] from comment #8) > > This issue is not reproducing. If it is, the world should explode but we're > > not aware of that. Temporally close this one. > > Yeah, a good way how to get rid of just user. Who cares, right? If this issue is still reproducing to you, please feel free to reopen this issue. Closing issues with WORKSFORME doesn't mean we don't want to solve it. It just means we cannot reproduce that.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: