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
you have disabled notifications in android system settings
Читать полностью…
It no longer sends codes, especially the login code for Iran. It gives an error or won't let you in, or it fakes sending an email request and still doesn't send the code. Please check this.
Читать полностью…
Does allowing notifications permission change anything for you? (You can disable again after that, it's just to check if there's difference)
Читать полностью…
Do you have notifications turned off in permissions of telegram x?
Читать полностью…
Now I got the keyboard to not work anymore. Apparently it happens on private chats?
But it's constantly pinging the keyboard to open, thus it never opens properly
(I may send a recording of what happens exactly but currently I'm in the 1 hour cooldown)
Unexpected runtime error
Player release timed out.
Telegram X 客户端 0.28.10.1796-arm64-v8a (850771ae)
TDLib: 1.8.66 (tdlib/td@022d602)
androidx-media3: 1.10.1 [common, decoder.opus, decoder.vpx, decoder.flac, decoder.ffmpeg, exoplayer.hls, exoplayer, decoder, datasource, extractor]
tgcalls: TGX-Android/tgcalls@850771ae
Recaptcha: 18.9.2
WebRTC: TGX-Android/webrtc@850771ae
Android: 13 (33)
Device: OPPO OPPO PEGM10 (PEGM10_13.1.0.2101(CN01))
Screen: 2285x1080 (density: 3.0, fps: 60.000004)
Build: OPPO/PEGM10/OP4E59:13/TP1A.220905.001/R.1e3a263-1-2:user/release-keys
Package: org.thunderdog.challegram
Locale: en_US (app: zh)
Installer: com.android.packageinstaller
Initiator: com.android.packageinstaller
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68
Unexpected runtime error
Player release timed out.
=== Stack Trace Dump ===
Unexpected runtime error
or1: Unexpected runtime error
at xc1.h(SourceFile:23)
at i10.run(SourceFile:892)
at xz2.b(SourceFile:89)
at xz2.e(SourceFile:4)
at gs1.B(SourceFile:174)
at mo6.g(SourceFile:235)
at b93.s(SourceFile:29)
at gf3.b6(SourceFile:7)
at h74.b6(SourceFile:5)
at pn.onPause(SourceFile:86)
at org.thunderdog.challegram.MainActivity.onPause(SourceFile:1)
at android.app.Activity.performPause(Activity.java:8609)
at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1604)
at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:5400)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:5361)
at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:5308)
at android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:53)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2470)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at android.app.ActivityThread.main(ActivityThread.java:8423)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)
Caused by: qs1: Player release timed out.
at xc1.h(SourceFile:15)
... 27 more
=== Cause #1 ===
Player release timed out.
qs1: Player release timed out.
at xc1.h(SourceFile:15)
at i10.run(SourceFile:892)
at xz2.b(SourceFile:89)
at xz2.e(SourceFile:4)
at gs1.B(SourceFile:174)
at mo6.g(SourceFile:235)
at b93.s(SourceFile:29)
at gf3.b6(SourceFile:7)
at h74.b6(SourceFile:5)
at pn.onPause(SourceFile:86)
at org.thunderdog.challegram.MainActivity.onPause(SourceFile:1)
at android.app.Activity.performPause(Activity.java:8609)
at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1604)
at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:5400)
at android.app.ActivityThread.performPauseActivity(ActivityThread.java:5361)
at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:5308)
at android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:53)
at android.app.servertransaction.ActivityTransactionItem.execute(ActivityTransactionItem.java:45)
at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2470)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loopOnce(Looper.java:240)
at android.os.Looper.loop(Looper.java:351)
at android.app.ActivityThread.main(ActivityThread.java:8423)
at java.lang.reflect.Method.invoke(Native Method)
It's from 2015 Material Design, with most buttons and cards deduced to lists to maximise content and touch area, a common practice of IM apps.
The actual problem about design is, thanks to people like Luke Wroblewski, every new design comes with enormous border radius, that either take up space cuts both content and touch area. Which just don't work well at all.
Just check Telegram X's top right menu, it has a border radius of 2dp, embedded onto first & last item, don't take any space, almost invisible.
Newer design's radius start at 16dp, that's about the height of normal text. If embed that radius onto the first & last item, their size would be at least ~1% smaller than other items and become visually different. iOS design is affected by this for 2 decades and just pretend this problem don't exist.
And there is no good solution to the differences caused by that radius. Make 1st & last item sightly larger causes different height. Give the radius its own non-touchable area causes useless area. Make radius smaller got you fired by the managers who don't give a fuck to practicality in design.
---
Main Telegram is still a mix of everything just like before. The addition of iOS elements don't make it brand new. The lists are still 100% Android. The huge gap between group of items in the top right menu breaks both iOS and Android design and come from absolutely nowhere. Pinned chats are no longer splited or bgcolor-differed from other chats for no reason...
Go to Telegram and take a look:) It's simple.
Читать полностью…
why is this msg unsupported on x:
/channel/Arashnm80_Persian/3182
what type of a msg is it exactly?
it looks like a media with caption, how its not supported hmm...
its lagging and crashes
🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘🆘
how to return to stable version without unstalling it
Telegram 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, exoplayer, decoder, datasource, extractor]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 15 (35)
Device: Xiaomi Redmi 23106RN0DA (AP3A.240905.015.A2)
Screen: 1600x720 (density: 2.0, fps: 60.0)
Build: `Redmi/gale_global/gale:15/AP3A.240905.015.A2/OS2.0.202.0.VGPMIXM:user/release-keys`
Package: org.thunderdog.challegram
Locale: en_GB (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: 23/07/2026, 06:35
Date: 02/07/2026, 00:05
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.e9.k(SourceFile:29)
at og.d9.d(SourceFile:1880)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loopOnce(Looper.java:249)
at android.os.Looper.loop(Looper.java:337)
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:3260)
at android.os.Parcel.createException(Parcel.java:3240)
at android.os.Parcel.readException(Parcel.java:3223)
at android.os.Parcel.readException(Parcel.java:3165)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:3816)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1042)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:1030)
at og.y8.d(SourceFile:150)
at og.y8.c(SourceFile:74)
at og.e9.k(SourceFile:29)
at og.d9.d(SourceFile:1880)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loopOnce(Looper.java:249)
at android.os.Looper.loop(Looper.java:337)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:1043)
at com.android.server.notification.NotificationManagerService$12.createNotificationChannelsImpl(NotificationManagerService.java:4256)
at com.android.server.notification.NotificationManagerService$12.createNotificationChannels(NotificationManagerService.java:4306)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1728)
at android.os.Binder.execTransactInternal(Binder.java:1507)
Stack trace:
java.lang.RuntimeException
He is talking about updating the app because X design is like from 2019 and uses oldest Google desing. There is already Material Design 3 and Material Design Expressive nowadays. Even tga got full redesign but tgx is being outdated
Читать полностью…
at least they haven't abandoned the android style like the main app did
Читать полностью…
actually i like X for its smooth simple UI
but yes agreed, we need all the important features added to it.
if u like the current default tlg UI, try tlg plus(it has more customizations) :}
Is it possible to move up the time stamp on the same line as the message? It would make multiple messages in a row much more readable
Читать полностью…
yes, apparently. The bugs seem gone (keyboard opens fine-ish and gestures work without reopening the app)
Читать полностью…
yeah, I use the main app to get notifications (as they're often more reliable and when I press reply it replies to the message I'm replying to instead of sending a message without reply)
I use TGX as a lighter client as the main app is a battery hog
but these are the only useful messages I found on matlog, there does not appear to be any error message of sort
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:584)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1013)
InputDispatcher(1642): Not sending touch event to a94f3e3 org.thunderdog.challegram/org.thunderdog.challegram.MainActivity because it is paused
InputDispatcher(1642): Channel [Gesture Monitor] swipe-up (server) is stealing touch from [a94f3e3 org.thunderdog.challegram/org.thunderdog.challegram.MainActivity (server), [Gesture Monitor] edge-swipe (server)]
Please add this feature to Save Massage Telegram X
View as ChatЧитать полностью…
Even though it looks like one it's not. It's an article-like message with paragraph and an image block.
Читать полностью…
Does the new version of Telegram X support displaying Stars on posts?
Читать полностью…
"people like you"? I literally have no complaints about tgx other than Bluetooth headset not working, this chat is constantly full of people criticising tgx as being outdated and not like tga, or like iPhone. their solution is simple, use tga or iphone (which is based on tgx anyway). the chat is not feature request chat, or a make a complaint abput tgx chat. it is for bug reporting of current beta versions.
Читать полностью…
Telegram X Beta Features Summary
🆕 What's new? (0.28.10.1796 BETA)
- Add more prominent contacts sync alert
- Sync strings.xml with translations.telegram.org
🛠 Technical Changes:
- None
BugFix:
- None
📝 Changes in old Beta:
- Upgrade tgcalls
- Add new TDLib options
- Optimize application launch
- Update FCM to 25.1.1
- Fix OpenSSL linking
- Exclude unused OpenSSL components
- Optimize archive entry on main screen
- iOS client bug workaround: do rudimentary transcoding for rotated videos
- Support new service message types
- Display replied poll option
- BugFixes & Improvements
- Crashfixes
- Add lock emoji to Secret Chat notifications
- Fix opening Instant View with media without captions
Rules and report bugs
Getting crash log files
(Only when requested)
APK & Changelog for latest beta
0.28.10.1796 beta
#beta
Is criticizing the only thing people like you know how to do?
If that's how you respond to everything, you'll never improve
if you want liquid glass go and buy an iPhone
Читать полностью…
Subject: UI is outdated + Polls broken ("Unsupported Message")
Telegram X hasn't had a real design update in years, it still looks like it's from 2019 😭, while the main Telegram app has already moved to a proper iOS-style (Liquid Glass) redesign. X just feels like a stripped clone of the old app with nothing distinct going for it. Even adopting Material 3 properly would be a huge upgrade over what's there now.
Bug: Polls show as "Unsupported Message"
*Create a poll in the main Telegram app
*Open the same chat in Telegram X
*The poll renders as "Unsupported Message" instead of an interactive poll
This has been broken for a long time with no fix. Polls are a core feature, this shouldn't still be unresolved.
I like Telegram X and want to keep using it, but right now it feels neglected compared to the main app. Please prioritize a UI refresh and fix the poll rendering bug.