[00:14] good evening/early morning everyone [00:16] installing touch onto my 2012 Nexus 7, after the last step installing the very last autodeploy.zip of the ubuntu touch, it reboots, installs, then, I just get a black screen [00:16] current command running now: adb push trusty-preinstalled-touch-armhf.zip /sdcard/autodeploy.zip && adb reboot recovery [00:17] this will be my third attempt === CarlosNeyPastor_ is now known as CarlosNeyPastor [00:22] if this last install doesn't work, its firmly bed time [00:28] bed time [00:37] Trying to install autopilot 1.4 to Ubuntu 13.10 using ppa:autopilot/1.4 but getting this with apt-get upgrade: [00:37] The following packages have been kept back: ubuntu-sdk-libs ubuntu-ui-toolkit-autopilot ubuntu-ui-toolkit-doc [00:37] Am I missing something? [00:56] ajalkane: i just added that ppa and then "apt-get update" and then "apt-get dist-upgrade" and it installed [00:56] Setting up python-autopilot (1.4+14.04.20131125bzr410saucy0) ... [00:56] no problem [00:56] (on 13.10) [01:05] charles: still around? [01:05] thomi: yep [01:05] thomi: what's up? [01:06] charles: I'm still trying to get upstart working on my laptop. I wonder if you have any ideas from the mail thread? [01:06] charles: maybe other people I can poke to try and get an answer? [01:09] I thought dist-uprade would do some naughty stuff... okay I'll run it [01:09] dist-upgrade is always the thing to do [01:10] Still get ubuntu-ui-toolkit-autopilot being kept back, but I'll try anyway if this works [01:11] ajalkane: So there still is an issue with that ppa and Saucy. The back-porting hit a snag and didn't proceed. We ahve another option available to us which we should hope to implement soon. Sorry about the delay [01:12] thomi: let me see if I can reproduce the crash you reported in mail on a non-dev system [01:13] veebers: ah ok. Thanks for the info. I'll wait for the fix then. [01:28] thomi, I'm seeing this too, even with a deb built from trunk where all the unit tests passed. [01:29] charles: cool, at least it's not just me [01:29] thomi, imo you've found a large hole in the test coverage... :-) [01:29] yay! [02:06] . === duflu_ is now known as duflu [02:33] plars: ah, much better :) http://ci.ubuntu.com/smokeng/trusty/touch_custom/mako/131:20140116.1:20140115.1/6117/ [02:56] cwayne: way better :) === chihchun_afk is now known as chihchun === ricardodrosales is now known as ricdros [05:46] ogra_: ah, we read power button from xev? we can surely simulate that, yes (either with AP or with python-evdev, or even with umockdev) === vying is now known as Guest78944 [06:34] help /quit [08:02] Mirv: i commented on https://bugs.launchpad.net/ubuntu/+source/telepathy-qt5/+bug/1267835 [08:02] Ubuntu bug 1267835 in telepathy-qt5 (Ubuntu) "telepathy-qt5 fails to build against Qt 5.2" [Critical,New] [08:06] tsdgeos: ok, great! I'll test if it works with both 5.0 and 5.2 and propose a branch with a new patch to it (since it's not our upstream) [08:07] Mirv: i think it worked fine for me here in 5.0 and 5.2 but yeah a double test is in order, it's too early in the morning so i may have not done the testing correctly :D [08:09] in times like this it'd be nice if builders were even faster. qtbase needing a rebuild because libxcb-sync transition, a couple of retries, qtdeclarative snapshot waiting its turn after that, and only after that I can turn my attention these other packages, assuming the qtbase rebuild resolves the other problems in PPAs. [08:09] but if it would be the old PPA builders, the armhf build wouldn't be ready today.. === schmidtm_ is now known as schmidtm [08:23] hello guys I need to know!!! can I install ubunti touch onzte grand x in?????? [08:32] didrocks: yay [08:33] pitti: hey! ;) [08:33] Happy Friday everyone! [08:35] It *is* and happy Friday! :) [08:35] popey: thanks for the g+ post btw, it heated my heart ;) [08:36] :D [08:36] thought you'd like that [08:37] heh, I still investigated a little bit in the crashers to ensure we were really safe, but all was green! [08:37] waiting for ogra_ to wake up to promote an image now (slacker! ;)) [08:37] Maybe he's stuck in traffic on that long and terrible commute to the office!? [08:38] I myself had a tricky time this morning climbing over two cats to get to my laptop [08:38] aka. "coffee maker is broken"? :-) [08:38] good morning [08:38] popey: lol [08:38] popey: waow, what an adventure! :) [08:39] * didrocks waits for a "I twisted my legs when going to work" [08:39] It is when one of them hasn't been fed yet. You take your life in your hands in our kitchen in the morning. [08:39] Scratched ankles is not an uncommon ailment! [08:39] ahah :) [08:43] hello everyone! [08:43] i need some help [08:44] i want to start developing apps for ubuntu touch what programming languages i need to know? [08:48] heyy [08:48] any one here to help? [08:48] i have some questions [08:49] Anmol, hi, many questions can be answered over at http://developer.ubuntu.com/apps/ [08:50] Anmol: hi [08:50] i installed ubuntu touch 14.04 on nexus 4 it now shows black screen on boot up can u tell whatsa the problem? [08:50] Anmol: what process did you follow to install it? [08:51] mzanetti, ping [08:51] i first flashed android 4.2,2 [08:51] then i went to fastboot [08:51] and flashed all boot recovery and system [08:51] then rebooted to recvoery and installed both zips [08:51] not it boots with black screen [08:52] mzanetti, do you know about some qml component that gives visualization of visible gps satellites? [08:52] can you access the device via adb Anmol ? [08:52] yes i can [08:52] Anmol: and do you get an ubuntu prompt? [08:52] device is mounted as mtp [08:53] yes usind adb shell [08:53] system-image-cli -i [08:53] what version does it report? [08:53] current build number: 0 device name: mako channel: daily last update: Unknown [08:53] that looks odd [08:53] ? what happened [08:54] is there some problem with android version? [08:54] Anmol: what channel is reported? [08:54] latest 14.04 [08:55] http://paste.ubuntu.com/6766765/ [08:55] thats what my dev phone looks like [08:55] (nexus 4) [08:55] how ca i check that? [08:55] thats the output from "adb shell system-image-cli -i" [08:56] can you pastebin the entire output from yours? [08:56] current build number: 0 device name: mako channel: daily last update: Unknown [08:56] this is the output i get from terminal [08:57] should i try flashing it over another android version? [08:57] hmm [08:57] tvoss: no, I don't think Qt supports that atm [08:57] I don't flash mine the way you did [08:57] what version of android you used? [08:57] Anmol: my nexus 4 had whatever it came with, 4.2 probably, i flashed months ago [08:58] i use "phablet-flash" to flash my device [08:58] see https://wiki.ubuntu.com/Touch/Install for details of the recommended way to flash devices [08:58] i have the manually downloaded the files [09:00] which ones? [09:00] can you tell me which files you grabbed? [09:00] manual download the latest daily build 14.04 from here http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/ [09:01] boot ,recovery.system armel armhf for mako [09:02] but not the main one, trusty-preinstalled? [09:02] that may be why you have a blank screen [09:02] trusty-preinstalled-touch-armhf.zip [09:02] the zip at the bottom [09:02] i downloaded it [09:02] i flashed it [09:02] all five files [09:04] i am now flashing again with kitkat android 4.4 [09:04] hmm, i don't know. when ogra awakens (shortly) poke him, he will know. [09:04] no, dont do that [09:04] why? [09:04] kitkat isnt supported? [09:04] not yet [09:04] AIUI [09:05] so i should stick with 4.2.2 ? [09:05] hybris needs porting to 4.4 [09:05] yes [09:05] for now [09:05] okay thanks [09:05] i think it's the radio firmware that breaks us in 4.4 === vrruiz_ is now known as rvr [09:05] :( [09:06] but check dual boot ubuntu and android they have provided with a radio for 4.4 [09:06] it'll be fixed soon I suspect [09:06] https://wiki.ubuntu.com/Touch/DualBootInstallation [09:06] its fixed [09:06] right, it's an older one AIUI [09:06] so that's good [09:07] yep [09:07] when will ogra_ come back? [09:08] Anmol: soon [09:08] okay [09:08] oh, ogra_ is here [09:08] ☻ [09:08] thanks :) [09:09] morning [09:09] Good morning. [09:09] hello morning ogra [09:09] i need some help [09:09] Anmol, i'm not sure the manual install process still works since we use signed system images [09:09] so what should i do? [09:09] we should deprecate them if not. [09:10] popey, right, i need to talk to stgraber about that [09:10] :( [09:10] Anmol: what OS is your host running? [09:10] ubuntu 13.04 [09:11] oh, use phablet-flash from the phablet-tools ppa then. [09:11] i will have to download it again? [09:11] it will download it [09:11] ohh shit :'( [09:11] right, what popey said [09:11] cant i use the files i downloaded? [09:12] manually> [09:12] no, they are not the right ones [09:12] okay [09:12] sorry. [09:12] these are only the input files for the signed images [09:12] so why dont the ubuntu team remove that wrong article :( ? [09:13] when manual is not working!! [09:13] Anmol: a valid question [09:13] Anmol, because nobody checked manual installs in a while [09:13] okay [09:13] thanks for your valuable testing though, now we probably can deprecate that set of instructions! [09:13] so, there is a positive to this ☻ [09:13] thank you lovely people :) [09:14] heh [09:14] Anmol, if they still work and the wikipage just needs changing we will hear that from the system-image developer, but he lives in a US timezone, it will take some hours for him to wake up [09:14] okay [09:15] i want to start writing apps for ubuntu touch what languages i need to know and some source of tutorials? [09:15] http://developer.ubuntu.com should be a good starting point [09:15] qml, qt, c++ [09:16] html5 [09:16] :) [09:16] thanks and some tutorials? [09:16] javascript too ... [09:16] see the url above, there should be tutorials [09:16] okay please tell me your google account so that i can consult you in future ? [09:17] there is also an ubuntu app developer community on google plus where people often share howtos and instructions [09:18] just come here or go to #ubuntu-app-devel, thats better (i might not always be around, others might know certain things better etc) [09:18] thanks for the help ogra and popey :) [09:19] np [09:19] so what should i use to flash it phablet-flash ? just? [09:19] phablet-flash ubuntu-system --bootstrap --channel=devel [09:20] :) [09:20] and yeah, a bunch of devs hang out in #ubuntu-app-devel [09:20] and we have a G+ community [09:20] whats the name of g+ community [09:21] https://plus.google.com/u/0/communities/111350780270925540549 [09:21] (y) [09:21] thanks [09:22] np [09:58] hi all, just flashing ubuntu touch for the first time onto my nexus 10. I'm currently at (on device) 'ROM may flash stock recovery on boot, fix?'. The install guide says to wait at any steps like this, should i continue? its been around 15minutes so far === dandrader is now known as dandrader|bbl [10:03] Morning all [10:06] davmor2, morning, can you help with my issue above ? [10:09] bitnumus: pass never seen that screen but I know it takes a good long while to flash [10:09] it says 'Ubuntu Update Complete' [10:10] on device that is [10:14] ERROR:phablet-flash:Installation is taking too long or an error occured along the way. [10:15] There is no mention of this in > https://wiki.ubuntu.com/Touch/Install [10:15] so what am i supposed to do ? [10:18] bitnumus, reboot the N10 and see [10:18] i just clicked no [10:18] and i'm into ubuntu now [10:18] first thing, connecting to WiFi, the keyboard is on its side and i can't use it lol [10:20] pretty the shift key closes the keyboard also [10:20] i thought it was stable ? [10:21] well, there are reasons we are about to drop everything but N4 and the 2013 N7 soon [10:21] file bugs though, so it gets fixed [10:22] which channel did you flash [10:23] to get your network set up you can use pahblet-network from a laptop with working WLAN, that will copy over the WLAN settings to the N10 [10:26] --channel stable [10:26] why drop nxus 10, its probably the best device to use this with [10:26] i won't use it on anything else, maybe my HTC one but not until its actually stable [10:26] better use the devel channel, it has far more fixes [10:27] stable is really more to provide app devs a non moving base [10:27] ogra_, ok cool, is there a simply way to upgrade from this channel ? [10:27] adb shell ... [10:27] system-image-cli -c devel -b 0 -v [10:28] note that the download manager gives no feedback, just be patient [10:29] Error: https://system-image.ubuntu.com/gpg/image-master.tar.xz:NETWORK ERROR [10:29] maybe i'm safest starting frmo scratch [10:29] err, did you get your wlan set up yet ? [10:29] thats indeed a requirement to download images :) [10:30] ogra_, i've listerally only just touched any of this 30minutes ago [10:30] ☻ [10:30] yeah, connect to wifi and then run that command, should work. [10:30] right [10:30] or re-flash from scratch [10:30] ok, is that easier than running phablet-flash ubuntu-system --channel devel --bootstrap then ? [10:30] not especially [10:31] you don't need --bootstrap [10:31] its the same, just running on the device [10:31] * ogra_ upgrades his daily phone to image 132 [10:32] popey, hmm, did you do an OTA upgrade to 132 when testing it ? [10:33] yes [10:33] this boot took endlessly long [10:33] and updated my daily phone too [10:33] yes, it did [10:33] kalikiana, tvoss: any chance to review https://code.launchpad.net/~pitti/qtubuntu-sensors/integration-tests/+merge/201742 soon? [10:33] pitti, yup, sorry for the delay [10:34] tvoss: thanks [10:35] (sorry, I didn't mean to sound "why didn't it happen yet"; just a gentle reminder) [10:42] black screen this time :O [10:44] pitti, nothing serious, a question for the qemu-issue mostly [10:44] tvoss: thanks [10:44] pitti, I think noting down the qemu bug for missing timerfd support would be helpful, too [10:44] tvoss: that's not new from this MP, that's already with the simulation sensor backend in lp:platform-api [10:45] but TBH, we get a lot of failures in emulated qemu [10:45] I hope Erik will fix this, he said he was going to work on it [10:48] ogra_: can you plug your maguro into your computer and let me know if the mtp works, I'm still getting failures here however the n4 and grouper are working fine === chihchun is now known as chihchun_afk [10:53] morning [10:54] is there a latest version of Ubuntu-Touch I can try on my Nexus 7 2012? The version I got from the installation instructions just boots to a black screen, I can still get on it via adb shell [10:57] landstalker, use the devel channel [10:57] irc or apt? [10:58] tvoss: thanks; will update on Monday, I need to leave early today [10:59] tvoss: i. e. fix the include and point towards the sensor data format documentation [10:59] pitti, ack and thx, have a nice weekend [11:00] ogra_, that devel flash is giving a black screen, any ideas? [11:03] hmm [11:04] i'm back into CWM [11:04] works here [11:04] can i use phablet from here? [11:04] as long as there is adb root sccess you should be able to, yes [11:04] *access [11:05] might just try it again then [11:05] it keeps asking during the process about flashing a new recovery [11:05] yes, it needs to [11:05] 'ROM may flash stock recovery on boot, fix?'. [11:05] yes or no to this, i've been pressing no [11:06] you need the ubuntu recovery so gpg works to read the signature of the images [11:06] other recovery images do not have gpg on board [11:06] so is that a yes or no? lol [11:06] the install guide says to press nothing [11:07] right, it should do that automatically [11:07] it doesnt, so what to press here [11:07] also, "phablet-flash will not work unless you have booted your device (it must not be displaying the boot loader screen and "adb devices" should list your device). " [11:07] so i can't even flash it now ? [11:07] you should see a robot on violet background with a progressbar underneath during the process [11:07] if you see that, it uses the ubuntu recovery [11:08] not sure if i'm explaining myself well enough, its giving me a prompt which i pasted above [11:08] i have no idea where that prompt could come from [11:08] unless you use --bootstrap or some such [11:09] well i can't do anything now, so should i reinstall android and then use phablet again ? [11:09] no [11:09] if you have the ubuuntu recovery you can just flash again [11:09] no i'm in default recovery [11:10] android laying on his back [11:10] thats not recovery [11:10] thats fastboot flash mode [11:10] right [11:10] its CWM [11:10] no [11:10] thats in the rom of the hone [11:10] *phone [11:11] (with a giant "Start" on the screen by default) [11:11] its CWM 6.0.2.8 [11:11] has ubuntu logo! [11:11] ah, sounds good then [11:12] (but there shoulld be no lying android) [11:12] yea there isn't now i was on the home bit [11:12] ok i can get it via adb [11:12] in* [11:13] so all is good ... [11:14] bitnumus: you installing on a Nexus 7? I'm getting a black screen when I try to boot into Ubuntu Touch [11:14] landstalker, nexus 10 for me [11:14] ogra_, in what respect? lol [11:14] do i need to try and install it manually from here then [11:14] bitnumus, you got the right recovery in place already [11:14] no [11:14] phablet wont let me do anything [11:14] it should just bot [11:14] INFO:phablet-flash:Device detected as /sbin/sh: getprop: not found [11:14] (note that the first boot takes quite long) [11:15] no, it keeps cycling google, google, google [11:15] ~2min or a little more [11:15] i need to flash it again, how can i do that from recovery [11:15] use "-d manta" with phablet-flash [11:16] bitnumus: you sound like you're having the same issue as me. I have boot, recovery and system installed via fastboot flash and the last two steps involve installing the zip's. I do that, then it's supposed to boot into Ubuntu Touch, but doesn't. [11:16] landstalker, you need to use phablet-flash ... i dont think the manual process works anymore [11:16] ERROR:phablet-flash:Backup requested but cannot be completed succesfully, try with --system-image-ready if the system is already on an Image Based Ubuntu System to force it or use --bootstrap if data saving is not important or the system is not already on an Image Based Ubuntu System [11:16] i'll try with that switch then ogra_ ? [11:16] --system-image-ready [11:16] ogra_: don't think that's available in Fedora :) [11:16] bitnumus, no, --bootstrap instead [11:17] oh, maybe it is [11:23] ogra_, same prompt [11:24] ROM may flash stock recovery on boot, Fix? > Yes, no, go back [11:26] this phablet-flash is downloading: quantal named images, I installed trusty. Which is right? [11:27] landstalker, you want trusty [11:28] bitnumus, wait for sergiuens to come around, he maintains phablet-flash ... i have never seen that prompt [11:28] are you using phablet-flash from the ppa? [11:28] apt-cache policy phablet-tools [11:28] yes [11:29] that prompt aside, its booted but screen is blank again [11:29] installation according to phablet successfully finished [11:29] ah, we're there! [11:29] no, phablet-tools from here popey: http://rpm.pbone.net/index.php3/stat/4/idpl/23727034/dir/fedora_19/com/phablet-tools-0.1-6.1.noarch.rpm.html [11:30] ey keyboard is fixed [11:30] whats ogra_ , popey [11:30] thanks** [11:30] :) [11:31] but dont expect to much, the N10 has quality problems ... [11:31] (like the old N7 does) [11:31] I'll wait for this to finish, see if it bricks my N7, then if not, I'll change the URL to trusty and let it try again. [11:33] bzoltan1: is the framework version used anywhere right now in click meta data etc.? [11:33] saucy is definitely far behind trusty ... it was a snaphot to give app devs a non moving target, it lacks a lot of features that were added throughout the trusty cycle [11:33] asac, iirc in click [11:33] bzoltan1: so if we would move to 14.04 framework, will the click apps just be disabled and not be available for download from store ? [11:33] e.g. if i install an image that doesnt have 13.10 framework anymore, does all that stuff work? [11:34] * ogra_ guesses thats rather a question for the click lens developers than for the sdk team [11:34] beuno: ^^ maybe also you for the store side [11:34] beuno: do you guys already honor framework versionm somehow when serving what click apps are installable? [11:34] asac: the dfault framework in the templates is ubuntu-sdk-13.10 [11:35] asac: I do not know how the framework field of the manifest file is handled on the platform side. [11:36] asac: as far as I know you can still force to install click packages and ignore the frameworks [11:37] right [11:37] so i think we need to find out: [11:37] 1. does our image disable apps that have no compatible framework anymore [11:37] 2. does the store already honour this and connected to that: does the click scope etc. actually send that info to store [11:37] bzoltan1: force install? [11:38] bzoltan1: do we have special "force" UI? [11:38] asac, from cmdline [11:38] or is that through cmdline? [11:38] ah... sure [11:38] well that makes sense [11:38] * beuno reads [11:38] but in the click scope etc. we should disable/grey out the apps that dont work anymore, no? [11:38] asac, bzoltan1, yes [11:38] the client tells the server what framework(s) it has [11:38] not grey out ... hide them [11:38] and the server filters results based o that [11:38] beuno: so click scope sends you a list of frameworks supported by device? [11:38] asac, it does [11:39] beuno: a list? :) [11:39] or just one? [11:39] sorry, need to double check so i dont makea check mark on something [11:39] asac, just one atm, still need to change it to support multiple ones [11:39] which is what I have on my plate right now [11:39] the transition between framework story === _salem is now known as salem_ === MacSlow is now known as MacSlow|lunch [11:56] hi everyone :) [11:56] can i backup my ubuntu touch from recovery? [12:07] #ubuntu-app-devel [12:36] tsdgeos: the new qtdeclarative snapshot + cherry picks is now in beta2 PPA, but I'm not yet noticing new successful builds with help from that after relaunching a bunch of them [12:36] no? [12:37] at least they should fail "later"? === alan_g is now known as alan_g|lunch [12:37] tsdgeos: the problem of course is that there are so many packages that I fail to remember which failed so that maybe could succeed now [12:37] Mirv: the toolkit still fails i gather? [12:37] tsdgeos: yes, looks similar to before [12:37] damn [12:37] do you have the url? [12:39] tsdgeos: https://launchpad.net/~canonical-qt5-edgers/+archive/qt5-daily/+sourcepub/3829605/+listing-archive-extra only amd64 so far, looks familiar. but I wonder if it's because of qtpim would be broken and I've one branch from Chris to fix its own tests now which I'm planning to test next. [12:40] let me see if i can repro that here [12:40] not that datepicker for example would directly use it, but still ui-toolkit uses qtpim in some places [12:40] I also uploaded test build of telepathy-qt5 now so I can push the branch for proposing (and have the branch build meanwhile unblocking more packages) [12:41] Mirv: are you building ubuntu-ui-toolkit package or ubuntu-ui-toolkit from bzr? [12:41]