View Single Post
Posts: 114 | Thanked: 381 times | Joined on Jan 2014
#1
So this now is an annoying issue for many Aqua Fish owners. And some claim, they don't have it. Anyway, I hope this thread can give some insights or even possibly solve the issue on Aqua Fish. May be the next update will solve it, but patience has limits and curiousity does not.

This is what I know. At every boot, systemd starts a service to send an sms to a predefined number after three hours of uptime and stops the service.

Code:
[root@Sailfish nemo]# cat /usr/lib/systemd/user/sms-activation-intex.service
[Unit]
Description=Sends an activation SMS to Intex

[Service]
Type=simple
EnvironmentFile=/var/lib/environment/sms-activation-intex/sms-activation-intex.conf
ExecStart=/usr/libexec/sms-activation-intex

[Install]
WantedBy=user-session.target
I suppose commenting "ExecStart=..intex" should prevent the code to send sms from executing.

The coonfiguration file has the number to which sms is sent.
Code:
[root@Sailfish nemo]# cat /var/lib/environment/sms-activation-intex/sms-activation-intex.conf
INTEX_SMS_ACTIVATION_NUMBER=+919582943043
INTEX_SMS_ACTIVATION_DONE_FILE_PATH=/mnt/vendor_data/.sms-activation-intex-done
So I checked the path which mention the activation completed file. And there is no ".sms-activation-intex-done" file created, which may be triggering the sms sending procedure after a reboot again.

Can I simply delete the .service and .timer files, of course after making a backup at some other location? Or how can I prevent that being run at every boot?

And could AquaFish owners who are not facing the recurring sms issue please check location /mnt/vendor/data for the file ".sms-intex-activation-done" and share its content if that doesn't seem to be something confidential like a unique activation code.

Update:
Masking the timer seems to be a working solution for now.
Refer this post. Thanks to mautz!

Last edited by lal; 2016-08-03 at 02:42.
 

The Following 5 Users Say Thank You to lal For This Useful Post: