📱 General ☁️ Sync & Drive 🤖 AI & Processing 📝 Notes & Files 🔧 Troubleshooting ⚙️ Developer Mode
Common questions
What devices are supported?

Android — fully supported, available on the Play Store now. Requires Android 10+ with at least 4 GB RAM for on-device AI.

iOS & macOS — in development. Join the waitlist via the landing page to be notified at launch.

Windows, Linux, and Web — planned for a future release.

On-device AI (Gemini Nano) requires Android AICore support. See the full list of supported devices. If your device does not support it, AI features will gracefully degrade.
Is there a Mindverse account or server?

No. There is no Mindverse account, no Mindverse backend, and no Mindverse server. Your notes never touch our infrastructure.

The only external connection the app makes is to your own Google Drive when sync is enabled — using your Google account, not ours.

Does the app work offline?

Yes — fully. Notes, AI, transcription, tag generation, and Skills all work with no internet connection. Everything runs on-device.

Google Drive sync queues changes and uploads when connectivity is restored. YouTube and web link capture require internet at capture time.

Where are my notes stored on the device?

Notes live in the app's private documents directory as plain .md files with YAML frontmatter. Images go in an images/ subfolder; audio recordings go in audio/.

A lightweight SQLite index powers fast search and sorting — but the Markdown files are the source of truth. The index can always be rebuilt from them.

Google Drive backup
How does Google Drive sync work?

Mindverse creates a mindverse/ folder in your Google Drive and syncs all notes, images, and audio there as plain files. Notes are stored as .md files — readable directly in Google Drive without any app.

Sync is ID-based: each note has a stable Drive file ID, so renames do not create duplicates. Sync runs automatically in the background after any change.

Can I add .md files from my computer and have them appear in the app?

Yes — with a few requirements:

  1. Place the .md file inside the mindverse/notes/ folder in your Google Drive.
  2. The filename should follow the YYYY-MM-DD-HH-mm-title.md format (e.g. 2026-05-01-12-00-my-note.md). Files with different names still import but may sort incorrectly.
  3. Open Mindverse on your phone and trigger a manual sync from Settings → Sync.
  4. The note will download and appear in your library.
Files with YAML frontmatter (tags, category, created_at) will have their metadata preserved. Plain Markdown without frontmatter also imports fine — Mindverse will generate metadata on first sync.
Will deleting a note in the app delete it from Drive?

Deleting a note moves it to the in-app Trash. Notes in Trash are not immediately removed from Drive. They are deleted from Drive only when you permanently empty the Trash.

To keep a note in Drive but hide it from the app, archive it instead of deleting it.

Sync is stuck or not updating. What should I do?
  1. Pull down to refresh on the home screen to trigger a manual sync.
  2. Check that you have an active internet connection.
  3. Go to Settings → Sync and tap Sync Now.
  4. Sign out of Google Drive in Settings and sign back in to refresh the auth token.
  5. If sync still appears frozen, enable Developer Mode (see below), then use Sync (Dry Run) to diagnose, followed by View Sync Logs.
On-device AI
What AI runs on my device?
  • Gemini Nano — auto-tagging, categorization, AI Q&A, Skills. Choose between Stable, Preview, or Full in Settings → AI Model.
  • WhisperKit — on-device voice transcription (iOS/macOS). On Android, transcription uses ML Kit Speech locally.
  • ML Kit — OCR text extraction from photos, image labeling and scene recognition.

No data is sent to any external AI service. All inference runs locally.

AI processing is stuck or showing a spinner for a long time.

AI tasks have a built-in 2-minute timeout — after which the task is marked failed and the queue moves on.

  1. Wait 2 minutes. The task will time out automatically.
  2. Force-close the app and reopen it. The processing queue resumes automatically.
  3. If a specific note is stuck, open it and use the note menu to retry processing.
  4. As a last resort, enable Developer Mode and use Reprocess All Notes.
Gemini Nano has a rate limit. Saving many notes rapidly causes the queue to process them with ~30-second gaps between each. This is expected behavior, not a bug.
Tags or categories are wrong or missing.

Open the note, tap the three-dot menu, and select Reprocess. This re-runs tag generation and categorization via Gemini Nano.

To regenerate tags across all notes at once, enable Developer Mode and use Reprocess All Notes.

Voice transcription is slow or inaccurate.

Transcription runs fully on-device. On a modern flagship phone, a 5-minute recording typically transcribes in 30–90 seconds.

  • Record in a quiet environment — background noise degrades on-device models significantly.
  • Speak clearly with brief pauses between sentences.
  • After transcription, run the Clean Up Voice Note skill to fix formatting and minor errors.
Working with notes
Images are missing or broken after reinstalling the app.

Image paths in the index are absolute. After reinstalling, the app's documents directory path changes, breaking those references.

  1. Make sure Google Drive sync is enabled and all images are in mindverse/images/ in your Drive.
  2. Trigger a full sync from Settings → Sync.
  3. Enable Developer Mode and tap Rebuild Index. This rescans all files on disk and fixes broken path references.
I accidentally deleted a note. Can I recover it?

Deleted notes go to Trash first — they are not permanently removed immediately.

  1. Open the sidebar menu and tap Trash.
  2. Find the note and tap Restore.

If the note was already permanently deleted from Trash, check your Google Drive — the .md file lives in Drive's own Trash for 30 days before Drive removes it permanently.

Can I use Mindverse notes in Obsidian, VS Code, or other editors?

Yes. Every note is a plain .md file. Open the mindverse/notes/ folder in your Google Drive as a vault in Obsidian, or any other editor. Edits made outside the app sync back in on the next sync cycle.

Mindverse notes include YAML frontmatter with metadata (tags, category, created/modified timestamps). Obsidian handles this natively. Other editors show it as plain text at the top of the file.
Notes are showing up as duplicates.

Duplicates can appear if the same note was created on multiple devices before sync was enabled, or if the index lost track of Drive file IDs.

  1. Enable Developer Mode and tap Rebuild Index. The rebuild uses Drive IDs to deduplicate.
  2. Trigger a full sync after the rebuild.
  3. If duplicates remain, delete one copy manually — the other will persist.
Fixing common issues
The app is slow or sluggish with many notes.
  • Enable Developer Mode and run Rebuild Index — a fragmented index can slow queries.
  • Check if a background task (reprocessing or sync) is running — the status bar shows active tasks.
  • Restart the app to clear memory pressure from a long session.
Google Drive sign-in keeps failing or I'm signed out repeatedly.

Usually an OAuth token expiry issue.

  1. Go to Settings → Sync and tap Sign Out.
  2. Go to your Google Account security settings and revoke Mindverse's Drive access.
  3. Sign back in through the app — this issues a fresh token.

If the issue recurs, check whether Android's battery or data settings have restricted background network activity for Mindverse.

A Skill is not triggering automatically on save.

Auto-trigger skills join the background processing queue after save — they will not fire instantly if the queue is busy.

  1. Open the Skills screen, tap the skill, and verify Auto-trigger on save is on.
  2. Confirm Gemini Nano is available (Settings → AI Model should show a model, not an error).
  3. Wait for any other queued tasks to finish — the skill runs after them.
  4. If it never triggers, toggle the auto-trigger off and back on.
The app crashed and some notes no longer appear.

The notes are almost certainly still on disk — the index likely got out of sync during the crash.

  1. Enable Developer Mode and tap Rebuild Index.
  2. Pull down to refresh the home screen after the rebuild.
  3. If notes are still missing and Drive sync is enabled, trigger a manual sync — missing notes will re-download from Drive.
Knowledge Graph or Related Notes is not showing connections.

Relationships are built incrementally as notes are processed. After a bulk import or index rebuild, they may not yet be computed.

Enable Developer Mode and tap Rebuild Relationships. This runs across your full library and can take a few minutes. Once complete, related notes will appear on each note's detail view.

Power user & debug tools
How do I enable Developer Mode?
  1. Open the sidebar menu (tap the menu icon on the home screen).
  2. Scroll to the very bottom of the menu.
  3. Tap the version number (e.g. v1.0.0) 5 times rapidly.
  4. A password prompt appears. Enter iddqd (alternate: idkfa).
  5. The version label changes to v1.0.0 (dev) and new options appear in the menu.
Developer Mode is session-only — it resets when you close the app. Re-enable it each time you need it.
What tools does Developer Mode unlock?
  • Reseed Built-in Skills — restores or updates the default Skills. Use this if a built-in skill was accidentally deleted or you want new defaults after an app update.
  • Rebuild Index — rescans all .md files on disk and rebuilds the SQLite index from scratch. Fixes missing notes, broken image paths, and duplicate entries.
  • Rebuild Relationships — runs the Knowledge Graph algorithm across all notes to find and store cross-note connections.
  • Reprocess All Notes — re-queues every note for AI processing (tags, categories). Useful after changing AI model settings or after bulk import.
  • Sync (Dry Run) — runs the full sync logic without making any changes. Diagnose sync issues without risking data. Check logs afterward to see what would have changed.
  • View Sync Logs — opens a scrollable log viewer showing all recent sync and processing events with timestamps.
When should I use Rebuild Index vs Reprocess All Notes?

Rebuild Index is a structural fix. Use it when notes are missing from the list, images are broken, or the database is out of sync with files on disk. It reads existing Markdown files and rebuilds the SQLite index — fast (seconds), non-destructive, no AI involved.

Reprocess All Notes re-runs AI on every note — tags, categories, relationship mapping. Use it when metadata is stale, you switched Gemini Nano models, or you imported notes without metadata. This takes significant time on a large library and consumes Gemini Nano's rate limit, so avoid running it casually.