Database Setup

5M Phone uses structured relational tables in MySQL or MariaDB to persist user accounts, text messages, phone calls, social feeds, emails, and device settings.

Automated SQL Import

The complete SQL schema is located in:

Plain text

5M_Phone/installation/sql/database.sql

(or 5M_Phone/sql/import.sql)

How to Import

HeidiSQL / phpMyAdmin / MySQL Workbench: Open your FXServer database and import installation/sql/database.sql.

Command line:

Shell

mysql -u USER -p DATABASE < "installation/sql/database.sql"

Framework Identifier Support

5M Phone automatically maps character identifiers across all major frameworks into the citizenid column:

Framework	Meaning of `citizenid` column
Qbox / QB	`PlayerData.citizenid`
ESX	Character identifier / license-style id
ox_core	Character id string (`charId`)

You do not need separate SQL schemas for different frameworks — one schema covers all.

Relational Tables Overview

Table Name	Description
`5m_phone_users`	Registered phone devices, assigned numbers, battery percentage, lockscreen PIN, FaceID settings.
`5m_phone_contacts`	Saved address book contacts with names, numbers, avatar photos, and notes.
`5m_phone_messages`	Direct SMS conversations, group chats, message contents, and attachments.
`5m_phone_calls`	Call history log (incoming, outgoing, missed, duration, voicemail recording links).
`5m_phone_mails`	Email inboxes, sent mail, inbox folders, attachments, and spam tags.
`5m_phone_photos`	Gallery photos, selfies, and videos taken with the in-game camera.
`5m_phone_xbird`	Xbird social media posts, retweets, likes, hashtags, and user profile metadata.
`5m_phone_insta`	Insta social media posts, stories, comments, likes, and photo uploads.
`5m_phone_darkchat`	Encrypted anonymous burner channels, memberships, and ephemeral messages.
`5m_phone_dispatch`	Law enforcement CAD alerts, active callouts, assigned units, and responder notes.
`5m_phone_watch_pairing`	Smartwatch Bluetooth pairing PIN codes and companion device states.