![]() ![]() To check the three-digit identifier your device uses, find "Google Play services" in Android's "Apps" section of settings, and look for the last three digits in the version number (eg: version 7.0.99 (1809214- 430) ). If this is you, great! If not, flash at your own risk because apps relying on the services (which is most of them) could contain hickups. ![]() The current version, Google Play Services v7.3.27-438, is version 7.3.27, for Android Lollipop (4), armeabi-v7a architecture (3), and 480 DPI displalys (8). The more troubling aspect is that this file is model & OS specific. Calkulin has graciously pledged to update his post every time this happens, but it is an arduous task and requires vigilance on everyone's part. By its very nature, this file will be overwritten by Google when the next Play Service update is pushed, silently killing your device once again. Instead of the preferable system-wide solution, this flashable file is a modified version Play Services with the offending code removed. Recognized Developer Calkulin has thankfully stepped up with a partial fix in the OnePlus One forum, but it comes with a few caveats. Whack-a-mole hack - If you've made it this far in the post, my sympathies are with you and your battery.CyanogenOS - Fix coming next week? Read on for a temporary workaround, and check back with Cyanogen for more details.CyanogenMod 12.0 Nightly - Folded into the repo yesterday.CyanogenMod 12.0 - Folded into the stable repo yesterday.A solution from Google is the only way to ensure that this article never requires a followup. Gooogle Patch - This is a known issue.For your battery needs, here is the full rundown of your patch options from most to least effective. Obviously this is still imperfect, but is a clever trick that will hopefully appear in other Lollipop ROMs soon. The net result is that when the service checks for updates, it immediately fails and terminates. The Cyanogen solution elegantly re-enables SystemUpdateService, but restricts its receivers. There are several ways to go about solving this annoying issue, from custom flashable versions of Play Services to the more resilient official ROM patches for CyanogenMod and OS. But fear not, the solutions are already falling into place for this latest round of trouble. and the company even has an attractive identity theft insurance policy for good measure. It offers help in recovering from identity theft and its consequences. Any device running any ROM that either hasn't limited the SystemUpdateService, or is on Lollipop without a Lollipop-specific patch will see these wakelocks. PrivacyGuard can detect and alert you to identity threats early on, sometimes even before a financial loss and other damages occur. Getting back to the original question, the global nature of this bug means its reach is similarly widespread. This is obviously a problem, and leads to screenshots of plummeting battery meters and solid "Awake" lines flooding every forum within earshot. In essence, the phone is now woken up to perform a check, fails to contact the (disabled) SystemUpdateService, and continues to wait around indefinitely for a response that will never arrive. Starting with Android 5.0 and Gooogle Play Services 7.x, the update mechanism includes a wakelock checker. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |