[00:28] <Elleo> jhodapp: what does media-hub do to make the sound indicator aware of its mpris service?
[00:30] <drsn0w> Hello, I'm interested in porting Ubuntu Touch to Nexus 5X (bullhead) however I'm having many issues, and I think they're to do with the fact that bullhead is a 64-bit device, and the existing tree doesn't seem to have any of the required make files
[06:17] <swalladge> where would i report a bug relating to wifi on ubuntu touch?
[06:18] <swalladge> system settings?
[06:20] <lpotter> that would be ok. people will redirect it if needed
[06:23] <swalladge> ok
[06:23] <swalladge> actually i might just ask on the answers.launchpad.net first
[06:24] <swalladge> my M10 isn't remembering wifi ap's properly - ie. it saves info about it, but doesn't associate the network with saved ones
[06:25] <swalladge> so in previous networks i have a list like MyWifinetwork1, MyWifinetwork2, MyWifinetwork3 .... etc., and asks for password to the network everytime i turn on the device
[06:25] <swalladge> any ideas?
[07:38] <minhaj3> Hi
[07:38] <minhaj3> Anyone here??
[07:40] <minhaj3> I wanted to know what can i do to port in huawei honor holly?
[07:55] <mardy> DanChapman: https://code.launchpad.net/~mardy/dekko/+git/dekko/+merge/301457
[08:04] <mardy> popey: hi! I guess you are the most experienced in this: I want to put a click package in a silo, how do I do it?
[08:04] <mardy> popey: package is dekko, built from https://code.launchpad.net/~mardy/dekko/+git/dekko/+merge/301457
[08:07] <popey> we generally just put a link to the click in citrain
[08:07] <popey> which may be hosted anywhere
[08:20] <mardy> popey: OK; and is there a way to let launchpad build an armhf click for you?
[08:25] <popey> mardy: dan usually builds the click.
[08:35] <faenil> duflu: great to see the wheel speed fix! :)
[08:35] <duflu> faenil: Yeah, but more exciting high-res touchpad scrolling comes for free from that
[08:36] <duflu> Need to fix other components still
[08:36] <duflu> I can't figure out where the offending code that's slowing down Qt apps is
[08:37] <faenil> duflu: yeah :) glad you found the issue in the end
[08:38] <faenil> duflu: at least scopes are using custom maximumVelocity and the likes
[08:38] <faenil> duflu: not sure about codepath for browser. It could also be that the default Flickable maximumVelocity is too low
[08:39] <duflu> faenil: would the max be enforced while you're still touching it?
[08:39] <duflu> That would explain lag
[08:39] <faenil> duflu: yeah I read your comment about that, I'm not sure, I don't think it should but I don't think I've ever actually read the logic there
[08:40] <faenil> duflu: let me have a quick peek and see if anything comes out
[08:40] <duflu> I don't know where to look or whether to look. It's approaching EOW
[08:40] <faenil> duflu: https://github.com/qt/qtdeclarative/blob/5.4/src/quick/items/qquickflickable.cpp
[08:41] <duflu> faenil: From the name alone it should be OK. It's not a "flick" if you're still touching the screen
[08:41] <faenil> duflu: wheel events surely are slowed down according to maxVelocity
[08:42] <duflu> faenil: I think wheel is a different problem - like wrong scaling factor (e.g. 15 instead of 120)
[08:42] <faenil> but when your finger is on screen, that shouldn't affect it
[08:42] <duflu> It's different code for wheel and touch
[08:42] <faenil> duflu: of course
[08:42] <faenil> duflu: https://github.com/qt/qtdeclarative/blob/5.4/src/quick/items/qquickflickable.cpp#L1269 this is how the wheel is slowed down
[08:43] <faenil> duflu: but mouseMove shouldn't be https://github.com/qt/qtdeclarative/blob/5.4/src/quick/items/qquickflickable.cpp#L987
[08:44] <duflu> faenil: I think angleDelta is wrong for Qt apps. And assume there is some project other than qtmir where we convert mir events into Qt??
[08:44] <duflu> Either that or we just have Qt logic with the wrong scale, and Mir is unrelated to the bug
[08:44] <faenil> mmm
[08:45] <faenil> duflu: what is the exact issue you see? the one related to the surface moving too slowly while the finger is on screen
[08:45] <faenil> the bug report explains the wheel stuff
[08:45] <faenil> could it not be just because we're 2-3 frames late at rendering?
[08:45] <duflu> faenil: Touch and wheels are completely separate bugs. I've been talking about multiple bugs here
[08:45] <faenil> duflu: yeah, do you have a bug report for the touch as well?
[08:46] <duflu> Yes......
[08:46] <duflu> faenil: Touch is not bad. Only:  https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1523823
[08:47] <faenil> duflu: thanks, I don't think I've seen that before in my emails, let me read
[08:47] <faenil> (ps: I'm just trying to see if I can help here, I'm not the input handling guru ;) )
[08:48] <duflu> Bug feel free to ignore that because we can live with it and ignore it for much longer than the wheel problem after the QtMir fix
[08:50] <faenil> duflu: at least on Krillin I can't see that. Aside from the natural lag, that imho comes from the fact that we're missing too many frames between input processing and rendering
[08:52] <duflu> faenil: Graphics lag is an issue yes, but does not explain why the dash is worse than the webbrowser on the same phone :)
[08:52] <faenil> duflu: browser and scopes seem to behave the same, on Krillin. Maybe it's device/resolution/whatever specific. Which
[08:52] <faenil> device do you see it on?
[08:52] <duflu> All
[08:53] <faenil> if I just drag up and down without releasing my finger I see mostly the same (too much) lag on both browser and scopes
[08:55] <faenil> duflu: do you see it, right now, on krillin (BQ E4.5) on ubuntu-touch/rc-proposed/bq-aquaris.en channel?
[08:57] <duflu> faenil: Always. But it might just be because the dash has much higher CPU+GPU usage
[08:58] <duflu> Anyway, phone/touch bugs are not what I'm focusing on right now
[08:58] <faenil> duflu: I just want to make sure we're talking about the same thing, because I'm quite sensitive to these kind of things, and I can't see any relevant difference at this point between browser and scopes on krillin
[08:58] <faenil> both are a few frames behind input
[08:58] <faenil> but nothing like speed throttling, just rendering/input lag
[08:59] <faenil> so I'm wondering if I'm misunderstanding your report...do you have a video anywhere of the bug?
[08:59] <duflu> faenil: Don't worry about it. Long term I will finish frame notification that will kill all lag
[08:59] <faenil> duflu: looking forward to that day :) I still would like to see the video though, if you feel like it :)
[09:00] <faenil> because I do worry about it :)
[09:00] <duflu> Well it's 5pm on a Friday. I'm finishing smaller and simpler things right now
[09:02] <faenil> duflu: oh sure, no rush! enjoy your weekend! I did not mean to imply I want you to do it now ;)
[09:30] <Mister_Q> swalladge just out of curiosity.. Did you use the bq oem tool to reflash your m10?
[09:33] <hwk> 12:30 pm here
[09:35] <faenil> duflu: have you seen this? http://bazaar.launchpad.net/~phablet-team/qtubuntu/trunk/view/head:/src/ubuntumirclient/input.cpp
[09:37] <duflu> faenil: That's what I missed. Thanks!
[09:37] <faenil> duflu: awesome!
[09:38] <faenil> not sure it will help that much, but let's hope so :)
[09:42] <mardy> jgdx: hi! Do you have some time (and desire) to test https://requests.ci-train.ubuntu.com/#/ticket/1722 ? I've attached a dekko click to it, too
[09:45] <duflu> faenil: You rock. Webbrowser scrolling (etc) now fixed too
[09:46] <faenil> duflu: woooot :) well done!
[09:46] <duflu> With high-res touchpad precision now
[09:46] <faenil> duflu: (now I'm even more curious to see what was the actual bug that I can't seem to reproduce on krilling :P )
[09:46] <faenil> awesooome
[09:48] <faenil> ah ok you meant you fixed wheel scrolling duflu, not touch, right?
[09:48] <duflu> faenil: yes, wheel and touchpads, not touch
[09:48] <faenil> duflu: ok, still super cool, yay
[09:58] <jgdx> mardy, yes
[10:11] <jgdx> tedg, hey, could you point me to the docs for ubuntu_app_launch_start_application from libubuntu-app-launch2-dev?
[10:11] <jgdx> tedg, I fail to launch an app using an appid, even if it seemingly conforms to the spec: https://wiki.ubuntu.com/AppStore/Interfaces/ApplicationId
[11:37] <jgdx> mardy, testing now…
[11:38] <mardy> jgdx: thanks!
[11:44] <jgdx> mardy, I need to refresh in Dekko it seems. I guess Dekko has no means of getting notified?
[11:44] <mardy> jgdx: refresh? I'm not sure what do you mean
[11:45] <mardy> jgdx: you just have to give Dekko access to your gmail account, and that should be all
[11:45] <jgdx> mardy, I got a notification, tapped it, entered Dekko. The newly received email is not visible in Dekko lest I refresh
[11:45] <mardy> jgdx: mmm... here it refreshed automatically
[11:46] <jgdx> lemme try again
[11:46] <mardy> jgdx: anyway, the Dekko part still needs improvement, it should be made to open the new message right away
[11:48] <zzarr> when will Ubuntu launch on phones/tablets? (I mean when will devices be available in shops)
[11:49] <k1l_> zzarr: they are since some time. or do you mean a specific device?
[11:50] <jgdx> mardy, right, and Dekko is dispatched with an URL sufficient to do that. So it's up to Dekko, not account-polld, to implement this?
[11:50] <zzarr> I know they are available from ubuntu.com (I have an Ubuntu phone) I mean when operators will begin to sell them
[11:51] <mardy> jgdx: exactly
[11:51] <k1l_> zzarr: they do already
[11:51] <k1l_> zzarr: and ubuntu doesnt sell them. its the manufacturers who sell them
[11:52] <jgdx> mardy, rog. Okay, looks good here
[11:52] <zzarr> k1l_, I know, but service providers don't sell them yet (not in Sweden in any way)
[11:52] <k1l_> zzarr: this is from a german IT supermarket: https://twitter.com/toddyfranz/status/672467605555453952
[11:53] <mardy> jgdx: thanks, I also did some testing and didn't notice any issues; I'll hand it over to QA, then
[11:53] <peat-psuwit> Hello. I'm porting Ubuntu Touch to Samsung Galaxy Tab 2 7.0. The screen's native orientation is in landscape, but touchscreen expects the screen to be in portrait. So, how to set screen's native rotation? Or, alternatively, how to swap touchscreen's axes?
[11:53] <k1l_> zzarr: well, look at the manufacturers who have ubuntu phones and if they sell to sweden.
[11:55] <zzarr> k1l_, I didn't know they were sold in shops in Germany, but when I think about it I'm not surprised
[11:55] <robinhero> mardy, What do you think, will this modification of account-polld available in OTA-13?
[11:56] <mardy> robinhero: yes it will, unless we find some regression that forces us to pull it off
[11:56] <zzarr> k1l_, I know how to get a phone here
[11:56] <robinhero> mardy, sounds good, thanks :)
[11:56] <jgdx> mardy, one sec, can you reproduce this: Open dekko, swipe away dekko, receive email, tap notification: i can't open the newly received mail
[11:58] <zzarr> k1l_, the reason for my question is when will the real native apps come, I mean there are already many very good apps
[11:58] <k1l_> zzarr: the manufacturers have very strange strategies with where to sell and how marketing should work. i dont understand where, when and why they are selling them or not selling them.
[11:58] <robinhero> mardy, I'll be home in a few hours, and will give it a try on my testing device :)
[11:58] <robinhero> *at
[11:58] <k1l_> zzarr: what native apps?
[11:59] <zzarr> Dekko is in fact the best mail browser I have used on a mobile device
[12:00] <zzarr> well very many apps are webapps so far
[12:00] <zzarr> but I think that native apps give a more solid feeling
[12:01] <zzarr> in any way, I'm impressed with the phone so far
[12:02] <jgdx> zzarr, yeah, I think we need quantum computers to make webapps feel native
[12:02] <k1l_> that depends on the developers beeing able to make native apps.
[12:02] <zzarr> jgdx ;)
[12:02] <jgdx> zzarr, :)
[12:02] <mardy> jgdx: trying...
[12:04] <jgdx> there are a couple of preceding errors in the log, but not sure if pertinent or not
[12:06] <jgdx> mardy, http://pastebin.ubuntu.com/21394369/
[12:06] <mardy> jgdx: ah! weird: Dekko refreshed, shows the e-mail, but indeed nothing happens if I tap it
[12:07] <mardy> jgdx: actually, I cannot open any message
[12:07] <jgdx> right, me neither
[12:08] <jgdx> seems to be triggered by the dispatcher, as performing the steps above without tapping a notification does not reproduce.
[12:11] <mardy> jgdx: seems like bug 1570774
[12:11] <mardy> jgdx: I'll add a comment to that bug
[12:11] <jgdx> indeed
[12:12] <jgdx> mardy, I would think that became critical for that release though.
[12:12] <jgdx> s/release/silo 55
[12:12] <mardy> jgdx: indeed
[12:51] <jhodapp> Elleo, media-hub just exports the MPRIS dbus service
[12:51] <swalladge> Mister_Q: re flash tool: yes' because i somehow managed to semi brick it so had to fix the partitions...
[12:53] <Mister_Q> swalladge then that most likely explains your wifi bug :/ Did you "Format everything & Download" or just "Download" in the tool? Format everything deletes the imei partitions and that makes the network manager act weird even if it works on android. check if your serial number is something lik 01234
[12:57] <swalladge> Oh right wow. Yeah i'm pretty sure i formatted because just download didn't work
[12:58] <Mister_Q> swalladge you have to send it in to bq for an imei repair :/
[12:58] <swalladge> I'll check out the serial numbers tomorrow.
[12:58] <swalladge> Ouch really? Surely the bq tool should put it to factory condition?
[12:58] <Mister_Q> swalladge unfortunately not
[12:59] <swalladge> Could that explain it not recognizing/outputting to a monitor via HDMI as well?
[12:59] <Mister_Q> yes !
[12:59] <Mister_Q> "format everything" does literally what it says. including _every_partition
[13:00] <swalladge> Aaah well that explains everything. Thanks :)
[13:01] <Mister_Q> thats why I've wrote a tool for reflashing ubuntu devices. to stop people from using dangerous oem tools https://github.com/MariusQuabeck/magic-device-tool
[13:02] <swalladge> Nice
[13:02]  * Mister_Q may accidentally formatted everything once as well ;)
[13:05] <swalladge> Lol I'll literally have to send it half way around the world to get it fixed... (And then back again)
[13:07] <Mister_Q> you cant restore the imei partitions yourself :/ bq has to do that
[13:12] <Elleo> jhodapp: odd, I'm doing the same (i.e. registering org.mpris.MediaPlayer2.CuteSpotify) but sound-indicator doesn't pick up on it
[13:12] <Elleo> jhodapp: wasn't sure if there was some extra call I need to make to something to make it aware of that
[13:32] <jhodapp> Elleo, try doing a dbus capture of Rhythmbox on the desktop when it comes up and you'll capture it exporting MPRIS...that's the best and easiest example to capture and emulate
[13:33] <Elleo> jhodapp: okay, thanks
[13:50] <jgdx> dobey, hey, you get to take a look at that u-push hack?
[13:52] <dobey> jgdx: i said in irc it looks ok, but maybe not what i'd necessarily do. i'd probably just get rid of the vendorizing and just rely on the packages if possible
[14:00] <jgdx> dobey, sorry, missed that. Yeah, that's what I want too, but then we wouldn't get it to build on vivid due to a lack of deps.
[14:00] <dobey> jgdx: eh? then how does it build on vivid in the archive today?
[14:01] <jgdx> dobey, yeah, but that's using the old deprecated go packages that does not exist upstream.
[14:02] <jgdx> e.g. the code.google.com go-sqlite has disappeared upstream, and it's replacement has no deb package in vivid
[14:02] <jgdx> as I understand it
[14:02] <dobey> jgdx: oh, well, all code.google.com has disappeared because google shut down code
[14:03] <dobey> jgdx: i'd probably kill the symlinks stuff and just fix the imports to reference the github stuff instead, if you have to use vendorized stuff there
[14:04] <jgdx> dobey, kill the symlink to usr/share/gocode/src… ?
[14:05] <dobey> jgdx: no, in your MP you're making a symlink to preserve the "code.google.com/..." paths for the things that moved to github, rather than changing the imports that use them
[14:08] <jgdx> dobey, right, so if I change the imports for sqlite to use the recommended lib, I need to backport golang-github-mattn-go-sqlite3 to the overlay. IIUIC
[14:08] <jgdx> because otherwise the dev setup would be fine, but at build time, it would fail on vivid+overlay
[14:09] <dobey> jgdx: didn't you just say the current things aren't packaged in vivid+overlay?
[14:11] <jgdx> dobey, the code.google imports have debs, the things I'm symlinked do not have debs, but we just use the code.google debs.
[14:12] <jgdx> it's a mess
[14:12] <dobey> jgdx: ok, then i guess we have to use the symlinks to work around that issue for now
[14:12] <dobey> yeah, i am very not fond of golang
[15:46] <qrazi> Quick question: I installed multirom on my nexus 5, and my primary rom is stock Android 6.0.1
[15:47] <qrazi> When I install Ubuntu Touch through multirom, I cannot boot. It shows the Google logo for a bit, and then reboots
[15:47] <qrazi> What could be the problem?
[15:48] <Mister_Q> qrazi, did you install a kexec capable kernel (as suggested in the multirom app)?
[15:49] <qrazi> Yes... (99% sure, but can't check as I left that phone at home... :-/ )
[15:59] <olofm> is the appstore broken at the moment? i can not find QVBA-M :(
[16:00] <olofm> it is listed in uapp explorer but i can not find it in the store
[16:56] <dobey> olafh: on a phone/tablet, or on a PC?
[16:57] <dobey> olafh: are you on ota12?
[16:58] <dobey> olafh: that app is using a long deprecated framework which was recently removed. the app needs to be udpated
[16:59] <dobey> err
[16:59] <dobey> olafh: oops, sorry. that was for olofm who apparently left, but has a nick irresponsibly similar to yours :)
[17:16] <ohyash> mariogrip : ping
[17:16] <ohyash> is this page ever gonna show up? https://wiki.ubports.com/wiki/Porting-to-new-device
[17:23] <genii> ohyash: You can also refer to https://developer.ubuntu.com/en/phone/devices/porting-new-device/
[17:24] <ohyash> genii : Doesnt seem to be updated in a long while. Does it still work?
[17:34] <genii> ohyash: The process has not changed much since then, it can still be used as a guide
[17:36] <ohyash> genii : Interesting. Ubuntu's proting guide seems pretty straight foreward. I havent seen one like this anywhere else.
[17:37] <ohyash> SailfishOS' porting guide is pretty harder compared to this
[17:46] <hwk> is there a channel dedicated to debian-arm distro?
[17:47] <hwk> was thinking if i can start systemd manually in a chroot environment
[17:47] <ohyash> try talking in raspbian's channel. (if it exists, IDK)
[17:47] <genii> There's also #ubuntu-arm but it's usually somehwat quiet in there
[17:49] <dobey> maybe #debian-arm ? :)
[17:51] <hwk> population 10 :D
[18:01] <ohyash> how hard would porting ubuntu-touch be if my device comes with cyanogenOS installed, sources are in git, and I've never ported any OS before?
[18:06] <hwk> do you know the source coude of you device well?
[18:07] <hwk> drivers, apps which integrate with the drivers
[18:10] <ohyash> hwk, havent checked into it.. But I guess yes. They're opensource friendly, thats what they said when they launched to company. (YU)
[18:12] <ohyash> hwk, here : https://github.com/YUTeleventures/device_yu_lettuce
[18:25] <hwk> dont see much code there
[18:28] <ohyash> How do I use whatever's required from there?
[18:28] <ohyash> Oh, and how much time approximately does final rom compilation take?
[18:34] <dobey> it's not a matter of just compiling things and then it will work
[18:34] <dobey> porting a device takes a whole lot of time, even for someone that knows what they are doing
[18:36] <ohyash> dobey, was just asking cuz my laptop run AMD A4. which takes half and hour to compile compiz. and almost 2 to compile wine
[18:38] <dobey> ohyash: right. i don't know how long it will take to cross-compile the stuff
[18:39] <peat-psuwit> Can anyone with supported device give me the content of /etc/ubuntu/devices.conf, please?
[18:51] <DexterF> hi
[18:52] <DexterF> how does app separation / permission restrictions work on U/T? like: how does it keep a website from telling my location from the GPS module? keep games from telling my movement profile to their authors? etc
[18:53] <dobey> well, if you allow a game to access your location, then while that game is being played, it can freely send your location data to somewhere on the internet
[18:53] <dobey> however, while the screen is locked, or the app is in the background, it is not running, and can no longer process data
[18:54] <dobey> if an app needs location data, then when it tries to use the API the first time, you get a popup asking if you want to allow/deny it access to location data
[18:55] <dobey> there's similar popups for camera and mic access
[19:33] <abcd> hello
[19:34] <abcd> I've got a nexus 4 which i've put ubuntu on. I've bought a slimport adapter to vga, the screen detects a signal, but just shows a black desktop.
[19:34] <abcd> are there problems with certain hardware?
[19:44] <dobey> abcd: very possible, yes
[19:45] <dobey> abcd: have you verified the adapter works with android?
[19:45] <abcd> dobey: thanks
[19:45] <abcd> dobey: nope, I could put android back on....
[19:46] <abcd> other than that can anybody recommend one that works?
[19:46] <polylux> good evening everyone, somebody around who is using syncevolution?
[19:47] <dobey> abcd: well, i don't think anyone has tested any that would use vga anyway. i think only ones that have been tested are hdmi.
[20:01] <DexterF> dobey: I meant: where are these permissions defined? how does control work?
[20:10] <DexterF> where do I find documentation about Touch? api descriptions etc
[20:20] <dobey> DexterF: https://developer.ubuntu.com
[20:22] <DexterF> dobey: thanks
[23:14] <swalladge> Mister_Q: yep, my M10's serial number is 0123456789ABCDEF
[23:14] <Mister_Q> swalladge then you have to send it to bq sorry