So every GOS user is using a different keyboard or have they been living with a broken keyboard for years? I don't understand that. It's extremely annoying and you can't just accept it in your daily life. I have also come to terms with it, but it takes me significantly longer to write texts. That's just crazy...

I never reported this before because I thought that something so obvious would be reported by others anyway. And the problem has existed for more than 3 years.

Here's a video: https://www.youtube.com/shorts/s8AfcxIrWn4

So do we just have to accept this, and the bug is just a part of GOS? I actually don't want to install another keyboard. And I find it strange that the GOS developers assume this. If there are such obvious errors, then there's really no need to integrate the standard keyboard at all.

    This problem occurs for me too but it is new. Only happening since the last update, never before.

    Pixel 6A stable build

    Hm, strange. I have the problem since my Pixel 5 in 2021 or so. And now I have a Pixel 8 since 1-2 years and there is the same problem. But its not always. After I posted the problem here, I didn't have the error anymore, for example. It was quite strange. But today it is back, and I immediately recorded a video.

    Pewdue https://www.youtube.com/shorts/s8AfcxIrWn4

    That is interesting!

    Pewdue So every GOS user is using a different keyboard or have they been living with a broken keyboard for years?

    I suspect many users have been using the default keyboard but not experiencing that problem. I further suspect that the issue shows up depending on various keyboard settings. For example, for those experiencing this, which languages and layouts are enabled?

          de0u

          German without autocorrect

          fid02

          What does this mean? Can someone explain? But why do some have it and some do not, when it is actually known and has been part of the system for years?

              Pewdue
              Strange.
              I never had this issue.
              For security reasons and because alternative keyboards have their own issues, I am using the original AOSP keyboard.

              As I cannot reproduce the problem, I assume that the error is in the language file and not in the keyboard code?

              This can also occur if you use automatic replacement of words or characters and have stored certain words or character strings in your own dictionaries.

              As English is not my native language, I have stored two languages in the keyboard settings to switch between them.
              I also use three dictionaries:

              1. for both languages for language-independent words
              2. specifically for the native language, only words occurring in the native language
              3. specifically for English, words that only occur in English

              This works very well once you have set it up.

                I had this bug every time I wrote an email in the proton mail pwa. German language + default AOSP keyboard. Can't remember it ever happening outside of a PWA.

                I cannot reproduce your bug but I have automatic replacements/suggestions disabled. German language as well.

                Does your problem disappear when you turn off the numerous automatics? If yes, which one causes the problem?

                  fid02 This was a bug in apps using the new Compose user interface system instead of the traditional view-based system. Those apps need to update to current Compose libraries. Apps which have not updated their libraries will still have the bug.

                      schweizer Does your problem disappear when you turn off the numerous automatics? If yes, which one causes the problem?

                      Yes. The option "Suggestions for changes" (DE: "'Änderungsvorschläge") is the problem.

                      GrapheneOS

                      But then the problem are the apps in which I enter the text and not the Android system, right? So we have the solution. I just find it strange that very popular apps have accepted this bug for years. Aren't all other Android users affected who don't use GOS? Why is no one complaining then? I don't understand that.

                            GrapheneOS Recently I had the same keyboard issue as the OP. I was in Vanadium replying to a post on this forum. Not PWA, so I think it's different. Reboot fixed it for now. Can't confidently say I had it before though.

                              Pewdue Yes. The option "Suggestions for changes" (DE: "'Änderungsvorschläge") is the problem.

                              Not for me.
                              I am using all these options (switch = [on]) in that setup submenu, where they are listed.
                              Exception: “Suggest contacts” switch = [off].

                              Everything works fine for me.
                              Therefore, I suspect the error is either in a language file (but not German or English) or in an app that is used in this context.

                                  I cannot reproduce the issue as well with "Änderungsvorschläge" on.
                                  Tested Vanadium DS Note and FairEmail.

                                  Eagle_Owl Well, we have already established that this is a problem specific to certain apps. So it's not the case for every app. And for the apps where this is the case, disabling everything helps.

                                  But I still don't understand why such popular apps have these issues. This should affect almost all Android users, since most of them use the standard Android keyboard, right?

                                  One app where the error occurs is, for example, Perplexity.

                                      Pewdue most of them use the standard Android keyboard, right?

                                      Nope, barely anyone uses the AOSP keyboard. It's just FOSS OS's like Graphene that use it for lack of a better alternative. There isn't a single Android vendor out there who would ship the AOSP keyboard.

                                        Oh, okay... So the bug will be there forever. Then the only solution is still to change the keyboard or to not use Suggestions or the app where the error happens.