-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request] Support 32-bit Windows #1636
Comments
To be honest, it's not very high on our list. We have more people asking for support for different distributions of Linux. Our research indicates that the vast majority of Windows users are on 64bit installs at this point. Maybe you could tell me more about your situation? Find others in your situation? |
Backblaze claims only 4.3% of their Windows users run 32-bit versions of their software. Assuming it's the same for Signal, it doesn't seem worth bothering with it. As Scott said, I would prefer if they found a way of keeping their Flatpak up to date so that people won't be running ancient versions in a few months. |
I'm using 32bit Windows and wonder if it is really so much more work supporting 32bit Windows than some Linux distribution that has much less users. |
You are absolutely right that there are fewer Linux users than 32-bit Windows users. However, I'd say there are more Signal Linux users than Signal 32-bit users since Linux users are usually more tech sawy and Signal has always been a nerd program. As Scott said, they are getting more requests for a Flatpak than they are for a 32-bit Windows version. Maybe they will consider making one for 32-bit users if the interest is high when the Flatpak is out, so who knows? My last post here, don't want to spam Scott with emails. Feel free making a thread on the forum: |
I think you will lose less time developing a web-based solution like Whatsapp did, than developing 10 different OS versions. |
Firefox's hardware report (source) says that 18% of FireFox users are still on 32-bit operating systems. There's a small decline in number of 32-bit users each quarter, but 18% is still a sizeable portion of computer users. |
I tried to install Signal in ReactOS. It didn't worked. Because ReactOS doesn't have 64-bit support. |
A 32-bit client would be 100% compatible with 64-bit Windows, and would be universal. On a tiny app like this are there even any benefits to being 64-bit only? Microsoft highly recommends using 32-bit Office (on 64-bit machines), unless spreadsheets are so large they run into memory constraints. Only then is 64-bit advised. I use 32-bit clients whenever possible (VMs, etc) for speed and reduced memory footprint, and was utterly surprised when I found that Signal was 64-bit only. As of May 2018, Firefox shows 30%+ of users are running 32-bit Firefox , and 18%+ of users are on a 32-bit OS. (Both metrics exclude XP/Vista.) This is a sizable chunk to write off completely. |
@a-woolf In general, you should avoid 32bit builds because 64bit has a plentitude of benefits, not limited to:
A more complete list is at wikipedia. Signal-Desktop uses electron and thus is almost a full browser, not a small app. 32bit binaries would neither be faster (because they would use less registers and not cause significantly more cache misses), nor would the memory footprint increase by a noteworthy amount, since only pointers grow to the double of their size. |
But do we have any disadvantage? The 32bit client would run on any windows. |
I fully agree... kill a dozen birds with one stone. Go web-based as opposed to native apps. While most of my gear is x64, I do have a tiny Win10 32-bit tablet/hybrid I use for travel that I can no longer use Signal on. Major bummer. Web-based is definitely the way to go. I understand that there are security concerns with that... aka using a compromised or outdated browser... but that is the same for native apps... if the device is compromised or outdated, it poses increased risk. If you can't do web-based for some reason, at least do x86 for your main platform as mentioned above... then it will work on both x86 and x64 architectures. |
Nah... Web based things are slow and lack offline possibilities (in case you need to read something while disconnected). Telegram also has a native 32bit Windows app. Can't be too difficult if you can cross-compile the soure. |
I'd like to mention a case where it's become impossible to run Signal on new(ish) hardware. Some laptops and tablets, even though the hardware is 64bit capable, have shipped with 32bit Windows 10 due to limited eMMC capacity of 32GB and perhaps other reasons. So it has become impossible to run Signal on these types of devices (prob. what also Soldier4Life above has experienced). |
I hear you... it is definitely a trade-off between broad spectrum compatibility and features/performance. It seems like the simple solution would be to just use x86 based architecture for all of Windows Desktop... then it can run on both. Unless there is a specific reason not to do so, that I might be missing. |
I doubt I will be installing new copies of an operating system just to run an program that has been working for many years. At least let us use the old app and we can bear any security issues. |
I am incline to agree with MagentoUno, as long as the security issues are restricted merely to the 32bit machine, and not compromising the entire signal accounts on the contact list. |
I'm currently running Windows 7 32-bit and it's the only desktop PC I have. I use Signal on my phone because it has all the features I require. I am sure I am not alone in the idea that most users do not care about the architecture of the software, but whether or not they can use it on all of their devices to stay connected. If I had the skills, I would build a 32-bit release myself, but I do not. It would be a lot to a lot of people to be able to have this option. |
I just wanted to install Signal on my thin laptop, too - tiny ssd, <4gb ram so it's running Win32 OS. Alas, no can do. Bye bye Signal, back to good ol' workin' Telegram. Meh. |
Listen, I am a nerd too. I own a Google Pixel 3a and will only buy phones whose bootloaders may be unlocked. My home computer runs Linux Mint. However, I am at the mercy of my employer during weekdays. I have for years used Google Hangouts to message my wife because I can do so using the computer without having to alternate between my phone and my computer. As many of you know, Google Hangouts/Google Chat is a completely unsecured messaging system and the messages are infinitely stored on Google's servers for you to see. I would like to use Signal on my work Windows desktop computer, but it's running 32-bit Windows. This may not change for a few years when they replace the computer. So I may be a nerd and have updated phones and a computer. But my workplace is another story. Please make it a priority to have a 32-bit Windows version. If there is already a 64-bit Windows version, is it much more work to port it to a 32-bit Windows version? Is this really an uncommon request? If there is no 32-bit Windows version, I might want to switch to Whatsapp instead. Whatsapp is now owned by Facebook. I have never trusted Facebook and have not had a Facebook account for years. |
@midtempo you'd better switch to Riot.im if you want to stay with open source, this even has a federated server structure. Only downside is that you have to verify every device if you want to have encryption. But back to Signal: Does a 32 bit version need a lot of rework, or does it just need someone who is able to compile a 32bit version without having to change a lot? In that case it would be great to have the possibility for donating for certain features. |
I've switched to Wire by now, it's evolving to a very mature oss client (https://github.com/wireapp/wire) and of course has a 32bit version (https://wire.com/en/download) ... I'd still like to use Signal for my legacy contacts, but as supporting a broad userbase isn't Signal's priority, supporting Signal isn't mine either. |
ARM64 Windows 10 can run Win32 (x86) apps, but cannot run Win64 (x86-64) apps without recompiling. This reinforces the need for a Win32 build - universal compatibility, as requested here over 2 years ago. |
To add yet another use case, there's also a number of Intel Atom tablets out there (the 32-bit UEFI only ones, ie Clover Trail) which can only run 32-bit Windows 10. Some of us don't have the budget to replace these. And the above line of "Signal has always been a nerd program" is the wrong approach, and a little bit self-defeating - if you want to get things like Signal into the hands of more people and not just journalists and nerds, you need to make it more widely compatible. |
Tech nerd here using a Microsoft Surface Pro X with an arm64 cpu that can run x86 apps but not x64. Both arm64 or x86 builds would work for me, but neither are supported. VSCode just released arm64 support, here's their github issue: microsoft/vscode#33620 |
Just build the dang 32 bit version already. People have been asking for it for years now. |
Hi there. Thanks for mentioning purple-signal. I am the author of purple-signal. I want to access signal without a resource-hogging browser solution. Long-term goal is a fully-fledged signal integration in Pidgin (with Pidgin 3 – if it ever gets released – probably supporting audio and video conferencing, too) and chatty. However, with libsignal-service-java being moved and hidden within the Signal-Android sources, libsignal-protocol-c looking abandoned and libsignal-client not deemed ready for production, I am trying to hit an elusive target which turns out to be moving rather swiftly. I will not supply users with the native binaries libsignal-service-java is depending on, especially if the number of dependencies increases. Right now with dennisameling, we are in luck, but that may change any time. |
32 bit version when :( |
Great news! I was able to get Signal to boot on Windows 10 32-bit (in a VM): We at least need the following PRs to be merged before the Signal team could even consider 32-bit builds:
For cross-reference: issue for Windows ARM64 support: #3745 I'm working from this branch: https://github.com/dennisameling/Signal-Desktop/tree/windows-multi-arch-support ✅ All automated tests are passing after applying the PRs above: Test logsPS C:\Users\Admin\repos\signal-desktop> yarn test yarn run v1.22.10 $ yarn test-node && yarn test-electron $ electron-mocha --file test/setup-test-node.js --recursive test/app test/modules ts/test-node ts/test-both |
I welcome dennisameling's win32 builds of |
@scottnonnenberg-signal looks like some volunteers are making progress on building signal 32 bit for windows and judging by the number of comments and participants this is not really an insignificant number of 32 bit users. is there any plan to change this in your priority list and start working with @dennisameling to bring this into official release? there are lots of older hardware in the less developed areas that runs 32bit windows because there is no justification for a more resource hungry 64bit build on the same hardware. a 2010 HP desktop that originally was shipped with windows xp, now runs windows 10 LTSC 32bit (receives security updates until 2029!!!) very well, but cannot use 64bit apps. except for exposing hypervisor features into a kvm guest and passing through a pci domain into a kvm guest, I've never needed 64bits on a desktop machine. all 32bit variants of the browsers run faster than their 64bit parts without missing any web features. I understand you devs look forward into the future and the future is 64bit, but ask yourself, is this actually worth it? is it worth to leave the less developed areas/contries into the dark just because they can't afford hardware to run 64bit at decent speed? |
please, get rid of that xp. it was the absolute best windows microsoft ever made but now it is a big risk of getting ransomware. if your cpu platform is Wolfdale or newer, windows 10 ltsc 32bit runs fine and you get security updates until 2029. it can do video calling and social media without problems. it's quite a pain to upgrade (xp -> vista -> 7 -> 7 enterprise -> 10 ltsb 2015 -> 10 ltsc 2019) so consider a fresh install instead on next visit. move the OS to a SSD, add some ram if you have free dimm sockets, setup automatic updates, install an antivirus and you get a fast and automatic secure solution for your folks that doesn't need intensive maintenance until 2029! |
Here's a production build of Signal Desktop 5.2.0 arm64+ia32 (32-bit): https://github.com/dennisameling/Signal-Desktop/releases/tag/v5.2.0 I plan to update the production builds regularly until the Signal team does, but it also means that auto-updating is disabled for now. You can either subscribe to this issue or my fork to be notified when a new version becomes available 😊 |
[signalapp/Signal-Desktop] [Feature Request] Support 32-bit Windows (#1636)
Hello Dennis
Thank you for the 32bit signal.
I have missed signal on my PC for years now.
dennisameling on Monday, May 24, 2021, 6:31:41 AM, you wrote:
+++++ [snip] +++++
Here's a production build of Signal Desktop 5.2.0 arm64+ia32 (32-bit): https://github.com/dennisameling/Signal-Desktop/releases/tag/v5.2.0
I plan to update the production builds regularly until the Signal team does, but it also means that auto-updating is disabled for now. You can either subscribe to this issue or my fork to be notified when a new version becomes available 😊
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
+++++ [end snip] +++++
Regards
Bob Korbel
Adelaide, Australia
|
Yesterday evening I installed the 32 bit Signal Desktop on the most underpowered notebook I could find (Atom N570, 2 GB, Win 10). Et voilà, it worked! At one point it failed to open the settings dialog (showing a blue rectangle instead) and had to be stopped via Task Manager, but that may be due to the sparse hardware resources. Many thanks, Dennis, for the excellent work! |
@MagentaFocus thanks for the kind words and for the sponsorship! Really appreciate that! 😊 Thanks for testing @Septa9, I just tried in my 32-bit Windows 10 VM and was able to open the settings dialog there. But the VM has 4GB RAM available 😊 Do let me know if you come across any other problems! If you haven't seen it yet, you can now also download v5.3.0: https://github.com/dennisameling/Signal-Desktop/releases/tag/v5.3.0-multi-arch |
Some very exciting news - just released 5.4.0 with a bunch of optimizations! Auto-updates are enabled now through my custom server. So, you should automatically be notified when 5.5.0 becomes available at some point. Next to that, the app has been fully signed with a Code Signing Certificate, so over time you most likely won't get warnings from Windows Defender SmartScreen anymore 👍🏼 Large parts of the build process are now automated, but there's still quite some moving parts that I'd like to automate even more. Will work on that in the coming weeks, though with low prio now that we have a stable foundation. Do let me know if this release works for you - can't wait for you to see the auto-update mechanism in action when the next version comes out! Tested it locally and it works great 🎉 |
[signalapp/Signal-Desktop] [Feature Request] Support 32-bit Windows (#1636)
Hello Dennis
Signal 32 has been going fine. Thank you very much for this.
The previous and current release , get a red flag from "Zemana Antimalware "
I've white listed here.
dennisameling on Sunday, June 6, 2021, 6:50:47 AM, you wrote:
+++++ [snip] +++++
Some very exciting news - just released 5.4.0 with a bunch of optimizations! Auto-updates are enabled now through my custom server. So, you should automatically be notified when 5.5.0 becomes available at some point. Next to that, the app has been fully signed with a Code Signing Certificate, so over time you most likely won't get warnings from Windows Defender SmartScreen anymore ��
Large parts of the build process are now automated, but there's still quite some moving parts that I'd like to automate even more. Will work on that in the coming weeks, though with low prio now that we have a stable foundation.
Do let me know if this release works for you - can't wait for you to see the auto-update mechanism in action when the next version comes out! Tested it locally and it works great 🎉
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
+++++ [end snip] +++++
Regards
Bob Korbel
Adelaide, Australia
|
5.4.1 is out! https://github.com/dennisameling/Signal-Desktop/releases/tag/v5.4.1-multi-arch Users who are already on 5.4.0 will get an in-app notification that an update is ready 🚀 |
Hi Dennis, There was a small inconvenience when manually installing 5.4.0, but this probably had to be expected: I had to re-link the phone, thereby losing all the chats already stored in desktop Signal. However, your auto-update to 5.4.1 worked like a charm, Congratulations! |
@Septa9 Yes, that's expected indeed, since I use a different App ID now for Signal Unofficial, to not cause conflicts with the official Signal client. I think you can copy over the contents of |
Not worth the effort. I just reported this for the sake of completeness. |
...installed automatically, no issues so far. |
This is an automated message that version 5.7.1 is now live. Please note that it might take 1-2 hours for the binaries to be uploaded to the server. Release URL: https://github.com/dennisameling/Signal-Desktop/releases/tag/v5.7.1-multi-arch |
This is an automated message that version 5.8.0 is now live. Please note that it might take 1-2 hours for the binaries to be uploaded to the server. Release URL: https://github.com/dennisameling/Signal-Desktop/releases/tag/v5.8.0-multi-arch |
Just wanted to inform folks here that I'll have to stop supporting Signal 32-bit. Over the last few months, my main focus was to get Signal to work on Apple Silicon and Windows arm64. The main chunk of that work was to get their native dependencies like ringrtc and signal-client to build for other architectures than x64, which was the only architecture the Signal team supported back then. Though the Signal team merged my work on cross-compilation into their native dependencies, they were still only providing official x64 prebuilds for ringrtc and signal-client. It did mean, however, that I could start providing consistent prebuilds for non-x64 architectures like ia32 and arm64 by simply building them myself. For every single update the Signal team did to their native dependencies, I had to trigger a build of those for ia32, x64 and arm64, and update the commit ref in my fork to point to these prebuilds. Luckily GitHub Actions helped me a lot to automate large parts of that process (building ringrtc takes 1+ hour!), but it did require me to spend some time every release to kick off that process and incorporate it into my fork. That's between 30-40 times since May/June 2021! Not every Signal Desktop update included updates to its native dependencies, but many of them did. This is changing now. The Signal team introduced official Apple Silicon support in version 5.27.1, meaning they also started providing prebuilds for However, those official prebuilds are not available for 32-bit platforms. Next to that, usage of ia32/32-bit Windows is still steadily declining (market share of 0.4% at the time of writing), and Windows 11 is not even available for 32-bit systems. For the two reasons above, I can't justify the significant maintenance burden anymore of building the native dependencies just for ia32/32-bit, let alone testing whether Signal runs properly on that platform. If someone wants to take this on, I'm more than happy to explain how you can do it (including code signing, setting up your own update infrastructure, etc.), but I'll stop providing "my" builds for ia32/32-bit soon. I'll keep doing it for the coming two minor versions (5.34.0 and 5.35.0), but those will be the final releases. Thanks everyone for the great enthusiasm and support, really appreciate it! Again, if you are or know anyone who can and wants to take this on, it is certainly possible. I'll just be spending my energy on other open source work moving forward. 🙏🏼 |
Hi Dennis, it's a pity that you have so stop supporting Win32 signal, but I understand your reasons. Thanks a lot for all the work you've done in the past! |
Of course I normally run Signal on my 64 bit machines, but my CNC controller for Mach3 needs 32 bit Windows. It would be nice to have Signal on it so that I don't have to use my phone when I am in front of it. |
@dennisameling maybe you could find time to publish guide on building Signal for 32bit Windows? |
The desktop version for Windows only supports 64-bit Windows. Do you develop a version for 32-bit Windows in future?
The text was updated successfully, but these errors were encountered: