[00:16] <htcm7> any new development on m7spr?
[00:17] <htcm7> aka htc one sprint?
[00:22] <htcm7> vthompson: any news regarding getting the cellular working on the m7?
[00:23] <vthompson> htcm7, no I'm sorry. I haven't had any time or desire to port to the device lately
[00:23] <htcm7> kk anyone else you aware of working on it?
[00:24] <vthompson> It's been forever since I've checked xda-developers but I'd hope someone would have made progress. It's been over 6 mo since I last checked
[00:24] <vthompson> I'm not sure anymore
[00:24] <htcm7> dang
[00:24] <htcm7> thx I would want to run it on this phone but I don't want to lose the ability to call and text
[00:25] <htcm7> If I knew more about the subsystems I'd work on it
[00:26] <vthompson> Well, I'm not sure any Sprint radios (aka, CDMA) are working. Anyone here know?
[00:27] <htcm7> I've read a lot saying that the base image is just cm is that true
[00:28] <vthompson> I can't really speak to that, as I've kinda forgot what they've changed now that I'm just fat dumb and happy getting regular updates on a Nexus 4. But it was originally CM that booted ubuntu, but the images are far less CM and far more Ubuntu now
[00:28] <htcm7> Plus I'm kind of in the dark with all this Android versus true Linuxo anyways I'm kind of new to Linux game
[00:29] <htcm7> lol
[00:30] <vthompson> I'm sure there are kernel version differences, but Android feeds their updates back upstream occasionally. So hopefully the mainline kernel has some of the Android kernel goodies.
[00:30] <htcm7> Lol off that subject it would be funny if they came out with an ibuntu
[00:31] <vthompson> Free, open source, expensive, closed hardware... that's a double oxymoron
[00:31] <htcm7> lol
[00:31] <htcm7> It is just UNIX anyway though
[00:32] <htcm7> Very very neutered version
[00:32] <vthompson> eh, modified BSD with GNU-ish toolchain
[00:33] <vthompson> I like my macbook though. It's best use is testing to see if my Linux machine actually crashed by ssh'ing to it
[00:33] <htcm7> Did you ever find out the cause for the random crashes and hangs noted on the device page for the HTC One?
[00:33] <htcm7> lol
[00:34] <vthompson> No, I don't even recall getting that far. Someone else may have updated the wiki if that's where you see the info. (check the bottom of the page to see who to harass)
[00:35] <cjwatson> tedg: OK, I managed to get this done tonight after all.  https://code.launchpad.net/~cjwatson/upstart-app-launch/libclick-manifest/+merge/210520
[00:36] <cjwatson> Not often I get to optimise something to a fifth of its former runtime
[00:36] <htcm7> gg
[00:37] <htcm7> Well I may end up playing with it I have to do a nand first,
[00:38] <htcm7> And considering this is my secondary phone I really want something more non Google on it
[00:39] <htcm7> Anyway I'll let you get back to your Nexus
[00:39] <vthompson> Ha, thanks. Good luck!
[00:39] <htcm7> ty
[00:44] <sarnold> is it expected that the swipe-from-left app launcher 'dock' thing should have a dozen blank spots between one icon at the top and one icon at the bottom?
[00:45] <sarnold> clicking on some does nthing, clicking on others brings up the keypad (dialer maybe?)
[01:02] <mhall119> nhaines: yeah you should have had membership, you have to log in outside of Summit though (SSO doesn't like being embedded in an iframe)
[02:01] <nhaines> mhall119: yeah, unfortunately I logged in outside of Summit (twice!) just about the same time you added me.  Soo... we live in a world of mystery.  :)
[03:13] <Aaa_> Bricked my nexus 4 after installing ubuntu
[03:14] <Guest3099> Bricked my nexus 4 after install ubuntu
[03:15] <Guest3099> Please help
[03:16] <Guest3099> Anybody there
[08:19] <jussi> hrm... does youtube not work on touch? is there no actual application for it?  rowser seems to forever load videos...
[08:58] <JamesTait> Good morning all; happy No Smoking Day! :-D
[09:02] <ogra_> pfft
[09:05] <didrocks> ogra_: I hope you will comply!
[09:06] <ogra_> nah ... not me :P
[09:06] <didrocks> "pfft"
[09:06] <jussi> ogra_: always the rebel :D :D
[09:06] <ogra_> heh
[09:06] <jussi> ogra_: hows things?  been a while since we talked...
[09:09] <ogra_> jussi, well, all fine here, how about you ?  was that your brother going to liverpool i saw on G+ ?
[09:09] <jussi> ogra_: I was just in Liverpool with my brother in law. (wifes brother)
[09:09] <ogra_> ah
[09:12] <jussi> ogra_: was a fun trip... driving fast cars and stuff :D
[09:13] <ogra_> haha, well, for fast cars you need to come to germany ... doesnt help if they are fast but you cant drive them the right way ;)
[09:15] <jussi> ogra_: we went to a racetrack, so we could drive as fast as they could go (at least on that racetrack's small ish space), which was nice.
[09:15] <jussi> He took the Ferrari Modena, I had the mclaren...
[09:16] <ogra_> wow, nice !
[09:19] <jussi> ogra_: yeah, its suprisingly cheap to do, and was really fun :)
[09:19] <ogra_> i used to live close to the nuerburgring in my last house ... i never managed to go there :(
[09:20] <jussi> heh
[09:21] <ogra_> well, i bought a porsche instead and now i use the autobahn ;)
[09:21] <jussi> ogra_: http://www.three-sisters.co.uk/driving-experiences/ferrari.asp
[09:21] <jussi> ogra_: sssh :P
[10:50] <aquarius> dbarth,  ping
[10:54] <dbarth> aquarius: pong
[10:54] <dbarth> hi
[10:59] <aquarius> dbarth, heya. See lp:~sil/+junk/U1FilesHTML5/ which is an Ubuntu One client in HTML5.
[10:59] <ogra_> ps ax
[10:59] <ogra_> oops :)
[11:00] <aquarius> dbarth, as mentioned yesterday, it can't download anything because we don't have Download API bindings yet, and it can't give downloaded files to anyone else becuase we don't have New Content Hub bindings yet. But the core of the app is there
[11:01] <dbarth> aquarius: oh,that's awesome! :)
[11:01] <dbarth> i will share with alex
[11:01] <dbarth> that can be the perfect example of app for the new content hub api
[11:02] <aquarius> which is why I hassled kenvandine to make the content hub able to deal with U1's use case ;)
[11:02] <aquarius> also, the HTML5 bindings don't do transitions and things like QML does, but hopefully all that sort of thnig will get fixed without need of doing it in my app.
[11:04] <dbarth> yup
[11:04] <dbarth> i'm trying but it fails cause i'm just in the middle of testing our new oxide container
[11:04] <dbarth> sorry that i can't comment right now
[11:04] <dbarth> i need to fix that oxide runtime
[11:05] <oodavid> Have a mouse issue that *may* be linked to touchscreen - was told to come here
[11:05] <oodavid> http://imgur.com/YRZwrOZ < when I move my mouse (using the touchpad) it skips vertically, but only when a particular monitor is plgged in
[11:05] <dbarth> oodavid: hi, what type of mouse issue?
[11:05] <oodavid> Yoga 11s
[11:06] <oodavid> dbarth, the weird looking pointer is my gif program, it looks fine on screen
[11:06] <oodavid> just the jumping
[11:06] <dbarth> oh sorry, we're in #ubuntu-touch here, i guess that'd be #ubuntu-desktop instead
[11:08] <oodavid> Sorry about that, I think the Yoga is bit of a funny hardware
[12:19] <stevenm> Hey, I'm following the dual boot wiki article - i've ran the dualboot.sh script but it just sticks me in the clockworkmod recovery screen
[12:20] <stevenm> if I just tell it to reboot - then i find there is no ubuntu dual boot app installed
[12:20] <Darkwing> What device?
[12:20] <stevenm> nexus 10
[12:22] <Darkwing> looking for the wiki url?
[12:23] <stevenm> https://wiki.ubuntu.com/Touch/DualBootInstallation
[12:24] <Darkwing> For dualboot to work, you need a multirom recovery.
[12:24] <stevenm> which is what? something missing from the instructions?
[12:24] <Darkwing> according to that wiki page, https://wiki.ubuntu.com/Touch/DualBootInstallation#Requirements only the Nexus 4 device works.
[12:25] <stevenm> and it lists a the bottom others that work
[12:25] <Darkwing> Now, you can check XDA to see if someone has multirom (Kind of like grub in it allows you have more than one rom) for the N10
[12:26] <Darkwing> It states, they work in theory, but have not been tested.
[12:31] <stevenm> I'd rather try and work out what is wrong with the instructions - or additional steps needed for Nexus 10's
[12:31] <stevenm> Not poke around with other stuff
[12:31] <stevenm> Perhaps someone in here has accomplished this with a Nexus 10 or could offer some pointers
[12:32] <Darkwing> I just did my Nexus 4 but, that's what everything is tested on, sorry mate.
[12:32] <Darkwing> On my Nexus 7 I installed a program on the Android side called MultiRom Manager and it has a card to install and dual boot ubuntu from there.
[12:33] <stevenm> a "card" ?
[12:35] <Darkwing> In the app there is a section for installing Ubuntu
[13:23] <boiko> rsalveti: hey, I have one MR for telepathy-qt5 that is already reviewed by salem_, how can I proceed to propose that for landing?
[13:42] <mardy> Kaleo: hi! Do we have a "placeholder" style in the UI toolkit? See https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1289433
[13:46] <rsalveti> boiko: got the link?
[13:48] <boiko> rsalveti: yep, https://code.launchpad.net/~boiko/ubuntu/trusty/telepathy-qt5/conf_call_client_side/+merge/210302
[13:49] <rsalveti> boiko: it seems pitti uploaded it already
[13:49] <rsalveti> sorry, that one was uploaded by me a few weeks ago
[13:50] <rsalveti> guess I just forgot to get it merged
[13:50] <rsalveti> but the package was already available in the archive for a few weeks already
[13:54] <lool> cjwatson: Hey, around?
[13:55] <lool> cjwatson: Just wanted to confirm that once the new click is in, the only thing I need to worry about it adding a bunch of -dev .framework files
[13:55] <lool> cjwatson: ISTR that you didn't like them shipped in the -meta package though, did you want this in a new source package?
[13:56] <Kaleo> mardy, no we don't
[13:57] <Kaleo> mardy, designers should discuss among themselves to agree on what they need there
[13:57] <mardy> Kaleo: OK. Can I add ubuntu-ui-toolkit as affected by this bug?
[13:57] <Kaleo> mardy, sure
[13:57] <mardy> Kaleo: OK, thanks
[13:58] <boiko> rsalveti: wait, there was one branch from salem_ a couple weeks ago, but this MR complements that other one
[13:59] <boiko> rsalveti: there were some things missing on the client side of telepathy-qt, and  also some more changes on the service side were needed
[13:59] <salem_> rsalveti, I think this is a different MR
[14:00] <cjwatson> lool: Yeah, we just need to do that (but after Qt 5.2 as I understand it?).  I have some aesthetic problems with them being in the metapackage but there are advantages to that too, and I don't think it's worth changing, certainly not now
[14:00] <cjwatson> lool: We do need to make sure that the framework files (inc. existing ubuntu-sdk-13.10) have appropriate Base-Name and Base-Version fields
[14:01] <lool> cjwatson: we probably want to change the default framework used in click packages to a 14.04-dev one while landing qt 5.2
[14:01] <cjwatson> lool: that's QtCreator's problem
[14:01] <lool> so that we dont generate clicks on top of qt 5.2 that declare 13.10
[14:01] <cjwatson> click doesn't have a default
[14:01] <lool> right, new frameworks need to exist though
[14:01] <cjwatson> lool: we first need to get click chroot to support 14.04 though
[14:01] <cjwatson> I think that was in the master plan somewhere
[14:02] <lool> is it used in all cases now?
[14:02] <cjwatson> I don't know
[14:02] <lool> if it is, we're good
[14:02] <cjwatson> I think so
[14:02] <lool> pmcgowan: ^
[14:03] <rsalveti> boiko: salem_: sorry, maybe pitt got confused then, let me check the code
[14:03] <pmcgowan> lool, everyone is in sessions now so I will verfy with qtc guys
[14:03] <pmcgowan> lool, that is defintely the plan
[14:03] <boiko> rsalveti: there was one patch updated and one more added
[14:04] <lool> pmcgowan: so there is no dep with the 5.2 landing then, or rather it just needs to happen afterwards
[14:04] <pmcgowan> lool, right, shortly after ;)
[14:04] <cjwatson> right, it shouldn't block 5.2
[14:04] <lool> pmcgowan: a) land qt 5.2, b) add new frameworks, c) add support for 14.04 to click chroot, d) use 14.04 frameworks by default
[14:04] <lool> or something like that
[14:04] <cjwatson> but I think we've done all the hard bits in click now
[14:05] <pmcgowan> cool
[14:05] <cjwatson> it's just bits of bookkeeping now
[14:06] <boiko> mterry: hi! there is just one more case not covered in your MR: contacts with multiple phone numbers, I commented there about it
[14:07] <mterry> boiko, just now pushed a fix, I think.
[14:07] <mterry> boiko, sorry for churn
[14:07] <boiko> mterry: ah nice! let me check
[14:07] <mpt> awe__, hi. When a phone has multiple SIMs, what kind of information is available for users to tell one from the other?
[14:08] <awe__> mpt, ;D
[14:08] <awe__> sorry... this has been a recent theme the past few days...
[14:08] <boiko> mterry: I think it is good now, I will just wait for jenkins to run to give it a try
[14:09] <mpt> awe__, from other designers? If so, sorry :-]
[14:09] <awe__> mpt, it depends on how the SIM was populated by the Operator/MVNO ( ie. the source that programmed the SIM )
[14:09] <awe__> mpt, no worries...
[14:10] <awe__> so, on some SIMs, the associated subscriber phone number *may* be available
[14:10] <awe__> but it's not guaranteed
[14:10] <awe__> in discussions about settings UI, my recommendation was to use a generic SIM1/SIM2 label
[14:10] <awe__> that hopefully could be customized by an OEM if need be
[14:11] <awe__> I think the primary label should match the actual printed label on the hw
[14:11] <awe__> which could be SIM1/SIM2, SIM0/SIM1, GSM1/GSM2, ...
[14:12] <mterry> boiko, I have a second branch based on top of that one that I want to land too.  Will point you to it after I finish doing checklist
[14:13] <awe__> it'd be nice if we had an optional secondary label which could be populated with the phonenumber or less friendly IMSI ( Subscriber Number ) or card ID
[14:13] <awe__> but those latter aren't going to be too obvious to the average consumer
[14:13] <mterry> boiko, I have a second branch based on top of that one that I want to land too.  Will point you to it after I finish doing checklist
[14:14] <awe__> s/those latter/those latter two options/
[14:14] <awe__> mpt, make sense?
[14:16] <mpt> awe__, yep, let me summarize that and see if I got it right
[14:16] <rsalveti> salem_: mind updating debian/changelog as well?
[14:16] <rsalveti> salem_: and please merge lp:ubuntu/telepathy-qt5 before doing that as well
[14:17] <salem_> rsalveti, it's boiko's MR
[14:18] <boiko> mterry: ok
[14:18] <rsalveti> boiko: ^^ :-)
[14:19] <boiko> rsalveti: let me update it
[14:21] <rsalveti> sil2100: do you know if ci is able to handle lp:ubuntu/<pkg> MRs properly?
[14:21] <rsalveti> I believe it should probably just work, but not sure if we tried that already
[14:32] <sergiusens> rsalveti, heh; I asked that question a couple times, don't think that's handled
[14:40] <mpt> awe__, does <https://wiki.ubuntu.com/Networking#sim-id> look good to you?
[14:43]  * awe__ checks
[14:47] <awe__> mpt, that looks great!
[14:49] <sil2100> rsalveti: by CI you mean citrain?
[14:50] <mpt> cool
[14:52] <boiko> rsalveti: telepathy-qt5 MR updated.
[14:53] <boiko> pitti: ^
[14:53] <pitti> boiko: ah, thanks
[15:05] <rsalveti> sil2100: yes
[15:06] <rsalveti> sil2100: but it seems pitti uploaded it directly
[15:06] <pitti> wasn't it meant to be?
[15:07] <pitti> we can still block it in -proposed if needed, but it seems it already was tested
[15:07] <pitti> it was an Ubuntu merge proposal, not an upstream/CI one, after all
[15:07] <rsalveti> I believe it's fine, we might just need to rebuild it for qt 5.2
[15:07] <rsalveti> Mirv: ^
[15:07] <pitti> sure
[15:08] <rsalveti> Mirv: regarding telepathy-qt5
[15:08] <sil2100> rsalveti: it should all be handled, as to CITrain it doesn't really matter where the final merge happens - it doesn't have to be trunk, it can be any branch
[15:08] <rsalveti> sil2100: right, cool then
[15:09] <Mirv> rsalveti: sil2100: uh oh, ok. I've many uploads of telepathy-qt5 to the PPA, now they're outdated wrt that.
[15:10] <sil2100> uh
[15:10] <Mirv> https://launchpad.net/~ci-train-ppa-service/+archive/landing-006/+sourcepub/4011677/+listing-archive-extra - basically just the last two, powerpc + ppc64el + arm64 symbols
[15:11] <Mirv> so I'd need to do ubuntu12 and incorporating those changes plus rewriting the changelog
[15:12] <rsalveti> oh, indeed
[15:12] <Mirv> (telepathy-qt5 is not in CI train)
[15:25] <mterry> boiko, https://code.launchpad.net/~mterry/telephony-service/greeter-ringtones/+merge/210506 is the other one
[15:26] <mterry> boiko, this is so that the greeter knows which user to look up the ringtone for
[15:26] <mterry> er, so that telephony-service knows which user to look it up for
[15:26] <mterry> mostly just moving code around
[15:33] <attente> hi
[15:37] <Mirv> rsalveti: ok telepathy-qt5 resynced with archive in qt 5.2 landing PPA. this is partly why it'd be nice to land Qt 5.2 sooner rather than later - there are maybe 20 manual uploads in addition to Qt and CI Train packages in the PPA
[15:38] <Mirv> yesterday I updated lightdm, but that at least is just a rebuild
[15:40] <rsalveti> Mirv: yeah, we're getting there :-)
[15:42] <mdeslaur> what's the status with MMS messages, are they supported yet?
[15:43] <awe__> mdeslaur, no
[15:43] <mdeslaur> ok, thanks
[15:43] <awe__> mdeslaur, that said, the work is currently in-progress
[15:44] <ogra_> we'll just wait until they are nobsolete :)
[15:44] <ogra_> -n
[15:44] <awe__> but can't give you an ETA of when it will land yet
[15:44] <mdeslaur> cool, looking forward to that
[15:44] <rsalveti> another mms user?
[15:44] <ogra_> yeah, seems there are a few rich people
[15:44] <rsalveti> haha
[15:44] <mdeslaur> what, nobody ever gets pictures?
[15:44]  * rsalveti never used mms before
[15:44] <awe__> ogra_, yea maybe.  We'll see what all the WhatsApp folks think once FB starts trying to "monetize".  ;)
[15:44] <ogra_> mdeslaur, i send email ... sending pics by MMS in europe i would get away cheper by making a postcard out of it
[15:45] <rsalveti> we got other similar apps now
[15:45] <mdeslaur> oh, interesting, quite the opposite here
[15:45] <rsalveti> telegram is the new thing it seems
[15:45] <ogra_> well, thats just another whatsapp
[15:45] <rsalveti> yeah
[15:45] <ogra_> but open at least
[15:46] <ogra_> in europe many people moved to threema
[15:46] <awe__> ogra_, some operators don't charge all that much for MMS anymore... I mean seriously, w/4G bandwidth, you're not burning much data sending tiny images ( VGA/QVGA )
[15:46] <ogra_> awe__, tell that to our carriers in europe (or the rest of the world thats not north american)
[15:46] <rsalveti> ogra_: is it open as well?
[15:46] <ogra_> rsalveti, nope, fully closed
[15:47] <rsalveti> right, let's wait someone to create an app compatible with telegram at least
[15:47] <ogra_> but at least has end to end encryption (they say) it was the best in plenty security tests
[15:47] <cjwatson> my wife sends MMSes sometimes, I don't think I get any others
[15:50] <rsalveti> it seems we got someone working on it
[15:50] <rsalveti> https://code.launchpad.net/~rmescandon/ubuntu-telegram-app/trunk
[15:51] <jdstrand> MMSes?
[15:51] <ChickenCutlass> rsalveti: that's awesome
[15:51] <jdstrand> I get them all the time from friends an family
[15:52] <jdstrand> well, I should say that friends and family send them to me and are disappointed when I don't respond cause I don't see them
[15:52] <rsalveti> sergiusens: you can have your friends back, just ask them to move away from whatsupp and start using telegram :P
[15:52] <rsalveti> haha, mms is really a us thing
[15:52] <jdstrand> interesting
[15:53] <sergiusens> rsalveti, nice
[15:53] <mpt> Hm, I guess call roaming is SIM-specific
[15:53] <ogra_> yeah, they should have called it US-media-service :)
[15:53] <jdstrand> it is pretty important to US people. I've asked everyone who has sent me an MMS that I didn't receive if they know about whatapp, and they've all said 'no'
[15:53] <sergiusens> jdstrand, yeah; mms isn't really designed the right way
[15:53] <sergiusens> they got the billing part right
[15:53] <jdstrand> maybe
[15:54] <jdstrand> but as someone who dogfoods the phone, I don't really care. I just know that people aren't too impressed that I can't receive MMSes
[15:55] <jdstrand> (note, this is like a weekly thing for me-- friends and family like to send pictures and things via MMS, and I lose)
[15:56] <cjwatson> mms is hilarious on at least some phones that don't support it
[15:57] <cjwatson> you get the raw control data over sms ...
[15:58] <jdstrand> interesting
[15:59] <awe__> jdstrand, we're working on it...but unfortunately there wasn't a working out-of-the-box solution
[15:59] <jdstrand> awe__: oh! that is awesome. I knew it was on a todo list, but I thought I heard it was deferred
[16:00] <jdstrand> glad to hear it isn't forgotten (which is why my tone was what it was :)
[16:00] <sergiusens> we're refactoring a couple of things
[16:00] <awe__> I too want to be able to shitty concert photos from friends & family!
[16:00] <jdstrand> I apologize if I was a bit snarky
[16:00] <sergiusens> lower layers should be done soon (at least the receive part)
[16:00] <jdstrand> awe__: yes! :)
[16:00] <awe__> s/able to/able to get/
[16:00] <awe__> jdstrand, no worries!
[16:01] <jdstrand> I meant to be only snarky enough to persuade people it is important :)
[16:01] <awe__> to me, the big dealkiller for the longest time was not getting voicemail notifications!
[16:01] <jdstrand> awe__: yes. that is a pain. however, as a tmobile user I found a workaround for that
[16:02] <jdstrand> awe__: are you on tmobile?
[16:02] <awe__> yes
[16:02] <jdstrand> let me find the bug
[16:02] <awe__> has someone written a t-mobile visual voicemail app for touch that I don't know about??? ;D
[16:02] <jdstrand> or maybe I shouldn't, so you stay motivated :P
[16:02] <awe__> haha
[16:02] <jdstrand> awe__: hah, no, not that far
[16:04] <jdstrand> awe__: I can't find the bug, but basically, I noticed that whenever I got a voicemail, I would get a text from 18056377243
[16:04] <jdstrand> awe__: so I created a contact named 'Voicemail - TMobile' with that number
[16:04] <awe__> jdstrand, yes... the core ofono wasn't consuming the message-waiting SMS
[16:05] <jdstrand> awe__: now when I receive that text, it says in the indicator and the messaging app that I got something from 'Voicemail - TMobile'
[16:05] <awe__> this is still a problem with ATT voicemail notification; there's a bug I'm working on for this
[16:05] <jdstrand> so I know I have a voicemail
[16:05] <awe__> pmcgowan filed it.  he gets a text from 10001000 with a  bunch of hex
[16:05] <awe__> jdstrand, great idea!
[16:05] <awe__> ;)
[16:06] <jdstrand> I have another one for '129'
[16:06] <jdstrand> I forget which does what
[16:07] <jdstrand> but yeah, setup a contact for the number you get from them :)
[16:15] <john_____> Good evening from Greece, Crete.... How i can install ubuntu on my tablet.... anyone???
[16:16] <john_____> anyone??
[16:18] <t1mp> john_____: everybody is busy in the UDS http://summit.ubuntu.com/uds-1403/2014-03-12/
[16:18] <t1mp> john_____: but have a look at https://wiki.ubuntu.com/Touch/Install
[16:18] <popey> also !devices | john_____
[16:18] <popey> bah
[16:18] <t1mp> !devices | john_____
[16:18] <t1mp> :)
[16:18] <popey> thanks
[16:19] <popey> if it's not on that list.. it needs porting
[16:20] <john_____> my tablet its inside....
[16:21] <john_____> its supporting but i need help because i dont understanding
[16:22] <john_____> ¨)
[16:22] <popey> john_____: which tablet?
[16:22] <john_____> :)
[16:22] <john_____> Galaxy tab 7.7 P6800
[16:23] <john_____> im trying to install but i I did not accomplish him
[16:23] <john_____> sorry for my bad english
[16:24] <popey> john_____: probably best to contact the person who made the port.
[16:25] <john_____> how??? maybe you know how i can contact him
[16:26] <popey> https://launchpad.net/~dun1982 there's a button in the top right
[16:27] <john_____> Perfect!! Nice to meet you and thanks for advice and help!!
[16:27] <mpt> awe__, does it make sense for multiple SIMs to use automatic carrier selection? Would they ever end up with different carriers if you did that?
[16:27] <john_____> *your advice and help
[16:29] <awe__> mpt, yes and ?
[16:29] <awe__> I'm not sure I understand your 2nd question
[16:29] <awe__> auto carrier selection means that the SPN on the SIM will be preferred, unless not available ( roaming )
[16:30] <awe__> sorry not SPN, SP
[16:30] <awe__> basically the phone will try to select the carriers specified by each SIM automatically
[16:31] <awe__> so if I have an ATT SIM and T-Mobile SIMs in the phone, both will be automatically selected if available ( ie. I'm not roaming )
[16:31] <awe__> now I could have a T-Mobile in one SIM
[16:31] <awe__> and an Orange SIM from the UK in the other slot
[16:31] <awe__> I might in that case choose to manual selection for the slot with the Orange SIM
[16:32] <awe__> because one local carrier might have cheaper roaming rates and/or better coverage
[16:55] <ikhthiandor> Hi folks! When is official support for Nexus 7 2013 edition is expected to be available?
[16:56] <cwayne> ikhthiandor, right now! it's already supported
[16:57] <ogra_> ikhthiandor, since a while :)
[16:58] <cwayne> zsombi, btw: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1291485
[16:58] <ikhthiandor> great job!
[16:59] <ikhthiandor> I checked a week earlier. I think it wasn't supported then
[17:08] <cwayne> sergiusens, random question -- do we have a plan for removing preinstalled clicks?
[17:10] <sergiusens> cwayne, like for customization?
[17:10] <cwayne> sergiusens, yeah, i mean we already have a way to ship preinstalled clicks for customization but
[17:10] <cwayne> what if an oem/carrier doesn't want to ship a phone with a preinstalled terminal app?
[17:11] <sergiusens> cwayne, the answer is no from my side; not even sure who would guide this decision
[17:11] <sergiusens> cwayne, yeah; I understand that fully; given that it's in the store; they can't do much if they want to work around the 'access' part
[17:12] <sergiusens> cwayne, I'm going to drop this on pmcgowan :-)
[17:12] <rsalveti> maybe we don't have them by default at all
[17:12] <rsalveti> and instead ship a default custom tarball
[17:12] <rsalveti> that would have them
[17:12] <sergiusens> rsalveti, yeah, but the 'what are you trying to solve' comes to mind
[17:12] <cwayne> well, this goes to the one unified rootfs too
[17:13] <rsalveti> base image would then be the minimal and common for all images
[17:13] <sergiusens> if it's not there to prevent snooping or stealing drm or whatever; then the purpose is moot as it's on the store
[17:13] <cwayne> because atm, these are built directly into the rootfs, which is wrong
[17:13] <rsalveti> sergiusens: but we might decide to have a few preinstalled
[17:13] <rsalveti> cwayne: exactly
[17:13] <rsalveti> that's my point
[17:13] <sergiusens> cwayne, so mayhaps all images should be custom
[17:13] <rsalveti> it's like CM and google apps
[17:14] <rsalveti> or AOSP
[17:14] <sergiusens> rsalveti, that's different though
[17:14] <sergiusens> it's political
[17:14] <ogra_> you should be able to uninstall them though
[17:14] <sergiusens> ogra_, yes and no
[17:14] <rsalveti> ogra_: but a carrier might want something not installed by default
[17:14] <cwayne> but you shouldn't have to
[17:14] <rsalveti> yeah
[17:14] <ogra_> not sure that persists over an OTA upgrade though
[17:14] <sergiusens> ogra_, it doesn't
[17:14] <ogra_> i guess they would come back
[17:14] <rsalveti> that's why I'd prefer having default-rootfs + default-custom-ubuntu-tarball for our default images
[17:14] <ogra_> right
[17:15] <rsalveti> and then default-rootfs + carrier-custom-tarball
[17:15] <sergiusens> rsalveti, yeah, that's my mind set too
[17:15] <cwayne> rsalveti, we can handle multiple custom tarballs, right?
[17:15] <ogra_> rsalveti, hmm, no
[17:15] <sergiusens> rsalveti, we can also have tablet and phone differences in an easier fashion
[17:15] <rsalveti> cwayne: not sure
[17:15] <ogra_> you would want a basic set of apps too ...
[17:15] <rsalveti> sergiusens: exactly
[17:15] <ogra_> default-rootfs + default-custom-ubuntu-tarball + carrier-custom-tarball
[17:15] <sergiusens> ogra_, like the dialer on a tablet?
[17:15] <rsalveti> ogra_: sure, but they would then be part of the default-rootfs
[17:16] <ogra_> sergiusens, no, but the dialer on all phone images
[17:16] <rsalveti> ogra_: but for example, we shouldn't add terminal app by default
[17:16] <rsalveti> but we could add that as part of default-custom-ubuntu-tarball
[17:16] <ogra_> well, i still thik we would want a three layer thing
[17:16] <rsalveti> don't need to be a three layer thing
[17:16] <ogra_> rootfs without any apps and default theme
[17:16] <rsalveti> as the carrier could end up replacing all the default apps
[17:16] <ogra_> one layer with the default apps
[17:17] <rsalveti> (click apps)
[17:17] <ogra_> and an OEM layer on top
[17:17] <sergiusens> rsalveti, yeah, it should be allowed to; but that's something bfiller would own; not us ;-)
[17:17] <ogra_> that carrier would be special cased then and just get the rootfs
[17:17] <rsalveti> right, but I don't think that's a special case
[17:17] <sergiusens> that makes the testing plan more complicated as well :)
[17:17] <ogra_> the average carrier still gets dialer and messaging apps preinstalled
[17:17] <sergiusens> the bse image would almost always pass :-)
[17:18] <sergiusens> and the custom ones would differ
[17:18] <rsalveti> if the carrier wants to ship stuff from the default-custom-ubuntu-tarball, they could just make merge it together with carrier-custom-tarball
[17:18]  * sergiusens goes for lunch; seems everything is sorted
[17:18] <ogra_> well, do we actually want to allow that carriers replace dialer or messaging ?
[17:18] <cwayne> sure
[17:18] <rsalveti> right, it's a click package :-)
[17:18] <ogra_> scary
[17:19] <rsalveti> you can replace mostly everything in android
[17:19] <cwayne> what if carrier has wifi-calling or something
[17:19] <ogra_> its a click package that makes a ton of assumptions about the underlying system ... and is deeply integrated there
[17:19] <rsalveti> ogra_: still
[17:19] <rsalveti> ogra_: one could make another dialer-app
[17:19] <ogra_> i wouldnt want that random carriers ship their own broken dialer
[17:19] <rsalveti> but should we force them to use our default app?
[17:19] <ogra_> ansd we get blamed for the breakage in the end
[17:20] <rsalveti> guess this is more a product management decision :-)
[17:20] <ogra_> or have people that show up in support with that
[17:20] <cwayne> is dialer even a click yet?
[17:20] <ogra_> like we have today with mint
[17:20] <rsalveti> but we indeed shouldn't be installing the click packages as part of the rootfs
[17:20] <cwayne> rsalveti, +1
[17:20] <ogra_> (ask xnox how much fun he has with tehir hacked up ubiquity in bugs)
[17:20] <rsalveti> they should be part of a custom tarball (the default one)
[17:20] <cwayne> sorry to start a big thing, just wanted to bring up that one point :)
[17:21] <rsalveti> and also allow more than one custom tarball to be used
[17:21] <ogra_> yes
[17:21] <rsalveti> then the rest is up to the management team to decide
[17:21] <cwayne> right
[17:21] <cwayne> exactly
[17:22] <ogra_> not thrilled though :P
[17:22] <ogra_> having to rip apart the build system *again* next cycle
[17:22] <cwayne> it's removing one hook...
[17:22] <cwayne> that frankly, should never have existed
[17:22] <ogra_> and impllementing something completely new
[17:23] <ogra_> that our system has no setup for yet
[17:23] <cwayne> well, doing this right sounds a lot better to me than 'here lets have another separate full rootfs that doesn't have terminal installed'
[17:24] <ogra_> well, doing it right should have done from the beginning ... instead of redoing it three times
[17:24] <ogra_> (but that means that someone would have writtne down a clear plan before anyone started working on it ... which didnt happen)
[17:25] <cwayne> AIUI the plan was always going to be 'one unified rootfs for everything', it's just that it wasn't followed as strictly as it could have been imho
[17:25]  * ogra_ never saw such a plan
[17:26] <cwayne> and i don't think this is particularly super-urgent yet, but it is definitely something we should have in mind before shipping our first phones..
[17:26] <rsalveti> right, that's fine, we can fix it now
[17:26] <ogra_> yes, all i'm saying is that we should really plan that better next time
[17:26] <rsalveti> I'd love if we could do better planning for everything :_)
[17:26] <ogra_> so that we can do it right from the beginning
[17:26] <rsalveti> sometimes it just happens
[17:26] <ogra_> indeed
[17:27]  * ogra_ would really like to have time to optimize at some point ... instead of doing firedrill after firedrill because we missed planning 
[17:33] <jdstrand> ogra_: hey, can you take a look at my comments in bug #1270248 from today and yesterday? I realize the thing that is filling up my disk won't be handled by logrotate... please advise on if you want a new bug
[17:34] <ogra_> jdstrand, well, i had some talks with apw about quietening the kernels ...
[17:34] <ogra_> but that conversation kind of died, i'll take care for it after UDS
[17:34] <jdstrand> ogra_: my comments are for ~/.cache/upstart/mtp-server.log actually. guessing need a new bug
[17:35] <ogra_> ah, yeah, we should quieten that
[17:35] <jdstrand> yes-- 1.2G across a reboot or two is kinda a lot
[17:35] <ogra_> jdstrand, hmm, it shouldnt have had any ill effects on system behavior
[17:36] <jdstrand>  /home fills. I think anything in the user session will have a problem if it creates tmp files, etc
[17:36] <jdstrand> saves configuration, etc
[17:36] <ogra_> root@ubuntu-phablet:/# ls -l /home/phablet/.cache/upstart/mtp-server.log
[17:36] <ogra_> -rw-r----- 1 phablet phablet 423 Mar 11 10:58 /home/phablet/.cache/upstart/mtp-server.log
[17:36] <jdstrand> I can promise you. there are ill effects. if I remove the file, and reboot, everything is fine
[17:36] <ogra_> jdstrand, hrm
[17:37] <jdstrand> I have > 8G of music on my device
[17:37] <ogra_> i thought reserving 5% for root would keep us safe
[17:37]  * ogra_ hacked that into the upgrader
[17:37] <jdstrand> it goes to 100%
[17:37] <ogra_> sigh
[17:37] <ogra_> how can that be
[17:37] <ogra_> if the filesystem is set to reserve 5%
[17:38] <ogra_> so my mtp-server log is tiny
[17:38] <ogra_> on all devices
[17:38] <ogra_> cyphermox, any idea why mtp-server would log so much for jdstrand ?
[17:39] <ogra_> jdstrand, any idea about the contents ?
[17:39] <jdstrand> it was filled with a bunch of stuff for the music
[17:39] <ogra_> oh, it lists every file it exports ?
[17:40] <jdstrand> eg, http://paste.ubuntu.com/7080441/
[17:40] <jdstrand> that was a bad paste, but you get the idea
[17:40] <pmcgowan> cwayne, sergiusens hmm, yeah we need preinstalled clicks to be managed in the click space not the rootfs
[17:40] <pmcgowan> need to be removeable
[17:41] <jdstrand> music and pictures. right now it is on 3MB, but it got to 1.2G between yesterday and today
[17:41] <ogra_> jdstrand, yeah, seems cyphermox added a lot of debugging we should actually remove
[17:41] <jdstrand> and I didn't do anything special
[17:41] <jdstrand> (reboot, connect with adb a few times, etc)
[17:41] <ogra_> http://paste.ubuntu.com/7080450/
[17:41] <ogra_> thats mine ... after multiple days
[17:42] <ogra_> but i dont have any shared files on that device
[17:42] <jdstrand> at the moment, it is mostly behaving-- if I remove the cable and connect it, it is only adding 2M or so
[17:43] <ogra_> it re-reads all contents ...
[17:43] <jdstrand> I faily confident I didn't connect my device 512 times since yesterday though
[17:43] <ogra_> and writes a debug line for every file in the log
[17:43] <jdstrand> s/I faily/I'm fairly/
[17:43] <ogra_> well, i guess it also writes data when you transfer files back and forth
[17:44] <jdstrand> yeah, I didn't actually do that
[17:44] <jdstrand> I guess something runs away at some point. If I hit it again, I'll add more info
[17:45] <ogra_> re-plugging (which means restarting the server) adds ~40k here
[17:45]  * jdstrand nods
[17:45] <ogra_> while thats still to much, thats not a lot
[17:45] <jdstrand> I wonder if 'reboot' is what is doing it
[17:45]  * jdstrand tries
[17:46] <jdstrand> no, it isn't, and I certainly wouldn't have noticed it if that was all it was
[17:47] <jdstrand> no, that didn't do it
[17:47] <jdstrand> weird
[17:47] <jdstrand> up to ~6M now
[17:48] <ogra_> run tail -f on the file in the terminal app :)
[17:49] <ogra_> and then re-plug
[17:49] <ogra_> mtp-server really needs to lose debug output
[17:53] <jdstrand> yeah
[18:10] <sergiusens> pmcgowan, not really uninstalled, but not provisioned in the default rootfs (have a nimble one) and all other images would be custom (like phone-base or tablet-base). Something along those lines; that's where the conversation was headed
[18:10] <pmcgowan> sergiusens, seems like all app installs need to be overlayed
[18:12] <sergiusens> pmcgowan, but new apps (from vendors) would have a different namespace
[18:12] <sergiusens> overlaying could be worked out though
[18:12] <pmcgowan> sergiusens, the terminal example where community wants it and production does not
[18:13] <pmcgowan> could be true for any app
[18:13] <sergiusens> pmcgowan, well it is in the rootfs, so it may be seen; but it will be on image
[18:14] <pmcgowan> sergiusens, yeah, no apps should be in rootfs?
[18:14] <sergiusens> pmcgowan, the cleaner option seems that the vanilla build should just be a custom build
[18:14] <sergiusens> pmcgowan, and for that we need the vanilla build to be a custom one
[18:14] <pmcgowan> was realizing this when we hit the click bug, finally understood it
[18:14] <pmcgowan> yes
[18:14] <sergiusens> ok, so we at least all agree on this
[18:14] <sergiusens> now we just need to do it :-)
[18:14] <sergiusens> let me email the phone list with this
[18:24] <bosnjak> hi all
[18:25] <bosnjak> is it possible to write applications in python that would run on ubuntu touch? What about interfacing the hardware in this way?
[18:34] <cjwatson> cwayne: removing preinstalled clicks - you can hide them in a higher database
[18:35] <cwayne> cjwatson, like having an empty click with no desktop file?
[18:35] <cjwatson> cwayne: no
[18:35] <cjwatson> cwayne: same thing that happens if you remove a preinstalled package as a user now
[18:35] <cjwatson> cwayne: except it'd be an @all -> @hidden symlink in /custom
[18:36] <cjwatson> (not exactly like that, I'm going from memory)
[18:36] <cjwatson> cwayne: there's basically a whiteout scheme
[18:36] <cwayne> cjwatson, hm, is this documented anywhere?
[18:36] <cjwatson> cwayne: we probably want to make some apps non-removable in the topmost (user) database at some point to stop people removing the dialer by accident, but that doesn't have to apply to /custom
[18:37] <cjwatson> cwayne: can't remember, have to run now, sorry
[18:37] <pmcgowan> bosnjak, we do not officially support python in the app sdk, but some folks are playing with that anyway
[18:37] <cjwatson> cwayne: anyway the design allows for this, we just need to polish details I guess
[18:38] <bosnjak> pmcgowan: but there should be no problem with running python in ubuntu, right? The only issue is with the hardware interfacing beyond the SDK? Am i right about this?
[18:38] <sergiusens> cwayne, pmcgowan rsalveti ogra_ sent an email to the list
[18:38] <cwayne> sergiusens, see above bits from cjwatson ^
[18:38] <cjwatson> I suspect you can do something like sudo click unregister --all-users --root=/custom package-name
[18:39] <pmcgowan> bosnjak, the issue is for a "production" app you would need to provide python with your app to ensure it runs
[18:39] <pmcgowan> technically it will work, and for development purposes its fine
[18:39] <sergiusens> cwayne, yeah; I some of that
[18:39] <cwayne> cjwatson, but we shouldn't have to do that
[18:39] <cjwatson> uh?
[18:39] <sergiusens> cjwatson, but if there's an OTA and there are new clicks they would be reinstalled, right?
[18:39] <cjwatson> no
[18:39] <cjwatson> I really have to go, I'll explain later
[18:40] <pmcgowan> sergiusens, the updates would come ota but separate from the rootfs right
[18:40] <sergiusens> cjwatson, sure; I understand you; just want to explore this possibility
[18:40] <bosnjak> pmcgowan: it should be an issue to provide python, right? As long as I have actual access to the device? In that case, this should be straightforward?
[18:40] <cjwatson> sergiusens: I designed all this specifically for this kind of thing
[18:40] <sergiusens> cjwatson, sent an email to ubuntu-phone which you can follow up on
[18:40] <pmcgowan> bosnjak, with complete access yes you are fine, to put an app in the store needs to provide all it needs
[18:41] <bosnjak> pmcgowan: thats enough for me, i have the access to the device.
[18:41] <sergiusens> pmcgowan, hmm, I can't make out your question; OTA are bits of the rootfs if delta type
[18:41] <pmcgowan> bosnjak, be aware of one other thing...
[18:41] <bosnjak> pmcgowan: what about using the tablet hardware, will this approach impact me with this?
[18:41] <pmcgowan> bosnjak, if you flip to write mode and install apps, then system updates may not work
[18:41] <pmcgowan> bosnjak, same on tablet
[18:42] <pmcgowan> sergiusens, in the future, you go into update on system settings and see the system update and the app updates, but they are separate
[18:42] <pmcgowan> sergiusens, so we need to decide if dialer app is treated as system or click
[18:43] <sergiusens> pmcgowan, oh, now I follow; yeah, OTA is for the read only bits; clicks themselves apply to the user/writable bits
[18:43] <sergiusens> pmcgowan, you can still potentially update the dialer; just not remove i
[18:43] <sergiusens> it
[18:43] <pmcgowan> ok
[18:43] <bosnjak> pmcgowan: i see.. what about the question about the hardware?
[18:44] <pmcgowan> bosnjak, right, so we did not provide bindings for python to our platform api, so for example QtSensors works but in python you need to do it
[18:44] <bosnjak> pmcgowan: what about PyQt or PySide?
[18:45] <pmcgowan> bosnjak, that I dont know, which way is the mapping? ie. python talks to qt?
[18:45] <pmcgowan> then it could work
[18:45] <bosnjak> pmcgowan: is there a way to interface hardware beyond the API bindings?
[18:46] <bosnjak> pmcgowan: like in a regular PC?
[18:46] <pmcgowan> bosnjak, you could, but I think platform api would be easier in most cases
[18:46] <pmcgowan> the HAL s from Android and we front end that
[18:46] <bosnjak> pmcgowan: ofcourse, if i could get it to work with python.. I am still considering my options, so i will most likely ask more questions soon :)
[18:47] <pmcgowan> bosnjak, maybe it depends on what you need to access
[18:47] <pmcgowan> bosnjak, or write html and javascript code ;)
[18:47] <bosnjak> pmcgowan: touchscreen, microphone, speaker, buttons, gsm, 3g, wifi, basically everything :D
[18:48] <pmcgowan> bosnjak, well, lots of work I fear, whereas in QML and HTML we do it for you
[18:48] <bosnjak> pmcgowan: i would need some advanced options like cpu core binding, process control, IPC mechanisms, etc. This is why I'm considering the lowest level linux approach instead of HTML+js
[18:49] <pmcgowan> ok
[18:49] <pmcgowan> sounds like a special case
[18:49] <bosnjak> pmcgowan: there is no such options with the sdk, right?
[18:49] <bosnjak> pmcgowan: pretty much
[18:49] <bosnjak> pmcgowan: if i go with c++, maybe then i could use the sdk with the native stuff i need
[18:49] <pmcgowan> bosnjak, the APIs are app oriented, so sounds like not at the level you need
[18:49] <pmcgowan> c++ would be good yes
[18:50] <bosnjak> pmcgowan: hm.. thank you very much for your answers. I need to do more research, and will come back with more q's :)
[18:50] <pmcgowan> bosnjak, sure good luck
[18:50] <bosnjak> pmcgowan: you are a ubuntu developer?
[18:51] <pmcgowan> bosnjak, more manager, but I try ;)
[18:51] <bosnjak> pmcgowan: great. nice to meet you, keep up the good work :D
[18:51] <pmcgowan> thanks
[18:52] <bosnjak> pmcgowan: ah, you went to CMU?
[18:53] <pmcgowan> bosnjak, oh the internet knows
[18:53] <pmcgowan> yes
[18:53] <pmcgowan> a while ago ;)
[18:53] <bosnjak> pmcgowan: yes, your linkedin profile :)
[18:54] <pmcgowan> heh
[18:54] <bosnjak> pmcgowan: i know CMU because Nickolay Shmyrev works there on the CmuSphinx project. Nice people.
[18:54] <pmcgowan> bosnjak, yeah lots of smart folks
[18:55] <pmcgowan> great school
[18:55] <bosnjak> pmcgowan: sounds like it
[18:55] <bosnjak> pmcgowan: anyway, talk to you again :) and thanx
[18:56] <pmcgowan> bosnjak, ok keep us posted
[18:56] <bosnjak> pmcgowan: will do
[19:22] <cwayne> fginther, ping
[19:26] <cwayne> fginther, any idea what's going on here? http://s-jenkins.ubuntu-ci:8080/job/savilerow-trusty/18/console
[19:27] <cwayne> we did change the trunk a bit earlier, maybe we just need to remove the whole thing and start fresh?
[19:28] <fginther> cwayne, looking
[19:30] <fginther> cwayne, I'll clean the workspace out and see if that helps
[19:30] <cwayne> fginther, awesome, thanks
[19:46] <fginther> cwayne, build successful
[19:47] <cwayne> fginther, wonderful, thank you!
[20:32] <boiko> mterry: do you have the second MR for telephony-service already? I have a couple  more pending release, so I could request a release of them all together
[20:32] <mterry> boiko, thought I gave that to you already.  Let me get it again.  probably my IRC ate it
[20:32] <mterry> boiko, https://code.launchpad.net/~mterry/telephony-service/greeter-ringtones/+merge/210506
[20:33] <boiko> mterry: nice! thanks!
[20:37] <boiko> mterry: hmm, I'm not sure I like having the ringtone settings reading in GreeterContacts, sounds a bit odd
[20:37] <boiko> mterry: on the other hand it really makes sense having GreeterContacts as a singleton
[20:37] <mterry> boiko, I can rename the class to "AccountsService" or "GreeterSettings" or some such
[20:39] <boiko> mterry: well, maybe we should keep it like this now, and revisit it later
[20:39] <mterry> boiko, I did try to make its larger scope clearer by renaming "setFilter" to "setContactFilter"
[20:42] <boiko> mterry: yep, saw that
[20:42] <boiko> mterry: let's keep it this way for now, I actually like the fact that the settings reading is out of the ringtone class anyway
[20:42] <boiko> mterry: let me give it a try
[20:54] <boiko> mterry: so looking at the code again, maybe we could have a GreeterContacts::isGreeterMode() or something like that instead of having the qgetenv thing all over the place?
[20:55] <mterry> boiko, sure, makes sense
[20:55]  * mterry does that
[20:55] <boiko> mterry: nice! thanks!
[20:56] <boiko> mterry: do you want me to comment about this on the MR or there is no need to?
[20:57] <mterry> boiko, naw, I got it
[20:58] <mterry> boiko, pushed
[20:59] <boiko> mterry: nice! thanks!
[23:04] <Felsangom> Hello, may I get some help?
[23:07] <Felsangom> I need some help with the Ubuntu Touch installation on a Nexus 4 device
[23:08] <cjohnston_> Felsangom: if you gave some info about the problems your having, it would be easier for people to help you
[23:09] <Felsangom> Well, I'm following the instructions from https://wiki.ubuntu.com/Touch/Install#Manual_Download_.26_Installation
[23:09] <Felsangom> but, when in recovery mode, there is a message "E: Can't mount /sdcard"
[23:13] <vthompson> Image landing and Qt5.2 migration folks: I recently updated my apt repository to include ppa:ci-train-ppa-service/landing-006 and did a dist-upgrade to pull in some of the new stuff for Qt5.2. I noticed it includes both the new mediascanner-2.0 and it seemingly has the media-hub (allows continuous media playback while app is suspended)--with the music-app lifecycle exception removed. My question is, will all this be lan
[23:13] <vthompson> ding at the same time as Qt5.2?
[23:18] <Felsangom> There is a log message that says "E:Can't mount /sdcard"
[23:18] <Felsangom> and, after that: "I:using /data/media for /sdcard"
[23:22] <Felsangom> if I try to mount sdcard using dab shell
[23:23] <Felsangom> *adb
[23:23] <Felsangom> the following error occurs: "mount: can't find /sdcard in /etc/fstab"
[23:38] <ChickenCutlass> vthompson: The media-hub is not going to land with qt 5.2.  But shortly after
[23:39] <vthompson> ChickenCutlass: do you know if the custom component is installed via the ppa I upgraded with?
[23:40] <nhaines> Hmm, I threw the new Ubuntu background over into the phone in my Pictures folder, and I can't get it to show up in the gallery.  Not even if I rename it to jpg.
[23:40] <ChickenCutlass> vthompson: not sure.  I don't think the current media hub should get pulled in.
[23:40] <vthompson> ChickenCutlass: to me it *seemed* like it was because when the music app was suspended it kept playing... but it didn't proceed to the next track because I we haven't stepped up to that part of the media-hub
[23:40] <ChickenCutlass> vthompson: when it is done -- it will support both video and audio
[23:41] <ChickenCutlass> vthompson: the built in music player currently supports background music playing.  It is a special case.
[23:41] <ChickenCutlass> vthompson: but once the media-hub is in.  Any app that uses it will have that option
[23:41] <vthompson> ChickenCutlass: right, I'm one of the music-app devs
[23:41] <ChickenCutlass> lol
[23:41] <ChickenCutlass> right
[23:41] <ChickenCutlass> ok
[23:42] <vthompson> ChickenCutlass: hence why I'm balancing on the cutting edge
[23:42] <ChickenCutlass> vthompson: so the use of media-hub will be pretty transparent.
[23:42] <ChickenCutlass> we will just swap out the under layer
[23:42] <vthompson> ChickenCutlass: except we'll have to change the apps methodology of maintaining the queue of items
[23:43] <ChickenCutlass> vthompson: yes, the playlist part will be slightly different
[23:45] <vthompson> ChickenCutlass: So, if what I'm seeing isn't the media-hub. Then something has changed such that when the app is suspended (screen off) it won't proceed to the next track, but it proceeds to the next track when another app has focus or the music app is "minimized"
[23:46] <ChickenCutlass> vthompson: so not sure.  But I wouldn't rely on any behavior in the ppa.  The real solution will be landing very soon
[23:48] <vthompson> ChickenCutlass: Ok, I'll keep an eye on any lifecycle issues--but most likely I'll try to expedite our step up to jhodapp|afk's media-hub
[23:48] <ChickenCutlass> great
[23:48] <ChickenCutlass> vthompson: the new media-hub is going to be awesome
[23:48] <ChickenCutlass> :)
[23:49] <vthompson> I can't wait until we can let our beast of an app sleep instead of spin all day long :P