Hi, Anatel requires to implement Cell Broadcast in 2G for displaying the area code for each of the states of Brazil. For instance, in Sao Paulo and Rio de Janeiro, the device should display: "VIVO SP 11" / "VIVO RJ 21" However this message is not being displayed. Ikura 1.0.1 is showing this message fine, however. Nominating for leo? Thanks! David
Anshul, can you check this as it has a commercial ril?
I suggest you raise this with Leo.
Dear leo colleagues, this is a legal requirement, could you check it before we cannot test in the real environment? Sorry to say this is urgent.
The newer version (FW ver.: V08a) was released. This issue was fixed in V08a. Please, check it and make a feedback. If it is not reproduced, I will change the status.
This issue is also present with v08a: Gecko revision : 08e8a7bbebec924c24a5187a3c0b2ef1ef6d08da Gaia revision : e2346ca0297f40547e64a7eebc4bd2e4a4cdaf86 Commercial RIL : AU_LINUX_GECKO_ICS_STRAWBERRY.01.01.00.019.115 We're testing this yesterday with your colleague José de María here in SP.
Blocking on this as written, please resolve/invalid if this isn't an issue.
This is a big issue for regulatory and certification reasons. Thanks for setting it to Leo+. However, I do not understand why this is marked as POVB. Could you please clarify it? Thanks in advance.
Are you checking the lockscreen or are you looking for a dialog? That version of Gaia still only shows content on the second line of the lockscreen. From your logs, I see the message successfully coming up from RIL and the MCC is BRAZIL as needed. I can test this on a network box and it works.
David, please check this issue and provide more info. I will add an attachment about how it looked like the last time we tested in BR. David, please test also by setting the device under only 2G mode and only 3G mode.
We marked as POVB since we thought it was specific to Ikura, not 1.1. Sounds like this is a regression in that case? Where do we think the fix needs to be made here? We don't have good access to a repro case to figure out who to assign this bug to.
Partner has a patch for this bug. ni? leo
Yes, I'm sorry I didn't catch this earlier - not sure how that happened; a fix is incoming https://bugzilla.mozilla.org/show_bug.cgi?id=884486
Shall we mark this issue as dup of bug 884486?
It's most likely this issue is due to the fix in bug 884486. Please reopen if that is not the case.