FDroid updated my jami Client to 20260213 last night. I’m using Lineage OS 23.2-20260212-NIGHTLY-sunfish on my phone. Updated version closes as soon as it opens. If it helps I’m getting the below when trying to install his Fdroid. Have manually installed 20260209-01
1 Like
Let’s try if the latest version has fixed this issue
Still the same version (20260213-01) on F-Droid. Will keep on the 20260209-01 until there is a version change on F-Droid
1 Like
Can we expect a newer version of Jami will be updated quickly?
Or user community will be left with this not opening issue?
how to know if it is under review ?
A newer Jami version, 20260214-01 (486), has been merged into the code.
Thank you for confirming that Jami from F-Droid runs on LineageOS.
Can you please advise any corrections or improvements to the following Jami LineageOS setup page?
Thank you
Yes. A newer version of Jami is expected soon.
No. The issue will be fixed, and Jami will open.
Search for the “update version” string on the Jami Gerrit site.
It looks like the Jami team has finished the review and has already merged the patch.
Please click the following link to donate to the Jami developers.
Thank you
1 Like
thanks for the update. I’ll keep an eye out on F-Droid
The Lineage instructions look fine - ignoring the unified push service as I think that is broken at the moment. For the moment I stick to DHT Local + enable notifications manually for the Jami app in Lineage OS, by default this i soff.
1 Like
Just installed 20260214-01 from F-Droid. Looking much better. Thanks
1 Like
Sorry for the belated reply.
Thank you for your recommendation, which has been added to the LineageOS setup instructions in the following link.
Unfortunately, I don’t have access to a LineageOS device. If there are further corrections or improvements, please write the exact wording from LineageOS.
Thank you once again.
The Lineage OS instructions look fine for me and reflects my experiences between Jami and LineageOS, just requiring the manual changed of enabling notifications manually and setting the Connectivity Mode setting to Local DHT node
1 Like
I’m having this same problem on Android 16.
Welcome to the Jami forum Jev.
Are you still having issues? There is an updated version available which fixed my issue, it maybe worth checking to see if your Jami app is up to date?