=== chihchun_afk is now known as chihchun
=== slango20_ is now known as slango20
=== JanC_ is now known as JanC
=== ndec|vacations is now known as ndec
[09:46] <Exterminador> hi guys. i'd like to know how hard is to a newbie to port ubuntu touch to a new device?
[09:51] <Exterminador> i'd love to try it out in my old phone, but it seems very hard to port. :/
[10:21] <iAmVille[m]> Ubuntu touch is still lacking in documentation :(
=== ahayzen_ is now known as ahayzen
=== _salem is now known as salem_
[11:55] <jgdx> matv2, hey, the output is saying that the 80211 driver fails somehow. I think you should tweak your channel settings on the 2.4g network
[11:55] <matv2> jgdx hi
[11:56] <matv2> thanks for looking!
[11:56] <matv2> in what way would I do that?
[11:56] <jgdx> matv2, not really sure, but if it's on auto, choose some infrequently used channel
[11:57] <jgdx> also, if that fails, try disabling 80211n and retry
[11:59] <jgdx> lastly, try googling "cfg80211-error wl_cfg80211 disconnect reason 3" and see what the Internet says
[12:01] <matv2> jgdx I can do that :)
[12:04] <matv2> jgdx Thanks so much for taking the time. I will certainly let you know if anything definite comes out of it. bye
[12:05] <jgdx> davmor2_, hey, got time to help me flash x+o on m10?
[12:06] <jgdx> matv2, np
[12:07] <vigo> jgdx, hey! davmor2_ is off today but I think I can help you :)
[12:08] <vigo> jgdx, just try to flash like this
[12:09] <vigo> ubuntu-device-flash touch --channel ubuntu-touch/staging/frieza_arm64 --device=frieza_arm64 --revision 102 --recovery-image ~/Downloads/recovery/recovery-frieza.img --bootstrap
[12:09] <vigo> oops mistake
[12:09] <vigo> jgdx, ubuntu-device-flash touch --channel ubuntu-touch/staging/ubuntu --device=frieza_arm64 --revision 102 --recovery-image ~/Downloads/recovery/recovery-frieza.img --bootstrap
[12:10] <vigo> jgdx, build 102 is the last image working
[12:10] <jgdx> vigo, will try that, thanks!
[12:10] <vigo> from 103 on, it's broken :) we're working on it
[12:10] <vigo> jgdx, yw =)
[12:13] <sil2100> jgdx: we're in the middle of investigating why it's broken though
[12:14] <sil2100> The new lxc xenial upload busted it
[12:15] <jgdx> sil2100, good to know
=== xiinotulp is now known as plutoniix
[12:17] <jgdx> vigo, getting "can't flash recovery image" right now. Haven't gotten that in other attempts
[12:18] <vigo> jgdx, verify the path to recovery image is the right one for you
[12:18] <vigo> and that you've got the recovery-frieza.img file
[12:19] <jgdx> vigo, http://pastebin.ubuntu.com/23733231/
[12:19] <vigo> jgdx, https://wiki.ubuntu.com/Touch/Devices all recovery images are here
[12:19] <jgdx> i have that one
[12:21] <vigo> jgdx, mmm it should work, it was in bootloader mode right?
[12:21] <jgdx> fastboot, yeah
[12:22] <vigo> jgdx, that also happened to me some times but eventually works, the command looks good
[12:23] <jgdx> vigo, right, FAILED (remote: low power, need battery charging.)
[12:23] <jgdx> :)
[12:24] <vigo> jgdx, cool
[12:49] <Exterminador> is there any way to automate the whole process? i'm using a mediatek phone. and i dont understand well the directives on the webpage in how to port to a new device
=== petevg_holidays is now known as petevg
[13:04] <Exterminador> well, i've been looking into the Devices page.
[13:04] <Exterminador> Emulator (ARM) -> what does this exactly means?
=== chihchun is now known as chihchun_afk
[14:45] <jgdx> vigo, okay, got it working :) Any trick to getting e.g. phablet-shell/adb/bileto to work?
[14:45] <jgdx> have enabled dev mode
[15:01]  * mterry testing latest unity8-session snap -- seems mostly fine, except for snap launching still
[15:02] <Exterminador> anyone available to help me porting Ubuntu Touch for a device? i'm completely newbie in this
[15:06] <mterry> Exterminador: https://developer.ubuntu.com/en/phone/devices/porting-new-device/  (this is all I know, I have never tried porting Touch)
[15:06] <Exterminador> mterry: tks, i'll take a look at that
[15:17] <vigo> jgdx, :) great
[15:18] <jgdx> vigo, those commands work for you?
[15:19] <jgdx> seeing ???????????? no permissions from adb devices
[15:19] <vigo> jgdx, I got adb by flashing the recovery from fastboot
[15:19] <jgdx> vigo, okay
[15:21] <vigo> jgdx, fastboot flash recovery <path_to_recovery> iirc
[15:21] <jgdx> yup, thanks
[15:27] <Exterminador> jeez.. i wont even try to port.. this is too much for a newbie
[15:27] <Exterminador> :/
[15:28] <dobey> yeah, if you're not familiar with building android kernels and images already, it's quite a bit daunting
[15:29] <Exterminador> indeed. i'd love to try ubuntu in my old phone.. but damnit.. those are complicated commands
[15:29] <Exterminador> lol
[15:30] <dobey> well hopefully porting should get a lot easier once we've got snap based builds working
[15:30] <Exterminador> maybe i'd be able to do it in a few years
[15:31] <Exterminador> LOL
[15:59] <Dev^Null4> I am looking to put ubuntu touch on a Galaxy S5 it does not need to function as a phone. but I need it to run java and connect to wifi. I have yet to find any instructions for porting a new device can someone help me.
[16:01] <dobey> see /topic
[16:01] <dobey> but sounds like you don't really want an ubuntu phone image, but something else instead
[16:02] <dobey> why do you need to "run java" exactly?
[16:03] <Dev^Null4> we are looking for a smaller form factor then a tablet. to be used on a factory floor to run a java application. a phone (4.5 - 5") would be the right size.
[16:06] <dobey> i don't know if any java implementations have support for running directly on mir, but...
[16:06] <dobey> kgunn: ^^ this sounds like something the mir kiosk stuff would be best for?
[16:13]  * kgunn reads
[16:13] <kgunn> huh, cool
[16:14] <kgunn> Dev^Null4: so if you are intrested....please check out https://developer.ubuntu.com/en/snappy/guides/mir-snaps/
[16:14] <kgunn> Dev^Null4: altho, sounds like you'd need an ubuntu-core port none the less....
[16:14] <dobey> dragonboard or rpi + touchscreen seems like it would do there
[16:14] <kgunn> or that
[16:14] <dobey> and probably a lot cheaper than buying phones
[16:14] <kgunn> true that
[16:15] <kgunn> unless they already own all the phones
[16:15] <dobey> well, cheaper than maintaining a port for a phone :)
[16:15] <kgunn> yeah that's true
[16:16] <kgunn> oh...caveat....rpi kernel still hosed for gfx atm
[16:16] <dobey> plus phones have plenty of extra hardware that could leave open potential security holes
[16:16] <kgunn> so dragonboard is immediately available....we're working with kernel team on the gfx stuff
[16:16] <Dev^Null4> wish i would have known about this about 3 months ago I took a general ubuntu-desktop install threw open box on it and locked down what the user could do that way for another project.
[16:19] <Dev^Null4> we can't / wont use rpi or similar due to the unrelability with version control. you never know what your going to get we went down that road before with catastrophic failure.
[16:20] <Dev^Null4> you can buy cheap phones for like 50.00 or less each if they get damaged who cares. security holes is a good point. but since these are industrial devices they will never see an internet connection.
[16:21] <dobey> cheap phones are cheap for good reason
[16:22] <dobey> not sure whta you mean about version control with rpi
[16:23] <Dev^Null4> we found veriations in the hardware between revs
[16:24] <dobey> oh. seems like something i'd expect for a hardware product if the version bumped.
[16:26] <dobey> internet connection wasn't exactly what i meant with security
[16:26] <Dev^Null4> dobey the hardware variations were between rev's i would expect it when they released a new rev but not before.
[17:00] <CoderEurope> Hiya ! anyone know where the road-map for the Ubuntu browser is at ?
[17:06] <CoderEurope> !help
[17:06] <ubot5`> Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience
[17:06] <CoderEurope> !paiteience
[17:11] <CoderEurope> Anyone working/here today ?
[17:17] <pmcgowan> CoderEurope, theres a large backlog, anything in particular you are interested in?
[17:35] <kevjava> So, I'm trying to install Ubuntu touch on my Nexus 4, and I'm following all the instructions on https://developer.ubuntu.com/en/phone/devices/installing-ubuntu-for-devices/
[17:36] <kevjava> Every time I do the flash, it pushes all the files over, the progress bar gets about 70% through, and it reboots into Android again.
[17:36] <kevjava> Is there any way I could see more information as to what's going wrong with the boot process?
[17:38] <dobey> what version of android do you have on the phone? do you have a weird recovery?
[17:38] <kevjava> It's stock Android - sitting at 5.1.1.
[17:39] <kevjava> I haven't rooted it or anything.
[17:39] <kevjava> Whoa - I tried it a fifth time on a lark, and I got the setup screen. :)
[17:39] <dobey> flash stock 4.4 on it, boot to android, then reboot to bootloader and try again with --bootstrap option
[17:40] <dobey> oh
[17:40] <kevjava> All I had to do was ask about it, I guess.
[17:40] <kevjava> Thanks a lot for your help, dobey.  If I have any more issues, I'll try it from the stock 4.4.
[17:40] <CoderEurope> pmcgowan: I was looking at the last post on this ubports post-forum : https://forums.ubports.com/topic/127/browser-won-t-run-on-nexus-5/24
[17:43] <dobey> CoderEurope: i don't think there is really a "roadmap"
[17:44] <pmcgowan> unfortunately no complete public version
[17:44] <CoderEurope> theres no 'plans' for Ubuntu Browser ? dobey, pmcgowan ?
[17:44] <dobey> i don't see how having a roadmap would really help there
[17:44] <pmcgowan> btw from that post sounds like he used the devel channel which is never recommended
[17:45] <dobey> the "plans" are fix bugs, improve convergence, add features.
[17:45] <CoderEurope> I thought all Ubuntu projects are supposed to have a plan ?
[17:45] <dobey> pmcgowan: that's not the devel channel
[17:46] <dobey> having a plan and a TODO list is not the same as having a public roadmap
[17:46] <CoderEurope> could we create one ? would it help users / coders ?
[17:46] <dobey> i don't see how it would help with that thread on ubports forum
[17:47] <CoderEurope> I am murming about Ubuntu the browser.
[17:47] <pmcgowan> dobey, maybe I misunderstood  "I tested the devel_rc-proposed image"
[17:47] <dobey> pmcgowan: devel_rc-proposed is rc-proposed but built with android 5 base, on ubports, at least for nexus 5
[17:47] <CoderEurope> **murmering
[17:49] <dobey> if the browser is "crashing" reliably and consistently there, then it's probably some bug; roadmaps don't tend to include arbitrary bugs
[17:49] <CoderEurope> can you specifiy a bug ?
[17:50] <ogra_> broken code
[17:50] <dobey> the problem isn't a missing feature
[17:50] <dobey> it's faulty code
[17:52] <CoderEurope> dobey - I am looking for something to point 'them' in the right direction <Signposting (it's called)> ?
[17:52] <dobey> whom?
[17:52] <CoderEurope> the guys onblinkin' ubports.com
[17:54] <popey> Step 1: file a bug. Attach logs from browser and / or upstart logs from ~/.cache/upstart
[17:55] <dobey> well if it's actually a crash, then likely already filed
[17:55] <popey> possibly
[17:55] <popey> assuming they didn't disable apport
[17:55] <dobey> https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1500117
[17:55] <ogra_> to file a bug ... see the channel topic link "bug filing"
[17:55] <ubot5`> Error: ubuntu bug 1500117 not found
[17:55] <dobey> seems to have 103 instances reported today already
[17:55] <popey> looks good
[17:56] <CoderEurope> Cheers popey - That's what I shall tell them.
[17:56] <popey> number 78 on errors.ubuntu.com
[17:56] <popey> CoderEurope: looks like we already have a bug
[17:56] <CoderEurope> errors.ubuntu.com ? Does that work for just 'users' ?
[17:56] <dobey> not sure if that's what's happening here though
[17:57] <popey> CoderEurope: define "work"?
[17:57] <ogra_> CoderEurope, see the launchpad.net url that dobey posted above
[17:57] <popey> CoderEurope: basically, get them to file a bug, if it's a duplicate, we'll mark it as such
[17:57] <popey> ogra_: private bug
[17:57] <ogra_> oops
[17:57] <popey> so he wont be able to see it
[17:57] <dobey> CoderEurope: no, i think it's limited to certain teams, as crashes may have private data in them
[17:57] <CoderEurope> well can I find 'error 78' on that part of the ubuntu website ?
[17:57] <ogra_> yeah,. i missed the red bar at the top
[17:58] <CoderEurope> dobey, Oh gottcha.
[17:58] <CoderEurope> so its private :(
[17:58] <popey> CoderEurope: i just went to errors.ubuntu.com and looked for the bug number dobey filed
[17:58] <popey> which is down at 78
[17:58] <popey> that one is, but your friend can create a new public one if they wish
[17:58] <dobey> oops
[17:59] <dobey> i just realized that was for 16.04 crashes
[17:59] <popey> thats not what errors says
[17:59] <dobey> so maybe not the same as the issue on n5
[18:00] <popey> maybe, maybe not, best for user to file a bug anyway
[18:00] <dobey> well, the 103 instances today was on 16.04
[18:00] <CoderEurope> popey - it only goes down to 79 on mine (when I log-in).
[18:00] <popey> goes to 100 here
[18:00] <CoderEurope> never been there - so sorry for bein' n00bish.
[18:00] <popey> np
[18:00] <popey> that crash has apparently happened 36 thousand times or so
[18:00] <CoderEurope> https://archive.fo/8Skse
[18:01] <popey> seems a recurring thing
[18:01] <dobey> might be the typical qtmir not being able to connect to mir issue
[18:01] <popey> yeah, it's an insta-crash
[18:01] <popey> could be
[18:02] <popey> someone reported it over xmas on G+, I asked for logs but they'd already wiped the device
[18:02] <dobey> well first thing i would suggest is to check /var/crash to see if it's actually crashing
[18:02] <dobey> and make sure error reporting is enabled
[18:02] <dobey> and if it's not that, then check the log in ~/.cache/upstart/ for webbrowser-app
[18:02] <popey> in fact the 16.04 crashes are on amd64
[18:02] <popey> mostly
[18:02] <dobey> yeah
[18:03] <dobey> as i'd expect them to be
[18:03] <popey> in fact precisely none are armhf
[18:03] <dobey> the qtmir weirdness usually happens when unity8 session is installed and qtmir backend selection gets wonky between x and mir
[18:04] <dobey> and the u8 snap is also built from 16.04
[18:04] <dobey> i think it really only happens on the phone when one tries to just run "webbrowser-app" in terminal or such
[18:05] <popey> \o/ food time
[18:05] <popey> o/
[18:05] <CoderEurope> Do you mean remmina at bug 79? https://imgur.com/a/5ZPxE
[18:05] <ubot5`> bug 79 in Baz (deprecated) ""baz diff" interface differs from cvs/svn" [Medium,Invalid] https://launchpad.net/bugs/79
[18:05] <dobey> yeah, i really should eat
[18:05] <dobey> CoderEurope: i doubt it
[18:06] <dobey> CoderEurope: and i just managed to cause a bunch of confusion with my suggestion it might be that bug
[18:06] <popey> yeah, file a bug :)
[18:06] <dobey> CoderEurope: anyway, i suggest verifying if it's actually a crash or not, and checking the logs, and filing a new bug
[18:07] <dobey> CoderEurope: but he meant 78 in that picture, not 79
[18:07] <CoderEurope> oh cheers - webbrowser app bug 78 , right-oh
[18:07] <ubot5`> bug 78 in Baz (deprecated) "When asking you to sign something; baz should tell you what" [Medium,Won't fix] https://launchpad.net/bugs/78
[18:08] <dobey> no, it's the 78th most reported crash. not a bug numbered 78
[18:08] <dobey> and "reported" here means from automatic crash reporting
[18:09] <CoderEurope> well that is the ranked 8th crash & IT is a web vbrowser bug.
[18:09] <dobey> and almost all hits of it, are on x86 PCs
[18:09] <CoderEurope> **78th
[18:09] <dobey> yes, but the bug numer is not 78
[18:09] <dobey> it's the link i pasted earlier to lp
[18:09] <CoderEurope> yeah I get that.
[18:10] <CoderEurope> It doesn'r exist : https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1500117
[18:10] <ubot5`> Error: ubuntu bug 1500117 not found
[18:11] <CoderEurope> Anywauy I food new food like popey said , so  see-ya'll
[18:16] <CoderEurope> **need new food ......
[22:38] <JoeDoe> Hello, will ubuntu touch support gtk3 in future ? Thanks in advanced
[22:46] <JoeDoe> Is there a way to create an C/C++ app without QML , only OpenGL ?
[22:56] <dobey> you don't need to use qml; you could just create a QWindow that has a surface in it if you want
[22:57] <dobey> and gtk3 has a mir back-end today. you would just need to build gtk3 with the support and include it in your app directly
[22:58] <dobey> JoeDoe: someone built the qt3d teapot example for the phone and put it in the store, for example
[22:59] <JoeDoe> OK thanks. does is mean that i have to use QT ?  Or can I use CodeLite/CodeBlocks for example to create the gtk3 app ?
[23:09] <dobey> you can use whateveer you want to create an app (so long as whatever you're using support rendering to Mir); however, the further you deviate from the default sdk, the more complex/difficult it gets to build a working app
[23:12] <dobey> anyway, i have to go now. good luck
[23:26] <JoeDoe> Thanks