[00:00] <d^_^b_> hello
[00:01] <d^_^b_> someone can help me to install ubuntu-touch in samsung galaxy tab 2 7" (p3100)? thanks
[00:08] <dobey> ghosalmartin: we don't have builds on top of 5 yet even.
[00:08] <dobey> !devices | d^_^b_
[00:09] <ghosalmartin> i assume you guys use libhybris?
[00:15] <k1l_> ghosalmartin: iirc yes
[00:16] <ghosalmartin> k1l_ how do you guys inject it into the android build?
[00:20] <k1l_> ghosalmartin: see this for a start: https://wiki.ubuntu.com/Touch/ContainerArchitecture
[00:21] <k1l_> or this is somewhat more detailed http://elinux.org/images/c/cf/Ubuntu_Touch_Internals_1.pdf
[00:26] <ghosalmartin> ah I see
[00:32] <d^_^b_> thank you dobey
[00:32] <d^_^b_> i've found this one but the links doesn't works
[00:40]  * JanC wonders why ubuntu-sdk-ide _requires_ SQLite, Postgres, MySQL, ODBC *and* Sybase/MSSQL database drivers...
[05:23] <mac_> Hello guys
[05:24] <mac_> Currently working on poritng ubuntu touch device on my hd2... Our device doesnt have standard recovery and installs everything on partition sdcard instead of nand
[05:25] <mac_> I have already built a system.img using phablet_4.4.2 for my device and also patched the kernel.
[05:27] <mac_> I want to know how can I flash the preinstall-tar.gz (vivid or xenial) and the system.img , if adb on my recovery is not working
[06:25] <Querty> Testing
[07:29] <dholbach> good morning
[10:17] <JamesTait> Good morning all; happy Monday, and happy Fibonacci Day! 😃
[10:19] <jgdx> seb128, re: bug 1518732, what's wrong? I assume I misused i18n.tr
[10:20] <seb128> jgdx, the template parser doesn't like single quote for some reason
[10:20] <seb128> '...' -> not good
[10:20] <seb128> "..." -> good
[10:20] <seb128> and you put those strings in single quote
[10:20] <jgdx> oh man, okay
[10:20] <jgdx> seb128, thanks
[10:20]  * jgdx creates a precommit check for that
[10:22] <seb128> jgdx, yw
[10:22] <seb128> we should look if that can be fixed, or caught by CI
[10:43] <jgdx> seb128, I found some tr errors in ApnEditor as well, using the script. Do you want a branch or will you fix them as well?
[10:44] <seb128> jgdx, well I didn't look at those yet, I was going to grep for "i18n.tr('" and fix everything list
[10:44] <seb128> but if you are already on it feel free to do the change and mp it
[10:45] <jgdx> seb128, okay, I can do it.
[10:46] <seb128> thanks
[11:09] <ahayzen> Hi, does anyone else get a rather large stutter in the UI, on mako, when an application is suspend/closed ?
[11:15] <davmor2> I take the overwhelming silence to mean no ;)
[11:17] <ahayzen> :(
[11:18] <jgdx> ahayzen, I have a mako on ota8. How do I repro that?
[11:19] <ahayzen> jgdx, open multiple apps, say the browser and music... switch from browser to music and scroll up/down the list ~2second after switching when the app is suspended you see a stutter
[11:19] <ahayzen> or a similar thing when an application is closed
[11:21] <ahayzen> or even just scrolling up/down the scopes
[11:22] <jgdx> ahayzen, I see it. Could you file that? Maybe against the canonical-devices-system-image proj
[11:23] <ahayzen> jgdx, yup :-) and maybe qtmir? i'm not sure what actual project to blame
[11:23] <jgdx> me neither
[11:23] <ahayzen> do you have a bq/mx4 to try on asw ell?
[11:23] <ahayzen> *as well
[11:27] <ahayzen> jgdx, i've reported bug 1518935, i'm going at ask in the mir channel if they think it could be in that part of the platform
[11:29] <jgdx> ahayzen, thanks
[11:39] <Mirv> attente: hey! the new maliit-framework looks great otherwise but it seems you missed the ubuntu12 upload of the old version - could you restore the patch 0015 required for Qt 5.5? http://launchpadlibrarian.net/220408536/maliit-framework_0.99.0%2Bgit20130923%2B17fdf86-0ubuntu11~gcc5.1_0.99.0%2Bgit20130923%2B17fdf86-0ubuntu12.diff.gz
[11:40] <Mirv> attente: (I saw the changelog entry for ubuntu12 being removed from the new upload)
[11:44] <om26er_> jgdx, Hi!
[11:44] <jgdx> om26er_, yo
[11:45] <om26er_> jgdx, is there an ofono script to change active data connection SIM on a dual sim device ?
[11:46] <om26er_> jgdx, in my test, I want to switch data connection from SIM2 to SIM1 for example
[11:46] <jgdx> om26er_, yeah, the script I gave you, but you have to supply the script the paths
[11:46] <jgdx> so disable-gprs /ril_0 && enable-gprs /ril_1
[11:47] <jgdx> paths you can get from dbus or the other ofono scripts (list-modems)
[11:48] <om26er_> jgdx, thanks, that should do it
[12:10] <Mirv> attente: ignore the earlier, I looked at the new code the wrong way, it seems the patch is yet another that can be dropped (but the changelog entry was indeed accidentally removed)
[12:23] <davmor2> mpt: Hey dude I have a designy issue. Settings→Sound there is  a slider that is under the title Ringer but that is just a volume control and not specific to the ringer right?
[12:26] <mpt> davmor2, that’s bug 1396986. The slider label should change to reflect what it is currently changing the volume of, but that should be output devices, not roles.
[12:26] <davmor2> mpt: ah nice thanks
[12:27] <davmor2> mpt: also any movement on changing about phone to something other than phone when it isn't on a phone
[12:27] <mpt> no
[13:43] <attente> Mirv: ah, ok, thanks. i'll do it now
[13:45] <attente> Mirv: is there a better packaging branch that is synched with what's most recent in archive?
[13:56] <attente> dholbach: hey, Mirv pointed out that i missed this changelog entry: https://launchpadlibrarian.net/220408536/maliit-framework_0.99.0+git20130923+17fdf86-0ubuntu11~gcc5.1_0.99.0+git20130923+17fdf86-0ubuntu12.diff.gz. is it still possible for me to fix it?
[14:02] <dholbach> attente, I uploaded it already -- it could be retractively added with the next upload?
[14:03] <crypted> The changelog link does not seem to give alot of info. Do any of you guys know when native VOIP features will be introduced to Ubuntu-Phone OS?
[14:07] <attente> dholbach: should we do another upload now to fix it? or should we wait to the next release? i'm not sure what the process is here, and i'm not sure any more if there's a bzr branch that is up-to-date with archive. i'm also not sure if anyone will remember to do it when the next release is ready...
[14:09] <dholbach> attente, Mirv: I'm not sure I understand... is the branch which I uploaded from not up to date with archive?
[14:09] <attente> dholbach: apparently that branch was missing a changelog entry from wily
[14:10] <attente> so it seems not...
[14:10] <attente> it was also missing a patch, but that was already merged upstream so wasn't needed any more
[14:14] <attente> dholbach: i guess i'll just update that branch anyways since it seems most up-to-date, and we can just merge, but not upload it so we don't forget
[14:19] <dholbach> ok, cool
[14:22] <Mirv> attente: possibly there's no up-to-date packaging branch or something.
[14:22] <Mirv> dholbach: ^
[14:23] <Mirv> attente: dholbach: anyway, the patch was already in upstream so basically just changelog entry deleted
[14:23] <attente> Mirv: ok, so the problem is worse than just the one changelog entry. i missed a bunch of changes comparing it to what's in wily
[14:24] <attente> Mirv: the debdiff is pretty big, i'm not sure if most of these changes were integrated upstream though
[14:25] <attente> i guess i have to comb through the entire thing to get the branch up-to-date
[14:33] <ncls> hi all, I need to install Android on my Ubuntu Phone (was a good experience, but I need Android for dev purpose) two questions : is it possible from Mac OSX ? at which moment should we press the "download" button like on this tutorial ? http://a25.co/ubuntu-phone-how-to-install-android/
[14:33] <ncls> I tried to do it from a VM on my Mac but it didn't seem to work
[14:35] <dobey> ncls: you should contact bq support for help with that i guess. the mediatek tool is only available for windows or linux though i think.
[14:35] <ncls> dobey: ok I will, thank you
[14:35] <ncls> just wanted to know if it was possible without this tool
[14:36] <ncls> but they might know that too
[14:36] <dobey> no, the tool is required for mediatek based phones
[14:42] <ncls> ok thank you dobey
[14:45] <Mirv> attente: ah, ok, well good to check then the others
[14:50] <Saviq> morphis, hey, I found an issue with BT transmitting the network name to my car kit - I've two sims in the BQ phone (one a left over from a trip), and one of them is offline due to lack of roaming and the car says "No network", even though my main card is fine, not really sure how to solve this as I imagine the profiles used don't understand multi SIM
[14:50] <Saviq> but I'd like to file a bug for future's sake
[14:55] <morphis> Saviq: thas is kown and will be fixed soon
[14:55] <morphis> basically ofono picks the first modem it finds currently
[14:56] <morphis> Saviq: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1418040
[14:57] <Saviq> morphis, ah good, thanks :)
[14:57] <Saviq> morphis, what if there's no default modem? :D
[14:57] <morphis> Saviq: there will be one
[14:57] <morphis> that is what we're currently changing
[14:58] <Saviq> morphis, I mean that the user might've selected "ask me every time"
[14:58] <Saviq> oh, and also, I didn't get a call history entry I think when I used the car kit to dial
[14:59] <morphis> Saviq: also known: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1479442
[15:00] <morphis> Saviq: ask me every time is currently not considered but would be a pure UI decision
[15:00] <Saviq> morphis, no no, I meant that the *phone* app didn't show a call I placed with the car kit
[15:00] <morphis> Saviq: ah
[15:00] <morphis> interesting, can you file a bug for that?
[15:00] <Saviq> will do
[15:01] <Saviq> unfortunately my car kit is old enough that I never found a phone that could share any meaningful data with it
[15:02] <morphis> Saviq: and can you include a syslog with debug information?
[15:02] <morphis> Saviq: https://wiki.ubuntu.com/DebuggingBluetooth
[15:03] <morphis> that would be pretty great
[15:03] <Saviq> morphis, will try and repro and file if I do
[15:04] <Elleo>  o
[15:04] <Elleo> oops
[15:10] <morphis> Saviq: can you file one for the netreg thing too?
[15:20] <Saviq> morphis, netreg? you mean "no network" in the car kit?
[15:21] <slvn_> Hello, some question .. on Ubuntu Touch, qtbase is compiled with which "platform" directory ?
[15:22] <pmcgowan> Mirv, ^
[15:24] <dobey> slvn_: there is no ubuntu touch, there is only ubuntu
[15:25] <dobey> the qt5 on the phone isn't a "special build." it is the standard ubuntu qt5 build with the same build options as everywhere
[15:26] <slvn_> dobey,  I mean on ubuntu for phones/tablet.
[15:26] <slvn_> maybe my question is not well asked .. I explain
[15:26] <dobey> slvn_: i mean, ubuntu is ubuntu
[15:27] <slvn_> my app is based on mir, and, even in fullscreen, it displays the status bar
[15:27] <dobey> i don't know what the "platform" directory you're referring to is specifically, but there isn't a special build of qt5 for phones. it is the standard qt5 build for armhf that's in ubuntu
[15:27] <slvn_> but, camera-app, for instance does not display the status bar
[15:27] <dobey> you mean the top panel of unity8?
[15:28] <slvn_> maybe ... not sure of the name .. the top bar
[15:28] <dobey> the one with the radio/battery/sound indicators?
[15:28] <slvn_> yes
[15:29] <dobey> how are you doing full screen in your app?
[15:29] <dobey> your app shouldn't be using mir directly, btw
[15:29] <slvn_> yes, but this is a C++ app, calling mir function
[15:30] <slvn_> using sdl2, which calls mir ..
[15:30] <dobey> well sdl2 has a mir backend, but you are not calling mir directly in your app are you?
[15:30] <slvn_> no
[15:30] <dobey> ok
[15:30] <slvn_> but I double check the mir stuff to make stuff the correct calls were done
[15:31] <tvoss> slvn_, you want to check with bschaefer for requesting full screen
[15:31] <tvoss> slvn_, he did the sdl2-mir backend mostly
[15:31] <dobey> yeah
[15:31] <slvn_> tvoss, i know i will ask him later
[15:32] <slvn_> but I am looking at the camera-app
[15:32] <slvn_> to understand how it goes fullscreen
[15:33] <slvn_> it seem to call qml/qt stuff and, if i am correct, the corresponding packages are : qtdeclarative-opensource-src and qtbase-opensource-src
[15:34] <tvoss> slvn_, that's very unlikely, as qt would only call mir, too
[15:34] <tvoss> slvn_, for the respective qt-mir interaction: lp:qtmir
[15:35] <slvn_> tvoss, ok so I look the wrong package, thanks !
[15:37] <tvoss> slvn_, yw
[15:42] <Mirv> slvn_: all platform plugins are available, you can see them with eg qmlscene -platform test. on the phone, mirserver and libubuntuclient are installed (from qtmir/qtubuntu) in addition to the normal qtbase upstream ones (which include eglfs, kms, linuxfb, miminalegl etc)
[15:44] <mcphail> slvn_: SDL apps can go fullscreen too
[15:48] <slvn_> Mirv,  not sure I expressed correctly. I end up on qtbase-opensource-src/src/plugins/platforms/ and there was many platforms (android, coca, direct2d, winrt, etc..) not sure there are all need on a ubuntu device. but it seems I was looking at the wrong place. and I am currently looking into lp:qtmir
[15:49] <slvn_> mcphail,  hi, I know but it does not go to full-screen. there is still the top status bar !
[15:49] <mcphail> slvn_: you can get proper fullscreen
[15:49] <mcphail> slvn_: (I just can't remember how at this second)
[15:50] <mcphail> I think apps which use SDL2's virtual resolution approach get true fullscreen
[15:51] <mcphail> IIRC, Neverball/neverputt get fullscreen. You could have a look at their code
[15:53] <Mirv> slvn_: right, that's the place. upstream Qt 5.6 now has mirclient plugin there too, and mirserver is in a branch, but in our Qt 5.4 production code the plugins come from lp:qtmir and lp:qtubuntu
[15:54] <mcphail> slvn_: good work on your games, btw. Have you uploaded any to the store?
[15:54] <Mirv> slvn_: lp:qtubuntu is the libmirclient one which probably apps would use
[15:54] <slvn_> mcphail,  currently, I have no phone ... but that would be great if you could check Neverball app to see if there is the statusbar ..
[15:55] <mcphail> slvn_: I'll check when I get home and on to wifi
[15:57] <slvn_> Mirv,  yes lp:qtubuntu is more interesting ! it does the translation Qt:WindowFullScreen to mir_surface_state_fullscreen
[15:58] <dobey> https://uappexplorer.com/app/neverball.lb
[15:58] <dobey> screenshot there doesn't show the unity8 panel
[15:59] <popey> slvn_, neverball and neverputt are proper full screen
[15:59] <swex> hi there
[16:00] <swex> googling for a while and can't get answer: how to instlal ubuntu-touch on x86 tablet?
[16:01] <slvn_> popey, dobey ... you tried it on a ubuntu phone ?
[16:01] <popey> yes
[16:01] <slvn_> do you where i can see the code ?
[16:02] <popey> https://github.com/pseuudonym404/neverball-touch
[16:02] <mcphail> slvn_: I _think_ you get true fullscreen if you use SDL_WINDOW_FULLSCREEN_DESKTOP
[16:03] <mcphail> slvn_: that's the kind of virtual-resolution fullscreen which came in with SDL2
[16:04]  * mcphail needs to check if this still holds true since we got platform-level orientation
[16:04] <dobey> !devices | swex
[16:05] <swex> dobey: nothing related to x86 found :(
[16:05] <dobey> swex: right, so you'd need to port to your device
[16:06] <swex> dobey: ok,but what is that? http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/
[16:06] <dobey> swex: if it's a windows tablet, it's probably going to be more difficult to port, at least.
[16:07] <dobey> the daily-preinstalled tarball is the base image the device-specific images are built from
[16:07] <slvn_> mcphail,  you might be right ... I use SDL_WINDOW_FULLSCREEN, whereas neverball-touch use SDL_WINDOW_FULLSCREEN_DESKTOP ..
[16:08] <pixel_> slvn_, you are using SDL2 right?
[16:08] <slvn_> but that would be really weird that the method named setFullScreen is not called with SDL_WINDOW_FULLSCREEN
[16:08] <slvn_> pixel_, yes
[16:09] <pixel_> slvn_, how do you load images?
[16:10] <slvn_> pixel_,  with SDL2_image ... but this is more a sdl question ...
[16:11] <pixel_> slvn_, if so the the sdl2 extensions are also available SDL_image, SDL_ttf, and SDL_mixer etc
[16:11] <pixel_> slvn_, yeah.. i was just curious :D
[16:11] <mcphail> slvn_: SDL_WINDOW_FULLSCREEN_DESKTOP is much nicer anyway
[16:11] <pixel_> not related to the fullscreen question
[16:12] <slvn_> pixel_,  yes I cross compile sdl2 image/ttf/mixer !
[16:12] <mcphail> slvn_: although I don't know how well touch events translate with SDL_WINDOW_FULLSCREEN_DESKTOP
[16:13] <pixel_> slvn_, do you know what is available on the phone? do you have to put all the sdl and extension into a click?
[16:13] <pixel_> slvn_, or are already available on the phone
[16:13] <mcphail> pixel_: you need to bundle everything
[16:13] <pixel_> ewww
[16:13] <mcphail> pixel_: it is the future :)
[16:13] <pixel_> yeah :D
[16:14] <slvn_> mcphail,  I am still very sceptical about the SDL_WINDOW_FULLSCREEN_DESKTOP. I mean, if someone want to test, I can rebuilt quickly an app !
[16:14] <mcphail> slvn_: I'm happy to have a look this evening
[16:14] <mcphail> slvn_: remember that you set a virtual resolution in SDL_WINDOW_FULLSCREEN_DESKTOP, though
[16:15] <slvn_> pixel_,  yes all rebundled ...  but whatever is working on android, ios, tvos, winrt, macosx, linux, now work on ubuntu device
[16:16] <pixel_> slvn_, that's nice.. so i just download sdl2 https://www.libsdl.org/download-2.0.php and compile it with mir support?
[16:16] <pixel_> slvn_, what ide are you using? qt creator?
[16:19] <slvn_> pixel_,  .. I cross compiled it, so I set up a partial chroot .. no ide, I have a couple of script to rebuild everything from scratch
[16:19] <slvn_> actually, the script for the partial chroot comes from mir
[16:20] <popey> slvn_, I have a few devices, happy to test
[16:21] <pixel_> slvn_, i see, thanks :P
[16:22] <slvn_> mcphail,  Mirv, I am still sceptical about the  flags with _DESKTOP :) ... though I saw a difference between lp:qtubuntu  and SDL2/mir backend.  lp:qtubuntu is doing a "mir_wait_for(mir_surface_set_set_state(fullscreen))" whereas SDL2 is not doing that ...
[16:25] <tvoss> slvn_, mcphail best to report to bschaefer, I'm not sure where we track bugs for the sdl2 backend
[16:25] <Mirv> greyback_: see possible slvn_:s questions regarding lp:qtubuntu etc, although mainly he's about improving the sdl2 backend apparently and just looking for tips from lp:qtubuntu
[16:26] <mcphail> yes, would be nice if both FULLSCREEN approaches gave true fullscreen
[16:27] <slvn_> tvoss, Mirv  dont worry I let this know to bschafer ..
[16:28] <Mirv> slvn_: oh, ok
[16:29] <bschaefer> yeah i dont do that
[16:30] <bschaefer> but theres no reason i dont ...
[16:30] <slvn_> popey,  told me there is still the status bar with _DESKTOP
[16:30] <slvn_> I will try to patch SDL2/mir with a wait_for like in lp:qtubuntu
[16:31] <bschaefer> i dont think that will solve that issue since it become fullscreen
[16:31] <bschaefer> at some point
[16:31]  * bschaefer didnt read the backlog
[16:32] <greyback_> slvn_: that is the correct way to set the fullscreen flag on a mir surface yes. It should cause the unity8 panel to go away
[16:32] <mcphail> bschaefer: SDL_WINDOW_FULLSCREEN_DESKTOP seems to give proper fullscreen
[16:32] <bschaefer> mcphail, well setting that?
[16:32] <slvn_> mcphail,  no, even with SDL_WINDOW_FULLSCREEN_DESKTOP, there is still the status bar ..
[16:32] <bschaefer> for the touch to remove the toolbar?
[16:33] <bschaefer> IIRC greyback_ told me about setting things to fullscreen and the toolbar when away in my example
[16:33] <bschaefer> but that was like ... 6 or so months ago
[16:33] <mcphail> slvn_: really? Wonder what makes the difference then. All my SDL_WINDOW_FULLSCREEN_DESKTOP test apps went proper fullscreen
[16:33] <slvn_> on my app .. but not on neverball it seems there is not status.   but neverball is not using SDL_Renderer, it use direct call to egl
[16:34] <mcphail> slvn_: have you used SDL_RenderSetLogicalSize?
[16:35] <morphis> Saviq: exactly
[16:38] <pixel_> slvn_, what is this? https://code.launchpad.net/~brandontschaefer/+junk/SDL2-new-mir-ABI
[16:39] <bschaefer> thats the branch to move to the newer mir ABI/API
[16:39] <bschaefer> (moving to 0.15 and greater)
[16:39] <bschaefer> pixel_, cant sync those changes with upstream SDL2 until ubuntu LTS
[16:39] <bschaefer> (since thats what SDL2 aims for) with out a very ugly patch :)
[16:41] <pixel_> bschaefer, oh i see :D thanks
[16:42] <mcphail> slvn_: This is the code I use to bring up SDL in a little pong game which show up as true fullscreen - http://paste.ubuntu.com/13477772/
[16:42] <bschaefer> np!
[16:44] <slvn_> mcphail,  I dont use Render Logical .. but I could ... but that should not make any difference
[16:45] <mcphail> slvn_: that's what SDL_WINDOW_FULLSCREEN_DESKTOP expects
[16:46] <mcphail> slvn_: you let SDL fill the desktop and give you a logical surface on top
[16:46] <mcphail> slvn_: with letterboxing as needed
[16:50]  * mcphail suspects you can coerce SDL_WINDOW_FULLSCREEN to do the same thing if the resolution is set to include the statusbar area
[16:59] <slvn_> mcphail, I have build a game that use logical size, will see if it goes full screen ...
[16:59]  * mcphail crosses fingers
[17:00] <ryao> Where do the Kubuntu mobile guys hang out?
[17:03] <pixel_> Steam provides both SDL 1.2 and 2.0 in this manner, for both x86 and amd64, in addition to several add-on libraries like SDL_mixer. When shipping a Linux game on Steam, do not ship a build of SDL with your game. Link against SDL as normal, and expect it to be available on the player's system. This allows Valve to make fixes and improvements to their SDL and those fixes to flow on to your game.
[17:03]  * pixel_ like steam
[17:05] <mcphail> pixel_: that's why steam breaks with open source drivers
[17:06] <dobey> mcphail: steam works fine on intel
[17:06] <mcphail> dobey: you have to kill steam's libc++ with nouveau and radeon
[17:07] <mcphail> runtimes can be evil
[17:07] <dobey> gcc is evil
[17:07] <dobey> i presume you're talking about on 15.04 or 15.10?
[17:08] <mcphail> I've had problems on 15.04 and 15.10. Not sure if I used open source drivers on 14.04
[17:08] <dobey> steam doesn't support those releases
[17:08] <mcphail> yep
[17:08] <dobey> well, 15.10 has gcc5, which is a problem, and 15.04 has gcc 4.9, which is binary incompat with 4.8, which 14.04 has
[17:08] <dobey> and steam only officially supports LTS
[17:09] <dobey> i just stay with LTS for my production host OS, and use contains for building on newer releases for development
[17:09] <mcphail> and an unsupported runtime is worse than no runtime at all
[17:10] <dobey> i don't know if steam even officially supports 14.04. they might still only support 12.04 officially
[17:11] <mcphail> I think the games list 14.04 in the requirements, so I assume it is supported. But the open source drivers on 14.04 are poor for gaming, so it is a catch 22
[17:11] <timppa_> hello!
[17:11] <timppa_> I've been struggling lately with Nexus 7 deb
[17:12] <mcphail> deb?
[17:12] <timppa_> mcphail LTE version of Nexus 7
[17:12] <mcphail> aah
[17:13] <mcphail> timppa_: not sure if that is a supported device
[17:13] <dobey> deb is not officially supported
[17:13] <timppa_> there is http://system-image.tasemnice.eu which hosts the deb images as well
[17:13] <dobey> and tassadar is in the wind
[17:14] <timppa_> lately those images stopped working
[17:14] <dobey> and i have no idea how to set up a similar image server
[17:14] <timppa_> I managed to build my own version of the android bits and now the new images work again.
[17:14] <timppa_> I'd like to create an image server but I don't know how
[17:15] <dobey> mcphail: you can try the lts backport kernel/xorg and it might work better. my main issue is getting 4K@60Hz working properly on intel
[17:15] <dobey> i'm happy to host an image server
[17:15] <dobey> and i have infinite bandwidth/storage for it
[17:15] <timppa_> dobey: do you know how to create one?
[17:15] <dobey> i just don't know how to get the scripting set up to do it right
[17:16] <dobey> but i need to figure out how
[17:16] <dobey> because my phone badly needs updates
[17:16] <timppa_> which phone you have?
[17:18] <dobey> nexus 5
[17:18] <timppa_> Btw, anyone happen to know if 16.04 images/rootfs has the new bluez as well?
[17:18] <dobey> afaik it does
[17:18] <timppa_> dobey: so you have the same issue that the new images do not boot anymore?
[17:18] <dobey> but afaik, xenial images are known broken at the moment
[17:19] <dobey> timppa_: no, i don't use devel-proposed because it breaks
[17:19] <dobey> i have an image that mariogrip made and put on his server, but i don't think he's built any more images since
[17:19] <timppa_> ok, I just flashed the latest xenial image and it seems to run but "deb" still has the issue that bluetooth does not work
[17:19] <dobey> and i don't think he cares to maintain builds for other devices
[17:20] <dobey> oh, there is a new image there, yay
[17:20] <dobey> but only has stable channel
[17:21] <timppa_> I have Nexus 4 and the LTE version of Nexus 7, I cannot test N5.. :(
[17:22] <timppa_> So the reason I'd like to create my own image server is to use 15.10 release train and not 16.04.
[17:22] <timppa_> If someone could share the knowlegde :D
[17:23] <mcphail> timppa_: 15.10 isn't in use, afaik
[17:23] <mcphail> timppa_: wily has been skipped
[17:23] <popey> yeah, we're not using 15.10
[17:23] <timppa_> 15.04 then ;D
[17:23] <dobey> timppa_: you shouldn't be using devel-proposed anyway
[17:26] <timppa_> never had that many issues on devel-proposed on any of the devices
[17:27] <cwayne1> has anyone had issues with mx4 on ota8 where the battery indicator is wrong?
[17:27] <slvn_> mcphail,  SetLogicalSize does not improves, there is still the status bar ..
[17:28] <slvn_> mcphail, bschaefer,  somethings strange, MIR_SetFullScreen is always call with fullscreen=0, so it disable fullscreen ... But even forcing fullscreen it is not hiding the status bar
[17:35] <dobey> timppa_: devel-proposed gets basically no QA and is known to possibly break. it's not currently 1:1 with what's in rc-proposed, either, in terms of features.
[17:37] <timppa_> dobey: I know, I've been rather quietly been watching the development of things since UT was announced
[17:38] <timppa_> is there any way to sideload the vivid-preinstalled-touch-armhf.tar.gz on a device?
[17:39] <slvn_> Mirv, tvoss, bschaefer, in fact, ignore my previous remark about "mir_wait_for",  SDL2 use the API mir_surface_set_spec_set,  whereas lp:qtubuntu use the one withou "_spec_" ... so the mir_wait_for was not relevant .. sorry
[17:43] <slvn_> mcphail, bschaefer, I have done many tries of application with popey and we got a solution for the statusbar bug. well it's not a solution, but a way to get it working
[17:43] <bschaefer> nice, i've not gotten the time to look at that issue :(
[17:43] <popey> \o/
[17:44]  * popey is busy playing tic-tac-toe
[17:44]  * popey loves his job
[17:44] <slvn_> the call "MIR_mir_surface_apply_spec(mir_window->surface, spec);"  seem not to perform well
[17:44] <slvn_> but  "MIR_mir_wait_for(MIR_mir_surface_set_state(mir_window->surface,state));"  was working better
[17:45] <slvn_> it's not a fix .. but it points something wrong ...
[17:46] <tty> silly question - can ubuntu 'phone os' be installed on mobiles such as samsung s6 etc?
[17:46] <bschaefer> slvn_, hmm the only issue i can think of is the spec that was created applied to the surface?
[17:46]  * bschaefer thought it was
[17:46] <slvn_> http://paste.ubuntu.com/13478383/
[17:46] <bschaefer> slvn_, also im pretty sure that function is deprecated :(
[17:48] <bschaefer> looks like it is... slvn_ i mean the wait_for isnt needed? If you remove that ... it should still work
[17:48] <bschaefer> with the old function
[17:48] <bschaefer> slvn_, you check the state of the window as well?
[17:48] <bschaefer> after a little bit (after the apply) to see if its fullscreen?
[17:48] <bschaefer> (with the set spec)
[17:49] <tty> oo.. see it's available for nexus devices... is ubuntu touch the same as ubuntu phone...?
[17:50] <mcphail> slvn_: this is brilliant work, getting to the bottom of all of this. If we get this fixed I might even be able to read the text on my version of Baldur's Gate :)
[17:53] <slvn_> bschaefer, I am on the phone, please let me know how to check the validity of surface
[17:54] <bschaefer> slvn_, mir_surface_get_state(surface1) == mir_surface_state_fullscreen
[17:54] <bschaefer> pretty much
[17:55] <bschaefer> but you've to wait for some amount of time (since it has to go through the IPC to the server and actually update the surface that its fullscreen)
[17:55] <bschaefer> before it *should* tell you that it is indeed fullscreen
[17:55] <bschaefer> slvn_, you can just add a print statement in the event loop
[17:55] <bschaefer> so you can press a key to get the current state of the surface
[17:55] <bschaefer> (when a key is pressed or w/e)
[17:57] <mac_> During boot up of ported ubuntu, upon executing "mount -o loop,rw /tmpmnt/system.img ${rootmnt}"
[17:57] <mac_>  I get this in last/kmsg "EXT4-fs (loop0): bad geometry: block count 652288 exceeds size of device (573440 blocks)"
[17:57] <mac_> my partition size is 7GB and system.img is 2.6GB
[17:57] <mac_> What am I doing wrong?
[18:00] <mac_> Also How do I view irc ubuntu-touch logs? to view if anyone answered my question yesterday
[18:02] <ahayzen> mac_, this would be yesterday's log http://irclogs.ubuntu.com/2015/11/22/%23ubuntu-touch.txt
[18:16] <slvn_> bschaefer, I have updated with this code ... http://paste.ubuntu.com/13478688/
[18:17] <bschaefer> slvn_, i ment to check using the set spec way
[18:17] <bschaefer> as if the surface is getting fullscreen
[18:17] <bschaefer> then it would be qtmir
[18:17]  * bschaefer will have to look at it at some point
[18:17] <bschaefer> slvn_, as i've used the set spec for fullscreen before
[18:17] <bschaefer> and im not sure why the tool bar doesnt go away in this case
[18:18] <slvn_> I should remove the "no_spec" also ?
[18:21] <bschaefer> slvn_, o sorry mis read
[18:21] <bschaefer> the issue with that, is it takes some time (milliseconds)
[18:21] <bschaefer> to change, but your log is right after the change
[18:21] <bschaefer> soo it'll be false
[18:21] <bschaefer> but will be true in a few milliseconds
[18:22] <slvn_> ok !
[18:32] <mac_> If someone would kindly explain difference between "bootmode=ubuntu" and "bootmode=android"
[18:32] <mac_> in initrd /script/touch we have "# Our current list of supported boot modes: 	## BOOT_MODE = ubuntu and android"
[18:32] <mac_> any expert can explain?
[18:35] <dobey> mac_: i'm not an expert, but my first guess would be that ubuntu boots into ubuntu, and android boots into only the android container with none of the ubuntu services
[18:41] <slvn_> bschaefer, log+code http://paste.ubuntu.com/13478971/
[18:42] <slvn_> there is the status bar, and it does not report fullscreen
[18:42] <slvn_> btw, there is always the Force to ON .. see the code
[19:00] <Paddy_NI> I want to put Ubuntu Touch back on my bq Aquaris E4.5 and was wondering which channel will get me the latest build?
[19:00] <Paddy_NI> popey: Which build do you use?
[19:00] <popey> depends
[19:00] <popey> i have more than one device :)
[19:01] <Paddy_NI> Ah yes you also have the MX4
[19:01] <Paddy_NI> Lovely
[19:01] <popey> ubuntu-touch/rc-proposed/bq-aquaris.en is what I run on my most used bq phone
[19:01] <popey> which updates ~daily
[19:01] <Paddy_NI> Cool
[19:01] <Paddy_NI> Thanks :-)
[19:01] <popey> if it's your second device then that's a good idea
[19:01] <popey> if it's your primary device I'd use the stable channel
[19:01] <Paddy_NI> Absolutely, I think that is what I had on it before
[19:11] <Paddy_NI> popey: I had previously flashed it with the stock E4.5 version of android so I am a little unsure as to how to flash this back to Ubuntu
[19:12] <Paddy_NI> I did "sudo ubuntu-device-flash touch --channel ubuntu-touch/rc-proposed/bq-aquaris.en --bootstrap recovery-krillin.img" whilst in fastboot mode
[19:12] <Paddy_NI> Device KRILLIN not found on server https://system-image.ubuntu.com channel ubuntu-touch/rc-proposed/bq-aquaris.en
[19:15] <popey> Paddy_NI, there's an askubuntu Q&A about this... one mo
[19:15] <popey> http://askubuntu.com/questions/602035/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5-and-aquaris-e5
[19:15] <Paddy_NI> Cool, thanks for your time :-)
[19:15] <Paddy_NI> Ah yes I was on that
[19:15] <dobey> you did not pass --reocvery it seems
[19:15] <Paddy_NI> ah
[19:15] <Paddy_NI> I thought that was a problem
[19:16] <Paddy_NI> The syntax is wrong in that Q&A
[19:16] <Paddy_NI> --recovery-image
[19:16] <Paddy_NI> Is not recognised
[19:17] <Paddy_NI> Hmm unknown flag --recovery
[19:17] <dobey> it's --recovery-image
[19:17] <dobey>       --recovery-image=  Specify the recovery image file to use when flashing,
[19:17] <Paddy_NI> I've done both
[19:17] <dobey> also do not run ubuntu-device-flash under sudo
[19:17] <Paddy_NI> ah
[19:18] <dobey> and as per the askubuntu answer, if you get unknown flag for --recovery-image option, you need to add the PPA and upgrad phablet-tools
[19:19] <Paddy_NI> Silly me
[19:19] <Paddy_NI> Tired
[19:19] <Paddy_NI> :-)
[19:21] <Paddy_NI> Not my night
[19:21] <Paddy_NI> $ ubuntu-device-flash touch --channel ubuntu-touch/rc-proposed/bq-aquaris.en --bootstrap --recovery-image recovery-krillin.img
[19:21] <Paddy_NI> 2015/11/23 19:21:00 Expecting the device to be in the bootloader... waiting
[19:21] <Paddy_NI> 2015/11/23 19:21:00 Device is |KRILLIN|
[19:21] <Paddy_NI> Device KRILLIN not found on server https://system-image.ubuntu.com channel ubuntu-touch/rc-proposed/bq-aquaris.en
[19:21] <Paddy_NI> Oops
[19:21] <Paddy_NI> I should have used pastbin
[19:21] <Paddy_NI> *paste
[19:23] <dobey> it shouldn't be all caps
[19:23] <dobey> maybe you need to --device krillin too
[19:23] <Paddy_NI> I know that's odd
[19:23] <Paddy_NI> cool
[19:24] <Paddy_NI> dobey: http://paste.ubuntu.com/13479346/
[19:25] <Paddy_NI> The devise itself says USB Transferring | USB Transmission OK Time:424ms Vel:21769KB/s
[19:26] <Paddy_NI> And that is what it still says
[19:26] <dobey> ok, i don't know why that is
[19:26] <Paddy_NI> Fair enoough
[19:26] <Paddy_NI> Enough
[19:26] <dobey> this is an e4.5 that originally came with ubuntu? or with android?
[19:27] <Paddy_NI> Ubuntu
[19:27] <Paddy_NI> I flashed it with the official Android ROM for the device
[19:27] <Paddy_NI> In the past it normally just flashed without fuss
[19:27] <jgdx> popey, quick q, if you own a mako, what channel should you use for rc-proposed?
[19:28] <dobey> Paddy_NI: do you currently have android 5.x on it?
[19:29] <Paddy_NI> dobey: YEp
[19:29] <dobey> Paddy_NI: try flashing back to the original android 4.4 rom for it, and then try flashing ubuntu again
[19:29] <dobey> jgdx: i use ubuntu-touch/rc-proposed/ubuntu on my mako
[19:30] <popey> what dobey said
[19:30] <jgdx> dobey, yeah me too. I will recommend that.
[19:30] <popey> jgdx, the same channel used on e4.5
[19:30] <dobey> e4.5 is bq-aquaris.en
[19:30] <Paddy_NI> dobey: Will do
[19:39] <Paddy_NI> brb I think a reboot might help me a little
[19:39] <dobey> probably not too much :)
[19:42] <Paddy_NI> meh
[19:46] <Paddy_NI> I've tried licking the screen and everything
[19:49] <dobey> did you flash to android 4.4 and boot it up, then reboot back to the bootloader and try to flash ubuntu again?
[19:50] <Paddy_NI> Trying to find the 4.x roms for it
[19:51] <Paddy_NI> BQ have a download on their site for 2.0.1_20150623-1900_bq-FW.zip
[19:51] <Paddy_NI> I think it might be KitKat not sure
[19:52] <Paddy_NI> And it seems to require the use of the dreaded SP_Flash_Tool
[19:52] <brendand> Paddy_NI, you can force the device '--device=krillin'
[19:52] <Paddy_NI> brendand: I did that
[19:52] <Paddy_NI> It fails to flash the device then
[19:52] <brendand> Paddy_NI, what is on it at the moment?
[19:52] <Paddy_NI> Android 5.x
[19:52] <Paddy_NI> Was originally Ubuntu Touch
[19:53] <brendand> Paddy_NI, and you reboot it into fastboot mode?
[19:53] <Paddy_NI> Yep
[19:54] <Paddy_NI> I just performed a factory reset from within android and letting it boot now
[19:54] <Paddy_NI> Going to give it another go
[19:54] <brendand> so it says  '=> FASTBOOT mode...' in the bottom corner
[19:54] <Paddy_NI> Yeah
[19:54] <Paddy_NI> The files transfer across but it then just fails
[19:54] <brendand> Paddy_NI, do you know which url you got the recovery image from?
[19:55] <Paddy_NI> brendand: Recovery image for ubuntu touch?
[19:55] <wligtenberg> What cable would I need to test/demo convergence on a Nexus4?
[19:55] <Paddy_NI> brendand: http://people.canonical.com/~jhm/barajas/recovery-krillin.img
[19:57] <pmcgowan> wligtenberg, slimport
[19:57] <wligtenberg> pmcgowan, so not MHL?
[19:58] <brendand> Paddy_NI, ok. just be double sure the file you're specifying in --recovery-image is that one. i would advice specifying the full path to that file, even if it is in the current working directory
[19:59] <pmcgowan> wligtenberg, not for nexus 4
[19:59] <Paddy_NI> brendand: Good point
[19:59] <wligtenberg> pmcgowan, ok thanks, good that I asked, I though MHL would have been the correct one. Thanks!
[20:00] <brendand> Paddy_NI, the behaviour sounds like the recovery image not being installed properly but i'd need to see your command + its output and the device output to know for sure
[20:00] <brendand> Paddy_NI, especially when you say 'USB Transferring | USB Transmission OK Time:424ms Vel:21769KB/s' is the last thing it says
[20:01] <brendand> Paddy_NI, now i see your pastebin from before and i'd be positive that's the problem
[20:02] <Paddy_NI> I feel confident that it'll work this time
[20:03] <brendand> Paddy_NI, you'll know pretty quickly as there'll be a lot more activity both on the console and the device
[20:07] <Paddy_NI> brendand: http://paste.ubuntu.com/13479760/
[20:07] <Paddy_NI> grrr
[20:08] <Paddy_NI> Maybe I should try and find an android 4.x rom for this E4.5. I also remember having to use Windows in order to get that dreaded SP_Flash_Tool working
[20:09] <brendand> Paddy_NI, it works on ubuntu
[20:09] <Paddy_NI> I could never get it working
[20:10] <brendand> Paddy_NI, the command above works on my krillin but i had ubuntu on it previously. shouldn't really matter though..
[20:14] <Paddy_NI> Perhaps I'll revisit this tomorrow http://paste.ubuntu.com/13479819/
[20:14] <Paddy_NI> brendand: ^
[20:14] <wligtenberg> bought a slimport, can't wait to test the convergence stuff :D
[20:16] <Paddy_NI> brendand: I wonder if that flash tool is available in a ppa
[20:17] <brendand> Paddy_NI, no definitely not
[20:17] <Paddy_NI> brendand: Am I even running it correctly
[20:18] <brendand> Paddy_NI, i just use ./flash_tool.sh without sudo
[20:18] <Paddy_NI> I get permission denied there too
[20:30] <dobey> Paddy_NI: yes, you need to find the 4.4 rom for the e4.5
[20:32] <dobey> "Optimisation of operating system for upgrading to Lollipop."
[20:33] <dobey> Paddy_NI: i'm pretty sure that "2.0.1 firmware" is android 4.4
[20:33] <Paddy_NI> dobey: Sadly the will require Windows
[20:33] <Paddy_NI> :-(
[20:34] <dobey> ? you should be able to flash using the mtk tool for ubuntu
[20:34] <Paddy_NI> Should
[20:34] <Paddy_NI> The Flash Tool just give me "Permission Denied"
[20:34] <dobey> oh
[20:34] <Paddy_NI> I have only ever been able to get it to work on windows
[20:35] <dobey> ok. i don't have a krillin here myself
[20:36] <Paddy_NI> That's no worries
[20:36] <dobey> so i can't offer much mor ehelp
[20:36] <Paddy_NI> I intend on kicking it's ass tomorrow
[20:36] <Paddy_NI> Thank you all for your help
[20:36] <dobey> np
[20:36] <Paddy_NI> Cheers popey brendand and dobey
[20:36] <Paddy_NI> Later
[21:00] <mterry> tedg, I'm looking at ubuntu-app-launch.  You seem to have gone to some lengths to keep very little state around (ubuntu_app_launch_observer_add_app_starting don't operate on a data structure, and don't seem prepared to be called multiple times).  And you also use dbus signals into the void (like UnityStartingBroadcast) instead of calling a method on a dbus name like com.canonical.Unity (despite expecting Unity to be the only one listening).  Wo
[21:00] <mterry> uld it be so terrible to call a method on unity?  (I'm looking at extending the handshake dance between UAL and Unity to allow unity to reject an app start -- so I am playing with the best way to get a response to UAL
[21:11] <mariogrip> dobey: I can make builds for devel-proposed (or rc-proposed) on my server if you want.
[21:11] <ahoneybun> hola mariogrip
[21:11] <mariogrip> Hey ahoneybun :)
[21:12] <ahoneybun> :)
[21:13] <dobey> mariogrip: hi. i'd actually like to get something set up to build on my server. i just don't know how to do it exactly
[21:18] <mariogrip> dobey: yeah,  just give me an ping if you need me
[21:18] <mariogrip> https://wiki.ubuntu.com/ImageBasedUpgrades
[21:20] <dobey> mariogrip: is there some way to use web hooks to for example cause my stuff to build new images, when certain channels on the official server get new images in them?
[21:28] <mariogrip> dobey: you can probably setup a webhook that run the build command
[21:29] <dobey> so the official server have webhooks?
[21:29] <dobey> or do i have to poll and parse the json?
[21:30] <mariogrip> I have a cron that run the import-images command
[21:30] <mariogrip> When there is no new images it just skips
[21:31] <dobey> ah
[21:31] <mariogrip> I have a cron every 2 hour
[21:40] <slvn_> leaving .. bye!