Also, DEFINITION UPDATE FAILED. Network error attempting to access the Webroot servers. Please ensure your device is connected to the Internet.
Also, Webroot Secure Anywhere Mobile Premier (process com.webroot.securing full) has stopped unexpectedly. Please try again.
DEFINITION SET 330. Version 22.214.171.12459.
Is somebody know what to do??? The HELP recommended to post on FORUM to get E-mail from MODERATOR to send collected system data from phone for tech support. Or may be it would be solved by itself??? For example, via updates?? But how come, the updates fail to be installed?
Best answer by MikeRView original
Not sure what to do now...
I did not add any coverage, nor did I cancel any devices. I merely renewed my contract. I have always had two phones and my computer registered with you.
Please take care of this.
Force Definition Update: Open SecureAnywhere>tap Security>tap Antivirus>tap Schedule>tap Force Definitions Update Now
Have you tried to uninstall and then reinstall? That sometimes helps update problems. Let us know if that works, as others may have additional ideas and you can also Submit a Trouble Ticket as well.
I started getting these OOM errors around a week ago with the WSA Complete app. My last successful definitions update was 468. Before this, it worked fine on my HTC Desire 2.2, even if the phone was fully loaded with other apps.
I've tried everything. I even did a factory reset on my phone and reformatted the SD card, and installed the app again. Now the current definitions are 464 and utdates fail with OMM errors.
There is only one other third-party app on the phone now, and available RAM seems to be around 100MB + 185MB.
I suspect it has something to do with v. 126.96.36.19965 released on March 5.
What a novice like me do find a little strange, is that the amount of RAM the WSA app is using is varying from 15MB to 85MB when the phone is passive (just being monitored).
(What's even stranger, is that nobody else is mentioning this. Do they just uninstall the app and never look back?)
Can you kindly revert with result after upgrade to the latest version (188.8.131.5242) from the Google Play as Mike suggested? We would like to monitor whether the OOM error has been resolved for all devices. If the upgrade doesn't resolve it for you, could you inform about your Android device?
Thanks & regards,
"Definitions Update Failed" errors should be resolved. Please try updating the app from the Google Play store.
I underwent an extensive testing of the latest 3.1 build on my HTC focusing on the definition set updates which were malfunctioning due to the OOM error. I was playing with the date & time, I was shifting them back and forth to see if AV definitions will be automatically installed or the error will be occuring again. I have got satisfying results ... AV definitions were installed successfuly and no more errors appeared. After that I reverted the date & time back to the actual and waited for updates as per the set schedule which resulted in receiving AV set 400 yesterday and AV set 401 today.
Therefore I dared to proclaim the OOM error was defeated :D
I want to express my thanks to all at Webroot who contributed to resolve this issue. Well done ;)
Furthermore, I want to encourage all users who were plagued with the OOM error to share their experience with the latest 3.1 build.
Thanks & regards,
I am anxious to hear how it is going after a few days of use in the field.
Thanks Jim, Roloc and others of Webroot for your hard work to beat this error.
Stay tuned ;)
There will be improvements in version 3.1 that may help to address the remainder of the OutOfMemory issues still being experienced. 3.1 should be available soon, but we don't have an exact date since Google still has to go through their QA process. Roloc or I will reply back again when it's out. 🙂
Yesterday WSA auto updated to AV set 391. It was the first time when it was done automatically without necessity to undergo terrifying terminating/restarting procedure stated in my above post. However today WSA automatically checked for updates (observed notification Last checked for definition update on 22.11.2012 at 7:50) and reverted definition set to 373. It seems that this AV set plays an important role in this OOM error issue. I have checked the web console and again there was last definition update before 42 years. Funny thing, indeed. So then I manually run update and received AV set 393 what is now correctly recorded in the console.
Sorry for bothering with my posts in this thread but I want to give Webroot staff as many information as possible. On the other hand I would appreciate Webroot breaks its silence and begins to again communicate via this thread or PM.