Telegram-FOSS-Team / Telegram-FOSS

Unofficial, FOSS-friendly fork of the original Telegram client for Android
GNU General Public License v2.0
2.78k stars 361 forks source link

Doesn't accept calls ringtones #509

Open mbnoimi opened 3 years ago

mbnoimi commented 3 years ago

Whenever I set any customized ringtone (whether it comes from external source or from the embedded ringtones) the incoming call became without any sound (muted) unless I set calls intone to default one. image image

This issue doesn't occur with old versions (recently I upgraded TgFOSS)

IMPORTANT: Customized notification sound works fine (as seen below) image

Younes-L commented 3 years ago

This sounds like an upstream bug, here are your options :

Telegram made public part of their suggestions and issue tracking platform, but I did not find anything related to the description you provided.

mbnoimi commented 3 years ago

try with official telegram beta client and see whether the same problems happen there

The link doesn't point to the official domain. May you please send to me an official source (whether brand Tg of TgFoss)

Younes-L commented 3 years ago

try with official telegram beta client and see whether the same problems happen there

The link doesn't point to the official domain. May you please send to me an official source (whether brand Tg of TgFoss)

The link points to the distribution platform used by the developer of telegram client for Android. It is the only place where the beta version of telegram is distributed by the developer himself. Similar to this link https://play.google.com/store/apps/details?id=org.telegram.messenger As you can see, play.google.com is not an official telegram domain. Does that mean it is not an official distribution of a telegram client ?

Fortunately, the current stable version of telegram for Android is up to date with the beta, so they should be the same. You can download the stable version from https://telegram.org/dl/android/apk Or from https://play.google.com/store/apps/details?id=org.telegram.messenger

The reason I linked to the beta instead of the stable is because the developer asks people to first try the beta version before reporting any bugs in the group chat. This is a general rule of thumb and usually makes sense when the beta version is newer than the stable version.

If you look at this project's readme, you'll see a link to the github repository of telegram for android. Click on that link and you'll find that the original project is owned by DrKlo (Nikolay K.) Compare it with the previous link : ↓ drklo https://install.appcenter.ms/users/drklo-2kb-ghpo/apps/telegram-beta-2/distribution_groups/all-users-of-telegram-beta-2 Also notice when you click on the above link, it says

Telegram Beta 2 for Android by Nikolay

If you need even more proof, Nikolay (nick) is an admin in the group chat @tgbetachat , go to the group and click the search button, then search by user, then nick, and you'll find his messages. You could even ask in the group "where is the link for the official beta version of telegram" , if you choose to disregard the pinned message.

Telegram doesn't mention the existence of (any) beta version, because it's not meant to be used by everybody. These beta versions are distributed by their respective developers to help test features and find bugs. Telegram themselves don't care about this and are not involved.

Each individual telegram app (iOS, android, desktop, web, macos) is made by a different person or group of people independently, and each beta version of these respective apps is distributed using a different platform :

As you can see, none of the beta clients are distributed under telegram's domain name