Phone app terminates if take the call after update 2.0.5.6 [not for everybody solved]

Question

8

Phone app terminates if take the call after update 2.0.5.6 [not for everybody solved]

asked 2016-11-24 20:24:41 +0300

chris_bavaria
1088 ●21 ●37 ●35

updated 2016-12-03 20:16:36 +0300

Hi,

I use a INTEX Aquafish with https://together.jolla.com/question/148893/how-to-make-aqua-fish-to-think-its-jolla-c-not-modem/ and updatet to 2.0.5.6. The phone rings, but every call terminate if I accept the calling. As well to call out, if my telephon call accepts the call. The call terminates while the first second, I hear a little short answer.

Is there a solution by replacing certain packages?

Thanks, Chris

[root@Sailfish nemo]# ssu s 
Device registration status: not registered
Device model: Jolla C (l500d / JP-1601)
Device UID: 911514800051268
Release: 2.0.5.6
Domain: sales

ofono-version

ofono-1.17+git36.1-1.48.1.armv7hl

ofono.log

Nov. 24 18:59:15.966 drivers/ril/ril_netreg.c: ril_netreg_get_signal_strength() gw: 7, cdma: -1, evdo: -1, lte: 99
Nov. 24 18:59:15.969 drivers/ril/ril_netreg.c: ril_netreg_strength_notify() 22
Nov. 24 18:59:15.969 RIL1> RESPONSE_VOICE_NETWORK_STATE_CHANGED
Nov. 24 18:59:15.972 RIL1> 0000: 01 00 00 00 ea 03 00 00                             ........
Nov. 24 18:59:15.977 drivers/ril/ril_network.c: ril_network_voice_state_changed_cb() ril_0 
Nov. 24 18:59:15.980 drivers/ril/ril_network.c: ril_network_poll_state() ril_0 
Nov. 24 18:59:15.980 RIL1< [00000233] OPERATOR
Nov. 24 18:59:15.985 RIL1< 0000: 16 00 00 00 33 02 00 00                             ....3...
Nov. 24 18:59:15.992 RIL1< [00000234] VOICE_REGISTRATION_STATE
Nov. 24 18:59:15.998 RIL1< 0000: 14 00 00 00 34 02 00 00                             ....4...
Nov. 24 18:59:16.002 RIL1< [00000235] DATA_REGISTRATION_STATE
Nov. 24 18:59:16.006 RIL1< 0000: 15 00 00 00 35 02 00 00                             ....5...
Nov. 24 18:59:16.008 RIL1> [00000232] OK
Nov. 24 18:59:16.011 RIL1> 0000: 00 00 00 00 32 02 00 00  00 00 00 00 01 00 00 00    ....2... ........
Nov. 24 18:59:16.014 RIL1  0010: 00 00 00 00 01 00 00 00  81 00 00 00 00 00 00 00    ........ ........
Nov. 24 18:59:16.017 RIL1  0020: 01 00 00 00 00 00 00 00  01 00 00 00 00 00 00 00    ........ ........
Nov. 24 18:59:16.019 RIL1  0030: 00 00 00 00 00 00 00 00  01 00 00 00 ff ff ff ff    ........ ........
Nov. 24 18:59:16.022 RIL1  0040: 01 00 00 00 00 00 00 00                             ........
Nov. 24 18:59:16.028 drivers/ril/ril_voicecall.c: ril_voicecall_parse_clcc() [id=1,status=0,type=1,number=,name=]
Nov. 24 18:59:16.028 RIL1> [00000233] OK
Nov. 24 18:59:16.032 RIL1> 0000: 00 00 00 00 33 02 00 00  00 00 00 00 03 00 00 00    ....3... ........
Nov. 24 18:59:16.034 RIL1  0010: 0b 00 00 00 56 00 6f 00  64 00 61 00 66 00 6f 00    ....V.o. d.a.f.o.
Nov. 24 18:59:16.037 RIL1  0020: 6e 00 65 00 2e 00 64 00  65 00 00 00 08 00 00 00    n.e...d. e.......
Nov. 24 18:59:16.041 RIL1  0030: 56 00 6f 00 64 00 61 00  66 00 6f 00 6e 00 65 00    V.o.d.a. f.o.n.e.
Nov. 24 18:59:16.044 RIL1  0040: 00 00 00 00 05 00 00 00  32 00 36 00 32 00 30 00    ........ 2.6.2.0.
Nov. 24 18:59:16.048 RIL1  0050: 32 00 00 00                                         2...
Nov. 24 18:59:16.052 RIL1> [00000234] OK
Nov. 24 18:59:16.055 RIL1> 0000: 00 00 00 00 34 02 00 00  00 00 00 00 0f 00 00 00    ....4... ........
Nov. 24 18:59:16.057 RIL1  0010: 01 00 00 00 35 00 00 00  04 00 00 00 32 00 30 00    ....5... ....2.0.
Nov. 24 18:59:16.060 RIL1  0020: 31 00 35 00 00 00 00 00  08 00 00 00 30 00 30 00    1.5..... ....0.0.
Nov. 24 18:59:16.062 RIL1  0030: 30 00 30 00 32 00 61 00  34 00 36 00 00 00 00 00    0.0.2.a. 4.6.....
Nov. 24 18:59:16.065 RIL1  0040: 02 00 00 00 31 00 36 00  00 00 00 00 ff ff ff ff    ....1.6. ........
Nov. 24 18:59:16.068 RIL1  0050: ff ff ff ff ff ff ff ff  01 00 00 00 30 00 00 00    ........ ....0...
Nov. 24 18:59:16.070 RIL1  0060: ff ff ff ff ff ff ff ff  01 00 00 00 30 00 00 00    ........ ....0...
Nov. 24 18:59:16.072 RIL1  0070: ff ff ff ff ff ff ff ff  01 00 00 00 30 00 00 00    ........ ....0...
Nov. 24 18:59:16.075 RIL1  0080: ff ff ff ff                                         ....
Nov. 24 18:59:16.079 drivers/ril/ril_network.c: ril_network_parse_response() ril_0 roaming,2015,00002a46,16,gsm,(null),(null)
Nov. 24 18:59:16.079 RIL1> [00000235] OK
Nov. 24 18:59:16.082 RIL1> 0000: 00 00 00 00 35 02 00 00  00 00 00 00 0b 00 00 00    ....5... ........
Nov. 24 18:59:16.085 RIL1  0010: 01 00 00 00 32 00 00 00  ff ff ff ff ff ff ff ff    ....2... ........
Nov. 24 18:59:16.087 RIL1  0020: ff ff ff ff 01 00 00 00  30 00 00 00 02 00 00 00    ........ 0.......
Nov. 24 18:59:16.089 RIL1  0030: 32 00 30 00 00 00 00 00  ff ff ff ff ff ff ff ff    2.0..... ........
Nov. 24 18:59:16.092 RIL1  0040: ff ff ff ff ff ff ff ff  ff ff ff ff                ........ ....
Nov. 24 18:59:16.102 drivers/ril/ril_network.c: ril_network_parse_response() ril_0 searching,(null),(null),-1,,0,20
Nov. 24 18:59:16.105 drivers/ril/ril_network.c: ril_network_poll_data_state_cb() ril_0 data registration changed
Nov. 24 18:59:16.109 src/gprs.c: ofono_gprs_status_notify() /ril_0 status 2
Nov. 24 18:59:16.111 drivers/ril/ril_voicecall.c: ril_voicecall_hangup_all() Hanging up call with id 1
Nov. 24 18:59:16.111 RIL1< [00000236] HANGUP
Nov. 24 18:59:16.114 RIL1< 0000: 0c 00 00 00 36 02 00 00  01 00 00 00 01 00 00 00    ....6... ........
Nov. 24 18:59:16.355 RIL1> [00000236] OK
Nov. 24 18:59:16.355 RIL1> 0000: 00 00 00 00 36 02 00 00  00 00 00 00                ....6... ....
Nov. 24 18:59:16.355 RIL1< [00000237] GET_CURRENT_CALLS
Nov. 24 18:59:16.355 RIL1< 0000: 09 00 00 00 37 02 00 00                             ....7...
Nov. 24 18:59:16.413 RIL1> OEM_HOOK_RAW
Nov. 24 18:59:16.413 RIL1> 0000: 01 00 00 00 04 04 00 00  2b 00 00 00 51 4f 45 4d    ........ +...QOEM
Nov. 24 18:59:16.413 RIL1  0010: 48 4f 4f 4b f7 03 08 00  1b 00 00 00 76 73 69 64    HOOK.... ....vsid
Nov. 24 18:59:16.414 RIL1  0020: 3d 32 38 32 38 35 37 34  37 32 3b 63 61 6c 6c 5f    =2828574 72;call_
Nov. 24 18:59:16.414 RIL1  0030: 73 74 61 74 65 3d 31 00                             state=1.
Nov. 24 18:59:16.414 RIL1> RESPONSE_CALL_STATE_CHANGED
Nov. 24 18:59:16.414 RIL1> 0000: 01 00 00 00 e9 03 00 00                             ........
Nov. 24 18:59:16.414 RIL1> [00000237] OK
Nov. 24 18:59:16.414 RIL1> 0000: 00 00 00 00 37 02 00 00  00 00 00 00 00 00 00 00    ....7... ........
Nov. 24 18:59:16.414 src/voicecall.c: ofono_voicecall_disconnected() Got disconnection event for id: 1, reason: 1
Nov. 24 18:59:16.419 RIL1> OEM_HOOK_RAW
Nov. 24 18:59:16.419 RIL1> 0000: 01 00 00 00 04 04 00 00  11 00 00 00 51 4f 45 4d    ........ ....QOEM
Nov. 24 18:59:16.419 RIL1  0010: 48 4f 4f 4b fa 03 08 00  01 00 00 00 00 00 00 00    HOOK.... ........
Nov. 24 18:59:16.432 RIL1> SIGNAL_STRENGTH
Nov. 24 18:59:16.432 RIL1> 0000: 01 00 00 00 f1 03 00 00  07 00 00 00 00 00 00 00    ........ ........
Nov. 24 18:59:16.432 RIL1  0010: ff ff ff ff ff ff ff ff  ff ff ff ff ff ff ff ff    ........ ........
Nov. 24 18:59:16.432 RIL1  0020: ff ff ff ff 63 00 00 00  ff ff ff 7f ff ff ff 7f    ....c... ........
Nov. 24 18:59:16.433 RIL1  0030: ff ff ff 7f ff ff ff 7f  ff ff ff 7f                ........ ....

EDIT: Title adjusted. EDIT_2: add "after update 2.0.5.6" to title EDIT_3: mark title to "solved" EDIT_4: mark title to "not for everybody solved" because open request is pending

edit retag flag offensive close delete

Comments

Are you by chance on GSM2?

lakutalo ( 2016-11-24 20:42:42 +0300 )edit

I tested all the bands, but nothing changed. Mobile data is running in every band. :confused:

chris_bavaria ( 2016-11-24 21:10:04 +0300 )edit

Now I tried

zypper ref
zypper up

Is the problem with the packages farstream telepathy-farstream telepathy-qt5 telepathy-qt5-farstream ?

All repositories have been refreshed.
[root@Sailfish nemo]# zypper up 
PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running.
Tell PackageKit to quit? [yes/no] (no): yes
Loading repository data...
Reading installed packages...

The following package updates will NOT be installed:
  farstream telepathy-farstream telepathy-qt5 telepathy-qt5-farstream 

Nothing to do

.

chris_bavaria ( 2016-11-24 21:24:41 +0300 )edit

2

You are sailing on risky waters if you start updating individual packages. This may break the integrity of the OS in your device.
The primary tool for getting Sailfish OS updates is at the menu page Settings > Sailfish OS updates.
Should that fail for a reason or another, then the next option is to go on the command line and do:

version --dup      ## note the two (2) dash characters

This command checks if the package versions of your device are in line with the OS version indicated by command ssu status. It downloads and installs any required updates. After the command has completed you should restart your device.

jovirkku ( 2016-11-28 10:23:25 +0300 )edit

Are you by chance on GSM2?
lakutalo ( 2016-11-24 20:42:42 +0300 )edit
I tested all the bands, but nothing changed. Mobile data is running in every band. :confused:
chris_bavaria ( 2016-11-24 21:10:04 +0300 )edit
Now I tried
zypper ref zypper up
Is the problem with the packages farstream telepathy-farstream telepathy-qt5 telepathy-qt5-farstream ?
All repositories have been refreshed. [root@Sailfish nemo]# zypper up PackageKit is blocking zypper. This happens if you have an updater applet or other software management application using PackageKit running. Tell PackageKit to quit? [yes/no] (no): yes Loading repository data... Reading installed packages... The following package updates will NOT be installed: farstream telepathy-farstream telepathy-qt5 telepathy-qt5-farstream Nothing to do
.
chris_bavaria ( 2016-11-24 21:24:41 +0300 )edit
You are sailing on risky waters if you start updating individual packages. This may break the integrity of the OS in your device.
The primary tool for getting Sailfish OS updates is at the menu page Settings > Sailfish OS updates.
Should that fail for a reason or another, then the next option is to go on the command line and do:
version --dup ## note the two (2) dash characters
This command checks if the package versions of your device are in line with the OS version indicated by command ssu status. It downloads and installs any required updates. After the command has completed you should restart your device.
jovirkku ( 2016-11-28 10:23:25 +0300 )edit

Answer 1

1

answered 2016-11-25 07:30:48 +0300

Bundyo
1288 ●16 ●25 ●25

updated 2016-12-02 23:02:14 +0300

I have the same problem, but on OnePlus X. If I upgrade to 2.0.5.6, every call terminates after one of the sides picks up. Problem resolves if I downgrade to 2.0.4.14.

When I ran zypper up, I also had farstream blocked, but there were several other packages too.

EDIT: I found the problem - purple-facebook is clashing with the new farstream - needs to be removed for the update to go through. You can also force the farstream installation with

zypper in farstream

as root, which will ask you what to do and you can choose to remove purple-facebook and its minions. Everything works after that, except of course Facebook Messenger integration in accounts :)

edit flag offensive delete publish link

Comments

The same problem.....

I downgradet to 2.0.2.51 with "ssu re 2.0.2.51", after reboot I get the update to 2.0.5.6 in "Settings > Sailfish OS updates"

I think some farstream packages were damaged in 2.0.4.14, so the update from 2.0.4.14 to 2.0.5.6 was not complete.

I hope you can solve your problem with it, Chris

chris_bavaria ( 2016-11-30 05:39:38 +0300 )edit

Answer 2

1

answered 2016-11-28 19:48:11 +0300

chris_bavaria
1088 ●21 ●37 ●35

I solved it with:

ssu re 2.0.2.51
version --dup
reboot

then I get an update with "Settings > Sailfish OS updates" and pull down to seek for update 2.0.5.6

Done!!

edit flag offensive delete publish link

Comments

So basically, downgrading to an older version and then executing a full upgrade again can fix this problem (just describing your solution more generally in case someone has the same problems in the future where 2.0.2.51 is no longer available)

ghling ( 2016-11-29 11:35:03 +0300 )edit

Unfortunately, I do not know what the problem is located. Numerous attempts have brought me to the idea of downgrading a stage lower and it has worked. The ofono.log I sent to the developers, I think they will consider this problem in the final update.

chris_bavaria ( 2016-11-30 05:45:36 +0300 )edit

Answer 3

0

answered 2016-11-24 22:13:43 +0300

chris_bavaria
1088 ●21 ●37 ●35

Hi,

after several attemts, I found errors in non-updated packages during upgrade from 2.0.4.14 to 2.0.5.6

Installed   farstream-0.1.2-1.1.6.armv7hl               Libraries for video conferencing applications
Available   farstream-0.2.7-1.2.2.armv7hl               Libraries for video conferencing applications
Installed   telepathy-farstream-0.4.0-1.1.6.armv7hl Telepathy client library to handle Call channels
Available   telepathy-farstream-0.6.0-1.2.3.armv7hl Telepathy client library to handle Call channels
Installed   telepathy-qt5-0.9.4+git2-1.6.6.armv7hl      Qt 5 Telepathy library
Available   telepathy-qt5-0.9.7+git1-1.9.1.armv7hl      Qt 5 Telepathy library
Installed   telepathy-qt5-farstream-0.9.4+git2-1.6.6.armv7hl    Qt 5 Telepathy/Farstream integration
Available   telepathy-qt5-farstream-0.9.7+git1-1.9.1.armv7hl    Qt 5 Telepathy/Farstream integration

Someone knows a solution to solve this?

Thanks Chris

edit flag offensive delete publish link

Comments

I just checked with my Aqua Fish (which I also "converted" to a Jolla C) and did not found any packages that were not installed during the update to 2.0.5. In fact, all packages you mention are installed in the updated version on my phone. I'd also recommend trying to update those packages and see if this resolves your problem. May I recommend using pkcon to try to update those packages?

pkcon get-updates

should list those updates as well, then

pkcon update

should update them. If the update fails, I'd check journalctl to see what causes the error.

ghling ( 2016-11-25 12:13:51 +0300 )edit

Hi, pkcon takes the old packages without alerts. try

zypper ref
zypper up

can you post your output from

pkcon search name telepathy
pkcon search name farstream

Have you updatet to 2.0.5.6 and your callings are fine?

chris_bavaria ( 2016-11-25 18:50:05 +0300 )edit

Hi, I have updated my phone to 2.0.5 and everything seems to work normal (phone calls included). Both pkcon and zypper tell me that all my packages are up to date (the one you mentioned included). So my idea was that it is possible those outdated packages on your phone are the reason for your problems (or the problem is the reason why they can't be updated).

I'm sure you already tried that, but if not: try to update those packages and see, if / what errors occur.

ghling ( 2016-11-27 18:28:24 +0300 )edit

Answer 4

0

answered 2016-12-03 13:45:13 +0300

This post is a wiki. Anyone with karma >75 is welcome to improve it.

updated 2016-12-03 13:45:13 +0300

foo
1 ●1 ●2 ●4

I have the same problem with calls. Downgraded to 2.0.2.51 and then up to 2.0.5.6 again, but the call problem persists. Any ideas about how to solve this?

edit flag offensive delete publish link

Comments

Check my answer above - you need to remove purple-facebook for the update to go through.

Bundyo ( 2016-12-04 23:26:36 +0300 )edit

Phone app terminates if take the call after update 2.0.5.6 [not for everybody solved]

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Stats

Related questions

Phone app terminates if take the call after update 2.0.5.6 [not for everybody solved]

Comments

4 Answers

Comments

Comments

Comments

Comments

Question tools

Public thread

Stats

Related questions