02-06-2012 10:41 AM
Welcome to the community.
You message implies that before you installed these two apps your battery usage was low and that now with just these two added it is high. If this is the case then I would be surprised as I do not think anyone else has reported it. If this is the case, may I suggest that you post details of the phone you are using, the version of Android and the versions of the two apps.
However you may like to look at the actual battery usage of your phone which you can probably get to from: Menu: Settings: About phone: Battery use. Just checking this myself, the only Norton app that is shown is Norton Security at 2% which hardly seems too worrying. In my case the main user it Voice Calls at 70%!
What does yours show?
02-06-2012 12:47 PM
I have version 2.3.4 android, and the android system is what uses the most battery at 70% and it doesn't even list Norton in the battery use file.
02-06-2012 12:49 PM
What settings did you configure in NMS and NAT? Did you change any of the default settings? Have you changed the discovery interval for NAT on the antitheft web portal?
02-07-2012 09:37 PM
My Nexus S with 2.3.6 has recently started to have the same problem.
I have had this installed for a couple of months and I have not changed any NAT settings and now it is showing NAT using 72%!
02-07-2012 09:40 PM
What's the update frequency set for NAT? Go to http://antitheft.norton.com and check for your device. Try decreasing the frequency and see what that does to the usage. It's possible that NAT is having difficulty getting a location fix leading to it using Location Services more.
02-08-2012 08:12 AM
It was set at 1 hour so I dropped it to 3 hours.
However, my point was that NAT has worked fine and that I have not changed anything and then all of the sudden in the past week or so my battery has started being drained by NAT.
Therefore, has something changed in latest update to NAT to cause this? I think this is where we should be looking.
02-08-2012 08:16 AM
Any ideas around when this started? The last update was over a month ago, so it could be something different entirely.