Information:

Here will be shortcut of our best ideas discussed below and information about available projects.
There are two points of view, how this functionality should looks. That's why there are described both.
The priority is the basic form.

When somebody want me to add something in 1st post you call me up using "@"
However I'll try to mark helpful information here in spare time.

Started & Connected Projects:

ICE - Personal Safety App - by @syper

OpenStore - https://open-store.io/app/indicator-ice.ubuntouchfr
Source - https://framagit.org/syper/ice-personal-safety-app
Support - https://framagit.org/syper/ice-personal-safety-app/-/issues

This Project adds ICE Information on status bar but for now there is no possibility to call contact form owners phone or to access this screen using button - you have to swipe down from statusbar

Big thanks for @syper

Basic form:

(simplicity and other popular mobile OS are the key)
Overview: The idea is to create SOS, ICE, EMERGENCY screen available without permission on UT lock screen.
Layout: Simple access to that screen after double tap ICE/EMERGENCY button available on lock screen. Button may be at the bottom of the screen. It shouldn't be aggressive looking. It can be transparent. However writings border looks good and may be a good choice. Button redirect to screen where place is separated in two parts: ICE Contacts and Owner Information

ICE Contacts includes:

1. Priority Number on list
2. Name
3. Phone number
4. Call button - in stress this way may better than gestures

Owner information fields:
(Excluding 2, these points you can find in LineageOS 17)

1. Owner Name, age, gender
2. Owner (this phone) number
3. Blood Type
4. Allergies
5. Medicine
6. Address
7. Organ Donor
8. Note - here may be everything we forgot to include

Extended form:

(proposed by @3T_Ed )

#1. parameters

• open source UT
• Armor/confined (lowering treshold for installing)
• basic feature with minimal data permissions
• extensions (opt-in) for geolocation, QR-code, etc

#2. Front-end: structure/lay-out
a. lockscreen: emergency call button + medical ID button (one tab to -> b.)
b. one click to Overview (basic/essentials), similar to this existing ICE app (last screenshot)
c. Overview:

• Tab 1. overview (current: basic medical ID with optional links to geolocation, call nearest ER, etc.)
• Tab 2. owner details
• Tab 3. medical condition (optional linking to Tab 6.)
• Tab 4. medical history (opt-in extension)
• Tab 5. relationships
• Tab 6. show procedure/ (manual input or standard first aid procedure)
• Tab 7. Red Cross standard guide on common first aid procedures, preferably in your own language
• Tab 8. User log (logging access usage+detecting unauthorized usage)

After consensus on #2., #5. and #6. a visual draft can be made.

#3. back-end: structure/lay out

• to be determined

#4. Usability and possible opportunities
By allowing more permissions

• direct call emergency rooms
• pinpoint the exact location for helpers to guide emergency services to that spot
• QR code/NFC for emergency services
• geolocation for sending out emergency text to ICE in case of falling (think diabetics, elderly people)

#5. Must have/Nice to have

• see #1
• see data provided by @BigB

#6. List of data fields
Tab 1: Overview

• photo (identifying owner)
• name, date of birth (+age), gender
• this/owner's phone number
• ICE (most important + dropdown showing rest)
• family doctor (name, phone number)
• blood type
  *height + weight
  *allergies
  *medication
• medical condition(s) - clickable to Tab 3.
• Organ donor

Tab 2. Owner details

• full name
• call name
• address
• phone needed
• important notes (like children nearby - extra ambulance needed)
• relationships (clickable -> showing Tab 5)

optional by opt-in:

• insurance data
• car data + nearest servicepoint
• upload organ donor registration

Tab 3. medical condition(s) details

detailed description (bullet points of each separate condition + dropdown for description)
linking to Tab 7. to show procedure

Tab 4. Medical history (only by privacy opt-in/extended permissions!!)

• detailed history health issues
• detailed history medication + dose
• upload medical/dentist/etc. records
• upload x-rays
• upload donor registration

Tab 5. Relationships (only by privacy opt-in/extended permissions!!)

• status (married/single/divorced)
• name spouse + phone number(s)
• children (names+date of bidefault+phone numbers)
• address (same as owner by default)
• next of kin (in case of emergency if it involves family)

Tab 6. first aid procedure

• description by owner how to respond/act in case of known issue x,y,z
• show general procedure in case of medical issue according to first aid guide (direct link)
• show first aid guide Red Cross + language selection (default: country of address)

Tab 7. user log (only by privacy opt-in/extended permissions)

• registration times of use + how long
• optional by opt-in: take picture of user (getting image of helper to identify/thank him/her later or identifiable abuser
• registration for doctor to determine history

Other Ideas:

• Problem with too any information (in extended form) - group information for basic available in basic for and rest hidden under second button "more". Empty field shouldn't be displayed.
• Problem with storing this data - those are really personal information so It could be good to store it in restricted part of system.

Pros and Cons of both forms:

Basic form
Pros:

• Simple and fast to use in stress
• Similar to other mobile OS. That means it wouldn't causes problems in use for paramedics

Cons:

• Sometimes it's to less information

Extended form
Pros:

• Really enough information for everyone not only paramedics to help
• Good for people living alone, who doesn't have anyone to call
• Identifying person, contacts, facts is much simpler especially when someone dies...
• Medical history can help when someone is ill for not ordinary disease

Cons:

• It's easy to get lost when these information are not grouped/hidden properly
• problems for paramedics to get needed information they should fond in regular phone (they are not notified how to find it on Ubuntu Touch)
• Someone unwanted (thief, founder of lost device) could know your restricted, personal data...

Important Posts:

@Flohack about project and ideas

"some words on that from the core team:

• Adding a colored icon like this to the indicator bar will break the style that we try to keep consistent for system-realated things. So this wont be acceptable at all for taking it into the main OS
• Even if we would accept it, its much too small. Somebody who does not know ,Ubuntu Touch and that is the majority of the ppl on the planet will never ever figure out that they can find ICE contacts and infos
• Why don´t you use the free space below the circle for that:
  
• Yes, that change involves hacking into Lomiri quite a bit, but it is not that complicated. And then add it to the system settings for configuration.
• In this position the icon can be colorful, and big enough so ppl recognize it.
• If you want to align design ideas with the core team, please ping @CiberSheep for that, he is always a friendly sheep "

@Flohack wrote important information: "The problem is make something accessible on the lock screen. (...) That's basically that you need to design an API for that"

@Lakotaubp & @theare27 proposed temporary solution for only displaying some information in circle using app: https://open-store.io/app/circle-message.mivoligo but as @dobey said to change information in circle you have to double tap it and it ma causes problem for first aid.

@Flohack about NFC - "NFC is currently not an available option in UT, the API is not implemented down to the Android layer."

First post changelog:

• 2020.07.28 - Title changed
• 2020.07.13 - added @Flohack 's post to important posts.
• 2020.07.13 - Added Started & Connected Project Section and written about @syper project, changed header "Missing (...)" to Information, added [solutions] to title
• 2020.07.07 - Added headers, split to basic and extended form, added NFC information, added "Other Information section", added Pros and Cons of both forms, added lock screen tag (@3T_Ed I couldn't add more than 5 so I picked lock screen)
• 2020.07.06 - added draft including information what we need to design everything, quotes, temporary solution, moved my first message to bottom

First message:

Hello everyone,
It would be wonderful if on lock screen there will be available big red/green button Emergency (for now it's too small in my opinion). Under it, there is dial pad. What I miss there, is second button for medical services called ICE Contacts & Owner information. I heard that paramedics are notified how to find this in regular phones, like android or apple. According to that, in contacts/settings we should have option to mark contacts as ICE and create queue of displaying them - not automatically by alphabet, but you know, your choice of most important person. The last thing is medical information like blood type, am I an organ donor and so on. It's pretty well done in LineageOS so it may be base model, but yeah, if you could include more and more information (and mentioned special contacts queering), It would be wonderful. I write it because I use my UT device as daily driver. It may safe life one time.
Thank You

Introduction

Hi,
I found out, that Ubuntu Touch has big opportunities. Especially terminal is so cool.
However, there are some lacks in GUI and opening termianl, retyping password then repeating same commands for simple things can be hard sometimes.

Started Projects

Scriptor

Unfortunately official latest it's for 15.04 version.
@jonius added a clickable.json and changed the framework to 16.04 so now app can run on 16.04 remember to click thanks to @jonius below

Download compatible version:
find "releases" in @jonius repo

Idea

App to run and control specified previously long commands and scripts

With this app you don't need to retype password repeat commands, find scripts location.

Example: Let's say I want to control my vpn and wrote loop script to force it reconnect all the time. Later I want to stop it because e.g. now I need TOR. With this app I just click the switch.

It would be great If in the half screen appeared preview with tabs.

Important

([] are my annotations.)

In Scriptor there are some bugs described below.

@jonius: It [scriptor] still works well on Ubuntu Touch. I added a clickable.json and changed the framework to 16.04: https://gitlab.com/jonnius/scriptor
If someone is interested in maintaining the app, please just fork the repo and release it to the OpenStore. The README needs to be cleaned up and the busybox download in app does not seem to work. But I don't think it is even necessary, so maybe it could just be removed.

First post changelog

• 2020.08.09 - added header started project, changed title to [WIP]
• 2020.18.08 - idea appeared

@3T_Ed Thank You for support, links, ideas I mean continuing thread

So I created simple layout concept. Don't look at colors, background etc. It's just first quick idea.

On first Image I modified my lock screen screenshot by adding button under the circle. This button should open emergency screen after double click (second attached image)

Button should be visible but not aggressive looking. Background of it may be transparent, borders may be thin and writing regular. (I left button there because It is the fastest way to get needed information and common phones can be unlocked by swipe-up not like UT devices and in stress it may cause problems)

On second image I created simple emergency screen layout

On top we have ICE contacts. On bottom more information about owner.

In my opinion, on android, there are too many steps to get needed information, so that's why I simplified it.

Please write Your ideas, I'm only a human and probably I forgot about adding something.

Hi,

I was thinking about how to make Ubuntu Touch more popular and how to get porters.

1 - Way of thinking

Ok so, Ubuntu Touch is connected with slogans like "Real linux distributions for mobile devices" from we can be proud of.

But it's not connected whatsoever with ordinary devices. I won't find it if I don't search for what exactly Ubuntu Touch is. However to become a strong alternative to android UT needs to be popular. So we need to appear in many environments somehow connected with mobile devices

2 - devs, our brothers

Nowadays there are mass of custom roms avaliable for almost any phone. Devices are continuously maintained, trees are updated.
But where does it happen? Mostly on XDA.

What do you think about joining officialy XDA. Writing an articles that will be on the first site on XDA feed. Maybe this will help experienced developers to know something about UBports and join this forum and they could help with porting UT to new devices?

*Note that started as I have just read about new xda phone! My goal is to keep beeing visible there ans post UT ports as threads like custom roms for those who doesn't follow feed.

3 - foolproof

Why iOS is so popular? Things become popular because they are easy to use, easy to install, easy to manage, easy to be turned on/off. Unfortunately GUI is important for those who are annoyed of something and want to make a change.

Other thing here is porting to new devices. Noob porters like me needs to have step by step documentation to help grow UT.

4 - Privacy

We know what is massive surveillance preinstalled in our phones bought from ordinary market. I see now pissed off people that just want to have simple mobile which is not watching or hearing him/her 24/7. So popularizing UT in some privacy oriented communities may help.

5 - Easy to get - marketing

Ubuntu Touch needs to be first operating system that will be preinstalled on device. It's happening: PinePhone , VollaPhone and f(x)tec Pro1 but To achieve success we need something bigger - UBports shop, where you can buy any Ubuntu Touch supported phone, new or used and million stuff connected, logos, shirts but it needs to be together. This can make feel the someone belongs to group.

How to organise this shop... It's harder. I suppose that it might be something like association of people on the whole world, that can buy or transfer some devices flash and sell locally.

Example:
I go to the official ubports site and then I see big button called buy.
Inside there will be map of the world which tells you where it's available to buy now or order. Then you will have filters: ram internal storage brand etc. Like in normal shop. And offers, contact.

(if billing will be organized without any mess I can be a volunteer, my government does search for people who are the "sly-ones" but I'd really love to help!)

6 - Promotion

Famous people, unfortunately It might be irritating but when someone popular will have such a device... Who knows

On the other hand, we have our families, friends. Why not to try introduce them Ubuntu Touch device? This way I convinced e.g. my dad to switch!

9 - try before you buy

You know, I like to test things before I buy something. Probably most people. So if we don't want to search youtube for old reviews we could start virtual machine on the ubports site with every channel. Like in android studio. You know. You are using virtual phone.

10 - documentation organized

It'd be great if we could share our knowledge in ordered way in one place. Some tricky things are known by specialists but not everyone. We could have split documentation starting from really basic things, ending on porting etc. It could also be written by community guys.

Feel free to comment, correct me

First post changelog

I may remember something later, that's why

• 2020.10.27 - removed statements, because there were not exactly the true and we should be ethical. So just left idea. mistakes corrected,
• 2020.10.26 - topic creation

What do You think about ICE contacts and medical information quick access on lockscreen?
https://forums.ubports.com/topic/4551/request-privileged-ice-contacts-available-on-lockscreen-medical-information

@3T_Ed sure

@arubislander

You are right. You pointed out the true. So let me remove those statements and leave just idea

Hi,

I'm so happy, that someone remembered about old xperias. They are great!

However honami is xperia z1 (xperia xz1 is called poplar).

Which halium version did you build? If there are so many problems maybe you could consider halium 9 porting with Generic System Image (GSI)? As there are Lineage 16 avaliable for honami (and other based on android 8 and later) so all after project treble where device specific code is moved to vendor partition. Read about the differences between previous halium version and 9 in GSI llink

I'm not a developer but I hope it may be helpful

Do you have any experience which you could find helpful and share about porrting UT to sony phones? I have couple devices which I'd like to be running UT,

1. Xperia XZ1 compact (lilac) - now I'm working on it...
2. Xperia XZ1 dual (poplar_dsds)
3. Xperia Z2 (sirius) - same "z" family as honami
4. Xperia Z3 compact (z3c) - same "z" family as honami

@Capsia
Big Thanks!!!

I also had problems like @herr-b -

NetworkManager ... result="success"
... Started the VPN service ...
... Saw the service appear; activating connection ...
... <error> ... vpn-connection ... Failed to request VPN secrets #3: No agents were available for this request.

But I followed nmcli steps and got it working with custom gateway port.

I'll soon update first post for solution and change title to solved.

Once again thank You

Hi,

I try to build halium 9 for Sony xperia xz1 compact codname "lilac".
It was shipped with android 8 then updated to 9. It has quiet good support on XDA I mean repositories, device tree, vendor.

I'm just passionate not experienced dev, but I'm determined and I like learning :).

My building machine is (fortunately, only for some time) xubuntu 18.04 12GB ram, 12GB SWAP HDD 1tb, intel i5-5200u 4 threads. then something 2 times better when I'll finish my PC.

I visited XDA for custom roms building guides, Lineage site and the halium, ubports porting guide but then redirected here and here

Here are needed device configuration, branch lineage-16 (Note that the manifest is slightly different, but it's explained in only one issue in this repository)

My steps:

1. Previously - Built AOSP 11 using sony guide - learned how basic tools and repo work
2. Previously - Building crDroid based on android 10 - learned what are manifest, device tree, kernel, vendor etc.
3. Now - Building Halium 9 - learned what is project treble, GSI

• Step 1 - repo init -u https://github.com/Halium/android -b halium-9.0 note that --depth=1 didn't work for me
• Step 2 - repo sync
• Step 3 - added local manifest in ~/.repo/local_manifests/roomservice.xml and repo sync

<manifest>
<!-- SONY -->
<project name="whatawurst/android_kernel_sony_msm8998" path="kernel/sony/msm8998" remote="github"/>
<project name="whatawurst/android_device_sony_common-treble" path="device/sony/common-treble" remote="github"/>
<project name="whatawurst/android_device_sony_yoshino" path="device/sony/yoshino" remote="github"/>
<project name="whatawurst/android_device_sony_lilac" path="device/sony/lilac" remote="github"/>
<!-- Pinned blobs for lilac -->
<project name="whatawurst/android_vendor_sony_lilac" path="vendor/sony/lilac" remote="github"/>
</manifest>

• Step 4 - Applied patches by running cd ~/hybris-patches then . apply-patches.sh output here with one warning
• Step 5 - Here I stopped...
  Make your device tree inherit from halium.mk (...):
  Ok , I understood that I need to change my ~/device/sony/lilac/lineage_lilac.mk

$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# Inherit device configuration
$(call inherit-product, device/sony/lilac/device.mk)

### LINEAGE
$(call inherit-product, vendor/lineage/config/common_full_phone.mk)

to

$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
# $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/halium.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# Inherit device configuration
$(call inherit-product, device/sony/lilac/device.mk)

### LINEAGE
# $(call inherit-product, vendor/lineage/config/common_full_phone.mk)

Changes: commented full_base_telephony.mk and lineageOS stuff added halium.mk instead

Unfortunately I have no idea what to do with: "remove Java-dependent parts" what is that file, where is it located?

I know I need to learn muuuch more, could you help my find some guides, documentation related to this. What statement should I search for?

Thanks in advance!

@guf

Thank you I'll try, when I have some time!

Tbh, I started working on postmarketOS build as documentation is more clear for me (new to porting), but I'll watch both guides and maybe I'll finally manage to do at least one of linux for lilac.

(I prepared device APKBUILD, sucessfully compiled kernel and flashed it to device but I don't know what actually happened. Only thing that tells device is on is slightly glowing sony logo like on calculator. I have to try connecting to device by ssh or telnet. However maybe someone could help me proceed by preparing kernel path that adds blobs to kernel. Something like this was done for older kernel, diffrent commit, which breaks on newer build, so maybe it can be corrected?)

I asked on pmOS buliding group for help. I got extra information about this device. Something like "It has really broken UFS that want's to delete itself so be carefull while minelining it"

@saveurlinux

Thanks for interesting I really wish I coud do that asap. I decided to read some books about linux in general because I feel that I need to understand much more to proceed... However I really want to do it especially because postmarketOS has problems with booting on this device. I'll write here about progress.

@arubislander

You are right. You pointed out the true. So let me remove those statements and leave just idea

@Luksus

Thanks for reply and spending your time helping me understand

Unfortunately there's still no success.

I think I just missed something important before. I'll start from beginning. I'll Read everything once again. And than try, not to consume more time. I'll try then to make step list. Eventually I'll wait for Halium 9 full documentation.

Hi,

I was thinking about how to make Ubuntu Touch more popular and how to get porters.

1 - Way of thinking

Ok so, Ubuntu Touch is connected with slogans like "Real linux distributions for mobile devices" from we can be proud of.

But it's not connected whatsoever with ordinary devices. I won't find it if I don't search for what exactly Ubuntu Touch is. However to become a strong alternative to android UT needs to be popular. So we need to appear in many environments somehow connected with mobile devices

2 - devs, our brothers

Nowadays there are mass of custom roms avaliable for almost any phone. Devices are continuously maintained, trees are updated.
But where does it happen? Mostly on XDA.

What do you think about joining officialy XDA. Writing an articles that will be on the first site on XDA feed. Maybe this will help experienced developers to know something about UBports and join this forum and they could help with porting UT to new devices?

*Note that started as I have just read about new xda phone! My goal is to keep beeing visible there ans post UT ports as threads like custom roms for those who doesn't follow feed.

3 - foolproof

Why iOS is so popular? Things become popular because they are easy to use, easy to install, easy to manage, easy to be turned on/off. Unfortunately GUI is important for those who are annoyed of something and want to make a change.

Other thing here is porting to new devices. Noob porters like me needs to have step by step documentation to help grow UT.

4 - Privacy

We know what is massive surveillance preinstalled in our phones bought from ordinary market. I see now pissed off people that just want to have simple mobile which is not watching or hearing him/her 24/7. So popularizing UT in some privacy oriented communities may help.

5 - Easy to get - marketing

Ubuntu Touch needs to be first operating system that will be preinstalled on device. It's happening: PinePhone , VollaPhone and f(x)tec Pro1 but To achieve success we need something bigger - UBports shop, where you can buy any Ubuntu Touch supported phone, new or used and million stuff connected, logos, shirts but it needs to be together. This can make feel the someone belongs to group.

How to organise this shop... It's harder. I suppose that it might be something like association of people on the whole world, that can buy or transfer some devices flash and sell locally.

Example:
I go to the official ubports site and then I see big button called buy.
Inside there will be map of the world which tells you where it's available to buy now or order. Then you will have filters: ram internal storage brand etc. Like in normal shop. And offers, contact.

(if billing will be organized without any mess I can be a volunteer, my government does search for people who are the "sly-ones" but I'd really love to help!)

6 - Promotion

Famous people, unfortunately It might be irritating but when someone popular will have such a device... Who knows

On the other hand, we have our families, friends. Why not to try introduce them Ubuntu Touch device? This way I convinced e.g. my dad to switch!

9 - try before you buy

You know, I like to test things before I buy something. Probably most people. So if we don't want to search youtube for old reviews we could start virtual machine on the ubports site with every channel. Like in android studio. You know. You are using virtual phone.

10 - documentation organized

It'd be great if we could share our knowledge in ordered way in one place. Some tricky things are known by specialists but not everyone. We could have split documentation starting from really basic things, ending on porting etc. It could also be written by community guys.

Feel free to comment, correct me

First post changelog

I may remember something later, that's why

• 2020.10.27 - removed statements, because there were not exactly the true and we should be ethical. So just left idea. mistakes corrected,
• 2020.10.26 - topic creation

@Luksus

Thank you for replying! I almost understood

I'm still, not sure only where I should search mentioned .mk files - what is exactly device root directory you mentioned? Is it~/device/sony in my case?

However I tired to make halium-boot hoped that hybris-patches did all job and build complied successfully.

Then I got my device with stock firmware and TWRP, then wiped data, flashed halium-boot as boot and GSI zip.

Device didn't booted in UT and didn't returned to recovery so I went to TWRP by pressing buttons, wiped all partitions and re-flashed both files and nothing happened.

I tired same thing with lineage as system befor UT, with no change.

Hi,

I try to build halium 9 for Sony xperia xz1 compact codname "lilac".
It was shipped with android 8 then updated to 9. It has quiet good support on XDA I mean repositories, device tree, vendor.

I'm just passionate not experienced dev, but I'm determined and I like learning :).

My building machine is (fortunately, only for some time) xubuntu 18.04 12GB ram, 12GB SWAP HDD 1tb, intel i5-5200u 4 threads. then something 2 times better when I'll finish my PC.

I visited XDA for custom roms building guides, Lineage site and the halium, ubports porting guide but then redirected here and here

Here are needed device configuration, branch lineage-16 (Note that the manifest is slightly different, but it's explained in only one issue in this repository)

My steps:

1. Previously - Built AOSP 11 using sony guide - learned how basic tools and repo work
2. Previously - Building crDroid based on android 10 - learned what are manifest, device tree, kernel, vendor etc.
3. Now - Building Halium 9 - learned what is project treble, GSI

• Step 1 - repo init -u https://github.com/Halium/android -b halium-9.0 note that --depth=1 didn't work for me
• Step 2 - repo sync
• Step 3 - added local manifest in ~/.repo/local_manifests/roomservice.xml and repo sync

<manifest>
<!-- SONY -->
<project name="whatawurst/android_kernel_sony_msm8998" path="kernel/sony/msm8998" remote="github"/>
<project name="whatawurst/android_device_sony_common-treble" path="device/sony/common-treble" remote="github"/>
<project name="whatawurst/android_device_sony_yoshino" path="device/sony/yoshino" remote="github"/>
<project name="whatawurst/android_device_sony_lilac" path="device/sony/lilac" remote="github"/>
<!-- Pinned blobs for lilac -->
<project name="whatawurst/android_vendor_sony_lilac" path="vendor/sony/lilac" remote="github"/>
</manifest>

• Step 4 - Applied patches by running cd ~/hybris-patches then . apply-patches.sh output here with one warning
• Step 5 - Here I stopped...
  Make your device tree inherit from halium.mk (...):
  Ok , I understood that I need to change my ~/device/sony/lilac/lineage_lilac.mk

$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# Inherit device configuration
$(call inherit-product, device/sony/lilac/device.mk)

### LINEAGE
$(call inherit-product, vendor/lineage/config/common_full_phone.mk)

to

$(call inherit-product, $(SRC_TARGET_DIR)/product/core_64_bit.mk)
# $(call inherit-product, $(SRC_TARGET_DIR)/product/full_base_telephony.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/halium.mk)
$(call inherit-product, $(SRC_TARGET_DIR)/product/languages_full.mk)

# Inherit device configuration
$(call inherit-product, device/sony/lilac/device.mk)

### LINEAGE
# $(call inherit-product, vendor/lineage/config/common_full_phone.mk)

Changes: commented full_base_telephony.mk and lineageOS stuff added halium.mk instead

Unfortunately I have no idea what to do with: "remove Java-dependent parts" what is that file, where is it located?

I know I need to learn muuuch more, could you help my find some guides, documentation related to this. What statement should I search for?

Thanks in advance!

Hi,

I'm so happy, that someone remembered about old xperias. They are great!

However honami is xperia z1 (xperia xz1 is called poplar).

Which halium version did you build? If there are so many problems maybe you could consider halium 9 porting with Generic System Image (GSI)? As there are Lineage 16 avaliable for honami (and other based on android 8 and later) so all after project treble where device specific code is moved to vendor partition. Read about the differences between previous halium version and 9 in GSI llink

I'm not a developer but I hope it may be helpful

Do you have any experience which you could find helpful and share about porrting UT to sony phones? I have couple devices which I'd like to be running UT,

1. Xperia XZ1 compact (lilac) - now I'm working on it...
2. Xperia XZ1 dual (poplar_dsds)
3. Xperia Z2 (sirius) - same "z" family as honami
4. Xperia Z3 compact (z3c) - same "z" family as honami

Introduction

Hi, I use my UT device as my daily driver.
One day I thought: Maybe I'll start updating OpenStreetMaps as my area is quiet outdated and I'd like to do some for others

Question

Is there any tested OSM editor (could be web-based) that works well on Ubuntu touch?

App Idea

Ubuntu Touch OpenStreetMap Editor:

• Multi-touch touch-screen compatibility
• Edit maps (quickly correct mistake e.g. store name)
• Upload he pictures
• Take picture with geotag and upload it later (when you don't have internet connection)
• Track me to update road data (useful for e.g. bicycle roads)

This is just quick syllabus, I'll surely correct and precise it lately after registartion and sample work with vespucci. If you know what should be included in app, because you are participant of OSM community feel free to correct me and comment

Other Information

List of available OSM editors, some of them are open-source

First post changelog

• 08.10.2020 - topic creation

@thrrgilag Thanks! Works great on my nexus 7 stable and nexus 5 RC

The strange thing happens when I test it on another nexus 5 RC and nexus 7 RC (in general I have 4 devices), apps crashes I mean - flfuffy frezzes and logs out from account
I was searching for the reason and... maybe it happens when device powers off, casued by critically low battery. This is what happened on both mentioned decices and after this situation fluffy stopped working
(reinstalling both apps and clearing data didn't work, so only OS reflash may work...)

For everyone interseted in matrix on UT device, with new qt web engine avaliable on RC, you can create simple webapp, there is no notifications and it lookls like desktop version but for now it may be alternative for devices where fluffy/pantalaimon crashes. Video and Pictures work, I'll test calls later.