Skip to main content

Omi device on - no transcription or "ask Omi"

Bugs & ErrorsHigh PriorityAndroidOmi CV1 Device

Everything was working perfectly till September 27th.

I noticed on the 28th that my phones battery had gone into “power savings mode” (s24 ultra) - this was then turned off.

No damages have occurred to the device.

It is not muted and no settings have been changed.

All tasks have disappeared, the “ask Omi” does not work, device is powered and connected but doesn't show any transcriptions.

There are also over 2000 pending audio to be processed and regardless of Bluetooth or wifi connection i have watched it complete to 100% and watch as nothing changes.

Currently the device seems to be possibly recording, light is blue and connected, but nothing occurs

What are the correct steps to trouble shoot this issue to figure out what has occurred?

Please see the attached screenshots.

Posted by Jonathan Praeger ·
Status: Completed4 comments

Log in to comment and vote

Comments4

  • L1 Support Team - Omi AI

    •

    Mar 2

    Hello! This looks like an authentication/session issue, the MCP error ("Invalid authentication credentials") is the key clue. Your session token likely expired or got corrupted, which would explain why everything stopped working at once: no transcription, no Ask Omi, no task processing, pending audio stuck. Try these steps in order:

    1. Force sign out and sign back in

    → Gear icon → Profile → scroll to bottom → Sign Out → Sign back in with the same account → This refreshes your authentication token, which should fix the MCP error and restore all features

    1. If sign-out doesn't work, clear app data

    → Phone Settings → Apps → Omi → Clear Cache first, then try → If still broken: Clear Data (this resets the app but your conversations are stored in the cloud, so nothing is lost) → Reinstall the app if needed → Sign back in

    3 - For the 2000+ pending audio files

    → After signing back in, go to the sync page

    → Try syncing via Bluetooth (more reliable than Wi-Fi) → Let it complete fully — this may take a while with 2000+ files → If it completes to 100% but nothing processes, the auth fix from step 1 should resolve that since the server was rejecting your credentials

    4- Check battery optimization

    → Phone Settings → Battery → App battery usage → Omi → set to Unrestricted → This prevents power savings from killing the app's background services again

    The root cause is likely that when your phone went into power savings mode, it killed the app aggressively, which corrupted the session token. Everything downstream (transcription, AI chat, task processing, sync) depends on valid auth credentials.

    Start with step 1 — if the MCP error goes away after re-signing in, everything else should follow.

  • Jonathan Praeger

    •

    Mar 2