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

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

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

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.

@peat_psuwit do you have a spec for the Thai EBS? Looks like they require a working SIM card?

I still maintain that we'll need a CB topic database from e.g. Android and should not not rely on hardcoded set of topics from a non-regional specification.

In theory we should only need the table from 9.4.1.2.2 of 3GPP TS 23.041.

Unfortunately, the test today is inconclusive on whether we need to explicitly subscribe to topic "4370" or not.

We don't already? According to the same table, 4370 is not supposed to be settable by the user and always subscribed (I'm kind of extending the 3GPP definition of MMI here) so this shouldn't be a question - since afaik it's not required to be implemented at modem level, we should check what ofono reports and subscribe to the missing ones.

@CiberSheep the dream of Waydroid-less UT died with every bank under the sun choosing to implement PSD2 with custom apps

@pparent iirc my immodules hack won't work for Wayland, and you won't get an onscreen keyboard in Mir 1.8 because it's missing all the IME protocols.

I haven't looked at what electron-only features the signal-desktop app uses, but you could look into packaging Node.js and running the back-end parts there with a shim in WebEngine to communicate with that. Not trivial, but would give you near-perfect integration with the OS.

@pparent your store description is a bit misleading

• The application is somewhat slugish because it is not GPU-accelerated (because apparmor prevents the app from accessing the GPU)

It's sluggish because you run it under Xorg - which is your choice, not a system limitation.

• It is not possible to copy and paste text from other applications (should be solved with Mir 2.0)

It won't be solved by Mir 2 because you are running it under Xorg, and the difference with Mir 2 is that it supports the Wayland clipboard protocol.

If you are going to support ContentHub at some point, clipboard is easy and handled by the same service.

@FixOne said in It's done! KDE Connect finally works on UT:

ATTENTION! KDE Connect can only be installed via APT. Do not attempt to install it in Libertine or nix (Cracle), as it will not work or will be extremely unstable. If you are concerned that the application will break your system, you can relax (but backups are still important). Changes to the system will be minimal.

Please don't give guarantees you can't keep. Using apt will break the OS at some point, it's not the question of "if" but "when".

Your script also installs avahi and enables it unconditionally, which is a very bad idea for a mobile device that might connect to public hotspots - you should at least put a warning in your post.

@CiberSheep fyi this has nothing to do with app development.

@t12392n said in App security (new KeepassRX app):

A local Keepass should not talk to the internet.

Where did you get the idea that it does?

@arubislander said in App security (new KeepassRX app):

If the app is confined (as this one is) you don't need to blindly trust that the package in the open store was compiled by the code that is linked, to be sure it doesn't phone home. If you know what to look for, you can download the .click package and examine the contents.

All versions of OpenStore also show the permissions list and that should be the first thing people check, can't expect non-technical users to unpack clicks before installation.

Kind of related, we should probably update the popup when you install from a local .click file to show more info and definitely show permissions.

Interesting, though it needs Qt 6 afaict. Still nice, I was waiting for servo to get a bit better scores on the WPT tests before trying to run it on UT, but maybe it's worth looking into for some simpler sites.

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

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

@mymike Btw some watches require an account to set up, so I plan on having some functionality for that anyway - might be able to pull data from a Garmin account too if they are not changing that too frequently.