[01:24] <mhall119> wasn't expecting a promotion this afternoon, but man it makes me happy :)
[02:51] <cwayne> mhall119: has anyone tried out our rss template yet
[03:07] <squinty> no bluetooth devices supported right now besides audio related, is that correct?  Any other bluetooth support coming later down the line or....?
[03:45] <mhall119> cwayne: for scopes?
[12:01] <popey> mzanetti: \o/ http://popey.mooo.com/screenshots/device-2014-08-09-130043.png
[12:48] <mzanetti> popey: hehe :)
[12:48] <mzanetti> popey: hope you like it
[12:49] <mzanetti> popey: the circle around the ISS is white when its in daylight and gray when its in earth's shadow.
[13:02] <ybon> How do one close an app in the new promoted image? :)
[13:03] <ybon> popey: who should I bug to know about the last update on QtLocation?
[13:04] <mzanetti> ybon: you can close apps in the right edge spread
[13:04] <mzanetti> ybon: what up with qtlocation? maybe I can help
[13:06] <ybon> mzanetti: I just read some news that it has been updated, plus the deal with Here/Nokia, plus https://bugs.launchpad.net/osmtouch/+bug/1351046, so I'm just wondering what should I do on OSMTouch
[13:06] <ybon> like if the aGPS is active, I would love to start using it :)
[13:06] <Mirv> qtlocation itself hasn't been touched for a while, but the location-service etc is evolving
[13:07] <ybon> oh, I think I'm mixing both
[13:07] <ybon> what's the location-service?
[13:09] <ybon> mzanetti: got it for closing apps, very nice :)
[13:09] <nik90> Mirv: do you know when aGPS will be enabled by default?
[13:09] <nik90> Mirv: I need it for the clock app
[13:09] <mzanetti> ybon: not really sure what the problem with apparmor denials are. how are you getting the location?
[13:09] <ybon> I really really love the UI of Ubuntu Touch, and very change makes it better and better :)
[13:10] <ybon> mzanetti: I think the problem has been fixed
[13:10] <nik90> popey: in the mood for testing?
[13:10] <ybon> I was just trying to have a bit of info of what have changed, in case I can better my code
[13:10] <mzanetti> ybon: mhm... well, I only use the QtLocation api as it ever existed and it seems to work and not causing any issues
[13:10] <ybon> mzanetti: https://bugs.launchpad.net/bugs/1352977 this is the fix I think
[13:10] <mzanetti> interesting...
[13:11] <ybon> mzanetti: ok, for example, do you know if the aGPS is now available?
[13:11] <Mirv> ybon: location-service is just middleware, usage should be as usual through Qt. hmm, regarding the apparmor denials and such, it's possible that bug is already fixed now and nothing needs to be changed in OSMTouch, but need to re-check next week maybe with davmor2 directly
[13:11] <ybon> Mirv: yes, I think you are right, it's fixed
[13:11] <mzanetti> ybon: I don't think so. but I heard its close now
[13:11] <ybon> now when I launch OSMTouch, I'm prompted about giving access to my location
[13:11] <ybon> mzanetti: ok, cool
[13:12] <Mirv> ybon: one real problem was that the popup for allowing/denying location for the app was hidden, but that was fixed. regarding apparmor, there were some warnings/errors but it remained unclear to me whether something needs to be fixed in an app or not.
[13:12] <mzanetti> ybon: but I don't have any more knowledge on their timeline and progress... just heard rumors, so maybe try to confirm with someone else, like tvoss
[13:12] <Mirv> nik90: no, I don't know about the plans other than reading from the mailing list.
[13:12] <ybon> mzanetti: ok, do you know if tvoss is sometimes here around on IRC?
[13:12] <Mirv> hopefully really soon, I actually thought at some point that maybe it has been already, but then noticed I did not get a location indoors so probably not.
[13:13] <nik90> Mirv: ah ok..eagerly waiting for it.
[13:13] <mzanetti> ybon: he is, mostly during work hours. You have to be a bit lucky to catch him on weekends.
[13:13] <Mirv> nik90: me too :)
[13:13]  * nik90 hates the placeholder "location" text in the clock app
[13:13] <mzanetti> nik90: hey, how is it going with the network stuff?
[13:13] <ybon> mzanetti: ok, thanks, I will try in the working hour next week so :)
[13:14] <ybon> thanks mzanetti and Mirv for your infos :)
[13:14] <ybon> In summary, nothing to do on my hand right now
[13:14] <nik90> mzanetti: I haven't had a chance to work on it yet. Something else came up.
[13:14] <mzanetti> ok
[13:14] <ybon> Aside that I will need to update the UI not to use the bottom toolbar anymore soon
[13:14] <nik90> mzanetti: but I looked through your code example briefly again and plan to rewatch your tutorial video to jog my memory a bit
[13:15] <nik90> ybon: cool :)
[13:15] <ybon> on this side, I'm not sure what's the ideal UX when you have a full screen app, btw
[13:16] <nik90> ybon: may be look at other app from other platforms for reference and see if you can relate it to the ubuntu touch UI
[13:34] <popey> nik90: sure, wassup?
[13:34] <nik90> popey: https://code.launchpad.net/~nik90/ubuntu-clock-app/add-vibration-support/+merge/229327
[13:34] <nik90> popey: you will need image #180
[13:35] <popey> i have that.
[13:35] <popey> is this a pig to build?
[13:35] <popey> ( a click )
[13:35] <nik90> yeah
[13:35] <popey> got a click? ☻
[13:35] <nik90> 1 sec
[13:39] <nik90> popey: http://people.ubuntu.com/~nik90/com.ubuntu.clock.devel_0.1_armhf.click
[13:41] <popey> got it
[13:42] <nik90> popey: in the manifest file, what should the arch read? For the old clock app it was "all" since there was nothing to build.
[13:42] <popey> hmm, hang on, this is called "clock"
[13:42] <popey> is this going to replace my existing clock?
[13:43] <popey> oh, clock.devel
[13:43] <popey> armhf
[13:43] <nik90> it is using the clock devel id instead of my personal id that I change manually before every store upload
[13:43] <nik90> popey: for the new clock app, I technically need "all" since I test on armhf phone and on i386 emulator, wouldnt I?
[13:44] <popey> do "all" packages contain multiple binaries?
[13:46] <nik90> popey: I haven't tried recently since the emulator has been broken recently, but in my tests, I always use "all" and it runs on my phone properly
[13:47] <nik90> however just to be on the safe side, all click packages to you and the store have been armhf packages
[13:50] <popey> hmm, installing that click...
[13:50] <popey> http://popey.mooo.com/screenshots/device-2014-08-09-145007.png
[13:50] <nik90> yup that makes sense
[13:51] <nik90> popey: 1st (old clock), 2nd (new clock with my personal id nik90), 3rd (clock.devel id that I just gave you)
[13:51] <popey> ok, found the right one! http://popey.mooo.com/screenshots/device-2014-08-09-145109.png
[13:52] <nik90> popey: yup, sry for the confusion. It will all go away once we replace the old ancient clock with the new one :D
[13:52] <popey> heh, np
[13:52] <popey> your tab doesn't disappear when pulling up from bottom...
[13:52] <popey> http://popey.mooo.com/screenshots/device-2014-08-09-145240.png
[13:52] <nik90> tab?
[13:52] <popey> http://popey.mooo.com/screenshots/device-2014-08-09-145246.png
[13:53] <popey> the tab you grab hold of, apparently its now design decision that it should disappear, check the screenshots
[13:53] <nik90> ah, that's because I forgot to merge trunk which has that fix
[13:53] <nik90> the store also has that fix
[13:53] <popey> ah okay
[13:53] <popey> sweet!
[13:53] <nik90> I just merged them all
[13:54] <popey> so am I testing alarms with no sound?
[13:54] <popey> or alarms with sound _and_ vibrate?
[13:54] <nik90> both sound + vibrate
[13:54] <nik90> and with just sound
[13:54] <popey> should it play them when choosing an alarm sound?
[13:54] <popey> (it doesnt)
[13:55] <nik90> choosing the alarm sound from the UI doesn't work yet since I am waiting on the SDK fix to land first
[13:55] <popey> added an alarm, takes some seconds still to appear
[13:55] <nik90> this MP is just for the vibration support for alarms. You control whether you want vibration when an alarm is triggered
[13:55] <popey> ok
[13:55] <popey> set for 3pm, so 5 mins time we'll see
[13:55] <nik90> ok
[14:00] <popey> sound+vibrate works
[14:01] <nik90> sweet :D
[14:05] <popey> nik90: when setting a new alarm, it defaults to 00:00. Would make more sense to default to now+1 IMO
[14:06] <popey> takes ~6s for an alarm to appear in the list
[14:06] <nik90> popey: I will have to check with design, quite easy to implement
[14:07] <nik90> popey: bug report for the 00:00 default pls
[14:07] <nik90> as for the 6s that is long, it takes a second or two for me at most. But it has to be EDS crunching numbers as usual
[14:09] <popey> ☹
[14:10] <popey> vibrate off works too
[14:13] <ogra_> rsalveti, wired tethering: DONE ;)
[14:13] <ogra_> (well, in 181)
[14:14] <nik90> popey: ok so that MP is done pretty much. balloons feel free to give your +1 as well to the vibration branch. The indicator-datetime branch it needed landed in #180 mako :)
[14:15]  * nik90 proceeds to review other MPs meanwhile
[14:24] <popey> yay
[19:16] <cousteau> If Ubuntu Touch is still in development, wouldn't have been better to version it as 0.1 rather than 1.0?
[19:16] <cousteau> 1.0 sounds like "Pick me! I'm ready to go!"
[19:18] <cousteau> Recently saw a review on it and it wasn't very optimistic; they tagged it as promising but still a work in progress.
[19:19] <rsalveti> ogra_: awesome
[19:25] <cousteau> Do Ubuntu phones have a "lock" button to turn the screen on/off, or not even that?
[19:37] <Beldar> cousteau, There is no ubuntu phone yet.
[19:37] <cousteau> I saw some bq models on the Internet
[19:37] <Beldar> cousteau, Link?
[19:38] <cousteau> ("Ubuntu phones" meaning "phones that natively come with Ubuntu Touch", not "phones branded by Canonical" like the Ubuntu Edge)
[19:38] <Beldar> just the ubuntu touch install as of now as far as I know
[19:38] <cousteau> well, these models aren't selling yet I think
[19:38] <Beldar> cousteau, Exactly.
[19:39] <cousteau> http://www.cnet.com/products/bq-aquaris-ubuntu-edition/
[19:39] <cousteau> but they seem to be developed
[19:39] <cousteau> as in, they may be on stores soon
[19:40] <Beldar> there has been a try of getting interest from a phone purveyor, however this is a small user base at this point. The link has a key word, "prototypes"
[19:40] <cousteau> I was asking because, although apparently Ubuntu Touch needs no buttons, maybe the user wants to install Android on it as well
[19:41] <Beldar> I would think it will be a standard phone of sorts
[19:41] <Beldar> releasing a limited access makes no sense
[19:41] <cousteau> afaik the Ubuntu Edge was planned to have both Android and Ubuntu (which I think is a good idea, since Touch seems to be experimental and maybe users don't like it; this way they'd always have Android as a backup plan)
[19:42] <cousteau> ok, that makes sense
[19:42] <Beldar> the touch sits on top of a android base I believe.
[19:42] <cousteau> (although having an unused key doesn't...  although I guess Touch could be programmed so that buttons do specific actions)
[19:43] <cousteau> huh?  I thought it was something more from scratch
[19:43] <Beldar> there are dual boots for the nexus 7 a tablet and the nexus phones not sure which model through an app at google play, dual boots are not that difficult, just knowing how is all.
[19:43] <cousteau> can I install normal Ubuntu programs on Touch, btw?
[19:44] <Beldar> not sure to be honest, I'm hoping the original idea of a phone that docks as the OS will materialize.
[19:44] <cousteau> because that's one of the things that has most of my attention; being able to run normal Linux programs on a cellphone (although the UI may not be prepared for this)
[19:46] <Beldar> cousteau, The ubuntu os was installable for awhile, not as of now in a supported form is all.
[19:48] <cousteau> I see, so I could install Ubuntu (not Ubuntu Touch) on a smartphone since it's basically a computer, but then I could barely do anything on it
[19:49] <cousteau> (no keyboard, no optimized programs, maybe the touchscreen needs installing something more...)
[19:49] <Beldar> cousteau, Not a OS that is within support ubuntu has limited support times is all, not really a good idea.
[19:51] <cousteau> my question is whether I can pick a random Ubuntu program (say, XChat) which is available in the repos for that architecture, and install it in Touch and use it
[19:59] <Beldar> cousteau, Not sure myself.
[19:59] <cousteau> that would be a very useful thing
[20:23] <cousteau> I didn't figure out if the "button-less" interface of Ubuntu Touch means that it doesn't even have a lock button as most tactile devices have (even PDAs used to have!)
[20:24] <cousteau> if that's the case, that sounds like it'll have to be constantly checking the touchscreen, which sounds rather battery-consuming
[20:24] <cousteau> (although I have no idea whether it'd actually be)
[20:25] <Beldar> cousteau, The phones you show in the link have buttons on the side.
[20:25] <cousteau> oh, I didn't see them
[20:25] <popey> yes, power and vol+/-
[20:25] <cousteau> although I was asking about ...ok
[20:25] <Beldar> looks like a volume and another, or a port
[20:25] <popey> you can lock with the power button
[20:26] <popey> same as other phones
[20:26] <cousteau> having soft power button sounded like a rather bad idea, and vol +/- probably comes in handy too
[20:26] <cousteau> ...although a wheel may be easier to use...
[20:26] <popey> not sure how a soft power button would work
[20:26]  * cousteau starts thinking on a clickable wheel, like the ones computer mice have
[20:27] <popey> arguably they're all soft buttons
[20:27] <cousteau> popey, yeah, didn't think the cellphone needs some way to power on
[20:27] <popey> via the power of your mind!
[20:27] <cousteau> I meant "soft" as in "not hardware", i.e. not an actual button that will be there always
[20:28] <cousteau> popey, or connecting it to a PC
[20:28] <popey> right, no we dont have those virtual buttons like android
[20:28] <cousteau> duh, I forgot I was playing a video and my PC was at full load
[20:29] <cousteau> well, you can have all the virtual/soft/whatever buttons you want, in-app or in-OS, but there definitely have to be some hard ones
[20:30] <cousteau> ...maybe one is enough; not sure the volume ones are that important
[20:30] <anpok> buttons are good concepts when they are tactile ... you have your feedback and know that you hit them before you press them... touch screens are better used with gestures..
[20:31] <cousteau> (although a mute one may be important too...  friend of mine had some trouble with his tablet in a meeting)
[20:31] <cousteau> anpok, problem with gestures is that you can't see them
[20:32] <cousteau> you can always have a button that says "Play", so you know touching there plays, but for a "Play" gesture that consists on "sweeping with two fingers from the top right", you somehow have to instruct the user about that.
[20:32] <cousteau> (and the user may not be good at remembering them)
[20:33] <anpok> if they are consitent across most of the applications they go into muscle memory
[20:33] <anpok> i still use webos gestures on my nexus 4
[20:40] <cousteau> well yeah, you could say the same about keyboard shortcuts for example
[20:40] <cousteau> (except with LibreOffice and the damn localized shortcuts...  oh, how I hate those)
[21:16] <squinty> any plans for ubuntu touch to support bluetooth for other devices besides audio related ones?
[21:18] <popey> yeah, i believe so, beyond the first wave of devices
[21:19] <matv1> has the toppled osk been reported yet? osk opens sideways(so in lanscape mode) when device is held upright when using scopes search
[21:20] <matv1> on r179 and mako
[21:28] <matv1> what package would such a bug that be filed against?
[21:29] <popey> matv1: how do you reproduce that exactly?
[21:31] <matv1> well the video scope came up empty. so i wanted to see if results would come if i did a search. When i did OSK lauched sideways and sticks there
[21:31] <matv1> lemme try and reproduce
[21:32] <matv1> i just did :)
[21:33] <matv1> popey if you can confirm and tell me what the related package is, iwill see if anything has been filed. If not i will file.
[21:36] <popey> doesnt happen here
[21:36] <popey> kb is right way up
[21:36] <matv1> popey but you will be on a devel proposed channel I assume?
[21:37] <matv1> i am on latest promoted
[21:37] <popey> i have 179 and 180
[21:37] <matv1> hmm
[21:37] <matv1> i can do a screenshot if you want buts its pretty much what i just said
[21:38] <matv1> popey hang on let me try a reboot
[21:38] <popey> k
[21:41] <matv1> popey no longer happening after reboot
[21:42] <matv1> wont bother filing a bugrep now. If i get repeats, i will
[21:45] <popey> kk
[22:13] <matv1> popey sorry I am trying to get my head around some appearent flakiness.. after that last reboot, my osk prob was gone but now network indicator failed to show up in the indicator panel att all. after another reboot that too reappeared
[22:14] <matv1> also video scope remains empty for me all the time
[22:14] <matv1> any suggestions?
[22:14] <matv1> general troubleshootingwise
[22:18] <popey> i bet you have run out of disk space
[22:18] <popey> that causes odd behaviour
[22:20] <matv1> popey not according to storage panel from system settings
[22:20] <matv1> not by a mile actually
[22:21] <popey> what about "df -h"
[22:21] <popey> /dev/mmcblk0p23                 5.7G  2.9G  2.6G  53% /home
[22:27] <matv1> popey nope loads of room there
[22:45] <matv1> popey calling it a day. lets see what a good nights sleep will do for both me and this blasted machine. Thanks as always