No luck even after disabling the service sms-activation-intex.service
seems like sms-activation-intex.timer launches it again

but both are disabled, still it sends SMS
(It was disabled as normal user not root)

Well, seems to be working for me when run as nemo. The journal has no trace of that service being executed after last reboot. But anyway, I rebooted again a while back, to be sure. Service status shows disabled when I checked after the reboot. Will update how it turns out.

For me it was showing disabled but no luck
I will check with devel-su now

You are right that didn't work. But this time the phone sent an SMS after four hours. Anyway, the status of sms-activation-intex.timer was shown as active all this while and service was shown disabled.

Is there a specific way to disable a timer? What I found in my search is to manually manipulate the timer file.

You could try to mask the sms timer with systemd:

systemctl stop sms-activation-intex.timer

systemctl mask sms-activation-intex.timer

If it's a user timer like the service you have to use the --user option.

Masking the timer with and without --user seems to be working

Right, masking the timer worked like a charm! Thanks mautz.

how about this link?

https://together.jolla.com/question/...rom-aqua-fish/

(haven't tried yet, my device is still on its way)..

How can i know , if my phone is sending this sms. I havent been able to see these said messages. After buying the phone , i have travelled internationally and used it in at least two countries . I still havent noticed any drop in my account balance. If it was sending messages , i would have at least noticed when i was on international roaming. Is there any logs or sent messages folder which i can check to see if this is happening. Or is this occurring to only few phones?

@Ravi, those actions can be found among journal entries.
As root, type #journalctl -b | grep sms-activation
-b returns journals in current boot. Anyway, Aquafish's journals are by default configured to be volatile and allocated a very small storage space. I made it persistent and increased the log size manually to monitor better. So if you are having a very long uptime, old entries might have already been popped out. To see the time at which your journal starts, simply type journalctl as root and check first line.