[00:27] <melvster> has anyone tried running telegram on ubuntu touch?
[00:36] <AlexandreSa> melvster: I'm has installed telegram in my ubuntu touch without problem.
[00:38] <AlexandreSa> I'm use Nexus 4. With Mako Image
[00:46] <melvster> AlexandreSa: thats fantastic news, thanks.  Did you install the web version or the native ubuntu app?
[00:48] <AlexandreSa> melvster: I was installed the native app.
[00:48] <melvster> awesome, thanks!
[00:49] <AlexandreSa> melvster: You are welcome
[01:44] <AlexandreSa> I like know if have some scope to integrate at OwnCloud service.
[01:50] <OerHeks> AlexandreSa, not yet ... https://uappexplorer.com/apps?q=owncloud
[01:50] <AlexandreSa> OerHeks: ThankYou
[04:46] <bzoltan> zyga: sadly I can not make it to the FOSDEM. We have found a simple problem with that package, the UITK examples conflict with the archive UITK example package. But it is not a problem, just remove and reinstall the distro UITK example.
[07:20] <h2o64> Hi ! I'm working on ubuntu touch for my Moto G but LXC container is crashing my kernel (break=mountroot is the proof). Can someone help me ?
[08:39] <cedian_linux> http://paste.ubuntu.com/11712805/ got some problems
[08:46] <h2o64> @cedian_linux you need to do 'make cyanogenmod_bacon_defconfig' first
[08:47] <cedian_linux> not found
[08:47] <h2o64> Really ?
[08:47] <h2o64> Wierd
[08:48] <cedian_linux> I'll try to make
[08:48] <h2o64> cd android_kernel_oneplus_one && make cyanogenmod_bacon_defconfig
[08:48] <cedian_linux> I know that
[08:49] <h2o64> No ! You set the 3.19.0-18-generic config :p
[08:49] <cedian_linux> I didn't
[08:49] <cedian_linux> it wasn't me
[08:49] <h2o64> do cat  arch/arm/configs/cyanogenmod_bacon_defconfig
[08:49] <h2o64> you did by calling the old-config thing
[08:50] <cedian_linux> it's there
[08:50] <h2o64> Maybe
[08:50] <h2o64> cp arch/arm/configs/cyanogenmod_bacon_defconfig .config
[08:50] <h2o64> will manually use it
[08:55] <cedian_linux> it asks for pc stuff
[08:55] <h2o64> Yes because you set the thing to use your PC defconfig
[08:56] <cedian_linux> no I copied as you sai
[08:57] <h2o64> That's wierd ...
[08:57] <h2o64> Did you said the ARCH=arm
[08:57] <cedian_linux> no now I dud
[08:58] <cedian_linux> unrecognized values
[08:59] <h2o64> Could you pastebin this ?
[09:00] <cedian_linux> I'll do
[09:02] <cedian_linux> http://paste.ubuntu.com/11712886/ the letters are wrong because of no utf-8
[09:06] <cedian_linux> fixed signs: http://paste.ubuntu.com/11712894/
[09:08] <cedian_linux> h2o64: I've added it
[09:09] <h2o64> Did you try make clean and then make again ?
[09:26] <cedian_linux> no
[09:26] <h2o64> try :p
[09:26] <cedian_linux> I'm oing it
[09:27] <cedian_linux> still doing
[09:27] <cedian_linux> errors
[09:28] <h2o64> hmmm
[09:28] <h2o64> Maybe clone made shit
[09:28] <cedian_linux> it's cloned indeed, but for ubuntu touch
[09:45] <cedian_linux> I fund a .config
[11:28] <cedian_linux> I get a boot.img of 700 kb
[12:18] <cedian_linux> Can't add modules
[12:28] <cedian_linux> got a 700 kb size image
[13:01] <cedian_linux> got the error no rule to make target cnd
[13:15] <cedian_linux> prepare0 fails
[14:25] <bunty> Hi guys,  I am facing problem with X11 Server on ubuntu touch from command line. anybody has any idea about it?
[14:29] <Sleep_Walker> sorry for not helping you, but you're running X11 at the same time as MIR? or it is some X server for MIR?
[14:55] <mariogrip> i see a new folder on the system-image server called "ubuntu-personal" what is that? snappy desktop? :D
[15:14] <cedian_linux> I've found out the click packages archives, I won't talk too much about it though
[15:15] <cedian_linux> it's a site
[15:24] <nik90> mariogrip: In the recent Q&A, it was mentioned that snappy personal would be used for user desktops..could it be that?
[15:25] <nik90> it would contain necessary stuff like unity8, mir etc...while snappy would just be the core that is used for other devices like pi, beagle boards etc.
[15:32] <cedian_linux> mariogrip: I got some issues with compiling, but it seems it continues
[15:46] <mariogrip> nik90: :D That's cool
[15:47] <mariogrip> cedian_linux: do you have some logs?
[15:47] <cedian_linux> yes
[15:50] <cedian_linux> mariogrip: http://paste.ubuntu.com/11714821/
[15:51] <mariogrip> for me it seems like you don't have the correct version of gcc
[15:52] <cedian_linux> ok
[15:52] <mariogrip> btw, are you still using -i?
[15:52] <cedian_linux> mariogrip which should I use? yes
[15:53] <cedian_linux> else it still buggss out
[15:53] <mariogrip> http://wiki.ubports.com/index.php/OnePlus_One_Build#Manual_setup_of_development_environment
[15:53] <mariogrip> use the tools that are listed there
[15:54] <cedian_linux> that doesn't work
[15:58] <mariogrip> that should work
[15:59] <cedian_linux> it doesn't it gives errors about incompatible so's
[16:01] <cedian_linux> and it compiles the kernel partially
[16:05] <mariogrip> humm, i think you might need to do some cleanup, and remove -i and fix errors as they come. I haven't seen that error before so i don't know what will fix it. maybe you need to reinstall some tools/remove some tools that overwrite for other tools
[16:10] <taiebot> Hi all, As i am on willy not sure if it s really worth opening a bug report. But just in case can someone confirm. If you open contacts app. select a contact,open the messaging app via the little messaging icon. it opens the messaging app but not the correct thread and fails to send any message
[16:10] <h2o64> Hey, is somebody ready to help me hack initrd because my LXC container is mountable in recovery but make the kernel panic while booting
[16:13] <mariogrip> h2o64: I tried to set console=null on my oneplus one and it gave me and kernel panic, so i really think you need to console=tty0 and remove androidboot.console.
[16:15] <h2o64> Shit ! I didn't noticed the androidboot.console. console=tty0 is set. Do you think adb will come thanks to that ?
[16:25] <hevyhomie> good evening
[16:26] <h2o64> good evening
[16:27] <hevyhomie> I am porting touch to motorola moto e, and when I execute lunch, I get: build/core/product_config.mk:222: *** Can not locate config makefile for product "condor".  Stop.  ** Don't have a product spec for: 'condor' ** Do you have the right repo manifest?
[16:27] <hevyhomie> could you guide me what could be the issues?
[16:28] <h2o64> I'm porting touch on Motorola Moto G ^^
[16:28] <h2o64> Luk is porting for Moto G 4G
[16:28] <h2o64> See here https://github.com/ubuntu-touchCAF
[16:32] <hevyhomie> I already have the cm 11.0 binary files, vendor files, kernel files and the manifests as well, where should I put them?
[16:32] <hevyhomie> in the phablet dir
[16:34] <h2o64> First sync ubuntuTouch CAF
[16:34] <h2o64> then you do a local_manifest like this one
[16:34] <h2o64> <?xml version="1.0" encoding="UTF-8"?>

[16:34] <h2o64> <!-- Falcon Trees -->
[16:34] <h2o64>   <project name="ubuntu-touchCAF/android_device_motorola_falcon" path="device/motorola/falcon" remote="github" revision="ubuntu-touch" />
[16:34] <h2o64>   <project name="ubuntu-touchCAF/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" revision="ubuntu-touch" />
[16:34] <h2o64>   <project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />
[16:34] <h2o64>   <project name="ubuntu-touchCAF/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" revision="ubuntu-touch" />
[16:34] <h2o64>   <project name="ubuntu-touchCAF/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="ubuntu-touch_OLD" />

[16:34] <h2o64> Replace with the condor things. Then you have a few patches to apply on trees and kernel. APK/JAR has to be remove from vendor, and you are good to go
[16:35] <cedian_linux> mariogrip: if I remove tools it  gives errors that it may break my system
[16:47] <mariogrip> h2o64: btw did you replace the adbd this a unlocked one?
[16:47] <mariogrip> cedian_linux: yeah, don't remove them if they break your system
[16:48] <cedian_linux> ok
[16:48] <cedian_linux> what are dtb files mariogrip?
[16:48] <h2o64> The unlocked one provided by you or canonical ?
[16:49] <mariogrip> by ogra_  one of the ubuntu developer
[16:49] <h2o64> Errr ... No I didn't
[16:49] <mariogrip> http://people.canonical.com/~ogra/adbd
[16:49] <cedian_linux> and mariogrip do you got the original .config?
[16:49] <mariogrip> see all the way down on this page h2o64 https://developer.ubuntu.com/en/start/ubuntu-for-devices/porting-new-device/
[16:50] <mariogrip> cedian_linux: what .config?
[16:50] <cedian_linux> of your kernel
[16:50] <h2o64> Ahhh ! That's what I was checking. No I don't use it. I should ?
[16:50] <cedian_linux> because I can't get it working
[16:51] <mariogrip> cedian_linux: do you mean this? https://github.com/ubports/android_kernel_oneplus_one/blob/master/arch/arm/configs/cyanogenmod_bacon_defconfig
[16:51] <hevyhomie> how do I paste code here?
[16:51] <cedian_linux> that one doesn't work
[16:52] <h2o64> mariogrip : Same error. However, I have extra line in the kmsg wich tell me that the crash is mmc related
[16:52] <mariogrip> h2o64: the adbd binary shipped with Ubuntu checks if the device's screen is unlocked and if there is a password set for the phablet use, so you need to replace it if you want adb to start before it got mir to start
[16:53] <mariogrip> can you send me the kmsg?
[16:53] <cedian_linux> it works
[16:53] <cedian_linux> I use the android armhf now
[16:54] <mariogrip> cedian_linux: okay
[16:54] <h2o64> mariogrip : It crashes only 10 seconds after I turn it up. Do you think it will make adb works while a "break" is going on
[16:55] <h2o64> mariogrip : here is the log if you're interessting in it http://pastebin.com/MG42nWxW
[16:55] <mariogrip> i still see console=null :P
[16:55] <h2o64> console=null  must be a translate from console=tty0
[16:56] <cedian_linux> mariogrip: should I use ramdisk-recovery.cpio
[16:56] <h2o64> mariogrip : here is my cmdline androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags androidboot.write_protect=0 console=tty0 apparmor=0
[16:56] <hevyhomie> h2o64: I get an error when i sync http://pastebin.com/06KG6qkM
[16:57] <h2o64> hevyhomie : 'rm -rf .repo/manifest* && repo init -u git://github.com/ubuntu-touchCAF/android_local_ubuntu-touchCAF.git -b ubuntu-touch"
[16:59] <mariogrip> h2o64: see line 28, it says console=null, i think that is your problem. not syncing: Attempted to kill init! was the same error i got when i set console=null on the oneplus one
[17:00] <mariogrip> try to force it to use tty0 somehow
[17:02] <mariogrip> yeah, i think that's your problem, i'm 90% sure about that...
[17:03] <hevyhomie> h2o64: Im gonna work on it and keep you updated. THank you and God Bless you. Have a wonderful rest of the week.
[17:04] <mariogrip> h2o64: use the boot_info tool (http://forum.xda-developers.com/attachment.php?attachmentid=2033369&d=1370917036) to check your boot.img if it has correct cmdline
[17:04] <mariogrip> ./boot_info boot.img
[17:05] <h2o64> Actually, my boot.img is already problematic : I have to unpack it each time in order to put a cmdline in it
[17:06] <mariogrip> cedian_linux: you cannot use the ramdisk for the recovery for boot.img
[17:06] <cedian_linux> thanks
[17:06] <mariogrip> h2o64: have you tried to delete the boot.img before make? so it needs to rebuild it
[17:07] <h2o64> I did I did
[17:07] <cedian_linux> why was my boot.img 700 kb? And what files can be used for boot.img?
[17:07] <h2o64> $ adb shell "cat /proc/cmdline"
[17:07] <h2o64> console=null androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags androidboot.write_protect=0 androidboot.emmc=true androidboot.serialno=TA883031EV androidboot.baseband=msm androidboot.mode=normal androidboot.device=falcon androidboot.hwrev=0x83C0 androidboot.radio=0x1 androidboot.powerup_reason=0x00020000 bootreason=kernel_panic androidboot.write_prote
[17:07] <h2o64> :'(
[17:08] <mariogrip> have you tried to move common configs file to device config?
[17:08] <mariogrip> BoardConfigCommon.mk -> BoardConfig.mk
[17:09] <mariogrip> or have them both just that it so it will overwrite
[17:09] <h2o64> BoardConfigCommon.mk is directly included by BoardConfig.mk
[17:10] <h2o64> I CAN CHANGE IT DIRECTLY IN THE KERNEL !!!!!! Using CONFIG_CMDLINE=
[17:10] <h2o64> and CONFIG_CMDLINE_FORCE=y
[17:11] <mariogrip> humm, but did you try the boot_info tool? so we can check if it's the image file or the device that has wrong console
[17:11] <h2o64> I'll do that I just a minute
[17:12] <mariogrip> I hope it's the image file that has wrong cmdline, that's easier to fix xP
[17:13] <cedian_linux> mariogrip: why is android-ramdisk.img only 271kb?
[17:13] <mariogrip> cedian_linux: i don't know, did you choose the right device in launch?
[17:14] <cedian_linux> yes
[17:14] <mariogrip> cedian_linux: did you edit anything in the kernel?
[17:14] <h2o64> $ ./boot_info boot.img
[17:15] <cedian_linux> yes the apparmor
[17:15] <cedian_linux> no
[17:15] <cedian_linux> sorry
[17:15] <cedian_linux> it's 371 kb
[17:16] <mariogrip> h2o64: did it output something?
[17:17] <mariogrip> cedian_linux: humm, i really don't know what's going on with your build, i suggest you do a full cleanup.
[17:17] <cedian_linux> ok
[17:18] <mariogrip> cedian_linux: you can push the apparmor patch to a fork of the kernel and i can build it with the ci server
[17:18] <cedian_linux> ok
[17:19] <cedian_linux> but ci failed
[17:19] <mariogrip> cedian_linux: i will fix that
[17:26] <h2o64> IRC Crash... Still there ? Did you say something since I posted boot_info results ?
[17:27] <mariogrip> h2o64: im here, i didn't get the boot_info
[17:27] <mariogrip> can you pastebin it?
[17:27] <h2o64> crap
[17:27] <h2o64> I will yes :)
[17:27] <mariogrip> the irc does not like multiline paste
[17:27] <h2o64> (Btw, I'm flashing the build with forced cmdline
[17:28] <mariogrip> okay
[17:28] <h2o64> http://pastebin.com/Lrbs8wkx
[17:29] <h2o64> This build didn't crash 10 sec later for now..
[17:29] <h2o64> adb is un-reachable
[17:30] <mariogrip> that's a progress i guess
[17:31] <mariogrip> did you add adbd to upstart so it starts at boot?
[17:31] <h2o64> crash is gone
[17:31] <h2o64> I'm using the same rootstock as you but adpated for my device IDs
[17:32] <mariogrip> so it cp the adbd.conf into etc/init
[17:33] <mariogrip> and you replaced the adbd in /sbin with the unlocked one?
[17:33] <h2o64> I forced-shutdown the device in order to get a kmsg and check if everything's good. And it is. It just spam the "[rev_rmnet8] error: rmnet_ioct called for unsupported cmd[35585]" at the end. Should I wait as long as I can ?
[17:33] <h2o64> Yes, cp is done.
[17:33] <h2o64> No I didn't replaced adbd
[17:34] <mariogrip> you need to do that in order to let it start at boot
[17:34] <mariogrip> and you getting unsuppered cmd that's a nice progress
[17:34] <h2o64> That's the log I got http://pastebin.com/8MNTzMwk ;)
[17:34] <mariogrip> so now we're inside the ubuntu system,
[17:35] <mariogrip> that's good, now you can also try to pull syslog that should contain a better log than kmsg
[17:36] <mariogrip> syslog is located in var/log inside system.img in data
[17:36] <h2o64> I'm replacing the adbd
[17:37] <mariogrip> okay, that should bring adbd to life :)
[17:37] <h2o64> I place in in ubuntu rootfs sbin ?
[17:37] <mariogrip> yes
[17:38] <mariogrip> the upstart config starts exec /sbin/adbd
[17:38] <mariogrip> btw, did you get my mail?
[17:39] <h2o64> I do (just seen it)
[17:39] <h2o64> I would be happy to join :)
[17:40] <mariogrip> Awesome! :D making you mod on the forum right now
[17:40] <h2o64> To change adb I must mount system.img ?
[17:41] <mariogrip> yes
[17:42] <h2o64> Ouf ! I was worried that something went wrong :p
[17:44] <h2o64> still no adb
[17:45] <cedian_linux> I do as is said on the forums and get weird output
[17:46] <cedian_linux> http://paste.ubuntu.com/11715552/
[17:46] <mariogrip> then i might not have reach to upstart before it crashes, then we need to exstract the syslog without adb, reboot to recovery mount (maybe make a .sh file that does that automatically) and pull var/log/syslog
[17:46] <mariogrip> h2o64: ^
[17:47] <cedian_linux> I meant on the wiki mariogrip ^
[17:48] <mariogrip> humm, have you tried to build it without the patch you did just to check if it's the patch that makes the build goes wrong?
[17:49] <cedian_linux> no not yet
[17:49] <h2o64> mariogrip : syslog does exist
[17:49] <mariogrip> pull it and pastebin it
[17:50] <h2o64> http://pastebin.com/khPvBMgT
[17:50] <mariogrip> ah it does not exist okay. then we are stuck with kmsg
[17:51] <mariogrip> cedian_linux: maybe you should try that fist
[17:51] <h2o64> I search in the whole hdd : nothing
[17:51] <cedian_linux> how?
[17:51] <h2o64> (I was talk to mariogrip : "I search in the whole hdd : nothing")
[17:52] <mariogrip> cedian_linux: just cut the kernel folder out to a temp folder and resync the repo
[17:52] <mariogrip> h2o64: if it exist it should be in var/log.
[17:52] <h2o64> I searched just in case
[17:53] <mariogrip> btw check dmesg
[17:53] <cedian_linux> I'm trying now
[17:53] <h2o64> mariogrip : dmesg will show me the recovery log nope ?
[17:54] <mariogrip> no, i mean the dmesg in var/log
[17:56] <h2o64> /data/tmp/var/log # cat dmesg
[17:56] <h2o64> (Nothing has been logged yet.)
[17:56] <h2o64> LOL
[17:57] <cedian_linux> still fails mariogrip
[17:57] <mariogrip> xP then we are stuck with kmsg
[17:58] <h2o64> Wiat ... new kmsg is wierd
[18:00] <mariogrip> cedian_linux: what fails? make?
[18:00] <cedian_linux> yes
[18:00] <mariogrip> log?
[18:01] <cedian_linux> not yet
[18:01] <cedian_linux> didn't make one
[18:01] <cedian_linux> I mean a log mariogrip ^
[18:01] <mariogrip> can you send me the output of make+
[18:01] <cedian_linux> yes soon
[18:05] <h2o64> (I lost a entire afternoon because of deving xD)
[18:06] <mariogrip> xP
[18:07] <mariogrip> btw, what i see from the kmsg your android HAL is crashing
[18:10] <mariogrip> why are you using cyanogenmod repos? and not aosp from ubuntu git?
[18:12] <cedian_linux> mariogrip I don't understand how I should I rebase the packages I need a clear explanation not something like rebase xxx without knowing what xxx must be
[18:12] <h2o64> mariogrip : because I want to base ubuntu touch of a CAF rom as CM11 or pure CAF branch itself
[18:14] <h2o64> Android HAL crashing ;... interessting
[18:14] <h2o64> Lastest longest log http://pastebin.com/Hf67ARY9
[18:16] <mariogrip> h2o64: i don't know, but using CAF might cause problems... I don't know, but i tried caf for oneplus one and it didn't work as well for me, but i probably did something wrong...
[18:17] <h2o64> My device can't boot AOSP
[18:17] <h2o64> That's why I made such a choice
[18:17] <mariogrip> the oneplus one has no AOSP ether but i made it work
[18:18] <h2o64> Yes, but you doesn't have RIL and Camera (frameworks)
[18:19] <mariogrip> the ril has some problems with ofono, the rild work in the android hal
[18:19] <cedian_linux> I can't find the patches it's not good described
[18:19] <mariogrip> cedian_linux: in the ubuntu wiki?
[18:19] <h2o64> My device is very specific. I know that I can make it boot with AOSP
[18:19] <cedian_linux> not described.
[18:20] <cedian_linux> I can't find out which I need
[18:20] <cedian_linux> and when I rebase it says it is clean
[18:20] <mariogrip> cedian_linux: i don't know, i haven't tried yet
[18:20] <cedian_linux> ok
[18:21] <mariogrip> h2o64: okay
[18:21] <cedian_linux> and the patches won't work
[18:21] <cedian_linux> I'm getting depressed :P
[18:21] <cedian_linux> :(
[18:21] <h2o64> Could you (if you have time) test if my sources work on your device mariogrip ?
[18:22] <mariogrip> h2o64: sure
[18:22] <mariogrip> cedian_linux: you need to stay positive and just try everything :)
[18:22] <cedian_linux> I did what I could
[18:23] <cedian_linux> searched the whole web nothing found
[18:24] <mariogrip> cedian_linux: apparmor is not an easy task if you not have much experience with kernels, so maybe if you want, work on something else that's a little easier? like camera or headphone plug?
[18:24] <cedian_linux> That's good
[18:25] <cedian_linux> Mariogrip I just need apparmor for now
[18:25] <cedian_linux> but other stuff is great, my sound didn't work at all though
[18:26] <mariogrip> cedian_linux: i can see if i can take a look at it today
[18:26] <Sleep_Walker> apparmor is still alive?
[18:26] <mariogrip> apparmor3
[18:26] <Sleep_Walker> scary :)
[18:27] <mariogrip> xP
[18:27] <cedian_linux> I need my apps which won't install with click
[18:30] <cedian_linux> mariogrip I don't understand why they use apparmor3 which isn't ready yet
[18:31] <mariogrip> cedian_linux: That's not up to me, that's how Ubuntu touch is
[18:31] <cedian_linux> yeah, but they could at least add more information, if they want users to port it
[18:48] <cedian_linux> trying noe
[18:55] <cedian_linux> mariogrip what's the normal size of the kernel?
[18:56] <h2o64> mariogrip : Did you red my last log ?
[18:56] <mariogrip> that last thing you said was "Could you (if you have time) test if my sources work on your device mariogrip ?"
[18:57] <h2o64> Ah :p
[18:57] <h2o64> Did you saw that ? http://pastebin.com/EMaJCDnn
[18:57] <cedian_linux> mariogrip could you (if you have time) build apparmor3?
[18:58] <mariogrip> you shuld try irccloud.com h2o64
[18:58] <mariogrip> cedian_linux: yeah
[18:58] <mariogrip> h2o64: are you back to console=nulll?
[18:58] <cedian_linux> and then it accidentally works, by me :P just a joke
[18:58] <h2o64> wait, taht's not the right kmsg
[18:58] <h2o64> What's irccloud.com ?
[18:59] <cedian_linux> an irc client I guess ;)
[18:59] <h2o64> I mean why this one in particular
[18:59] <h2o64> log : http://pastebin.com/NQZRdYs
[18:59] <h2o64> * http://pastebin.com/NQZRdYsQ
[18:59] <mariogrip> a irc client that runs on the web so it keeps you alive and you will receive/send all messages
[19:00] <h2o64> I'm using piding on Ubuntu but each time I close the windows it kills the conv
[19:01] <cedian_linux> I'm using hexchat right now
[19:04] <mariogrip> but with irccloud if you cloese the window it still is alive in the cloud, that's why im always on this channel
[19:04] <h2o64> Ahhhhhhhhhhhhhhh !
[19:06] <h2o64> Nice
[19:06] <h2o64> Me and my team are use to hanghout
[19:06] <h2o64> *hangout
[19:09] <mariogrip> ah, I have used that before, but we moved to irc
[19:10] <mariogrip> cedian_linux: i build the kernel now with apparmor3 let's see if it works
[19:11] <cedian_linux> ok
[19:12] <cedian_linux> I'm looking up some info about some Dutch law which might be fake. A lot of signs are made with the same text
[19:13] <mariogrip> nice it works!
[19:13] <cedian_linux> yay
[19:15] <mariogrip> I can download apps now :D
[19:15] <cedian_linux> cool give me the kernel ;)
[19:16] <mariogrip> uploading
[19:16] <cedian_linux> nice
[19:17] <h2o64> Back with irrcloud
[19:17] <cedian_linux> ok
[19:19] <h2o64> mariogrip : Where did you get https://github.com/ubports/qcom_conn_init ?
[19:20] <mariogrip> a mix of codeaurora and aosp
[19:20] <mariogrip> mostly aosp
[19:20] <h2o64> On mako ?
[19:21] <mariogrip> jup
[19:21] <h2o64> And how did you patch hardware/qcom/display ?
[19:22] <h2o64> (I'm thinking about make nice branches with good commits on github :3 )
[19:22] <mariogrip> https://github.com/ubports/qcom-display/commit/d8380fc043a55019513dc22663e2a156cdc9ff92
[19:22] <cedian_linux> mariogrip: any luck with uploading
[19:22] <h2o64> i saw but hwhy did you made those changes ?
[19:23] <mariogrip> some of them are copy form codeaurora and some form linux
[19:23] <h2o64> Okay
[19:25] <mariogrip> h2o64: something i need to do i clean up, but that's not my priority now.
[19:25] <mariogrip> is*
[19:26] <h2o64> Sure sure :)
[19:26] <h2o64> But I'll have a lot of spare time soon so I'll do it :)
[19:31] <seth__> im trying to install Ubuntu on my Motorola Xoom. when i try to flash the device i get "Device wingray not found on server https://system-image.ubuntu.com channel stable"
[19:32] <cedian_linux> mariogrip: any update on boot.img upload?
[19:33] <kwah> Hi All
[19:34] <kwah> Want to file a bug about lock-screen not reacting on input
[19:34] <mariogrip> yeah i forgot, it's donw
[19:34] <mariogrip> it's on the download server
[19:34] <kwah> any ideas on the package/sub-system to file a bug against?
[19:34] <cedian_linux> thanks
[19:34] <mariogrip> http://download.ubports.com/Ubuntu-Touch/OnePlus-One/dev/20150514/
[19:35] <cedian_linux> thanks
[19:35] <cedian_linux> why in 2015054?
[19:38] <mariogrip> that's todays date
[19:38] <cedian_linux> no that's 20150614
[19:41] <mariogrip> oh yeah, my bad :P i will correct that. I'm still in may
[19:41] <mariogrip> thanks :D
[19:41] <cedian_linux> me too sometimes
[19:50] <mariogrip> cedian_linux: I will say thanks for trying to get Apparmor3 to work, i feel little bad that i just took apparmor3 from you... sorry about that. but you're welcome help with other stuff :D
[19:51] <cedian_linux> installed, it doesn't matter I love to learn things, I thank you for letting me help
[19:51] <cedian_linux> mariogrip ^
[19:51] <mariogrip> :D
[19:53] <mariogrip> did you download some apps, i just downloaded podbird
[19:57] <cedian_linux> yes I downloaded utilities
[20:04] <cedian_linux> mariogrip I'm installing a lot ;)
[20:09] <ahayzen> Hi, anyone else ever got "2015/06/14 21:08:18 error pushing: " and then nothing else in the output when trying to ubuntu-device-flash to a mako ?
[20:17] <lpotter> hey. Does canonical actually use any of these packages? https://code.launchpad.net/nemo-mobile
[20:20] <taiebot> ahazen recently got quite some erros with flashing. Most of the time i delete the .cache folder on my desktop sometimes it helps
[20:26] <ahayzen> taiebot, hmm maybe going to recovery mode and doing it that way
[20:28] <ahayzen> ..yeah thats seems to be working/doing more \o/ maybe adb is just nicely broken in wily or something