ubuntu-phone team mailing list archive
Mailing list archive
Re: Xenial (16.04) Status on Touch
On Mon, Nov 21, 2016 at 9:09 AM, Lukasz Zemczak <
> As mentioned by YC already, the most effort right now was to get
> xenial arm64 working on frieza (M10). There was basically no work done
> on the mako or any other platforms so far so it's rather 'expected'
> that staging doesn't work on this platform. Devel-proposed was
> yakkety/zesty based and got developer attention. Devel is very old -
> it was a manual promotion channel from devel-proposed.
Anyway, the consensus: we have no idea of the mako state with xenial,
> I wouldn't really count on it being usable anytime soon (it's a really
> really old device). I did try krillin a few weeks before and it was
> booting, at least, but best bet is to just use frieza.
So given that my only ubuntu capable device is mako (I'm waiting for a new
ubuntu capable phone release), my current options are:
1. use devel img 8 from 2016-02.
2. Use rc-proposed with the latest working img
Then is there any reasonable way of pushing a newer version of qt in any of
them? I actually only need to be able to import QtLocation 5.5 from the
qml part of my app, to be able to use the here maps plugin.
I found that there is a "Canonical Qt5 Edgers team" with a ppa apparently
used for Qt5 testing purposes... could it be a possible way to explore?
Thanks a lot for the help!
> On 21 November 2016 at 12:42, Dave Morley <davmor2@xxxxxxxxxxxxx> wrote:
> > On Mon, 21 Nov 2016 08:36:40 -0300
> > Felipe De La Puente <fdelapuente@xxxxxxxxx> wrote:
> >> Hi Yc,
> >> Thanks for the feedback, good to know what was the purpose of the
> >> staging channel.
> >> I did some experiments yesterday:
> >> 1. Tried ubuntu-touch/staging/ubuntu: It doesn't boot.
> >> 2. Tried ubuntu-touch/devel: It doesboot, is xenial but the latest
> >> image is from 2016-02. Tried to install my app using the 15.04
> >> framework and it fails due to invalid apparmor (probably infebruary
> >> this framework didn't exist, and the 14.10 framework uses apparmor
> >> 1.2, while now its 1.3). Didnt try that yet.
> >> 3. Tried the latest img of devel-proposed: As expected, doesnt boot
> >> and is probably based on the current devel ubuntu zitsy?
> >> 4. Tried the oldest img of devel-proposed: Probably based on yaketty
> >> and doesnt boot.
> >> 5. Tried rc-proposed, does boot, looks nice but qt version is the
> >> same as stable, so my app doesnt work.
> >> Should I expect the apparmor trick to work on (2)?
> >> Is there a recommended way to push a newer version of qt to
> >> rc-proposed?
> >> Is there a way to update devel? (On (2) I tried writable fs, apt
> >> dist-upgrade, but then it doesnt boot).
> >> Thanks!