Topics created by Emphrath

@emphrath I changed the profile to "online maps" only, and rerouting now works fine. 😉

@lduboeuf stable. I'll check logs later this evening.

@emphrath Yeah this happens from time to time and has been happening for a long time. It's not too often though. In my observation, sometimes it's isolated in an app which can be fixed by restarting the app or sometimes by focusing a text field outside the app and going back again to the app. Sometimes it's an actual crash of the keyboard which restarts by trying to focus a text field like the search field in the app drawer.

@domubpkm I didn't find the list either, but I still have the app installed, tell me the one you are looking for and I'll confirm to you if it's there.

As of today, I discovered a variant of this bug: the simcard asks for my pin number to connect to the network - it's slightly less annoying since I don't have to reboot. Are there any logs I should check ?

Indeed it works fine with other bluetooth speakers. I'll markthis solved

@Lakotaubp I am already running devel, although I am on RC right now just to help test the freeze of OTA-13.

@Lakotaubp well... i didn't come to ut to scroll through piles of nonsense again anyway ^^

@AppLee Nice. thx

@kugiigi nope.

Got a similar issue 3 days ago when activated alarm for work the next day.
Button not stayed grey, green ok.
But alarm didn't poped on the notification bar, and time untill it rings was about 30 days later, and not next morning.
Tried all presetted alarms, all broken.
Tried lot of things to resolve it, but only setting up a new alarm with same settings worked.
Then i deleted the first broken one i had, and all the others now work again.

First time in five years using uTouch that i have issue with alarm, it's the only one i have to not be late to work...

@kristatos said in MMS situation:

Some days or weeks later there is an incoming SMS that tells me, that there's an unread MMS and a link where I can watch at it.

Got this once on my MX4 since updated on UBP OTA-11 stable.
Weird because on canonical OTA15, MMS worked like a charm.

@domubpkm
for reference: https://github.com/ubports/messaging-app/issues/189

Could it be that this commit broke anbox support for the FP2?
https://github.com/ubports/anbox/commit/e117ed1af2f47469eba8db5510d1ce547c9a0a94

It adds a change of the device name to lowercase. Which might be ok for most devices but obviously not for the FP2.

Edit: I opened an issue on github about it
https://github.com/ubports/anbox/issues/39

@Keneda
I do it outside because I want my phone to get line of site radio communication with the satellites.

Fun Fact: you can contact astronauts on the ISS with 3 watts of rms power on a handheld when they are over head. 😁

Also, if you want to talk me with audio, I have been known to monitor 27.32500 megahertz on double side band amplitude modulation from time to time. I may or may not be able to get out with 500 watts. Heck of a time when the sunspots are in line.

Sorry, its Friday and I'm on a rabbit trail.

@Emphrath You could add solved to the title if you feel like it. Just click the three little dots to the right.

shame really.not wanting to start an issue but these I always found useful especially when @rubencarneiro sorted them out again

@Fla no the Android layer is not the reason, this is very little RAM usage. The problem is that unity8 was never optimized for low-memory devices without swap: It comes from a desktop world, and with it a lot of services that just like to spend RAM.

Unfortunately the core team has no resources to tackle those issues with unity8 right now, and the Yunit project, which wanted to fork and maintain unity8, has silently died away. So currently we can only be patient with that situation.