Windows 10 Mobile - 10586.63 - a change with no identity

MS released the 3rd Cumulative Update to Windows 10 Mobile - Build 10586.63 to Fast Ring folks Friday Jan 8.  

 There was literally no announcement on the Windows Insider Blog - so therefore there is no detail on what exactly changed from 10586.36 released on Dec 17. 

 But obviously these "fixes" are trying to address issues with the new 950/950XL line.  But as to what they are... its a big question.

 As always I updated 1 x Lumia 735 and 2 x Lumia 635 devices and again as always - the install downloaded and installed without issue.  A Store update afterwards downloaded updates to XBox and Motion.

 Browsing around after the update - there were still a few tiny issues.  For example  in All Apps a few apps have a blank icon box.  Additionally in settings/extras - the display selection has a lower case "d" instead of Caps.

 I have noticed a little jerkiness to the screen with 10586.63 as well.  In the past this has indicated to me that maybe the update was not perfectly clean and that maybe I need to perform a reset.  But for right now avoiding it since I hate having to reconfigure start screen, etc..

 As I mentioned in a previous post - MS has continued this 10586.xx build sequence for these updates for Lumia.  This to me continues to reinforce my theory that Lumia devices will not go down the Redstone branch of Windows 10. 

 Until I see an 11082 or greater build for Windows 10 Mobile - I have the feeling that Lumia is in maintenance mode and that they will only get 10586 variant builds.  So if you just bought one of those shiny new 950s - chances are you are only going to get updates for maybe a year - then thats it.

 The interesting question will be - just as MS has effectively dropped app updates for WP 8.1 - will this happen to WP 10 Lumia devices once Redstone has completed..  

Comments

Post a Comment

Popular posts from this blog

Solar Storage - 2023 Update

  A few years back I published a 2 Part post discussing Solar Energy systems.  The discussion focused on all the due diligence and prep work needed and what were some of the key considerations around designing and implementing a solar system. One of the discussion points was around solar storage or batteries.  What were the use cases for batteries and if they were a good investment and should you incorporate them into your design. Back in 2020 - the math around batteries said no - that you wouldn't be able to break even on the cost of a storage system over its normal warranty life of 10 years. So here we are three years later and so I figured it was time to revisit.   There are two primary uses cases for solar storage.    First is what's called peak offset or peak shifting.  This is a concept where you utilize stored solar generation to run your home during what many utilities call Peak Periods that are part of a general category of rate plans known as Time of Day (TOD) plans.
Read more

ASUS RT-AC68U Router & WDS - a nice solution for a large home.

I recently had a newer Asus RT-AC87U Router die.  The wireless chipset never seemed to work well and first the 5Ghz bands started to fail and then the 2.4Ghz failed leaving my 25 wireless device household high and dry. So after some due diligence I decided to replace with 2 of the older RT-AC68U and implement a Wireless Distribution System (WDS) configuration. In the past - I've mentioned an open source router OS called DD-WRT.  The Asus routers come pre-installed with their version of DD-WRT.  Asus does utilize their own UI overtop DD-wrt and overall I do not like nearly as much as the traditional UI - but core dd-wrt capabilities are there.   Additionally you can flash the RT-AC68 with native DD-WRT if your so inclined. In my previous configuration I was also using an older Linksys 4200 running dd-wrt configured in Client Bridge mode that allowed clients to connect to the Linksys as well as use some of the bands to connect back to the RT-AC87U. While it worked - I felt that
Read more

Home Automation Platforms + Matter - Early Observations

For those of us who have been involved in automating homes by adding "smart" devices from light switches to thermostats, cameras, sensors, controllers, etc - there was always a challenge with managing the wide range of devices. While each OEM had their own app that would allow you to control their devices - you'd often end up with anywhere from 4 - 10 apps that were required to manage the entire home.  And depending on your product choices you also had to have hubs to communicate from your Wifi network to other RF networks like Zigbee or Z-Wave.  With many of these "hubs" they had native support across multiple vendors or you had to add plugins or provide specific OEM support. Some OEM apps were great, some sucked, but it became challenging to provide a solution for a client where they could easily manage their home on their own.  Between having to maintain multiple credentials/logins across the apps and even communicating which app controls what - it sometimes
Read more