BUG: Acode using Samsung keyboard overwrites words when "Keyboard mode" is "Normal" or "No suggestion"

[oskint]

Check for existing issues

• [X] Completed

Describe the bug / provide steps to reproduce it

(I firstly did Settings >> Restore default settings.) Use Samsung keyboard. (Edited after comments.)

Go to Settings App Settings Keyboard mode and select: Normal or No suggestion

In editor go to the new line and write e.g. aaaa bbb Then click e.g. in the end of the word aaaa and insert space.

RESULT: Acode automatically changes text aaaa bbb to abbb bbb

It means it overwrites word aaaa with bbb.

The bug is so annoying that this menu option is completely unusable. And without the option user is forced manually correct every typo. In my case to use other editor.

Environment

Samsung A52 Samsung keyboard application 5.6.00.51 Android 13 Acode 1.10.5 20th Oct 2024

If applicable, add mockups / screenshots regarding your vission

No response

If applicable, attach your Acode.log file to this issue.

Acode.log

[bajrangCoder]

I tried to reproduce it. But failed.

As it's working fine for me with all the three keyboard modes available.(Btw the no suggestions mode is good for different devices, as it doesn't disable suggestions) I'm using gboard.

[bajrangCoder]

Maybe your have any ai based , system level auto correct feature, which can cause this

I guess you are using samsung keyboard, ?

[oskint]

I use Samsung keyboard version 5.6.00.51 (just actualised) and the bug is still there. But you are right, using the Gboard the bug disappears, I just tried it. E.g. QuickEdit editor with Samsung keyboard does not produce the bug. Therefore the cause is the combination of Acode with Samsung keyboard.

Thank you. I edited the title and the bug description.

[NishchayKQ]

on fresh install, acode 1.10.5(953), samsung keyboard - 5.9.00.63, one ui 6.1.1, normal keyboard mode/no suggestions, i couldn't reproduce it

tried on an older device as well (samsung keyboard 5.6.10.40)

[oskint]

My problem persists even after updates, clearing data and caches, and removing languages.

---

Just updated my Samsung Galaxy A52:

Android 14
(writes "Your software is up to date"), English (US), removed other languages. Settings >> General Management >> Language: English (United States)

Samsung One UI 6.1.

Samsung Keyboard 5.8.20.10 (writes "The latest version installed"), cleared cache & data. Languages and types: English (US), removed other language Auto replace: no languages selected

Acode 1.10.5 just uninstalled + installed, cleared cache & data Settings >> App Settings >> Keyboard mode: Normal

---

BUG REPRODUCING Change happened.

On a new line typing aaaa bbb then moving to the end of "aaaa" and typing SPACE does nothing - works OK.

But, when i move the cursor to the end of "aaaa" and write e.g. letter c then the result is abbbc bbb

That is instead of result aaaac bbb it rewrites it to abbbc bbb

SO, THE MODIFIED BUG IS STILL THERE.

OTHER APPS: QuickEdit editor: no such bug Jota+ editor: no such bug NeutriNote editor: no such bug WhatsApp: message input: no such bug

---

I am really furious about the Acode thing because in hunt for the bug solution I had to delete many settings that worked for me ok for years.

---

Samsung Galaxy A52 Android 14 - English (United States) Samsung One UI 6.1 Samsung Keyboard - 5.8.20.10 - English (US) Acode 1.10.5

---

Any ideas?. Thank you in advance

[NishchayKQ]

yes the modified version of the bug i can consistently reproduce, further the old bug still is there, its just not consistent to reproduce it

https://github.com/user-attachments/assets/637ab4af-b8e3-4e37-98f4-abf2cb5c32f0

[oskint]

thanks for the confirmation

[UnschooledGamer]

I've tested it with Latest Version of Acode(Play Store) on my samsung device with samsung keyboard, Confirm it as a Bug. It's a consistent bug for me.

[UnschooledGamer]

Update: I turned off predictive text from samsung keyboard settings, And now the Acode typing experience feels fine.

[RohitKushvaha01]

@bajrangCoder I don’t have a Samsung device, so I’m not sure I’ll be able to fix this.

[deadlyjack]

You can use online emulator for samsung device to test.

On Sat, 24 May, 2025, 10:24 am Rohit Kushvaha, @.***> wrote:

RohitKushvaha01 left a comment (Acode-Foundation/Acode#1057) https://github.com/Acode-Foundation/Acode/issues/1057#issuecomment-2906409728

@bajrangCoder https://github.com/bajrangCoder I don’t have a Samsung device, so I’m not sure I’ll be able to fix this.

— Reply to this email directly, view it on GitHub https://github.com/Acode-Foundation/Acode/issues/1057#issuecomment-2906409728, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJHIHI5CLEDOORZZP24ZWA32773O7AVCNFSM6AAAAABQIIL2DOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSMBWGQYDSNZSHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[UnschooledGamer]

You can use online emulator for samsung device to test. …

Emulators do not always give the actual device Experience compared to a real Device. Sometimes, it might work fine on Emulators, but on a Real Device, it may have issues.

[NishchayKQ]

can we help in any way, like with logcat or something? i could also try to debug this (though im limited to kotlin) i prolly can't fix it but might be able to find out the cause (just point me where to begin), can this be debugged in android studio?

[UnschooledGamer]

can we help in any way, like with logcat or something? i could also try to debug this (though im limited to kotlin) i prolly can't fix it but might be able to find out the cause (just point me where to begin), can this be debugged in android studio?

If you have an actual Samsung Device where that Issue occurs, You can help in confirming if the above Fix I gave works currently or not.

[NishchayKQ]

turning predictive text off does fix the issue.

However if i have it on, and disable auto replace, it still results in the bug (ex: use case suggestions are allowed but don't automatically replace)

[RohitKushvaha01]

The Sora editor has the exact same issue, and I think the Ace editor has this issue too. It probably occurs due to multithreading/worker issues.

[github-actions[bot]]

Hi there! 👋 We're working to clean up our issue tracker by closing older issues that might not be relevant anymore. If you are able to reproduce this issue in the latest version of Acode, please let us know by commenting on this issue(i.e Bump!), and we will keep it open. If you can't reproduce it, feel free to close the issue yourself. Otherwise, we'll close it in 14 days. Thanks for your help!

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.