Manage the app
Troubleshooting
Keep the current data and working connection while you check the specific stage that failed.
In the appYou → FAQs · AI connection · Data and backups
My account is connected, but a model request fails.
Use Check connection, review Connection details, and select another model returned for that account. Identity verification and inference are different checks. Account/model eligibility, web-search access, plan limits, or workspace policy can still block a request. Review the connection flow.
The browser finishes, but MeBot does not reopen.
Use Open MeBot or Android recent apps. If Android killed the app or the attempt expired, start a fresh sign-in. Do not copy callback URLs or authorization codes into a support issue.
I reached a plan or capability limit.
Open Manage usage and review the provider’s controls. Automatic AI can pause while public-source updates continue. Raising the local cap or choosing Unlimited cannot bypass upstream limits. A deliberate retry is available after the underlying limit is resolved.
My API key or personal service does not connect.
Check the selected route, model ID, project access, and provider billing. My service needs its separate service token and matching server model, not a provider key in the token field. Its URL must be public HTTPS; localhost and private/LAN hosts are unsupported. Failed replacement attempts keep the previous working connection.
The feed has few stories.
Enable the modules you want, inspect their focus/preferences and AI connection, then refresh. Most modules need connected AI or configured feeds. Weather needs a recognizable place; Horoscope needs a sign. A provider can return no suitable supported sources rather than a padded result.
Recommendations do not fit me.
Review confirmed notes and their module permissions under You → My context, then tune the module’s topic and preferences. A general default cannot infer your qualifications, budget, subscriptions, or precise location. The context guide shows a focused approach.
A story suggestion still seems off.
Optional AI story-fit is guidance, not a guarantee. Review the source, adjust a confirmed note or module focus, and use Relevant / Not relevant if you want to steer that module. You can keep using public sources without AI.
A forecast or event disappeared from my feed.
MeBot removes expired source-verified forecasts and event listings from active reading so they are less likely to look current. Unknown dates remain unknown. This does not delete saved or starred stories; open Saved or Starred to find items you kept.
An explanation stops mid-answer.
The story remains readable. Check the connection and request allowance, then retry. Partial text is not a completed cached answer. The original source is still available if the provider cannot finish.
Search is disabled or returns no results.
Connect AI, enable a supported factual module, enter a query, and submit. Weather and Horoscope are excluded. Search returns up to eight results; no matching supported source is a valid empty result. Try a clearer query or different module selection.
An image or source page will not load.
Cached story text may remain available. Check connectivity and retry the original source. Publisher restrictions, removed pages, and unavailable image metadata can prevent media display. MeBot does not bypass paywalls.
Can signing in automatically import my ChatGPT memory?
No. The account integration does not expose conversations or saved memory. Use Prepare in ChatGPT, review the resulting context JSON, then import or paste it. You choose what transfers.
My context JSON is rejected.
Use mebot-context-v1, correct field types, unique note IDs, supported scopes, and a valid timezone or blank value. Files are limited to 512 KiB, pasted text to 131,072 characters. A ChatGPT export ZIP or full feed backup cannot be imported as context. Open the empty valid example.
After import, I do not see my notes.
After you confirm a reviewed import, MeBot returns to You → My context and shows the saved notes. Cancelling review or correcting invalid input leaves the current draft. See the import guide.
Background updates do not arrive at an exact time.
Android scheduling is approximate. Check Allow background updates, notification permission, per-module alerts, quiet hours, and whether new content is eligible. There is at most one feed digest per local day. Quiet hours suppress notifications, not all retrieval.
A save or restore reports a storage error.
Do not erase data as the first recovery step. Check available device space, keep the existing data, and retry. Use You → Data and backups → Troubleshooting when available. An invalid import must not replace current data.
My alarm is silent.
Test bundled Pulse. Check saved alarm volume, the phone’s alarm stream, Do Not Disturb, output route, and the setup access for Exact timing, Notifications, and Lock screen. Check manufacturer battery restrictions and run Test in 10 seconds with the screen locked.
My chosen file plays in preview but not after a restart.
Use a file stored locally and reselect it if its provider or permission changed. Before first unlock, custom files may be inaccessible; the alarm falls back to bundled Pulse. Backups include a URI, not audio bytes or file access grants.
The tone plays, but the spoken message does not.
Enable Spoken wake-up message and check for an installed offline voice in the chosen language. Scheduled speech waits for the volume ramp, with at least 1.5 seconds of delay. The tone continues when voice is unavailable.
Android says the update cannot be installed.
Check Android 8.0+ support, the downloaded file, available space, package identity, and signing certificate. Release and debug are separate apps. A different signing key or lower version cannot replace the installed release. Export data before deliberately changing installations; do not uninstall as a routine update fix.
Why is an older version unavailable?
The download page links only files verified as part of a public release. Some early releases have no recoverable public APK. Do not substitute an unverified download from another source.
Include the MeBot version, Android version, device model, connection route, safe error stage/code, and steps using synthetic data. Say what you expected and what happened. A small, nonprivate screenshot can help.
Never post API keys, OAuth callback URLs/codes, personal exports, private responses, or signing material. Security-sensitive reports follow the security policy; ordinary bugs can be filed in GitHub Issues.