A friend is having problems with his kids home, all needing their own devices for zoom classes. I have an extra Raspberry Pi 4 that I could give him, but unfortunately zoom does not run on boards based on ARM chips. The Raspberry Pi is a cheap computer board and the Raspberry Pi 4 works quite well as a desktop system, capable of running multiple monitors with 4k HDMI. Would it be possible to get a Debian package built for ARM?
Hi @tonylhansen, I definitely see the use case and wish we could provide this; however, we have to prioritize client and SDK engineering resources on other efforts at this time.
Thank you for replying, @michael.zoom
I figured as much, but wanted to put this out there in case any of your engineers found some free time to do a recompile. Or at least got it into your queue of feature requests.
Thanks @tonylhansen, for any thoughts or feedback, please do submit at https://zoom.us/feed. While we might not be immediately able to jump on this, we always look for new ideas
I would love to see an RPi4 build as that is my main desktop computer. If you can manage an RPi4 build, how about a build for another ARM CPU, the Rockchip RK3399 as used in the PineBook Pro and other SBCs?
Another request for a Raspberry Pi4 build as well - weāre a hospital system who have been testing these devices as thin-clients for VDI and to have a Zoom client would be key for us to deploy en masse.
Thereās a bunch of people on the Raspberry Pi forums who also want a RPI-compatible Zoom client.
Currently their only option is to use the join.zoom website. Unfortunately, itās extremely laggy, and missing a lot of features.
A much better alternative would be the Chromebook App. After all, Raspberry Pies ship with the Chromium browser, and you can install Apps and Extensions.
Many users, including me, have tried using the Chromebook app. For some reason, attempting to login fails with the āLogin time outā error.
Also, when trying to join a meeting, the āConnectingā¦ā spinner shows indefinitely. It never connects.
Weāre so close! A nearly-compatible app has already been developed, and it almost works.
Almost. But why does it never connect?
If that NaCl code is removed or made compatible with armhf, I fully expect the Chromebook App to work flawlessly.
IMHO, fixing the Chromebook App would take relatively little effort, compared to the alternatives like an armhf DEB package.
Also IMHO, fixing the Chromebook App is entirely worth the effort. Raspberry Pies are used by many school students, low-income families, and others who desperately need to stay in touch with their loved ones. With over 30 million devices affected, Iād say this is probably the most worthwhile āFeature Requestā ever made.
Iām going to āthirdā the above post concerning Raspberry Pi support.
My partner is an educator and her district requires using Zoom to meet with students. For reasons not relevant to the discussion, she uses a Raspberry Pi (recently upgraded from a Pi3 to a Pi4) as her home computer. To date she has been using a very restrictive and unstable arrangement of a myriad devices thatās far from ideal, extremely unreliable, and totally impractical.
The only way she can use Zoom on the Pi is through the web-based version in the browser; in her case, Chromium (Chrome). However, that method is unstable because the tab hosting the session crashes. That requires reloading the tab. Furthermore, on starting a session, there is substantial lag between the time everything loads, and when the āconnectā button becomes clickable (20-50 seconds). Itās one thing when youāre hosting and/or are setting up ahead of time, but quite another if the tab crashes mid-session.
Unfortunately, because of the school districtās Zoom requirement, she cannot use another platform that is not only stable, but also supported by the armhf and aarch64 architectures. Sheās kind-of stuck. Unspoken in all of this is that she is doing all of this with a combination of visual disabilities that makes everything even more difficult for her.
But back to the Raspberry Pi: āA bunch of peopleā¦who want a RPI-compatible Zoom clientā is just the tip of the iceberg. That merely refers to the people discussing it in the aforementioned Pi forums. Since its initial release, as many as 30 million Pi units have been sold worldwide as of December, 2019. This number, which keeps growing, should be another motivation for Zoom to produce a native Pi/armhf/aarch64 client. The aforementioned bunch of people are not the only ones who stand to benefit from it.
I have recently started using a Raspberry Pi 4 for watching lectures and for doing coursework. Zoom support for ARM32/ARM64 under Wayland would be greatly appreciated.
I have the same request as the others in this queue, a Raspberry Pi compatible version of Zoom. We have three sons and two of the three have Raspberry Pi 4 computers for school work. Microsoft Teams works on the Raspberry Pi, but Zoom seems to be plagued with issues on the ARM architecture. They would like to use Zoom to stay in contact with others.
While there isnāt a Zoom desktop client for Raspberry Pi, you can run the Zoom client application, or even host a meeting, directly in the browser.
Open your browser, navigate to join.zoom.us, and enter the meeting ID and password; if you have received an email invitation, you can click directly on the meeting request URL in the email.
Click on the āCancelā button when prompted to āOpen xdg-openā by Zoom
Then, when you get asked to āOpen xdg-open?ā in the system dialog that opens, click on āCancelā.
Next click on the āclick hereā link near the bottom of the page where it says āIf nothing prompts from browser, click here to launch the meetingā¦ā. Another āOpen xdg-open?ā system dialog will open, and you need to click on āCancelā again.
Then you should see a new āstart from your browserā link in really small font at the bottom of the page. Go ahead and click on the this link.
Your Zoom meeting should now start normally in your browser.
Yes, I am aware of this join.zoom option. (and addressed it in my earlier post)
However, everyone who has tried it has said that itās really laggy, even at a 2GHz overclock. (as of several weeks ago)
Edit: some people have recently said that the video is now a lot smoother playing, though Iāve not had a chance to test it again yet.