Webroot is actively working to address the issues with the Webroot Mobile Security & Antivirus app and again apologizes for any inconvenience you may be experiencing. So far, our QA testing indicates the 5.5.5 beta version shows improved app performance and reduces device resource usage significantly.
We want to release an update as soon as possible but we have yet to complete a full QA cycle.
This is where you can help.
If you're able, please head over to our beta signup page to request access. After completing the steps, you'll be able to download one of the beta builds as we'd love to hear your feedback while we continue our internal dev and QA work. Again, this isn't mandatory nor the official release but receiving real-world feedback will greatly expedite the official update.
This topic has been closed for comments
Page 2 / 5
Got another update for everyone:
Update - 4/17/19 - WSA Mobile 5.5.5 is now available to all users in the Google Play store. You will receive an update notification soon if you haven't already. This release improves app performance, responsiveness, automatic scanning functionality, and battery consumption.
Customers who have already installed our beta version are on the latest version. No action is required on your part. The beta group will be closed when we release the next version of WSA Mobile and you will be notified to upgrade to the latest release.
If symptoms persist after upgrading to version 5.5.5, please open a Support Ticket.
Does running a VPN affect the functioning of webroot v5.5?
I am using AdGuard AdBlocker for Android which acts like a VPN (the combo of AdGuard & Webroot worked perfectly previously).
I have tried disabing AdGuard, but still the same Error CODE_1011.
Thank you.
I do not believe that
But I don't believe AdGuard has anything to do with the Beta error that we are getting.. I run VPN (Webroot WiFi Security). So I just think we will have to wait for a fix..
That is a great question though.
Thank you
It's good if Webroot could confirm & rule out this possibility as we do not know what are the "Under the hood app security enhancements" implemented.
If you read through the reviews in Play Store for the release version, there are other users getting this error with v5.5 & they are running a VPN.
Have a nice weekend!
You're right.. April 2nd is the last scan log..
you beat me to that Daniel!
Had they been listening to beta feedback previously , v5. 5 would not be hastily released as final & affected more.....
You're right.. April 2nd is the last scan log..
you beat me to that Daniel!
Yes you are right about that! I wonder if the transition to Carbonite is effecting the Webroot Developers?🤔
It's certainly frustrating. I wish Webroot would roll back to the previous stable production release. That's at least a quick stop gap so more time can be spent on troubleshooting / identifying root cause.
--Patrick--
--Patrick--
Support answered my ticket after 4 days. That particular support agent was unaware of the battery & etc, etc, etc, etc problems caused by the update. They suggested I was misinterpreting causation and implied the cause wasn't the update. I didn't bother to respond because the information here in the Community is superior to what I received in reply to my Support Ticket.
Yeah like TripleHelix, with the v 5.5.5.38021, which was way better battery usage wise that before, I did catch that version with high usage yesterday for the first time as my phone got hot. But I was never able to replicate again.
As long as the devs are aware of this IN v 5.5.5.38021 as opposed to prior versions last week then that's good to know.
As long as the devs are aware of this IN v 5.5.5.38021 as opposed to prior versions last week then that's good to know.
User experience is similar to recent betas, but different enough from prior production releases to raise questions :
- Under 3 second scan time (I have over 300 apps on my phone). Don't know if this supposed to be case from initial scan. I do see network/internet activity from SecureAnywhere on each scan.
Is the app infrastructure keeping a database of prior scanned apps & hashes per user device, and subsequent scans just checks new/changed app hashes to send to Webroot for central analysis? If so, then is this db stored locally? I don't see one on the phone.
- Underneath the scanning status/progress bar there's no added visual indicator of file name scanned (prior production releases had it).
- Scanlog.txt not been updated since end of March.
- Setting control for persistent notification was taken out. Is this intentional?
Will be keeping an eye on battery usage over the weekend.
Exactly we need to know what to expect, but no they keep pushing these new builds but no details......
The Scan log is still at April 2nd..maybe after a few more scans or/and a reboot.. It might change unless Webroot has removed the Webroot Log txt.
THANK YOU Daniel!!😊
Maybe that's the way it is now? Like I said before we don't know what to expect as we are told nothing!
Since we haven't any Mobile Beta Support on this Forum.. Drew is all we got to contact the Developers. Why run the Beta without the questions and answers?
Appreciate some feedback someone please. 😊
With the Introduction of Webroot Mobile Security 5.5.5, we have improved the way we scan files and identify malicious activity on your device. We initially scan all files on your device and cache the results for those files. We then actively monitor your device for updates or changes and will scan any newly added files. We are in the process of rolling out an upgrade to the app to properly display a scan progress bar.
Drew I just hope there is more details in the Release Notes when it's released to everyone! So far it's working well it just doesn't show the files (paths) that are being scanned and wondered if that is the new normal?
Thanks,
Missed your post earlier. But thank you for the update! ☺️
Yes thanks for the update
Does running a VPN affect the functioning of webroot v5.5?
I am using AdGuard AdBlocker for Android which acts like a VPN (the combo of AdGuard & Webroot worked perfectly previously).
I have tried disabing AdGuard, but still the same Error CODE_1011.
Thank you.
HI
I do not believe that
But I don't believe AdGuard has anything to do with the Beta error that we are getting.. I run VPN (Webroot WiFi Security). So I just think we will have to wait for a fix..
That is a great question though.
Page 2 / 5
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.