=== aaron__ is now known as ahoneybun [00:16] Hello all, anyone around? [00:18] awe: now i get this "received=Q and expected=QOEMHOOK", i'm using parcel_w_string [00:18] parcel_w_string(rilp, "QOEMHOOK"); [00:54] Hola Hombres === aaron is now known as Guest57402 === chihchun_afk is now known as chihchun [03:23] http://news.softpedia.com/news/Mark-Shuttleworth-Introduces-Snappy-Ubuntu-Core-at-Internet-of-Things-World-2015-483125.shtml === freeflying__ is now known as freeflying === salem_ is now known as _salem [04:48] /join #xubuntu [04:48] of course parsing is wrong. lol. === tvoss|lunch is now known as tvoss [06:40] good morning [07:55] HI [07:56] I wondered if I could get a dual boot on a BQ Aquaris 5 Ubuntu touch / Android [07:57] If it is possible it's definetely going to be my next smartphone [07:57] it wont be sold like that, no ... but the saystem is all open :) [07:57] *system [07:58] Well i knw that it's not goign to be sold this way however I visited BQ's website this morning [07:58] (someone could surely make it work with multirom or some such... with some passion and knowledge) [07:58] and I saw the Aquaris E5 ++ with 1080p screen [07:58] that was kinda affordable [07:58] that wont be sold with ubuntu [07:59] only the 720p version [07:59] yes [07:59] that's why i wondered if I could get a dual boot working on such a device [07:59] I mean the only tutorial i coul dfind on ubuntu [07:59] was how to replace [07:59] android by ubunut [08:00] ubuntu [08:00] I used to have a dual boot on my old galaxy nexus [08:00] android / Ubuntu [08:00] it was not very efficient so i got rid of my ubuntu part [08:01] but the perspective of getting a dual boot on a BQ could worth a try [08:01] there are nexus4, 7 and nexus5 support in multiboot, talk to Tassadar (once he is around) he made them work i think [08:01] but you wont easily get that with a non supported device since you would have to do a full port first [08:02] hi, is the battery life on nexus 5 still aweful? [08:05] Ok thanks [08:05] sorry got disconnected [08:51] Good morning, folks! Happy Repeat Day, and happy Repeat Day! 😃 === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [09:06] ogra_: lxc-android-config has ./etc/init/ureadahead.override with "manual" -- I'm confused, didn't you say we want/need ureadahead for bootspeed? [09:09] pitti, yes, look deeper :) [09:09] there are more ureadahead jobs ... [09:09] we dont have a rootfs setup like the original ureadahead expects ... ureadahead-touch re-orders the scan to take the specific mounts setup into account [09:10] ogra_: aaah! thanks, I missed that [09:10] (the -touch variant also starts a lot earlier since we do the mounting in initrd) [09:13] kenvandine, mandel, hey, I've an issue with some updates on bq/vivid, one app is listed for upgrade (umetronome 1.5), I can upgrade it and it lists "no upgrade available" but the update comes back every time I reopen the updates screen [09:14] seb128, cound that be because it targets a diff framework? I know ken did some work on that so that we did filter the contents [09:14] pitti, since i got you here :) ... do youi know if there are any plans to have support for bootchart like io-graphs (cpu/disk) in the systemd equivalent ? i find the systemd charts rather useless without that info [09:14] mandel, different framework than? [09:14] mandel, it's the same one that was listed on bq/rtm and failed to upgrade because it was requiring sdb 15.04 which was not available, but that's available on vivid [09:15] seb128, I know some apps targeted the framework in vivid when we were in trusty and that caused problems [09:15] sdb->sdk [09:15] right [09:15] but that device is on the vivid channel now [09:15] and the upgrade seems to happen fine [09:15] 1.5 is installed [09:15] frameworks are backwards compatible (at least on paper) [09:15] it shouldnt block the download/installation [09:15] ogra_: I don't understand -- what's missing on http://people.canonical.com/~pitti/tmp/bootchart-20150603-1115.svg ? [09:16] ogra_: these have more info than the ones from our "bootchart" package.. [09:16] pitti, oooh ! [09:16] how do i get that ? [09:16] ogra_: oh, were you perhaps looking at systemd-analyze plot? [09:16] yeah [09:16] thats with the init= modification, i see [09:16] ogra_: init=/lib/systemd/systemd-bootchart (see https://wiki.ubuntu.com/BootCharting) [09:16] * ogra_ hugs pitti [09:16] ogra_: ah, yes; analyze plot only knows the timestamps, there is no additional probing [09:17] (your Xorg is slow :P ) [09:17] ogra_: i. e. analyze plot is always available and has no overhead; bootchart is on request and has the usual probing overhead/slowdown [09:17] ogra_, the update installs fine, and it's installed, but it keeps being listed in the update panel still despite being uptodate [09:17] ogra_: nah, I just had to type my password into lightdm, and mistyped once.. [09:17] seb128, ah, then i misunderstood ... still though, the framework shouldnt be the issue, is your disk full ? [09:18] ogra_, no it's not, there is like 1.5G [09:18] the install looks fine [09:18] weird [09:18] anything in logs ? [09:18] unsure how u-d-m determine there is an update [09:18] the log looks like it finds an update and install it [09:18] no error I can see [09:19] ogra_, mandel, in fact that click is installed twice [09:19] aha ! [09:19] "_directory": "/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.monichols.umetronome", [09:20] "framework": "ubuntu-sdk-14.10-dev2", [09:20] "_directory": "/opt/click.ubuntu.com/.click/users/phablet/umetronome.otter", [09:20] "framework": "ubuntu-sdk-15.04", [09:20] [09:20] so I guess it finds the first one [09:20] namespace change ... [09:20] and try to update [09:20] beuno, ^^^^ [09:20] ogra_: http://people.canonical.com/~pitti/tmp/bootchart-20150603-1119.svg <- with autologin (but compiz is still slow, we know that :) [09:21] not to bad ! [09:21] ogra_: but I suppose the QEMU video driver isn't the fastest either :) [09:21] heh, yeah [09:21] pitti, 7s to loaded desktop? it's quite good :-) [09:22] seb128: well, cheating -- there's no I/O as it's a cached QEMU image [09:22] that's why CPU utilization is perfect [09:22] k [09:22] i. e. it tells us that we at least don't spend time with useless waiting [09:22] yeah [09:23] I haven't done a bootchart on my laptop for a while, I ought to do that [09:32] What's the process for approving Ubuntu Store updates for the phone these days? [09:33] I just updated tutanota-webapp.nhaines, which passed all tests. And I think the last time I had a minor update it sat around for a few days. I basically dropped the custom user agent string and added "content_exchange" to the policy groups. [09:37] seb128, that is not in our area of expertise ;) [09:38] mandel, I guess that's one for beuno? [09:38] seb128, yes, or for the click people [09:39] seb128, we just download and make calls [09:39] right [09:41] Huh, looks like it sailed right through this time. Well, thanks. :) === Guest55129 is now known as mibofra [10:18] Is there a way to configure the fron page of the Ubuntu Store to only feature apps/scopes which are available in your language? [10:18] mcphail, not yet [10:19] davidcalle: ok, thanks. Do you know if that feature is planned? [10:20] mcphail, it would make sense to have it IMHO, but I don't know if it's on the roadmap. thostr_ ? ^ [10:22] It would be good, particualryl as you can't even cut/paste the text to put through Google Translate to see what the current "Highlight of the week" is/does [10:24] davidcalle: mcphail: we don't have this on our roadmap, but from scope side this should be easy/quickly to do if we support that on the store side [10:25] thostr_: I hope the Chinese Meizu phone is a roaring success, but don't anticipate a lot of the Chinese scopes will be interesting/relevant to me without translation. As such, I hope I can screen them out [10:27] same for comments / reviews [10:28] On the bright side, the store API seems to be ready on that front (https://wiki.ubuntu.com/AppStore/Interfaces/ClickPackageIndex#Localisation) [10:28] That's good to know [10:30] * mcphail makes a mental note to include gettext support in anything he writes for the store === alan_g is now known as alan_g|afk [10:46] http://news.softpedia.com/news/Canonical-Working-to-Add-Whatsapp-and-Dropbox-as-Services-and-Not-Apps-483172.shtml [10:50] we are!? [10:52] lol [10:52] hillarious article [10:53] whatsapp service straight into the OS [10:53] brunch875: why is that bad? It won't be installed by default, but the user can choose to install dropbox as a service. [10:54] brunch875: I have seen imgur services which when installed doesnt show up as an application, but only when using content-hub as a destination to share images [10:55] I think we're not using the same definition of service [10:55] whatsapp for androis is very unsecure, i wonder how that will turnout from touch? === alan_g|afk is now known as alan_g [10:56] lotuspsychje: insecure as in others can read messages while it is being sent? [10:57] aren't they using textsecure protocol nowadays? [10:57] nik90: yeah many security flaws in whatsapp for android [10:57] libaxoctl, whatever [10:57] nik90: lucky we have telegram now === chihchun is now known as chihchun_afk [11:04] nerochiaro, there are two minor conflicts when merging your keyboard navigation branch into the latest trunk, can you please resolve them? [11:04] oSoMoN: i will be on that shortly [11:05] thx [11:27] oSoMoN: merged === MacSlow is now known as MacSlow|lunch [11:31] nerochiaro, thanks [11:40] the OTA4 looks so promising I want to jump into the devel channel [11:42] brunch875: so what's sopping you :) - easy enough to go back... [11:42] arggh, I'm just scared I might brick it big time [11:43] im on devel-proposed with nexus7 and i just love it [11:43] brunch875, how would you brick it? [11:43] * popey notes latest gets 3 more points on html5test.com over current [11:43] brunch875: all flashing carries risks, but for androidy-type things there is usually a solution to reflash through recovery [11:44] brunch875: and changing channels isn't that much different to an OTA :) [11:44] I wonder what the actual risk is, given the amount of devices and the amount of flashings between the participants in this channel [11:44] It's more or less a phobia... my first smartphone was a windows6.5; I continued with windows7 and that device bricked itself with a normal update [11:45] and I couldn't get to talk to it via USB or anything [11:45] hardbricked [11:45] but what the hell... this thing is much better done [11:45] brunch875, bq? [11:45] besides, it should help the developers debug, shouldn't it? [11:46] nah, it was an HTC mozart I think [11:46] nopf, your current device [11:46] yeah, BQ [11:46] brunch875: yes - if it hard-bricks, the devs here will buy you a new one. I'll make that promise on their behalf :) [11:46] i'll chip in [11:46] :D [11:46] $10 is what 10%? [11:47] * mcphail would like to point out he is not a dev and will not be contributing to the new phone [11:47] changing channel is _way_ less intrusive than flashing android [11:47] fine fine, you convinced me! [11:47] which channel should I get then, devel proposed? [11:47] or wait a week and get it when all the other people do :) [11:47] ubuntu-touch/rc-proposed/bq-aquaris.en is the channel I have mine on [11:47] brunch875: do you like the bq-specific apps/scopes? [11:48] euuuh, I don't really use them [11:48] in fact, I don't even think I know which ones they are :p [11:49] the only scope I really use is the news one [11:50] I'll copy popee [11:52] brunch875: I suppose the benefits of the channels with "bq" in the name is you get the HERE maps and GPS database [11:53] unfortunalely the GPS doesn't work... === alan_g is now known as alan_g|lunch [11:58] ogra_, seb128, mandel, what what? [11:59] beuno, updates list some click that needs to be updated even if it's uptodate [11:59] beuno, "_directory": "/opt/click.ubuntu.com/.click/users/phablet/com.ubuntu.developer.monichols.umetronome", [11:59] "framework": "ubuntu-sdk-14.10-dev2", [11:59] "_directory": "/opt/click.ubuntu.com/.click/users/phablet/umetronome.otter", [11:59] "framework": "ubuntu-sdk-15.04", [11:59] beuno, seems like that's installed under different names and confuses things [12:00] seb128, different names are different apps for the systems [12:00] so the developer re-uploaded under a new namespace [12:01] beuno, well, not sure what's going on but I've a "umetronome 1.5" update listed every time I open the panel, and installing it works fine [12:01] that version is installed but it keeps wanting to "upgrade" to it [12:01] so I guess the update panel gets confused by the rename and think the old name has an update when it doesn't or something [12:02] seb128, so that piece of json comes from the client, no the server [12:03] there is no rename as such, the device would see and update them separately [12:03] it's all namespace-based === chihchun_afk is now known as chihchun [12:03] if there's 2 different strings, it's 2 different apps [12:03] so something else is confused [12:04] the call to the server doesn't tell if there's something new [12:04] you tell it what apps you have, and it tells you what the latest versions are [12:05] beuno, k, I guess it's a bug in the updates panel backend and needs debugging there [12:05] beuno, I'm going to try to have a look [12:05] 2015/06/03 14:02:43 Rebooting into recovery to flash [12:05] Failed to enter Recovery [12:05] brunch@Long:~$ [12:06] well damn [12:06] * brunch875 crosses fingers and waits for de ubuntu logo to finish spinning on his phone [12:06] seb128, I can't think of what would trigger it, sorry :( [12:06] if you havent installed an unlocked recovery that message is normal [12:06] beuno, no worry [12:07] splash screens make me nervous :P I always hit ESC when booting my computer [12:08] I guess the average human is afraid of screen outputs [12:12] Aaaand the phone made it alive! Wooo! There's no doubt the ubuntu team made the flashing tool amazing [12:12] Cheers guys! [12:15] \o/ === MacSlow|lunch is now known as MacSlow [12:32] i just found that I am physically unable to write "TRANSLATORS" by using shift to make capital letters [12:32] or, err.. it could be a bug in keyboard driver [12:33] jgdx, what's the issue? [12:33] seb128, I press SHIFT then "T" "R" and then "A" and I get "TAR" back [12:34] is that on a desktop? [12:34] or osk on a device? [12:34] dell xps 13 [12:34] weird [12:34] in what editor? [12:34] how does that work, you are supposed to get letter entered in real time [12:34] gnome-terminal, gedit [12:34] what happens when you hit R? [12:35] does it input a R? [12:35] I think T and R are down simultaneously at some point [12:35] does that go back and change it when you enter the third char? [12:35] hum? [12:35] you press shift [12:35] then hit T and relase the key [12:35] no [12:35] then hit R and release the key [12:36] no? [12:36] Pilot error :) [12:36] I don't understand what you are doing :-/ [12:36] it was originally meant as a joke on myself [12:36] so no wonder :P [12:37] lol === _salem is now known as salem_ === alan_g|lunch is now known as alan_g [12:56] hum... I can't add a PIN for my phone (to enable developer mode) - I'm on devel-proposed [12:56] anyone else having the same problem? [12:57] dholbach, PIN != developer mode [12:57] uh, devel-proposed ? thats quite brave [12:57] dholbach, the developer mode has to do with password, that can be pincode or passphrase [12:57] seb128, what am I supposed to do with your reply? :) [12:57] (zero QA ... not planned to go onto phones etc) [12:58] seb128, I can't add a pincode (step 1) to enable developer mode (step 2) :) [12:58] dholbach, well, try to change the unlock mode rather than the PIN [12:58] dholbach, PIN is a SIM card thing [12:58] sorry, in the german translation it says PIN [12:58] dholbach, go to settings about -> dev mode, select the bottom item to change auth mode [12:58] can you select passphrase? [12:59] what is not working when you select a pin? [12:59] yeah, in german it somehow is "PIN" and "SIM-PIN" [12:59] yes, but when I try to set the password, it says "security mode can't be enabled" [12:59] not sure why :P [12:59] or whatever the English equivalent is [12:59] same as with the pincode [12:59] mterry, ^ do you have any idea about that? [13:00] ogra_: so I should be testing stuff on which channel exactly? devel ? [13:00] * ogra_ would just say "its wily, who cares" but i guess a few people would disagree [13:00] dholbach, seems like https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1460017 [13:00] Launchpad bug 1459730 in ubuntu-system-settings (Ubuntu) "duplicate for #1460017 passcode set on device, developer mode->lock security" disagrees" [Low,Incomplete] [13:00] ah ok [13:00] dholbach, is that the first boot after install? try to reboot [13:00] nik90, one fo the rc-proposed ones [13:00] no, not first boot [13:01] dholbach, weird :-/ maybe try to reboot anyway... [13:01] ogra_: ack. [13:01] ogra_, yeah, I disagree, wily is trunk and where most of the bugfixes land, we have a stack of improvements and fixes that are not in the vivid overlay [13:01] seb128, I just rebooted, but I'll try to again [13:01] dholbach, sorry, dunno then :-/ [13:01] seb128, dholbach: huh, reading [13:02] seb128, and wily is planned to break heavily soon [13:02] ogra_, well, we need somewhere to land fixes [13:02] unsure where that is [13:02] seb128, i wouldnt even test against any of tehse images, i have no idea who made such insane requirements [13:03] seb128, imho it should be somewhere else ... or snappy development for phones needs to be somewhere else [13:03] either way the two wont go well together i guess ... until snappy is stabilized [13:03] ogra_, yeah, just saying that atm we don't have any place where to do phone work [13:03] vivid+overlay ... [13:03] ogra_, we have fixes landing in vcs trunk, but that's mapped to no usable serie [13:03] ogra_, haha, good one [13:03] probably we should have vivid+overlay+overlay ;) [13:03] yeah [13:03] well maybe it's better after ota4 [13:04] but atm with things frozen it sucks [13:04] seb128, dholbach: not sure why that would happen specifically, seems like wizard fails to set password, but it's really weird that a reboot fixes it [13:05] mterry, let me see if a reboot fixes it over here [13:05] How can i get ubuntu touch source? [13:05] mterry, dholbach's case seems different, it's not after first boot for him [13:05] seb128, dholbach: ah [13:05] It's very urgent. [13:05] mterry, but it's the same error [13:05] How can i get Ubuntu Touch source? [13:05] It's close source? [13:05] dupingping, sources are in launchpad [13:05] or open source? [13:06] seb128, oh, sir. let me try. [13:06] dupingping, http://code.launchpad.net/ for you are interested in [13:06] dupingping, e.g https://code.launchpad.net/telephony-service to pick a random component [13:07] it shows me something. [13:07] ogra_: what's the difference between ubuntu-touch/rc/ubuntu-developer and ubuntu-touch/rc/ubuntu ? [13:07] But I could not choose anyone. [13:09] ogra_: nvr mind I see the following statement "Channel with a developer-oriented custom tarball, including extra payload useful for app-developers" [13:25] nerochiaro, there’s one autopilot test that’s broken in the keyboard-navigation branch, I’ve commented on the MR [13:28] oSoMoN: weird, they all worked when i tried them. looking [13:51] Elleo: do you have a guide of how to add layouts to the keyboard? [13:53] elopio: not really, I started writing one; but it's rather incomplete and I'm currently in the process of completely changing the way layouts are created (making them *much* simpler, and possible to be distributed as click packages) [13:53] elopio: so its probably best to wait until the new layout mechanism lands before embarking on the creation of any new layouts [13:54] elopio: as the new ones are basically just simple json files that are incredibly easy to create, instead of whole custom QML layouts as the current ones are [13:54] Elleo: ok. I want to write a simple one for Esperanto, so when you have something ready, let me know and I'll beta test it :) [13:54] elopio: okay, cool :) [13:54] Elleo: what I saw was a lot of duplication, for the normal, email and url mode. [13:55] elopio: the old mechanism was nasty in a whole number of ways, which is why I'm glad to be replacing it ;) [13:55] ok, thank you. [13:55] I'll wait. [13:57] elopio: http://mikeasoft.com/~mike/keyboard_layout.json <-- this is basically all you have to do now to create all the layouts (it's using escaped unicode in that example, but it should work with unicode chars directly embedded in the json too) [13:58] email/url are still fully defined layouts, so there's still potentially some duplication there, but overall its much simpler [13:59] Elleo: cool, +1. [13:59] yes, I see {"shifted": ["Q", "1"], "default": ["q", "1"]}, three times. [13:59] might be nice to define a section that applies to all the modes. [13:59] but that's just a detail, this is a huge improvement already. [13:59] Elleo: do you have an ETA on when that will be done? [14:00] elopio: yeah, that'd need some co-ordination with the skeyer team though, as these json files are also used to provide spatial information for much better auto-correct [14:00] oh, nice. [14:01] popey: I have stuff that roughly works for a couple of layouts (with bugs) now, there's probably another few weeks of work in it, but I have some other content-hub stuff to do this sprint, so probably won't be finished for another sprint or two [14:01] ok [14:01] Elleo: there's an old spreadsheet request about "prototype of integration with libskeyer". can it be removed or do you + bfiller want eg a wily or dual landing silo for it for testing? [14:03] Mirv: as far as I'm concerned it probably isn't needed (we can create a new silo when all this is actually ready); bfiller ^? [14:03] Elleo: it's fine to free it [14:04] Elleo: bfiller: thanks, cleaning up [14:11] ping boiko: I'm trying to make a test with UriHandler. I'm looking at your code here and trying to understand how it works: [14:11] http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/src/qml/messaging-app.qml#L153 [14:11] boiko: when you launch the application with message:///test, then that will be passed to the qml in uris? [14:12] elopio: when launching with URIs, it will be handle by the C++ code [14:13] boiko: but that's because you are calling application.parseArgument? or it will never hit this code? [14:13] elopio: that line is for when the app is already running and an URI is passed to the app via url-dispatcher [14:13] interesting. [14:14] elopio: http://bazaar.launchpad.net/~phablet-team/messaging-app/trunk/view/head:/src/messagingapplication.cpp#L84 [14:17] kenvandine, could you take a look at what I added to the punch list? [14:17] I think we'd best warn in that case as well [14:18] agreed [14:19] it's inline with what we decided for the other case [14:19] so good [14:48] popey: quick question, I flashed ubuntu-touch/rc/ubuntu-developer and it doesn't seem to have the ubuntu-sdk-15.04 framework..Isn't this the channel from which OTA-4 will be cut? [14:48] or do I need to be on ubuntu-touch/rc-proposed/ubuntu-developer to get it? [14:48] hm, I honestly don't know. [14:48] I don't think it's going to come from that channel though [14:49] more likely from a -proposed one [14:49] I will flash the rc-proposed one and check now [14:49] sil2100: will know where the image comes from for ota4 [14:50] nik90: the image will be taken from ubuntu-touch/rc-proposed/* [14:51] nik90: it will only be copied to the rc channel once preliminary tests pass [14:51] sil2100: what is the purpose of the ubuntu-touch/rc/* channel for a beta tester/user [14:51] it is the "stable" channel [14:51] Not really stable ;) [14:52] ogra_: well there is ubuntu-touch/stable/ubuntu for that ;) [14:52] The rc channel is like the preliminary place for stable images [14:52] sil2100: ah ok..I understand [14:52] So, the idea of the rc channel currently is - the stable channel in theory gets updates once per month, while RC can get those more often, we copy images there once QA is done with testing [14:52] nik90, ubuntu-touch/stable/ubuntu is a community channel ... different images [14:53] But we only copy images from the rc channel to stable once we have an OTA planned and the device manufacturers are happy with the images [14:53] (at least until we still ask manufacturers for feedback before release) [14:56] ack. === PaulW2U_ is now known as PaulW2U === chihchun_afk is now known as chihchun [15:21] nerochiaro, I found a few more functional issues on the keyboard navigation branch, commented there [15:21] oSoMoN: ok, caught up with basic auth, i will try to address them all before the end of today or first thing tomororw [15:21] nerochiaro, thanks [15:28] nerochiaro, unrelated, but there are conflicts when merging https://code.launchpad.net/~uriboni/webbrowser-app/merge-url-functions/+merge/257641 into trunk, when you have a moment can you resolve them? [15:30] oSoMoN: wow, that's an old one [15:31] yeah, it had fallen off my radar, let’s try to merge it with the next landing === dandrader is now known as dandrader|lunch === chihchun is now known as chihchun_afk [16:08] tedg: I now can launch the application with url-dispatcher. But if the application is already opened, and I call url-dispatcher on it, it's closed. [16:08] should that scenario be supported with what you told me to do? [16:11] DAMNIT! This wifi is terrible! Is tethering implemented yet? [16:16] elopio, Is it focused? And then you're sending a new URL to it? [16:17] yes, and yes. [16:17] brunch875, it is real close [16:17] wifi hotspot that is [16:17] i think usb tethering already works... if you know the magic to enable it :) [16:18] mlt, hi [16:18] tedg: yes, and yes. (forgot the ping) [16:19] elopio, So that could be a shell bug, we just in that case ask for it to be focused. Not sure what they do with an app that is focused that focuses again. [16:19] tedg: let me try unfocused. [16:32] why is adb so fidgety on devel-proposed? [16:33] dobey, because devel proposed isnt for using it ? [16:33] thats wily [16:33] (probably adb knows that :) ) [16:34] ogra_: right, and i am trying to test stuff for landing in wily. but i don't see why adb would be affected and my phablet-shell session would keep getting disconnected [16:35] yeah, i dont know either ... i really dont get how we can say on one hand "wily isnt for phones" and also plan to break it to a point where it will be unbootable for a while and at the same time ask people to test there [16:36] ogra_: well, i guess we can't really break it to the point it's unbootable, since proposed migration blocks on a boot test for things that are shipped on the phone images? [16:36] we will have to [16:37] else we wont be able to switch to snappy [16:37] anyway, we aren't at that point yet [16:37] at some point we will need to replace the initrd [16:37] so i don't see why adb is having issues *now* [16:37] i dont either [16:37] what device is that [16:37] mako [16:38] well, i dont think anything changed in adb since several months [16:38] right, and the android bits are the same as in vivid/rtm images, no? [16:39] in facct adb hasnt even been rebuilt in wily [16:39] oh [16:39] the android package has though ... but only for dropping the remaining dead code of grouper [16:39] hmmm [16:40] (and it hardcodes its own toolchain, so shouldnt be binary different to vivid) [16:44] dobey, if it would be really flaky i would expect plars to scream and shout though ... could it be your host ? [16:45] ogra_: i guess it could be, but i've only just started having these issues the past couple of days (granted, i haven't actually done any testing on the device for a while, and was on vacation last week) [16:46] dobey: ubuntu-touch/devel-proposed/ubuntu seems to be booting on mako ok for the most part [16:47] plars: yeah, it boots and works mostly fine for me. i'm only having a problem with adb being flaky while i'm trying to use phablet-shell [16:47] 214 at least got that far, but we did have some test failures it looks like. As for the boottest process, that only runs on krillin [16:47] or maybe it's not adb that's flaky, but sshd? [16:47] ah [16:47] dobey: for smoke runs, we do things over adb. I have problems with ssh a lot to phones here lately when trying to mess with adt-run and boottest though [16:48] lots of adt-run failures with 255, which means some command it was running over ssh died because of ssh I believe [16:48]