Notification sounds and received SMS commands

Avast Mobile Security Avast Mobile Security for Android
1

I have been trying out avast! Mobile Security, and it’s very good in my opinion.

There are a couple of things that I don’t like, but I am wondering whether they are caused by avast, or by the way my phone is set up.

I have a ZTE Blade (rooted) running “Swedish Spring RLS5 Remix2 - Phat One”. This has GO SMS Pro installed on it as the only SMS app.

When I send an SMS to my phone with (for example) the command “1111 SIREN ON”, the phone turns on the siren as expected and texts me back to confirm it.

However, all the SMS command messages received by my phone cause the phone to make its SMS notification sound, and the messages are stored within GO SMS Pro, meaning that they could be read (including the command PIN) if the phone was not locked with a PIN. There is no sign, however, of the outgoing SMS messages which makes me think that maybe the incoming ones should be intercepted by avast as well? Please can someone tell me what is meant to happen? I will have a play with some settings in GO SMS Pro and see if I can stop this, but there’s no point if this is the expected behaviour!

Also, when my phone sends the text back to say the siren is now on, my provider sends me a system message with my balance. This causes yet another different beep sound! I can, however switch off balance notifications through my provider so that’s not a big problem.

Apart from that, it is brilliant!

2

Hi nigelg,

custom SMS applications are known to interfere with the SMS commands due to the nature they are written, sorry.

Filip

3

Hi Filip,

Thanks for your reply. Is there an app that I could install for SMS that would not cause this problem? My ROM already had GO SMS Pro installed, so presently it is the only SMS app that I have.

Nigel.

4

Hi,

I would need to check them all, right now I don’t know any apart from the stock messaging application provided by Google. Maybe you could try to search for this one (package name should be something like com.android.mms).

Filip

5

Filip,

Just thought that I’d let you know that I have now tried Handcent SMS, and it works correctly.

Nigel.

6

OK, thanks, glad to hear that :slight_smile:

Filip

7

hello the only issue we have is with gosms. all other sms apps work fine. we tried to contact gosms because the problem is on how they use the sms system but the dev team seems to be dead. i recommend uninstalling gosms and use another tool.

8

yes, gosms pro is using some kind of SMS blocker which colliding with AMS call&blocker; I did find out, that some parts of this apps are not really safe, like the flex part and some strange methods used by externals API. Some of that could be the reason of conflicts.

9

I had a same problem with GO SMS on my Desire@Oxygen ROM… I had to uninstall it and use only default SMS app…
Then it works perfectly.

If you have pre-installed GO SMS as the only SMS app, then try to remove and try to use another one… maybe push the HTC’s SMS app ointo ZTE :smiley:

10

you can use ANY other SMS app except Go SMS - they all work as of our current knowledge.

11

I have the same issue.
Could it be the Go SMS private innboks feature that causes the problem? The feature intercepts SMSs aswell, hence you get a compatibility problem with Avast AT?

12

GOSMS uses a very uncommon way to access SMS - as the dev team of Go SMS seems to be no longer existing (no replies after several tries) we suggest using another SMS program.

13

GoSMS put up a new update release just yesterday as well as the new FB chat plug-in, so it’s safe to assume they’re still pretty much active.

Perhaps they are unresponsive because don’t see this issue as their problem, but rather, as Avast’s?

14

i have contacted them again today - hope they’ll answer soon. its not much of a thing they have to fix, but its annoying.

15

Hello Reinhard,

That’s good news. I suggest putting a note in upgrade description so users are informed it’s safe to use GO SMS, I suppose many of them don’t visit this forum reglarly.

16

they didnt answer yet - so no fix :frowning: