We’re rolling out Windows 10 Mobile Insider Preview Build 10549 right now to Windows Insiders on the Fast ring. However, this build comes with a caveat. We discovered a bug late last night that caused phones upgrading from Build 10536 to get stuck at a black screen after this new build is installed. Rather than making you wait a little bit longer for us to fix this bug – we decided to release this build as a single update from Windows Phone 8.1. Current Insiders that would like to try out Build 10549 should:
- Go back to Windows 8.1 first using the Windows Device Recovery Tool.
- Once you’re on Windows Phone 8.1, install the Windows Insider app, choose the Fast ring, and reboot your phone.
- After that – this build should download and install on your phone.
If you choose to remain on Build 10536 – that’s fine too. You will not receive today’s build but we’re working to ensure you’ll be able to receive the next one. We know having to go back to Windows Phone 8.1 to get this new build is a bit of work. By doing so you are also helping us test the upgrade path that millions of Windows Phone 8.1 customers will take to upgrade to Windows 10 Mobile, so we appreciate the adventurous Insiders who choose to go this route and give us feedback.
Here’s what’s new in this build:
Improvements to Cortana: Cortana now works for Insiders in Japan and in English for Insiders in Australia and Canada. For more information on new languages in Cortana – see my post here.
Messaging app improvements: The Messaging app now has a text box that can be expanded as you enter text. Previously, the text box had 2-3 lines which made it really hard to see what you were typing. As I mentioned yesterday with Build 10565 for PC, an upcoming build for mobile will include the integrated Skype capabilities for you to preview.
Diverse emoji: With this build, we are adding support for Unicode’s diversity emoji’s. Consistent with Unicode’s vision, we’re excited to offer people all over the world with emoji that reflect more human diversity. We added this capability to the PC with Build 10547 and now we’re extending to mobile. Check out our new diverse emoji and let us know what you think.
An update for Lumia 1020 users: Lumia Camera is no longer uninstalled when you update to Windows Mobile 10, so you can continue using it when you update your phone from Windows Phone 8.1. You should use Lumia Camera in order to take advantage of all of the Lumia 1020’s great camera capabilities. Lumia Camera is not yet available in the Store for Windows 10 devices so you will need to use the Windows Phone Recovery Tool to return to Windows Phone 8.1 in order to get the app back.
Here are some things we have fixed:
- The Windows Camera app no longer crashes when certain applications launch it to capture a picture.
- We fixed an issue where the touch keyboard would get dismissed every time you sent a message, which made sending 2+ texts in quick succession difficult.
- We fixed an issue where swiping away a notification was causing the notification icon to appear top of your screen.
- Screenshots were not being properly saved resulting in many top social messenger apps such as WeChat, WhatsApp, LINE, WeiBo, and QQ unable to find saved screenshots. This has been fixed.
- We fixed an issue where you couldn’t launch apps saved on SD cards after reinserting your SD card.
- Pinch to zoom should work properly in the Maps app now.
- We fixed an issue where trying to set a custom ring or text tone for a contact shows a black screen for 10 seconds, then does nothing.
- We have added back vibrate-only alarms.
- We have fixed call-blocking.
Known issues:
- After upgrade, you might be missing a few apps. If you experience this, the workaround is to reset your phone.
- After rebooting your phone, you won’t see notifications, such as new messages, until you unlock your phone for the first time. After that, you should see notifications for new messages just fine. This bug is fixed in a later build.
- You will be unable to make calls with Skype for Business, WhatsApp and other apps after upgrading to this build. The workaround is to uninstall and reinstall these apps from the Store.
Thanks,
g