This guide details the step-by-step process of setting up and utilizing the SMS Forge application.

Upon the first launch, the application will immediately request Superuser (Root) permissions. Grant Root: You must grant this permission via your chosen Root management tool (e.g., Magisk or SuperSU).

The most crucial step is identifying the correct communication path to your device’s cellular modem.

1. Navigate to the Basic Options (second tab).
2. Locate the Modem Selection section. The application automatically lists known and potential modem device paths.

Common Paths: These paths often depend on the device’s System on Chip (SoC):

• Snapdragon: Tends to use paths like /dev/smd*
• Mediatek: Often uses paths like /dev/at* or /dev/radio/at*

Since devices vary widely, you need to verify which path is active and compatible.

1. Select a Device: Choose one of the listed devices from the dropdown or input field.
2. Click “Verify” / “Check”: Tap the verification button.

Successful Verification: If the SMS Forge successfully communicates with the device using initial AT Commands, the device will be flagged as compatible in the list, and related information (if available) will be displayed. The App will remember this successfully verified device for future sessions. You can verify multiple devices. All successful paths will be saved.

If verification fails for all listed paths, it does not mean your device is incompatible, but that the App doesn’t recognize the specific path your manufacturer uses.

Action Required: If you cannot verify any device, please follow the steps in the Support & Troubleshooting section:

1. Go to Settings.
2. Enable Debugging/Logging.
3. Attempt the verification again.
4. Use the Send Report button located in the Settings Menu to automatically attach and email the generated log report to the developers for analysis. Your log help me identify new modem paths and others issues for future updates.

The basic functions are mandatory for any successful SMS Forge transmission.

⚠️ IMPORTANT: Pre-Purchase Compatibility Check
Before purchasing the Full Version, you must ensure your device is fully compatible.
Proof of Compatibility: Your device is considered fully compatible only if you have successfully selected and verified a modem (Section 2) AND successfully sent a basic, standard SMS through the application. If you cannot send a basic SMS, the full version will not work, you should see in Support & Troubleshooting section instead for support.

The application requires two mandatory elements for sending any message:

1. Verified Modem: A modem device that has been successfully checked via the “Verify” button.
2. Destination: Enter the recipient’s phone number. The App supports both:
   
   
   
   • International format (e.g., +34..., +1...).
   • Local format (without country prefix).
   • Contact Selection: You can also select the number directly from your device’s contact list (Address Book).

1. Message Body: Type your text in the main input area.
2. Send: Tap the Send button. (Note: In Limited Mode, this sends a standard SMS).

Once unlocked via In-App Purchase, the full range of controls becomes active across the Basic and Advanced tabs. The remaining features and settings are optional and subject to the user’s requirements.

• Message Class: Use the spinner to select the message class (e.g., Class 0 for Flash SMS, Class 1-4 for standard types), or select Substitution SMS.
• MWI (Message Waiting Indicator): Select whether to send an MWI message (used to light up the message notification icon), choosing between DCS (Data Coding Scheme) or UDH (User Data Header) methods.

• Silent Flag: When enabled, the SMS will be silent (depending on the recipient’s device interpretation).
• Ephemeral Flag: Designates the message as ephemeral (time-sensitive/temporary/autodeleted).
• Reply Path: Allows the recipient to use the same Service Center Address when replying.

Access these global settings via the Settings Button (top right corner):

• Service Center Address (SCA): Define the SMSC number.
• Validity Period (VP): Set the message expiry time (Absolute, Relative, or Enhanced formats).
• Reply Path (TP-RP): Configures the Reply Path requirement.
• Protocol Identifier (TP-PID): Set the specific protocol for the message.
• Message Reference (TP-MR): Define a unique reference number for the message.
• Status Report Request (TP-SRR): Request a delivery confirmation report.
• Duplicate Message (TP-RD): Flag to indicate a duplicate message.

For detailed definitions of all these terms, please consult the Core Concepts.

The Settings menu is divided into two main areas:

1. PDU Settings: (Described above, full version only).
2. Application Settings:
   
   
   
   • Language Selection: Choose the preferred language for the interface.
   • Color Scheme: Select a dark or light theme.
   • Debugging: Enable or disable logging. If enabled, the Send Report button will appear, allowing you to automatically attach and email the log files for developer analysis.
   • Reset Application: Wipe all saved settings and return the application to its default state.

The Unlock Button (left side, bottom bar) initiates the In-App Purchase process to upgrade to the Full Version and activate all PDU controls.

I’m constantly evaluating user feedback and technical capabilities to enhance SMS Forge. Future updates will focus on specialized and highly advanced functionalities, including, but not limited to:

• RAW PDU Input: Allowing users to construct and send messages using completely raw, custom PDU strings for maximum control.
• WAP Push SMS: Functionality to send WAP Push messages.
• Additional Advanced Features: Ongoing assessment for other specialized tools and protocol flags to be added in subsequent releases.

Of course, any suggestion will be heard, and if it is feasible and in line with SMS Forge’s philosophy, it will be considered.