6223
This group is dedicated to testing and bug reporting Telegram X for Android. English only. Rules: telegra.ph/TGX-rules-07-02 Beta: play.google.com/apps/testing/org.thunderdog.challegram Channel: @tgx_android Themes: @tgx_perfection APK: @tgx_log
تيليجرام X 0.28.3.1785-arm64-v8a (4ac597ca)
TDLib: 1.8.60 (tdlib/td@0da5c72)
androidx-media3: 1.9.0 [common, decoder.opus, decoder.vpx, decoder.flac, decoder.ffmpeg]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 13 (33)
Device: realme realme RMX3195 (RMX3195_11_F.25)
Screen: 1448x720 (density: 2.0, fps: 60.0)
Build: `realme/RMX3195/RMX3195:13/SP1A.210812.016/R.1ab9c02-18618:user/release-keys`
Package: org.thunderdog.challegram
Locale: ar_EG (app: ar)
Installer: Google Play
Initiator: Google Play
APK Fingerprint: `66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68`
Total: 1
Now: ٢٥/٧/٢٠٢٦, ١:٣٨ م
Date: ٢٥/٧/٢٠٢٦, ١:٣٣ م
Step: channel
og.w8: java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist
Stack trace:
java.lang.RuntimeException
at og.y8.d(SourceFile:175)
at og.y8.c(SourceFile:81)
at og.y8.<init>(SourceFile:41)
at og.e9.u(SourceFile:87)
at og.b9.isEmpty(SourceFile:23)
at og.g9.g(SourceFile:2)
at og.b9.d(SourceFile:77)
at og.d9.d(SourceFile:310)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at sf.h.run(SourceFile:32)
=== Cause #1===
java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3044)
at android.os.Parcel.createException(Parcel.java:3024)
at android.os.Parcel.readException(Parcel.java:3007)
at android.os.Parcel.readException(Parcel.java:2949)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:3497)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:948)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:936)
at og.y8.d(SourceFile:150)
at og.y8.c(SourceFile:81)
at og.y8.<init>(SourceFile:41)
at og.e9.u(SourceFile:87)
at og.b9.isEmpty(SourceFile:23)
at og.g9.g(SourceFile:2)
at og.b9.d(SourceFile:77)
at og.d9.d(SourceFile:310)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:957)
at com.android.server.notification.NotificationManagerService$10.createNotificationChannelsImpl(NotificationManagerService.java:4009)
at com.android.server.notification.NotificationManagerService$10.createNotificationChannels(NotificationManagerService.java:4054)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1585)
at android.os.Binder.execTransactInternal(Binder.java:1326)
Stack trace:
java.lang.RuntimeException
Hi,
I'm truly grateful for all the effort you've put into Telegram X over the years. I've been using it since 2018, and I absolutely love everything about this app.
I especially want to thank the wonderful and kind developer for creating and maintaining such an amazing project.
I just wanted to let you know that, after updating to the latest version (1796) for ARM64 on my S26, the app consistently crashes exactly three seconds after opening, every single time. Since updating, I haven't been able to use it at all.
Thank you again for all your hard work, and I hope this issue can be fixed soon.
You are wrong again – in-app login codes can be received in any Telegram client.
Читать полностью…
if you don't want to use the solution given in this chat which is the official tgx support chat, maybe you should consider not using tgx at all
Читать полностью…
Telegram X hasn't been working for a long time to register new users. SMS messages aren't coming through. It says it was sent to another Telegram, even though the phone number is new. When can I expect it to work again?
Читать полностью…
No, you still are doing it wrong by ask the fix in group, when the channel already said to PM the admins (with a template in above message) instead:
/channel/tgx_dev/41717
Also notice "the only account you have" part. It's written for some reason I guess?
Technically, devs need error logs to fix most problems. You either provide the log (which might not exist if TGX don't save log before login...) or provide the infomation they need in PM. Few can be done if you only report the behavior.
And this can very well be a tdlib problem, which Telegram X depend on but has little control from. TGX author might report that to tdlib devs and got the fix in some time, during which everything you post here would be meaningless.
Hello. I encountered a problem with registration, I enter my phone number, and the confirmation code says that it goes to the Telegram application, although I do not have an account on this number, how to solve this? Please tell me
Читать полностью…
/report Please ban these Telegram account sellers along with all their accounts, who report registration problems like that's the only thing TGX does. Most users (1) don't even know Telegram X when they register, (2) don't even have an account to share in this group when register falled, and (3) would just use other official clients for registration. Oh, normal account sellers also just go use other clients, instead of show up in official support groups as a stupid abuser and get banned.
One even has linked a "TELEGRAM ACCOUNTS FOR SALE" channel on its profile. Check that with updated non-TGX clients. Can't ask for this elsewhere but, as this is a official group, I think you may ask Telegram abuse department to look into them if you are not sure.
It was working just a few weeks ago, I'm interested in solving the problem, not in advice I already know.
Читать полностью…
You need to make account on official tg app
Then login on tgx
Telegram X hasn't been working for a long time to register new users. SMS messages aren't coming through. It says it was sent to another Telegram, even though the phone number is new. When can I expect it to work again?
Читать полностью…
تيليجرام X 0.28.3.1785-arm64-v8a (4ac597ca)
TDLib: 1.8.60 (tdlib/td@0da5c72)
androidx-media3: 1.9.0 [common, decoder.opus, decoder.vpx, decoder.flac, decoder.ffmpeg]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 15 (35)
Device: HONOR HONOR ALI-NX1 (ALI-N21 9.0.0.211(C185E14R3P1))
Screen: 2652x1200 (density: 3.25, fps: 120.00001)
Build: `HONOR/ALI-NX1/HNALI-Q:15/HONORALI-N21/9.0.0.211C185E14R3P1:user/release-keys`
Package: org.thunderdog.challegram
Locale: ar_SY_#u-nu-latn (app: ar)
Installer: Google Play
Initiator: Google Play
APK Fingerprint: `66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68`
Total: 1
Now: 24/7/2026، 10:00 ص
Date: 16/7/2026، 7:20 م
Step: channel
og.w8: java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist
Stack trace:
java.lang.RuntimeException
at og.y8.d(SourceFile:175)
at og.y8.c(SourceFile:67)
at og.y8.<init>(SourceFile:41)
at og.e9.u(SourceFile:87)
at og.b9.isEmpty(SourceFile:23)
at og.b9.d(SourceFile:84)
at og.d9.d(SourceFile:310)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:114)
at android.os.Looper.loopOnce(Looper.java:237)
at android.os.Looper.loop(Looper.java:325)
at sf.h.run(SourceFile:32)
=== Cause #1===
java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3265)
at android.os.Parcel.createException(Parcel.java:3245)
at android.os.Parcel.readException(Parcel.java:3228)
at android.os.Parcel.readException(Parcel.java:3170)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:3727)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1047)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:1033)
at og.y8.d(SourceFile:150)
at og.y8.c(SourceFile:67)
at og.y8.<init>(SourceFile:41)
at og.e9.u(SourceFile:87)
at og.b9.isEmpty(SourceFile:23)
at og.b9.d(SourceFile:84)
at og.d9.d(SourceFile:310)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:114)
at android.os.Looper.loopOnce(Looper.java:237)
at android.os.Looper.loop(Looper.java:325)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:1239)
at com.android.server.notification.NotificationManagerService$12.createNotificationChannelsImpl(NotificationManagerService.java:4468)
at com.android.server.notification.NotificationManagerService$12.createNotificationChannels(NotificationManagerService.java:4514)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1674)
at android.os.Binder.execTransactInternal(Binder.java:1534)
callee: null 2603/4120
Stack trace:
java.lang.RuntimeException
What's going on with my telegram notifications
Читать полностью…
I'm not misguided, I just don't know the deep technical side, which are two different things. I'm commenting from the perspective of a regular user talking to another regular user. I look at this from the outside and see a massive wave of complaints from everyday users like me, though I might be wrong about them being just regular users and not spammers. I admit I know nothing about bot farms or spammers.
Читать полностью…
Yeah, I agree the screenshot is from a different app. But my point is about the logic itself. Even if someone manages to register an account directly in Telegram X via SMS, what’s next? For any future login on a new device, the code will only go inside the app, not through SMS. So they’ll end up needing the official Telegram app anyway just to receive those codes. Why not just create the account in the official app from the start? They’ll have to use it sooner or later anyway.
Читать полностью…
Sorry
From February 18, 2023, new Telegram authorization rules have come into effect, according to which the alternative clients users can receive the SMS code only from the official Telegram client. Please install Telegram app and log into your account there if you need the SMS code, after which you can re-request the code in *** (it will come in the Telegram service chat).
Close
Open Telegram👌
Good evening. I encountered a problem that I can't register an account through TelegramX, the code goes to some device where there is Telegram, although there are no profiles and devices on this SIM card!! I saw that they wrote about registering in the official TG, and then transferring to TelegramX, but this option doesn't suit me, don't ask why. Please tell me if there is any work being done to repair your application?
Читать полностью…
I dumped everything that was needed from me in the admin's private messages. I write in the chat about the problem, because I don't see any specifics. and when I constantly remind them about it, they usually take it more seriously, maybe you don't agree with this, but for me it's completely normal and right
Читать полностью…
Read the chat... /channel/tgandroidtests/295722
Читать полностью…
Whether people sell Telegram accounts or not, you shouldn't worry. You write, ban sellers and those who report a problem with registration, that is, it's better not to know that there is such a significant problem in the application, it's better not to write such things in chats that are made for this, you are a brilliant person (no). I write and will write about this problem until it is solved, and I consider it correct. And I recommend that you don't go where you are not asked. There is a problem, and it needs to be solved, and you only spam the chat.
Читать полностью…
Can we please get mini app support here on tgx! 🙏
Читать полностью…
I have the same problem and even the Telegram login code cannot be sent. It seems like it's just a dummy button, only for appearance
Читать полностью…
Greetings. For more than a week, I and other users have been concerned about a big global problem with Telegram X, namely the problem with registering accounts when people go to a Telegram account, but accounts are not registered to these numbers. I want to hear specifics when this will be resolved. I am attaching a screenshot below, use the translator
Читать полностью…
Telegram X 0.28.3.1785-armeabi-v7a (4ac597ca)
TDLib: 1.8.60 (tdlib/td@0da5c72)
androidx-media3: 1.9.0 [common, decoder.opus, decoder.vpx, decoder.flac, decoder.ffmpeg]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 14 (34)
Device: INFINIX Infinix Infinix X6525D (X6525D-F069MIfIgIh-UGo-OP-S2-260410V1263)
Screen: 1532x720 (density: 2.0, fps: 60.0)
Build: `Infinix/X6525D-OP-S2/Infinix-X6525D:14/UP1A.231005.007/260410V1263:user/release-keys`
Package: org.thunderdog.challegram
Locale: en_US (app: en)
Installer: Google Play
Initiator: Google Play
APK Fingerprint: `66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68`
Total: 1
Now: 7/24/26, 11:31 AM
Date: 7/24/26, 10:09 AM
Step: channel
og.w8: java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist
Stack trace:
java.lang.RuntimeException
at og.y8.d(SourceFile:175)
at og.y8.c(SourceFile:74)
at og.y8.<init>(SourceFile:41)
at og.e9.u(SourceFile:87)
at og.b9.isEmpty(SourceFile:23)
at og.b9.d(SourceFile:84)
at og.d9.d(SourceFile:310)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at sf.h.run(SourceFile:32)
=== Cause #1===
java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3082)
at android.os.Parcel.createException(Parcel.java:3062)
at android.os.Parcel.readException(Parcel.java:3045)
at android.os.Parcel.readException(Parcel.java:2987)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:3613)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1001)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:989)
at og.y8.d(SourceFile:150)
at og.y8.c(SourceFile:74)
at og.y8.<init>(SourceFile:41)
at og.e9.u(SourceFile:87)
at og.b9.isEmpty(SourceFile:23)
at og.b9.d(SourceFile:84)
at og.d9.d(SourceFile:310)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:294)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:987)
at com.android.server.notification.NotificationManagerService$11.createNotificationChannelsImpl(NotificationManagerService.java:4029)
at com.android.server.notification.NotificationManagerService$11.createNotificationChannels(NotificationManagerService.java:4075)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1640)
at android.os.Binder.execTransactInternal(Binder.java:1339)
Stack trace:
java.lang.RuntimeException
Nobody knows as long as you don't share error logs
Читать полностью…