ScumStopper
Call blocker for SailfishOS.
ScumStopper now has a SourceForge project. For advanced usage instructions, see the Wiki page. For the source code, see the Git repository.
Category:
Application versions:
| Attachment | Size | Date |
|---|---|---|
 harbour-scumstopper-0.1-1.armv7hl.rpm | 66.97 KB | 10/08/2014 - 20:12 |
| harbour-scumstopper-0.2-1.armv7hl.rpm | 86.67 KB | 16/08/2014 - 18:09 |
| harbour-scumstopper-0.3-1.armv7hl.rpm | 96.4 KB | 24/08/2014 - 21:16 |
| harbour-scumstopper-0.4-1.armv7hl.rpm | 122.87 KB | 31/08/2014 - 21:38 |
| harbour-scumstopper-0.5-1.armv7hl.rpm | 132.25 KB | 06/09/2014 - 03:47 |
| harbour-scumstopper-0.6-1.armv7hl.rpm | 153.04 KB | 14/09/2014 - 20:54 |
Changelog:
- Added online directory lookup feature
- Added ability to test number lookups from command line
- Keep notifications visible until call is disconnected
- Added Swedish translation by Åke Engelbrektson
Comments
shults
Mon, 2021/05/24 - 11:49
Permalink
Does it work on SFOS 4
OpenDen
Sun, 2019/11/10 - 02:45
Permalink
К сожалению не работает с последними версиями ОС
wickedsp1d3r
Tue, 2019/10/29 - 18:49
Permalink
Please, update it to work with 3.1.x!
mercurio
Sun, 2019/08/11 - 12:53
Permalink
What a pity! On Xperia X with the 3.1.0 update, it doesn't work anymore!
Malakay
Thu, 2019/03/21 - 00:34
Permalink
Are czech blacklist supported?
yuri
Fri, 2016/07/22 - 22:02
Permalink
For italian users
create /home/nemo/.config/harbour-scumstopper/it.xml containing:
<services>
<service>
<provider>Pagine Bianche</provider>
<type>directory</type>
<request>http://paginebianche.it/ricerca-da-numero?qs=</request>
<personNameTag>//div[@class="org fn"]</personNameTag>
</service>
<service>
<provider>Chi sta chiamando</provider>
<type>blacklist</type>
<request>http://www.chistachiamando.it/numero-telefono/</request>
<personNameTag>//div[@class="description"]</personNameTag>
<personNameExp>negativa</personNameExp>
</service>
</services>
Victorious
Sat, 2015/09/19 - 21:28
Permalink
Hello! In the latest versions of the firmware don't work, although I worked like a charm. Decided to do a full reset and set 1.1.9.28 (in the hope that the new system will work correctly), I installed daemon -
cp /usr/share/harbour-scumstopper/systemd/* /usr/lib/systemd/user
cd /usr/lib/systemd/user/user-session.target.wants
ln -s ../harbour-scumstopper.service
After rebooting, nothing works. What are the solutions?
ovekaaven
Sun, 2015/09/20 - 20:24
Permalink
As some of the other comments say, you can try not using the invoker (edit harbour-scumstopper.service to start harbour-scumstopper directly instead of through the invoker). I've been too busy to figure out exactly why the invoker is behaving differently yet, seems like it could be some Sailfish bug.
Victorious
Mon, 2015/09/21 - 15:14
Permalink
Thank you for your willingness to help! I replaced it
[Unit]
Description=ScumStopper
After=dbus.socket pre-user-session.target
Requires=dbus.socket
[Service]
Type=dbus
ExecStart=/usr/bin/harbour-scumstopper --daemon
BusName=org.ScumStopper
Restart=always
RestartSec=1
[Install]
WantedBy=user-session.target
but again nothing works
djedail
Thu, 2015/07/09 - 14:59
Permalink
It was working well... until the last Sailfish update (2015-06-15).
Now it doesn't block anything (blacklist, private numbers) and the "last call" log doesn't work either.
I tried to reinstall the app but it's the same.
ovekaaven
Tue, 2015/07/14 - 17:03
Permalink
It seems to work at least for some time. I'm investigating. So far my current suspicion is that it works after starting it, but stops working if you make an outgoing call. Could that be the case?
ovekaaven
Mon, 2015/08/17 - 08:58
Permalink
Seems the way the invoker works may have been changed in a way that breaks ScumStopper. For now, until I can find a fix, try to start the daemon without the invoker, if you use daemon mode.
coderus
Fri, 2015/04/03 - 15:11
Permalink
daemon mode exec line is wrong. should be /usr/bin/harbour-scumstopper --daemon without invoker. also for autostart service should be enabled.
ovekaaven
Tue, 2015/07/14 - 17:55
Permalink
In daemon mode, this is not a Sailfish Silica app, but it is still a Qt5 app, so I think using the invoker would still be beneficial for the memory footprint of the daemon. Jolla themselves use the invoker for systemd services (e.g. /usr/lib/systemd/user/commhistoryd.service), so this is not wrong.
Currently, I have the user install and enable the service themselves if they want autostart, since I can't have the rpm do it if I want this to be allowed into Harbour at some point.
purplewakanda
Sat, 2015/03/14 - 11:55
Permalink
Thanks. Great app. Works well :)
jolla_jo
Fri, 2015/01/23 - 10:55
Permalink
Installed it yesterday and basic functionality is working fine. Unfortunately, the settings (at least the one about whether to disconnect immediately) are not saved.
Also, I noticed the screen turns on every time a blocked call comes in. (And it stays on for the whole time of the phone silently ringing if the 'disconnect immediately' was unchecked.) Could this be changed in some future release so that the screen would just stay turned off? I hope this not another problem with commhistory, etc..
UPDATE: I also noticed that it apparently does not work at all in daemon mode. I double-checked the daemon is running, and also made sure it does work when the UI is open. Also restarted the daemon several times.
ovekaaven
Tue, 2015/07/14 - 17:21
Permalink
The settings are saved for me, not sure what could be wrong.
Unfortunately, yes, the screen turning on is because of commhistory (or something related) also being a Telepathy observer, and therefore I can't stop it from turning the screen on, or from trying to launch the phone UI. I can only stop the phone UI from being able to access the Telepathy channel, so that it fails to start and doesn't ring.
Mutosan
Wed, 2015/01/14 - 15:48
Permalink
Just installed it and its not working. Blacklistet my number from the office but still it came trough. I set that it should disconnect right away.
salyavin
Sun, 2014/11/23 - 01:34
Permalink
Love this software. Do we have anything in Jolla together open to vote on changing commhistory from observer to approver or handler so it would be possible for you to block SMS as well like FirewallPro did on Harmattan?
anasyntes
Mon, 2014/10/20 - 13:41
Permalink
Thanks a lot, very nice application. Do you accept donations?
ovekaaven
Mon, 2014/10/20 - 23:31
Permalink
I'd happily accept code contributions, but I haven't looked into accepting money. I have a decent day job (as a software engineer working with earth observation satellites) which pays quite well already. So I lack time more than I lack money, and it would probably take quite a lot of donations to change that for me.
Of course, more money wouldn't hurt, and if you really want to donate, I can probably look into it. Just keep in mind that there are people out there who starve much more than I do.
veeall
Wed, 2014/09/24 - 04:17
Permalink
Are there any plans to support regular expressions on black&whitelists?
ovekaaven
Wed, 2014/09/24 - 11:19
Permalink
Interesting idea. If you can explain what it would be good for and how it should work, I'll consider it. Would wildcards also work?
veeall
Wed, 2014/09/24 - 18:44
Permalink
Yep, i ment wildcards. :)
It worked in n9 with firewallpro app. There, country code sometimes made a difference if the number was blocked or not, so i used * before a number.
ovekaaven
Wed, 2014/09/24 - 20:01
Permalink
Ah, the country code. Well, you won't need that with my app. Since version 0.4, it has handled country codes automatically. (It gets the mobile network's MCC/MNC from ofono, uses the bundled "regions.xml" database to find out which country code that corresponds to, and automatically adds that to incoming phone numbers that don't already have a country code. And in the app settings, you can define which country code your blacklists/whitelists should use, for entries that don't explicitly specify the country code. Everything is designed to Just Work, even if you travel abroad. (Of course, that doesn't mean it actually will just work, but at least that's how it's designed.))
veeall
Mon, 2014/10/06 - 05:27
Permalink
I figured out a usecase for regex and wildcards, that is, if i want to be unreachable but still see who's calling me, because flight mode leaves me totally blind and without internet.
ovekaaven
Mon, 2014/10/06 - 20:16
Permalink
If the wildcard would just be "*", then wouldn't it be better to just have a settings option for that?
While I could implement wildcards, I'm still not sure how to handle wildcards in the blacklist editor UI. I'm using the "dialable characters" input method hint, but at least a "?" would not really be a dialable character. I probably couldn't make it possible to input it without showing the full keyboard with letters and stuff.
daveinuk
Thu, 2014/09/18 - 21:00
Permalink
Installed today, seems OK but needs more basic features that come as standard on most androids such as add number from phone book, call list and sms, apologies if any of these features exist but I fail to find them if they do! Would rather use a native app' over androids and decided against installing and android app to see how this pans out, thank you for your time and effort so far, it is appreciated.
ovekaaven
Thu, 2014/09/18 - 22:14
Permalink
Also, you'll probably find that Android apps don't work at all for blocking calls, I've tried. So I guess this app is really your only option.
ovekaaven
Thu, 2014/09/18 - 21:50
Permalink
Sorry, Jolla does not permit Harbour apps to access contacts yet. Once they add an official way, I'd of course use it (they're "working on it"). Access to the phone's call list is also kind of prohibited, so ScumStopper currently just maintains its own independent call log. Essentially, ScumStopper is already pushing what apps are allowed to do, it's not really possible to do much more without cooperation from Jolla. I can only hope that if this app becomes popular, they will agree to change Sailfish so that more features become possible...
Pages