[00:35] <Bearz> I'm trying to build a port for 'HTC evo 4g lte' and I'm a bit confused about what kernel config to edit under arch/arm/configs.
[06:12] <jgdx> muka, I think he was talking about wifi tether. And that does not work on mako, currently.
[09:13] <dhbiker> hi there
[09:13] <dhbiker> just got my MX4 in the mail :>
[09:14] <popey> \o/
[09:14] <dhbiker> they still have that Flyme print
[09:15] <dhbiker> and an apology lol
[09:15] <guest42315> silver or gold?
[09:15] <dhbiker> gold
[09:15] <guest42315> nice :D
[09:15] <guest42315> just in time for OTA6
[09:15] <dhbiker> need to update it later
[09:16] <guest42315> probably next week
[09:16] <dhbiker> sweet.
[09:17] <dhbiker> camera isn't true 20MP yet ?
[09:18] <dhbiker> shoots in 1440p
[09:18] <ogra_> yeah, fixes are in the works
[09:19] <svij> known bug: https://bugs.launchpad.net/camera-app/+bug/1468341
[09:20]  * guest42315 𝖎 𝖓𝖊𝖊𝖉 𝖇𝖑𝖔𝖔𝖉!
[09:21] <dhbiker> aah
[10:19] <mandel> seb128, can you take a look at https://code.launchpad.net/~mandel/ubuntu-system-settings/correct-nm-usage/+merge/268582 will ping ken to take a look too
[11:17] <Elleo> mandel: ping?
[11:17] <mandel> Elleo, pong
[11:18] <Elleo> mandel: heya, we're currently implementing downloads within the browser (so the browser downloads stuff internally, which can then be sent to an app later, in addition to being able to send something directly to an app); however one thing we're a bit unsure of is what to do if the browser gets closed while the download is happening
[11:18] <Elleo> mandel: since as I understand it at the moment there's then no way to get alerted by download manager when it's finished, is that right?
[11:19] <mandel> Elleo, ok, so lets think about it carefully, you want the browser to be closed, the download continue and if the browser gets opened to be notified if the download was done or not, is that correct?
[11:19] <mandel> Elleo, what would happen if the browser is never opened?
[11:19] <Elleo> mandel: yeah, much like content-hub currently does for pending transfers
[11:20] <Elleo> mandel: well presumably the download would get cleaned up on the next restart, same as for content transfers
[11:20] <Elleo> mandel: as things stand you can get a situation where the user hasn't even closed the browser themselves (it's just been closed by the OOM killer) and so their download is lost without any clear reason (from their perspective)
[11:21] <mandel> Elleo, very well, but the transfer indicator should show that a download is being done, right?
[11:21] <Elleo> mandel: yeah (although it doesn't currently due to a bug)
[11:22] <mandel> Elleo, ok, we can either uses the transfer indicator or we can find a way to indicate that a download was performed. We can show an indication (something to talk with design) or I can expose a method for the browser to query the state of a download using its uuid
[11:23] <mandel> Elleo, that API will return the state of the download (finished, success or in the process) and if it is in the process it can return the object path to be used to get the progress signals
[11:23] <Elleo> mandel: querying the state sounds good to me, as we need to update the browser's internal download database and move the file to the ~/Downloads directory once it's done
[11:24] <mandel> Elleo, ok, so we can do that without too mny changes from my side since we already keep track of the downloads in a local db for udm
[11:24] <Elleo> (or possibly other locations in the future, as the desktop version may allow the user to save anywhere)
[11:24] <mandel> Elleo, and since the uuid is unique, you will have no issues
[11:25] <mandel> Elleo, we should create a bug for this in udm and I'll get to it asap (not next week since  I have a sprint in London)
[11:25] <Elleo> mandel: great, and I'm already storing the uuid in the browser's download database
[11:25] <Elleo> mandel: awesome, I'm on holiday next week anyway, so that's all fine
[11:25] <mandel> Elleo, perfect, we need to store it in both places since udm is taking care of several apps that might want to do the same at some point
[11:26] <Elleo> mandel: yeah, I'd like to use this for podbird too once we have it all ironed out for the browser :)
[11:26] <mandel> Elleo, superb
[11:26] <Elleo> mandel: I'll file a bug now :)
[11:27] <mandel> Elleo, the browser is a good candidate to drive the feature development
[11:27] <Elleo> yeah
[11:27] <mandel> Elleo, let me know and I'll add it in asana so that the manager know about it
[11:27] <Elleo> mandel: sure thing
[11:35] <zzarr> hello! I've bought a micro USB to HDMI adapter ( I checked that my phone, Meizu MX4 Ubuntu Edition, has hw support first)
[11:35] <ogra_> it doesnt
[11:35] <zzarr> can I get it to work now?
[11:35] <nhaines> I'm almost certain that doesn't.
[11:36] <zzarr> ogra_: how were you responding?
[11:36] <ogra_> (and even if it had, there would be no driver support)
[11:36] <ogra_> zzarr, by typing on a keyboard
[11:36] <ogra_> (funny question)
[11:36] <zzarr> who :O
[11:36] <ogra_> you
[11:36] <ogra_> :)
[11:36] <zzarr> I made a typo
[11:37] <Elleo> mandel: https://bugs.launchpad.net/ubuntu-download-manager/+bug/1486971
[11:37] <ogra_> there is no support for such stuff on the MX4
[11:37] <ogra_> and even if the HW woudl support it, the driver wouldnt
[11:41] <zzarr> okey, but will there be in the future?
[11:43] <zzarr> here it says "USB microUSB v2.0 (MHL TV-out), USB Host" http://www.gsmarena.com/meizu_mx4-6627.php
[11:43] <ogra_> unlikely
[11:43] <zzarr> what about OTG?
[11:44] <ogra_> that works OOTB
[11:46] <seb128> mandel, hey, I can try to have a look this afternoon, yetc
[11:46] <zzarr> :)
[11:46] <seb128> yes
[11:46] <mandel> seb128, awesome, is an improvement in the networking code, mem leaks etc..
[11:46] <mandel> seb128, ken knows about this
[11:46] <seb128> mandel, k, the previous improvements never landed though?
[11:47] <mandel> seb128, nope, and decided to start from scratch and make sure we do not have a huge diff etc..
[11:47] <seb128> mandel, k, so maybe mark https://code.launchpad.net/~mandel/ubuntu-system-settings/fix-network/+merge/244845 as rejected or delete it?
[11:47] <mandel> ok
[11:48] <seb128> thanks
[11:51] <zzarr> ogra_: do you think that it's possible that the mouse pointer will be visible in window mode on the next stable?
[11:51] <zzarr> (I'm running a stable release now)
[11:51] <ogra_> could be, not sure if that fix landed for this OTA ... but latest in 6 weeks for the next one
[11:52]  * ogra_ doesnt use a mouse on his phone :)
[11:52] <jgdx> old school
[11:52] <zzarr> why? it's next generation coolness ;)
[11:52] <ogra_> pfft
[11:53] <ogra_> snappy is the next generation coolness :)
[11:53] <ogra_> who cares about UIs :)
[11:53]  * popey adds 1
[11:53] <ogra_> lol
[11:53] <ogra_> popey, i didnt say it will fix anything !!
[11:54] <ogra_> (indeed we all know it will :) )
[11:54] <davmor2> ogra_: I have you on record as saying snappy fixes everything
[11:54] <ogra_> davmor2, you are not alone :)
[11:55] <jgdx> opening a pdf from the web is a suboptimal ux, do we have a bug for that?
[11:56] <popey> alan@bishop:~$ grep snappy irclogs/freenode/#ubuntu-touch.log | grep ogra | grep fix | wc -l
[11:56] <popey> 11
[11:56] <popey> I honestly expected more.
[11:56] <ogra_> LOL
[11:57] <popey> jgdx: what's up?
[11:58] <jgdx> popey, first I get "Åpne med (Open with)", I choose docviewer. Then I get "Downloaded. Åpne (Open)". Then, in docviewer, I have to press "Open" again, meaning I've mentally opened the document three times.
[12:00] <jgdx> so s/suboptimal/horrible
[12:01] <popey> we have discussed this in the past a few times.
[12:01] <popey> I think we have a bug for it.
[12:01] <jgdx> popey, any idea what project that was filed against?
[12:02] <zzarr> well to be fair, what would you do without a ui ogra_?
[12:02] <ogra_> zzarr, run the internet :)
[12:02] <zzarr> :)
[12:02] <popey> jgdx: docviewer
[12:02] <ogra_> has been done before :)
[12:03] <zzarr> yes
[12:03] <popey> jgdx: https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1469422
[12:04] <jgdx> popey, so docviewer is only part of the problem.
[12:04] <popey> jgdx: sure, but it's the bit I care about, speak to mardy and Elleo about the download part :)
[12:04] <jgdx> popey, I'll just file a bug first. :) And thanks
[12:06] <jgdx> boring lectures puts me in dogfood mode
[12:25] <GAM002> link to list of devices which support ubuntu and are in development
[12:26] <popey> !devices | GAM002
[12:28] <GAM002> thanks you
[12:28] <GAM002> thank you
[12:29] <kenvandine> mhall119, why does d.u.c still list 15.04 sdk as current development?
[12:29] <kenvandine> shouldn't that be 15.10?
[12:29] <seb128> jgdx, kenvandine, I though that I saw a hotspot "new design" changeset but can't find it now, did that land?
[12:29] <kenvandine> seb128, yes it did!
[12:29] <seb128> on vivid?
[12:29] <kenvandine> yes
[12:29] <seb128> shrug
[12:30] <kenvandine> you can't see it on your device?
[12:30] <seb128> maybe
[12:30] <seb128> not sure what is in it
[12:30] <seb128> I though it would fix bug #1484703
[12:30] <seb128> but that's not fixed on rc-proposed
[12:30] <kenvandine> it's now on the main grid
[12:30] <seb128> yeah, I've it
[12:31] <seb128> the panel just looks like the version I tested a week ago
[12:31] <kenvandine> that might not be include
[12:31] <seb128> I though jgdx had an UI refresh lined up as well
[12:31] <kenvandine> this is it
[12:31] <kenvandine> the actual setup screen isn't much different
[12:31] <seb128> k, so that doesn't include the fix for that bug ^
[12:31] <seb128> :-(
[12:31] <kenvandine> but it was moved to the main grid, instead of under cellular
[12:31] <seb128> right
[12:32] <seb128> you guys just approved/landed before I could try the new UI
[12:32] <seb128> the CI had failed on the mp because of the new depends
[12:32] <seb128> so there was no handy deb
[12:32] <kenvandine> yeah, i know
[12:32] <kenvandine> we had it in a silo for a week though :)
[12:32] <seb128> oh well, I guess we are going to need another change then
[12:32] <kenvandine> also note... now there is a toggle in the indicator
[12:32] <seb128> I just assumed whoever was going to approve would compare to the design
[12:32] <seb128> and block on obvious little things like that
[12:33] <seb128> yeah
[12:34] <kenvandine> part of that setup screen was intentionally not done, because we don't support it
[12:34] <seb128> right
[12:34] <kenvandine> the spec calls for the pass to be optional
[12:34] <seb128> well that bug I just mentioned as the wrong widget being use
[12:34] <seb128> used
[12:34] <kenvandine> which would create an insecure hotspot
[12:34] <seb128> so there is no reason to not fix it
[12:34] <kenvandine> but this could have still been changed
[12:34] <seb128> or to diverge from the design
[12:35] <seb128> it's basically Switch -> CheckBox
[12:35] <kenvandine> yeah
[12:35] <seb128> we should really validate the screens against the design before approving them
[12:36] <seb128> please you guys don't approve any of the new panels before I have a look :p
[12:36] <seb128> trying to do that today
[12:36] <kenvandine> sorry i missed that
[12:36] <seb128> no worry
[12:36] <kenvandine> i did look at the design... i just missed the checkbox thing
[12:38] <jgdx> seb128, timing man, we had a call for testing months ago :p
[12:38] <seb128> kenvandine, there is also "Setup" vs "Set Up"
[12:38] <seb128> kenvandine, and "hotspot" vs "Hotspot"
[12:39] <kenvandine> should be Hotspot... not sure i agree with Set Up
[12:39] <kenvandine> i think Setup is more correct, but i'm no english major
[12:40] <seb128> well then somebody should open a design bug ;-)
[12:41] <kenvandine> grrr... my mir fix didn't fix the touchpad support!
[12:41] <kenvandine> damn
[12:42] <seb128> kenvandine, jgdx, also the wiki has "Starting the hotspot will turn on Wi-Fi.”.  as text and the dialog seems to have "In order to create a hotspot, you need to turn Wi-Fi on"
[12:43] <jgdx> seb128, okay
[12:43] <seb128> jgdx, kenvandine, I can do a mp with the ui tweak
[12:44] <seb128> jgdx, I just though you said a week ago you were working on a "design refresh"
[12:44] <seb128> and that I saw a mp email passing by while I was at debconf
[12:44] <jgdx> seb128, you're looking at it (rc proposed)
[12:44] <seb128> but I think I deleted it and I can't find it up for review
[12:44] <seb128> k
[12:44] <seb128> no worry, I'm going to do an easy tweaks follow up then
[12:44] <kenvandine> i don't think it automatically turns on wifi
[12:45] <kenvandine> you have to choose to turn on wifi
[12:45] <kenvandine> at least for now
[12:45] <seb128> we just misunderstood each others, I though you said your refresh would fix the checkbox/switch thing
[12:45] <jgdx> seb128, let's try to kill more birds per stone here. The whole key -> password story hinges on allowing insecure hotspots, which the backend does not currently support. We could support that and put the whole thing very close to spec.
[12:45] <jgdx> s/could/should
[12:45] <zzarr> ogra_: when is the next stable release?
[12:45] <seb128> kenvandine, k, I'm just going to file that as a design/feature gap then
[12:45] <kenvandine> so i think that text is more appropriate until we don't have to prompt
[12:46] <ogra_> zzarr, it was scheduled for next week iirc ...
[12:46] <kenvandine> jgdx, but we shouldn't block fixing the checkbox on the backend support insecure hotspots
[12:47] <ogra_> the images are in final testing already ... but looking at seb128 and kenvandine above we might get a re-spin, so it might take longer :)
[12:47] <kenvandine> we can do that in 2 steps
[12:47] <kenvandine> ogra_, i don't think any of these are critical
[12:47] <seb128> ogra_, lol
[12:47] <kenvandine> minor ui tweaks :)
[12:47] <seb128> yeah, those are details
[12:47] <ogra_> :)
[12:47] <kenvandine> ota7 :)
[12:48] <jgdx> kenvandine, if anything, the insecure hotspots feature should come before the checkbox thing, right?
[12:48] <ogra_> bah, why can gnomes disk management tool not resize partitions :/
[12:49] <ogra_> it replaces gparted for everything for me ... just not that :/
[12:51] <kenvandine> jgdx, no... the checkbox fix is simple, the insecure hotspots is blocking on other components right?
[12:52] <zzarr> thanks :)
[12:52] <jgdx> kenvandine, just the connectivity api code that used to be in USS
[12:53] <kenvandine> jgdx, and done we need mpt's updated spec to make it more strongly prefer secure vs. insecure?
[12:53] <kenvandine> or did he update it already?
[12:53] <jgdx> kenvandine, Femma updated that
[12:54] <kenvandine> ok
[12:54] <greyback> kenvandine: hey I added that branch for your touchpad to silo0
[12:54] <kenvandine> greyback, yeah, i noticed, thanks!
[12:54] <kenvandine> greyback, but it didn't fix my pointer :/
[12:54] <greyback> np
[12:54] <kenvandine> but it's not any worse
[12:55] <greyback> ah boo
[12:55] <kenvandine> from what i can tell...
[12:55] <kenvandine> i think it's a proper fix anyway
[12:55] <kenvandine> a touchpad should be a pointer :)
[12:56] <kenvandine> i couldn't find any other obvious things like that...
[12:56] <kenvandine> greyback, thanks for building it in the silo, i couldn't get a build of the thing to test :)
[12:57] <greyback> kenvandine: no worries
[12:59] <kenvandine> greyback, what's interesting is RAOF said his magic trackpad works as a pointer in mir_demo_server
[13:00] <kenvandine> greyback, which makes me think maybe it's not a mir problem... but something else in the stack
[13:00] <greyback> kenvandine: then it's our cursor implementation in qtmir at fault
[13:00] <kenvandine> that's what i was thinking
[13:00] <kenvandine> do you have similar enums like that for input types ?
[13:00] <greyback> I'm not totally happy with it, so dunno if we'll put effort into bugfixing
[13:01] <greyback> kenvandine: no, I think it just listens for mouse input events, and positions cursor where it wants. It may be we're not listening for the right mouse events?
[13:02] <greyback> or does your trackpad offer relative mouse events
[13:02] <greyback> as those are the ones we're listening to, not the absolute position coords in hte mouse event
[13:02] <kenvandine> i would think it's the same as a mouse
[13:04] <kenvandine> greyback, could it be something in the qpa?
[13:05] <greyback> kenvandine: it's the qpa plugin in qtmir which instructs unity8 where to position the cursor.
[13:05] <kenvandine> oh, qtmir provides the qpa plugin?
[13:06] <greyback> kenvandine: it provides *a* qpa plugin
[13:06] <greyback> qtubuntu is the qpa plugin for mir clients
[13:06] <greyback> qtmir contains a qpa plugin for Qt to be a mir server
[13:06] <kenvandine> i was thinking what if it wasn't getting the position changes
[13:06] <kenvandine> could it be qtubuntu?
[13:06] <greyback> no
[13:06] <kenvandine> ok
[13:07] <greyback> it's qtmir
[13:07] <mpt> kenvandine, working on it now
[13:07] <dhbiker> hmm
[13:08] <dhbiker> USB MTP isn't the most reliable thing eh ?
[13:10] <Sutter> Hi to someone!
[13:10] <dhbiker> oh... 20150602
[13:10] <Sutter> I have one problem with Ubuntu and Meizu mx4
[13:11] <Sutter> I am italian boy and my bearer is TIM - telecom italian mobile
[13:12] <Sutter> So My phone don't work 3g and 4g
[13:12] <Sutter> It works only with E and H..
[13:12] <Sutter> I can do something?
[13:17] <jgdx> Sutter, H is 3G
[13:18] <jgdx> Sutter, what does TIM say about 4G? Do you need any special configuration?
[13:19] <dhbiker> says H here but it works quite quickly... almost too quick for 3G :D
[13:20] <jgdx> dhbiker, excactly. It's an improvement over 3g on the 3g network, called hspa.
[13:20] <kenvandine> greyback, is there a way to enable more debug logging in qtmir?
[13:23] <greyback> kenvandine: yeah, I think if you set the env var: QT_LOGGING_RULES="qtmir.mir.input.*=true" - you should get more input related logging
[13:23] <dhbiker> jgdx yep i know that :D
[13:23] <kenvandine> greyback, and where do the logs go?
[13:24] <kenvandine> to the shell?
[13:24] <greyback> kenvandine: unity8.log
[13:24] <kenvandine> great
[13:29] <Sutter> Wait that I must translate..;)
[13:29] <Sutter> :D
[13:32] <Sutter> It's true?? H is 3g ??Nope nothing about speciial configuration...
[13:33] <Tea> All these years and I had no idea H was actually 3G....
[13:33] <Tea> I thought it was "your phone is too crap to get 3G here"
[13:33] <Tea> Which made me ask what all the fuss with 3G was because it was fairly snappy on H
[13:35] <jgdx> Sutter, System Settings -> Cellular -> Check that 4G is ON.
[13:35] <Sutter> Yep.. is on!
[13:35] <kenvandine> greyback, should i see some log output that starts with qtmir.mir.input ?
[13:38] <jgdx> Sutter, you are in a area with 4g coverage?
[13:38] <dobey> Tea: H is not 3G
[13:38] <Sutter> So.. the phone is fast...sincerely... so I missed only the 4g..uummm
[13:38] <kenvandine> 3.5G
[13:38] <dobey> 2.5G
[13:38] <kenvandine> hspa+
[13:39] <Sutter> Yes... first I had Nexus 5 with the same Sim card and 4g'll work..
[13:39] <dobey> kenvandine: that would be H+
[13:39] <Tea> dobey: okay i'll go back to wondering what all the fuss is about then
[13:39] <kenvandine> i don't think we differentiate
[13:39] <kenvandine> my arale shows an H when on hspa+
[13:41] <dobey> kenvandine: well either the icons are wrong, or something weird is going on, because every time i've been on 'H' it's been slower than when on '3G'
[13:42] <jgdx> dobey, okay, could you give me a source on that? I want to be informed here, since wikipedia may be wrong
[13:42] <greyback> dandrader: did I get that env var right, to enable more input logging in qtmir: QT_LOGGING_RULES="qtmir.mir.input.*=true" - or are they already enabled?
[13:43] <kenvandine> dobey, and i thought hspa was 3g and hspa+ was 3.5g
[13:43] <dobey> jgdx: i think wikipedia is probably right, but my experience is that on android and ubuntu, the speeds don't match what they should be
[13:43] <zzarr> ogra_: I want the functionality I wrote about a time ago, the possibility to make and answer phone calls on a computer in the same LAN as my phone (and speak), something like a remote for the phone app and contacts app
[13:44] <Sutter> OK now i must go... tnx friends...I come back if I'll get some news..tnxk again!
[13:44] <dobey> kenvandine: 3g is 3g, hspa is either HSDPA or HSUPA, and hspa+ is hspa+
[13:44] <kenvandine> last i checked with speedof.me i was getting nearly 30 megs on H
[13:44] <dobey> kenvandine: i think we need an H+ icon to distinguish it from the slower asymeetric HS{UD}PA speeds
[13:44] <dandrader> greyback, to be honest it's usually a struggle for me to get those logging filter rules to do what I want
[13:44] <zzarr> is there a possibility for me to develop that functionality my self?
[13:45] <zzarr> (I work as a programmer in Qt Creator)
[13:45] <dobey> kenvandine: hmm, i've never had any luck with speedof.me
[13:45] <dandrader> greyback, it might work
[13:45] <kenvandine> dandrader, yeah... i'm not seeing anything logged that looks input related
[13:45] <dandrader> greyback, although "qtmir.mir.input.debug=true" might be safer
[13:45]  * kenvandine tries that
[13:46] <dobey> zzarr: it's certainly possible to develop it, but doing so is going to require a deep amount of hacking across the system, not just in a single app
[13:46] <dandrader> kenvandine, with upstart, I'm never sure whether unity8 picked up the env var or not
[13:46] <greyback> dandrader: kenvandine: yeah that works
[13:46] <dandrader> kenvandine, and if you add more then one log filter rule, you have to separate them with \n
[13:46] <kenvandine> i tried setting it with initctl and restarting unity8
[13:46] <kenvandine> then i tried adding it to /etc/environment and rebooting :)
[13:46] <greyback> or this: initctl set-env --global QT_LOGGING_RULES="qtmir.mir.*=true"
[13:46] <dandrader> kenvandine, as if you were writing an .ini file
[13:47] <greyback> then stop unity8, start unity8
[13:47] <dandrader> I learned it the hard way
[13:47] <kenvandine> greyback, yeah, that's what i did first
[13:47] <dobey> kenvandine: anyway, H and 3G are definitely not the same level of data connection
[13:47] <kenvandine> dobey, i'm just saying i'm pretty sure we display an H icon when on hspa+
[13:47] <dobey> kenvandine: if we do, i think that's a bug. we should definitely show H+ instead
[13:48] <dandrader> greyback, kenvandine, when despair takes over I just add it straight into /usr/share/upstart/sessions/unity8.conf  :)
[13:48] <kenvandine> dandrader, ah... that's much better!
[13:49] <kenvandine> greyback, only events i see logged are MirTouchInputEvent
[13:49] <kenvandine> nothing from the touchpad
[13:50] <kenvandine> or even from the mouse
[13:50] <kenvandine> and the mouse is working fine
[13:50] <dandrader> kenvandine, for what it's worth, my touchpad doesn't work with mir
[13:50] <kenvandine> weird
[13:50] <kenvandine> dandrader, what kind?
[13:50] <kenvandine> also... to pair it on the device, you need my branch of system-settings :)
[13:50] <dandrader> kenvandine, I don't know. but it's a lenovo yoga 2 laptop
[13:50] <kenvandine> ah...
[13:51] <kenvandine> not on a device
[13:51] <kenvandine> we need touchpads to work :)
[13:51] <kenvandine> dandrader, i'm adding the settings panel to configure them
[13:51] <dobey> hmm
[13:52] <kenvandine> i thought i'd get MirPointerEvent logged
[13:52] <kenvandine> not just MirTouchEvent
[13:52] <kenvandine> but the MirPointerEvent is moving the pointer with the mouse
[13:52] <dandrader> kenvandine, maybe we just didn't add logging for pointer events in qtmir
[13:52] <kenvandine> maybe we lack debug output where i need it :/
[13:54] <dandrader> kenvandine, yeah. just checked. in qtmir we log only touch events. key and mouse events go through silently :/
[13:54] <kenvandine> grr
[13:54] <kenvandine> dandrader, greyback: could we add that in silo0?
[13:55] <greyback> kenvandine: we could, but we need to decide if the mouse approach in silo0 is the one we'll actually use. WE're having that discussion next week
[13:56] <kenvandine> greyback, ok... how's the work implementing the settings stuff we need?
[13:56] <kenvandine> or is that pending the discussion next week?
[13:57] <greyback> kenvandine: all depends on how we decide to implement
[13:57] <kenvandine> greyback, i'm almost done with the settings panel for it :)
[13:57] <kenvandine> just writing tests now
[13:58] <greyback> kenvandine: good for you :)
[14:18] <jgdx> bfiller, do you have a sim pin on the sim in your arale?
[14:18] <bfiller> jgdx: yes
[14:19] <bfiller> jgdx: actually no
[14:19] <bfiller> no pin
[14:19] <jgdx> bfiller, okay.
[14:20] <faenil> greyback: we don't have a px independent metric, do we? something that translates to the same physical size on all devices. GU and dp is certainly not
[14:21] <greyback> faenil: pixels are available. Are you using Qt?
[14:21] <faenil> px independent :D
[14:21] <greyback> faenil: ah, misread
[14:22] <greyback> faenil: that is roughly what GU is for
[14:22] <faenil> except tablets all have 90GUs and different screen size :D
[14:22] <faenil> (same applies to phone, etc)
[14:22] <greyback> faenil: this 90GU thing isn't what GU was designed for initially
[14:23] <faenil> greyback: sure, but that still means 1GU can't translate to a unique physical size
[14:24] <greyback> the intention was if you have 2 devices with different screen pixel densities, with a box 1GU x 1 GU, the box would appear roughly the same size
[14:24] <greyback> physically
[14:25] <greyback> we don't have cm, mm units, if that's what you're asking
[14:26] <greyback> you may be able to calculate close-to physical sizes by getting the DPI of the screen, which may be accurate, and calculate the number of pixels per physical unit
[14:27] <greyback> but not every device correctly advertises its physical size, for the DPI to be calculated
[14:28] <faenil> greyback: exactly, your last line is why I was looking for something provided by the platform
[14:28] <seb128> how does one "ignore silent mode"? is there a special audio role to use?
[14:29] <seb128> rsalveti, ^ (sorry, unsure who to ask about sound questions)
[14:29] <greyback> faenil: we can't provide such a thing reliably, so we don't. We were going to provide GU, which would help enforce visual consistency, but that notion is being screwd with, so now have nothing
[14:30] <faenil> greyback: doesn't android provide dp?
[14:31] <faenil> (longer version: maybe we could do what android does? if Android can get the dp, we should be able as well)
[14:32] <faenil> they use mdpi and hdpi etc
[14:32] <faenil> so I think the computation isn't that correct in their case either
[14:33] <greyback> faenil: we have GU and DP in our SDK. They were designed to be equivalent to android's DiP
[14:33] <faenil> yeah dp is just 1/8's GU, isn't it
[14:33] <faenil> so it's actually the same thing
[14:33] <greyback> faenil: not at low values
[14:33] <faenil> really? what's the definition?
[14:34] <faenil> ok, I should go read the doc again
[14:34] <greyback> faenil: why are you asking me this? It's not my work?
[14:34] <greyback> faenil: Kaleo was the author, and the SDK guys own it
[14:34] <faenil> greyback: sorry, I just thought, since you work with graphics, that it'd be your stuff
[14:34] <faenil> no worries, sorry
[14:35] <tshirtman> android uses a file that contains the screen's dpi, this is provided by constructor, and can be changed if you are root, that's the only point of reference that can be used by the OS to calculate physical sizes
[14:36] <faenil> tshirtman: so we do have that value, as long as we're basing on libhybris, right?
[14:36] <greyback> faenil: I've told you the original design intention of GU, which is to deliver what you want. Unfortunately this 40/50/90 thing totally screws with that. As a result, your perfectly reasonable request has become incredibly awkward to answer
[14:36] <faenil> greyback: no worries mate :)
[14:39] <tshirtman> faenil: i think that's what greyback meant by saying it *may* be accurate, if that initial value is not, nothing can be done
[14:39] <faenil> tshirtman: well yeah, in cases where not even Android is accurate, I guess it's ok to fail
[14:39] <jgdx> bfiller, while I'm testing here, anything else you can tell me? I'm currently flashing -> hotspot ON -> going to cellular panel to see if it spins.
[14:40] <faenil> since we're the small fishes anyway
[14:40] <jgdx> bfiller, if you got the chance maybe pm syslog and output of /usr/share/ofono/scripts/list-modems
[14:41] <bfiller> jgdx: flash, then turn on hotspot and set the password, then for me cellular indicator went away, cellular panel spins and dialer reports No Network
[14:41] <bfiller> jgdx: actually, after turning on hotspot I then connected from a client
[14:42] <bfiller> and couldn't browse, which was when I did the other steps
[14:42] <jgdx> bfiller, okay, real fine. I'll try that.
[14:42] <jgdx> huh, now my nm-applet died. heh
[14:43] <jgdx> pete-woods1, hey, have you seen the indicator dying lately, when testing hotspots on arale?
[14:43] <pete-woods1> jgdx: I haven't
[14:43] <pete-woods1> nm-applet != network-indicator, though
[14:44] <jgdx> pete-woods1, yeah, that was an aside :p
[14:51] <mandel> kenvandine, did you see the small MR I made with the nerwork fixes, I want to go step by step
[14:51] <mandel> kenvandine, that one removes a lot of mem leaks, we will move from there
[14:53] <kenvandine> mandel, not yet, but i'll look
[14:54] <mandel> kenvandine, awesome, the use of the QScopedPointer + the deleteLater fixes a lot of issues
[14:55] <kenvandine> mandel, so is that in place of fix-network ?
[14:55] <kenvandine> i suspect this will conflict
[14:59] <kenvandine> mandel, i've confirmed your branch does find updates and properly install them :)
[15:03] <knivsta> Who has E5 here?
[15:03] <knivsta> is it a nice phone?
[15:22] <rbasak> Are requested platform features tracked anywhere?
[15:24] <faenil> rbasak: in the corresponding package bugs list I'd say
[15:25] <rbasak> No master list?
[15:25] <rbasak> Maybe a bug tag?
[15:25] <faenil> you could use the project "ubuntu-ux" for that
[15:25] <rbasak> It's not really UX though.
[15:25] <faenil> then I don't know :) there may be another project, like ubuntu-phone
[15:25] <rbasak> For example, I'd like scheduled notifications (rather than depending on an external push server to work around)
[15:26] <faenil> I don't remember all :)
[15:53] <robin-hero> DanChapman: Hi! I know I bother you many times because of this. But when will the next dekko version arrive? Because I have a very frustrating bug (the app closes itself many times), and I see you fixed this issue. :)
[15:56] <popey> rbasak: there is a master list we track.
[15:56] <popey> rbasak: https://bugs.launchpad.net/canonical-devices-system-image
[15:57] <popey> which has milestones
[16:02] <rbasak> popey: thanks. Any thing narrower than that though? Specifically for platform features? I don't want to duplicate requests. Maybe a platform roadmap?
[16:53] <Kaleo> faenil, we can talk about it, no problem, just not now because I'm in the middle of release critical bugs
[16:53] <faenil> Kaleo: no worries ;)
[18:21] <Nexus5> just installed Ubuntu Touch on my Nexus 5. Looking for an answer on if/how the ring volume can be fixed. It currently doesn't ring, just vibrates.
[19:31] <Tea> boo - screwing around with xmir, fluxbox (and also scummvm) are getting denied by apparmor
[19:32] <Tea> can i tell apparmor to gtfo somehow?
[19:33] <Tea> oh wait - it's launching via .desktop but crashing right away, heh
[20:26] <dhbiker> i'm surprised noone made flashlight app yet
[20:29] <svij> dhbiker: this? https://uappexplorer.com/app/com.ubuntu.developer.majster-pl.utorch
[20:30] <dhbiker> oh.
[20:30] <dhbiker> whoops
[20:30] <dhbiker> ty
[20:31] <svij> ;)
[20:32] <Tea> Well screwed around. Got fluxbox running in xmir with scummvm going too, but had some weird glitch so scummvm was unusable
[20:32] <Tea> It was appearing all ghostly like behind the main app screen
[20:41] <dobey> i don't know if i'd call utorch a flashlight app
[20:42] <dobey> would be better if something could just toggle the flash LED to max brightness and keep it on, to get a flashlight
[20:42] <dobey> ie, how it works on android
[20:43] <dobey> Tea: you're trying to run fluxbox on the phone, or you're trying to get a local session on your PC working with fluxbox under mir?
[20:44] <Tea> dobey: On the phone - it is running, it's just glitchy. And I had to use an Xmir bin from wily
[20:44] <dobey> Tea: http://askubuntu.com/questions/620740/how-to-install-regularcli-deb-packages-on-bq-aquaris-e4-5-ubuntu-edition/623311#623311
[20:45] <Tea> dobey: I don't think running it in a chroot would be any different tbh
[20:46] <dobey> Tea: well it won't disappear when you upgrade the system image, and it keeps the root fs readonly and upgradeable, to do everything in a chroot
[20:46] <dobey> not that i would suggest running fluxbox in a phone at all, of course :)
[20:46] <Tea> dobey: I uninstalled it all and went back to ro anyway
[20:46] <Tea> I got it running, observed it didn't work, moved on
[20:46] <Tea> Next time I screw around I'll go with a chroot though. Safer and I have a big enough sd card for all that, won't risk anything
[20:47] <dobey> right, that's why the answer to "how do i install foo.deb on a phone?" is "use a chroot." :)
[20:47] <Tea> yeah
[20:47] <Tea> Yeah I get that but
[20:47] <Tea> Just didn't do it in THIS instance
[20:48] <Tea> I'm an Arch user and thus reckless as hell. Getting a phone with fully exposed Linux was a terrible idea :D
[20:48] <Tea> I should just reflash Android to save me from myself
[21:51] <Tea> Can I have a .desktop file launch a thing which invokes root somehow? ie asks for a password like gksu does? Would like a shortcut to start/stop the SSH server
[22:09] <hasan2> Hello friends!
[22:09] <hasan2> I can't wait for OTA 6 :D
[23:12] <maggots> how do i turn off resolution scaling for a qml rectangle?
[23:12] <maggots> it displays and adapts perfect on the desktop build but scales on the mx4
[23:13] <maggots> funnily enough text dosent scale and that what i want
[23:14] <maggots> trying to make a ruler application and scaling is an issue
[23:14] <maggots> echo
[23:26] <maggots> need help
[23:26] <maggots> with scaling issue
[23:36] <maggots> whats the folder on the phone i need to reference in order to call a qml image?