Device Power in Syllivo: Eco, Balanced, or Full for your phone
Published · Last updated
Part of the guide: On-Device Voice Guide
Device Power is the setting at the top of Syllivo's Settings that decides how hard voice generation pushes your phone. It is worth understanding before you blame a slow generation on your script or your voice choice: the same script, in the same voice, can run very differently under Eco, Balanced, and Full. If you have not yet picked a voice, start with choosing a voice by characteristic, and when you are ready to try a setting, open Studio and change it in Settings first.
One honest limit first
A browser cannot set an exact CPU percentage the way an operating system's task manager can. There is no browser control for "run at 40% CPU", so Syllivo does not show you a percentage, real or invented. What Device Power controls instead are the real knobs that decide how hard generation pushes a device: whether it uses accelerated graphics or plain software rendering, how many threads it uses, how many inference steps it runs, how large each chunk of audio is, and how long it pauses between chunks. Each mode below is a different combination of those knobs, and Settings shows the combination, not a fake number.
The three modes
- Eco — lightest load. Software rendering only, one thread, the lowest inference steps, the smallest chunks, and a pause between chunks. This is the slowest mode, and deliberately so: it is the mode that keeps an ordinary or older phone from hanging, and the least likely to make the page unresponsive. If your phone struggles, start here.
- Balanced — the everyday choice. Accelerated graphics when your device has it, software rendering otherwise, up to four threads, your own inference steps, and normal chunks. This is the default for most devices, and the right starting point if you have no reason to pick anything else.
- Full — full power. Accelerated graphics first, all available threads, higher inference steps, larger chunks, and no added pause. It is the fastest mode on a strong device, and the riskiest on a weak one: on a phone that cannot handle it, Full can heat the device or slow the page instead of speeding anything up. Choose it only on purpose, never as a reflex.
What the app picks for you, and what it never overrides
On first launch, Syllivo picks a mode for your device on its own: Eco for a weaker device, Balanced otherwise. Full is picked automatically only on a high-end device, meaning all three of these hold at once: 8 GB or more of memory, 8 or more processor cores, and accelerated graphics support. If any one of those is missing, Full is never chosen for you.
Once you pick a mode yourself, the app never changes it again on its own. Your choice wins over the automatic suggestion until you press "Use recommended for this device" in Settings, which is the one way to hand the choice back. That matters on a shared or borrowed phone: the mode you set stays set, so check it before a long session rather than assuming it is still the automatic one.
Which mode should you pick?
- Your phone feels slow, or the page has gone unresponsive during generation before: Eco. Slower is better than stuck, and Eco's single thread and pauses are exactly what keeps a weak device steady.
- A normal, modern phone, and you just want to get on with it: Balanced. It is the default for a reason, and changing it without a symptom to fix usually buys nothing.
- A strong phone, and you want the fastest generation it can give: Full, chosen deliberately. If the phone heats up or the page slows down under Full, that is the device telling you it is not a Full device: drop back to Balanced and treat that as the answer, not as a failure to retry.
A useful test is a short paragraph, not a long script. Generate one paragraph in the mode you are considering and watch what happens: steady progress and a responsive page means the mode fits; stuttering, heat, or an unresponsive page means it does not. Only then run the long script, as how on-device voice generation works also suggests for testing a voice: short first, long second.
If generation is still slow
Device Power is one cause of slowness, not the only one. Work through this order before concluding anything is broken: first drop to Eco and test a short paragraph, then shorten the script and split it into smaller pieces, and only then try a different voice. A long script in Full on a weak phone is the worst combination of all three choices, and fixing any one of them — usually the mode — is worth more than changing all three at once.
Frequently asked questions
What does Device Power actually change?
It changes the real knobs behind generation: accelerated graphics versus software rendering, thread count, inference steps, chunk size, and the pause between chunks. It does not set a CPU percentage, because a browser cannot do that, so no percentage is shown.
Will Syllivo switch my mode back automatically?
No. Once you pick a mode yourself, it stays until you change it or press "Use recommended for this device" in Settings. The automatic choice only applies on first launch, before you have chosen.
Why is Full not automatic on my phone?
Full is picked automatically only when all three high-end signals hold: 8 GB or more of memory, 8 or more cores, and accelerated graphics support. If any one is missing, only you can pick Full, and on a weaker device it may heat the phone or slow the page.
Should I always use Eco on an older phone?
If the phone has struggled or gone unresponsive during generation, yes, Eco is the right starting point. It is slower, but steadier, and a finished generation beats a stuck one. If Eco still struggles, shorten the script as well rather than pushing the mode higher.