As prompted by the tablet, I authorized a Android Jelly Bean update on my Nexus tablet. All went fine except I can no longer open NMS (version 3.0.0.697). When i try to open NMS, I get the following message : "Unfortunately, Norton Mobile Security has stopped".
I bought on Google play the full paid version of the App, so i would like to know the best course of action so as not to loose my App and my money...
Any one from symantec that could help??? Thks in advance
Ok, thks for that. My device actually works fine. Every now and again, the same message from NMS pops up saying that it has stopped. I just ignore it and all is fine. I do understand that i am probably not currently protected until the issue is sorted, hopefully in the coming days.
However, updates normally occur automatically. Is there a possibility with this bug that my NMS will not update automatically???
If you have your device set up for automatic updates and do not uninstall then it should update automatically. Which is good. However other apps may also update and not be checked by NMS - not so good but the risks are probably not high for a few days.
If you have not had an update by the middle of next week then you can always come back to this forum and see if an update has been reported.
I have the same problem on my nexus7. As a sort of workaround I uninstalled Norton and reinstalled an earlier version which works ok . Hopefully it will give some protection till a proper fix arrives Joe
As prompted by the tablet, I authorized a Android Jelly Bean update on my Nexus tablet. All went fine except I can no longer open NMS (version 3.0.0.697). When i try to open NMS, I get the following message : "Unfortunately, Norton Mobile Security has stopped".
I bought on Google play the full paid version of the App, so i would like to know the best course of action so as not to loose my App and my money...
Any one from symantec that could help??? Thks in advance
For all of you with the problem caused by the latest Google upgrade to JellyBean. Norton have now released an update to Norton Mobile Security taking it to 3.2.0.769. I would expect that to contain the fix you need. Why not try it and let us know if it solves your problem?