I was not allowed to edit my previous comment. I should have said that T-Mobile and Trac Phone customers of Android phones who are using the same Kit Kat 4.4.2 version are experiencing the same problem. Prior and later versions of Kit Kat are not seeing the same problem. Google+ was upgraded by the Android upgrade to Kit Kat. It was that upgrade which also upgraded Google+ which broke the AVS Service, not the other way around. THAT is why disabling Google+ or deleting the latest upgrade restores the AVS Service. If, as you wrongly keep insisting, it is the AVS Service which is the cause of the problem, then Verizon would be telling you how to disable the AVS Service. They are not doing that, because it is Google+ causing the problem; so they are telling you to disable Google +. Fix the problem caused by the Android upgrade, and both Google+ and the AVS Service will work together, and play nicely without any further problems.
Google+ is not the operating system, it is merely an app to play games, buy things, access social media etc. The operating system is Android Kit Kat. The AVS Service is what allows banks to verify your address when you try to make a purchase over your phone, and it is what allows 911 to verify your address when you make an Emergency call. If it is not working, there is a chance that your purchases will not go through, and you might not be able to get through to 911, if Google+ is not working, you might not be able to play Candy Crush. OMG!
There is a newer version of Android Kit Kat available, which completely solves the problem. I assume since you know so much already, that I don't have to tell you how to find it or install it. Verizon is aware of this updated version, as they use it on some of their more expensive phones. Nice to have both Google+ AND AVS Service working at the same time. Good luck. TA!
I'm not buying it.
If the AVS Service is broken on T-Mob and Tracphone I can't find a single link to it. If it's broken there it should also be broken on Sprint and AT&T and there's nothing there either.
Verizon is the ONLY provider where I can find ANY mention of the AVS service having issues. And just because you say it's the Address Verification Service does not make it so. Again, no one seems to know what this service is doing. And if it was a true AVS service, why would Verizon need to make their OWN version (denoted by the VZ). This is a Verizon issue, not a Google issue. Unless you can point me to an authoritative source that says the VZAVSSERVICE IS the Address Verification System Service, it stays disabled. The only link I found that says it's the Address Verification Service is a link from an Android forum, to, guess what, your post on the Verizon forum.
And as for Verizon having an updated version for their more expensive phones, more bullhockey. I have a brand new G3 and many have an S5, I doesn't get any better than that.
I'm having the same issue/error. Also, has anyone else noticed, since you started getting the VZWAVS error on reboot, that your gmail push has stopped working? It may just be coincidence, but about the time I started seeing this error, push for gmail and google voice stopped working as well--I have to open both applications for them to sync...
The push for my Gmail and Google Voice seems to be working just fine with this error. I have neither disabled the VZWAVSService or Google+ and still get the message the few times I reboot my phone.
I HAVE disabled the VZWAVSService, have the updated Google+, no longer get the "Service has stopped" (it's disabled!) and my Gmail and G+ notifications have not stopped at any point, even when I WAS getting the error. I funnel several email accounts through my Gmail, and would notice if it stopped pushing - emails are coming in constantly!
It like everything else should be able to be updated.
I wonder if something like this also shares some relationship to NFC and other pay-using-phone services similar to ISIS wallet, like Google Wallet. Could these crashes be removed or otherwise eliminated by having NFC turned on?
I have KitKat on my S3 and have never seen this error appear. Another S3 which I was replacing for a co-worker, experienced this error only once, during which time I was updating all of the applications on their phone.
Good grief. Just want this thing fixed.
Start a new topic or ask questions in the open forum.
