# V 2.64 is still not avalible on f-droid?

**URL:** <https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995>\
**Category:** Mutual Help\
**Created:** [October 30, 2026, 3:18pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995 "2026-10-30T15:18:37Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![ycEric](https://forum.delta.chat/user_avatar/forum.delta.chat/yceric/32/3848_2.png) [@ycEric](https://forum.delta.chat/u/ycEric)\
**Post date:** [October 30, 2026, 3:18pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/1 "2026-10-30T15:18:37Z")

</div>

the 2.64 version is available on github releases, but i still can’ t find its update on f-droid, did u forget that?

---

<div class="post-metadata">

**Author:** ![duub](https://forum.delta.chat/user_avatar/forum.delta.chat/duub/32/3238_2.png) [@duub](https://forum.delta.chat/u/duub)\
**Post date:** [October 30, 2026, 4:05pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/2 "2026-10-30T16:05:14Z")

</div>

F-droid takes a little bit more time to be published, the two releases before took 2 and 3 days to be published on f-droid after the github release, maybe this one is taking a little bit longer.

---

<div class="post-metadata">

**Author:** ![duub](https://forum.delta.chat/user_avatar/forum.delta.chat/duub/32/3238_2.png) [@duub](https://forum.delta.chat/u/duub)\
**Post date:** [October 30, 2026, 4:10pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/3 "2026-10-30T16:10:17Z")

</div>

I forgot to mention, if you like to update ASAP I recomend to use ObtainX or Obtanium (I’ve used both, now I’m using the first one, It made me easier to add new apps) this software let you follow the github repositories being faster to get every update.

---

<div class="post-metadata">

**Author:** ![ycEric](https://forum.delta.chat/user_avatar/forum.delta.chat/yceric/32/3848_2.png) [@ycEric](https://forum.delta.chat/u/ycEric)\
**Post date:** [October 31, 2026, 8:55am UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/4 "2026-10-31T08:55:33Z")

</div>

thanks for introducing! the obtain looks good, but, first, the deltachat in github releases is different from f-droid version! if u have a try, you will find that you can install two same Delta Chat apps, one is from github/googleplay, the other is from f-droid…

在 2026-10-31 00:20:24，duub [delta-forum@testrun.org](mailto:delta-forum@testrun.org) 写道：

---

<div class="post-metadata">

**Author:** ![duub](https://forum.delta.chat/user_avatar/forum.delta.chat/duub/32/3238_2.png) [@duub](https://forum.delta.chat/u/duub)\
**Post date:** [October 31, 2026, 9:16am UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/5 "2026-10-31T09:16:45Z")

</div>

I don’t deeply understand how it works but I’ve read something about f-droid do their own compiling stuff and sign the apps with their own key, maybe is that

---

<div class="post-metadata">

**Author:** ![ycEric](https://forum.delta.chat/user_avatar/forum.delta.chat/yceric/32/3848_2.png) [@ycEric](https://forum.delta.chat/u/ycEric)\
**Post date:** [October 31, 2026, 11:50am UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/6 "2026-10-31T11:50:34Z")

</div>

yes u r right, the F-Droid version of the same app differs from versions obtained from other app sources(like github/googleplay) and i want to test my deltachat, u can add & chat with me if u like​👋 [Message privately on Delta Chat](https://i.delta.chat/#503354626D514BA609C9E90A7A2D5C52DCD938FE&v=3&i=hC6DRd79GYtYIBzxJymX11KF&s=1ngTx5unQDh2aT9zp4QCQooP&a=fblm3dxl8%40nchrcht.la10cy.net&r=w4qc8wfjz@chat.tinydispatch.org&n=EricYuan%2DEU_Relay)

在 2026-10-31 17:26:49，duub [delta-forum@testrun.org](mailto:delta-forum@testrun.org) 写道：

---

<div class="post-metadata">

**Author:** ![punkero](https://forum.delta.chat/user_avatar/forum.delta.chat/punkero/32/3455_2.png) [@punkero](https://forum.delta.chat/u/punkero)\
**Post date:** [October 31, 2026, 12:33pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/7 "2026-10-31T12:33:06Z")

</div>

If you’re unaware, there’s an endpoint (and even an Android app) to monitor the F-Droid build queue located here: [https://monitor.f-droid.org/builds](https://monitor.f-droid.org/builds)

Fun trivia, if you follow the links towards the bottom to look at the “checkupdates” pipeline, the tasks almost always fail because it takes longer than 3 hours to run (so technically it’s always running). It also appears the build order (generically, there are exceptions) is reverse alphabetical of the internal package name; take a look to the currently running build cycle and you’ll see the pattern in the names, refresh, look again, etc.

---

<div class="post-metadata">

**Author:** ![ycEric](https://forum.delta.chat/user_avatar/forum.delta.chat/yceric/32/3848_2.png) [@ycEric](https://forum.delta.chat/u/ycEric)\
**Post date:** [October 31, 2026, 3:36pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/8 "2026-10-31T15:36:15Z")

</div>

wow so interesting, i already get the new version, my mirror repo in china is a little delay…

在 2026-10-31 20:43:10，“[punkero.org](http://punkero.org)” [delta-forum@testrun.org](mailto:delta-forum@testrun.org) 写道：

---

<div class="post-metadata">

**Author:** ![system](https://forum.delta.chat/uploads/default/original/1X/d435ee2a3c515521f06387caee1b32a67e183f89.jpg) [@system](https://forum.delta.chat/u/system)\
**Post date:** [November 7, 2026, 3:36pm UTC](https://forum.delta.chat/t/v-2-64-is-still-not-avalible-on-f-droid/5995/9 "2026-11-07T15:36:59Z")

</div>

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
