[00:02] urgh, you never want to see this in irc: Day changed to 18 Jan 2014 [00:02] ☻ [00:02] i see it most days [00:03] I'm sure many people do [00:04] popey, mhall119, is timp the best person to talk to regarding the swipeDelete component? me and Victor have some questions/modifications we want to ask/make [00:09] ahayzen: I'm not sure who exactly is best, but someone on bzoltan's team [00:09] mhall119, ok thanks [00:09] np [00:11] huh, so the adb backup doesn't backup the accounts etc [00:11] I guess that's all in the system area? [00:17] which accounts? [00:17] Android or Ubuntu? [00:19] Android [00:19] it was a pre-oem unlock backup [00:20] ah,I have no idea about Android stuff [00:20] :) [00:34] ok, bedtime. [01:36] can someone help me to instal ubuntu on my nexus 4 [01:38] hello; [02:15] So there's a video of someone running android on the beagle bone black with the 7" lcd touch screen cape. https://www.youtube.com/watch?v=y4INacVuTI0 [02:15] Given that it can run android, it sounds like it would be ideal for ubuntu touch. [02:17] The beagle is only $50 and the cape is $90. Plus I suppose you need a battery and wifi adapter. [02:17] but it boils down to an open hardware solution for touch, which is different than what I've been seeing proposed === salem_ is now known as _salem === LarrySteeze|Away is now known as LarrySteeze [03:38] Hi everybody! === vying is now known as Guest10008 === LarrySteeze is now known as LarrySteeze|Away [06:33] may I ask for a status update regarding the 4.4er rebase? [06:34] is still 2 weeks in the focus? [07:07] hey guys i have a query regarding ubuntu touch app devlopmet [07:08] anyone online> [07:08] ? === vying is now known as Guest50933 [09:43] ahayzen: address yourquestions to timp, zsombi or to me === vying is now known as Guest14757 [11:55] Hello [11:55] I have one question [11:56] I have dual boot Ubuntu/Android 4.4.2 on Nexus 4 and sound doesn't work [11:56] is that becouse of the radio issue? [11:56] the sam issue as with wifi not working? [12:05] have just found out that it is radio issue :) [12:33] hello [12:33] can install ubuntu-touch on my super big fist dildo? [12:33] so it get ability to touch me inside. now it no touch [12:34] fist touch me in inside my sloppy bootie? [12:36] !devices [12:36] You can find the full list of devices, official images, community images, and works in progress at https://wiki.ubuntu.com/Touch/Devices [12:36] maybe you can find your dildo there :D === FuLgOrE__ is now known as FuLgOrE [12:49] thank u [12:49] u fist me with ubuntu-touch? [12:49] oor i touch u inside? [12:49] u finny gui? [12:49] funny gui? [14:53] hello dhere? [14:53] how to try ubuntu touch ? === andrewbrandt is now known as climber806 [15:45] With Nexus 7 (first-gen) support ending, when will support for the 2013 version begin? [15:59] hello there I am helping out a person who is making a app for vlc . a remote to be more direct. The issue is with avhai on VLC. It is not showing up aka I can not find the service. though I have scanned for it with 3 different tools and have not been able to find it. Any suggestions ? [16:02] are there plans for google sync support? === bitnumus is now known as Guest29255 === Nothing_Much is now known as NothingMuchHereT === NothingMuchHereT is now known as Nothing_Much [18:02] Hello everyone, I've just got some weird behaviour on ListItem.ItemSelector and I'd like to share with you (there is a video link there): [18:02] https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1270430 [18:02] Ubuntu bug 1270430 in Ubuntu UI Toolkit "ItemSelector loses focus on SelectedItem when expand and collapse" [Undecided,New] [18:02] I'd also like to know if that's really a bug and how could I help to solve it. [18:06] hi all, daughter dropped her Nexus 7 2012 and cracked screen....could this device run Ubuntu Touch and act as a headless server [18:06] because cost to fix/hassle is not worth it....but hate to throw in the garbage [18:16] hey guys [18:16] im installing Ubuntu Touch on my Nexus 4 and am having difficulties [18:17] can someone help please? [18:19] anyone there? [18:21] sashank: wassup? [18:22] dante123: yeah, you could possibly, if you can flash and unlock it. would enable you to run apt on it, and spin up some kind of server [18:23] im already running arkos/owncloud on a raspberry pi, [18:23] nice [18:23] which i manage from browser [18:23] not checked arkos recently, is it progressing? [18:23] so i thought i could maybe do something similar...or use it as some kind of media server [18:23] IO is sluggish on the n7 [18:24] id say so. I have an external usb hdd plugged into pi and using it with owncloud....1tb of network storage [18:24] using webdav to share files with xbmc on ouya, or android devices etc. === vying is now known as Guest94943 [18:25] well, the n7 might just be toast i guess.....but i hate not finding some use for it even in its cracked screen condition [19:58] "charlando con un arbol pregunte: porque tenia el cerebro enterrado? responde: la mision es proteger la tierra" bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival* === administrator is now known as Guest98964 [21:19] hi al [21:20] hello [21:20] somebody trying to fix the work Wifi compatibility? [21:22] i don't want to use previously 4.3 ver. [21:23] :( [22:01] so, I'm trying to do some autopilot tests against ubuntu-emulator using phablet-test-run, with the current devel-proposed build (134) [22:01] and the first tests I try are failing with an error 'Failed to load platform plugin "ubuntu".': http://paste.ubuntu.com/6776660/ [22:02] can anyone tell me what I'm doing wrong? [22:02] hmm [22:02] i use a script around phablet-test-run to do the setup [22:02] * popey pastebins [22:03] http://paste.ubuntu.com/6776667/ [22:03] ./foo.sh lp:ubuntu-clock_app ubuntu_clock_app [22:03] er [22:03] ./foo.sh lp:ubuntu-clock-app ubuntu_clock_app [22:03] is the kind of invocation I use. [22:03] It does all the faff to get autopilot setup in the phablet home directory [22:04] and then runs the tests [22:04] so might be worth looking at that script for any setup stuff you may not have done prior to your tests. [22:06] popey: so I've done the phablet-config autopilot --dbus-probe enable by hand already, having cribbed it from xnox's script; and I would assume since I'm testing a .deb right now, I shouldn't need phablet-click-test-setup ? [22:07] slangasek: what version of autopilot is on the device? [22:07] popey: also, my frustration level is very high at hearing that you also have a local script you use to run tests... this stuff needs to get properly encapsulated, so that anyone can reproduce test runs at the push of a button [22:07] slangasek: oh, this is better than it was! [22:07] popey: 1.4+14.04.20131125-0ubuntu4 [22:07] this is one script, rather than 4 wiki pages all suggesting different things! [22:08] popey: except it's *your* script, instead of phablet-test-run DTRT! :) [22:08] well, yes, (although it's balloons' script) [22:08] heh [22:09] anyway, this is up-to-date devel-proposed, so current python-autopilot from trusty [22:09] i have felt the same pain for a couple of cycles though, so empathise [22:09] should I compare with the current promoted image? [22:09] (I guess that will take a while, since the apparmor regen stuff for --dbus-probe enable takes quite a while :/) [22:09] not sure I can be much help there, I generally run that script like an automoton [22:10] popey: and you've run it with success against the current devel-proposed image? [22:10] i run it regularly, happy to test now with some app of your choice [22:10] hum, how about if you pick one :) [22:10] ok [22:11] ok, my phone is up to date with latest devel-proposed [22:11] gimmie a few mins to run a test [22:11] which one are you running? I can run it in parallel here [22:12] ./testing.sh lp:ubuntu-calendar-app calendar_app [22:13] note, keep the phone awake until autopilot starts [22:13] if you let the phone go to sleep the tests fail [22:13] * slangasek nods [22:13] i tap the screen periodically [22:13] 22:13:26.863 INFO autopilot:139 - Autopilot Source Version: 1.4.0 [22:13] tests begun, app is open and doing stuff [22:14] I'm not sure how I know if the emulator has gone to sleep - when the screen locks, I guess? [22:14] ah! [22:14] I am doing this on a device, sorry. [22:14] I should restart in the emulator. duh [22:14] that's fine, the results should be the same [22:14] there are some emulator-specific failures, but this wasn't one of the ones xnox reported [22:14] hah, your optimism is delightful [22:15] grr, "error: device not found" - where is phablet-tools caching the device serial? [22:15] oof [22:15] not seen that [22:15] usually "adb devices" Just Works ™ [22:15] adb devices *does* work [22:15] this is phablet-tools refusing to talk to the device [22:15] oh. [22:16] presumably because it's passing some -s option that has gotten cached somewhere without my consent [22:16] you dont have a phone attached do you? [22:16] i know there's a known issue if you have two "devices" [22:17] strange, it's calling 'adb root' and that's failing [22:17] that.. unnecessary. surely? [22:18] it's part of phablet-test-run, I dunno why [22:18] but it's failing, and doesn't at the commandline [22:19] oh argh [22:20] phablet-test-run does 'export ANDROID_SERIAL=$(adb devices -l | grep usb | cut -f 1 -d " " | head -n1)' [22:20] and emulator != usb :P [22:20] \o/ [22:22] ok, so I'll hack around that in the wrapper script for the moment [22:23] Ran 17 tests in 592.715s [22:23] OK [22:24] FWIW [22:27] * slangasek nods [22:27] I'm getting timeouts here, but that's not terribly surprising [22:27] however, what I'm not getting is the error I got when doing the deb test [22:27] bug #1270497 filed [22:27] bug 1270497 in Phablet Tools "phablet-test-run doesn't work with emulators out of the box, looks for 'usb' in adb" [Undecided,New] https://launchpad.net/bugs/1270497 [22:28] (also, getting the white screen instead of the properly-rendered app, which ogra_ mentioned on the list) [22:39] slangasek: anything else I can do to help? gonna go afk otherwise [22:40] popey: well, still not sure what's going on with this .deb test, but I'll see if I can work it out [22:40] evidently it's not a known issue, whatever it is :) [22:40] heh, indeed [22:52] so this seems to trace back to QT_QPA_PLATFORM=ubuntu in the environment (the error message is a Qt message); but why should the system have decided this is no longer supported?