Comodo Mobile Security (CMS) v2.0.275481.10 is now released on forum.

I’m experiencing the same updating bug (keep updatingto version 87).
I spotted another bug: it uses too much battery while scanning apps being installed or updated.
I have 100% on battery and I update 7 apps with Comodo. The process is three times slower and it drains my battery to 96%.
Without Comodo or using another security product the process is faster and battery goes to 98 - 99%.

Please fix and optimize this.

yes, its a bug. we will fix it soon. thank you

Thank you for the info :-TU

I keep getting an error when trying to update I’m on definition 86

The remote erasing data is formatted internal or external SD-card?
I’m sorry for my english :wink:

I have just changed phones from a Samsung Galaxy S3 to the S4 and it’s failing to update, not sure if it is the device change though, presently on Version 86.0 virus definitions :frowning:

All CMS users experience the same thing now it has nothing to do with your phone. It’s a bug in the CMS update which is being fixed that’s why. Just wait :slight_smile:

Oh well yes its a bug that means… I get error saying Update failure…
Initially I thought it was coz I updated the device from GingerBread to JellyBean but seems it ain’t so…

I feel that CMS development is very slow.

When things don’t go right, you get to see the difference between a free app and a paid for one!..come on comodo, how long does it take to fix this update issue ?

Hi, sai !

CMS plans to release a backdrop for Windows Phone?

I too feel the development is slow & Devs dont give much attention to CMS threads.

And there is no false positive submission thread. I know you can submit FP through CMS but submission in the forum are solved fast as in the case of CIS. But do they solve FPs in CMS case? I submitted couple in the forum here too many days back, they are still detected by version 1.5 & 2 too. I know they can be added to trusted lists but FPs need to be fixed.

I personally feel comodo needs more programers of higher quality and maintain release notes better. they could also get rid of some programs

Hi trscsaeg,
This is possibly true, but then again if it was an ideal world there would be no need for security devices. :wink:

Just to let you guys know that the CMS 2.0 update bug seems to be fixed. Latest virus database 88.0 :-TU

Welcome to the Forum, alen sheriff.

What is not working? And are you running stock sms?

Sorry CMS IS VERY GOOD ;D :viva:

New CMS 2.0 update bug?

  1. Open CMS 2.0 and run the update you will get VD version 88.0 again (if you had it before).

  2. After try to check for the VD update again it would say that the database is up to date.

  3. Exit CMS 2.0 and run the CMS 2.0 again if you check for the update it will load VD version 88.0 again (if you had it before).

Yes, I have the same problem.

Idea of an improvement of updating process:

  1. Now, database is updated only when user opens CMS interface (otherwise, CMS will not check for the updates). Sadly, many users install a security app and want to forget about it. They don’t open it at all → CMS has obsolete databases all the time, it cannot detect newest threats. It should be changed - maybe another service checking for updates every time when user will connect to the Wi-Fi etc. (depending on user’s settings). without user’s interaction.

  2. Health Check - Health Check scans for malicious apps and many other risky things. Unfortunately, update logic here is not correct. Health Check first of all check for malicious apps and in the end of this process it checks for the updates. That doesn’t make any sense.
    How should it look like is:

  3. User starts Health Check.

  4. CMS checks for updates&downloads them and install (if available).

  5. CMS starts preforming a scan.

I hope they fix it soon for good. I see. +1^