Mobile App

This page covers the issues most often reported with the Snippbot mobile app, with a symptom → cause → fix layout so you can jump straight to what you’re seeing.

Text is cut off across the whole app (Android)

Symptom. On Android — most commonly Samsung phones — text is clipped everywhere in the app:

Single-line labels lose their last character: dark shows as dar, medium as mediu, Theme as Them.
Wrapped text, like a chat message, loses its whole last line.

The tell-tale sign is that it’s always exactly one character too short on a single line, or one line short when the text wraps. It happens on every screen, not just one.

Cause. This appears when your phone’s system-wide Bold font accessibility setting is turned on. Android applies the bold styling when it draws the text, but the app reserves space based on the regular (non-bold) font. Bold letters are slightly wider, so the text draws past the edge of the space set aside for it and the last bit gets clipped. It’s a known Android limitation that affects many apps, not just Snippbot.

Fix. Turn off the system Bold font setting. On Samsung:

Open Settings on your phone.
Go to Display.
Tap Font size and style.
Turn the Bold font toggle off.

Text stops being clipped immediately on every screen — no app restart needed. On other Android phones the setting lives in a similar place, usually Settings → Display or Settings → Accessibility, under a Bold text or Font option.

The model picker is missing newer models

Symptom. The model dropdown shows only a short list, or is missing models you know your daemon supports.

Cause. The app loads the current list of models live from your daemon. If it can’t reach the daemon — because the daemon is stopped, the connection settings point at the wrong address, or the device pairing has expired — the app quietly falls back to a small built-in list so you can still pick something. That fallback is what you’re seeing.

Fix.

Make sure your Snippbot daemon is running.
Open the app’s connection settings and confirm the daemon address is correct — the right host, port, and http/https for how you reach it. See Connection & Auth.
Check that the connection status shows Connected. If it shows an error or the pairing has expired, re-pair the device.
Reload the app.

Once the app can reach the daemon again, the full, up-to-date model list loads automatically.

I changed the model but replies still come from the old one

Symptom. You selected a different model, but responses seem to keep coming from the previous one, or your change doesn’t seem to take effect.

There are two common causes.

The daemon is running older code

The mobile app is only the front end — the actual work runs on your daemon. After you update Snippbot, the daemon keeps running the old code until you restart it. Reloading the mobile app is not enough.

Fix. Restart the daemon so it picks up the new version:

snippbot stop && snippbot start

Then reload the mobile app.

You’re judging by what the reply says

Language models are unreliable narrators about their own identity. A model will often name a different version than the one you actually selected — its own name may not have existed yet when it was trained, so it guesses. Asking “what model are you?” is not a reliable way to check which model is in use.

Fix. Trust the model you selected in the picker, not the name the reply mentions. The model that actually answered is the one the server routed your request to, regardless of what the text claims. If you want to confirm a switch really happened, compare the behavior or response quality rather than asking the model to name itself.

The app works at home but not when I’m out

Almost always one of three things, in order of likelihood.

Remote access is off

On your own network the app reaches the daemon directly and needs no tunnel, so this only shows up the moment you leave. Turn it on in Settings → Remote Access — see the guide.

The phone only knows your local address

If you paired before turning remote access on, the app only ever learned a 192.168.x.x address, which is unroutable from outside. Turn remote access on, then re-pair by QR so the phone picks up both addresses.

The tunnel didn’t come back after a restart

Tunnels stop when the daemon stops. Turn on Reopen on restart under Settings → Remote Access → Advanced so it comes back by itself.

To check quickly: open Settings → Remote Access on the desktop. If it says Tunnel up with an address, the daemon side is fine and the problem is on the phone — re-pair. If it says Tunnel down, start there.

Still stuck?

See the general FAQ and Common Errors, or the Debug Guide for deeper diagnostics.