Bug 49047 - Keyboard is missing on Samsung Galaxy s4 and Samsung Galaxy Note 3
Summary: Keyboard is missing on Samsung Galaxy s4 and Samsung Galaxy Note 3
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.1.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-12-05 20:19 UTC by smorsi27
Modified: 2017-06-19 19:00 UTC (History)
5 users (show)

Is this bug a regression?: ---
Last known good build:

Example app exhibiting the bug (34.02 KB, application/x-zip-compressed)
2017-02-21 10:09 UTC, MG Potgieter

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description smorsi27 2016-12-05 20:19:17 UTC
I have a Xamarin.Forms Android app that has Entries where when you focus or tap on the Entry, the keyboard is supposed to pop up and you can enter text into the Entry. 

It works on most devices except Samsung Galaxy s4 and Samsung Galaxy Note 3. Our users are complaining the keyboard is missing when they're trying to sign up on our flow. 

I am wondering if this is a known bug or not. Please can the Xamarin team test this on these devices and see if the keyboard shows up or not?
Comment 1 adrianknight89 2016-12-05 21:14:05 UTC
Were you testing this on 2.1.0? Did you try 2.3.3? Not sure if the issue exists there or not, but it's good practice to test the latest nugest first.
Comment 2 John Miller [MSFT] 2016-12-05 21:48:13 UTC
I didn't find an issue with Forms 2.3.3 on those devices. Perhaps I missed an OS or version combo for what you are using - please confirm. 

Also, if you have a sample project you can provide that replicates this, please include. 

You can view my results here: https://testcloud.xamarin.com/test/bug49047_89f402ec-1599-430e-8d57-e8e7ac79605e/?step=0_1_1
Comment 3 smorsi27 2016-12-05 22:00:23 UTC
I'm not using Xamarin.Forms 2.3.3 or latest stable because of this reason: https://bugzilla.xamarin.com/show_bug.cgi?id=47378

It's a blocker to upgrade because xlabs breaks. I will investigate using another library for better UI controls that's more up to date. 

John, can you try the following if you have access to: 

Samsung note 3 (4.4.2). QA is reporting it's able to reproduce the missing keyboard on that OS with version Xamarin.Forms 2.1.0. 

On another note, here are some user stats where the keyboard is missing: 

Device Galaxy S4 
Manufacturer Samsung 
Device type Phone 
Device language English
CPU make Qualcomm 
CPU model APQ8064 
Native platform armeabi-v7a, armeabi RAM (MB) 2048 
Screen size 1080 × 1920 
Screen density (dpi) 480 
OpenGL ES version 2.0 
OS Android 4.4

Device Galaxy S4 Active 
Manufacturer Samsung 
Device type Phone 
Device language English 
CPU make Qualcomm 
CPU model APQ8064 
Native platform armeabi-v7a, armeabi RAM (MB) 2048 
Screen size 1080 × 1920 
Screen density (dpi) 480 
OpenGL ES version 2.0 
OS Android 4.4
Comment 4 smorsi27 2016-12-06 15:48:40 UTC
Here's a small, very basic sample project targeting Xamarin.Forms 2.1.0 with one entry cell you can test: https://drive.google.com/file/d/0BwLvWb8Ef6TVcXZEeDVodEdBS2M/view?usp=sharing
Comment 5 John Miller [MSFT] 2016-12-06 18:12:31 UTC
Still unable to reproduce with 2.1 on any of the devices you mentioned:

Comment 6 MG Potgieter 2017-01-31 06:39:46 UTC
I was able to reproduce this on a physical Galaxy S4. It happens with FormsAppCompatActivity, but not with FormsApplicationActivity.

The keyboard doesn't show up, but you can still interact with it. As in you can't see the buttons but you can still press them. The same thing happens for other Android UI elements, including the notification pull down bar and copy/paste contextual popup.
Comment 7 MG Potgieter 2017-01-31 06:47:57 UTC

I've included some screenshots, one of the device details, the other a screenshot of the application in question with the notification pull down bar pulled down and not invisible on top of the application.
Comment 8 smorsi27 2017-02-13 20:14:53 UTC
I haven't had the chance to look into this issue further but MG Potgieter, do you have a sample app to share here for Xamarin team to test? 

Also do you know if it happens with Xamarin.Android as well or just Xamarin.Forms? Thanks!
Comment 9 MG Potgieter 2017-02-21 10:09:52 UTC
Created attachment 19890 [details]
Example app exhibiting the bug

I can't upload the whole project due to the size. It's a standard Xamarin Forms template application, with a few changes to the MainActivity.cs as well as a custom theme, which I'm also including.

While making this example app I also figured out the exact method call that causes the problem.

When I call Window.AddFlags(WindowManagerFlags.DrawsSystemBarBackgrounds) in order to color the status bar on newer Android versions, this problem arises with this specific device.  Remove that method call, the bug goes away.
Comment 10 smorsi27 2017-02-21 15:22:59 UTC
I am using that method as well in my mainactivity!: 

//set this flag so the status bar color on new OS version is displayed correctly

Someone give an update to whether this should be fixed in a later release or not?
Comment 11 smorsi27 2017-02-21 15:32:13 UTC
MG Potgieter, 

Would something like this mitigate the issue? If I set a flag for build version? 

 if (Build.VERSION.SdkInt >= BuildVersionCodes.Lollipop)

So that it will not occur on 4.4.2 specific devices that have that issue? 

Unfortunately, I don't have a physical device to test on at hand.
Comment 12 MG Potgieter 2017-02-21 15:39:53 UTC

Checking for build version like that should also get rid of the issue.

In my case I removed the method call completely, I'm not sure if it is because I updated to latest stable of Xamarin Forms, something I changed in the theming or something else entirely, but that call seems to be unnecessary now.  The status bar draws the correct colour without it in my app now.
Comment 13 smorsi27 2017-02-22 15:27:14 UTC
MG Potgieter, thank you! Remote team tested and it's fixed! Thank you! Once I go on the latest version again (had to downgrade due to another crash issue in latest release), I'll probably remove it as you said it is no longer necessary.
Comment 14 Samantha Houts [MSFT] 2017-06-19 19:00:09 UTC
This looks like it's fixed. Please reopen if I have read the conversation incorrectly. Thank you!