[02:57] <uhhimhere> https://translate.googleusercontent.com/translate_c?depth=1&hl=en&ie=UTF8&prev=_t&rurl=translate.google.com&sl=auto&tl=en&u=http://marsohod.org/index.php/projects/marsohod2&usg=ALkJrhi6x9T3vp7vZdyI420CH-A-hvo5-Q
[04:26] <mhall119> dobey: davidcalle is going to be working on the porting guide
[04:27] <mhall119> kgunn: not sure what you mean
[08:25] <dholbach> good morning
[09:48] <jgdx> Wellark, ping
[09:48] <jgdx> Wellark, seeing http://pastebin.ubuntu.com/9754790/
[09:49] <jgdx> Wellark, from calling UnlockAllModems from u-s-s.
[09:52] <galen104> hello, is someone here using ubuntu touch on a non ufficially supported smartphone? If so, which one?
[09:53] <jgdx> dobey, are you running it on the nexus 5? ^
[09:53] <JamesTait> Good morning all; happy Super Bowl I Anniverary Day! :-P
[09:54] <JamesTait> Hey jgdx! o/
[09:54] <jgdx> \o JamesTait
[09:54] <jgdx> :)
[09:54] <JamesTait> How are things?
[09:54] <jgdx> Things are good! How's Jay in the UK?
[09:55] <JamesTait> Not too bad now, thanks. :)  Just about getting back into the swing of things!
[09:56] <jgdx> Great:) Speaking of swing, how's Callum's golf swing doing? :)
[09:57] <jgdx> or was it Connagh?
[09:58] <JamesTait> jgdx, both now! Callum started lessons late-ish last year.  They're doing well, Connagh got most improved player at the Derbyshire Futures Tour.
[09:59] <jgdx> JamesTait, cool :)
[10:02] <JamesTait> jgdx, how are the studies going?
[10:04] <jgdx> JamesTait, it's really fun and very useful.
[10:08] <matv1> so I am not being able to update mako r163, but i should be able to do so from the pc using adb shell. Is that it?
[10:21] <dpm> morning sil2100, is this commit needed, shall we approve or reject it? https://code.launchpad.net/~sil2100/reminders-app/empty_commit/+merge/242091
[10:25] <dholbach> can somebody please retrigger a build in jenkins for https://code.launchpad.net/~dholbach/ubuntu-html5-theme/fix-doc-typo/+merge/246425?
[10:26] <sil2100> dpm: let me take a look, it seems to be some left-over from CI Train releases I think
[10:29] <dpm> thanks sil2100
[11:40] <mardy> dobey: hi! I just created this: https://code.launchpad.net/~mardy/ubuntuone-credentials/lp1376445-migration/+merge/246553
[13:27] <nik90_> charles: ping
[14:14] <dobey> jgdx: yes i am
[14:15] <dobey> mardy: hmm, i wonder if migration should perhaps be a separate bug
[14:19] <mardy> dobey: I think it's kind of the same; it fixes the issue for old accounts
[15:03] <sergiusens> Elleo: I need a spanglish setting for the keyboard, and maybe a portuñol one :-P
[15:05] <Elleo> sergiusens: heh
[15:27] <kenvandine> mandel, do you think there will be any conflicts between your fix-pause branch and the fix-network and fix-network-errors branches?
[15:27] <charles> nik90_: pong
[15:28] <mandel> kenvandine, there should not, but I can check for you, let me finish a test with mms and I'll take a look
[15:31] <kenvandine> mandel, thx
[15:31] <kenvandine> mandel, fix-pause is building in silo 26
[15:32] <mandel> kenvandine, awesome!
[15:33] <nik90_> charles: hey, I was just about to inform you about bug 1411171 but I see you already assigned it to yourself :)
[15:34] <charles> nik90_, yeah. I haven't had a chance to triage it yet but it sounds like there must be a bug in the code that recognizes the alarm as repeating
[15:35] <charles> ugly
[15:35] <nik90_> charles: btw the alarms in vivid at the moment is broken (alarms cannot be edited and other minor issues)...so it would be best to target your fix to rtm directly for better testing
[15:35] <charles> nik90_, thanks for the heads up. will do
[17:16] <kenvandine> elopio, can you provide any insight into this error?
[17:16] <kenvandine> https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-vivid-mako/713/testReport/junit/ubuntu_system_settings.tests.test_reset/ResetTestCase/test_reset_launcher/
[17:17] <kenvandine> elopio, that just started happening in vivid, but it's consistent
[17:21] <davmor2> kenvandine: something broke it produced that error ;)
[17:22] <kenvandine> davmor2, that's very enlightening :)
[17:22] <kenvandine> i was thinking the sdk or autopilot, but neither seems to have changed
[17:22] <kenvandine> just started happening yesterday
[17:23] <kenvandine> the same code passes on utopic desktop and rtm device
[17:23] <kenvandine> only fails on vivid
[17:23] <kenvandine> so i'm pretty sure it's something outside of settings that broke it
[17:24] <kenvandine> but i'd suspect it would be related to testing the Dialog, so we'd see other projects failing too
[17:26] <elopio> kenvandine: that's because of bug https://bugs.launchpad.net/autopilot/+bug/1350532
[17:27] <elopio> kenvandine: the toolkit released a new dialog custom proxy object, so you need to add this workaround
[17:27] <elopio> kenvandine: https://code.launchpad.net/~canonical-platform-qa/sudoku-app/autopilot-workaround_dialog/+merge/246255
[17:28] <elopio> that is, make sure that the Dialog class matches none of your components.
[17:28] <kenvandine> oh... thanks!
[17:28] <kenvandine> elopio, i knew someone had to of seen this :)
[17:29] <elopio> kenvandine: sorry about that. It's something we are still trying to handle bettter.
[17:29] <elopio> and I thought the toolkit wasn't going to be released before the tests were updated. There is something wrong with the release gates there.
[17:37] <kenvandine> elopio, mind reviewing my branch?
[17:38] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/autopilot_workaround_dialog/+merge/246612
[17:47] <mhall119> twice now I've had Contacts and Messaging apps fail to load my contacts, is there a bug for this?
[17:48] <mhall119> messaging app eventually times out and just displays phone numbers
[17:48] <mhall119> address-book times out and says I have no contacts :(
[17:51] <mhall119> after rebooting all my contacts are visible and everything works
[17:51] <mhall119> so I don't know if EDS has crashed, or the apps just can't connect to it, or what
[17:58] <elopio> kenvandine: looks good. But please confirm that the tests are all passing before landing :)
[17:58] <kenvandine> i did :)
[17:58] <kenvandine> they passed on my vivid device
[17:58] <kenvandine> which was failing before
[17:59] <elopio> kenvandine: ok, but I meant on CI.
[17:59] <kenvandine> sure, i'm waiting on that
[19:13] <charles> nik90_, ping
[19:37] <nik90_> charles: pong
[19:38] <charles> nik90_, question about clock app, in one of datetime's manual tests it says "NOTE: due to a refresh bug in clock-app you may need to refresh its alarms page (by swapping back to the main page, then the alarm page again, this is tracked in #1362341) in order to see the alarm change from enabled to disabled."
[19:39] <charles> is that still broken?
[19:39] <nik90_> charles: yes, but I discussed this with popey and will have a MP fix for it tomorrow.
[19:39] <charles> nik90_, cool :)
[19:39] <nik90_> :)
[19:53] <dobey> so, the bug in system updates that caused updates to be brkoen. was that something in system-image-cli that caused it to always time out?
[19:55] <dobey> hmm, what makes it so incredibly slow to switch between 3g/wifi?
[19:57] <dobey> 0.0.0.0         0.0.0.0         255.255.255.255 UH    0      0        0 rmnet0
[19:57] <dobey> i guess that doesn't help
[20:01] <dobey> phablet@ubuntu-phablet:~$ sudo route del -net 0.0.0.0 netmask 255.255.255.0 dev rmnet0
[20:01] <dobey> SIOCDELRT: No such process
[20:02] <dobey> oh, right, .255
[20:02] <dobey> but still. and deleting that route didn't seem to help either :-/
[20:05] <kgunn> kenvandine: just checkin' before i log a bug...on a nexus4 vivid from y'day, i can't seem to select another screen timeout (stuck on 1 minute)
[20:05] <kgunn> known bug ?
[20:06] <kenvandine> kgunn, not known...
[20:07] <kenvandine> kgunn, wfm with image 66
[20:08] <kgunn> kenvandine: hmmm....i'm on 64
[20:09] <kgunn> rebooting to try again
[20:09] <kenvandine> kgunn, none of that code has changed in ages, i'd be surprised if it was broken
[20:09] <kenvandine> perhaps something is out of whack
[20:10] <kgunn> kenvandine: does "developer mode" effect that setting?
[20:10] <kenvandine> nope
[20:10] <kenvandine> i'm just thinking the setting might be failing to save in gsettings
[20:10] <kenvandine> look in the upstart logs for it perhaps
[20:18] <beuno> anyone with a phone around?
[20:18] <beuno> there's a new app called "hello"
[20:19] <beuno> I'd much appreciate someone test install it
[20:19] <beuno> davmor2, hi!
[20:19] <davmor2> beuno: no I don't trust you it's going to break my phone
[20:20] <beuno> it's all cool man, confinemnt
[20:20] <davmor2> beuno: hello canonical free?
[20:20] <beuno> just enter your credit card when it asks, the phone will keep it safe
[20:21] <beuno> davmor2, it's just hello, has a yellow icon
[20:21] <davmor2> beuno: there is Hello-world with a yellow icon and hello that has an ubuntu icon
[20:22] <davmor2> beuno: one is by you the other is by canonical
[20:22] <pmcgowan>   beuno tried to send you a message and got unknown nick
[20:24] <nimmersatt> hello, does ubuntu have plans on hybrids (tablet-laptops)?
[20:25] <nhaines> nimmersatt: yes, it's called Unity 8.
[20:25] <davmor2> beuno: http://people.canonical.com/~davmor2/hello.png  which one?
[20:25] <nhaines> And it's just going to be a feature of Ubuntu.
[20:25] <nimmersatt> yeah i know, thats awesome
[20:26] <nimmersatt> so for instance,  when I have a keyboard and mouse plugged in, I can use the desktop version and if not, I can use it as tablet?
[20:27] <kgunn> kenvandine: figured it out....my home dir was full
[20:27] <kgunn> deleting some stuff allowed me to change it
[20:27] <nhaines> nimmersatt: yup.
[20:27] <beuno> davmor2, mine
[20:27] <kgunn> ...interesting, i also couldn't see or change any of my wifi settings
[20:28] <pmcgowan> kgunn, thats not too good
[20:28] <kgunn> pmcgowan: yeah, wonder should we warn the user when getting close to consuming home
[20:28] <davmor2> beuno: it install so tap me hello I tap it is says world! and then does nothing even though it still say tap me
[20:29] <beuno> davmor2, perfect, than you!
[20:29] <nimmersatt> nhaines: thanks. do you know of any cool hybrid laplets?
[20:31] <nhaines> No, unfortunately not!  With no real interesting Linux support for hybrids, I'm not interested.  When Ubuntu develops good hybrid support, that's when I'll start.
[20:32] <nimmersatt> Thanks a lot, thats my plan, too
[20:43] <rickspencer3> hey all, so I am looking at the bootloader screen of my flo
[20:43] <rickspencer3> when I try to flash it, ubuntu-device-flash says: 2015/01/15 15:43:02 Expecting the device to expose an adb interface...
[20:43] <rickspencer3> device cannot be detected over adb
[20:43] <rickspencer3> :(
[20:44] <dobey> rickspencer3: you need to be in recovery for adb. in bootloader you have to use --bootstrap option (which i think will also delete data)
[20:44] <rickspencer3> dobey, is recovery where the android logo is on his back with his case open
[20:45] <rickspencer3> and it says Start real big at the top?
[20:45] <dobey> no. use volume to select recovery and then hit power to boot to recovery
[20:45] <dobey> you're in the bootloader now
[20:45] <kenvandine> kgunn, no fun
[20:46]  * rickspencer3 tries
[20:46] <rickspencer3> same deal
[20:46] <rickspencer3> 2015/01/15 15:46:21 Expecting the device to expose an adb interface...
[20:46] <rickspencer3> "
[20:46] <rickspencer3> :/
[20:47] <dobey> check the cable? if you're in recovery you should be able to adb to the device
[20:48] <rickspencer3> dobey, oh, adb shell works
[20:48] <rickspencer3> dobey, does this make sense?
[20:48] <rickspencer3> rick@rick:~$ ubuntu-device-flash touch --bootstrap
[20:48] <rickspencer3> 2015/01/15 15:48:21 Expecting the device to be in the bootloader... waiting
[20:48] <nhaines> rickspencer3: well, it means you're not in the bootloader.
[20:49] <rickspencer3> nhaines, right, dobey told me to go to recovery :)
[20:50] <dobey> i said you have to boot to recovery OR use --bootstrap in the bootloader
[20:50] <rickspencer3> dobey, oh
[20:50] <rickspencer3> sorry
[20:50] <dobey> :)
[20:51] <rickspencer3> so, weirdly, adb shell does not work in bootloader mode
[20:51] <dobey> no, that's normal/expected
[20:51] <dobey> bootloader isn't running an OS
[20:51] <rickspencer3> dobey, well, --bootstrap didn't work, it said it wanted adb shell, I think
[20:51] <rickspencer3> let me futz a bit more
[20:52] <dobey> if you're in recovery, just do "ubuntu-device-flash"
[20:52] <dobey> and you'll get stable
[20:52] <rickspencer3> and it
[20:52] <rickspencer3> dang it
[20:52] <rickspencer3> dobey, well, adb shell doesn't work when I am booted into Ubuntu on the device, either
[20:52] <rickspencer3> so, something is busted busted
[20:52] <dobey> do you have dev mode enabled?
[20:53] <rickspencer3> dobey, well, I do in the UI
[20:53] <rickspencer3> but I can't test with adb shell, of course ;)
[20:53] <dobey> rickspencer3: i had enabled it one time, but adb didn't work, then when i went back into settings it somehow was disabled. so exit system settings then go check again, just to be sure :)
[20:54] <rickspencer3> dobey, yeah, I've done that like 100 times over the last week
[20:54]  * rickspencer3 tries disabling and enabling again
[20:54] <rickspencer3> d'oh
[20:54] <rickspencer3> it worked that time
[20:54] <dobey> heh
[20:55] <dobey> :)
[20:55]  * rickspencer3 bangs head on desk
[20:55] <rickspencer3> Failed to locate latest image information
[20:55] <rickspencer3> never had this much trouble before
[20:59] <dobey> hmm
[20:59] <dobey> rickspencer3: what image are you currently running?
[20:59] <rickspencer3> 15.04 r1
[21:00] <dobey> oh ok. i guess that's not the same issue that davmor2 mailed about then :)
[21:02] <rickspencer3> I get the same error when I try --bootstrap from the boot loader
[21:04] <rsalveti> that error is new
[21:04] <rsalveti> trying to flash latest vivid with --bootstrap on flo?
[21:04] <rickspencer3> rsalveti, yeah
[21:04] <rsalveti> let me try to remove the dust from mine
[21:04] <rickspencer3> rsalveti, well, I've been trying off and on to do this for a couple of weeks, actually
[21:06] <rsalveti> 161     //If we reached this point, that means we haven't found the image we were looking for.
[21:06] <rsalveti> 162     if revision == 0 {
[21:06] <rsalveti> 163         err = errors.New("Failed to locate latest image information")
[21:06] <rsalveti> yeah, that should mean that I'm probably able to get the same error
[21:06] <rsalveti> rickspencer3: what channel? using --revision?
[21:07] <rickspencer3> rsalveti, this is my latest incantation:
[21:07] <rickspencer3> ubuntu-device-flash touch --bootstrap --device=flo
[21:07] <rickspencer3> I'm in the bootloader
[21:07] <rickspencer3> but I got the same error when adb shelled into the running Ubuntu, with just ubuntu-device-flash
[21:07] <rsalveti> do you get the same error when giving --channel=ubuntu-touch/vivid-proposed ?
[21:07] <rickspencer3> I didn't try
[21:07] <dobey> rickspencer3: oh, there are no stable images for flo
[21:08] <rickspencer3> ah
[21:08] <dobey> rickspencer3: so you get the "no images found" error
[21:08] <rsalveti> yeah, that might be it
[21:08] <rsalveti> don't remember if we ever promoted something for it
[21:08] <rickspencer3> working now
[21:08] <dobey> if you use vivid-proposed you'll get something
[21:08] <rickspencer3> \o/
[21:08] <rsalveti> and what would be the default channel used (should be stable)
[21:08] <rsalveti> awesome
[21:08] <rickspencer3> well, when I specified a channel, I always specified just "stable"
[21:08] <rickspencer3> :/
[21:09] <dobey> bug people to promote something on flo :)
[21:09]  * rickspencer3 shrugs
[21:09] <rsalveti> we should be focusing more on vivid really soon
[21:09] <rsalveti> which should help on that front
[21:09] <rickspencer3> maybe someday ubuntu-device-flash can have a fall back if stable is not available
[21:09] <rsalveti> yeah
[21:10] <rickspencer3> it's all fine
[21:10] <dobey> 14.09-proposed has flo images. i think they just haven't been getting all the testing like the phones have
[21:10] <rickspencer3> I'll be interested to see how well it is working when done
[21:10] <rickspencer3> it's nice to have a tablet at home
[21:10] <rickspencer3> especially one that runs my apps ;)
[21:10] <dobey> well, you aren't the first one who had a problem with stable on flo not having an image :)
[21:11] <dobey> but yeah, at least you got it flashing now
[21:14] <rickspencer3> just as the network in my co-working space slows to a crawl
[21:14] <dobey> heh
[21:18] <sergiusens> rickspencer3: rsalveti stable point to ubuntu-rtm
[21:18] <sergiusens> flo doesn't exist there
[21:18] <rickspencer3> aha
[21:18] <rsalveti> oh, there you go
[21:19] <rickspencer3> *sigh*
[21:19] <rickspencer3> so slooooow
[21:19] <sergiusens> rickspencer3: I'm always under the dilema of thinking why a tablet if my phone does everything...
[21:19] <rickspencer3> sergiusens, I like it because the screen is bigger
[21:20] <rickspencer3> I use it instead of my laptop, not instead of my phone, if that makes sense
[21:20] <dobey> my laptop has a smaller screen than the latest phones
[21:20] <rickspencer3> somehow I think dobey might be pulling my leg
[21:21] <Amun-Ra> tablet, because it has a bigger screen
[21:21] <dobey> rickspencer3: my fujitsu u820 is literally smaller than a nexus 6, and has longer battery life :)
[21:27] <julianwi> can ubuntu touch be build on a cm11 base
[22:01] <Adrian47> dobey: i tried now with AOSP kernel,but still get the same error
[22:06] <dobey> Adrian47: ok. like i said, i don't know what to tell you. i haven't ported ubuntu to other devices, so i don't know the process. all i know is that the porting guide is in terrible need of being updated :)
[22:09] <julianwi> can I build ubuntu touch on a cm11 base? Or is only cm10.0 supported?
[22:10] <dobey> julianwi: AOSP is used for the official images, afaik
[22:10] <dobey> AOSP 4.4.2 i think
[22:16] <julianwi> which repo manifest should I use for 4.4.2 aosp?