We have moved to a new Sailfish OS Forum. Please start new discussions there.
1 | initial version | posted 2019-03-20 11:56:36 +0200 |
I could update my device, but the dialer seems to crash: If I start the dialer, the home screen shows the cover page with a spinner for a short time bevore it disappears.
Any solutions?
2 | No.2 Revision |
I could update my device, but the dialer seems to crash: If I start the dialer, the home screen shows the cover page with a spinner for a short time bevore it disappears.
Any solutions?
I could reproducte the problem after factory reset. I updated my Intex Aqua Fish to the latest release, that Intex did provice. Then I updated step by steop to the stop releases:
devel-su
ssu release 2.2.0.29
version --dup
reboot
devel-su
ssu release 3.0.0.8
version --dup
reboot
Next upadates are not possible with this approach. So I had to use the folliwing commands:
devel-su
ssu release 3.0.1.11
pkcon refresh
pkcon -v update
reboot
devel-su
ssu release 3.0.2.8
pkcon refresh
pkcon -v update
reboot
With a direct update from the stop release 3.0.0.8 to 3.0.2.8 I get a white screen after reboot. So I did execute the intermediate step after another factory reset.
3 | No.3 Revision |
I could update my device, but the dialer seems to crash: If I start the dialer, the home screen shows the cover page with a spinner for a short time bevore it disappears.
Any solutions?
I could reproducte the problem after factory reset. I updated my Intex Aqua Fish to the latest release, that Intex did provice. Then I updated step by steop to the stop releases:
devel-su
ssu release 2.2.0.29
version --dup
reboot
devel-su
ssu release 3.0.0.8
version --dup
reboot
Next upadates are not possible with this approach. Unfortunately, this is a well known behaviour. So I had to use the folliwing commands:
devel-su
ssu release 3.0.1.11
pkcon refresh
pkcon -v update
reboot
devel-su
ssu release 3.0.2.8
pkcon refresh
pkcon -v update
reboot
With a direct update from the stop release 3.0.0.8 to 3.0.2.8 I get a white screen after reboot. So I did execute the intermediate step after another factory reset.