Software Update v1.0.26 is available now

Don’t mind him. He seems to post random negative posts :sweat_smile:

Hello @macsan0123,
Why post comments on presumed disfonctions If you don’t have (still) the PPM in your hands?
Is not better to wait and then talk about things that you can verify by yourself?

Agreed but I’m apprehensive…wanted reassurance…got it…why do PPL post videos like that which gives a bad impression of the pico…

@Philips_Support_P Hi Prashant. Weird stuff started after updating to 1.0.26. When I put appleTV to sleep, the ppm max will shut off automatically (previously not). This is a good thing.

However, when I started it again, the ppm will turn off by itself after started. I will then have to use the remote to turn it on again. Any idea why? Previous version do not have this issue.
Thanks

Seems like the HDMI CEC commands are now working, putting the PPM to sleep once the input source device turns off.

When you say that:

… is the PPM still connected to the AppleTV that’s turned off?
If so, can you test what happens if you have AppleTV and PPM on, turn off the AppleTV (PPM also turns off), and then disconnect the HDMI cable before turning the PPM back on?

Yes exactly, I will check what’s up with CEC in this build.

In other news, 1.0.27 beta will be out tomorrow so maybe try that too.

1 Like

@Philips_Support_P Time for the new v1.0.27 thread?

I think the CEC is working as it should be. The ppm shuts down when AppleTV went to sleep. When I turn the ppm on again, i now think it powered off because I long press on the remote off button. Now I just need to short press on the remote power button to ‘wake’ the ppm up.

1 Like

Hi @imdevu v1.0.27 has been in beta but has a few rough edges, so we decided to skip it from public release. We’ll go directly to 1.0.28.

I think going forward we’ll continue it with even numbered public release and odd number beta release.

4 Likes

Sounds good @Philips_Support_P! Maybe kick off a new thread on 1.0.28 with the items targeted. Not asking for timelines as I understand how Software upgrades are… :wink:

Following all threads in #picopix-max:feature-suggestions is not practical for everyone.

2 Likes

Hi, do you have any update about 1.0.28 ?
(planning, problems solved…)

Do you have any specific issues you need resolving or just generally curious? :nerd_face:

A post by @PhilipsPrashant was split to a new topic: Current Bug / Planned Features list

This is a lot of fixes expected in the next version! Looking forward for beta-testers’ feedback on this!

Check the target version column. Not everything will make it to the next SW update.

i did already… its still quite a list! :slight_smile:

Hello @Philips_Support_P.

Gregory from passionhomecinema update his test with a custom apk designed for color calibration.
After his update, we can see a huge calibration improvement.

Where is this apk ?
I can’t see it in the roadmap.

Thank you

Hi @William this apk is accessible to beta testers only. Due to thermal concern we won’t release it until adaptive fan control is working. If you want it, being aware of the risks, please Join the beta testers list

1 Like

Just generally curious.
I read almost everything, i’am happy with my ppm because i found alternative to my issues.

I wait for :
feature 3
feature 14

And i’d like to have “Saving and loading images preset settings”
or something like that.
I believed it was evoqued, but i’am not seeing it in the list.

I’am little bit concerned about the Netflix apps that require a modification from Philips to work.
That’s mean that, when Netflix will change his apps and Philips not update it, it will not work anymore.

So, I know originally you wanted to release an update a week. That proved a bit too ambitious so a new system was thought up, one week internal version, one week public version.

That seems like it might also not be feasible? Not to pin you down on a date however, but what is your planned release structure? Assuming your team are sprint-ing through the issues.

1.0.26 - Public
1.0.27 - Would be public - but wasn’t ready?
1.0.28 - Internal only (continuation from 10.0.27?)
1.0.29 - will be sent to beta testers but not to public? If I read your sentence right.
1.0.30 - Will this be a public release finally?

Just trying to get an idea of structure of public releases that fits the iterative process of software development.

I have no doubt you and your team are working hard on improving the software, we’re just excited to see these improvements for ourselves :wink: