TGX-Android / Telegram-X

The main repository of Telegram X — official alternative Telegram client for Android.
https://play.google.com/store/apps/details?id=org.thunderdog.challegram
GNU General Public License v3.0
3.4k stars 533 forks source link

Notification Style revert to Silent after received message #590

Open henrythebuilder opened 5 months ago

henrythebuilder commented 5 months ago

Hi, I have a problem with the notification configuration: although they are set to 'Sound and pop-up' after receiving a message (with notification) the setting is reverted to 'Silent', so to have the sound enabled again you need to manually change the configuration to 'Sound and pop-up'. This happens for all categories, 'Private chats', 'Groups' and 'Channels', after receiving any type of message, making the application unusable. I don't have any problems of this type with the other installed applications.

Actual settings:

Attempts and tests made without success:

Thanks in advance. Enrico

Telegram X 0.26.3.1674-armeabi-v7a (8b30d0fe)
TDLib: 1.8.23 (tdlib/td@d963044)
Android: 10 (29)
Package: org.thunderdog.challegram
Locale: it_IT (app: en)
Installer: Google Play
henrythebuilder commented 4 months ago

Unfortunately, I have the same problems with the latest beta version too:

Telegram X 0.26.7.1704-armeabi-v7a (ccefce2b)
TDLib: 1.8.28 (tdlib/td@2424d68)
tgcalls: TGX-Android/tgcalls@6adef64
WebRTC: TGX-Android/webrtc@df2ed68b47
Android: 10 (29)
Device: wheatek Blackview BV5500Plus
Package: org.thunderdog.challegram
Locale: en_US (app: en)
Installer: Google Play
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68

as further tests I attach some screenshots of the configuration:

1) starting configuration

tgx-1

2) configuration changed after receiving a message

tgx-2

3) configuration reset by "Reset All Notifications" from app settings

note that some entries are duplicated!

tgx-3

4) configuration changed 'by hand': re-enable sound!

tgx-4

at this point, when a new message arrives, the configuration automatically returns to configuration 2).

If it's possible, I’d be grateful for any help in order to resolve the issue. Thanks in advance

vkryl commented 4 months ago

@henrythebuilder 1704 is not the latest, and it did not include any relevant fixes.

henrythebuilder commented 4 months ago

My bad, I didn't see the new release. As of now, for my phone isn't on the play store yet, but as soon as it's available I'll update it and update the status of the issue. thanks for the support :+1:

vkryl commented 4 months ago

You can download the 1706 through GitHub Releases section or https://t.me/tgx_log (arm64-v8a or armeabi-v7a APK, depending on your device). It is exactly the same one uploaded to GP, except it doesn't have a delay caused by Google Play review process (which takes days even for beta).

henrythebuilder commented 4 months ago

Unfortunately also with the latest Beta version I have the same problems:

Telegram X 0.26.7.1706-armeabi-v7a (86a6deea)
TDLib: 1.8.28 (tdlib/td@4d90c2a)
tgcalls: TGX-Android/tgcalls@6adef64
WebRTC: TGX-Android/webrtc@df2ed68b47
Android: 10 (29)
Device: wheatek Blackview BV5500Plus 
Package: org.thunderdog.challegram
Locale: en_US (app: en)
Installer: Google Play
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68

A note about the configuration: the duplicate configurations in the system introduced by "Reset All Notifications" are restored to three items if some changes are made from the app settings (notifications). Apart from this I have the same situation described previously.

vkryl commented 4 months ago

@henrythebuilder kindly include full information from the 'copy report details'. Also note that losing modifications made in the system notification settings is expected when editing notification settings inside the app (this behavior won't be changed).

henrythebuilder commented 4 months ago

thanks @vkryl, here is the full report details:

Telegram X 0.26.7.1706-armeabi-v7a (86a6deea)
TDLib: 1.8.28 (tdlib/td@4d90c2a)
tgcalls: TGX-Android/tgcalls@6adef64
WebRTC: TGX-Android/webrtc@df2ed68b47
Android: 10 (29)
Device: wheatek Blackview BV5500Plus (BV5500Plus_EEA_E535_V1.0_20200729V11)
Screen: 1344x720 (density: 2.0, fps: 60.0)
Build: Blackview/BV5500Plus_EEA/BV5500Plus:10/QP1A.190711.020/1595954285:user/release-keys
Package: org.thunderdog.challegram
Locale: en_US (app: en)
Installer: Google Play
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68
vkryl commented 4 months ago

I've fixed seeing the duplicate notification categories in system settings until the Telegram X restart in 4e88956 (which is "3) configuration reset by "Reset All Notifications" from app settings" in your original comment).

However, the "although they are set to 'Sound and pop-up' after receiving a message (with notification) the setting is reverted to 'Silent'" seems to be something related to your build / some software installed.

By design, Android apps create a system notification category, which becomes read-only from that moment, and modifiable only by system. Nobody can modify them, including Telegram X. When you press Reset All Notifications, all notification categories in the system related to the account are deleted, and new ones are created (and the bug that was fixed in 4e88956 is that the old category was properly removed only during app launch).

This means that there must be something in your system that modifies Telegram X notification categories when it tries to show a notification.

henrythebuilder commented 4 months ago

Thank you very much for the support and analysis of the problem.

I don't know if at this point it can be useful but the problem is the same if instead of resetting the notifications from apps (3), notifications are changed from the system.

However, I'm not practical of the Android system so I don't know how to proceed further, I had very similar problems with the 'original' Telegram client (but recently, I don't remember since, certainly not at the beginning) and I was hoping to improve the situation with this client ...

The strange thing is that I have these problems only with Telegram, and not having notifications in many cases makes it 'difficult' to use.

If the problem is really due to the system, for me, you can also close this issue.

Thanks again for everything.

vkryl commented 4 months ago

Try reproducing the issue with the next (1707) beta to see if there's any difference. Also are there any system updates or an upgrade available for your device?

henrythebuilder commented 4 months ago

At the moment there are no further updates available for the system. Today I tried the latest beta via apk but unfortunately the problem still exists.

Telegram X 0.26.7.1708-armeabi-v7a (8b6b2580)
PRs: #598 (abaf9310)
TDLib: 1.8.28 (tdlib/td@4d90c2a)
tgcalls: TGX-Android/tgcalls@6adef64
WebRTC: TGX-Android/webrtc@df2ed68b47
Android: 10 (29)
Device: wheatek Blackview BV5500Plus (BV5500Plus_EEA_E535_V1.0_20200729V11)
Screen: 1344x720 (density: 2.0, fps: 60.0)
Build: Blackview/BV5500Plus_EEA/BV5500Plus:10/QP1A.190711.020/1595954285:user/release-keys
Package: org.thunderdog.challegram
Locale: it_IT (app: en)
Installer: 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
vkryl commented 4 months ago

@henrythebuilder could you please update the screenshots in the original post with the 1708 build? Need to check couple details.

henrythebuilder commented 4 months ago

Yesterday I tried again to reinstall telegram (stop+clean storage+uninstall+install), so the current version is the same but from 'Play Store':

Telegram X 0.26.7.1708-armeabi-v7a (8b6b2580)
PRs: #598 (abaf9310)
TDLib: 1.8.28 (tdlib/td@4d90c2a)
tgcalls: TGX-Android/tgcalls@6adef64
WebRTC: TGX-Android/webrtc@df2ed68b47
Android: 10 (29)
Device: wheatek Blackview BV5500Plus (BV5500Plus_EEA_E535_V1.0_20200729V11)
Screen: 1344x720 (density: 2.0, fps: 60.0)
Build: Blackview/BV5500Plus_EEA/BV5500Plus:10/QP1A.190711.020/1595954285:user/release-keys
Package: org.thunderdog.challegram
Locale: en_US (app: en)
Installer: Google Play
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68

Here are the Screenshots:

1) starting configuration

tg1-1

2) configuration changed after receiving a message

tg2-1

3) configuration reset by "Reset All Notifications" from app settings

tg3-1

4) configuration changed 'by hand':

unnecessary, I only disabled 'New Contacts Notification'

vkryl commented 4 months ago

@henrythebuilder could you try selecting some custom notification sound in the system immediately after the step 1? Note that it is important to do this from the system settings, not from the in-app Telegram X settings.

henrythebuilder commented 3 months ago

In the past I had already tried to change the sound but without success. Unfortunately now, even with the custom notifications, I had no benefits. However, trying to configure the system as indicated I noticed some differences. For each test I reset the notifications configuration from the app before configuring them in a new way from the system settings:

Telegram X 0.26.8.1717-armeabi-v7a (11cd548e)
TDLib: 1.8.29 (tdlib/td@e4796b9)
tgcalls: TGX-Android/tgcalls@6adef64
WebRTC: TGX-Android/webrtc@df2ed68b47
Android: 10 (29)
Device: wheatek Blackview BV5500Plus (BV5500Plus_EEA_E535_V1.0_20200729V11)
Screen: 1344x720 (density: 2.0, fps: 60.0)
Build: Blackview/BV5500Plus_EEA/BV5500Plus:10/QP1A.190711.020/1595954285:user/release-keys
Package: org.thunderdog.challegram
Locale: en_US (app: en)
Installer: Google Play
APK Fingerprint: 66:46:21:34:34:5a:6a:da:c3:c1:d5:ae:a9:ce:f0:42:1b:7c:ab:68