Friday, January 27, 2017

Acer reportedly won’t deliver the Windows 10 Anniversary Update for its Jade Primo

Acer released its Jade Primo device running Windows 10 Moble more than a year ago. The device featured a 5.5-inch display, the Snapdragon 808 processor, a 21MP rear camera and an 8MP front camera. The device was also one of the first Windows 10 Mobile devices to support Continuum for phones, which was really the main highlight of this device. The device initially supposed to be released in 2015, but it later got delayed as Microsoft wasn't able to deliver Windows 10 Mobile in time. And now, it looks Acer is dropping support for OS updates on the Jade Primo.

According to a statement to German site WindowsUnited by an Acer spokesperson, the company won't be delivering the Windows 10 Mobile Anniversary Update for the Jade Primo. Apparently, the Anniversary Update leads to "instability" on the Jade Primo, which is why the company has decided not to roll the update out after "thorough" consideration:

"Unfortunately, the Anniversary Update for the Acer Liquid Jade Primo leads to instability of the operating system. As the satisfaction of our customers is our number one priority and the current version is technically flawless and resilient, we have decided to refrain from an update after thorough consideration."

This is, indeed, quite concerning for Jade Primo owners as the Anniversary Update actually improved the performance and stability of Windows 10 Mobile on other Windows 10 Mobile devices. Microsoft is also set to release the Windows 10 Creators Update in the coming months, but it's unlikely Acer will release the Creators Update for its Jade Primo considering the fact that the company isn't even releasing the Anniversary Update.

Do keep in mind that you can get the Anniversary Update if you are part of the Windows Insider program — so if you really want to be on the latest version of Windows 10, you should probably join the Insider program and roll into the Production ring.



from MSPoweruser http://ift.tt/2kB2xDM
via IFTTT

No comments:

Post a Comment