Did the update without any problems. But, don’t know if it’s caused by the update or just coincidence, I have a problem pairing the airmote now. Turning on the PPM it connects instantly to the echo bluetooth. And airmote is paired but not connected so I have to connect it manualy every time.
Most probably it as due to high Sharpness setting. That is why they made it 5% by default now. Otherwise the image was too sharp and the thumbnails were pixelated.
There is definitely a bug somewhere in that “Check for update”. I have seen it in the previous update I have done and this time I left a laptop on the same WiFi access point constantly monitoring the connection and there was absolutely no glitch in the Internet connection.
Also once the update was found I had 8-9MB/s download (that is 64-72Mbps) which is very good.
@Philips_Support_P can you tell me what is the URL of the check for update that PPX is calling?
I could try calling that with curl/wget manually from a device connected in the same WiFi as PPX (or even directly from the PPX if I can install Termux or something .
The link always points to the latest version, regardless of Params. But I agree there must be a different endpoint which returns latest available version number.
Ah no, previously that post was pointing to a generic endpoint that always updated to the latest version , not to the exact file. But seems it is now edited manually to the S3 storage of specific version. Sorry for the confusion, I should have checked first.
I guess PhilipsNono will keep editing the post with links to latest versions manually now.
Thanks alot Ivo! I’ve tried running curl directly from my phone playing with the version parameter and found that as long as that is something lower than 1.1.03 it will receive a 200 HTTP code and start downloading the image immediately. If you pass 1.1.03 (tried also 1.1.04) you get 404 HTTP code (Page not found) and no other content.
If found that in all cases where a download was supposed to start, it actually did albeit I did not wait for all my attempts to finish the download.
So it was very reliable.
Seems that the issue is somewhere in the update code on PPM which doesn’t not read properly the server answer.
After the update, projector is not saving the keystone correction, every start up I need to manually do it again, never had this issue before with previous versions.
The client side has bugs. The server side also uses non-standard HTTP headers in its reply and runs on top of Tomcat, preventing us from using a more reliable CDN. We are planning to replace it with a more stable system on top of plain https, and also rewrite the client-side updater. It will let us issue app updates without whole OS updates.