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

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

@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

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

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

@mymike It is not only the fresh new design. But being able to delete those items from system settings I would call a breakthrough. Definitely worth appreciation.

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

@matejrokos I am almost sure its impossible to get any idea or estimate. Volunteers don't do time tracking. Looking at an MR doesn't answer the question if a professional did that in half an hour or a hobby coder in three days.

The foundation numbers may give you an idea about cost for infrastructure. But only partially as well, since we use for instance free hosted weblate or contributors use their own free gitlab CI minutes, so they don't count on the foundation servers.

Volunteers also don't have funding. If they are lucky they get a "thanks" or some smaller donations. But that is not tracked at all.

@matejrokos Please don't expect the foundations money to reflect development cost for Ubuntu Touch. Most development work is done by volunteers who don't get payed.

Und ja: Es gibt einen Port für das OP8T von Ari (@aribk). Er arbeitet gerade daran den soweit fertig zu machen, dass er im Installer und auf der Geräteseite hinzugefügt werden kann. Ich helfe da mit Tests und kleineren Dingen. Läuft schon ganz gut...

Und Scott Howards hat in der englischen Telegramgruppe einen Screenshot von einem OP8 Port geteilt. Aber zu diesem Port habe ich keine weiteren Informationen, außer eben, dass es ihn gibt.

@rocket2nfinity There is a port for OP8T by Ari (@arbk) where I am helping with testing and smaller things. He is currently trying to get things ready to make it available in installer and on devices page. Not sure about status, but should hopefully be available soon.

And there is also a port for OP8 by Scott Howards who shared a screenshot in main group on TG. I have no information about that at all except of this info.

In case you stumble upon this post here first, there is also an English version available at: https://forums.ubports.com/post/91516.

For the installer for Ubuntu Touch to work successfully, it is essential that the version of the original operating system for which the port was created is installed. This depends on the device, but should be specified on the device's page. This is usually not the latest version available! For the Oneplus5(T), for example, this is version OxygenOS 10.0.1, and for the OP8T it is 11.0.13.13.

Note: There might not be an image available for the exact version you need. Then pick the one below that comes closest. Install that and then update via system updates to the required version.

If you are lucky, you can use the downgrade wizard integrated in OOS. To do this, download the appropriate file and proceed as follows:

• Settings
• About device
• Info box with version information -> three dots menu
• Local installation
• Select file

Let's be realistic. Life rarely does us this favour.
Here is the second method using MSMDownloadTool.

Requirements:

• PC with Windows 10/11 and administrator permissions
• adb and fastboot installed (e.g. in the terminal via `winget install Google.PlatformTools)
• Required image for OxygenOS (zip) including MSMDownloadTool v4 downloaded
• OP8T, others?: info about the RAM type DDR4 or DDR5 (usually DDR4), shown e.g. with the app Device Info HW

Note: There is a pure Linux way to flash an image with so-called flash-all.sh scripts. However, I have not tried this and it is only intended for experienced users who know which file needs to be flashed to which partition. This is the, um, simple version...

The OSS image (zip file) usually contains the MSMDownloadTool in the correct version to install the right OS version. With this proceed as follows:

• plug in your device
• head for windows system updates and check optional updates, there should be a qualcom driver update, might need a search
• open a terminal, check your device is recognized with adb devices, then enter EDL mode either with adb reboot edl or manually:
  • power-off your device completely
  • unplug the device from the computer
  • press & hold both Volume down + Volume Up, keep holding them
  • connect the device to your computer
• now start the MSMDownloadtool as admin
• your device should be recognised and marked as connected
• select your version (EU, Global, India)
• select the ram type (DDR4 or DDR5)
• press start
• now download and installation should start
• once the process has finished, the phone automatically reboots (the entry becomes green earlier, wait for reboot)
• after the reboot go to system updates and make sure to upgrade to required version of OxygenOS

Now proceed as usual:

• enable developer tools, enable oem unlocking (may need wifi or mobile data to be on)
• boot the device into fastboot mode via adb reboot fastboot or manually:
  • unplug device
  • shut down device
  • a) press & hold Volume Up, Volume Down, and Power keys together
  • b) press and hold Volume Down and Power, after vibration let power key go, in the boot menu select language, select advanced, select boot to fastboot
• when in fastboot mode (NOT fastbootd!), plug the device in your machine, run fastboot devices to check that your device is recognized and ready to go, then run fastboot flashing unlock
• on screen select "unlock bootloader" and confirm with power button

Note: There is also fastboot oem unlock. According to web sources, that may do exactly the same, but may also behave different depending on the manufacturer.

• wipe data partition to format it as ext4 to remove android encryption either via boot menu (boot into boot menu, select advanced, reboot recovery), advanced, wipe or by booting into fastbootd mode (aka bootloader ) and running fastboot format:ext4 userdata
• run the installer

Fingers crossed you now get a nice Oneplus device with Ubuntu Touch installed.

Falls hier jemand landet, der nicht so gut Englisch kann, eine deutsche Version dieser Anleitung gibt es hier: https://forums.ubports.com/post/91507.

Anleitung getestet mit OP8T. Andere Modelle können leicht abweichende Vorgehensweisen erfordern.

Für den erfolgreichen Einsatz des Installers für Ubuntu Touch ist es zwingend erforderlich, dass die Version des ursprünglichen Betriebssystems installiert ist, für die der Port erstellt wurde. Diese hängt vom Gerät ab, sollte aber auf der Seite des Geräts angegeben sein. Dies ist im Regelfall nicht die neueste verfügbare Version! Für das Oneplus5(T) ist das z.B. die Version OxygenOS 10.0.1, für das OP8T ist es 11.0.13.13.

Hinweis: Es kann sein, dass kein Image für die genaue benötigte Version verfügbar ist. Dann das nächst niedrigste Image installieren und über die Systemaktualisierung auf die benötigte Version aktualisieren.

Wenn man ganz viel Glück hat, kann der in OOS integrierte Downgrade Assistent genutzt werden. Dazu die entsprechende Datei herunterladen und wie folgt vorgehen:

• Einstellungen
• Über das Gerät
• Infobox mit der Versionsinfo -> drei Punkte Menu
• lokale Installation
• Datei auswählen

Seien wir realistisch. Das Leben tut uns selten diesen Gefallen.
Hier der zweite Weg per MSMDownloadTool.

Voraussetzungen:

• PC mit Windows 10/11 und Administratorrechten
• adb und fastboot installiert (z.B. im Terminal per winget install Google.PlatformTools)
• erforderliches Image für OxygenOS (zip) inklusive des MSMDownloadTools v4 heruntergeladen
• OP8T, andere?: Kenntnis des Ram Typs DDR4 oder DDR5 (meist DDR4), kann herausgefunden werden mit Device Info HW

Hinweis: Es gibt eine reine Linuxversion mit sog. flash-all.sh Skripten. Diese habe ich aber nicht probiert und ist nur für erfahrene Nutzer gedacht, die wissen welche Datei auf welche Partition geflasht werden muss. Das hier ist die ähm einfache Variante...

In dem Image steckt in der Regel die "richtige" Version des MSMDownloadTools drin, die die korrekte Version installiert.
Damit wie folgt vorgehen:

• stecke das Gerät per USB Kabel in den Rechner
• gehe in die Systemeinstellungen und aktivere optionale Updates und prüfe auf neue Updates, jetzt sollte ein optionales Qualcom Treiber Update verfügbar sein (falls nicht schon installiert)
• bringe das Gerät in den EDL Modus, entweder per adb mit adb reboot edl oder manuell:
  • Gerät komplett ausschalten
  • Gerät vom Rechner abziehen
  • Vol + und Vol - drücken und gedrückt halten
  • verbinde das Gerät mit dem Rechner
  • das Gerät sollte jetzt im EDL Modus sein, auch wenn am Bildschirm nix zu erkennen ist, der bleibt schwarz
• starte jetzt das MSMDownloadTool als Administrator (Rechtsklick -> Ausführen als Administrator)
  • das Gerät sollte als connected angezeigt werden, falls nicht, ist es evtl. doch nicht im EDL Modus -> das nochmal machen
  • wähle die Version aus (EU, Global, India)
  • wähle ggf. den Ram-Typ aus, am OP8T kann das DDR4 oder DDR5 sein)
  • drücke auf Start, der Prozess sollte jetzt losgehen
  • warte solange bis das Gerät neu startet, auch wenn der Eintrag davor schon grün geworden ist
  • überprüfe in den Einstellungen die Version, aktualisiere ggf. auf die benötigte Version

Fertig. Jetzt sollte die richtige Version installiert sein.
Ab hier wie sonst auch

• Entwickleroptionen aktivieren (unter System 7 mal auf die Build-Nummer tippen)
• OEM Entsperrung erlauben (in den Entwickleroptionen, braucht Internetverbindung per WLAN oder mobile Daten)
• den Bootloader entsperren
  • in fastboot Modus gehen, nicht fastbootd z.B. per adb reboot fastboot oder manuell
    • Gerät abziehen
    • Gerät ausschalten
    • a) Vol + drücken und halten, Einschalttaste drücken und halten bis das Gerät vibriert nur diese dann loslassen
    • b) Vol + und Vol - und Einschalttaste alle zusammen gedrückt halten bis das Gerät vibriert dann nur Einschalttaste loslassen
    • im Bootmenü fastboot auswählen (English wählen -> advanced -> boot to fastboot)
  • mit fastboot flashing unlock den Bootloader entsperren, hier muss am Gerät eine Bestätigung erfolgen (beim OP8T waren die Optionen genau falsch dargestellt, also ggf. nochmal machen), danach sollte ein Erfolgsmeldung erscheinen
  • es gibt zwar auch fastboot oem unlock, das sollte eigentlich das gleiche tun, macht es aber im Einzelfall nicht
• die Nutzerpartition formatieren damit die Geräteverschlüsselung gelöscht wird, sonst geht die Installation nicht
  !Dadurch werden alle Daten gelöscht. Vorher sichern falls noch etwas benötigt wird.
  • per Terminal mit fastboot format:ext4 userdata
  • Bootmenü aufrufen wie oben beschrieben
  • in Recovery booten (advanced -> reboot to recovery)
  • advanced -> wipe
• den Installer starten

So, ich hoffe ich habe keine wichtigen Schritte vergessen. Viel Erfolg!

@RJDan Also a big "Thanks" to you for running the vote and your sponsorship.

@atarilinux Maybe adding an icon in a corner for indicating desktop app or waydroid app or snap might be a first step to reduce such mistakes. But I agree, having a filter might be good in the long run if we have more apps of those types (thinking also of crackle or nix).