whatsapp

Rating: 
3.727275
Your rating: None Average: 3.7 (11 votes)

i created a whatsapp app based on whatsmeow, which is written in go. unfortunately it is only possible to register as second device, like the browser. it only has minimal  saljail permissions out of the box, internet and secrets for  storing the registration. one  can add contacts permssions or meda files permissions through a command that can be copied to clipboard and  edits the desktop file to add or remove these optional permissions. for listening to voice messages you can put the phone to your ear, and sound comes through the earpiece and the display is turned off, if you remove the phone from your ear both are turned back, like in original whatsapp. i used claude "ai" to develop this app. sources are here: https://github.com/smatkovi/harbour-whatsapp i updated  whatsmeow and fixed the errors you reported. thanks for all your comments and  error reports.

Screenshots: 
Application versions: 
AttachmentSizeDate
File harbour-whatsapp-0.9.183-1.armv7hl.rpm6.99 MB31/07/2026 - 18:56
File harbour-whatsapp-0.9.183-1.i486.rpm7.26 MB31/07/2026 - 18:56
File harbour-whatsapp-0.9.183-1.aarch64.rpm6.83 MB31/07/2026 - 18:56
File harbour-whatsapp-0.9.184-1.i486.rpm7.26 MB31/07/2026 - 19:09
File harbour-whatsapp-0.9.184-1.armv7hl.rpm6.99 MB31/07/2026 - 19:09
File harbour-whatsapp-0.9.184-1.aarch64.rpm6.83 MB31/07/2026 - 19:09
File harbour-whatsapp-0.9.188-1.aarch64.rpm6.84 MB31/07/2026 - 22:22
File harbour-whatsapp-0.9.188-1.armv7hl.rpm6.99 MB31/07/2026 - 22:22
File harbour-whatsapp-0.9.188-1.i486.rpm7.27 MB31/07/2026 - 22:22
File harbour-whatsapp-0.9.189-1.armv7hl.rpm7 MB31/07/2026 - 23:27
File harbour-whatsapp-0.9.189-1.i486.rpm7.27 MB31/07/2026 - 23:27
File harbour-whatsapp-0.9.189-1.aarch64.rpm6.84 MB31/07/2026 - 23:27
File harbour-whatsapp-0.9.193-1.i486.rpm7.28 MB01/08/2026 - 00:52
File harbour-whatsapp-0.9.193-1.armv7hl.rpm7.01 MB01/08/2026 - 00:52
File harbour-whatsapp-0.9.193-1.aarch64.rpm6.85 MB01/08/2026 - 00:52
File harbour-whatsapp-0.9.195-1.armv7hl.rpm7.02 MB01/08/2026 - 01:24
File harbour-whatsapp-0.9.195-1.i486.rpm7.29 MB01/08/2026 - 01:24
File harbour-whatsapp-0.9.195-1.aarch64.rpm6.86 MB01/08/2026 - 01:24
File harbour-whatsapp-0.9.196-1.i486.rpm7.29 MB01/08/2026 - 01:24
File harbour-whatsapp-0.9.196-1.armv7hl.rpm7.02 MB01/08/2026 - 01:24
File harbour-whatsapp-0.9.196-1.aarch64.rpm6.86 MB01/08/2026 - 01:24
File harbour-whatsapp-0.9.198-1.aarch64.rpm6.87 MB01/08/2026 - 10:39
File harbour-whatsapp-0.9.198-1.armv7hl.rpm7.03 MB01/08/2026 - 10:39
File harbour-whatsapp-0.9.198-1.i486.rpm7.3 MB01/08/2026 - 10:39
File harbour-whatsapp-0.9.199-1.i486.rpm7.3 MB01/08/2026 - 11:46
File harbour-whatsapp-0.9.199-1.armv7hl.rpm7.03 MB01/08/2026 - 11:46
File harbour-whatsapp-0.9.199-1.aarch64.rpm6.87 MB01/08/2026 - 11:46
File harbour-whatsapp-0.9.201-1.i486.rpm7.3 MB01/08/2026 - 14:33
File harbour-whatsapp-0.9.201-1.armv7hl.rpm7.03 MB01/08/2026 - 14:33
File harbour-whatsapp-0.9.201-1.aarch64.rpm6.88 MB01/08/2026 - 14:33
File harbour-whatsapp-0.9.206-1.i486.rpm7.31 MB01/08/2026 - 15:37
File harbour-whatsapp-0.9.206-1.armv7hl.rpm7.04 MB01/08/2026 - 15:37
File harbour-whatsapp-0.9.206-1.aarch64.rpm6.88 MB01/08/2026 - 15:37
File harbour-whatsapp-0.9.207-1.i486.rpm7.31 MB01/08/2026 - 20:12
File harbour-whatsapp-0.9.207-1.armv7hl.rpm7.04 MB01/08/2026 - 20:12
File harbour-whatsapp-0.9.207-1.aarch64.rpm6.88 MB01/08/2026 - 20:12
File harbour-whatsapp-0.9.214-1.i486.rpm9.66 MB02/08/2026 - 01:05
File harbour-whatsapp-0.9.214-1.armv7hl.rpm9.39 MB02/08/2026 - 01:05
File harbour-whatsapp-0.9.214-1.aarch64.rpm9.24 MB02/08/2026 - 01:05
File harbour-whatsapp-0.9.215-1.i486.rpm9.67 MB02/08/2026 - 04:55
File harbour-whatsapp-0.9.215-1.armv7hl.rpm9.39 MB02/08/2026 - 04:55
File harbour-whatsapp-0.9.215-1.aarch64.rpm9.24 MB02/08/2026 - 04:55
File harbour-whatsapp-0.9.217-1.armv7hl.rpm9.39 MB04/08/2026 - 17:55
File harbour-whatsapp-0.9.217-1.i486.rpm9.67 MB04/08/2026 - 17:55
File harbour-whatsapp-0.9.217-1.aarch64.rpm9.24 MB04/08/2026 - 17:55
File harbour-whatsapp-0.9.229-1.i486.rpm9.69 MB07/08/2026 - 19:24
File harbour-whatsapp-0.9.229-1.armv7hl.rpm9.42 MB07/08/2026 - 19:24
File harbour-whatsapp-0.9.229-1.aarch64.rpm9.26 MB07/08/2026 - 19:24
File harbour-whatsapp-0.9.230-1.i486.rpm9.7 MB07/08/2026 - 19:42
File harbour-whatsapp-0.9.230-1.armv7hl.rpm9.42 MB07/08/2026 - 19:42
File harbour-whatsapp-0.9.230-1.aarch64.rpm9.27 MB07/08/2026 - 19:42
File harbour-whatsapp-0.9.245-1.i486.rpm9.72 MB11/08/2026 - 22:14
File harbour-whatsapp-0.9.245-1.armv7hl.rpm9.44 MB11/08/2026 - 22:14
File harbour-whatsapp-0.9.245-1.aarch64.rpm9.29 MB11/08/2026 - 22:14
File harbour-whatsapp-0.9.255-1.i486.rpm9.74 MB13/08/2026 - 14:41
File harbour-whatsapp-0.9.255-1.armv7hl.rpm9.47 MB13/08/2026 - 14:41
File harbour-whatsapp-0.9.255-1.aarch64.rpm9.31 MB13/08/2026 - 14:41
File harbour-whatsapp-0.9.263-1.i486.rpm9.75 MB15/08/2026 - 20:45
File harbour-whatsapp-0.9.263-1.armv7hl.rpm9.48 MB15/08/2026 - 20:45
File harbour-whatsapp-0.9.263-1.aarch64.rpm9.32 MB15/08/2026 - 20:45
File harbour-whatsapp-0.9.264-1.i486.rpm9.75 MB15/08/2026 - 22:51
File harbour-whatsapp-0.9.264-1.armv7hl.rpm9.48 MB15/08/2026 - 22:51
File harbour-whatsapp-0.9.264-1.aarch64.rpm9.32 MB15/08/2026 - 22:51
File harbour-whatsapp-0.9.272-1.i486.rpm9.76 MB20/08/2026 - 21:12
File harbour-whatsapp-0.9.272-1.armv7hl.rpm9.49 MB20/08/2026 - 21:12
File harbour-whatsapp-0.9.272-1.aarch64.rpm9.34 MB20/08/2026 - 21:12
File harbour-whatsapp-0.9.278-1.i486.rpm9.77 MB20/08/2026 - 23:29
File harbour-whatsapp-0.9.278-1.armv7hl.rpm9.5 MB20/08/2026 - 23:29
File harbour-whatsapp-0.9.278-1.aarch64.rpm9.34 MB20/08/2026 - 23:29
File harbour-whatsapp-0.9.279-1.i486.rpm9.77 MB22/08/2026 - 04:59
File harbour-whatsapp-0.9.279-1.armv7hl.rpm9.5 MB22/08/2026 - 04:59
File harbour-whatsapp-0.9.279-1.aarch64.rpm9.35 MB22/08/2026 - 04:59
Changelog: 

- whatsmeow updated to 2026-08-20 (6eefbff4), carrying proto v1045649367.
Deliberately not the newest commit: a day later whatsmeow raised its
minimum Go version to 1.26, and the toolchain here is 1.25. Taking the
commit just before that leaves the protocol update in place and the build
working, which is the point of the update; the Go bump can wait until the
toolchain moves. Dependencies unchanged, no API breakage, race detector
clean

Comments

rob_k's picture

Hey, you're faster than your shadow :) Yes, this works again!

aviarus's picture

Thanks. Glad to read

rob_k's picture

Latest version 0.9.90-1 crashes on my Xiii on Pispala 5.1.0.11

aviarus's picture

yes for me it didn't even start. it should be fixed now, if  not just tell me .

kempertom's picture

How to unarchive chats?

aviarus's picture

I thought i have to program again^^, but this is already implemented thankfully. Archived chats are not hidden — they move to the very bottom of the chat list, dimmed and marked "· archived". Scroll down to find them, then long-press the chat and choose "Unarchive" from the menu (the same long-press menu also has Archive, Pin and Mute). The state syncs to your other WhatsApp devices via app state, so unarchiving here unarchives everywhere.

kempertom's picture

It gets more and more perfect. Thank you !!!

rob_k's picture

Idea: add empty file .nomedia to Whatsapp folders, or the content will clutter the Gallery. I'm really happy that this app exists, AAS is now off by default and this saves battery! Thanks again!

aviarus's picture

It's a good suggestion, if media access is enabled you have the option to put .nomedia files for different media types

kempertom's picture

Sorry, but all permissions are granted. I did the process. But the mic doesn't turn into a timer and on the main page is a message saying: Recording failed ([Errno 13] no permission: 'gst-launch-1.0) grant the microphone permission in Settings and restsart the app
I did before and reststarted the app...even SFOS>Settings>Apps>whatsapp is showing that it has mic permission .... Very strange.
Your App is a micrometer away from being perfect!!!

aviarus's picture

Okay it could be that gstreamer1.0-tools wasn't installed. I added it as a dependency and it should install now if you update

kempertom's picture

Permissions are granted, but returning to main screen a message is shown, that says that it has no permission

kempertom's picture

How to record a voice note?

kempertom's picture

I just turned my Motorola G7 Power into my daily driver with SFOS - without Android - because of your work. Only thing missing are Voicenotes

rdomschk's picture

Hello, it works perfect. Thanks, Thanks, Thanks. The one problem is, I have to open all Chats separate to reset the counter. I have manny chats, maybe you can made later a menu point to set all chats at readed... But no pressure. A other question is, its possible to activat a notification at the evenscreen to see new messages. BR

aviarus's picture

You can activate notifications in settings now and Mark all as read is also available now per chat

rdomschk's picture

Hello - you are very diligent every day. Thanks for it. The pin function now works afte restart. One question, how can I see which chat had new messages. I miss a highlighting at the chat names or a othe sign. But no pressure it works perfect in the moment and I could switch off the AppSuport. 

aviarus's picture

Your wish is my command^^ i made a red counter with unread messages

rdomschk's picture

Hello, a big Thanks only 1 day later so many changes - now the first pairing work from desktop file and the new statuspage is also very nice. I have only problems with videos. I cannot open a video with the gallerie. I gave all right for contacts and media in Terminal but the gallery shows 0 byte for each video? What I make false? The contacts names the status header after the command. The pin function for chats lost after reopen the app but this is not so importand.

aviarus's picture

oh yes that could be it, did you close the app after the terminal commands and opened it again? the new  sailjail permissions only take effect when the app is launched again, otherwise the gallery has no read permissions in the sandbox, but if the app has write permissions to the gallery the gallery can just open it. i could implement  a video player in the app though, so people who don't want to give this permission  could also watch  a video. the pinning i will look into

aviarus's picture

I didn't test it yet so much with videos, i will look into it. It could be the media permissions for sailjail or something else. Thanks for pointing it out

rdomschk's picture

Hello - nice that you support your good work from last year! For the first pairing the user must start it via terminal "sailfish-support harbour-whatsapp" without this the pairing button not work. After it the app start perfect with the desktop icon. What I miss now is to see the status and a setting option for languages. It a good alternative to stopp the origianal WA service from ASS. Thanks and don't lose your joy of programing on this app. BR

rob_k's picture

It appears images in messages from before the pairing, are not shown. New stickers and images are shown properly. I like it!

rob_k's picture

Very interesting development! I just installed it, pairing works, list looks good. This is a chance for me not to have Android active all the time. Thanks!PS I see we don't have pictures yet, still very promising

aviarus's picture

I tried to implement what i think you meant, but if you specify it i can add it.

aviarus's picture

Okay thanks. What do you mean exactly? You cannot open Pictures sent to you or something else?

Manisak's picture

I'd rather do a matrix bridge. This one is a construction site. But the will counts.

aviarus's picture

Thanks! That's expected: history is only synced once, at pairing time, and versions before 0.4.9 dropped media messages during that import. WhatsApp doesn't re-send history, so media from chats imported with an older version can't be recovered retroactively. If you log out and pair again, the history sync runs with the new importer and old chats will show their media (tap to download). Everything received after the update works without re-pairing.

nkyst's picture

Perhaps a beginner's question, but what format should I use to 'pair' the account? I tried several ways to enter my phone numbet such as with or without + of country code etc. Or am I missing anything ?

aviarus's picture

with country code but without + and without 00

Pages