Posts made by klh

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

@br1 That's a really nice solution, but please try to keep the discussion on topic

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

@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

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

@dtarrant

Device must be running Android 9 (don't know if it still is)
Device must be unlocked (don't know if it still is)
Device musf be in Developer mode (can't switch to Developer mode)

None of those apply if you were on UT already (re-locking the bootloader is a manual step done in fastboot, so I doubt you did it by mistake). If you got an error message post the installer logs here (~/.cache/ubports/ubports-installer.log).

If you had to select your device manually then your PC probably didn't detect the device, so it probably wasn't in fastboot mode (unless it's one of the weird ones).

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

@flohack In general I'd agree, but from my understanding CB is/was opt-in - one of the reasons we got an SMS based emergency alert system instead of using CB here. But I don't suspect a government project of doing proper research, so it wouldn't surprise me if the info in the documents was wrong

In addition to the above, since UT doesn't have AGPS enabled/working the initial time-to-fix is very long, since it's a full cold boot - 12.5 minutes on modern GPS hardware, up to 40 minutes on older ones. After that the fix should be faster if you use GPS once in a month.

Best is to set the screen to never turn off, open an app like uNav and leave it on until it gets a lock (might have to be outside, good time to get some coffee outside ). After that you should be set.

Is it going to be opt-in or opt-out?

Also full Cell Broadcast is much more than emergency alerts - we had something like Craigslist in Poland that was based on CB in early 2000s - it's probably not active anymore since the carrier is also gone, but if you want the full experience we also need an info "level", a screen with message history and another to select channels to subscribe to (maybe with the ability to define per-country channel id <-> name mappings?).

And definitely a way to silence a channel while still being subscribed - for example it doesn't make sense to get alerts from channel 50 for most countries, but checking it manually is a valid use-case.