[00:07] <popey> elimisteve: sure it was
[00:07] <popey> elimisteve: loads of photos and video posted online from MWC showing the MX4
[00:07] <popey> elimisteve: https://www.youtube.com/watch?v=dl4R-iI9JHQ
[00:08] <popey> elimisteve: the phone runs Ubuntu. There may be flyme services on top which match the Android FlyMe services, but it's Ubuntu
[06:01] <yacuken> Hi all
[06:01] <nhaines> Hi
[06:06] <yacuken> (Sorry for my bad English) I started to read wiki on https://wiki.ubuntu.com/Touch/AndroidDevel. I'm interested in patches section. But ufp-export not found on Launchpad. This script deprecated?
[06:12] <nhaines> You're going to want to use the new porting guide: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[06:13] <DonkeyHotei> cm-10 is not used anymore anyway
[06:14] <DonkeyHotei> nhaines: on the nexus 5, is bluetooth completely dead, or just not meaningfully functional?
[06:16] <nhaines> DonkeyHotei: appears to not be detected.  But I can reboot my phone and do any tests you like.
[06:17] <DonkeyHotei> your phone is dual-boot?
[06:17] <nhaines> Yup.
[06:18] <DonkeyHotei> can you get me a listing of /sys/devices and /sys/devices/platform?
[06:18] <yacuken> nhaines: thanks
[06:19] <nhaines> DonkeyHotei: yup!
[06:19] <nhaines> yacuken: my pleasure.
[06:24] <nhaines> DonkeyHotei: http://pastebin.ubuntu.com/10547939/
[06:27] <DonkeyHotei> oh geez, can the answer really be that simple?
[06:27] <nhaines> Let's hope so!
[06:28] <nhaines> I mean, it's totally obvious now.  But maybe for the logs and everyone else in the channel you should spell it out.
[06:29] <DonkeyHotei> the platform device is not there
[06:31] <DonkeyHotei> is there a /proc/bluetooth?
[06:33] <nhaines> Yes.
[06:33] <nhaines> phablet@ubuntu-phablet:~$ sudo ls /proc/bluetooth/
[06:33] <nhaines> sleep
[07:05] <DonkeyHotei> nhaines: can you type "rfkill list" ?
[07:13] <nhaines> DonkeyHotei: http://pastebin.ubuntu.com/10548317/
[07:26] <DonkeyHotei> nhaines: lsmod?
[07:30] <nhaines> phablet@ubuntu-phablet:~$ sudo lsmod
[07:30] <nhaines> Module                  Size  Used by
[07:30] <nhaines> bcmdhd                571716  -2
[07:41] <nhaines> DonkeyHotei: ^^
[08:13] <angry_m4n> hello !
[08:14] <DonkeyHotei> hi
[08:16] <angry_m4n> sup Hotei
[08:18] <dholbach> good morning
[08:18] <nhaines> Good morning, dholbach.
[08:18] <dholbach> hi nhaines
[08:19] <nhaines> DonkeyHotei: anything more I can do to help?
[08:21] <DonkeyHotei> nhaines: i'm looking through sources atm, might find something
[08:23] <gaspa> hi, did anyone experience a "cannot find ubuntu-click" error on a newly created project?
[08:23] <DonkeyHotei> nhaines: might save me a bit of time if cyphermox were around
[08:25] <angry_m4n> hi gaspa , did you get framework related error message as well?
[08:29] <gaspa> angry_m4n, seems not,  i got something like: "09:26:57: Could not find the manifest.json file in /home/gaspa/Projects/build-prova-myinstance_GCC_i386_ubuntu_sdk_14_10_utopic-Debug/.ubuntu-sdk-deploy." , but maybe related to the one above...
[08:29] <DonkeyHotei> if i could get a dmesg and/or syslog from a mako/nexus4, that might help me atm
[08:31] <nhaines> Wish I had one.
[08:32] <angry_m4n> i was getting similar error messages i could solve it by chosing different project ( by hit n trial )
[08:33] <gaspa> lol :)
[08:34] <angry_m4n> use the project that creates a .manifest file by default..might solve ur issue
[08:58] <DonkeyHotei> ok, in desktop ubuntu, bluetooth device drivers live in the kernel, but in android they appear to live in userspace, and i don't see either in ubuntu-touch. is anyone around who can shed light on this?
[08:59] <nhaines> DonkeyHotei: they live in the LXC container running the Android kernel, and then libhybris does the thing and then it works.
[08:59] <popey> "the thing"
[09:00] <popey> libhybris is *magic*
[09:00] <nhaines> popey: it's probably exactly that easy.  :)
[09:00] <DonkeyHotei> but ubuntu uses a bluetooth stack that depends on kernel drivers
[09:00] <DonkeyHotei> and cyphermox said libhybris isn't being used for bt
[09:01] <nhaines> DonkeyHotei: I suspect https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/#anchor4 will be elucidating.
[09:01] <nhaines> Oh?  I'd heard differently.  Hrml.
[09:01] <nhaines> Maybe Tassadar knows!
[09:01] <popey> Well, bluetooth is well supported in the kernel.
[09:01] <popey> unlike gps/gsm stuff
[09:02] <nhaines> popey: DonkeyHotei is investigating Bluetooth support for the Nexus 5.
[09:02] <popey> super
[09:02] <nhaines> I keep meaning to ask him why, since he doesn't have one, but I don't want him to think about it too deeply.
[09:03] <popey> I'm looking forward to ports to Sony devices
[09:03] <popey> they look pretty
[09:03] <popey> and have nice cameras
[09:04] <nhaines> At SCALE whenever someone asked me how it was running on my N5, I said it was the nicest hardware to run Ubuntu on if they hated Bluetooth.
[09:05] <DonkeyHotei> nhaines: that stuck in my mind
[09:06] <elimisteve> nhaines: hopefully that changes soon with UT running on the MX4 :-)
[09:07] <dpm> mardy, on bug 1195274, where is the documentation in d.u.c and from which package it's generated?
[09:08] <mardy> dpm: it's generated from accounts-qml-module, and it's at https://developer.ubuntu.com/api/qml/sdk-14.10/Ubuntu.OnlineAccounts/
[09:09] <dpm> mardy, so is all the source documentation included in accounts-qml-module instead of a dedicated -doc package?
[09:09] <elimisteve> if I can get the MX4 here in the US for ~$350 some time in the next few months, I think I will
[09:09] <elimisteve> I want an Ubuntu server in my pocket
[09:10] <mardy> dpm: ah, no, there is a -doc package: accounts-qml-module-doc
[09:10] <elimisteve> and a device where I can write native mobile apps in Go that run on it
[09:10] <DonkeyHotei> popey: the thing is, bt clearly works on mako, yet i see no kernel driver for it
[09:11] <DonkeyHotei> elimisteve: that's as much as some i3 laptops
[09:11] <dpm> mardy, ok, got it, thanks
[09:19] <nhaines> willcooke: good morning!  How was MWC?
[09:19] <willcooke> hey nhaines.  Really long week, tough on my old feet :)  But it was AWESOME!
[09:19] <nhaines> So happy to hear it.  :)
[09:21] <willcooke> People were clapping the convergence demo
[09:21] <willcooke> :D
[09:21] <nhaines> Ooh.  :D
[09:21] <elimisteve> DonkeyHotei: $350? Yes, like the Chromebook I'm running right now :-)
[09:22] <elimisteve> willcooke: sweet! Who got to see that demo? Was this an on-stage presentation, or were you in a booth?
[09:22] <nhaines> willcooke: what would I have to do to my Nexus 5 if I wanted to run a desktop app on it today?
[09:23] <elimisteve> willcooke: (2) When do you think some of that convergence-y code will be available in mainline? The UbuntuOnAir video from a couple days ago made it sound like this summer-ish?
[09:23] <willcooke> elimisteve, on the stand, publically
[09:23] <willcooke> *publicly
[09:23] <elimisteve> stand? stage?
[09:23] <willcooke> s/stand/booth
[09:23] <DonkeyHotei> elimisteve: acer had windows machines for that
[09:24] <elimisteve> cool
[09:24] <willcooke> nhaines, not sure if the N5 is supported, but if is you'd need to run devel-proposed channel, and you'd be good to go
[09:24] <nhaines> willcooke: it's not, but there's a build server anyway, <3 Tassadar.
[09:25] <nhaines> willcooke: Do you just launch something from the Terminal?
[09:25] <popey> willcooke:  you feature in this super video https://www.youtube.com/watch?v=dl4R-iI9JHQ
[09:25] <popey> ~3m40 in
[09:25] <willcooke> popey, I saw that video - I sound like a jibbering idiot
[09:26] <popey> hahah
[09:26] <willcooke> in my defence, I was drunk
[09:26] <willcooke> ;) jk
[09:26] <willcooke> I am just a jibbering idiot
[09:26] <tsdgeos> Elleo: i did try for a second time a clean devel-proposed + the qt ppa and maliit-server is still crashing all the time :/
[09:26] <popey> confirmed
[09:26] <willcooke> nhaines, gsettings set com.canonical.unity8 usage-mode [automatic|staged|windowed]
[09:26] <willcooke> nhaines, ^^^ from memory, so might be wrong
[09:27] <willcooke> I'll get instructions up next week
[09:28] <nhaines> willcooke: that's good to know!  At the moment, it's the XMir bits I'm more interested in than windows mode.
[09:28] <elimisteve> popey: anyone create a syncthing front-end on Ubuntu Touch yet, as far as you've heard?
[09:28] <popey> not that I have seen
[09:29] <nhaines> The trouble with windowed mode is I haven't yet found any way to resize existing windows.  :)
[09:30] <willcooke> nhaines, ack - Xmir is in mlankhorst's ppa
[09:30] <willcooke> nhaines, but he's not happy with it quite yet
[09:30] <willcooke> sooooooon
[09:30] <willcooke> :D
[09:30] <willcooke> nhaines, windows do resize but the controls are very hard to get hold of, only a couple of pixels wide
[09:31] <willcooke> nhaines, and maximising a window can lead to it becoming un-movable
[09:31] <willcooke> nhaines, easy enough to fix
[09:32] <nhaines> Ooh, I never seemed to see the cursor change on my laptop in a live session with Unity 8, so I just assumed it was on the todo list.
[09:32] <nhaines> When I get a maximized window I can't move, I just foreground another window, and then drag the problem window down!  :D
[09:33] <nhaines> I know all the really exciting hard work is end-user-invisible, so I'm sure it's all progressing pretty well.  :)
[09:35] <ogra_> willcooke, do you expect us to put that in the default phone image ?
[09:35] <ogra_> (i assume it will pull in megabytes of Xorg packages)
[09:35] <ogra_> (regarding your "soon" :) )
[09:35] <willcooke> ogra_, don't think it would be, but meh - why not.  Storage is cheap ;)
[09:36] <ogra_> not on phones
[09:36] <ogra_> :)
[09:36] <willcooke> heh
[09:36] <willcooke> Do you want to run X apps or not?!?  Sheesh, you guys. ;D
[09:37] <ogra_> i dont
[09:37] <ogra_> but others seem to
[09:37] <willcooke> hehe
[09:37] <ogra_> i wonder if we need a second image for this
[09:37] <willcooke> actually, *loads* of people asked about the terminal
[09:37] <ogra_> you really dont want to have this on low end phones where you perhaps only have 8G storage in total
[09:38] <ogra_> (and already eat 3-4G for the system)
[09:38] <willcooke> ogra_, we should be able to clickifiy it, right?
[09:38]  * willcooke adds that as a user story 
[09:38] <ogra_> well, perhaps ... it would have to be unconfined
[09:38] <willcooke> ahh, yes
[09:38] <willcooke> hrm
[09:38] <willcooke> more thinking required
[09:39] <ogra_> willcooke, there is more ... i.e. xorg will pull in dbus behavior we dont want on the phone image (differemt dbus-launch command for example)
[09:39] <nhaines> I think a clickified convergent experience would be sorta neat.
[09:39] <ogra_> this wont just be "flick a switch"
[09:39] <ogra_> packages of functionality will clash, that will take time to sort out
[09:40] <ogra_> (take that into your story too :) )
[09:40] <ogra_> s/of/or/
[09:40] <willcooke> ogra_, rickspencer3 has asked me to curate a list of all the things we still need to do in order to get the feature "finished" - so mind sparing me 30 mins next week to list your concerns and issues?
[09:41] <willcooke> seb128, you too ^^ :)
[09:41] <ogra_> willcooke, well, i cant predict all issues, none will be unsolvable, but we will have to solve them first most likely :)
[09:41] <willcooke> ogra_, sure, not asking for all issues - but you obviously have some ideas here, so would be good to make sure I capture them
[09:41] <ogra_> it is a matter of trying and collecting info
[09:42] <ogra_> for that we will need an image where we can go wild
[09:43] <seb128> willcooke, the feature being xmir?
[09:43] <ogra_> yeah
[09:43] <ogra_> in the phone image
[09:43] <seb128> k
[09:44] <seb128> well, first we should get it on desktop-next iso imho
[09:44] <seb128> it's more useful there
[09:44] <seb128> and less disruptive
[09:44] <ogra_> right, but we need to knwo how it interacts with the system modifications on the phone
[09:44] <ogra_> since it is supposed to land there too eventually
[09:48]  * willcooke is moving to the gate - bbl
[09:49] <seb128> right
[09:53] <nhaines> I really do like the Today scope.  It's replaced the Weather Channel scope for me as my favorite scope.  :)
[09:54] <Elleo> tsdgeos: strange :/ are you testing on mako or krillin?
[09:54] <tsdgeos> Elleo: nexus4
[09:54] <Elleo> okay, that's what I'm using too
[09:55] <Elleo> I might have had a few extra things installed from testing something else beforw, so I'll try with a blank slate
[09:56] <Elleo> tsdgeos: could you also upload your latest crash file, just so we can be sure its happening in the same place?
[09:57] <Add_> Any guys here on an active porting project?
[09:58] <JamesTait> Good morning all; happy Friday, and happy Day of Unplugging! :-D
[10:12] <DonkeyHotei> can someone with a mako/nexus4 please pastebin syslog?
[10:26] <mardy> any idea why "adb shell" returns "error: closed"?
[10:27] <abeato> mardy, you need to unlock the phone before using adb nowadays
[10:29] <mardy> abeato: like explained here? https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[10:30] <mardy> abeato: it tells me it's already unlocked
[10:30] <abeato> mardy, no, I was talking about simply unlocking the screen, and you need developer mode activated too
[10:31]  * abeato guessing ubuntu already installed on the phone :)
[10:31] <mardy> abeato: yes, it's installed :-) I'll try that, thanks!
[10:31] <abeato> np
[10:33] <mardy> abeato: indeed, that was it
[10:54] <ogra_> ricmm, sabdfl is asking about a location service crash in #ubuntu-desktop ... bu 1419405 ... looks like platform-api kills it there ...
[10:54] <ogra_> *bug 1419405
[10:55] <ogra_> is that because the dummy provider isnt running ?
[13:02] <studio_> hi
[13:04] <popey> hi
[13:04] <popey> studio_: i have a message from renatu for you...
[13:04] <renatu> hi
[13:04] <popey> oh. there he is
[13:04] <popey> http://paste.ubuntu.com/10550273/
[13:04] <popey> to save renatu typing ㋛
[13:05] <renatu> thanks :D
[13:17] <studio_> how to update only this one package? normally i make "sudo apt-get upgrade", but i shouldn't do that right?
[13:17] <ogra_> you use apt-get install
[13:18] <studio_> ok
[13:20] <studio_> hmm, now i have import from sim card, but it tells me sim card is empty?
[13:21] <ogra_> well, wait for bfiller to show up ... he can probably help you
[13:21] <studio_> ok
[13:23] <studio_> no, wait, now i can see all contacts! :)
[13:23] <ogra_> ah, just took a while
[13:23] <studio_> cool :)
[13:23] <ogra_> sim cards are perhaps not the fastest interface :)
[13:27] <studio_> cool, was able to import all contacts from the sim card. many thanks :
[13:28] <popey> nice!
[13:28] <popey> thanks for testing studio_
[13:28] <studio_> np :)
[13:29] <ogra_> let bfiller and renatu know :)
[13:29] <renatu> studio_, thanks
[13:33] <studio_> ok, bbl :)
[13:33] <studio_> bye
[13:50] <jjkl> hello everybody
[13:51] <popey> hi
[13:57] <jack__> how can ic aht here |??
[13:57] <jack__> hello
[13:57] <jack__> anybody here ??
[13:57] <popey> yes
[13:57] <jack__> oh nice
[13:57] <jack__> hi popey
[13:57] <popey> hello
[13:58] <jack__> could you help me ?
[13:58] <popey> dunno, depends what you need help with.
[13:58] <popey> Mindreading, I don't do.
[13:58] <jack__> i have galaxy tab p7500 but i found that ubuntu touch is only for p4wifi how can i install ubuntu on my tab
[13:59] <popey> you'd need to port it.
[13:59] <popey> we have a porting guide
[13:59] <popey> It's not a simple / straightforward process.
[13:59] <popey> Or you can find someone else to do the port for you.
[14:00] <jack__> i falshed the cm10 but for p4 and install ubuntu but i couldn't succed
[14:02] <jack__> COULD ANYONE INSTALL UBUNTU ON P7500 TAB ?
[14:02] <jack__> anybody there ??
[14:03] <popey> jack__: dude, I answered you!
[14:03] <jack__> ok thanks
[14:03] <jack__> i described my issue if you see that
[14:04] <jack__> i can explain again would you ?
[14:04] <popey> jack__: I answered you. Can you not see the answer above?
[14:04] <bregma> the webbrowser-app is broken on the Unity 8 desktop trying to look for a non-existent X server, anyone know who can look at that?
[14:05] <popey> bregma: oSoMoN
[14:05] <jack__> popey: i can't see your comment
[14:06] <popey> jack__: http://imgur.com/wtQsLqy
[14:07] <popey> jack__: it looks like there is no port for p7500, but you could port it, or someone else could port it.
[14:07] <Elleo> tsdgeos: made some progress! with a completely clean install the crashes do still happen, however after installing the ubuntu-keyboard-autopilot package they stop (which is why it was working for me previously, because I usually have that installed); so I suspect it's some dependency of that package which actually solves the problem and should be added as a dep to the ubuntu-keyboard package
[14:07] <oSoMoN> bregma, can you please file a bug against https://bugs.launchpad.net/webbrowser-app/+filebug with relevant info?
[14:07] <tsdgeos> Elleo: wow, that's weird :D
[14:08] <jack__> how can i learn to port ? could you give me the link ?
[14:08] <Elleo> tsdgeos: now I just have to figure out why that's the case with 5.4.1 and not 5.4.0 and which package it is we need
[14:08] <popey> jack__: https://wiki.ubuntu.com/Touch/Porting
[14:08] <bregma> oSoMoN, https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1429135
[14:09] <oSoMoN> bregma, thanks, will take a look
[14:09] <jack__> popey : thanks alot popey i try it now ;)
[14:10] <popey> jack__: no problem
[14:10] <Elleo> tsdgeos: looks like I spoke too soon :P after restarting its now back to crashing again :/
[14:10] <tsdgeos> :/
[14:11] <jack__> popey: sorry it's complicated is there any other way ?
[14:12] <jack__> popey:i managed to install ubuntu but it installed in my data folder at root
[14:13] <jack__> popey:i can see all of ubuntu touch conent but they are all in data/ubuntu
[14:15] <jack__> popey:i can't install it in my root
[14:15] <adrian47> I have 4.1MB boot partition and 6.7MB boot.img file, someone has idea what can i do?
[14:17] <jack__> popey: are you there ?
[14:17] <popey> jack__: sorry, went to get some lunch
[14:18] <popey> jack__: yes, it's complicated, I said that
[14:18] <dobey> jack__: you can't just put an existing image for another device on your device. you must build the proper kernel with proper drivers and create a new image specifically for your device, then flash it on
[14:19] <jack__> which device is nice ?
[14:20] <jack__> i don't know about porting and cooking
[14:20] <dobey> then you'll have to wait until someone else with the same device, does the work
[14:21] <jack__> hi dobey ok but i managed to install ubuntu
[14:21] <jack__> but i boot into cm10 and all of ubuntu touch contents installed in data/ubuntu
[14:22] <jack__> if i copy it's contents to root is there any hope
[14:22] <popey> thats not how it work
[14:23] <jack__> i'm newb help me please
[14:23] <dobey> no you didn't install ubuntu
[14:24] <dobey> i don't know what data you put in the data/ubuntu/ folder, but that is not how you install ubuntu
[14:24] <popey> jack__: you have the answers.
[14:24] <popey> jack__: port it, or find someone else to port it, or buy a different device (like a nexus 4)
[14:25] <jack__> no i didn't put it i installed ubuntu in cwm then i see all of it's contents in data/ubuntu
[14:25] <dobey> no
[14:25] <popey> jack__: it doesn't work like that.
[14:26] <dobey> there is no image for your device, so you can't have installed it
[14:26] <Elleo> jack__: it's possible that you might have setup an ubuntu chroot on android, that's a completely different thing to installing ubuntu touch though
[14:26] <jack__> but p4wifi is very similler to p4 as you know
[14:27] <jack__> i even succeed to install p4wifi stock firmware on my tab
[14:29] <jack__> but what is the difference between two device ?
[14:31] <sil2100> tsdgeos, Elleo: hmmm, I just installed Qt 5.4.1 from the silo PPA on my vivid phone and maliit is still crashing
[14:31] <sil2100> Is that only on my phone? (krillin)
[14:32] <Elleo> sil2100: no, the rebuild doesn't fix it, that was just coincidental
[14:32] <Elleo> sil2100: at some point after having it installed it seems to stop crashing
[14:32] <sil2100> Ah, ok :)
[14:32] <dobey> jack__: generally, drivers. i don't know the exact differences. but you need an image built specifically for that device, and one does not exist.
[14:32] <Elleo> sil2100: but I have no clue why
[14:32] <sil2100> hmmm
[14:32] <Elleo> sil2100: I hate this bug :P
[14:32] <sil2100> heh ;)
[14:33] <jack__> ok so there is no way except porting it this right ?
[14:34] <dobey> jack__: as we've already said several times, yes, it must be ported
[14:35] <jack__> how can i learn porting is there any site for training i love these stuffs
[14:36] <dobey> jack__: again, that was already answered and you were pointed to the porting guide link, which is also in the channel topic
[14:37] <jack__> you're right but i can't start it from it's level i don't know anything about building porting cooking and so fourth
[14:39] <jack__> ok thank you dear popey and dobey good luck and have fun
[14:40] <kenvandine> mardy, i saw your qtmir bug 1428246, so that's failing to create the session?
[14:40] <kenvandine> mardy, in my content-hub branch, i think my session is getting created, but i'm having problems with it rejecting the client
[14:41] <kenvandine> mardy, i get starting then stopping state changes
[14:41] <kenvandine> mardy, so that's different than what you're getting?
[14:42] <mardy> kenvandine: yes, it's different; AFAICT, we have a problem when we nest a trust session withing another one (created by pay ui)
[14:42] <kenvandine> oh that sounds nasty :)
[14:43] <kenvandine> i've been frustrated just doing one :)
[14:43] <mardy> kenvandine: I don't think that that bug is relevant to the content hub
[14:43] <kenvandine> now i enabled some more reporting in Mir, and the shell isn't starting :/
[14:43] <studio_> back
[14:43] <mardy> kenvandine: do you have a log? I don't understand why the client could be rejected
[14:44] <kenvandine> not handy... but the session goes to starting then to stopping
[14:44] <mardy> kenvandine: do you mean the initiator client, or the newly created one?
[14:44] <kenvandine> initiator
[14:44] <kenvandine> i see the session created, started then stopped
[14:44] <kenvandine> i was having a ref problem
[14:44] <kenvandine> when it was getting destroyed
[14:45] <kenvandine> but i fixed that, no longer even hit the destructor
[14:45] <mardy> kenvandine: could it be that you are starting the second process outside of the trust session, which would cause it to get focused and your session to get stopped?
[14:45] <kenvandine> mardy, i was just wondering if i might have been hitting a mir bug now :)
[14:45] <kenvandine> the other app never even starts up
[14:45] <studio_> i have seen, there is a bug in the filemanager, it can't show a link in the "normal" mode
[14:46] <kenvandine> my handler runs it in the trusted session, and Mir rejects it
[14:46] <kenvandine> so it exits
[14:46] <kenvandine> before even starting the app
[14:46] <kenvandine> mardy, i also know i have a valid handle for the file descriptor
[14:47] <mardy> kenvandine: if you don't start the handler, do you still get the session stopped?
[14:47] <kenvandine> actually... wait i'm not getting the stopped now :)
[14:47] <kenvandine> forgot i fixed that last night :)
[14:47] <kenvandine> so  yeah, it's started
[14:47] <mardy> :-D
[14:47] <kenvandine> but the client is rejecting it
[14:48] <kenvandine> before it threw an error
[14:48] <kenvandine> now just logging the rejection and exiting
[14:48] <mardy> kenvandine: client being the second one being started, right?
[14:48] <kenvandine> yeah
[14:48] <kenvandine> i'm using something very similar to pay-service
[14:49] <kenvandine> the mir-connection-demangler
[14:49] <kenvandine> mardy, have you had any success enabling more logging from Mir?
[14:49] <kenvandine> i needed some reporting in the env, and now it's not starting
[14:49] <mardy> kenvandine: never did that, sorry
[14:49]  * kenvandine askes in the mir channel
[14:54] <studio_> maybe someone can check this: http://paste.ubuntu.com/10550783/ ?
[15:11] <dobey> studio_: file a bug. irc isn't where bug reports get filed, launchpad is
[15:14] <studio_> i thought, you can send it to the right person? i am not an "active" beta tester, but i like to learn :)
[15:34] <dobey> studio_: https://bugs.launchpad.net/ubuntu-filemanager-app/+filebug
[15:36] <popey> studio_: it won't be, file manager knows what a real sd card is
[15:37] <popey> studio_: open file manager and open the menu in the top right, and choose "unlock full access"
[15:37] <studio_> popey, but it can't handle a link
[15:37] <dobey> popey: it should probably support symlinks though
[15:37] <popey> then you will probably see it
[15:37] <popey> no, its working as desingned
[15:37] <popey> I expect studio_ hasn't unlocked it
[15:38] <dobey> symlinks only work with "full access" ?
[15:38] <studio_> as i told, in advanced mode it is working
[15:38] <popey> dobey: only specific mtp folders are shown by default
[15:38] <popey> nothing to do with symlinks
[15:38] <popey> yeah, tested here, works fine when you unlock full access
[15:39] <studio_> my device is locked, and link is only working in advanced mode?
[15:39] <popey> yes
[15:39] <studio_> why?
[15:39] <dobey> oh ok
[15:39] <dobey> studio_: he just answered that
[15:40] <popey> Long story.
[15:40] <popey> The app is unconfined which is rare in the store.
[15:40] <popey> As a security precaution we only expose a fixed set of folders, Music, Documents etc in the file manager
[15:40] <popey> if you type in your pin, you unlock it and you can do anything
[15:40] <studio_> popey, is it depending on sd-card or on a link, i do not understand your answer? sorry :(
[15:41] <popey> No, neither.
[15:41] <popey> The file manager only shows specific folders by default.
[15:41] <popey> The same folders we expose over MTP
[15:41] <popey> If you enter your pin, you unlock the app and can use it to access and file on the filesystem
[15:41] <popey> Which includes your symlink and the SD card.
[15:41] <studio_> "The file manager only shows specific folders by default." ok, but why no link?
[15:42] <popey> because it's not one of the specific folders
[15:42] <popey> the specific folders are Documents, Downloads, Music, Pictures, Videos.
[15:42] <popey> Your folder is not one of those.
[15:42] <dobey> sigh
[15:42] <ogra_> it is a hardcoded list of paths
[15:42] <cyphermox> magic word.
[15:43] <popey> :)
[15:43]  * ogra_ swings the wand
[15:44] <studio_> so even if i have a "link" to my local network, for exp. a video it will not be schon?
[15:44] <popey> correct
[15:44] <studio_> hmmm ...
[15:44] <popey> unless you put the file in one of those folders
[15:44] <popey> or unlock the app
[15:45] <studio_> ok
[15:45] <popey> or build your own version of the app without this feature
[15:45] <popey> \o/ Free Software
[15:48] <ogra_> studio_, do you see the "unlock full access" button at the bottom of the app ?
[15:48] <ogra_> tap it, enter your pw and you should see the link
[15:48] <popey> its not at the bottom, its in the menu at the top
[15:48] <ogra_> not on my vivid
[15:48] <popey> what version?
[15:49] <ogra_> might be i'm a bit behind though
[15:49] <popey> oh, maybe I am :)
[15:49] <ogra_> a few days old
[15:50] <popey> nope, just installed from store, its in the menu
[15:50] <popey> what version do you have? and why is it so old?
[15:50] <popey> com.ubuntu.filemanager  0.4.386
[15:51] <ogra_> phablet@ubuntu-phablet:~$ click list|grep file
[15:51] <ogra_> com.ubuntu.filemanager	0.3.303
[15:51] <popey> do you have a funky phone or something?
[15:51] <studio_> ogra_, yes, that is what i called "advanced" mode
[15:51] <popey> this is worrying
[15:51] <ogra_> i'm on arale, with a location service custom tarball ...
[15:51] <ogra_> might be that there is some old cruft in there
[15:52] <ogra_> i'll start to get worried once arale is on the server :)
[15:52] <popey> ok
[15:52] <dobey> ogra_: and you haven't installed the udpate from the store i guess :)
[15:52] <studio_> ogra_, in "advanced" mode i can see the link
[15:52] <ogra_> i usually dont check for updates since i need to re-flash anyway
[15:52] <ogra_> studio_, good, then all is fine
[15:53] <studio_> sorry, don't understand that
[15:53] <dobey> the app works as designed
[15:54] <ogra_> studio_, that we dont want people that you hand your phone to browse your files without knowing your pin/pw ?
[15:54] <studio_> is it "designed" with that bug?
[15:54] <ogra_> this is a feature, not a bug
[15:54] <studio_> :) ok
[15:54] <ogra_> if you give someone your unlocked phone to make a call he can not access your files
[15:55] <ogra_> same goes for the terminal app btw
[15:56] <studio_> ahh, now i understood, sorry took some time ...
[15:59] <studio_> but, how to make a different between unlock the screen and unlock the phone?
[16:01] <popey> studio_: i dont understand the question
[16:02]  * ogra_ notes that popey sounds liek a bot today 
[16:02] <ogra_> popey, are you a 13 year old boy from urkaine ?
[16:02] <popey> haha
[16:02] <popey> Just call me Eliza
[16:02] <studio_> screen is closed after for exp. 1 min. i have to use password or pin to unlock, but it is the same as the "root" password / or pin
[16:02] <ogra_> (that proves it !)
[16:03] <popey> studio_: yes
[16:03] <ogra_> studio_, yes, we use the passwd file to store it :)
[16:03] <ogra_> (or the shadow file rather)
[16:03] <ogra_> like on your desktop
[16:04] <studio_> the "normal" sd-card in fat32 is allways mounted, sorry my is now ext4, and it is shown in the filemanager?
[16:05] <ogra_> yes
[16:06] <studio_> so ext4 is more secure than, because it in not shown in the filemanager?
[16:06] <ogra_> no, ext4 is simply not supported yet
[16:06] <studio_> ext4 is supported
[16:06] <ogra_> you can get all sorts of issues with file permissions etc
[16:06] <ogra_> that nothing in the UI can handle
[16:07] <ogra_> so we do not support it yet
[16:07] <ogra_> (if we will at all)
[16:08] <studio_> i have full access to my ext4 formated sd-card, why do you say it is not supported?, i do not understand that :(
[16:09] <ogra_> we do not support it
[16:09] <ogra_> despite the fact that you can technicall yuse it, it is not part of our phone concept to support etx4 SD cards yet
[16:10] <ogra_> (and possibly also not in the future)
[16:12] <studio_> that means yin yang?
[16:12] <popey> studio_: "supported" can mean "it works", or it can mean "We will help you if it breaks"
[16:12] <popey> studio_: in this case, it works, but we won't help you if it breaks.
[16:12] <popey> ergo, "not supported"
[16:13] <studio_> ok, i understood, can do, but not supported ...
[16:14] <popey> yes
[16:14] <ogra_> like you can use apt ;)
[16:14] <studio_> ;)
[16:15] <studio_> ok, now i have another question, how to browse my local network on ubuntu-touch?
[16:17] <popey> not implemented yet
[16:17] <studio_> ok
[16:43] <yacuken> hi folks. i wanna run ubuntu on my 1+1. maybe someone has already started to poring? for join team instead of working from scratch (:
[16:46] <popey> tsdgeos: where should I get the debug symbols for everything calendar is using? (trying to debug it now)
[16:46] <tsdgeos> popey: do you have the ddebs repository enabled?
[16:47] <popey> tsdgeos: no, assume I know nothing :)
[16:47] <popey> its a fairly clean install on a nexus 7 running vivid
[16:48] <tsdgeos> so the process would be
[16:48] <tsdgeos> run it in gdb
[16:48] <tsdgeos> make it crash
[16:48] <tsdgeos> look for lines that say somelibrary.so
[16:48] <tsdgeos> then you do a dpkg -S  somelibrary.so
[16:48] <tsdgeos> to know which package it's part of
[16:48] <tsdgeos> and install the correspondign dbgsym for that package
[16:49] <tsdgeos> dbgsym packages are created in http://ddebs.ubuntu.com
[16:49] <popey> ok
[16:49] <popey> tsdgeos: when it crashed it didnt mention libraries
[16:50] <tsdgeos> popey: if it's the backtrace you showed me the other day, it did
[16:50] <popey> tsdgeos: do i need all the ones from line 19 down http://paste.ubuntu.com/10551334/
[16:50] <DonkeyHotei> cyphermox: are you around?
[16:50] <ogra_> yanghy, you want mariogp i think ... he did a port thats not complete yet
[16:50] <tsdgeos> popey: no, not all, showme the backtrace once it has crashed and we can go on from there
[16:51] <ogra_> (but he doesnt seem to be here currently)
[16:51] <popey> tsdgeos: ok
[16:51] <popey> Program received signal SIGSEGV, Segmentation fault.
[16:51] <popey> 0xb6d7fe4a in QQuickItemPrivate::siblingOrderChanged() () from /usr/lib/arm-linux-gnueabihf/libQt5Quick.so.5
[16:52] <popey> tsdgeos: http://paste.ubuntu.com/10551340/
[16:52] <tsdgeos> hmmm
[16:52] <tsdgeos> this backtrace is differnet from the other day
[16:52] <popey> very easy to reproduce
[16:52] <popey> could be, yes.
[16:52] <popey> but this is the one I can easily reproduce
[16:52] <tsdgeos> anyway, so now you need the symbols of libQt5Quick.so.5
[16:53] <tsdgeos> so dpkg -S libQt5Quick.so.5
[16:53] <tsdgeos> which will tell you libqt5quick5
[16:53] <tsdgeos> so install libqt5quick5-dbgsym
[16:54] <tsdgeos> make sure you have deb http://ddebs.ubuntu.com vivid main universe
[16:54] <tsdgeos> in your apt config
[16:54] <tsdgeos> and have apt-get update 'd
[16:55] <yacuken> ogra_: ok. i found him. mariogrip. thankyou
[16:55] <DonkeyHotei> ok, in desktop ubuntu, bluetooth device drivers live in the kernel, but in android they appear to live in userspace, and i don't see either in ubuntu-touch. is anyone around who can shed light on this?
[16:55] <DonkeyHotei> ogra_: ^
[16:55] <ogra_> the actual drivers live in the android container ...
[16:56] <DonkeyHotei> ogra_: i don't see any bluetooth provisions in the libhybris that's used
[16:56] <ogra_> for broadcom BT hw you need to load the firmware to make teh driver do something though ... the firmware loading is done from eth ubuntu side for these
[16:56] <ogra_> no, BT doesnt go trough hybris iirc
[16:57] <DonkeyHotei> so how does ubuntu talk to it, then?
[16:57] <ogra_> the basic initialization of the driver happens on the android side, further bits live all on the ubuntu side
[16:57] <ogra_> via device nodes
[16:57] <DonkeyHotei> how does ubuntu discover them?
[16:57] <popey> tsdgeos: ok
[16:58] <ogra_> no idea, thats a question for cyphermox
[16:58] <tsdgeos> popey: then rinse and repeat
[16:58] <ogra_> i kno how the driver init works ... thats al
[16:58] <DonkeyHotei> i wanna see where the init is
[16:58] <ogra_> in /etc/init on the phone
[16:58] <ogra_> look for anything with bluetooth
[16:58] <DonkeyHotei> init.rc?
[16:59] <ogra_> in the upstart jobs
[16:59] <ogra_> init.rc lives iin the container
[17:03] <DonkeyHotei> ogra_: out/target/product/*/root appears to be the container, but i don't see where the touch fs is made
[17:04] <ogra_> the ubuntu rootfs you mean ?
[17:04] <DonkeyHotei> yes
[17:05] <studio_> hmm, seems to be a problem after the latest update from today, to get sync with the phone?!
[17:05] <ogra_> DonkeyHotei, thast built like any ubuntu iso on cdimage ...
[17:06] <ogra_> from deb packages
[17:06] <studio_> tunar can't mout it anymore?
[17:06] <studio_> mount
[17:07] <studio_> adb is still working
[17:07] <ogra_> studio_, is the screen unlocked ?
[17:07] <studio_> no
[17:07] <DonkeyHotei> ogra_: they're not expanded into a directory?
[17:07] <ogra_> studio_, then this is also expected behavior
[17:08] <ogra_> DonkeyHotei, how do you mean ?
[17:08] <ogra_> studio_, unlock it and you should b able to browse
[17:08] <DonkeyHotei> afaik isos are built by expanding debs into a squashfs
[17:09] <ogra_> well, for touch this is a tarball
[17:09] <DonkeyHotei> tarballs are created from a directory
[17:09] <ogra_> which gets consumed by system-image together with a device tarball made from the git tree
[17:09] <ogra_> sure
[17:09] <DonkeyHotei> i don't see that directory
[17:09] <cyphermox> ogra_: DonkeyHotei: no use looking too hard on hammerhead there is nothing useful, because it gets all done behind the scenes by bluedroid
[17:09] <ogra_> on your phone ?
[17:10] <ogra_> it is / there
[17:10] <ogra_> cyphermox, ah, no brcm then
[17:10] <studio_> ogra_, will that be fixed in a "release version? I thought mtp is the normal way to sync?
[17:10] <DonkeyHotei> ogra_: i am looking in the build dir
[17:10] <ogra_> studio_, fixed ?
[17:10] <cyphermox> ogra_: yeah, brcm
[17:10] <DonkeyHotei> cyphermox: how is it done on mako?
[17:10] <ogra_> cyphermox, then brcm-patchram should work, no ?
[17:10] <ogra_> with adjustments indeed
[17:11] <ogra_> studio_, this is wanted behavior ... liek with the filemanager we dotn want anyone who steals your phone to be able to download your photos or call logs via mtp
[17:11] <studio_> ogra_, i never had this error before, this is new to me
[17:11] <ogra_> there is no error :)
[17:12] <ogra_> the mtp server on the phone doesnt serve anything if the screen is locked on connect attempt
[17:12] <cyphermox> ogra_: it *should* but you'll still need to figure out what device to use, and what parameters to pass it
[17:12] <ogra_> as soon as you unlock th screen it will start to serve you
[17:12] <studio_> first my device was "unlocked" and i had no problems to sync with ubuntu, but now i have?
[17:12] <ogra_> cyphermox, right
[17:13] <ogra_> studio_, if it is locked now, it does what it should
[17:13] <ogra_> if your screen is unlocked and you cant access the phone, that would be a bug
[17:13] <DonkeyHotei> cyphermox: how is it done on mako?
[17:14] <ogra_> pointis, if the user did set a pin or password it is clear that he cares about security
[17:14] <ogra_> so we want all access to the phone to beprotected by this pin/password
[17:14] <studio_> screen unlocked and no sync, that is what i told you
 studio_, is the screen unlocked ?
 no
[17:14] <ogra_> that is what you told me :)
[17:15] <ogra_> i it is in fact unlocked and you cant open drs on the device via mtp, that is a bug
[17:16] <ogra_> and most likely one i'm just working on a fix for ;)
[17:16] <studio_> mtp not possible :( so that is new ...
[17:16]  * ogra_ is in the middle of re-designing the behaior of all USB related services (adb, mtp, usb-tethering)
[17:17] <ogra_> studio_, feel fre to file a bug on launchpad and assign it to me or point me to the bug number and i can assign it
[17:19] <studio_> how many copys of the bug report do you need? ;)
[17:19] <ogra_> one is enough for the management to actually assign worktime for it
[17:19] <ogra_> :)
[17:22] <ogra_> rsalveti, lol, grepping for "timeout" in /etc/init reveals that everyone has his own implementation of timeouts :)
[17:23] <rsalveti> ogra_: yup :-)
[17:23] <rsalveti> DonkeyHotei: hammerhead is different because we don't have an hci driver in the kernel
[17:23] <rsalveti> DonkeyHotei: it depends entirely on bluedroid, which creates a problem for us because we don't support that yet
[17:24] <popey> renatu: is this even remotely useful for a calendar crash? http://paste.ubuntu.com/10551473/
[17:24] <rsalveti> we don't yet support using the android hardware abstraction layer for bluetooth
[17:24] <DonkeyHotei> rsalveti: hi. what did you think of my proposal?
[17:24] <ogra_> popey, why do you crash the calendar ! want to make davmor2 jobless ? thats his job !!
[17:24] <ogra_> :)
[17:24] <rsalveti> sorry, didn't yet check, many meetings this week
[17:25] <popey> ogra_: it's super easy to crash it
[17:25] <davmor2> ogra_: Cause I'm too busy killing vivid
[17:25] <DonkeyHotei> rsalveti: what hci driver in the kernel is used for mako?
[17:25] <ogra_> popey, i never open it ... in fact i only have it installed to get gcal events :P
[17:25] <popey> i need to be able to debug this
[17:25] <popey> because I don't want davmor2 to reject it from going in the image
[17:25] <popey> so help welcome!
[17:25] <popey> :)
[17:26] <davmor2> popey: :)
[17:26] <ogra_> nothing a good box of tea couldnt help with, no ?
[17:27] <rsalveti> DonkeyHotei: just check the mako's kernel tree and you'll see
[17:27] <popey> ooh got a better one
[17:27] <rsalveti> don't remember the driver name out of my head
[17:28] <popey> renatu: http://paste.ubuntu.com/10551505/ might be better!
[17:28] <DonkeyHotei> rsalveti: is it under drivers or under arch/arm?
[17:29] <rsalveti> DonkeyHotei: either there or under drivers/, would have to look
[17:30] <renatu> popey, it does not look like a eds crash
[17:30] <renatu> popey, looks like some problem with qML model
[17:31] <popey> any idea where to file a bug?
[17:31] <DonkeyHotei> rsalveti: i'll look. check for an e-mail i sent
[17:31] <ogra_> rsalveti, oh, is my calendar mad or do we have a meeting ?
[17:31]  * ogra_ thought we did the sprint review last week
[17:31] <ogra_> my phone just notified me
[17:31] <renatu> popey, ok the first one looks like EDS related
[17:32] <renatu> popey, but I am not sure
[17:32] <rsalveti> ogra_: which calendar, from the phone?
[17:32] <ogra_> yeah
[17:32] <rsalveti> ogra_: if so, then it's the usual not-in-sync issue
[17:32]  * ogra_ checks on google
[17:32] <rsalveti> if there is one thing that makes me unhappy with the phone is the calendar app and calendar sync process
[17:32] <rsalveti> the app crashes all the time for me
[17:32] <ogra_> yeah. lies !!!
[17:32] <rsalveti> and sync never really works
[17:33] <ogra_> right, i just brought that up on #ubuntu-ci-eng
[17:33] <popey> rsalveti: see above!
[17:33] <renatu> popey, add qtogranizer-eds as affected on the bug report
[17:33] <popey> renatu: ok
[17:33] <ogra_> the app runs for me on rtm krillin
[17:33] <renatu> popey, but I will need do a deep investigation to confirm that
[17:33] <rsalveti> popey: ewww
[17:33] <ogra_> (i just openend it)
[17:33] <renatu> popey, is that critical?
[17:33] <popey> yes.
[17:33] <rsalveti> crashes for me on rtm/krillin
[17:34] <ogra_> funny
[17:34] <popey> it is easy to crash it by switching views when it's loading the events
[17:34] <rsalveti> it's that app that I get the feeling that it hates me
[17:34] <renatu> popey, then you should ping bfiller to put it on the list
[17:34]  * ogra_ checksfor app update
[17:34] <popey> renatu: ok, thanks
[17:34] <ogra_> hmm, seems i'm up to date
[17:34] <popey> renatu: the reason I say critical is because product management have asked to include in the image
[17:34] <ogra_> probably i'm just lucky
[17:34] <popey> but we can't if it wont pass QA
[17:35] <renatu> popey, would be very nice if the calendar guys could isolate the bug in a small example
[17:35] <renatu> popey, calendar app is to complex t test it
[17:35] <popey> hm.
[17:36] <ogra_> ricmm, oh, i just remembered what i wanted to ask you ... on arale i get white screen webviews all the time ... is that a cache issues (or rather cgroups or oxide)
[17:36] <ogra_> every tie the app was in bg for a while ... not necessarily killed though (happens with only two apps open as well, so i dont think OOM kicked in)
[17:37] <ricmm> ogra_: no idea, but the cache works the same on all devices
[17:37] <ricmm> there are not device specific issues
[17:37] <ogra_> k
[17:37] <ricmm> also, what does not necessarily killed mean
[17:37] <ricmm> did you check the process list
[17:37] <ogra_> nope
[17:37] <ricmm> its either killed or running
[17:37] <ogra_> but i cantreally imagine it was OOMed
[17:38] <ricmm> you'd surprised
[17:38] <ogra_> with that amount of ram ?
[17:38] <ricmm> sure why not
[17:38] <ogra_> and only two webapps open
[17:38] <ricmm> really depends on what it does with images and so on
[17:38] <ricmm> how Qt manages stuff in memory, etc
[17:38] <ricmm> in general, things consume more ram on arale than on krillin
[17:38] <ogra_> ok, i'll keep an eye on the procsslist
[17:38] <ricmm> due to assets that go through ram before being uploaded to texmem
[17:42] <rsalveti> oxide eats a *lot* of memory
[17:42] <rsalveti> that and qt, boom
[17:42] <rsalveti> but that's just any browser nowadays
[17:46] <ogra_> 88M for the oxide renderer and 74 for the webapp container
[17:46] <ogra_> for G+
[17:46] <ogra_> i dont think thats enough to trigger OOM if nothing else runs
[17:48] <DonkeyHotei> rsalveti: is drivers/staging/prima what's used for bt on mako?
[17:49] <DonkeyHotei> cyphermox: flo uses broadcom, no?
[17:49] <rsalveti> yeah, that's the one
[17:50] <DonkeyHotei> ok, i see the difference from how hammerhead works, but what about flo?
[17:51] <rsalveti> flo works similarly to mako I guess
[17:52] <ogra_> yeah
[17:52] <ogra_> iirc the upstart jobs to load the patchram are close to identical
[17:55] <DonkeyHotei> ogra_: so mako uses patchram too?
[17:55] <ogra_> i think so, look at the upstart jobs
[17:56] <DonkeyHotei> to see the upstart jobs, i need to find the rootfs dir in the build tree
[17:58] <ogra_> just look on your phone
[17:58] <DonkeyHotei> i don't have one till monday
[17:59] <ogra_> there should be a bluetooth-touch package in the archive that has them
[17:59] <ogra_> jst pull th source
[17:59] <DonkeyHotei> thanx
[18:00] <DonkeyHotei> fwiw, mako has a kernel hci driver and hammerhead does not, but i'm not sure about flo
[18:09] <DonkeyHotei> rsalveti, cyphermox: do grouper or maguro have a kernel hci driver, or are they more like hammerhead?
[18:11] <rsalveti> iirc it also has an hci driver
[18:11] <rsalveti> any hardware that supports android <= 4.1 has it afaik
[18:11] <DonkeyHotei> interesting
[18:12] <dobey> rsalveti: but does it still have it with android 4.4 is the question, i guess
[18:16] <Tassadar> hammerhead didn't have 4.1
[18:17] <DonkeyHotei> Tassadar: question is, did anything that had 4.1 have a driver that could work on hammerhead?
[18:20] <DonkeyHotei> rsalveti: since 4.2 and above may not have hci drivers, is the plan from this point forward to cobble together hci drivers at this time, or expand libhybris to bluetooth? sailfish uses libhybris for bluetooth
[18:22] <rsalveti> is making bluez to work with libhybris in order to support the android HAL for bluetooth
[18:22] <Stskeeps> rsalveti: you guys started that yet, ooi?
[18:23] <Stskeeps> and b5 or b4?
[18:23] <rsalveti> Stskeeps: not yet, in our backlog still, but that would be for b5
[18:23] <Stskeeps> :nod:
[18:23] <rsalveti> because intel already made bluez to support hal when running natively on android
[18:24] <rsalveti> so it would need a mix of that and a mix of the default implementation
[18:24] <Stskeeps> morbid question, did you do the bluetooth certification of your bluez4 stack for bq device?
[18:24] <Stskeeps> we thought same regarding b5/hal, so
[18:24] <rsalveti> Stskeeps: that's a good question, would need to ask the product team
[18:24] <Stskeeps> and recertification of existing devices will be a mess
[18:25] <rsalveti> indeed
[18:25] <Stskeeps> which then means some devices in field might be b4, some b5, etc..
[18:26] <DonkeyHotei> rsalveti: i've seen reports that hci support in bluez hal is incomplete
[18:26] <rsalveti> yeah, we're trying to push one image across many devices, so that would help a bit
[18:26] <rsalveti> but yeah, it's kind of a mess
[18:27] <rsalveti> Stskeeps: luckily both meizu and bq can easily share the same kernel driver
[18:27] <DonkeyHotei> rsalveti: http://www.spinics.net/lists/linux-bluetooth/msg58248.html
[18:27] <rsalveti> but the next device/bsp might require this bluez 5 x hal integration
[18:27] <Stskeeps> nod
[18:28] <Stskeeps> it is a tiny bit tempting to just sidestep bluez, but that's even harder for you guys since you have desktop to take into consideration too
[18:28] <cyphermox> I don't think the issue has anything to do with hci in the kernel
[18:28] <DonkeyHotei> rsalveti: did you read that thread?
[18:29] <cyphermox> this is most likely just one of those evil devices that require you to flash firmware on to some part of the chip before it allows you to do anything
[18:29] <rsalveti> yup, it's not yet fully complete
[18:29] <rsalveti> well, everything is moving to userspace now, on android at least
[18:29] <rsalveti> and that requires all sorts of hackish things
[18:29] <cyphermox> rsalveti: bluez does have a hal support version
[18:29] <cyphermox> rsalveti: it's just a matter of building it
[18:30] <rsalveti> cyphermox: well, not that simple, but yeah, it's a start
[18:30] <cyphermox> (provided it actually has what's needed on android)
[18:30] <cyphermox> right, given the right kernel and a bunch of other crap, but it's "that simple"
[18:30] <rsalveti> right
[18:31] <cyphermox> if the build-depends are there we could have the bluez 5 package build both the linux kernel and android HAL versions with the right conflicts:
[18:31] <cyphermox> from there you just seed whichever is relevant for the type of device
[18:34] <DonkeyHotei> cyphermox: but if there won't be hci drivers for new devices going forward, wouldn't it make sense to rely on just the hal?
[18:34] <rsalveti> right, yeah, that's the goal :-)
[18:34] <cyphermox> DonkeyHotei: the problem is, there are hci drivers on non-Android
[18:35] <cyphermox> we ship a package, it needs to work everywhere
[18:35] <DonkeyHotei> ah
[18:35] <DonkeyHotei> then yes, this is the right approach
[18:35] <cyphermox> so what I was proposing is a way to make the bluez5 source package work on both Touch and Desktop/server, given usage of HAL or otherwise
[18:36] <cyphermox> but it's just speculation, I don't know if we have everything to make the HAL bluez5 version work with our stuff
[18:36] <DonkeyHotei> cyphermox: is the hal currently packaged separately?
[18:36] <cyphermox> no, it's not built at all right now
[18:36] <cyphermox> it comes from the same source
[18:37] <DonkeyHotei> then the source needs repackaging
[18:37] <cyphermox> ie. upstream bluez ships both
[18:37] <cyphermox> no
[18:37] <cyphermox> it's just debian packaging fu if it works
[18:37] <zono> Just got touch working on a device, but touch location is all wrong. Any ideas where to look?
[18:38] <DonkeyHotei> cyphermox: that's exactly what i mean
[18:38] <zono> location being actual touching of the display
[18:39] <cyphermox> DonkeyHotei: it's not repackaging though
[18:39] <cyphermox> it's just changing some things around
[18:39] <DonkeyHotei> yes
[18:39] <cyphermox> actually, more like adding a few lines of code to the rules
[18:40] <DonkeyHotei> yes
[18:40] <DonkeyHotei> what is the src pkg name?
[18:41] <cyphermox> bluez
[18:41] <cyphermox> don't bother spending much time on it now, it needs some other work first
[18:41] <cyphermox> namely, it needs to wait until after we switch to bluez 5
[18:42] <cyphermox> so if you want to do testing, I'd suggest you build bluez 5 on your own (not with the packaging) from the upstream code, for the HAL version, and see if you can make it work on hammerhead
[18:42] <cyphermox> rsalveti: ^ probably doesn't need kernel changes, too
[18:43] <cyphermox> DonkeyHotei: however, this is likely to break bluetooth headset support, because it will need changes in ofono
[18:43] <rsalveti> yeah, might not require any other kernel change
[18:43] <cyphermox> the big *if* I think is whether it has all its build dependencies in a suitable fashion
[18:44] <cyphermox> hmm... and whether it exports DBus functions :)
[18:44] <zono> ah, think I figured it out
[18:46] <DonkeyHotei> cyphermox: debian already has bluez5
[18:47] <dobey> DonkeyHotei: debian isn't built to run on top of android hal
[18:48] <DonkeyHotei> dobey: but the source is still there, no?
[18:48] <ogra_> we have the source in some PPA as well
[18:48] <ogra_> doesnt help if the integration isnt done :)
[18:48] <dobey> right
[18:50] <ogra_> DonkeyHotei, defaulting to bluez5 means that xubuntu.,kubuntu, lubuntu, touch, ubuntu-studio and whatnot need to work with it ... it isnt just "dump it into the archive and forget"
[18:50] <ogra_> ubuntu isnt debian :)
[18:51] <DonkeyHotei> ogra_: so everything has to wait until vivid+1?
[18:51] <cyphermox> not necessarily
[18:52] <cyphermox> but we're coordinating everyone
[18:52] <cyphermox> and that is also still without the HAL build, that will need to be added after
[18:52] <DonkeyHotei> i'd like to be included in the coordination
[18:52] <DonkeyHotei> but isn't the hal included in the upstream source?
[18:53] <cyphermox> it is, but there is further work needed to make it get built
[18:53] <ogra_> DonkeyHotei, the phone most likely has to wait til +1
[18:54] <ogra_> desktops most likely wont
[18:54] <DonkeyHotei> cyphermox: that can be done without touching non-hal binary pkgs
[18:55] <cyphermox> yes, but rather than make multiple changes at once, and risk introducing major issues for everyone, we'd rather do the version transition first, and then look into adding the HAL build
[18:56] <DonkeyHotei> cyphermox: ok, and that's after vivid is released, or after vivid+1 is released?
[18:56] <cyphermox> the version transition should happen incessantly
[18:56] <DonkeyHotei> incessantly?
[18:56] <cyphermox> urgh
[18:57] <cyphermox> wrong word
[18:57] <cyphermox> very soon
[18:57] <DonkeyHotei> like, before vivid is released?
[18:57] <bfiller> popey: are your calendar crashes on rtm or vivid?
[18:57] <cyphermox> hopefully
[18:57] <DonkeyHotei> interesting
[18:57] <popey> bfiller: both
[18:58] <popey> bfiller: the ones listed in my most recent comment were vivid
[18:58] <bfiller> popey: ok, cause vivid has some qtorganizer5-eds changes that rtm does not, but doesn't sound like it fixes your problem
[18:58] <popey> sadly not.
[19:08] <DonkeyHotei> rsalveti: check pm
[19:51] <tntpop> hi
[19:53] <tntpop> I'm looking for some help porting to a new device
[20:16] <zono> tntpop. How much of the porting guide did you follow?
[20:17] <zono> or where are you stuck at?
[20:18] <DonkeyHotei> i'd like to know what directory the ubuntu rootfs is built in
[20:20] <ogra_> in / on a buildd
[20:20] <ogra_> well, in / of a chroot on abuildd rather :)
[20:21] <ogra_> like the desktop isos ... not much different
[20:21] <DonkeyHotei> ogra_: so when i use phablet-dev-bootstrap it just pulls down a prebuilt rootfs?
[20:21] <tntpop> zono. got up to enabling a new device but there seems to be some difficulties when I look at the "Vendor" part
[20:22] <ogra_> DonkeyHotei, no, the android tree onyl builds the container content
[20:23] <tntpop> zono. I have done the steps to get the UT repo and I also have the latest update for device and the sources for the device (afaik what the vendor gives)
[20:23] <DonkeyHotei> ogra_: so a prebuilt ubuntu rootfs is used?
[20:24] <zono> tntpop, if cyangenmod, etc. has already been ported to your device you can locate vendor files from github. Otherwise you can flash cyanogenmod, etc and then get the vendor files.
[20:25] <tntpop> zono, I don't think CG has been ported to this device (let me double check)
[20:26] <ogra_> DonkeyHotei, the system-image OTA server uses a device taball (the container), a generic rootfs (what you ask about) and one or multiple custom tarballs (device specific software selection, vendor changes, branding or whatever) and assembles them to a OTA image
[20:27] <DonkeyHotei> ogra_: but i mean when i use phablet-dev-bootstrap
[20:27] <ogra_> then you build the device tarball (container) nothing more
[20:28] <zono> tntpop. Should also be able to pull in vendor files from the offical rom of the device as well.
[20:28] <tntpop> zono, I'm trying to port to ASUS PadFone (A66) since the HW is fairly interesting and I also have the extensions (tablet and keyboard dock)
[20:29] <DonkeyHotei> ogra_: ah i see, it uses something called rootstock to combine the two. correct?
[20:29] <ogra_> no, rootstock is a hack to use tehtarballs to install a developer setup on a phone/tablet
[20:30] <zono> tntpop so if you can adb pull the vendor dir from the phone, then you should be able to get the files.
[20:30] <ogra_> it uses the system-image server
[20:30] <ogra_> to assemble them ...
[20:30] <ogra_> and your instll uses the system-image client on upgrades to install what the system-image server provides
[20:31] <tntpop> zono, can't do that... been fiddling around with device and tried flashing a rom. Only recovery works now (:( )
[20:31] <DonkeyHotei> ogra_: but to override the rootfs installed i'd need rootstock, right?
[20:31] <ogra_> if you would want to replace it (no idea why anyone would want to though) yes, you could use rootstock
[20:31] <zono> tntpop, No adb in recovery? It isn't always available there but its nice when it is.
[20:32] <ogra_> rootstock is more for porting ... if you dont have a system-image server set up yet for your device
[20:32] <tntpop> zono, can adb in recovery but no more rom installed on device
[20:32] <DonkeyHotei> ogra_: the reason i ask is if i want to test things not in what the system-image server provides
[20:33] <zono> ah. so if no vendor files found on internet, and no rom... idk how your going to get them.
[20:33] <ogra_> and you want to roll a full rootfs for that ?
[20:33] <DonkeyHotei> ogra_: is there a better way?
[20:33] <ogra_> why dont you just use the installed one and modify it
[20:33] <tntpop> zono, I have full rom
[20:33] <DonkeyHotei> on the phone directly?
[20:33] <tntpop> I'll try to flash it
[20:33] <zono> tntpop, so if you can extract them from the rom image, then your golden.
[20:34] <DonkeyHotei> ogra_: on the phone directly?
[20:34] <tntpop> zono, give me a sec ;)
[20:34] <ogra_> fi you have a device that already runs ubuntu you can just make it writable and hack around (indeed better dont use it as a phone since that makes it insecure ... and be prepared that it might fall apart and you need to re-flash)
[20:35] <ogra_> there is no need to roll external rootfses ... you can hack like you do it on your desktop ...
[20:35] <DonkeyHotei> ok
[20:35] <zono> tntpop, extract probably isn't best work. mount image and copy them out.
[20:36] <zono> *best word
[20:36] <DonkeyHotei> and i can use dpkg to test pkg mods?
[20:36] <ogra_> sure
[20:36] <DonkeyHotei> ok
[20:36] <zono> *or whatever it is if its not an image
[20:37] <ogra_> you cant apt-ge upgarde and you will eventually have to re-flash if you hack your system enough ... but  yes, otherwise hacking on it isnt much differennt from any other ubuntu
[20:37] <tntpop> zono, could you help me out here? packages are zip files with boot.img, system folder and loads of .mbm files
[20:37] <DonkeyHotei> i managed to score a 32gb hammerhead with a cracked screen for US$127, it's being delivered monday or tuesday
[20:37] <dobey> ogra_, DonkeyHotei: or just make a chroot within which you do the hacking, on the phone
[20:38] <ogra_> dobey, i assume he wants to test his stuff to :)
[20:38] <ogra_> but yeah, if you need to re-build packages or some such a chroot is the best choice
[20:38] <dobey> ogra_: well you can do the hacking in the chroot, and then test the built deb in the actual system
[20:38] <ogra_> right
[20:38] <zono> tntpop check system folder for vendor folder. N
[20:39] <DonkeyHotei> i hadn't thought of that
[20:39] <dobey> because installing gcc and all the deps on / will lead to a full / partition and pain, very quickly
[20:39] <tntpop> zono, sure
[20:39] <DonkeyHotei> well, where is there room for a chroot?
[20:39] <tntpop> zono, have 2 folders : lib, pittpatt
[20:39] <dobey> DonkeyHotei: in the user home directory
[20:39] <DonkeyHotei> ok
[20:39] <dobey> it's the big data partition
[20:39] <studio_> stupid question, where can i find the nokia navi after the update from today?
[20:39] <zono> tntpop that's it :-(
[20:40] <tntpop> yup
[20:40] <ogra_> studio_, you mean HERE maps ? thats not on the normal enduser images ...
[20:40] <studio_> yes
[20:40] <ogra_> err
[20:40] <ogra_> s/enduser/developer/
[20:40] <tntpop> zono, trying to get other images but network seems slow
[20:40] <ogra_> it is only in the bq image
[20:40] <dobey> studio_: install it from the store
[20:40] <ogra_> dobey, we have it in the store ?
[20:40] <tntpop> zono, any tip on what I should be seeing?
[20:41] <dobey> ogra_: i think it is
[20:41] <studio_> it is in 14.09 but was removed in 15.04?
[20:41]  * ogra_ hasnt seen it 
[20:41] <ogra_> studio_, it is in the 14.09 bq image
[20:41] <ogra_> and only there
[20:41] <zono> tntpop. Um.. I have no idea what's out there. You need a vendor folder or vendor files.
[20:42] <zono> tntpop. When you find that you hopefully found what you need.
[20:42] <studio_> any chance to install that in 15.04?
[20:42] <DonkeyHotei> i ordered a nano-micro-standard sim adapter kit but it's getting drop shipped from overseas so no telling when i'll have it
[20:42] <ogra_> well, i dobey is right the app is in the store
[20:42] <tntpop> zono, any chance the kernel source be of any help?
[20:42] <dobey> ogra_: oh, it is? i just searched and didn't find it
[20:42] <zono> tntpop. Nope
[20:42] <tntpop> zono, it has drivers and firmware
[20:42] <dobey> maybe it was changed to eu only
[20:42] <ogra_> dobey, you just said it is !
[20:43] <dobey> ogra_: oh you typoed :)
[20:43] <ogra_> i thought it was only in the oem tarball from/for bq
[20:43] <dobey> i guess that 'i' was an 'if' :)
[20:43] <DonkeyHotei> ogra_: you've been a valuable resource. thank you
[20:43] <dobey> i thought it was in the store, but i can't see it there
[20:43] <zono> tntpop. Vendors are premade files. So it its pre-made it could be it. But if its in with the kernel source it probably isn't.
[20:43] <ogra_> dobey, yeah, my kbd sucks and i'm on it for to long today already :)
[20:43] <dobey> ogra_: time for scotch :)
[20:43] <ogra_> DonkeyHotei, welcome
[20:43] <ogra_> dobey, !
[20:44]  * ogra_ looks for the glenmorangie
[20:44] <dobey> heh
[20:44] <zono> tntpop. I'm going to do a search too.
[20:45] <tntpop> zono, cheers mate ;)
[20:49] <studio_> so is it possible to install the nokia here on 15.04 or not?
[20:50] <ogra_> well, apparently it isnt in the store
[20:50] <ogra_> http://appstore.bhdouglass.com/ btw
[20:50] <ogra_> (unofficial store webui from the community)
[20:51] <ogra_> so no, it wont be until 15.04 switches over to the bq image
[20:51] <ogra_> (it is shipped with the other vendor bits for bq)
[20:52] <studio_> how to search on "http://appstore.bhdouglass.com/" with firefox on ubuntu?
[20:53] <ogra_> well, its a website, yeah
[20:53] <ogra_> there i a webapp of it in the store :)
[20:53] <ogra_> kind of "inception" the store app for the store in the store
[20:53] <studio_> did you tried it with ubuntu firefox?
[20:53] <DonkeyHotei> nhaines: are you around?
[20:54] <ogra_> studio_, works fine
[20:54] <studio_> maybe i am blind, but there is no "search"
[20:55] <ogra_> there is a thin black line at the top left
[20:55] <ogra_> oh, err, you need to click on apps & scopes indeed
[20:56] <studio_> on top of the left is ubuntu-touch and this is the page
[20:57] <ogra_> do you have javascrip disabled or some such ?
[20:57] <ogra_> works just fine her
[20:57] <studio_> ogra_, there "https://appstore.bhdouglass.com/apps" is also no "search" :(
[20:58] <ogra_> well, i just used it
[20:58] <ogra_> it definitely uses a lot javascript and html5 stuff
[20:58] <studio_> what browser are you using?
[20:58] <ogra_> firefox on utopic
[20:58] <studio_> hmm, same here ....
[20:59] <ogra_> (a few weeks outdated, didnt have time for upgrading my laptop)
[20:59] <ogra_> and i know the page works on my trusty desktop too
[21:00] <studio_> i have category and sort, but not search ?
[21:00] <ogra_> on the left
[21:00] <ogra_> right underneath the "857 apps"
[21:01] <ogra_> there is a thin black line ... thats the search field
[21:01] <ogra_> click it and you get a cursor
[21:01] <studio_> ahhh, now an old guy understood :)
[21:01] <ogra_> :)
[21:01] <studio_> was difficult to understand :)
[21:01] <popey> file a bug :)
[21:02] <studio_> *lol*
[21:02] <ogra_> https://github.com/bhdouglass/ubuntu-appstore/issues
[21:02] <ogra_> ;)
[21:03] <dobey> oi
[21:03] <ogra_> has no bugs ... must be good :)
[21:04] <dobey> i find it amusing that you're willing to accept the TOS for HERE, but you won't create a u1 account to install apps from the store
[21:04] <ogra_> dobey, he has a U1 account now ...
[21:04] <ogra_> studio_, yu should use it on the phone ;)
[21:04] <studio_> sorry for my Chinese , but i am still having problems with the language ;)
[21:05] <ogra_> TOS -> terms of service (EULA)
[21:05] <dobey> oh he does? well that deserves scotch
[21:05] <ogra_> cheers
[21:06] <studio_> dobey, are you sure i dindn't created an account? ;)
[21:07] <dobey> i'm sure you've whine about it plenty in this channel
[21:07] <studio_> ok
[21:08] <dobey> but if you finally created one, then great :)
[21:08] <studio_> ;)
[21:08] <studio_> you help me and i try to help you ....
[21:09]  * ogra_ wanders afk for the evening
[21:11] <popey> \o/
[21:11]  * popey cracks open a doombar and noms a dick
[21:11] <popey> er
[21:11] <popey> duck
[21:11]  * popey leaves
[21:12]  * rww raises an eyebrow
[21:13] <Stskeeps> O_o
[21:17] <tntpop> zono, you found anything interesting?
[21:17] <tntpop> zono, I can give you a few links if you want
[21:18] <zono> ah. it looks like you may have had it. The lib and pittpatt are in the vendor dir
[21:18] <zono> The problem then becomes how to get the make files set up.
 That I don't know how to do as they've always been created already for my devices.
[21:18] <zono> but cyanogenmod gives some info on that. You'll have to search for examples of the files in use for other roms.
[21:18] <zono> http://wiki.cyanogenmod.org/w/Doc:_porting_intro
[21:18] <zono> see -> Add the blobs to the vendor/ directory
[21:18] <zono> Hopefully, you'll know when it works or not as they will cause building to error.
[21:18] <zono> that is if they are not found, etc.
[21:19] <zono> I didn't type that fast
[21:20] <zono> ...unless you already have them
[21:20] <tntpop> zono, I'm trying to get the roms and will try flashing them (let's go the easy way)
[21:20] <tntpop> I'd realy like to get this device up with UT
[21:21] <zono> it is a good idea to get an already build able rom working first
[21:22] <tntpop> sure
[21:22] <zono> It took me a year and half to get ut working lol :-)
[21:22] <tntpop> lol
[21:22] <studio_> hmm, i can't find these nokia here (maps) on the shop :(
[21:23] <tntpop> I think the PAdFone is a really good playground here. the way it goes from a mobile to a tablet then to a netbook
[21:25] <zono> Sounds like a pretty cool device.
[21:25] <tntpop> it is indeed
[21:26] <tntpop> but then ASUS stopped doing these devices and moved to the "phablet" type of device
[21:30] <zono> that's a phabletly phabulos phablet.
[21:33] <tntpop> ok... can't seem to flash a rom
[21:33] <zono> what's happening. flash failing when flashing?
[21:36] <tntpop> recovery is a TWRP, when I try to flash it just says fail
[21:37] <zono> could be the build is for wrong device or its the wrong recovery version for build.
[21:37] <tntpop> I tried WW and CHT (it's a CHT version
[21:37] <tntpop> the TWRP should be able to flash any for that device
[21:39] <zono> the updater-script in the build.zip will say what device the build is flash-able for.
[21:39] <zono> past that, idk. Don't have the device to know its quirks.
[22:50] <renatu> popey, could you give this a try: https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-1423185/+merge/252184
[22:50] <renatu> popey, jenkins will build a package in 1 or 2 hours :d
[22:50] <popey> renatu: sure. will do. thanks.