[00:50] <evan__> Having trouble new to ubuntu new hard rive
[00:50] <evan__> drive
[00:55] <krabador> !support
[01:03] <evan__> please help
[01:26] <stu_> Hi -- a bug that I reported a short while ago (https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1422521) was recently set to status fixed. However, the fix is incomplete. Is it enough to add a comment, or do I need to do something more for this bug to be looked at again?
[01:27] <stu_> Hmmm... I see the bot just picked up that I did something.
[01:30] <stu_> But, the status has not changed... Does anyone know if it is possible to get the bug reopened somehow?
[04:13] <muka> are there any plans to support webRTC for web browser?
[04:15] <muka> https://support.mozilla.org/en-US/kb/which-browsers-will-work-firefox-hello-video-chat
[07:25] <aLeSD> hi all
[07:26] <aLeSD> I am interested in porting ubuntu-touch on my device
[07:26] <aLeSD> I found the sources for my devices : https://github.com/bq/aquaris-E5
[07:26] <aLeSD> is it usefull ?
[07:26] <aLeSD> it's the kernel
[07:57] <aLeSD> alò
[07:57] <lotuspsychje> aLeSD: morning
[07:57]  * aLeSD "is anybody out there"
[07:58] <aLeSD> lotuspsychje, hy
[07:58] <aLeSD> hi
[07:58] <aLeSD> lotuspsychje, r u able to compile an ubuntu touch system ?
[07:58] <lotuspsychje> no sorry, im just a happy nexus7 user
[07:59] <lotuspsychje> aLeSD: wich device are you trying?
[07:59] <aLeSD> Bq E5
[07:59] <lotuspsychje> thats the one with android on?
[08:00] <aLeSD> I need someone that point me to the big steps I need ... all the documentation is very foggy out there
[08:00] <aLeSD> lotuspsychje, it is
[08:00] <lotuspsychje> aLeSD: did you try the XDA forums? maybe your device has been ported
[08:00] <nhaines> aLeSD: https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[08:02] <lotuspsychje> nhaines: nice page
[08:06] <aLeSD> nhaines: ok ...
[08:06] <aLeSD> but I need some infos
[08:07] <aLeSD> for example.. I found the page with the kernel for my device source. It's publiched by the maker
[08:07] <aLeSD> is it usefull ?
[08:07] <aLeSD> I mean Do I will compile that kernel ?
[08:08] <aLeSD> mmm
[08:08] <aLeSD> it seems that the deploy of ubuntu touch environment download cyanogen kernel
[08:10] <nhaines> Yeah, you're going to recompile everything.
[08:11] <lotuspsychje> alot of things gonna happen @ MWC15: https://twitter.com/ubuntu
[08:13] <aLeSD> nhaines: ok ... how to know if the hw of my device is supported ?
[08:13] <nhaines> If it's a Nexus 4 or Nexus 7, or if it shipped with Ubuntu, it's supported.  In all other cases, it is not.
[08:14] <nhaines> That's why you'll need to actively port Ubuntu to your hardware or wait for someone else to do so.
[08:14] <aLeSD> nhaines: I'll do it
[08:21] <aLeSD> there something I'd like to konw
[08:22] <aLeSD> What if I install my custom ubuntu-touch and the kernel crash ?
[08:22] <aLeSD> is it possible to return back ?
[08:23] <nhaines> That is entirely up to your device.
[08:24] <nhaines> Nexus devices are nearly impossible to brick, so I've never had to worry about it.  But you'll want to make sure you can completely restore your device from the bootloader.
[08:25] <aLeSD> ok
[08:29] <aLeSD> for example my GPU is a Mali 400
[08:32] <nhaines> I don't believe there are any open drivers for that, so you'll need to reuse the binary driver from your device.
[08:38] <aLeSD> nhaines, it means get into the device (adb) and copy the kenrel modules ?
[08:38] <nhaines> Yes.
[08:38] <aLeSD> that means I have to use the same version of kernel that my device uses ?
[08:38] <nhaines> Correct, which needs to be 3.4.0.
[08:38] <aLeSD> that could differ from the ubuntu-touch one
[08:39] <nhaines> Yes, but you're going to need to patch that kernel to add AppArmor support as well, at least.
[08:39] <aLeSD> the kernl is 3.4.67
[08:39] <nhaines> Might be fine.
[08:40] <aLeSD> so .. the path is to get the binary drivers. compile the ubuntu-touch kernel adding my drivers
[08:40] <nhaines> Yeah, it's all going to be laid out in the porting guide.
[09:00] <aLeSD> nhaines: you mean the cyanogen one ?
[09:56] <taktak> i need help for install to nexus 7
[11:06] <Lihis> Hi, I'm trying to port to new device and I'm currently trying to build recovery, build was succesful but when I boot to recovery I only see a blink of the purple color and then screen goes blank, adb is still accessible.
[11:08] <Lihis> Any help what could be the problem?
[12:33] <strahtw> Hello together!
[12:33] <blackjack_> hello
[12:33] <strahtw> Do someone know if the Ubuntu SDK runs also on a other Debian based distro then Ubuntu?
[12:34] <blackjack_> idk to be honest, I dont see why it wouldnt if you have all the correct libraries though
[12:34] <blackjack_> btw, im trying to port ubuntu touch and im kinda tripped up over a particular issue
[12:35] <strahtw> mh... okay. So I will try it by myself
[12:35] <blackjack_> would anyone be able to guide me in the right direction
[12:35] <strahtw> for that I am the wrong person, sorry…
[12:36] <blackjack_> darn, I asked that in the ubuntu channel and they told me I should come here
[12:36] <blackjack_> meanwhile im still doing research on the issue
[12:58] <studio_> hi
[13:03] <studio_> how to change the white background from the apps/scopes to another (transparent) colour?
[13:10] <Lihis> blackjack_: I would need help with porting too..
[13:11] <blackjack_> what issue did you run into?
[13:12] <blackjack_> i run into this build/core/product_config.mk:222: *** Can not locate config makefile for product "cm_hercules".
[13:12] <blackjack_> tho i figured out what was causing the issue, still dont know how to resolve it atm tho
[13:13] <Lihis> I successfully built recovery but when I boot it I only see blink of purple color and then screen goes blank, adb is accessible though
[13:13] <blackjack_> wow you made it alot further than i did
[13:13] <blackjack_> what device did you port it too?
[13:14] <Lihis> Huawei u8800pro
[13:14] <blackjack_> how did you add the new deice?
[13:14] <blackjack_> see im stuck at the part where you do the lunch command
[13:15] <blackjack_> I added my device to the device folder but I run into that error when doing the lunch command
[13:18] <Lihis> I used my old device tree which I made for building TWRP recovery, but I think you can follow any CM or omnirom guide how to add new device
[13:20] <Lihis> do you have cm_hercules.mk in your device dir? And in that file, set PRODUCT_NAME: cm_hercules?
[13:21] <blackjack_> I have cm.mk
[13:22] <blackjack_> yep it says that in there as well
[13:23] <blackjack_> im porting it to the galaxy s2 btw
[13:25] <blackjack_> Oh, ok so im looking at the building cm guide for my device, so in theory I can apply the getting device specific code to this
[13:25] <studio_> @blackjack_, nice to hear, i thought the s2 is dead?
[13:25] <blackjack_> studio_, no way, its alive and strong!
[13:26] <blackjack_> still has decent hardware, runs lollipop well but I want to try ubuntu touch
[13:26] <studio_> a friend of mine got 2, and i thought he can try ubuntu touch on it but i in the guides it was marked as "dead", no more developing ...
[13:27] <blackjack_> I think there was an official port for the i900 varient, but im doing a port for the t-mobile (t989) version
[13:27] <blackjack_> there hasnt been any builds for that particular model
[13:28] <studio_> https://wiki.ubuntu.com/Touch/Devices/i9100 that was from 2013
[13:31] <studio_> ah, ok, the t989 is a different model
[13:31] <blackjack_> yep, completely different chiset as well
[13:31] <blackjack_> qulacom
[13:36] <studio_> bbl, bye
[13:43] <uuhimhere> ubuntu os vs sailfish
[13:43] <uuhimhere> which is snappier
[13:43] <uuhimhere> more responsive
[14:32] <Lihis> New build of recovery, now the screen cycles through between blank and purple..?
[14:33] <Lihis> Must be something with custom graphics.c?
[15:12] <popey> ogra_: my unity/mir has frozen so i cannot unlock my phone to adb in to debug it :S
[15:12] <popey> we need a backdoor :)
[15:13]  * popey realises he has ssh enabled and thus has a backdoor :)
[15:13] <awe_> ;D
[15:13] <popey>    29 root      20   0       0      0      0 R  96.4  0.0  56:55.13 kswapd0
[15:13] <popey> well that's not good
[15:24] <ogra_> popey, ugh ...
[15:26] <ogra_> popey, krillin ?
[15:26] <wolflarson> poooooooooopey
[15:37] <jgdx> cyphermox, could you reply to my email as well? If you're busy, then just skip that. Either way, I'll talk to the security team in the latter case?
[15:37] <MoPac> Hello. I've been trying out Unity8 in the LXC container on 15.04 Desktop (HP Envy x360 hybrid/convertible touch laptop). I wanted to ask whether it's "supposed" to be more or less completely non-functional at this point on that kind of hardware? I'm hoping to ensure that it's not just me setting it up wrong
[15:38] <MoPac> I can log in, but the tutorial shows every time, there is no connectivity wired or wireless (and no wireless settings options), not much touchpad functionality, no way to open X11 programs, etc
[15:39] <ogra_> can you boot off a USB drive ?
[15:40]  * ogra_ would recommend to instead try the desktop-next image 
[15:40] <ogra_> though i dont think X11 app execution works in any released code yet
[15:40] <ogra_> not without fiddling
[15:41] <MoPac> I could try it off USB -- it wasn't clear to me that there was that big a difference between the two. Is the behavior I described more or less standard for the lxc container?
[15:41] <ogra_> i haveno idea how well maintained the lxc variant is
[15:41] <ogra_> you would have to ask in #ubuntu-desktop ... though best during the work week
[15:42] <MoPac> ahh, k. Thanks
[17:04] <jgdx> cyphermox, filed https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1426923
[17:10] <popey> ogra_: yes
[17:11] <ogra_> :(
[17:11] <popey> not sure where to look
[17:11] <popey> why do we not have timestamps in unity8.log?
[17:18] <ogra_> not sure
[17:27] <mariogrip_> 10 000 Views on my video :=D I did not expect that at all! That's crazy, what have you guys done? xP
[17:33] <Azelphur> while true; do youtube-dl ... ;done :P
[17:34] <popey> mariogrip_: nice!
[17:34] <ChloeWolfieGirl_> mariogrip_  what was the quote? if you make it people will come? something like that? weldone getting all the views!
[17:35] <popey> If you build it, they will come.
[17:35] <popey> Kevin Costner.
[17:36] <mariogrip_> :D
[17:38] <ChloeWolfieGirl_> popey I knew I was wrong but I was close :P :D
[17:42] <mariogrip_> I got the device to detect rmnet
[17:44] <mariogrip_> but it cannot connect to the sim
[17:46] <mariogrip_> rmnet is the network interface for cell data btw
[17:51] <stu_> I tried to ask this last night but probably too late so no-one was around...  How do I ask to have a bug re-opened?  The fix is on the right track but does not really fix the issue.  https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1422521
[17:54] <stu_> Also, how come so few people are affected by this bug? Without tinkering apps just do not work on vivid...
[17:56] <ogra_> stu_, because mesa doesnt work andisnt used on phones :)
[17:57] <ogra_> (that would be quit insane ... SW renderign would eat your battery pretty quickly)
[18:03] <muka> is there a plan to support webRTC in the browser?
[18:08] <ogra_> muka, yes, long term there is ...
[18:08] <ogra_> there is no implementation for secure mic or camera access yet ...
[18:27]  * rpadovani has just rm -rf the android source folder
[18:27]  * rpadovani cries out loud
[18:32] <NewOne> Hello
[18:32] <NewOne> I have a question
[19:18] <peat-psuwit> Do you have any hint on debugging video playback?
[20:08] <stu_> ogra_: But apparmor denies start of apps due to the apps trying to access /usr/lib/arm-linux-gnueabihf/mir/client-platform/mesa.so, /usr/lib/arm-linux-gnueabihf/mir/client-platform/android.so, and /usr/lib/arm-linux-gnueabihf/mir/client-platform/dummy.so.
[20:09] <stu_> I do not know if any of these are needed, but I guess denying access to all of them makes apps not working.
[20:09] <stu_> At least allowing access (by disabling apparmor) makes the apps work.
[20:21] <studio_> hi
[20:36] <Verc> HelpHelp :D
[20:37] <Verc> my mako reboots when I use Browser
[20:37] <Verc> eg. I read an article and it reboots
[20:37] <studio_> i am not sure, but is it allowed to ask "again" for help "how to mount an ext4 formated sd-card in ubuntu-touch permanently"?
[20:38] <Verc> what is interesting: normally when it boots it turns on the GPS but after the "browser reboot" the GPS is turned off (as I wanted it to_
[20:45] <studio_> I can't find informations about that, today I figured out how to ssh to ubuntu-touch, for a "beginner" it was not so easy, but it is working now. would be nice to get some help.
[20:47] <popey> studio_: just like any other system, add it to /etc/fstab
[20:48] <studio_> @popey, fstab is tempfs, and after a reboot phablet is gone
[20:49] <popey> right, you'd have to make the phone read/write
[20:50] <studio_> i made with "sudo mount -o remount,rw /" but after reboot also no luck
[20:50] <Verc> should I report a bug?
[20:51] <popey> studio_: did you touch /userdata/.writable_image ?
[20:51] <studio_> i tried wit /mnt/sdcard but it is only ro after reboot
[20:51] <studio_> no?
[20:52] <popey> you need to
[20:52] <popey> or it wont mount rw on reboot
[20:52] <popey> however if you do this, you break ota updates really
[20:52] <studio_> ok will try ...
[20:53] <jgdx> Verc, do you know why it reboots?
[20:53] <Verc> nope
[20:53] <popey> Verc: have you made it RW?
[20:53] <Verc> no
[20:53] <Verc> i have reflashed the device
[20:53] <Verc> with --bootstrap and --wipe
[20:54] <Verc> and I have NOT used apt
[20:54] <Verc> or mount
[20:54] <popey> and it just reboots when you open browser?
[20:54] <Verc> no
[20:54] <Verc> when I use it
[20:54] <Verc> I open eg facebook
[20:55] <Verc> read somebody's post
[20:55] <Verc> and rhe device reboots
[20:55] <Verc> or I enter some news site and it reboots
[20:55] <Verc> it happens not regullary
[20:55] <popey> how odd.
[20:55] <popey> if you can reproduce it with a public site that would be helpful
[20:55] <popey> rather than a facebook post
[20:55] <popey> and then file a bug
[20:56] <Verc> now I'm out of wifi
[20:56] <Verc> is there  possibility to reinstall the browser?
[20:56] <Verc> I couldn't find it in tne Store
[20:57] <popey> that almost certainly wont help
[20:57] <popey> that's the windows way to fix things
[20:57] <Verc> :D
[20:58] <popey> do you have a news site you looked at recently?
[20:58] <popey> that I can test here
[20:59] <studio_> popey, it was nice to see, to make ssh to the ubuntu-touch device more "secure" but for "normal users" it is difficult to understand, because there is no good how-to ...
[21:03] <Verc> I think it was a blog or something
[21:03] <Verc> I do not remember
[21:03] <Verc> sorry
[21:04] <ogra_> studio_, you cant use th fstab, it gets generated on every boot ... ext2/3/4 SD cards are not supported because this most likely causes permission probs (ext filesystems will store UID data that most likely doesnt exist on the phone) ...
[21:04] <studio_> to the ubuntu-touch device ssh user@device is not working but from the ubuntu-touch device to ubuntu-pc is working without problems
[21:05] <ogra_> if you really want to use an ext4 fs, you will have to hack your way around it ...
[21:05] <ogra_> ssh only allows key auth ... and is managed by the android-gadget-service command ...
[21:06] <studio_> ogra_, to mount ext4 formated sd-card in a running system is no problem.
[21:06] <studio_> the problem is afte reboot
[21:06] <ogra_> right, so write an upstart job or add it to rc.local
[21:07] <popey> thats a better idea, yes.
[21:07] <ogra_> and make sure to disable ciborium ... thts the disk manager
[21:07] <ogra_> also note tht making the system writable will break upgrades ...
[21:08] <yolonnn> hey everybody
[21:08] <yolonnn> im new
[21:08] <yolonnn> there
[21:08] <popey> hello.
[21:08] <yolonnn> just asking
[21:08] <yolonnn> is already out there an ubuntu touch rom for the g900f _
[21:09] <yolonnn> or should I need to compilee it by myself_
[21:09] <popey> !devices | yolonnn
[21:09] <popey> check that page
[21:09] <popey> but someone probably needs to update it, if there is one
[21:09] <studio_> ogra_, yes and i found this "http://askubuntu.com/questions/563573/cant-ssh-into-ubuntu-touch-device" today
[21:09] <yolonnn> already checked it out
[21:10] <yolonnn> but says nothing about my phone
[21:10] <Verc> poppey: I cannot remember what I do when it reboots
[21:10] <yolonnn> !devices
[21:11] <ogra_> studio_, really, if you want to use the phone do not turn pw auth on, just copy your key over
[21:11] <popey> +1
[21:11] <studio_> ogra_, how to find a way to make the system writable and also get updates?
[21:11] <ogra_> the phablet user is known to the world and hardcoded in many places ... a brute force attack against a phone with open ssh is trivial
[21:12] <ogra_> studio_, there is none
[21:12] <studio_> hmmm ...
[21:12] <ogra_> it is not designed for this ... the writable mode is for devs to work on the plumbing layer
[21:12] <ogra_> and expected to break ...
[21:14] <ogra_> apt upgrades wont work due to the setip of the writable bind mounts ... system-image upgrades will just pverwrite your apt changes since system-image applies diffs against an expected unchanged readonly base
[21:14] <ogra_> (an will eventually break too)
[21:15] <ogra_> if you want to play with debs to build an app or some such on the phone, create a chroot in /home/phablet or on the sd card and do it there
[21:15] <ogra_> or if you are fancy, create an lxc container ;)
[21:16] <studio_> i figured out, that there have benn son problem with apt-get update and apt-get upgrade in the /stable/bq- channel ... since i switched to rc i din
[21:16] <studio_> dint#t tried that
[21:16] <ogra_> it isnt supported ...
[21:16] <ogra_> it is as simple as that
[21:16] <ogra_> at some point it will completely fall apart
[21:16] <studio_> ok
[21:17] <studio_> so the "rc"-channel is also not supported?
[21:17] <ogra_> (it i a matter of the packages that get upgraded, not all of them break the system ... it will degrade over time until you hit a reallybad package ... then it will fall over)
[21:17] <ogra_> no, apt is not suported
[21:18] <studio_> ok
[21:18] <ogra_> in no channel
[21:18] <studio_> i understood
[21:18] <ogra_> if you switch to writable and anything breaks there is no way but to re-flash
[21:19] <ogra_> which is why i suggest to use a chroot or an lxc container and leave the system untouched
[21:19] <studio_> no way? also withot the mtk-tools?
[21:19] <ogra_> at least if you want to use the phone for more than building arm packages
[21:20] <ogra_> well, if the phone doesnt boot anymore because a package broke it ...
[21:20] <studio_> ogra_, i am trying to use the phone for "learning"
[21:20] <ogra_> ... then your only choice is to re-flash
[21:21] <studio_> ok
[21:21] <ogra_> the system is designed for diff upgrades of full images ... for that you need a non-moving base ... which the readonly system gets us
[21:22] <studio_> but the aquaris E4.5 is on WIP on the ubuntu-touch device list?
[21:22] <ogra_> this only works if teh rootfs the server uses to generate the diiffs and the rootfs on the phone are identical
[21:23] <ogra_> dunno, probably someone missed to update it :)
[21:23] <studio_> ok
[21:23] <ogra_> it iis on sale so it is definitely not WIP :)
[21:26] <studio_> yes, but the rom isn't also "real" on public ;)
[21:28] <ogra_> ?
[21:28] <studio_> bq still don't offer the rom on their pages, but on http://androidheadlines.com/2015/02/install-ubuntu-phone-os-onto-bq-aquaris-e4-5-smartphone.html is a nice "how-to" :)
[21:29] <ogra_> how do you think updates are provided ?
[21:30] <ogra_> the "rom" lives on system-image.ubuntu.com ... like all others
[21:30] <studio_> for the peoples outside the Eu is now easy to try ubuntu-touch on the bq e4.5
[21:31] <ogra_> people outsidee the eu would be silly to buy it
[21:31] <popey> unless they're developers on wifi
[21:31] <ogra_> doesnt support the right us freqs
[21:31] <ogra_> yeah
[21:35] <studio_> ogra_, "the "rom" lives on system-image.ubuntu.com ..." maybe, but for me it was difficult in the beginning to find a rom for the aquaris e4.5. system "update" was working for me without loosing the emei ...
[21:37] <ogra_> well, we dont really support rooting and flashing the android version ... it is up to bq to provide that
[21:37] <studio_> and that is one of th things i do not understand
[21:37] <ogra_> we only write the software
[21:37] <ogra_> it is their device
[21:38] <studio_> that's the point, where to buy a real ubuntu-touch-device?
[21:38] <ogra_> the preinstalled version has extra bits added that bq povides and has contracts for
[21:38] <ogra_> at bq :)
[21:39] <studio_> no. it is mtk
[21:39] <ogra_> mtk builds the board ... not the phone
[21:40] <studio_> but mtk do not offer to built a native linux device
[21:40] <ogra_> bq is a customer of mtk ... they order HW and decide which SW gets preinstalled
[21:41] <ogra_> weather that is android or ubuntu is up to them ... deciding what apps get preinstalled on either of the QSes too ..
[21:42] <ogra_> *OSes
[21:42] <studio_> hmm, do you think their "release" is different to the "rc"-channel?
[21:42] <ogra_> i havent held a preinstalled bq phone in my hands yet :)
[21:42]  * ogra_ has to wait like everyone else 
[21:43] <studio_> ok, but what about a real ubuntu-touch device, is there or will be there one?
[21:43] <ogra_> i have seen some at th launch event though
[21:43] <ogra_> what is a "real ubuntu-touch device" ?
[21:43] <studio_> whithot android
[21:44] <ogra_> without the ability to make calls ?
[21:44] <studio_> no
[21:44] <ogra_> right
[21:44] <studio_> pure linux device
[21:44] <ogra_> so that answers your question :)
[21:45] <ogra_> if you want to use any mobile modem HW, and mobile sensors and anyof the mobile graphics HW, you have no choice
[21:45] <studio_> is it depending on money?
[21:45] <ogra_> it is depending on the HW vendors
[21:46] <studio_> yes, but the hw vendor will never support pure linux?
[21:46] <ogra_> the people developing that HW dont give out the specs nor do they have any interest in providing drivers for a corner OS
[21:46] <ogra_> if a linux vendor gets big enopugh they might
[21:46] <ogra_> or if a vendor puts enough money on the table ...
[21:47] <studio_> what vendor is doing this "maybe"?
[21:47] <ogra_> the ubuntu edge might have been a bit more open than a normal phone ... but the edge didnt happen ... so everything goes a lot slower (wrt convergence) and we have to live with the compromose
[21:48] <studio_> i was worry about to read the ubuntu edge is dead, that was a big chance
[21:48] <ogra_> well, it didnt make it
[21:49] <ogra_> eventuallythere will be phones at that HW class ... but it takes longer
[21:49] <ChloeWolfieGirl> If I could turn back time, If I could find a way, I'd make sure Ubuntu edge would make it, and it'd be here?
[21:49] <ogra_> yea
[21:49] <ogra_> h
[21:51] <ogra_> you could start a crowdfunding campaign to build a time machine with which you then could make the edge happen retroactively :)
[21:51] <studio_> :)
[21:54] <studio_> what about the meizu and its mt6595, will it be full supported under ubuntu-touch?
[21:57] <ogra_> sure
[21:57] <studio_> sure?
[21:57] <ogra_> why would it onl be half supported :)
[21:58] <studio_> the mt6595 can recive miracast!
[21:58] <ogra_> you mean send
[21:58] <studio_> no
[21:58] <studio_> receive
[21:59] <ogra_> why would you want to recieve ?
[22:00] <studio_> to receive different miracast displays, and to send them to a monitor
[22:00] <ogra_> (and no, i doubt that will be supportd in ubuntu soon, we have other missing bits and pieces to handle first ... but patches will indeed be acceptd ;) )
[22:00] <ogra_> why would you want to recieve other displays ? you want to set to your TV or monitor
[22:00] <studio_> i don't know if the mt6595 can do mhl, but most devices with the mt6595 are bad fron the hardware
[22:00] <ogra_> s/set/send/
[22:00] <popey> yeah, surely you want to send from the phone
[22:02] <ogra_> anyway, thats still far out
[22:02] <studio_> the mt6595 or mt6795 can do 120 fps with the cam, and also 4k display, but the most devices are using poor hardware
[22:02] <ogra_> with luck the SW is ready by 15.10
[22:02] <ogra_> for beta testing ...
[22:03] <ogra_> we promised desktop mode for 16.04 ... by then there will hopefully also be proper laptop class HW inside of phones ...
[22:03] <studio_> so miracast will also work on ubuntu-touch?
[22:04] <ogra_> so that you have proper amounts of ram to run an office suite etc
[22:04] <ogra_> well, the desktop mode will have to ue sme way to get the picture to a monitor/TV
[22:04] <ogra_> *some way
[22:04] <ogra_> in the beginning surely only MHL
[22:05] <studio_> how to set-up my phone to miracast?
[22:05] <ogra_> find it out ... no idea
[22:05] <studio_> :)
[22:05] <ogra_> and as i said ... we wont look into that yet ... there are other fich to fry first :)
[22:05] <ogra_> *fish
[22:05] <studio_> yepp
[22:42] <PLA1> Hi. In an HTML5 Ubuntu Touch app, what would cause onclick Javascript code intermittently not execute? You can clearly see the button respond to the touch but the onclick code is not executed. The test demonstration video is here: https://www.youtube.com/watch?v=VkMnKzTacaU and the source code is here: https://github.com/pla1/TouchTest
[23:08] <studio__> hmm, how do i setup my desktop like this: https://i.ytimg.com/vi/AWuOSwg7e0g/mqdefault.jpg
[23:18] <studio__> is it different to the bq E4.5? a white background is not so nice ...
[23:20] <nhaines> studio__: you can't.  That was from the original Mobile World Congress demo two years ago.
[23:26] <studio__> @nhaines, is there a "desktopmanager" available to make the standard "desktop" more colour full? white is a little bit bored ...
[23:29] <studio__> btw, the screenshot is from that video: https://www.youtube.com/watch?v=AWuOSwg7e0g
[23:30] <studio__> i don't know, why they but that desktop to the default image for the video ...
[23:30] <nhaines> studio__: as I said, no.
[23:30] <studio__> ok
[23:32] <studio__> so the default background is only for the "locked screen"?
[23:37] <nhaines> For the welcome screen, yess.
[23:38] <studio__> so, only locked screen, other screen are only with white background
[23:39] <studio__> and why?
[23:40] <ChloeWolfieGirl> nhaines, I beleive mhall119 said that people are trying to figure out how to make the scopes work to allow people to choose there own background for scopes that are see through such as the app scope
[23:43] <studio__> ChloeWolfieGirl, i am trying to figure out, why the default desktop i choosed in the settings in only available in the locked screen and not shown on "normal screens" ...
[23:44] <nhaines> studio__: because they took the option out 18 months ago and are in no hurry to put it back in.
[23:45] <nhaines> ChloeWolfieGirl: mhall119 said that, but considering it's something Ubuntu already does on the desktop, I'm unimpressed.
[23:45] <nhaines> I'm sure it'll happen by 16.04 LTS or whenever convergence hits.
[23:46] <studio__> @nhaines, for what thay made the "option" under desktop image? i am a little bit confused ... :(
[23:49] <ChloeWolfieGirl> studio_ because on the phone the background currently doesn't change with the scopes, if you mean unity 8 on desktop then it should change...
[23:49] <nhaines> studio__: it's not called desktop image.  It's called "Background"
[23:49] <nhaines> ChloeWolfieGirl: actually, the background does change on a per-scope basis.  Most scopes simply don't set a custom background.
[23:50] <lotuspsychje> maybe more themes will release in the future?
[23:50] <studio__> nhaines, ok, but why isn't the "background" shown or only in the locked screen?
[23:50] <nhaines> studio__: because that's what the design team wants.
[23:51] <studio__> hmmm, ok ...
[23:51] <lotuspsychje> studio__: you could join the design team and make sugestions maybe
[23:51] <ChloeWolfieGirl> nhaines, doesn't that depend on developer though, like I think the developer can set the background to what ever they want, but the end user doesn't have a choice right?
[23:52] <lotuspsychje> ChloeWolfieGirl: welcome to open source
[23:52] <nhaines> ChloeWolfieGirl: right.
[23:52] <nhaines> lotuspsychje: the design team only consists of Canonical employees.  :)
[23:52] <ChloeWolfieGirl> lotuspsychje, Yeah but not everyone with an ubuntu phone is going to know how to edit code :P
[23:52] <studio__> i personal think this is an disadvantage ...
[23:53] <lotuspsychje> nhaines: users are free to apply for a job at canonical?
[23:53] <nhaines> lotuspsychje: this isn't really good advice for someone wanting an extra setting in System Settings.
[23:53] <lotuspsychje> lol
[23:54] <lotuspsychje> maybe not
[23:54] <nhaines> studio__: in the past, custom backgrounds made the home screen really difficult to read.
[23:55] <nhaines> The design team decided they didn't have time to spend on this problem (it *is* more difficult than it sounds) and removed it, so they could focus on other things.  They'll be revisiting it in the future.
[23:55] <ChloeWolfieGirl> Mother: "Hey Chloe, How do you change the background on the ubuntu phone?" Me: "Well first you download the source code" x'D
[23:55] <k1l> like on any other desktop or OS development, the fancy user settings come when the basis is done.
[23:56] <lotuspsychje> im sure we will see alot of candy on ubuntu touch soon
[23:56] <k1l> i thought you dont have a desktop on the phone at all.
[23:57] <lotuspsychje> https://twitter.com/ubuntu
[23:57] <studio__> it is not depending on customers backgrounds. i am using ubuntu now since 2 years and i can decide is i want do use xfce with some desktop effects or gnome with many desktop effects ...
[23:57] <studio__> is=if
[23:59] <lotuspsychje> studio__: you can unlock your phone in write mode and experiment with it how you like