[08:43] <zzarr> hello!
[08:44] <zzarr> will Meizu MX4 move to 16.04 in the future?
=== jamesh_ is now known as jamesh
[10:02] <mardy> morphis: hi! I was checking oxide code; is it fine if hybris_camera_initialize() is called more than once?
[10:02] <morphis> mardy: it shouldn't hurt
[10:03] <mardy> morphis: ok, thanks
[10:04] <morphis> mardy: have some improvement in the pipe I will push somewhere soon
[10:04] <morphis> mardy: I guess you only need this in xenial, right?
[10:04] <mardy> morphis: excellent!
[10:05] <mardy> morphis: well, I'd say xenial and later releases
[10:05] <morphis> ok
[10:47] <zzarr> will xenial come to current phones?
[10:47] <zzarr> (like my MX4?)
[11:02] <davmor2> zzarr: I don't think the kernel supports the newer features of xenial which is what prevented the move much earlier iirc
=== _salem is now known as salem_
[12:26] <brunch875> that's it, I'm getting a fairphone next
[12:39] <zzarr> davmor2, it's the android drivers that are built for and older kernel?
[12:39] <zzarr> (which prevents using a newer kernel?)
[12:41] <davmor2> zzarr: not sure on the why's just know there was a reason that prevented it already and from memory was to do with the android stack and kernels
[12:43] <zzarr> okey, what would be needed i order to run a newer kernel? (new drivers?)
[12:48] <davmor2> yeap so the chip manufacturer, then the android kernel, then the board manufacturer and then the phone manufacturer and then filter all that down to us
[12:51] <zzarr> does not sound promising, what will happen when there's a phone with a newer kernel/xenial with the phone I have?
[12:52] <zzarr> will all work be discontinued?
[12:53] <zzarr> or is there a plan to let kernel 4.4 piggyback on 3.10 or 3.14 (or something like that?)
[12:54] <zzarr> I'm thinking something like a vm
[13:39] <camako> oSoMoN, hi I'm trying to test unity8 on the desktop with the new Mir. My webbrowser-app doesn't seem to be working. Is there any setup required?
[13:52] <davmor2> camako: known issues are it doesn't like nvidia gfx and snapcraft lastest shortened the link for running the app meaning it doesn't start because the app doesn't exist fixes for the last is in progress the first is still being looked at I believe
[14:00] <zzarr> davmor2, if this side is http://forum.flymeos.com/thread-7697-1-1.html correct that the MX4 supports Android 7 which according to this site http://android.stackexchange.com/questions/51651/which-android-runs-which-linux-kernel runs kernel 4.4.1 it should be possible to run xenial on the MX4
[14:00] <zzarr> but I don't know if it's correct
[14:02] <davmor2> zzarr: on arm64?
[14:02] <dobey> zzarr: note that a lot of devices have newer android system, but still use old kernels too
[14:02] <dobey> davmor2: arm64 isn't a requirement for making xenial/snaps work.
[14:03] <dobey> and arale isn't arm64 anyway
[14:05] <zzarr> nope, the MX4 have a 32bit SoC
[14:44] <oSoMoN> camako, is this with the unity8 snap, or with unity8 installed from deb?
[14:45] <camako> oSoMoN, unity8 installed from a deb
[14:46] <camako> It still complains about EGL/GL
[14:46] <oSoMoN> camako, does this look like bug #1590561 ?
[14:46] <ubot5> bug 1590561 in Oxide "webbrowser-app crashes on startup on fresh zesty Unity8: No suitable EGL configs found" [Critical,Confirmed] https://launchpad.net/bugs/1590561
[14:46] <camako> oSoMon, indeed it does
[14:47] <camako> sorry can't look in the bug... on the U8 side atm with no browser :-)
[14:47] <oSoMoN> heh
[14:47]  * camako switches back to U7
=== petevg is now known as petevg_noms
=== petevg_noms is now known as petevg
=== boiko__ is now known as boiko