[00:10] <pngo_> I can send mms but can not receive one. Is this known issue or is it only my phone?
[02:33] <gaducouch> hey guys! I'm totally new to this chat and with ubuntu touch, so i have a question regarding my phone and sms not working
[02:33] <lotuspsychje> gaducouch: wich device?
[02:33] <gaducouch> I looked it up and found some things about removing the pin-code from my sim card but there is none
[02:34] <gaducouch> nexus 5 (hammerhead)
[02:34] <lotuspsychje> gaducouch: maybe nhaines might know this
[02:34] <gaducouch> unless i just checked wrong
[02:34] <lotuspsychje> he has a n5 i think
[02:35] <gaducouch> ok and how can i contact him?
[02:35] <lotuspsychje> idle here sometime
[02:35] <lotuspsychje> !devices
[02:35] <gaducouch> okay thx a lot
[02:36] <lotuspsychje> check also the status here
[02:36] <gaducouch> ok will do one sec
[02:36] <lotuspsychje> some things might not work properly on some devices
[02:36] <gaducouch> okay browsing it right now
[02:38] <gaducouch> okay seems i could have some trouble with the bluetooth but i don't really mind but thx guys i'll try to get to nhaines
[02:38] <lotuspsychje> kk
[02:44] <nhaines> lotuspsychje: I do have an N5 but I don't use pin codes on my SIM.
[02:44] <gaducouch> okay so I don't have any problems booting or anything but my phone and sms don't work
[02:44] <gaducouch> well that's the point here
[02:45] <gaducouch> cuz I don't think i have either unless there's something i didn't understood
[02:45] <gaducouch> but it still doesn't work
[02:45] <nhaines> Oh, Bluetooth just doesn't work on N5.  So that's easy enough.
[02:45] <gaducouch> also i have multirom so it's a secondary boot partition
[02:45] <nhaines> What happens, does your N5 just not see your SIM?
[02:45] <gaducouch> it does see it though
[02:46] <nhaines> I use multirom too.  It shouldn't have an effect.
[02:46] <gaducouch> okay
[02:47] <gaducouch> can i make sure somehow with cm11 that my sim doesn't have a pin-code?
[02:47] <nhaines> I don't know.  I suspect you'd have to unlock your SIM each time you turned on your phone if it did.
[02:48] <nhaines> Can you press the VolUp and VolDown buttons together to take a screenshot and show us what the problem is?
[02:48] <gaducouch> sorry i can't since i have to install stuff to take screenshots though but i can't try to install those and take a screenshot
[02:49] <gaducouch> what would be relevant to screenshot the system info? or the sim card info?
[02:49] <gaducouch> and i can try i meant
[02:49] <gaducouch> looking it up
[02:50] <nhaines> You don't have to install anything to take a screenshot.
[02:51] <gaducouch> no? i thought i had to because of a nexus 5 issue i'll try right away then
[02:52] <gaducouch> ok it does work
[02:53] <gaducouch> what info could be relevant?
[02:53] <gaducouch> is there a terminal log you'd like to see?
[02:53] <gaducouch> oh and is there a terminal built-in? or i have to download an app for that purpose?
[02:56] <nhaines> You have to download the terminal now.
[02:56] <nhaines> I don't understand what your problem is.
[02:57] <gaducouch> meh thx a lot anyway! I' continue looking it up but i really don't need this this is more like a challenge to me right now cuz cm11 works perfeclty :) thx a lot again and thx for the patience have a nice one!
[02:58] <nhaines> You're welcome, but I literally mean I don't know what you're asking.  You have a SIM card with no PIN, and no way to remove the PIN.
[03:01] <gaducouch> holy shit i got it, it was in my carrier option all i did was check my carrier in the APN section (altough I don't really understand all of it, it somehow worked... XD)
[03:01] <gaducouch> cheers guys!
[03:05] <nhaines> Congrats!
[07:57] <dholbach> good morning
[08:44] <pitti> ogra_: guten Morgen, wie gehts?
[08:45] <pitti> ogra_: would you know how I could boot touch (in the emulator in particular) with temporarily modified kernel args?
[08:45] <ogra_> pitti, moin moin
[08:45] <ogra_> hmm, specifically for the emulator i dont know that
[08:45] <pitti> ogra_: there's obvioulsy no grub, but is there something in between fastboot and linux, or does fastboot directly boot the kernel?
[08:47] <Wellark> jgdx: hi!
[08:47] <ogra_> pitti, its just qemu but i dont know where/how the cmdline args are set for it
[08:48] <pitti> ogra_: ah, looks it migth all be hardcoded into /usr/bin/ubuntu-emulator indeed
[08:48] <Wellark> jgdx: was there a reason why this was not landed for rtm as well? http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/revision/1247
[08:48] <ogra_> ubuntu-emulator used to be a script so you could look that up in the past ... sadly it is go now
[08:48] <Wellark> jgdx: you seems to have approved the vivid MP
[08:51] <ogra_> ogra@anubis:~$ grep parameters .local/share/ubuntu-emulator/touch/hardware-qemu.ini
[08:51] <ogra_> kernel.parameters =  androidboot.hardware=goldfish clocksource=pit
[08:51] <ogra_> pitti, ^^^
[08:52] <pitti> !
[08:52]  * pitti hugs ogra_
[08:52] <pitti> didrocks: ^
[08:52]  * didrocks reads
[08:52] <didrocks> nice!
[08:56] <pitti> ogra_, didrocks: hm no, that doesn't seem to work
[08:59] <pitti> I can set a bogus/nonexisting kernel.path or add additional options to kernel.parameters, no change
[08:59] <ogra_> then i have to refer to sergiusens
[09:00] <ogra_> not sure if there is any other option you can set
[09:00] <pitti> ogra_: I'll poke around in the .img files
[09:00] <didrocks> :/
[09:00] <pitti> thanks so far!
[09:00] <ogra_> yeah, sorry i couldnt help
[09:02] <ogra_> LOL
[09:02] <ogra_> pitti, didrocks "ubuntu-emulator run --help"
[09:02] <pitti> $ strings sdcard.img |grep hardware=
[09:02] <pitti> cmdline = console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677
[09:02] <pitti> ogra_: *blush* that's clearly too easy!
[09:04] <didrocks> ;)
[09:04] <pitti> ogra_, didrocks: works like charm, danke!
[09:04] <ogra_> :D
[09:04] <didrocks> sweet
[09:16] <pitti> ogra_: /etc/init/android-tools-adbd.conf does "exec su - -c adbd" -- what is the su doing there? for changing the environment in some way, or starting PAM?
[09:18] <ogra_> pitti, making locales work
[09:19] <pitti> ogra_: oh, ok; thanks
[09:46] <JamesTait> Good morning all; happy Friday, and happy International Hot and Spicy Foods Day! :-D
[10:00] <pitti> ogra_: will we ever go back to the "non-flipped" model? I suppose not, i. e. /etc/init/lxc-android-boot.conf is obsolete?
[10:01] <ogra_> pitti, porters used to start from unflipped for the first porting step (to then switch to flipped)
[10:02] <pitti> ogra_: ah, ok; I was wondering if it's worth porting that to a systemd unit, or just drop it
[10:03] <ogra_> i guess dropping is fine for all the mount stuff ... keeping the copying of the udev rule somewhere as a saftey net wuld be nice though
[10:03] <pitti> ogra_: i. e. do that if there is no /android? sure, that sounds simple enough
[10:04] <pitti> ogra_: yep, I'll include that then
[10:04] <pitti> ogra_: btw, I'm quite optimistic -- didrocks and I got the emulator to boot with systemd all the way up to unity and stuff
[10:04] <pitti> automating that now :)
[10:04] <ogra_> nice
[10:06] <pitti> ogra_: we just need to provide a systemd unit for starting the container, and an equivalent for lightdm.override -- quite simple for now :)
[10:06] <pitti> (of course that's still missing lots of services like HERE and stuff, but one after the other)
[10:53] <uhhimhere> so reading up on mir on wiki suggests some controversy
[10:53] <uhhimhere> "In September 2013, an Intel developer removed XMir support from their video driver and wrote "We do not condone or support Canonical in the course of action they have chosen, and will not carry XMir patches upstream""
[10:54] <uhhimhere> why all the fuss?
[10:54] <uhhimhere> GPL vs MIT?
[10:54] <uhhimhere> wouldnt GPL be easier
[10:56] <uhhimhere> and "healthier"
[11:07] <didrocks> ogra_: I'm unsure to understand well android-tools-adbd.upstart
[11:07] <didrocks> ogra_: is that the developer mode as well and /sys/class/android_usb exists in developer mode?
[11:34] <ogra_> didrocks, developer mode consists of three parts that should never go out of sync (very very tricky to get that working race free) ... one is the android side that manages the usb_gadget config, one is adbd on the ubuntu side and there is the upstart property bridge making them talk to each other
[11:35] <ogra_> the upstart start condition is only true if the container is running *and* the property contains "adb"
[11:35] <ogra_> the /sys/class/android_usb check is for the emulator
[11:35] <didrocks> ogra_: my emulator instance doesn't have /sys/class/android_usb?
[11:36] <ogra_> (if the gadget device exists (which it indeed only does on real HW) it mounts a possible adb functionfs
[11:36] <ogra_> would be odd if it had that, yeah
[11:37] <didrocks> not sure to understand this gadget device part and mounting a possible adb functionfs (I see the job does that, but unsure what this means actually :))
[11:37] <ogra_> the gadget driver only supports two functions by default ... i.e. adb and mtp
[11:38] <didrocks> yeah, and you switch between one or the other
[11:38] <ogra_> some kernels have a functionfs for the driver that allows more features to run at the same time
[11:39] <ogra_> adb wont work at all on such kernels if the functionfs inst initalized since the in-container boot scripts need to configure it forst
[11:39] <didrocks> ah, making sense
[11:39] <ogra_> so the script checks sysfs if the ffs is enabled at all in kernel ... and then mounts it
[11:40] <didrocks> and that's why you store the developer mode flag inside the container?
[11:40] <ogra_> i store it in the property system as persistent property
[11:41] <ogra_> the property system is accessible from both sides ...
[11:41] <ogra_> android as well as ubuntu
[11:41] <ogra_> (properties with persistent. pürefix
[11:41] <ogra_> oops
[11:41] <ogra_> (properties with persistent. prefix are stored on disk)
[11:42] <didrocks> ogra_: this is the persist.sys.usb.config=*adb, right?
[11:42] <ogra_> yeah
[11:42] <uhhimhere> so why is there so much negativity around mir?
[11:43] <ogra_> usually either persist.sys.usb.config=adb or persist.sys.usb.config=mtp,adb in our case
[11:43] <didrocks> ogra_: just to sum up, it's the android container kernel which creates /sys/class/android_usb, visible on both side?
[11:43] <didrocks> (if the device has this capability)
[11:44] <ogra_> /sys/class/android_usb is created when the usb gadget driver is initialized
[11:44] <didrocks> and this driver is inside the container? (or I totally misunderstood the container part)
[11:44] <ogra_> there is no such thing like a "container kernel"
[11:44] <didrocks> yeah sorry, I mispoke my thought :)
[11:45] <ogra_> there is a kernel ... and it has drivers :)
[11:45] <ogra_> both systems make use of these drivers
[11:45] <ogra_> usually the driver for adb is compiled into the kernel (not as a module) on touch
[11:45] <ogra_> so on real devices you most likely always have that sysfs node
[11:46] <didrocks> interesting
[11:46] <ogra_> the whole configuration of the device is done by init.rc configs on the android side and controlled by the property system
[11:47] <ogra_> the whole daemon part is handled by the upstart job *based* on the property setting
[11:47] <didrocks> ok, I think I need to dive into this a little bit more, but now, at least, I have a good base :)
[11:47] <didrocks> thanks ogra_ for all the help :)
[11:48] <ogra_> np, ping me if you have more questions
[11:48] <didrocks> will certainly do! :)
[11:49] <ogra_> (it is easier to understand if you understand the android boot and how the init.rc files manage the boot ... but thats true for everything in touch where the container is somehow involved)
[11:50] <didrocks> ogra_: ok, will start from the init.rc then
[14:37] <pitti> ChickenCutlass: hey Michael, how are you?
[14:37] <ChickenCutlass> pitti: hey
[14:37] <pitti> ChickenCutlass: do you care about reviewing adding a systemd unit to powerd, or are you ok with doing that between didrocks and me?
[14:37] <pitti> https://code.launchpad.net/~pitti/powerd/systemd-unit/+merge/246715
[14:38] <ChickenCutlass> pitti: I trust you :).  But sure I will take a look
[14:38] <pitti> ChickenCutlass: it's a no-op for upstart, and I tested it in the emulator; I'll test the arm debs on the real phone of course
[14:38] <pitti> but it's simple enough
[14:38] <ChickenCutlass> ok great
[14:59] <pitti> sil2100: I wanted to add a silo for my powerd branch, but the job failed because powerd was already in another silo
[14:59] <pitti> sil2100: which is correct, it's in http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-000
[14:59] <pitti> sil2100: but it seems even though the job failed, it assigned a silo anyway: http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu&q=landing-001
[15:00] <pitti> sil2100: should this be "unassigned" again, to not block the silo?
[15:00] <sil2100> pitti: hey! I actually took and overwrote the warning, since we now allow having silos with conflicting components
[15:01] <sil2100> But well, we prefer if those are coordinated between landers
[15:01] <sil2100> pitti: so if you make sure that rsalveti is aware of your work and you coordinate with him who lands first, it's all ok
[15:01] <sil2100> The other person will have to rebuild after the first lands though
[15:02] <pitti> sil2100: (meeting, bbl, but I'm fine with postponing mine)
[15:07] <rsalveti> pitti: let me check
[15:08] <rsalveti> pitti: have one landing for vivid and should be doing yours in a few
[15:08] <rsalveti> so don't worry
[15:08] <pitti> rsalveti: right, thanks
[15:09] <pitti> sil2100: so I guess we should unassign mine?
[15:09] <rsalveti> no need
[15:09] <rsalveti> just need to coordinate the build & landing steps
[15:15] <sil2100> pitti: yeah, it can stay assigned and you can build when rsalveti lands his parts
[15:32] <jgdx> Wellark, I wonder if this is a bug in your connectivity code? https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1411714
[15:33] <jgdx> Wellark, incidentally, that was the thing I was pinging you for
[15:33] <jgdx> just remembered
[15:36] <kenvandine> jgdx, so your tech-switch branch, should really be tested on both mako and krillin right?
[15:36] <kenvandine> jgdx, just for regressions on mako
[15:36] <kenvandine> since it has only one modem
[15:36] <jgdx> kenvandine, yes
[15:37] <kenvandine> so on mako, i should test tech pref changes right?
[15:37] <jgdx> yes
[15:37] <kenvandine> anything else?
[15:40] <jgdx> kenvandine, I'm doing something on krillin right now, mind posting list-modems | grep has3G ?
[15:42] <kenvandine> jgdx, sure, one sec
[15:42] <kenvandine>         Has3G = 0
[15:42] <kenvandine>         Has3G = 1
[15:44] <jgdx> kenvandine, huh? mako?
[15:44] <pitti> sil2100: ok, if blocking the silo for a few days isn't hurting
[15:44] <pitti> sil2100: (sorry, was in a long meeting)
[15:45] <kenvandine> jgdx, whoops... that's krillin :)
[15:45] <kenvandine> jgdx, 5m on the mako
[15:45] <jgdx> PHEW
[15:50] <kenvandine> jgdx, returns nothing on mako
[15:51] <jgdx> ++
[16:00] <ogra_> dholbach, HÄÄÄPPIE BÖÖÖRSDÄÄÄIII
[16:00] <dholbach> thanks ogra_ :))
[16:06] <kenvandine> jgdx, it'll be a little bit before i get to testing that branch, my krillin is busy running the full AP suite for silo 18 :)
[16:06] <kenvandine> i really wish our tests were faster
[16:08] <jgdx> seconed
[16:08] <jgdx> Ursinha, I second that
[16:08] <jgdx> Ursinha, tab fail, sorry
[16:13] <jgdx> Wellark, seems connectivity has nothing to do with it. Updated the bug.
[16:15] <Ursinha> jgdx: :)
[16:15] <jgdx> :)
[16:23] <phun> Hey, I'd like to know how to get into developing for the Ubuntu Touch platform via Launchpad?
[16:33] <jgdx> kenvandine, just did some mako testing using the tech switch package: looks good
[16:34] <jgdx> kenvandine, now, some krillin single sim testing
[16:34] <kenvandine> jgdx, ok, cool
[16:42] <gcollura> Elleo, ping
[16:42] <Elleo> gcollura: pong?
[16:43] <gcollura> Elleo, do you remember https://code.launchpad.net/~gcollura/content-hub/fix-1384490/+merge/240156 ? can I make a branch with the fix for the labels color (and header background for vivid ui-toolkit), since you're just want the background to always be plain white? :)
[16:44] <Elleo> gcollura: ah yeah, sorry, I was meaning to get back to that after the break, but let it slip
[16:45] <Elleo> kenvandine: How do you feel about exposing colour settings for the content peer picker? I see the mhall119 has already done some hacks in his reddit app to set the colour, so I figure it might be best to just let people do that reliably than have them implement hacks around it?
[16:45] <MasterAwesome> I have doubts regarding the build process
[16:45] <Elleo> gcollura: I'm thinking now that maybe we should just expose a few colour properties for the background, but lets see what ken's thoughts are
[16:46] <MasterAwesome> i keep getting no rule to make target .../extract_elf_ramdisk which is required by boot.img
[16:46] <MasterAwesome> but i have created an android.mk file
[16:46] <mhall119> Elleo: all I needed was 2 properties, but really you can probably expose just one and use Qt.darker/lighter to produce the other
[16:46] <MasterAwesome> and i included it in the yuga.mk
[16:46] <mhall119> Elleo: or just make it transparent?
[16:47] <gcollura> mhall119, Elleo in the current MP branch I'm setting the background as the same as the app
[16:47] <Elleo> mhall119: transparent could work
[16:48] <Elleo> gcollura: that doesn't set it the same as the app unfortunately, that sets it to the theme colour (which gets determined by the app colour, but isn't the same)
[16:48] <gcollura> mhall119, like this? http://bazaar.launchpad.net/~gcollura/content-hub/fix-1384490/revision/161
[16:49] <gcollura> Elleo, ok
[16:49] <Elleo> gcollura: I'll have a play with making it transparent on monday and let you know how it goes, otherwise I'd be infavour of exposing colour properties if kenvandine's okay with it
[16:50] <Elleo> gcollura: making the background rectangle transparent, not the white apps rectangle
[16:50] <mhall119> thanks Elleo
[16:50] <gcollura> Elleo, ok
[16:51] <Elleo> the main issue would be whether it might cause any issues for apps already using it
[16:51] <mhall119> Elleo: if the apps rectangle won't be transparent, we should add a color property to change it
[16:51] <Elleo> I think really we need to expose colours
[16:51] <Elleo> making it transparent seems risky, since some apps aren't embedding it in pages they're embedding it in dialogs
[16:52] <mhall119> I'd be happy with that, then you can default to what it is now and won't break anybody's app
[16:52] <Elleo> yeah
[16:52] <mhall119> I just want to remove that really ugly hack from my app :)
[16:52] <Elleo> heh
[16:52] <mhall119> it (rightfully) pains me to see it in there
[16:53] <gcollura> Elleo, most apps are using ContentPeerPicker this way I think http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/src/qml/PictureImport.qml#L47
[16:53] <gcollura> Rectangle should be white by default
[16:53] <Elleo> gcollura: we can't guarantee all apps are though
[16:56] <gcollura> Elleo, ok, let me know how you will tackle this issue as soon as you decide :)
[16:57] <Elleo> gcollura: will do
[16:57] <gcollura> thanks
[16:58] <Elleo> gcollura: I'll put it to the top of my list for Monday, assuming I can get the bug I'm working on now sorted before EOD
[16:58] <kenvandine> Elleo, that's fine with me
[16:58] <Elleo> kenvandine: okay, cool
[16:58] <kenvandine> as long as the app grid isn't
[16:58] <kenvandine> that could be hard to read
[16:59] <Elleo> kenvandine: keep the app grid white at all times?
[16:59] <kenvandine> i think so
[16:59] <kenvandine> well... i guess color properties would be ok
[16:59] <Elleo> kenvandine: we could be using the luminence tools to make sure the font is always readable (like the toolkit does)
[16:59] <kenvandine> if a developer really wants to make it hard to read, they can :)
[16:59] <Elleo> heh
[16:59] <kenvandine> that helps
[16:59] <kenvandine> play around with it :)
[17:00] <Elleo> okay
[17:08] <kenvandine> jgdx, should changing has3G change which sim to use for data?
[17:08] <kenvandine> jgdx, i set sim1 to 3g, and it was already set as the sim to use for data
[17:08] <kenvandine> after the switch, it changed to sim2 for data
[17:10] <cyphermox> nuclearbob: hey hey
[17:11] <nuclearbob> cyphermox: ahoy
[17:11] <kenvandine> jgdx, the sim change for data happened like a full minute after the 3g switch
[17:11] <cyphermox> nuclearbob: power management metering is coming up again, do we have a way to get this in daily testing?
[17:11] <cyphermox> ie. I'm thinking wifi power, battery usage and such
[17:11] <nuclearbob> cyphermox: there's a power meter on its way to me, when it gets here I'll be automating power measurements on it
[17:13] <cyphermox> ah, I guess yeah the lack of tools can't help
[17:13] <cyphermox> do you know when we'll receive it?
[17:13] <nuclearbob> should be early next week
[17:14] <cyphermox> great
[17:16] <kenvandine> jgdx, oh... this might have been my fault
[17:16]  * kenvandine reboots
[17:16] <jgdx> kenvandine, /me reads
[17:16] <jgdx> yeah, after upgrading ofono you'll need a reboot
[17:16] <kenvandine> jgdx, for t-mobile i need to force it to not use ipv6 after wiping
[17:16] <kenvandine> i forgot to do that
[17:16] <kenvandine> do i need to upgrade ofono?
[17:17] <kenvandine> i thought the right ofono was in vivid already
[17:17] <jgdx> I don't think so, the plan is to land them together
[17:18] <kenvandine> so where do i get the right ofono?
[17:18] <kenvandine> i thought landing together was for the rtm landing
[17:19] <jgdx> kenvandine, maybe it is
[17:19] <jgdx> right, https://code.launchpad.net/~phablet-team/ofono/vivid-update-1/+merge/242287
[17:20] <kenvandine> seems better now that i worked around the ipv6 problem
[17:21] <kenvandine> jgdx, but... there is a bit of a delay in updating the UI after the UI comes back
[17:21] <jgdx> kenvandine, if you hit 1411714, maybe just mark as affecting you too
[17:21] <kenvandine> when the spinner stops, it says data is off
[17:21] <jgdx> kenvandine, yeah… not sure what to do about that
[17:21] <kenvandine> then 10 seconds or so later it switches
[17:21] <jgdx> we stop spinning when present is true.. if we wait for connman, we could wait forever
[17:22] <jgdx> (data might be off)
[17:22] <kenvandine> right
[17:22] <kenvandine> could you wait for connman if data was on when the switch started?
[17:22] <kenvandine> i guess if it fails to register that could happen too
[17:23] <jgdx> hm, we could
[17:24] <jgdx> I have a thing now, but I'll be back later
[17:24] <jgdx> bad timing
[17:27] <julienrbt> Hello
[17:27] <julienrbt> I've recently bought a Nexus 4 and installed Ubuntu Touch
[17:27] <julienrbt> question: the nfc works?
[17:30] <ogra_> julienrbt, i dont think it does yet ...
[17:31] <julienrbt> ok
[17:31] <ogra_> iirc mzanetti took a glance once
[17:31] <ogra_> not sure he had the time to actually implement anything for ti yet
[17:31] <ogra_> *it
[17:31] <mzanetti> nah, haven't gotten anywhere
[17:32] <davmor2> mzanetti: man you been slacking off and only working 24hours a day instead of 48 again?
[17:34] <mzanetti> ... sort of, yes
[19:01] <rezaa> Hi
[19:02] <rezaa> I Can Install ubuntu Tuch For Sony Xperia Z Ultra
[19:11] <julienrbt> rezaa https://wiki.ubuntu.com/Touch/Devices :)
[19:11] <julienrbt> if it is not available: https://wiki.ubuntu.com/Touch/Porting :D
[19:38] <kenvandine> mandel, confirmed, your rtm backport for fix-pause works :)
[19:42] <kenvandine> mandel, i top approved, i see you had a silo request already, so i leave that with you
[19:42] <kenvandine> mandel, thanks again!
[19:47] <mandel> kenvandine, awesome
[20:13] <jgdx> kenvandine, lol, pass on a ap run
[20:13] <jgdx> (on jenkins)
[20:13] <jgdx> good job!
[20:29] <kenvandine> jgdx, :-D
[20:30] <touch> what tablets are good for Full desktop convergence
[20:31] <touch> what tablets are good for Full desktop convergence
[20:32] <jgdx> !devices | touch
[20:32] <ZacharyIgielman> BUG: I have a weekday alarm which should repeat everyday but now turns off after each alarm so I have to turn it back on everyday after the alarm. Anyone else getting this?
[20:33] <jgdx> kenvandine, ok that I land https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/rtm-1388044/+merge/244878 and https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/rtm-1390557/+merge/242121 monday?
[20:33] <kenvandine> jgdx, please do!
[20:33] <jgdx> kenvandine, I'm looking into your comment.
[20:33] <kenvandine> thx
[20:34] <kenvandine> jgdx, if you could, land other rtm branches that are ready and ack'd for ww03 or ww05 :)
[20:34] <kenvandine> jgdx, i'll be out monday
[20:35] <jgdx> kenvandine, roger
[20:35] <jgdx> kenvandine, for how long are you on tonight?
[20:35] <kenvandine> jgdx, the fix-pause branch is in an rtm silo building now
[20:35] <jgdx> k
[20:35] <kenvandine> hopefully that'll get cleared out before you are ready to land those
[20:35] <kenvandine> 2 more hours
[20:35] <kenvandine> maybe 1.5 hours :)
[20:35] <kenvandine> it is friday
[20:36] <kenvandine> jgdx, what do you need?
[20:36] <kenvandine> maybe another review of tech-switch?
[20:37] <jgdx> kenvandine, yea
[20:37] <kenvandine> if i'm afk by the time it's ready, i'll likely look at it later tonight
[20:38] <jgdx> thanks
[20:39] <kenvandine> jgdx, np
[20:40] <nik90> ZacharyIgielman: that has been fixed in the latest rtm promoted image today
[20:40] <nik90> ZacharyIgielman: btw it just appears turned off, but it works as expected in case you still have the bug
[20:41] <ZacharyIgielman> So it has been fixed? I don't have to report it?
[20:43] <nik90> ZacharyIgielman: yup it has been fixed in the latest promoted image #14
[20:43] <jgdx> kenvandine, problem: connMan.powered both come back false after the reboot
[20:43] <ZacharyIgielman> Fantastic thanks! Where can I find the release notes for each image?
[20:43] <nik90> ZacharyIgielman: here's the bug report that was submitted before https://bugs.launchpad.net/ubuntu-clock-app/+bug/1411171
[20:44] <nik90> ZacharyIgielman: not sure since there are a couple of images before they promote one .. so one has to combine the changelog for a couple of images
[20:45] <ahoneybun> does anyone have working mms?
[20:46] <ZacharyIgielman> Thanks guys :D
[20:46] <kenvandine> jgdx, i guess that makes sense
[20:46] <kenvandine> and we have to wait for them to come up
[20:46] <jgdx> kenvandine, not if the interfaces isn't there, which it is not
[20:46] <kenvandine> jgdx, do we have to display "off" for data access in that case though?
[20:46] <jgdx> I think it's a bug in libqofono, and I'll file it.
[20:46] <kenvandine> ah
[20:46] <kenvandine> ok
[20:46] <jgdx> but I can wait for the interface to come back up :)
[20:47] <jgdx> so yay, most likely fixable
[20:49] <kenvandine> cool
[20:50] <touch> what tablets are good for Full desktop convergence
[20:51] <nhaines> touch: none.
[20:51] <nhaines> Check back after 16.10.
[20:54] <touch> nhaines:what do you mean
[20:55] <touch> none
[20:55] <nhaines> touch: full desktop convergence doesn't exist in Ubuntu.
[20:55] <nhaines> So one will need to wait until the feature is developed before we will know which hardware it will run on.
[21:07] <dobey> ahoneybun: works fine for me
[21:08] <ahoneybun> dobey, what settings do you have for apn and what carrier?
[21:08] <dobey> ahoneybun: if you have t-mo us (or another carrier that defaults to inet6 you need to change the apn to use inet)
[21:09] <ahoneybun> I have cricket (at&t) dobey
[21:09] <ahoneybun> the apn says ndo
[21:10] <dobey> ahoneybun: https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1324157
[21:11] <dobey> not sure if that will help though
[21:11] <ahoneybun> dobey, not sure about receiving, but I can;t send
[21:11] <dobey> https://bugs.launchpad.net/ubuntu/+source/android-src-vendor/+bug/1351434 might help too
[21:12] <dobey> ahoneybun: i've had problems sending when network connection was finicky too
[21:12] <dobey> switching between wifi/3g and such
[21:12] <ahoneybun> dobey, I have the apn as ndo for internet but not sure what to do with the mms apn
[21:12] <ahoneybun> in android the apn handles both
[21:13] <dobey> i don't know what ndo is
[21:14] <ahoneybun> well cricket says it is a the apn: https://www.cricketwireless.com/support/apps-and-services/bring-your-own-device-byod/customer/bring-your-own-android.htmlhttps://www.cricketwireless.com/support/apps-and-services/bring-your-own-device-byod/customer/bring-your-own-android.html
[21:14] <ahoneybun> crap
[21:18] <dobey> ahoneybun: does 3g data work?
[21:18] <ahoneybun> yea
[21:19] <ahoneybun> I set the mms apn as custom but I can't switch it to same as the internet apn
[21:19] <ahoneybun> there is a list to select it but I can't change
[21:23] <dobey> not sure
[21:23] <dobey> jgdx: ^^ any ideas, if you're still around?
[21:24] <jgdx> dobey, not really. Wellark ^
[21:25] <ahoneybun> bbl
[21:46] <jgdx> kenvandine, it looks like the connection manager is pondering for ~10 secs before telling libqofono that sim n is using data. So right now I don't have a solution. Other than maybe waiting 10 extra seconds.
[21:47] <jgdx> awe_, ping
[21:48] <awe_> jgdx, pong
[21:51] <kenvandine> jgdx, ugly
[21:51] <jgdx> awe_, we're having a problem in u-s-s after a modem reboot. When the ConnectionManager interface is re-created (reported to exist by ModemInterface), it spends ~10 seconds figuring out that one of the SIMs had "Powered" set to true before the reboot.
[21:54] <jgdx> awe_, I'm not sure where the lag is. Ofono-monitor is not reporting exactly when the ConnectionManager powered setting changes, so it could be libqofono's fault. What do you think?
[21:54] <awe_> monitor-ofono should show all the prop changes...
[21:55] <awe_> it may be that it takes that long for the ConnectionManager iface to get re-created after the reset
[21:56] <awe_> I can try on my end if you'd like?  I think your best bet is to send an email to me & Alfonso with the details
[21:57] <jgdx> awe_, that'd be great. I see Attached and Bearer events, but not Powered. This is after the reboot, not under normal conditions, then I see Powered as well.
[21:59] <jgdx> hm, Powered is set to false on has3G = true. I missed that.
[21:59] <jgdx> Noskcaj, that's on Modem
[21:59] <jgdx> Noskcaj, I mean
[22:00] <jgdx> aaaaahgh
[22:00] <awe_> OK.  The devil's in the details... ;)-
[22:00] <awe_> if you need me to run the scenario, I will
[22:01] <jgdx> awe_, I dont' know what's best considering the plan. It's seems to be an ofono bug and I don't know where that leaves us.
[22:01] <jgdx> awe_, I'm going to send alfonso an email asap.
[22:01] <awe_> ok. Please send the email, and I can give it a try over the weekend.
[22:02] <jgdx> cool, thanks
[22:02] <awe_> np
[22:12] <SturmFlut> I'm building a cheap network scanner app and my current approach is to run /bin/ping on the phone using QProcess. The app works on the desktop, but fails on the phone with error type QProcess::FailedToStart. Is QProcess generally unavailable on the phone or do I need additional apparmor privileges besides "networking"?
[22:13] <dobey> SturmFlut: you're not allowed to run processes that aren't part of your own app, under confinement
[22:22] <SturmFlut> dobey: I see, thanks. On to the next approach...