[00:00] <studio__> lotuspsychje, without a "nearly" guide i don't like to try, because i don
[00:00] <studio__> 't like to breake my system
[00:01] <nhaines> Note that switching your phone to readwrite mode means you can never receive Ubuntu updates again.  You'll have to reflash your phone first.
[00:02] <lotuspsychje> would be wiser to just accept the default background unlock screen then :p
[00:02] <studio__> hmm, i figured out, without a ubuntu one account i also can't update my system :(
[00:03] <DonkeyHotei> i'm curious: would a port to a phone with a locked bootloader be possible using safestrap?
[00:04] <nhaines> studio__: that is correct.
[00:04] <nhaines> studio__: you can still get system updates though!
[00:05] <studio__> how?
[00:05] <nhaines> studio__: System Settings > Updates
[00:05] <studio__> i am on 27.02. for exp, but i do nt get updates
[00:05] <DonkeyHotei> no idea?
[00:05] <studio__> wait
[00:06] <nhaines> studio__: it depends on what channel you're on, but if you're on ubuntu-rtm/stable or ubuntu-rtm/14.09, the last update was Friday.  They only update every 2-4 weeks.
[00:07] <studio__> " it depends on what channel you're on" i am on bq rc
[00:07] <studio__> and it tells me i need an account
[00:07] <nhaines> studio__: then you can expect an update every 3-4 weeks.
[00:07] <nhaines> You need an account to get application updates, but your system itself will stay up to date.
[00:08] <studio__> ok
[00:08] <lotuspsychje> nhaines: rtm/14.09 still working smooth on my n7 here tnx again!
[00:08] <nhaines> lotuspsychje: that's good!
[00:09] <nhaines> I hope they spend time working on the tablet interface this cycle.
[00:09] <studio__> what is the latest version, 14.09 or 14.10?
[00:09] <lotuspsychje> its strange its working better then channel=devel
[00:09] <lotuspsychje> scopes are fast and stable on rtm
[00:10] <nhaines> studio__: 14.10.  The channel is named differently for developmental reasons, but the OS is still 14.10.
[00:10] <studio__> ok
[00:11] <nhaines> In about a month or so they'll get ready to switch to 15.04, and that will be exciting.  :)
[00:11] <lotuspsychje> :p
[00:11] <nhaines> studio__: it'll just happen with a system update.  You won't notice anything.
[00:12] <nhaines> lotuspsychje: first time an imaged-based update will upgrade Ubuntu on a retail device without reflashing.  I think that's exciting.
[00:12] <nhaines> It'll be really good news for Snappy Ubuntu Core when it works.
[00:12] <lotuspsychje> nice
[00:13] <lotuspsychje> this looks nice on the twitter too: Ubuntu Phones, Convergence, Snappy Ubuntu Core to Be Showcased at MWC 2015
[00:13] <studio__> but what about john-mcaleely an his work, is it only "experimental"?
[00:14] <nhaines> studio__: I don't know what you're referring to.
[00:14] <studio__> https://wiki.ubuntu.com/Touch/Devices
[00:17] <nhaines> The only thing he did on that page was rename the BQ Aquaris entry and resort the table of ports.  I don't know what you mean by his work.
[00:17] <lotuspsychje> oh nice that telegram app works for android too
[00:19] <nhaines> If you mean the link to the port, it's not "experimental".  It's the official software released on the bq Aquaris Ubuntu Edition.
[00:22] <studio__> i do not understand, http://people.canonical.com/~jhm/barajas/ shows 14.09, but bq rc is 14.10
[00:23] <nhaines> studio__: 14.09 is a code name based on developmental reasons.  The OS is 14.10.
[00:23] <studio__> so it is "just" a mirrow?
[00:24] <nhaines> No.  It's a carefully curated image that's been thoroughly tested.  It matches the same images you'll get through System Settings > Updates
[00:26] <studio__> hmm, i was first on "stable", then i changed to "rc", and wor i am not sure, what is good for "daily" images ... :( i'd like to test and try ...
[00:27] <studio__> wor=now, sorry
[00:28] <lotuspsychje> studio__: did you check this page? https://developer.ubuntu.com/en/start/ubuntu-for-devices/image-channels/
[00:28] <nhaines> They've been renaming the images lately to clean them up.
[00:28] <nhaines> studio__: I should warn you that the daily images are often broken.
[00:29] <studio__> yes, but it is only for google-devices
[00:29] <lotuspsychje> ive seen Bq images too on the list channels command
[00:29] <studio__> nhaines, no risc no fun!
[00:30] <studio__> the bq E4.5 is just for learning
[00:33] <nhaines> I don't think there's a channel for that at the moment.
[00:34] <nhaines> I'm not seeing 14.09-proposed anymore, and devel-proposed (which is vivid) has been broken for two months.  I wouldn't recommend tryng that until they get another promoted image.
[00:35] <studio__> therefore i thought  john mcaleely can answer some questions, but he is offline ....
[00:38] <nhaines> I don't know if I've ever seen him in here.
[00:38] <nhaines> In any case, you can always ask your question to the mailing list.
[00:39] <studio__> i know, but i prefer personal/direct contact, therefore i am here
[00:41] <nhaines> at 11:42pm on a Sunday night.
[00:42] <studio__> ok :) and what about rsalveti? also only on weekend?
[00:43] <nhaines> Most Canonical employees are only in here during European working hours Monday-Friday.
[00:44] <studio__> i thought he's from brazil?
[00:45] <nhaines> I don't know.  He's still not here on weekends.  :)
[00:45] <studio__> :)
[00:46] <DonkeyHotei> rsalveti is in brazil
[00:46] <studio__> ok
[00:46] <DonkeyHotei> i know for a fact he will be around tomorrow
[00:48] <DonkeyHotei> so, no idea about the locked bootloader question?
[00:50] <DonkeyHotei> well, it's already tomorrow in europe
[00:58] <studio__> one last question for today, where is the different between "ubuntu-device-flash" and
[00:58] <studio__> Ubuntu SDk
[00:58] <studio__> Tools - Ubuntu - Device  Control - Flash daily image on device
[00:59] <studio__> ?
[01:06] <nhaines> Why do you think they are different?
[01:07] <studio__> i don't know, it was just a question. is it the same?
[01:13] <studio__> have to go to sleep, it's too late, maybe you could answer offline and i'll read it tomorrow ... thanks for help for today.
[01:13] <studio__> bye
[01:15] <DonkeyHotei> nhaines: do you know enough about the hardware enablement to know whether that can be done?
[01:17] <nhaines> DonkeyHotei: whether what can be done?
[01:17] <DonkeyHotei> ubuntu-touch on a device with a locked bootloader using safestrap
[01:18] <DonkeyHotei> that is, with the stock signed kernel
[01:21] <Wanzt> I don't think that's possible. Most probably the bootloader has to be unlocked in order for safestrap to work.
[01:22] <Wanzt> Oh, no - that's multirom...
[01:22] <nhaines> I don't know anything about safestrap.
[01:27] <k1l> seems like some samsung kexec thingy
[01:28] <nhaines> k1l: well, that's already how MultiROM Manager works.
[01:29] <Wanzt> safestrap seems not to need an unlocked bootloader and doesn't touch the main rom
[01:34] <DonkeyHotei> k1l: afaik it does not use kexec but just runs the rom under the stock kernel, but i could be wrong
[01:35] <DonkeyHotei> question is, would that be enough for ubuntu-touch
[01:37] <k1l> it uses kexec to "boot" custom kernels
[01:37] <nhaines> It wouldn't, because Ubuntu requires AppArmor.
[01:41] <DonkeyHotei> well, it it really does use kexec, it could kexec an apparmor-enabled kernel, no?
[02:24] <nhaines> DonkeyHotei: correct.
[02:25] <DonkeyHotei> interesting
[04:24] <cpatrick08> I was wondering why there are still grouper images on the ubuntu cdimage website as seen at http://cdimage.ubuntu.com/ubuntu-touch/ubuntu-rtm/14.09/daily-preinstalled/pending/ for an example. I though that grouper was deprecated
[04:50] <nhaines> cpatrick08: it is deprecated.
[04:51] <cpatrick08> so why are they being build on the cdimage site
[07:18] <peat-psuwit> Do you have any hint on debugging video playback?
[07:54] <dunebuggie> Guys, is it possible to flash Ubuntu Touch on a Micromax Funbook?
[07:55] <DonkeyHotei> dunebuggie: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[08:07] <dholbach> good morning
[08:08] <dunebuggie> DonkeyHotei: Thanks, but I couldn't find my device listed here: https://wiki.ubuntu.com/Touch/Devices
[08:17] <nhaines> dunebuggie: then you'll either have to port it (using the steps DonkeyHotei linked) or wait for someone else to.
[08:24] <fry_> Where is the ubuntu touch iso for download?
[09:30] <matv1> is the telegrams plugin to notifications center broken  on devel proposed?
[09:31] <matv1> or is that different design from rtm?
[09:59] <nhaines> fry_: There is no universal ISO.  You have to use ubuntu-device-flash to install Ubuntu on a supported device, or the port maintainer's instructions to install a port.
[10:01] <nhaines> fry_: If you're looking for something to install on a PC-compatible system, you can try http://cdimage.ubuntu.com/ubuntu-desktop-next/daily-live/current/ although I actually haven't installed from there--only tried it live.
[10:01] <nhaines> There isn't really anything called Ubuntu Touch, so I had to guess what you might have meant.
[10:13] <JamesTait> Good morning all; happy Dr. Seuss Day! :-D
[10:14] <DonkeyHotei> i do not like green eggs and ham
[10:14] <DonkeyHotei> i do not like them sam i am
[10:50] <mandel> elopio, please, let me know whenever you are around, we need to talk about some testing with the browser and 7 digital
[11:11] <tsdgeos> oSoMoN_: we don't support autorization requests in ewbbbrowser?
[11:16] <tsdgeos> oSoMoN__: we don't support autorization requests in webbbrowser?
[11:25] <popey> tsdgeos: not yet. known bug
[11:25] <tsdgeos> oki :)
[11:25] <tsdgeos> is it reported or shall i report it?
[11:29] <popey> tsdgeos: bug 1422534
[11:29] <tsdgeos> tx
[11:29] <popey> np
[11:33] <oSoMoN> rpadovani, hey, there’s a trivial conflict in debian/control when merging the latest trunk in https://code.launchpad.net/~rpadovani/webbrowser-app/addressBarFullWidth/+merge/239039
[11:36] <peat-psuwit> Excuse me, can libandroid_runtime be built in Ubuntu Phone's tree? My device's GPS library seems to need it.
[11:37] <rpadovani> oSoMoN, fixed, thanks!
[11:39] <oSoMoN> rpadovani, thanks
[11:41] <oSoMoN> rpadovani, sorry, that’s incorrect, your branch re-adds the build dependency on qtdeclarative5-private-dev which was removed a few days ago, it shouldn’t
[11:42] <rpadovani> oSoMoN, oh, I see now, I was indeed a bit confusing, sorry. Fixed!
[11:42] <rpadovani> *confused
[11:46] <oSoMoN> thanks!
[11:56] <rsalveti> nik90: hey, sorry, just noticed I had one ping from you last friday
[12:02] <elsewho> hi
[12:02] <elsewho> is ubuntu touch a real native linux. can i run background services, have full acess to hardware and gcc?
[12:03] <janimo> elsewho, should be similar to a regular ubuntu device, yes
[12:03] <elsewho> thats awesome!
[12:03] <elsewho> thank you.
[12:04] <janimo> elsewho, although its similarity may be influenced by however the vendor will chose to restrict the phone it that happens
[12:04] <ogra_> it is a real native linux but you can not run background services by default (you can hack it though) and by design the rootfs is readonly ... you can access the hardware via the platform api and indeed can install gcc
[12:04] <janimo> elsewho, the default images currently flashed do not have the full archive at your disposal, only a subset, but can be solved by reflashing a custom image
[12:05] <nhaines> janimo: err, that's not really true at all.
[12:05] <janimo> ogra_, you can not run backround apps from the command line?
[12:05] <janimo> nhaines, which part of it?
[12:05] <ogra_> janimo, you can ... thats what i meant with "hack it"
[12:05] <nhaines> That the default images don't have the full archive at your disposal.
[12:05] <elsewho> ok, crazy. i am still waiting for a smart phone that is like a real computer!
[12:05] <ogra_> you would want to create an upstart job in your home dir or some such
[12:05] <janimo> nhaines, in my experience it does not
[12:05] <nhaines> You just enable readwrite mode and update your /etc/apt/sources.list and you're all set.
[12:05] <elsewho> ubuntu touch seems to be the closest thing, that also is stable and user friendly
[12:06] <ogra_> nhaines, except that you break upgrades
[12:06] <nhaines> ogra_: sure, but there's nothing to be done about that.  There's no custom image to reflash.
[12:06] <ogra_> elsewho, you wont find a phone like that :) even in the future ...
[12:06] <janimo> nhaines, well, that means the default image does not have the full archive at your disposal. Changing to another apt target qualifies as modifying the default
[12:06] <ogra_> elsewho, but yeah, ubuntu is as close as it will get
[12:07] <nhaines> janimo: I disagree with that.  That certainly doesn't equal "flashing a custom image".
[12:07] <ogra_> the "default image" ?`
[12:07] <nhaines> You might as well say that a default Ubuntu install doesn't have the full archive at your disposal because multiverse isn't enabled.  I don't remember whether universe is before you run Software Center.  :)
[12:07] <janimo> nhaines, true. I ignored the change apt sources step as it may be risky to dist-upgrade there but indeed it is valid
[12:08] <ogra_> note that the "default image" is a roling release ... while the curent phones are pre-installed with a special build, this will just change to standard vivid soon
[12:08] <nhaines> ogra_: I'm looking forward to that!  :)
[12:08] <ogra_> nhaines, 80% of the touch packages still live in universe, so indeed that is enabled
[12:08] <nhaines> ogra_: I was thinking of the desktop system, not the phone.
[12:09] <elsewho> when using ubuntu, i always tried to use LTS version, actually im gentoo/arch user and i advice people to use ubuntu wgen stepping away from windows. is ubuntu roling release now?
[12:09] <ogra_> multiverse isnt and would be pointless ... there isnt much arm stuff in there
[12:09] <nhaines> elsewho: no.
[12:09] <ogra_> elsewho, the phone is, yes
[12:09] <elsewho> ah ok.
[12:09] <ogra_> desktop will follow suit when convergence is ready
[12:09] <ogra_> i would assume around 16.04
[12:09] <janimo> nhaines, multiverse contents is not usually what someone using the term native linux environment thinks of first, but acces to something like git is :)
[12:10] <nhaines> janimo: I don't think so.  VLC is the first thing I want to install.  :)
[12:10] <janimo> a developer point of view at least
[12:10] <nhaines> ogra_: I'd be curious to see documentation about release cadence and so forth then.
[12:10] <janimo> nhaines, ok, I was thinking what a regular command line user or tinkerer would want from the phone when asking is it regular linux
[12:10] <ogra_> nhaines, just follow snappy :)
[12:11] <ogra_> nhaines, eventually snappy will become the base of everything
[12:11] <nhaines> ogra_: but at the moment I'm very curious to see what Will Cooke is up to over at MWC.  Is there any way to follow along with that this week?  :)
[12:11] <ogra_> beyond G+ posts ?
[12:11] <ogra_> not sure
[12:11] <lotuspsychje> twitter shows some usefull stuff
[12:11] <ogra_> i doubt they have much time to take videos and share them etc
[12:11] <nhaines> Yeah.  I'll have to keep a closer eye on insights.ubuntu.com maybe.
[12:12] <lotuspsychje> https://twitter.com/ubuntu
[12:12] <ogra_> right and G+ and twitter will occasionally get pics and reports i guess
[12:14] <popey> yeah, the booth is usually rammed busy
[12:14] <popey> they work >12 hour days
[12:14] <nhaines> popey: they should block out 15 minutes of every hour to update the social feeds.  :)
[12:14] <popey> good luck with that
[12:15] <ogra_> we should pay some community stalkers to do that ;)
[12:15] <nhaines> SCALE a week ago was insane and that was only 3000 or so people.  Lots of fun though.  :)  Happy I didn't get sick this year.
[12:16] <nhaines> ogra_: +1
[12:32] <Vishnudev> Hi guys n
[12:33] <Vishnudev> anyonethere?
[12:34] <matv1_> Vishnudev just ask what you want to know. if ppl know they will respond
[12:35] <Vishnudev> Is there any official ports of ubuntu touch for nexus 6?
[12:35] <nhaines> No, and there never will be.
[12:35] <nhaines> !devices
[12:36] <k1l_> because we hate the nexus6, its to biggy ;p
[12:37] <Vishnudev> @nhaines why are you saying ther never be? Its good for the dev community to allow the
[12:38] <Vishnudev> OS intalled and tried in multiple devices
[12:38] <popey> nhaines: why never?
[12:39] <nhaines> popey: it's what Canonical has said over and over.
[12:39] <Stskeeps> popey: it's incredible anybody survives this environment
[12:39] <nhaines> If I had to guess, the Nexus 4 would be replaced by a retail Ubuntu device in the future.
[12:40] <nhaines> That's, naturally, mere supposition.
[12:40] <Vishnudev> the link https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/ looks promising :)
[12:40] <Vishnudev> Don't know how tough it will be
[12:41] <nhaines> Vishnudev: the OnePlus One got ported in a week after that guide was published, and is looking very promising by all accounts.  I'll bet someone has a Nexus 6 build before long.
[12:41] <popey> Stskeeps: hmm?
[12:41] <k1l_> look at xda-developers if someone already got it working
[12:41] <popey> nhaines: just seems a bit final to say "No, and there never will be"
[12:42] <k1l_> no as in no official nexus6 dev device, afaik
[12:42] <popey> Stskeeps: oh, the mwc environment? :)
[12:43] <Stskeeps> popey: yes. just on my first break since the morning
[12:43] <popey> Stskeeps: Keep your fluid levels up! :)
[12:43] <popey> Stskeeps: good to hear you clearly have a busy stand!
[12:44] <nhaines> popey: no sense in purchasing a N6 or waiting around hoping for it.  My advice is either get to work on a port or consider an already supported device, and don't expect supported devices to remain supported long.  And over the past 2 years it's been pretty good advice!
[12:44] <matv1_> jgdx fyi https://bugs.launchpad.net/ubuntu/+source/ofono/+bug/1427009
[12:44] <Stskeeps> popey: yeah.. i need to go check out the canonical one at some point
[12:44] <nhaines> Vishnudev: I can't promise that there will never be an official Nexus 6 port.  But I wouldn't hold my breath waiting for Google to port it.
[12:45] <ogra_> Vishnudev, only if there are kitkat trees for the N6 (or if someone backports an N6 tree to kitkat)
[12:45] <popey> or we move to lollipop
[12:45] <ogra_> the android bits ubuntu uses are 4.4 based atm
[12:45] <ogra_> and that wont change until there is a vendor requiring us to move
[12:45] <Vishnudev> ogra: why there is a kitkat dependanct?
[12:46] <jgdx> matv1_, thanks, that's a well filed bug. I'm looking at the output and seeing that the Connection is bore by edge. One way to dig deeper is to 1) get APN data from your cellular provider and 2) compare this to the current APN settings (easily found by running /usr/share/ofono/scripts/list-contexts
[12:46] <nhaines> My Nexus 5 running Lollipop is running kernel 3.4.0.  I don't remember what it was running on kitkat.
[12:47] <Vishnudev> nahaines but you downloaded a prebuilt version of ubuntu touch
[12:47] <nhaines> Yes, an unofficial Nexus 5 port.
[12:48] <nhaines> It's probably the best way to run Ubuntu if you hate Bluetooth.
[12:48] <ogra_> Vishnudev, we (have to) use the android binary drivers https://developer.ubuntu.com/static/devportal_uploaded/136981fa-6287-49d3-9874-06f40b2e4eb7-cms_page_media/380/ubuntu_touch_architecture.png
[12:48] <ogra_> Vishnudev, see the blue box there
[12:48] <matv1_> jgdx ok i will add that to the bug soon!
[12:48] <ogra_> this is all based on a kitkat tree currently
[12:48] <popey> that diagram needs work
[12:48] <popey> lib
[12:48] <popey> hy
[12:49] <popey> bri
[12:49] <popey> s
[12:49] <ogra_> if you want to do a port you have to merge a kitkat tree for your device into that
[12:49] <popey> also, 14.04.
[12:49] <ogra_> for the N6 there is no kitkat to my knowledge
[12:49] <k1l_> popey: tell the design team ;p
[12:49] <nhaines> popey: vertical text is highly overrated.
[12:49] <jgdx> matv1_, though, you do say that 3g has worked before? Then it's a bit less likely that the APN settings are wrong.
[12:49] <k1l_> wasnt 4.4.4 kernel 3.4 too?
[12:49] <popey> ogra_: where'd you get that image? Is it linked in a page somewhere?
[12:50] <simosx> I am on Ubuntu 14.04.2 and got the ubuntu-sdk-team PPA enabled. "apt-cache policy sdk" shows only a package from 'universe' at version "1.126.1". Is that right?
[12:51] <Vishnudev> ogra_ did you tried to port ubuntu to any phones before?
[12:51] <matv1_> jgdx no I didnt. I used to run rtm images. I switched to 15.04 proposed a couple of days ago. I did a --wipe so that should be considered a clean install i guess
[12:51] <ogra_> popey, its from a talk rsalveti
[12:51] <popey> simosx: should you not use apt-cache policy ubuntu-sdk ?
[12:51] <nhaines> simosx: no, the package you want is 'ubuntu-sdk'
[12:51] <ogra_> *held
[12:51] <ogra_> Vishnudev, yes
[12:52] <Vishnudev> good
[12:52] <simosx> popey, nhaines: my typo, I used 'apt-cache policy ubuntu-sdk' earlier.
[12:52] <Vishnudev> I was going through the porting guid
[12:52] <matv1_> jgdx so i meant that it did work on the rtm images.
[12:52] <popey> simosx: thats only one package, there's others.
[12:52] <popey> simosx: what about qtcreator-plugin-ubuntu ?
[12:53] <Vishnudev> ogra_ I am still not getting why we need kitkat rom for nexus 6
[12:53] <simosx> popey, Here is the output of the command: http://pastebin.ubuntu.com/10501219/
[12:53] <ogra_> Vishnudev, you dont need a rom ... you need a code tree
[12:54] <popey> simosx: what about qtcreator-plugin-ubuntu ?
[12:54] <ogra_> Vishnudev, the lollipop tree will not cleanly merge with the ubuntu kitkat tree
[12:54] <Vishnudev> but in older devices they ported it even before lolipop
[12:54] <simosx> popey, http://pastebin.ubuntu.com/10501229/
[12:55] <popey> simosx: so you're missing that, it seems
[12:55] <popey> bzoltan_:  zbenjamin ^^
[12:55] <popey> bzoltan_: zbenjamin we support sdk from ppa on 14.04? simosx has issues - above
[12:56] <bzoltan_> popey: yes, we do support
[12:56] <bzoltan_> popey: simosx: but the ubuntu-sdk might not be up to date... what is missing?
[12:57] <simosx> bzoltan_, popey: I used to have ubuntu-sdk working, and I assume that some related PPA caused the issues. Have a look at http://pastebin.ubuntu.com/10501239/
[12:57] <jgdx> matv1_, right. It could also be that kpn uses ipv6. Ofono does not support that, but will know when we've looked at the contexts.
[12:57] <simosx> will purge other related PPAs.
[12:58] <Vishnudev> ogra_ I am still getting confuced. In which step we need them to merge? I thought ubuntu repo is completly independed of android. it only taked the kernal/driver files to make the build
[12:58] <bzoltan_> simosx: I guess I know the problem
[12:58] <bzoltan_> simosx: would you tell the apt-cache show qtcreator-plugin-ubuntu
[12:59] <ogra_> Vishnudev, did you look at the picture i gave you above ?
[12:59] <matv1_> jgdx but ofono doesn't support ipv6 in rtm either. And i never had any problem in rtm. So that doesnt seem likely to me
[12:59] <ogra_> Vishnudev, it is drivers and the services that make the drivers work ...
[12:59] <simosx> bzoltan_, http://pastebin.ubuntu.com/10501266/
[13:00] <ogra_> Vishnudev, everything inside the blue box
[13:00] <Vishnudev> ogra_ i red "This is a working gerrit server with everything needed to build the Android images used by Ubuntu Touch. The reference tree in there is based on AOSP (4.4.2 specifically), so make sure your device specific repositories are compatible with AOSP at least."
[13:00] <ogra_> Vishnudev, exactly
[13:00] <Vishnudev> ohh
[13:01] <ogra_> :)
[13:01] <ogra_> so either you need a backported N6 tree for kitkat or you need to wait til we switch our tree to lollipop
[13:01] <ogra_> "just merging" wont work
[13:02] <Vishnudev> the issue will come if there is any driver level change happend for kitkat to lolipop
[13:03] <ogra_> or any of the services/daemons changed
[13:03] <bzoltan_> simosx: the unity-control-center is not sdk related... but he webapp-container is strange. Would you check why it does not install?
[13:03] <ogra_> or the format of init.rc files ... etc etc
[13:03] <jgdx> matv1_, good point. The syslog would be useful too, so we can take a look at what NetworkManager is doing. NetworkManager received a lot of relevant changes in vivid.
[13:04] <simosx> bzoltan_, I had this PPA, https://launchpad.net/~didrocks/+archive/ubuntu/ubuntu-developer-tools-center which I just purged.
[13:04] <popey> didrocks: ^
[13:05] <popey> outrage!
[13:05] <matv1_> jgdx ok will have a look at that and add to the bug
[13:05] <jgdx> matv1_, awesome, thanks.
[13:05] <didrocks> popey: I strongly doubt that this ppa ever had a qtcreator-plugin-ubuntu package :)
[13:06] <bzoltan_> simosx:  I do not see anything in that PPA what could conflict with the SDK
[13:06] <bzoltan_> didrocks:  ^ you have nothing to do with this
[13:06] <bzoltan_> simosx:  let's check that webapp-container
[13:06] <didrocks> bzoltan_: yeah, I'm back at blaming popey anyway :p
[13:07] <bzoltan_> didrocks: that is always a good strategy :D
[13:07] <didrocks> heh
[13:07] <simosx> bzoltan_, also had this PPA, http://chrismwayne.com/?p=277 which I purged.
[13:08] <simosx> bzoltan_, http://pastebin.ubuntu.com/10501349/
[13:08] <nhaines> Oh, I had the Ubuntu SDK installed on 14.10 and tried to run the Telegram app (which I compiled and runs great in ubuntu-desktop-next from a vivid live image) and got the following error message after './run.sh':
[13:08] <nhaines> file:///home/nhaines/app/telegram.qml:226 Type GroupProfilePage unavailable
[13:08] <nhaines> file:///home/nhaines/app/ui/GroupProfilePage.qml:4 module "Ubuntu.Contacts" is not installed
[13:09] <nhaines> I poked around a bit but couldn't find the missing package name.
[13:09] <bzoltan_> simosx: does it install?
[13:10] <simosx> bzoltan_, 'ubuntu-sdk' does not install, http://pastebin.ubuntu.com/10501355/
[13:10] <janimo> nhaines, qtdeclarative5-ubuntu-contacts0.1 ?
[13:10] <simosx> bzoltan_, qtcreator-plugin-ubuntu does not install: http://pastebin.ubuntu.com/10501363/
[13:10] <bzoltan_> simosx:  I know that one ... would you try to install the webapp-container
[13:10] <nhaines> janimo: not installed but there's a candidate.  :)
[13:11] <simosx> bzoltan_, webapp-container does not install http://pastebin.ubuntu.com/10501367/
[13:12] <nhaines> janimo: and now it launches and runs perfectly.  Thanks so much!  :D
[13:12] <Vishnudev> ogra which picture?
[13:13] <Vishnudev> ogra_ can you please put the link again?
[13:13] <bzoltan_> simosx:  As I see your system is bleeding from more than one wound
[13:15] <bzoltan_> simosx:  I am really not sure what is going on there. I would recommend to to first bring your packages in a state where a simple apt-get upgrade returns without errors
[13:16] <ogra_> Vishnudev, https://developer.ubuntu.com/static/devportal_uploaded/136981fa-6287-49d3-9874-06f40b2e4eb7-cms_page_media/380/ubuntu_touch_architecture.png
[13:17] <ogra_> Vishnudev, it is in the porting guide
[13:17] <simosx> bzoltan_, 'apt-get upgrade' shows all clear, 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[13:17] <simosx> bzoltan_, will check any remnants from other PPAs. Thanks.
[13:19] <bzoltan_> simosx:  I am not sure, that last paste shows about a dozen of broken packages in your system. Most likely you have some packages installed from non supported PPAs and they block official packages. I would suggest a major purge session :)
[13:19] <popey> I would "apt-get install ubuntu-desktop^" and see what else you're missing
[13:20] <Vishnudev> ogra_ to be precise current lib Hybris is for 4.4.2 ,
[13:20] <ogra_> Vishnudev, and rild, and openmax ... and other services
[13:24] <simosx> bzoltan_, popey: error on install of ubuntu-desktop, http://pastebin.ubuntu.com/10501538/
[13:25] <simosx> when purging 'ubuntu-sdk' in order to reinstall, I got "E: Release 'trusty' for 'ubuntu-sdk-qmake-extras' was not found".
[13:26] <popey> simosx: no, i said ubuntu-desktop^
[13:26] <popey> simosx: assuming you use unity :)
[13:26] <popey> (the caret on the end is important)
[13:27] <DanChapman>  popey what does the caret actually do? It's saved me a few times but i have no idea how it's magic works
[13:27] <popey> installs the task
[13:27] <popey> not the metapackage
[13:27] <popey> over time some people add/remove all kinds of crap
[13:27] <popey> and sometimes core packages get removed by accident
[13:27] <popey> that re-installs them.
[13:28] <simosx> popey, okay, with 'ubuntu-desktop^' I it's installing packages, X.Org related.
[13:28] <popey> :)
[13:28] <DanChapman> ah that makes sense. Thanks :-)
[13:28] <simosx> popey, also unity, webapps. looks good.
[13:29] <popey> so you probably had something missing which was causing all this nonsene
[13:29] <popey> *nonsense
[13:30] <ChloeWolfieGirl> "something missing" "nonsene" oh Popey you, I hope that was on purpose!
[13:31] <simosx> in the process I reverted to the 3.13 kernel of trusty ;'-(
[13:32] <popey> bzoltan_: what's the framework we should use for 15.04? I don't see ubuntu-sdk-15.04* ? only ubuntu-core-15.04* ?
[13:32] <bzoltan_> popey: whatever your device likes .. my likes 14.10 most
[13:33] <popey> bzoltan_: no good for people on vivid - qt5.4
[13:34] <popey> if someone makes an app that is binary, needs 5.4, then puts in the store with 14.10 framework, it won't work
[13:34] <popey> (this has happened)
[13:34] <popey> https://appstore.bhdouglass.com/app/com.ubuntu.developer.pawstr.headerchallenge
[13:34] <bzoltan_> popey:  I know, we have talked about it with mzanetti and others ...
[13:34] <popey> simosx: not really reverted, but pulled in as it's a dependency, you have a newer kernel too, right?
[13:36] <mzanetti> popey, I guess the issue is that we allow building with 15.04, yet using a framework of 14.10 in the manifest file
[13:37] <popey> that, and I see no framework for 15.04
[13:37] <popey> is ubuntu-core-15.04 our new framework?
[13:37] <popey> (I thought that was snappy only)
[13:37] <mzanetti> hmm... indeed
[13:37] <mzanetti> so far I've only been using 14.10, didn't even notice yet
[13:38] <simosx> popey, I installed the utopic kernel on 14.04.2 per the instructions at https://wiki.ubuntu.com/Kernel/LTSEnablementStack
[13:39] <popey> simosx: ok.
[13:39] <simosx> popey, it's good now, ubuntu-sdk is working. thanks all.
[13:39] <popey> \o/
[15:31] <seb128> what would be the right project to file a bug about a "impossible to go back in webapp, gets user stuck" ... webapps-applications?
[15:31] <seb128> oSoMoN, alexabreu, ^ do you know?
[15:31] <alexabreu> seb128, webbrowser-app, ... mark it w/ a [container]
[15:31] <seb128> (I guess that might already be reported but I didn't find it)
[15:32] <seb128> alexabreu, thanks
[15:32] <alexabreu> seb128, for whic webapp?
[15:32] <alexabreu> which
[15:32] <seb128> alexabreu, e.G googlemap
[15:32] <seb128> if you click on a place, on the "get more details" it brings you to a google search view
[15:32] <seb128> and you can't go back to the map
[15:32] <alexabreu> seb128, ok, add it to webapps-core then
[15:32] <seb128> got the same in google translator
[15:32] <alexabreu> since it is rather specific
[15:32] <seb128> I got an auth page
[15:33] <seb128> can't go back to the previous page
[15:33] <seb128> alexabreu, k, thanks
[16:19] <peat-psuwit> Excuse me, /var/log/syslog on my device disappear. What is the possible causes?
[16:19] <ogra_> a bug
[16:20] <ogra_> what device is that ?
[16:20] <peat-psuwit> ogra_: It's LG L90 Dual. I
[16:20] <ogra_> ah, so you dont use a proper image yet
[16:20] <ogra_> did you ever apt-get update ?
[16:20] <ogra_> or rather upgrade
[16:21] <peat-psuwit> I re-run rootstock-touch-install once, to upgrade preinstall tarball.
[16:23] <ogra_> well, if you used apt inbetween that might have caused this
[16:23] <ogra_> is the dir actually gone ?
[16:23] <peat-psuwit> What directory?
[16:24] <ogra_> /var/log
[16:24] <ogra_> and if not, if you ls -l /var ... who owns it ?
[16:24] <ogra_> (log that is)
[16:25] <peat-psuwit> drwxrwxr-x 11 root android_input 4096 Jan  4 06:34 log
[16:25] <ogra_> thats your breakage then
[16:25] <ogra_> needs to be root.syslog
[16:26] <ogra_> chown it and you should be fine again
[16:26] <peat-psuwit> Oh I see. Thank you!
[17:02] <peat-psuwit> Excuse me, what does "session type" mean in context of RILD?
[17:03] <ogra_> abeato or awe_ should be able to tell you
[17:08] <awe_> peat-psuwit, can you give me some more context for your question?
[17:11] <peat-psuwit> http://paste.ubuntu.com/10503804/
[17:11] <peat-psuwit> Particularly at line 803-804.
[17:13] <Chipaca> rsalveti: whenever you're around, i need to go over the sound volume thing with you again (if it is still with you)
[17:13] <Chipaca> rsalveti: because bug #1426418 is a thing
[17:15] <Chipaca> pmcgowan: nice bit of user-feedback there
[17:15] <Chipaca> pmcgowan: always nice to hear from users :)
[17:16] <pmcgowan> Chipaca, there is a fair bit :)
[17:21] <peat-psuwit> awe_: http://paste.ubuntu.com/10503804/ from "sudo /system/bin/logcat -b radio"
[17:22] <awe_> k, gimme a minute...
[17:23] <peat-psuwit> awe_: Take a look at line 803-804
[17:23] <awe_> yea. got it
[17:24] <awe_> peat-psuwit, http://androidxref.com/4.4.2_r1/xref/hardware/ril/include/telephony/ril.h
[17:24] <awe_> lines1191-1204
[17:25] <rsalveti> Chipaca: right, the silo mode is a thing that would need to be reimplemented at some point
[17:25] <awe_> the parameter give  to a RIL_*_GET_IMSI request
[17:25] <awe_> is an application ID
[17:25] <rsalveti> Chipaca: the way I see it, it would just mean pulse would mute one specific audio role
[17:25] <awe_> I'm certainly no expert on SIMs
[17:25] <Chipaca> rsalveti: the "silo mode"?
[17:25] <Chipaca> rsalveti: not sure what that is :)
[17:25] <rsalveti> and anyone could try to play
[17:25] <awe_> but they basically have the capability to run different apps
[17:25] <rsalveti> Chipaca: *silent
[17:25] <Chipaca> ah
[17:25] <rsalveti> :-)
[17:26] <rsalveti> Chipaca: right now it's up to the client to read the silent mode config value and then deciding to play or not the notification
[17:26] <rsalveti> which is kind of dumb
[17:26] <Chipaca> rsalveti: um
[17:26] <rsalveti> but it is what it is :-)
[17:26] <Chipaca> rsalveti: months and months ago, i asked how to do this, when we were planning roles and stuff, and after some work you told me to set that env var and it would just work
[17:26] <rsalveti> Chipaca: so for that bug, you'd need to query the silent mode value and then deciding to play or not the notification
[17:27] <rsalveti> Chipaca: that is for the right role
[17:27] <rsalveti> Chipaca: not for the silent mode
[17:27] <Chipaca> eeeeewha?
[17:27] <peat-psuwit> awe_: So, "session type" in this case is application ID in the SIM?
[17:27] <rsalveti> that is for one sound to not interfere with the other one
[17:27] <awe_> peat-psuwit, that's what it looks like to me
[17:27] <rsalveti> allowing you to have multiple volumes per audio role
[17:27] <rsalveti> Chipaca: but yeah, in theory that would indeed be enough
[17:28] <rsalveti> but then when silent mode was implemented, they made that just a config, not really using pulse
[17:28] <Chipaca> rsalveti: but volumes do do it by role?
[17:28] <rsalveti> Chipaca: yup
[17:28] <rsalveti> Chipaca: it's just that silent mode has nothing to do with volume current
[17:28] <awe_> peat-psuwit, so in our ofono rilmodem driver
[17:28] <rsalveti> Chipaca: it's just a flag
[17:28] <rsalveti> which is wrong imho
[17:29] <awe_> we grab the aid_str when the SIM is intialized
[17:29] <rsalveti> but well, it's how it was done
[17:29] <awe_> and we then use it later when we send the GET_IMSI request
[17:29] <rsalveti> so you can still have the alert volume to be 100% even when silent mode is enabled
[17:29] <rsalveti> because there is no connection between both
[17:29] <Chipaca> that's ... fucked up
[17:30] <Chipaca> :(
[17:30] <awe_> peat-psuwit, checkout: https://github.com/rilmodem/ofono/blob/master/drivers/rilmodem/sim.c
[17:30] <rsalveti> Chipaca: in theory, what I would like silent mode to be, is simply a mute on the specific role
[17:30] <awe_> and look for 'aid_str' and GET_ISMI
[17:30] <rsalveti> silent mode on -> mute alert role
[17:30] <rsalveti> but not how it got done
[17:30] <rsalveti> that's why I said it would need a rewrite at some point
[17:31] <rsalveti> so for now the only way for you to fix that is client side
[17:31] <rsalveti> but we need to rewrite it to make it system side instead
[17:32] <peat-psuwit> awe_: Well, why RILD complains that session type is not proper, then?
[17:35] <peppelakappa> hello! did anyone tried to port ubuntu touch to moto x 2013?
[17:35] <peppelakappa> the hardware is capable of running it with ease
[17:37] <awe_> peat-psuwit, yea it doesn't like what's being sent
[17:37] <awe_> what device are you working on
[17:37] <awe_> ?
[17:38] <awe_> are you working on a port?
[17:38] <ogra_> yes, hje is
[17:39] <ogra_> LG L90 Dual
[17:39] <peat-psuwit> I'm porting to LG l90 dual.
[17:39] <awe_> got it
[17:39] <ogra_> does the dual mean two sims ?
[17:39]  * awe_ shudders
[17:39] <peat-psuwit> Yes
[17:39] <awe_> hmmmmmmmmm
[17:39] <ogra_> might be you simply get info from the wrong one by default
[17:39] <awe_> so a couple of comments, and then I have to leave to go get some lunch
[17:40] <awe_> I'd happy to spend more time with you later today, or tomorrow as well
[17:40] <awe_> so first problem is that if an OEM
[17:40] <awe_> doesn't use stock android
[17:40] <awe_> they like to make variations of standard RIL messages
[17:41] <awe_> ( addtl parameters, different valid constants for some parameters, ... )
[17:41] <awe_> also, some OEMs like to use non-std RIL requests
[17:41] <awe_> ( ie. not defined by AOSP's ril.h header
[17:41] <awe_> )
[17:42] <awe_> and finally, most dual-SIM implementations were done before AOSP supported dual-SIM
[17:42] <awe_> AFAIK
[17:42] <awe_> so there's yet more custom control of the device required
[17:42] <awe_> if you feel brave, and want to dive into Ubuntu's ofono code
[17:43] <awe_> take a look at ofono/plugins/ril.c
[17:43] <awe_> and mtk.c
[17:43] <awe_> ( the latter is the device plugin that supports krillin; which is a MTK-based modem )
[17:43] <awe_> you also should take a look at ofono/drivers/rilmodem/ and /mtkmodem/
[17:44] <awe_> as mtkmodem leverages rilmodem, but handles many of the quirks I mentioned above
[17:44] <awe_> if there's a Cyanogenmod port, that would give you a good blueprint for what needs to be quirked
[17:44] <awe_> otherwise, it might require some reverse engineering
[17:45] <peat-psuwit> There is cm port for this device
[17:46] <peat-psuwit> In fact, it is the base for my port.
[17:48]  * peat-psuwit feel unlucky
[17:48] <abeato> peat-psuwit, as awe_ says one way of doing the port would doing reverse-engineering, which here means printing the full hex traces if the rild messages in cm and compare with what is being sent by ofono
[17:49] <abeato> also, compare cm code with ofono's rilmodem plugin
[17:51] <awe_> peat-psuwit, don't feel bad... telephony unfortunately is one of those areas that OEMs feel the right to do whatever they want
[17:52] <Chipaca> rsalveti: i was already somewhat upset on friday with having to check settings wrt vibrate; this mute thing is more of the same, but worse. Rage-inducing for me. Hope none of it got your way, and if so sorry.
[17:52] <peat-psuwit> abeato, problem is that I don't know where should I look in CM.
[17:52] <awe_> peat-psuwit, looks for RIL.java to start
[17:52] <awe_> but yea, I feel your pain if this isn't something your familiar with
[17:53] <awe_> in general, Ubuntu works great with devices that run stock AOSP
[17:53] <rsalveti> Chipaca: yeah, I share your pain, we need to improve those things for sure
[17:53] <awe_> and if not, someone has to do the grunt work to make the modem work properly
[17:53] <awe_> peat-psuwit, http://androidxref.com/source/
[17:54] <awe_> is helpful for browing AOSP source
[17:54] <awe_> ( hope that's not something too obvious )
[17:54] <awe_> and you can do searches for stuff
[17:54]  * awe_ wonders if there's a browsable xref for CM online
[17:54] <awe_> anyways, gotta run
[17:54] <awe_> again feel free to ping me later if you have more questions
[17:55] <awe_> ttyl
[18:00] <abeato> peat-psuwit, yeah, it can get tricky, especially for dual SIM devices... but fortunately you have a qcomm modem, which usually do not deviate too much from AOSP
[18:00] <abeato> peat-psuwit, one additional reference:
[18:00] <abeato> https://wiki.mozilla.org/B2G/RIL
[18:01] <abeato> describes the ril messages
[18:44] <DonkeyHotei> ping ChickenCutlass rsalveti
[18:45] <rsalveti> DonkeyHotei: pong
[18:45] <DonkeyHotei> anything i should do to prepare for the interview in just over an hour?
[18:48] <DonkeyHotei> ^^ ChickenCutlass rsalveti
[18:49] <rsalveti> DonkeyHotei: nothing specific for now
[18:50] <DonkeyHotei> i've been doing reading on snappy core
[18:50] <DonkeyHotei> and the hardware enablement layer
[19:08] <Verc> popey? Are you here?
[19:08] <Verc> You
[19:09] <Verc> *You've asked me which websites make my browser reboot the entire telephone Nexus 4
[19:09] <Verc> Well, it's not only the browser. The clock too. And the sound settings too.
[19:10] <Verc> When I tried to set an alarm I changed an hour and during swiping to change the minutes the telephone rebooted
[19:11] <Verc> and when I tried to play my current ringtone the telephone rebooted
[19:11] <Verc> actually it really reboots when it wants to
[19:11] <Verc> and it is really annoying
[19:13] <Verc> And I am not informed about received SMS. I just apperars in Messages
[19:27] <Verc> I've just reflashed and it is the same
[19:27] <Verc> When somebody's calling to me the telephone does not ring
[19:34] <xtr-stuff> Hello
[19:35] <xtr-stuff> I am trying to port to international HTC One and the boot process seems to stop because of: pid:473(ureadahead)(parent:471/sh)  (debugfs) umounted filesystem, does anyone know what this might be due to?
[19:37] <xtr-stuff> I can provide more logs if it helps however I haven't managed to get adb to work yet (which would probably help)
[19:44] <xtr-stuff> I guess I'm asking at a wrong time
[19:49] <Verc> I've got angry and switched back to stable
[19:51] <kenvandine> mandel, what's the status of rtm silo 9?
[19:51] <mandel> kenvandine, hello! I was going to ask you to take it for a sping
[19:51] <mandel> spin*
[19:51] <mandel> kenvandine, before I accept t
[19:52] <kenvandine> mandel, cool, i can test the settings update portion
[19:53] <mandel> kenvandine, that was exactly what I needed
[19:53] <kenvandine> i need to refresh my memory on how to run that test server, i think i documented that in the bug report
[20:12] <xtr-stuff> hey mariogrip, I saw you were making progress on your port, how did you get adb to work? I tried using ogra_'s adbd and adbd.conf files but no luck
[20:16] <Isotop7> hello...i have a problem regarding the twitter app...if i want to connect with my phone number, the app keeps working (shows loading screen) but it doesnt do anything...can somebody help me? i reinstalled it several times...
[20:31] <kenvandine> mandel, good news... settings is now getting the onErrorFound
[20:31] <kenvandine> but, the retry button isn't getting disabled
[20:32] <mandel> kenvandine, hm... weird.. I'll take a look after dinner
[20:32] <kenvandine> mandel, i'll look at it, hang on
[20:32] <kenvandine> this is part of that fix we could never test before
[20:35] <littlegreen> Guys can I get some help resolving a minor issue I'm experiencing atm? I am at a friend's place and I'm trying to get a couple photos out of my phone (It's running the latest stable build on a Nexus4). I hook it up to a windows computer and windows being windows sees the device, but the phone doesn't mount MTP or something like that, the device appears to be "Blank" .. adb sees it, but I'm not familliar with the file structur
[20:35] <littlegreen> e to attempt to pull the files out. Do you have any advice?
[20:36] <Fishscene> I wonder if I have an old script that can do that… standby
[20:37] <Fishscene> Nope. I don't. :(
[20:37] <kenvandine> mandel, wait... is said that wrong... i was thinking the retry button looked disabled, but it actually isn't
[20:39] <Isotop7> do you have enabled the developer mode? dont know if it makes any differences...is it detected in device manager?
[20:39] <Isotop7> if you have access via adb you can also pull files...
[20:39] <littlegreen> Before I enabled developer mode windows didn't even recognize the device... sadly adb shell doesn't work :/
[20:40] <littlegreen> anyway - I am creating a linux live usb to boot up and do things the proper way ;-)
[20:43] <Isotop7> maybe another usb port if you use usb3.0?
[20:44] <littlegreen> tried both USB3.0 and 2.0 it's the same thing
[20:45] <littlegreen> hmmm funny thing - a different usb2.0 port actually works like a charm!
[20:45] <littlegreen> thanks for the tip! :)
[20:46] <Isotop7> no problem!
[20:52] <kenvandine> mandel, the real problem is the progress bar is still showing after the error, and the error isn't being shown
[20:53] <kenvandine> mandel, probably something wonky with those installed, installing and retry variables in the delegate
[21:10] <kenvandine> mandel, if you could take a look, you can base it off my backport branch
[21:11] <kenvandine> mandel, the good news is it's getting the error from udm now
[23:55] <DonkeyHotei> Tassadar: is there some way i can help coding bluetooth for hammerhead?
[23:56] <Tassadar> ...code it?
[23:56] <DonkeyHotei> what exactly is missing?
[23:56] <Tassadar> I dunno
[23:56] <Tassadar> I don't think anybody actually knows
[23:57] <DonkeyHotei> no one has looked into it?
[23:57] <Tassadar> I don't know
[23:58] <Tassadar> I just set-up a server to build the images
[23:58] <DonkeyHotei> who contributes?
[23:59] <Tassadar> pretty much nobody fixes stuff on hammerhead
[23:59] <Tassadar> I fixed some minor issues and rsalveti did the initial bringup, but that's about it