Key Takeaways
- SMS send/receive, notifications, and battery exemptions are the production trio. Denying one looks like an API outage.
- OEM “battery optimization” and autostart screens are not in the Play permission dialog. Skip them and overnight OTP dies.
- Notification access is for inbound/status surfaces — confirm current behavior in the install guide, not a guessed SDK.
- Revoking SMS after pairing does not politely queue forever. Jobs fail at the radio.
- You still bring the phone and operator credit. Permissions do not change device-plus-volume pricing.
An android sms gateway permissions guide is a first-launch and OEM document, not a second OpenAPI. If SMS is denied, the radio is a brick. If notifications and battery are denied, the radio sleeps and your dashboard still looks “paired.” Start with install and first launch, then device setup.
Product: how the gateway works. You bring the Android and operator credit. Devices and send volume.
Grant · then OEM battery
Play dialog “Allow” is half the job. Xiaomi/Oppo autostart is the rest.
Why the app asks
The handset is a modem. Sending SMS, reading inbound for two-way, and showing status need OS grants. This is not a spyware pitch — it is the minimum to be a radio. Two-way inbox. Confirm current prompts on a spare phone before a fleet. Developer Center owns HTTP fields, not Android runtime permissions.
A paired device with SMS revoked is a polite lie. The API will take the job. The SIM will not.
Permission matrix
| Grant / setting | Needed for | If denied | Related |
|---|---|---|---|
| SMS send / receive | Radio path | Jobs never leave | First launch |
| Notifications | Operator-visible status | Silent failures overnight | Notification access |
| Ignore battery optimizations | Unattended send | OEM kill after 20 minutes | OEM restrictions |
| Phone / default SMS (version-dependent) | Some OEMs for send | Intermittent send | Retest after OS update |
OEM extras that are not Play permissions
Autostart, locked apps, “intelligent power,” dual-app clones. App uptime. After every OS update, re-canary. Updating without breaking pairing. Work profiles: multiple profiles caution.
What breaks when you revoke
Revoke SMS: outbound dies. Revoke notifications: you miss inbound/DLR UX. Battery restricted: queue depth climbs while pairing looks green. Incident response. Canary on a cold handset after any grant change. Real-handset tests.
SMS Retriever on the receiving app is a different Google API (SMS Retriever). Do not mix it with gateway send grants.
Fleet and work-profile caution
MDM that strips SMS will “secure” you into an outage. Tablets vs phones: tablet vs phone. Isolate OTP devices so a marketing handset’s permission experiment cannot starve auth. OTP. Consent/STOP still apply on promo. Messaging practices.
Next steps
Spare phone: first launch, OEM battery, SMS canary, then a second canary after reboot. Install the app. Spend 300 lifetime SMS proving grants before customer traffic.
Related product pages
Jump to the live product docs for this topic—not another long-form article.
- device and SMS volume pricingPlans and allowances
- Android SMS gateway product guideDefinition, product, and how to buy
- SMS API documentationLive endpoint reference
- download the Android gateway appGet the APK
