[00:29] <omac2> good evening...where are the apis for fileopen/filesave/fileselection dialogs with ubuntu-sdk
[00:30] <omac2> running with devel on nexus4.  everything phone/SMS text works, but mobile data(3g) still not working out of the box.
[00:34] <omac2> devel channel image 32's wifi seems to work fine for me, but not the mobile data(3g). 3g icon still flashes on and off and then settles to off.
[00:35] <omac2> I have had the same mobiled data(3g) buggy behaviour in the saucy stable version and the trusty devel version image 32.
[01:43] <nlsielicki> hey all. My name's Nick. I'm a student at UW Madison.
[01:43] <nlsielicki> I'm really sick of all this NSA spying. I'm interested in flashing ubuntu touch to my nexus 4.
[01:43] <nlsielicki> I'm a CS student and so I'm interested in writing some apps too, could be fun.
[01:43] <nlsielicki> my question revolves around how featured the phone is yet-- is 3g radio supported on the nexus 4?
[01:44] <nlsielicki> I need to be sure that basic features like calling, text messaging, and 3g data connectivity is supported.
[01:44] <nlsielicki> battery life, speed, etc. are less concerning problems.
[04:41] <crocket> ubuntu touch for the win!!!!
[07:34] <dholbach> good morning
[09:02] <Oria> je suis parti sur l'irc #ubuntu-touch/part
[09:03] <some_dude> Hi there, I've been checking the online spreadsheet that tracks progress of Ubuntu Touch for the Galaxy Nexus (etc). To me, it looks like there's no more progress (and it's still not usable). So, my question: is Ubuntu Touch dead already?
[09:10] <dholbach> some_dude, not really
[09:10] <dholbach> some_dude, check http://people.canonical.com/~j-lallement/touch/changes/ for changes which landed
[09:36] <some_dude> dholbach, thanks, was getting worried seeing all those other phones/OSs coming out recently and Ubuntu not really being launched
[09:37] <dholbach> some_dude, everybody's putting loads of work into it :)
[09:38] <some_dude> Ok, cool, I'll stand by... :-)
[10:00] <ogra_> barry, https://jenkins.qa.ubuntu.com/view/Trusty/view/AutoPkgTest/job/trusty-adt-system-image/ARCH=amd64,label=adt/lastCompletedBuild/console ....
[10:00] <ogra_> still failing ... (FYI)
[10:21] <janimo`> ogra_, hey, what was the main blocker to getting the x86 images on cdimage, incomplete as they are?
[10:21] <janimo`> I only remember the click packages being hardcoded to armhf right now
[10:21] <ogra_> well, adding x86 support at all to cdimage
[10:21] <ogra_> (for touch)
[10:22] <ogra_> it currently only knows about armhf and the android subarches ...
[10:22] <janimo`> ogra_, oh, I figured that was simple from your conversation with rsalveti back then
[10:22] <ogra_> it was simple for goldfish, since thats just an armhf subset
[10:22] <ogra_> s/set/arch/
[10:23] <janimo`> ogra_, is the ubuntu.zip dependent on whether it runs on goldfish or on actual hw?
[10:24] <ogra_> no
[10:24] <ogra_> thats as generic as a rootfs can be
[10:24] <janimo`> ogra_, ok, I just did not see why golfish mattered for the ubuntu.zips
[10:25] <ogra_> it isnt over complicated to add publishing support for it ... just needs a bit of work
[10:25] <ogra_> oh, it didnt
[10:36] <mterry> pitti, hello!  I love your phonesim-autostart stuff.  Is there a way to simulate receiving a text message?
[10:36] <pitti> mterry: kind of; you can send one and get it bounced back, sec
[10:38] <mterry> hmm
[10:39] <pitti> mterry: http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/tests/autopilot/messaging_app/tests/test_messaging.py#L123
[10:40] <pitti> mterry: sorry, forget about the bouncing, I mixed that up with calls
[10:40] <pitti> mterry: you can probably copy "def receive_sms()" as it is
[10:41] <mterry> pitti, that's some black magic.  pointing at js over dbus?
[10:41] <mterry> pitti, but awesome!
[10:41] <mterry> pitti, thanks
[10:41] <shuduo> hello, where is right place to report bug for system-settings-touch? there is no 'report a bug' in lp:~system-settings-touch page[B
[10:42] <pitti> mterry: yes, that's how to drive a Qt GUI remotely
[10:42] <pitti> mterry: ofono-phonesim runs on a private D-BUS as nobody, to avoid introducing a security problem
[10:43] <pitti> mterry: I agree it's ugly, but it's the only way that exists
[10:43] <mterry> pitti, yar, I noticed it was nobody.  Sure.  Plus, phonesim isn't exactly a common thing
[10:43] <mterry> pitti, yup, not hating on it, just impressed with its hackery
[10:43] <pitti> mterry: https://kernel.googlesource.com/pub/scm/network/ofono/phonesim/+/master/doc/scriptable.txt FYI
[10:44] <pitti> mterry: if we need this outside of messaging-app, it seems we should add that as a convenience script to ofono-phonesim
[10:45] <pitti> $ ofono-phonesim-receive-sms "sender" "text"
[10:45] <pitti> or so
[10:45] <mterry> pitti, just useful for testing greeter right now
[10:45] <pitti> wrap the ugly innards into a shiny CLI :)
[10:45] <mterry> not sure it's a widely useful thing
[10:58] <davmor2> Morning all
[11:05] <asac> mzanetti: Saviq: there?
[11:05] <mzanetti> asac: yes
[11:08] <asac> mzanetti: heard you guys really land regression tests for bugs?
[11:08] <mzanetti> asac: is that really a question?
[11:08] <asac> yes :)
[11:08] <asac> i suspected that noone did it, but heard you guys really do it
[11:08] <asac> which is great news :P
[11:09] <mzanetti> yeah, we try as much as we can
[11:11] <asac> mzanetti: you use qmlttests right? and we cant run that in our infrastructure yet?
[11:11] <mzanetti> asac: we run qml tests in the upstream merger
[11:12] <mzanetti> asac: we also use autopilot for integration tests. but we couldn't test everything with autopilot for multiple reasons. So yeah. most of our tests are qmltests with mocked backends
[11:17] <asac> mzanetti: can i run qmltests against an image if i wanted?
[11:17] <asac> mzanetti: could we package them so we have them available pre-built?
[11:19] <mzanetti> asac: well, so the backends are mocked which means it wouldn't reveal any breakage in things like services or such (which is where we use autopilot). But it would still add *a lot* of tests for example for SDK components. So yes, I'd say running them in the release jenkins would make sense
[11:19] <mzanetti> asac: as regard to packaging: IMHO a massive waste of time
[11:22] <mzanetti> asac: those tests are build time tests and rely on the source code file structure. So they also do coverage measurements etc which requires source files in place etc
[11:23] <mzanetti> that said. I'm not entirely sure what would be the best way to run them in the release jenkins. I would need to think a bit about it
[11:23] <mzanetti> but I'm sure there would be a nice way (although most likely involving tasks to extend those jenkins jobs with some building capabilities etc)
[11:24] <asac> mzanetti: i was hoping to use them as a second option for UI testing at image level... could qmltests be used that way at all?
[11:25] <mzanetti> asac: yes. it would be possible
[11:25] <asac> (e.g. without mocked backend and with maybe just debug symbols)
[11:33] <mzanetti> asac: so... for qml only applications (or well, applications which are launched using qmlscene) it's a no brainer. Just use it and it'll work
[11:34] <mzanetti> asac: for applications that have their own c++ main(), that main() would need to be adjusted in a way that it doesn't do much on their own but just call some other function for initialisation, so we could use QT_TEST_MAIN which just calls the same and then we'd be ready to go
[11:35] <mzanetti> asac: or maybe we could find a way to load the qmltestrunner stuff in the applications main (for example calling it with --test or the like)
[11:35] <asac> mzanetti: so we could make our framework that folks dont write main, but ubuntu_main and then have a generic main that does the right thing when run in test env?
[11:35] <mzanetti> asac: so bottom line is: for qmlscene based apps we could just use it right now. for C++ it'd be a little effort to make it happen, but nothing really critical
[11:36] <mzanetti> yes.. something like that would work
[11:36] <asac> mzanetti: so question is if upstream would like writing qmlscene more than autopilots :)?
[11:36] <asac> and if we also maybe fix a feww flakiness problems
[11:37] <mzanetti> asac: I'm all for it
[11:37] <mzanetti> a big fat +1000 actually from me
[11:37] <asac> i still believe autopilot is needed somewhat, but maybe just to test that the mouse pointer etc. thing
[11:37] <asac> mzanetti: ok i would suggest that we really play this through by maybe adding a trivial UI test this way to one of our apps
[11:37] <mzanetti> asac: I guess there are things where AP still has good value. especially for full stack integration testing
[11:37] <asac> and at best for unity
[11:38] <asac> mzanetti: right, but we should cover the mass of our UI functions in qmltests as far as i understand
[11:38] <mzanetti> I'd say yes
[11:38] <asac> and really just see autopilot as a layer that then also tests things from the mouse pointer level
[11:39] <mzanetti> asac: qmltestrunner supports mouse interaction quite nicely
[11:40] <asac> mzanetti: hmm. but you said autopilot would test full stack integration... so what can autopilot test that we cant test in qmltests?
[11:40] <mzanetti> asac: but it injects events directly into the framework, so you'd bypass e.g. X11 (which is actually where a lot of autopilot's flakyness comes from)
[11:40] <asac> i hoped the diff is minimal
[11:40] <asac> ah ok... yeah.
[11:41] <mzanetti> asac: qmltestrunner could not (easily) do things like this: you set an alarm in the clock app, and then connect to the alarm service to check if everything set up in there
[11:41] <asac> mzanetti: so assuming everyione has great UI testing coverage that we can run against our images ... can you think of a systematic way to understand what exactly we would need to test on top in autopilot to cover the gaps left with just qml?
[11:41] <asac> mzanetti: ok i see... are we doing that?
[11:41] <asac> :)
[11:41] <mzanetti> asac: you could obviously set the alarm in there and then still check if the whole round-trip has been successful, but not easily to IPC to other processes than the tested one
[11:42] <asac> yeah. wonder how much we use autopilot that way right now
[11:42] <mzanetti> asac: just saying... that's the difference and that's where autopilot has more possiblities
[11:42] <asac> somehow feels we are just doing full roundtrip atm
[11:42] <asac> (in AP)
[11:42] <mzanetti> asac: yes. see my mail on the phablet mailing list a while back
[11:42] <mzanetti> lemme search
[11:42] <asac> maybe autopilot could collaborate with qmltest?
[11:42] <asac> e.g. drive UI through qmltest, but then also add logic like this on top?
[11:43] <asac> mzanetti: whats the output format of junit? is that compatible with our autopilot format?
[11:44] <mzanetti> asac: would need to think more about combining both...
[11:44] <mzanetti> asac: re output format:
[11:44] <mzanetti>  -txt                : Output results in Plain Text
[11:44] <mzanetti>  -xunitxml           : Output results as XML XUnit document
[11:44] <mzanetti>  -xml                : Output results as XML document
[11:44] <mzanetti>  -lightxml
[11:44] <asac> ok. guess AP uses junit?
[11:45] <mzanetti> I think it's just the same. let me search for a jenkins job with an example
[11:46]  * asac notes down to talk to bfiller and sergio next
[11:50] <totos> Hello, I am thinking of buying a Nexus 10, to use it for simple tasks like web browsing and reading books. Is there a nexus 10 that is more stable than the others with the ubuntu touch installed?
[11:51] <mzanetti> asac: can't find a real xml file as jenkins seems to parse them and just show data in the website: e.g. http://s-jenkins:8080/job/unity-phablet-qmluitests-trusty/596/testReport/
[11:51] <mzanetti> asac: anyways, that means jenkins is fine with the output format
[11:52] <totos> I have read on the internet, that nexus exynos plays well with ubuntu touch.
[11:54] <asac> tdaitx__: nexus exynos? N4?
[11:54] <asac> totos: ^ ?
[11:54] <asac> (sorry tdaitx__ )
[11:56] <totos> asac: Nexus exynos isn't supported for 10 inches? My bad...
[11:57] <ogra_> nexus 10 is supported ... but it is a lot more buggy than i.e. the nexus 4
[11:57] <ogra_> we only start to focus on tablets this cycle
[12:00] <totos> ogra_: so is any installation of ubuntu to nexus 10, that is less buggy than the others?
[12:02] <ogra_> no, its all the same
[12:09] <totos> ogra_: nice, thanks.
[12:32] <t1mp> when I phablet-flash ubuntu-system, without options, I get INFO:phablet-flash:Pushing /home/tim/Downloads/phablet-flash/imageupdates/stable/maguro/version-100.tar.xz to /cache/recovery/
[12:32] <t1mp> is that correct? that version-100 file has a timestamp of October
[12:35] <ogra_> t1mp, yes, thats correct ... you are flashing stable/saucy if you dont pick a different channel
[12:41] <t1mp> normally I use --channel trusty-proposed
[12:41] <t1mp> ogra_: I guess what I want now is trusty. Is there a way to see which channels are available?
[12:43] <ogra_> t1mp, --list-channels is in sergios new go based flash tool, but thats not ready yet ...
[12:44] <ogra_> stable = saucy, stable-proposed = saucy-proposed, devel = trusty, devel-proposed = trusty-proposed.... on release day trusty will become stable and the U release will become devel ...
[12:46] <t1mp> ogra_: great, thanks :)
[12:47] <ogra_> i would suggest to stay away from release names and just stick with devel or stable ;) using devel will acutally get you a somewhat rolling release (since the name underneath will just change at release day)
[12:52] <t1mp> ok
[13:12] <sasi> hi
[13:13] <sasi> can any one please guide porting steps of ubuntu-touch on to arm cortex A9 processor
[13:14] <ogra_> see the channel topic, there is a link to the porting guide
[13:25] <sasi> Hi orga i didnt found any link to the porting guide can u please post it over here
[13:31] <cwayne> mardy: ping
[13:31] <popey> sasi: look in the /topic of this channel
[13:32] <popey> | Porting guide (advanced) https://wiki.ubuntu.com/Touch/Porting |
[13:33] <ogra_> and if you dont typo my nickname i actually get a notification ;)
[13:37] <sasi> hi popey thanks for your information, i'm new to this.. can you please guide me how to look in /topic of this channel
[13:38] <sasi> popey: hi popey thanks for your information, i'm new to this.. can you please guide me how to look in /topic of this channel
[13:39] <popey> sasi: its at the top of your browser window
[13:41] <sasi> popey: sorry i can't able to find it. i can only see "Status" and "#ubuntu-touch" can you please help me
[13:42] <popey> i pasted it
[13:42] <popey> 13:32:10 < popey> | Porting guide (advanced) https://wiki.ubuntu.com/Touch/Porting |
[13:42] <popey> that link
[13:43] <sasi> popey: i am asking about /topic, where can i find this
[13:44] <popey> sasi: if you're using some kind of web based irc client it should be on screen somewhere in your browser window
[13:45] <popey> it starts "Ubuntu Touch Support & Discussion... "
[13:46] <sasi> popey: ok fine thanq
[13:46] <t1mp> sasi: what happens when you type "/topic" in the same box where you type your chat messages?
[13:51] <sasi> t1mp: i didnt understood about "/topic" clearly. as i came to know that i am in "Ubuntu Touch Support & Discussion... " i think this indicates "/topic"
[13:54] <rsalveti> ogra_: janimo`: adding x86 images into cdimage should be easy now, after I added support for goldfish
[13:54] <janimo`> rsalveti, great
[13:55] <ogra_> rsalveti, goldfish only affected subarches
[13:55] <rsalveti> ogra_: right, but I changed that code in a way that it makes way easier to support a new arch
[13:55] <ogra_> we need to change the toplevel arches and make sure only the zip and tgz are published for it)
[13:55] <rsalveti> right
[13:56] <ogra_> it *might* even just work and we could possibly just add i386 to default-arches for touch
[13:56] <ogra_> since the file schema for zip and tgz should be the same (modulo the arch name) ...
[13:56] <rsalveti> atm we'd only publish the zip file, right?
[13:57] <rsalveti> we actually need to change a few things in there, as the piece that generates the zip file is still armhf specific
[13:57] <rsalveti> we need a x86 compatible updater-script in the zip file
[14:01] <pitti> is there a standard way to run "make test" or "ctest" during package build?
[14:01] <pitti> or do I need to put in the full override_dh_auto_test / check for "nocheck" / call ctest dance?
[14:02] <barry> ogra_: can't that be easily retried?
[14:02] <barry> ogra_: *can
[14:02] <ogra_> no idea, ask in #ubuntu-release
[14:02] <ogra_> rsalveti, oh, right
[14:03] <ogra_> rsalveti, hmm, the zip *creation* should be arch agnostic ... we just need the other binary ... but then ... we dont have android bits anyway yet, we could just go with the tarball for the start
[14:08] <rsalveti> ogra_: yeah
[14:23] <bhalu> how to install ubuntu touch on development arm boards
[14:23] <bhalu> ?
[14:25] <mardy> cwayne: pong (I'm on holiday and my VM is not running, but if I can help even like this, I'll help gladly :-) )
[14:26] <mardy> jdstrand: hi! Any ETA for bug 1245903? I'd a branch which depends on that, waiting to merge
[14:26] <cwayne> mardy: ah, sorry to barge in on your holiday!  I just wanted to let you know that I've got click-hooks working for account-plugins :D  and was gonna ask if you'd think it 'd make sense to bundle them with u-s-s-o-a or just create a new package
[14:26] <mardy> cwayne: they should be bundled
[14:28] <cwayne> mardy: ack, thanks.  now go enjoy your holiday :)
[14:28] <bhalu>                                                                                                                                                                                                                                                                                                                                                                                                                                                                          
[14:28] <bhalu>                                                                                                                          how to install ubuntu touch on development arm boards
[15:12] <MacSlow> rsalveti, btw... https://code.launchpad.net/~macslow/unity8/fix-1257312
[15:13] <kenvandine> mpt, ping
[15:14] <kenvandine> mpt, looking for some clarification on the background panel spec
[15:15] <mpt> kenvandine, I just removed the scaled-back v1 design, leaving only the original design behind … Did I over-trim?
[15:15] <kenvandine>  “Same background for both” is set, the welcome screen and home screen thumbnails combined should function as a single tappable button"
[15:15] <kenvandine> not that
[15:15] <mpt> ah
[15:15] <kenvandine> i read that as merging them so you only see one
[15:16] <kenvandine> if it is set to dupe
[15:16] <kenvandine> but now i'm not sure that what you meant
[15:16] <kenvandine> note:  i implemented that last night :)
[15:16] <mpt> kenvandine, you still see both thumbnails, and they’re in exactly the same positions as they were before, but they are now inside a single button
[15:16] <mpt> rather than being in separate adjacent buttons
[15:16] <kenvandine> ok
[15:21] <kenvandine> mpt, another question
[15:21] <kenvandine> on the preview page
[15:21] <kenvandine> you say to make the page and header transparent
[15:21] <kenvandine> which makes sense
[15:21] <kenvandine> but the sdk doesn't give us a clean way of doing that
[15:22] <kenvandine> and it breaks the visual design guidelines
[15:22] <kenvandine> but i do think it makes sense for a background preview
[15:22] <kenvandine> maybe hide the header instead of making it transparent?
[15:23] <mpt> kenvandine, I wouldn’t expect it to be in the SDK or the visual design guidelines, because it’s a one-off.
[15:23] <kenvandine> yeah
[15:23] <kenvandine> so the sdk doesn't give us a clean way of doing it
[15:23] <mpt> kenvandine, we could hide the header, but then we would still need something to tell you what the screen is for. :-)
[15:23] <kenvandine> i have a nasty hack that changes the header to transparent
[15:24] <kenvandine> but it is tricker to change the header text color
[15:24] <kenvandine> at least i haven't found a way there
[15:24] <kenvandine> and i have to be careful to change the background color back after previewing is done
[15:24] <kenvandine> it's nasty :)
[15:24] <kenvandine> so if we really want this, i think we need to request it to be added to the sdk
[15:24] <kenvandine> mpt, i could hide the header
[15:24] <mpt> Maybe it’s a matter of copying, pasting, and tweaking the header code from the SDK implementation?
[15:25] <kenvandine> and then add some text
[15:25] <kenvandine> mpt, yeah... but i worry about maintenance
[15:25] <kenvandine> as they change API
[15:25] <kenvandine> etc
[15:25] <mpt> If you’re using your own copy, any API change is irrelevant, right?
[15:25] <kenvandine> not completely
[15:25] <kenvandine> depends on how much i copy
[15:25] <mpt> The worst that can happen is the visual design of the standard header changes, and you’re still using the previous font size or whatever
[15:26] <kenvandine> we'd have to have our own PageStack
[15:26] <mpt> whoa, really?
[15:26] <kenvandine> i think so
[15:26] <kenvandine> or maybe Page
[15:26] <kenvandine> but that is still quite a bit
[15:26] <mpt> Okay, I think a Page with no header should be part of the SDK, at least
[15:26] <kenvandine> mpt, how about a popover bubble kind of thing?
[15:26] <kenvandine> mpt, i think i can make it hide the header pretty easily
[15:27] <kenvandine> or maybe some text above the buttons?
[15:28] <mpt> kenvandine, could you hide the header and then put some text in the same position and size that header text would be?
[15:29] <kenvandine> should be able to
[15:29] <kenvandine> let me see if i can hide the header in a clean way
[15:29] <mpt> kenvandine, cool, and maybe add a shadow to the text in case that part of the image happens to be white :-)
[15:29] <kenvandine> the risk there is the visual might become inconsistent if they change the page component
[15:30] <mpt> Understood. I think that risk is fine.
[15:30] <kenvandine> mpt, maybe the header area could have a semitransparent black background?
[15:30] <kenvandine> with white text?
[15:30] <kenvandine> so it's easier to read
[15:31] <mpt> kenvandine, that sounds very similar to the original design. :-D
[15:31] <kenvandine> and you changed it?
[15:31] <kenvandine>  :)
[15:32] <mpt> No, I mean the design that's in the spec now
[15:32] <mpt> Maybe I’m misunderstanding what you’re suggesting
[15:32] <davmor2> n
[15:32] <kenvandine> well that doesn't have a darker header
[15:32] <kenvandine> making the header area have a background rectangle of black, with opacity of like 0.5
[15:33] <kenvandine> and the white text
[15:33] <kenvandine> you can still see the background through it
[15:33] <mpt> It’s kinda hard to tell because of the clouds, but I think it is semitransparent black
[15:33] <mpt> Anyway, yes, that would be good
[15:33] <kenvandine> ok
[15:33] <kenvandine> cool
[15:35] <mpt> Thanks!
[15:37] <bhalu> how to install ubuntu touch on  arm dev boards?
[15:38] <ogra_> you would have to port it
[15:48] <bhalu> ogra: I mean how to port it?
[15:48] <ogra_> bhalu, see the channel /topic ... there is a url
[15:48] <ogra_> (to the porting guide)
[15:57] <mhall119> kenvandine: are you still working on content hub this cycle?
[15:57] <kenvandine> mhall119, yes
[15:58] <mhall119> kenvandine: do we have a roadmap on when features should land?  I want to plan the next app showdown for a time when we have new APIs/services to use
[16:00] <mhall119> olli_: tvoss: who is going to be working on the push notifications API?
[16:01] <mpt> charles, https://wiki.ubuntu.com/Bluetooth?action=diff&rev2=35&rev1=34
[16:01] <kenvandine> mhall119,    https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0As1Fg7XBGWTjdGUtbm0yQUFFYjE2czNVNlVqbXlfTWc&usp=drive_web#gid=0
[16:01] <olli_> mhall119, client side?
[16:01] <kenvandine> mhall119, doesn't have eta's though
[16:01] <mhall119> olli_: yes
[16:01] <olli_> mhall119, ricmm or somebody on that team
[16:02] <olli_> mhall119, that's for the implementation
[16:02] <olli_> the definition is driven by Chipaca
[16:02] <mhall119> thanks olli_
[16:02] <mhall119> ricmm: ping me when you have a minute to talk about push notifications
[16:21] <ricmm> mhall119: hi
[16:21] <ricmm> sup?
[16:23] <pmcgowan> mhall119, what a very well constructed ping
[16:24] <mhall119> pmcgowan: I wouldn't want to start another long email thread
[16:24] <mhall119> ricmm: hey, I was wondering if we had a roadmap with delivery dates for the push notifications API
[16:25] <mhall119> ricmm: I'm starting to plan the next app showdown, and I would like to make it late enough that push notifications are available to start using
[16:29] <mhall119> alright, one more question, who was working on the sensor service and haptics feedback?
[16:34] <rickspencer3> mhall119, I think that is ChickenCutlass or his team
[16:37] <ogra_> mhall119, ChickenCutlass wrote usensord ... just needs to be packaged (which is a bit tricky sine it is in go and one of the first go packages we have at all)
[16:38] <ogra_> mhall119, https://plus.google.com/109707276156531554811/posts/LAoPzq9DZhG
[16:42] <mhall119> thanks ogra_, rickspencer3
[16:42] <mhall119> ChickenCutlass: ping me when you have a few minutes to talk about haptics/sensor service roadmap
[16:57] <ChickenCutlass> mhall119 ok
[17:13] <mhall119> ChickenCutlass: hey, so I'm starting to plan the next app showdown, and I'd like to time it so that some of the new APIs are available, do you have a roadmap with delivery dates for the work on sensors and haptics
[17:13] <mhall119> ?
[17:14] <pitti> can someone please ack https://code.launchpad.net/~thomas-voss/process-cpp/fix_pkgconfig_setup/+merge/198025 ? (blocking sensor testing)
[17:16] <door> getting a 'checking for auto-deploy.zip auto deploy.zip not found error
[17:16] <ChickenCutlass> mhall119 so we are trying to land the new sensor service soon.  Like next week.  It will only have haptics implemented.
[17:16] <mhall119> kenvandine: got time for a couple questions?
[17:16] <ChickenCutlass> mhall119 still working out the API
[17:16] <ChickenCutlass> on the Platform API side
[17:16] <mhall119> ChickenCutlass: do you think by mid-January the API will be available, even if it's just a first version?
[17:16] <ChickenCutlass> yes
[17:16] <mhall119> and will it be available in QML from the start?
[17:17] <ChickenCutlass> of course
[17:17] <mhall119> perfect, thanks ChickenCutlass
[17:17] <ChickenCutlass> mhall119 the API will be much like the android one.
[17:17] <ChickenCutlass> on / off
[17:17] <ChickenCutlass> and pattern
[17:17] <mhall119> cool, let me know when it starts to come together and I'll make sure we get the docs published early on
[17:18] <ChickenCutlass> ok
[17:18] <door> sorry to interrupt, but is this the right room to discuss installing Ubuntu onto andriod?
[17:18] <mhall119> door: depends on what you mean
[17:19] <mhall119> door: are you talking about installing Ubuntu's phone OS on an Android device?
[17:19] <kenvandine> mhall119, sure
[17:19] <door> yes
[17:19] <mhall119> beuno: do we have an ETA on getting ratings and reviews working in the store and dash?
[17:19] <door> a Nexus 4
[17:20] <mhall119> door: then you're in the right place
[17:20] <mhall119> door: https://wiki.ubuntu.com/Touch/Install has instructions for installing it, it's easy if you have Ubuntu on your desktop/laptop, otherwise it's the same as flashing an Android ROM
[17:21] <mhall119> kenvandine: so the work that an app would need to tell the Content Hub that it can open, say, a PDF, do you think that will land by mid-January?
[17:21] <door> has anyone heard of / seen the error E: Can't open /cache/recovery/ubuntu_command ?
[17:21] <kenvandine> mhall119, yes
[17:21] <jdstrand> mardy: sorry, I didn't know you were blocked (I knew you wanted the fix of course). I'll prioritize for monday
[17:21] <mhall119> kenvandine: awesome, thanks!
[17:21] <kenvandine> np
[17:21] <beuno> mhall119, I refer you to ralsina
[17:22] <mhall119> ralsina: do we have an ETA on getting ratings and reviews working in the store and dash?
[17:22] <jdstrand> mardy: I started what I needed to finish before that upload yesterday and have a good handle on it
[17:22]  * jdstrand wanders off
[17:23] <mhall119> kenvandine: also, box2d and it's qml plugin are in the trusty archives now, right?
[17:23] <kenvandine> yes
[17:23] <mhall119> what do we need to do to make that part of the platform available to click apps?
[17:23] <kenvandine> yes
[17:23] <kenvandine> or, it could be bundled in
[17:23] <kenvandine> which someone did already
[17:24] <mhall119> hmmm, bundling might be safer for compatibility
[17:24] <mhall119> kenvandine: could you put together a .tar.gz that somebody could just download and un-pack into their project folder in order to use it?
[17:25] <kenvandine> seb128, which screen did you think my margins were too big on?
[17:25] <kenvandine> mhall119, not sure it's that easy... do you know who it was that had bundled it?
[17:25] <seb128> kenvandine, the grid
[17:25] <mhall119> nope
[17:25] <kenvandine> it uses qmake, and our default project templates don't
[17:26] <kenvandine> i don't think
[17:26] <mhall119> kenvandine: it was seagull strike, wasn't it?
[17:26] <kenvandine> ah, yes
[17:26] <mhall119> Michael Sheldon then
[17:26] <seb128> kenvandine, compare http://ubuntuone.com/20q4XFO8ZhvbJpxen4ifoR and https://wiki.ubuntu.com/Appearance?action=AttachFile&do=get&target=phone-background-welcome.mockup.png
[17:26] <kenvandine> maybe we can ask him what he did
[17:26] <kenvandine> seb128, so margins and spacing?
[17:26] <mhall119> yeah, I'll do that, thanks kenvandine
[17:27] <kenvandine> mhall119, np!
[17:27] <seb128> kenvandine, yes
[17:28] <kenvandine> seb128, can you try out what i just pushed?
[17:28] <kenvandine> see if you like that better
[17:28] <kenvandine> it includes all the other changes we talked about earlier
[17:33] <seb128> kenvandine, building (u-s-s is slow to build nowadays :/)
[17:35] <seb128> kenvandine, the spacing between column is still at least double of what it should be...
[17:36] <seb128> kenvandine, http://ubuntuone.com/1AMoi15hjexkImhM9YW4RY
[17:37] <kenvandine> -        spacing: units.gu(1)
[17:37] <kenvandine> +        spacing: units.dp(5)
[17:37] <kenvandine> seb128, try that in WallpaperGrid.qml
[17:39] <seb128> kenvandine, that's give me much bigger spaces...
[17:39] <seb128> which is what you would expect from increasing the spacing
[17:39] <kenvandine> ?
[17:39] <kenvandine> no
[17:39] <kenvandine> dp
[17:39] <kenvandine> not gu
[17:40] <Elleo> kenvandine / mhall119: I'm Mike Sheldon, what were you wanting to ask?
[17:40] <seb128> kenvandine, oh!
[17:41] <seb128> kenvandine, yeah, that looks better ;-)
[17:42] <seb128> kenvandine, even a bit less is better, e.g 3
[17:42] <mhall119> Elleo: ah, hello!
[17:43] <mhall119> Elleo: I was wanting to make it easy for app developers to use Box2d in their apps
[17:43] <mhall119> Elleo: I was wondering how you bundled it with Seagull Strike, and how it worked with the build process
[17:43] <seb128> kenvandine, in fact deleting the spacing line makes it about right...
[17:44] <seb128> kenvandine, though margins are bit small then, you might want margins: 3 * spacing or something
[17:46] <Elleo> mhall119: I basically just did a quick and dirty bundling of it; built qml-box2d, shove libBox2D and a qmldir definition in my package and set added it to the QML plugin include path from C++
[17:47] <mhall119> Elleo: how/where did you build it? on an arm device or using cross-compiling?
[17:48] <Elleo> mhall119: just on-device
[17:48] <Blackwizard> Hi
[17:48] <mhall119> Elleo: ok
[17:48] <Elleo> I do have a scratchbox environment setup for some arm dev, but it targets armv6
[17:48] <mhall119> Elleo: are the files you used for this available somewhere I can download them?
[17:48] <Blackwizard> How can I find tablets support ubuntu touch?
[17:49] <Elleo> mhall119: https://gitorious.org/qml-box2d/qml-box2d/ <-- you'll want the qt5 branch
[17:49] <Elleo> should build without any real difficulties
[17:49] <mhall119> Blackwizard: the original Nexus 7 and Nexus 10 are the only officially supported tablets at this time
[17:49] <mhall119> thanks Elleo!
[17:49] <kenvandine> seb128, spacing defaults to 0, so that breaks some of the calculations a bit
[17:49] <Elleo> mhall119: one thing I noticed that might cause you issues is that qmlscene on UT doesn't seem to support custom plugin paths, it's --help claims it has the option, but it then doesn't recognise it when you try to use it
[17:49] <kenvandine> but i can make it real small :)
[17:49] <Blackwizard> what about Samsung Note 8
[17:50] <Elleo> and iirc the .desktop launcher doesn't like environment variables being set in the Exec line
[17:50] <mhall119> Elleo: using -I ?
[17:50] <Elleo> yeah
[17:50] <seb128> kenvandine, well, even at 0 it's more spacing than the mockup, that's weird
[17:50] <mhall119> hmmm, ok, I'll check on that, thanks again
[17:50] <Elleo> no problem
[17:50] <kenvandine> seb128, some of that is the itemWidth i use, to allow room for the border on the current image
[17:51] <kenvandine> seb128, the design shows that border larger than the thumb
[17:51] <seb128> kenvandine, I see
[17:51] <Blackwizard> Does Samsung Note 8 Supports Ubuntu touch?
[17:57] <kenvandine> seb128, try now :)
[18:03] <ralsina> mhall119: maybe a week or two. Paul Liu is working on it and ran into some snags.
[18:06] <seb128> kenvandine, the spacing being previews look fine ;-) the margins on the left/right of the grid should be more though (the mockup has those on the right of the titles)
[18:06] <davmor2> Blackwizard: https://wiki.ubuntu.com/Touch/Devices
[18:06] <Blackwizard> tnx
[18:06] <Blackwizard> :D
[18:15] <mhall119> ralsina: by mid-January do you think we'll have an API developers can start using?
[18:16] <mhall119> oh wait, that's R&R, ignore that comment
[18:16] <ralsina> mhall119: well, the API is there for creating ratings and reviews, what's not done yet is showing/creating them from the dash
[18:16] <mhall119> thanks ralsina
[18:16] <ralsina> mhall119: right
[18:23] <mhall119> alex-abreu: are we still on trach to have a unified HTML5 template & plugin by end of December?
[18:25] <mhall119> alex-abreu: also, any idea when Ubuntu will be added to http://cordova.apache.org/docs/en/edge/guide_platforms_index.md.html#Platform%20Guides ?
[19:21] <om26er> when does the next image build ?
[20:24] <blmvxer> Hello guys, I am running Ubuntu 14.04 Touch on my Nexus 7(2012) and have a craked screen where the upper half is dead. is there anyway to rotate only while being inside an app?
[20:38] <airking> So I think I got the issue where the battery won't charge on my Nexus 4
[20:38] <airking> What can be done to fix this?
[20:43] <cyphermox> airking: does anything show up in dmesg or /var/log/syslog when it's plugged?
[20:43] <airking> I tried adb devices
[20:43] <airking> no dice
[20:43] <airking> let me try again
[20:44] <airking> nope
[20:48] <airking> A couple minutes ago, when switching from wall power to pc, I got the little red light to turn on, and the screen light up with the charging logo (battery with lightning bolt), but then I accidentally unplugged the USB, and haven't been able to get that back.
[20:50] <airking> cyphermox: What else should I try?  Is there anything else I can do?
[21:00] <airking> ifI hold down voldown+power a little red light comes on
[21:08] <airking> It's on!
[21:23] <cyphermox> airking: right, it's just very low battery you need to wait for it to charge