Telegram-FOSS-Team / Telegram-FOSS

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

Foss version update frequency #507

Open jithinjames916 opened 3 years ago

jithinjames916 commented 3 years ago

Sir, The app Store in the playstore are releasing updates faster, but no much updates on telegram foss version..

Nickoriginal commented 3 years ago

Hello, @jithinjames916! As stated in the README file,

This is an unofficial, FOSS-friendly fork of the original Telegram App for Android.

You can see only Telegram and Telegram X apps in the Google Play Store, if I understand right. Their and Telegram-FOSS's development cycles are not related each other. This fork adapts for self new Telegram versions more slowly than original application as expected (to remove unwanted components). You can download the most fresh beta versions here: https://github.com/Telegram-FOSS-Team/Telegram-FOSS/releases

logicalup commented 2 years ago

Any chance an Fdroid repo can be setup to not depend on Fdroid building/approving this at their convenience, and get updates as soon as they come out here? Something like this https://f-droid.org/en/tutorials/create-repo/

Nickoriginal commented 2 years ago

It requires additional resources and efforts to create and support your own repo in F-Droid, additionally F-Droid can guarantee that it spreads true FOSS apps and check them for viruses or unwanted changes.

Friptick commented 2 years ago

Latest F-Droid version 5.11 here.

An in-app warning says that I must upgrade or the app will stop working "soon".

Does this really mean dumping F-Droid and having to install from source, if using Googleware is out?

PS I know this is not your fault, just fishing for advice or unexplored options.

stefan-niedermann commented 2 years ago

Latest F-Droid version 5.11 here.

Check your setup @Friptick ...

Screenshot_20211203-213300_F-Droid

Younes-L commented 2 years ago

Latest F-Droid version 5.11 here.

An in-app warning says that I must upgrade or the app will stop working "soon".

Does this really mean dumping F-Droid and having to install from source, if using Googleware is out?

PS I know this is not your fault, just fishing for advice or unexplored options.

How did that happen ? Plz go to https://f-droid.org/packages/org.telegram.messenger/

And download latest version (8.1.2 or newer)

And consider uninstalling whichever f-droid client you're using x)

sigprof commented 2 years ago

Well, on some older device I have this (the latest 8.2.7 version is not available — apparently it has been built only for arm64-v8a): available versions @Friptick What device do you have — maybe it has some strange architecture which is no longer supported in the new builds?

Friptick commented 2 years ago

Thanks for the feedback!

Yes @sigprof is surely right. I did already check everything was updated in F-Droid, including F-Droid itself.

It is Android 8.1.0, F-Droid 1.13.1. A 2017 Samsung J-series. Technically insecure because Samsung stopped security updates but it works fine and personally I do not buy the latest hardware just for the sake of it.

Albnu14 commented 2 years ago

Hi, i also got a message to update, but on fdroid the latest update is only available for arm46-v8a while mine is a armeabi-v7a, sadly this happens on several other apps like vlc and i don't have any idea how to solve it, or who to contact for this ( the app devs, or fdroid)

Younes-L commented 2 years ago

Hi, i also got a message to update, but on fdroid the latest update is only available for arm46-v8a while mine is a armeabi-v7a, sadly this happens on several other apps like vlc and i don't have any idea how to solve it, or who to contact for this ( the app devs, or fdroid)

Screenshot_20211203-222330_cropped

Technically you don't need version 8.2.7, which is currently arm64 only. You can install or make sure you have 8.1.2 build 24321 which is the arm package : https://f-droid.org/packages/org.telegram.messenger/ Anything newer than v8.0.1 supports the new mandatory int64 user IDs , and telegram won't enforce sponsored messages until 2022, and v8.1.2 already supports sponsored messages so there's 0 reason for telegram to ask you to update your app if you're already using 8.1.2

Albnu14 commented 2 years ago

Anything newer than v8.0.1 supports the new mandatory int64 user IDs

And here i was wondering why it would ask to update, i'm using the 8.0.0 version, i didn't feel i wanted to upgrade to 8.1.2 so i decided to wait for the next one, in this case i will just update to whatever is available.

Younes-L commented 2 years ago

Anything newer than v8.0.1 supports the new mandatory int64 user IDs

And here i was wondering why it would ask to update, i'm using the 8.0.0 version, i didn't feel i wanted to upgrade to 8.1.2 so i decided to wait for the next one, in this case i will just update to whatever is available.

@Albnu14 8.0.0 doesn't support int64 IDs, but 8.0.1 does, cause it was a major update with a minor version number ... 8.1.2 is pretty safe it you want to update to it, no major issues as far as I know. In fact I'd recommend you skip 8.0.1 because it has a wonky database upgrade, and in eithercase , when going from 8.0.0 to a newer version, it's much easier to logout from all accounts, update, then log back in (unless you have secret chats, then optimising the database and clearing cache from settings before update is best)

Friptick commented 2 years ago

You can install or make sure you have 8.1.2 build 24321 which is the arm package : https://f-droid.org/packages/org.telegram.messenger/

Thanks. But the point of the F-Droid app is to avoid having to download from URLs.

Managed to resolve the issue inside F-Droid by enabling "incompatible" versions. This revealed a bunch of recent incompatible versions and also, magically, a few which were NOT incompatible. Including 8.1.2. I remember having this F-Droid issue before. Maybe if a single version is listed as incompatible, F-Droid will hide more recent compatible ones unless the "incompatible" setting is enabled. Or something. An F-Droid problem anyway.

Thanks for your help.