What does the DRM info app do, and is it safe to update it independently? APKPure is offering to update it for me but I’m not sure I should let it.
This app is used in the factory to verify that Widevine decryption key is burnt correctly.
The default launcher hides it, you’ll need to start it from an alternative launcher or APKPure / Aptoide etc. It’s safe to update.
1 Like
@Philips_Support_P am I allowed to share these personal measurement results elsewhere on the forum or even beyond? Noting that they aren’t official, calibrated tests done in a proper SPL testing facility with proper SPL testing equipment, and that everyone’s mileage may vary due to ambient temperature and stress levels on the PPM?
1 Like
Sure, feel free.
1 Like
So will the update push through today? Will it include the Kodi/GPU fix?
1 Like
Yes and yes. Waiting for the release build.
5 Likes
I failed as a beta tester because I did not test this version 
And I failed to comment about the manual keystone correction UI.
It would be better if it has indicators or at least the middle.
Anyway, at least it’s working 
1 Like
It’s too busy at the moment
But that doesnt make sense to the errortext; especially when retry/download again the system asks me if he should overwrite
Offline went fine
I tried to playback the same file with FW 1.1 under the same circumstances as my previous testing with this, but I still experience sluggishness, was something forgotten in the FW update? I can’t get to my adb setup at the moment to verify the settings however…
Turn automatic keystone off and back on.
1 Like
First of all, sorry for not thoroughly reading the release notes in my rush to share the news; this was mentioned in there.
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.
1 Like
@Philips_Support_P I’m not sure if it’s my idea or changed conditions in my living room, but I can now hear the fan again whereas on 1.0.32 I couldn’t hear it. Were there changes made between these two versions in this regard? It’s not as loud as it used to be in 1.0.29 but I can hear it again in Energy Saver in 1.1.0.
Depending on your reply I’ll run a sound measurement tomorrow, revert to 1.0.32 and measure again, then update to 1.1 again after.
I also found that 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.
1 Like
@Philips_Support_P, @Philips_Support_2!
BIG PROBLEM!
I was watching internal video source, set a “sleep timer”, PPM correctly shut down while playing, then I woke up some hours later with the PPM on and stuck on the “no input signal” screen. However, the fan was not running and the PPM was crazy hot. AirMote wouldn’t power off the PPM. It was painful to push and hold the power button on the unit it was so hot.
I just did the update to 1.1.0, will monitor to see if symptom recurs, but I’m really worried that this will damage the unit or start a fire…
I got the same error once at first but after many retries, it went successfully. Downloading the update hasn’t went smooth since the start. Something to improve
@fhteagle That is worrying, was it plugged during that time? In any case, if anything happens, I would assume Philips would be responsible especially if it’s a regression in the firmware.
Yes it was plugged in to the OEM usb-c charger, but no usb-c video or HDMI cable were connected. It literally woke itself up without turning the fan on for zero reason.