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 there isn't. Best thing you can do might be download them from Chat info - Media tab, where all media are shown in the same size, and the still-small download buttons are in predictable position.
Читать полностью…
Use default DPI / scale settings in your Android system settings?
Also, switch to a device with larger screen if you can
The telegram user that was opened on my number was enabled with two factor verification through a gmail I changed the gmail so my telegram user got banned how can I get my user back
Читать полностью…
#feature suggestion: Pin to bottom - Pin a chat to the bottom of a folder / archive, alert user about possible inconvenience if archive / that folder has a lot of chats (around 50 chats?)
This can't be synced across clients until TG server supports it, but I think that should be fine
https://www.google.com/search?q=Android%20push%20messages
Travel back to 20 years ago (VK starts in 2006, exactly 20 years ago), and tell Durov to work on a new mobile phone OS with its own message push system, instead of the VK thing, might fix this.
Telegram X also support keep a connection with Telegram to receive messages, or use Huawei Mobile Services. Former uses more battery and the latter is just another Firebase.
Greetings!!!
Why should Telegram X still depend on Google's Firebase and not use it like Telegram.Web?
we don't need to read Chinese to recognise it is spam 😂 - also tgx has translation built in so even if we did, we can read it first
Читать полностью…
Now, here's another thing: you're talking specifically about Telegram, and this supergroup is for identifying bugs and submitting suggestions for improvement Telegram X (Tgx). Read the pinned message in the group header at the top. To avoid waiting for your suggestion to be implemented, you can watch the Telegram video right now in any video player installed on your device: while watching or pausing the video, click the three dots in the upper right corner and select "Open in..." That's it. Good luck! And success in your studies! 😊🤝
(!)By the way, Telegram X doesn't have this problem: The control buttons for the video in Tgx are located at the very bottom, and if you pause the video and then tap on the video image that isn't covered by the accompanying text, the buttons and some of the text disappear, leaving a completely blank screen!!! — And perhaps most importantly, with Telegram X, you don't need to download videos—as the Telegram app requires. You should download the latest version of Telegram X from this link /channel/tgx_log/1527 in the official channel, or from the app store!
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: samsung samsung SM-A055F (AP3A.240905.015.A2.A055FXXSBDYJ2)
Screen: 1600x720 (density: 1.875, fps: 60.0)
Build: `samsung/a05mxx/a05m:15/AP3A.240905.015.A2/A055FXXSBDYJ2:user/release-keys`
Package: org.thunderdog.challegram
Locale: id_ID (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: 4/17/26, 15:12
Date: 4/17/26, 14:59
Step: channel
og.w8: java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist : pkg=org.thunderdog.challegram, channel group=account_8642416175
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:103)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:342)
at sf.h.run(SourceFile:32)
=== Cause #1===
java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist : pkg=org.thunderdog.challegram, channel group=account_8642416175
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3261)
at android.os.Parcel.createException(Parcel.java:3241)
at android.os.Parcel.readException(Parcel.java:3224)
at android.os.Parcel.readException(Parcel.java:3166)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:4973)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1201)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:1189)
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:103)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:342)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(qb/102108534 aedde750b3ee72c127b1c1791bea92c8bf9d43adbcd7021b194b4726f100bca6:112)
at com.android.server.notification.NotificationManagerService$17.createNotificationChannelsImpl(qb/102108534 aedde750b3ee72c127b1c1791bea92c8bf9d43adbcd7021b194b4726f100bca6:98)
at com.android.server.notification.NotificationManagerService$17.createNotificationChannels(qb/102108534 aedde750b3ee72c127b1c1791bea92c8bf9d43adbcd7021b194b4726f100bca6:38)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:2169)
at android.os.Binder.execTransactInternal(Binder.java:1536)
Stack trace:
java.lang.RuntimeException
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: samsung samsung SM-A055F (AP3A.240905.015.A2.A055FXXSBDYJ2)
Screen: 1600x720 (density: 1.875, fps: 60.0)
Build: `samsung/a05mxx/a05m:15/AP3A.240905.015.A2/A055FXXSBDYJ2:user/release-keys`
Package: org.thunderdog.challegram
Locale: id_ID (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: 4/17/26, 15:05
Date: 4/12/26, 18:07
Step: channel
og.w8: java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist : pkg=org.thunderdog.challegram, channel group=account_7819208978
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:103)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:342)
at sf.h.run(SourceFile:32)
=== Cause #1===
java.lang.IllegalArgumentException: NotificationChannelGroup doesn't exist : pkg=org.thunderdog.challegram, channel group=account_7819208978
Stack trace:
java.lang.RuntimeException
at android.os.Parcel.createExceptionOrNull(Parcel.java:3261)
at android.os.Parcel.createException(Parcel.java:3241)
at android.os.Parcel.readException(Parcel.java:3224)
at android.os.Parcel.readException(Parcel.java:3166)
at android.app.INotificationManager$Stub$Proxy.createNotificationChannels(INotificationManager.java:4973)
at android.app.NotificationManager.createNotificationChannels(NotificationManager.java:1201)
at android.app.NotificationManager.createNotificationChannel(NotificationManager.java:1189)
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:103)
at android.os.Looper.loopOnce(Looper.java:257)
at android.os.Looper.loop(Looper.java:342)
at sf.h.run(SourceFile:32)
=== Cause #2===
android.os.RemoteException: Remote stack trace:
at com.android.server.notification.PreferencesHelper.createNotificationChannel(qb/102108534 aedde750b3ee72c127b1c1791bea92c8bf9d43adbcd7021b194b4726f100bca6:112)
at com.android.server.notification.NotificationManagerService$17.createNotificationChannelsImpl(qb/102108534 aedde750b3ee72c127b1c1791bea92c8bf9d43adbcd7021b194b4726f100bca6:98)
at com.android.server.notification.NotificationManagerService$17.createNotificationChannels(qb/102108534 aedde750b3ee72c127b1c1791bea92c8bf9d43adbcd7021b194b4726f100bca6:38)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:2169)
at android.os.Binder.execTransactInternal(Binder.java:1536)
Stack trace:
java.lang.RuntimeException
Oh this 2024 issue is also happening on me a few days ago. A real ARM device with factory ROM, fingerprint, and a locked bootloader with Google certificates, plus a local broadband Internet. I just happened to find that they use a diffefent workflow with different API arguments for user sign-ins, which might cause this issue, so I used the TDlib client for the original Telegram app and it went through.
Читать полностью…
Well you have 2 architectures available, at least one must work in the emulator I guess. Depends of your emulator if supports arm64
@tgx_log
I know: you have "data saving" enabled in your data settings phone; Telegram X automatically uses this setting phone. Disable data saving in your phone settings, and then the toggle switch in Telegram X settings will also be disabled. Telegram X can't ignore your phone settings!
Читать полностью…
22:05
How and why? 🤔
22:07
I see, but why they still didn't 😐. Thanks for info.
I would like to ask if telegram X has any
relevant Settings that can change the shape
or size of the download button? I noticed that for each video to be downloaded, two different download buttons would be randomly displayed. One was larger and easier to press, while the other was smaller
Hello,
I have been using Telegram X for quite a long time and there is an issue I need to address. I want to download a large number of videos on Telegram, but sometimes the download button becomes extremely small.
The download button is positioned very close to the video play button, to the point where I easily mis-tap the play button whenever I try to click download.
Could you please let me know if there is a way to resolve this issue?
I guess as it could concentrate flows to only Google servers from the Telegram server, giving an insulation lauer preventing massive users to obtaining push messages from scattered places, to ensure stability of the TG server.
This is a common practise, and it's why many AOSP devices receive delayed push messages.
Telegram works, but it sends me a notification saying I'm using an emulator, and I don't know if it's a warning about being banned..
That only happens to me with TGX
Hi admins, I noticed the recent Chinese spam. As a native speaker in an Asian timezone, I can easily spot these messages and help keep the chat clean while you are offline. Let me know if you need an extra mod!
Or, for a more aggressive approach, we could just set up a bot to automatically delete and ban any non-English content.
You paused the video, and it's preventing you from "watching content without distractions."?
Decide—are you watching the video or have you paused it? Is the pause preventing you from watching the video? I don't know if this is a joke or what.
During playback, tap on the image or video and the text will disappear.
This is (!)Telegram X, and you mention Telegram. Please provide the app's version number and your device's version number.
"The latest version" is for your device, unknown to the developers. What doesn't work on your unknown device isn't necessarily the same—it doesn't work on all devices. If you want it fixed, well, give us your device details.
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 KI7 (KI7-V7510AACDGHJKLMN-T-GL-240403V4815)
Screen: 2352x1080 (density: 3.0, fps: 60.0)
Build: `TECNO/KI7-GL/TECNO-KI7:13/TP1A.220624.014/240403V4815: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: 4/17/26, 8:49 AM
Date: 4/17/26, 8:43 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.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: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:74)
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: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:3842)
at com.android.server.notification.NotificationManagerService$10.createNotificationChannels(NotificationManagerService.java:3887)
at android.app.INotificationManager$Stub.onTransact(INotificationManager.java:1616)
at android.os.Binder.execTransactInternal(Binder.java:1281)
Stack trace:
java.lang.RuntimeException
Does using a PC emulator affect performance? Because I keep getting a Telegram ad saying I'm using an .
Читать полностью…
Because it's not implemented yet
* Edit your msg for reply when 1h msg limit is on
No "reply in another / private (chat)" on Telegram X?
Читать полностью…