Memory vault initialization timeout

[phpaulhanson-cmd]

Device: Red Magic 11 Pro (Snapdragon 8 Elite, 24GB RAM, Android 16
App version: 1.2.2 (from Play Store, after full reinstall)

Issue:

• After full reinstall, first chat + test phrase saves and loads on reopen (auto/manual).
• Second chat/new message → phrase does not survive reopen; vault initialization timeout returns.
• Manage tab in Memory Vault: "File not open".
• Logs show: "VaultHelper is not initialized. Call initialize() first...." after successful early writes.
• Clearing cache gives temporary new chats but corruption recurs.
• TTS auto-load ON always triggers timeout.

Steps to reproduce:

1. Reinstall app → choose Text + TTS setup.
2. Start chat, send test phrase, close/reopen → phrase visible.
3. Start new chat, send another phrase, close/reopen → timeout / phrase missing.

Expected: Chats persist across sessions reliably.
Actual: Vault degrades after first successful session.

Attachments: [attach your log screenshot if possible]

[Siddhesh2377]

This might solve the issue : https://github.com/Siddhesh2377/ToolNeuron/releases/tag/ToolNeuron-2.0.0

[phpaulhanson-cmd]

Hello, Thank you for you reply. I found it was a phone issue actually. My Red Magic 11 1b 24gb snap dragon phone was auto dumping the ram when I would swipe the app away. If I chose to force stop the conversation logs would then retain memory. It was not a Tool Neuron issue at all, I meant to drop an update sooner. Thank you for your reply!

…

On Sat, Feb 21, 2026, 12:16 Siddhesh ***@***.***> wrote: *Siddhesh2377* left a comment (Siddhesh2377/ToolNeuron#71) <#71 (comment)> This might solve the issue : https://github.com/Siddhesh2377/ToolNeuron/releases/tag/ToolNeuron-2.0.0 — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B6OXYADUJNKVMUS6EUEKYNT4NCVHPAVCNFSM6AAAAACVKBWWZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMZZGI3TKNBSGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Siddhesh2377]

ahhh no no it was also from TN now it is fixed !!!!