[00:02] <landstalker> urgh, you never want to see this in irc: Day changed to 18 Jan 2014
[00:02] <popey> ☻
[00:02] <popey> i see it most days
[00:03] <landstalker> I'm sure many people do
[00:04] <ahayzen> 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] <mhall119> ahayzen: I'm not sure who exactly is best, but someone on bzoltan's team
[00:09] <ahayzen> mhall119, ok thanks
[00:09] <mhall119> np
[00:11] <landstalker> huh, so the adb backup doesn't backup the accounts etc
[00:11] <landstalker> I guess that's all in the system area?
[00:17] <mhall119> which accounts?
[00:17] <mhall119> Android or Ubuntu?
[00:19] <landstalker> Android
[00:19] <landstalker> it was a pre-oem unlock backup
[00:20] <mhall119> ah,I have no idea about Android stuff
[00:20] <landstalker> :)
[00:34] <landstalker> ok, bedtime.
[01:36] <newbieubuntu> can someone help me to instal ubuntu on my nexus 4
[01:38] <newbieubuntu> hello;
[02:15] <savagejen> 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] <savagejen> Given that it can run android, it sounds like it would be ideal for ubuntu touch.
[02:17] <savagejen> The beagle is only $50 and the cape is $90. Plus I suppose you need a battery and wifi adapter.
[02:17] <savagejen> but it boils down to an open hardware solution for touch, which is different than what I've been seeing proposed
[03:38] <Ya123> Hi everybody!
[06:33] <FuLgOrE> may I ask for a status update regarding the 4.4er rebase?
[06:34] <FuLgOrE> is still 2 weeks in the focus?
[07:07] <anmol> hey guys i have a query regarding ubuntu touch app devlopmet
[07:08] <anmol> anyone online>
[07:08] <anmol> ?
[09:43] <bzoltan> ahayzen: address yourquestions to timp, zsombi or to me
[11:55] <lapor> Hello
[11:55] <lapor> I have one question
[11:56] <lapor> I have dual boot Ubuntu/Android 4.4.2 on Nexus 4 and sound doesn't work
[11:56] <lapor> is that becouse of the radio issue?
[11:56] <lapor> the sam issue as with wifi not working?
[12:05] <lapor> have just found out that it is radio issue :)
[12:33] <FistMeHard90> hello
[12:33] <FistMeHard90> can install ubuntu-touch on my super big fist dildo?
[12:33] <FistMeHard90> so it get ability to touch me inside. now it no touch
[12:34] <FistMeHard90> fist touch me in inside my sloppy bootie?
[12:36] <FuLgOrE__> !devices
[12:36] <FuLgOrE__> maybe you can find your dildo there :D
[12:49] <FistMeHard90> thank u
[12:49] <FistMeHard90> u fist me with ubuntu-touch?
[12:49] <FistMeHard90> oor i touch u inside?
[12:49] <FistMeHard90> u finny gui?
[12:49] <FistMeHard90> funny gui?
[14:53] <soumith> hello dhere?
[14:53] <soumith> how to try ubuntu touch ?
[15:45] <climber806> With Nexus 7 (first-gen) support ending, when will support for the 2013 version begin?
[15:59] <myNameIsWho> 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] <climber806> are there plans for google sync support?
[18:02] <jdorleans> 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] <jdorleans> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1270430
[18:02] <jdorleans> I'd also like to know if that's really a bug and how could I help to solve it.
[18:06] <dante123> 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] <dante123> because cost to fix/hassle is not worth it....but hate to throw in the garbage
[18:16] <sashank> hey guys
[18:16] <sashank> im installing Ubuntu Touch on my Nexus 4 and am having difficulties
[18:17] <sashank> can someone help please?
[18:19] <sashank> anyone there?
[18:21] <popey> sashank: wassup?
[18:22] <popey> 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] <dante123> im already running arkos/owncloud on a raspberry pi,
[18:23] <popey> nice
[18:23] <dante123> which i manage from browser
[18:23] <popey> not checked arkos recently, is it progressing?
[18:23] <dante123> so i thought i could maybe do something similar...or use it as some kind of media server
[18:23] <popey> IO is sluggish on the n7
[18:24] <dante123> id say so.  I have an external usb hdd plugged into pi and using it with owncloud....1tb of network storage
[18:24] <dante123> using webdav to share files with xbmc on ouya, or android devices etc.
[18:25] <dante123> 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] <miseria> "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*
[21:19] <aclever> hi al
[21:20] <dante123> hello
[21:20] <aclever> somebody trying to fix the work Wifi compatibility?
[21:22] <aclever> i don't want to use previously 4.3 ver.
[21:23] <aclever> :(
[22:01] <slangasek> 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] <slangasek> and the first tests I try are failing with an error 'Failed to load platform plugin "ubuntu".': http://paste.ubuntu.com/6776660/
[22:02] <slangasek> can anyone tell me what I'm doing wrong?
[22:02] <popey> hmm
[22:02] <popey> i use a script around phablet-test-run to do the setup
[22:02]  * popey pastebins
[22:03] <popey> http://paste.ubuntu.com/6776667/
[22:03] <popey> ./foo.sh lp:ubuntu-clock_app ubuntu_clock_app
[22:03] <popey> er
[22:03] <popey> ./foo.sh lp:ubuntu-clock-app ubuntu_clock_app
[22:03] <popey> is the kind of invocation I use.
[22:03] <popey> It does all the faff to get autopilot setup in the phablet home directory
[22:04] <popey> and then runs the tests
[22:04] <popey> so might be worth looking at that script for any setup stuff you may not have done prior to your tests.
[22:06] <slangasek> 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] <popey> slangasek: what version of autopilot is on the device?
[22:07] <slangasek> 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] <popey> slangasek: oh, this is better than it was!
[22:07] <slangasek> popey: 1.4+14.04.20131125-0ubuntu4
[22:07] <popey> this is one script, rather than 4 wiki pages all suggesting different things!
[22:08] <slangasek> popey: except it's *your* script, instead of phablet-test-run DTRT! :)
[22:08] <popey> well, yes, (although it's balloons' script)
[22:08] <slangasek> heh
[22:09] <slangasek> anyway, this is up-to-date devel-proposed, so current python-autopilot from trusty
[22:09] <popey> i have felt the same pain for a couple of cycles though, so empathise
[22:09] <slangasek> should I compare with the current promoted image?
[22:09] <slangasek> (I guess that will take a while, since the apparmor regen stuff for --dbus-probe enable takes quite a while :/)
[22:09] <popey> not sure I can be much help there, I generally run that script like an automoton
[22:10] <slangasek> popey: and you've run it with success against the current devel-proposed image?
[22:10] <popey> i run it regularly, happy to test now with some app of your choice
[22:10] <slangasek> hum, how about if you pick one :)
[22:10] <popey> ok
[22:11] <popey> ok, my phone is up to date with latest devel-proposed
[22:11] <popey> gimmie a few mins to run a test
[22:11] <slangasek> which one are you running?  I can run it in parallel here
[22:12] <popey> ./testing.sh lp:ubuntu-calendar-app calendar_app
[22:13] <popey> note, keep the phone awake until autopilot starts
[22:13] <popey> if you let the phone go to sleep the tests fail
[22:13]  * slangasek nods
[22:13] <popey> i tap the screen periodically
[22:13] <popey> 22:13:26.863 INFO autopilot:139 - Autopilot Source Version: 1.4.0
[22:13] <popey> tests begun, app is open and doing stuff
[22:14] <slangasek> I'm not sure how I know if the emulator has gone to sleep - when the screen locks, I guess?
[22:14] <popey> ah!
[22:14] <popey> I am doing this on a device, sorry.
[22:14] <popey> I should restart in the emulator. duh
[22:14] <slangasek> that's fine, the results should be the same
[22:14] <slangasek> there are some emulator-specific failures, but this wasn't one of the ones xnox reported
[22:14] <popey> hah, your optimism is delightful
[22:15] <slangasek> grr, "error: device not found" - where is phablet-tools caching the device serial?
[22:15] <popey> oof
[22:15] <popey> not seen that
[22:15] <popey> usually "adb devices" Just Works ™
[22:15] <slangasek> adb devices *does* work
[22:15] <slangasek> this is phablet-tools refusing to talk to the device
[22:15] <popey> oh.
[22:16] <slangasek> presumably because it's passing some -s option that has gotten cached somewhere without my consent
[22:16] <popey> you dont have a phone attached do you?
[22:16] <popey> i know there's a known issue if you have two "devices"
[22:17] <slangasek> strange, it's calling 'adb root' and that's failing
[22:17] <popey> that.. unnecessary. surely?
[22:18] <slangasek> it's part of phablet-test-run, I dunno why
[22:18] <slangasek> but it's failing, and doesn't at the commandline
[22:19] <slangasek> oh argh
[22:20] <slangasek> phablet-test-run does 'export ANDROID_SERIAL=$(adb devices -l | grep usb | cut -f 1 -d " " | head -n1)'
[22:20] <slangasek> and emulator != usb :P
[22:20] <popey> \o/
[22:22] <slangasek> ok, so I'll hack around that in the wrapper script for the moment
[22:23] <popey> Ran 17 tests in 592.715s
[22:23] <popey> OK
[22:24] <popey> FWIW
[22:27]  * slangasek nods
[22:27] <slangasek> I'm getting timeouts here, but that's not terribly surprising
[22:27] <slangasek> however, what I'm not getting is the error I got when doing the deb test
[22:27] <slangasek> bug #1270497 filed
[22:28] <slangasek> (also, getting the white screen instead of the properly-rendered app, which ogra_ mentioned on the list)
[22:39] <popey> slangasek: anything else I can do to help? gonna go afk otherwise
[22:40] <slangasek> 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] <slangasek> evidently it's not a known issue, whatever it is :)
[22:40] <popey> heh, indeed
[22:52] <slangasek> 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?