Closed Bug 836383 Opened 11 years ago Closed 11 years ago

SMSs received from non-numeric origins (e.g. Google) are not shown in SMS application and prevent further SMSs to be shown until device is rebooted

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(blocking-b2g:tef+)

Status:
RESOLVED DUPLICATE of bug 788441
Project Flags:
blocking-b2g tef+

People

(Reporter: giorgos, Assigned: vicamo)

References

Details

I've a German SIM and a unagi running the latest beta build (*) and I occasionally don't receive calls and SMSes.

Missed call/sms log:
- I missed a call originating from a O2 network and I'm on 'tchibo' which is using the O2 network. Usually I get to talk with this number just fine.

- I never received any SMSes from the number above. I can send normally to it.

- I didn't receive SMS from another network (VodafoneGR)  which I usually receive

- I didn't receive call from VodafoneGR which I usually receive.


If there are any logs I can provide please let me know where I can find them.

Thanks!




Details:
Build ID: 20130123070202
Update Channel: beta
Network: Tschibo (O2) Berlin / Germany
blocking-b2g: --- → shira?
:vicamo, any idea on this? any logs need to be provided? thanks
Giorgos and myself played with that yesterday and he didn't receive any of the SMS I sent. But a phone call at the same time came through. Given that we haven't seen anything via adb logcat, how can we further investigate this problem? Are there other logs we should check?
Flags: needinfo?(vyang)
Giorgos can you use adb shell cat /proc/version and output that information here ? 

Can you also try plugging the sim into another phone, sending an sms and seeing what happens ? 

Then repeat with unagi phone. 

What happens if you reboot the phone ?
(In reply to Henrik Skupin (:whimboo) from comment #2)
> Giorgos and myself played with that yesterday and he didn't receive any of
> the SMS I sent. But a phone call at the same time came through. Given that
> we haven't seen anything via adb logcat, how can we further investigate this
> problem? Are there other logs we should check?

Hi, you may turn on RIL debug messages by:
1) adb pull /system/b2g/defaults/pref/user.js .
2) < edit user.js and set "ril.debugging.enabled" to true >
3) adb push user.js /system/b2g/defaults/pref
4) adb shell sync && adb reboot
Flags: needinfo?(vyang)
I also don't get any SMS sent to me while my SIM card is in Unagi. Polish number in Orange network.

SMSes report at sender as not received after their expiration time.

Working great on Android phone with the same SIM card. It doesn't change after reboot or factory reset.
I'm waiting for Giorgos now. He wanted to get back to me once he has credits again on his SIM card. So we can try the other way around.
bpiec@ubunt:~$ adb shell cat /proc/version
Linux version 3.0.8-perf (songsy@ubuntu-cdr) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Wed Dec 5 04:47:49 PST 2012
Want to make sure everyone knows that Shira is targeting 2/15 code freeze. 
Shira+ bugs needs more attention for unassigned, needinfo?,  review?
Full regression test is planned on 2/6. Need to have shira+ bugs landed by the end of 2/5 to be covered in full regression testing. Thanks
:whimboo, :giorgos, can you also verify that you have the correct date/time/timezone on the device?

Vingtetun has found that SMS depends highly on the time on the device; I verified.

https://bugzilla.mozilla.org/show_bug.cgi?id=827725#c5
I can't seem to replicate with the US carriers... I think it might be more carrier specific if it's not something like comment 9....
Flags: needinfo?(hskupin)
Flags: needinfo?(giorgos)
Keywords: qawanted
I can't do anything without Giorgos. So next steps depend on him.
Flags: needinfo?(hskupin)
shira- for now. if this is reproducible, please renom. Thanks
blocking-b2g: shira? → ---
Sorry for being quiet the last days. I unfortunately had to give away my unagi as a demo device for AppDays so currently I don't have a device :/

On comment #9, yes the timezone, time was correct, I believe it was just on the automatically set from network.
Flags: needinfo?(giorgos)
I believe the timezone is set when you setup your device, is it also set automatically ?
Still doesn't work for me and this prevents me from using that phone as a primary phone :(

I get some messages but the SMS from my bank doesn't appear. It is sent from special number with custom sender name, maybe that is the issue?

Can I help with debugging anyhow?
Nominating to shira+, I can reproduce it every time I log in to my bank.
blocking-b2g: --- → shira?
I can reproduce it similarly to Bartosz - text messages from my bank don't work.
Stas also can reproduce it with the same bank - BZWBK. It's critical for Poland, as it seems like it affect systems with automated text messages (which is a common scenario in Poland for e-tickets, parking tickets, payments, bank codes etc.)
logcat does not record any activity when it receives text messages, and no JS error is thrown for when the bank message is received.
I can't reproduce this.  I tried both a v1.0.1 build and a v1-train one.

Bartosz, you may be using an old Gonk/Gecko build, even if your Gaia is up-to-date.

Can you paste your phone's /system/b2g/application.ini?
bpiec@ubuntu:~$ adb shell cat /system/b2g/application.ini
[App]
Vendor=Mozilla
Name=B2G
Version=18.0
BuildID=20130224230200
SourceRepository=http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1
SourceStamp=3a5a27992a75
ID={3c2e2abc-06d4-11e1-ac3b-374f68613e61}

[Gecko]
MinVersion=18.0
MaxVersion=18.0

[XRE]
EnableExtensionManager=1

[Crash Reporter]
Enabled=1
ServerURL=https://crash-reports.mozilla.com/submit?id={3c2e2abc-06d4-11e1-ac3b-374f68613e61}&version=18.0&buildid=20130224230200
I flashed the 20130224230200 build, but I still can't reproduce.
I just reproduced it with:

zbraniecki@host-2-163:~/projects/l20n/js (simpleres %=)$ adb shell  cat /system/b2g/application.ini
[App]
Vendor=Mozilla
Name=B2G
Version=18.0
BuildID=20130319163114
ID={3c2e2abc-06d4-11e1-ac3b-374f68613e61}

[Gecko]
MinVersion=18.0
MaxVersion=18.0

[XRE]
EnableExtensionManager=1

[Crash Reporter]
ServerURL=https://crash-reports.mozilla.com/submit?id={3c2e2abc-06d4-11e1-ac3b-374f68613e61}&version=18.0&buildid=20130319163114
we did a bit more testing with stas.

I was able to call stas's polish number from my polish number, I was able to text him and he was able to text me.

But the BZWBK text message didn't go through and there was no error in logcat.

zbraniecki@Zbigniews-MacBook-Pro:~/Downloads/b2g/b2g-distro$ adb shell  cat /system/b2g/application.ini
[App]
Vendor=Mozilla
Name=B2G
Version=18.0
BuildID=20130301070202
SourceRepository=http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1
SourceStamp=69e249bf251c
ID={3c2e2abc-06d4-11e1-ac3b-374f68613e61}

[Gecko]
MinVersion=18.0
MaxVersion=18.0

[XRE]
EnableExtensionManager=1

[Crash Reporter]
Enabled=1
ServerURL=https://crash-reports.mozilla.com/submit?id={3c2e2abc-06d4-11e1-ac3b-374f68613e61}&version=18.0&buildid=20130301070202

One idea that Piecu has is that those text messages are coming from numbers displayed on android phones as names (like: "BZWBK24" or "AliorBank") instead of a number. Maybe that's broken?
(In reply to Zbigniew Braniecki [:gandalf] from comment #24)

> One idea that Piecu has is that those text messages are coming from numbers
> displayed on android phones as names (like: "BZWBK24" or "AliorBank")
> instead of a number. Maybe that's broken?

This might be an interesting lead.

Gandalf's carrier is Play, Bartosz's is Orange.  Both get texts from their banks from a name ("BZWBK24").  My carrier is T-Mobile and I get the same texts from a number (2424).  I'm the only one who actually gets these texts on Firefox OS.  I'll need to check if this is the same when I'm back in Poland.
we also tried switching phones and sim cards and builds. I'm also receiving text messages from my operator itself from number "123".
FYI I was not receiving SMS from regular phone numbers, so maybe sender name is not related to this bug.
Giorgos -- is there any chance you were supposed to receive a text from a named number before your other expected texts went missing?

I can reproduce this bug with the following steps:

0. Restart the device and send a text from a regular number to it.
1. Make Google Calendar send me a verification code for SMS notifications.  The text is from "Google".  It is never received.
2. No other text messages can be received from this point until I restart the device.
3. When I restart the device, I get all the text messages sent before as if they got stuck in a queue.

Bartosz, can you repro the bug when you follow the steps above?
Flags: needinfo?(bpiec)
shira? -> tef?
blocking-b2g: shira? → tef?
(In reply to Staś Małolepszy :stas from comment #28)
> Bartosz, can you repro the bug when you follow the steps above?

Yes, I can reproduce the same behavior. However, after the phone restart I got a message sent from my regular phone but I didn't get a message from Google.
Flags: needinfo?(bpiec)
(In reply to Bartosz Piec from comment #30)
> (In reply to Staś Małolepszy :stas from comment #28)
> > Bartosz, can you repro the bug when you follow the steps above?
> 
> Yes, I can reproduce the same behavior. However, after the phone restart I
> got a message sent from my regular phone but I didn't get a message from
> Google.

Yep, I can see the same behavior.

Drivers: when triaging, please considering the fact that almost all banks in Poland use text messages to send security tokens for transfers and most of them come from named numbers.  This is potentially a stop-ship bug.
Agree this is a blocker, but I believe this should be morphed into something more accurate with the problem we are facing. Please feel free to update again title if you don't agree.
blocking-b2g: tef? → tef+
Summary: Phone calls and SMSes go missing. → SMSs received from non-numeric origins (e.g. Google) are not shown in SMS application and prevent further SMSs to be shown until device is rebooted
The new summary makes much more sense, thanks Daniel!

To whomever is going to take this bug:  please let me know what kind of debug information you need to start.
Borja, is there any quick way to check if those SMSs get eventually to Gaia? Happy to help with the test if that is required.
Flags: needinfo?(fbsc)
I can reproduce the same behavior as Stas described in comment 28.

On top of that, if I wait Long Enough (tm) without restarting phone the text message from a number will get delivered.

It feels as if the carrier tried to deliver the named message and because FxOS did not confirm receiving it, it didn't go with the next one. When the named message expires, the next in the line gets delivered properly.

If we want, I have friends at polish carriers, we can get help in emulating environment in order to reliably reproduce the behavior.
I'm also going to be in SF office from Thursday and will have my play mobile sim card so I can assist in reproducing the behavior if any dev is willing to play with it.
(In reply to Zbigniew Braniecki [:gandalf] from comment #35)

> It feels as if the carrier tried to deliver the named message and because
> FxOS did not confirm receiving it, it didn't go with the next one. When the
> named message expires, the next in the line gets delivered properly.

For further information. I have a dual subscription (two physical SIMs with exactly the same number) and have one of the SIM Cards on FirefoxOS and another one in other device. The "Google" SMS is delivered only to the other device, subsequent SMSs are delivered to the other device without any issue.
I can also reproduce this behavior with non-numeric sms blocking sms receiving.

Restarting doesn't always solve the problem, maybe the non-numeric sms has to timeout first.

The original bug is also about Calls gone missing. Any progress on that? Should we open another bug?
(In reply to Giorgos Logiotatidis [:giorgos] from comment #37)
> The original bug is also about Calls gone missing. Any progress on that?
> Should we open another bug?

I tried to reproduce calls going missing, but I couldn't.  Can you open a new bug for this?  It might be related, but might require a different set of steps to repro.
Who can take this?  Borja?  Vicamo?  Joe, is there someone I'm not thinking of?
Flags: needinfo?(jcheng)
not sure if this can be reproduced in Taipei. 
Vicamo can you try to reproduce and see if this can be reproduced in Taipei? thanks
Flags: needinfo?(jcheng) → needinfo?(vyang)
Keywords: qawanted
With comment 28, this duplicates bug 788441. Will try locally to make sure it fixes the problem here.
Assignee: nobody → vyang
Flags: needinfo?(vyang)
Flags: needinfo?(fbsc)
QA Contact: atsai
Confirmed. No such bug in m-c and b2g18 gets fixed with that patch cherry-picked. I'm going to mark this issue as duplicated and nominate bug 788441 for tef+.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Keywords: qawanted
I filed bug 855481 about a similar issue, before finding this one. I'm actually certain that I am facing both issues Giorgos has been facing (missing messages and calls) in addition to recent regressions in the communications app (call log and message lists appearing empty). I'm also on Vodafone Greece FWIW.
verified that fix from bug 788441 fixed this bug for me.
I'm also now getting SMS from Google.
You need to log in before you can comment on or make changes to this bug.