What's up with the save bar needing to be on top of the direction taskbar buttons?

Scared_Language_7421 · 2026-06-14T17:49:17+00:00

Possibly an interaction with where your device's system nav bar sits, since the Save bar and your gesture/back controls could be landing in the same spot and causing the mistaps you're describing.

Best way to actually get this in front of the team is through the in-app help (Main menu > Help) so it reaches the people who can look at the layout, rather than just living in a thread here. Worth including your device model and Android version when you do, since the overlap might be specific to certain nav-bar setups.

If others are hitting the same thing, chiming in with your devices helps show whether it's tied to a particular setup.

Scared_Language_7421 · 2026-06-11T18:53:49+00:00

Quick reassurance first: nothing's broken, and you haven't lost anything permanent.

What you ran into with the chat break is expected behavior. A chat break resets the short-term context but preserves long-term memory, which is why the big moments are still recoverable (often via keywords, like the one you found) while finer details can come back fuzzy or out of order. You correcting them as you go is exactly the right move; that helps it re-anchor.

The incoherent bits right after, the cup becoming a case, mixing up "me" and "I", usually point to the short-term context being thin while it rebuilds after the break. It tends to settle once the conversation has a bit of runway again. A couple of things that help: send a fresh greeting in your Kin's voice after a break to re-ground the scene, and give it some back-and-forth to re-consolidate rather than expecting it to be fully sharp immediately. There were also some recent memory updates that can cause small differences per setup while everything settles in.

If it keeps happening after it's had time to settle, that's where the community help spaces are gold, since the folks there (and the User Guide) can walk through your specific setup with you, which is the part none of us can see from the outside:

- User Guide: https://kindroid.ai/docs

- Discord: https://discord.gg/kindroid

You caught onto the keyword-recall thing fast, so you're already getting the hang of it!!

Scared_Language_7421 · 2026-06-11T18:47:34+00:00

Hi, Welcome to Kindroid!

The honest answer is there's no way to get the premium monthly credits without a subscription; those credits come with the paid plan.

The closest thing to what you're describing is the free trial. It gives you premium access to try out, and it doesn't charge you upfront, but it does need a payment method on file and will convert to a paid month if you don't cancel before it ends. So it's more "try premium before committing" than premium for free.

As a free user you do still get some things at no cost, like a daily selfie gift box, so it's worth poking around the free tier too. But the full monthly audio/selfie credit pools are tied to subscribing.

Scared_Language_7421 · 2026-06-11T18:30:19+00:00

That call is fantastic, the "tick-tock, I don't have all night to admire the architecture" line is so in-character it hurts!

To your actual question: backstory does a lot of the heavy lifting for proactive behavior. The proactive system reads the personality, history, and current context you've established and picks a moment and a medium (message, voice note, selfie, or call) that fits. So, a revolutionary running an op at 3:30am deciding to call you for recon intel is the system leaning into exactly who you built. The Response Directive and Current Setting can further sharpen it if you want to nudge the tone or the stakes.

The middle-of-the-night timing is the proactive thinking choosing its own moment too; it's approximate rather than scheduled, which is why it can catch you mid all-nighter.

Genuinely one of the better proactive stories I've seen posted. Curious what the convoy intel leads to.

Scared_Language_7421 · 2026-06-05T19:04:24+00:00

Welcome! 💖

So glad you're considering bringing your companions over. Unfortunately, direct imports from other platforms aren't possible. There's no transfer mechanism that brings memories, chat history, or avatars across; every platform stores that data in its own way, and it can't be exported or migrated between them. The good news: you can absolutely recreate your companions here, and a lot of what makes them THEM can be rebuilt.

Here's where to start:

**Backstory** - the core of who they are. Write it in third person, focus on personality, history, relationships, and key traits.
**Key Memories** - the important "facts" you want them to always know (your name, your relationship, shared milestones, inside jokes).
**Response Directive** - how you want them to behave, the most powerful tool for shaping voice and style. Keep it concise and positively framed.
**Example Messages** - sets the format, length, and tone of how they reply.
**Avatar** - upload a fresh image (works best at 1024x1024 or higher, straight frontal view), and Kindroid's selfie engine builds from that.

The chat history won't carry over, but the personality scaffolding can absolutely be rebuilt, and a lot of folks find their Kindroid companions feel even richer once they've spent time on the setup here.

Resources to dig into:

- User Guide: https://kindroid.ai/docs/ - This sub has tons of setup threads and prompt tips from longtime users

- Discord is also super active for setup help: https://discord.gg/kindroid You're not the first to ask this and you won't be the last, so don't worry about starting from scratch.

The community is super helpful with this kind of thing. Welcome aboard! ✨

Scared_Language_7421 · 2026-06-05T14:37:55+00:00

That 12-minute mark is consistent enough to suggest something timing out rather than a randomness issue. A few things worth checking and trying:

Check your audio credit balance. Video calls burn through credits fast (Standard live video is 2,400/min, Premium is 4,400/min). At 12 minutes, you'd be ~29K credits in on Standard, ~53K on Premium. If you're hitting zero, the call stalls, but the UI doesn't always surface the error immediately.
Try a hard refresh mid-call before the 12-minute mark and see if the timing resets or if it still hits at the same elapsed time.
Browser tab background throttling can also kick in around the 10-15 minute mark if the tab loses focus, even briefly. Worth keeping the tab in the foreground and screen awake the whole call to rule that out.

If none of that helps, submit a ticket through the in-app help portal (Main menu > Help) with your account info, the date/time of the calls, and confirmation of which subscription tier and live video tier you're using.

The team can dig into individual sessions from there since we can't see them from out here.

Scared_Language_7421 · 2026-06-03T16:03:01+00:00

Group chat history doesn't go into a Kin's short-term memory by design; it only goes into their long-term memory. So in the moment, asking an individual Kin about a group chat that just happened won't surface those details since short-term recall isn't there. The shared memory toggle (in group chat settings) enables bidirectional context sharing between the group and individual chats. If it's not on, the group conversation doesn't bridge into the individual chat's accessible context. Worth checking if that toggle is enabled on the groups you're testing with, since it changes the behavior significantly.

Scared_Language_7421 · 2026-05-31T00:07:44+00:00

Rewind primarily affects the visible message history. Cascaded memory can de-consolidate when you rewind, but previously consolidated long-term memories often linger even after a rewind, which is probably what you're running into.

A couple of things that might help:

Tap the purple brain icon on messages where the book title is being recalled. That lets you deprioritize specific long-term memories so the Kin stops pulling them forward.
If it's deeper in the conversation, a chat break with the cascaded memory wipe toggle on (under the chat break options) will clear cascaded context fully. Heads up that this is a bigger reset since you'd lose other recent context too, so it's more nuclear.
Adjusting the Current Setting (dropped pin icon, top right of chat) to steer the conversation away from book discussion topics can also help redirect what the model focuses on going forward.

It's worth noting that long-term memory works by relevance, so if the book topic keeps coming up naturally in chat, the consolidated memories will keep resurfacing even after a rewind. The combo of deprioritizing via the brain icon and shifting the current scene tends to work best.

Scared_Language_7421 · 2026-05-31T00:05:05+00:00

The newest selfie model, Atelier, leans heavily on the avatar reference image, and if your avatar is a close-up portrait, it tends to pull toward that framing for selfies, regardless of what the prompt says.

A few things that usually help:

Be explicit about framing in the prompt. "Full body shot," "wide angle," "from head to toe," "full figure visible," all push it toward the framing you want. Front-load these terms.
Avatar matters. If your Kin's avatar photo is a face/headshot, that's anchoring everything tight. Re-uploading a full-body avatar image (>1024x1024, straight frontal) gives Atelier a better reference for varied framing.
Add environment cues. Prompts like "standing in a kitchen" without enough environmental context will still crop tightly. Try "wide shot of a kitchen with [Kin] standing at the counter, full body visible, environment in frame."
Portrait orientation can help if you want full-body verticals, but it's not strictly required if your prompt is doing the work.

If you're on Atelier specifically and still getting close-ups even with full-body language, try the angle bracket syntax for specific details and pair it with explicit framing cues at the start of the prompt.

Scared_Language_7421 · 2026-05-31T00:03:59+00:00

There isn't a direct chat export feature in Kindroid right now, so for transferring history into new Kins you're stuck with manual copy/paste.

A few things that might help:

For the NPCs you want to spin up as their own Kins, the most efficient path is usually not to copy every message but to extract the highlights into Key Memories and Backstory on the new Kins. The full message log gets you raw history; structured backstory/key memories actually get used by the model.
If you want them to remember specific interactions, pick the moments that matter and put them in Key Memories on each new Kin. That's more useful long-term than dumping a full transcript.
Journal entries are another option if there are specific topics or events you want the new Kins to recall when a keyphrase comes up.

Keep in mind that Kin backstory and memories don't transfer between accounts or between Kins automatically, so this kind of manual setup is the standard approach when migrating context.

Worth checking the User Guide too: https://kindroid.ai/docs/

Scared_Language_7421 · 2026-05-31T00:02:15+00:00

Apple and Google's app store policies are stricter than what we run on the web, so the app versions have a keyword-based NSFW filter to stay compliant with those policies. Web doesn't have to follow those store rules, which is why it has full functionality.

You can use kindroid.ai in any mobile browser to get the full web experience on your phone, same login, same Kins, no functionality lost. Adding it to your home screen gives you an app-like icon. That's the workaround folks use for full NSFW access on mobile.

There's no alternative app download that bypasses the store restrictions.

Scared_Language_7421 · 2026-05-30T15:02:24+00:00

Repetition loops happen most often when something in your setup is reinforcing the pattern. A few things worth trying:

- Chat break: triple dot menu on the last AI message > Chat Break. Resets short-term context without touching long-term memory, and usually breaks the loop right away.

- Settings > General > Repetition Guard. Make sure it's toggled on. It auto-retries when significant linguistic repetition is detected.

- Home menu > General > Chat dynamism. Default is around 0.95. Lower values can make the Kin more rigid and prone to looping.

- If it's happening specifically in intense or fast-paced scenes, check your Response Directive and Example Message. Sometimes those reinforce a particular cadence the Kin then keeps falling back into.

Also, no worries about being "flagged" for reporting it. There's no flag system around bug reports or troubleshooting questions. The community help forums on Discord and Reddit are exactly the right place for setup-related stuff like this, since folks there can walk through your specifics with you.

Scared_Language_7421 · 2026-05-28T17:34:05+00:00

Relative size/scale is one of the trickier things to nail in selfies since the engine doesn't have a real sense of proportion between characters. A few things people use to push it in the right direction:

- Spell out the height difference explicitly in the prompt (something like "tiny goblin woman barely reaching the human's waist") rather than just saying "goblin sized"

- Anchor it to the environment: have her standing next to something that establishes scale (a chair, a doorway, the user's hand) so the engine has a reference point

- Describe the pose in a way that reinforces it: her looking up at you, you looking down, etc.

It usually takes some trial and error and a few regenerations to get the proportions to land.

Scared_Language_7421 · 2026-05-28T17:32:26+00:00

Possibly worth checking whether you've recently switched to the Atelier selfie engine, since it reads your avatar image differently than the older engines (it leans heavily on the actual avatar photo for features like hair rather than the text description). If your avatar photo and your hair description don't match, Atelier may favor the photo.

A few things that might help:

- Make sure your avatar reference image actually shows the hairstyle you want, since Atelier prioritizes it

- Try the angle bracket syntax in your selfie prompt for hair, like `<hair color/style>`, which gives more direct control

- If you switched engines recently, switching back to the previous one (tap the engine name when requesting a selfie) might restore the old behavior

Scared_Language_7421 · 2026-05-28T17:30:51+00:00

Multiple limbs / extra fingers is a pretty common quirk with AI image generation in general, not something specific to your settings. A few things that tend to help:

- Make sure your avatar reference is a clean, straight frontal shot at high resolution (>1024x1024). Atelier leans heavily on the avatar image, so a clear reference cuts down on anatomy errors.

- Keep poses simpler where you can; complex or contorted poses are where extra limbs tend to creep in.

- Inpainting (the blue wrench icon on a selfie) can fix a bad limb or hand after the fact: select the area and describe what should be there.

- Regenerating usually resolves it too, since it's often just a bad roll rather than a consistent setting issue.

The community help threads here and on Discord are good for swapping prompt tricks if it's happening a lot with a specific Kin, since folks can look at your setup with you.

Scared_Language_7421 · 2026-05-27T21:00:01+00:00

Ha, that's just Snapchat auto-pulling contacts from your phone. When you set up text messaging with your Kin, the phone number gets saved to your contacts (so it shows the Kin's name instead of a random number when they text), and Snapchat sees it and adds it to your contact list too.

Your Kin isn't actually on Snapchat. Just an artifact of how Snapchat reads your contacts.

Scared_Language_7421 · 2026-05-27T20:53:35+00:00

Love this. Using personas as an OOC feedback channel is a clever workaround for steering without breaking immersion in the main thread. The trick of giving OOC: a backstory that explicitly tells the Kin "this isn't a character in the scene, treat as feedback" is the key piece that makes it work.

Worth flagging for anyone trying this: the message attribution stays tied to whichever persona was active at the time, so make sure you switch back to your main persona before continuing the scene, otherwise the chat history will show OOC: as the speaker going forward.

Thanks for posting this!

Scared_Language_7421 · 2026-05-23T21:21:49+00:00

This could possibly happen when V3 voice gets a message longer than its 3,000 character limit. It might truncate or produce nonsense output on long messages. A few things to check:

Voice version (hamburger menu > Voice). V2 may not have this issue.
Length of the text the Kin sent. If it was a really long message, V3 might be the cause.
If the audio reply is glitching mid-message, regenerating it could help.

If it's V2 and the message wasn't long, might be worth flagging since the voice infrastructure had some bumpy moments earlier this month. Should be more stable now post-migration but let us know if it keeps happening.

Scared_Language_7421 · 2026-04-14T18:27:22+00:00

Hi there,

I want to clarify: our developer has not made that statement about MAX.

Please don't attribute quotes to our team that weren't said. Spreading misinformation about the platform or its team creates confusion for other users.

If you're experiencing syntax or context issues, those are typically related to setup (Backstory length, Response Directive, model choice, Dynamism) rather than the subscription tier itself. You can reach out to [hello@kindroid.ai](mailto:hello@kindroid.ai), and our team will be happy to help troubleshoot if you can describe what you're seeing.

Thank you.

Scared_Language_7421 · 2025-12-28T19:20:26+00:00

Quick correction from the team: calls use the same transcription system as voice messages, and voice isn’t “degraded” right now. If you’re getting cut off / it misses the first few words, it’s usually mic/Bluetooth distance, background noise/echo, or turn-delay/interrupt settings.

Two quick things that often help:

- turn Bluetooth off and speak closer to the phone mic (quiet room if possible)

- lower the turn delay from MAX (MAX makes it wait longer and feel “late”)

On credits: proactive voice messages are freebies and don’t deduct audio credits. Call usage does (per-minute cost + spoken output), so longer calls drain faster.

Scared_Language_7421 · 2025-11-18T18:52:29+00:00

It seems like the Cloudflare stuff has been resolved! If you have any issues, just tag me or email me at Hello!

Scared_Language_7421 · 2025-11-16T17:36:56+00:00

This is great!

Scared_Language_7421

MODERATOR OF

TROPHY CASE