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
No, not in a secret chat, but in a regular chat, with a new contact who's saved to my phone's address book and synced with Telegram. The "Auto-delete messages" option for new contacts is located in the main "Privacy" settings in Telegram, and only there. I understand what a secret chat is, and I wouldn't write about it. Young people might have no problem remembering this, but there are older people too... However, as they say around here, "My job is to offer, yours to refuse" (C).
I don’t insist, especially since I found the problem and fixed it, and let the owner decide for himself. "he's the boss." (C)
UPD: Settings > Privacy > Auto-Delete Messages >
"Auto-Delete Messages
ello
Self-Destruct Timer
Self-Destruct Timer
Are you sure you want all messages in your new private chats and in new groups you create to be automatically deleted for everyone 1 day after they are sent?
Cancel
Enable
Set Custom Time
If enabled, all new messages in chats you start will be automatically deleted for everyone at some point after they are sent. You can also apply this setting for your existing chats."(C)
Hi! Suggestion for improvement: add the "Auto-delete messages" option (for new contacts) to Tgx. I encountered a situation where my new and close contacts' chat messages are being deleted after 1 day. Now it turns out this option is enabled in the Telegram app, but not in Tgx! Yes, I saw a message flashing briefly in TGX about the deletion timer being turned on. I searched throughout the Tgx app and couldn't find it anywhere. Or maybe this option is available in Tgx? I don't use Telegram, only Tgx, and I don't remember my Telegram settings. Why is it that the settings of one app affect the other, and I can't disable these settings or even understand that they are enabled in the official app? It seems ridiculous, considering the fact that both Tg and Tgx are products from Telegram FZ-LLC .
Thanks for your attention and Tgx!
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]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 16 (36)
Device: OPPO OPPO CPH2659 (CPH2659_16.0.8.300(EX01))
Screen: 2376x1080 (density: 3.375, fps: 90.0)
Build: `OPPO/CPH2659/OP5AB0L1:16/BP2A.250605.015/V.R4T3.336bca0-f44493-f4c7ea:user/release-keys`
Package: org.thunderdog.challegram
Locale: en_SG (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: 22/7/26, 4:54 pm
Date: 9/7/26, 3:30 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:67)
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:112)
at android.os.Looper.loopOnce(Looper.java:306)
at android.os.Looper.loop(Looper.java:416)
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:3373)
at android.os.Parcel.createException(Parcel.java:3353)
at android.os.Parcel.readException(Parcel.java:3336)
at android.os.Parcel.readException(Parcel.java:3278)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:3958)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1269)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:1257)
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.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:112)
at android.os.Looper.loopOnce(Looper.java:306)
at android.os.Looper.loop(Looper.java:416)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:1215)
at com.android.server.notification.NotificationManagerService$12.createNotificationChannelsImpl(NotificationManagerService.java:5123)
at com.android.server.notification.NotificationManagerService$12.createNotificationChannels(NotificationManagerService.java:5174)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1782)
at android.os.Binder.execTransactInternal(Binder.java:1448)
Stack trace:
java.lang.RuntimeException
Doesn't TgX use Google Cloud Messaging API for efficient power usage and reliability?
It does not show up for me on normal telegram clients.
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]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 15 (35)
Device: OPPO OPPO CPH2557 (CPH2557_15.0.0.1801(EX01))
Screen: 2400x1080 (density: 3.0, fps: 90.0)
Build: `OPPO/CPH2557/OP573DL1:15/AP3A.240617.008/T.R4T2.23ba084-2f45a:user/release-keys`
Package: org.thunderdog.challegram
Locale: ru_KZ (app: ru)
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: 17
Now: 22.07.2026, 08:03
Count: 3
Date: 22.07.2026, 08:03
Step: display
chat: -1003771414359, title: ВАКАНСИЯ КАРАКАЛПАКСТАНusername: @vakansiya_karakalpakstann
java.lang.IllegalStateException: User 0 is locked or not running
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3279)
at android.os.Parcel.createException(Parcel.java:3255)
at android.os.Parcel.readException(Parcel.java:3238)
at android.os.Parcel.readException(Parcel.java:3180)
at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:3210)
at android.app.NotificationManager.notifyAsUser(NotificationManager.java:766)
at android.app.NotificationManager.notify(NotificationManager.java:716)
at y1.w.c(SourceFile:69)
at og.g9.f(SourceFile:389)
at og.b9.h(SourceFile:348)
at og.d9.d(SourceFile:1835)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loopOnce(Looper.java:282)
at android.os.Looper.loop(Looper.java:387)
at sf.h.run(SourceFile:32)
=== Cause #1===
android.os.RemoteException: Remote stack trace:
at com.android.server.pm.ShortcutService.throwIfUserLockedL(ShortcutService.java:1384)
at com.android.server.pm.ShortcutService$LocalService.getShortcuts(ShortcutService.java:3069)
at com.android.server.pm.LauncherAppsService$LauncherAppsImpl.getShortcuts(LauncherAppsService.java:1306)
at android.content.pm.LauncherApps.getShortcuts(LauncherApps.java:1488)
at com.android.server.notification.ShortcutHelper.getValidShortcutInfo(ShortcutHelper.java:207)
Stack trace:
java.lang.RuntimeException
Count: 9
Date: 22.07.2026, 08:03
Step: display
chat: 8127514293, title: Анонимный чат • Чат рулеткаusername: @secretme
java.lang.IllegalStateException: User 0 is locked or not running
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3279)
at android.os.Parcel.createException(Parcel.java:3255)
at android.os.Parcel.readException(Parcel.java:3238)
at android.os.Parcel.readException(Parcel.java:3180)
at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:3210)
at android.app.NotificationManager.notifyAsUser(NotificationManager.java:766)
at android.app.NotificationManager.notify(NotificationManager.java:716)
at y1.w.c(SourceFile:69)
at og.g9.f(SourceFile:389)
at og.b9.h(SourceFile:348)
at og.d9.d(SourceFile:1835)
at bg.w2.handleMessage(SourceFile:173)
at android.os.Handler.dispatchMessage(Handler.java:103)
at android.os.Looper.loopOnce(Looper.java:282)
at android.os.Looper.loop(Looper.java:387)
at sf.h.run(SourceFile:32)
Count: 3
Date: 22.07.2026, 08:03
Step: display
chat: -1003948487662, title: 𝐀𝐭𝐚𝐥𝐠𝐚𝐧username: @senga_atalldi
java.lang.IllegalStateException: User 0 is locked or not running
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3279)
at android.os.Parcel.createException(Parcel.java:3255)
at android.os.Parcel.readException(Parcel.java:3238)
at android.os.Parcel.readException(Parcel.java:3180)
at android.app.INotificationManager$Stub$Proxy.enqueueNotificationWithTag(INotificationManager.java:3210)
at android.app.NotificationManager.notifyAsUser(NotificationManager.java:766)
at android.app.NotificationManager.notify(NotificationManager.java:716)
at y1.w.c(SourceFile:69)
at og.g9.f(SourceFile:389)
I don't have this bug on my device 🤔 Must be system specifc
Bottom of Settings - tap the version code - Copy Report Details - send it here
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]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 13 (33)
Device: TECNO TECNO TECNO KJ5 (KJ5-H6931ABCDEFGHI-T-OP-241009V1507)
Screen: 1452x720 (density: 2.0, fps: 90.0)
Build: `TECNO/KJ5-OP/TECNO-KJ5:13/TP1A.220624.014/241009V1507: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/21/26, 11:37 PM
Date: 7/21/26, 1:15 PM
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:102)
at android.os.Looper.loopOnce(Looper.java:204)
at android.os.Looper.loop(Looper.java:291)
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:3025)
at android.os.Parcel.createException(Parcel.java:3005)
at android.os.Parcel.readException(Parcel.java:2988)
at android.os.Parcel.readException(Parcel.java:2930)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:3578)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:935)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:923)
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:102)
at android.os.Looper.loopOnce(Looper.java:204)
at android.os.Looper.loop(Looper.java:291)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:961)
at com.android.server.notification.NotificationManagerService$10.createNotificationChannelsImpl(NotificationManagerService.java:3930)
at com.android.server.notification.NotificationManagerService$10.createNotificationChannels(NotificationManagerService.java:3975)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1616)
at android.os.Binder.execTransactInternal(Binder.java:1286)
Stack trace:
java.lang.RuntimeException
what are you talking about, if you delete the message it's gone, there is no tick. tick is to confirm sent, 2 tick to confirm it has been read
Читать полностью…
Even now, the second tick to confirm the message has been deleted for the other party is not displayed.
Читать полностью…
Seems like the only way to grab developers attention to fix the login code is by ranting 😃
Читать полностью…
What does "Option 1" mean? What kind of support is being offered?
Читать полностью…
What if TGX has got "profile music" like main TG app
Читать полностью…
auto delete timer is available for tgx secret chats, but secret chat you see in tgx isn't visible in tga, and vice versa. this next comment is not directed at you Niko, but because of timer i want to send in same message.
---‐---------------------------------------------------
it's amazing that people complain and complain for an update, and the first thing they do when there is an update is demand more features and complain again that tgx doesn't have tga features... GO AND USE TGA THEN
Hello - I beg you
Please add the "Direct" feature, which is specifically for channels,
to your wonderful application.
Thank you.💚
because you have disabled notifications in system settings
Читать полностью…
It does, unless you see any error in Settings - Notifications.
Читать полностью…
ticks work for me, nothing to do with deleting the message
Читать полностью…
The "check" option, which is supposed to indicate whether a message has been read by the recipient, is not working. Please fix this bug.
Telegram X 0.28.10.1795-arm64-v8a
Telegram X 0.28.10.1795-arm64-v8a (e2baffd9)
TDLib: 1.8.66 (tdlib/td@022d602)
androidx-media3: 1.10.1 [common, decoder.opus, decoder.vpx, decoder.flac, decoder.ffmpeg, exoplayer, decoder, datasource, extractor, exoplayer.hls]
tgcalls: TGX-Android/tgcalls@e2baffd9
Recaptcha: 18.9.2
WebRTC: TGX-Android/webrtc@e2baffd9
Android: 11 (30)
Device: samsung samsung SM-A505F (RP1A.200720.012.A505FDDS9CWA1)
Screen: 2131x1080 (density: 2.625, fps: 60.000004)
Build: samsung/a50dd/a50:11/RP1A.200720.012/A505FDDS9CWA1:user/release-keys
Package: org.thunderdog.challegram
Locale: fa_IR (app: en)
Installer: com.google.android.packageinstaller
Initiator: com.google.android.packageinstaller
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68
I had this problem, but it's also possible I misunderstood you (I'm translating the text from English). See the message at the link: /channel/tgandroidtests/293848
UPD: Go to Telegram X Settings, click on the app version at the very bottom, then on "Experimental Settings", then click "Continue," and in the menu that appears, turn off the switch next to "Disable edge to edge." That's it: The "Delete For... " option will be visible again. Good luck to you!
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]
tgcalls: TGX-Android/tgcalls@8e27a92
Recaptcha: 18.8.0
WebRTC: TGX-Android/webrtc@6ecff4f
Android: 12 (31)
Device: samsung samsung SM-A125F (SP1A.210812.016.A125FXXS6CXJ1)
Screen: 1465x720 (density: 1.875, fps: 60.0)
Build: `samsung/a12nsxx/a12:12/SP1A.210812.016/A125FXXS6CXJ1:user/release-keys`
Package: org.thunderdog.challegram
Locale: ru_RU (app: ru)
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: 21.07.2026, 22:53
Date: 21.07.2026, 12:40
Step: channel
og.w8: java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist : pkg=org.thunderdog.challegram, channel group=account_8745237780
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.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:226)
at android.os.Looper.loop(Looper.java:313)
at sf.h.run(SourceFile:32)
=== Cause #1===
java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist : pkg=org.thunderdog.challegram, channel group=account_8745237780
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:2442)
at android.os.Parcel.createException(Parcel.java:2422)
at android.os.Parcel.readException(Parcel.java:2405)
at android.os.Parcel.readException(Parcel.java:2347)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:4790)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1048)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:953)
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.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:226)
at android.os.Looper.loop(Looper.java:313)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(PreferencesHelper.java:1038)
at com.android.server.notification.NotificationManagerService$14.createNotificationChannelsImpl(NotificationManagerService.java:4551)
at com.android.server.notification.NotificationManagerService$14.createNotificationChannels(NotificationManagerService.java:4582)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1858)
at android.os.Binder.execTransactInternal(Binder.java:1215)
Stack trace:
java.lang.RuntimeException
I had the SMS issue with rooted Xiaomi 17 ultra, is it due to integrity?
Читать полностью…
Telegram X Beta Features Summary
🆕 What's new? (0.28.10.1795 BETA)
- Add lock emoji to Secret Chat notifications
- Fix opening Instant View with media without captions
🛠 Technical Changes:
- None
BugFix:
- Fix typo that was causing crash in Recent Actions
- Fix RECAPTCHA_VERSION content
📝 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
Rules and report bugs
Getting crash log files
(Only when requested)
APK & Changelog for latest beta
0.28.10.1795 beta
#beta