13
Planned

Tasker to register for default SMS app

Since Tasker has been green lighted for SMS/MMS, would it be permitted if Tasker could register as default SMS/MMS App?
 
I suggest this idea as with the SmsManager class/objects, we could control SMS/MMS much more. This would include building our own SMS/MMS apps, backing up/restoring, organising and filtering as well as blocking/spam filtering. It would also allow us to see hidden short codes from those dodgy SMS spammers.
 
Essentially, Tasker would just need to register it for now, rather than you make anything forward facing for it. Java could then do the rest. I for one would start experimenting with SMS Backup/Restore features.
 
Pretty please 😁
 
Thank you!
Follow

5 replies

Votes Newest Oldest
SC

Any news on this ?  I'm really keen for this one!

Comment
IG

TBH, you can just give Tasker the permission via ADB `appops set net.dinglisch.android.tasker WRITE_SMS allow` and it can delete SMS via Java Functions. It can already read and send with the SMS access it currently has. Admittedly, I haven't tried this since Android Pie.

Comment

Thanks for the extra info! :)

Just leaving this here for when I have the time to implement it: https://stackoverflow.com/a/30133663/1002963

Comment
DG

Did this idea invoke enough interest? I think this would be highly useful.

Comment

I actually planned to do this eventually so that Tasker could delete SMS. We'll see how it goes from there :)

Comment
Reply