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).

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

Now we can keep testing

@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, 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.

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.

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

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.

@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?

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

I generated my own API ID/hash, but it didn't make a difference

The log doesn't tell me much:

[71623] live: start
[71623] live: refresh peers start
[71623] live: refresh peers done
[71623] live: session open start
[71623] live: session open FAIL
[71623] live: no auth -> login flow
[71623] live: run_window start
[71623] photo cache: scan done files=0 MB=0
[71623] window: RGB888 inline-photo replay active
[71623] window: double-buffer 820x560 depth 24
[71623] window: drag-and-drop enabled
[71623] window: setup complete
[71623] paint1: off-screen rendering start
[71623] login paint: clear
[71623] prim 1: fill 0,0 820x560
[71623] login paint: title+status
[71623] prim 2: text 354,232 14x0
[71623] prim 3: text 290,264 30x0
[71623] login paint: input box
[71623] prim 4: fill 270,284 280x24
[71623] login paint: footer
[71623] prim 5: text 306,328 26x0
[71623] login paint: done
[71623] paint1: blit start
[71623] paint1: blit done
[71623] window: first paint done
[71623] window: activating
[71623] window: opened
[71639] login: send_code start
[71640] login: send_code done

Thanks, that narrows things down a lot! The request left your Amiga fine and Telegram accepted it the only missing piece is the actual delivery of the code.

There's one big thing to rule out, and it's likely on my end, the app currently ships with shared api_id and api_hash keys. When too many people use the same key, Telegram throttles it; the client sees a normal "code sent" status, but nothing ever reaches your phone (which would explain why it suddenly resolved on its own last time).

Could you try with your own credentials?

Generate a pair at my.telegram.org (under API development tools).
Add them to data/telegram-api.txt (first line: api_id, second line: api_hash).
Delete telegram-auth.bin and data/phone-code-hash.txt, then try logging in again.
If it works with your own keys, we have our answer and I'll sort out a proper fix. If it still doesn't, launch with --gui-live-debug and send over PROGDIR:tg-gui-debug.log.
(I'm also adding the delivery method and digit count to the log in the next build, so we won't need to rely on screenshots anymore!)

Telegram Amiga 0.0.92 alpha - AROS x86_64

I've already tried what you're suggesting.

After entering my phone number, the screen shown in the attached screenshot appears.
I have the Telegram app open on my phone (I also have the Telegram service chat).

Thanks so much for your patience, and sorry for the runaround!

To help narrow this down, quick question: what exactly does your screen say when you request the code? It should tell you whether it sent it via SMS, a phone call, or inside Telegram.
(Heads up: if it says "in Telegram", look for it in the official Telegram service chat with the blue checkmark on a device where you're already logged in — just make sure that chat isn't muted or tucked away in your Archived folder).

In the meantime, it's worth trying this:

Delete telegram-auth.bin and data/phone-code-hash.txt, then restart the client.
Request the code once and wait a couple of minutes without spamming it (Telegram rate-limits quickly).
Just so you know, right now the client shows the same error whether a code is wrong or just expired (my bad, working on a fix!). If none of that helps, let me know your version and build (i386 or x86_64) and we'll sort it out together.

I wanted to test the new version, but I'm having trouble receiving the code for the app again. TelegramAmiga displays a message saying that the code has been sent and is waiting for me to enter the 5-digit code, but nothing is showing up on the app on my phone.

Now I'm wondering - is Telegram generally so unreliable that it doesn't deliver these codes, or is there perhaps an issue with the AROS-side app? Is there any way we can debug this?

Telegram Amiga 0.0.9 alpha is out for AROS (i386/x86_64).

Photos have finally arrived: inline rendering with progressive decode, built-in viewer, native JPEG sending and message forwarding to other chats.

https://androidla...orwarding/

The new Telegram Amiga alpha 0.0.8 release is now available.

The main additions are non-blocking file transfers, multi-datacenter downloads and Workbench drag-and-drop upload. The client remains usable while a file is being transferred: you can keep chatting, switch conversations and receive messages.

There is much more as well, including local chat search, a configurable download drawer and clickable URLs.

https://androidla...-blocking/

It's finally working After logging in on my home computer, the code finally arrived on my phone. Maybe the missing code was just a temporary issue with Telegram? I'll try to confirm that tomorrow. I'll keep testing it and let you know if I run into any problems.

Good news: found it and fixed it, thanks to your hint about deleting telegram-auth.bin, that was the decisive clue. The client was tearing down a shared network library while other connections were still using it, which is exactly what happens on a relaunch after an aborted login. Fix will be in 0.0.7, on all platforms.

Your AROS versions are fine by the way, the stable 20250418 is the same base I use as reference for the x86_64 build, so no need to change anything.

About the login code: after you enter the phone number, does it say "Login code sent"? If yes, Telegram accepted the request and the code should appear in your phone app, in the service chat called "Telegram" (not as SMS). Also note Telegram won't resend a new code for a few minutes if one is still pending, so quick retries can look like nothing arrives.

Unfortunately, the code isn't coming through via SMS or in the app (which I have running on my phone).

I noticed that I have to delete the telegram-auth.bin file; then I can restart it without it crashing.

As for the x86_64 version, I tested it on the latest stable release (20250418-1 + U3) and on the latest nightly build.

If there’s another specific version that works, please provide a download link. This app looks really promising

Hi, thanks for testing! Three quick things:

The login code goes to your Telegram app on an already-logged-in device (check the chat called "Telegram" on your phone), not by SMS unless you have no other session. Did you check there?
Which AROS exactly? The x86_64 build is picky: it needs a trunk-matched AROS and won't run properly on AROS One v0.38 (different kickstart), crashes included. On AROS One or hosted setups the aros-i386 ABIv0 package is the safe one.
For the crash on relaunch: delete data/phone-code-hash.txt before retrying and tell me if it still crashes. If you can capture the crash text or Guru number, even better.