Interesting. Just started Whisperfish (as I shut it off this morning and used Signal for some hours) and now it is working again… 
Do you want me to send some logs, anyway?
And yes: I didn’t re-register.
Only if you can reproduce… There are quite some fixes upcoming. Has the offending message come up again with an extra checkmark?
1 Like
No extra checkmark. These messages just have one hook, instead of two.
2 Likes
Hi! Recently, I don’t see messages of more and more contacts in Whisperfish. I see my messages I sent to them though. Is this a known bug or should I capture logs?
1 Like
Known issue with a known fix. Should get released asap.
7 Likes
Thank you for whisperfish.
I have a JP2 with SFos 5.2. I tried to install the share plugin, from openrepos. the pre 4.2 version was available, while the 4.3+ version wasnt. I tried anyway, and unsurprisingly got an error.
yet, afterwards, the 4.3+ version resulted installed, and it works
Im happy it works, but the process was confusing, to say the least.
2 Likes
I just migrated my Whisperfish installation to my new JP2026 following the migration guide on the Whisperfish Wiki. Basically all I had to do was copying two folders as described and install Wisperfish. Now I can start Whisperfish on the new device and see all my past conversations. That worked well - thank’s for the Wiki guide!
Unfortunatly Whisperfish seems to have a connection problem after migration. Running from console with “–verbose” I can see messages like these popping up :
2026-09-15T12:50:00.791321Z ERROR whisperfish::worker::client: Error starting stream. Retrying in 10s error=Websocket error: websocket upgrade failed
2026-09-15T12:50:11.156219Z ERROR whisperfish::worker::client: Error starting stream. Retrying in 10s error=Websocket error: websocket upgrade failed
2026-09-15T12:50:21.530037Z ERROR whisperfish::worker::client: Error starting stream. Retrying in 10s error=Websocket error: websocket upgrade failed
2026-09-15T12:50:31.902885Z ERROR whisperfish::worker::client: Error starting stream. Retrying in 10s error=Websocket error: websocket upgrade failed
2026-09-15T12:50:42.278005Z ERROR whisperfish::worker::client: Error starting stream. Retrying in 10s error=Websocket error: websocket upgrade failed
I am connected to WiFi and have a working internet access. I installed latest Whisperfish with Storeman from OpenRepos via WiFi/internet without connection problems.
What could I do or try to let Wisperfish connect?
For the sake of completeness, it should be noted that I did not alter power settings with “mcetool --set-suspend-policy=disabled“ so far on my new JP2026. I don’t know if this is still necessary with JP2026 - that’s why I left that step out for now.
Hmm… I’m afraid I re-registered - without meaning to - my primary device during the migration to my new phone (see post above). I assume that therefor I have lost the linking with Whisperfish.
What happened: I used Molly FOSS as my primary device and Whisperfish as my secondary device. The term device is a bit misleading here because both apps were actually running on the same SailfishOS device: Molly FOSS via Android App Support (AAS) and Whisperfish as native app.
During the migration to my new JP2026 I first migrated Molly FOSS. I did that by starting with a fresh installation via F-Droid on the new phone and used a local backup file as a starting point for Molly FOSS. I created that local backup file upfront on the old phone. It all went fine - I see all my chats in Molly FOSS and can send and receive messages
Neverthless I don’t see any linked devices on the new phone when I check the settings in Molly FOSS (Settings → Linked devices). I though this way of migration with a local backup file would transfer the whole Molly FOSS installation 1:1 to the new device. But that doesn’t seem to be the case.
Do I see this right: Althoug I copied all Whisperfish data to my new phone and although I see all my chats there (and in Molly FOSS too) I have to reset Whisperfish (losing all my chats in Whisperfish) to be able to register again ( Frequently Asked Questions · Wiki · Whisperfish / Whisperfish - Signal on Sailfish OS · GitLab )? No chance to re-register Whisperfish as secondary device and keep all my data?
I’m using Whisperfish as a secondary client and Signal Android as my primary one. Most things seem to work, although I need to use it more. However, if I delete a message in Signal Android, it isn’t deleted in Whisperfish.
I don’t like the sound that plays when I receive a message in a chat that I already have open. It would be cool if we could disable it.
1 Like
A request, if not already in scope: A possibility to silence notifications from specific persons or groups, like the one in the Signal app. 
1 Like
this is already possible: long press on the chat and you can choose “silence” among other options
2 Likes
The one thing I didn’t test, aaaahahahaha - thanks
2 Likes
Oh. Do we still have this in our README? I haven’t used that myself in my previous two or three phones now. @direc85, thoughts?
I think you see this right, indeed. You could try to run @j6s’ message restore tool though: GitHub - j6s/harbour-whisperfish-message-restore · GitHub
That’s interesting, although I know about some related bugs. Do I assume correctly this is a Whisperfish-sent message deleted from Android?
I’m starting to think it’s indeed not very Sailfish-y either. Noted.
5 Likes
Both ways if I remember correctly
I thought I already removed that! I don’t think I have ever used that… (And by “ever” I mean since February 2021 which is my first commit of Whisperfish.) That has been there since 2017, when Whisperfish was still a Go application, so I’m sure the reason for that doesn’t exist anymore. MR created to fix that (and buncha others) issues in .md files!
I added that because that’s what Sailfish Messages app does. But the typical SMS pattern is “send a few messages here and then” and not so much “keep the conversation going” so I think there should be an option to disable it.
This seems to be broken in note-to-self chat at least (but that’s not a huge burning issue). Is this broken in 1-on-1 and group chats as well? I couldn’t easily reproduce this myself. (But then again, I’m running on a, well, slightly experimental branch.) (It shouldnt have touched these things though…)
My largest group is “only” ~100 members, so your group really is a valuable test case! Okay, there are four things, some of which already are being improved:
- Opening the groups are slow (merged, not released)
- Sending delivery/read receipts in group is slow (merged, not released)
- Sending messages in group is slow (in progress)
- Scrolling the list of members is slow (reported)
I wasn’t really aware that scrolling through the group member list was an issue. I hacked my group info page to have ten times the members, and sure enough, scrolling through a thousand recipients is a slideshow. QML already does a lot of implicit magic to save resources, but I think that’s only solvable by pagination of some sort.
2 Likes
Oh yeah, It was in a note-to-self chat.
2 Likes
The group I am in is more of a news channel, where only admins can send messages - thus I can only really test the following of your points:
For both of them, I can confirm that they are pretty slow. I’ll check on monday, if I can get the Sailfish SDK set up on Linux. Somehow, it didn’t like my docker environment on macOS (Can’t blame it, I don’t like the weird “Docker in a VM” setup on OSX either)
Interestingly, I did notice 2 things about Signal recently:
- When sending pasted links on official clients fast enough, link previews will not appear on the receiving end
- At least in the signal desktop database, link previews seem to be part of the received message
This leads me to believe, that the previews are generated on the sending device and transmitted alongside the message itself. This should, in theory mean, that adding receiving link previews shouldn’t be incredibly hard. Maybe I’ll have a crack at it.
(Sending link previews should be a whole different beast, I would imagine)
Yeah, it is like that
1 Like
Thanks for verifying!
This is a known issue; Whisperfish supports the setting, but not yet the feature. The link preview data is indeed sent along the message – the same status here.
Welp, turns out this is my own doing… Created a merge request to properly fix those issues once and for all! (Fetching group members from database is still “slow”, but not so slow it would matter here.)
1 Like