OTA4 SMS function now fails

[LionelB]

Since downloading r23 this morning, my SMS no longer works. It shows a red message with fail. [n.b. there is credit!] Calls work as normal. SMS has worked fine up until now. I am using Phonecoop Mobile in the UK.
Oddly, the new auto-reply feature [an SMS saying "I will call you back later etc."] DOES send! Or at least it shows green in the messages list. Could be that the re-configure to auto-reply is the source of the problem ?
Incidentally, not sure how I configure auto-reply ...

[LionelB (retweet)]

An update. SMS is now working. This morning, the fails happened when I was not connected to wifi. SMS worked this evening, while connected to wifi. Whether that is relevant [it corrected ? / there was a network fault this morning ? / it fails only when not on wifi ?] I do not know.

[LionelB (retweet)]

SMS now seems to be working normally, whether the phone is in wifi range or not. The failure may have been a coincidental fault on the network or may have resulted from a delay while settings were reset following the software update.

[LionelB (retweet)]

Successfully sent an SMS this morning but the recipient got a fail when they tried to respond. So there is still an error.

[LionelB (retweet)]

Under 'Carrier' in Settings I have an option for 'Automatically' - which was ticked and defaulted to Phone Co-op.

I also have two manual settings available, both of them named Phone Co-op.

I am guessing one is the default picked up from the SIM card and the other is from the [recently updated] provider database.

A conflict between the two entries could cause an intermittent fault ? Automatic allocation could result in a 50% failure rate, logically. Though presumably only if one set of parameters is incorrect in some particular ?

I have chosen one of the manual sets available. Hope I chose the right one :-)

[LionelB (retweet)]

Since choosing one of the duplicate carrier entries manually, I have had no further problems with SMS.

So, assigning settings automatically when there is a duplicate carrier entry causes random failure. Solution - assign the settings manually by selecting the carrier from the list in Settings.

[LionelB (retweet)]

An update. Sadly most incoming and outgoing SMS fail. There are exceptions. Notably when using the provider service on 1250.

[Tony Espy (awe)]

@LionelB

Could you add some information to your bug report that'll help us determine what's happening?

From the fact you mentioned downloading r23, I'm assuming your have a BQ phone, is that correct? Can you provide us the system details for your phone via 'system-image-cli -i'?

Have you made your phone writable? Installed any additional software using apt?

Could you please attach the file /var/log/syslog from your phone, and the output of:

# /usr/share/ofono/scripts/list-modems

Also, so we can rule out the upper layers, can you try to send a SMS via a command-line script:

# /usr/share/ofono/scripts/send-sms <modem> <to> <message> 0

...where <modem> is '/ril_0' or '/ril_1' ( drop the quotes; /ril_0 == 1st SIM slot, /ril_1 = 2nd SIM slot ).

[LionelB (retweet)]

Writable, no. No software via terminal either.

Yes it is a BQ 4.5.

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
> Have you made your phone writable? Installed any additional software
> using apt?

[LionelB (retweet)]

SMS texts send and receive without any problems on the ‘3’ network. The problem is particular to the Phone Coop network.

That should rule out most possibilities to do with the phone’s architecture.

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
> Could you add some information to your bug report that'll help us
> determine what's happening?

[LionelB (retweet)]

Tried that as a terminal command. It says not recognised.

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
> Can you provide us the system details for your
> phone via 'system-image-cli -i'?

[LionelB (retweet)]

Limit is 10 Mb. Syslog is 19 Mb.

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
> Could you please attach the file /var/log/syslog from your phone

[LionelB (retweet)]

Attached:

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
> and
> the output of:
>
> # /usr/share/ofono/scripts/list-modems

[LionelB (retweet)]

Not clear from this what goes in <to> and what the ‘o’ on the end is.

An example written out as it would appear would help.

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
> # /usr/share/ofono/scripts/send-sms <modem> <to> <message> 0

[LionelB (retweet)]

Ah. Syntax ! Missed a space.

current build number: 23
device name: krillin
channel: ubuntu-touch/stable/bq-aquaris.en
last update: 2015-06-16 08:40:02
version version: 23
version ubuntu: 20150611.3
version device: 20150529-8e13c5f
version custom: 20150528-722-29-15-vivid

> On 14 Jul 2015, at 22:46, Tony Espy <email address hidden> wrote:
>
>> From the fact you mentioned downloading r23, I'm assuming your have a BQ
> phone, is that correct? Can you provide us the system details for your
> phone via 'system-image-cli -i'?

[Tony Espy (awe)]

@LionelB

Thanks for the feedback.

First, here's an example of using the send-sms script ( with dummy numbers ):

/usr/share/ofono/scripts/send-sms /ril_1 6176666666 "dummy message" 0

The other thing to try is to swap your SIMs and see if that makes a difference. You currently have the 3 SIM in slot 1, which is currently enabled for 3g, whereas the Phone Co-op SIM is in the second slot, which is only capable of 2g. It could be that Phone Co-op's network doesn't support non-3g SMS messages. You can change which slot is capable of 3g via the Cellular system settings, or you can merely swap the SIMs and reboot.

[Tony Espy (awe)]

@Lionel

Also, have you contacted BQ's customer support regarding this problem?

[LionelB (retweet)]

That is interesting to know. I didn’t realise that the slots were different.

I have had the Phonecoop in SIM2 since I bought the phone though. So that can’t be the answer.

> On 21 Jul 2015, at 21:12, Tony Espy <email address hidden> wrote:
>
> The other thing to try is to swap your SIMs and see if that makes a
> difference. You currently have the 3 SIM in slot 1, which is currently
> enabled for 3g, whereas the Phone Co-op SIM is in the second slot, which
> is only capable of 2g. It could be that Phone Co-op's network doesn't
> support non-3g SMS messages. You can change which slot is capable of 3g
> via the Cellular system settings, or you can merely swap the SIMs and
> reboot.

[LionelB (retweet)]

In Settings, I have set SIM2 to 2g/3g and SIM1 to 2g. Does that mean I am limiting both to 2g ???

If there is a hardware difference, there shouldn’t be that 50:50 chance of getting it wrong ?

> On 21 Jul 2015, at 21:12, Tony Espy <email address hidden> wrote:
>
> The other thing to try is to swap your SIMs and see if that makes a
> difference. You currently have the 3 SIM in slot 1, which is currently
> enabled for 3g, whereas the Phone Co-op SIM is in the second slot, which
> is only capable of 2g. It could be that Phone Co-op's network doesn't
> support non-3g SMS messages. You can change which slot is capable of 3g
> via the Cellular system settings, or you can merely swap the SIMs and
> reboot.

[LionelB (retweet)]

It says “no such file or directory” when I do that.

> On 21 Jul 2015, at 21:12, Tony Espy <email address hidden> wrote:
>
> /usr/share/ofono/scripts/send-sms /ril_1 6176666666 "dummy message" 0

[LionelB (retweet)]

I haven’t. I did send an email about settings and they said they would get back to me but they never did.

At that time, it was working fine though with calls and texts. The problem I had then was not getting data.

They are a very small company and I suspect that I am the only person with that phone / provider combination.

Texts were fine up to the OTA, very sporadic immediately the update had loaded. So some change in the software triggered it, barring extreme coincidence.

3 continues to work fine.

I just switched briefly to Phone Coop to try a couple of test SMSs and both failed.

> On 21 Jul 2015, at 21:13, Tony Espy <email address hidden> wrote:
>
> Also, have you contacted BQ's customer support regarding this problem?

[LionelB (retweet)]

Apologies. I somehow read that as “have you contacted Phone Coop”.

No, I haven’t contacted BQ. It is 99.9% likely that the OTA triggered the fault and basic functionality is fine because 3 is unaffected.

Phone Coop said that “if there is a signal, it should work” ...

> On 21 Jul 2015, at 21:13, Tony Espy <email address hidden> wrote:
>
> Also, have you contacted BQ's customer support regarding this problem?

[LionelB (retweet)]

I checked this. 2g is still being used by Phone Coop for SMS at the moment but they are phasing it out.

Can you clarify, is SIM2 a 2g only based on hardware i.e. a different type than SIM1 ? Or did you just mean that was the setting on my phone at the time ?

> On 21 Jul 2015, at 21:12, Tony Espy <email address hidden> wrote:
>
> The other thing to try is to swap your SIMs and see if that makes a
> difference. You currently have the 3 SIM in slot 1, which is currently
> enabled for 3g, whereas the Phone Co-op SIM is in the second slot, which
> is only capable of 2g. It could be that Phone Co-op's network doesn't
> support non-3g SMS messages. You can change which slot is capable of 3g
> via the Cellular system settings, or you can merely swap the SIMs and
> reboot.

[Tony Espy (awe)]

As the phone was sold to you by BQ, you should probably contact them.

Regarding the SIM slots. The phone has what's called a dual-standby SIM implementation. Only of the two SIM slots is allowed to use a 3g network at any time.

> In Settings, I have set SIM2 to 2g/3g and SIM1 to 2g. Does that mean I am limiting both to 2g ???

No, it means SIM2 is the only SIM allowed to use 3g, but it may fall back to 2g if that's the only technology available. SIM1 is limited to 2g only.

Note, if you change SIM2 to allow 2g/3g, then the settings screen will show a spinner, and then automatically set to SIM to just 2g. This also causes a modem reset to occur.

Regarding the send-sms script, you're trying to run it on the phone itself, correct ( via the terminal or adb )? I double-checked and the path I gave you is correct. You can alternatively try to change to that directory and the command there:

$ cd /usr/share/ofono/scripts
$ ./send-sms /ril_0 6176666666 "dummy text message" 0

[LionelB (retweet)]

They said 2g is being phased out. Maybe their news is not up to date …

If it has already gone would I be seeing the signal still or would that disappear ?

> On 22 Jul 2015, at 19:53, Tony Espy <email address hidden> wrote:
>
> No, it means SIM2 is the only SIM allowed to use 3g, but it may fall
> back to 2g if that's the only technology available. SIM1 is limited to
> 2g only.

[LionelB (retweet)]

I put my first card in SIM 2. Guessing most would use SIM1 by default. Which would mean restricting their service unknowingly …

> On 22 Jul 2015, at 19:53, Tony Espy <email address hidden> wrote:
>
> No, it means SIM2 is the only SIM allowed to use 3g, but it may fall
> back to 2g if that's the only technology available. SIM1 is limited to
> 2g only.

[LionelB (retweet)]

I was reluctant to try this as I don’t want to ruin the service which is working well!

An interesting result though. With Three in slot 2 that service works fine (on 2g only).

The PhoneCoop card in slot1 does not function (2g and 3g enabled).

That is maybe the simplest and most conclusive test.

It seems to say that the configuration data for PhoneCoop is incorrect or the SIM card is damaged. The second explanation makes no sense. It was safe inside the slot.

> On 21 Jul 2015, at 21:12, Tony Espy <email address hidden> wrote:
>
> The other thing to try is to swap your SIMs and see if that makes a
> difference. You currently have the 3 SIM in slot 1, which is currently
> enabled for 3g, whereas the Phone Co-op SIM is in the second slot, which
> is only capable of 2g. It could be that Phone Co-op's network doesn't
> support non-3g SMS messages. You can change which slot is capable of 3g
> via the Cellular system settings, or you can merely swap the SIMs and
> reboot.

[LionelB (retweet)]

An update. I bought a voucher to put some credit on Phone Coop but I cannot call the number so I cannot add the credit ...

Since moving the Phone Coop SIM to slot 1, I have had one missed incoming call, two successful inward SMS text messages, one successful outgoing SMS text message.

It would be easier to understand if the failure was 100% of the time but there are those few examples of where it works.

The outgoing success was to a short dial text. Send BALANCE to 1250 and it responds with a balance. I just tried that again. Success out, success back. That service is free (and I have zero balance now). Still, there may be something about it being short dial. It has been quite reliable since the fault began.

There are other ways to top up but it means experimenting with £10. I was able to try the voucher experiment for only £5 !

To clarify - the number to call for adding credit is a free service. At the moment, other calls and toll SMS texts are not going to work because there is no credit. Some might (?) work if there was credit.

[LionelB (retweet)]

I have tried the Phonecoop SIM for the first time since the new OTA. A 'new voicemail' message appeared in Notifications. It dates to 19 September, as it turns out. Has appeared for the first time today though.

Today, I made a call twice to a short dial number. Both times it went through okay. So now I have credit ! My call to the voicemail (again using short dial) also went through without any problem.

A test text message just sent without problems.

It appears therefore that Phonecoop is now functioning properly again. I am still using the original SIM.

Seems that the OTA must have included a fix.

[LionelB (retweet)]

Confirmed. Phonecoop is now functioning normally again. Thank you.

[Jean-Baptiste Lallement (jibel)]

Thanks for following up. I'm closing this report due to your last comment.
Don't hesitate to submit any new bug.