If you’re a Verizon Wireless customer who just happens to own and use the LG G3, you may or not have been surprised to find out that the network’s advanced calling feature was not present on the device at the time of purchase. Whether or not that affected you is another thing entirely. The good news is that Verizon is now rolling out an update to LG G3 users that finally turns on the support for the Advanced Calling 1.0 feature of the device, which should bring in HD quality voice, 1-way/2-way video calls, and 6-way conference calls over LTE data. That’s a whole lot of goodies and extras for people who engage in voice calls as a primary part of their phone plan, but that isn’t the only thing coming along with this update.
The usual bug fixes and improvements apply here just like with any software update pushed out to a device, but one notable fix is pointed out by Verizon which seemed to be a prominent bug people were having where the email inbox would persistently show that the emails were updating whenever a user switched folders. After this update, whenever you switch to a different folder inside of your email inbox the update should happen normally without hanging in that update status.
Verizon is also updating a handful of their specific carrier applications on the device too, including My Verizon Mobile bringing it forward to version 10.0.710, the Softcard Wallet app is being updated to version 2.02.01, and the GMSR5 application. Alongside those apps there is a selection of LG specific apps that have been updated as well, which includes the Contacts, Email, LG Backup, Camera, and LGLTECall applications. In the world of Android, software updates to the OS version are certainly the most exciting, but little updates like this one are still essential and provide a better user experience, or at least that’s the goal. If you use an LG G3 on Verizon’s network, let us know what you think of the Advanced Calling 1.0 feature, and whether or not the email updating bug has really been fixed for you, that is if you ever had the issue in the first place.