If you’ve got a supported device and are testing, you’re in for a surprise…
Ring master Gabe Aul from Microsoft has released Windows Mobile 10 Build 10136 to Fast Ring Windows Insiders as of noon-thirty CDT on 2015-0-16. If you’re a Windows Insider and you’re registered for Fast Ring Builds, AND you’ve got a supported mobile device, you can expect a little bit of additional love from Microsoft today. This build replaces Build 10080, released to Fast Ring Insiders on 2015-05-15; or about a month ago.
The first thing you need to know is that no new phones are supported in this Build. I have that directly from Gabe Aul:
I’m finding this a bit problematic.
There aren’t a lot of Windows Phones on the market. There really aren’t. I have a BLU WinHD LTE, and it has Windows Phone 8.1 Update 2 on it, but the device isn’t supported for testing Windows 10 Mobile yet. This may be partially because the WPRT (Windows Phone Recovery Tool) doesn’t have a Windows phone 8.x recovery image for it (yet??); or it may be because Microsoft just isn’t opening the device testing pool open to any non-Lumia device besides the HTC One M8 (but again… How many different types of Windows Phones are available, REALLY?!?)
Secondly, if you want to install this build, you’re going to need to do so from Windows Phone 8.1. You can’t do it from Windows Mobile Build 10080. The upgrade won’t be offered to you. To get the build, you’re going to have to use the WPRT (Windows Phone Recovery Tool) to restore your phone back to Windows Phone 8.1 and then go through any and all WP8.1 upgrades (recommended, but not required). After that, you’ll need to download and install the Windows Insider app, register for the Fast Ring, reboot your phone and then check for updates.
Once the update installs, it’s been reported that the upgrade lock screen will appear frozen, without the date and time on it, for up to 10 minutes. Stop! Leave it alone. It’s actually processing stuff in the background. The Windows Insider Team has instructed users experiencing this to be patient and let the device sit and finish. It will eventually show the date and time and allow you to unlock the device and use it. If you get impatient and restart the device or try locking/unlocking your phone, you’ll wind up in a “funky state.” Leaving the device alone so it can finish the upgrade process is the recommended and proper action.
In a nutshell, here are the changes:
Tons of fit and finish changes: There are far too many subtle changes in the UX to cover; but spit and polish are starting to be applied.
Improvements to Cortana: Cortana is now very close to the final design. She’s gotten smarter and she’s had some previously disabled abilities turned back on.
Photos and Camera Improvements: General improvements are available to everyone. If you’ve got a Lumia device,Lumia Camera Beta can also be your default camera app.
One-Handed Use: The experience on larger devices – those with a screen of 5 inches or greater – is now much better. Press and hold the Start button and your screen will slide down so you can reach items at the top of your screen. The screen slides back up when you tap the Back button.
- We have fixed the MMS bug in Build 10080, and you should receive MMS messages normally.
- We have fixed the issue where touch will stop responding on the Lock screen preventing you from swiping up to unlock your phone.
- We have fixed some visual glitches in Action Center when expanding/collapsing.
- We have fixed the issue where the text in the People app was too small.
- When you toggle the Wi-Fi quick action in Action Center, it now disables/enables Wi-Fi instead of taking you to the Wi-Fi Settings page. This was one of the top 5 pieces of feedback we heard from Windows Insiders.
- Your Start screen background should be scaled correctly now.
- You can add a detailed status to display on your Lock screen from apps like Outlook Calendar without having the Settings app crash.
- We also fixed the issue where a mouse cursor would appear when pressing the back button on your phone.
- After upgrading, you will still see duplicate tiles for apps like Search and Phone under All Apps.
- If you have too many PIN unlock attempts, you’ll see the “enter A1B2C3” reset experience. However, there is an issue in this build where after you enter the code you won’t see the PIN pad. The workaround is to press Emergency Call after entering the code, then press Back and you’ll be able to enter your PIN.
- We recommend disabling the double-tap-to-wake feature on some Lumia devices by going to the Settings app then Extras > Touch > Wake to prevent any accidental PIN unlock attempts.
- There is an issue that may cause Skype not to work after upgrade. The best workaround is to uninstall Skype on Windows Phone 8.1 *before* you upgrade to this build and then reinstall it after upgrading. If you miss that step though, you can usually resolve by uninstalling it and reinstalling from the Store once you’re on 10136.
- If you’re having issues installing new Language Packs in this build, see this forum post.
You can check out the specifics on the Windows 10 Blog, here.