Configuring Ubuntu Touch¶
In the previous section you adjusted a configuration file directly in the UBports rootfs. The rootfs contains a number of other configuration files with some standard settings that do not necessarily conform to your device. These must be modified to fit your device. The rootfs itself is read only and identical for all devices. You cannot modify the rootfs itself. Instead, the correct way to adjust the configuration is with overlay files, as described below.
Note that as a rule of thumb, the method described below applies if the file you need to edit can be found in the /etc directory (or a subdirectory of this) on your device. You should not attempt to overwrite files located elsewhere using this method. Note also that it is not possible to transfer executable files using this method, and that you cannot insert new files either. The only thing this method does is to overwrite a file that is already present in the build. Thus, by following the steps described here you can replace existing configuration files with ones that are tailored specifically to your device.
It is also worth noting that, as of writing, there are a number of legacy files in the mentioned directories that serve no purpose but exist there simply pending removal. Therefore, make sure you are overwriting files that are actually used by the system as your changes otherwise will have no effect.
In your device directory, create a subdirectory named ‘ubuntu’. Collect the files you wish to inject into your build in this directory.
- Relevant files are for example (but this list is incomplete):
70-android.rules (the udev rules for your device, see previous section)
android.conf (for display scaling, see below)
touch.pa (for pulseaudio sound configuration/initialization, see below)
These files are then injected by adding a code block to the file
device.mk in your device directory. For the three files above add the following code:
### Ubuntu Touch ### PRODUCT_COPY_FILES += \ $(LOCAL_PATH)/ubuntu/70-android.rules:system/halium/lib/udev/rules.d/70-android.rules \ $(LOCAL_PATH)/ubuntu/android.conf:system/halium/etc/ubuntu-touch-session.d/android.conf \ $(LOCAL_PATH)/ubuntu/touch.pa:system/halium/etc/pulse/touch.pa ### End Ubuntu Touch ###
The string before the colon ‘$(LOCAL_PATH)/ubuntu/70-android.rules’ specifies the path to the source file to be injected. The string after the colon ‘system/halium/lib/udev/rules.d/70-android.rules’ specifies where you want it placed on the device.
- The general steps to follow are thus:
Copy the file you wish to modify to the ‘ubuntu’ directory you have created in your device source tree.
Edit the file as needed.
Add a line to the PRODUCT_COPY_FILES section of your device.mk file as shown above.
Rebuild your system.img and reflash together with the ubports rootfs.
The target paths for the files mentioned above are not randomly chosen. You must use the specified paths.
When you specify target path ‘system/halium/etc/myfilename’ your file ‘myfilename’ will end up in the ‘/etc’ directory of your device (i.e. without the leading ‘system/halium’)
When you have made the adjustments you need and prepared your source as described above, you have to rebuild your system.img:
mka systemimage. When rebuilding the system image after small changes like these, you need not
mka clean first. However, changes to PRODUCT_PROPERTY_OVERRIDES might not get detected by the build system. Go to your output folder, enter the system folder and delete
build.prop in order to get it regenerated.
Extract the file 70-android.rules which you created in the previous section using
adb pull or
scp and copy it to the ‘ubuntu’ directory of your device source tree. Complete steps 3 and 4 above.
There are two variables that set the content scaling for Unity 8 and Ubuntu Touch applications:
There are also other options available that may be useful for you depending on your device’s form factor. These are mentioned below and all of these settings are explained in depth in the reference section on Display settings.
All of these settings are guessed by Unity 8 if none are set. There are many cases, however, where the guess is wrong (for example, very high resolution phone displays will be identified as desktop computers). To manually set a value for these variables, simply edit the file at
etc/ubuntu-touch-session.d/android.conf specifying them. For example, this is the file for the Nexus 7 tablet:
$ cat /etc/ubuntu-touch-session.d/flo.conf GRID_UNIT_PX=18 QTWEBKIT_DPR=2.0 NATIVE_ORIENTATION=landscape FORM_FACTOR=tablet
The Display settings section details methods for deriving values for these variables.
Once you have adjusted the
android.conf file to the display settings needed for your device, this file should be incorporated into your build.
Create the file android.conf in your ‘ubuntu’ directory and enter the settings you determined and tested in the previous section. Complete steps 3 and 4 above, taking care to remember the note on how to Rebuild system.img.
Apply apparmor kernel patches¶
Start by downloading the backported apparmor patch corresponding to your device’s kernel version. Your kernel version is specified at the beginning of your kernel defconfig file, i.e. the one you edited in section Edit kernel config above.
You now need to delete your entire BUILDDIR/kernel/VENDOR/MODEL/security/apparmor subdirectory and replace it with the one you downloaded. Then rebuild halium-boot.
If you get errors when building, you will need to resolve them one by one, modifying your source code as needed. Note that you should only modify the code in the apparmor subdirectory if at all possible. Modifying code elsewhere will more than likely just compound your problems.
Seek help as needed from one of the sources mentioned in section Getting community help.
The supplied touch.pa file located in the /etc/pulse directory of your device needs adjustment. Extract the file and copy it to your ‘ubuntu’ directory.
Locate the line:
load-module module-droid-discover voice_virtual_stream=true
and replace it with this:
load-module module-droid-discover rate=48000 quirks=+unload_call_exit
At the end of the file, append this:
### Automatically load the audioflinger glue .ifexists module-droid-glue-24.so load-module module-droid-glue-24 .endif
Now complete steps 3 and 4, taking care to remember the note on how to Rebuild system.img.
When porting to devices running older kernel versions (mainly 3.x), it is necessary to replace the kernel bluetooth stack with a newer one. This is because the newer bluetooth hardware in today’s bluetooth peripheral devices often has trouble talking to the older bluetooth drivers. This can be fixed by bringing in driver code from newer Linux kernel versions. The process is called backporting.
Backporting has been greatly facilitated by the Linux Backports Project which has existed for some time. This project is aimed at mainline Linux kernels and the tools (scripts) therein are not specifically tailored to Ubuntu Touch. They will consequently abort at some point during the process. However, they are the best option available, and can provide significant help all the same. The method below is based on the use of a version of these scripts which has been specially prepared by Canonical.
Although there are other kernel versions besides v4.2 available, the backports script is specifically tailored to backporting from version 4.2 and thus effectively limits you to this option.
Bluetooth backporting steps¶
The steps are as follows:
Record bluetooth driver and settings
Download backports script
Download 4.2 kernel source
Run backports script and fix errors
Apply security patch
Apply new settings
Build and flash halium-boot.img
Build and flash system.img
Record bluetooth driver and settings¶
By the time you reach this point in the porting process, you will have completed building halium-boot (probably a number of times). Your kernel defconfig will contain bluetooth settings including one that designates the driver used by your device. These must be recorded before proceeding.
The experienced developer will likely be able to determine the relevant settings manually by searching through the defconfig file. Many of them will appear next to each other in one place in the file. Some may be spread elsewhere making them difficult to locate. When searching manually, help can be found by consulting the Kconfig files in relevant subdirectories of your kernel source tree.
If you do not have extensive experience, use the
menuconfig tool instead, taking care to use it ONLY for reference, i.e. without making any changes.
Modifications done with
menuconfig will not affect your kernel defconfig file, but may still corrupt your build.
After completing a build of halium-boot.img:
cd out/target/product/[DEVICE]/obj/KERN_OBJ ARCH=arm64 make menuconfig
(If your device is armhf, use
Navigate to the bluetooth drivers submenu and note down all activated settings and what they do. Also note which other settings they depend on (found under Help).
For the Samsung Galaxy S7 (herolte) the original defconfig file contains a number of CONFIG_BT settings, none of which actually designate the bluetooth driver used by this device. The setting for the driver itself is CONFIG_BCM4359=y. This was not one of the drivers brought in by the backporting steps below. It therefore had to be added afterwards.
Download backports script¶
Clone the backports scripts into a directory outside your halium source tree by issuing this command from your home (~) directory:
git clone https://github.com/ubuntu-phonedations/backports.git -b for-ubuntu backport-scripts
This downloads the backports scripts prepared by Canonical based on the Backports Project mentioned above, and places them in the directory
~/backport-scripts. The scripts are specifically written to backport from kernel version 4.2.
Download 4.2 kernel sources¶
Create a directory (outside your halium source tree) for the kernel source from which you will pull the newer drivers:
Now clone the kernel source for v4.2:
cd ~/kernel-backports git clone https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next -b v4.2
Run backports script and fix errors¶
Navigate to your backports scripts directory and issue the command below (using Python2 as shown):
python2 ./gentree.py --copy-list ./copy-list --integrate --clean --git-revision v4.2 ~/kernel-backports/linux-next ~/halium/kernel/[VENDOR]/[MODEL_NAME]
It is to be expected that there are errors during this step. You will then have to determine the cause, fix it and retry. The last error message concerns the Makefile and includes info about having generated a file named
Makefile.rej, this means you will find information in this file about changes that did not complete successfully, but which you can apply yourself. These need to be completed before proceeding with the build.
Apply new settings¶
Your kernel config file (defconfig) needs to be modified in order for the backported driver and protocol code to be activated.
Start by locating all lines beginning with
CONFIG_BT_ and move these to the end of the file. Collecting them there makes the subsequent steps somewhat easier by helping to keep track of the changes you make.
Next, deactivate all that are activated, i.e. do not have a leading
#, by inserting this leading
#. At the same time, for each one, add a corresponding one beginning with
and then insert the corresponding line for backports:
Now add these settings:
#Depending options for new stuff from backports #CONFIG_CRC16=y CONFIG_CRYPTO=y CONFIG_CRYPTO_BLKCIPHER=y CONFIG_CRYPTO_AES=y CONFIG_CRYPTO_CMAC=y CONFIG_CRYPTO_HMAC=y CONFIG_CRYPTO_ECB=y CONFIG_CRYPTO_SHA256=y CONFIG_CRYPTO_USER_API=y CONFIG_CRYPTO_USER_API_HASH=y CONFIG_CRYPTO_USER_API_SKCIPHER=y #CONFIG_TTY=y
At this point, check for any remaining settings you recorded from your original defconfig, which were dependent upon
CONFIG_BT=y and have not been replaced by a corresponding
CONFIG_BACKPORT_BT_XXXX=y setting, making sure not to forget your device’s bluetooth driver. Such settings will no longer have any effect and must be pulled into the build in the following manner:
The corresponding source file(s) will have to be migrated from their original location to the corresponding location under
backport/bluetooth/. The files
Kconfig need to be edited to include this missing setting or else they will not be built. Check the corresponding files in the original location for the necessary settings.
Once the above is complete, add the following lines and edit as necessary, following the directions below:
CONFIG_BACKPORT_DIR="backports/" CONFIG_BACKPORT_INTEGRATE=y # CONFIG_BACKPORT_KERNEL_3_5=y #disable for kernel > 3.4 # CONFIG_BACKPORT_KERNEL_3_6=y #disable for kernel > 3.4 # CONFIG_BACKPORT_KERNEL_3_7=y #disable for kernel > 3.4 # CONFIG_BACKPORT_KERNEL_3_8=y #disable for kernel > 3.4 # CONFIG_BACKPORT_KERNEL_3_9=y #disable for kernel > 3.4 # CONFIG_BACKPORT_KERNEL_3_10=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_11=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_12=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_13=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_14=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_15=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_16=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_17=y #disable for kernel > 3.10 # CONFIG_BACKPORT_KERNEL_3_18=y #disable for kernel = 3.18 CONFIG_BACKPORT_KERNEL_3_19=y CONFIG_BACKPORT_KERNEL_4_0=y CONFIG_BACKPORT_KERNEL_4_1=y CONFIG_BACKPORT_KERNEL_4_2=y CONFIG_BACKPORT_KERNEL_NAME="Linux" CONFIG_BACKPORT_KERNEL_VERSION="v4.2" CONFIG_BACKPORT_LINUX=y CONFIG_BACKPORT_VERSION="v4.2" CONFIG_BACKPORT_BPAUTO_USERSEL_BUILD_ALL=y
As an example, the lines above have been edited to conform with backporting from kernel 4.2 to a device with kernel version 3.18. For devices running lower kernel versions enable each line specifying a version above the device’s kernel version by removing the leading
# on these lines.
You are now ready to build.
Build and flash halium-boot.img¶
Return to the root of your BUILDDIR and build:
Build errors may occur and will vary depending on device. Handle them one at a time, seeking help as necessary.
After building and flashing halium-boot, check the output of
dmesg on the device to see that bluetooth has been enabled:
dmesg | grep tooth
Your output should resemble the following (from the Samsung Galaxy S7):
phablet@ubuntu-phablet:~$ dmesg | grep tooth [ 2.219667] lucky-audio sound: moon-aif3 <-> lucky-ext bluetooth sco mapping ok [ 2.252591] Bluetooth: RFCOMM TTY layer initialized [ 2.252601] Bluetooth: RFCOMM socket layer initialized [ 2.252613] Bluetooth: RFCOMM ver 1.11 [ 2.252626] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 2.252631] Bluetooth: BNEP filters: protocol multicast [ 2.252639] Bluetooth: BNEP socket layer initialized [ 2.252646] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 2.252654] Bluetooth: HIDP socket layer initialized [ 2.252661] Bluetooth: Virtual HCI driver ver 1.5 [ 2.252736] Bluetooth: HCI UART driver ver 2.3 [ 2.252743] Bluetooth: HCI UART protocol H4 registered [ 2.252749] Bluetooth: HCI UART protocol BCSP registered [ 2.252754] Bluetooth: HCI UART protocol LL registered [ 2.252760] Bluetooth: HCI UART protocol ATH3K registered [ 2.252765] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 2.252771] Bluetooth: HCI UART protocol BCM registered [ 2.252876] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 2.253388] [BT] bcm4359_bluetooth_probe. [ 2.253630] [BT] bcm4359_bluetooth_probe End [ 5.376110] [BT] Bluetooth Power On. [ 7.499943] [BT] Bluetooth Power On. [ 8.051620] [BT] Bluetooth Power On.
If you do not get similar output, something has gone wrong. Check that you completed all steps above as described and seek help as needed.
You have now rebuilt your halium-boot.img to include updated bluetooth drivers and only one final step remains.
Build and flash system.img¶
The system image needs to be rebuilt with a configuration script for bluetooth adapted to your device. On the completed build, this file is located at:
An example script can be found here. Make sure to adapt as necessary.
Place this script in your
device/[VENDOR]/[DEVICE]/ubuntu directory and inject it using the overlay file method described above.
Rebuild and flash your