Database Info

[APP] Avanos, the first guest mode for Android

One day when I was jogging, a little girl that looked scared and confused approached me. She couldn't find her mother and she asked if she could use my phone to call her. I thought to myself 'Sure, I'm helpful.' When I was waiting for her to finish her phone call, I noticed that she was swiping her finger on the screen. I was thinking to myself, 'Why does she need to scroll during a phone call?' I took my phone back and lo and behold, she was going through my pictures. I reprimanded her, telling her that she shouldn't be going through other's phones like that. I felt real bad that I had to take my phone back before she could find her mother, but what else was I supposed to do? It's not like there's an app that can do that.
That's when Avanos was born.
It's a simple phone dialer that locks the user in it so that no other app can be opened, fullscreen so that the notification bar cannot be accessed, It even closes the long home press automatically. It operates just like the built in dialer. After the person hangs up, it opens a password prompt that unlocks the phone and makes it go back to normal when the correct password is entered. I honestly think this is a revolution in Android. It can be helpful to coaches when kids that don't have phones need to call their parents, nice people who gives their phone out to others frequently, or as an everyday emergency phone.
So tell me what you guys think; I need the feedback.
Mod edit: No commercial advertising without free version.

Ooooh great idea!Congratulations!I wish i was an adult and could buy apps from play store.
Thank you
Sent from my LG-P880 using Tapatalk 4 Beta

It seems like a great idea to me. You might want to edit your post since its missing the play store link.
I tried the reviewer version. Unfortunately running cyanogenmod nightly 7/27 for the Sprint gs3 it won't lock. Press the home button it goes home, long press and task manager comes up.
Long press also still works on the menu button to bring up search and back button to kill the app. Not sure if you can fix that though.
If it gets updated for cyanogenmod would definitely pay the 99 cents.
Sent from my SPH-L710 using xda app-developers app

[Q] Odd classic voice dialer intermittently when using wired headset

Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3

bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.

joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3

take a screenshot of your classic looking dialer and post it here.

simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3

bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.

simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3

instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.

simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3

Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3

bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.

simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3

bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.

[Q] Google Keyboard Prediction Problem in Lollipop?

I really hate what Google have done to the keyboard in Lollipop. The predictions have been changed for the current word to show suggestions that aren't what you are trying to type, (if you are typing accurately.)
On the face of it, this seems to be a logical decision. In practice though, your eyes have to keep going upto your message to check what you have just typed is correct. You then have to go all the way down to the space bar to get the next word prediction. :silly:
Under the old system, if you were typing accurately, you would just press the middle button without your eyes ever having to go up and find where you are typing. This would then prompt the next word prediction without ever having to look upto the message or down to press the spacebar.
Is there any way to get the Kit Kat keyboard into Lollipop. (Its a deal breaker for me and could influence the Moto X 2014 vs Nexus 6 decision!)
See attached Kit Kat and Lollipop. In the example, I'm trying to type, "The."

I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?

StringerE said:
I just tried your scenario and it seems to be working fine on Lollipop.
As soon as I type 'T', the Google keyboard suggests the word 'The'. If I tap on that suggestion it then suggests the next predicted word.
If I type 'Th', it still suggests 'The' as the predicted word, but it also highlights or bolds the suggested word, indicating that I can hit the space bar to accept the suggested word 'The'.
If I go ahead and type the whole word 'The' without selecting the suggested word after either of the first two times it suggested it, it assumes I didn't want the word 'The' after all and suggests a different word.
Is that not the behavior you're seeing?
Click to expand...
Click to collapse
It is also what I see in Lollipop. Whilst it seems logical, when you are swiping, you only tend to check the word when you have finished a swipe. In KK, this mean't always going to the suggestion bar and confirming which also mean't insert space and then mean't next word please. Your eyes need almost no movement.
In lollipop however, when you have finished the swipe, your eyes have to go all the way upto the text, find where you typed and check it is what you wanted, then go all the way down to the spacebar and press it to ask for the next word suggestion.
It just means you can swipe so much faster on KK than you can on LP as your eyes are having to work alot less. :crying:

For me, the L version seems to be better at determining what I'm trying to swipe without me having to check it. I usually go ahead and swipe out the 2-3 sentences I want in my text/reply/post/whatever and then go back and verify it says what I wanted to say. And I've found it has been more accurate on L than it was on KK. Any incorrect words I see at that point I click on and the suggested replacement is usually what I wanted. If I verified each word as I swiped it would definitely be slower.
In other words, I rarely select the suggested words. I just swipe out what I want to say without looking up and then go back and verify before sending. And it's typically pretty accurate.

Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.

kgry said:
Is anyone seeing really bad lag while typing? Maybe I just type too fast but after I think I'm done with a word I look at the screen and it's still spelling it. I have vibrate on key press on, popup on keypress on and the text correction on.
Click to expand...
Click to collapse
I've had no problems with keyboard lag and I'm using 5 on the Nexus 7 2013, (Which is a much slower device.)

IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.

MrObvious said:
IDK about Swype type input but tapping is worse with white on white keys. I fixed it by switching to the older theme. I realized my eyes play a part in my accuracy apparently because muscle memory isn't enough. It's weird.
Click to expand...
Click to collapse
It's good that Google gave you the choice to switch back to the old keyboard look. I just wish Google would give me the option to switch back to the kit kat swipe functionality. I can't buy a nexus 6 until they fix this!

I faced the problem on android 5.0, did they solved on 5.1?

McGyver dei poveri said:
I faced the problem on android 5.0, did they solved on 5.1?
Click to expand...
Click to collapse
The keyboard still sucks in 5.0.2
I don't think 5.1 is out yet?

It's out but not for my note3... Only the LG keyboard is as fast and comfortable as this for me. A part the autocorrection problem, they also removed the option to remove the "change language button" it wastes space for nothing... Bah..
For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers

For example now I'm typing on the forum and I have to watch the super small text in the forum box ... I'm a lot slower than before that was in the center of the keyboard, and ofc I make more mistakes... Silly choice by google's engineers
Click to expand...
Click to collapse
Exactly the problem I have. If Google don't sort it out in 5.1 I'm staying on kit kat for sure. I get what Google were trying to achieve but they need the option to do both kk and lollipop prediction methods.

Personally I hate it. I have had to type words like "complaint" dozens of times over even though my swiping technique hasn't changed because the software thinks I'm trying to type "composition". Now, mind you, I swipe over to the A and there is no A in "composition".

Any news from android 5.1?

McGyver dei poveri said:
Any news from android 5.1?
Click to expand...
Click to collapse
No change.

Argh!!! That really sucks. Looks like it's staying on kk for me. :crying:
Would be nice if someone could hack the Google keyboard :angel:

Just an update for people having the same issue as me in Lollipop.
On the Play store, there is an app called Jellybean Keyboard 4.3. :highfive:
This app pretty much gets around my issue with the Google Keyboard and has worked fine for the last week I've been testing it with only a few niggles:-
- Emotions requires a separate download.
- When the app updated a few days ago, it forgot what it had previously learned.
I still dont understand why Google Keyboard cant contain a tick box in the settings entitled, "Include typed word in suggestion box in Lollipop." :crying:

Oh dear god. I tried Lollipop once on my N4 - it was awful. Now I plan to switch to 5.1 and see how it is one more time (and check if there is better battery life) but that keyboard abomination still scares me and its sad to know that it still persists...
However I'll try to live with that - at least for one day - cuz I wanna try EuphoriaOS tommorow Maybe I'll try to install Google Keyboard from 4.4.4... Somehow.

Just go for the jellybean keyboard as above. :angel:

Android Wear, what I love and Hate

Ok as some of the members of this forum may know I got off to a shaky start with my Android wear watch (a Sony SW3).
I've now had it about four weeks and have over come the major problems I initially had, so I thought I would start a tread highlighting the things I love and the things I hate so others can assess if a smart watch is for them.
Firstly, what I love:
- Reading messages from Text, Email, Whatsapp and Messenger
It's so simply to just quickly look at my wrist see if I'm interested, if not I delete, if I am, may read further on the watch or if the message is to long, find my phone and continue there.
- Voice control
A really unexpected plus for me. I thought 'OK Google' was a bit of a gimmick at first, but how wrong could I have been. It's fantastic (OK, I feel a bit of a nerd saying OK Google to get it started, but that's a tiny problem). Driving and going to be late, OK google, Send text message to XXXX, then speak your message eg ' Sorry running late will be with you in 30 minutes. The translation is actually pretty accurate and it's done, you don't have to take your eyes off the road!
- It's an accurate watch, not sure where it gets it's time from but I guess it comes from the phone which in turn gets the time from the network which means no more setting, not running fast or slow. Not sure how it works when you change time zone though but I'll find that out soon enough.
- It's waterproof. Don;t forget to turn the touch screen off, but I've now been swimming with it, I regularly shower with it. Not a hint of a problem.
- Control you music system. I use Sonos around my home and I can turn the volume up and down, change track. Ok it's limited but it still an unexpected benefit.
- Control Bluetooth music with Spotify. Really a feature best used in the car. There's an app that will fire up Spotify on your phone which in turn will use the blue tooth audio to connect to your car. No more digging around to find you phone, unlock it, fire up spotify, find your play list etc etc etc.
- Incoming calls. Nice feature as I can decide if I want to take the call without having to find my phone to see who's calling.
What I hate (ok hate is a bit strong, but)
- The UI I think is not properly thought through You have al these options, tilt to wake, tilt to scroll through cards. Clumsy at best and a battery drain at worst (tilt to wake particularly) Even the touch screen to wake is not that cleaver as it can be operated but a lot of things touching the screen not just me, eg a sleeve, particularly one that is damp
- Voice control Ok I know I've said above that voice control is fantastic but it has one major down side, it needs internet connectivity. If it doesn't have it, it just doesn't work! Wish it would use the processing power of my phone to process voice.
- Wifi, ok I accept this is probably a bug, but wifi doesn't currently work properly, for some reason it will drain all the all the battery for no apparent reason and it does it very fast. I've now turned it off and only turn it on on the occasions because it's great to have full functionality
- Screen, the screen is fine, but that's damming it with faint praise. I would really like to see a higher quality screen and a little bit bigger would be nice.
- Incoming calls. When rejecting a call, it would be good to be offered a 'rejection message' that is sent via text giving a reason for the rejection.

When rejecting calls you can slide up instead of left por right swipe ano it will show up predefined messages that it will automaticly send to The caller.
::enviado do meu oneplus one via tapatalk::

My complaints (1 month usage) is the app tray feels bloated. Not every app needs to be displayed. Not every app has options set through the watch. Also the layout feels cramped to me. I would prefer some options (icons only, 1x2, list mode, 1x1 mode, text/no text, recent shortcuts at top on/off, etc.)
2. Embedded speaker for taking quick calls without digging for your phone last minute. 1 problem a watch introduces is that your phone starts to be left behind. I now leave my phone on the counter while I buzz around my home. Phone rings, its a mad dash down stairs to find my phone.
3. Some sort of keyboard. I'll take the old school T9 input. Just let me type a few things.

player911 said:
My complaints (1 month usage) is the app tray feels bloated. Not every app needs to be displayed. Not every app has options set through the watch. Also the layout feels cramped to me. I would prefer some options (icons only, 1x2, list mode, 1x1 mode, text/no text, recent shortcuts at top on/off, etc.)
Click to expand...
Click to collapse
Download wear mini launcher from the playstore. It's a brilliant replacement that let's you customise the watch to how you want it.

I totally agree with you. I also use Android wear for
Reading messages from Text, Email, Whatsapp and Messenger
Voice control

Agree with some points according to my experience with my old android wear.
Hope my new one will work better.

My most of my complaints are solved with the Asus ZenWatch2. It is a solid upgrade to the LG G Watch. Once Marshmallow drops, we'll get a new app tray and speaker support (Zenwatch2 and Huawei) for calls.
I tried the alt launchers and it doesnt replace the stock launcher but runs over top of it. So it just adds to the chaos. However after the nostalgia wore off, I dont really use apps thus dont need to go into the app drawer.

Keyboard: try FlickKey
player911 said:
3. Some sort of keyboard. I'll take the old school T9 input. Just let me type a few things.
Click to expand...
Click to collapse
Try FlickKey Keyboard for Wear. It adds a keyboard to any app that wants to call it. Right now, that is limited to Wear Messenger, Coffee for Wear, and K-9 for Wear - you need one of those messaging apps to be able to use it. BTE, FlickKey is not a T9 style keyboard - it works better than that.

I have tried various keyboards. What I was referring to was an option, by default, in Android wear to have a keyboard input. I don't use any of those apps, thus having a keyboard right now would be irrelevant.

What apps would you like to use a keyboard with?
player911 said:
I have tried various keyboards. What I was referring to was an option, by default, in Android wear to have a keyboard input. I don't use any of those apps, thus having a keyboard right now would be irrelevant.
Click to expand...
Click to collapse
I certainly agree that users should be able to decide for themselves if they want to use a keyboard or not, and which one they want on their smartwatch. What apps would you like to use a keyboard with? FlickKey can be added to any app with just about 15 lines of code. So message the dev who makes the app you want FlickKey in and let them know they can easily add it for free.

I find Android Wear to be very useful - when it works. Performance on my original 360 hasn't been very consistent either but I'm sure the S400 watches fare much better. Seriously though - every Android OEM needs to switch to AMOLED as soon as possible since it's much more suitable for smartwatch use.

I have installed AW on a Samsung Gear 2 (ported to the watch by @biktor_gj) and it runs really great !
Much much better than the default Tizen where it comes with normally.
Since I am using AW, I'm really hooked on it.
I love to be able to navigate with my watch and/or get notifications (from Google Maps) about any traffic jams or hold ups on my route.
I love to be able to use my voice to respond to whatsapp messages or even use my voice to make a new message without even holding my phone.
Really looking forward to the upcoming version (Marshmellow?), which suppose to have speaker support, because the Gear 2 has a build-in speaker.
So that means I can make calls too again from my watch (which is now only possible in Tizen, but not AW).

Hangouts and Messenger and Email (I know there are email clients that support wear and flickkey). I doubt Hangouts or Messanger will get it support.

Gboard - voice to text mic missing in messages

Hi,
Just got my unlocked Pixel 4a today. No custom roms or anything. Android 11. Build RQ1A.201205.008.
I'm a bit of a minimalist, and I went through the keyboard settings for messages (it had this little emoji bar thing that also did the predictive words I wanted to get rid of). Also in that bar was the microphone for voice to txt. When I shut off those unneeded options and turned the dedicated numerical row on, the microphone disappeared. I've tried resetting the options to the best of my memory, but it still isn't back to where it was, and the microphone is still gone.
There is another microphone in the preview box, but that is a tap-and-hold-to-send-a-recording microphone. Not what I'm looking for. That works.
I checked permissions, Gboard has permissions. I checked the keyboard settings, voice to text is enabled. Anyone know the 'magic combination' of options to get this back? I use it frequently!! I'd hate to have to reset-to-factory just to restore this one feature.
Thanks!

I finally found it after much headaches. It seems the voice to text microphone is part of the "suggestion strip" that is under "Text Correction". No idea why this isn't integrated into the keyboard as it's own icon as it's been in earlier versions of Android.
If anyone has any recommendations on how I can potentially make that integration and get rid of the suggestion strip, please let me know.

I tried to reproduce the missing voice2text mic that you reported and failed.
I went to Gboard settings > text correction then:
Disabled show suggestion strip
Disabled next-word suggestions
Disabled emoji suggestions
Disabled sticker suggestions
Going back to the keyboard, the suggestion strip/stickers/GIF/clipboard/settings and the mic were all gone.
I re-enabled all the above and the mic reappeared, along with the other stuff.
One thing you could try short of factory reset is to go to the App Info for the Gboard, force stop, and clear the cache. Relaunch the keyboard to see if it brought the mic back.
---
Looks like you resolved it. I think this design change was made a few cycles ago and am not aware of any way to re-integrate it. You could try SwiftKey to see if that has the feature you want.

I think installing a different keyboard can be helpful here. Have you tried to do it? To be honest, it was one of the most significant problems that made me change a model of my phone. I did have a Samsung Note, and the problem with the Gboard was repeating very often. I have been browsing different sites to find a solution, but was never successful in it. One day, one of my sisters visited me and took my phone while I was in the kitchen. She fixed the problem instantly, would you believe it? I came to the room and was surprised after she showed me it. She said she visited https://techplugged.com/5-best-solutions-to-fix-the-gboard-not-working-error/ and followed all the instructions given there. I have forgotten about the problems with Gboard for a long time, but there were other reasons for me to change my phone to the latest iPhone.