Setup hub
Home, Apps, Packages, Core, Manual, Settings. Start/Stop with a green lamp when the port is up. Searchable qpkg table. Themes: Aubergine, Midnight, Ember, Paper.
BerryCore v0.88.0 — setup hub + talkbutton
█▀█ █▀▀ █▀█ █▀█ █ █ █▀▀ █▀█ █▀█ █▀▀ ● ● █▀█ █▀ █▀▄ █▀▄ ▀█▀ █ █ █ █▀▄ █▀ ● ● ● █▄█ █▄▄ █ █ █ █ █ █▄▄ █▄█ █ █ █▄▄ ● ●
QNX userland · Term 49
Open Term49 and the setup hub is already running at
127.0.0.1:8098 — Apps, Packages, Core, Settings, and Talkbutton
dictation on the same aubergine brand as the splash.
The on-device hub is a product now — same aubergine as Term49, and it comes up when you open the terminal.
Home, Apps, Packages, Core, Manual, Settings. Start/Stop with a green lamp when the port is up. Searchable qpkg table. Themes: Aubergine, Midnight, Ember, Paper.
Play/pause dictation on the Passport. QSA mic, warm Vosk, transcript to the
clipboard and the Hub. qpkg install vosk then qpkg install talkbutton.
Official splash stays: white BERRYCORE, 7-dot berry, #300A24.
Every launch shows Running locally at 127.0.0.1:8098 and
setup boot brings the hub up if it is down.
BerryCore is a workshop for system fundamentals — the shell, the process, the packet, the compiler. The opposite is cognitive surrender: handing your will to a black box that thinks for you, locks the stack, and rents you back your own attention.
Never cognitively surrender your will. Learn the system.
Type the command. Watch the file land. Know what ran.
qpkg install, ssh, python3 — you operate the machine,
you do not rent an icon.
QNX, processes, packages, SSH, packets. If you can name the layer, you can change it. Fundamentals transfer to every system you touch next.
On-device AI, speech, and tools that still work when the cloud is gone. A model on the Passport is yours. A prompt in someone else's datacenter is not.
Compile a port. Read the source. Swap the binary. No store review, no permission slip. The device still belongs to you.
Whether you are setting up your first Passport or running a small fleet of BB10 devices, the SW7FT stack covers install, daily use, and remote coordination.
The on-phone runtime: updated binaries, qpkg packages, SSH tooling,
media utilities, and on-device AI. This is what you install on the handset.
Your Mac, Linux, or Windows control panel — discover devices on the LAN, push files, provision SSH keys, sideload BARs, and track new releases.
Explore BerryBridge →The public hub and fleet bridge — documentation, downloads, and a device messaging relay so BerryCore hardware can talk to each other from anywhere.
Explore the gateway →A typical path from zero to a working BerryCore device.
Grab berrycore.zip from GitHub or pull it through BerryBridge.
Transfer to the device, run install.sh, source env.sh.
SSH in, use qpkg, register with the gateway, and build.
Start with the install guide, or download the latest release and follow along in BerryBridge.