Hello, I'm interested in implementing a system-wide call/number blocking feature (re: https://github.com/ubports/dialer-app/issues/18, https://github.com/ubports/telephony-service/issues/43).

I know what I would like from it:

• contacts app integration
• call blocking
• sms blocking
• ability to see history for blocked numbers
• ability to easily block a number after the call

But I'd also like to hear what the community wants so I don't miss anything, so let me know.

THIS IS NOT A TOPIC TO ASK FOR PROGRESS, NOR WILL ANY PROGRESS BE SHARED HERE.
Please stay on topic and post what you need from such a functionality. Asking for progress here is pointless - once I have time and have something you will definitely hear about it

@domubpkm Yeah, I know about f-call But this feature should be integrated into the OS though, so that's what I'm going to do. SailfishOS's ofono fork will help a lot.

@dizzy Silent mode / dnd was split into a separate topic (can't find it now though, not sure what happened - if nobody beats me to it I'll probably work on that one too). This one is about blocking specific numbers from being able to call/message you

I want this to be a part of the OS, not an app. As for donations, you can always donate to UBports: https://ubports.com/donate

@keneda I've been deep in ofono recently so let's say the force is guiding me pretty well

No ETAs as usual, but things are slowly falling into place.

@dtarrant Going back to Android first might be the easiest - should all happen in fastboot so once you boot that it should be fine.

@kugiigi It's a pin code, security is not improved that much by not showing the length - best UX would be to offer a choice.

But if we are not saving the length then it should start with no circles - we could show some helper text like "enter PIN" and "enter PIN or use the fingerprint scanner" if that's also set up.

The circles could show up empty and fill over ~200ms to preserve the current design a bit too.

Also, @lduboeuf why 12 as the new limit?

@emphrath said in Talk to the Non-Geek People:

[...] You don't want me to touch html code

Good thing is the docs are written in reStructuredText, no HTML involved and pretty easy to write in any text editor. Or I can convert an odf/docx file for you, if you want (and make some simple diagrams if you add photos/images/doodles/descriptions).

@bolly Yeah, mandatory "here is a list of issues that seem similar" before you are able to post.

@homer That should be relatively easy, depending on the features of the app. I might put it on my todo list (it's a bit long though, I still need a few apps to properly daily-drive my UBT device).

@UniSuperBox throw an AI at it, soul-crushing work is what they do best

@dizzy I'm just a volunteer, no affiliation with the foundation. But if you like the feature once it's done, I'd prefer donations there - we wouldn't be here without it anyway

I think silent mode should be a separate feature - with blocking you won't even know that you were called until you go into some menus so that won't really work even if we turn it into an allowlist - I like to get all notifications after I turn off dnd

@roese-leo Thanks for your suggestion, I didn't think about wildcards!

As for recording, it's a complicated issue that spans multiple jurisdictions (for example where I live it would be perfectly legal to record the call I'm a party in, but in the USA each state has different rules) - I don't think this could ship by default, so it should be a 3rd party app.

@keneda Oh, I misunderstood your post as recommending the 12 character, text field and manual submit as the requirements for the screen lock, sorry

@keneda That's how you end up with "password123" everywhere. Not everyone stores sensitive data on their phone + as long as the bootloader is unlocked and data unencrypted any point about security is moot

@kugiigi It's a pin code, security is not improved that much by not showing the length - best UX would be to offer a choice.

But if we are not saving the length then it should start with no circles - we could show some helper text like "enter PIN" and "enter PIN or use the fingerprint scanner" if that's also set up.

The circles could show up empty and fill over ~200ms to preserve the current design a bit too.

Also, @lduboeuf why 12 as the new limit?

@marekf Using the installer is the only supported installation method, this doesn't change with focal.

@arubislander Brian already did, I wrote it here for reference since the review on the MR is rather long. I can take a look at doing it once I finish higher priority stuff, I've been really missing this option in Podphoenix

@arubislander what is actually needed here, is a way to tell media-hub to stop playback after some time - doing this on the app side is not a good solution, since it requires either keeping the screen on, or not suspending the app, both consuming resources/battery.

With the fix in media-hub other apps could use it as well (Podphoenix is a good example).

@digi6622 I don't see any feature requests about what you describe here: https://gitlab.com/ubports/development/core/mediaplayer-app/-/issues
Where was the request made if nobody responded to it?

Oh, also @Yougo I see you have a Pixel 3a and that definitely has working 20.04, so you could also check (ofc only if this is not your only device, I can't repeat enough that 20.04 is not ready for general use ;p)

@moem hmm, did you do a clean install with wipe and bootstrap? It's an older device, there were some kernel changes needed for 20.04 to work so might be safer with these options.

@moem I see you have an Xperia X (forum signature) - can you install 20.04 on it and check if the watch connects there? Not sure if the issue is visible without the app, but if not I can try and build it for 20.04.

I think the easiest is to install with the installer, checking "show hidden system-image channels" in the options and selecting 20.04 devel. Beware ofc that this is not end-user ready and a lot of things are missing.