If you didn’t do it then don’t expect it to be on par with external sources 
So have you tried this beta version? Maybe you can confirm if it was actually fixed or missed by the developers.
Just to share, after the workaround was shared for fixing the picture quality, I never used my firestick and RPi again and instead exclusively used the internal system. However, I got my surround speakers so I’m now using my PC for anything I want to play with 5.1 surround 
My feedback was off course related to 1.0.27 which is the topic in this thread. How else could I comment on the 2x scale?
Oh yeah, stupid me 
So can you check the image settings if everything’s set to 50?
Thanks for the feedback of the beta patch.
A good way to test choppy playback in Kodi is to play/stream a 1080p video in Kodi of any scene that has long moving shot where the camera moves from right to left or left to right or zooms out or zoom in to scene.
You got to observe the corners/sides of the screen where the scene unfolds or folds in… You’ll notice the slow frame rate like a fast slide show. That’s choppy playback.
It’s especially irritating while watching high speed action-packed scenes. Or even fast animated moving expressions/expressive gestures.
Which surround speakers did you get? And how are you connecting them to PPMax?
It’s a cheap one that’s actually for gaming - Logitech z607. It has bluetooth., aux, and RCA. No optical or HDMI so it’s connected to my PC and not directly to the PPM…well either way, there’s no way to connect to the PPM
This is getting a bit off topic though
1.0.27beta
DAZN
Does not start from desktop icon
Opening DAZN from the app store launches the app
Some apps don’t start from the launcher indeed, that’s a known issue indeed.
To be honest. I don’t understand why this 1.0.27 beta software has been released now as an official build. There must be a lot of preasure to execute this step. Some of the findings have not been mentioned in the release notes. I also don’t get what the gamma fix is not doing. Is it setting the tweaked settings in the hidden advanced video settting s menue now automatically ? Why hasn’t it been renamed to 1.0.28 as mentioned in the release plan. This will confuse again a lot of users.
Mainly to get the netflix and home button bugfixes out asap before the next wave of deliveries arrives.
By the way, it’s not the same as 1.0.27 beta. This was internally 1.0.29beta but got renamed to 1.0.27 for whatever reasons…
We are the only ones to have gotten .27a, so only we know about the previous shortcomings. This is .27f probably, so we will have to redownload it and install it.
Thanks for clarification. So is it worth installing the official 1.0.27 over the 1.0.27 beta ? - What exacly has been changed about the missing video settings tweak in 1.0.27 beta ?
That’s why I asked this question in this part of forum which should be restricted to beta testers.
Yes it is absolutely recommended to get off the (older) beta and to the current release.
The video settings apply the same adjustment as described in the KB article. There is nothing mysterious, the android output needed to be adjusted to account for the video chip’s response curve.
In the future we will call betas as 1.0.28beta1, 1.0.28beta2 etc. until 1.0.28 is finally released. Though it looks like next one will directly jump to 1.1.0 due to new features. Don’t fixate so much on the numbering scheme… it’s all arbitrary.
FYI the delta between 1.0.27beta and 1.0.27 release is:
so there’s quite a lot.
kodi fix didn’t make it, its a long business discussion.
Since I am working in the testing and verification department I am used thinking like the average Joe user - So whenever there are logical breaks or disagreements according to plan my alarm sense is ringing. 
With regards to making the announcement a banner, it has removed the news update summary from that spot.
Shall we leave it that way till there’s more news next week? After that I’ll just quote (part of) the firmware announcement in that thread, is that workable for you guys from Philips?
My mistake, please put the announcement banner back again.
I know, ideally we should have uploaded it as another beta here first. But we felt a surging need to offer another update with these urgent fixes now before the next wave hits. Now next week we can work on the real UX improvements and hard bugfixes.
I know how you feel that beta testers were ‘bypassed’ …
Can we install this OTA or only by offline update, seeing as our version is the same as the new one numerically speaking.
Yes OTA should work. The beta should’ve been called 1.0.27beta in your picopix, can you please check? This will get pushe the release version without the beta tag.
No problem, I know that is part of the game. - Sometimes buisness decisions regarding time shedule overrule those test sessions. - Drawback from my experience is sometimes this decisions are firing back, and bring some not so nice consequences with itself.