=== salem_ is now known as _salem === chriadam|away is now known as chriadam === chihchun_afk is now known as chihchun [06:32] Hi all [06:37] Cheesy wheezhy === cedian_linux is now known as Procyionidae === chriadam is now known as chriadam|away [06:58] finally os updated to 15.04 [06:59] is there a link to see what did update and what is new? [07:10] bqphone: more or less OTA-4 changelog is https://insights.ubuntu.com/2015/05/29/phone-updates-may/ [07:10] thx [07:10] yw [07:30] good morning [07:32] mzanetti, sil2100, dholbach: Ping [07:33] hey SturmFlut [07:34] Hey [07:35] sil2100: Did you reach barry yet? [07:36] SturmFlut: sadly no... he's in the US timezone, so we'll have to wait for a few more hours [07:36] Yesterday he had a day off I think [07:36] sil2100: Argh, right. stupid timezones [07:36] The phasing period is about to finish in 2 hours, I just hope there was nothing really broken in the previous s-i [07:37] And, well, not much we can do for an already-released image, we'll just have to make sure we get all the fixes for the next one [07:37] But damn... [07:40] sil2100: I came across another bug that can be annoying, the whole display framebuffer seems to be shifted to the right by one pixel on krillin sometimes. It happened to me on three out of ten reboots. I already talked about it with mzanetti, seems there is no fix yet. [07:44] sil2100: The only problem I ever had with older system-image versions is that when I first got my krillin, it simply wouldn't automatically update from r16 to r20. I remember that there was a small amount of people who either had to wait for a long time until it finally came to its senses, or you had to run system-image-cli often enough. I don't remember system-image ever being broken in a way that would prevent updates at all. So if OTA-4 [07:44] really shipped with an older version of it, it will either just work or there will be some people who have trouble updating to OTA-5. === danielg4 is now known as DonkeyHotei === Procyionidae is now known as cedian_linux [07:58] Ping SturmFlut [07:58] cedian_linux: Pong [07:59] SturmFlut: pang [07:59] Can you implement any bash script in an app for UB touch? [08:00] I'm installing Ubuntu 14.04 [08:01] sil2100, wow, if the vivid-changes ML doesnt lie then system-image was never uploaded to vivid [08:04] Data about changes never lie Ogra_ [08:05] ogra_ ^^^^^^ [08:06] cedian_linux: You can ship a bash script with your app, yes, and you can run it, but you are running under confinement and are restricted by the App Lifecycle. [08:07] so this is whats in the archive https://launchpad.net/ubuntu/+source/system-image/2.5-0ubuntu1 ... now thats really old [08:08] SturmFlut: I had the same issue with the old s-i that you mentioned when I first got my krillin...somehow it managed to update to OTA-3 at the very end. [08:08] at least the rtm uploads should have been parallel landings [08:08] hmm [08:09] ogra_: I hate it when I'm right. I have a tendency to immediately hit such problems when I start to dig a bit :/ [08:09] ogra_: But if it's just an old version, and not a broken one, things will probably not be so bad [08:09] SturmFlut, yeah, that was a really bad one :/ [08:10] well, its a pre-release version ... [08:10] the rtm version has a bunch of important fixes that never went into the archive [08:11] https://launchpad.net/ubuntu-rtm/+source/system-image [08:11] one upstream bump and two ~rtm uploads [08:12] https://launchpad.net/ubuntu-rtm/+source/system-image/2.5.1-0ubuntu1~rtm1 [08:12] this is missing ... [08:13] and https://launchpad.net/ubuntu-rtm/+source/system-image/2.5.1-0ubuntu1~rtm2 [08:13] ogra_: I can already say that the phased update logic is broken, the function that calculates the value the client uses to decide if it should do the update does not spit out a fixed value, but it changes on every call. That will probably result on updates not being evenly distributed over the phasing period, but that would most likely only mean a higher load on the servers. [08:14] That's how I realised that things are not right, I had seen the code shipped with OTA-3.5 and that one was correct [08:15] the second one is more worrying ... but only if this image gets factory flashed [08:15] On Ubuntu 14.04 mingw32 exists [08:17] ogra_: Oh, right [08:18] SturmFlut, that pixel shifted to the right has been there in 14.10 already [08:19] ogra_: 2.5.1-0ubuntu1~rtm1 fixes the phased update logic I was talking about, I think we can live without that [08:19] SturmFlut, yes [08:19] but ~rtm2 does the reset after factory tests i guess [08:20] mzanetti: At least on my device it has never happened before, and I did a *lot* of reboots [08:20] SturmFlut, i get it once every other month :) [08:21] same here ^ [08:22] SturmFlut, well, if you figure how to repro it, let us know [08:24] mzanetti: Will do [08:30] mzanetti: I had a feeling that it happens more often if I had booted into recovery before, but couldn't confirm that yet [08:38] I've found out you can install armhf debs [08:45] cedian_linux: unfortunately "can" and "should" are mutually exclusive :) [08:45] Yeah mcphail [08:45] I'm syncing repos [08:46] cedian_linux: building a system image? [08:46] Yeah trying to help mariogrip again macphail [08:46] neat [08:47] I installed Ubuntu 14.04 instead of 15.04 on my laptop [08:48] Because things don't work out on Ubuntu 15.04 I was still on the newer is better train, but it has proven false again [08:55] Good morning all; happy Fresh Veggies Day! 😃 [09:03] JamesTait where? [09:04] cedian_linux, https://www.daysoftheyear.com/days/fresh-veggies-day/ Here! [09:05] JamesTait I meant in which country [09:05] mzanetti, so with rotated shell i often end up with only shadows of apps in the spread [09:06] huh [09:06] cedian_linux, in internet country :) [09:06] hadn't seen that yet [09:08] mzanetti, here is one http://i.imgur.com/0YDXG2e.jpg === vrruiz_ is now known as rvr [09:08] (hard to see but it is between the dash and G+) [09:08] odd... ogra_, any way to repro? [09:09] i just have a few webapps open and switch between them [09:09] cedian_linux, what ogra_ said. ☺ I doubt it's officially recognised anywhere. [09:09] we need to adjust the screenshooter ... that shot was taken in landscape ;) [09:10] mzanetti: I see that now and again, I think the last time was a content-hub window that maybe hadn't had it's process fully stopped [09:10] ogra_: ^ [09:10] ohh [09:11] davmor2, only since shellrotation? or had that before too? [09:11] right, it seems to happen with all webapp windows where the app got suspended for me ... if i tap the shadow the app comes up black and then reloads the page after a bit [09:11] mzanetti: had it before [09:11] uhhh [09:11] interesting [09:12] I'll look into it, thanks guys! [09:12] * mzanetti should use more webapps, but usually I get so annoyed by them that I rather write a native one [09:12] also it feels a bit weird that the spread is copmpletely unresponsive if you rotate the device while it is open [09:13] (not sure there is much we can do ) [09:16] OTA4 seems very slick right now. Thanks everyone! [09:30] JamesTait sad it isn't recognized [09:31] cedian_linux, true. But we can still recognise it here. ☺ [09:37] I still haven't received OTA-4. My current config looks like: http://pastebin.ubuntu.com/11723980/ And when I try to force the update I get: http://pastebin.ubuntu.com/11723998/ [09:38] I'm guessing my device is pointing at the wrong channel? [09:38] JamesTait, you just didnt win the lottery yet :) [09:38] the phasing takes 24h [09:39] only 12-14 are over yet i think [09:40] ogra_, but even with --percentage 1? Is it correct that https://system-image.ubuntu.com/ubuntu-touch/stable/ubuntu/mako/index.json still only shows version 19? [09:40] * mcphail feels smug [09:42] I totally lost track of the email threads about images and devices and renames. [09:47] JamesTait, ah, i dont think the community image got released [09:47] sil2100, ^^^ should that get a release too ? [09:52] Me feels smaug [09:52] Or do I just need to switch channel? [09:53] hm, let me discuss that with QA [09:54] Since I only promoted the mako device in the bq-aquaris.en channel, didn't know if QA checked the ubuntu images [09:55] Fails to build apparmor can't find apparmor.h in the same directory :( [09:56] While it's in there [10:01] ogra_ is it just me that doesn't want to win the lottery === mvo__ is now known as mvo [10:39] ogra_: Phasing was already at 90 percent at nine o'clock this morning [10:39] ogra_: According to the server it is finished now [10:40] Yeah, it should be done now [10:44] ah [10:44] i thought it takes 24h [10:50] Can the update server tell how many devices are still running utopic? [10:51] probably, but I doubt we publish that data [10:52] hm, 15.04 and still upstart [10:52] if you know the total amount of devices you can indeed easily make a diff and check the amount of upgraded devices [10:52] Sleep_Walker, no systemd for phones until they switch to snappy [10:53] ack [10:54] Not a big issue just now (relatively small amount of users) but would be good to know in future so we know when to drop old frameworks [10:55] I would imagine most phones are either a) updated, b) switched off [10:55] so updating your framework to 15.04 should be fine :) [10:57] popey: It would be nice to get some relative numbers after a while, like what percentage of the phones that regularly contact the system-image server are on which image. Just so we developers get a feeling for how long we have to wait after an update until we can bump the framework of our apps and upload a new version to the store [10:58] but if you update your app, the user will not see it until they go to system settings -> update [10:58] and then they will see the system update anyway [10:58] So IMO right now, with all phones getting 15.04 updates, it's rather moot, surely? [10:58] popey: I know lots of people who will happily update an app, but are reluctant to upgrade the whole system. [10:59] maybe on other platformz [10:59] s/z/s/ [11:03] congrats on what seems to be a success OTA all [11:04] I get the error no such file or directory when including apparmorfs.h from the same location security/apparmor/include [11:04] Any other files got the same issues [11:06] rickspencer3: cant believe we just literally upgraded from utopic to vivid..a distro upgrade gone so smooth..would be awesome to see this confidence with ubuntu desktop upgrades as well..in the near future I suppose [11:06] nik90, sure, for those who prefer it, ti should be an option [11:07] the whole system-image concept really does seem to have paid off in a big way, at least in terms of robustness [11:07] indeed === chihchun is now known as chihchun_afk [11:11] I'll try to make an extra directory with the same files [11:28] cedian_linux: are you using #include "file.h" or #include ? [11:31] Mcphail #include "file.h" [11:31] rickspencer3, while that might be true, the overlay ppa concept hasnt paid off so well ... (sadly the system-image package was accidentially reverted to the utopic version in OTA-4) [11:36] cedian_linux: and you've definitely got the right file? You've called it apparmor.h at one point and apparmorfs.h at another, or were those separate errors? [11:37] Separated mcphail [11:37] did you solve the first one? [11:37] No [11:38] Apparmor.h fails to include apparmorfs.h [11:40] cedian_linux: I haven't tried building apparmor before. If I get a chance I'll have a look tonight [11:40] OK [11:40] what source are you using? [11:41] The official back port, I got the sources from mariogrio [11:41] Mariogrip [11:55] Found it it can't find label.h which is missing === MacSlow is now known as MacSlow|lunch [11:59] ogra_, rickspencer3: well, yeah... I wouldn't say the old s-i issue is actually a problem with the overlay, since we would have the same thing in a derived distro [11:59] As we would derive the distro from vivid anyway, which had the old s-i [12:00] It's just that we actually need to remember about all those low-level packages next time as well, and it's easy to miss since it won't pop up in the standard tests [12:03] sil2100, well, i dont really understand it, iirc slangasek did a mass sync from rtm [12:04] i wonder how that slipped through [12:05] Well, no... [12:05] We didn't do any mass-sync from ubuntu-rtm [12:06] We did a mass sync from vivid-overlay to wily, ubuntu-rtm and vivid were too much different [12:06] we did a wave of syncs from vivid-overlay to wily [12:06] that's maybe what you remember? === alan_g is now known as alan_g|lunch [12:06] oh, riht, sorry, i mis-remembered === mzanetti is now known as mzanetti|run [12:13] Warning aa_may_chmod redefined enabled by default gives an error [12:13] Yay working shell rotation in rc-proposed mako [12:15] Hello, am I right here if I'm searching for some kind of support? (my aquaris phone does not start after system update) [12:17] hi criztovyl [12:17] as good a place as any, I suppose [12:17] hi rickspencer :) [12:17] popey, ever hear of a failed to reboot after the update? [12:18] * rickspencer3 assumes this is after taking the OTA yesterday/today? [12:18] criztovyl, note that this OTA takes a long time with no feedback that it is doing anything [12:18] after it installs the update, it sometimes has to work for up to 30 minutes while the screen is blank [12:19] I let it alone 2 hours and afterwards the screen was black. [12:19] that should have been more than sufficient [12:19] And the phone doesn't respond to anything [12:19] criztovyl, is it fully charged again? [12:20] rickspencer3: nope [12:20] criztovyl: generally hold down power for 10s+ to reboot [12:20] criztovyl, if it were me, I would plug it into the wall for a few hours, then hold down the power button until it reboots [12:21] now? yes. [12:21] criztovyl, and if you hold down the power button for > 10 seconds, nothing happens? [12:22] Wait, I have not problem correctly, i will write it down now [12:22] Why gives it the warning aa_may_chmod redefined [enabled by default] error forbidden warning? [12:25] Social Media is going completely crazy over OTA-4 and the MX4 [12:26] My phone doesn't stop vibrating because of all the notifications [12:27] sturmflut2: is the worldwide version of mx4 released? [12:28] mcphail: "Next week" [12:28] In the morning I woke up and take a look on my phone to get the time. Then there was the "System Update Available" Notification and I've run the update, the phone shut down and the typically updating screen appeared an I fall asleep again. I woke up again two hours later and the screen was black. The I wait a half hour more. Afterwards I searched the Internet If anybody has an similar problem and found the 30 Min problem on the la [12:28] nice [12:28] unchpad ubuntu phone mailing list. The I decided to write a support request to bq and they respond I should go to recovercy mode. Recovercy mode didn't help (i want to try to keep my data). Now the phone is in Fastboot mode an i want to try to reinstall the kernel. But before i want to ask somewhere if there is an other solution. [12:28] mcphail: It will be shipped to insiders today [12:28] Hopefully the battery doesn't went empty during update :/ [12:29] popey, can criztovyl use udf to reinstall without wiping data? [12:29] sturmflut2: lucky ladies and gents [12:29] yes [12:29] udf? [12:30] criztovyl: http://askubuntu.com/questions/602035/how-do-i-use-ubuntu-device-flash-with-the-bq-aquaris-e4-5-and-aquaris-e5 [12:30] Uh, ubuntu-disk-flash... the i have to boot into my ubuntu... [12:31] Can i also use Debian for something like ubuntu-disk-flash (e.g. fastboot)? [12:35] I now can access my phone in recovercy with adb. [12:35] did you try holding down power for 10+ seconds to force reboot? [12:35] Used the image from the link and did fastboot boot [the image] [12:36] popey Yes, then it runs until the rotating ubuntu icon and switches off afterwards and this until i turn it off again [12:36] I think the battery went empty during upgrade [12:37] But as I said I now can access the phone in recovery mode via adb [12:37] * mcphail thinks it would be good if the UI would issue a warning if you try to flash with <50% battery [12:37] can you plug it into power, reboot it and just leave it? [12:38] popey Yes [12:38] I will try :) [12:41] Oh, the red LED is blinking on boot, I think this is the indicator the battery went empty during update/upgrade (wich on is it?) [12:42] john-mcaleely: do you know what red-flashing LED means on krillin? ^ [12:43] criztovyl: i think you're right, it's probably dead battery. [12:43] or very nearly dead [12:43] Yes, but now it power is plugged in so that shouldn't the problem :) [12:43] popey, I'm unsure, but that is certainly a good guess === mzanetti|run is now known as mzanetti [12:44] Huh, I think its the tenth reboot now^^ === mibofra is now known as Guest38476 === _salem is now known as salem_ [12:45] is it in a reboot loop? [12:46] I dont know, but i can remember now that after the last system update/upgrade it also did reboot often and then somewhen booted correctly [12:48] Where can I ask development related questions about Ubuntu Touch [12:48] ? [12:48] ultimatetux: for apps, #ubuntu-app-devel [12:48] ultimatetux, here [12:48] right, for apps what mcphail said [12:49] ubuntu [12:49] ubuntu [12:49] lol [12:49] (now you all know my password for the ubuntu user ... damned) [12:50] ogra_ Happens. [12:50] aah - I use that one for root [12:50] you dont use "password" for root ? [12:51] i thought that was a general convention [12:51] I'm too clever for that [12:51] (if you dont use "1234" [12:51] ) [12:51] I'm trying to reach Tassadar [12:51] I don't use the root with password, i use only sudo -s ^^ [12:51] ultimatetux, well, patience then ... he drops by here every now and then [12:51] The guy running the repos of Touch for Nexus 5 [12:52] ogra_, aha so he hangs around here.. [12:52] at times, yes [12:52] Why not sudo -I? [12:52] sudo -i [12:53] so if I intend to start some apps adjustments and core system changes, What's the best dev bed phone to work on? [12:53] cedian_linux because i didn't know yet but it's very useful, isn't it? ^^ [12:54] ultimatetux: bq e4.5 or e5 :) [12:55] popey, what about Nexusw 4? [12:56] My phone is still rebooting... ^^ [12:56] Nexus 4 is getting a bit old now === alan_g|lunch is now known as alan_g [12:56] criztovyl: I don't know the solution for this other than re-flash it as per that web page [12:56] sorry [12:56] Then i will try it, thx :) [12:57] noooo, dont tell my n4 its getting old :( [12:57] And adb access isn'n nothing :) [12:57] Yeah, it wont because you need to unlock the phone with PIN [12:58] someone on the ubuntu-phone list is also seeing boot loop [12:58] so you're not alone === MacSlow|lunch is now known as MacSlow [12:58] I will take a look. [12:58] popey, so it'll lag future support or is already not supported on current latest builds? [12:59] ultimatetux: It wont get as much attention as the retail devices === dandrader_ is now known as dandrader [12:59] criztovyl: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1465660 [12:59] Launchpad bug 1465660 in Canonical System Image "ota-4 appears to trigger bootloop in some handsets" [Undecided,New] [13:01] popey, I can't get hold on a bq device however I can get hold of a nexus 4, I already have a nexus 5 but don't wanna get into the hassle of the patches made to bring it to life [13:02] popey, if Nexus 4 can work as a development bed it will be good for me [13:02] it works [13:02] hellou [13:02] a bunch of people here have one [13:02] criztovyl, if you see the rotating logo with a small bar underneath, that is actually the falshing process [13:02] *flashing [13:02] ogra_ I see the standard icon :) [13:03] what is the "standard icon" ? [13:03] I got the update yesterday :) but my circle still saying no data source available :( [13:03] ogra_ The rotating Ubuntu icon without the bar :) [13:04] criztovyl, ah, on black bakground instead of violet ... ok, that is shown when it tires to start the UI [13:04] Yes cryztovyl [13:04] (after boot) [13:04] * ogra_ wonders how you got into that state [13:04] ogray_ Okay, so the UI is failing? [13:04] Got errors [13:05] did you ever meake the image writable ... install debs or anything ? [13:05] Errors everywhere [13:05] ogra_ I? [13:06] criztovyl, did you tinker in any way with the image via terminalm, adb or ssh ... for example make it writable or install deb packages ? [13:07] usually the upgrade doesnt fail ... which is why i'm interested how you got to a failing state with yours [13:07] ogra_ I now what you mean but i didn't if you asked me ;) [13:07] ah :) [13:07] And yes, I did, for calendar sync with my owncloud [13:07] aha [13:07] the syncevolution package [13:08] well, that might/could cause issues ... not sure ... [13:08] I think it was via apt but i also could be it was via dpkg -i ... [13:08] the OTA images are not designed for this [13:08] so it could indeed be caused by adding debs [13:08] ogra_ I can access the aquaris in recovery mode via adb, i will see what i can do [13:09] ogra_ So at least we found the source of the problem, cool :) [13:09] criztovyl, in recovery: mount /data ... then touch /data/.adb_onlock ... then reboot and adb should let you in even without a session running [13:09] that way you could check the processes running etc [13:10] orgra_ in which state should i boot? [13:11] just a normal boot [13:11] am I fast enough to get in before it reboots? [13:12] the .adb_onlock file tells adbd to not wait for a UI session to let you in [13:12] heh, thats a good question :) [13:12] Let's give it a try [13:13] Now it displays a battery, and the percentage :D [13:13] Hm. [13:13] 70% [13:14] 238138 [13:14] popey, john-mcaleely Red LED seems to be charging indicator [13:15] criztovyl, press and hold power ... then it will boot [13:15] ogra_ Another password? [13:15] ^^ [13:15] heh, no, a 2fa token ... my yubikey is a bit close to another USB port i just plugged something in [13:16] cool === pete-woods1 is now known as pete-woods [13:19] Can't find an error origin [13:20] mm getting "ssh_exchange_identification: read: Connection reset by peer" while trying to phablet-shell on an rc-proposed BQ [13:20] any idea guys? [13:22] has localhost been added to the denyhosts by any chance? [13:22] I'm back, my computer decied to stuck. [13:23] mmm it works now...nothing changed...interesting... [13:23] r36 fwiw [13:25] faenil, i was about to say, nothing changed in quite a while in that area [13:26] ogra_ I'm now in recovercy shell environment via adb [13:26] I'll try to compile I'll keep you informed [13:26] criztovyl, mount /data [13:26] criztovyl, touch /data/.adb_onlock [13:26] orga_ It's alread mounted [13:27] good [13:27] so touch the file and on next reboot you should be able to get in via adb [13:27] Yeah, and if i touch and reboot i got the battery and if i reboot i'm back in the loop. [13:28] ogra_: I wonder what went wrong in the first tries :/ [13:28] Can't find some files [13:31] Apparmor.o won't compile === Guest38476 is now known as mibofra [13:50] .o. [13:52] Where can I find the sources for Ubuntu Touch? [13:59] ultimatetux you can find it on the porting page [14:00] Okay [14:00] It's Ubuntu touch + CM [14:00] Or AOSP [14:01] How Or ? :) [14:01] From my understanding its Ubuntu Touch + CM over AOSP ! === chihchun_afk is now known as chihchun [14:09] OK [14:15] davmor2, hey Dave, I'm looking at bug 1463841 and wonder if this has something to do with the operator? Because I can't reproduce it. [14:15] bug 1463841 in ubuntu-system-settings (Ubuntu) "Call waiting status not always the same" [High,In progress] https://launchpad.net/bugs/1463841 [14:15] davmor2, did you use giffgaff and is that an mvno? [14:18] jgdx: so it looks to me like a krillin issue, sim is on by default, if you set if off it stays off, if you turn it back on it is turned off. Where as sim 2 is always off after a reset [14:18] jgdx: for me it was more first boot vs hard reset [14:19] jgdx: let me update the bug [14:19] davmor2, wait, if there are two sims why wasn't that in the original bug? [14:20] jgdx: it might happen on arale too I'll have a look in a minute for you [14:20] davmor2, thanks, I'll try that as well [14:25] jgdx: see if that makes sense [14:25] I'm hoping the apparmor still works [14:25] davmor2, thx [14:27] so if I have wifi on I can't send pic messages on mako [14:27] latest rc-proposed [14:31] Generically.. Where can I find the sources for the deb packages for a certain distro version? for example 14.04 ?! [14:32] I'm coming for RedHat world so we keep everything organized under SRPMS [14:33] ultimatetux: you can enable deb-src in /etc/apt/sources.list (we also have an UI for this) [14:33] then apt update, and apt source [14:34] ultimatetux: https://www.debian.org/doc/manuals/apt-howto/ch-sourcehandling.en.html [14:34] (simple google search ;)) [14:34] didrocks you mean sudo apt-get update sudo apt-get source, most of the time [14:34] cedian_linux: apt update gives you nicer progress (apt v2!) [14:34] interesting, apt source isn't a thing though [14:35] OK didrocks [14:37] I'm sure I'm just blind, but where's the WiFi Tethering switch in OTA-4? [14:38] I don't see it in rc-proposed [14:38] sturmflut2 I've never seen it [14:39] cedian_linux: Wasn't OTA-4 supposed to have it [14:39] * ahoneybun looks for changelog [14:39] http://people.canonical.com/~lzemczak/landing-team/ota/ota-4.changelog === davidcalle_ is now known as davidcalle [14:40] I don't see it there [14:40] ahoneybun: Hmmmm, me neither, and I was pretty sure that I had read about this multiple times [14:40] Well, if it isn't there it isn't there [14:40] pushed back maybe? [14:41] ahoneybun: Probably [14:44] jgdx: so it is the same on arale it seems to behave-ish, on flash it is on, I turn it off reset and it is off, I turn it on, I reset and it's on which is Guess is a network setting it fetches correct? So it maybe specific to krillins 2 sims [14:46] davmor2: Doesn't krillin have the "feature" that the SIM Slot is actually powered off and removed from the bus when it's turned off, something other phones don't do? Or something like that [14:46] jgdx: I think the big issue is full reset you expect the phone to be the same as it is after a fresh install. Ie call waiting is turned on by default. [14:46] davmor2, you could repro on arale? [14:47] Not sure I understood what happened on arale.. But yes, it's a network setting AFAIK. [14:48] jgdx: it is not the same on arale even sorry. It does different things on arale which I might assume are correct. [14:49] davmor2, okay, but that's good. Thanks for testing :) [14:49] jgdx: I think the issue is the understanding of what reset does. To me it would mean everything is reset, so if the default is on, I turn it off, and I reset I expect that thing to be on again not off [14:49] jgdx: but krillin is definitely not behaving the same way [14:50] davmor2, okay. Ugh, I don't know if we should touch the sim on reset. Haven't given it much thought. Sounds wrong though.. [14:50] imagine that we nuked all sim contacts on reset. That ain't right [14:53] jgdx: indeed that would be bad [14:56] davmor2, I think "Erase & Reset" is really a "Factory reset" [1], so we won't do anything wtr to SIM settings. [1] bug 1292932 [14:56] bug 1292932 in ubuntu-system-settings (Ubuntu) "Add "factory-reset" option" [Critical,Fix released] https://launchpad.net/bugs/1292932 [15:14] davmor2, what channel and image rev? [15:15] davmor2, I just flashed with SIM1 call waiting ON before the flash. Call waiting was ON after the flash. Is it intermittent? [15:17] jgdx: no, when you fresh flash, call waiting is on, on sim1, turn it off reset, and it is off, turn it on and reset and it is off again rc-proposed 32 off the top of my head give me 5 and I'll double check that for you then [15:19] jgdx: 26 I tested against [15:31] davmor2, thanks [15:37] davmor2, reproduced! [15:38] jgdx: \o/ === cwayne1 is now known as cwayne [16:01] How can I join the official ubuntu phone mailing list please? [16:02]