Troubleshooting
Fixes for the most common oxide-tablet problems — startup, opening the tablet, apps, home screens and saving, wallpapers, notifications, and settings.
Fixes for the most common problems, grouped by area. Most problems leave a clue in one of two places, so check them first:
- The server console: the window (or txAdmin's live console) where your server prints its messages.
- The F8 console: press F8 in game to open it. Messages from the tablet's screens show up here.
Lines from the tablet start with [oxide-tablet], or look like [WARN][oxide-tablet][...].
Startup Issues
Opening the Tablet
Apps
Home Screen and Saving
Wallpapers
Notifications
Settings and Configuration
General Debugging
Enable Debug Mode
Before the first start, set this in shared/config.lua:
Config.Debug = trueAfter the first start, run /tablet settings, switch to the Advanced tab, open Advanced, turn on Debug logging, and press Save Changes. It takes effect straight away.
With debug mode on:
- Extra lines starting with
[oxide-tablet]print to the F8 console, for example when the tablet opens or closes, when a resource adds an app (app registered: their_app (their-resource)), when a notification is dropped, or when a wallpaper image is skipped. - A Demo app and two demo widgets are added, so you can check the tablet works without any other resource. Install the Demo app from the App Store like any other app.
Turn debug mode off again on a live server.
Warnings That Always Print
These lines print even with debug mode off. Search the server console or F8 for them:
| Line contains | What it means | Where to look |
|---|---|---|
framework does not support usable items | o-link didn't find your framework | Everything behaves as if no framework is installed |
inventory cannot persist item metadata | Tablets can't get their own IMEI | Every tablet shares one home screen or has no IMEI |
app did not report ready | An app took too long to load | An app says it didn't respond |
home layout rejected, install list rejected, preferences rejected | A player's change couldn't be saved | Your home screen changes could not be saved |
setting is large enough that clients may not receive it | A setting is too big to send to players | A setting saved but players don't see the change |
refused a write before settings finished loading | A setting was saved while the tablet was still starting | settings are still loading, try again shortly |
client reported an unloadable model | A model is missing on a player's game build | A model warning mentions the tablet prop |
tablet settings denied (or wipe, notify) | Someone without admin permission tried an admin command | Admin Tools → Permissions |
Send Yourself a Test Notification
As an admin, type:
/tablet notify tablet_settings Hello from the serverA notification from the Settings app should appear: a banner if the tablet is open, or a bubble at the bottom right if it's put away. If it does, notifications work, and a missing notification from another app comes from that app or its install state (see Notifications).
Getting Help
If none of the above solves your problem:
Turn on debug mode and make the problem happen again.
Copy any lines mentioning oxide-tablet or o-link from the server console and the F8 console.
Note your framework (QBCore, QBX or ESX), your inventory resource, and your o-link version.
Contact Oxide Studios support with all of the above.