Cannot receive calls or text messages with 3G Enabled in Italy on BQ Aquaris E4.5

[Nicola]

After running some test on my BQ Aquaris E4.5 I have finally found it!

This is WHY some incoming calls are not shown and the phone don't ring! ( so you receive the message of a miss call by your mobile operator)

Here the procedure:

- Turn on your BQ Aquaris E4.5
- At first you will connected with 2G
- Ask someone to call you: it will work
- Wait some second for the 3G connection
- Ask someone to call you again: don't work! ( so you will be only notified by your mobile operator of a missed call)

How to solve:

- Go in your connection settings
- Choose to use only 2G connection
- Ask someone to call you: it will always work!

Please work on IT! Thanks from Italy!

[nives (nives)]

Yes, 3G connection still don't work properly since ota-5 :-(

[nives (nives)]

Also 3G Connection is really unstable. Works only for few seconds then stops again ( Using Vodafone Italy)

[Antonio (antoema)]

With 2G/3G mode it's impossible to receive messages and calls. I confirm that the only working mode is the 2G (battery save) only mode. Anyone has already fixed it?

Help me

[Jean-Baptiste Lallement (jibel)]

Thanks for your report.

@Nicola and Antonio which operator are you using?

Could you please provide the version of your phone (system-settings / about this phone / OS) ?

If you're comfortable with shell commands, could you please enable developer mode, install android tools on a PC, connect the phone to a PC with a USB cable, reproduce the issue and run the following commands (the way to connect to the device, install android tools for adb and collect the information below may slightly differ depending on the host operating system):
$ adb pull /var/log/syslog /tmp/syslog
$ adb shell /usr/share/ofono/scripts/list-modems > /tmp/list-modems
$ adb shell /usr/share/ofono/scripts/list-contexts > /tmp/list-contexts
$ adb shell nmcli d > /tmp/nmcli-d

and attach the files /tmp/syslog, /tmp/list-modems, /tmp/list-contexts, /tmp/nmcli-d to this bug report.

Thanks.

[Alfonso Sanchez-Beato (alfonsosanchezbeato)]

It would also be interesting to gather the radio log while trying to call the phone. Please try this:

adb shell
sudo /system/bin/logcat -b radio -c
sudo /system/bin/logcat -b radio > /tmp/radio.txt

* Now try to call the phone. After it fails:

exit
adb pull /tmp/radio.txt /tmp/

and attach /tmp/radio.txt to the bug.

[Nicola (jackoswebsolutions)]

Sure, I will run some test when I'will back from work.
Thanks

[Nicola (jackoswebsolutions)]

@Jean-Baptiste Lallement

For now, here are the phone/os version:

Bq Aquaris E4.5 running Ubuntu 15.04 - armhf (20150825-170536) build 25

build: KRILIN01A_BQ_L100EN_2025_150825

[Nicola (jackoswebsolutions)]

Guys I've a little problem: I have already setted my device as an ADB interface but...the adb.exe can't see my device :|
Any idea?

[Jean-Baptiste Lallement (jibel)]

@Nicola, given the name of the binary I suppose you are using windows and, unfortunately I have no experience with windows version of adb. Can you make sure developer mode is enabled on your device, then disconnect/reconnect the device to your machine?

[Nicola (jackoswebsolutions)]

@Jean-Baptiste Lallement

sure it's enabled!

So...i will try on a linux machine as suon as possible ;-)

[Nicola (jackoswebsolutions)]

Here we go! I hope this will work!

@Alfonso Sanchez-Beato This first attachment is for you!

[Alfonso Sanchez-Beato (alfonsosanchezbeato)]

@Nicola, I see a call in the radio log that is apparently hang up from the user side, so apparently all is normal. Please try this:

adb shell
sudo su
stop ofono
OFONO_RIL_DEVICE=mtk OFONO_RIL_NUM_SIM_SLOTS=2 OFONO_RIL_HEX_TRACE="" OFONO_RIL_TRACE="" ofonod -nd -P stktest,provision,sap,udev,dun,smart,hfp &> /tmp/ofono.txt

* Wait to see you have 3G coverage and make the call. After it fails:

* Press Ctrl+C

exit
adb pull /tmp/ofono.txt /tmp/

and attach /tmp/ofono.txt to the bug. Please just make one call to have a clean log. If at a first try you cannot reproduce the error, press ctrl+c and follow these steps from the beginning.

Finally, just reboot to return your phone to a good state.

[Nicola (jackoswebsolutions)]

Alfonso i will try this evening.

Some times using "pull" command shows "command don't exist"..
I'll keep you update

[Nicola (jackoswebsolutions)]

@Alfonso here we go ;-)

[Nicola (jackoswebsolutions)]

News?

[Alfonso Sanchez-Beato (alfonsosanchezbeato)]

@Nicola, I have been taking a look at the log, it shows 2 calls, one is hang from the phone, the other one is hang from the remote end. Do you remember how many times did you try to call to the phone and of those which were successful (phone ringing) or not?

If you do not remember exactly it might be worth retrying the steps in #12, now keeping the record of the calls you did, which were successful, where did you hang the call from, the order, etc. Otherwise it is difficult to know if something is wrong in the traces or not.

[Nicola (jackoswebsolutions)]

I made two calls, both fails!

[Alfonso Sanchez-Beato (alfonsosanchezbeato)]

@Nicola, then it might be a powerd bug instead of an ofono bug.

Did you hear a calling tone in the caller phone?

Could you attach /var/log/syslog after another failure (no special steps in this case :)

[Nicola (jackoswebsolutions)]

Negativa, from the calling phone the only thing that I can hear is the voicemail

Sure I will try to get that log too :)

[PAVUK (marek-antozi)]

Hello,

there is similar issue reported in bug 1634544, may be related. I posted my ofono.txt and syslog outputs there.

Regards,

-Marek Antozi