[02:23] <kgunn> so anyone else on vivid image #79 finding wifi is hosed ?
[02:23] <kgunn> nexus4
[06:24] <commander_> hello everyone
[06:24] <commander_> i need help
[06:26] <commander_> my app is showing a message on  runtime that QNetworkRequest::setHeader() to fix this problem ,,,,my app is written in qml and contain a webview
[06:28] <commander_> my app is showing a message on  runtime that QNetworkRequest::setHeader() to fix this problem ,,,,my app is written in qml and contain a webview
[06:30] <commander_> hi jaywink
[06:31] <jaywink> hi
[06:31] <commander_>  my app is showing a message on  runtime that QNetworkRequest::setHeader() to fix this problem ,,,,my app is written in qml and contain a webview
[06:32] <commander_> how to fix this anyidea ?
[06:32] <commander_> how to set request header ?
[06:42] <jaywink> sorry cannot help :)
[06:42] <commander_> jaywink, its okay
[06:46] <commander_> silence showing the progress of ubuntu-touch lol :D
[06:50] <nhaines> !patience
[06:51] <nhaines> commander_: none of the main developers start working for another 70 minutes.
[06:52] <commander_> hmm:/
[08:12] <dholbach> good morning
[09:44] <uhhimhere> https://www.scribd.com/doc/253959029/GT-S7390-2-Service-Manual ; those variable names are they the kernel/module drivers?
[09:51] <commander_> my app is showing a message on  runtime that QNetworkRequest::setHeader() to fix this problem ,,,,my app is written in qml and contain a webview
[09:53] <JamesTait> Good morning all; happy Data Protection Day! :-D
[10:52] <Volpsi> Hi
[10:52] <Volpsi>  it`s possible to install the ubuntu OS in my smartphone?
[11:05] <seb128> mpt, hey, I've a question about https://wiki.ubuntu.com/SecurityAndPrivacySettings#error-text
[11:05] <mpt> Yes?
[11:05] <seb128> "If the “Current…” field (where present) has an incorrect value, it should then acquire the standard error style (bug 1222787), the error text should appear as a caption"
[11:06] <seb128> mpt, should that happen "real time"?
[11:06] <seb128> like if my password is "1234" and I start typing "1", should it turn red?
[11:07] <seb128> same for choose/confirm?
[11:07] <seb128> ups
[11:07] <seb128> ignore that
[11:07] <seb128> "When you choose the main action: "
[11:09] <seb128> mpt, do you know if there is a description of what the "error style" is, since that's not implemented in the toolkit
[11:11] <mpt> seb128, I gave some suggestions in the bug report: e.g. maroon text, and a subtle sound effect played when it is displayed
[11:13] <mpt> seb128, and yes, “When you choose the main action” means not before :-) (That’s a common mistake on Web sites asking for passwords etc)
[11:16] <seb128> mpt, "Whenever a “Confirm new…” field does contain exactly the same number of characters as the “Choose new…” field, but the values do not match, the main action button should still be insensitive"
[11:16] <mpt> oh poop
[11:16] <seb128> mpt, how can you end up in the "Otherwise, if the “Choose…” and “Confirm…” fields (where present) do not match" validation case?
[11:16] <mpt> right
[11:16] <mpt> hmm
[11:22] <mpt> seb128, is there a minimum length for passphrases?
[11:22] <mpt> oh yes there is, bug 1412523
[11:25] <seb128> mpt, yeah, I'm unsure what are the criterious, but you can't enter an empty or trivial password
[11:26] <mpt> So maybe the correct principle is “Show an error at the earliest possible non-annoying moment”
[11:26] <mpt> When two “Choose new…” fields are different lengths, that doesn’t count as non-annoying, because maybe you just haven’t finished typing yet
[11:27] <mpt> Therefore we need to wait until you try to choose the action before showing you the error, therefore in that case the button should be sensitive
[11:28] <mpt> seb128, spec updated. <https://wiki.ubuntu.com/SecurityAndPrivacySettings?action=diff&rev2=56&rev1=55>
[11:28] <seb128> mpt, thanks
[11:40] <seb128> mpt, I'm unsure to understand the logic in that dialog, in some error cases the user is stopped to hit the confirmation button (e.g current pincode != 4 digits) and in some not (e.g different length between new passwd/confirmation)
[11:40] <seb128> what's the difference between those cases?
[11:42] <mpt> seb128, so like I said, it’s about showing the error at the earliest possible non-annoying moment
[11:43] <seb128> mpt, is blocking the button considered as an "error"?
[11:43] <mpt> When a pincode/PIN field has the wrong number of digits, you can see that for yourself, so we don’t need to let you hit the button before telling you. We can keep the button insensitive until you fix it.
[11:43] <seb128> if you know that PIN has to be 4 digits
[11:45] <mpt> But when two passphrase fields don’t match, that might be hard to see. They might both be wider than the field, for example. But we also shouldn’t tell you until we’re sure that you’ve finished typing, because that would be annoying. And the only way we can be sure that you’ve finished typing is when you hit the button. That’s why the button needs to be sensitive in that case.
[11:45] <mpt> Does that make sense?
[11:47] <seb128> hum
[11:47] <mpt> Sorry, by “don’t match” I meant “don’t have the same length”
[11:47] <seb128> yeah, that case makes sense
[11:48] <mpt> In the case where they have the same length, BUT don’t match, then you probably think you’ve finished, so we jump in and tell you before you even get to tap the button
[11:50] <mpt> Oh, that means step 3 is wrong, doesn’t it?
[11:50] <mpt> the main action button is still insensitive, so you can’t have tapped it
[11:51] <mpt> Oh, no, it’s right. Step 3 covers the case where they don’t match and are even different lengths.
[11:51] <mpt> It still could be clearer, though
[11:52] <seb128> sorry, taking a bit of time to think about it :-)
[11:57] <seb128> yeah, makes sense (I think ;-)
[12:13] <mpt> seb128, it should be clearer now. <https://wiki.ubuntu.com/SecurityAndPrivacySettings?action=diff&rev2=57&rev1=55>
[12:15] <mpt> Hmm, one more mistake
[12:19] <mpt> Fixed. <https://wiki.ubuntu.com/SecurityAndPrivacySettings?action=diff&rev2=58&rev1=57>
[12:32] <seb128> mpt, thanks
[12:36] <seb128> mpt, so the only cases where the main action button should be insensitive is when the input format doesn't match the one from the entry (e.g passcode != 4 digits, passphrase with no char, SIM ![4-8])?
[13:08] <jgdx> seb128, wanna take a look at [1]? Addressed the divider issue as well as implementing ded_nick's switch logic. [1] https://code.launchpad.net/~jonas-drange/ubuntu-system-settings/sound-other-vibrations/+merge/240261
[13:08] <jgdx> (also the schema dep bump)
[13:15] <seb128> jgdx, hey, sure can
[13:20] <jgdx> seb128, thanks
[13:27] <boiko> rsalveti: hi, we have a change in telepathy-qt5 we need to land, would you by chance have time for it?
[13:27] <boiko> rsalveti: here is the MR: https://code.launchpad.net/~tiagosh/ubuntu/vivid/telepathy-qt5/emit_selfHandleChanged/+merge/243435
[13:27] <rsalveti> boiko: sure, will get to it in a few
[13:28] <boiko> rsalveti: thanks a lot!
[13:28] <seb128> boiko, rsalveti, before that lands could somebody address my question on the mp about why is that not upstreamed?
[13:29] <boiko> seb128: ah yes, I think salem_  forgot to mention: most of the service-side implementation is not upstream yet, we are trying to allocate some time for it, but that didn't happened yet
[13:29] <boiko> seb128: we will upstream it at some point, but we need time to write tests,and make the changes fully compliant with the upstream process
[13:30] <seb128> boiko, could also somebody reply to https://lists.ubuntu.com/archives/ubuntu-devel/2014-December/038566.html ?
[13:31] <boiko> seb128: yep, let me do that
[13:31] <seb128> boiko, thanks
[13:37] <rsalveti> boiko: this change looks fine, but it would indeed be nice to rebase the patches on top of 0.9.5
[13:38] <rsalveti> so we can have a more recent package in vivid
[13:38] <rsalveti> and of course, try to get them upstream
[13:38] <boiko> rsalveti: yep, upstreaming will take a bit more time, but I am talking to bfiller to check if we can allocate some time for that
[13:38] <rsalveti> great
[13:52] <rsalveti> kgunn: what is the wifi issue you're having with vivid?
[13:52] <rsalveti> I know we landed a new networkmanager in there
[13:53] <rsalveti> oh, but that one is still in proposed
[13:53] <kgunn> rsalveti: it just refused to show any network on the first boot, reboot seemed to fix it
[13:53] <rsalveti> oh, ok
[13:54] <tsdgeos> boiko: is this ever going to land https://code.launchpad.net/~aacid/dialer-app/AllIsNotAll ?
[13:59] <lee_> if i install vivid on nexus4 which file should i download
[13:59] <lee_> anyone knows
[14:00] <ogra_> ubuntu-device-flash will download what it needs and install it for you
[14:00] <ogra_> https://developer.ubuntu.com/en/start/ubuntu-for-devices/installing-ubuntu-for-devices/
[14:11] <mterry> kenvandine, you were seeing a bug with the password change dialog?
[14:11] <mterry> kenvandine, a failure to change password?
[14:11] <kenvandine> mterry, are you talking about my comments on your MP?
[14:11] <mterry> kenvandine, yeah
[14:12] <kenvandine> i think that wasn't really a failure... just not what i expected
[14:12] <kenvandine> i put in the wrong current pass
[14:12] <kenvandine> and the new pass i entered was actually the current pass
[14:12] <kenvandine> i expected it to tell me the passwd was wrong
[14:12] <seb128> mpt, I guess the error codes shouldn't include
[14:12] <kenvandine> but it just appeared to succeed
[14:12] <seb128> ups
[14:12] <kenvandine> mterry, in reality it didn't need to... because it was a noop
[14:13] <seb128> mpt, I guess the error msgs shouldn't include "Try again" in the case where the password mismatch is detected before hitting the action button?
[14:13] <mterry> kenvandine, ok I saw that comment, but I thought I saw a later comment that suggested it was a real thing.  Glad it's not  :)
[14:13] <kenvandine> nope :)
[14:13] <kenvandine> i just verified i saw the same thing without your branch
[14:13] <kenvandine> and it's really not a bug...
[14:14] <seb128> it is a bug
[14:14] <kenvandine> mterry, i'll backport it to rtm
[14:14] <mterry> kenvandine, my branch?
[14:14] <seb128> if your pwd is wrong it should tell you
[14:14] <kenvandine> mterry, yeah
[14:14] <kenvandine> seb128, but you aren't actually changing it
[14:14] <seb128> still
[14:14] <mterry> seb128, I tend to agree it's not great
[14:14] <kenvandine> it's not great
[14:14] <mterry> seb128, i.e. a bug, but not a high priority
[14:14] <mpt> seb128, I think that’s ok, since usually you won’t be able to tell exactly which character(s) was wrong, so you’ll have to start from scratch
[14:15] <kenvandine> it wasn't a regression
[14:15] <seb128> mpt, ok, good, that makes the code easier ;-)
[14:15] <kenvandine> and functions properly :)
[14:15] <seb128> kenvandine, sure
[14:15] <kenvandine> ie it won't get you to a point you can't login :)
[14:15] <mterry> kenvandine, I'm actually curious how that happened, since I thought we tried to change the password mode before we change the password itself.  I'll look at it
[14:18] <kenvandine> mterry, i'm not 100% sure that's how i reproduced it
[14:18] <kenvandine> i only reproduced it a couple times
[14:18] <kenvandine> and later i realized i was only using 2 passcodes
[14:19] <kenvandine> so i *think* that's why
[14:19] <kenvandine> that was after i had reverted to what was in vivid
[14:20] <kenvandine> and i did reproduce it that way in without your branch, and waiting long enough for the credential to have expired
[14:20] <boiko> tsdgeos: on vivid silo 15, testing it now
[14:20] <tsdgeos> boiko: \o/
[14:21] <kenvandine> seb128,  you have a merge conflict in your branch
[14:21] <kenvandine> dbarth_, please submit a MP for your trust-store check fix to trunk as well
[14:22] <kenvandine> dbarth_, i don't want to risk it landing in rtm without trunk, because we'll be syncing soon
[14:25] <dbarth_> kenvandine: that line change can be dropped i think; it was not the root cause
[14:25] <kenvandine> dbarth_, oh... can you delete your MP then?
[14:25] <dbarth_> kenvandine: mardy fixed the model side of things which is now in silo 021 (rtm)
[14:26] <dbarth_> and mardy's fix already landed on trunk
[14:26] <dbarth_> kenvandine: yes, will do
[14:26] <kenvandine> dbarth_, thanks
[14:34] <seb128> kenvandine, hum, thanks
[14:35] <kenvandine> seb128, np
[14:37] <seb128> kenvandine, resolved and pushed again over it
[14:44] <kenvandine> seb128, do you recall a problem with QtSystemInfo.BatteryInfo not getting property changes?
[14:45] <kenvandine> googling uncovered an irc conversation with gatox asking you about problems with BatteryInfo
[14:45] <kenvandine> but i didn't see any real answers as to the problem
[14:46] <mterry> kenvandine, hrm, I can't reproduce using "change passcode" so maybe it's a trickier thing than we think
[14:46] <kenvandine> mterry, yeah, i got it twice out of over a dozen attempts
[14:47] <mterry> kenvandine, :-/
[14:47] <kenvandine> mterry, so i guess my assumption wasn't correct?
[14:47] <kenvandine> that was a hunch :)
[14:47] <kenvandine> mterry, also... there was nothing interesting logged when it happened
[14:48] <kenvandine> i was watching the log
[14:48] <mterry> hmph
[14:48] <seb128> kenvandine, that rings a bell, I don't think we ever debugged it though
[14:49] <seb128> kenvandine, I suggested that he uses the upower backend we have from battery iirc
[14:49] <kenvandine> i debugged it yesterday... without system-settings
[14:49] <kenvandine> it's definately not getting property changes :/
[14:49] <kenvandine> so i think i need to rewrite the bit to get currentChargingState
[14:49] <kenvandine> drop BatteryInfo
[14:50] <seb128> kenvandine, better would be to fix the bindings so they work, no?
[14:50] <kenvandine> our snapshot of qtsystems is from 2013
[14:50] <kenvandine> and has seem tons of changes since
[14:50] <kenvandine> including API breaks
[14:50] <kenvandine> so updating that would be risky
[14:51] <kenvandine> there was big changes to BatteryInfo, completely refactored
[14:51] <kenvandine> i'd much rather use qtsystems
[14:53] <seb128> we are using qtsystems no?
[14:53] <kenvandine> yes
[14:53] <kenvandine> in the battery panel just to get the state of current charging
[14:54] <kenvandine> i suspect latest from git might work
[14:54] <seb128> we should update in vivid
[14:54] <seb128> we don't have so many rdepends, do we?
[14:54] <kenvandine> at least they have lots of commits to the battery stuff, and upower backend
[14:55] <kenvandine> not sure
[14:55] <kenvandine> i wonder if mirv has looked at updating it
[15:06] <sturmflut-work> pete-woods, Wellark_: Will the connectivity-api also be responsible for Bluetooth? Since Qt Bluetooth doesn't seem to be part of the Touch images
[15:08] <kenvandine> mandel, don't forget to push that check-hash fix
[15:10] <pete-woods> sturmflut-work: that would make sense to me. at any rate you could still log bugs against the connectivity API
[15:14] <jgdx> seb128, that othervibrate u-s-s branch you just reviewed will fail due to the gsettings package being non-existent. How do I solve that? Will we need to land gsettings first?
[15:19] <seb128> jgdx, need to put them together in a silo
[15:21] <jgdx> seb128, right
[15:21] <kenvandine> jgdx, shall we setup a silo?
[15:21] <jgdx> zsombi, ^ ?
[15:21] <jgdx> zsombi, ready to roll?
[15:22] <zsombi> jgdx: there is an other UITK silo ongoing, I'd wait that first, maybe we will have some conflicts which then I shoudl fix
[15:23] <zsombi> jgdx: that one is more important than this (wk05 deadline)
[15:23] <jgdx> ack
[15:23] <jgdx> kenvandine, let's wait for that
[15:23] <kenvandine> jgdx, ok
[15:25] <jgdx> kenvandine, if you get a chance, the sim unlock is ready for review
[15:25] <kenvandine> seb128, so i wonder if this qtsystems breakage really happened because of the upower transition?  maybe that's why we're not getting property changes
[15:25] <kenvandine> i should look at just fixing our snapshot of qtsystems first
[15:26] <kenvandine> jgdx, cool, CI build debs yet?
[15:28] <jgdx> kenvandine, yeah
[15:28] <kenvandine> jgdx, no... the debs are from yesterday
[15:28] <kenvandine> latest run failed to build them
[15:28] <jgdx> kenvandine, nothing's change except the test
[15:29] <kenvandine> ok
[15:29] <kenvandine> jgdx, can you add steps to test this?
[15:29] <jgdx> kenvandine, sure
[15:31] <kenvandine> jgdx, and this is probably a good example of where we should have a qmltest
[15:31] <kenvandine> but i could see the need for AP test as part of a user story, which of course we aren't really following yet
[15:34] <mandel> kenvandine, I wont. sorry, I was feeling a bit under the weather and I started later today
[15:37] <jgdx> kenvandine, yea
[15:37] <jgdx> kenvandine, https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/rtm-lp1205294/+merge/246727 is ready to go into a silo
[15:37] <jgdx> do you want me to take it there? Do you have anything else lined up?
[15:40] <kenvandine> jgdx, isn't the rtm landing gates closed?
[15:40] <oSoMoN> rpadovani, hey Riccardo, I remember you started playing with settings in the browser back in Washington, is this something you still want to implement?
[15:41] <jgdx> kenvandine, right
[15:41] <kenvandine> jgdx, you can go ahead and setup a silo, just can't land it
[15:42] <rpadovani> oSoMoN, hey :-) Actually yes, I want to try it as soon as I have some spare time, but I appreciate it's something you need - so if you need it soon, go ahead :-)
[15:43] <oSoMoN> rpadovani, it’s not super urgent right now, but it’s something that we’d like to start integrating in the near future, so if you’re planning on continuing your work on it, great!
[15:45] <rpadovani> oSoMoN, tbh, I need to start from scratch, so it depends what you mean with "near future". I can starting work on it during this weekend, but you know I don't know C++ very well, so I need time (and probably suggestions by you). I totally understand if you prefer bootstrap it by yourself. Then, I always can integrate new settings options :-)
[15:47] <oSoMoN> rpadovani, no worries (and no rush), I’m busy with many other tasks atm, so when I get to it I’ll let you know and we’ll sync up
[15:48] <rpadovani> oSoMoN, ok, maybe we can talk during this Friday hangout :-)
[15:48] <oSoMoN> rpadovani, sounds good to me
[16:43] <seb128> kenvandine, re. upower, likely
[16:44] <kenvandine> seb128, yeah... so i think i need to figure out how to test this on the desktop to make it easier to fix BatteryInfo
[16:44] <seb128> right
[16:46] <kenvandine> maybe i can use dbusmock to trick it into charging/discharging
[16:48] <kenvandine> seb128, oh!  i just tried on my laptop... it does work there
[16:48] <kenvandine> wtf
[16:49] <kenvandine> i assume it's still getting that from upower
[16:50] <pmcgowan> kenvandine, hmmm?
[16:50] <kenvandine> pmcgowan, on the device we aren't getting any property changes in QtSystemInfo.BatteryInfo
[16:51] <kenvandine> but on my laptop i am
[16:51] <pmcgowan> kenvandine, is that on vivid?
[16:51] <kenvandine> no, utopic
[16:51] <kenvandine> good point :)
[16:51] <kenvandine> so maybe that proves it is upower 0.99
[16:52] <pmcgowan> kenvandine, is this hapening in rtm? whats the symptom?
[16:52] <kenvandine> the charging state isn't getting updated in the battery panel
[16:53] <kenvandine> yeah, rtm and vivid
[16:53] <kenvandine> i've ruled out anything in settings code
[16:53] <pmcgowan> oh that one
[16:53] <kenvandine> i have a simple qml example
[16:53] <kenvandine> yeah
[16:53] <pmcgowan> ok
[16:53] <kenvandine> our snapshot of qtsystems is from 2013
[16:53] <kenvandine> and it's seen lots of changes since then, so i suspect it doesn't handle upower 0.99
[16:53] <pmcgowan> I see
[16:53] <kenvandine> i guess i need to update upower on my laptop to better work on this
[16:53] <kenvandine> or just upgrade to vivid
[16:54] <kenvandine> can't imaging having to keep rebuilding for armhf :)
[16:57] <kenvandine> seb128, are you running vivid?
[16:57] <kenvandine> on your laptop
[16:57] <kenvandine> seb128, if so... please try lp:~ken-vandine/+junk/qml-battery
[16:57] <kenvandine> and test to see if the charging state changes when you unplug
[17:04] <seb128> kenvandine, no it doesn'yt
[17:04] <kenvandine> ok
[17:04] <kenvandine> seb128, thanks for confirming
[17:04] <seb128> yw!
[17:04]  * kenvandine updates to vivid to start hacking
[18:01] <kenvandine> jgdx, don't forget to add steps to test your unlock branch
[18:11] <squaresurf> Hi all, I've installed ubuntu touch on my nexus 4 and have really been enjoying it! I have been experiencing a few bugs. Where is the bug database? So I can report/check if they're already known.
[18:14] <kenvandine> squaresurf, launchpad.net for bug reports
[18:14] <kenvandine> but best to figure out what component to file bugs against
[18:14] <squaresurf> Thank you.
[18:14] <squaresurf> I'll search through there.
[18:16] <squaresurf> Are there any resources for starting development on the ubuntu touch core? I've found docs on building apps, but I would love to see if I could fix some bugs. I also like the ability to do general hacking on my phone ;)
[18:17] <ZacharyIgielman> squaresurf: this should get you started https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[18:20] <squaresurf> I was disconnected. I'm sorry if someone already answered my question, but here it is again.
[18:21] <squaresurf> Are there any resources for starting development on the ubuntu touch core? I've found docs on building apps, but I would love to see if I could fix some bugs. I also like the ability to do general hacking on my phone ;)
[18:25] <ZacharyIgielman> squaresurf: this should get you started https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[18:25] <squaresurf> Thank you.
[18:26] <squaresurf> What component would the lock screen be in?
[18:26] <ZacharyIgielman> The lock screen is not one of the core apps!
[18:26] <ZacharyIgielman> You're welcome ;-)
[18:27] <squaresurf> I figured it wouldn't be. Where would that code be? Is all of ubuntu touch open source?
[18:28] <pmcgowan> squaresurf, yes all open source, you can get the debian source packages or find the code on launchpad
[18:29] <squaresurf> Good news. Just curious what project the lock screen would be under on launchpad.
[18:30] <pmcgowan> squaresurf, I believe unity8
[18:31] <squaresurf> Thank you. I'll look there.
[18:32] <ZacharyIgielman> Possibly this: https://code.launchpad.net/~doanac/phablet-tools/unlock_screen
[18:33] <squaresurf> I'll look at that as well. Thank you all for your help.
[18:34] <squaresurf> I think I have what I need to start hacking :)
[18:35] <pmcgowan> squaresurf, for example http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/unity8/vivid/files/head:/qml/Greeter/
[18:35] <pmcgowan> and probably other stuff under src
[18:36] <squaresurf> I see. Starting to all make sense.
[20:00] <jgdx> kenvandine, think I added it one sec after we talked about it :)
[20:01] <jgdx> kenvandine, https://wiki.ubuntu.com/Process/Merges/TestPlan/ubuntu-system-settings#SIM_Unlock_.28Single_SIM.29
[20:03] <kenvandine> jgdx, oh... i was looking for it in the MP :)
[20:03] <kenvandine> jgdx, thx!
[20:08] <jgdx> kenvandine, ah, sorry
[20:13] <kenvandine> jgdx, and this uses a private API, can we trust that API won't change on us?
[20:17] <dobey> ah, changing private APIs
[20:18] <jgdx> kenvandine, if it does, I'll go to finland myself
[20:18] <kenvandine> :-D
[20:19] <kenvandine> the label "private" there tends to make people think they can change it with little impact
[20:21] <jgdx> then u-s-s and dialer-app, in the very least, will fail
[20:22] <jgdx> probably messaging-app as well at some point
[20:24] <kenvandine> jgdx, yeah
[20:24] <jgdx> kenvandine, that one test failure will have an MP by tomorrow. test_change_background somehow started failing due to backgrounds being sorted differently
[20:24] <jgdx> I'm going to make that more robust
[20:51]  * ryukafalz wishes the messaging app were a generic Telepathy client
[21:00] <om26er> mterry, check your email, I sent you the video
[21:01] <mterry> om26er, oh thanks!  I'm working on this now...  Have a potential maybe hunch, but still having hard time reproducing, video might hel
[21:01] <mterry> p
[21:57] <aquarius> is there any CLI app on an Ubuntu phone that will let me connect to a serial port? that is: like screen or minicom can, but neither of those are installed...
[22:01] <dobey> aquarius: cat? :)
[22:01] <dobey> aquarius: or echo maybe
[22:01] <aquarius> I tried that
[22:01] <aquarius> something weird is going on
[22:02] <dobey> what serial port are you trying to connect to?
[22:02] <dobey> or what are you even trying to do at all? :)
[22:02] <aquarius> a bluetooth one. :)
[22:02] <dobey> oh
[22:03] <dobey> how did you create a bluetooth serial connection on ubuntu on a phone? :)
[22:03] <aquarius> because I am l33t, that's how ;)
[22:03] <aquarius> it's actually very nearly working
[22:04] <dobey> except it won't work when your app is confined?
[22:04] <aquarius> this isn't actually to be an Ubuntu app
[22:04] <aquarius> I have a bluetooth serial console running on my raspberry pi
[22:04] <aquarius> and I need to connect to it to confirm that it's working
[22:04] <dobey> oh
[22:05] <dobey> is your laptop broke? :P
[22:05] <aquarius> and I only have two bluetooth-capable devices -- the N4 running Ubuntu, and the iPhone. And the iPhone is weird about bluetooth and doesn't let apps use it, unless it's Magic Blessed Apple Bluetooth.
[22:05] <aquarius> huh. laptop.
[22:05] <aquarius> did not think of the laptop. :)
[22:05] <dobey> lol
[22:05] <aquarius> my desktop doesn't have bluetooth :)
[22:05] <aquarius> because I basically did not care :)
[22:05] <dobey> pretty sure your laptop does
[22:06] <aquarius> it does
[22:06] <aquarius> that's in the other room though!
[22:06] <aquarius> ok, my path is clear :P
[22:07] <dobey> i want to write some apps that require bluetooth serial connections, but i haven't really even tried yet because the story for bluetooth connections in apps is not anywhere near where it needs to be yet :-/
[22:07] <aquarius> nope
[22:07] <aquarius> rfcomm etc works
[22:07] <aquarius> so it's all doable
[22:07] <aquarius> but not under confinement.
[22:07] <aquarius> well... I *assume* you get confined away from this stuff
[22:07] <dobey> well i have some code i wrote like 8 years ago that might be helpful for me
[22:08] <dobey> if i can find it and write a test confined app based on it, it will at least tell me if i can cheat or not
[22:08] <dobey> but even then, the whole lack of background processing is going to be a pain there
[22:22] <adrian47> Hello, where can I find changes that appeared in ubuntu-touch-generic-initrd_0.81_armhf.deb (0.80 -> 0.81)
[22:40] <ibuntu> awe_, are you around? that radio fw thing happened again and I can't connect to my network. Any chance there is a way to fix this without reflashing back to android and reinstalling ubuntu touch?
[22:40] <awe_> ibuntu, mako?
[22:41] <awe_> rtm or devel-proposed?
[22:41] <ibuntu> awe_ i think so, let me double check, its a nexus 4
[22:41] <awe_> that's mako
[22:41] <ibuntu> rtm
[22:41] <awe_> unfortunately I have to leave in a few minutes to pickup a friend...
[22:42] <ibuntu> no worries, when is a good time to check back in with you?
[22:43] <awe_> I'll be back on later this evening ( probably _2h or so from now )...  honestly though there may not be a quick turnaround on this, as it may require some debugging.
[22:44] <awe_> also we have a network/telephony meeting in the morning, so if you file a bug, it's something we can put on the agenda if I'm not able to help you later on this evening
[22:44] <ibuntu> awe_, thanks, I will talk to you about it then. if I can help improve the OS I would be happy to do some work debugging or whatever I can do to help
[22:44] <awe_> well.. unfortunately I think this is more of a device-specific problem vs. an OS problem
[22:44] <awe_> but we'll still look into it
[22:45] <ibuntu> awe_, thanks I will check back in with you in 2-3 hours
[22:46] <awe_> ibuntu, sounds good, I'll keep an eye out for you as well