Telegram Desktop for Raspberry Pi

[Professor]

Hi there, guys.
My endeavours had finally paid off, and I managed to bring Telegram Desktop build to ARM architecture.
We already had telegram-cli and telegram-purple plugin for Pidgin, but I believe it's much more convenient to just use native official client. So, you're welcome to use it!
You can get it here https://drive.google.com/open?id=0BzaLG ... VJzMEt3OXc.

P.S. You gotta disable automatic updates in the settings, otherwise you'll end up with updated x86 version instead of one for ARM.

[asavah]

No way I personally will install binaries which some random guy posted on the forums.
Provide link to sourcecode or be gone.

[Professor]

No way I personally will install binaries which some random guy posted on the forums.
Provide link to sourcecode or be gone.

Oh, come on. If it's not about binaries, I'd not even post. Since it's a headache to compile it, I provide binaries. Seriously, who does ever need to put some malware on raspberries?

GitHub repo https://github.com/telegramdesktop/tdesktop, is it your relief?

[mfa298]

No way I personally will install binaries which some random guy posted on the forums.
Provide link to sourcecode or be gone.

Oh, come on. If it's not about binaries, I'd not even post. Since it's a headache to compile it, I provide binaries. Seriously, who does ever need to put some malware on raspberries?

GitHub repo https://github.com/telegramdesktop/tdesktop, is it your relief?

I've seen plenty of scammers who's first line is "You can trust me, this isn't a scam" that doesn't mean it's true. We don't know who you are or even where you are so there's not much to trust. Having the source code and instructions to use it can go a long way to providing that trust.

And yes, there are Raspberry Pi's out there with malware on them (usually through being poorly configured), but the aim from knowledgeable people should be about making people more security conscious (change the default password, don't install software from unknown sources etc.) rather than getting them to just install stuff they found on a forum.

[tpylkko]

Telegram has a very functional web version.

[Professor]

No way I personally will install binaries which some random guy posted on the forums.
Provide link to sourcecode or be gone.

Oh, come on. If it's not about binaries, I'd not even post. Since it's a headache to compile it, I provide binaries. Seriously, who does ever need to put some malware on raspberries?

GitHub repo https://github.com/telegramdesktop/tdesktop, is it your relief?

I've seen plenty of scammers who's first line is "You can trust me, this isn't a scam" that doesn't mean it's true. We don't know who you are or even where you are so there's not much to trust. Having the source code and instructions to use it can go a long way to providing that trust.

And yes, there are Raspberry Pi's out there with malware on them (usually through being poorly configured), but the aim from knowledgeable people should be about making people more security conscious (change the default password, don't install software from unknown sources etc.) rather than getting them to just install stuff they found on a forum.

Well, I was using the gyp/qmake guide to build. If you follow the instructions you'll meet some troubles with dependencies or configuration scripts. If you solve them you'll end up with as same binaries as mine ones. Since it's a pain in the butt to mess with it I just posted already compiled binaries. Calm your paranoia, I have no interest in your little green PCB. If you're not convinced enough, do a backup, download binaries, and you will see - it's just a client.

About web version. If you run it in chromium you will see how much it eats the RAM. Native client uses just about 70-90 MB, it's not that much as 200-300 in web version.

[mfa298]

Well, I was using the gyp/qmake guide to build. If you follow the instructions you'll meet some troubles with dependencies or configuration scripts. If you solve them you'll end up with as same binaries as mine ones. Since it's a pain in the butt to mess with it I just posted already compiled binaries. Calm your paranoia, I have no interest in your little green PCB. If you're not convinced enough, do a backup, download binaries, and you will see - it's just a client.

About web version. If you run it in chromium you will see how much it eats the RAM. Native client uses just about 70-90 MB, it's not that much as 200-300 in web version.

It's of little concern to me, I don't run a gui on my Pi's. I can't even get it on my Pi as trying that link in the only web client on my Pi (wget) just gives a bunch of html and javascript.

However the Pi is about learning and there are two ways you could have helped with that:
1) Document what you did, what issues you found and how you worked around them. Often that's the interesting part of the exercise and can help others learn how to do similar things themselves.
2) Teaching others good security practices, i.e. how to keep their pi's secure (one of the first steps is how to determine if a download is safe or not)

[Professor]

It's of little concern to me, I don't run a gui on my Pi's. I can't even get it on my Pi as trying that link in the only web client on my Pi (wget) just gives a bunch of html and javascript.

However the Pi is about learning and there are two ways you could have helped with that:
1) Document what you did, what issues you found and how you worked around them. Often that's the interesting part of the exercise and can help others learn how to do similar things themselves.
2) Teaching others good security practices, i.e. how to keep their pi's secure (one of the first steps is how to determine if a download is safe or not)

My goal was to build a thing and to put it somewhere where people can easily get it. Trust me, it's not nearly a interesting process. More about fixing undefined references than learning something, so if people wish to use my work, they will. If don't, they won't.

[juppiter89]

Thank you, it works great, except for one thing: it crashes on GIF or video play. I debugged the trouble, I think it's related to FFMPEG Neon assembly routines, maybe disabling them the trouble could be resolved...

Btw, a guide on how to compile Telegram for arm would be nice

[juppiter89]

Well, I managed to solve the crash hacking the binary hex code (God bless IDA disassembler )
Use an hex editor (such as Bless), search for hexadecimal code cbf80430584609 and edit 5846 in 00bf.

I hope that is of help to someone

[rainer.brito]

Sorry for necro this post, but I would like to say "THANKS! IS STILL WORKS GREAT!"

The binaries are very nice, really!
How can I update the app?

(It works with much less ram than via Chromium)

[rainer.brito]

Just to answer my own question:

The Debian armhf version is working great! (stretch backports)
Quite easy to install!

Just downlad the .deb and the tb voip.deb, install and it's working!

[sevengames7]

Hi there, guys.
My endeavours had finally paid off, and I managed to bring Telegram Desktop build to ARM architecture.
We already had telegram-cli and telegram-purple plugin for Pidgin, but I believe it's much more convenient to just use native official client. So, you're welcome to use it!
You can get it here https://drive.google.com/open?id=0BzaLG ... VJzMEt3OXc.

P.S. You gotta disable automatic updates in the settings, otherwise you'll end up with updated x86 version instead of one for ARM.

oh thanks... but... but... how can i update it?
this version is a bit limited

[Taxman]

Telegram-desktop from debian armhf can work in Raspbian as well.
My way:

Code: Select all

sudo apt install -y libavcodec-extra57 libavformat57 libavutil55 libminizip1 libminizip1 \
libasyncns0 libdouble-conversion1 libflac8 libgles2-mesa libglew2.0 libglu1-mesa libjpeg8 \
libmng1 libopenal-data libopenal1 libpcre16-3 libpulse0 libqt5core5a libqt5dbus5 libqt5gui5 \
libqt5network5 libqt5svg5 libqt5widgets5 libsndfile1 libsndio6.1 libswscale4 libwebpdemux2 \
libxcb-icccm4 libxcb-keysyms1 libxcb-randr0 libxcb-render-util0 libxcb-xinerama0 libxcb-xkb1 \
libxkbcommon-x11-0 libxkbcommon0 mesa-utils qt5-gtk-platformtheme qt5-image-formats-plugins \
qttranslations5-l10n

Then you need two files from debian:

Code: Select all

wget http://ftp.ru.debian.org/debian/pool/main/t/telegram-desktop/telegram-desktop_1.1.23-1~bpo9+1_armhf.deb
wget http://ftp.ru.debian.org/debian/pool/main/libt/libtgvoip/libtgvoip1.0_1.0~git20170704.445433f-4~bpo9+1_armhf.deb

And at last:

Code: Select all

sudo dpkg -i libtgvoip1.0_*_armhf.deb
sudo dpkg -i telegram-desktop_*_armhf.deb 

However versions of packages will vary, so you must check the debian repository
http://ftp.debian.org/debian/pool/main/libt/libtgvoip/
and
http://ftp.debian.org/debian/pool/main/ ... m-desktop/

Experience had shown, that version higher than 1.1.23 doesn't work in Raspbian Stretch, cause it requies newer libraries.

[tigernero]

By terminal

1) sudo apt install snapd
2) sudo snap install telegram-desktop
3) telegram-desktop

See you

[Thinkcat]

What if I want to avoid Snap at all costs and run a newer Telegram Desktop than 1.5.11? Currently running Buster on a Pi4.

Are there newer unofficial packages somewhere?

Is it difficult to learn how to construct a package?

Is it easy to compile the newest version?

Is there some sort of testing or unstable repository I could borrow from?

I don't understand why are people so against resurrecting dead threads? What should they do instead? Start a new thread about exactly the same thing? I don't like Discourse that much, but at least there you clearly see when the discussion has been dormant for a while.

[mahjongg]

I don't understand why are people so against resurrecting dead threads? What should they do instead? Start a new thread about exactly the same thing? I don't like Discourse that much, but at least there you clearly see when the discussion has been dormant for a while.

re-opening an ancient thread means that google will direct more people to that thread, and if the stuff in that thread is obsolete, and unsuitable for the current OS it will cause chaos, In that case its best to start a new thread, as the new content is NOT about "exactly the same".
in this case that reason for starting anew isn't applicable, but do know that readers are less likely to respond to threads that already have many answers.

[Moonmarch]

What is stopping people from installing Telegram Desktop using the repository? Install Telegram Desktop using the command in the terminal:

Code: Select all

sudo apt install telegram-desktop

I have not tested out Telegram, I don't use instant messaging software. I know about software, doesn't mean I use all kinds of software. If you are unable to use the Telegram program, consider using a different instant messaging program. There are web browser versions of instant messaging programs or social media websites. I did find instructions on the Telegram Desktop GitHub website that will show you how to compile Telegram. Here are the compiling instructions for the Telegram program:

tdesktop/docs/building-cmake.md - GitHub
https://github.com/telegramdesktop/tdes ... g-cmake.md