=== chihchun_afk is now known as chihchun [07:12] Can we still find meizu mx4 in Europe ? [07:49] Is there a gesture for closing the displayed application? I know I can switch by swiping from the right but I need two actions to close it. Is there a shortcut I’m not aware about? [07:59] http://news.softpedia.com/news/here-s-what-s-new-in-the-ubuntu-touch-ota-9-update-for-ubuntu-phones-499419.shtml [07:59] lookin good guys! [08:11] lotuspsychje, very nice, very nice indeed [08:12] I wonder.... if the MX4 lacks the hardware to output MHL, why is this here? https://github.com/meizuosc/m75/tree/master/mediatek/kernel/drivers/mhl/driver/mhl_tx_drv [08:13] zzarr: really dont know mate, i have bq myself.. [08:13] no need to tell me that it haven't been updated lately, I can see that my self [08:15] the reason I'm so interested in connecting my MX4 to an external display is that... yea, it's about 2 3 times faster than my stationary computer [08:23] I think it's the same with the BQ devices (lacks MHL) [08:34] * tathhu needs working bluetooth in nexus7, then it's time to say goodbye for a laptop [08:35] or that rumored bq tablet.. [08:36] https://bugs.launchpad.net/ubuntu/+source/bluetooth-touch/+bug/1502524 [08:36] Launchpad bug 1502524 in bluetooth-touch (Ubuntu) "Bluetooth - Ubuntu Touch" [Undecided,Confirmed] [08:49] sil2100, hi, I read your mail last night, and you wrote there will be no delay for OTA-9, is this mean that the OTA-9 will be release tomorrow? [08:49] robin-hero: hey! Yes, that is the current expectation :) [08:50] thanks, this would be awesome \o/ :) [09:37] Good morning all! Happy Tuesday, and happy Australia Day! 😃 [09:46] and tomorrow ota :D [09:54] yayyy [09:54] you guys rocknroll! [09:57] Hi all! [09:58] quick question =) [09:58] I'm in rc 242 [09:58] with krillin and I found something strange in camera [09:59] in camera settings, when selecting 4:3 and 16:9 MP shown are incorrect [09:59] I think [10:02] victor_bq: will take a look, thanks for highlighting [10:03] davmor2 great! Would it be better if I look for it on Launchpad and report it if it's not reported yet¿ :) [10:05] on my vegetahd only option available is 16:9 (19.5MP) [10:06] that's wrong too [10:06] krillin has 8Mpx sensor and vegeta 13Mpx [10:06] u're in rc to ? [10:07] yep [10:08] would be great having that Mpx haha interpolated =) [10:14] victor_bq: hmmmm so just tested the rc image on krillin, I get too different sized images 2448x4352 and 3168x4224 [10:14] for me N4 shows 4:3 (8MP) on rc-proposed [10:20] victor_bq: is it that the MP reported are just incorrect [10:29] Kaleo, ^ do you know why the MPx reported by the camera do not correspond to the resolution of the sensors? (8Mpx and 5Mpx) [10:29] on krillin [10:30] jibel, yes [10:31] jibel, for krillin there is 2 resolutions for each sensor [10:31] jibel, the native one and the "interpolated" one [10:31] jibel, the second one is sold by BQ as a feature [10:31] jibel, and we made the decision to keep it [10:31] victor_bq, ^ does it answer your question? [10:33] thanks Kaleo [10:36] victor_bq, http://www.bq.com/es/aquaris-e4-5 "8Mpx - 13Mpx interpolados (Dual flash y autofocus)" "5Mpx - 8Mpx interpolados" [10:36] victor_bq, maybe it's a little sparsely sourced, if you have more info about it, let me know [10:39] Kaleo: so one question, 2448x4352 I assume is the 8MP mode if you take only the 1000's but is just of 10MP in reality is that a normal thing? Do the manufacturers just round down? [10:39] s/of/over [10:41] davmor2, where do you get the 2448x4352 ? [10:42] Kaleo, the specs about interpolated MPx in E4.5 are only in Android FW as far as I know, as well as the specs in E5 [10:42] Kaleo: from the image data that I took in the different modes [10:42] davmor2, I'm going to guess you are using the default settings of the camera, that you did not touch the aspect ratio in the bottom edge panel? [10:42] If Ubuntu camera app has MPX interpolated implemented that's ok [10:43] davmor2, right, that's 16:9, the default [10:43] davmor2, which is unrelated to the announced resolution [10:43] Kaleo: 2448x4352 and 3168x4224 were the too different sizes in EOG [10:43] davmor2, if you select 4:3 in the settings of the camera you'll get the "announced" 13.4MP [10:43] two even [10:43] but the HW camera specs are 8MPx rear and 5 MPx front [10:43] for E4.5 [10:44] victor_bq, right, since we are using part of the Android FW for the camera, I figured we could use the same interpolated resolutions [10:44] victor_bq, I'm not sure actually [10:44] victor_bq, would need to speak with the BQ engineer that did the interpolation bit [10:44] victor_bq, if you have his/her contact [10:44] I guess I can get it for you ;) [10:44] :=) [10:45] give me some minutes =) [10:45] davmor2, you see the aspect ratio setting right? you know which one I mean? [10:47] Kaleo: yes, and 4:3 (13.4MP) which match the interop spec, and then 16:9 (10.4) which doesn't should be 8 and 13 according to the spec right? But I assume we are giving the resolution that we are receiving from the file ie 10.4 and 13.x right [10:47] 10.7 even [10:49] Kaleo: our idea of resolution seems to match the image not the spec given, and on the front camera you have 16:9 (8.3MP) which again is probably correct by the image taken but is in the spec at 5 MP [10:50] davmor2, that's make more sense to me now :) [10:51] davmor2, no [10:52] davmor2, it's way simpler [10:52] Kaleo: oh okay [10:52] davmor2, 4:3 is the native aspect ratio of the back camera sensor [10:53] davmor2, the obvious thing to do is to use that sensor at the maximum resolution allowed with an aspect ratio of 4:3, which should be 8MPx [10:53] davmor2, now, because of the interpolation feature, it turns out this max resolution is 13MPx [10:53] davmor2, which is exactly what you get today when you set the camera setting to 4:3 [10:53] Kaleo: ah so the 16:9 which is the only mode available on the front camera is in interpolation mode then right [10:54] davmor2, and by 13MPx I mean 13.4MPx [10:54] davmor2, right [10:54] davmor2, now the front camera sensor is a bit peculiar [10:54] davmor2, it's native resolution has an aspect ratio of 16:9 IIRC [10:55] davmor2, and as you said we use the max resolution available with that aspect ratio, the interporlated resolution [10:55] davmor2, now the reason why we sometimes have a second different aspect ratio selected by default [10:55] davmor2, is that we want the camera to fill up the entire screen (which in case of BQ's is 16:9) [10:56] Kaleo: that clears that up then thanks :) [10:56] :)à [10:57] thanks kaleo for the clarification :) [10:59] Kaleo: on a plus side our reported MP's match the image sizes so as far as I am concerned we are all good, I just didn't understand the discrepancy between Size reported on site vs actual size :) [11:00] davmor2, ah right :) [11:01] * mcphail thinks a camera should take photos in 6:4 ratio by default [11:04] mcphail: wash you mouth out with soapy water ;) [11:06] davmor2: I'm serious. Any other resolution for photos is a pain. It's the de facto standard [11:07] Every print shop and every frame will have a 6" x 4" variant [11:08] 16x9 is becoming more common, I'll admit, but isn't what your granny would buy [11:09] mcphail: that's not a 6:4 ratio though, that's a 3:2 ratio :P [11:09] :) [11:12] mcphail: and technically 3:2 didn't match the old film ratio either which I'm sure was 4:3 to make it commercially viable for the film and camera industry of the time :) === _salem is now known as salem_ [11:16] davmor2: no - fame size on 35mm film was 24x36mm I think [11:16] *frame [11:18] Same as full-frame digital cameras today [11:19] cine 35mm was always 4:3, but still was 6:4 (or 3:2 if you must) [11:38] dpm: ping :) [11:39] hey [12:53] sneaks up on mzanetti in a different channel and BOO! [12:53] :) === alan_g is now known as alan_g|lunch [13:04] mariogrip: hey! [13:15] sil2100: Hi! === chihchun is now known as chihchun_afk === alan_g|lunch is now known as alan_g [13:42] hi every one i am looking for a neat swype keyboard for touchscreens under linux [13:43] i heard that ubuntu-touch has one but i am not sure where to find its name [13:43] zirafinu: ubuntu-keyboard but it isn't swype style yet that is to come [13:44] ahh ok sorry to bother you [14:14] davidcalle: hi! I've got a newbie question: how do I build the click for a scope from the command line? [14:14] davidcalle: if I run "make install", all files are installed on / [14:21] mardy: I really don't know, I've only used the sdk to work with clicks, pstolowski ? ^ [14:21] mardy, davidcalle run 'click-buddy' from the top-level dir of the scope source [14:22] * mardy tries [14:23] Oooh, this is neat [14:23] * mardy hugs pstolowski [14:25] davidcalle: I am lloking to start developing apps for the Ubuntu Phone...I see you use the SDK so I wanted to ping you. Are there any good guides that you know of? [14:25] *looking [14:27] tsimonq2: what language are you into? [14:28] seb128, hey, you around? If I build-dep on libgnome-desktop-3-dev, any way of figuring out what the binary depends on? [14:28] davidcalle: what can I choose from? [14:28] tsimonq2: there is a great opportunity right now if you are into JS [14:28] davidcalle: I'm fluent :) [14:28] tsimonq2: nice! https://developer.ubuntu.com/showdown/ [14:29] Oh! I heard about this! [14:29] jgdx, apt-cache show ? [14:29] tsimonq2: (great opportunity in the sense "stuff to win" :) ) [14:29] davidcalle: what if I don't have an app idea? :P [14:29] :D [14:29] jgdx, but if you want indirect depends easiest is to install it in a pbuilder or such [14:30] seb128, rather, I want to know what I am supposed to put in the binary section of debian/control.. [14:30] seb128, installing my uss deb right now produses dependency errors [14:30] tsimonq2: there is a live Q&A about this contest on thursday, I'm pretty sure live commenters on IRC will come up with suggestions :) [14:31] jgdx, sorry but I'm not sure to follow [14:31] davidcalle: well I am a teen so for me to participate it would have to be late UTC :) [14:31] jgdx, what sort of errors? [14:31] davidcalle: when is it? [14:32] seb128, that makes two of us. Let me try again: I've added libgnome-desktop-3-dev as a build dep in System Settings. Trying to install that .deb gives me these [1] errors. [1] http://pastebin.ubuntu.com/14671976/ [14:32] tsimonq2: 17 UTC [14:33] tsimonq2: blog post incoming today with more details about it. But even if you miss it, it will be recorded. [14:33] jgdx, oh, use apt [14:33] davidcalle: ahh okay, thanks :) [14:33] seb128, and trying to install libgnome-desktop-3-10 gives another dep error, that I need to install gnome-desktop3-data. I can install both fine, but do both have to be in debian/control for the binary? [14:33] dpkg doesn't resolve depends [14:33] no [14:33] just list what you need [14:33] apt takes care of resolving the depends [14:34] davidcalle: I might participate :D [14:34] seb128, aah. Thanks, seb. The -dev package deps on all of that. [14:35] jgdx, yw! [14:35] davidcalle: can I put my app on Github while I am working on it, or does it have to be private code? and when does it end? [14:42] tsimonq2: sure, that's up to you :) It ends february 29th [14:42] davidcalle: ok, I was just making sure that it wasn't against the rules [14:43] Hello everyone - sorry if this question has been asked a million time, but is it possible to build ubuntu touch on the latest AOSP or does it have to be the 4.2.2 branch? [14:46] davidcalle: can I work with a team? [14:47] davidcalle: as in, is it against the rules? [15:00] tsimonq2: sure, it can be a team entry if you are fine with splitting prizes if you win :) === boiko__ is now known as boiko [19:32] hi, why i cant unlock my N7000? can you help me? [20:24] <_Sponge> QUESTION: If I buy this Nexus7,2013 4G device and put Ubuntu Touch on it, can I use it as a Wifi Hotspot ? (Noob question) [20:25] <_Sponge> Here's the device: http://www.ebay.co.uk/itm/Google-Nexus-7-2013-32GB-WiFi-LTE-Black-Unlocked-Android-6-0-1-Marshmallow-/161957511931 [20:27] <_Sponge> popey, ping === salem_ is now known as _salem [20:32] <_Sponge> still here, waiting. [20:37] _Sponge, yes that should work although suport for that device may not be extended much longer [20:37] official support that is [20:47] <_Sponge> pmcgowan: Should I wait for the convergence phone for a real 4G wifi Hotspot phone then ? Just to be sure of the support side of things ? [20:48] _Sponge, a newer device would be better as thats near end of life [20:48] and that was always a reference not a true OEM product [20:51] <_Sponge> pmcgowan: Your probably right as this website : [20:51] <_Sponge> https://developer.ubuntu.com/en/start/ubuntu-for-devices/devices/ [20:51] <_Sponge> says nothing for "4G" device side of things for the Nexus 7 4G. [20:52] <_Sponge> (2013) that is. [20:54] <_Sponge> pmcgowan: I'm waiting for the "Mir Integration Launch" when I think 4K phone shall be coming along nicely, I think ... [20:54] <_Sponge> I shall be a convergence phone, [20:54] <_Sponge> multi-boot it with Android & Ubuntu ... [20:55] <_Sponge> and add my Android apps appropriately. [20:56] * mcphail thinks life is too short for a dual-boot phone [21:01] <_Sponge> Do you think the new Phone will run Android aswell ? [21:02] I'd hope not. Why would I want precious disk space used by android? [21:03] _Sponge, pong [21:04] <_Sponge> popey, It's pretty much sorted now - just wanna know if the 4G element of the Nexus 7 2013 was fully operational as a wifi hotspot ? yur thoughts ? [21:04] mariogrip: ping [21:05] <_Sponge> hi mhall119 [21:05] mhall119: pong [21:05] hi _Sponge [21:05] _Sponge, don't think we ever enabled 4G on that [21:05] hello mhall119 [21:05] good flight? [21:05] <_Sponge> mhall119: Did Tuesday's Q&A #ubuntuonair go ahead as planned ? [21:05] How was ubucon popey mhall119? [21:06] mariogrip: would you be available tomorrow for a catchup call with me, dpm and Alfonso at the the normal time? [21:06] mariogrip, great! Got your mail, need to digest and reply. sorry I haven't yet [21:06] popey: yup, how was your flight? [21:06] super [21:06] mhall119: Yes, that's perfect :) [21:06] <_Sponge> popey, Someone was saying that support could reach End Of Life soon for that model. Is this correct ? [21:06] mariogrip, people liked playing with my One Plus One last week ;) [21:06] mariogrip: great [21:07] _Sponge, which model? [21:07] <_Sponge> N72013 [21:07] popey: :D [21:07] _Sponge, news to me [21:07] <_Sponge> ok, fair enough - someone said incorrectly, then. [21:08] <_Sponge> popey, I can't find the Launchjpad bug to enable 4G on the N7-2013 4G model, couldn't lend a hand finding it could you ? [21:08] Not sure there is even a bug for that [21:08] <_Sponge> thats probably why then. [21:09] Looks like it might work actually [21:09] https://lists.launchpad.net/ubuntu-phone/msg06945.html [21:09] Don't know if anyone in the company has one of those, so chances are it's not well tested [21:10] <_Sponge> ok, not sure if it'll get all the OTA updates either, but hey ho. [21:11] I think we only targeted the wifi version of the N7 [21:11] <_Sponge> Hmmm... [21:11] <_Sponge> I should raise a bug, I guess, on Launchpad. [21:12] mhall119: what's the status on "device alias" implementation? [21:12] <_Sponge> popey, When, probably shall Mir arrive on an OTA update ? [21:12] eh? [21:13] Mir is already default on the phone. [21:13] <_Sponge> Mir on the phone. [21:13] <_Sponge> oh ok. [21:13] <_Sponge> sorry :O [21:15] * _Sponge pokes popey about snapchat on convergence phone :-) === dandrader is now known as dandrader|afk [21:17] You'd have to ask snapchat [21:20] mariogrip: I haven't spoken to sergiusens or slangasek about it since mentioning it to them last week (on account of UbuCon/SCALE) [21:21] mhall119: ack [21:22] <_Sponge> mhall119: Did you ask JonoB. about coming onto the Q&A at the UbuCon.us ? [21:22] mariogrip: what's the branch you made for ubuntu-device-flash/ [21:23] _Sponge: I barely had a change to talk with him actually, I was hoping to chat about many things and just never had the chance [21:23] https://code.launchpad.net/~mariogrip/ubuntu-system-image/device-alias && https://code.launchpad.net/~mariogrip/goget-ubuntu-touch/device-alias [21:26] <_Sponge> mhall119: Oh nuts. [21:26] * _Sponge tutts at mhall119 [21:26] mariogrip: thanks, I've added them both to https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1464754 and also market it as affecting goget-ubuntu-touch [21:26] Launchpad bug 1464754 in goget-ubuntu-touch (Ubuntu) "Support for Device aliases" [Undecided,New] [21:27] mhall119: ack [21:28] mariogrip: are you still working on those branches, or are they ready to be proposed for merging? [21:31] mhall119: they are ready [21:34] Apparently we're due a new OTA very soon. I'll be sad to see OTA8.5 go. It has been the most stable smartphone experience I've had since the days of Symbian. Well done ladies/gents. [21:35] you mean its the windows xp from ubuntu touch? :) [21:35] ha! [21:36] k1l_: you know if you say windows xp three times it reinstalls on your computer? [21:36] hihi [21:41] http://www.bbc.co.uk/news/business-35412892 - and Ubuntu phone sales last year were the biggest in history. Coincidence? I think not ;) [21:43] hehe [21:49] <_Sponge> popey, Which is the best Nexus-device that has '4G' support with Ubuntu touch ? [21:50] _Sponge, Nexus 5? [21:50] <_Sponge> right-oh [21:52] only the Nexus 4 and Nexus 5 are supported atm [21:55] _Sponge: nexus 4 has 4g if you use the old radio from before it was disabled [21:56] true [21:58] Does the nexus 5 support convergence with OTA 9? [21:58] _Sponge but you will get poor sound in calls in return if I remember correctly :) [21:58] I think the N5 has MHL support [21:59] It does [21:59] I guess that's the only way - no miracast or UDL support I guess [22:05] slimport i guess, not mhl [22:06] but nexus 5 is not an officially supported device [22:06] bluetooth doesn't work on it, so it's going to be hard using the slimport adapter with a bt kb/mouse to demo convergence on a nexus 5 [22:09] rekt [22:11] hmm dobey what version of UT is bluetooth broken in? https://wiki.ubuntu.com/Bluetooth/TouchBluez5Testing leads me to believe it might work if I use a nightly [22:12] it's not "broken" exactly [22:12] bluetooth has never worked on the nexus 5 [22:15] hm :/ [22:15] Seems like Canonical and Partners don't want me to have a UT device [22:16] the nexus 5 has never been an officially supported device. [22:16] the nexus 4 is though [22:17] I know but the nexus 4 is.... 3 years old now? [22:18] I feel like I can't expect much from it / it wouldn't be a good device to demo convergence on [22:18] it is a great device for it I think [22:18] If there was something more modern that I could flash I'd pick it up on my home tonigh [22:19] *tonight [22:19] you mean like all the existing demos that are running on it? [22:19] well all the convergence pics and videos are of the nexus 4 so... [22:20] the nexus 5 is 2.25 years old too [22:22] dobey yeah I know but I can't buy the Meizu MX4 anywhere, the BQ 4.5/5 aren't very powerful either, The N7 is too big, the 1+1 doesn't have HDMI out [22:22] The pickings are extremely thin [22:22] edude03: the bq 4.5/5 and mx4 don't do mhl either [22:22] Right [22:23] I'd buy a MX4 just to play with if I could find it though [22:24] well i've been using a nexus 5 with ubuntu for about 2 years now [22:24] god I need bluetooth in my life too much for that [22:24] official support would be nice, as would bleutooth, but eh, it works pretty well as a phone [22:25] bluetooth is a necessity for convergence apparently though [22:25] Is 16.04 still based on AOSP 4.2.2 by the way? [22:26] i think some people are expecting way more out of having a phone appear on a large screen as a traditional pc interface, than they are going to get [22:27] i guess it's 4.4, but yes, it's still 4.x [22:27] not 5.x yet [22:27] I'm possibly one of them [22:30] the 1+1 port is getting rebased on 5.x I believe [22:30] trying to fix the current issues that way [22:31] ahoneybun: there's general work to make stuff work on 5.x, because 5.x is needed for 64-bit and various other things [22:32] oh [22:32] and i guess the cost of 64-bit chips has come down enough that there's a larger market shift to it happening [22:42] hmm [22:43] I wish the CM porting guide was out [22:43] I'd take a stab at it if I knew where to start [22:43] what CM porting guide? [22:45] Word around the web is that one is coming one day [22:46] dobey: there is one promised on the AOSP porting guide. Has never appeared, though [22:47] oh, well CM is based on AOSP, so i guess it should be pretty obvious what to do there [22:47] i don't see what good a secondary guide that says to do the exact same stuff, would be [22:48] same deal [22:49] If I had a device that could run a new version of CM or AOSP (like the nexus 6) there isn't a guide that describes how to go from that to UT [22:52] uh, the porting guide describes exactly that === popey_ is now known as popey [23:24] popey did you say you have a oneplus one running a ut port? [23:25] i do [23:25] cool [23:25] who maintains it? [23:28] popey I remember news of it being ported early in 2015. I didnt realize it is still being maintained. Is it up to date? [23:31] mariogrip maintains it [23:34] matv1: jup, I'm working on getting the android base to 5.1 [23:34] mariogrip thats pretty neat. [23:34] where do you have the image hosted? [23:35] http://system-image.ubuntu.com/ [23:35] http://system-image.ubports.com/ [23:35] really? [23:35] oh ok [23:35] The last one [23:36] yeah, i was going to say :) [23:36] Copy pate error :P [23:36] Paste* [23:37] mariogrip found it, thanks [23:39] I noticed fairphone 2 has same cpu gpu === jonas1 is now known as jgdx