[Android Software Development] spocky12:
Good point, I'll try to get the engineering menu values of the projectors tested by Greg.

Concerning 494/536 you can't really tell from the UI, except by using a file explorer and check the /system/etc/pq* files (extract 494, check the files, then extract 536 and check the files again, they should have changed). Note that I don't say that this is definitely the only cause of the differences between both wemax tested by Gregory. It just happens to be files related to color calibration and that they have been updated in the only firmware update available, so that would explain pretty well the difference seen by Gregory. I have nothing to make measurements myself (well, except for my eyes) so I can't confirm. As I wrote in another PJHC post, there is also another possibility : a hardware difference between both. As noted by someone who owned 2 1080p devices much earlier in this thread (in the 1st few pages), he saw a great difference in image quality between both and this was confirmed by engineering menu where "contrast ratio" value was almost doubled comparing both.

Concerning the 860 rgb/xy values I don't really know what they represent unfortunately. What I can confirm however is that laser luminosity is 200 in movie mode and 255 in highlight mode and no matter what you do (I tried some low level stuff), you can't use any other value, so there's no way to lower this value, it's hard coded somewhere in the drivers.

1- you should have 2 usb ports. If not, you can use a usb hub.

2- binding your google accounts (and getting your youtube history), disabling most chinese stuff (granted you can also disable many things with adb commands on un unrooted device), lowering input lag...

3- yep, install another launcher and freeze the stock one (with my tools on a rooted device, or with adb commands if unrooted)

4- don't you have a remote control ?

5 - on our devices, standard apps don't receive the "BOOT_COMPLETED" event and/or their RECEIVE_BOOT_COMPLETED permission is not granted. I had to develop a workaround for my tools.

6- I wouldn't count on it, but you never know, they updated some of their tvs...

7- it could be this, the unavailability of google services on stock firmwares, and specificities (limitations) of xiaomi framework

8- nope

9- key layout is not available for it on our system. I might be able to fix it though, I'll have a look at it.

The update blocker is on my todo list but I was on another feature recently. I only confirmed that manually installing the google play update cause the same issue you had (but on rainman/batman, Google doesn't automatically updates Google Play, so the issue is less visible)

Can't tell for the wifi issues, I only connect using rj45.

1- Nobody managed to root it yet. But my app should offer the ability to boot on another input even on unrooted devices. Theoretically, it should work on international devices too (you need to enable the Accessibility service)

2- I don't know : the SOC is different and the software as well

3- That can't be done

Concerning ATV, that's a bug in the current version of my tools, it's fixed in the upcoming release.

As for Youtube, I can't really tell, it has always been difficult to install : sometimes it refuses to install a version but another one can be installed. Once done, you can update to the first version that didn't install earlier... The behavior doesn't seem consistent, I don't know if it's related to aptoide or xiaomi internal code...

1- No idea

2- ATV is a standalone app. Leanback requires installing Google Apps from my tools. As long as Leanback is installed, it will automatically be the default launcher, so if you wan't to switch to ATV, you need to freeze it.

Somebody already reported bluetooth and youtube didn't play well together. I can't tell you why, that's probably related to some magic Google is doing in their code, that is not compatible with xiaomi's framework.

Please use english here. I'll reply to your MP pretty soon.