[02:18] <CimmerianX> hello all
[02:19] <CimmerianX> Can anyone tell me if the nexus 4 has any issues being detected on a phablet-flash -b ?
[02:20] <CimmerianX> mine shows as a 'unsupported device, autodetect dails device'
[02:21] <RobbyF> should work
[02:21] <RobbyF> I believe there is just the one model world wide
[02:22] <CimmerianX> yep - Model Nexus 4  Ver 4.2.2
[02:22] <CimmerianX> this one seems to be running  AOKP
[02:23] <RobbyF> shouldn't matter.
[02:23] <RobbyF> you can just flash via recovery
[02:24] <boydoy> hi! there i way i can change the OS of my android phone into Ubuntu Mobile?
[02:24] <CimmerianX> do you mean a manual install from here: https://wiki.ubuntu.com/Touch/Install
[02:25] <RobbyF> yup
[02:25] <RobbyF> just download, adb push to /sdcard/autodeploy.zip
[02:25] <RobbyF> I just did it as we speak :)
[02:25] <CimmerianX> ack.   it's being pushed to /sdcard/ now.
[02:25] <RobbyF> should work :)
[02:25] <RobbyF> boydoy, which android?
[02:26] <boydoy> im using o+ 8.52
[02:26] <boydoy> its that ok to change
[02:26] <RobbyF> no idea what that is, but check this ported list here: https://wiki.ubuntu.com/Touch/Devices
[02:26] <boydoy> and ubuntu they have also like google play
[02:27] <boydoy> i can download a free games
[02:27] <RobbyF> boydoy, not yet, the os is still in developer preview mode
[02:27] <RobbyF> about half a year from regular user interaction.
[02:27] <boydoy> ahh ok.. but if ever i try they have a way i can back to original OS?
[02:28] <RobbyF> I don't see why not
[02:28] <RobbyF> :)
[02:35] <CimmerianX> wow - how large is the armhf?
[02:35] <CimmerianX> still pushing.
[02:37] <RobbyF> takes me like 3-4 minutes
[02:37] <RobbyF> I did raring which is 523M
[02:43] <CimmerianX> still pushing.
[03:18] <CimmerianX> Robby - still here?
[03:19] <CimmerianX> I did the armhf push to /sdcard/autodeploy.zip and did the reboot recovery....   as per the wiki.
[03:20] <CimmerianX> I'm in the recovery project menu.  If I reboot, I go back to the AOKP android OS.    Is there a step I'm missing?
[03:20] <CimmerianX> oh duh/....
[03:26] <CimmerianX> that did it - It's loaded.
[03:27] <CimmerianX> that;s a big flash...
[03:27] <CimmerianX> hmmm....   i have the wallpaper - but phone is unresponsive....
[03:28] <mhall119> CimmerianX: swipe from the left or right edge in to the center
[03:29] <CimmerianX> oic
[03:29] <CimmerianX> ALL the way to the center
[03:31] <mhall119> well, no, but "to the center" it easier that "a little way in from the left for the launcher, follow through for the Apps lens, swipe from the right a little to peak at the next window, follow through to switch to it"
[05:15] <DrCode> hi all
[05:15] <DrCode> dose ubuntu-tuch have support for samsung s3?
[05:48] <dijzon> hi ppl
[05:48] <dijzon> i have a droid razer m ,and i been working on getting full ubuntu installed on it but i need some help
[05:50] <DrCode> dose ubuntu touch support in samsung s3?
[05:50] <dijzon> so is there anyone that can help
[05:50] <dijzon> yes it dose
[05:50] <dijzon> just need to get the driver stacks for ur hardware
[05:50] <dijzon> stacks cdma gsm wifi cpu gpu and etc
[05:53] <dijzon> drcode what arm do u have
[05:53] <dijzon> v6-v7?
[05:59] <dijzon> so the droid razer m running ubuntu ,but i wanna get the full ubuntu on my test phone
[06:17] <Mirv> lool: hate to ask, but I don't find a trace of the new ubuntu-ui-toolkit upload, in queues or elsewhere in LP
[06:30] <didrocks> Mirv: it's in the unapproved queue
[06:30] <didrocks> Mirv: https://launchpad.net/ubuntu/raring/+queue?queue_state=1&queue_text=
[06:31] <didrocks> Mirv: you probably need to talk on #ubuntu-release to get it in
[06:31] <Mirv> didrocks: oh, funny, I thought I checked that but apparently I was in a different section
[06:32] <didrocks> Mirv: maybe you check NEW?
[06:32] <Mirv> probably..
[06:38] <Mirv> didrocks: that getting raring is btw the only remaining part I know of required to have the different aspects of the documentation being wrong fixed
[06:38] <Mirv> in both web and archives
[06:38] <didrocks> Mirv: oh, even the tutorial? excellent!
[06:39] <Mirv> didrocks: I'm not sure if dpm has updated everything yet, but at least from my point of view the package/trunk is fixed and the other things are on the move by michael and david
[06:39] <didrocks> ok
[06:39] <didrocks> great ;)
[06:40] <dpm> didrocks, Mirv, on it, sorry for the delay. The documentation is up to date, the tutorial I'm working on
[06:41] <Mirv> dpm: great! the important thing IMHO was identifying what things needed to be fixed and where.
[06:44] <dholbach> good morning
[07:37] <mpt> mhall119, lol
[08:15] <nik90> fginther: is there a way to know if the jenkins autolanding system is back online?
[08:20] <sil2100> didrocks: so, a follow-up to the topic of integration tests for qtubuntu-camera, as I had a quick chat with gusch
[08:21] <sil2100> didrocks: right now there are no real plans for introducing explicit integration tests for that package, but what we could theoretically do is to install and execute camera-app integration tests for qtubuntu-camera
[08:21] <sil2100> As those are practically doing the integration testing
[08:21] <didrocks> sil2100: so similar to what we've done for indicators up to now?
[08:23] <didrocks> sil2100: they are both on the same stack already, so integration tests will be run and everything will be in or rejected :)
[08:25] <didrocks> sil2100: gallery-app FTBFS in the daily-build-next ppa, so not integration tests will be run, mind having a look?
[08:36] <sil2100> ACK
[08:39] <oSoMoN> tmoenicke: hey Thomas, would you mind reviewing/testing https://code.launchpad.net/~osomon/webbrowser-app/addressbar-behind-osk/+merge/159382 ?
[08:40] <tmoenicke> oSoMoN: checking
[08:40] <oSoMoN> thx
[08:42] <tmoenicke> oSoMoN: great thx
[08:42] <tmoenicke> oSoMoN: is it invisible?
[08:43] <oSoMoN> tmoenicke: I was hoping you could test on your device(s), but yes, in theory the address bar is not visible below the osk anymore
[08:43] <tmoenicke> oSoMoN: i will test it
[08:44] <tmoenicke> thx
[08:48] <sil2100> didrocks: hm, it seems that python -c "from distutils.sysconfig import get_python_lib; print get_python_lib()" returns none in the PPA during the gallery-app build?
[08:49] <sil2100> didrocks: python should be already on the chroot, right?
[08:49] <sil2100> Maybe we need a dep
[08:50] <didrocks> sil2100: no, it's not part of the chroot
[08:50] <didrocks> contrarly to CI that adds some deps for nothing unfortunately :/
[08:51] <sil2100> So ok, I think the dep needs to be added ;p
[08:51] <didrocks> sil2100: yep, nice catch! :)
[08:51] <didrocks> sil2100: btw, how did you spot it from the logs? /me curious
[08:52] <sil2100> didrocks: I checked that it said no DESTINATION is given, while the DESTINATION is ${PYTHON_PACKAGE_DIR} in this case, which is fetch through execute_process and the python command in the CMakeLists.txt file
[08:53] <didrocks> sil2100: interesting, nice work :)
[08:55] <sil2100> https://code.launchpad.net/~sil2100/gallery-app/build_dep_on_python/+merge/159570
[08:55] <sil2100> brb in a moment
[09:52] <didrocks> sil2100: I'm rerunning gallery-app and the app stack build
[10:10] <DrCode> hi all
[10:10] <DrCode> any support for samsung galaxy s3 or only nexus?
[10:11] <nik90> !devices | DrCide
[10:11] <nik90> DrCode: check the link to see if your device is supported
[10:11] <DrCode> I realylike to test ubuntu-tuch
[10:12] <DrCode> dose ubuntu0tuch come with all pkgs in ubuntu
[10:12] <nik90> DrCode: The S3 international is not supported...but there are version for verizon I think
[10:12] <DrCode> like aircrack-ng?
[10:12] <DrCode> I see
[10:12] <nik90> DrCode: not sure.
[10:12] <DrCode> what I love in s3 is that I can use microsd
[10:12] <DrCode> didn't found it in nexus
[10:13] <nik90> DrCode: I have a S3 international as well, but not supported yet :(
[10:13] <DrCode> when a stable release will be of ubuntu-tauch?
[10:13] <DrCode> I see
[10:13] <DrCode> I realy love this mobile
[10:13] <nik90> DrCode: the beta should be available this october hopefully...
[10:14] <DrCode> wow, nice
[10:14] <nik90> DrCode: I think they are targetting first quarter of 2014 for final release
[10:14] <DrCode> it will be very intersting
[10:14] <nik90> DrCode: You can already try out some core apps like calendar, clock, calculator, facebook etc on your computer
[10:14] <DrCode> dose thay plan to support most devices?
[10:15] <DrCode> or only spcifics?
[10:15] <nik90> Officially canonical are supporting the nexus devices, but the community or any one can port to any device you want.
[10:15] <DrCode> ok
[10:16] <popey> mardy: you about?
[10:16] <Neo> excuse
[10:17] <Guest13130> does ubuntu touch support restoring your old android ?
[10:17] <Guest13130> on HTC Desire hd or htc one x
[10:17] <Guest13130> ?
[10:30] <sil2100> didrocks: hmmm, my branch with the explicit list of packages was merged, right? Since I see that the hud stack generic job failed because of extra packages wanting to be installed
[10:31] <sil2100> Was all correctly deployed?
[10:32] <didrocks> sil2100: yeah, it's in and deployed
[10:32] <didrocks> sil2100: the stacks are running with those now
[11:11] <sil2100> didrocks: in what moment is the packages list used? You once said it's being used as a comparison table - that if an extra package is installed and not in the packages list, the warning gets emitted, right?
[11:12] <didrocks> sil2100: indeed, it's when we install the machine which will run autopilot
[11:12] <sil2100> didrocks: is there an easy way to check what 'packages' were in the config during a generic build that has been fired?
[11:13] <sil2100> In the packages parameter?
[11:13] <sil2100> Since it looks as if it was ignoring all the packages we put there recently :
[11:13] <sil2100> :|
[11:13] <didrocks> sil2100: what are you looking at exactly?
[11:15] <sil2100> didrocks: http://10.97.0.1:8080/job/ps-generic-autopilot-release-testing/98/label=autopilot-ati/console
[11:16] <didrocks> sil2100: yeah, I told you to discare those and looking at what we are going to run :)
[11:16] <didrocks> sil2100: so run 102 for instance
[11:16] <didrocks> I redeployed this morning
[11:16] <sil2100> Ah, so there's no up-to-date results right now ;p?
[11:17] <sil2100> I think I misunderstood and thought that since you re-deployed in the morning, those should he the 'latest'
[11:17] <sil2100> Ok, so I go back to my HUD-hunting then
[11:21] <didrocks> sil2100: not yet :)
[11:21] <didrocks> sil2100: yep ;)
[11:25] <sil2100> hmm
[11:25]  * sil2100 wonders how we got that test passing for armhf in HUD in the past
[11:29] <didrocks> sil2100: was it passing when we were building with the platform api?
[11:34] <sil2100> didrocks: not sure now, maybe you're right and it never did - need to poke the platform-api people, since I think I know what's wrong but need to check with them on if I'm right
[11:34] <didrocks> ok :)
[12:00] <sil2100> ricmm: ping
[12:16] <ogra_> rsalveti, i managed to drop another 700M (unpacked) from the tarball
[12:29] <Taiten987> trying to build /ubuntu in another AOSP here, but keep receiving failure
[12:29] <Taiten987> checked files under /build but I can't really find what did I missed
[12:31] <Taiten987> here is the log http://pastebin.ubuntu.com/5718645/, please advice if you have any idea :(
[12:35] <ogra_> janimo, lol ... see above ... i removed most of the superfluous toolchains  in my testing
[12:35] <ogra_> funny that we always sectretly look at the same stuff without the other knowing
[12:40] <pmcgowan> hey Taiten987 how are you
[12:40] <Taiten987> pmcgowan, working on the patches :)
[12:40] <Taiten987> pmcgowan, a bit stuck here
[12:41] <pmcgowan> if rsalveti is around he may be able to help
[12:41] <Taiten987> pmcgowan, I just figured out it was surfaceflinger API changes
[12:41] <Taiten987> pmcgowan, yes, I had pinged him
[12:41] <Taiten987> pmcgowan, hopefully he can see it
[12:41] <pmcgowan> Taiten987: can you use the same version of AOSP? did you see my email?
[12:42] <Taiten987> pmcgowan, yes I do
[12:46] <janimo> ogra_, heh :)
[12:47] <ogra_> i just answered your mail
[12:47] <janimo> not usre where' above to look, will check the email
[12:47] <ogra_> we want to actually start building the android stuff on the package builders
[12:48] <ogra_> to do that the source tree needs quite some cleanup though ... so you dont have to upload a 1.4G tarball for every change
[12:48] <janimo> ogra_, the problem with removing some of all prebuilts is that some  kernels only build with a specific one
[12:48] <ogra_> http://phablet.ubuntu.com/export/
[12:48] <janimo> so mako kernel did not build for me with raring gcc a while ago
[12:48] <janimo> ogra_, also I tried building for a huawei device and that to only built with an inlcuded 4.6
[12:48] <ogra_> well, rsalveti added a patch to actually use the packaged binary instaed
[12:48] <ogra_> so you dont need to build the kernel at all
[12:49] <janimo> if we expect people to contribute ubuntu touch ports they may have an additional hurdle if they need to find a toolchain
[12:49] <ogra_> for porters we will have to keep the full tree around
[12:49] <janimo> although not sure how we could move stuff to cdimage and support many crazy toolchains
[12:49] <ogra_> but for building for something supported we want a cut down set
[12:49] <janimo> so I hope we can make all work with stock gcc
[12:49] <pmcgowan> janimo: thats a valid concner
[12:49] <pmcgowan> concern
[12:50] <ogra_> well, you need to shuffle a lot ... gcc, and gcc-cross need to work
[12:50] <janimo> ogra_, well we only have packaged kernels  for nexus 7
[12:50] <ogra_> but since yesterdays desaster with image builds we decided we want a very small tree and use the package builders for rolling images
[12:50] <janimo> a lot of the rest of devices are either 3rd patry hacked up OEM kernels or too new SoCs we do not package yet
[12:50] <janimo> hopefully multiARM kernels will come to the rescue soooooon
[12:51] <sil2100> didrocks: the phone-app with the changes made works like a charm on my desktop
[12:51]  * ogra_ tried to implement image building on the livefs builder ... that resulted in the machine to die for a full day 
[12:51] <sil2100> didrocks: there's one merge that needs to go in though
[12:51] <didrocks> sil2100: \o/ excellent news ;)
[12:51] <didrocks> sil2100: ah?
[12:51] <ogra_> luvefs builders arent designed for cross compiling :P
[12:51] <ogra_> *livefs
[12:52] <ogra_> janimo, we also plan to package the android bionic toolchain for cross building
[12:52] <ogra_> thats a long term plan though
[12:52] <ogra_> in the short term using the packaged toolchains (or packaging linaros android cross chain) is the plan
[12:53] <sil2100> didrocks: https://code.launchpad.net/~mterry/phone-app/hud1/+merge/158201 <- waiting for CI to finish the re-build
[12:55] <didrocks> sil2100: mediumtests failed
[12:55] <Oranger> mhall119: Hey ! My branch seam to be clean now. I want to work on the package but can't do it still your branch "package-fixes" isn't merged
[12:55] <Oranger> *seem
[12:57] <sil2100> eeek, all of them!
[12:57] <sil2100> hmmm
[12:57] <sil2100> Strange, since HUD 1.0 is in the daily PPA already
[12:58] <ogra_> use the large tests then, not the mediumtests :P
[12:58] <sil2100> didrocks: what PPA is CI using when running the autopilot tests, do you know by any chance?
[12:59] <didrocks> sil2100: I think they start using your daily-build-next ppa, but better to check with fghinter
[12:59] <didrocks> ogra_: tsss :p
[13:00] <Guest87519> I would like to know if it is possible to contribute as a tester, I mean not only for bugs but also to describe things that can be improve (for example, I suggest to blcok the switch between apps from the top and the bottom corner of the right part of the screen)
[13:16] <sil2100> ;)
[13:22] <fginther> nik90, the best way to know if jenkins is back online is to check the url: http://91.189.93.125:8080/
[13:23] <fginther> nik90, The server is online at the moment (Hooray!) but it's a little more work to setup the jobs for each project.
[13:30] <sil2100> \o/
[13:39] <awe_> lool, I don't see anyone from the indicator/settings team?
[13:41] <mzanetti> cyphermox: ping
[13:43] <Oranger> mhall119: ping
[13:45] <cyphermox> mzanetti: pong
[13:45] <mzanetti> cyphermox: hi
[13:45] <mzanetti> cyphermox: regarding https://code.launchpad.net/~mzanetti/autopilot-qt/add-tests/+merge/153695
[13:45] <mzanetti> cyphermox: I guess its now or never
[13:46] <cyphermox> rock on!
[13:46] <mhall119> Oranger: pong
[13:47] <mzanetti> cyphermox: its still on Needs Fixing from you
[13:47] <Oranger> mhall119: 1 point
[13:47] <mzanetti> you mind approving?
[13:47] <Oranger> mhall119: Hum sorry ^^
[13:47] <Oranger> mhall119: Hum so I did what you ask me yesterday, the directory is clean
[13:47] <mhall119> Oranger: checking it out now, thanks
[13:47] <Oranger> mhall119: And I want to finish the package but actually I can't until your branch isn't marge
[13:47] <Oranger> *merge
[13:48] <cyphermox> mzanetti: done.
[13:48] <mzanetti> cyphermox: thanks a bunch
[13:49] <cyphermox> note that this won't land in raring as-is; you'd need to file it against lp:autopilot-qt/0.8
[13:49] <cyphermox> that said, does it need to be in raring?
[13:49] <cyphermox> actually, ignore me
[13:49] <mzanetti> cyphermox: no... just need to get it merged because other work that requires adding more tests is pending
[13:49] <cyphermox> you got the FFE ack anyway, so might as well if we have the chance
[13:50] <cyphermox> once that gets merged I'll re-run the qa stack
[13:50] <cyphermox> could you file it against the 0.8 branch too?
[13:51] <mhall119> Oranger: can you review my package-fixes branch?
[13:51] <Oranger> mhall119: Yes I do it now
[13:51] <mhall119> thanks
[13:54] <mzanetti> cyphermox: https://code.launchpad.net/~mzanetti/autopilot-qt/add-tests/+merge/159636
[13:55] <mhall119> Oranger: your branch is approved
[13:55] <Oranger> mhall119: Thanks
[13:55] <mhall119> fginther: so is jenkins back on the job, or still recovering?
[13:58] <fginther> mhall119, It looks to be alive. I'm checking to make sure the build tools are in place before I deploy the jobs
[13:59] <mhall119> thanks fginther
[14:00] <rsalveti> sergiusens: you noticed already but I pushed your stuff yesterday
[14:01] <rsalveti> and sent the kernel one after doing the 4 builds and also producing a test grouper one based on the ubuntu package as well
[14:01] <Oranger> mhall119: I approved
[14:03] <mhall119> thanks Oranger
[14:08] <fginther> mhall119, I've pinged martin about the jenkins server. There is still a little more work to do that I can't complete.
[14:08] <dpm> fginther, thanks for bringing Jenkins back to life. While you're at it, and if there isn't one already, would it be possible to add a job to run the autopilot tests in the core apps branches?
[14:10] <fginther> dpm, the test infrastructure is currently insufficient to do this, but I'll discuss this with my team to see if we can get it on the roadmap
[14:10] <sergiusens> rsalveti: yes, I am reviewing now... and I did check as I mentioned it in the gcc email thread :-)
[14:10] <sergiusens> rsalveti: I can only test build the mako and grouper, those are the two devices I don't have ;-)
[14:10]  * sergiusens just noticed he was marked away
[14:11] <rsalveti> sergiusens: that's fine, we can request someone else to test mako if needed
[14:11] <sergiusens> rsalveti: I will review, I trust you did the testing I will review
[14:11] <sergiusens> rsalveti: who has a mako? I can build and send
[14:11] <sergiusens> oh plars  :-)
[14:12]  * sergiusens thinks he might be abusing plars' devices
[14:12] <plars> yesss? :)
[14:12] <dpm> thanks a lot fginther. Just asking to have some more context: why is the test infrastructure currently insufficient?  Is e.g. the number of jobs that the jenkins instance limited and we've reached the limit? Or is it related to autopilot not playing well with jenkins... ?
[14:13] <dpm> sorry, I meant "that the jenkins instance can run"
[14:14] <sergiusens> plars: give me a couple and I'll create a mako image... still reviewing the code ;-)
[14:14] <plars> sergiusens: sounds good
[14:15] <didrocks> mterry: FYI, sil2100 did some progress on touch today, and we are almost being able to build and test everything. Do you mind checking with him if you have time for finishing up the autopilot things?
[14:16] <mterry> sil2100, talk to me!  :)
[14:16] <fginther> dpm, the main reason is that autopilot tests can't run inside a pbuilder, they need a real desktop environment. The likely solution is to do this in a dedicated VM, which isn't too difficult, but there may be some resource constraints that I'm not aware of.
[14:17] <sergiusens> rsalveti: I take that in 2 weeks time that raring in the BoardConfig will change to slug?
[14:17] <sil2100> !
[14:18] <benkaiser> anyone got an ETA for GSM in Ubuntu Touch (e.g. data)
[14:18] <sil2100> mterry, didrocks: so... I had a talk with fginther, and soon we should be able to get both the phone-app HUD version bump and qtvideo-node arches merges in, those are required for us to carry on
[14:18] <dpm> thanks fginther, understood
[14:18] <rsalveti> sergiusens: yeah
[14:18] <sil2100> I'm trying to figure out now with the help of rsalveti on how to deal with the armhf test failure on HUD, as it's a problem with android-specific bits
[14:20] <mterry> sil2100, yay
[14:20] <benkaiser> anyone? gsm ETA?
[14:43] <ogra_> sergiusens, so i looked into removing the oggs and mp4's, seems there are a bunch of changes needed for the build system to get rid of them (and i'm also not sure if we use something like i.e. the camera sound from teh android side when taking pics)
[14:43] <sergiusens> ogra_: that's already done
[14:43] <sergiusens> ogra_: update and see
[14:43] <ogra_> oh
[14:43] <ogra_> well, i'm playing with the tarball here :)
[14:44] <ogra_> but havent pulled todays yet
[14:44] <sergiusens> ogra_: or just look at http://phablet.ubuntu.com/gitweb?p=CyanogenMod/android_frameworks_base.git;a=shortlog;h=refs/heads/phablet-10.1
[14:44]  * ogra_ hugs sergiusens 
[14:44] <sergiusens> ogra_: also made the changes to the makefiles as necessary in vendor/cm
[14:44] <ogra_> yay
[14:45] <ogra_> so now the toolchains and kernels and we should have a sweet 500M tarball :)
[14:45] <sergiusens> ogra_: after getting this kernel review in, I'll be looking into making it smaller
[14:45] <ogra_> or even less
[14:45] <sergiusens> yes
[14:45] <ogra_> yeah, sadly the gcc-cross one doesnt work
[14:45] <ogra_> not sure if slangasek got it solved
[14:45] <sergiusens> ogra_: this would of been done sooner if we ever had this git repo in place for more than 2 months :-)
[14:46] <ogra_> no hurry
[14:46] <MalMen> anyone can tellme if that tablet support touch http://www.efox.com.pt/envios-da-europa-vido-n101-ii-android-4-1-rk3066-dual-core-10-1-1280-x-800-ips-32gb-3g-wifimara-dupla-tablet-pc-p-300356 ?
[14:46] <MalMen> thank you
[14:46] <ogra_> after all i'm happy  that i can skip raring :)
[14:46] <ogra_> and concentrate fully on S
[14:46] <ogra_> (for the image builds)
[14:47] <wilee-nilee> MalMen, your link has a bad wot popup
[14:47] <WebVisitor-3> Hello! Sorry  for the interruption. I bought a Vaio T13 touchscreen ultrabook hoping that Windows 8 is a usable os. This isn't so, I found Windows 8 very user unfriendly and slow OS. So I installed Ubuntu 13.04 on my ultrabook. The problem is that the multitouch is not supported. I mean I cant click, drag with the touchscreen. I read that I need to install some kind of touchscreen driver. Could you please explain where do
[14:48] <MalMen> wilee-nilee what specs i can give you to know if is compatible ?
[14:48] <wilee-nilee> MalMen, none I'm just on the channel.
[14:51] <rsalveti> ogra_: the reduced toolchain and pre-built set should happen later today as well
[14:52] <rsalveti> ogra_: today's tarball is also xz
[14:52] <rsalveti> with -6e
[14:52] <ogra_> rsalveti, yup seen :)
[14:52] <rsalveti> takes quite a while to generate it hehe :-)
[14:52] <ogra_> only 1.4G
[14:52] <rsalveti> yeah, step by step
[14:52] <ogra_> yeah
[14:52] <ogra_> 500M or so in the end would be good
[14:54] <ogra_> rsalveti, did you talk to slangasek ? i didnt see him comment anything after the linker error
[14:54] <rsalveti> ogra_: nop, and as I said, I'm not convinced we should remove all pre-built toolchains at this point yet
[14:54] <rsalveti> so I'll just remove the stuff we're not using at least
[14:55] <ogra_> rsalveti, if we can se should ... from the tarball ... i would say lets keep the git tree completely untouched
[14:55] <ogra_> s/se/we/
[14:55] <sergiusens> rsalveti: any reason why cm.dependencies for mako still lists the kernel?
[14:56] <rsalveti> sergiusens: the kernel source is needed still for the headers
[14:56] <ogra_> the tarball will be used for autobuilds and we only need the bits for building the supported sets ...
[14:56] <rsalveti> sergiusens: it's used by some hardware/qcom components
[14:56] <ogra_> the git tree should have as much as possible for porters
[14:56] <rsalveti> ogra_: well, we can create a separated tarball with the toolchain once we get a working toolchain from the archive
[14:56] <sergiusens> rsalveti: let's keep it for now and figure out how to get just the headers in
[14:56] <ogra_> rsalveti, thats what i mean ;)
[14:57] <sergiusens> iirc aosp doesn't install the kernel headers by default
[14:57] <rsalveti> sergiusens: hm, iirc this qcom component is the same from aosp
[14:57] <rsalveti> might be something cm specific though
[14:57] <ogra_> we have a headers package as well :)
[14:57] <rsalveti> but yeah, to be investigated
[14:57] <rsalveti> sure
[14:57] <sergiusens> rsalveti: and we do have external/kernel_headers as well
[14:57] <rsalveti> but I believe these headers are mako specific
[14:58] <rsalveti> we might try to reuse the headers available from the kernel package as well
[14:58] <sergiusens> rsalveti: typo in the previous comment, aosp doesn't install kernel sources by default
[14:58] <rsalveti> will see if I can get something to work based on that later today
[14:58] <sergiusens> rsalveti: I won't block the patch in any case, just wondering what the result was of the conversation from yesterday :-)
[14:59] <rsalveti> sergiusens: right, yeah, this will follow, just wanted to get something that works first
[15:00] <rsalveti> ogra_: problem is that if it's indeed mako specific, it might not be available at the headers package
[15:00] <rsalveti> had similar issues with panda in the past
[15:00] <rsalveti> that's why I decided to investigate this later :-)
[15:00] <ogra_> ah
[15:00] <ogra_> well, no hurry :)
[15:01] <ogra_> (you two seem to do everything *right now* .... we're not on a race :)
[15:20] <crix> hello?
[15:24] <sergiusens> gusch: saw your updates to the bug... I recall the issue and a workaround jhodapp made to get it going (I'm pretty sure it was him). But yeah, the crash has been there for some time.... :-/
[15:25] <sergiusens> rsalveti: code looks good, building now (had to wait for meeting to end)
[15:25] <rsalveti> sergiusens: sure
[15:26] <gusch> sergiusens: the crash is there since the beginning, but the side effect of the flipped preview occured somewhen after the MWC demo image
[15:27] <sergiusens> gusch: yup, which brings up the question if we should focus on the crash instead
[15:29] <gusch> sergiusens: that's what I do now ;)
[15:29] <slangasek> ogra_: I got past the linker error (just needed to add -fuse-ld=gold in the right place), then ran into problems because of libgcc references - which is kind of what I was expecting to find.  We need to build an -> armel cross-compiler to target android specifically
[15:29] <slangasek> ogra_, rsalveti
[15:29] <ogra_> yeah
[15:29] <slangasek> ogra_, rsalveti: and at least for upload to the archive, we would need to solve the use of prebuilt compilers... as distributing those without source is a GPL violation
[15:30] <rsalveti> right
[15:30] <ogra_> i doubt we need to build it ... since linaro has one :)
[15:30] <slangasek> yes we do.
[15:30] <ogra_> ah, we cant use the linaro one ?
[15:30] <rsalveti> we can probably use if we grab the sources used to built it
[15:30] <rsalveti> *build
[15:30] <ogra_> right
[15:31] <rsalveti> but yeah, at the archive it'd be better to use our own toolchain
[15:42] <slangasek> rsalveti: given that we are already building cross-toolchains in the archive for other targets, and we track the Linaro patches for the arm builds, we should build the android toolchain the same way rather than introducing a parallel toolchain source
[15:43] <jhodapp> sergiusens: yeah, I was helping gusch figure out how to use gdb on the android side
[15:43] <rsalveti> slangasek: sure, no question about that
[15:43] <rsalveti> just saying that it's doable to use the prebuilt one if really needed
[15:43] <rsalveti> just need to find the sources
[15:44] <rsalveti> slangasek: who can be allocated to do that work?
[15:44] <slangasek> well, if we're putting it in the archive we also need to *build* the toolchain, not use the prebuilt
[15:44] <slangasek> anyway
[15:45] <rsalveti> sure, it'll just force ogra_ to wait until the toolchain is in place
[15:45] <ogra_> as i said, i'm not in a hurry
[15:45] <ogra_> lets discuss it at the sprint and do proper planning
[15:46] <rsalveti> sure, we'd need to get someone to work on this
[15:46] <ogra_> we wont start raring builds based on that right now ... so it is S material
[15:46] <rsalveti> yup
[15:46] <rsalveti> but it's a high prio to be able to spin builds based o S, right?
[15:46] <ogra_> i personally would prefer if doko could do it, everyone else will need double the time
[15:46] <rsalveti> at least via cdimage
[15:46] <ogra_> but i dont know how heavily booked he is
[15:47] <ogra_> rsalveti, right, but even in S we can live with the jenkins builds in the beginning
[15:47] <ogra_> i expect the S builds to be bumpy in the beginning anyway
[15:47] <Oranger> mhall119: You don't do something in particular for core apps to merge branches than "merge + commit + push" ?
[15:47] <rsalveti> ogra_: right, that's why I said if we want to build them at cdimage
[15:47] <ogra_> doesnt make them less bumpy :)
[15:48] <ogra_> we'll have to keep raring building for a while in parallel if we want usable images ... important is that by S release we will not have two parallel builds anymore but can smoothly transition to T this time
[15:49] <ogra_> thats my major target ...
[15:50] <ogra_> while i want S builds as early as possible they dont need to be in place on day one imho
[15:50] <ogra_> (would be a nice to have ... but i have no illusions here)
[15:51] <sergiusens> plars: http://people.canonical.com/~sergiusens/cm-10.1-20130418-UNOFFICIAL-mako.zip
[15:52] <slangasek> rsalveti: I need to talk to doko yet about the cross-toolchain requirements and when we can have this done; if you have anyone on your team who can help doko identify the necessary configure arguments for gcc, that will probably let us get it done faster
[15:52] <rsalveti> plars: got a mako as well?
[15:52] <rsalveti> plars: just to know in case I need someone else to help me validating stuff
[15:53] <plars> rsalveti: I do... I just realized something on it though, it's dead again
[15:53] <rsalveti> plars: :-(
[15:53] <rsalveti> plars: does it require you to remove the battery as well?
[15:53] <plars> rsalveti: Its odd, I can leave my galaxy nexus sitting without it being plugged in for a long time and nothing happens, but it seems like the mako dies quicker
[15:53] <plars> rsalveti: not so far
[15:53] <rsalveti> slangasek: right, that's fine, linaro produces a build script which is public
[15:54] <plars> rsalveti: need to take a look at that, could be that I had wifi enabled on one and not the other
[15:54] <rsalveti> might need a android specific sysroot, need to check that
[15:54] <plars> rsalveti, sergiusens: let me charge it for 10-15 min then I'll pull down that build and try it
[15:54] <rsalveti> plars: cool, thanks
[15:55] <plars> sergiusens: just use that one with today's rootfs?
[15:55] <plars> sergiusens: what was included in this? what was it intended to fix?
[15:56] <sergiusens> plars: oh, left a sentence incomplete
[15:56] <sergiusens> plars: it's using a packaged kernel instead of the one from the android tree for mako
[15:57] <sergiusens> plars: packaged by the kernel team
[15:57] <rsalveti> aka ubuntu kernel
[15:57] <slangasek> rsalveti: can you point me to that build script? :)
[15:57] <plars> sergiusens: ah, cool
[15:57] <ogra_> slangasek, the other issue seems to be that the CM kernels seem to not get along with gcc > 4.6 ... we will need the 4.6 in the tree still for porters
[15:57] <rsalveti> slangasek: yup, looking into it
[15:57] <rsalveti> ogra_: that's fine, we can produce different tarballs
[15:57] <ogra_> (not for what we upload to the archive eventually indeed)
[15:57] <slangasek> ogra_: the kernel team is already building the kernels; we should not be building them as part of the "android" source package, porters should be getting that elsewhere
[15:58] <ogra_> slangasek, but porters do
[15:58] <ogra_> so we need that for the community in the git tree still
[15:58] <slangasek> ogra_: completely irrelevant to the source package question
[15:58] <ogra_> not in the exported tarballs
[15:58] <ogra_> just a note :)
[15:59] <sergiusens> plars: I leave wifi and 2g network on all the time on the maguro and it lasts at least 2 days (less with screen on)
[16:00] <rsalveti> slangasek: http://android.git.linaro.org/gitweb?p=toolchain/build.git;a=tree
[16:00] <sergiusens> ogra_: they can add it to their cm.dependencies and we could remove it with no issues
[16:00] <sergiusens> talking about gcc
[16:00] <ogra_> sergiusens, ohhh ... good idea !
[16:01]  * ogra_ didnt think about that
[16:01] <rsalveti> slangasek: seems everything is there
[16:01] <mhall119> Oranger: usually Jenkins will automatically merge approved merge proposals into the project's trunk branch for the Core Apps
[16:01] <rsalveti> sergiusens: yeah, the toolchain will still be available at phablet
[16:02] <rsalveti> and we can spin a separated tarball with them like ogra_ said
[16:02] <rsalveti> then we're all good
[16:02] <ogra_> yeah
[16:02] <Oranger> mhall119: Oh ok, Jenkins is very usefull... when he is alive :p
[16:02] <mhall119> yeah, he's been under the weather recently :)
[16:03] <Oranger> mhall119: Do you know when he will come back ?
[16:03] <rsalveti> http://android.git.linaro.org/gitweb?p=toolchain/build.git;a=blob;f=README; is also quite informative
[16:03] <mhall119> Oranger: fginther might now, he may be back now and just churning through his backlog
[16:04] <Oranger> mhall119: ok, thanks :)
[16:05] <fginther> Oranger, sorry. the server is back up and running, but there is some additional setup that needs to be done. I've pinged someone to help me. Sorry for the inconvenience.
[16:06] <rsalveti> sergiusens: I'm +1 regarding the latest patch from janimo
[16:07] <Oranger> fginther: No it's good ! Thanks you for working hard on it ! ;) Take all the time you need !
[16:07] <rsalveti> sergiusens: let me know if you want me to apply it
[16:16] <shadeslayer> ChickenCutlass: hahaha, if I try to boot android with a custom kernel with VT and FRAMEBUFFER_CONSOLE support, it bootloops
[16:17] <shadeslayer> ogra_: ^^
[16:17] <shadeslayer> so fbcon is just plain broken
[16:19] <rsalveti> yeah, seems a common issue with android based kernels
[16:19]  * rsalveti bbl
[16:20] <shadeslayer> hehe
[16:21] <ChickenCutlass> shadeslayer: interesting.  I have it now where it boots then keeps rebooting
[16:21] <ChickenCutlass> shadeslayer: same as you
[16:22] <shadeslayer> yeah it's a bit weird
[16:23] <shadeslayer> ChickenCutlass: but you can control the brightness via the initrd right
[16:27] <ChickenCutlass> shadeslayer: yes
[16:28] <shadeslayer> well
[16:28] <shadeslayer> I'm kind of out of ideas since fbcon doesn't even work with android
[16:28] <shadeslayer> clearly enabling fbcon here is an issue
[16:29] <ogra_> well, you will need a working framebuffer for your Xorg ...  the console is just for getting there
[16:30] <shadeslayer> true
[16:30] <ogra_> i still dont get why g_serial doesnt work for you though ... fbcon is often differing by device ... gadget support shouldnt
[16:30] <shadeslayer> hmm, I'll try with android
[16:30] <shadeslayer> if g_serial works
[16:31] <ogra_> note that it kills adb ...
[16:31] <shadeslayer> yeah that's fine
[16:31] <ogra_> since that uses the gadget driver too
[16:31] <shadeslayer> I know :)
[16:31] <ogra_> if g_serial doesnt work you can also try g_composite as alternative ... i have found devices wheer that one works better
[16:31] <ogra_> (has additional USB net support)
[16:32] <shadeslayer> oh
[16:32] <shadeslayer> hmm, will try
[16:38] <shadeslayer> ogra_: booted android after enabling g_serial, nothing
[16:39] <ogra_> with proper console= args on the kernel cmdline ?
[16:39] <shadeslayer> trying composite
[16:40] <shadeslayer> nope
[16:40] <shadeslayer> I just booted it without any arguments
[16:40] <shadeslayer> trying with console=ttyGS0 now
[16:40] <shadeslayer> ooooh
[16:40] <ogra_> yeah, thats needed
[16:41] <shadeslayer> hmm .. maybe that was just fastboot
[16:41]  * shadeslayer tries flashing again
[16:42] <shadeslayer> nope, nothing with console=ttyGS0
[16:43] <ogra_> nothing in dmesg on the host ?
[16:43] <shadeslayer> nothing
[16:43] <shadeslayer> last message is when I was in fastboot
[16:44] <ogra_> hmm
[16:47] <shadeslayer> ogra_: CONFIG_USB_CDC_COMPOSITE > is that the composite gadget you're talking about?
[16:48] <ogra_> yep
[16:48] <shadeslayer> there's also a CONFIG_USB_G_MULTI
[16:48] <shadeslayer> which is a "Multifunction Composite Gadget"
[16:48] <ogra_> never tried that
[16:48] <ogra_> that likely works only as module and needs options passed
[16:48] <ogra_> to flick the switches on and off
[16:50] <shadeslayer> hmm okay
[16:50]  * shadeslayer tries with CONFIG_USB_CDC_COMPOSITE
[17:02] <shadeslayer> hah
[17:02] <shadeslayer> ogra_: compiling with the composite driver is not possible
[17:02] <moocow_> So, remember that Ubuntu build I got to compile for encore? It flashes alright, but it powers off about 5 seconds later. So, this must be the debug part I heard so much about...
[17:02] <shadeslayer> ogra_: http://paste.kde.org/727622/
[17:03] <ogra_> woah
[17:03] <ogra_> bitter
[17:03] <shadeslayer> :)
[17:11] <Chandrakant_B> hello all
[17:12] <Chandrakant_B> Anyone has tried touch on Pantech Burst or anyone developing it????
[17:14] <moocow_> Chandrakant_B, if there is a cyanogenmod for it, you could try and build it yourself.
[17:30] <Chandrakant_B> or just idle
[17:30] <Chandrakant_B> Does anyone chat here?
[17:31] <ogra_> only if we have something to say :)
[17:32] <shadeslayer> ogra_: so what I'm trying now is : copy adbd binary to initramfs and just run the thing after sysfs/proc stuff is mounted
[17:32] <shadeslayer> maybe, just maybe, it'll work
[17:46] <shadeslayer> nope, doesn't work
[17:52] <shadeslayer> :S
[17:55] <shadeslayer> ChickenCutlass: ogra_ I'm still quite confused as to what s3cfb.bootloaderfb is exactly
[17:56] <ChickenCutlass> shadeslayer: what device are you on
[17:56] <shadeslayer> Nexus 10
[17:57] <ChickenCutlass> shadeslayer: are you trying to get X running
[17:57] <shadeslayer> uh, at the end of the day, yes
[17:57] <ChickenCutlass> shadeslayer: if so, I doubt there is a good enough fb driver
[17:57] <ChickenCutlass> that X needs
[17:58] <shadeslayer> oh? Isn't there the xf86 arm soc driver?
[17:58] <ogra_> armsoc should work
[17:58] <ChickenCutlass> shadeslayer: you need one for that specific chip
[17:58] <ChickenCutlass> ogra_: it might
[17:58] <ogra_> you will need the mali GLES libs
[17:58] <ogra_> ChickenCutlass, its the same board as in the chromebook
[17:58] <shadeslayer> right ^ and we can get that from the android sources?
[17:59] <ogra_> i'm using armsoc here
[17:59] <ogra_> yep
[17:59] <ChickenCutlass> ok good
[18:00] <shadeslayer> ogra_: oh ... if the rootfs is armhf, won't that cause issues? ( or is the mali gles built against armhf? or can armel libs run on armhf? )
[18:00] <ogra_> you can use the armhf chromebook libs ...
[18:00] <shadeslayer> oooh awesome
[18:01] <shadeslayer> mmmm
[18:01] <shadeslayer> android not booting anymore :P
[18:08] <shadeslayer> eh wait
[18:08] <shadeslayer> ogra_: can't I just use your kernel + initrd
[18:08] <shadeslayer> since it's the same board
[18:09] <ogra_> i use the preinstalled kernel on my chromebook
[18:09] <shadeslayer> oh
[18:09] <ogra_> havent updated ever
[18:10] <shadeslayer> wait, you used the one that came with your chromebook?
[18:10] <ogra_> but hrw has a kernel iirc, talk to him in #ubuntu-arm
[18:10] <shadeslayer> ack
[18:10] <ogra_> yes, still using it
[18:10] <ogra_> i even used the chrubuntu script to switch from chromeos to ubuntu ...
[18:11] <ogra_> (then i mostly re-did the userspace as raring though)
[18:11] <rumba> hi
[18:11] <shadeslayer> heh
[18:12] <shadeslayer> I feel this is going to be one of those long nights
[18:37] <Oranger> mhall119: I'm sorry i'll can't be at the meeting at 19:30 UTC
[18:43] <mhall119> Oranger: that's okay, I'll see if anybody else shows up and is interested in helping
[18:43] <mhall119> otherwise you and I can just keep chatting anytime in here
[18:44] <Oranger> mhall119: Ok :) I hope that someone will be there
[18:45] <mhall119> me too, we can use more devs
[18:45] <Oranger> bye
[18:54] <hashLAB> Everywhere it says wifi is possible. How to configure wifi?
[18:55] <awe_> hashLAB, you can use the network indicator to select an access point to connnect to
[18:55] <awe_> if secure, you can enter a password
[18:56] <hashLAB> No, there it says Empty!
[18:56] <awe_> there's not much else implemented for wifi control at this point
[18:56] <mhall119> kenvandine: is qtdeclarative5-accounts-plugin
[18:56] <awe_> your're other option is to use phablet-deploy-networking
[18:56] <mhall119> not built for quantal armhf?
[18:56] <awe_> which will copy a NM profile from your laptop to the device
[18:56] <hashLAB> Is wifi only working with quantal?
[18:57] <awe_> it should work on both our quantal & raring images
[18:57] <hashLAB> okay thanks
[18:57] <awe_> np
[19:22] <kenvandine> mhall119, it is somewhere...
[19:23] <kenvandine> mhall119, in  ppa:super-friends/ppa
[19:23] <mhall119> thanks kenvandine
[19:24] <kenvandine> mhall119, np
[19:24] <perat> hi all
[19:25] <perat> could somebody help me to manage problem with android restoring?
[19:25] <mhall119> kenvandine: did you see my video of the facebook app?
[19:25] <perat> first, a run adb reboot-bootloader
[19:26] <perat> and in bootloader mode device is not found
[19:26] <perat> lsusb:
[19:26] <perat> Bus 002 Device 008: ID 04e8:685d Samsung Electronics Co., Ltd
[19:26] <perat> sudo adb devices gives me nothing
[19:27] <perat> I use Ubuntu 13.04
[19:27] <ogra_> there is no adb in bootloader mode
[19:27] <perat> my device Samsung Galaxy Note 10.1 (GT-N8000)
[19:27] <mhall119> kenvandine: any ETA on getting a UOA front-end on the phablet so I can give it my Facebook account?
[19:28] <perat> when I run takju-jdq39$ ./flash-all.sh I'm getting only < waiting for device >
[19:29] <perat> what can I do to bring it up?
[19:30] <ogra_> what do you actually try to install there ? does samsugn actually offer original images for self install ?
[19:33] <kscloud> Anyone help me with an SDK issue?
[19:35] <perat> sorry, I triyed to run firmware for my phone))
[19:35] <perat> instead of tablet image
[19:35] <kscloud> I was looking at mhall119's app development thing and noticed his first step was to select an ubuntu app or something to that effect, but my install of the sdk doesn't have this option. Nor does it have Qt Quick 2.
[19:35] <kenvandine> mhall119, not really, designs were just ready last week
[19:35] <kenvandine> and work has started on read/write qml bindings
[19:36] <kenvandine> mhall119, want to test my script?
[19:37] <kenvandine> mhall119, http://paste.ubuntu.com/5719686/
[19:37] <kscloud> It's 13.04 btw
[19:37] <kenvandine> mhall119, save that as something like uoa-create
[19:37] <kenvandine> then
[19:37] <kenvandine> ./uoa-create SERVICE USERNAME
[19:37] <kenvandine> like
[19:37] <kenvandine> ./uoa-create twitter kenvandine
[19:38] <kenvandine> mhall119, it only handles facebook and twitter for now
[19:40] <kscloud> Would reinstalling fix the issue?
[19:53] <mhall119> kenvandine: thanks, I'll give it a try later
[19:53] <kenvandine> mhall119, cool, let me know how it goes
[19:53] <mhall119> will do
[19:53] <kenvandine> i'm going to blog soon with details on how to do it
[19:53] <WarlorZ> hi folks, can someone please tell me what code name package i need to get for the ubuntu i would like to try out too : Samsung I9250 ( south africa)
[19:53] <kenvandine> after i get it in the daily image
[19:54] <mhall119> kscloud: did you follow the instructions on developer.ubuntu.com to get the SDK packages?
[19:54] <mhall119> kscloud: http://developer.ubuntu.com/get-started/gomobile/
[19:54] <mhall119> you'll need to add some PPA's and install Qt packages + Ubuntu plugins
[19:54] <kscloud> Some time ago, when it first came out (this was a 12.10 install)
[19:55] <mhall119> kscloud: oh, then you'll need to remove and purge those old packages
[19:55] <mhall119> otherwise they'll conflict with the new ones
[19:55] <kscloud> Ah, didn't think of that. Is ppa-purge default or just in the repos?
[19:56] <mhall119> kscloud: don't know, probably in the repos though
[19:56] <kscloud> Thanks mhall119
[19:58] <The_Matrix_> Am I alowed to ask a question regarding ubuntu touch app development? I am playing with the sdk and I don't know how to accomplish something. If no, can someone lead me to the right channel.
[19:59] <pmcgowan> The_Matrix_: you can ask here
[19:59] <pmcgowan> although most sdk guys done for the day
[20:01] <The_Matrix_> I just want to accomplish something. I want to retrive text from one file and display it on the main program. How do I do this?
[20:01] <WarlorZ> hi folks, can someone please tell me what code name package i need to get for the ubuntu i would like to try out too : Samsung I9250 ( south africa) ?
[20:02] <The_Matrix_> Can I adapt this the code from blackberry to use in this case: http://supportforums.blackberry.com/t5/Cascades-Development/Calling-an-element-id-from-one-QML-file-to-another/td-p/1969775
[20:03] <kenvandine> WarlorZ, i don't see that on the list of ports
[20:03] <kenvandine> https://wiki.ubuntu.com/Touch/Devices
[20:09] <mhall119> ogra_: rsalveti: how would I tell the phablet to open text documents using a specific app?
[20:10] <rsalveti> mhall119: not sure, kaleo might know better
[20:10] <mhall119> kaleo: ^^ ?
[20:10] <mhall119> the ubuntu-docviewer-app can accept a filepath as it's first argument now, and will display it's contents
[20:11] <mhall119> and I believe the file manager can request that a filepath be opened by an external app
[20:11] <mhall119> I just need to connect the dots
[20:15] <pmcgowan> mhall119: the basic model in is the other way around which is why we do not plan to use a filebrowser afaik
[20:16] <pmcgowan> mhall119: I dont  think we have file type associations yet, part of overall content management
[20:17] <mhall119> pmcgowan: well filebrowser is just one example, we'll need to do the same with the browser when downloading a PDF for example
[20:18] <pmcgowan> mhall119: right, then we will have associations so the content goes to the app that can deal with it
[20:20] <sergiusens> mhall119: http://www.theorangenotebook.com/2013/04/testing-ubunutu-touch-images-now-with.html
[20:20] <sergiusens> pmcgowan: rsalveti ^^
[20:20] <mhall119> sergiusens: just saw it on G+
[20:21] <rsalveti> sergiusens: cool
[20:31] <user82> hello all. is the problem still existing that a lg nexus 4 can only be completely turned off via adb?
[20:42] <fginther> mhall119, Oranger, popey, nik90, the jenkins server is back online and has completed processing the merges that were pending. Please let me know if you find anything amiss.
[20:43] <popey> thanks fginther !
[20:50] <mhall119> fginther: I noticed, thanks a bunch for getting him back online
[20:50] <fginther> mhall119, np
[21:12] <mhall119> popey: is the weather team blocked on anything atm?
[21:14] <popey> mhall119: i think they feel blocked on design, but I expect a conversation with design on the hangout to alleviate that worry
[21:15] <mhall119> ok
[21:15] <mhall119> popey: https://wiki.ubuntu.com/Touch/CoreApps/Blockers
[21:15] <mhall119> can you look over that and let me know if I'm missing anything?
[21:21] <popey> oh nicely done, will look over in the morning, sleep is calling
[21:25] <mhall119> g'night popey
[21:27] <nik90> fginther: thanks a lot..I noticed the automatic merges by jenkins.
[21:38] <rsalveti> plars: mind giving http://people.canonical.com/~rsalveti/cm-10.1-20130418-UNOFFICIAL-mako.zip a try?
[21:39] <moocow1452> Brunch for the Nook Color compiles, but crashes upon flashing and needs to be manually restored. http://paste.ubuntu.com/5719982/ Any ideas?
[21:42] <rsalveti> plars: this one is with the ubuntu kernel
[21:42] <rsalveti> basically similar to what sergiusens created earlier today
[21:42] <rsalveti> but this is with latest everything, and works just fine (clean build as well)
[22:08] <kdub> yay, raring images
[22:08]  * kdub updates mir
[22:09] <moocow1452> Anyone want to help with my Nook Build?
[22:30] <plars> rsalveti: does this look right?
[    0.000000] Linux version 3.4.0-0-nexus4 (buildd@sigbin) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.2-23ubuntu2) ) #1-Ubuntu SMP PREEMPT Fri Apr 12 17:11:47 UTC 2013
[22:37] <plars> rsalveti: boots, spot checking a few things I don't see anything better or worse than the stuff I tested in the same image earlier
[22:37] <plars> rsalveti: just looking at functionality (wifi, camera, etc)
[22:45] <rsalveti> plars: right, yeah
[22:45] <rsalveti> it should behave exactly the same :-)
[23:08] <mhall119> balloons: still around?