[00:00] if you swipe back up to the top of the screen it will make the network indicator disappear [00:02] Is it possible to add my google contacts yet? It says that I should go into the accounts in system settings but there is only twitter and facebook there [00:02] there is a command line tool to do it [00:02] is there a thread with useful command lines such as that? [00:03] http://sergiusens.github.io/posts/google-contacts-on-ubuntu-touch.html [00:11] I keep getting this error "bash: ubuntu_chroot: command not found" [00:11] Anyone synced repos and try building again? Mine's having an issue with the ubuntu-boot.img file not being present. Started looking around but just wanted to see if anyone else had this issue [00:12] murrayuk: ahh interesting, where are you seeing instructions to use ubuntu_chroot? [00:12] we no longer need that [00:13] Ah okay, it was on the link you gave me :) [00:13] * popey pokes sergiusens to fix that [00:14] * sergiusens thinks about updating blog entry [00:14] \o/ [00:14] is there a default sudo password for the phone? [00:15] phablet [00:16] I'm getting this error now "[INFO] addressbook: looking for databases... [00:16] [ERROR] GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed [00:16] [INFO] addressbook: backend failed [00:16] " [00:29] cyphermox: you said that by now i can roam nicely between 3g and wifi? [00:29] e.g. is it worth me giving that a try? [00:31] yes [00:31] ok cool [00:31] todays image has 3g on by default [00:31] let me double check i have the latest image [00:31] s/today/yesterdays/ [00:31] how can i find that out without installing latest? [00:32] well let me just flash and be safe [00:32] heh [00:32] if i could remember how to tell, I'd tell you, then put it in the FAQ [00:32] still would love to be able to see the build id somewhere in the UI :) [00:32] or shell [00:32] its in a file somewhere, i just dont recall where [00:32] popey: yeah. no problem my memory is at least as bad as yours :) [00:33] we are just old [00:33] so true [00:33] interesting ... so phablet-flash didnt download anything, just went directly to flashing... guess that means i had the latest :) [00:33] /system/ubuntu_stamp [00:34] yes [00:34] which means you could CTRL+C [00:34] it is already pushing [00:34] i am scared that it will be trashed [00:34] you can kill that [00:34] ok done :) [00:34] thats just like ftping a file up [00:34] and now? [00:34] reboot [00:34] just pull power? [00:34] adb reboot [00:34] nice ... screen is off :0 [00:35] now it boots [00:41] ok the wifi indicator is still bogus i guess ... i am connected against a 70/70 AP and its completely black. but i can ping [00:41] nm-tool [00:41] i find that the best way to see what connections i have [00:42] cool... both are connected :) [00:42] wonder if thats good for power consumption ... is that also the case on android if i am on wifi? [00:44] bfiller: when is "remember password" for webbrowser targetted? [00:45] * asac goes for smoke [00:47] alright, unlocked my galaxy datt, time to ubuntu touch it up [00:49] anyone done this before and want to walk me through it, first time ever. not a dev [00:49] asac: 3g eats battery way more than wifi === chriadam|away is now known as chriadam [00:56] popey: right... hence i thought that on android they go to pure phone and turn off 3g if you hit wifi [00:56] while here it seems we have now both cooking :) [00:56] ok going for real :) [00:56] bbib [01:12] Hi, Just dropped Ubuntu touch onto Nexus 4. I'm having issue making phone calls though when i press the dial button nothing happens. [01:12] Did i do something wrong? [01:14] anyone here? [01:15] people are here === SkavenXX^ is now known as SkavenXXI-[OFF] [01:16] ok thanks Rob [01:20] must be busy [01:20] shouldn't have a problem with making a call [01:20] I was on 0708 build and it was ok [01:25] zdlite, do you have a pin on your sim === arussello is now known as anthonyr === anthonyr is now known as lyric340 [02:03] Hi, I'm just getting started and involved, is the data for maguro accurate (https://wiki.ubuntu.com/Touch/Devices/Nexus)? [02:07] lyric340, that page is a bit out of date, maguro is a primary reference so support there will be as good as any device === dlan is now known as dlan_ [02:14] @pmcgowan, Thanks for the heads up. Is there any documentation on what is not working on Galaxy Nexus? === dlan_ is now known as dlan [02:15] I'm looking for an area to help... [02:15] lyric340, not really an up to date list, better to ask here, the PIN support just landed for example [02:16] lyric340, happy to have help, whats your interest [02:16] I'm a little more partial to kernel/HAL layer when working with Android, but interested in looking at Ubuntu Touch as a whole. [02:17] lyric340, did you get on the email list as well? [02:18] ubuntu-phone@lists.launchpad.net [02:18] @pmcgowan, not yet. I have only just now pulled the code, and begun setting up my environments and keys. [02:19] lyric340, we are using much of he HAL so thats good [02:19] most of the devs are offline this evening [02:19] @pmcgowan, I'm in the market for a new phone to free up my galaxy nexus for work on this. [02:19] great [02:20] Okay, I'll sign up for the mailing list, and then plod through the code and read through the mailing lists. As soon as I can get a replacement phone, I'll wipe and flash my galaxy nexus and begin more in depth work. [02:20] reflashing is pretty straight forward but it wipes android so its all or nothing [02:20] good [02:22] lyric340, anything that is working will work on the nexus so its a good device to use [02:22] Exactly why I need the replacement first... [02:23] ok [02:23] @pmcgowan, All signed up, I have some reading to do. Thank you so much for your time this evening. [02:24] ok will look for you next time === ssweeny` is now known as ssweeny === balloons_ is now known as balloons === daker_ is now known as daker === Aww_ is now known as EvilAww === chihchun_afk is now known as chihchun === jono is now known as Guest7396 === Gh0sT_ is now known as mahabal === Mirv_ is now known as Mirv [04:53] hello? === Namidairo`bnc is now known as Namidairo [06:18] if I can get into ubuntu touch chroot but my screen is black [06:18] how do I fix this, can I post/view logs that will help find whats wrong === pipedrea1 is now known as pipedream [07:06] hey all, does anyone know if awe's PIN support is in the current build if I do phablet-flash now? [07:06] or do I need to wait for popey and ogra to validate the image? [07:09] didrocks, ^ do you know? awe's mail said something about "today's image" [07:10] rickspencer3: no, I'm more reviewing our work to publish as much as packages as possible, didn't flash before ogra or popey gives the green flag :) === Namidairo is now known as Namidairo`bnc [07:16] didrocks, ok [07:16] didrocks, I thought they were going to validate the image and the move it to current [07:17] so you couldn't get an "awful" image with phablet-flash [07:17] did I understand that correctly? [07:17] rickspencer3: I understood that too, so if you're wrong, we both are :-) [07:18] (not sure it's a good relief though ;)) === Namidairo`bnc is now known as Namidairo [07:18] :) [07:19] didrocks, should be interesting to see how it goes when all the auto-pilot tests are being run on the daily images [07:19] rickspencer3: well, TBH, I don't expect that much difference as explained in the email as we already run 80% of them in daily releases [07:20] (but better once we will be able to run then on the hardware) [07:20] didrocks, I think we will see issues [07:20] they are, the apps stacks have tests failing for 2 days for instance [07:21] I think running the tests on the daily image will cause back pressure to ensure that the daily upstream releases are good [07:21] but you shouldn't see those as the components are then blocked for release [07:21] I suspect it will make your job easier [07:21] I hope so as well :) also, it's another data point to try to ducktype where the breakage happened [07:21] if it passed dailies [07:21] didrocks, also, I think adding the existing testes are just a start [07:21] and then it's broken, we'll see that it's something else from distro [07:21] we can use auto-pilot for testing all kinds of things [07:21] didrocks, exactly [07:21] integration testing is a good thing [07:22] yep :) [07:22] and if it goes smoothly because the individual stacks are well tested, that's also a good thing [07:22] the key will be our speed in which we respond to test failures [07:22] rickspencer3: we always take latest image with otto (and dist-upgrade in the morning), so we already catched several times regression from distros impacting us. [07:22] yep, agree on the speed to respond to issues [07:24] didrocks, yeah, like asac said, it will be good if we get to green quickly because of the work you already did [07:24] I think running the tests that we already have is step 1 [07:24] step 2 will be adding new tests [07:24] step 3 will be making it simple to run the tests in emulation, for developers and in the lab [07:24] imo [07:25] yep, totally agreed that step3 is a little bit too hard still for developers [07:26] or just to be able to reproduce the env localy even [07:29] didrocks, that's longer term ... I think our focus on daily quality right now is the best way to go, rather than waiting for magic tools to be developed ;) [07:29] but we'll get to step 3, I am certain [07:30] right, but I really think we need to have better manual testing right now [07:30] like what we did for unity [07:30] write a lot of manual tests, that we do for every release [07:30] then, those manual tests would be transformed into autopilot tests [07:30] that will ensure we always have a consistent phone image, knowing exactly the scenarios that works [07:31] (and if we discover a new one failing, extending the manual test doc) [07:35] hi [07:40] popey: maybe that will make sense to you to ease your dogfooding task, thoughts? ^ [07:41] good morning [07:44] rickspencer3: as I understand it phablet-flash currently doesn't pull from "current" but latest image on cdimage, it would need to be patched to do that. I don't see a bug filed for that https://bugs.launchpad.net/phablet-tools [07:44] hey popey [07:44] so if I phablet-flash now I can try the PIN support? [07:44] when did PIN support land? [07:44] the latest image on cdimage is yesterdays [07:45] popey, in awe's mail to @ubuntu-phone he said something about "today's" image [07:45] oh, not opened email yet [07:45] * popey does so [07:47] asac, ping [07:48] rickspencer3: I just apt-get update and apt-get install ofono-scripts on my phone which has yesterdays image [07:49] which would be "today" by awe's timezone [07:49] popey, so should I try phablet-flash? [07:50] did you flash it "yesterday"? [07:50] well you'll need to apt-get install ofono-scripts anyway, because that's not in the build (yet) [07:50] you certainly could phablet-flash if you want a clean start [07:51] popey, ok [07:51] In a bit I'll install the ofono-scripts and give it a try [08:04] didrocks: do you know of any manual tests we already have for any of the phone components? [08:04] ah yes, on the QA tracker [08:05] popey: yeah, it's quite limited, but it's a good starting base [08:05] * popey was looking in text files, silly me [08:12] rickspencer3: btw, what about putting on the dashboard the daily release tests result as well? [08:13] I think it will be valuable to see what failures blocked landing on some components [08:13] didrocks, wfm, but I guess talk to gema about that? [08:13] gema: ^ [08:13] didrocks, I think it would be good if you see a failure on the image, if you could see easily if the failure was on the daily release [08:13] didrocks: what testing are you referring to? autolanding? [08:13] rickspencer3: right, to see the diff :) [08:13] so you would quickly know if it's a pure upstream or an integration issue [08:14] gema: daily release, yeah [08:14] rickspencer3: exactly! [08:14] didrocks: we are working on that with the PS QA folks, the views are not quite where you can compare things straight away but we are working on it [08:14] gema: ah, so you will publish soon the daily release tests status as well? great! :) [08:15] didrocks: yep [08:15] great :) [08:15] didrocks: we'll land a first version soon and then we can work on making it better for your needs [08:15] didrocks: I am chasing your devices today [08:15] gema: excellent, that will be of a great help, thanks! [08:15] didrocks: the very least I am going to make one or two of the ones we already have available for your testing [08:16] and speed up the set up of the new ones [08:16] didrocks: next time ping me earlier, plz :D [08:16] gema: we opened a RT in may as requested, but I guess with pgraner transitionning and so on, the requests and pings were lost :) [08:17] didrocks: it's been quite busy, yep, but I wasn't on copy on that RT so I completely missed that [08:18] didrocks: I had been naively waiting for a while and thought you were busy with something else, rather than waiting for the devices [08:18] gema: well, I think otto will need some adjustement once in prod, but with our local devices, it's working fine [08:18] as we always refresh with latest images, but only provision once, it's fast as well :) [08:18] didrocks: yep, but to be able to adjust in prod you need something to run on [08:19] exactly ;) [08:19] didrocks: will let you and jibel know later today [08:19] thanks! [08:19] np [08:36] I can get into ubuntu touch chroot but my screen is black [08:36] how do I fix this, can I post/view logs that will help find whats wrong [08:37] I'd even be willing to offer VNC remote desktop if someone could assist with this === djcanadajeff is now known as djjeff === schwuk_away is now known as schwuk [09:02] do we have any way to lock screen rotation at the moment? === schwuk is now known as schwuk_away [09:03] Good morning all, happy World Population Day! :-D [09:03] is that going to be a Mir feature? do we have an api somewhere in the stack to read/set the screen rotation locking? [09:18] hmm, i wonder why the image doesnt finish today [09:18] seb128: we did have a tiny daemon doing screen rotation on nexus7-X, not sure if we have same for surfaceflinger.... [09:19] ogra_: still running or crapped out? [09:19] xnox, I doubt the solution used there works on the touch image [09:20] no, the rotation is managed through androids sensor service via platform-api [09:20] tvoss_, ^ do you know about that? [09:20] and hybris [09:20] seb128: yeah... i wouldn't expect it to..... [09:20] xnox, what's the use case you want to solve? [09:20] no idea if we can lock it already ... probably via a property (try getprop if you see anything rotation related) [09:20] tvoss_, I was the one asking [09:21] tvoss_, I'm trying to figure what I need the system-settings "lock screen rotation" switch to [09:21] tvoss_, I'm trying to figure what I need to plug the system-settings "lock screen rotation" switch to [09:21] popey, look like it is still running .... i'm probably just impatient [09:21] seb128, hmmm, should end up somewhere in the shell. saviq, can you help out here? [09:23] tvoss_, seb128, well, we have no such thing yet [09:23] I can't unlock my phone anymore after apt-get upgrade this morning. Is there a way to unlock the screen from shell? [09:24] Saviq, so all apps listen to the rotation sensor? [09:24] Saviq, is that on a roadmap (Mir, shell, platform api, ...)? [09:24] tvoss_, yes [09:24] Saviq, I think we should put it on the roadmap [09:25] tvoss_, and I still don't know how we can communicate with the app for that (and other questions the shell might need to ask the app) [09:25] tvoss_, I've asked many times, didn't get no answer [09:25] we == shell [09:26] m-b-o: i dont see that issue. do you not get the launcher when you pull in from left? [09:26] i upgraded then rebooted and it's fine [09:26] Saviq, ack. I was wondering if it would make sense for the shell to "own" the device rotation system setting, with apps listening to it [09:26] s/system setting/system property [09:27] tvoss_, still, what if the app doesn't support the orientation you've locked in? [09:27] Saviq, up to the app to not react to it [09:28] tvoss_, let me find a doc [09:28] Saviq, ack [09:28] ah, there is the image [09:33] popey: I can't turn on the screen anymore, when it's gone black after idling. [09:33] m-b-o: can you adb shell in over usb and see if unity8 is running? [09:33] popey: and I can't turn of the screen when using on/off button. it fallsback to the lock screen, the screen dimms some times and turns off [09:34] unity8 is running [09:34] and when i click the on/off button, cpu load is on unity8 [09:35] if you adb shell in and look in /home/phablet/.ubuntu-session/logs - anything interesting? === mote is now known as Guest32532 [09:37] popey: nope [09:37] m-b-o: rebooted it? [09:39] several times. only came up after some persuasion and after the battery was removed [09:40] erk [09:40] you are using the latest flipped image? [09:40] i.e. when you "adb shell" you get an ubuntu root prompt, not an android one? [09:41] haven't tried adb, was ssh'ing [09:41] ah ok [09:45] popey: have a gnex. using on/off key, screen falls back to lock screen instead of getting switched off. can swipe away lockscreen. when on lockscreen and doing nothing, screens dimms slowly before getting switched off [09:45] ogra_: does your gnex do the above after an apt-get upgrade? [09:46] image is from end of last week, flashed via twrp [09:46] ah [09:46] you probably want to flash newer, 20130710 - or wait for todays image a bit later [09:46] the powerd upstart job moved today [09:46] oh, todays image arrived [09:47] yeah [09:47] http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/20130711/ [09:47] * popey flashes [09:47] i said so above, but didnt ping you, sorry [09:47] np [09:47] so you did [09:54] ogra_: out of interest, what will we do at weekends, still flash and manually move to current? (I am happy to do that) [09:54] hmm, good question [09:54] given saturday image may well have friday crack / fun in it [09:54] and for some saturday is a good day to flash [09:54] well, i hope we wont have to do that for more than one weekend [09:55] you're expecting automation? [09:55] i know plars_ is working on fixing automated testing [09:55] ok [09:55] yes [09:55] happy to do it until that happens [09:55] there are a few parts missing on the build side too ... i'm just trying to fix them [10:00] \o/ German SIM with PIN is working! [10:01] yay [10:01] ogra_: flashed 20130711 to mako, made phone call, browsed web, started some apps okay [10:01] great [10:02] however I am now seeing what m-b-o reported [10:02] rickspencer3, yay [10:02] can't wake/unlock the phone from slumber [10:02] check syslog for powerd [10:02] (and check if powerd runs at all) [10:02] dmesg | grep powerd returns blank [10:03] Jul 11 09:55:28 ubuntu-phablet kernel: [ 1.225118] sp_tx_vbus_powerdown: 3.3V output disabled [10:03] Jul 11 09:55:28 ubuntu-phablet kernel: [ 1.283290] sp_tx_hardware_powerdown: anx7808 power down [10:03] Jul 11 09:55:49 ubuntu-phablet kernel: [ 26.221455] init: powerd main process (446) killed by SEGV signal [10:03] Jul 11 09:55:49 ubuntu-phablet kernel: [ 26.257836] init: powerd main process ended, respawning [10:03] Jul 11 09:55:50 ubuntu-phablet powerd[1133]: Using backlight at /sys/devices/i2c-0/0-0038/backlight/lm3530 [10:03] oops [10:03] same on nexus 7 [10:05] do you see it in the pprocesslist ? [10:05] it seems to have respawned [10:05] yes [10:05] root 1133 0.0 0.2 71624 5404 ? Ssl 09:55 0:00 /usr/bin/powerd [10:05] hmm, thats weird [10:06] https://bugs.launchpad.net/touch-preview-images/+bug/1200156 [10:06] to track it [10:06] Ubuntu bug 1200156 in touch-preview-images "Can't wake phone from sleep" [Undecided,New] [10:06] i used to ship a powerd.override job before ... but that was completely moved over into powerd now [10:06] wonder who got bug 1200000 [10:06] bug 1200000 in Midori "about:version should include activated extensions" [Medium,Confirmed] https://launchpad.net/bugs/1200000 [10:07] it shold behave exactly the same still [10:07] ogra_, popey: is there an issue with network manager? Since the 3g auto connect thing has been in place the wifi list hasn't been populated. Or has been but sporadically [10:07] popey: anything useful in /var/log/upstart/powerd.log ? [10:07] __pthread_gettid -2 [10:07] __pthread_gettid -2 [10:07] "no" [10:09] * ogra_ waits for his flash to finish [10:09] davmor2: can't tell right now as my phone is a bit borked [10:10] m-b-o: could you confirm bug 1200156 [10:10] bug 1200156 in touch-preview-images "Can't wake phone from sleep" [Undecided,New] https://launchpad.net/bugs/1200156 [10:10] popey: is that a hint not to upgrade this morning [10:10] yes [10:10] popey: yes [10:10] thanks [10:11] popey: thanks for the hint I was going to flash my devices after reading emails :) [10:11] always worth checking in here first ☻ === Guest66824 is now known as sash_ === sash_ is now known as Guest1089 [10:13] Hi guys,anyone knows when the phone function is going to be usable in denmark ? [10:14] mcute: should work in any region that has GSM [10:14] popey: then that bug's important is quite high, I'd say critical [10:14] i can recieve calls, but cant make them :) [10:15] mcute: what is the problem with making a call, are you trying to call a normal number or a services number? === Guest1089 is now known as sash_ [10:15] gema: Naaaaaaaaaaaaa it's only a flesh wound [10:15] gema: fixed === valleycat is now known as arya [10:15] popey: it's fixed?! that was quick :D [10:15] hah [10:16] i wish [10:16] a normal cell number..it just goes to voicemail, no matter who i'm calling [10:16] mcute: what happens when you call a home number? [10:17] didn't try that, don't know anyone that uses one : ) [10:17] heh [10:17] mcute: haha, can you tell me what image you are using? [10:18] don't recall the version number, but its for the n4/mako [10:18] when did you flash it ? [10:18] and it was a week ago i had it on [10:18] mcute: phone me! :D [10:19] Note: I am not in Denmark. [10:20] i did talk on the phone while using it...but coldn't make a call, straight to voicemail and then they would call back [10:20] k, doesnt suspend here either on maguro [10:21] restarting powerd doesnt help apparently [10:21] i doubt it is related to the upstart job [10:22] ogra_: needed to talk to you about the manual testing you guys are doing and was wondering if we could automate that and hook those tests to the publication of the images like we do with desktop [10:22] ogra_: it'd help to know everything you guys are verifying as a minimum [10:22] gema, i think plars_ was already working on it [10:23] ogra_: yes he is, the problem is that I don't think our default tests as they are cover all you need [10:23] gema, flashing, booting, starting an app and looking around if the shell is populated is what i do [10:23] or I don't know if they do, rather [10:23] i guess popey also tries a call [10:23] ogra_: what action should get triggered when pressing on/off key? [10:24] uhmmm... maybe we should add the phone-app tests to the default job that'll run on every image [10:24] m-b-o, powerd should recieve a message via dbus and switch the backlight on/off (and some other stuff) [10:24] i called earlier, yes [10:24] it worked but the phone app was very laggy [10:25] gema, i think there is a test suite for the coreapps, when we had a broken image recently they properly all failed for asac [10:25] i guess that would be a good one to run [10:26] beyond that, my tests are very visual (check if the lenses in the shell are all populated for example) not sure how to automate that [10:26] ogra_: there's several for the core apps [10:26] we're mostly doing shakedown tests [10:26] to make sure it's not catastrophically broken [10:26] ack [10:26] today i flashed, booted, launched 5 apps, dialled a number, made sure internet worked [10:27] popey: whenever we switch to automating checking, we may miss some of the things you guys are checking until all the tests are working properly [10:27] i dont plan on stopping doing my daily shakedown [10:27] because I'd like to hook them up to stop images only when we are happy that they work as expected most of the time [10:27] I've been doing them for weeks already [10:27] popey: yeah, but if we hook up the automated tests to daily images they'll get published based on jenkins' feeling, not your testing [10:28] popey: even though you can continue to do your testing afterwards [10:28] you may find some problem has escaped us [10:28] well maybe we should throw some deliberately broken images at jenkins and see whether it passes them or not [10:28] e.g. todays and 20130709 [10:29] because if it passes really bad images then i dont think it can be trusted to gate the images [10:29] popey: http://reports.qa.ubuntu.com/smokeng/saucy/ [10:29] * popey has a mirror of past images you can throw at jenkins:- http://popey.mooo.com/mirror/ [10:29] it does [10:29] well, today's results are not there yet [10:29] wow look at all those passes for 20130709 [10:29] thus proving my point [10:29] popey: yes [10:30] and my worry [10:30] that should have red lights on it [10:30] that's why I want to improve those tests [10:30] ergo we should not trust it yet [10:30] popey: what was broken on the 9th image? [10:30] I'd be happy to video myself doing a morning test so you can see exactly what I do, because I may not describe it well ☻ [10:30] gema, the shell [10:30] shell didn't show any dynamic content [10:30] popey: that'd be super useful [10:31] alright, will video it tomottow === schwuk_away is now known as schwuk [10:31] -typos [10:31] popey: ack [10:32] gema: I do a heavier shakedown on an evening as I use the galaxy nexus and n7 as my daily devices where I can. [10:32] I miss youtube play back though :) [10:33] davmor2: that's good, I need to make sure you don't get broken and your evening entertainment obscured by bugs then :P [10:33] davmor2: although you being you, you'll find other bugs :) === chriadam is now known as chriadam|away [10:33] gema: It's me they could say it was perfect and I'd find the only bug :) [10:34] davmor2: yep, and I'd find the one after you no problem :P [10:35] gema: hahaha [10:35] this is true [10:35] hmm [10:38] dpm: hi! Regarding the docs you uploaded for me yesterday - do they update automatically with distro releases of the -doc package? === dandrader is now known as dandrader|afk [10:40] ʘ‿ಠ [10:43] ogra_: coloured output of android build looks "funny" in launchpad build logs.... =) but waiting for it to build and hopefully not fail like last time. [10:44] xnox, yay [10:44] ogra_: who should we poke with that bug? [10:44] popey, working on it [10:44]