Feedback & bug reports

TalX is developed by a single person and tested on two devices. Android is not a uniform platform – much of it only shows up on a device that is not in this cupboard. Every usable bug report saves hours.

A good report in four sentences

What happened. What you expected. How to reproduce it. On which device.

The builder below asks for exactly that and formats it into a text you can copy and send.

Nothing is submitted from here

This page has no form that sends data to a server. The report is assembled exclusively in your browser. It only leaves your device once you copy it and send it yourself, over a channel you choose.

Short headline

What happened?What did you expect?How can it be reproduced?

DeviceAndroid versionTalX version

Assemble the reportReset

Please do not include

Finding a bug needs no content. Before sending, please check that none of this is in the report:

• message texts, photos or files from real conversations
• names and profile pictures of other people
• safety numbers, pairing codes or connection handles
• your backup passphrase or TOTP codes – never, under any circumstances
• screenshots with visible chat content; black them out first

What does help: the sequence of events, the transport path used, the device model, the Android version, and whether it is reproducible.

Found a security problem?

Then please not in public. Report it confidentially first, using the contact route in the legal notice, so that a fix can ship before the description is circulating.

Helpful in such a report:

1. What an attacker can achieve with it – reading along, altering, blocking, defeating a check?
2. What they need for it – proximity, the same network, control of the brokering, physical access, a rooted device?
3. A way to reproduce it.
4. The affected app version.

You will get a reply as soon as the point has been assessed. What comes of it then lands traceably in the audit findings – like every finding so far, including the uncomfortable ones.

There is no bug bounty programme; TalX is a private project with no budget for one.

Before you report: a quick look

The most frequent reports are not bugs but explainable behaviour. A glance at the frequently asked questions is worth it – especially for:

What you see	Explained there
The tick does not appear	It only comes with the recipient’s confirmation – in groups, from everyone
Messages arrive late	Usually the manufacturer’s battery optimisation kills the background service
No nearby device found	Bluetooth, permission, Play Services, the “offline connections” switch
A warning about a key change	Usually the other side reinstalled
Nothing arrives after a reboot	The service is not allowed to start by itself from Android 15
No “translate” under a message	Too short, same language, or the language is not supported

What else you can contribute

• Test on unusual devices. Especially manufacturers that kill background services aggressively.
• Check translations. 91 languages have been machine-verified – but nobody speaks them all. A note about an awkward phrasing is welcome.
• Check this website. Unclear passages, wrong statements, broken links.
• Spread the word. A messenger without a directory lives on two people installing it at the same time.

And if you would like to support the project financially: support the project.