[00:32] <cyphermox> sergiusens: rsalveti: heh, phablet-tools, I didn't wake up about it, no point now what there has already been a release in PPA...
[01:29] <rsalveti> sergiusens: https://code.launchpad.net/~phablet-team/phablet-extras/ofono-release-112phablet1/+merge/158261
[02:18] <sfrique> rsalveti, are you here?
[02:19] <sfrique> does anyone who knows about ofonod and ril can help me?
[02:25] <sfrique_> anyone?
[02:41] <binhgreat> hello
[02:42] <binhgreat> I flashed ubuntu-touch to my Sony Arc from http://forum.xda-developers.com/showthread.php?t=2226406
[02:42] <binhgreat> It's boot but performance is low
[02:44] <binhgreat> I checked by "top" and find that, hud-service always around 54%, rsyslogd is 44%
[02:45] <binhgreat> Could anyone help me? I think if hud-service and rsyslogd can be disabled or reduce the cpu usage, ubuntu-touch may be run good in my phone
[02:52] <sfrique_> anyone on ril or ofono that can help me?
[03:28] <sfrique_> Ursinha-afk, are you there?
[06:46] <oSoMoN> good morning
[07:08] <dholbach> good morning
[08:00] <road>  hi
[08:01] <road> nobody
[08:47] <shadeslayer> I'm curious, could someone explain how the graphics stack works right now ( the X bits ) on ubuntu touch?
[08:47] <shadeslayer> more specifically to the N10
[08:49] <shadeslayer> ogra_: do you have any idea ^ ?
[08:49] <ogra_> no X bits involved :)
[08:49] <oSoMoN> dpm: ping
[08:50] <dpm> hey oSoMoN
[08:50] <ogra_> in the android layer you have SurfaceFlinger which the Ui attaches to from the ubuntu container via libhybris
[08:50] <oSoMoN> hola dpm
[08:50] <dpm> buenas :)
[08:50] <ogra_> that part will soon be replaced by Mir
[08:50] <oSoMoN> dpm: do you know if jenkins/autolanding is enabled for the core app template branch?
[08:51] <oSoMoN> dpm: I have https://code.launchpad.net/~osomon/ubuntu-phone-commons/appTemplate-packaging-fixes/+merge/157077 which is approved, but hasn’t landed yet
[08:51] <ogra_> shadeslayer, see the Mir spec pon the ubuntu wiki, it has  an overview of "today" and "tomorrow"
[08:51] <ogra_> s/pon/on/
[08:52] <shadeslayer> ogra_: I see, and what if for Kubuntu we want to use X + kwin_gles
[08:52] <shadeslayer> since kwin won't have Mir integration
[08:52] <shadeslayer> ( atleast that's the situation right now )
[08:52] <ogra_> you will be able to use X as you do now
[08:52] <shadeslayer> but graphics acceleration?
[08:52] <dpm> oSoMoN, I think it's only enabled for the core apps. If you think it makes sense for it to autoland, I think we can just ping mmrazik (who doesn't seem to be online right now) and add it to jenkins. For now, I could merge in your change manually
[08:52] <ogra_> we dont plan to drop it from the archive :)
[08:53] <ogra_> once Mir enters the desktop there will also be XMir
[08:53] <shadeslayer> haha, no, I mean, lets say I install ubuntu-touch and then install Kubuntu ontop of that
[08:53] <ogra_> ah, that wont work (doesnt work with gnome or other stuff either)
[08:53] <oSoMoN> dpm: not sure autolanding is really needed for this branch, but if you can merge mine I’d appreciate :)
[08:53] <ogra_> shadeslayer, you would need to port kwin to QtMir
[08:54] <shadeslayer> right, so my question is, is there a way to get the drivers from https://developers.google.com/android/nexus/drivers#manta, plop them somewhere and make it work?
[08:54] <ogra_> or just live without Kwin ... the apps should just work
[08:54] <shadeslayer> ogra_: uh, Martin's position is pretty clear on Mir atm
[08:54] <ogra_> btter ask that in #ubuntu-mir
[08:55] <ogra_> yoou cant just use the android drivers without their context i guess ... you will need some android env around it
[08:56] <ogra_> (the kernel and HAL layer)
[08:56] <shadeslayer> I see
[08:58] <ogra_> in any case the guys in #ubuntu-mir are far more qualified than i am, i'm mostly guessing based on what i know today ...
[08:58] <dpm> oSoMoN, ok, merged :)
[08:58] <ogra_> they can surely go more into detail
[08:58] <shadeslayer> okay will ask
[08:58] <oSoMoN> dpm: awesome, thanks!
[09:01] <shadeslayer> possibly the mer people have also figured out something
[09:10] <xnox> jhodapp: rsalveti: when you will have a moment later today, I'd like to chat about platform-api & ubuntu-sensors and testing. I did run the test_* apps from the platform-api for the hybris implementation and they do work. Are those being run in jenkins setup somewhere. Similarly for qtsensors, there are no tests at the moment - but it's a plugin for qt framework.
[09:11] <xnox> should it like have (1) api-compat unit tests against qt framework (2) sensors regulartly tested (autopilot or manually or some funky integration tests "e.g. change brightness via api & check if kernel reports a delta change)
[09:13] <ogra_> xnox, i think that stuff isnt finalized yet
[09:13] <xnox> I mean if either of platform-api / sensors get broken and "slip-in" it will be detected quite quickly. But i'd like some automated safety net against braking phablet images due to bugs in either of those.
[09:14] <xnox> ogra_: ok. Then I'm happy to start daily landing those - tbh.
[09:14] <xnox> ogra_: cause we will have autopkgtests to check buildability for example and I will push for api-compat monitoring.
[09:14] <xnox> didrocks: ^^^^^^ any other thoughts.
[09:15] <ogra_> dont quote me on that though ... but i think the majority of sensores isnt even working afaik
[09:15] <xnox> ogra_: i've tried raring chroot and reverted back to quantal/raring frankenstein, because I was not getting wifi on the raring chroot.
[09:15] <xnox> ogra_: i twiddle the brightness slider with my finger in the indicator and it totally works on nexus 7 =)
[09:16] <didrocks> xnox: ok, do you mind coordinate on it with mterry? as I think some of his work is dep on yours
[09:16] <ogra_> yeah, no network is a known bug
[09:16] <xnox> ogra_: ok.
[09:16] <didrocks> xnox: sad that we can't have them being running before or as part of the daily release
[09:16] <ogra_> should be fixed this week though according to sergio
[09:16] <didrocks> xnox: meaning, we are breaking something and then fixing
[09:16] <didrocks> rather than the other way around :)
[09:16] <Mirv> loicm: could you sponsor lp:ubuntu-ui-toolkit (0.1.41) into raring? I merged your raring specific changes so it should be fit for archive upload as well (with the general FFe for mobile related stuff)
[09:16] <didrocks> xnox: please put all details in the spreadsheet so that we can have a summary
[09:17] <xnox> didrocks: true. but we are a bit in a chicken & egg situation: cannot test this stack (e.g. raring/s daily image flashed to a tablet), since we don't have all the pieces built/bootstrapped/image generated.
[09:18] <didrocks> xnox: yeah, just mark that down and check with mterry to have the stack daily landing now
[09:18] <didrocks> xnox: you have the bootstrap commits and everything?
[09:18] <xnox> once we have first image, we can start doing things similar to daily-iso-testing-desktop.
[09:18] <xnox> didrocks: will fill the details on the spreadsheet and commit bootstrap marker.
[09:18] <xnox> otherwise sensors are fine. and platform-api is landing into ppa already.
[09:19] <P3T3> ogra_, Hi, as I remember you know how to detect version of build image?
[09:19] <didrocks> xnox: great! :)
[09:19] <xnox> P3T3: .disk/info or some hidden file?!
[09:19] <ogra_> P3T3, somewhere in /system/etc ...
[09:19] <xnox> oh.....
[09:19] <ogra_> there is a stamp file
[09:20] <ogra_> or was it /etc ? ... /me forgot
[09:21] <ogra_> xnox, that will likely be there once we do actual cdimage builds :)
[09:21] <ogra_> in S or so
[09:21] <P3T3> OK there is /etc/buildstamp
[09:21] <ogra_> right
[09:21] <xnox> didrocks: hm.... your comments seemed to be gone from the spreadsheet? or they got marked "resolved"
[09:22] <didrocks> xnox: urgh?
[09:22] <xnox> didrocks: nevermind found them.
[09:22] <didrocks> yep ;)
[09:22] <P3T3> I have an image from popey with acubens Fri, 01 Mar 2013 05:23:11 +0000
[09:23] <P3T3> This image is later then MWC demo and it boots in UI, is this image from daily builds?
[09:23] <popey> yes P3T3
[09:23] <popey> P3T3: march 1st is the datestamp on it
[09:23] <P3T3> I know, but do not know which date starts daily images :-)
[09:25] <popey> P3T3: how will that help?
[09:25] <popey> i think the first public build was on feb 19
[09:25] <popey> or thereabouts
[09:26] <P3T3> popey, latest daily builds fails to boot in GUI, I am searching what changed and when
[09:27] <popey> sure, but you said the one you have works?
[09:27] <popey> so surely something broke _after_ the image you have, not before
[09:27] <P3T3> this one is from you and it works
[09:28] <popey> right, and that's from march 1st, so you want to find out what broke after?
[09:28] <P3T3> thats right!
[09:28] <popey> we can do a bisect ☻  I can upload one from half way between then and now
[09:29] <P3T3> I think enough will be date 10th March
[09:29] <popey> ok, thats build 17, want that one?
[09:30] <P3T3> if you can :-D
[09:30] <popey> sure
[09:31] <popey> P3T3: it's uploading to the same place, will be there later
[09:31] <P3T3> popey, Thank you, I will wait
[09:33] <popey> np
[09:35] <P3T3> otherwise, I think this image from March 1st is a bit faster then MWC one
[09:35] <popey> thats possible
[09:45] <shadeslayer> ogra_: I'm reading up on the xf86-video-armsoc , which seems to be a driver for the Mali T6xx series
[09:46] <ogra_> shadeslayer, well, yeah, but it has its issues with composite (i'm using it right now)
[09:47] <shadeslayer> oh
[09:47] <ogra_> i thought you were after running kde on top of ubuntu touch
[09:47] <shadeslayer> hm, nope, I was thinking of running X -> Run KDE
[09:48] <ogra_> ah
[09:48] <ogra_> well you asked about the graphics stack of ubuntu touch initially
[09:48] <ogra_> so i kind of assumed that
[09:48] <shadeslayer> yeah, I was investigating how it works on ubuntu touch :)
[09:48] <shadeslayer> I think I understand now
[09:48] <ogra_> k
[09:49] <ogra_> armsoc will work indeed
[09:49] <shadeslayer> yay, but with issues, that's fine
[09:49] <ogra_> but has its issues and you need to hack around in the ldconfig setup
[09:49] <shadeslayer> atleast there's something I can start off with
[09:49] <shadeslayer> oh?
[09:49] <ogra_> (to prevent mesa from taking over)
[09:49] <shadeslayer> ah
[09:50] <ogra_> you want mesa for GL stuff but not for GLES
[09:50] <shadeslayer> roger
[09:50] <ogra_> and the driver doesnt have a concept fro this (since the GLES driver is completely unlicensed, so cant be distributed in packages)
[09:51] <shadeslayer> fun, do you have your setup documented somewhere? or can you throw it up in a pastebin real quick?
[09:52] <shadeslayer> the N10 has very bad button placement :(
[09:53] <shadeslayer> so awkward to press the buttons at the top
[09:53] <popey> shadeslayer: all android devices have bad button placement ☻
[09:53] <xnox> didrocks: lp:qtubuntu-sensors has the bootstrap node, comments added on the spreadsheet, bugs filed against the project and linked to the blueprint to create WI.
[09:53] <shadeslayer> popey: haha
[09:53] <xnox> didrocks: please "add" qtubuntu-sensors to start landing into the ppa.
[09:54] <ogra_> i just removed the /etc/ld.so.conf.d/arm-linux-gnueabihf_GLES.conf link, put the libGLES stuff for mali into /usr/lib and run ldconfig here
[09:55] <didrocks> xnox: does it have autolanding? (upstream merge)
[09:55] <didrocks> xnox: I don't find it in the current stack
[09:55] <shadeslayer> ogra_: 'here' ?
[09:55] <ogra_> on my chromebook
[09:55] <shadeslayer> ah okay
[09:55] <ogra_> (same HW)
[09:57] <popey> P3T3: http://people.canonical.com/~alan/phablet/17/ finished
[09:58] <shadeslayer> ogra_: and regarding the libGLES stuff for mali, did you use the libGLES so that google provides or the driver from the archive?
[09:58] <ogra_> there is no driver from the archive
[09:58] <shadeslayer> the driver I downloaded from google has a libGLES_mali.so
[09:58] <ogra_> as i said, its not distributable
[09:59] <shadeslayer> uh
[09:59] <ogra_> i copied the files from chromeos
[09:59] <shadeslayer> http://pad.lv/u/xf86-video-armsoc
[09:59] <xnox> didrocks: hmm... explain. It was part of the blueprint tasks for cleanup & landing. And this: https://code.launchpad.net/~mterry/qtubuntu-sensors/bootstrap/+merge/157399
[09:59] <xnox> did get merged.
[09:59] <ogra_> that doesnt contain any mali libs
[09:59] <ogra_> its only the driver
[09:59] <shadeslayer> ah I see
[09:59] <didrocks> xnox: yeah, interesting, I don't find the configuration of the CI jobs, not sure how they dealt with it, but looks good, I'm adding it to the daily release stack
[10:00] <xnox> ack.
[10:00] <xnox> didrocks: not sure what to do with this "changelog-entry-only-merge" https://code.launchpad.net/~jhodapp/qtubuntu-sensors/qtubuntu-sensors_release/+merge/152181
[10:01] <didrocks> xnox: seems they did a "release" the old way (they change the changelog) for phablet
[10:01] <didrocks> xnox: you can get it merged if you want, would be more clear if the top changelog is the one with the boostrap though
[10:01] <didrocks> (but not 100% necessary)
[10:02] <shadeslayer> ogra_: how's ubuntu on the Chromebook though?
[10:02] <ogra_> shadeslayer, fine apart from the composite issue ... unity doesnt catch that and runs (even thinks it is fully supported) but it slow as hell
[10:02] <ogra_> so i have to resort to other WMs
[10:03] <ogra_> waiting for Mir desktop support :)
[10:03] <shadeslayer> heh :)
[10:04] <shadeslayer> I can't wait to flash this literally-brand-new-N10
[10:04] <ogra_> alternatively hoping that someone fixes it in early S  for arm desktops :)
[10:05] <didrocks> xnox: added to the daily FYI
[10:05]  * ogra_ loves unity (like manu others) on arm desktops ... so it would be nice if that cound be fixed at some point 
[10:05] <ogra_> s/manu/many/
[10:06] <xnox> didrocks: cool, thanks.
[10:06] <didrocks> thanks to you :)
[10:06] <shadeslayer> ogra_: just to make sure I understood this correctly, the armsoc is the driver, that's opensource and licensable, OTOH samsung ships it's own libGLES that cannot be packaged, correct?
[10:06] <ogra_> right
[10:06] <shadeslayer> okay
[10:06] <ogra_> and armsoc uses the libGLES for acceleration if it is available
[10:06] <shadeslayer> right
[10:11] <P3T3> popey, downloaded and now in flashing process. I will inform you about result
[10:18] <popey> P3T3: great
[10:20] <P3T3> popey, fails, have black screen
[10:21] <popey> bummer
[10:21] <P3T3> can we try other build ?
[10:21] <P3T3> I have Mar 1st working and MAr 11th non working
[10:22] <P3T3> first one is build #8 and second one is #17
[10:40] <popey> P3T3: sure
[10:40] <popey> P3T3: i have 9, 10, 11, 13, 16
[10:42] <P3T3> popey, 13 as it is happy number in China
[10:42] <smartboyhw> P3T3, but it isn't in Western countries (I'm from China)
[10:43] <popey> my house is 13. but the stupid builders were superstitious so they labelled it 12A ☹
[10:43] <P3T3> My house number is 13 too
[10:44] <popey> P3T3: uploading, same place
[10:45] <P3T3> popey, and you can delete 17 if you no longer need it
[10:45] <popey> thanks
[11:05] <ftpd> Hi all. Does 3g data work on current build?
[11:06] <ogra_> nope
[11:06] <ftpd> :/ So still have to wait. Thanks.
[11:07] <ogra_> but it is actively being  worked on
[11:15] <shadeslayer> ogra_: the phablet-armhf.zip is basically just a debootstrapped ubuntu + packages right?
[11:34] <P3T3> popey, #13 is black too. So remains 9,10,11. Can you give me 10 please? 13 is to delete
[11:35] <tsdgeos> bzoltan: is there any reason the 1.41 toolkit release is not in raring?
[11:35] <tsdgeos> 0.1.41
[11:35] <bzoltan> tsdgeos: we do not (can not ) release straight to Raring
[11:35] <bzoltan> tsdgeos:  so there is a delay between our release and the distro release
[11:35] <tsdgeos> ok
[11:36] <bzoltan> tsdgeos:I suggest to use the SDK Release PPA if you need the latest Toolkit
[11:36] <tsdgeos> that's what i'm doing
[11:36] <tsdgeos> but using ppa's makes me sick :D
[11:39] <andril> hello all
[11:44] <tsdgeos> hi
[11:44] <ogra_> shadeslayer, well, it is ubuntu-minimal + android integration + ubuntu touch UI
[11:45] <shadeslayer> right, I'm just trying to create my own zip
[11:45] <shadeslayer> seems like there are some other files in there too META-INF/com/google/android/update-binary
[11:45] <ogra_> yeah, android stuff
[11:47] <shadeslayer> where does that come from?
[11:48] <shadeslayer> aha
[11:48] <shadeslayer> phablet-dev-bootstrap gens the zip
[11:49] <jhodapp> xnox: we can chat about that whenever you want
[11:52] <xnox> jhodapp: well, I think between myself, ogra & didrocks we agreed to start autolanding qtubuntu-sensors. We just need to come up with testing strategy for it.
[11:53]  * ogra_ is out for ~2h
[11:53] <jhodapp> xnox: indeed
[11:53] <xnox> jhodapp: are sensors api exercised via autopilot tests somehow at the moment? or since they are - well - sensors they need manual testing?
[11:54] <popey> P3T3: ok
[11:54] <jhodapp> xnox: manual testing, although we should be able to add some simple unit tests to some of those functions
[11:54] <xnox> I have filed http://pad.lv/1167825 http://pad.lv/1167818 for pure api/abi stability monitoring.
[11:54] <jhodapp> xnox: though I'm sure someone could get creative in simulating the sensors
[11:56] <xnox> jhodapp: well, we don't want to mock the sensors, cause that's not the point. When I ask to dim the screen - it should dim for real, cause it's a bit pointless to say that well the mock sensors does dim... but the actual tablet regresses and doesn't change brightness.
[11:57] <xnox> I wonder if Certification team has something in checkbox to test that already - e.g. testing the britness keys on the desktop. But instead of manually pressing buttons, we can go via qtubuntu-sensors api to up/down brightness.
[11:57] <xnox> jhodapp: what type of unit tests were you thinking? to exercise / checks all functions. Is there like a standard qtsensors examples which we can be compiling/running atainst qtubuntu-sensors plugin?
[11:58] <jhodapp> xnox: right but that's a functional test...I'm talking more unit testing
[11:59] <jhodapp> xnox: really basic ones, qtubuntu-sensors really doesn't do a whole lot...it's just very simple glue between the AAL layer and a Qt/QML app
[12:00]  * Namidairo sniffs qtubuntu-sensors
[12:00] <xnox> jhodapp: ok. well if you have something in mind that could be done, please open a bug against sensors or add a WI to the landing raring touch blueprint.
[12:00] <xnox> jhodapp: would you be willing to write those?
[12:01] <jhodapp> xnox: I don't have anything specific in mind atm, but if I think of something I will certainly add it
[12:01] <jhodapp> xnox: a bug/blueprint entry
[12:02] <xnox> jhodapp: ok. I'll poke the code again once we get the raring/s images.
[12:02] <jhodapp> xnox: also know that I'm no longer the person actively working on that code
[12:03] <P3T3> popey, if 10 will work then I will need 11, otherwise 9. But first I will need to test it. Will inform you
[12:03] <xnox> jhodapp: hmm.... who became "goto person" about it?
[12:04] <popey> P3T3: np
[12:04] <jhodapp> xnox: I'm not sure offhand, but I can find out for you if you like
[12:04] <xnox> jhodapp: please do. I'm not familiar with the upstream teams hacking on this stack. I'm from ubuntu engineering trying to get it to land into archive =)
[12:05] <jhodapp> xnox: ok, np then
[12:20] <P3T3> popey, downloading 10, thanks
[13:07] <P3T3> popey, #10 fails. Remains #9, can you upload it?
[13:07] <popey> sure
[13:09] <P3T3> popey, 10 & 13 you can delete
[13:10] <popey> done, thanks
[13:11] <P3T3> me too
[13:15] <id0_stupid_user> Hi, may I ask if UT caters for phones with hardware buttons ?
[13:17] <pmcgowan> the UI is designed to not require hardware buttons, but I think some ports have mapped them to certain functions
[13:18] <id0_stupid_user> thank you pmcgowan I shall try to search for said 'ports'
[13:18] <smartboyhw> id0_stupid_user, what phone do you use?
[13:19] <smartboyhw> Try to find yours at https://wiki.ubuntu.com/Touch/Devices
[13:19] <Upender> I have Nokia N8
[13:19] <Upender> is it possible to install ubuntu on NOkia n8
[13:19] <smartboyhw> Upender, whoa I don't think so. Someone needs to port Android to Nokia N8 first:P
[13:20] <id0_stupid_user> smartboyhw: I have an old android tablet that I pushed generic ubuntu LTS armhf to.
[13:20] <Upender> okies..actully i am not happy with nokia belle any more
[13:21] <Upender> hence looking to chagne but no issue will check for any other update or possiblity in furthre
[13:21] <Upender> future
[13:21] <id0_stupid_user> I've got the hardware buttons working via a C script that I wrote... Obviously not having X I can't use xevents
[13:21] <id0_stupid_user> Upender: cool ... My wife has an N8 - I need to repurpose that too ;)
[13:23] <ali1234> N8 is symbian, good luck rooting it
[13:23] <id0_stupid_user> :)
[13:23] <Upender> hmm
[13:23] <ali1234> Upender: if you just hate belle there is a secret way to downgrade to S^3
[13:30] <id0_stupid_user> Good luck ladies and gentlemen
[13:35] <shadeslayer> uh hi
[13:36] <shadeslayer> when running adb root I get : adbd cannot run as root in production builds
[13:36] <shadeslayer> causing phablet-flash to fail
[13:36] <shadeslayer> any ideas?
[13:37] <popey> P3T3: 9 is done
[13:39] <P3T3> popey, thanks, going to test it
[13:45] <shadeslayer> mmm
[13:45] <shadeslayer> I'll have to root it?
[13:49] <jhodapp> xnox: you'll want to talk to ChickenCutlass about the sensors now, he's leading that charge
[13:49] <xnox>  jhodapp ok, thanks.
[13:50] <jhodapp> xnox: np
[13:51] <P3T3> popey, #9 works, it's buildstamp = arneb Sat, 02 Mar 2013 05:02:52 +0000 , manhattan-quantal-armhf-20130302-1
[13:53] <popey> P3T3: good luck finding what changed ⍨
[13:55] <P3T3> popey, is there any log with changes?
[14:23] <nik90> hey guys in the ubuntu touch component showcase, I see a tab for icons. I also read the demo code. However where does one find the entire list of icons?
[14:24] <rsalveti> xnox: ogra_: indeed, the sensors are not "done" at this moment, and I believe the apis will probably change with the new desired implementation at the platform-api
[14:24] <nik90> I see them using call-start, computer-symbolic etc..but I am unaware as to what other icons are available
[14:24] <rsalveti> ChickenCutlass is the owner of sensors in general, so he might know more
[14:24] <rsalveti> xnox: but we have the infra available already to run test apps at a real device already
[14:24] <popey> kaleo: see nik90's question? Do we have a full list?
[14:25] <rsalveti> so we just need the proper plumbing
[14:25]  * ogra_ looks for his wrenches
[14:25] <xnox> rsalveti: ack. What about the test_* apps in platform-api? same story?
[14:26] <rsalveti> xnox: yup
[14:26] <rsalveti> they were just quick test apps to make sure hybris wasn't failing while doing the development mostly
[14:26] <rsalveti> as we're redesigning platform-api, I also believe it'll change quite a bit
[14:31] <kaleo> popey: nik90: sorry there is no list yet
[14:32] <kaleo> popey: nik90: moreover the list is different on the desktop and on touch right now
[14:32] <kaleo> popey: nik90: we use ubuntu-mono-dark on the desktop and ubuntu-mobile on ubuntu touch
[14:32] <nik90> kaleo: oh ok ... then I'll wait until we get the icons officially for the touch
[14:32] <kaleo> dpkg -L ubuntu-mono will give you the desktop ones
[14:32] <kaleo> dpkg -L ubuntu-mobile will give you the touch ones
[14:32] <kaleo> nik90: just hang on :)
[14:34] <nik90> kaleo: where do I find the ubuntu-mobile package?
[14:47] <tsdgeos> intetesting
[14:47] <tsdgeos> our calculator is mathematically correct
[14:47] <tsdgeos> which means people will complain :D
[14:48] <tsdgeos> well, now i did 12 * 8 and got 9696
[14:48] <tsdgeos> forget that mathematically correct part :D
[14:49] <nik90> tsdgeos: do you mean in the ubuntu-calculator-app?
[14:49] <tsdgeos> nik90: whatever is shipped in the phone
[14:49] <tsdgeos> i guess yes
[14:52] <nik90> tsdgeos: just tried it now...wierd
[15:02] <shadeslayer> ogra_: once you're back, I'd like to talk :)
[15:02] <kaleo> nik90: it's part of the ubuntu-themes source package
[15:03] <kaleo> nik90: which is or will be soon in raring
[15:03] <kaleo> nik90: otherwise I think there is a PPA http://ppa.launchpad.net/phablet-team/desktop-deps/ubuntu/
[15:06] <ogra_> shadeslayer, i'm here
[15:14] <dholbach> sergiusens, rsalveti, ogra_: so client-1303-sponsoring-community-touch-builds is for "1303" obviously - I'm just wondering if with the next UDS happening at 14-16 May 2013 it'd be something we should discuss there?
[15:14] <dholbach> or do we expect many bits already having fallen into place by then?
[15:14] <ogra_> i hope the android builds will happen on cdimage by then
[15:14] <kvarley> I use my tablet for web browsing and playing videos, will the preview serve my purposes yet? I'm a long term ubuntu user and wouldn't mind some bugs
[15:15] <ogra_> kvarley, both technically work ... but the browser doesnt know about tabs yet for example ...  so its not very comfortable as an enduser
[15:16] <kvarley> Ok, well my setup is basically TV on my tablet and IM on my phone so I guess I can browse on my phone too
[15:17] <mhall119> kvarley: depends on the device too, videos play on my Nexus 7, but sound doesn't
[15:17] <mhall119> but a couple weeks ago, videos didn't play
[15:18] <mhall119> so, progress!
[15:18] <shadeslayer> ogra_: hey, so, I'm curious, the chroot that phablet-flash flashes, that contains android stuff and ubuntu chroot correct?
[15:18] <ogra_> mhall119, just enable subtitles :)
[15:18] <shadeslayer> ogra_: what if I don't want the android tools and just want a minimal ubuntu chroot ( debootstrap + ssh server )
[15:18] <ogra_> shadeslayer, it contains the ubuntu side of the platform api and libhybris
[15:19] <ogra_> shadeslayer, you can do that but wont be able to use any graphical stuff i belive
[15:19] <shadeslayer> oh, not even by using the methods we talked earlier?
[15:19] <ogra_> you will need to talk to SurfaceFlinger soemhow
[15:19] <ogra_> (the android display server)
[15:20] <smartboyhw> shadeslayer, wait for Mir:P
[15:20] <shadeslayer> no no, what if I don't want surfaceflinger and just want to use X?
[15:20] <ogra_> or build your android in a way that it doesnt fire that up
[15:20] <mhall119> ogra_: if I wanted to read a movie, I'd buy the book :P
[15:20] <shadeslayer> smartboyhw: KWin upstream is not going to accept Mir integration :P
[15:20] <shadeslayer> smartboyhw: Martin made that very clear
[15:20] <smartboyhw> shadeslayer, I know (LOL) so that:P :P
[15:20] <ogra_> mhall119, audiobooks ftw :)
[15:21] <shadeslayer> okay, I thought you were serious ;)
[15:21] <ogra_> (with subtitles indeed)
[15:21] <mhall119> ogra_: unless you have to audio....
[15:21] <mhall119> do audio books have subtitles?
[15:21] <P3T3> rsalveti, do you know something about compilation parameters of daily builds?
[15:21] <smartboyhw> shadeslayer, I did watch the whole conversation.
[15:21] <ogra_> lol, dunno
[15:22] <rsalveti> P3T3: sure
[15:22] <shadeslayer> ogra_: recall our conversation earlier today, can't I boot minimal rootfs, put more things that I want ontop of it and then use the libGLES from Samsung to get HW acceleration? ( No Android things at all on the system )
[15:22] <rsalveti> dholbach: I believe we should be done with it before next uds, but I'd also vote to have some sort of community porters checkpoint
[15:22] <dholbach> rsalveti, ok great
[15:22] <rsalveti> to see what we could do to improve the porting experience and such
[15:22] <ogra_> shadeslayer, you should be able to ... try it :)
[15:22] <dholbach> sounds great
[15:23] <shadeslayer> right, now my actual question :D
[15:23] <ogra_> oh, you did hide it behind smalltalk !
[15:23] <P3T3> rsalveti, today I have discovered that build from March 3rd causes my problem which leads in black screen
[15:23] <shadeslayer> how do I switch out the zips? :P
[15:23] <ogra_> dunno, why do you want zips ?
[15:23] <shadeslayer> because I don't quite understand how the booting works here
[15:23] <P3T3> I need to know something about changes between MArch 2nd and 3rd
[15:23] <shadeslayer> oh
[15:23] <rsalveti> P3T3: hm, we didn't change any parameters back then
[15:23] <rsalveti> P3T3: which hardware?
[15:24] <P3T3> HP Touchpad
[15:24] <shadeslayer> so I can flash quantal-preinstalled-boot-armel+manta.img and then flash a rootfs to the /data ?
[15:24] <shadeslayer> and it will all just work?
[15:24] <ogra_> shadeslayer, have a look at the nexus7 codepath of ac100-tarball-installer ... thats what we use for the n7 desktop images ... should workj similar for the n10
[15:24] <ogra_> you want a boot.img and put in an initrd that contains the ac100-tarball-installer bits
[15:25] <shadeslayer> I see
[15:25] <ogra_> then you can just use a rootfs tarball you prepare
[15:25] <ogra_> might need some hacking but essentially thats the process i would use
[15:25] <shadeslayer> okay, thanks :)
[15:25] <rsalveti> P3T3: I wonder if that is an incompatibility of the platform-api and the compat layer at hybris
[15:25] <shadeslayer> I'll try and figure out how the AC100 does things
[15:26] <rsalveti> it might be related with the ubuntu rootfs you're using as well
[15:26] <dholbach> rsalveti, shall I make it part of the community track?
[15:26] <ogra_> shadeslayer, better look at the nexus7 codepath in there ... thats way simpler
[15:26] <ogra_> the ac100 has a ton of checks etc that you dont really want
[15:27] <rsalveti> dholbach: yeah
[15:27] <dholbach> sweet, on it
[15:27] <P3T3> rsalveti, my hybris and platform-api are newest one
[15:27] <rsalveti> P3T3: weird, have the logs from logcat?
[15:27] <rsalveti> would be nice to compare the ones from the working and not working images as well
[15:28] <ogra_> rsalveti, P3T3 is Petr Bláha on the ML btw :)
[15:28] <rsalveti> ogra_: thanks!
[15:28] <rsalveti> :-)
[15:28] <ogra_>  http://pastebin.com/ir3Gdk1K
[15:28] <ogra_> from the black screen thread
[15:28] <P3T3> http://pastebin.com/ir3Gdk1K
[15:28] <ogra_> :)
[15:28] <P3T3> I am too slow
[15:29] <P3T3> it dies at ubuntuappmanager, I think
[15:30] <dholbach> sergiusens, rsalveti, ogra_: https://blueprints.launchpad.net/ubuntu/+spec/community-1305-touch-porting
[15:30] <P3T3> ogra_, rsalveti true, I am Petr Blaha :-D
[15:30] <rsalveti> right, let me try to better find what changed between such builds
[15:30] <rsalveti> dholbach: great, thanks
[15:31] <ogra_> ah, already subscribed
[15:34] <sergiusens> dholbach: didn't we have a blueprint for this?
[15:34] <rsalveti> sergiusens: this is for uds
[15:34] <dholbach> sergiusens, one for 1303
[15:34] <sergiusens> dholbach: ah... I'm still confused by the milestones :-)
[15:34] <dholbach> :)
[15:35] <sergiusens> dholbach: that last one is for the next vUDS, right?
[15:35] <mhall119> http://www.reddit.com/r/Ubuntu/comments/1c51ci/building_an_ubuntu_sdk_app_rev_56/ could use some upvoting love
[15:35] <dholbach> yes
[15:35] <sergiusens> dholbach: also, porting is going to simplified a bit since we got breakfast to work and I plan on removing some stuff from the build :-)
[15:35] <dholbach> :-D
[15:35] <dholbach> awesome
[15:36]  * sergiusens doesn't know what he's missing but doesn't use reddit
[15:38] <P3T3> rsalveti, there is a logcat from working build = http://pastebin.com/3dRghCH0
[15:38] <mhall119> dpm: do you want to add my blog series to http://developer.ubuntu.com/resources/app-developer-cookbook/mobile/ ?
[15:38] <mhall119> or some other category of the cookbook?
[15:39] <rsalveti> P3T3: can you also get me your /system/quantal-ubuntu_stamp ?
[15:39] <rsalveti> but guess it'll be dev, nevermind
[15:39] <dpm> mhall119, sure, that sounds good. Feel free to add them, I think that's the right category.
[15:39] <mhall119> ok
[15:41] <P3T3> rsalveti, at working I have only "dev" inside
[15:41] <sergiusens> P3T3: open the phablet.*.zip from that image and check the tarfile name
[15:43] <rsalveti> sergiusens: manifests from march 1,2,3,4 are the same
[15:43] <P3T3> working build is : manhattan-quantal-armhf-tar-20130302-1.tar.gz
[15:43] <rsalveti> weird
[15:43] <P3T3> and non working is manhattan-quantal-armhf-tar-20130303-1.tar.gz
[15:44] <rsalveti> diff -Naur manhattan-quantal-armhf-tar-20130302-1.manifest.appcache manhattan-quantal-armhf-tar-20130303-1.manifest.appcache
[15:44] <rsalveti> nothing
[15:44] <rsalveti> anyway, need to grab food, brb
[15:44] <P3T3> and what about hardfloat compilation flag? I have this one with software backward compatibility
[15:45] <mhall119> dpm: http://developer.ubuntu.com/resources/app-developer-cookbook/mobile/ look good to you?
[15:45] <ogra_> rsalveti, hmm, did we add some hardcoded NEON stuff perhaps ?
[15:45] <ogra_> remember thats a tegra2
[15:46] <dpm> mhall119, looks good. Could you add the currency converter tutorial while you're at it? I see I forgot to add it.
[15:46] <P3T3> ogra_, but I have same problem wirh HP Touchpad
[15:46] <mhall119> dpm: sure
[15:47] <P3T3> HP has Snapdragon with neon, AFAIK
[15:47] <ogra_> ah, k
[15:47] <sergiusens> ogra_: There is no change fro manhattan-quantal-armhf-tar-20130302-1 to manhattan-quantal-armhf-tar-20130303-1 ... just reconfirming what rsalveti said
[15:47] <ogra_> yeah
[15:48] <mhall119> dpm: done
[15:48] <dpm> cool, thanks
[15:49] <mhall119> dpm: any other articles you know about that we can link in there?
[15:52] <dpm> mhall119, the one I can think of is Rick's blog post, there might be some others -> http://theravingrick.blogspot.com.es/2013/03/sweet-ubuntu-device-qtcreator.html
[15:52] <mhall119> he had a few of them, actually
[15:54] <sergiusens> rsalveti: ogra_ do you recall where that NVIDIA_HACK was?
[15:55] <ogra_> NVIDIA_HACK ?
[15:55] <ogra_> whats that >
[15:55] <ogra_> ?
[15:56] <mhall119> rickspencer3_: do you have any problem with us linking to your blog from http://developer.ubuntu.com/resources/app-developer-cookbook/mobile/ ?
[15:56] <nik90> mhall119: what about asking Stuart Langridge for tutorials...I remember him creating many apps like https://plus.google.com/108243663090085262773/posts/gmHwiRxKNxJ, https://plus.google.com/108243663090085262773/posts/W5Nic8PcrFS
[15:56] <ogra_> aquarius, ^^^
[15:56] <ogra_> sergiusens, can you elaborate ?
[15:56] <dpm> we ask him all the time :)
[15:57] <mhall119> nik90: does he have tutorials? or just apps?
[15:57]  * mhall119 probably asks aquarius for too much already
[15:57] <rickspencer3_> mhall119, fine with me
[15:57] <mhall119> thanks rickspencer3_
[15:58] <nik90> mhall119: he just posted videos of his apps..maybe should request he write tutorials
[15:59]  * aquarius grins
[15:59] <aquarius> nik90, that sounds like a good idea
[15:59] <aquarius> nik90, but I'd watch out for that Langridge person. He's a bit weird
[15:59] <aquarius> handsome guy, mind.
[16:00] <ogra_> lol
[16:00] <nik90> aquarius: :) u playing with my mind..hehe...with nicknames
[16:00]  * aquarius grins
[16:00] <aquarius> nik90, to be serious for a moment, dpm has asked me about six times to write some tutorials :)
[16:00] <aquarius> I plan to do something when I get a chance, indeed
[16:01] <dpm> nik90, I told you we had :)
[16:01] <mhall119> dpm: that cookbook page is looking much nicer now :)
[16:02] <dpm> mhall119, why, did you add a picture of aquarius to it?
[16:02] <nik90> dpm: hehe...adding more pressure always help :D
[16:02] <tedg> Uhm, this should be based on Qt, so it should work on Ubuntu Touch, no?  https://twitter.com/mairin/status/322377455186890753
[16:02] <tedg> Seems like something we should package and see :-)
[16:02] <mhall119> dpm: not that much nicer :)
[16:02] <mhall119> tedg: in theory
[16:03] <tedg> mhall119, Make it happen!  :-)
[16:03] <mhall119> or should I say, "in theory" with scare-quotes
[16:03] <aquarius> are the screenshots deliberately blurred? :(
[16:03] <tedg> Yeah, I'm not sure why.
[16:03] <aquarius> it depends on whether it's using components that we don't have
[16:04] <tedg> But apparently they're presenting at LGM as we speak.  It might be a capture from the stream.
[16:04] <aquarius> and it would obviously not follow the design guidelines, which is bad
[16:04] <mhall119> aquarius: maybe they took a picture of their screen witha phone
[16:04] <mhall119> then printed it out
[16:04] <mhall119> scanned it back in
[16:04] <mhall119> uploaded it to a photo sharing site
[16:04] <aquarius> and spilled a glass of water on it
[16:04] <tedg> aquarius, Hah, like those will hold up past v1 ;-)
[16:04] <mhall119> downloaded the thumbnail
[16:04] <nik90> :P
[16:04] <dpm> and sent via regular post
[16:04] <mhall119> upscaled it
[16:04] <mhall119> ...
[16:04] <aquarius> but in theory it's doable, at least
[16:04] <dpm> mhall119, nice work with the cookbook page
[16:04] <mhall119> in theory everything is doable
[16:05] <tedg> It's doable, we just have to figure out: how can we get enough beer and cigarettes to aquarius' house to make it happen?
[16:05]  * tedg checks amazon
[16:06] <aquarius> amazon won't deliver cigarettes, I don' tthink :)
[16:06] <mhall119> he doesn't smoke real ones anymore anyway
[16:07] <mhall119> can you download more electronic cigarettes?
[16:07] <ogra_> yeah. you could just have delivered a canister
[16:07] <ogra_> full of that stuff that tastes like old socks if you burn it
[16:08] <ogra_> or  a big box of nicotine patches :)
[16:29] <kaleo> seb128: cyphermox: https://code.launchpad.net/~tiheum/ubuntu-themes/new_icons/+merge/154470 is ready to be merged :)
[16:29] <seb128> kaleo, thanks
[16:31] <rsalveti> sergiusens: nvidia hack was at hybris
[16:32] <rsalveti> but still, the same version, weird
[16:33] <bfiller> dpm: trying to create a spec and put it on ubuntu wiki but can't login, you seeing this at all?
[16:33] <dpm> bfiller, let me try. In the meantime, have you tried to log out from SSO and log back in?
[16:34] <bfiller> dpm: let me check, don't think I was logged in to begin with
[16:34] <dpm> bfiller, I can still edit pages, but I was already logged in
[16:35] <bobweaver> ping mhall119
[16:36] <cyphermox> cool cool, thanks kaleo
[16:36] <cyphermox> jenkins will merge it shortly
[16:36] <mhall119> bobweaver: pong
[16:37] <bfiller> dpm: I'm in, had to log out first. thanks
[16:37] <dpm> bfiller, cool, glad it worked
[16:38] <bobweaver> hey mhall who should I talk to about vm intergration I also made new templets for it
[16:38] <bobweaver> and some extrenal tools
[16:40] <bobweaver> mhall119,  maybe you would like to try the new template. ... I will make a video
[16:41] <mhall119> bobweaver: I emails bzoltan your video, he's going to take a look
[16:42] <P3T3> rsalveti, sergiusens, ogra_ Thank you guys, I am going to investigate more deeper
[16:44] <shadeslayer> ogra_: and what exactly are these images? http://cdimage.ubuntu.com/kubuntu-active/daily-preinstalled/current/
[16:45] <bzoltan> mhall119:  I already did and pinged bobweaver
[16:45] <ogra_> shadeslayer, broken crap i forgot to remove :)
[16:45] <shadeslayer> hah
[16:46] <ogra_> we tried to do n7 builds of kubuntu-active ...
[16:46] <shadeslayer> yeah, I don't think kwin talks to SurfaceFlinger :P
[16:47] <ogra_> no, that was desktop based
[16:47] <bobweaver> bzoltan,  I am making a video of what I made should be done in ten minutes
[16:47] <shadeslayer> ah
[16:47] <shadeslayer> and when you say desktop based, you mean like the AC100 steps that you explained earlier right?
[16:48] <bzoltan> bobweaver: OK
[16:48] <ogra_> shadeslayer, like the nexus7 desktop image
[16:49] <P3T3> rsalveti, sergiusens Can you look at diifs between builds 20130303, 20130304, 20130305 and 20130306 ?
[16:50] <shadeslayer> no idea what that is 0.o
[16:51] <ogra_> http://cdimage.ubuntu.com/daily-preinstalled/current/
[16:52] <shadeslayer> ah okay
[16:56] <P3T3> I have to go, can you mail me diffs to pb@P3T3.org ? Thanks
[16:57] <kaleo> Saviq: https://code.launchpad.net/~fboucault/unity/phablet-use_icon_theme/+merge/158426
[16:57] <kaleo> Saviq: it's not quite ready but it's coming real soon
[17:01] <popey> hmm, todays image the OSK doesn't work when i want to type a WPA key for network.. known issue?
[17:02] <popey> on nexus 7
[17:03] <popey> keyboard doesn't appear
[17:03] <rickspencer3> popey, did you try rebooting?
[17:04] <rickspencer3> that was a bug that slipped in a week or so ago
[17:04] <rickspencer3> every few reboots, you get that
[17:04] <popey> rickspencer3: clean boot after new install, will reboot
[17:04] <rickspencer3> popey, yeah, I bet it works after you reboot
[17:04] <popey> ta
[17:05] <rickspencer3> mhall119, hey, I notice that on the lenses, when you scroll up, the title smoothly scrolls off the top of the page
[17:05] <rickspencer3> should I be setting up my apps in some way so that htey do that?
[17:05] <rickspencer3> kaleo, ^ ?
[17:06] <popey> nope, reboot still shows no keyboard
[17:09] <kaleo> rickspencer3: if I understand correctly what we are talking about, it should be automatic
[17:09] <kaleo> rickspencer3: if you are using a MainView and some Flickable/ListView inside it
[17:09] <popey> bah, reboot again it works
[17:10] <rickspencer3> kaleo, I am, but I wonder if I have it set up wrong
[17:10] <rickspencer3> it goes MainView{PageStack{ListView{}}}
[17:10] <kaleo> rickspencer3: we have documentation now! :)
[17:10] <kaleo> rickspencer3: http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/qml-ubuntu-components0-mainview.html
[17:11] <kaleo> rickspencer3: with examples
[17:11]  * rickspencer3 looks
[17:11] <kaleo> rickspencer3: hmm, PageStack, let me see
[17:12] <kaleo> rickspencer3: doc is unclear about that case
[17:12] <rickspencer3> kaleo, so the flickable needs to be a direct child of the MainView for this to work?
[17:13] <rickspencer3> kaleo, oh, I lided
[17:13] <rickspencer3> lied, even
[17:13] <rickspencer3> it goes MainView{PageStackPage{{ListView{}}}}
[17:13] <rickspencer3> dang it
[17:13] <kaleo> rickspencer3: :)
[17:13] <rickspencer3> it goes MainView{PageStack{Page{ListView{}}}}
[17:13] <kaleo> rickspencer3: I would expect that to just work but the doc does not say it
[17:13] <kaleo> rickspencer3: let's check with timp
[17:13] <bobweaver> I NEED MORE RAM !!! stupid thing keeps on frezzing
[17:14] <bobweaver> take 4 bobweaver  pulls his hair out ep 3
[17:14]  * ogra_ sends bobweaver a swapfile 
[17:15] <ogra_> also installing zram-config will help ;)
[17:15] <ogra_> (will magically add ~1/3 extra ram to your machine)
[17:15] <kaleo> rickspencer3: in the toolkit demos there is a similar case that works; let me look at the code
[17:16] <kaleo> rickspencer3: yeah it is the same structure: MainView{PageStack{Page{Flickable{}}}}
[17:17] <kaleo> rickspencer3: and it just works
[17:17] <rickspencer3> weird
[17:17] <kaleo> rickspencer3: can I test your code?
[17:17] <rickspencer3> yeah
[17:17] <rickspencer3> kaleo, let me see if I pushed it anywhere
[17:19] <rickspencer3> lp:~rick-rickspencer3/+junk/technews/
[17:19] <rickspencer3> kaleo, ^
[17:19] <kaleo> thx
[17:19] <rickspencer3> kaleo, aaah, I lied again
[17:19] <rickspencer3> there is a rectangle between the listview and the page
[17:19] <rickspencer3> I bet that is the problem
[17:19] <bobweaver> I need it but I hate it gstreamer !!
[17:19] <kaleo> rickspencer3: :)
[17:20] <rickspencer3> the rectangle is unnecessary, I think
[17:20] <rickspencer3> kaleo, so the rule is, if the child of the page is a flickable, the autoscrollng will work?
[17:20] <kaleo> rickspencer3: unless you want to display a colored rectangle then it is :)
[17:20] <kaleo> rickspencer3: yes
[17:20] <bobweaver> take 4
[17:20] <rickspencer3> I don't even know why I put them in rectangles, tbh :/
[17:21] <rickspencer3> seemed like the thing to do at the time :)
[17:21] <ogra_> because circles are trademarked by google ?
[17:21] <rickspencer3> ogra_, yeah, probably something like that ;)
[17:21] <kaleo> rickspencer3: fixed!
[17:21] <ogra_> :)
[17:22] <rickspencer3> thanks kaleo
[17:22] <rickspencer3> I'll fix it up and blog about it later
[17:22] <shadeslayer> ogra_: oh btw I can't find this on the interwebs, how does on start the adb daemon on the device?
[17:22] <ogra_> in ubuntu touch it runs by default
[17:22] <ogra_> nothing to start there
[17:22] <shadeslayer> sure, but what exactly is that called?
[17:23] <ogra_> ?
[17:23] <ogra_> its adbd and android fires it up on boot
[17:23] <shadeslayer> mm .. right, and adbd isn't something that's available in ubuntu
[17:25] <ogra_> i'm not sure if the adb package contains the daemon ... never looked at that
[17:25] <ogra_> but we usually dont use adbd in ubuntu, yeah
[17:25] <shadeslayer> well, since I'm debootstrapping a basic install, once I put it on the device, how do I connect to it
[17:25] <shadeslayer> which is why I needed adb
[17:26] <bobweaver> Allright got it that time Uploading it now bzoltan  and mhall119
[17:26] <shadeslayer> or rather adbd
[17:26] <ogra_> well, do you base on touch now ?
[17:26] <ogra_> then your android layer has adbd #
[17:26] <ogra_> and runs it on boot
[17:27] <shadeslayer> hmm, yeah, but I distinctly remember my TF101 didn't have android bits
[17:27] <shadeslayer> and it had adbd
[17:27] <ogra_> no idea then
[17:27] <ogra_> i know we have it in ubuntu touch by default
[17:27] <ogra_> in the android layer
[17:27] <shadeslayer> yeah
[17:28] <shadeslayer> lilstevie: ^^
[17:28] <shadeslayer> lilstevie: I distinctly remember the ubuntu chroot you provided for the TF101 had adbd
[17:28] <bobweaver> bzoltan,  and mhall119  video will be up in 5 minutes or so  http://www.youtube.com/watch?v=JARd_eMYqOA
[17:28] <bobweaver> notice the new tools
[17:29] <bobweaver> like the Ubuntu Virtual package (adding in debian stuff today ) and the tools to launch the VM
[17:29] <bobweaver> Need to fix the vm and get rid of all the bloat though
[17:30] <bobweaver> add some upstart scripts ect
[17:30] <shadeslayer> ah well
[17:31] <shadeslayer> I'll just make it use wpa_supplicant and connect to my network
[17:38] <bobweaver> bzoltan,  mhall119  video is done uploading let me know what you think
[17:38] <bobweaver> well besides that the vm needs work that is
[17:39] <bobweaver> for the wizards I see that you all are using json why not the reg way of xml? there are many more options and better ways to handle filenames
[17:40] <bobweaver> jppiiroi1en,  ^^^
[17:41] <bobweaver> as far as launching the VM I was thinking about putting that in with the cpp that is there for plugin already (ubuntu.pro) but I did not know if I should make my own button and screen do I just put it in extrenal tools for now
[17:42] <ogra_> sergiusens, so looking at that image test page on jenkins, i see a ton of app tests, but how do i know from that if the image is good to go or not ?
[17:43] <bobweaver> at any rate I do not need to plug in my nexus 7 and make sure that it is on touch and what not I can now just use the virtual machine to test Hud and what not
[17:44] <bobweaver> if qsortproxyfilter would be more nice and application plugin was there then I could integrate this fully into desktop
[17:44] <ogra_> sergiusens, do you have any toplevel thing i can poll (image good/image bad) instead of having to screen scrape the whole list of tests ?
[17:45] <bobweaver> seems like there needs to be more work done in that area but I have no clue who is in charge and what is and is not allowed so I am not touching that with ten foot pole
[17:45] <sergiusens> ogra_: I can probably right something
[17:45] <sergiusens> and right it in as a file
[17:46] <ogra_> yeah, that would help
[17:46] <sergiusens> s/right/write/
[17:46] <ogra_> currently it seems a lot of the app tests still fail
[17:47] <sergiusens> ogra_: that's an autopilot bug
[17:47] <sergiusens> ogra_: need to fix today
[17:48] <ogra_> well, if i would rely on the table at the bottom i wouldnt publish ... i can indeed easily just check if there are no fails at all but i would expect that we allow some level of fuzzyness
[17:54] <dobey> is aptdaemon running on ubuntu-touch platforms, or is there now python bits at all? and if it's not there, how does an app request that a package be installed/updated, or how does the user change mirrors or such?
[17:58] <bobweaver> so bzoltan  and jppiiroi1en  and who ever If you want me to do this just say yes or no. I just dont want to waste any time if it will never be used. As I have what I need atp  but I could make real professional if need be But I would like to do  a google hangout with the people that are in charge of this stuff so I DONT waste my time like I did With Ubuntu TV  thanks
[17:59] <popey> dobey: apt, apt-utils and apt-transport-http are on the phone, not much else in regards to application shopping
[18:00] <bzoltan> bobweaver:  As I saw in the video you start a regular Ubuntu in a VM and launch the unity-next as a standalone app in it. I do not see the added value compare to just starting the QML apps on the desktop.
[18:00] <dobey> popey: is everything run as root?
[18:00] <popey> dobey: by "everything" do you mean apps? if so, no, there's a non-root user 'phablet'
[18:00] <bobweaver> bzoltan,  you can use Hud in normal desktop ?  you can tie apps into touch on normal desktop ?
[18:01] <bobweaver> you can use on windows and mac on desktop ?
[18:02] <bzoltan> bobweaver:  using HUD is a good one.
[18:03] <bobweaver> bzoltan,  the idea would be to make the standalon app not stand alone and a shell. And make upstart for it make user "ubuntu" no login and kill unity and all that on start up
[18:03] <dobey> popey: how does "phablet" request that something be installed? you just have to open a terminal and run "sudo apt-get install foo" or something? is there a plan to have aptdaemon there, or are plans leaning toward something else?
[18:03] <bzoltan> bobweaver:  Sorry, I missed the part of tieing apps into touch. Where was it? Why not to start the next without the VM?
[18:03] <bobweaver> bzoltan,  that is the idea I only started this yesterday
[18:03] <popey> dobey: we don't have that functionality yet
[18:03] <popey> aiui
[18:03] <bzoltan> bobweaver:  but it was not in your demo
[18:04] <popey> dobey: I think aquarius is the best person to ask
[18:04] <dobey> i was afraid you might say that :)
[18:04] <popey> :D
[18:04] <bobweaver> bzoltan,  because that is not implanted as of yet. I would need to hack unity-next and if I am going to do that I need / want to make sure that what I am doing i the correct steps
[18:05] <bobweaver> no need to re-create the shell like I did with unity 2d if it is not what Canonical wants
[18:05] <bobweaver> so what I am saying or trying to lol  is that I do not wnt to hack on the shell and the virtual machine iso if there is no reason to :)
[18:06] <bzoltan>  bobweaver: What I am interested in is  1) a VM running the phablet image  2) qml-shell running in a nested display server
[18:06] <popey> +1 to a VM running phablet
[18:07] <bzoltan> popey: yes, that is real deal.
[18:07] <bobweaver> my plain of attack is as follows  1) talk to you all. 2)  hack the vm so that it i lean mean fighting machine. make the upload and paths and what not correct for the shell
[18:07] <bobweaver> 3)  make qtcreator have more options
[18:07] <bzoltan> bobweaver:  You talk to me, so that is a good start :)
[18:07] <bobweaver> 4 ) add button to launch the vm under the devices button
[18:08] <bobweaver> add tests to the wizards fo debian packaging
[18:08] <bzoltan> bobweaver:  I am frank with you. I think you attack on too many fronts. I personally prefer simple steps and properly done small features.
[18:08] <bobweaver> Hi frank :) j/k I am glad that you are that is the best ! thanks
[18:09] <bobweaver> bzoltan,  so the vm would need to be packaged with the sdk in the end with its own ssh keys and what not
[18:09] <bzoltan> bobweaver:  I know
[18:09] <bobweaver> bzoltan,  what do you think about that ?
[18:10] <bzoltan> bobweaver:  The best would be native VM with the armhf phablet image in it.
[18:10] <popey> still yet to see a reason why we can't use the android emulator
[18:11] <bobweaver> davik >
[18:11] <bobweaver> ?
[18:11] <bobweaver> like adk ndk style ?
[18:11] <bzoltan> bobweaver:  the second option would be to start the qml-shell in a nested display manager
[18:12] <bobweaver> bzoltan,  it is cgwinn chrooted ? for stock android ?
[18:12] <popey> alan@deep-thought:~/android-sdk-linux/tools$ file emulator-arm
[18:12] <popey> emulator-arm: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
[18:12] <popey> bobweaver: ^^ that one
[18:12] <bzoltan> bobweaver:  yes
[18:12] <bobweaver> popey,  that is fine but how to talk to qtcreator
[18:12] <bobweaver> adk ndk ?
[18:13] <popey> via adk
[18:13] <popey> adb etc
[18:13] <bobweaver> and what use ant for java
[18:13] <popey> java?
[18:13] <bzoltan> bobweaver:  qtc is a little problem
[18:14] <bobweaver> so is davik or how ever you spell it
[18:14] <bobweaver> adk ndk part ^^
[18:14] <bzoltan> dalvik
[18:14] <Rttommy> Anyone encountered the QQmlComponent: Component is not ready bug?
[18:15] <bobweaver> becuase it is cgwinn or how ever uyou spell that :)
[18:15] <bzoltan> bobweaver:  there are two options: 1) emulated platform with a full stack 2) emulated display server and shell
[18:16] <bobweaver> bzoltan,  do you think that it would be better for vm stuff to wait for necessitias to get to qt5 ?
[18:16] <bobweaver> seems like bogden or what ever his name is is working on that
[18:17] <bzoltan> bobweaver:  what is missing from qt5?
[18:17] <bobweaver> compiler and a couple of other things
[18:17] <bobweaver> phone brb
[18:18] <bzoltan> bobweaver:  compiler? I do not understand...
[18:18] <netcurli> Rttommy: yes
[18:18] <bobweaver> for a7
[18:19] <bobweaver> also I do not think that minestro has any repo for qt5
[18:19] <ogra_> why woudl you need a compiler in a vm ?
[18:19] <bobweaver> for apps
[18:19] <ogra_> you cross build already
[18:19] <Rttommy> netcurli: How can I fix it (I installed the SDK as instructed, on 13.04)
[18:19] <ogra_> no need for it to live in the vm
[18:19] <bobweaver> ogra_, Oo
[18:20] <ogra_> you only want the vm for executing your binaries and test them
[18:20] <bobweaver> no for qt I am saying
[18:20] <ogra_> (at least we do)
[18:20] <bobweaver> ogra_,  have you ever used necessitia ?
[18:20] <ogra_> compiling inside the vm will be slow as hell
[18:20] <bobweaver> no no no
[18:21] <bobweaver> it compiles and sends package to device
[18:21] <ogra_> no, i havent even ever used Qt ... but i have worked with arm vms for years
[18:21] <bobweaver> adt or whatever they are called
[18:21] <ogra_> right, and we would like to replace the device with a vm
[18:21] <bobweaver> android app like deb but for android
[18:21] <ogra_> but keep the setup beyond that as is
[18:22] <spanner3003> Hi I'm trying to build cm10.1 for padfone 2 anyone interested in helping me please.
[18:22] <ogra_> currently we do cross builds that we push to the real device running UTouch
[18:22] <ogra_> from the SDk
[18:23] <gustavold> nt?
[18:23] <ogra_> and we would like to have the VM for people that dont have a device
[18:23] <ogra_> no other changes
[18:23] <ogra_> so we need a VM that runs UTouch
[18:24] <ogra_> and that the SDK can push to
[18:24] <netcurli> Rttommy: you are only talking about the error message, right? the application runs fine otherwise?
[18:24] <bobweaver> so necessitia was made so that qt developers could make apps on vm to test (or to deploy to device ) if no device it launchs emulator (dalivik ) and then makes package for android  it then after adb pushing used necesstia to call minestro that looks at device if package is(qtcore / whatever) is installed your app launchs (this happens only once ) if it is not it installes them
[18:25] <bobweaver> project lighthouse I thinkit was called
[18:25] <Rttommy> netcurli: no, many elements (in the tutorial and the touch core apps) do not render correctly.
[18:25] <bobweaver> Think is key word
[18:25] <ogra_> bobweaver, right we would want the dalvik part without dalvik but instead with UTouch :)
[18:25] <bobweaver> correct
[18:25] <bobweaver> that is the hard part
[18:26] <netcurli> Rttommy: do you get other error messages as well?
[18:26] <ogra_> one idea was to have an x86 android build that runs in qemu
[18:26] <ogra_> same thing we run on the devices but x86 and qemu based
[18:26] <Rttommy> netcurli: the only output is : QQmlComponent: Component is not ready /usr/lib/x86_64-linux-gnu/qt5/bin/qmlscene exited with code 0
[18:26] <bobweaver> that is what I have in virtual box ogra_  but I just did not want to take all the time to fix it if not a good idea
[18:27] <ogra_> bobweaver, so you did an android x86 build ?
[18:27] <bobweaver> it is concept
[18:27] <bobweaver> ogra_,  yeah
[18:27] <ogra_> of our device tree ?
[18:27] <bobweaver> things are missing
[18:27] <bobweaver> device tree ?
[18:27] <ogra_> pahblet.ubuntu.com
[18:27] <ogra_> *phablet
[18:28] <ogra_> our stripped android base
[18:28] <bobweaver> I compiled it and had to alter some tests and what not Hud was a b&*^(
[18:28] <ogra_> Hud ?
[18:28] <ogra_> i'm talking about the device layer ...
[18:28] <ogra_> not the rootfs
[18:29] <bobweaver> no this is just concept:(  but the idea if x86 then take the ubuntu-minamal and start there build a working VM
[18:29] <bzoltan> bobweaver: I do not think we want a VM based cross compiler in the Ubuntu Touch SDK in the following half a year.
[18:29] <netcurli> Rttommy: and what exactly is not working? can you pastebin the code you try to run?
[18:29] <ogra_> we want to emulate the device layer ...
[18:29] <bobweaver> a great example of this would sailfish and how they are doing it
[18:29] <bzoltan> bobweaver:  for armhf target I suggest to use the real device or crosscompile on the desktop
[18:29] <bobweaver> but with out mer
[18:30] <Rttommy> netcurli: https://bazaar.launchpad.net/~dpm/+junk/CurrencyConverterUpdated/files/8
[18:30] <ogra_> bobweaver, the issue is that we need the platform-api and libhybris bits running in android to have proper emulation
[18:30] <ogra_> bobweaver, else it is just Ubuntu Touch being run in an x86 VM
[18:30] <ogra_> we want to emulate the whole stack
[18:31] <bobweaver> bzoltan,  I agree seems like you all have the device stuff under wraps all ready for the creator
[18:31] <ogra_> including the lowest layer
[18:31] <bobweaver> ogra_,  How to tie into qtcreator ? just wondering ?
[18:31] <ogra_> so Mir can eventually just blend in (and with luck directly talk to the deslktop Mir)
[18:31] <netcurli> Rttommy: and it doesn't look like the screenshots from the tutorial?
[18:32] <bzoltan> bobweaver:  what we want is what popey, ogra_ and me are saying... either emulate the whole stack or just run the shell in a nested display server on x86
[18:32] <ogra_> right
[18:32] <ogra_> what bzoltan said
[18:32] <ogra_> like xephyr ... but using Mir :)
[18:32] <std> how far has the terminal app yet?
[18:32] <bzoltan> ogra_:  exactly
[18:32] <ogra_> or a full android VM
[18:32] <bobweaver> yeah I am onboard for that bzoltan  Just wondering If I should start on the second one ?
[18:32] <std> *is
[18:33] <ogra_> bobweaver, thats hard since there is no Mir for the desktop yet
[18:33] <bobweaver> zephyer is AWESOME !
[18:33] <bzoltan> bobweaver:  That would be a great idea
[18:33] <ogra_> we would need one mir to talk to the other
[18:33] <bobweaver> correct
[18:33] <bzoltan> bobweaver: yes, I liked zephyer from the N900 and N9 SDK :)
[18:33] <ogra_> and to date only the android Mir is working afaik
[18:33] <Rttommy> netcurli: Nope, the header is empty, and part of the main area is hidden under the header.
[18:34] <bobweaver> ogra_,  / bzoltan  x11 VM super striped down that only has shell running ?
[18:34] <ogra_> nope
[18:34] <ogra_> that will not work :)
[18:35] <bobweaver> ogra_,  or bzoltan  google hangout ?
[18:35] <netcurli> Rttommy: then maybe that has to do with the tutorial code not having been updated for the current UI toolkit version
[18:35] <ogra_> nope, i had a full day of hangouts today ... (its late here) ... we can do one tomorrow if you like
[18:36] <bzoltan> bobweaver:  Only if you teleport to Finland in the unfortunate case my kids wake up from my voice....
[18:36] <ogra_> bobweaver, the point is that what you know as shell today will soon make full use of Mir features
[18:36] <bobweaver> I would like to start working on x86 striped down one
[18:36] <bobweaver> cool
[18:36] <ogra_> so X11 wont help
[18:36] <Rttommy> netcurli: That's what I'm starting to guess, thank you, I'll wait until the code is updated
[18:36] <bobweaver> yeah I meant x86
[18:36] <bobweaver> sorry
[18:36] <ogra_> ah
[18:36] <bobweaver> mir is a no go on x86 ?
[18:37] <ogra_> nope, but further from being ready than on arm
[18:37] <ogra_> they focus on the android drivers only atm
[18:37] <ogra_> so when S opens you will see Mir land for UTouch but not for the desktop yet
[18:38] <shadeslayer> lilstevie: poke poke
[18:38] <ogra_> what we need is something like http://www.android-x86.org/  ported to phablet.ubuntu.com
[18:38] <ogra_> as our base
[18:38] <ogra_> there Mir will just easily work
[18:39] <bobweaver> why not make it happen like that striped down x86 so the only thing that is running is the ubuntu-ui-toolkit example and also the shell (not as stand alon app though )    make dirs so thtat they are readable and have them install (qtcreator-->dirs) and have it restart unity on start up ?
[18:39] <ogra_> the alternative is to wait until the desktop Mir lands ... but that will be to late
[18:39] <bobweaver> so that way app can talk and act in shell (phablt)
[18:39] <ogra_> the prob is that we will start to rely on Mir functions
[18:40] <ogra_> you need a way to run that bit
[18:40] <bobweaver> so scrap it and add mir to it ?
[18:40] <ogra_> to what ?
[18:40] <bobweaver> from x11
[18:40] <bobweaver> the vm ^^
[18:40] <ogra_> if Mir only riuns on androids libGLES atm
[18:40] <ogra_> *runs
[18:41] <bobweaver> but later ? I mean it is going to run on x86 I would hope
[18:41] <ogra_> the problem is that there is no way to replace X11 yet
[18:41] <ogra_> yeah
[18:41] <ogra_> later it will
[18:41] <voyaflex> which apps are working right now
[18:41] <ogra_> but that will be to late for us :)
[18:41] <bobweaver> so x11 now then replace with mir
[18:41] <bobweaver> I mean the Virtual machines can be updated with package
[18:41] <ogra_> as soon as S opens and the new unity lands it will start depending on Mir
[18:42] <bobweaver> I have virtual machine of zephyer for Mer
[18:42] <ogra_> and will likely not be fully functional in an X11 based VM
[18:42] <bobweaver> I see
[18:44] <bobweaver> that is what I make all my qt5 apps for wayland on is the zephyer using Mer and qtcreator
[18:44] <bobweaver> would it not be the same with Mir ?
[18:44] <bobweaver> sorry just trying to get this all together ?
[18:44] <ogra_> not sure
[18:45] <ogra_> well, the think is that we will make heavy usage of the compositing of Mir in the UI
[18:45] <tedg> rsalveti, Do we have support for the light sensors on the current Nexus devices?
[18:45] <ogra_> *thing
[18:45] <ogra_> you wont be able to emulate that in X or zephyr
[18:45] <rsalveti> tedg: not yet, ChickenCutlass looked at that during the london sprint, but we didn't yet finalize the implementation
[18:46] <ogra_> its trivial
[18:46] <ogra_> (teh light sensors)
[18:46] <ogra_> you can read their value from sysfs
[18:46] <tedg> Hmm, we were just curious about that for indicator-power.  Whether it'd make more sense to use that data instead of a slider.
[18:47] <bobweaver> ogra_,  here is my zephyer set up https://lh4.googleusercontent.com/-_y2zcbpF7cw/UTo9rKCGEXI/AAAAAAAAA10/D3DF5ANvmWo/s902/Screenshot+from+2013-03-08+14%3A34%3A38.png                                I just use that as testing bed for apps (alot of things dont work yet on it though )
[18:47] <ogra_> tedg, http://paste.ubuntu.com/5699366/ ... thats what i use on the chromebook ... i dont have my nexus7 handy buts its similar
[18:47] <tedg> ogra_, Is there a upower interface for that?  I thought there was.
[18:47] <bobweaver> https://wiki.merproject.org/wiki/Zephyr
[18:47] <rsalveti> ogra_: getting the values is trivial, but we don't have an api for that
[18:47] <rsalveti> tedg: brighteness is different
[18:47] <rsalveti> you need to use sysfs indeed
[18:47] <ogra_> rsalveti, right
[18:47] <rsalveti> like what is done by g-s-d
[18:48] <bobweaver> so I guess that there will be a qt-mir like qt-wayland
[18:48] <ogra_> g-s-d doesnt do light sensors
[18:48] <rsalveti> but for the auto-brighteness you'd need that indeed
[18:48] <ogra_> bobweaver, yeah !
[18:48] <rsalveti> and that's why it's not yet supported even on phablet
[18:49] <ogra_> but getting an api together shouldnt be hard ... work of a day or two
[18:49] <ogra_> since you can already easily get and set the values
[18:50] <ogra_> just needs the high level definition
[18:50] <ogra_> and i think janimo started some work on that for the g-s-d nexus7 stuff for the desktop image
[18:50] <tedg> I'm surprised that Upower doesn't abstract it.
[18:50] <ogra_> not sure if there is proof of concept code
[18:50] <tedg> Is the sysfs interface constant for everyone?
[18:51] <ogra_> brightness is, lux/illuminance isnt afaik
[18:51] <rsalveti> tedg: at least for brightness it is
[18:51] <rsalveti> ogra_: doing the api is easy, the hard part is doing it in a way it's common and standard enough for us to use at somewhere else ;-)
[18:52] <rsalveti> we don't want to keep changing api all the time
[18:52] <ogra_> yep
[18:52] <bobweaver> +1
[18:52] <rsalveti> so that's why we decided no to do it until we have a standard way of handling all the sensors
[18:52] <tedg> Hmm, doesn't seem my laptop (which has a light sensor) has anything "illuminance" in there.
[18:52] <ogra_> look for lux
[18:54] <ogra_> i think the non standardization of the kernel interfaces is the reason you dont have that in upower and g-s-d
[18:54] <tedg> Uhg
[18:54] <ogra_> its usually a platform device on arm and everyone picks their own names
[18:54] <ogra_> not sure how it is on x86
[18:54] <ogra_> but i wouldnt expect much better there
[18:55] <rsalveti> even worse at the android based kernels
[18:55] <ogra_> the illuminance interface should be identical on the nexus 10 btw
[18:56] <ogra_> since chromebook and n10 have the same board afaik
[18:56] <rsalveti> that's why android has an abstraction layer for that
[18:56] <ogra_> yep
[18:56]  * tedg still hasn't found it on his machine
[18:56] <ogra_> heh
[18:56] <rsalveti> I think the only thing related with light sensor at upower is related with the keyboard
[18:56] <ogra_> x86 HW is so weird and ilogical ...
[18:56] <ogra_> :P
[18:57] <bobweaver> bzoltan,  soorry to nag well.... nr but should I make proff of Concept x86 I mean it is going to be super bare bones
[18:57] <davmor2> hey ogra_ touch version has no sound on a n7 is this something that should get fixed with the move to raring?
[18:57] <bzoltan> bobweaver:  no worries... you have heard  ogra_ about the possibilities
[18:58] <ogra_> davmor2, known bug, not fixed in raring
[18:59] <davmor2> ogra_: :( but know :)
[18:59] <ogra_> davmor2, the android layer is the same in raring and quantal ... its a low level thing
[18:59] <davmor2> ogra_: ah okay that makes more sense then
[18:59] <mhall119> davmor2: ogra_ recomments audiobooks with subtitles to work around it :)
[18:59] <ogra_> :)
[19:00] <davmor2> ogra_: is it the same thing with the camera though I haven't tried that lately
[19:00] <bobweaver> bzoltan,  ogra_  so just dont pull out qx11extras what ever I do then :P
[19:00] <davmor2> mhall119: are they not just called books at that point ;)
[19:01] <ogra_> davmor2, yeah, just draw signs with subtitles :)
[19:01] <mhall119> davmor2: no no, way better
[19:01] <ogra_> :)
[19:01] <davmor2> haha
[19:02] <davmor2> mhall119: I think you have worked with Europeans too long you seem to get sarcasm :P
[19:02] <davmor2> mhall119: that jono has a lot to answer for :)
[19:02] <mhall119> davmor2: I'm from the south, I was born into sarcasm
[19:03] <davmor2> mhall119: isn't that in Louisiana
[19:03] <mhall119> the dangly-part of the south
[19:04] <ogra_> the norway of the equator ?
[19:05] <mhall119> ha, I like that, I'm using it from now on
[19:05] <ogra_> :)
[19:30] <popey> hmm, qml shell seems to have barfed on my daily today
[19:31] <tedg> rsalveti, Okay, so it seems there's iio in the kernel that is supposed to be "the" way to do ambient light sensors.
[19:31] <popey> in fact there are no processes running as phablet
[19:31] <tedg> rsalveti, There are a few drivers for it.  Do you know what chips are in the nexus devices?
[19:31] <rsalveti> tedg: no, but can check
[19:31] <rsalveti> tedg: did you find which kernel subsystem this is in?
[19:32] <tedg> rsalveti, iio, which doesn't make sense to me.  But, eh.
[19:32] <popey> restarting qml-phone-shell now It cant see any networks
[19:32] <popey> seems properly borked
[19:32]  * popey reboots
[19:32] <tedg> rsalveti, Apparently it's relatively new.
[19:32] <rsalveti> tedg: right
[19:32] <rsalveti> let me investigate as well
[19:33] <tedg> rsalveti, meet sforshee, he has taught me everything I know about iio :-)
[19:34] <rsalveti> :-)
[19:34] <sforshee> geez, you must not know much then
[19:34] <sforshee> cause I sure dont ;-)
[19:34] <tedg> That is a very good assessment :-)
[19:35] <tedg> rsalveti, sforshee was also interested in figuring out what we're doing for various other HW abstractions.
[19:35] <tedg> I don't know much about that either, but thought getting you two to talk would be best.
[19:36] <sforshee> actually rsalveti and myself and some others are supposed to chat about it next week
[19:36] <rsalveti> as not everything at android is following the usual standards, and also providing stuff via binaries, we initially thought about abstracting the sensors interface via an api similar to the platform-api
[19:36] <rsalveti> so I believe we'd need some sort of api/abstraction layer
[19:36] <rsalveti> and hopefully get better drivers as well following whatever is standard at the kernel
[19:37] <sforshee> yes, I'm of a similar opinion after looking at the drivers for a couple of devices
[19:37] <sforshee> for some things the kernel interfaces are well-enough defined to serve as the abstraction, like input for example
[19:37] <sforshee> but for other areas like sensors, not so much
[19:38] <rsalveti> right
[19:38] <tedg> I mean, if we're going to invest in work there, would it make sense to do that work in the kernel to get better interfaces?
[19:38] <rsalveti> sure, but we could do that in parallel, as we cannot easily change the current drivers available
[19:38] <sforshee> except we're targeting android devices which are already using ad-hoc interfaces into the kernel
[19:39] <rsalveti> remember we need a way to reuse what is already available as well
[19:39] <rsalveti> besides looking forward for the right implementation
[19:39] <tedg> Sure, but if I remember right there's a way to do some sort of loopback style thing in a kernel driver.
[19:39] <tedg> So we could mimic the interface.
[19:39] <sforshee> for some types of devices
[19:39] <tedg> Sensors?  :-)
[19:39] <sforshee> we might have to invent it for e.g. iio
[19:39] <sforshee> I doubt it
[19:40] <sforshee> input has that
[19:40] <sforshee> also we have to keep in mind that some devices don't have a kernel driver at all
[19:40] <sforshee> gps on the nexus 4, for example
[19:40] <rsalveti> we also need to better understand how android is currently handling that, and how that's used at least for the devices we support
[19:40] <rsalveti> exactly
[19:40] <tedg> Hmm, that is much trickier.
[19:40] <rsalveti> they might only export the memory interfaces sometimes
[19:40] <sforshee> or not even that
[19:40] <rsalveti> or be completely user space
[19:41] <rsalveti> i2c?
[19:41] <sforshee> not positive, my guess is a uart
[19:41] <sforshee> plus some gpios
[19:41] <tedg> I guess I'd just like it to be where we could use something like udev or upower to access them.
[19:41] <tedg> Not invent another interface there.
[19:41] <mpt> Just completed initial design for "Cellular" phone settings. https://wiki.ubuntu.com/Networking#Phone
[19:42] <rsalveti> tedg: I'm not sure that this will be possible
[19:42] <rsalveti> we might end up needing another abstraction layer
[19:42] <tedg> rsalveti, :-(
[19:42] <tedg> I was hoping we could just tell udev that it's an iio device if that's what we think the final would be.
[19:43] <rsalveti> that's why the idea was to follow and extend kind of what is currently done at the platform-api
[19:43] <tedg> Even if udev is doing something crazy in userspace.
[19:43] <rsalveti> we cannot enforce this final decision either
[19:43] <rsalveti> we can enforce as a distro, but not when doing a product
[19:43] <sforshee> tedg, what might be realistic is that we provide abstraction libraries for the "standard" interfaces to make something like iio work automagically
[19:44] <sforshee> and someone making a product could supply their own libraries
[19:44] <rsalveti> we'll kind of get whatever the vendor is able to give us, and depending on the timeframe, we might not have time to do it the 'right' way
[19:44] <rsalveti> exactly
[19:44] <rsalveti> that's exactly the big and most useful thing from android
[19:44] <rsalveti> the abstraction layers, even if that makes a pita to maintain from a distro perspective
[19:45] <rsalveti> but working with oems is not an easy task
[19:45] <rsalveti> and android succeeded on that
[19:45] <tedg> Sure, I guess I just feel like we have an abstraction layer already.  Let's put more in there than build another one.
[19:45] <sforshee> in an ideal world ...
[19:46] <rsalveti> well, we're redesigning the current one, which is the platform-api
[19:46] <tedg> Let the vendor library link in there, not into the user space.
[19:46] <rsalveti> right
[19:46] <rsalveti> the platform-api is abstracting the access via hybris (and then android libs)
[19:47] <tedg> Well, platform API is kinda silly.  I mean, it's hard to use because it's all pure C/C++.  Where things like udev have simple libraries already built to access them.
[19:47] <rsalveti> right, that's why I said *we* can propose something better now
[19:47] <rsalveti> while we kind of redesign platform-api
[19:48] <rsalveti> and I believe that was the work ChickenCutlass was kind of responsible for
[19:48] <ChickenCutlass> rsalveti: what did I do now ?
[19:48] <ChickenCutlass> lol
[19:48] <tedg> I guess my thought would be that window and application management need to be separate from sensors/drivers.
[19:48] <tedg> That stuff has to be in user session, where the other is system level.
[19:49] <rsalveti> ChickenCutlass: discussing about the abstraction around the sensors :-)
[19:49] <ChickenCutlass> right
[19:49] <rsalveti> tedg: I'm +1 on that
[19:49] <rsalveti> I'd like to abstract that at a base os/platform layer
[19:49] <sforshee> +1 from me too
[19:50] <rsalveti> separated from ui and session handler
[19:51] <tedg> Trying to think of why it bothers me.  I think it's because one needs to go across user boundaries, and one doesn't.
[19:51] <tedg> There'll always be one rotation sensor, but there could be a session manager per suer.
[19:52] <tedg> (well, there could be two axis, but I think you get the point)
[19:52] <shadeslayer> ogra_: okay, last step remaining, I have no idea how one creates an initrd
[19:52] <rsalveti> and sometimes we'd also need to abstract to reduce sensor usage, in a way only the abstraction/provider would control the real access to the sensor
[19:53] <rsalveti> like, we don't want to have a bunch of apps taking the data in parallel directly from the hardware
[19:53] <rsalveti> but instead trying to sync that at a provider
[19:53] <tedg> rsalveti, Are you thinking just for accessing it at the same time issues, or power?
[19:53] <sforshee> I think both are valid concerns
[19:53] <rsalveti> yeah
[19:54] <sforshee> if all drivers are completely in the kernel then we _might_ be able to deal with concurrent access
[19:54] <ChickenCutlass> rsalveti: so currently there is a sensor service on the android side that controls access to the data.
[19:54] <sforshee> but I've seen drivers which do power control by exporting a gpio to userspace
[19:55] <sforshee> so if you have multiple processes trying to control power, things are likely to go bad
[19:55] <rsalveti> right, it's all kind of crazy, lack of standards all around
[19:55] <rsalveti> ChickenCutlass: right, we might end up using that or doing something similar to it
[19:55] <ChickenCutlass> rsalveti: yup
[19:56] <tedg> I think the key is that we need something that works for laptops too.  If we use it, we need to figure out how to make it work on that side of things.
[19:56] <tedg> Not sure if that's a big deal or not.  But I really want my backlight to use my ambient light sensor ;-)
[19:57] <rsalveti> sure, we need to abstract all use cases
[19:58] <tedg> So, what triggered all this is mpt asking whether we need a slider for brightness in the power indicator or we could solve this with ambient light sensors.
[19:58] <tedg> And it seems like there is generally support for it, but we're not quite close to making use of it.
[19:59] <rsalveti> well, we need both
[19:59] <rsalveti> we need auto-brightness and to allow the user to manually set the level of brightness
[20:00] <sergiusens> rsalveti: if you apt-get update the raring image, it will be mostly functional
[20:00] <rsalveti> sergiusens: cool, let me try
[20:00] <tedg> rsalveti, Because of ambient light sensor not being accurate enough, or because we don't have support for it?
[20:01] <tedg> For instance, iOS doesn't expose it easily.
[20:02] <rsalveti> tedg: well, android exposes both, so I just assumed that
[20:02] <rsalveti> I'd hate if the device didn't allow me to control brightness
[20:02] <rsalveti> just because I personally hate when the device tries to be smarter than me :-)
[20:02] <tedg> Heh, it's like the number of people at UDS that complain we don't have a good CPU monitor.
[20:02] <tedg> :-)
[20:03] <rsalveti> tedg: but I agree, that's easier to assume at i* devices
[20:03] <rsalveti> because they fully control the hardware
[20:03] <rsalveti> so they can make sure the sensor is good enough at most of the cases
[20:03] <rsalveti> which is not the case for android based devices, and which would be similar with us I believe
[20:04] <sforshee> and can we really assume that all devices even have an light sensor?
[20:04] <tedg> There is probably a chicken and egg problem there, eh?  The OEMs don't work on it because they figure users adjust it.
[20:04] <rsalveti> probably not
[20:06] <tedg> I would think so for mobile...
[20:06] <tedg> I mean, laptops, no.  But every phone would need at least a proximity and a light sensor.
[20:07] <rsalveti> yup, but if we allow the user to manually control the brightness level that would work for all cases already
[20:07] <rsalveti> so that's why I think we should have both
[20:07] <tedg> It seems to me like something that could be in settings instead of the indicators though.
[20:08] <rsalveti> tedg: the entire idea of the touch indicators was to allow the user to change stuff there directly ;-)
[20:10] <tedg> Heh, I wish we could have the few of settings.
[20:10] <tedg> that few
[20:10] <tedg> Would make my job easier!
[20:11] <rsalveti> :-)
[20:23] <shadeslayer> could anyone explain to me how the initrd.img for the boot.img is made?
[20:23] <shadeslayer> and if possible, which kernel is used ?
[20:24] <rsalveti> shadeslayer: they are built as a build step from the android image currently
[20:25] <rsalveti> using the kernel sources from android as well
[20:25] <rsalveti> depending on which device you built against
[20:25] <shadeslayer> okay, and what if I want to build a initramfs that can boot ubuntu but use the android kernel, is that possible?
[20:25] <rsalveti> shadeslayer: yup
[20:26] <shadeslayer> could you give me a quick run down? :)
[20:26] <rsalveti> ChickenCutlass: might have a few pointers easily, he is mostly doing the same thing at this moment
[20:27] <shadeslayer> aha
[20:27] <shadeslayer> :)
[20:27] <rsalveti> abootimg helps you extracting and creating the boot.img
[20:27] <shadeslayer> yeah I have that part down :P
[20:27] <rsalveti> so you can extract that, put your own initrd and create it again
[20:27] <shadeslayer> but I have no experience in creating an initrd
[20:28] <shadeslayer> I've always downloaded premade initrd's and they worked :P
[20:28] <rsalveti> right, that's done by the update-initramfs tool available at ubuntu
[20:28] <nubby> anyone here workign on a one x port ??
[20:29] <shadeslayer> rsalveti: what I'm trying to accomplish : Android kernel + any initrd that can boot ubuntu + a debootstrapped rootfs in userdata
[20:29] <shadeslayer> rsalveti: then I can pass rootfs=/dev/block/whatever and I think it'll work
[20:29] <nubby> as i ntoiced the current maintainers seem to be mia
[20:29] <shadeslayer> atleast that's how the TF101 worked
[20:29] <rsalveti> sergiusens: awesome, lens working again :-)
[20:30] <rsalveti> sergiusens: how far are we from fixing the resolv.conf issue?
[20:30] <rsalveti> shadeslayer: right
[20:30] <sergiusens> rsalveti: yup... I'll double check with tim... if not, I'll workaround it
[20:30] <rsalveti> sergiusens: ok, so we can have a fully working build tomorrow already
[20:30] <shadeslayer> oh, that sounds right?
[20:31] <rsalveti> shadeslayer: usually there's not much hardware specifics at the initrd
[20:31] <shadeslayer> rsalveti: yeah
[20:31] <shadeslayer> rsalveti: I wrote my own
[20:31] <rsalveti> you could have modules added by ubuntu, but you can remove that
[20:31] <nubby> i dont no what device oyur workign on btu whats teh problem with resolv.conf
[20:31] <shadeslayer> but it dodn't work :P
[20:31] <shadeslayer> it keeps rebooting
[20:31] <rsalveti> shadeslayer: :-)
[20:31] <rsalveti> crashing somewhere
[20:31] <nubby> humm resolv.comf is cuasign a system reboot or dchcpcs
[20:31] <nubby> cd*
[20:32] <shadeslayer> rsalveti: followed this http://www.ibm.com/developerworks/library/l-initrd/
[20:32] <rsalveti> ChickenCutlass: do you have the initrd you used as reference from the desktop image for nexus7?
[20:32] <rsalveti> we can just use that
[20:32] <shadeslayer> though that guide doesn't put a init call anywhere
[20:32] <rsalveti> right
[20:32] <rsalveti> otherwise would need to grab from my pand
[20:32] <rsalveti> pnda
[20:32] <shadeslayer> ^_^
[20:33] <ulph> why do I need ubuntu for android rather than runnning android with some chroot goodness?
[20:33] <nubby> ulph: im assumign becuas ubuntu is runnign from an android base btu is usign its own packages and i think its sitll rmeotely debian based
[20:33] <nubby> remotely*
[20:34] <shadeslayer> I have everything ready, I just really need a initrd
[20:34] <shadeslayer> :P
[20:34] <nubby> shadeslayer: erm what you need initrd for
[20:35] <shadeslayer> nubby: the idea is to use a ubuntu initrd + Android kernel and a debootstrapped ubuntu in userdata
[20:35] <shadeslayer> then I can get rid of surfaceflinger and use X + KDE
[20:35] <nubby> ahh what device
[20:35] <shadeslayer> not to mention other android stuff is also removed
[20:35] <shadeslayer> Nexus 10
[20:35] <nubby> ahh
[20:36] <nubby> wishign the dev team would do some work on the one x port
[20:36] <nubby> im to lazy to get the itnial boot working
[20:36] <shadeslayer> I have an HOX
[20:36] <nubby> but heh im pretty sure the lakc oif networkign is  ovrsite on ther part
[20:36] <shadeslayer> but I don't want to screw my only phone ;)
[20:36] <nubby> heh you shoudlent scrfew it the oen x is prety mcuh unbrickable
[20:37] <nubby> as logn ads oyu have recovery and a kernel installed you should be safe
[20:37] <shadeslayer> well, I meant, it's my only phone, and if I isntall unstable things, I won't be able to make calls or whatever
[20:37] <nubby> fair point
[20:37] <rsalveti> shadeslayer: right, let me boot my panda
[20:38] <shadeslayer> awesome
[20:38] <nubby> shades you lucky enogh to have an s-off'ed
[20:38] <shadeslayer> nubby: no idea, its all stock
[20:38] <nubby> ahh
[20:38] <nubby> lols
[20:38] <nubby> s-off'ed hoxs are rear as rockign horse shit
[20:39] <nubby> unless you got a the lte version
[20:39] <nubby> then there ment to be an s-off method sicne it isnt based on tegra 2
[20:39] <nubby> tegra3*
[20:40] <shadeslayer> rsalveti: I don't suppose you have an idea on how big the Nexus 10 boot partition is :P
[20:40] <rsalveti> shadeslayer: can try to check
[20:41] <shadeslayer> okay
[20:42] <shadeslayer> rsalveti: fwiw I made a ramdisk using mkinitramfs -o ramdisk.img in a armhf chroot
[20:42] <shadeslayer> bootloop
[20:42] <nubby> how big is the source for ubuntu-touch and all its nessercery bits and peices
[20:42] <shadeslayer> :(
[20:44] <rsalveti> shadeslayer: http://people.canonical.com/~rsalveti/initrd-raring.img
[20:44]  * shadeslayer tries
[20:44] <rsalveti> gzip -dc ../initrd-raring.img | cpio -ivd
[20:44] <rsalveti> find . | cpio -o -H newc > ../initrd-new.img
[20:45] <rsalveti> + abootimg should be enough
[20:45] <shadeslayer> erm why extract it?
[20:45] <rsalveti> in case you want to change it
[20:45] <shadeslayer> ah
[20:45] <shadeslayer> lets just try it
[20:47] <shadeslayer> mmm nope
[20:48] <shadeslayer> uhh
[20:48] <shadeslayer> rsalveti: can you md5sum that for me?
[20:49] <rsalveti> d68230a5edb8ca965ca3d46c7cffde25  initrd-raring.img
[20:50] <shadeslayer> okay
[20:51] <rsalveti> crap, my n10 is out of battery
[20:51] <shadeslayer> herp derp
[20:51] <shadeslayer> not in gzip format
[20:52] <ChickenCutlass> rsalveti: shadeslayer I just installed a kernel in my armhf chroot and grabeed that initrd
[20:52] <shadeslayer> ChickenCutlass: and it worked?
[20:53] <ChickenCutlass> shadeslayer: not yet
[20:53] <shadeslayer> heh :P
[20:53] <ChickenCutlass> shadeslayer: working onit
[20:53] <shadeslayer> awesome
[20:55] <shadeslayer> ChickenCutlass: any ideas on how big the boot partition of the N10 is?
[20:56] <ChickenCutlass> shadeslayer: I don't know off hand
[20:56] <shadeslayer> I've previously faced issues with the TF101 where the bootpartition was too small
[20:56] <shadeslayer> and the boot.img I flashed was too large ( the flash command returned successfully )
[20:56] <ChickenCutlass> shadeslayer: should be big enough for a minimal initrd
[20:56] <shadeslayer> well
[20:56] <shadeslayer> I /think/ it's 4 MB's
[20:56] <shadeslayer> from the android boot img
[21:01] <shadeslayer> well now I know
[21:01] <shadeslayer> it's 16 MB's
[21:01] <ChickenCutlass> plenty big
[21:01] <shadeslayer> http://paste.kde.org/722570/
[21:01] <shadeslayer> yep ^^
[21:02] <shadeslayer> the TF101 had 5-6 MB's I think
[21:03] <rsalveti> http://pastebin.ubuntu.com/5699761/
[21:04] <rsalveti> lrwxrwxrwx 1 root root 20 Apr 11 20:28 boot -> /dev/block/mmcblk0p6
[21:04] <rsalveti> BOARD_FLASH_BLOCK_SIZE := 4096
[21:04] <shadeslayer> you have 22 MB's? 0.o
[21:06] <shadeslayer> rsalveti: http://pastebin.ubuntu.com/5699768/
[21:06] <rsalveti> shadeslayer: yup
[21:06] <shadeslayer> quite different ... hmm
[21:06] <rsalveti> shadeslayer: which device?
[21:06] <rsalveti> also, I'm using 4.2.2
[21:06] <shadeslayer> N10
[21:06] <shadeslayer> ah
[21:06] <rsalveti> 4.0.4 should be different
[21:06] <shadeslayer> well I think I updated it earlier today
[21:06] <shadeslayer> when I got it
[21:06] <shadeslayer> so should be 4.2.2
[21:07] <shadeslayer> but then I flashed ubuntu on it
[21:07] <rsalveti> I don't even have dw_mmc.0 here
[21:07] <rsalveti> shadeslayer: what is the emmc size of yours?
[21:07] <rsalveti> mine is 16gb
[21:08] <shadeslayer> that probably made different partitions I guess
[21:08] <shadeslayer> same
[21:08] <rsalveti> and the controller
[21:08] <rsalveti> oh crap
[21:08] <shadeslayer> controller?
[21:08] <rsalveti> I'm doing that at nexus 4
[21:08] <shadeslayer> lol
[21:08] <rsalveti> too many devices plugged in
[21:08] <shadeslayer> clearly ;)
[21:08] <rsalveti> shadeslayer: now it matches yours
[21:09] <rsalveti> :P
[21:09] <shadeslayer> ^_^
[21:13] <BOY77X> http://www.reddit.com/r/XXXBITCHINBEACHXXX/comments/1c5t0e/beautiful_girl_big_boobs_beautiful_face_wonderful/
[21:15] <shadeslayer> what the fuck
[21:15] <IdleOne> Please mind your language
[21:15] <shadeslayer> sorry :S
[21:15] <IdleOne> All #ubuntu-* channels follow the same !guidelines please read them if you are not aware of them
[21:16] <IdleOne> !guidelines
[21:16] <RobbyF> I see nothing
[21:16] <BOY77X> http://www.reddit.com/r/XXXBITCHINBEACHXXX/comments/1c532e/worlds_stronges_vagina_guinness_book_of_records/
[21:16] <shadeslayer> IdleOne: ^^
[21:16] <shadeslayer> ....
[21:16] <IdleOne> :/
[21:16] <IdleOne> sorry I didn't see that before
[21:20] <shadeslayer> IdleOne: doesn't make me right ;)
[21:20] <IdleOne> true :)
[21:23] <popey> !ops
[21:23] <popey> yeah, that works
[21:23] <IdleOne> needs to be edited
[21:23] <popey> ignore that
[21:24]  * k1l looks in
[21:24] <popey> sorry
[21:26] <IdleOne> !no ops-#ubuntu-touch is <reply> Help! Channel emergency! (ONLY use this trigger in emergencies) - oubiwann, corp186, popey,  k1l,  Corey, wgrant, idleone, and ogra.
[21:26] <popey> sweet!
[21:27] <IdleOne> !ops
[21:27] <IdleOne> done
[21:31] <tedg> Not sure that oubiwann would want to be pinged there.
[21:34] <mhall119> thanks IdleOne
[21:34] <IdleOne> sure thing
[21:35] <IdleOne> Anybody who doesn't want to be in that bot trigger feel free to PM me and I'll fix it
[21:35] <IdleOne> if I forgot anybody let me know also
[21:40] <shadeslayer> ChickenCutlass: how does one even debug issues with the initrd? all I get is the google logo
[21:40] <shadeslayer> and then it reboots
[21:44] <plars> anyone ever see "protocol failure" when phablet-flash tries to push the zipfiles to the device?
[21:44] <plars> I retried the adb push by hand, and it worked fine
[21:47] <ChickenCutlass> shadeslayer: without a serial console it is flying blind.
[21:47] <shadeslayer> heh
[21:48] <shadeslayer> I don't suppose the N10 has a serial console muxed over USB
[21:48] <sergiusens> plars: yeah, but I only see it on raring
[21:48] <ChickenCutlass> shadeslayer: you could possibly build the kernel with the USB gadget driver and try to get a USB serial console going.
[21:49] <shadeslayer> ChickenCutlass: reading up on what a usb gadget driver is ..
[21:50] <ali1234> that will be a major pita
[21:50] <shadeslayer> oh
[21:50] <ali1234> might be easier to patch in early framebuffer
[21:50] <plars> sergiusens: this is on quantal desktop and latest quantal-preinstalled image
[21:51] <plars> sergiusens: I've seen odd timing issues with adb not being *quite* ready after a wait-for-device before, but this is a new one, trying to reproduce now but I suspect it's a fluke
[21:52] <ali1234> shadeslayer: http://www.samsung.com/global/business/semiconductor/file/product/Exynos_5_Dual_User_Manaul_Public_REV100-0.pdf
[21:52] <ali1234> looks like it has the pin muxing details
[21:52] <plars> protocol failure
[21:52] <plars> Error while executing adb -s 0149BD7E0200E00F push /home/ubuntu/Downloads/phablet-flash/69/quantal-preinstalled-phablet-armhf.zip /sdcard/
[21:52] <sergiusens> plars: might want to check you dmesg for usb resets or something similar... at least on raring, after that I get the annoying MTP message
[21:53] <shadeslayer> ali1234: better share that with ChickenCutlass
[21:53] <plars> I just got it twice in a row
[21:53] <plars> sergiusens: nothing interesting in dmesg, but I can still run it by hand with no problems
[21:53] <shadeslayer> he probably knows how to get this working better than me
[21:54] <ChickenCutlass> shadeslayer: I will get it working.
[21:54] <ChickenCutlass> shadeslayer: give me some time.
[21:54] <sergiusens> plars: hmmm... I'll check the script for weirdness, but I think I already have :-P
[21:55] <shadeslayer> ChickenCutlass: right :)
[21:55] <shadeslayer> I have no idea how to :P
[22:10] <ali1234> looks like the USB pins aren't muxxed with anything useful... i don't think you can even GPIO with them
[22:11] <shadeslayer> that sucks
[22:12] <shadeslayer> okay, I'm sleeping, will pursue this tomorrwo
[22:12] <shadeslayer> night :)
[22:27] <sergiusens> rsalveti: still around?
[22:27] <rsalveti> sergiusens: yup
[22:27] <sergiusens> rsalveti: have an MR for you
[22:27] <rsalveti> sergiusens: sure :-)
[23:00] <Linton> Is there an official Google blog for ubuntu touch somewhere? I want to know when the next release happens.
[23:26] <RobbyF> rsalveti, good raring tomorrow eh? what timezone are you in ? :p
[23:30] <wilee-nilee> Linton, there is a daily I believe.
[23:31] <RobbyF> https://plus.google.com/u/0/114111362741083777649/posts/1j5HvB1uqBT
[23:31] <RobbyF> tease
[23:31] <RobbyF> lol
[23:31] <Linton> I was missing the terms "daily" or "changelog".  That's what I needed.  Thanks!!
[23:42] <dank101> Help everyone
[23:42] <dank101> i MUST KNOW
[23:42] <dank101> what are the new lib hybris libs
[23:43] <dank101> my retarded little brother broke my android compiling laptop
[23:43] <dank101> i was wondering
[23:43] <dank101> can i just copy the new libs
[23:43] <chriadam> dank101: https://github.com/stskeeps/libhybris
[23:44] <dank101> Compiled?
[23:44] <chriadam> oh, sorry, I misunderstood what you were asking
[23:44] <dank101> Lol
[23:45] <dank101> Yeah pls