Hi,
Just a question regarding UT Installer.
I read daily here several support requests from people who're not able to install UT correctly using the installer.
Most of the time they just forgot to read documentation... Installer says: "Dont worry it's easy"
However, it seems that people do mostly not proceed to the following steps:

. Activate developer mode
. Enable USB debugging
. Install ADB drivers
. Install fastboot

As result, UT image is not installed correctly (mostly locked on bootloader), and morevover it's than pretty hard to reset the phone to it's initial state.

So would it be possible to optimise UT installer integrating by default ADB and Fasboot packages as it's a snap software?

And as for Mac / Windows version, add links to download those elements?
Than we could add a few steps in the installation guide such as:
Did you activate developer mode? NEXT -> ADB + Fastboot packages are required to install UT on your device, please click here to install.... NEXT-> Please reboot your device in bootloader.... Next ->

So the main goal is to simplify as much as possible in an "all in one".
Does this idea make any sens?

Thank you for your feedbacks.

@Flohack Done too! Thanks a lot for this survey!

@Moem To simplify the answer, it is a question of modernizing the kernel - or rather the material abstraction of the Android kernel - from version 5 to version 7 (Nougat if I well remember).

Halium is a collaborative project to unify the Hardware abstraction layer for projects which run GNU/Linux on mobile devices with pre-installed Android.

A few UT main flagships devices are concerned by this new port which started around the beginning of this year.
No idea of the time to wait yet.... (Maybe @Flohack could better answer ?)

On the other hand, the update will be released to the smartphone system updates - like OTA updates do come. So don't worry, nothing to reinstall.

This new port should notably correct the problems related to the cameras of the smartphones concerned (Nexus 5, OplusOne...).

@michelbdec Please be more precise. Ubuntu Touch is NOT Ubuntu. Apps are using .click files. There's no Ubuntu software in Ubuntu Touch, but an open store: https://open-store.io/ in which you'll find "Dekko 2", which is currently the only email client available for Ubuntu Touch. (and works pretty well)

Btw, you can install some other Linux software using a Libertine container, but they might not work as expected, especially since they aren't design for a smartphone screen.

I think Pinetab is on the way to be soon available. Here's a brand new demo from Marius that runs UT on Pinetab as well as 2 days ago announcement:

https://www.pine64.org/2020/05/15/may-update-pinetab-pre-orders-pinephone-qi-charging-more/

https://m.youtube.com/watch?v=Ii6lAjgfW3c

So, I think I have fix that issue! According to a user advice: 1) Open UTmedia 2) Tap and hold "Select file" till a popup shows "select all / close" 3) click on "close". 4) Click "select file" again 5) Browse on "files" and select the required video to play 6) Video is sucessfully loaded in UTmedia and can be played! Hope this tip will help other users...

@libremax I'm glad to confirm that BT music player does perfectly work on both systems (Ford Sync + Seat media).
Sound's just perfect.
Notice: "Unknown artist + unknown track" are displayed on both screens. But this doesn't really matter to me.

So, to resume: On both systems:

Working:

. BT initial pairing
. Auto pairing
. Contacts synchronization
. Coverage signal shown on the car screen
. Name of the device well displayed
. Outgoing / incoming calls
. Vocal command
. In car microphone + High speaker
. Phone volume adjustment
. Music via Bluetooth on the car radio
. Auto swap in call mode

Not working:

. Battery status display
. In music mode: Displays the track being played
. Phone calls: Loud background noise covering much of the speaker's voice (recipient hears well)

Hope I've been this time clearer on my description

@mnjrupp Detailed workaround (Nexus 5): 1) Open UTmedia 2) Tap and hold "Select file" till a popup shows "select all / close" 3) click on "close". 4) Click "select file" again 5) Browse on "files" and select the required video to play 6) Video is successfully loaded in UTmedia and can be played!

@Rebecca58 I would love an altimeter app

@domubpkm Btw the milestone of 100 units sold was reached today!
https://www.indiegogo.com/projects/volla-phone-free-your-mind-protect-your-privacy#/

@libremax I'm glad to confirm that BT music player does perfectly work on both systems (Ford Sync + Seat media).
Sound's just perfect.
Notice: "Unknown artist + unknown track" are displayed on both screens. But this doesn't really matter to me.

So, to resume: On both systems:

Working:

. BT initial pairing
. Auto pairing
. Contacts synchronization
. Coverage signal shown on the car screen
. Name of the device well displayed
. Outgoing / incoming calls
. Vocal command
. In car microphone + High speaker
. Phone volume adjustment
. Music via Bluetooth on the car radio
. Auto swap in call mode

Not working:

. Battery status display
. In music mode: Displays the track being played
. Phone calls: Loud background noise covering much of the speaker's voice (recipient hears well)

Hope I've been this time clearer on my description

@libremax I meant, Bluetooth communication (incoming, outgoing calls) technically works...
So next step I'll try the BT music player on those devices.

I confirm that Bluetooth works on my both cars (Ford Sync + Seat media system) using Nexus 5 OTA-14. But there's an awful high-pitched background noise making the speaker's words almost inaudible. (on both systems) On the other hand, my interlocutor can hear me correctly.
All features are working well except the battery which is displayed as empty. I didn't try to hear my music via Bluetooth on those systems.

@nocomp Unfortunately the fix has been postponed to OTA-15: https://github.com/orgs/ubports/projects/24

However, the previously mentioned .deb file plugin works like a charm

@antonyj Indeed, do not download the Anbox image on the Nexus 5. It is already pre-installed by default. Doing so might creating bugs.

Just start here:
sudo mount -o rw,remount /
sudo apt update
sudo apt install anbox-ubuntu-touch android-tools-adb
anbox-tool install
exit

If you have an error message telling you an insufficient memory in /var, you can try as following:

sudo mount -o rw,remount /
sudo rm -r /var/cache/apt # delete the apt cache; frees space on system image
sudo tune2fs -m 0 /dev/loop0 # space reserved exclusively for root user on system image set to zero
sudo apt update # recreate apt cache to install Anbox and adb
sudo apt install anbox-ubuntu-touch android-tools-adb
sudo mount -o ro,remount /
exit

@maldukhn Don't know if it's related to your bug, but did you first install ADB and Fasboot on your PC? (sudo apt-get install adb && sudo apt-get install fastboot). Thoses packages are needed to install Ubuntu Touch on Android devices.

@MixMac Here we go! https://github.com/orgs/ubports/projects/24#column-11303039

Good new, project has been moved to « To do » in OTA-15 section.

@LRV Great Thank you.

@MixMac Unfortunately not. But it’s integrated in the OTA-15 Github « nice to have » section...

@domubpkm No, I installed Anbox on an experimental basis and tried a few Android apps. But didn't use Firefox as Morph is really fine for me. But I guess you can install Firefox not using Anbox but with Libertines. (easier way)