**** BEGIN LOGGING AT Fri Mar 04 02:59:58 2016
Mar 04 05:08:03 <DougReeder_> Herrie, thanks for looking at #1113. settings.localContentCanAccessFileUrls: true sounds correct; is there a full list of flags somewhere?
Mar 04 05:27:23 <Herrie|2> DougReeder_: I think we have everything relevant in QtWebEngine of Qt 5.5 enabled
Mar 04 05:27:27 <Herrie|2> Let me find a link
Mar 04 05:27:33 <DougReeder_> ok
Mar 04 05:28:08 <Herrie|2> DougReeder: It's fairly limited in QT 5.5: https://doc.qt.io/qt-5/qml-qtwebengine-webenginesettings.html
Mar 04 05:29:36 * DougReeder_ reads
Mar 04 05:36:00 <Herrie|2> It could be just a bug somehow in Qt 5.5 or something in our implementation
Mar 04 05:36:12 <Herrie|2> Or a simple flag we need to enable in chromium somewhere
Mar 04 05:36:22 * DougReeder_ nods
Mar 04 05:37:00 <DougReeder_> It’s possible localContentCanAccessFileUrls and —allow-file-access-from-files are not connected.
Mar 04 05:37:27 <DougReeder_> So much for it being an easy fix.
Mar 04 05:39:46 <Herrie|2> DougReeder_: Well QtWEbEngine in Qt 5.5 was the first proper release. Tofe needed to back-port a few things from 5.6 to make it workable for us and to fix some bugs already
Mar 04 05:40:15 <Herrie|2> Tofe will be looking into migrating to Qt 5.6 shortly, which will give some new cool features as well and quite some bugfixes
Mar 04 05:41:10 <DougReeder_> We’re not running in incognito mode, right?
Mar 04 05:41:19 <Herrie|2> DougReeder_: See https://wiki.qt.io/New_Features_in_Qt_5.6
Mar 04 05:41:31 <Herrie|2> DougReeder_: Not sure but don't think we are
Mar 04 05:41:50 <Herrie|2> Just could be quite some things have been fixed
Mar 04 05:42:00 * DougReeder_ nods
Mar 04 05:42:23 <Herrie|2> Hence I think it's worth the upgrade and dig further if it doesn't fix it
Mar 04 05:45:13 <Herrie|2> DougReeder_: The banners not playing sound is on my radar, just need to get my head around it :P
Mar 04 05:45:21 * DougReeder_ nods
Mar 04 05:45:24 <Herrie|2> Did some work in the background, just need to hook all up
Mar 04 05:46:15 <Herrie|2> I probably should push the fix for the sound first. I've been combining it with the fix for miniIcon which I didn't solve yet.
Mar 04 05:53:57 <DougReeder_> Ok, time for me to sleep.
Mar 04 05:54:03 <DougReeder_> Thanks again!
Mar 04 05:56:04 <Herrie|2> morphis: ping
Mar 04 05:56:31 <morphis> Herrie|2: pong
Mar 04 05:59:01 <Herrie|2> morphis: morning :)
Mar 04 05:59:17 <Herrie|2> From what I read PulseAudio should switch to BT headset automatically when connected?
Mar 04 05:59:26 <Herrie|2> But it doesn't seem to do that for us.
Mar 04 05:59:34 <Herrie|2> Any ideas for an easy fix?
Mar 04 05:59:45 <morphis> Herrie|2: about which profile are we talking here? A2DP or HFP/HSP?
Mar 04 06:01:30 <Herrie|2> morphis: Not sure, how can I see which profile is connected?
Mar 04 06:01:44 <morphis> bluetoothctl
Mar 04 06:01:46 <morphis> then
Mar 04 06:01:49 <morphis> info <mac>
Mar 04 06:01:54 <morphis> ah wait
Mar 04 06:01:57 <morphis> you don't have bluez5
Mar 04 06:02:25 <morphis> Herrie|2: do a pactl list cards when the headset is connected
Mar 04 06:02:56 <Herrie|2> adb acting up, let me reboot N4
Mar 04 06:05:05 <Herrie|2> morphis: https://bpaste.net/show/c22b7822292b
Mar 04 06:05:29 <morphis> there is BT connection and so no new audio card
Mar 04 06:05:35 <morphis> s/is/is no/
Mar 04 06:06:01 <morphis> Herrie|2: is the bluetooth module for bluetooth loaded at all?
Mar 04 06:06:04 <Herrie|2> I guess it paired with another device :P
Mar 04 06:06:12 <Herrie|2> Let me try again
Mar 04 06:07:02 <Herrie|2> It tells me BT is connected and I get visual feedback in settings
Mar 04 06:07:08 <Herrie|2> When I tap to connect to headset
Mar 04 06:07:30 <morphis> that doesn't mean much
Mar 04 06:07:35 <Herrie|2> Still only have card#0
Mar 04 06:07:43 <Herrie|2> headset also says it connected
Mar 04 06:07:44 <morphis> pactl list modules
Mar 04 06:07:56 <morphis> that doesn't have to mean the right profile is connected
Mar 04 06:08:09 <Herrie|2> Ok got 0-14
Mar 04 06:08:36 <Herrie|2> https://bpaste.net/show/fb046f730582
Mar 04 06:15:52 <morphis> as I thought, you're missing the bluetooth ones
Mar 04 06:16:27 <Herrie|2> OK, any idea how to fix that? Since you're the BT expert I thought to ask you :)
Mar 04 06:16:46 <morphis> Herrie|2: see http://bazaar.launchpad.net/~phablet-team/ubuntu-touch-session/rtm-14.09/view/head:/touch.pa#L61
Mar 04 06:16:58 <morphis> those bluetooth lines is what you need in your pulseaudio conf file
Mar 04 06:17:06 <morphis> which must be somewhere in meta-webos-ports
Mar 04 06:17:34 <morphis> https://github.com/webOS-ports/meta-webos-ports/blob/master/meta-luneos/recipes-multimedia/pulseaudio/pulseaudio-distro-conf/webos-system.pa
Mar 04 06:17:50 <morphis> could be also that those modules aren't installed yet and therefore not loaded
Mar 04 06:24:39 <Herrie|2> morphis: They're not installed
Mar 04 06:24:49 <morphis> Herrie|2: there you go :-)
Mar 04 06:24:56 <Herrie|2> I unpacked a mako image, did a dir/s bluetooth-module*.so and nothing found
Mar 04 06:24:58 <morphis> Herrie|2: however HFP/HSP is different game
Mar 04 06:25:04 <Herrie|2> module-bluetooth that should be
Mar 04 06:25:09 <morphis> concentrate on A2DP first
Mar 04 06:25:10 <Herrie|2> I do have other module-*.so
Mar 04 06:26:03 <morphis> might be that the package name is just pulseaudio-module-bluetooth
Mar 04 06:26:06 <morphis> then add it to https://github.com/webOS-ports/meta-webos-ports/blob/master/meta-luneos/recipes-core/packagegroups/packagegroup-luneos-extended.bb
Mar 04 06:36:32 <Tofe> Morning!
Mar 04 06:36:52 <Herrie|2> Tofe: morning
Mar 04 06:37:53 <Herrie|2> morphis: So just to add it here: https://github.com/webOS-ports/meta-webos-ports/commit/700515caadbedb6ebf4221b84404fcdbb8334609 ?
Mar 04 06:39:31 <morphis> Herrie|2: like that but make sure the package really exists
Mar 04 06:39:35 <morphis> not sure about that
Mar 04 06:43:57 <Tofe> morphis: while you're there, do you have any idea what would cause a major android mismatch when using cm-11 (the one from your commit), 4.4.3, adapted kernel (also from your commit), latest qpa and latest hybris ? I'm a bit short of ideas
Mar 04 06:52:45 <Herrie|2> morphis: OK will check a bit
Mar 04 06:55:45 <morphis> Tofe: you used updated Android binary blobs?
Mar 04 06:56:05 <morphis> Tofe: or lets say, where do you got the Android build bits from?
Mar 04 06:57:38 <Tofe> morphis: from build.webos-ports.org/cm-11
Mar 04 06:58:31 <Tofe> but that's from the recipe
Mar 04 06:59:00 <Tofe> and otherwise it's a flash-all from Google's 4.4.3
Mar 04 07:08:33 <morphis> ah so you just took the latest tarball from there?
Mar 04 07:13:17 <Tofe> not the latest, I first tried the one your commit pointed to (mars 2015 iirc),and I got drivers errors and no graphics.
Mar 04 07:14:08 <Tofe> I tried a later one, out of curiosity, but same result
Mar 04 08:05:41 <Herrie|Veer> morning
Mar 04 09:00:43 <Tofe> re-morning
Mar 04 12:54:16 <JaMa> New unstable images for mako and maguro built on tahiti :)
Mar 04 13:25:37 <Herrie|Veer> JaMa: Should we expect any improvement for the mako situation?
Mar 04 13:37:22 <JaMa> Herrie|Veer: probably no
Mar 04 13:45:51 <Herrie|Veer> JaMa: OK, then I know I shouldn't be too disappointed if it still doesn't boot :P
Mar 04 18:17:12 <Herrie> elvispre: ping
Mar 04 18:57:48 <elvispre> Herrie: pong
Mar 04 20:15:51 <Tofe> mmh there's definitely something wrong with my way of flashing the N4...
Mar 04 20:16:38 <Herrie> Tofe: S
Mar 04 20:16:46 <Herrie> I remember doing the flash-all
Mar 04 20:17:15 <Tofe> The cm-10 based build I just did (I reverted the whole meta-smartphone changes, kept only qpa and hybris bumps) does work almost perfectly on my 4.4.3 N4
Mar 04 20:17:19 <elvispre> Tofe: I have done it so often lately that I feel like I'm getting good at it. I used to have trouble booting to recovery mode. Now I never fail.
Mar 04 20:18:05 <elvispre> Oh, you're talking about flashing back to Android.
Mar 04 20:18:16 <Tofe> elvispre, Herrie: I'm doing flash-all alright
Mar 04 20:18:38 <Tofe> but it looks like it doesn't install the whole thing, somehow
Mar 04 20:19:04 <Tofe> because the cm-11 based luneos build fails to boot on it, where the cm-10 succeeds
Mar 04 20:19:15 <Herrie> elvispre: TOfe is trying to upgrade to 4.4.x Android based
Mar 04 20:19:28 <Herrie> SAilfish OS guys fixed the issues that we also faced
Mar 04 20:19:43 <elvispre> Herrie: Yeah, I remembered.
Mar 04 20:20:07 <Tofe> Herrie: the good news is that bumping qpa and hybris to latest seems to work pretty well on our good ol' 4.2.2, so we'll be able to PR that at least
Mar 04 20:20:20 <Herrie> Tofe: Yeah why not :)
Mar 04 20:20:40 <Tofe> but I'm frustrated to not understand what I'm doing wrong with 4.4.3
**** ENDING LOGGING AT Sat Mar 05 02:59:58 2016