A new update for LG Optimus 7! Version 7.10.8107 [UPDATE x3 - Bug Posts incorrect]

We have received the update on Vodafone branded LG Optimus 7, tell us via comments if even those branded with another provider are receiving the update. Being an operating system upgrade, expected to arrive soon on all Windows Phone terminals on the market.

The version of the operating system goes specifically to version 7.10.8107.79, the improvements listed below:

It solves a problem of the keyboard on the screen, preventing the keyboard to disappear while typing
Resolves an issue with syncing Gmail
It solves a problem of access to the location. After the upgrade, the function IO hub sends to Microsoft anonymous information contact the Wi-Fi access points and antennas for mobile phones in the vicinity, only if you have allowed access to and use of location information from part of the "I'm here."
Revocation of certificates issued by DigiCert Sdn Bhd to solve a problem of encryption
Fixes a problem with the e-mail related to Microsoft Exchange Server 2003. When you reply to or forward an email, the original message is now included in the response.
Fixes an issue of notification of voicemail
Update x1:
Below you can see 2 screenshots showing the version information between the terminal Vodafone LG Optimus 7, before and after this update:


Update x2

In addition to the improvements mentioned above, we can confirm that with this update, if you have unlocked the device by modifying the registry, the release is !
In addition, we immediately noticed a change in the settings, specifically in the "cellular network". Unlike before we have the "3G Connection" can be activated by a switch or not, but it was changed to "speed connection" with the ability to select the type of network that we use:


Update x3:
Yesterday, several users have asked if Microsoft had with this update also fixed the bug in the Windows Phone Messages ( Windows Phone: A serious bug disables the messaging hub receiving an SMS ). The answer comes from a tweet by Tom Warren of WinRumors:

Tom Warren, confirms that the bug is not resolved with this update has been, so the fix will come in the future on our end!

source