MoloFolio

Molo Folio is a book-style foldable phone. Folded, it is a normal smartphone with one screen. Unfolded, it opens like a book and shows two apps side by side, so a player can read Messages on one half and scroll InstaPic on the other.

• 25+ apps: calls and video calls, messages with groups and voice notes, camera, social apps, bank, garage, services, weather, crypto, news and more.
• 13 languages: English, French, Spanish, Portuguese, Italian, German, Dutch, Swedish, Polish, Romanian, Czech, Turkish and Russian. Each player can pick their own.
• Any framework: ESX, QBCore, QBox or Standalone, detected automatically.
• A real 3D phone: it comes out showing the back, flips to the cover screen and the hinge opens with visible thickness. In the character's hand, the free half really rotates around the hinge.
• No database required: with oxmysql the tables are created on start; without it, everything is saved in a file.

What you need

• A FiveM server running ESX, QBCore, QBox, or no framework at all (Standalone).
• The two resources from your download: molo_phone and molo_phone_props.
• Optional: oxmysql. With it, data goes to your MySQL database. Without it, the phone stores everything in molo_phone_data.json. Migrating from LB Phone or Quasar does need oxmysql.

Step by step

1. Copy both folders into resources/ Put molo_phone and molo_phone_props in your server's resources folder. The 3D phone models live in their own resource so you can restart molo_phone without crashing players who are holding the phone.
2. Database: nothing to import With oxmysql the tables are created automatically on first start. If you prefer importing by hand, sql/install.sql is included.
3. Add the resources to server.cfg Place these lines after your framework, inventory and voice resources. The props must start first.

   ensure oxmysql          # optional, only if you use MySQL
   # ... your framework, inventory and voice resources ...
   ensure molo_phone_props
   ensure molo_phone

4. Make sure a phone item exists By default players need a phone item to open the phone. The accepted item names are set in Config.PhoneItems (default { 'phone', 'molo_folio' }). If your inventory has no such item yet, add one with the snippets below, or set Config.RequireItem = false so everyone can open the phone without an item.
5. Restart the server and open the phone Press F1 or type /phone. Players can change the key in FiveM Settings → Key Bindings. On start, the server console prints the framework and the integrations it detected.

Adding the phone item

Only add the item if your inventory does not already have one called phone. Keep it non-stackable: with unique phones, each phone item carries its own number.

ox_inventory (also QBox)

['phone'] = {
    label = 'Phone',
    weight = 190,
    stack = false,
    close = true,
    description = 'Molo Folio foldable smartphone',
},

QBCore (qb-inventory, ps-inventory, lj-inventory)

QBCore usually ships a phone item already. If yours does not:

phone = {
    name = 'phone', label = 'Phone', weight = 190, type = 'item',
    image = 'phone.png', unique = true, useable = false, shouldClose = true,
    description = 'Molo Folio foldable smartphone',
},

qs-inventory

Same fields as QBCore, in qs-inventory's items file. Set unique = true.

ESX (default inventory)

INSERT INTO `items` (`name`, `label`, `weight`) VALUES ('phone', 'Phone', 1);

The setup page: molo_folio_setup.html

Open the setup page →

Open it online with the button above (also included in your download as molo_folio_setup.html): pick your framework, language, app names, phone item, and media storage, and it writes your config.lua and the server.cfg lines for you, with the changed lines highlighted. Its Migration tab gives the exact commands for LB Phone or Quasar. The page runs in your browser and sends nothing anywhere.

Everything is in config.lua, which stays editable even with Cfx Asset Escrow. Restart molo_phone after a change. These are the options most servers touch, with their real defaults.

Basics

App names

The social apps show names players already recognise. Change any of them, give one name per language, or delete a line to use the built-in name (Pixa, Buzz, Loop, Flame, Shadow, Bazaar). Other apps can be renamed the same way: phone, messages, contacts, camera, gallery, mail, wallet, garage, services, maps, notes…

Config.AppNames = {
    pixa   = 'InstaPic',     -- photos
    buzz   = 'Birdy',        -- short posts
    loop   = 'Trendy',       -- short videos
    flame  = 'Spark',        -- dating
    shadow = 'DarkChat',     -- anonymous rooms
    bazaar = { en = 'Classifieds', fr = 'Petites annonces' },   -- one name per language
}

Battery and signal

Other scripts (power bank, charger) can recharge the phone with exports.molo_phone:ChargePhone(100) on the client.

Services and dispatch

Config.Services lists who players can call from the Services app. Each entry has an id, a label, the jobs that receive alerts, an icon and a color. Defaults: Police (police, sheriff), EMS (ambulance, ems), Mechanic (mechanic, bennys) and Taxi (taxi). Config.ServicesCooldown = 30 seconds between two requests from the same player, and alerts live for Config.ServicesAlertTTL = 3600 seconds.

Config.Services = {
    { id = 'police', label = 'Police', jobs = { 'police', 'sheriff' }, icon = 'shield', color = '#0a84ff' },
    { id = 'ambulance', label = 'EMS', jobs = { 'ambulance', 'ems' }, icon = 'medic', color = '#ff453a' },
    -- add your own: { id = 'lawyer', label = 'Lawyer', jobs = { 'lawyer' }, icon = 'pin', color = '#bf5af2' },
}

Video calls

Video calls go directly between players (WebRTC). The two public Google STUN servers in Config.VideoCalls.IceServers are usually enough. If some players get no picture, add a TURN server (Cloudflare Calls, Metered…):

Config.VideoCalls = {
    Enabled = true,
    IceServers = {
        { urls = 'stun:stun.l.google.com:19302' },
        { urls = 'stun:stun1.l.google.com:19302' },
        { urls = 'turn:your-turn-server:3478', username = 'user', credential = 'pass' },
    },
}

App settings

Each app has a small block you can adjust freely. The main ones:

Photos, videos and voice notes are uploaded by the server, so storage keys never reach players. Choose where they are kept with Config.Camera.Provider.

If the key for Fivemanage or Discord is not filled in, the phone falls back to 'local' by itself.

Public servers: set the media address

With local storage, players download photos from your server's address. When it cannot be detected, players on a public server see broken images. Add your public IP and port to server.cfg:

set molo_phone_media_url "http://YOUR_IP:30120"

You can also write it in Config.Camera.Local.BaseUrl. Left empty, the phone uses the Cfx address of a listed server, or 127.0.0.1 for a local test server.

Limits

MaxPhotosPerPlayer = 300, MaxVideoSeconds = 30, MaxUploadMB = 15 and MaxUploadsPerMinute = 12 per player, to prevent abuse.

Molo Folio looks for the resources below when it starts and uses the first one it finds. The server console prints what was detected, for example Banking: Renewed-Banking | Billing: okokBilling | Garages: jg-advancedgarages | Inventory: ox_inventory.

Forcing a bridge

If the wrong resource is picked, write its name instead of 'auto'. Voice is set with Config.Voice and vehicle keys with Config.Garage.Keys.

Config.Bridges = {
    Banking = 'okokBanking',
    Billing = 'auto',
    Garages = 'auto',
    Inventory = 'ox_inventory',
}

The bridge files (bridge/) stay open under Escrow, so you can adapt them to a custom resource.

One command in the server console (not in game) imports your players' data from LB Phone (v1 and v2) or Quasar Smartphone (qs-smartphone). It needs oxmysql and the same database as the old phone.

Commands

Type these one at a time in the server console (txAdmin Live Console or the FXServer window).

Safe procedure

1. Back up your databaseExport it from HeidiSQL or phpMyAdmin before anything else.
2. Install Molo Folio on MySQLKeep Config.Storage = 'auto' and start oxmysql before molo_phone.
3. Stop the old phoneRemove or comment its ensure line in server.cfg, but keep its tables in the database.
4. Run the dry runOn an empty server, in the console: molo_phone_migrate lb dry (or qs dry). Read what it found.
5. Run the migrationmolo_phone_migrate lb (or qs). Big servers can take a few minutes. If it stops, run it again: finished steps are skipped and it continues where it stopped.
6. Restart the phonerestart molo_phone so connected players reload their data.

What is migrated

Phone numbers

• Every character keeps their old number, so contacts and conversations still match.
• If the player already had a Molo number, or the old number is taken by another Molo player, the old data is attached to the right number.
• Quasar numbers are read from players.charinfo on QBCore / QBox, and from users.charinfo or users.phone_number on ESX.
• Unique phones (Config.UniquePhones = true): an LB phone item (lbPhoneNumber) or a Quasar phone item (phoneNumber) gets its number and data back the first time it is opened. A blank phone receives its character's migrated number once.

Other Quasar versions

Tables and columns are detected at runtime, and the dry run prints what it found. For qs-smartphone-pro or another version, add your table names in Migrate.QS at the top of server/migrate.lua (the file stays open under Escrow). If the dry run finds nothing, run molo_phone_migrate schema: it writes migrate_schema.txt with table and column names only, no player data. Send that file to support.

Each player can make the phone their own. With unique phones, settings follow the phone, not the character.

Control Center

Quick toggles for airplane mode, flashlight, silent mode, Do Not Disturb, dark mode and brightness.

Server exports

exports.molo_phone:GetPhoneNumber(src)
exports.molo_phone:GetSourceFromNumber('555-1234')
exports.molo_phone:HasPhone(src)
exports.molo_phone:SendNotification(src, { title = 'Bank', content = 'Transfer received', app = 'settings' })
exports.molo_phone:SendMessage('555-0000', '555-1234', 'Your package has arrived')
exports.molo_phone:GetBankBalance(src)
exports.molo_phone:TransferMoney(src, targetSrc, 500, 'Rent')
exports.molo_phone:SendMail(to, subject, body, sender)
exports.molo_phone:SendDispatch({ service = 'police', title = '...', message = '...', coords = coords, street = '...' })

Also available: AddWalletTransaction(...), SocialPost(...), SocialGetProfile(...).

Client exports

exports.molo_phone:IsOpen()
exports.molo_phone:OpenPhone()
exports.molo_phone:ClosePhone()
exports.molo_phone:GetPhoneNumber()
exports.molo_phone:SendNotification({ title = '...', content = '...' })
exports.molo_phone:ChargePhone(100)   -- power bank, charger...

Third-party apps (SDK)

Add your own app to the phone from any resource. It appears in the App Store under Third-party apps.

exports.molo_phone:AddCustomApp({
    id = 'my_app', name = 'My App', description = 'What the app does',
    icon = 'https://cfx-nui-my_resource/ui/icon.png',
    ui = 'https://cfx-nui-my_resource/ui/index.html',
    defaultInstalled = true,
})
exports.molo_phone:SendCustomAppMessage('my_app', { type = 'update', data = {} })
exports.molo_phone:RemoveCustomApp('my_app')

In your app's HTML, load the SDK:

<script src="https://cfx-nui-molo_phone/html/sdk/molo-phone-sdk.js"></script>

It gives you MoloPhone.onReady, MoloPhone.onMessage, MoloPhone.notify, MoloPhone.pickMedia, MoloPhone.contacts and MoloPhone.close.