While we are waiting for PureMaps to provide offline functionality, here some instructions on how to get offline maps for uNav working using downloadosmtiles. I do post this here because I did encounter a few stones on the road to success.

1. download downloadosmtiles from the left hand menu
2. extract to a folder on your harddisc, i.e. Downloads/osmtiles
3. run the script with perl downloadosmtiles.pl --link='http://www.openstreetmap.org/?lat=49.5782&lon=11.0076&zoom=10&layers=B000FTF' --zoom=5:16 --destdir=somewhere/maps

• of course replace coordninates with your target coordinates, the area seems to depend on the zoom value after the coords
• replace the path for destdir with another one, default is the current working directory
• change zoom levels, levels above 16 do take quite some time to download, you can download 5 to 16 first, and only level 17 or above later if you really need it

4. copy the map-files (foldernames = zoom level i.e. 5) onto your phone i.e. in a folder Documents/uNav_maps
   [zip the map tiles and copy the zip file, that is much faster than copying thousands of files]
5. in Terminal app run the following commands:
   cd Downloads/uNav_maps
rsync -avp . ~/.local/share/navigator.costales/maps
   [rsync is faster than cp and gives you progress information]
6. open up uNav, goto settings, change Modus to offline maps

EDIT:
To specify a bounding box for the tiles do be downloaded the command in step 3 needs to look like this:
perl downloadosmtiles.pl --latitude=47.35371:49.93708 --longitude=7.38281:10.54687 --zoom=5:7 --destdir=somewhere/maps
edit finished

Have fun! Don't get lost!

for lazy guys like me:
If you do this regularly, you may wish to create yourself a small shell script in your phones home folder called i.e. cpbash.sh. Then only open Terminal and run bash cpmaps.sh. Put the following two lines into the script:
cd Downloads/uNav_maps
rsync -avp . ~/.local/share/navigator.costales/maps

Troubleshooting: (on ubuntu 18.04)
... Can't locate Geo/OSM/Tiles.pm in @INC ...

• open the file downloadosmtiles.pl in a editor
• before line 6 add the following line: use lib '/Downloads/OSMtiles/Geo-OSM-Tiles-0.04/lib';, replace the path with your download location

... Can't locate Geo/OSM/Tiles.pm in @INC ...

• install YAML.pm by running: sudo apt-get install libyaml-perl

• you may need to create the folder maps to be like this: ~/.local/share/navigator.costales/maps, then map data wants to be in there in a structure like this (see https://unav.me/offline/) :
  ~/.local/share/navigator.costales/maps/10/
  ~/.local/share/navigator.costales/maps/10/523/
  ~/.local/share/navigator.costales/maps/10/523/331.png

Hi, I recently took over developing tedit app. I would like to try the forum, to gather some ideas and feedback regarding ongoing development.

In this thread, I will post questions regarding future design and functionality and let you, the users, comment and ask things. Lets see how this goes. We can always split it up or move discussions elsewhere.

I would still prefer to have issues and feature requests added in the gitlab repository, but I understand, that not everyone is familiar with gitlab and also that some things are easier to discuss here.

@Robipo When I wrote this post, I didn't know, that Github only provides downloadable files for users that are actually logged in to Github.

So currently you can either log into Github (if you have an account) and download it from there, or use the latest .click I provided in our Telegram QA group.

I will release Cinny soon in OpenStore (I got the "go ahead" from the old maintainer today.), but a couple of steps need to be done until that is achieved.

He has been mentioned, but many, many, many ... thanks to @bhdouglass master of OpenStore!!! What would we be without our OpenStore? Great work done there - and certainly a lot of time spend.

Many thanks to everyone working on clickable - I know for sure @bhdouglass and @jonius - who provide a magical and crucial tool for us to create apps.

Thanks @bhdouglass for asking me to maintain weather app. With your advice and a lot of starting help by @jonius , design guidance from some weeeee helper @CiberSheep I am happy to be able to contribute.

Also many thanks to all translators like @Anne017 for hours of translating, so others with less knowledge of the English language can enjoy Ubuntu Touch.

And thanks to everyone else here making up a nice community!

Edit: I forgot to mention two important contributors: @Krille and @nanu-c . With a lot of time and love they provide apps for matrix and signal. Significant add ons next to Teleports. So man thanks to you too!

For developers:

1. Ratchanan, because so much code for the OS wouldn't exist without him
2. Lionel for his work on calendar app, dialer and messages

For apps:

1. Teleports, what would we do without it?
2. OpenStore, again we would be nothing witout it

@vverve This number is the daily build for your specific device. All devices have their own number, since some changes may only affect one or few devices, but not all. So one device may get a build, others not. Some core changes may affect all devices, so all get a new build.

With a couple of hundred repositories its surely hard to track changes, but for tracking changes I am looking at merged MR's: https://gitlab.com/groups/ubports/development/core/-/merge_requests?scope=all&state=merged

@dtarrant I had a look, yes, the app is not using a terminal command (as I thought). It is changing a gsetting.

gsetting values can be changed via terminal too as described here.

The schema is "com.canonical.Unity8". The actual setting value is "usageMode". (taken from UT Tweak Tool's code, not checked)

So in theory something like this run in terminal should work:

gsettings set com.canonical.Unity8 usage-mode Staged
gsettings set com.canonical.Unity8 usage-mode Windowed
gsettings set com.canonical.Unity8 usage-mode Automatic

Havn't tried it though.

Edit:
If you wish to do this without terminal but from inside an app, have a look at my ThemeSwitch branch where I implemented a working way of changing a gsetting.

Edit 2:
I edited the mispelled commands here too as pointed out by @Pulsar33.Thanks for that.
Although if it is usage-mode, then I don't know why or how UT Tweak Tool can work, because that is using usageMode. But maybe I overlook something.

So to sum up what has been written here so far (what got stuck in my head), the main reasons for not moving to focal are is order of seriousness (and lack of workarounds):

• stability of focal and
• too many troubles when migrating from xenial to focal. Either taken from own experience with another device or from discussions.
• A clean install is the best way to do that, BUT we don't have a good backup solution.
• This is followed with devices not supporting focal, sure no workaround for that.
• Apps missing is an issue, but that is sorted easiest and also is due to developers not having moved to focal yet with their devices.

[edit, I forgot one big reason:]

• people are just happy on xenial, no need to move on

With 24.04 knocking at the door (middle of this year planned currently) this is valuable information. I will pass that on to the core dev team.

Of course this doesn't close this post. Its more a summary for others joining new and for myself :smiling_face_with_halo: .

@ancientsounds I do understand that this would be very convenient. But to achieve this, the app would need to be unconfined. And I would rather try to avoid that. I wrote some explanations in an issue recently.

You can share files to import them in tedit. I will (hopefully soon) find time to add content hub export too. Also you can create symlinks to tedit's file folder in other locations, as described in the README. I believe this does provide quite some flexibility to use.

@Moem time does solve some issues. There actually is a port for OP8 in the works by Scott Howards, he posted some photos on TG. And there is a port for OP8T being done by @aribk and me helping with testing on that. They may end up in the installer and on devices page at some point next year I hope.

@gpatel-fr We certainly can als use gsettings. I made a proof of concept for ThemeSwitch app a while ago (https://gitlab.com/Danfro/themeswitch/-/tree/gsetting_focal?ref_type=heads).

I am almost sure we can't use other apps values without loosing confinement. The value would need to be provided by the system. I guess if GRID_UNIT_PX could be changed in system settings and apps read that, that might work. Or it may need another apparmor rule. But I am really not that knowledgable to answer all details.

@gpatel-fr I do admit, I didn't look into Qt6 yet. Maybe that will bring us ways to improve. And you are right, since we use components like Qt or Ubuntu, there are professionals working on that. But it still needs people to make use of it in UT.

@pparent Looks like its somehow working with a config file: https://gitlab.com/myii/ut-tweak-tool/-/blob/master/src/app/qml/behaviourTab/LomiriScaling.qml?ref_type=heads#L32

@mango I remember discussions from TG groups every now and then. And @pparent I am sorry if my comment about glasses was misleading. I didn't wanted to be disrespectful for people with reduced sight.

The qml code does in theory allow to use relative text sizes. See: https://ubports.gitlab.io/docs/api-docs/index.html?p=lomiriuserinterfacetoolkit%2Fqml-lomiri-components-label.html
I think this might even be a Lomiri adjustment, because I don't see textSize property in normal Qt Label.
Maybe we should bring up this topic into develompent groups again.

But for instance buttons generally don't have word wrapping available by design. So increasing a label by using a larger text (not mentioning longer translations, German is bad in that regard ) may make the button label being cut off. Just as one example on how complex this is.
I guess I should start by using this setting in my apps and try to rework them at least step by step.

@gpatel-fr Sure, that's why I said its a personal thing. I am well aware that some people really need larger text. We had other users asking for that feature before. I gladly can still do without. But it doesn't change the situation, that we wish do help them, but haven't got the menpower to do so.

Although signal app might be different being a desktop app, if that allows scaling. So it could be done per app.

I actually compared the text size of teleports with signal app right now. Text in Signal app is a bit smaller than in teleports. This is on OP5T with default scaling at 21.

@mango readability is for sure a very personal thing and depending on your eyesight. I am using UT for ten years now and never saw the need to touch scaling, although I am wearing glasses.

The thing is, as always someone(tm) needs to do the work to allow UT to adjust text size. There needs to be made a setting, all app codes need to be adapted to use that setting. Larger text sizes will break lots of layouts in apps. App and system UI need to be changed to cover for that. This is a HUGE task. We are a small team of mostly volunteers (often non professionals like me) doing the coding in our free time. We don't have a multimillion budget with lots of professional developers.

There have been talks about text size adjustment years ago. And we do understand the need for it. But we simply haven't got the means to do it. So we provide UT for those who can use it, maybe with UT Tweak Tool overall scaling adjusting a bit. But unless you provide code or donate a significant sum of money, sadly I don't think this will change anytime soon.

@Caedem likely not how it works. The 3.5.1 was the last xenial release. Those 9k focal devices, are those who moved from xenial to focal. So there would be a bit less than 4k xenial left with numbers shrinking.

And we need to drop them for security reasons at some point. Or can you justify providing a unmaintained insecure system? Also some older devices will simply die due to hardware breaking.

@pparent No, it doesn't use a popup. After clicking that field another page does open. I do agree, I too don't see why this should fail. Its not a special function.

It might have been simply bad luck or rather bad timing. Maybe the requests had not been synced to this client but my laptop already had them.

But I decided to ask anyway, just in case you might have had an idea. So I guess lets not worry about this.

@pparent When you send someone a group link to invite them, depending on the settings, they need to be validated by a group admin before they can join.

When you tap on the group name to open the details page and scroll to the bottom, there are invites and join requests listed. But I got a zero there, although I had 2 pending invites. Also nothing was listed on the page that opens after clicking that entry.
Just a minute later I checked at signal desktop and there I had a number 2 displayed. After clicking I saw the two requests and could process them.
Of course it could have been just bad timing and lack of syncing.

Is it my bad math, or should +131 -1 = +130, not +129 in the very first paragraph?