ReleaseNotes

Differences between revisions 39 and 77 (spanning 38 versions)
Revision 39 as of 2013-07-24 08:22:03
Size: 16126
Editor: cpe-76-94-226-228
Comment: Added much-needed clarity the secure shell access steps
Revision 77 as of 2017-02-07 11:25:28
Size: 1001
Editor: sil2100
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
= Touch Developer Preview Release Notes = == Releases ==
Line 6: Line 6:
== Disclaimer == The release notes from earlier ETA's and preview releases weren't wikified, however you can see the changelogs.
Line 8: Line 8:
<<Include(../Disclaimer)>> [[http://people.canonical.com/~lzemczak/landing-team/ota/|Changelogs]]
Line 10: Line 10:
== Overview == [[Touch/ReleaseNotes/OTA-5|OTA-5]]
Line 12: Line 12:
The Ubuntu Touch Developer Preview is '''intended to be used for development and evaluation purposes only'''. It does not provide all of the features and services of a retail phone and is not intended to replace your current handset. This preview is the first release of a very new and unfinished version of Ubuntu and it will evolve quickly. [[Touch/ReleaseNotes/OTA-6|OTA-6]]
Line 14: Line 14:
Follow for [[../Install|the installation instructions]] to install Touch Preview, which include a list of supported devices. [[Touch/ReleaseNotes/OTA-7|OTA-7]]
Line 16: Line 16:
This '''release uses Ubuntu 13.10 as its basis'''. It introduces a revised version of [[Unity]] oriented toward touch devices and new concepts in user experience. It also introduces a set of applications written using the previously announced [[http://developer.ubuntu.com/gomobile|Ubuntu SDK Preview]]. [[Touch/ReleaseNotes/OTA-8|OTA-8]]
Line 18: Line 18:
== Accessing the system for development == [[Touch/ReleaseNotes/OTA-8.5|OTA-8.5 (hotfix)]]
Line 20: Line 20:
=== User Accounts === [[Touch/ReleaseNotes/OTA-9|OTA-9]]
Line 22: Line 22:
The images have a pre-configured user account called `phablet`, with the account password also set to `phablet`.
There is a set of default sample accounts for the tablet, the login passwords are set to the first name in lowercase. These are for demonstration purposes and do not affect the user session.
[[Touch/ReleaseNotes/OTA-9.1|OTA-9.1 (hotfix)]]
Line 25: Line 24:
<<Anchor(SshAccess)>>
=== Accessing the device over SSH ===
[[Touch/ReleaseNotes/OTA-10|OTA-10]]
Line 28: Line 26:
The recommended way to get shell access to the device is through SSH.
--(Ubuntu runs inside a custom container which uses a partitioned PID namespace. Using SSH allows a shell to be created within the new container, and thus have a proper view of the Ubuntu PID namespace.)--
[[Touch/ReleaseNotes/OTA-10.1|OTA-10.1 (security hotfix)]]
Line 31: Line 28:
Whenever you're asked for a password, it's `phablet`. [[Touch/ReleaseNotes/OTA-11|OTA-11]]
Line 33: Line 30:
To setup secure shell access, do the following:
 1. Follow the [[#AdbAccess|steps for access over ADB]]. From here, you should be in the phablet shell.
 1. Skip this step if you've already installed the `openssh-server` package on the device and your computer. Otherwise, run `sudo apt-get install openssh-server` as necessary.
 1. Run `ip addr show wlan0` or `ifconfig wlan0` on the device's terminal or the phablet shell to get its IP address (inet addr:). You will need this number for step 5. For the ifconfig option, you'll need to enable the `/proc` filesystem by running: `sudo mount -t proc proc /proc`.
 1. Press the Ctrl+D key combination 3 times to successively exit all shells. Alternatively, you can start a new terminal (Ctrl+Alt+T) to run the command in the next step
 1. Run `ssh phablet@ipaddress_of_device` to connect to the device. If you're connecting for the first time, you'll be prompted to add the device to your list of known hosts, so accept the prompt.
[[Touch/ReleaseNotes/OTA-12|OTA-12]]
Line 40: Line 32:
You also can use adb port forwarding to allow SSH access to the Ubuntu container via USB. To do this, run [[Touch/ReleaseNotes/OTA-13|OTA-13]]
Line 42: Line 34:
 {{{
adb forward tcp:8888 tcp:22
ssh phablet@localhost -p 8888
}}}
[[Touch/ReleaseNotes/OTA-14|OTA-14]]
Line 47: Line 36:

<<Anchor(AdbAccess)>>
=== Accessing the device over ADB ===

It is recommended to access the device through SSH to properly see the Ubuntu PID namespace. However you can adb into the device as well for some tasks. Do the following:

 1. Start a terminal on your computer by pressing the Ctrl+Alt+T key combination
 1. If you have already set up your environment for flashing Ubuntu images, skip to the next step. Otherwise [[../Install#Setup_the_Touch_Developer_Preview_Tools_PPA|install the Touch Preview tools PPA]].
 1. Run the following commands to connect to the device through ADB:
 {{{
adb root
adb shell}}}
 1. Execute the following command to run as user `phablet` (required to run apps in an initialized session):
 {{{
su - phablet}}}

NOTE: you will not be able to run `ps` or view processes by accessing the device in this manner; please [[#SshAccess|use SSH]] if you are intending to monitor processes.

=== Applications ===

The Developer Preview comes with the following functional applications:

 * Gallery
 * Phone (Dialer, SMS, Address Book)
 * Camera
 * Browser
 * Media Player
 * Notepad.

Other non-functional sample applications are included for demonstration purposes only: Weather, Music Player, Calculator and Ski Safari

=== Installing new apps ===

See the [[#SdkAlpha|SDK documentation]] for information on how to install apps on the device with Qt Creator.

=== Sample content ===

Sample content is preinstalled in the images. If desired it can be removed. [[#SshAccess|Access the device via SSH]] as user `phablet` and perform the following:

 * To remove sample contacts:
  * Run `manage-address-books.py delete`
  * Edit `/etc/[phone|tablet]-services` and remove `manage-address-books.py`
 * To remove sample video and music lenses:
  * Run `rm /usr/share/dbus-1/services/com.canonical.Unity.Lens.MockMusic.service`
  * Run `rm /usr/share/dbus-1/services/com.canonical.Unity.Lens.MockVideos.service`
 * To remove pictures from gallery:
  * Run `rm /home/phablet/Pictures/*`
 * To remove sample messages in messaging menu:
  * Edit `/etc/[phone|tablet]-services` and remove `chewie_messaging_populate_menu`


=== Adding Content ===

==== Contacts ====

Contacts can be added in the address book of the Phone application.
Launch the Phone application and swipe to the “Contacts” tab. You can manually enter your contacts from there.

Alternatively you can import contacts from a csv file. The csv file should be in same format as `/usr/share/demo-assets/contacts-data/data.csv`. Replace the sample `data.csv` file with your own version and run `manage-address-books.py create` to import your contacts.

You can also import your Google Contacts: http://sergiusens.github.io/posts/google-contacts-on-ubuntu-touch.html

==== Photos ====

Photos can be added to the device and viewed in the Gallery application. They can be copied into `/home/phablet/Pictures` folder and they will be displayed in the Gallery. Also, pictures can be taken with the Camera application and they will automatically appear in the Gallery.


==== Videos ====

Videos can be copied onto the device into the `/home/phablet/Videos` folder and viewed with the Media Player application. They can be surfaced in the video lens by modifying the `/usr/share/unity/lenses/mockvideos/mockvideos.json` file to point at your installed videos (this process will be automatic in the future).

Alternatively, you can run the Media Player from the shell by running the following command:
 {{{
media-player <full_path_to_video_file> --desktop_file_hint=/usr/share/applications/media-player.desktop
}}}


=== Upgrades ===

Some parts of the image can’t currently be upgraded, so it is best to [[Touch/Install|deploy a full updated image]]. Some individual apps can be updated with `apt`, though. First add the phablet-team ppa (https://launchpad.net/~phablet-team/+archive/ppa) to /etc/apt/sources.list. Then run the following command with root permissions to update apps:
 {{{
# apt-get update && apt-get upgrade
}}}


== Porting to other devices ==

If you are interested in getting the Touch Preview working on a new device, please see [[../Porting|our porting guide]].


== Known Issues ==

<<Anchor(PowerConsumption)>>
=== Power Consumption ===

Currently the devices can not be shutdown from within the UI or by pressing the power button. Even if you use the power button long press your battery will be drained.

To shutdown a device completely there are two options:
 1. Remove the battery and replace it. (Not an option if battery is not removable)
 1. Stop it from the adb shell by executing the following commands:
 {{{
  adb root
  adb shell reboot -p
}}}

'''Edit:''' This is now fixed with newer images.

=== Memory Usage ===

Memory usage has not yet been optimized for the devices. It is possible to experience application crashes due to having too many applications open at the same time. A workaround is to close apps that are not being used.


=== Timezone ===

The timezone needs to be manually set from the command line. Valid values for timezones can be found in the `/usr/share/zoneinfo/zone.tab` file. Run the following commands ( specifying your own time zone choice ) with root permission to set your timezone:

 1. [[#SshAccess|Access your device through SSH]]
 1. Then on the terminal connected to your device run:
 {{{
echo "America/New_York" | sudo tee /etc/timezone
sudo dpkg-reconfigure --frontend noninteractive tzdata
}}}

=== Language and keyboard ===

A Settings UI for selecting the language and keyboard/input method is currently in the works. In the meantime, the settings can be changed from the command line.

==== Keyboard ====
These instructions require you to be using a saucy version of Ubuntu Touch. If you are on raring, please upgrade to the latest Ubuntu Touch for saucy with `phablet-flash`.

 1. [[#SshAccess|Access your device through SSH]] or start the Terminal app on your device
 1. {{{mkdir /home/phablet/.config/maliit.org && cp /etc/xdg/maliit.org/server.conf /home/phablet/.config/maliit.org/server.conf}}}
 1. {{{vi /home/phablet/.config/maliit.org/server.conf}}} and change two things in the server.conf file. In this example we'll be changing the keyboard layout to German.
  1. Change '''{{{onscreen\active}}}''' to point at your desired keyboard language (e.g. change {{{en_us}}} to {{{de}}} for German). Note, not all langs are supported. Do {{{dpkg -L maliit-keyboard-data | grep languages}}} to see which languages have corresponding .xml files.
  1. Change '''{{{onscreen\enabled}}}''' and add an entry for your desired language such that it gets enabled. For example add a {{{libmaliit-keyboard-plugin.so:de}}} if you want to enable German. The resultant file should look like this: {{{
[maliit]
onscreen\active=libmaliit-keyboard-plugin.so:de

pluginsettings\libmaliit-keyboard-plugin.so\current_style = ubuntu
pluginsettings\libmaliit-keyboard-plugin.so\word_engine_enabled = false

onscreen\enabled=libmaliit-keyboard-plugin.so:en_gb, \
libmaliit-keyboard-plugin.so:en_us, \
libmaliit-keyboard-plugin.so:de, \
libmaliit-keyboard-plugin.so:es, \
libmaliit-keyboard-plugin.so:zh_cn_cangjie, \
libmaliit-keyboard-plugin.so:zh_cn_pinyin, \
libmaliit-keyboard-plugin.so:zh_cn_zhuyin,
}}}
 1. Restart the phone

==== Language ====

To set your system language to display localized strings (where available) in applications, do the following. In the example we'll be changing the language to Simplified Chinese (language code {{{zh_CN}}}). For any other language, replace the {{{zh_CN}}} by your language's ISO 639 code. E.g. {{{ca}}} for Catalan, {{{pt_BR}}} for Brazilian Portuguese, etc.

 1. [[#SshAccess|Access your device through SSH]] or start the Terminal app on your device
 1. Then on the terminal connected to your device run:
 {{{
sudo apt-get install fonts-droid # Required only if your language requires additional fonts
sudo locale-gen zh_CN
sudo vi /etc/default/locale # Then change LANG="en_US.UTF-8" to LANG="zh_CN.UTF-8"
sudo vi /etc/environment # Then change LANG="zh_CN.UTF-8" and LANGUAGE="zh_CN"
reboot
}}}

=== Networking ===

The Developer Preview has support for Wi-Fi networking via the new network indicator, which supports basic Wi-Fi connections (Open, WEP and WPA Personal). It is possible to configure more advanced settings, however at this time this requires working directly with Network Manager system connection files.

The following network features are not yet included in the Developer Preview:

 * Airplane Mode/Wi-Fi Power Control
 * Advanced Settings (e.g. Hidden SSIDs, Manual IP, VPN…)
 * Bluetooth
 * Hot Spot/Tethering


=== Telephony ===

The Developer Preview currently only supports '''limited voice and SMS over GSM and WCDMA'''.

The following Radio technologies are not yet included in the Developer Preview:
 * CDMA
 * LTE
 * Airplane Mode
 * Settings ( eg. APN choice, 2G only, … )

'''Mobile data is generally not supported, data is available via Wi-Fi only.''' However, for instructions on how to enable 3G on devices, please see the following [[https://plus.google.com/100264483712374857174/posts/3o1tjYo9Ghx|G+ post]] by Ricardo Salveti.

These Call features are not yet supported:
 * Emergency Call Support ( ie. ability to dial emergency numbers without a valid SIM card ).
 * PIN/PUK support for locked SIMs
 * No SIM filesystem support
 * Speakerphone

These SMS features are not yet implemented:
 * MMS
 * Send error handling
 * Delivery Reports


== Device Specific Issues ==

=== Galaxy Nexus ===

 * The 802.11a protocol (i.e. 5GHz) is currently not working.

=== Nexus 4 ===

 * In rare circumstances, '''the Nexus4 may get into a state where it may not boot at all after the battery is drained''' (even into recovery). If this happens, the only way to restore it is to disassemble the back of the phone and unplug/plug the battery connector. See [[#PowerConsumption|Power Consumption]] to learn how to avoid discharging the phone completely.

=== Nexus 10 ===

 * Taking pictures with the camera application causes an issue with audio. The volume indicator and volume keys will not work to control the sound until reboot.
 * People lens sometimes comes up empty after first flashing the device and booting. Rebooting fixes the issue.

=== Nexus 7 ===

 * Runs in portrait mode by default (no side stage)
 * Camera, video decoding and audio output do not function.
 * No multi-user login.

=== Devices with 1080 screens ===

Set the GRID_UNIT_PX environment variable to an appropriate value for the device (i.e. 30 for a 5” handset screen) in the `/usr/bin/ubuntu-session` script and in the `/home/phablet/.bashrc` file.

<<Anchor(SdkAlpha)>>
== Ubuntu SDK Alpha ==

You can now install and execute applications on your device from a computer running Qt Creator:

 1. '''Plug in''' your mobile device running Ubuntu on the '''USB''' port of your computer
 1. Make sure your device is also '''connected to a wireless network''' (SSH key pairing happens over the air)
 1. Start Qt Creator from the Dash, and select the new '''Devices''' tab
 1. Press the '''Enable''' button to activate '''Developer Mode'''
 1. Develop your QML projects as usual (best way is to use one of the '''Ubuntu application templates''' in the File > New File or Project... menu entry). They will ensure that there is an {{{ApplicationName.desktop}}} file (where {{{ApplicationName}}} is the name of your application) with content similar to the following one: {{{
[Desktop Entry]
Encoding=UTF-8
Type=Application
Terminal=false
Exec=/usr/bin/qmlscene
Name=ApplicationName
GenericName=ApplicationName
Comment=My project description
Icon=ubuntu-qmlrunner
}}}
 1. Once the device is connected, you can press '''Ctrl+F12''' to install and execute your app on the remote device

Alternatively, you can manually install Qt5/QML-based apps and run them on the device.

  1. Use `adb push` to copy your package or files to the device
  1. [[#SshAccess|SSH into your device]] as user `phablet`
  1. To run, use
{{{
qmlscene --desktop_file_hint=/usr/share/applications/qmlscene.desktop YourApp.qml
}}}

Applications will be launched minimized by default. Go to the '''Apps lens''' and select your app from the list of '''Running Applications''' to bring it to the foreground

=== Known Issues ===
 * Applications launched on the device from Qt Creator start up in a non-focused mode. Remotely-executed apps are in thumbview mode in the Running Apps section on the Apps lens
 * The remotely-executed apps can not be focused by tapping on the thumbview, they need to be focused with a right-edge swipe
 * Documentation for the remote deployment feature is not yet available
 *Qt Creator does not use the system fonts
 * The welcome screen needs some visual improvements coming up soon
[[Touch/ReleaseNotes/OTA-15|OTA-15 (security update)]]

Warning /!\ Ubuntu Touch is no longer maintained as a core product by Canonical. However, the Ubports community are continuing development.


Contents

  1. Releases

Releases

The release notes from earlier ETA's and preview releases weren't wikified, however you can see the changelogs.

Changelogs

OTA-5

OTA-6

OTA-7

OTA-8

OTA-8.5 (hotfix)

OTA-9

OTA-9.1 (hotfix)

OTA-10

OTA-10.1 (security hotfix)

OTA-11

OTA-12

OTA-13

OTA-14

OTA-15 (security update)

Touch/ReleaseNotes (last edited 2017-02-07 11:25:28 by sil2100)