@Futura I'm using exphone from the openstore for this. It's working fine for me.

@johndoe Last year I got 2 SIM-cards in that phone (one netzclub which is using O2 and one T-Mobile), this time I have only 1 card inserted (congstar which is using T-Mobile). My journalctl also doesn't contain anything related to CB. Maybe @lduboeuf does have an idea?

@_JCM_ Intrestingly my Volla with 20.04 also didn't receive a message via CB, and I'm pretty sure that it has worked last year...

OTA-10 isn't released yet. It seems that you are still on OTA-8 so you can upgrade to OTA-9, maybe the errors are gone then. If not, I would try to reinstall the OS via installer.

Hi,
with the new 0.5.0 release of Dekko it's not possible for me to fetch new mails from an existing mail-account running it under focal. The circle keeps spinning and spinning while checking for new mail. Also connecting a new mail-account is not possible.
I've already uninstalled Dekko and reinstalled, cleared the cache, deleted all the folders in the filesystem related to Dekko but nothing helped.
Than I installed 0.4.1 of Dekko which worked fine for me until the update to 0.5.0. Now this 0.4.1 still works like expected while 0.5.0 does not.
On my second phone, which runs 24.04, version 0.5.0 runs fine with the same mail-accounts connected.
Does anybody else also have this issue?

With the latest release of Dekko it's working like expected under noble

@sudo2017 No, not under noble. But let's wait if there is coming a new release as @arubislander said. Maybe it's already prepared for noble and will address these issues.

@messayisto Okay, when writing a new mail mine is also crashing. I've just tested installing, connecting to an account and fetching new mails. So, it needs to fill a bug-report for this issue. Can you fill one?

Dekko2 is already available and installable under noble. I've just installed it and connected it with one of my E-Mail-accounts and it just works.

@domubpkm When I had this issue in the past, I always could reliable "fix" it with deleting the cache. I don't had to restart several times or something like that.

@kugiigi That's right, I know So the next person which is having trouble with that, should not shoot at the whole ".cache-Folder" so that we could localize what specific cache-Folder is causing this issue. I think it has to do with mediascanner or components like that.

@kugiigi I don't remember correctly which special cache I've deleted, because I hadn't had this bug for a long time. But removing

~/.cache

should definitely work. But this way will also clear caches from other apps...

@domubpkm I've experienced this bug several times on several devices under several versions of UT
I don't know what's the cause of this and if it ever will be fixed, but clearing the cache always worked for me.

@domubpkm have you tried deleting the cache?

@AppLee said in 20.04 Focal: uNav freezes with GPS enabled:

I don't remember exactly but I think I make my search before asking to locate me.
Basically there is an order that work ; search the location, then start the navigation, then location activation.

That was the way I thought it would work reliable, but also this order freezes sometimes.
When you first locate your position and then try to do something else (e.g. search a destination, calculate a route ...) the crash is save for about 99,9%.

Long story short, there's nobody who can say, that the navigation is working for him like expected and without issues. And for me, that was the case under Xenial. There have never been any freezes in conjunction with GPS. So, how can we figure out what causes this freezes?

@lduboeuf Yes, he said it's working for him under noble. But It think he's using a Fairphone 4 or 5.
I don't think it's a device issue because there are multiple affected devices and under these, there are Mediatek and Qualcomm chipsets.
But, like @haagch said, it would be nice to know, how to debug this issue to help get this annoying bug fixed.

I also think RCS is one the next "big things" after VoLTE, but in my opinion the only variant that makes sense is 1. (modify existing messaging-app to be capable of RCS).

@CiberSheep @TheBird @zubozrout Can you please mention on which device these freezes happen to you? I've opened a bugreport but it seems to work on a Fairphone 4 (qualcom device...).
For me these freezes are happening on Vollaphone and Vollaphone22 running Focal and Noble.

@CiberSheep I think that's also the wrong place, because it must be a problem in the location-daemon/gps-daemon.
I've tested it again with todays build of noble and it's the same behavior like under focal: unav, puremaps and even morph are freezing once you have searched your position and want to do something with it (e.g. calculate a route from the actual position). Maybe @peat_psuwit does have an idea or can even take a look at it?

@ezst036 You have to unlock the phone first and then you can directly access the files on your phone via the filemanager on your computer.