Bug 27327 - Xiaomi device returns incorrect window details
Summary: Xiaomi device returns incorrect window details
Status: RESOLVED UPSTREAM
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2015-02-23 16:49 UTC by Cody Beyer (MSFT)
Modified: 2017-07-05 01:13 UTC (History)
2 users (show)

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

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:
Status:
RESOLVED UPSTREAM

Description Cody Beyer (MSFT) 2015-02-23 16:49:12 UTC
### Description 

On certain Xiaomi devices, TranslucentNavigation will be flagged as supported, even though the device is running API 18 and does not support this feature.

### Test Case

https://www.dropbox.com/s/r8wmhlkqoj9jdve/WindowDetails.zip?dl=0

### Steps to Reproduce

1. Run on a Xiaomi HM 1s 
2. Click Button

### Expected Results

TranslucentNavigation should not be listed on button text (such as https://www.dropbox.com/s/uefo1o4vzt6r18z/Screenshot%202015-02-23%2013.46.46.png?dl=0)

### Actual Results

TranslucentNavigation is listed

### Additional Information

I have had no way to test this as I do not have the device in question. Just getting this documented.

### Version

=== Xamarin Studio ===

Version 5.7.1 (build 17)
Installation UUID: 33d88ac5-6a46-48da-ae18-b355ffac4d9e
Runtime:
	Mono 3.12.0 ((detached/de2f33f)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 312000076

=== Apple Developer Tools ===

Xcode 6.1.1 (6611)
Build 6A2008a

=== Xamarin.iOS ===

Version: 8.6.1.20 (Business Edition)
Hash: 3b3ef43
Branch: 
Build date: 2015-01-24 09:42:21-0500

=== Xamarin.Mac ===

Version: 1.12.0.4 (Business Edition)

=== Xamarin.Android ===

Version: 4.20.0.28 (Business Edition)
Android SDK: /Users/codybeyer/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.1   (API level 12)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Build Information ===

Release ID: 507010017
Git revision: 0bc7d3550b6b088ac25b08dcf7bbe73bcc8658b3
Build date: 2015-02-03 19:43:29-05
Xamarin addins: f7b7d34419c9ec24501bfa7c658e80a6305613e0

=== Operating System ===

Mac OS X 10.10.2
Darwin Codys-MBP.router 14.1.0 Darwin Kernel Version 14.1.0
    Mon Dec 22 23:10:38 PST 2014
    root:xnu-2782.10.72~2/RELEASE_X86_64 x86_64
Comment 1 Jonathan Pryor 2015-02-25 15:45:18 UTC
Please try the same thing from Java and report what the value of getWindow().getAttributes().flags is. (Please ensure that AndroidManifest.xml contains the same targetSdkVersion and related values.)

Xamarin.Android should (more or less) do whatever Java does, so this is only a Xamarin.Android bug if Java behaves differently for the "same" code.
Comment 2 Cody Beyer (MSFT) 2017-07-05 01:13:51 UTC
behaves same on java