=== Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === XenGi is now known as XenGi_ [00:32] sergiusens: rsalveti: heh, phablet-tools, I didn't wake up about it, no point now what there has already been a release in PPA... === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [01:29] sergiusens: https://code.launchpad.net/~phablet-team/phablet-extras/ofono-release-112phablet1/+merge/158261 [02:18] rsalveti, are you here? [02:19] does anyone who knows about ofonod and ril can help me? [02:25] anyone? === Ursinha is now known as Ursinha-afk [02:41] hello [02:42] I flashed ubuntu-touch to my Sony Arc from http://forum.xda-developers.com/showthread.php?t=2226406 [02:42] It's boot but performance is low [02:44] I checked by "top" and find that, hud-service always around 54%, rsyslogd is 44% [02:45] 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] anyone on ril or ofono that can help me? === Ursinha-afk is now known as Ursinha === freeflyi1g is now known as freeflying === Ursinha is now known as Ursinha-afk [03:28] Ursinha-afk, are you there? === gxxxyyy is now known as gregk === gregk is now known as gregk8 === gregk8 is now known as gregk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === chriadam|away is now known as chriadam === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === msorvig_ is now known as msorvig === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [06:46] good morning === Ursinha is now known as Ursinha-afk [07:08] good morning === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [08:00] hi [08:01] nobody === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === ckpringle_ is now known as ckpringle === Ursinha is now known as Ursinha-afk [08:47] I'm curious, could someone explain how the graphics stack works right now ( the X bits ) on ubuntu touch? [08:47] more specifically to the N10 [08:49] ogra_: do you have any idea ^ ? [08:49] no X bits involved :) [08:49] dpm: ping [08:50] hey oSoMoN [08:50] in the android layer you have SurfaceFlinger which the Ui attaches to from the ubuntu container via libhybris [08:50] hola dpm [08:50] buenas :) [08:50] that part will soon be replaced by Mir [08:50] dpm: do you know if jenkins/autolanding is enabled for the core app template branch? [08:51] 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] shadeslayer, see the Mir spec pon the ubuntu wiki, it has an overview of "today" and "tomorrow" [08:51] s/pon/on/ [08:52] ogra_: I see, and what if for Kubuntu we want to use X + kwin_gles [08:52] since kwin won't have Mir integration [08:52] ( atleast that's the situation right now ) [08:52] you will be able to use X as you do now [08:52] but graphics acceleration? [08:52] 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] we dont plan to drop it from the archive :) [08:53] once Mir enters the desktop there will also be XMir [08:53] haha, no, I mean, lets say I install ubuntu-touch and then install Kubuntu ontop of that [08:53] ah, that wont work (doesnt work with gnome or other stuff either) [08:53] dpm: not sure autolanding is really needed for this branch, but if you can merge mine I’d appreciate :) [08:53] shadeslayer, you would need to port kwin to QtMir [08:54] 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] or just live without Kwin ... the apps should just work [08:54] ogra_: uh, Martin's position is pretty clear on Mir atm [08:54] btter ask that in #ubuntu-mir [08:55] yoou cant just use the android drivers without their context i guess ... you will need some android env around it [08:56] (the kernel and HAL layer) [08:56] I see === Ursinha-afk is now known as Ursinha [08:58] 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] oSoMoN, ok, merged :) [08:58] they can surely go more into detail [08:58] okay will ask [08:58] dpm: awesome, thanks! [09:01] possibly the mer people have also figured out something === Ursinha is now known as Ursinha-afk [09:10] 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] 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] xnox, i think that stuff isnt finalized yet [09:13] 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] ogra_: ok. Then I'm happy to start daily landing those - tbh. [09:14] ogra_: cause we will have autopkgtests to check buildability for example and I will push for api-compat monitoring. [09:14] didrocks: ^^^^^^ any other thoughts. [09:15] dont quote me on that though ... but i think the majority of sensores isnt even working afaik [09:15] 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] ogra_: i twiddle the brightness slider with my finger in the indicator and it totally works on nexus 7 =) [09:16] xnox: ok, do you mind coordinate on it with mterry? as I think some of his work is dep on yours [09:16] yeah, no network is a known bug [09:16] ogra_: ok. [09:16] xnox: sad that we can't have them being running before or as part of the daily release [09:16] should be fixed this week though according to sergio [09:16] xnox: meaning, we are breaking something and then fixing [09:16] rather than the other way around :) [09:16] 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] xnox: please put all details in the spreadsheet so that we can have a summary [09:17] 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] xnox: yeah, just mark that down and check with mterry to have the stack daily landing now [09:18] xnox: you have the bootstrap commits and everything? [09:18] once we have first image, we can start doing things similar to daily-iso-testing-desktop. [09:18] didrocks: will fill the details on the spreadsheet and commit bootstrap marker. === Ursinha-afk is now known as Ursinha [09:18] otherwise sensors are fine. and platform-api is landing into ppa already. [09:19] ogra_, Hi, as I remember you know how to detect version of build image? [09:19] xnox: great! :) [09:19] P3T3: .disk/info or some hidden file?! [09:19] P3T3, somewhere in /system/etc ... [09:19] oh..... [09:19] there is a stamp file [09:20] or was it /etc ? ... /me forgot [09:21] xnox, that will likely be there once we do actual cdimage builds :) [09:21] in S or so [09:21] OK there is /etc/buildstamp [09:21] right [09:21] didrocks: hm.... your comments seemed to be gone from the spreadsheet? or they got marked "resolved" [09:22] xnox: urgh? [09:22] didrocks: nevermind found them. [09:22] yep ;) [09:22] I have an image from popey with acubens Fri, 01 Mar 2013 05:23:11 +0000 [09:23] This image is later then MWC demo and it boots in UI, is this image from daily builds? [09:23] yes P3T3 [09:23] P3T3: march 1st is the datestamp on it [09:23] I know, but do not know which date starts daily images :-) [09:25] P3T3: how will that help? [09:25] i think the first public build was on feb 19 [09:25] or thereabouts [09:26] popey, latest daily builds fails to boot in GUI, I am searching what changed and when [09:27] sure, but you said the one you have works? [09:27] so surely something broke _after_ the image you have, not before [09:27] this one is from you and it works [09:28] right, and that's from march 1st, so you want to find out what broke after? [09:28] thats right! [09:28] we can do a bisect ☻ I can upload one from half way between then and now [09:29] I think enough will be date 10th March [09:29] ok, thats build 17, want that one? [09:30] if you can :-D [09:30] sure [09:31] P3T3: it's uploading to the same place, will be there later [09:31] popey, Thank you, I will wait [09:33] np [09:35] otherwise, I think this image from March 1st is a bit faster then MWC one [09:35] thats possible [09:45] ogra_: I'm reading up on the xf86-video-armsoc , which seems to be a driver for the Mali T6xx series [09:46] shadeslayer, well, yeah, but it has its issues with composite (i'm using it right now) [09:47] oh [09:47] i thought you were after running kde on top of ubuntu touch [09:47] hm, nope, I was thinking of running X -> Run KDE [09:48] ah [09:48] well you asked about the graphics stack of ubuntu touch initially [09:48] so i kind of assumed that [09:48] yeah, I was investigating how it works on ubuntu touch :) [09:48] I think I understand now [09:48] k [09:49] armsoc will work indeed [09:49] yay, but with issues, that's fine [09:49] but has its issues and you need to hack around in the ldconfig setup [09:49] atleast there's something I can start off with [09:49] oh? [09:49] (to prevent mesa from taking over) [09:49] ah [09:50] you want mesa for GL stuff but not for GLES [09:50] roger [09:50] and the driver doesnt have a concept fro this (since the GLES driver is completely unlicensed, so cant be distributed in packages) [09:51] fun, do you have your setup documented somewhere? or can you throw it up in a pastebin real quick? [09:52] the N10 has very bad button placement :( [09:53] so awkward to press the buttons at the top [09:53] shadeslayer: all android devices have bad button placement ☻ [09:53] 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] popey: haha [09:53] didrocks: please "add" qtubuntu-sensors to start landing into the ppa. [09:54] 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] xnox: does it have autolanding? (upstream merge) [09:55] xnox: I don't find it in the current stack [09:55] ogra_: 'here' ? [09:55] on my chromebook [09:55] ah okay [09:55] (same HW) === Ursinha is now known as Ursinha-afk [09:57] P3T3: http://people.canonical.com/~alan/phablet/17/ finished [09:58] 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] there is no driver from the archive [09:58] the driver I downloaded from google has a libGLES_mali.so [09:58] as i said, its not distributable [09:59] uh [09:59] i copied the files from chromeos [09:59] http://pad.lv/u/xf86-video-armsoc [09:59] 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] did get merged. [09:59] that doesnt contain any mali libs [09:59] its only the driver [09:59] ah I see [09:59] 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] ack. [10:00] 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] xnox: seems they did a "release" the old way (they change the changelog) for phablet [10:01] 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] (but not 100% necessary) [10:02] ogra_: how's ubuntu on the Chromebook though? [10:02] 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] so i have to resort to other WMs [10:03] waiting for Mir desktop support :) [10:03] heh :) === Ursinha-afk is now known as Ursinha === edulix2 is now known as Edulix === Edulix is now known as edulix [10:04] I can't wait to flash this literally-brand-new-N10 [10:04] alternatively hoping that someone fixes it in early S for arm desktops :) [10:05] 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] s/manu/many/ [10:06] didrocks: cool, thanks. [10:06] thanks to you :) [10:06] 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] right [10:06] okay [10:06] and armsoc uses the libGLES for acceleration if it is available [10:06] right [10:11] popey, downloaded and now in flashing process. I will inform you about result === Ursinha is now known as Ursinha-afk [10:18] P3T3: great [10:20] popey, fails, have black screen [10:21] bummer [10:21] can we try other build ? [10:21] I have Mar 1st working and MAr 11th non working [10:22] first one is build #8 and second one is #17 === Ursinha-afk is now known as Ursinha === chriadam is now known as chriadam|away === Ursinha is now known as Ursinha-afk [10:40] P3T3: sure [10:40] P3T3: i have 9, 10, 11, 13, 16 === SkavenXXI-[OFF] is now known as SkavenXXI [10:42] popey, 13 as it is happy number in China [10:42] P3T3, but it isn't in Western countries (I'm from China) [10:43] my house is 13. but the stupid builders were superstitious so they labelled it 12A ☹ [10:43] My house number is 13 too === Ursinha-afk is now known as Ursinha [10:44] P3T3: uploading, same place [10:45] popey, and you can delete 17 if you no longer need it [10:45] thanks === MacSlow is now known as MacSlow|lunch [11:05] Hi all. Does 3g data work on current build? [11:06] nope [11:06] :/ So still have to wait. Thanks. [11:07] but it is actively being worked on [11:15] ogra_: the phablet-armhf.zip is basically just a debootstrapped ubuntu + packages right? === Ursinha is now known as Ursinha-afk [11:34] popey, #13 is black too. So remains 9,10,11. Can you give me 10 please? 13 is to delete [11:35] bzoltan: is there any reason the 1.41 toolkit release is not in raring? [11:35] 0.1.41 [11:35] tsdgeos: we do not (can not ) release straight to Raring [11:35] tsdgeos: so there is a delay between our release and the distro release [11:35] ok [11:36] tsdgeos:I suggest to use the SDK Release PPA if you need the latest Toolkit [11:36] that's what i'm doing [11:36] but using ppa's makes me sick :D [11:39] hello all [11:44] hi [11:44] shadeslayer, well, it is ubuntu-minimal + android integration + ubuntu touch UI [11:45] right, I'm just trying to create my own zip [11:45] seems like there are some other files in there too META-INF/com/google/android/update-binary [11:45] yeah, android stuff [11:47] where does that come from? [11:48] aha [11:48] phablet-dev-bootstrap gens the zip [11:49] xnox: we can chat about that whenever you want [11:52] 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] xnox: indeed [11:53] jhodapp: are sensors api exercised via autopilot tests somehow at the moment? or since they are - well - sensors they need manual testing? [11:54] P3T3: ok [11:54] xnox: manual testing, although we should be able to add some simple unit tests to some of those functions [11:54] I have filed http://pad.lv/1167825 http://pad.lv/1167818 for pure api/abi stability monitoring. [11:54] Launchpad bug 1167825 in qtubuntu-sensors "needs reverse-dependency testing" [Undecided,New] [11:54] Launchpad bug 1167818 in qtubuntu-sensors "needs api stability tests" [Undecided,New] [11:54] xnox: though I'm sure someone could get creative in simulating the sensors [11:56] 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] 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] 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] xnox: right but that's a functional test...I'm talking more unit testing [11:59] 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] 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] jhodapp: would you be willing to write those? [12:01] xnox: I don't have anything specific in mind atm, but if I think of something I will certainly add it [12:01] xnox: a bug/blueprint entry [12:02] jhodapp: ok. I'll poke the code again once we get the raring/s images. [12:02] xnox: also know that I'm no longer the person actively working on that code [12:03] 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] jhodapp: hmm.... who became "goto person" about it? [12:04] P3T3: np [12:04] xnox: I'm not sure offhand, but I can find out for you if you like [12:04] 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] xnox: ok, np then === greyback is now known as greyback|lunch === MacSlow|lunch is now known as MacSlow [12:20] popey, downloading 10, thanks === Ursinha-afk is now known as Ursinha === LarrySteeze is now known as LarrySteeze|Away === _salem is now known as salem_ === Ursinha is now known as Ursinha-afk === greyback|lunch is now known as greyback === oreneeshy_ is now known as oreneeshy === Ursinha-afk is now known as Ursinha [13:07] popey, #10 fails. Remains #9, can you upload it? [13:07] sure [13:09] popey, 10 & 13 you can delete [13:10] done, thanks [13:11] me too === bzoltan1 is now known as bzoltan [13:15] Hi, may I ask if UT caters for phones with hardware buttons ? [13:17] the UI is designed to not require hardware buttons, but I think some ports have mapped them to certain functions [13:18] thank you pmcgowan I shall try to search for said 'ports' [13:18] id0_stupid_user, what phone do you use? [13:19] Try to find yours at https://wiki.ubuntu.com/Touch/Devices [13:19] I have Nokia N8 [13:19] is it possible to install ubuntu on NOkia n8 [13:19] Upender, whoa I don't think so. Someone needs to port Android to Nokia N8 first:P [13:20] smartboyhw: I have an old android tablet that I pushed generic ubuntu LTS armhf to. [13:20] okies..actully i am not happy with nokia belle any more [13:21] hence looking to chagne but no issue will check for any other update or possiblity in furthre [13:21] future [13:21] 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] Upender: cool ... My wife has an N8 - I need to repurpose that too ;) [13:23] N8 is symbian, good luck rooting it [13:23] :) [13:23] hmm [13:23] Upender: if you just hate belle there is a secret way to downgrade to S^3 === Ursinha is now known as Ursinha-afk [13:30] Good luck ladies and gentlemen [13:35] uh hi [13:36] when running adb root I get : adbd cannot run as root in production builds [13:36] causing phablet-flash to fail [13:36] any ideas? [13:37] P3T3: 9 is done [13:39] popey, thanks, going to test it [13:45] mmm [13:45] I'll have to root it? === Ursinha-afk is now known as Ursinha === dandrader is now known as dandrader|afk [13:49] xnox: you'll want to talk to ChickenCutlass about the sensors now, he's leading that charge [13:49] jhodapp ok, thanks. [13:50] xnox: np [13:51] popey, #9 works, it's buildstamp = arneb Sat, 02 Mar 2013 05:02:52 +0000 , manhattan-quantal-armhf-20130302-1 [13:53] P3T3: good luck finding what changed ⍨ [13:55] popey, is there any log with changes? === ckpringle_ is now known as ckpringle === Ursinha is now known as Ursinha-afk === dandrader|afk is now known as dandrader === Ursinha-afk is now known as Ursinha === t1mp_ is now known as t1mp [14:23] 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] 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] I see them using call-start, computer-symbolic etc..but I am unaware as to what other icons are available [14:24] ChickenCutlass is the owner of sensors in general, so he might know more [14:24] xnox: but we have the infra available already to run test apps at a real device already [14:24] kaleo: see nik90's question? Do we have a full list? [14:25] so we just need the proper plumbing [14:25] * ogra_ looks for his wrenches [14:25] rsalveti: ack. What about the test_* apps in platform-api? same story? [14:26] xnox: yup [14:26] they were just quick test apps to make sure hybris wasn't failing while doing the development mostly [14:26] as we're redesigning platform-api, I also believe it'll change quite a bit [14:31] popey: nik90: sorry there is no list yet [14:32] popey: nik90: moreover the list is different on the desktop and on touch right now [14:32] popey: nik90: we use ubuntu-mono-dark on the desktop and ubuntu-mobile on ubuntu touch [14:32] kaleo: oh ok ... then I'll wait until we get the icons officially for the touch [14:32] dpkg -L ubuntu-mono will give you the desktop ones [14:32] dpkg -L ubuntu-mobile will give you the touch ones [14:32] nik90: just hang on :) [14:34] kaleo: where do I find the ubuntu-mobile package? === francisco is now known as Guest35830 [14:47] intetesting [14:47] our calculator is mathematically correct [14:47] which means people will complain :D [14:48] well, now i did 12 * 8 and got 9696 [14:48] forget that mathematically correct part :D [14:49] tsdgeos: do you mean in the ubuntu-calculator-app? [14:49] nik90: whatever is shipped in the phone [14:49] i guess yes [14:52] tsdgeos: just tried it now...wierd [15:02] ogra_: once you're back, I'd like to talk :) === dandrader is now known as dandrader|lunch [15:02] nik90: it's part of the ubuntu-themes source package [15:03] nik90: which is or will be soon in raring [15:03] nik90: otherwise I think there is a PPA http://ppa.launchpad.net/phablet-team/desktop-deps/ubuntu/ [15:06] shadeslayer, i'm here [15:14] 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] or do we expect many bits already having fallen into place by then? [15:14] i hope the android builds will happen on cdimage by then [15:14] 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] kvarley, both technically work ... but the browser doesnt know about tabs yet for example ... so its not very comfortable as an enduser [15:16] 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] kvarley: depends on the device too, videos play on my Nexus 7, but sound doesn't [15:17] but a couple weeks ago, videos didn't play [15:18] so, progress! [15:18] ogra_: hey, so, I'm curious, the chroot that phablet-flash flashes, that contains android stuff and ubuntu chroot correct? [15:18] mhall119, just enable subtitles :) [15:18] ogra_: what if I don't want the android tools and just want a minimal ubuntu chroot ( debootstrap + ssh server ) [15:18] shadeslayer, it contains the ubuntu side of the platform api and libhybris [15:19] shadeslayer, you can do that but wont be able to use any graphical stuff i belive [15:19] oh, not even by using the methods we talked earlier? [15:19] you will need to talk to SurfaceFlinger soemhow [15:19] (the android display server) [15:20] shadeslayer, wait for Mir:P [15:20] no no, what if I don't want surfaceflinger and just want to use X? [15:20] or build your android in a way that it doesnt fire that up [15:20] ogra_: if I wanted to read a movie, I'd buy the book :P [15:20] smartboyhw: KWin upstream is not going to accept Mir integration :P [15:20] smartboyhw: Martin made that very clear [15:20] shadeslayer, I know (LOL) so that:P :P [15:20] mhall119, audiobooks ftw :) [15:21] okay, I thought you were serious ;) [15:21] (with subtitles indeed) [15:21] ogra_: unless you have to audio.... [15:21] do audio books have subtitles? [15:21] rsalveti, do you know something about compilation parameters of daily builds? [15:21] shadeslayer, I did watch the whole conversation. [15:21] lol, dunno [15:22] P3T3: sure [15:22] 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] 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] rsalveti, ok great [15:22] to see what we could do to improve the porting experience and such [15:22] shadeslayer, you should be able to ... try it :) [15:22] sounds great [15:23] right, now my actual question :D [15:23] oh, you did hide it behind smalltalk ! [15:23] rsalveti, today I have discovered that build from March 3rd causes my problem which leads in black screen [15:23] how do I switch out the zips? :P [15:23] dunno, why do you want zips ? [15:23] because I don't quite understand how the booting works here [15:23] I need to know something about changes between MArch 2nd and 3rd [15:23] oh [15:23] P3T3: hm, we didn't change any parameters back then [15:23] P3T3: which hardware? [15:24] HP Touchpad [15:24] so I can flash quantal-preinstalled-boot-armel+manta.img and then flash a rootfs to the /data ? [15:24] and it will all just work? [15:24] 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] you want a boot.img and put in an initrd that contains the ac100-tarball-installer bits [15:25] I see [15:25] then you can just use a rootfs tarball you prepare [15:25] might need some hacking but essentially thats the process i would use [15:25] okay, thanks :) [15:25] P3T3: I wonder if that is an incompatibility of the platform-api and the compat layer at hybris [15:25] I'll try and figure out how the AC100 does things [15:26] it might be related with the ubuntu rootfs you're using as well [15:26] rsalveti, shall I make it part of the community track? [15:26] shadeslayer, better look at the nexus7 codepath in there ... thats way simpler [15:26] the ac100 has a ton of checks etc that you dont really want [15:27] dholbach: yeah [15:27] sweet, on it [15:27] rsalveti, my hybris and platform-api are newest one [15:27] P3T3: weird, have the logs from logcat? [15:27] would be nice to compare the ones from the working and not working images as well [15:28] rsalveti, P3T3 is Petr Bláha on the ML btw :) [15:28] ogra_: thanks! [15:28] :-) [15:28] http://pastebin.com/ir3Gdk1K [15:28]