Definition Update Failed

I left WSA for another product a while ago, just after all this started and I'm now certain I was right to do so for my own sake.  The other product has as good a reputation as the Webroot product and it updates reliably.  So if memory management is the same for all Android applications which, of course, it is then I would have to assume that the product I am using is designed and coded differently to avoid such issues or, as you indicate, its developers are limiting the size of its threat register to avoid them by shedding some low risk definitions.  
 
If it is not shedding threat definitions and is dealing with the same range of threats as WSA, then it looks like it has managed the memory issue in a way that has eluded Webroot so far.   So far as I understand it,all  these security products rely on having a register against which to check for threats and, it seems to me, as the number of threats grows these registers are going to have to grow as well.  It could well end up as a race between these registers and the amount of system memory installed (and its management).  Sooner or later, a brick wall is going to be hit because memory can't be infinite while the number of threats could be in comparison.
 
WSA and its competing security products are, I guess, sooner or later going to have to undergo a root and branch re-think and re-design to minimise the dependence on an ever growing register/database of risk defintitions.  They are going to have to work differently.  Don't ask me how, I have not idea but it does seem to me to be an impending issue.  At the same time, it also seems that Android itself could do with a massive security overhaul.

We're sorry to see you go Jimbo. 😞 If a potential solution becomes available for the remaining affected users, we'll be sure to update this thread. In the meantime, you'd certainly want to have some protection on your device, so it make sense to do what you're doing for now. We'll continue to do everything we can to try to work around this issue. Just because it's affecting a small number of users doesn't mean we've given up on trying to solve the problem, but waiting for a fix in an unprotected state is inadvisable. So, you're doing the right thing for now. Hopefully we'll have some better news next time we post in this thread.

The story continues ...
 
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.

I also have this problem now.  Starts with "Definitions Update Failed".  After clicking through 'fix now', i get a 'network error attempting to access the Webroot servers".  I have verified i'm connected to the internet.  Suggestions?

Hi!
 
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. 3.2.0.5065 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?)
 
 
 

Will do. Thanks!

Unfortunately, my phone is having this problem again and it won't clear itself like it used to when I run a scan. Please help (see user name). 

The uninstall/reinstall suggestion or forcing a definition update will most likely resolve the issue.
 
Force Definition Update: Open SecureAnywhere>tap Security>tap Antivirus>tap Schedule>tap Force Definitions Update Now

Did you renew to a new suite? For example, from Internet Security Plus to Internet Security Complete? I only see the Complete subscription and if you upgraded the keycode it should have automatically mirrored the new days onto the mobile Complete app.

They are definitely covered under your Complete subscription. Just open the SecureAnywhere apps and tap register to make sure that they are using the keycode that I just sent you in a private message.

You can do a fresh uninstall/reinstall of the Complete app on your HTC device and use the keycode that I sent you via PM. Also, the sales number is 1-866-612-4268 if you would like to see if the seats can be adjusted for you. 😃

Thank you for the update - I am glad that worked. I removed the trial keycode as well but you can still contact sales to discuss how many seats you would like.