Google Keyboard (Gboard) Disappears

[sbs8331]

I'm not sure what happened, but my Google Keyboard seems to have disappeared. Google Keyboard is not showing as an option under "Keyboard & input methods". I have Flesky and Swiftkey, so I'm getting by, but I don't know how to get it working. Gboard shows under Apps, and I've tried clearing cache, clearing data, force stop, and uninstall/reinstall, but it still doesn't appear as an option to use as a keyboard. How can I rectify this? Thanks in advance to anyone who has a solution.

 

[guessingagain]

I'm not sure what happened, but my Google Keyboard seems to have disappeared. Google Keyboard is not showing as an option under "Keyboard & input methods". I have Flesky and Swiftkey, so I'm getting by, but I don't know how to get it working. Gboard shows under Apps, and I've tried clearing cache, clearing data, force stop, and uninstall/reinstall, but it still doesn't appear as an option to use as a keyboard. How can I rectify this? Thanks in advance to anyone who has a solution.

Google keyboard is replaced by Gboard but I think you already knew that. Also if you are on a custom ROM flash Gapps again. Gboard will appear on input options. If not maybe you have factory reset or wait for the app to be updated again .
PS did you reboot after clearing cache?

 

[sbs8331]

Google keyboard is replaced by Gboard but I think you already knew that. Also if you are on a custom ROM flash Gapps again. Gboard will appear on input options. If not maybe you have factory reset or wait for the app to be updated again .
PS did you reboot after clearing cache?

Thanks for the reply. I'm not rooted and therefore don't have a custom ROM, just the one that came with the device, so therefore I can't really flash anything. I went into recovery mode and did a cache wipe there, which, of course, requires reboot, to no avail. I'll wait to see if an update comes out soon and will live with 3rd party keyboards in the meantime. For what it's worth, I've included screen shots showing that Gboard is showing as an app but is not showing as an available keyboard. When I click "Current Keyboard", my only options are Flesky and Swiftkey.

The reply is appreciated.

 

[guessingagain]

Thanks for the reply. I'm not rooted and therefore don't have a custom ROM, just the one that came with the device, so therefore I can't really flash anything. I went into recovery mode and did a cache wipe there, which, of course, requires reboot, to no avail. I'll wait to see if an update comes out soon and will live with 3rd party keyboards in the meantime. For what it's worth, I've included screen shots showing that Gboard is showing as an app but is not showing as an available keyboard. When I click "Current Keyboard", my only options are Flesky and Swiftkey.

The reply is appreciated.

Sorry to hear. If you do manage to get it fixed please reply to this thread. Thanks. I am on 7.0 and Gboard is running fine.

 

[sbs8331]

Sorry to hear. If you do manage to get it fixed please reply to this thread. Thanks. I am on 7.0 and Gboard is running fine.

Update: I finally got Gboard back. I tried a number of things, including a manual download and install of the apk. I decided to try Slash keyboard, and, when I installed it, I was taken to the screen to enable it, and, voila', Gboard shows up with an enable option. I don't know what happened, but it's working now.

 

[doomed151]

Update: I finally got Gboard back. I tried a number of things, including a manual download and install of the apk. I decided to try Slash keyboard, and, when I installed it, I was taken to the screen to enable it, and, voila', Gboard shows up with an enable option. I don't know what happened, but it's working now.

Actually, in your second screenshot, if you tap on "Current Keyboard" there will be a button to choose keyboard. If you press that, it will bring you to the screen where you can enable/disable keyboards. That's probably why Gboard was hidden.

 

[sbs8331]

Actually, in your second screenshot, if you tap on "Current Keyboard" there will be a button to choose keyboard. If you press that, it will bring you to the screen where you can enable/disable keyboards. That's probably why Gboard was hidden.

Yep. Not intuitive to me, but you're correct. I thought "Current Keyboard" was just a prompt to select one from the pop-up window. Often the answers are simple if you know where to look. Thanks! :good:

 

[doomed151]

Yep. Not intuitive to me, but you're correct. I thought "Current Keyboard" was just a prompt to select one from the pop-up window. Often the answers are simple if you know where to look. Thanks! :good:

No worries! They changed the menu structure in Nougat so it's more intuitive now.

 

[daverobinson88]

Probably off topic but does anyone else not like the update they did to the keyboard? No way to remove that search menu row? I have never used the suggestions and wished I could remove it.

 

[guessingagain]

Probably off topic but does anyone else not like the update they did to the keyboard? No way to remove that search menu row? I have never used the suggestions and wished I could remove it.

Go to input > virtual > Gboard > settings > search and disable it.

 

[daverobinson88]

It removes the search G but still keeps the row there. See attachment.

 

[guessingagain]

It removes the search G but still keeps the row there. See attachment.

Yeah that's true. I can't find an option to disable that. Maybe it's not possible in this update.

 

[Owenboy89]

I am sort of in the same boat

Hey everyone.

Lastnight I installed, an android 7.0 custom rom to my tab pro 10.1. I used TWRP to flash install the ROM when it installed it automatically rebooted my device before I could go on to Gapps and install them with the the ROM. So when the ROM loaded up I connected to my hub (using the keyboards) then had a look at the new OS and the wife had a look out of interest with me and everything was working well in fact it was quicker than it was when we got it brand new.
Then playtime over rebooted back into TWRP and flashed Gapps. Then it rebooted again. When it finally loaded back in I was met with a loading screen saying Android is Starting which wouldn't go away but it asked me to sign back on to the Hub so went to do this on problem was.....no Keyboard.....so I managed to get into my setting through quick menu settings and find input settings and there is no keyboard installed to the device...it asked me to add one but I can't because I can't type and even if I could the android is starting message is still going.

Please help I am new to this and I want to learn all this type of thing but I am completely puzzled on what to do. I tried clear chase and data and even tried factory reset.....tried installing gapps on twice (before the factory reset) and nothing was working.

I am tough to use odin to flash it back to standard rom and start again but I could do with some pointers with what i have done wrong.

Thanks people

 

[echo92]

Hey everyone.

Lastnight I installed, an android 7.0 custom rom to my tab pro 10.1. I used TWRP to flash install the ROM when it installed it automatically rebooted my device before I could go on to Gapps and install them with the the ROM. So when the ROM loaded up I connected to my hub (using the keyboards) then had a look at the new OS and the wife had a look out of interest with me and everything was working well in fact it was quicker than it was when we got it brand new.
Then playtime over rebooted back into TWRP and flashed Gapps. Then it rebooted again. When it finally loaded back in I was met with a loading screen saying Android is Starting which wouldn't go away but it asked me to sign back on to the Hub so went to do this on problem was.....no Keyboard.....so I managed to get into my setting through quick menu settings and find input settings and there is no keyboard installed to the device...it asked me to add one but I can't because I can't type and even if I could the android is starting message is still going.

Please help I am new to this and I want to learn all this type of thing but I am completely puzzled on what to do. I tried clear chase and data and even tried factory reset.....tried installing gapps on twice (before the factory reset) and nothing was working.

I am tough to use odin to flash it back to standard rom and start again but I could do with some pointers with what i have done wrong.

Thanks people

You may wish to ask over in the Galaxy Tab Pro forums at https://forum.xda-developers.com/galaxy-tab-pro-12-10-8 - you've somehow wandered into the Moto G4 forums

But as a very general suggestion - sounds like your GApps isn't happy with your custom ROM. You may have to clean flash your custom ROM again and verify that the GApps you're flashing is suitable for your device/custom ROM.

 

[Owenboy89]

I agree with you I have just download the same rom and a stock gapps and I had the same message and again with no keyboard.....agian. Difference this time I haven't rushed to do a factory reset and gone back and reflashed the android 7.0 rom and I am back working again with keyboard but no google apps.

Is there a way of installing them a different way, only 2 google apps I use is play store and gmail. I have tried installing a google play store and play services apk but doesn't work. It goes to load and then just stops.....feels like I need a list of apps to get them going.

Hope someone can help

 

[Owenboy89]

I worked out my problem with Gapps, "android is starting messages" and no keyboard.

1. I needed to wipe my cache, data and davarlik (whatever it says....looks like darlik to me...lol) before and after.

2. Like fella before said my ROM didn't like the Gapps package I had downloaded, so everytime I had the android message I went back on to TWRP and restored back to the orginal point where the lineage ROM worked, then went back on to the net and installed the next Gapps package and repeated till I found a package that worked......that package was the "Micro" package.

Any google apps I was missing I simply just downloaded them via the playstore after.

I realise this is a moto G forum but I find that sometimes you need to go other places to find answers and I had originally looked in the samsung Tab Pro 10.1 forum section and couldn't find anything similar to my problem this fella at the beginning of the thread was the closest to my problem I could fine.

Hope this helps