1.1.0 Bugs list

[fhteagle]

Since we didn’t get to beta test 1.1.0 …

Clock incorrectly shows 0852am instead of the correct time of 2052 or 0852pm in launcher 1.4.0 settings menu.

Still unable to write to 3 different FAT32 microsd cards: 8, 16 , and 32gb from various brands. All checked in Linux laptop with F3 to verify they were not fake sized, no bad blocks, then used gparted to clean reformat to FAT32 after the f3 test. I am 100% sure this is a PPM issue. No idea if my unit has been hardware damaged by overheating events or if it is software issue. I suspect the latter based on the error message in xplore and the fact that others have reported this issue on this forum, though.

Manual keystone correction not saved from one power off to next power on.

[kugiigi]

GPU fix does not persist on reboots. You always have to toggle off and on the automatic keystone correction.

[trappm]

Yes. [vendor.hwc.compose_policy] is set to [0] again after reboot. Toggling Automatic keyston off on brings it back to 6.

[SchmuFoo]

@fhteagle

Clock is still 12 hrs behind for me in 1.1.0 / launcher 1.4.0 settings menu.

Launcher v1.4.0 alpha- need feedback on battery time remaining

Settings app is another team, I already asked them to improve it. Hope it makes it for this update, next one if not.

[IvoGrijt]

I reported this last night and got this answer:

@Philips_Support_P

@IvoGrijt

I checked, without doing your suggestion, I got these values:

W:\Android\platform-tools>adb shell getprop vendor.hwc.compose_policy
0

W:\Android\platform-tools>adb shell getprop persist.sys.keystone.display.id
-1

After your suggestion, the vendor.hwc.compose_policy is showing 6. But it’s not persistent, after a reboot it’s back to 0. What’s the thought behind implementing it this way, and is this definitive? To ask the Kodi user to do this after every reboot will grow tiresome, it would be great for heavy Kodi users like myself to be able to save the setting.

it’s supposed to be persistent. If not, looks like the merge got bungled. I’ll have it checked tomorrow. Thanks for reporting.

Also:

@IvoGrijt

while airplay mirroring or streaming, I can use the airplay shortcut to go back to my stream if I went to home. But it goes into the airplay receiver settings, and I have to press Back one time to get to the playing content. That should be documented if that works as intended (I can see that going into the settings to tweak something Airplay related might be needed, so no need to fix that, just needs to be documented in the relevant guide.

And may I suggest that in the future we as beta testers always get the latest release that’s going public before the public, so we can actually find stuff like these before they go live, l so they can be fixed, documented, or mitigated in time.

[fhteagle]

Added the cannot write to SD error to OP list.