[02:26] <cxdvty> Hey all is it possible to install ubuntu touch on ipod touch?
[02:28] <cxdvty> ???
[02:30] <cxdvty> hello
[04:20] <lotuspsychje> morning guys
[05:29] <ubuntuser13> unable to create i386 emulator. ubuntu-emulator command says unknown flag 'arch'.
[07:59] <dholbach> good morning
[08:05] <ogra_> pitti, hmm, touch builds end up with systemd-sysv installed
[08:50] <pitti> ogra_: hm, not good -- do you have a build long URL?
[08:51] <ogra_> pitti, https://launchpadlibrarian.net/199792081/buildlog_ubuntu_vivid_armhf_ubuntu-touch_BUILDING.txt.gz
[08:51] <ogra_> (ignore the build failure, that is transient)
[08:52] <pitti> Setting up upstart (1.13.2-0ubuntu9) ...
[08:52] <ogra_> yeah, and  systemd-sysv
[08:53] <pitti> ogra_: systemd-sysv will always be installed as part of debootstrap, that's just how required packages work; but I thought our livecd-rootfs change should uninstall it and install upstart?
[08:53] <ogra_> this is how i understood it too :)
[08:56] <ogra_> pitti, the build before it wasnt pulled in at all
[08:56] <ogra_> https://launchpadlibrarian.net/199709836/buildlog_ubuntu_vivid_armhf_ubuntu-touch_BUILDING.txt.gz
[08:57] <ogra_> Package 'systemd-sysv' is not installed, so not removed
[08:58] <pitti> ogra_: I suppose that was before the priority adjustments from yestday?
[08:58]  * ogra_ wonders if we actually install ubuntu-standard 
[08:58] <ogra_> hmm, no
[08:58] <ogra_> pitti, oh, yeah
[09:00] <pitti> ogra_: no, I checked that before (no u-standard on touch)
[09:01] <ogra_> right, but if it now gets pulled into debootstrap that explains it
[09:01] <ogra_> we fail before the removal attempt
[09:01] <ogra_> because the chnage shanged GIDs
[09:01] <pitti> ah, ok
[09:01] <ogra_> *the change changed
[09:02] <janimo> pitti, do you know which kernel features systemd needs from 3.7 that are not in 3.4 ?
[09:02] <pitti> ogra_: so until now everything still seems to be ok? or am I missing something?
[09:03] <ogra_> pitti, no, let me override the file chnage and lets see ... but in fact then this seems to be the first run with the actual change
[09:03] <pitti> janimo: mostly the improved name space handling; but that said, I haven't actually tested systemd on a 3.4 kernel, so I don't know if that just means some features aren't available, or it'd fail completely
[09:04] <pitti> janimo: I saw your phablet@ mail, just didn't yet get around to replying yet; these are pretty crazy long days for me :)
[09:04] <ogra_> pitti, i think we need a session at the sprint and plan this properly
[09:04] <pitti> ogra_: "this"?
[09:05] <pitti> oh, systemd on touch? right
[09:05] <ogra_> kernel vs systemd ... kernel vs snappy features
[09:05] <ogra_> systemd on old kernels in general ... it doesnt only affect the phones but also nearly all snappy arm arches
[09:06] <pitti> janimo: stgraber recently responded to some "snappy on touch" thread about some details about the namespace (LXC is affected similarly)
[09:06] <janimo> pitti, do you have a link? I may not be on that ml
[09:06] <pitti> ogra_: right; it'd be worthwhile to investigate how well it actually runs on 3.4; it might work well enough, or not be too much effort to make it run
[09:07] <janimo> pitti, or maybe stgraber will answer since he's on phablet
[09:07] <ogra_> pitti, i know jolla uses sytemd on 3.4 ... but they stick to 208
[09:07] <pitti> janimo: https://lists.ubuntu.com/archives/snappy-devel/2015-February/000306.html
[09:07] <janimo> pitti, thanks
[09:41] <mpt> seb128, yes, pretty much nothing on the screen for an individual Bluetooth device is interesting for a device you can’t connect to.
[09:42] <seb128> mpt, ok, what annoyed me most is not understanding why those items were disabled, nothing conveys the reason than it's because they are unsupported types
[09:43] <mpt> hmmm
[09:45] <mpt> So it’s which is least bad: (a) not showing it at all, “Grarrr, why isn’t it showing up”; (b) showing it insensitive, “Grarrr, why is it disabled”; or (c) making it selectable but unpairable, “Grarrr, why let me go all the way there when I can’t pair with it after all”
[09:53] <seb128> hum
[09:53] <seb128> is "reboot" doing a shutdown rather than a reboot for others as well
[09:53] <seb128> using rtm 253 on bq
[10:01] <popey> seb128: reboots here.
[10:01] <seb128> popey, hum, k, thanks for testing
[10:01] <popey> np
[10:23] <JamesTait> Good morning all; happy Organize Your Home Office Day! :D
[10:34] <k1l_> i dont like that day ;p
[10:43] <seb128> do we have a mode on our osk where the keyboard is a numpad by default but with a way to switch to letters?
[10:44] <seb128> Elleo, ^?
[11:04] <Elleo> seb128: nope
[11:04] <Elleo> seb128: if you specify a number pad you're locked into that for the field
[11:05] <Elleo> seb128: although you could have a button in an app that changes the field's hint from numbers to text; that might be a bit clunky though
[11:06] <seb128> Elleo, how would I do that? do we have an example of code doing it?
[11:07] <seb128> Elleo, oh, you mean some widget in the app itself, not on the osk
[11:07] <Elleo> seb128: yeah
[11:07] <seb128> Elleo, the design is https://wiki.ubuntu.com/Bluetooth?action=AttachFile&do=get&target=phone-bluetooth-pair.png ... I though you were describing the bottom left button ;-)
[11:07] <Elleo> seb128: so, set the inputMethodHint on the text field to be Qt.ImhDigitsOnly and then remove that hint when a button is pressed
[11:07] <Elleo> seb128: ah, no
[11:07] <seb128> Elleo, right, that's not really nice :-/
[11:08] <seb128> Elleo, do we plan to have  a mode like described on the mockup I just mentioned?
[11:09] <Elleo> seb128: not that I know of, but there is currently a bug for design to reconsider the current numpad design (as we'd like to add a return key to it for example), so might be worth commenting there that'd it be useful to also have a switch back to letters: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1321603
[11:09] <Elleo> seb128: although that said that should maybe be handled via the NumbersPreferred hint instead of DigitsOnly
[11:10] <Elleo> seb128: so maybe it'd be a good idea to file a separate bug for supporting the NumbersPreferred hint with a mechanism for switching to letters
[11:11] <seb128> Elleo, ok, doing that, thanks
[11:11] <Elleo> no problem
[11:12] <Elleo> seb128: can bluetooth pins actually be non-numerical then? it's not something I've ever encountered
[11:12] <seb128> Elleo, it can...
[11:12] <Elleo> interesting
[11:13] <seb128> Elleo, i found https://bugs.maemo.org/show_bug.cgi?id=2587
[11:13] <Elleo> ah
[11:13] <seb128> Elleo, the spec says it's 16 digits including alphanumeric chars, though that doesn't seem to be common
[11:13] <seb128> trying on my samsung android phone, they do what you described
[11:13] <seb128> they default to numeric osk with a checkbox on the dialog "the code includes letters"
[11:14] <seb128> which switch to normal layout
[11:14] <Elleo> ah
[11:14] <Elleo> well that could at least be a reasonable solution until we get something more general implemented in the keyboard
[11:17] <seb128> Elleo, yeah, I'm going to file that osk feature request and then a design workaround bug
[11:18] <Elleo> okay
[11:26] <seb128> Elleo, https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1430264
[11:27] <Elleo> seb128: great, thanks
[11:35] <seb128> Elleo, https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1430265
[11:35] <seb128> mpt^ fyi, would be nice if you could comment on that
[11:41] <seb128> Elleo, http://help.spark.co.nz/euf/assets/images/ibase/samsung-galaxy-noteII-BluetoothPCPair3.jpg is the dialog I was talking about
[11:44] <Elleo> seb128: yeah, that should be doable with the current support in the keyboard easily enough
[11:45] <seb128> right
[11:46] <seb128> not sure design would like it though
[11:46] <seb128> let see what mpt thinks
[11:53] <mpt> I think that blue clothes pegs should be banned
[11:54] <mpt> I don’t know why, but they are the ones that break first, before any of the other colors
[11:56] <seb128> mpt, sorry, looks like your IRC timeouted while we were discussing the topic
[11:56] <seb128> mpt, it was about https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1430265
[11:57] <seb128> mpt, currently the "bluetooth pin pairing" dialog has a full keyboard, which is inconvenient for entering digits, especially that those are not on the first osk screen, you need to switch mode to get to them
[11:57] <seb128> mpt, http://help.spark.co.nz/euf/assets/images/ibase/samsung-galaxy-noteII-BluetoothPCPair3.jpg is somewhat similar to the workaround we were discussing
[11:58] <seb128> mpt, the osk is not likely to support what we need soon, so we were pondering if we should just have the full keyboard experience meanwhile or look for a workaround like ^
[11:59] <mpt> ¯\_(ツ)_/¯
[12:06] <mpt> That screenshot is a bit depressing to look at (“Try 0000 or 1234 … one of them might work … idk”), I don’t know how it works
[12:06] <mpt> What happens if you check the checkbox, type some letters, then uncheck the checkbox? :-)
[12:11] <mpt> seb128, or there could be a System-Settings-provided “123”/“ABC” toggle that sits above the OSK
[12:11] <mpt> But that only works if something outside the OSK can change the current mode of the OSK
[12:13] <Elleo> mpt: yeah, that's possible by changing the input hint on the field
[12:13] <Elleo> at least I think the keyboard supports it changing whilst being focused, if not that's a bug
[12:13] <mpt> Elleo, I mean something outside the OSK that can change the OSK back to number mode *even if you have already typed letters*
[12:15] <Elleo> mpt: yeah, I think that'll still work; the keyboard doesn't care about the field's contents only its input hints
[12:15] <mpt> cool
[12:25] <seb128> mpt, Elleo, sorry, was at lunch, yeah changing the mode doesn't impact on what is in the text entry, the osk just allow to type it's not enforcing anything
[13:37] <studio_> hi
[13:40] <studio_> any idea when the mtp-problem with the bq e4.5 and the 15.04 will be fixed?
[13:41] <dobey> "soon"
[13:41] <studio_> ok
[13:44] <mcphail> Does anyone know when the touch os is going to change from click to snappy packages?
[13:45] <popey> "soon"
[13:45]  * popey adds "soon" to the /topic :)
[13:46] <mcphail> ha ;)
[13:47] <mcphail> it is like cyanogenmod's "never ask for an ETA"
[13:48] <studio_> this, https://wiki.ubuntu.com/Touch/ReleaseNotes is outdated, right?
[13:49] <mcphail> I'm playing with bundling libraries and it seems very straightforward with snappy. I don't want to learn click's plumbing if it is going to be obsolete "soon"
[13:51] <dobey> yes, saucy is way outdated
[13:55] <studio_> dobey, where do i find my "data.csv", contacts now on my phone to save/backup them?
[13:56] <dobey> studio_: it's not a csv file
[13:57] <studio_> isn't it?
[13:57] <dobey> studio_: it's an sqlite database. they are stored in the same location on the phone, as they are on Ubuntu on a PC
[13:57] <dobey> in ~/.local/share/evolution/
[13:58] <studio_> on the ubuntu-pc i use thunderbird :) ok, thanks
[14:08] <studio_> dobey, sorry for that "stupid" question, but how to backup the contacts from the phone?
[14:08] <dobey> adb pull ?
[14:09] <studio_> adb pull what?
[14:11] <dobey> the file, or the whole evolution directory
[14:13] <studio_> sorry, i never worked with evolution, only thunderbird. is there a how-to where i can read that?
[14:15] <tsdgeos> cyphermox: any idea how/what could be causing https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1428799 ? it's pretty annoying
[14:21] <studio_> dobey, here http://wiki.ubuntuusers.de/Evolution it said it is possible to export csv. is it different to ubuntu touch?
[14:24] <popey> we dont ship evoluion on the phone
[14:24] <dobey> studio_: evolution UI is not on the phone
[14:24] <dobey> and i am on a call...
[14:25] <cyphermox> tsdgeos: no, seems to work for me, but give me a minute I'll do more testing
[14:25] <tsdgeos> cyphermox: yeah it also works for greyback_ :/
[14:26] <tsdgeos> cyphermox: there's something weird with my router, i have "tsdgeos 1", "tsdgeos 2", "tsdgeos 3", "tsdgeos 4", "tsdgeos 5", "tsdgeos 6", "tsdgeos 7"
[14:26] <popey> studio_: http://stackoverflow.com/questions/75675/how-do-i-dump-the-data-of-some-sqlite3-tables
[14:26] <cyphermox> tsdgeos: that would explain it
[14:26] <tsdgeos> in nmcli c
[14:26] <cyphermox> tsdgeos: it's not your router
[14:26] <tsdgeos> all with different UUIDs
[14:26] <cyphermox> tsdgeos: look at them, probably all a different mac-address fields
[14:27] <tsdgeos> if UUID==mac yes
[14:27] <tsdgeos> otherwise don't know how to use the mac
[14:27] <cyphermox> nope
[14:27] <tsdgeos> s/use/know
[14:27] <cyphermox> there should be another field lower down in the file with a mac address?
[14:27] <tsdgeos> cyphermox: which file?
[14:28] <studio_> popey, i just try to figure out a simple way to im- and export contacts to or from the phone.
[14:28] <tsdgeos> http://paste.ubuntu.com/10574854/
[14:28] <cyphermox> in these connection files "tsdgeos 1", etc. under /etc/NetworkManager/NetworkManager.conf
[14:28] <tsdgeos> ah
[14:28] <tsdgeos> ok
[14:28] <cyphermox> ah
[14:28] <cyphermox> now I see what you mean :)
[14:28] <popey> studio_: sure, that post talks about dumping out the database
[14:28] <popey> studio_: i _think_ ./.local/share/evolution/addressbook/system/contacts.db is the database
[14:28] <tsdgeos> cyphermox: correct, different mac address
[14:29] <cyphermox> tsdgeos: I suspect last time you flashed, something went wrong and wiped out the mac address on the phone
[14:29] <tsdgeos> may very well be
[14:29] <tsdgeos> i've had some weird issues flashing lately
[14:30] <tsdgeos> can i recover it?
[14:34] <cyphermox> tsdgeos: I can't remember how I fixed it if it indeed happened on my mako and not on another device
[14:34] <cyphermox> I'd frst try to flash the factory image back on it
[14:34] <cyphermox> then re-do the flashing to put vivid on
[14:36] <cyphermox> also check whether /factory/wifi/.mac.info exists and has a mac address written in it
[14:37] <tsdgeos> cyphermox: lol, /factory is a broken symlink to /android/factory
[14:37] <tsdgeos> i guess it's bad that i don't have that folder :D
[14:38] <cyphermox> maybe not, it might just not be mounted
[14:38] <cyphermox> where else did the mac address live?
[14:38] <studio_> popey, for me http://stackoverflow.com/questions/75675/how-do-i-dump-the-data-of-some-sqlite3-tables is not "easy" to understand :(
[14:39] <popey> sorry, was the first sensible thing I could find
[14:39] <cyphermox> tsdgeos: I think there was some other wifi directory somewhere, /data or /etc/ or something, which also contained the MAC, but a reasonable first try would definitely be to flash the factory image, reboot to check that *it* is fine (ie MAC doesn't change), then flash again
[14:39] <tsdgeos> yeah not having  /android/factory doesn't look cool
[14:42] <studio_> it would be more easy, when "ci-train-ppa-service/landing-027" also "could" support export :)
[14:44] <ogra_> studio_, the mtp issue should be fixed with silo 19
[14:44] <kenvandine> Elleo, any thoughts on bug 1429691
[14:44] <ogra_> studio_, the package in there is one of the ones that are hard to install though
[14:45] <kenvandine> i haven't looked closely at the code for that yet, i'm just really surprised the store doesn't get used when filtering the ContentPeerPicker model with ContentType.All
[14:45] <Elleo> kenvandine: yeah, that's odd
[14:46] <kenvandine> i did reproduce it by changing Pictures to All in picker-qml example
[14:46] <kenvandine> but it works with Pictures
[14:46] <kenvandine> somehow we must be clearing the store property?
[14:46] <studio_> ogra_, i think i am on the wrong branch now. i am on "ubuntu-touch/devel-proposed/krillin.en" right now :(
[14:46] <ogra_> not sure what that is :)
[14:47] <studio_> ;)
[14:49] <Elleo> kenvandine: yeah, not sure how though; all we really do with All is iterate through the existing types as we would for a single one
[14:49] <kenvandine> yeah... i really didn't think i would be able to reproduce it :/
[14:50] <kenvandine> Elleo, it's nice to be hacking more on content-hub again :)
[14:50] <Elleo> where's the picker-qml example you're testing against?
[14:51] <kenvandine> Elleo, in the source, examples/picker-qml
[14:51] <Elleo> ah, I see
[14:51] <kenvandine> just change Pictures to All
[14:51] <kenvandine> oh
[14:51] <kenvandine> and add the store from the import-qml example :)
[14:52] <Elleo> so you're adding the store after the peer has been selected from the picker
[14:52] <kenvandine> then pass the store to request()
[14:52] <kenvandine> i added it as a sibling of ContentPeerPicker
[14:52] <kenvandine> and in peer.request(appStore)
[14:52] <kenvandine> for example
[14:52] <kenvandine> so the store gets passed to the peer
[14:52] <kenvandine> after selected
[14:52] <Elleo> yeah, but that peer.request is being done onPeerSelected right?
[14:52] <kenvandine> oh!
[14:53] <kenvandine> i know why
[14:53] <Elleo> oh?
[14:53] <kenvandine> maybe
[14:53] <kenvandine> no... ignore that :)
[14:53] <kenvandine> yeah
[14:53] <Elleo> I'd have thought All shouldn't really have much effect by that stage since the peer itself should be a specific type
[14:53] <kenvandine> in onPeerSelected we call peer.request(appStore)
[14:54] <kenvandine> it should have no effect
[14:54] <kenvandine> Elleo, i didn't look at the code path in the qml bindings yet, but it seems impossible
[14:55] <kenvandine> however, i did see it myself :/
[14:55] <kenvandine> i think there is a place in creating the transfer where it does some hubType lookup?
[14:55] <kenvandine> converting the type for the backend, which doesn't have an all
[14:56] <kenvandine> maybe if that fails we miss a code path
[14:56] <kenvandine> but i think that should only affect the default peer
[14:58] <Elleo> yeah, I don't see anything obvious in the qml all handling code
[14:58] <Elleo> it's setting up each peer as being for a specific content type, so anything from that point on should be the same
[14:59] <kenvandine> but how about in the Peer code?
[14:59] <kenvandine> anything there in the request?
[14:59] <Elleo> well the peer code doesn't know anything about All
[15:00] <kenvandine> yeah, but that is where the transfer is created
[15:00] <Elleo> and it sets the store content type based on the peer's content type in the request
[15:01] <Elleo> oh no, actually looking at the peer model, maybe we are setting the type as all on the peer
[15:01] <kenvandine>         qmlTransfer = contentHub->importContent(m_peer, m_contentType);
[15:01] <kenvandine> the peer doesn't really have a type
[15:01] <kenvandine> it could provide multiple
[15:02] <kenvandine> not sure why it cares though
[15:03] <Elleo> kenvandine: http://bazaar.launchpad.net/~phablet-team/content-hub/trunk/view/head:/import/Ubuntu/Content/contentpeermodel.cpp#L147 <-- I'm wondering if that and line 150 should actually be the otherway around
[15:03] <kenvandine> we set the store later
[15:03] <dobey> studio_: (mkdir -p evolution && cd evolution && adb pull .local/share/evolution .)
[15:04] <dobey> studio_: that will back up all the contacts and calendar data (including alarms) from the phone
[15:04] <kenvandine> Elleo, maybe... but still i don't think that should matter because a peer could support multiple types
[15:05] <kenvandine> const cuc::Type &hubType = ContentType::contentType2HubType(contentType);
[15:05] <Elleo> kenvandine: the current implementation has a single m_contentType member for contentpeer, which gets used when setting up the store
[15:05] <kenvandine> Elleo, maybe we need to do something different there for All
[15:05] <kenvandine> since All isn't going to map?
[15:06] <Elleo> kenvandine: so if it tries setting the store to all presumably the store doesn't match anything
[15:06] <kenvandine> yeah
[15:06] <studio_> dobey, thanks :)
[15:06] <kenvandine> Elleo, you mean type?
[15:07] <peat-psuwit> awe_, are you awake now?
[15:07] <awe_> yes, in the middle of a stand-up though
[15:07] <awe_> can I ping you when done?
[15:07] <awe_> ~5m
[15:07] <Elleo> kenvandine: I mean setting the store's type; it calls "store->updateStore(m_contentType);" when creating the request
[15:07] <awe_> sorry, ~20m
[15:07] <peat-psuwit> awe_, yes
[15:08] <kenvandine> oh!
[15:08] <kenvandine> so that fails
[15:08] <awe_> peat-psuwit, abeato added some comments to your bug, have you seen them?
[15:08] <Elleo> kenvandine: so either contentpeer needs to never receive All as its type, or the store needs to know about All
[15:08] <kenvandine> Elleo, you are probably right
[15:09] <peat-psuwit> awe_, not yet. Let me check it out.
[15:09] <Laney> who knows qmake?
[15:09] <awe_> peat-psuwit, thanks...
[15:09] <popey> Laney: bzoltan_
[15:09] <Laney> Can you get qtquickcontrols-opensource-src from the archive and see why the tests aren't built/make checked properly?
[15:09] <Laney> bzoltan_: hi! :)
[15:10] <bzoltan_> Laney:  yeah, I live in the same block with qmake...
[15:10] <Laney> It's using some magic thing called qt_parts
[15:11] <seanmavley> hello
[15:11] <Laney> but it's not magic enough to pick up tests/
[15:13] <bzoltan_> Laney: I will take a look at it tomorrow... I am busy with the UITK lanindg right now
[15:15] <kenvandine> Elleo, maybe the store should have Other?
[15:16] <kenvandine> Elleo, and we attempt to use the type the peer is known to handle
[15:16] <kenvandine> i guess we'll always have at least one type
[15:16] <kenvandine> so i guess just make sure it gets set to a type the peer handles?
[15:16] <kenvandine> so change the != to ==
[15:19] <Elleo> kenvandine: yeah, I think that'll sort it so that the default peers are always listed first for things requesting All
[15:19] <Elleo> kenvandine: which I would guess is what we actually intended there
[15:20] <Elleo> although not sure why that wouldn't be the case in the other condition too
[15:23] <awe_> peat-psuwit, I'm done.  Did you have another question for  me?
[15:26] <peat-psuwit> awe_, I actually know now why gsm_umts_index is 0, just think it's inappropriate to talk in that bug.
[15:27] <peat-psuwit> My phone actually need another request to select which app to use.
[15:27] <oSoMoN> brendand, https://trello.com/c/kaOl1PRE/1077-ubuntu-landing-003-oxide-qt-osomon is not needed any longer, I’ve asked the CI train team how I can mark the corresponding line obsolete, but wanted to also notify you that it can be ignored
[15:27] <awe_> why do you think it's inappropriate?
[15:28] <awe_> peat-psuwit, the rilmodem code that handles SIM status definitely needs to be updated
[15:28] <awe_> as it will use an invalid value currently
[15:28] <awe_> yes, your phone may need to send an extra request
[15:29] <awe_> and make it do so, is another bit of complexity, that's related but not the problem in the existing code
[15:29] <awe_> to do so, you'd need to figure out a why to identify your device
[15:30] <awe_> and craft a new device plugin which at minimum, sets a vendor type
[15:30] <awe_> depending on how the extra request works
[15:31] <awe_> it might be possible to send from the device plugin, or... detect the vendor type in the sim atom and send it there.
[15:31] <awe_> it can get tricky
[15:32] <awe_> my only advice would be to look at the mtk plugin
[15:32] <peat-psuwit> awe_, I actually made some crude hack that make it send that request. My phone can now register to network and talk USSD.
[15:32] <awe_> ok
[15:32] <popey> peat-psuwit: you working on a device port?
[15:32] <peat-psuwit> Yes, LG L90 Dual.
[15:32] <kenvandine> bfiller, do we have a common bug tag we use for convergence related bugs?
[15:32] <peat-psuwit> I think I've told that already.
[15:33] <awe_> if the rild is that different, eventually a device plugin, and a rilmodem-based extension driver might be necessary ( just like mtk/mtkmodem )
[15:33] <popey> peat-psuwit: cool, I didn't see, sorry.
[15:33] <awe_> peat-psuwit, dual-SIM?
[15:33] <peat-psuwit> awe_, Yes.
[15:33] <awe_> hmmm
[15:33] <awe_> sure you can hack it
[15:34] <awe_> but getting dual-SIM to work properly for krillin was a lot of work
[15:34] <awe_> extending the base ril plugin and rilmodem driver
[15:34] <awe_> most of the hard-work is done in the mtk plugin
[15:34] <awe_> however there may be some logic pushed down into the mtkmodem atoms
[15:36] <peat-psuwit> awe_, I may eventually make a new plugin for that. For now, I'll just hack the existing code. I don't know how to make a new plugin without duplicating too much code.
[15:37] <bfiller> kenvandine: I'm not aware of one
[15:38] <akiva-thinkpad> Ubuntu Team AMA on Google Hangouts starting in one hour | #ubuntu-on-air  (Preface any question you have with "QUESTION:" ) http://ubuntuonair.com/
[15:38] <awe_> understood.  There was actually a fair amount of a dup between the ril and mtk plugins when we started krillin.  I was opposed to this, but there wasn't an easy solution to the problem
[15:38] <akiva-thinkpad> Good time to ask ubuntu touch questions ~
[15:38] <awe_> peat-psuwit, and mtk has grown quite different than ril since...
[15:38] <akiva-thinkpad> erm
[15:39] <akiva-thinkpad> 20 minutes *
[15:39] <awe_> peat-psuwit, if/when you decide to create a new plugin, I'd use the mtk model as your base
[15:39] <awe_> you'll also need to look at the rildev plugin which decides which device plugin to load based upon an env var
[15:40] <awe_> this is our equivalent of the native ofono udev plugin
[15:40] <awe_> which we don't run
[15:42] <peat-psuwit> awe_, Thanks for the clue. But probably not now.
[15:42] <awe_> np
[16:05] <Saviq> Elleo, hey, sorry for the inflow of bugs for ubuntu-keyboard ;)
[16:05] <Saviq> I had a list that I was meaning to file for a while now
[16:06] <Saviq> looks like I'm done now ;)
[16:06] <kenvandine> Saviq, bug spam?  that's not nice :-p
[16:07] <Elleo> Saviq: no worries :)
[16:07] <Saviq> kenvandine, my list was halved since I wrote it ;)
[16:07] <kenvandine> that's good
[16:07] <Elleo> Saviq: I think a couple of them have a couple of branches waiting to land at the moment too
[16:08] <Saviq> Elleo, cool
[16:08] <Elleo> thanks for the reports :)
[16:09] <faenil> mm target creation in Ubuntu SDK returns an "chroot/blabla/sbin/initctl not found" error...known issue?
[16:10] <faenil> Framework 15.04
[16:24] <jgdx> faenil, hey, are you running uitk from the bleeding edge? (And welcome!)
[16:25] <faenil> jgdx: thanks :) I downloaded the sdk from the official website, as instructed
[16:27] <jgdx> maybe a systemd/upstart issue?
[16:27] <faenil> most likely :) just not sure how to act, since it's part of the targets
[16:27] <faenil> chroot targets
[16:29] <jgdx> there's https://wiki.ubuntu.com/SystemdForUpstartUsers
[16:30] <faenil> the problem is I don't think I have any access to the chroot targets, do I'
[16:30] <faenil> ?
[16:30] <faenil> "Click" just downloads the targets, unpacks the packages, then tries to configure the system --> fails --> cleans up everything
[16:34] <jgdx> Mine aren't cleaned up…
[16:38] <faenil> jgdx: yours doesn't clean up after an error?
[16:39] <faenil> it clearly says so in the log, in my case
[16:39] <faenil> :)
[16:42] <jgdx> faenil, mine weren't, but maybe my chroots failed post setup. $ schroot -l
[16:43] <faenil> :)
[17:00] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150310-ae1ddec.tar.xz
[17:00] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-20150310-ae1ddec.changes
[17:00] <john-mcaleely> http://people.canonical.com/~jhm/barajas/master/device_krillin-testresults-20150310-ae1ddec.ods
[17:00] <john-mcaleely> sil2100, krillin vivid tarball (I assume needs QA signoff now?)
[17:00] <john-mcaleely> rsalveti, ^ rtm coming shortly
[17:02] <rsalveti> john-mcaleely: thanks
[17:03] <rsalveti> john-mcaleely: yeah, we'll need qa signoff for both vivid and rtm
[17:03] <john-mcaleely> rsalveti, cool.
[17:06] <DonkeyHotei> rsalveti: did you see my /query a while back?
[17:07] <rsalveti> no, sorry, still need to reply the email
[17:07] <DonkeyHotei> rsalveti: i repasted the contents of the e-mail and added an update
[17:12] <DonkeyHotei> rsalveti: maybe i could somehow get started working with bluez 5 on ubuntu touch in anticipation of integration in the desktop flavors?
[17:13] <rsalveti> right, that's quite a bit of work, and mainly kernel at the moment
[17:14] <DonkeyHotei> rsalveti: i have some kernel experience. is there someone i could coordinate with?
[17:14] <dobey> faenil: you are running on top of 15.04, or you are trying to create a 15.04 target on a stable release of ubuntu?
[17:16] <popey> dobey: it's bug 1430436
[17:16] <dobey> ah ok
[17:17] <faenil> dobey: yeah just filed a bug, I'm on 15.04 btw
[17:17] <faenil> 14.10 target creation also failed...
[17:17] <rsalveti> DonkeyHotei: not right now, we still need to better understand what is required
[17:18] <faenil> now I rebooted, and I'm trying again with 14.10
[17:19] <DonkeyHotei> rsalveti: is there an alternate task i could take on to demonstrate that i have the needed experience?
[17:19] <rsalveti> DonkeyHotei: we'll discuss what are the following steps later this week, because we want something that can be common across candidates
[17:20] <rsalveti> so we'll keep you posted
[17:20] <DonkeyHotei> thanx
[17:21] <DonkeyHotei> on another front, is stuff that people are working on on 14.09 actively getting forward-ported to vivid?
[17:21] <ogra_> pitti, \o/
[17:21] <ogra_> The following packages will be REMOVED:
[17:21] <ogra_>   systemd-sysv
[17:21] <ogra_> https://launchpadlibrarian.net/199846905/buildlog_ubuntu_vivid_i386_ubuntu-touch_BUILDING.txt.gz
[17:21] <ogra_> finally ...
[17:21] <dobey> DonkeyHotei: usually stuff is back-ported to the 14.09 build from vivid
[17:21]  * ogra_ waits for armhf ... 
[17:22] <DonkeyHotei> dobey: on vivid there is no on-screen keyboard, so i can't enter the wpa key
[17:23] <dobey> DonkeyHotei: there is a keyboard on vivid. but there might be a bug where it isn't always popping up correctly
[17:23] <dobey> DonkeyHotei: try cancelling, then turning the screen off and on, unlocking, and then connecting to wifi
[17:23] <DonkeyHotei> dobey: well, it pops up on 14.09
[17:25] <dobey> yes, well, 14.09 is "stable" and vivid is not stable. there are some known issues in vivid that should hopefully be fixed soon as there is more work going on there now to make it as stable as 14.09 so we can switch users to it with an OTA update when it becomes stable
[17:55] <jgdx> kenvandine, I'll set [1] to "In review" when LP comes around. [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/hotspots-binding/+merge/252296
[17:56] <jgdx> kenvandine, so you're free to test it and hopefully break it horribly.
[17:57] <dobey> the list of apps in the location settings page, where is that stored on the phone?
[17:59] <ogra_> dobey, there is some db in the trusted-store
[17:59] <kenvandine> jgdx, ugh, is LP down?
[17:59] <jgdx> kenvandine, the code part it seems?
[17:59] <jgdx> they know
[18:01] <kenvandine> ok
[18:02] <jgdx> kenvandine, you have to use Exec=env USS_SHOW_ALL_UI=1 system-settings %u
[18:02] <jgdx> in the desktop file
[18:02] <kenvandine> jgdx, that reminds me...
[18:02] <jgdx> uh oh
[18:02] <kenvandine> do you want to prepare a branch exposing the other vibrate setting?
[18:02] <kenvandine> uitk landed in vivid :)
[18:02] <jgdx> that has landed?
[18:02] <jgdx> weee
[18:02] <kenvandine> indeed :)
[18:02] <kenvandine> friday
[18:02] <kenvandine> so we're good!
[18:02] <jgdx> dauym
[18:03] <kenvandine> so... does un-hiding existing hidden UI count as a feature?  :-D
[18:04] <kenvandine> i guess the other vibrate setting was included in some sort of FFe in order for it to land in the uitk
[18:04] <kenvandine> bfiller, ^^  do you know?
[18:04] <ogra_> kenvandine, would fall under the UI freeze i fear
[18:04] <kenvandine> sigh
[18:04] <kenvandine> you're right...
[18:04] <ogra_> (which is in effect together with the FF)
[18:04] <kenvandine> we couldn't expose it until the uitk landed their part
[18:04] <ogra_> just stop working on stuff in main :)
[18:05] <kenvandine> universe man!
[18:05] <ogra_> master of the ... :)
[18:05] <kenvandine> you know it!
[18:05] <kenvandine> jgdx, well at least propose the branch :)
[18:06] <kenvandine> worst case we don't land it right away :)
[18:06] <jgdx> it push it straight to production
[18:06] <jgdx> s/it/I'll
[18:06] <kenvandine> :)
[18:06] <jgdx> bzr push :production
[18:06] <jgdx> right?
[18:06] <kenvandine> that would be so cool... :production lands in distro and merges to trunk :)
[18:06] <jgdx> :D
[18:06] <kenvandine> we need a bzr plugin to do that
[18:06] <kenvandine> and make my coffee
[18:07] <kenvandine> it's great to see people using content-hub more again, seems there are new developers using it in waves... months with little feedback then bursts of feature request/bug reports
[18:08] <jgdx> kenvandine, how has the last week(s) been? Good momentum?
[18:08] <kenvandine> i hit a wall... need to hand it off to an expert :)
[18:08] <kenvandine> but now we've had some good bug reports come in this week
[18:09] <dobey> kenvandine: well, when we get away from the whole spreadsheet thing, and have a CI dashboard with a decent REST API, a bzr plug-in which pushes, creates an MP, and requests a silo, could be doable. would be nice if all the silo review stuff was integrated into the launchpad MP UX too
[18:10] <kenvandine> dobey, +1
[18:10] <jgdx> kenvandine, ah. :) That reminds me, when you're testing the AP story, you need to modify a wpa supplican't policy. Lolz
[18:10] <kenvandine> jgdx, please note it in the MP
[18:10] <jgdx> kenvandine, will do
[18:10] <kenvandine> jgdx, and that's just for AP testing?
[18:10] <jgdx> kenvandine, yes
[18:11] <kenvandine> isn't that going to cause a problem with CI?
[18:11] <jgdx> s/AP/hotspot really, I don't think we're exposing any other methods right now.
[18:11] <kenvandine> oh
[18:11] <kenvandine> i thought autopilot :)
[18:12] <jgdx> still, it will affect QA testing.. hm
[18:12] <kenvandine> we need good manual testing instructions
[18:13] <jgdx> jdstrand, hi, could you take another look at bug 1426923 ? Tony replied to your comment.
[18:16] <kenvandine> renatu, hadn't you filed a bug against content-hub about being able to send serialized vcards without generating a file to transfer?
[18:24] <kenvandine> renatu, i'm not seeing it, i wanted to bounce an idea off you when you have a minute
[18:24] <jdstrand> jgdx: hi! I can't get to it right now, but added it to my todo. thanks for the ping, I didn't see the response
[18:24] <jgdx> jdstrand, sure. Thank you!
[19:32] <brendand> barry, sorry, we forgot to add you to the standup again
[19:33] <brendand> barry, check your calendar again
[19:33] <barry> brendand: k
[19:34] <barry> brendand: still no event for today.  is it the same hangout url?
[19:34] <brendand> barry, https://plus.google.com/hangouts/_/canonical.com/qa
[19:46] <wxl> hey kids
[19:46] <wxl> if i wanted to make a suggestion (split screen like ghost commander for android) for the file manager, is making a wishlist bug the best?
[20:07] <jgdx> wxl, that sounds like a huge change. A wishlist bug with research and suggestions is probably best.
[20:07] <wxl> jgdx: yep didn't say it was small. just wanted to confirm the process; thanks!
[20:08] <dobey> good luck convincing design :)
[20:08] <jgdx> well, it would beat tabs on a tab/phone
[20:48] <kenvandine> nobody upgrade to vivid-proposed mako image 128, doesn't boot :/
[20:50] <robin_hero> hi! I tried 14.09-proposed image in emulator, but can't sync my gmail contacts in the address-book. I setted up my gmail account, and enabled the access to the contact, but nothing. But I know it was work in the past. Any idea?
[21:09] <yacuken> hi there
[21:13] <yacuken> who's can tell me in plain words, what files we need to flash ubuntu on device? Porting guide tell me about boot.img, recovery.img and system.img. But why we build android-boot.img and other?
[21:14] <dobey> the porting guide says what you need to do, to port to a device
[21:20] <yacuken> dobey: in "Flashing the image" section. I just look at an example and can not understand
[21:22] <dobey> yacuken: ok. i haven't done a port myself so i'm not sure what you're not understanding, but i can tell you that others have followed the guide successfully to port ubuntu to new devices
[22:06]  * PLA1 wishes he read kenvandine: comment an hour ago. :-(
[22:12] <DonkeyHotei> PLA1: ?
[22:14] <PLA1> DonkeyHotei: "16:48 < kenvandine> nobody upgrade to vivid-proposed mako image 128, doesn't boot :/"
[22:14] <DonkeyHotei> i think i have 127
[22:17] <PLA1> On my Nexus 7 2013 I was running vivid-proposed. I took today's OS update and it no longer boots. Stuck at the Google unlocked padlock screen. Oh well.
[22:19] <DonkeyHotei> PLA1: i am booted into vivid-proposed on hammerhead atm
[22:20] <DonkeyHotei> updating to 128 now
[22:20] <popey> PLA1: you can flash back to previous fairly easily...
[22:21] <PLA1> popey: Got that syntax in your head?
[22:22] <popey> ubuntu-device-flash touch --device=mako --channel=ubuntu-touch/devel-proposed --revision=127
[22:22] <popey> i _think_
[22:22] <PLA1> popey: Thanks!
[22:23] <DonkeyHotei> yep, 128 is not booting
[22:26] <DonkeyHotei> popey: is there a way to debug the boot?
[22:27] <popey> pass
[22:27] <popey> look how many updates... http://people.canonical.com/~ogra/touch-image-stats/128.changes
[22:28] <Foxtrot> Hey
[22:30] <DonkeyHotei> popey: pass? is that a tool?
[22:31] <Foxtrot> Is there any place for me to talk about Ubuntu Touch on the Nexus 6? The link in the topic and other Wiki references seem outdated
[22:34] <popey> DonkeyHotei: pass = I don't know
[22:34] <popey> Foxtrot: we don't have an official port for the nexus 6
[22:34] <popey> Foxtrot: someone in the community might port it
[22:34] <Foxtrot> Yeah i was looking to fix that and get it running on mine
[22:34] <popey> that would be awesome
[22:34] <PLA1> Hmm. ubuntu-device-flash on 14.10 says unknown flag `revision' even though it is in the help text. Do you see a typo here? http://pastebin.ubuntu.com/10577109/
[22:34] <Foxtrot> Reading through the articles now, just wondered if anyone else was active with it
[22:35] <popey> hmmm
[22:35] <Tassadar> nexus 6 only has lollipop, ubuntu's using only 4.4, it's gonna be a bunch of work probably
[22:35] <popey> ahh good point
[22:35] <DonkeyHotei> Foxtrot: someone else mentioned it in the channel recently
[22:35] <Foxtrot> ah
[22:42] <roeei> hi all, anybody tried porting to xperia z series?
[22:44] <roeei> Im having some doubts with the xperia aosp source code and where to put it
[23:03] <simosx> I am trying to run ./buildOnDevice.sh. It says in the script that: " * Make sure to have the networking and PPAs setup on the device beforehand (phablet-deploy-networking && phablet-ppa-fetch)." Where do I get them from? They do not appear to exist in "phablet-tools".
[23:05] <roeei> what device are you building for simosx?
[23:06] <simosx> roeei, the bq E4.5
[23:06] <roeei> i thought that came with ubuntu preinstalled
[23:07] <roeei> I now see there is also an android version
[23:08] <roeei> im using this to build for my xperia z1 compact http://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[23:08] <roeei> but im also kinda stuck
[23:08] <simosx> cannot find the files on the phone. will try anyway the script to build.
[23:08] <popey> simosx: what you trying to do?
[23:08] <simosx> popey, I want to build ubuntu-keyboard and install to the phone.
[23:09] <popey> ahh
[23:36] <mariogrip> Does the apple watch bend?
[23:38] <mariogrip> **wops wrong irc**
[23:38] <DonkeyHotei> it was worth the smile
[23:39] <mariogrip> :)
[23:57] <RobbyF> lol
[23:58] <DonkeyHotei> nhaines: did your phone get 5.1?