|
2016-07-31
, 12:27
|
Posts: 367 |
Thanked: 1,442 times |
Joined on Feb 2015
|
#2
|
|
2016-07-31
, 13:06
|
Posts: 367 |
Thanked: 1,442 times |
Joined on Feb 2015
|
#4
|
|
2016-07-31
, 14:37
|
Posts: 20 |
Thanked: 75 times |
Joined on Jul 2016
@ India
|
#5
|
|
2016-07-31
, 16:25
|
Posts: 20 |
Thanked: 75 times |
Joined on Jul 2016
@ India
|
#7
|
The Following User Says Thank You to bhavin192 For This Useful Post: | ||
|
2016-07-31
, 16:59
|
Posts: 635 |
Thanked: 1,535 times |
Joined on Feb 2014
@ Germany
|
#8
|
|
2016-07-31
, 17:18
|
Posts: 114 |
Thanked: 381 times |
Joined on Jan 2014
|
#9
|
|
2016-07-31
, 17:21
|
Posts: 20 |
Thanked: 75 times |
Joined on Jul 2016
@ India
|
#10
|
The TJC post has nothing to do with the sms service described here.
just stop the service with:
systemctl --user stop sms-activation-intex.service
and see if the problem is gone. To disable the service permanently use:
systemctl --user disable sms-activation-intex.service
Tags |
activation sms, aqua fish, intex |
|
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.
The coonfiguration file has the number to which sms is sent.
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.