Android 5.0 Lollipop
Android 5.0 Lollipop seems to have been hit by means of another Wi-Fi related Trojan horse that’s giving issues hooking as much as Wi-Fi networks to users presently running the most recent Android construct on their Nexus units. The Trojan horse up to now would not appear to be affecting non-Nexus units.
Google on Wednesday eventually introduced the Android 5.0 Lollipop OTA rollout for older Nexus units (specifically, the Nexus 5, Nexus 7 (2012 and 2013), and Nexus 10) alongside Motorola, which also began rolling out an OTA replace for its 2d-generation Moto G and Moto X smartphones.
Reporting the Trojan horse on the Android-Developer Preview web site titled “hassle connecting to a few Wi-Fi networks”, the Android 5.0 Lollipop customers are claiming that Nexus gadgets are failing in Wi-Fi connection.
Google has mentioned the difficulty and a challenge Member notes, “thanks for reporting this difficulty. We have now passed this on to the development team and will update this difficulty with extra data as it turns into to be had.” The Google worker however did not give a time period for the problem being fastened.
Android 5.0 Lollipop Wi-Fi Bug Affecting Some Users
One of the crucial users said, “I’m having the same issues [Wi-Fi connection] on my new nexus 9 tablet. My nexus 5 connects no problem to my work Wi-Fi, however the nexus 9 tries to attach after which offers me the message network saved. No connection. Have tried all the above ideas, no good fortune.”
Some other consumer claimed to be running an official Android Lollipop build wrote, “Having the same problem at work on our guest WI-FI network. After I enter my password it never connects it simply sits there saying it is connecting but it surely never does…i am running the respectable lollipop build LRX21O.”
Particularly, the Android 5.0 Lollipop global rollout was past delayed until November 12 due to some ‘outstanding bugs’. The worm was once later mentioned to be the Nexus 5’s battery drain Wi-Fi computer virus that caused the rollout of the latest version to be delayed. Google alternatively very quickly acknowledged the battery drain difficulty and even claimed that it was once mounted.