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.

@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.

@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

@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).

@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?

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

@domubpkm I have a plan and did some research, but no concrete implementation yet - I do think I could start some tests in the near future though. I'll keep you all updated in this thread.

While waiting for my Pebble Steel to arrive (so I can debug why it refuses to work on more recent BlueZ) I'm working on an app for a few smartwatches/bands I have (generic M16-mini, Amazfit Bip, Bangle.js 2, possibly Amazfit Stratos and Huawei Band 7).

I'll make it generic enough to make it easy to add new watches/bands (but at the same time support as close to 100% of the device functionality as humanly possible), but if there is a particular device a lot of people use or want to use I could try to get it and add it in the first release.

@Moem a bit too much happening at work, I didn't have the energy to do anything buuuut we did figure out that Pebbles work fine on focal, the issue is in the RockWork app and it would need a reimplementation - probably less work for me to add Pebble support to mine once it actually exists.

Other than Pebble, I definitely plan to support PineTime (with Infinitime) from the start since it seems like the second most popular one.

@007fred50 You can't browse device files directly because of security rules, you have to request them through the ContentHub.

The linked documentation also links to the source code of an app that uses it to select images: https://gitlab.com/cibersheep/webapp-creator/blob/master/webapp-creator/app/ImportPage.qml#L38

Not sure about the last error, can you post your clickable.json and .apparmor file?

@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

@yoni Not yet, I had some higher priority stuff so for now I've just been reading though the relevant code.

@reeered start by restoring your device with Xiaomi's tool: https://forum.xda-developers.com/t/miflash-guide-use-xiaomi-flash-tool.4262425/

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

@domubpkm Can you stop spamming this thread with ads for this app? I understand mentioning it once, but now it looks like advertising.

@lsitongia Here is the main doc: https://docs.ubports.com/en/latest/systemdev/online-accounts.html

Nextcloud QML plugin: https://github.com/ubports/account-plugins/tree/xenial/qml/nextcloud

@keneda Ah well, at least it's not phpBB And themes look pretty easy to do in it.

@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.

Hello!

I created a fix for indicator-power that should make it better at recognizing the real battery. If you would like to test this and are on the devel channel, run these commands on your device:

sudo ubports-qa install indicator-power 60

and

restart indicator-power

(or reboot your device).

To test simply unplug the device, observe the battery indicator, plug it back in and check again. Longer-term testing would be good too, to check if the battery level goes down as it should.

Let me know your device, and:

• if it worked for you before and now something is wrong (no charging indicator, always empty battery, etc)
• if it didn't work before and now it works (shows charging, proper battery level)
• if nothing changed

by posting here or in the PR (https://github.com/ubports/indicator-power/pull/60)

Thanks!

Keep in mind that this can behave weirdly if it breaks, have a backup / don't do it on your daily driver unless you know how to fix a potentially broken system.