Download Free Whatsapp Desktop [PORTABLE]
Leida Haury
What I noticed though is, that when the desktop version crashed my phone still tried to connect to the macbook in terms of linked devices and I ended up having 4 connections from the same macbook pro so keep an eye out...
It worked for a bit but then it crashed again so I decided to use Opera's Whatsapp sidebar feature since the browser is open anyway. Works a treat and doesn't use as much CPU/resources as the app so depending on the browser you're using, I'd rather go for this option.
Yes, I have. The program window closes, but when you check the running processes, Whatsapp is still running. And if someone sends a message, it pops up... that is intentional I suppose, but an option to actually shut it all down is missing.
While that works with every other program, whatsapp desktop does not close completely with that shortcut, it only closes the window, four other processes stay open. It does however close as expected, if I do File -> Quit.
As far as I understand from my own programming with Qt, a "close event" should implement whatever is necessary to do when the window (through whatever means) is closed. And my assumption here is, that whatsapp-desktop doesn't have this implemented.
I agree and understand this. And it was also my assumption; after all, whatsapp-desktop may have been designed to stay open without a window, so that messages can be received even when the user decided he just doesn't want the window open.
I realized today that whatsapp-desktop actually stays open if you close the window via its "X" from the window, as in the X icon of the window bar. So this just confirms that the idea of the whatsapp-desktop developers was to keep whatsapp running in the background, so that you can receive messages even if the window is closed.
Yes. And this is precisely the problem you are concerned about in this thread. Ctrl-Q when bound by the client generally means "quit", and you've stated that when you use Whatsapp's Quit menu entry it does indeed fully shut down.
The calls features are only available in WhatsApp native Desktop app 64-bit(Which the official website show that only Mac and window native app for desktop are available ), not in WhatsApp Web,and unfortunately they haven't developed the native app for Linux. The one which we are installing and using from Ubuntu-Software is Web version. That's why the call feature is not available in that.
Signal is made with the help of the original WhatsApp-Developer and it is much better. You have better voice quality if you call someone, you have Video-call integrated in the desktop-App and everything what you have with the phone-App. You can send pictures with original quality, they will not be converted down if you do not want it.
I'm wondering if anyone has any advice on a recent problem. It seems one of the rules on my pi-hole rasperry is blocking the whatsapp desktop on several computers. They refuse to login anymore for the last two days. The smartphone apps (iOS) work fine, just on the mac it won't login. Any suggestion on what to unblock maybe?
We have blocked the Social Networking category for all colleagues but I would like to allow access to WhatsApp and LINE. Looking at WhatsApp I've added whatspp.com and whatsapp.net to our global allow destination list. Neither of those appear to be blocked and the website is reachable.
Regarding the desktop apps not working even after allowing them in App Discovery, it might be helpful to check if there are any other blocks listed in the activity search. Sometimes, certain features or functionalities of the apps might require additional permissions or configurations.
I trying to figure out how to use WhatsApp desktop on my Mac. Everything in the app is clearly labelled, but finding messages is a bit of a chore. Has anyone else had success with using VoiceOver with WhatsApp desktop?
A couple of months back, I was working on a project and all the collaborators were staying in touch via WhatsApp. As it is a fairly large group of about 80 people, lots of photos tend to get generated each day. Since I was working on my laptop, I decided to use the desktop application rather than the mobile app, as it was more convenient. We were required to complete a certain task, within a fairly short amount of time, so everybody was working full throttle at that moment. As the deadline was approaching, the number of photos in the WhatsApp group started to increase. Moreover, as the navigation in the desktop application was becoming difficult, I decided to switch to the android app.
To my surprise, absolutely none of the photos had been downloaded on the app. As per my knowledge, whatever auto-download settings are applied to the mobile app, are also followed by the desktop application. But that didn't happen.
I've checked all my settings and everything seems to be fine. All permissions have been granted. There is no data usage check applied. But still, the auto-download feature didn't work on my phone, while it did flawlessly on the desktop application.
After that incident, there have been several other instances wherein auto-download was only working on the desktop application, instead of working on both the desktop and mobile version of WhatsApp in tandem. This has begun to worry me a little, as it is affecting my work. Can anyone suggest any tips to fix this?
Zorin Lite 16.2 XFCE
My mum now needs WhatsApp voice calls on her laptop.
WhatsApp Web does not do voice calls. And therefore anything that's just a wrapper around WhatsApp Web, like all the Linux "desktop clients" WhatsDesk, WhatsApp-for-linux, Ferdi/Franz, Rambox etc cannot do voice calls either. (And 99.9% of what I find on the web about WhatsApp on Linux involves one of those web wrappers.)
So that leaves a few options that I'd like to get the forum users tips or experience on.
I had remembered seeing whatsapp on Opera and installed to check it out. I haven't used it in a while . Any browser can be a data miner depending on how it is used and set up. With the exception of Firefox most better known browsers are chromium based.
After losing time trying to understand whether or not I have/should use/can use/can learn PlayOnLinux, winetricks, wineprefixes etc to install the whatsapp-portable.exe I've downloaded, I say "f#$k it" and just right click on the .exe and click "Open with Install Windows Application".
Yay! A Windows installer wizard starts up. Looks like "Run anyway" was the right choice. I complete the installer's steps, and click "Finish" (leaving "Run Whatsapp Portable" unselected, as something I saw earlier in PlayOnLinux suggested avoiding launching app on finish).
Entire screen goes black for a bit. Eventually screens returns to as before, including the installer again waiting for me to click Finish.
I click it again, and the installer goes away, normal screen this time.
In Zorin menu (well, whiskermenu), I go to "Wine" and Whatsapp is not there. (WeChat, which I installed the same way, is there.) Whatsapp is not in "Internet" either, and is not found by a menu search.
In Nemo, I go to .wine/drive_c. I look in Program Files: not there. I look in Program Files (x86): not there either. Doh! I see portapps has created its own folder on drive_c top level, and inside that /whatsapp-portable.
There's a readme.md (nothing useful in it), a "whatsapp-portable.exe", changelog, portapp.json and a folder called "app". Looking in /app, more folders and "WhatsApp.exe". And in one of those folders, another "WhatsApp.exe".
OK, I'll try the whatsapp-portable.exe in /whatsapp-portable and see what happens.
I double-click on whatsapp-portable.exe and again I get the message with the headline "You can use WhatsApp on the web" and the two buttons at bottom: "Run anyway" and highlighted "Launch WhatsApp". (Before it was just "Launch", this time "Launch WhatsApp".)
I still don't know the difference between Run and Launch, but at least the Launch button this time mentions the name of the program I want to use. So I click "Launch WhatsApp".
And it does not launch WhatsApp. Instead it opens a new tab in Chrome. Heart sinks. WhatsApp Web page, QR code to scan. The same process I've already tried re every other WhatsApp "client" on Linux, and which never allows voice calls. I scan the QR code anyway (who knows? maybe this is just an initial step to get the actual whatsapp-portable running.) The QR code is accepted... and I'm in the regular WhatsApp Web page in Chrome. That's it. No way to make voice calls. All these steps and all those folders and files just to open a web page??? That can't be right.
I close the WhatsApp Web page in Chrome, and try double-clicking on the whatsapp-portable.exe but this time I choose "Run anyway".
New folders are created (/data and /log) but no program visible yet. Then a very long (Wine?) error message, headlined "A JavaScript error occurred in the main process." Then long gibberish and just an "OK" button at bottom. I click OK, the error message disappears. No WhatsApp. I open the Task Manager which shows two processes both called "winedevice.exe", and one "wineserver". But no WhatsApp.
I try again (double-click, "Run anyway"), this time keeping an eye on the task manager.
Six WhatsApp.exe processes appear in the task manager, then the same (I believe) error message as before. I click OK again. But the WhatsApp processes do not disappear. I can't see any WhatsApp window anywhere but apparently it's running. But how to actually see it and use it? Or if not, shut it down?
Oh, yes, sorry, now that I read again the original post I saw it, sorry. I checked more and found Ubuntu WhatsApp desktop app with call features, the last 2 messages there are quite interesting, they say about Signal and other ways to do voice calls (if you may like a similar application with voice calls in the meantime). It's better to try seeing if at least one of alternative apps/websites can do what you'd like rather than waiting for a certain feature to be added (if it's planned to be done or even considered at least), just to not wait and wait with no concrete results.
Schermata da 2022-12-17 22-14-561366768 126 KB