[00:07] <paco_> hi everyone!
[00:07] <RobbyF> hi
[00:08] <paco_> i was looking for some info on ubuntu-phone, but couldnt find much on google...
[00:08] <paco_> does anybody knows when a second release of the image is going to be published?
[00:09] <paco_> something a bit more 'functional' than the preview from last month
[00:09] <rickspencer3> paco_, there are daily images
[00:09] <paco_> i see
[00:10] <paco_> are they ready to replace android yet?
[00:10] <rickspencer3> paco_, that's a tall order
[00:10] <rickspencer3> I would say "not yet"
[00:10] <paco_> i have a galaxy nexus but don't have a spare phone
[00:10] <paco_> haha
[00:11] <paco_> i know it's still early
[00:11] <rickspencer3> but, it's functional
[00:11] <rickspencer3> I use it on my Nexus 7 to browse the web a bit
[00:11] <paco_> but i mean if it's usable with contacts, sms and wifi
[00:11] <rickspencer3> facebook, twitter, etc...
[00:11] <rickspencer3> paco_, wifi works
[00:11] <rickspencer3> I don't have a phone, so I can't say how complete the experience is
[00:12] <RobbyF> I've use my old galaxy nexus, it's not ready for daily use
[00:12] <paco_> tbh i was a bit disapointed when i first installed it on my phone
[00:12] <rickspencer3> paco_, here are the install instructions
[00:12] <rickspencer3> https://wiki.ubuntu.com/Touch/Install
[00:12] <RobbyF> does appear to be more stable and less glitchy
[00:12] <paco_> thanks for the link rickspencer3!
[00:13] <rickspencer3> you can use the -l switch to install the daily
[00:13] <paco_> that's just the bit i was missing :) the -l
[00:14] <paco_> i was wondering because not long ago I read an article saying the image could be ready 'within two weeks'
[00:14] <paco_> after some discussion on using some cyanogen code
[00:15] <RobbyF> They still don't have complete core-apps
[00:16] <paco_> i'm really looking forward to installing ubuntu on the phone again!
[00:16] <paco_> (once it can be a replacement for android!)
[00:17] <paco_> ok guys, it's flashing time!!!
[00:17] <paco_> thanks for the info
[00:17] <RobbyF> enjoy
[02:04] <mhall119> anybody know of a way to change the ProgressBar image source?
[04:09] <dank101> Mwa, ha, ha... Humans and there desires! I'm free at last! I bring you destruction... I bring you terror.. I am Czar... Prepare yourselves!
[04:09] <mhall119> ok
[04:09] <SpacedOut> How long does it take to do a factory reset on the Nexus 10, 32GB?  I just unlocked the Nexus 10, and it is giving me the colorful X boot logo, it has been sitting here for 20 some minutes.
[04:10] <mhall119> didn't take that long on my N7
[04:10] <mhall119> maybe 10 minutes
[04:11] <SpacedOut> It would be nice to have some kind of a progress indicator.  I tried powering it off/back on once already.
[04:28] <SpacedOut> mhall119: Apparently a bootloop is common on unlocking and requires going into the boot menu again to wipe the data partition manually to clear.  Thanks for the info.
[04:54] <hopkinskong> ogra_: New logcat has been compiled, pushing
[05:09] <Mirv> jppiiroi1en: dpkg -l *qt5* for starters but it doesn't list everything. better option just apt-get dist-upgrade. but I haven't seen that exact error message.
[05:18] <bzoltan1> rickspencer3:  This is the best channel to ask about the SDK.
[06:14] <histo> Is there a gesture to close a window?
[06:15] <histo> Also if I install regular ubuntu desktop on a tablet will I have the ability to use gestures assuming the touch screen is detected properly by X
[07:50] <dholbach> good morning
[09:03] <AsGreyWolf> hello i have gt-s5570 and there aren't official cyanogen10 for my phone. are you going to port ubuntu for my phone?
[10:44] <thore_> hi all
[10:45] <thore_> is it possible to install ubuntu touch from clockworkmod recovery?
[10:45] <tvoss> ogra_, can you help thore_?
[10:46] <ogra_> thore_, just install your device specific image first, then the phablet zipfile
[10:46] <ogra_> thore_, and make sure /data and /system are mounted when flashing
[10:47] <thore_> ogra_: I don't use Ubuntu on my pc (I use ArchLinux) and phablet package is not available
[10:47] <ogra_> well, you need adb
[10:47] <ogra_> so make sure thats installed
[10:48] <ogra_> (and probably file a bug in arch so someone packages phablet-tools)
[10:48] <thore_> mmm.. I'm looking for an alternative way to install it.. something like a nandroid backup, there isn't?
[10:50] <ogra_> i gave you instaructions above ...
[10:51] <ogra_> -a
[10:55] <Anidel> hi to everyone
[10:56] <dun1982> thore_: good luck with Arch :)
[10:58] <thore_> ogra_: ok, thank you
[10:58] <thore_> dun1982: thx ;)
[11:02] <h01ger> hi. i've successfully flashed my nexus 4, booted, it displays the time (which is updated) and "14 tweets received" but it doesnt accept any input
[11:02] <ogra_> not even the default gestures ?
[11:02] <ogra_> (swiping from either side)
[11:03] <h01ger> those work
[11:04] <h01ger> but i cannot enable wireless. oh. guestures do work. thanks
[11:04] <h01ger> nice
[11:12] <thore_> Ok, I've installed android-sdk, and phablet package, when I try to do: "phablet-flash -b -l" I get: Starting new HTTP connection (1): cdimage.ubuntu.com
[11:12] <thore_> Jenkins data format has changed, incompatible
[11:12] <agcalamitaITA> Update your phablet-tools :)
[11:13] <thore_> is not so easy :D
[11:13] <thore_> ok.. I'll try
[11:15] <agcalamitaITA> sudo apt-get install phabet-tools
[11:16] <thore_> agcalamitaITA: I don't use ubuntu
[11:16] <diego_> hi guys. Is there any way to install ubuntu touch on my nexus4 without leaving android? I do not want to wipe my device. I would like to have it in a dual boot
[11:16] <thore_> I've downloaded it from: https://code.launchpad.net/~popey/phablet-tools/download-only , these aren't the last one?
[11:16] <thore_> diego_: no
[11:16] <agcalamitaITA> thore_: What OS are you using...?
[11:17] <thore_> agcalamitaITA: ArchLinux
[11:17] <agcalamitaITA> Not 100% familiar with that distro... no apt-get?
[11:17] <thore_> No, it uses another package manager, named "pacman"
[11:18] <thore_> and there isn't an official repository with phablet-tools
[11:18] <ogra_> there is, see the installl wikipage
[11:19] <thore_> ogra_: that repository is for apt
[11:21] <ogra_> deb packages use source tarballs ...
[11:23] <ogra_> and the upstream source is at https://code.launchpad.net/~phablet-team/phablet-tools/trunk
[11:23] <popey> thore_: you dont want that
[11:24] <popey> thore_: as ogra_ says you want the upstream branch, not my one
[11:24] <ogra_> or the tarball from the ppa
[11:24] <ogra_> (or just run ubuntu in a VM that understands USB )
[11:25] <h01ger> how do i quit this events > albums > photos application/view/whatever?
[11:25] <ogra_> swipe from the bottom until  the looking glass shows up under your finger
[11:25] <ogra_> then press the X on the bottom left
[11:26] <h01ger> thx. sigh, i tried this... (but only once and then everything else...)
[11:28] <thore_> ogra_: thank you
[11:35] <h01ger> is there a user guide somewhere?
[11:35] <agcalamitaITA> wiki.ubuntu.com/Touch
[11:36] <h01ger> i dont see a user guide there
[11:36] <h01ger> as in, how to use+modify the ui
[11:36] <ogra_> look at the release notes
[11:36] <ogra_> there are some hints
[11:37] <h01ger> i did, thats why i'm asking. so the answer to my question is "no".
[11:37] <ogra_> yes :)
[11:38] <ogra_> there is no UI tutorial (and i doubt there will be, but i guess we'll have some kind of first start tutorial app like android at some point)
[11:38] <h01ger> ogra_, thats all fine and dandy, but i did ask about the present
[11:38] <ogra_> given its a developer preview i think for now you just need to find your way around by asking other devs :)
[11:38] <h01ger> ok
[11:38] <h01ger> thats totally fine for me
[11:38] <ogra_> :)
[11:39] <h01ger> so how do i change the location for the weather app? vi $somefile? :)
[11:39] <h01ger> how do i remove apps from favorites? dpkg -r ?
[11:39] <ogra_> you can change the timezone from cmdline
[11:39] <ogra_> the weather app is still a fake i think ... its just a pic
[11:39]  * h01ger just dpkg --reconfigure tzdata :-)
[11:40] <h01ger> ah
[11:40] <ogra_> there is a weather app in the default apps ppa but i dont think its ready yet
[11:40] <h01ger> how can i remove (all) fake apps? ;)
[11:40] <ogra_> by hacking the code ...
[11:40]  * ogra_ doesnt know exactly which file 
[11:41] <ogra_> "fake app" essentially just means a png :)
[11:41] <h01ger> i know
[11:41] <h01ger> but thanks :)
[11:41] <ogra_> and a hardcoded .desktop entry in the ui code
[11:42] <h01ger> ic
[11:45] <h01ger> the release notes mention a notepad app but i dont see it
[11:46] <agcalamitaITA> h01ger: I think it's called 'Notes' :)
[11:46] <agcalamitaITA> It's definately there
[11:48] <h01ger> agcalamitaITA, i definitly dont see it in the "Apps" thingy
[11:50] <agcalamitaITA> What device?
[11:51] <h01ger> nexus 4
[11:51] <agcalamitaITA> Hmmm... should be under the apps lens
[11:51]  * agcalamitaITA powers on his Nexus 4
[11:51] <h01ger> its not
[11:52] <h01ger> understalled, below the ebay icon, there is an "empty icon", whcih leads to the Video lens
[11:55] <agcalamitaITA> h01ger: You're right! It's disappeared on mine too!
[11:55] <agcalamitaITA> h01ger: 2 secs...
[12:04] <krs360> hi guys. I was wondering if much had changed since the original launch of touch? Does it still contain the pre-loaded contacts, etc and is terminal included yet?
[12:09] <agcalamitaITA> krs360: A few things have been updated/changed. It's still not usable as a daily phone. The terminal is still in development
[12:09] <krs360> ah ok cool. :) wanted to revisit it but it's my main phone so kinda makes it a bit silly to do so! thank you for the reply.
[12:10] <agcalamitaITA> krs360: Yep! Check back in October :)
[12:11] <h01ger> "october" could maybe have been mentioned in these alpha-releasenotes ;)
[12:13] <agcalamitaITA> It's mentioned somewhere
[12:16] <cmcc> Hello. I just flashed ubuntu touch on a Samsung Galaxy Nexus (maguro) and it just turned off. Every time I try to turn it on, it displays "Google" then promptly turns off. Any hints ?
[12:17] <cmcc> I tried `adb logcat' but nothing comes up and the device simply dies
[12:17] <pmcgowan> cmcc: it sounds like the shell is not coming up, what version to you flash
[12:18] <pmcgowan> hmm adb logcat should have worked
[12:18] <cmcc> I flashed the current version
[12:18] <cmcc> I mean I just ran `phablet-flash -l` and it seemed to fetch the latest build
[12:20] <mkozjak> hi
[12:20] <mkozjak> is galaxy nexus still without a data (internet) support?
[12:21] <Mirv> a public outcry - does anyone have something to oppose copying of Qt 5.0.1 to qt5-proper PPA? I've written about it a couple of times, and it seems most parties have checked that things continue to build after the switch
[12:24] <pmcgowan> cmcc: can you get a shell with adb? frankly not sure why it failed to load, that image was used by several folks yesterday
[12:24] <pmcgowan> mkozjak: no data yet
[12:25] <cmcc> @pmcgowan No. I simply push the power button and after a few seconds it powers off.
[12:26] <pmcgowan> cmcc: is it possible its very low on battery?
[12:26] <cmcc> @pmcgowan I can enter the bootloader or recovery mode if needed (I am using clockworkmod)
[12:26] <cmcc> @pmcgowan Not likely, the battery was full when I started things and right now, with the phone powered down I can see it is almost fully charged
[12:27] <pmcgowan> cmcc: when some other devs come online I will ask them to help, I am not as familiar with the android tools
[12:28] <cmcc> @pmcgowan Thanks a bunch. Let me know if there is anything I can try in the meantime
[12:34] <sergiusens> cmcc: boot the phone and provide the output of adb logcat
[12:35] <sergiusens> cmcc: same for adb shell cat /cache/recovery/last_log
[12:35] <cmcc> @sergiusens Like I said before. If I power the phone up it displays "Google" for a few seconds and then shuts down. Nothing comes up on logcat
[12:36] <sergiusens> cmcc: oh... can you enter the bootloader? And what device is this? What was your upgrade path?
[12:36] <cmcc> sergiusens: It's a Samsung Galaxy Nexus, I9250
[12:37] <sergiusens> cmcc: that's a maguro, right?
[12:37] <cmcc> sergiusens: I flashed cyanogen mod 10.0 and then ran the phabflash tool
[12:37] <cmcc> sergiusens: Correct, it's a maguro.
[12:37] <cmcc> sergiusens: I can enter the bootloader. Now what ?
[12:43] <sergiusens> cmcc: try and go into recovery and adb sideload the 2 zips... if that doesn't work, download the system and boot img and install directly (what would be downloaded with phablet-flash -b -l)
[12:43] <cmcc> sergiusens: Pardon my ignorance, what do you mean by "adb sideload" the zips ?
[12:44] <ogra_> sergiusens, do you have any idea why our porting guide doesnt mention openjdk6 anywhere ? afaik we need it to sign the zips
[12:44] <sergiusens> ogra_: was it never there or was it removed?
[12:44] <ogra_> i dont think it was ever there
[12:45] <ogra_> i just noticed it while trying to implement it in the live builder ... where we use a virgin debootstrapped chroot to build
[12:45] <sergiusens> cmcc: try following the sideload part of the instructions from here: http://sergiusens.github.com/posts/installing-ubuntu-touch-preview-on-the-nexus-7-with-ubuntu-on-it.html
[12:46] <cmcc> sergiusens: Hey, thanks. I'll try that straight away.
[12:52] <cmcc> sergiusens: It says "error: closed"
[12:52] <cmcc> sergiusens: I must be having the wrong recovery image ?
[13:12] <sergiusens> cmcc: then follow the instructions on the blog fully
[13:12] <sergiusens> cmcc: but change grouper to maguro
[13:13] <cmcc> sergiusens: Okay, will do that in a bit and let you know
[13:35] <bfiller> gusch: ping
[13:35] <gusch> bfiller: pong
[13:36] <bfiller> gusch: you aware of the issue in the gallery with the header? if you open a photo from event view the header stays displayed
[13:37] <bfiller> gusch: in fact the navigation is broken completely. can't switch views once i open a photo
[13:38] <gusch> bfiller: I made a release yesterday, that fixes it
[13:38] <bfiller> gusch: ok, will update. last night's build failed so not seeing it.
[13:38] <pmcgowan> bfiller: as soon as the osk MR lands we need to spin a build
[13:39] <bfiller> pmcgowan: why do we need to wait on that?
[13:39] <pmcgowan> bfiller: sergiusens mentioned that there was a framework update without plugin ro soemthing like that
[13:40] <bfiller> pmcgowan: previous version seems to work fine so don't think that's a blocker.
[13:40] <pmcgowan> bfiller: ok he was concerned that the keyboard would not come up
[13:40] <bfiller> pmcgowan: I thought that too but it does come up
[13:41] <pmcgowan> ah ok
[13:41] <pmcgowan> so whenever you think then lets kickoff a build
[13:41] <bfiller> pmcgowan: problem last night was ibs build failed - looks like a ibs hiccup. sergiusens needs to just remake the image with the -0 ibs biuld that worked
[13:42] <pmcgowan> bfiller: ok
[13:42] <bfiller> pmcgowan: I just approved the MR for maliit-plugins so once that finishes we'll respin
[13:42] <pmcgowan> great
[14:01] <tsdgeos> ricmm: any idea why test-gtest-xless: /build/buildd/ubuntu-platform-api-0.18/src/android/ubuntu_application_api.cpp:51: {anonymous}::Bridge::Bridge(): Assertion `lib_handle && "Error loading ubuntu_application_api"' failed.  may be happening in the arm CI builders on running unity tests? They work fine here in the phone
[14:02] <tsdgeos> ricmm: maybe the ubuntu_application_api needs "a device" and the arm CI builders are "just" regular Ubuntu machines?
[14:20] <rickspencer3> jppiiroi1en, hey, fyi, mterry helped me fix my issue last night
[14:20] <rickspencer3> https://bugs.launchpad.net/ubuntu-qtcreator-plugins/+bug/1159967https://bugs.launchpad.net/ubuntu-qtcreator-plugins/+bug/1159967
[14:22] <jppiiroi1en> rickspencer3: ok kewl
[14:22] <rickspencer3> jppiiroi1en, of course, now I have a different issue, I can't make particles work because of weird stuff
[14:22] <rickspencer3> but I'll work on that later ;)
[14:22] <jppiiroi1en> ^^
[14:28] <mhall119> popey: the nemo plugin build failed for Quantal
[14:28] <mhall119> which means I can't test the ubuntu-filemanager-app on my N7 :(
[14:30] <kaleo_> loicm: https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/icon/+merge/155505
[14:31] <mhall119> does anybody know how I can get an installed app to appear on the Launcher or in the Dash?
[14:33] <ajalkane> mhall119: I'd guess by creating a .desktop file for it. /usr/share/applications/
[14:33] <pmcgowan> mhall119: I believe that is still hardcoded unless recently fixed
[14:34] <popey> yeah, it is
[14:34] <popey> mhall119: fginther ^^ could you look at nemo pls?
[14:35] <mhall119> pmcgowan: hardcoded in C/C++ or in a config file?
[14:35] <pmcgowan> mhall119: not sure if its qml or c++
[14:36] <mterry> sergiusens, what's the story with jenkins-ci testing unity/phablet merges against raring?  Aren't those guaranteed to fail?
[14:36] <pmcgowan> Saviq or greyback would know
[14:36] <Saviq> mhall119, be with you in 5
[14:37] <mhall119> thanks Saviq
[14:38] <greyback> mhall119: right now the applications being listed in the dash & launcher are hardcoded in
[14:39] <greyback> mhall119: obviously it's something we need to fix, Saviq might have a better idea on the timeline
[14:39] <pmcgowan> greyback: hardcoded in....
[14:39] <pmcgowan> where?
[14:41] <greyback> pmcgowan: mhall119: first need to add to Applications/applications.js. The launcher list is in Launcher/Launcher.qml. Dash lists in Dash/Apps/*Model.qml
[14:42] <greyback> mhall119: it's it's not obvious what to add, please ping me
[14:42] <pmcgowan> obviously need this fix asap
[14:43] <greyback> yeah. The SDK definitely needs it too
[14:50] <mhall119> greyback: SDK needs what?
[14:52] <greyback> mhall119: someone cannot create an application package, install it on their phone, and have their application icon appear on the Dash/launcher
[14:52] <mhall119> right, but that's a limitation of the Touch Dash/Launcher, not the SDK they wrote the app with, isn't it?
[14:54] <fginther> popey, mhall119. nemo appears to have finished building for armhf and i386.  I fixed the ppa dependency issue earlier today and it looks like it just finished building those two
[14:55] <sergiusens> mterry: what do you mean guaranteed to fail?
[14:55] <mterry> sergiusens, I didn't think our phablet stack in raring was ready yet
[14:55] <mhall119> fginther: ah, yes, looks good to go now, thanks
[14:55] <sergiusens> mterry: it's not, but it's almost there, just missing a couple of packages
[14:57] <mterry> sergiusens, hence my phrase "guaranteed to fail"  :)
[14:57] <sergiusens> mterry: ETA is tonight for an initial live build :-)
[14:58] <mterry> sergiusens, I guess I don't understand why the jenkins switch wasn't pulled tomorrow then.  I don't like blocking merges
[15:01] <sergiusens> mterry: what's failing?
[15:01] <sergiusens> mterry: no merge should be blocked
[15:01] <mterry> sergiusens, when the ci job fails on raring, it marks the merge as failing, so it doesn't get autolanded, eh?
[15:02] <sergiusens> mterry: yes, but what job is failing?
[15:02] <mterry> sergiusens, for example https://code.launchpad.net/~nicolas-doffay/unity/page-header-test/+merge/155242
[15:03] <mterry> sergiusens, but I'm not sure why you need an example, since you know raring will fail, and all merges get ci runs.  So all merges should fail
[15:03] <sergiusens> mterry: no merge should fail...
[15:04] <mterry> sergiusens, well, OK.  Good to hear that this is a bug, rather than intended behavior
[15:04] <mterry> sergiusens, so what's up with that merge above?  (and all merges since the switch was pulled)
[15:05] <sergiusens> mterry: maliit-plugins?
[15:05] <sergiusens> mterry: dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented changes to upstream files, see dpkg-source(1)
[15:06] <sergiusens> mterry: we switched to bzr bd -S a while back and the formatting in this package wasn't ok
[15:06] <mterry> sergiusens, that's not the message that stopped the build.
[15:06] <mterry> sergiusens, I think it was stopped for...  "no known conversion for argument 1 from 'unity::dash::Lenses' to 'const Ptr& {aka const std::shared_ptr<unity::dash::Lenses>&}'"
[15:07] <mterry> sergiusens, but actually, I had expected the failure to be because some packages weren't available
[15:07] <sergiusens> mterry: oh, unity....
[15:07] <mterry> sergiusens, well, I'm just using the example of the merge I linked above
[15:08] <sergiusens> mterry: well unity's primary task should be making it work on raring
[15:08] <sergiusens> mterry: or splitting it up
[15:09] <sergiusens> mterry: Saviq was working on it
[15:09] <Saviq> sergiusens, mterry, we should be merging the fix soon
[15:11] <mterry> sergiusens, you mean the unity team's primary task?  Is that a mandate by their manager?
[15:12] <mterry> sergiusens, (I mean, I know they need it eventually; I just don't like blocking progress for a few days to force them to do it.)
[15:18] <gusch> boiko nerochiaro oSoMoN renato_ anyone up for a (longer) review? https://code.launchpad.net/~schwann/gallery-app/gallery-photos-view-toolbar/+merge/155510
[15:19] <sergiusens> mterry: well it's in a blueprint
[15:19] <oSoMoN> gusch: diff > 1000 lines. does not compute.
[15:20] <oSoMoN> gusch: more seriously, I can put it in my to-do list, but I won’t get to it today
[15:20] <this1guy> if my device isn't officially supported by cyanogenmod then is this line seem right     <project path="device/htc/msm8660-common" name="CyanogenMod/android_device_htc_msm8660-common" remote="github" revision="refs/heads/cm-10.1" />  (i looked at my device cm.dependencies it only had 1)
[15:21] <this1guy> ***thats the line i put in manifest.xml and when i did repo sync it couldn't find it i guess
[15:21] <gusch> oSoMoN: I think it's only "new line" at the end that is missin
[15:22] <gusch> oSoMoN: thx for doing it
[15:22] <mterry> sergiusens, just because it's a work item does not mean it should stop the line until we fix it.  I'm just complaining the way it was done (switch was flipped before we were ready is all)
[15:22] <sergiusens> mterry: who determined "we were ready"
[15:23] <sergiusens> mterry: I mean 'who determines'?
[15:23] <mterry> sergiusens, if unity can build in raring, I'd guess
[15:24] <nerochiaro> gusch: can't take that one today i'm afraid
[15:24] <gusch> nerochiaro: that's ok
[15:26] <sergiusens> mterry: well, Saviq said he was working on it, so I don't understand the point
[15:26] <sergiusens> mterry: are you working on unity and is something blocked there?
[15:27] <mhall119> yay! I've got a file manager on my N7
[15:27] <sergiusens> mterry: and if by ready, I did tell all the teams
[15:27] <Saviq> sergiusens, mterry, here I agree, we were kind of surprised by the fact that suddenly we can't merge anything
[15:28] <sergiusens> Saviq: well I did give you a heads up
[15:29] <Saviq> sergiusens, must not have been explicit enough
[15:30] <Saviq> sergiusens, didn't stick, I'm afraid
[15:30] <mhall119> now I just need a terminal app
[15:30] <sergiusens> Saviq: I'll rollback, but today, unity and notify-osd are the only ones preventing a raring build
[15:30] <Saviq> sergiusens, no no, no rolling back
[15:30] <Saviq> sergiusens, we're almost there
[15:31] <Saviq> sergiusens, I think we just simply didn't know what that meant
[15:32] <sergiusens> Saviq: ok, sorry for the confusion then
[15:52] <this1guy> help please    when I do  cd device/htc/shooteru i get bash: cd: device/htc/shooteru: No such file or directory and yes i have adb and all that stuff. i ran adb devices and it shows my device. im on the step where you have to pull files from phone
[15:54] <sergiusens> this1guy: did you add those repos to the manifest?
[15:55] <this1guy> yea i added it awhile ago and did the repo sync it went thriugh this time i believe.
[15:55] <this1guy> From git://github.com/CyanogenMod/android_device_htc_msm8660-common  * [new branch]      cm-10.1    -> github/cm-10.1 Fetching projects: 100% (137/137), done.   Syncing work tree: 100% (136/136), done.
[15:55] <this1guy> thats what i got
  From git://github.com/CyanogenMod/android_device_htc_msm8660-common  * [new branch]      cm-10.1    -> github/cm-10.1 Fetching projects: 100% (137/137), done.   Syncing work tree: 100% (136/136), done.
[16:05] <sergiusens> this1guy: so if the path in the project node in the manifest is device/htc/shooteru you shouldn't have a problem
[16:06] <nerochiaro> oSoMoN: https://code.launchpad.net/~osomon/webbrowser-app/increaseScrollingVelocity/+merge/155304 approved
[16:06] <nerochiaro> oSoMoN: sorry it took so long
[16:07] <oSoMoN> nerochiaro: thanks
 So i can just skip over the step where you have to pull device files from the phone while running cm10.1?
[16:10] <sergiusens> this1guy: I mean, you shouldn't have a problem changing into that directory
[16:14] <boiko> gusch: I can take it, if nobody else did already
[16:15] <gusch> boiko: oSoMoN could do it tomorrow - if cou can do it today, that would be cool
[16:15] <this1guy> sergiusens: well it keeps saying no such file or directory when I do cd device/htc/shooteru (I'm trying to pull proprietary stuff). I see it say you can alternatively extract them from a zip. I have a zip of the rom i'm running now. I should just be able to unzip it them move the stuff to where it needs to go right? (sorry if i confused you I just started this kind of stuff)
[16:15] <labsin> Is it possible to use OpenGL ES apps compiled with Qt on Ubuntu Touch?
[16:15] <boiko> gusch: I can do it today
[16:16] <gusch> boiko: cool! thx - oSoMoN so no need for you to review
[16:16] <oSoMoN> gusch: ok
[16:22] <boiko> gusch: is setting the title via property binding still a problem in latest headers? I remember seeing it fixed
[16:24] <gusch> boiko: I tested it - still has issues :(
[16:25] <boiko> gusch: ok, it was just to confirm
[16:27] <sergiusens> this1guy: yes, you can copy from the zip if you want
[16:30] <this1guy> sergiusens: alright I just got done copying them over thanks and btw when copying them over do I just overrwright the etc foler and the other folders thats there or do I have to make a folder inside of vendor and htc/shooteru then place the files there
[16:34] <sergiusens> this1guy: it's probably not a direct copy
[16:34] <sergiusens> this1guy: you need to read what the script does and replicate from there
[16:35] <mhall119> popey: u1db-qt packages are in the PPA now \o/
[16:35] <popey> huzzah!
[16:36] <this1guy> sergiusens: oh alright i gottcha.
[16:42] <Anidel> hi everyone...
[16:43] <Anidel> I am having issues with QtCreator...having installed ubuntu-sdk on my 64-bits Ubuntu machine, I can't create new Qt Quick UI projects...it doesn't show in the list.
[16:44] <Anidel> I only see Other Projects / Non-Qt Project / Import Project
[16:45] <xcvb> Do you also have Qt4 dev installed?
[16:45] <Anidel> I followed the instructions from the Install page...let's check
[16:47] <Anidel> Qt4 was missing, I thought it'd install Qt5?
[16:48] <Anidel> (and qt5 dev is installed btw)
[16:48] <xcvb> I had the same issue when I had installed the Qt4 before.
[16:49] <boiko> gusch: I just added a couple comments, but other than that the MR looks good
[16:49] <Anidel> it doesn't detect any Qt dev at all (Tools->Options->Build&Run->Qt Versions)
[16:49] <xcvb> Do you have the Ubuntu welcome screen in QtCreator?
[16:50] <Anidel> yep and it's version 2.7 (i.e. 2.6.xxx)
[16:50] <Anidel> anyway I manually added it...and now it shows
[16:51] <gusch> boiko: ok - thx
[16:51] <Anidel> go figure why it didn't automatically detected it
[16:51] <Anidel> qmake was in the default path (/usr/bin)
[16:51] <nerochiaro> mzanetti: stupid autopilot question, but how do i assertThat something is greater than something else ?
[16:51] <xcvb> Is there anything in properties->kits (I don't have a computer with qtcreator at the moment, maybe it's called a little bit different)
[16:52] <Anidel> xcvb: I checked under Qt Versions and it didn't detect it. I went to Add it and gave it the path to qmake in /usr/bin/ and now it shows.
[16:52] <Anidel> one other question now is how one can developer HTML5 apps... if I choose the Applications->HTML5 Application it supports Desktop only
[16:54] <boiko> rsalveti: is call holding supported in the ofono side? I tested here with phonesim and it worked (phone-app putting a call on hold)
[16:54] <Anidel> xcvb: missing a dev kit now...let's see
[16:56] <bfiller> boiko: rsalveti on holidays this week, maybe awe knows
[16:56] <seb128> hey
[16:56] <seb128> do you guys log your IRC meetings somewhere?
[16:56] <boiko> bfiller: ah ok, thanks
[16:56] <seb128> I just learnt there was a meeting on #ubuntu-touch-meeting about the pdf app
[16:57] <bfiller> boiko: speakerphone would be a good one to get done, looks like it's on the list for this milestone
[16:57] <xcvb> HTML5 apps are just websites. The last time I tried Ubuntu Phone you had to define the apps inside a .js file. I guess in the future Ubuntu Phone will get the links from the .desktop files from /usr/share/applications
[16:57] <seb128> but that channel isn't logged on irclogs.ubuntu.com
[16:57] <boiko> bfiller: yep, will try to get that today or tomorrow
[16:58] <bfiller> boiko: cool
[16:58] <Anidel> xcvb: ok
[17:02] <xcvb> Anidel: Do you want to write html5-apps, or also qml-apps? The Ubuntu SDK is only required for the qml ones. In this case you can try "qmlscene qmlfile.qml" in the console to see if it works.
[17:02] <Anidel> xcvb: pure HTML5 apps
[17:10] <boiko> awe: hey Tony, do you know if enabling/disabling speaker mode is implemented at the ofono level?
[17:13] <awe> boiko, I haven't really looked at the ofono audio code too much, but I can check for you
[17:13] <boiko> awe: that would be nice, thanks
[17:13] <awe> yes, it's part of the call volume interface
[17:13] <awe> one sec, I can you point you at the code
[17:14] <awe> looks like it's controlled via a "Muted" property
[17:15] <awe> boiko, http://bazaar.launchpad.net/~phablet-team/phablet-extras/ofono/view/head:/src/call-volume.c
[17:15] <awe> by the way, we need to chat about PIN authentication at some point
[17:16] <awe> I'm not sure if this is something that should be handled by the connection manager, or by indicator-network/telephony
[17:16] <awe> the latter will have to handle it for desktop at some point, as that's what happens today with network manager & modem manager
[17:17] <awe> but I think it probably makes sense for the connection manager to always handle when using ofono
[17:18] <boiko> awe: I think it is not limited to pin auth only, there is more stuff to manage on pin, right?
[17:18] <awe> boiko, I have an "Investigate SIM auth UI" as a work item in my telephony blueprint
[17:18] <awe> can I assign to you?
[17:18] <awe> AFAIK, we have to impement the PIN/PUK
[17:18] <awe> UI logic
[17:19] <awe> We also have to implement hooks for the STK
[17:19] <awe> ( SIM tool kit )
[17:19] <boiko> awe: yes, I think you can reassign that to me, but actually it would be a good idea to have input from designers about that too
[17:19] <awe> definitely
[17:19] <boiko> awe: anyway, it makes more sense for me to handle that than it makes for you, so just go ahead and reassign it :)
[17:19] <awe> ack
[17:21] <boiko> awe: I'm checking the file you pointed me to, but it only seems to have methods to adjust the volume, not to switch to use or not the speakerphone
[17:22] <awe> hmmm, I guess I misread your initial question...
[17:22] <awe> once sec
[17:24] <boiko> awe: ok
[17:25] <boiko> gusch: now that I reviewed your MR, would you by chance have time to review this one? https://code.launchpad.net/~boiko/phone-app/clear_warnings/+merge/155289
[17:25] <awe> boiko, it doesn't appear to have code to handle speaker mode
[17:25] <gusch> boiko: sure
[17:26] <awe> boiko, we'll need to discuss with rsalveti when he's back, as our current voice plugin is hard-code to set the audio out to earpiece for phone calls
[17:26] <boiko> awe: ok, we postpone that then
[17:26] <boiko> bfiller: ^
[17:26] <awe> boiko, we'd need to have some kind of coordination between indicator-sound, and our ofono code too
[17:26] <boiko> bfiller: in the app and tp-ofono it is implemented up to the point of calling something to actually set the speaker mode
[17:27] <boiko> awe: yes, makes sense
[17:27] <awe> cause I imagine there'd be a button in the sound settings to enable the speakerphone, as well as a button in the phone app
[17:27] <boiko> bfiller: so, we postpone speakerphone setting ^
[17:27] <awe> so both will have to query current state, save it, then restore properly
[17:27] <awe> I'll add another work item for ofono
[17:27] <awe> thanks
[17:29] <boiko> awe: nice! thanks
[17:30] <awe> np
[17:37] <gusch> boiko: commented
[17:39] <nerochiaro> gusch: renato_: if you're low on bugs, can you have a look at fixing this one in camera-app ? https://bugs.launchpad.net/manhattan/+bug/1130342
[17:39] <boiko> gusch: nice, let me see
[17:41] <boiko> gusch: so, the if I keep the anchors.fill: parent there, it raises me tons of binding loop errors, not sure what UbuntuShape does internally that triggers this
[17:42] <gusch> boiko: ok then
[17:43] <boiko> gusch: I'll reply in the MR to document it
[17:43] <gusch> boiko: yes, thanks
[17:47] <boiko> gusch: I replied to the comment, can you check if you agree with that?
[17:49] <jhodapp> robru, ping
[17:49] <robru> jhodapp, hey
[17:49] <jhodapp> robru, did you get that build error figured out?
[17:49] <gusch> boiko: approved
[17:49] <robru> jhodapp, no not yet. the package builds on i386 but errors on amd64. I'm not a C guy so I don't know much about that stuff, but didrocks said it was some kind of incorrect cast.
[17:50] <jhodapp> robru, indeed, what changed to make that start failing though? That's what I'm somewhat confused about...this has been building ok for several months now.
[17:51] <robru> jhodapp, what changed is that I enabled amd64 builds ;-) previously it was only set to build for arm+i386
[17:51] <jhodapp> robru: ah ok, it's erroring also because the -Wall flag is set...that must not have been set for the other two archs
[17:51] <robru> jhodapp, hmmm, not sure how that happened.
[17:52] <robru> jhodapp, so is the solution to fix the cast, or is the solution to drop -Wall?
[17:52] <jhodapp> robru, I think I could get rid of the warning (error), let me see if I can prepare an MR
[17:52] <robru> jhodapp, oh, great, thanks
[17:52] <jhodapp> robru, fix the cast
[17:52] <boiko> gusch: thanks!
[17:53] <jhodapp> robru, the cast is fine, but I could make it so that it doesn't generate a warning through some magic :)
[17:53] <gusch> boiko: np
[17:58] <gusch> mzanetti boiko https://code.launchpad.net/~schwann/gallery-app/gallery-hopefully-stable-photos-tests/+merge/155568
[18:00] <boiko> gusch: so, in the previous condition it was less or equal 0.2, and now you used greater than, is that correct?
[18:01] <gusch> boiko: yes - the less was always suspect to me - now there is a visible break (for the timing)
[18:02] <gusch> boiko: and the way of writing it wouldn't even do that with "=>"
[18:03] <boiko> mzanetti: is there a condition to check to make sure a button is already visible and ready to be clicked?  I have one last test that is failing due to app startup races
[18:04] <mzanetti> boiko: the one with dialing the number where the "1" gets lost?
[18:04] <robru> jhodapp, ok, sounds good. just submit the MP against the branch that I asked you to review, and then I'll merge it into mine for testing. I gotta step out for a bit but I'll be back later to merge that stuff all together. thanks again!
[18:04] <boiko> mzanetti: yep, exactly this one :)
[18:05] <jhodapp> robru, ok
[18:05] <mzanetti> boiko: I've been thinking... maybe you can create a function like "press_number_button(int)" which uses the same pattern as I introduced for the swipe
[18:07] <boiko> mzanetti: but is there a way to check if the button was actually pressed? (without comparing the text label for the result)
[18:09] <mzanetti> boiko: hmm... there is a untested feature in autopilot that lets you connect to signals. I haven't ever used it so far and noone knows if it works
[18:09] <mzanetti> .D
[18:09] <mzanetti> :D
[18:09] <mzanetti> boiko: so probably you're better off figuring something yourself
[18:10] <boiko> mzanetti: hehe, ok, I'll check if I can figure out something
[18:11] <boiko> gusch: got time for one more MR? https://code.launchpad.net/~boiko/phone-app/fix_displaying_sent_messages/+merge/155348
[18:24] <Beremus> Hi, I need help. I installed Ubuntu for tablet on my Nexus 7. Now, I didn't used the tablet over a week or 2 and the battery drained out. Now I can't boot the device... How could I fix this?
[18:25] <Beremus> Hi, I need help. I installed Ubuntu for tablet on my Nexus 7. Now, I didn't used the tablet over a week or 2 and the battery drained out. Now I can't boot the device... How could I fix this?
[18:27] <pmcgowan> Beremus: the 7 is notorious for low battery behavior
[18:28] <pmcgowan> Beremus: it may take some time to get a minimal charge
[18:28] <Beremus> Ok, I'll let it plugged for at least.... 3 hours, then it should boot?
[18:29] <pmcgowan> yes, it can literally take 30 mins or more
[18:29] <pmcgowan> depending on the charger
[18:30] <Beremus> ok, because the only thing the tablet is doing is booting, but with a black screen with sometimes, snow.
[18:34] <boiko> awe: do you know if call holding is implemented at the ofono level? I tried phone-app + ofono-phonesim and it worked
[18:35] <boiko> bfiller: I moved the speakerphone item to the next milestone as this is not supported in the ofono level yet
[18:39] <awe> boiko, I don't know for sure... lemme take a look
[18:41] <awe> boiko, not implemented
[18:41] <awe> http://bazaar.launchpad.net/~phablet-team/phablet-extras/ofono/view/head:/include/voicecall.h
[18:41] <awe> ^^ is the ofono plugin API for voice
[18:41] <boiko> awe: for instance, I call org.ofono.VoiceCallManager.SwapCalls
[18:42] <awe> http://bazaar.launchpad.net/~phablet-team/phablet-extras/ofono/view/head:/drivers/rilmodem/voicecall.c
[18:42] <awe> ^^ is the rilmodem implementation
[18:42] <awe> so what you do, is look at the ofono_voicecall_driver struct in the plugin code and see what functions have been implemented
[18:43] <awe> very few at this point...
[18:43] <awe> dial, answer, hangup_all, and send_dtmf
[18:43] <boiko> awe: is that in your (or in rsalveti's ) blueprint items already?
[18:43]  * awe checks the ofono/telephony blueprint for work items
[18:44] <gusch> boiko: still need someone for reviewing?
[18:45] <boiko> gusch: yep, if possible
[18:45] <gusch> boiko: ok - looking at it
[18:45] <boiko> gusch: nice! thanks
[18:47] <awe> boiko, I added a work items for call holding & multi-call support
[18:47] <awe> not assigned to anyone right now.  We probably need to plan a hangout to discuss the telephony blueprint
[18:47] <awe> I'll try and schedule something for next week
[18:47] <awe> it's getting there, but still has some holes...
[18:48] <gusch> boiko: Using qrand() in a unit test? Why not a fixed number?
[18:50] <boiko> gusch: well, doesn't really matter for that case actually, I will replace by a fixed number :)
[18:55] <gusch> boiko: approved
[18:55] <boiko> gusch: thanks!
[18:57] <bfiller> boiko: thought rsalveti said speakerphone was already in there
[18:58] <boiko> bfiller: we have to wait for him anyways
[19:00] <boiko> bfiller: and for call holding, the phone-app and telepathy-ofono sides are implemented, it just needs implementation in ofono, I'll my the work item for phone-app as DONE
[19:01] <bfiller> boiko: ok
[19:02] <awe> bfiller, the speakerphone stuff looks hard-coded to always use ear-pieces for phone calls
[19:02] <awe> we'll need to coordinate with the indicator guys too, as indicator sound may have a speaker button that'd need to keep in sync with the phone-apps view of the world
[19:03] <awe> bfiller, I will schedule a hangout for next week to discuss telephony work items
[19:03] <awe> there's a lot to do, and it'd be nice to have some eyeballs on the blueprint/work items
[19:03] <awe> I've added a bunch of stuff today thanks to boiko
[19:04] <bfiller> awe: ok thanks
[19:09] <awe> hey lool, can you approve my telephony blueprint?
[19:09] <awe> also, would like to schedule a hangout next week to review work items, make sure folks are in sync as well...
[19:17] <Beremus> I let charge my nexus 7 for about and hour and half, still not boot..... I think it might be bricked or somethimg.
[19:19] <Tassadar> unless it is showing _something_ when you press power button, it is not charging
[21:21] <The_Matrix> I need help with ubuntu touch on a nexus 7
[21:22] <The_Matrix> I am unable to connect to my network. When I want to type my password, the keyboard does not show up.
[21:22] <The_Matrix> This is in the network indicator.
[21:23] <Tassadar> you should be able to get keyboard by using one of the icons in status area, the one which looks like 4 squares
[21:24] <Tassadar> it should have "Show keyboard" option or something like that
[21:24] <Tassadar> oh, wait
[21:24] <The_Matrix> What is the status area? Is it the indicator area
[21:24] <Tassadar> bad channel
[21:24] <Tassadar> sorry :/
[21:25] <Tassadar> thought this is #ubuntu-arm, and this is touch, so I dont know, for me, tapping to the textarea worked fine
[21:26] <The_Matrix> I hate to say it, but I can across a bug. I have rebooted the device. I guess I will try again.
[21:26] <The_Matrix> came
[21:26] <boiko> sergiusens: https://code.launchpad.net/~boiko/telepathy-ofono/fix_python_errors/+merge/155615
[21:27] <boiko> sergiusens: basically fixing the issues reported by pyflakes and pep8 (with the exception for long lines, those I didn't fix, if I get the time I'll fix in a separate MR)
[21:27] <boiko> bfiller: can you please review this release MR? https://code.launchpad.net/~boiko/phone-app/release_0.59.3/+merge/155619
[21:28] <The_Matrix> Got the keyboard. yay.
[21:30] <The_Matrix> Tassadar: Thank you for your help. :)
[21:30] <Tassadar> well I didn't do anything, but okay)
[21:31] <The_Matrix> well, at least you tried.
[21:32] <sergiusens> boiko: looking
[21:35] <bfiller> boiko: approved
[21:38] <sergiusens> boiko: added comment
[21:40] <boiko> sergiusens: hmm, I didn't get those when running it here, interesting. ok, I'll take care of those tomorrow
[21:41] <boiko> bfiller: thanks
[21:41] <boiko> sergiusens: thanks for looking into it
[21:43] <sergiusens> boiko: well they might only show up in pep8 1.3.3
[21:44] <sergiusens> boiko: one question before you leave, which ones are the branches for telepathy-logger, telepathy-python and telepathy-logger-qt
[21:45] <sergiusens> boiko: seems we have a package/branch name missmatch :-/ I'm just noticing it's the reason I was always confused :-)
[22:36] <The_Matrix> Anyone know what display server the Ubuntu Touch Daily images runs? Is it MIR?
[23:40] <uto_> hi there
[23:42] <uto_> who has build a functionnal rom please?
[23:42] <uto_> with a new device