Sailfish 'swallows' (ignores) incoming notifications (SMS & IM).

asked 2016-07-02 00:55:32 +0300

Mr.Pancake gravatar image

updated 2016-07-02 01:00:10 +0300

Hello,

I've seen a Jolla employee stating that if we find any discrepancies in any Sailfish OS releases we should report them, so here it goes.

On Sailfish OS 2.0.2.45 I noticed that sometimes it just ignores new text messages, both sms and im and just keeps silent. There is no LED notification, no sound, no indication in the events view. The text message is visible on Messages app cover, though.

My guess is that it might have something to do with the fact that the phone now wakes up to display occasional network changes, such as (connected to X; problem with connection; etc).

I have yet to find a pattern to reproduce it and/or note any specific actions that can lead to them. The issue affects native applications (perhaps, more than one?) as well as Android ones (Whatsapp in this case). Maybe there are other people out there who noticed something similar on this release, so I'm hoping for your help here.

P.S I updated to 2.0.2.45 to get rid of connectivity issues so I could start using the phone normally, so if you're about to tell me it's my fault for updating to unofficial versions - save our time.

edit retag flag offensive close delete

Comments

So you are using Jolla-C, right?

Because you just CANNOT use 2.0.2.45 on sbj-1, the HW adaptation in the release is not complete. Any bugs you encounter with this nonsupported configuration are your own fault and you just have to live with those.

I myself will wait until 2.0.2.x is released as preview candidate before updating to any other device than to Jolla-C.

juiceme ( 2016-07-02 21:25:26 +0300 )edit

Sorry, forgot to mention that I'm using a J1. The HW adaptation version is 1.0.0.13, not sure if it's the same for older firmwares.

I absolutely knew all the risks and I'm ready to live with that. It's just that everything worked absolutely fine in the beginning and now there is this issue out of nowhere.

I decided to share the finding if it is of any use to the devs and/or other people who might be running on 2.0.2.43 or *.45

Another reboot and the issue is gone, not sure for how long. If it will start working normally I'll delete the queation.

Mr.Pancake ( 2016-07-03 00:55:20 +0300 )edit
1

I've also noticed this, good to know I wasn't imagining things.

nthn ( 2016-07-03 14:35:45 +0300 )edit

+1 on J1. Haven't try to reboot yet. Just noticed the fact.

sail10 ( 2016-07-08 02:24:10 +0300 )edit

@Mr.Pancake do still have the issue? i have it with sfos 2.1.0.11

cemoi71 ( 2017-04-29 23:21:13 +0300 )edit