Your rating: None Average: 4.9 (14 votes)

jTox is a native Jolla/Sailfish OS instant messaging client implementing the Tox protocol.

JTox is decentralized and encrypted and does not require central servers.

Application versions: 
File harbour-jtox-1.0.0-1.armv7hl.rpm372.31 KB23/02/2017 - 09:25
File harbour-jtox-1.0.1-1.armv7hl.rpm373.59 KB24/02/2017 - 23:28
File harbour-jtox-1.1.0-1.armv7hl.rpm389.05 KB01/05/2017 - 04:27
File harbour-jtox-1.1.1-1.armv7hl.rpm387.23 KB04/05/2017 - 19:28
File harbour-jtox-1.1.2-1.armv7hl.rpm391.48 KB26/08/2017 - 17:58
File harbour-jtox-1.1.3-1.armv7hl.rpm381.4 KB14/01/2018 - 06:17
File harbour-jtox-1.1.4-1.armv7hl.rpm386.11 KB07/02/2018 - 19:57
File harbour-jtox-1.2.0-1.armv7hl.rpm386.59 KB16/04/2018 - 18:19
File harbour-jtox-1.2.1-1.armv7hl.rpm386.73 KB18/04/2018 - 04:09
File harbour-jtox-1.3.0-1.armv7hl.rpm403.4 KB11/05/2018 - 22:26
File harbour-jtox-1.3.1-1.armv7hl.rpm405.97 KB19/05/2018 - 21:27
File harbour-jtox-1.3.2-1.armv7hl.rpm405.88 KB20/05/2018 - 01:50
File harbour-jtox-1.3.3-1.armv7hl.rpm421.59 KB19/09/2018 - 09:55
File harbour-jtox-1.4.1-1.armv7hl.rpm1.45 MB15/05/2022 - 23:23
File harbour-jtox-1.4.1-1.aarch64.rpm1.43 MB15/05/2022 - 23:23

* 1.4.1 - update toxcore to v0.2.18 and add SailJail support

* 1.3.3 - toxcore 0.2.7 + avatar support

* 1.3.2 - fix clipboard regression

* 1.3.1 - fix crash on empty string send, add multiline send support, fix send file full path bug

* 1.3.0 add file transfers, upgrade toxcore to 0.2.2

* 1.2.1 remove trailing whitespace from sent msgs

* 1.2.0 update toxcore to 0.2.0

* 1.1.4 new translation, qrcode sizing fix

* 1.1.3 upgrade to toxcore 0.1.11, fix dpi issues, add account import to initial page

* 1.1.2 upgrade to toxcore 0.1.10 (should lower network usage)

* 1.1.1 fix crashes, pending messages and multiline send bar

* 1.1.0 offline sending support

* 1.0.1 fixed unencrypted profile imports + various UI fixes

* 1.0.0 initial release


zipotron's picture

Thanks a lot for maintain it again !!!


Just a question, where to locate the .tox file for import an account?

Almindor's picture

Documents folder is searched by default and with jailsail is the only place that will be accessible.

zipotron's picture

I have a file "zipotron.tox" in my Documents folder, but doesnt appears... Shall the file have any especific name?

Almindor's picture

Damn you're right, I forgot to add the Documents folder permission to sailjail settings. Try with v1.4.2 now.

zipotron's picture

No problem! Those are normal live issues! Please ,upload the 1.4.2 and I will test it!

zipotron's picture

Hello! Please, could you provide a compilation for aarch64 of this amazing app? Is it opensource app? In this case could you share the code? Thanks!!!

Almindor's picture

Yes it's open source, repo is at https://github.com/almindor/harbour-jtox

zipotron's picture

Thanks a lot!

Just in case I can motivate you, please, dont let the project die, try to adapt for Sailfish 4.3 and provide new compilations (I would like to do it but I have not the knowledge yet), no new features, just keep it functional. Is sad to lost this kind of apps.

olf's picture

@zipotron, you do not need much knowledge, just motivation and organisation: https://github.com/sailfishos-chum/main#submitting-abandoned-software

But first check with @almindor that he really does not indend to mainain it any longer: A clear statement from him (here or at GitHub) will be helpful.

Almindor's picture

I won't be actively maintaining any of my Sailfish projects. Jolla has utterly failed and I don't have the time to keep up anymore. I'll happily accept PRs on github as long as the changesets make sense tho.

olf's picture

@almindor, this is a bit sad to hear, especially for Lighthouse.  But I understand your point and decision well.

Yet, I suggest to make a clear decision, because …

> I won't be actively maintaining any of my Sailfish projects. […]
> I'll happily accept PRs on github as long as the changesets make sense tho.

… how is this going to work?  I.e.:

  • How are you going to "passively maintain" these projects?
    Note that there are two open Pull Requests for Lighthouse at GitHub for long.
  • How are you going to check that the contributions are working fine, without time, without motivation and (maybe) without a well working SailfishOS device?
    Note that "I don't have the time to keep up anymore." and still being ready for checking changesets for correctness is a bit of a contradiction.

While I do understand the motion of not letting go, exactly this creates the unfortunate state of "half-maintained" source code repositories, which is problematic.

Technically anyone can clone ("fork", i.e., make an exact copy of) any of your git-repositories at any time, which includes all commit-history etc.: This is the way git and git-based source-forges (as GitHub) are designed.

Thus I suggest that you make a clear decision, if you want to continue maintaining your SailfishOS-oriented GitHub-repositories at least on a minimal level, i.e., properly reviewing, testing and commenting Pull Requests.

If you decide that you just want to have your code publicly available (so it can be reused), but do want to avoid the efforts of maintaining it, then I strongly suggest to put your source code repositories into read-only mode (GitHub calls that "archive mode").  Such a situation is exactly what the "archive mode" is for, as it technically forces people being interested in re-using this source code to clone an archived repository and to maintain it by themselves.  Note that "archive mode" is also easily and fully reversible, if you should change your mind.
Here is how to achieve that:

For each of your SailfishOS-oriented repositories at GitHub, do …

  • open your repository in a web-browser.
  • click on the “…” entry of GitHub’s menu bar (the rightmost one) and then on the drop-down entry “Settings” (the bottommost one).
  • on the “Settings” web-page, scroll down to the bottommost section “Danger zone” and click on “Archive this repository”.
  • Follow the instructions displayed to archive this repository.

Hope that helps ("HTH")!

P.S.: You might want to review and may merge the two open Pull Requests for Lighthouse at GitHub before archiving this source code repository.

zipotron's picture

I will try to get this motivation as soon as I get a bit of free time! Thanks!

delocoyo's picture

How is the development of this app?

as400's picture

JTox is great - thanks a lot ! Are you still working on a project ?

Almindor's picture

Mostly maintenance mode atm. I do want to get audio/video working at some point tho.

as400's picture

Great news. Do you think it might be possible to reduce battery use in the future ? I have read they are working on it in toxcore.

Mister_Magister's picture

What about loginning into existsing toxme.io account?

Almindor's picture

What do you mean by that? You can always re-register the same account at toxme from jTox.

Caballlero's picture

So pretty jTox, thanks.

geher's picture

Do you plan to make audio and video calls?

Almindor's picture

Eventually yes. It's on the roadmap just not sure how hard it's going to be. Main thing is adding the requirement libraries to the static build (unless they are part of Sailfish acceptable libs but I highly doubt that).


After that is a lot of fiddling to make sure the hw works ok with it.

tvicol's picture

Thank yuu for this update ! Looking forward to see file transfer and video/audio calls implemented.

I have also a name sugesstion, "Pufferfish" the most toxic fish on the planet, far more toxic than cyanide. ;)

Almindor's picture

I believe that's openBSD's maskot :)

I'll probably stick with jTox, it's short, memorable and contains "tox" so people find it easy.

paolomi's picture

Thanks for this update! I have a feature request: multiline! i.e. when you are writing a message longer than one line, the message must continue on the next line, but now it is on the same line... and it is more difficult to read in full.

Almindor's picture

Good point. If you think of anything else please make an issue on github. Helps me not forget and organize things.

Almindor's picture

I tested imports with qTox's profiles. It's possible Cyanide and uTox don't encrypt their profiles with password so they won't work with currenct jTox. I'll look into it and allow plain imports too in 1.0.1

tvicol's picture

Thanks ! This solved the import issue.

bhyoram's picture

Same here, can't import, even if movinf file to the needed directory, the format seems to be incompatible.

tvicol's picture

It's good to see another client. However, I would also suggest to merge with cyanide.

So far I can not import tox account from utox or cyanide.

bhyoram's picture

perhaps it will make sence to merge with cyanide, another native tox client, with some aleready implemented features