Review for version 1.12.0
Author’s rating: ★★★★★ · Author of this review
@nico.n
The phone holds its own connection to Signal, as a linked device does. Receiving survives a gap — messages wait on Signal’s servers and arrive when the socket is back — but sending cannot happen without it, so the composer refuses rather than taking a message that would quietly never go.
What you hit is a fault in how that was said, though. Every launch begins disconnected for a second or two while the socket reaches for the server, and the line you saw made no distinction between that and a connection that is not coming back. So a phone that was about to work told you it was broken. Version 1.20.13, out now, says “Connecting to Signal” while it is reaching, and keeps the blunter line for when it genuinely cannot.
If it ever stays on the blunt one, the thing to check is battery handling — the Kompakt ships with Duraspeed, and anything that stops the app running in the background takes the connection with it. Tell me what the Signal section of Settings says and I will dig in.
Thanks for asking; “why does it say that” turned out to be the right question.
@TechVampire
You are right that there was no way in, and right to refuse the other one — registering the number afresh deregisters Signal wherever else it is, and on the Kompakt that means starting the thirty days over. Don’t do that.
The obstacle is optical rather than anything else: linking is one Signal reading another’s code with a camera, and a phone cannot photograph its own panel. So version 1.20.13, out now, puts the code somewhere your phone’s camera can see it — the page this app already serves to your own computer. Open Link this phone as usual, and if Desktop Sync is on, the screen gives you an address. Open that on your computer, and point this phone’s Signal at the monitor: Settings → Linked devices → Link new device.
No second phone, no SIM moved, nothing about your account changed. The code is only on that page while the link screen is open, and it is behind the same token as the rest of Desktop Sync.
Thanks for reporting it clearly. It was a real gap, and the fix is better than what I first tried.
@superannette
Two separate things, and you found a real bug with the second one.
The name: in a group, a person was named from your address book, or from your one-to-one conversation with them if you had one — and if neither existed it fell through to their number. Which is exactly why one person in your group read correctly and another didn’t. Signal knows that person’s name; the app simply never asked for it. Fixed in version 1.20.13, which is out now.
The import, I can’t explain yet, and I would rather say so than guess. What I can say is that it should never have stayed silent: if reading the export failed, it was telling you the folder was wrong, and if it finished while the screen was away, it said nothing at all. Both are fixed. Now that version 1.20.13 is out, please try again — it will tell you what actually happened, and that will be the thing I can fix.
One thing worth checking meanwhile: the folder to choose is the one that directly holds main.jsonl. If you copied a folder across, that may be the folder inside the one you picked.
@kirkmahoneyphd
Your instinct is right: on a route between countries, holding to one message is sound. It is the split into parts that goes wrong out there, not the length.
But 140 is not a character limit. It is the byte limit, and plain SMS text packs eight characters into seven bytes — so one message is 160 characters, not 140.
The part that will actually be biting you: that limit is not fixed. One character outside the plain SMS alphabet re-encodes the whole message, and then a part holds 70 characters rather than 160. A curly apostrophe counts. So does an accent, a dash, an emoji. Most keyboards turn a typed ’ into a curly one by themselves, so this happens without anything on screen saying so — and your careful 140 becomes three parts on a route where parts are what fails.
Two things. Settings has “Strip accents from outgoing SMS”, which keeps you on the plain alphabet and the limit at 160 whatever your keyboard inserts. And version 1.20.13, out now, says it out loud: when a draft has re-encoded, a line above the composer tells you the limit just became 70, and the counter starts counting from the first character instead of waiting until you are nearly out.
The counter was never removed, for what it’s worth — it is QUIK’s, unchanged. It just had nothing useful to say at 140 of 160. Thank you for the report; it found a real gap.