We have moved to a new Sailfish OS Forum. Please start new discussions there.
0

Android runtime crashes when dismissing Signal background notification notification

asked 2017-09-14 09:44:38 +0300

mobilthor gravatar image

I installed the Android Signal app on my Jolla 1, since the native Jolla one doesn't fly with the official server. Since the beginning, and also with Sailfish 2.1.1.26, I have to remember _not_ to dismiss the notification about Signal background notifications being activated. Once I do this, the whole Android runtime crashes along with other open apps.

This is 100% reliable for me, and has been that way since I tried Signal on the device. A side effect (if I remember not to dismiss the notification) of this is that I have to ignore the icon about Signal notifications pending, not having a clue about actual messages waiting or not.

Does nobody else have this problem? There is no chance involved. It happens every time for me.

edit retag flag offensive close delete

Comments

Using LibreSignal Jolla Edition I cannot reproduce the issue.

leszek ( 2017-09-14 12:28:58 +0300 )edit

You mean the LibreSignal Sailfish app, right (which is an abandoned dead end, AFAIR)? I am talking about the official Signal Android app, installed from a direct download from their website. I read something on the Sailfish release notes about such an issue, but for me the crash happens with the latest SFOS just like before.

mobilthor ( 2017-09-15 08:25:23 +0300 )edit

Same problem on SailfishX 2.1.3.7: After starting the Signal Android app, the notification about running background service is shown and pressing the notification in the events view leads to a crash of all open Android apps. The Riot.im Adroid app behaves as expected after pressing the notification in the events view: Riot app maximises, no Android App crashes.

dvdk ( 2017-12-12 03:56:32 +0300 )edit

1 Answer

Sort by » oldest newest most voted
0

answered 2017-09-15 08:31:26 +0300

quatrox gravatar image

updated 2017-09-15 08:34:32 +0300

If I close all the notifications from Telegram (or untappd), the program closes while the service still runs in the background. This means I don't see an icon on the home screen, but the service still listen for new events. If a new events occur, I get a notification. If I tap on the notification, the app opens.

Could this be what you are experiencing?

edit flag offensive delete publish link more

Comments

No. The Android runtime definitely crashes. I got Signal and another app as tile on the home screen. Both crash (get greyed out). When I tap on one of them, there is the delay associated with a fresh start of the Android runtime and the application opens anew, complete with the notification about the background service.

I have to wonder if this is really a peculiar situation with my device. Others don't seem to see this rather obvious problem. Well, it did not really want to do the latest update (only after several attempts it succeeded) … maybe I'd need to install a fresh OS image. But I must admit that my patience is running out and I'm investigating an Android device after all now. I got the Sailfish device for about 3 years and it never really worked right:-(

mobilthor ( 2017-09-19 08:13:49 +0300 )edit
Login/Signup to Answer

Question tools

Follow
1 follower

Stats

Asked: 2017-09-14 09:44:38 +0300

Seen: 193 times

Last updated: Sep 15 '17