We already have a browser for Raspberry Pi; Telegram for aarch64 would be useful too.

@retrofaza Thank you, that test was a huge help! It ruled out the API key and led me straight to a bug on my side:
Telegram sometimes answers with "no code sent: this account needs a verified login email first". My client caught the response but had no message for it, falling back to the standard "enter code" prompt. That explains everything.

Here is a test build for AROS x86_64: https://drive.goo...sp=sharing

Drop the binary into your drawer (keep data/ as is).
Run from Shell:
TelegramAmiga --gui-live-debug data/telegram-peers.txt
Request the code once.
Check PROGDIR:tg-gui-debug.log for this new line right after the request:
login: sent code type 0x........, N digits
Just send me that single line and whatever the screen displays .
Note: If it turns out to be the email issue, simply add an email in an official Telegram app (Settings → Privacy and Security) and then try the Aros again.

@Bohun Thanks! Aarch64 is definitely on my roadmap.
Is the bohunamiga/telegram GitHub fork yours? I saw the September branch did you manage to build it, or did you put it on hold? If you've dropped it, I can take over the port once I set up AROS on ARM here.

Quick question, do you know if AROS aarch64 runs on a Raspberry Pi 400 with working networking? Which board and build are you currently running?

Log line:
[08982] login: sent code type 0x3dbb5986, 5 digits

First, I sent it using the default API ID/hash. Then I repeated the process using my own generated API ID/hash. In both cases, the “sent code type” is the same.

But the code for TelegramAmiga isn't coming to my phone.

BTW, when I log in to my.telegram.org, the codes arrive in my phone’s app immediately.

I don’t have any other active Telegram sessions besides the one on my phone.

@kaffeine
Yes, that’s my fork. Unfortunately, when I saw that SSL was required—which isn't available for aarch64 yet—I held off.

I’d definitely like to port it to AROS aarch64 later, since I believe ARM64 is the ideal architecture for modern Amiga-like systems.

Do you know whether AROS aarch64 currently has working network support on the Raspberry Pi 400? I own one and it would be my target hardware.

Yes, two users have confirmed that the RPi 400 works correctly. From my experience with the 3B+, I know that a problem arises with saving network settings if you select the option to start the network at boot. It is better not to check that box; instead, enter the appropriate commands in "User startup"—you can find them in the Raspberry Pi 3 thread.

@retrofaza Found it! The fix was on my side, though the change came from Telegram.

I reproduced it on my own account. Telegram silently stopped delivering codes because the client sent the language as "en" instead of a full locale like "en-US". This worked fine since release one, but Telegram recently changed how it handles this check on their end. Switching it to "en-US" fixed it instantly, the code arrived on my phone in seconds!

Here is a test build for AROS x86_64 with the fix: https://drive.goo...sp=sharing

Replace TelegramAmiga in your drawer (keep data/ as is).
Delete telegram-auth.bin and data/phone-code-hash.txt.
Launch it, request the code once, and give it a minute.
(Heads up: if you made lots of attempts today, Telegram might throttle you for a few hours. If it doesn't arrive right away, wait a bit rather than retrying repeatedly).

Thank you so much for sticking with this! Your reports led straight to the solution, and this fix will now roll out to all platforms in the next release.

Yes! That's it - it finally works! Thank you so much.

Now we can keep testing

I noticed that when you iconify an application and then restore it, the colors get messed up.

AROS x86_64. The desktop is in 24bpp. I checked this on Linux Hosted and on QEMU (X11 driver and VMware driver).