**** BEGIN LOGGING AT Wed Jan 20 02:59:59 2016
Jan 20 06:27:15 <dkirker> Herrie: If you see nizovn, could you please point him my way?
Jan 20 06:27:45 <dkirker> I am going to wrap my head around the location services so that I can get something going for legacy webOS and not overlap any work if possible.
Jan 20 06:41:33 <Herrie> morning
Jan 20 06:42:04 <Herrie> dkirker: He's usually around European evenings, so your mornings & weekends
Jan 20 06:42:22 <dkirker> hmmmm, that makes it tough... lol
Jan 20 06:42:25 <dkirker> and mornin
Jan 20 06:45:44 <Herrie> dkirker: LuneOS will very soon be in a state you won't care about legacy anymore :P
Jan 20 07:40:36 <Herrie> Andolamin: The new change for Messaging works nicely :D
Jan 20 07:40:59 <Herrie> Tofe: Phone app now launches but not much more, outgoing calls & incoming doesn't work really
Jan 20 07:43:27 <Herrie> Tofe: I see things happening in log, but not much in UI
Jan 20 07:54:28 <Herrie> Seems my SIM might be blocked :P
Jan 20 07:54:33 <Herrie> Let me add some EUR to it :P
Jan 20 08:09:32 <Herrie> At least I can make calls with it on my Pre 3 now ;0
Jan 20 08:09:39 <Herrie> Let me put it in N4 :)
Jan 20 08:17:03 <Tofe> Morning!
Jan 20 08:17:47 <Tofe> Herrie: I should have a new SIM today or tomorrow
Jan 20 08:19:01 <Tofe> (in the current state, I prefer not to use my everyday SIM :p )
Jan 20 08:19:41 <Herrie> Tofe: Yeah can imagine ;)
Jan 20 08:19:51 <Herrie> Seems we get a SEGV along the line in webos-telephonyd
Jan 20 08:19:52 <Herrie> https://bpaste.net/show/2ead715cb482
Jan 20 08:20:00 <Herrie> Jan 20 03:13:12 mako systemd[1]: webos-telephonyd.service: main process exited, code=killed, status=11/SEGV
Jan 20 08:20:30 <Herrie> Jan 20 03:13:35 mako ofonod[1370]: Call 1 ended with RIL cause 65535
Jan 20 08:20:38 <Herrie> 65535 is suspicious code as well :P
Jan 20 08:21:04 <Herrie> This is for a call from my Veer->N4
Jan 20 08:23:37 <Herrie> Let me reboot and try to call from N4
Jan 20 08:34:24 <Herrie> Call seems to go through eventually, but no visual clues on screen ;)
Jan 20 08:38:23 <Herrie> Some progress: While on call when I do: luna-send -n 1 luna://org.webosports.audio/setCallMode '{}'
Jan 20 08:38:39 <Herrie> Some progress: While on call when I do: luna-send -n 1 luna://org.webosports.audio/setCallMode '{"inCall":true}'
Jan 20 08:38:56 <Herrie> I can hear what I say in my Veer over the speaker of N4 :D
Jan 20 08:39:03 <Herrie> Microphone for N4 doesn't work :P
Jan 20 08:39:13 <Herrie> But that's probably another LS2 call away :P
Jan 20 08:48:43 <Herrie> Ah wait that also works, just N4 has pretty good noice cancelling :P
Jan 20 08:48:54 <Herrie> Tofe: THat doesn't seem like a lot of work to fix anymore :P
Jan 20 08:54:17 <Herrie> Tofe: 1. so the display doesn't change when you press the dial button and you don't get the call timer, even though the call goes through. 2. Seems we need to do the LS2 call to luna://org.webosports.audio/setCallMode '{"inCall":true}' to activate the sinks
Jan 20 09:13:55 <Tofe> Herrie: good!
Jan 20 09:14:18 <Tofe> Herrie: no UI response either when receiving a call?
Jan 20 10:43:32 <Herrie> Tofe: Sorry was taking a nap with the little one ;) He's not been sleeping too well lately, so neither have we :P
Jan 20 10:43:53 <Herrie> Yeah no UI on incoming call either. That could be simple Z-index issue or the webos-telephonyd crashing as per my log
Jan 20 11:50:14 <Tofe> I think Z-index is fine, but there might be some bugs in voicecall
Jan 20 11:50:29 <Tofe> or the layer below
Jan 20 12:31:39 <Herrie> Tofe: Yeah most probably. I guess once you got it in a more or less working state it might be worth to just bump all connection components (connman, ofono, qtconnman, voicecall etc) to latest
Jan 20 12:31:46 <Herrie> That should resolve quite some issues down the line
Jan 20 13:01:52 <Tofe> probably
Jan 20 13:15:22 <Herrie|Veer> We're about 10 months and 150 or so commits behind on oFono from Mer :P
Jan 20 13:16:40 <Tofe> Herrie|Veer: Well, I can't say I'm really satisfied with the way my Jolla handles network connections sometimes
Jan 20 13:17:02 <Herrie|Veer> Tofe: Hehe :P
Jan 20 13:17:13 <Herrie|Veer> I have no experience but I believe you ;)
Jan 20 13:17:35 <Herrie|Veer> But there seems to be tons of commits that seem to solve various small issues.
Jan 20 13:18:26 <Herrie|Veer> I.e. memory leaks and lots of other small things :)
Jan 20 13:18:35 <Tofe> No longer than yesterday, I was in a state where the phone says "3G", but actually it seems like the whole mobile connection was broken (no call, no sms)
Jan 20 13:18:49 <Herrie|Veer> Tofe: Hmmmz
Jan 20 13:19:08 <Herrie|Veer> Well doesn't need to be oFono itself, can be other parts of course
Jan 20 13:19:11 <Tofe> Seems to happen when switching between mobile data and wifi, somehow
Jan 20 13:19:38 <Herrie|Veer> Not sure what's included in the image you're running?
Jan 20 13:19:52 <Tofe> let me see
Jan 20 13:22:33 <Tofe> ofono-1.16+git14-1.30.1
Jan 20 13:22:59 <Tofe> what's ours?
Jan 20 13:23:53 <Herrie|Veer> Also on 1.16
Jan 20 13:24:32 <Herrie|Veer> But that's from 04-Mar-2015, there's been tons of commits since to address tons of issues :P
Jan 20 13:24:32 <Tofe> https://github.com/webOS-ports/ofono/blob/webOS-ports/master/ChangeLog says 1.12
Jan 20 13:25:28 <Herrie|Veer> Recipe says 1.16. Was probably updated to 1.16 when we moved from Dora to Fido
Jan 20 13:25:40 <Tofe> mmh maybe I'm not looking at the right place
Jan 20 13:25:45 <Herrie|Veer> So not mentioned explicitly in the changelog :P
Jan 20 13:26:18 <Herrie|Veer> If I need to mention all package updates when switching OE the changelog will be a book :P
Jan 20 13:35:56 <Tofe> No I was not looking at the right place, we using upstream's repo directly, our ofono fork isn't used
Jan 20 13:40:05 <Herrie|Veer> Tofe: Yeah we should clean some things up a bit sometime
Jan 20 13:40:26 <Herrie|Veer> I already pulled a list of all our repo's and will check for license, status, access etc
Jan 20 13:40:32 <Herrie|Veer> To see how we can clean it up
Jan 20 15:15:28 <KyleMaas_Laptop> Working on bug #957: http://issues.webos-ports.org/issues/957
Jan 20 15:16:42 <KyleMaas_Laptop> Can't seem to figure out how to get touch events to register correctly on desktop Chromium.  Once I start a touch, it fires off a single move event and then doesn't fire off any more mouse/touch events (at least none that I've tried) until the touch finishes.
Jan 20 15:17:25 <KyleMaas_Laptop> Until I can catch the touch event, I can't block Chromium's built-in pinch-to-zoom, which means I can't get the pinch-to-zoom events to carry through into the app.
Jan 20 15:17:35 <KyleMaas_Laptop> Any suggestions?  Still kind of new to Enyo.
Jan 20 15:26:46 <Tofe> KyleMaas_Laptop: you can try to play a bit with index.html's "viewport" meta tag
Jan 20 15:27:32 <KyleMaas_Laptop> Tofe: I tried that with debug.html.  Didn't seem to fix anything.
Jan 20 15:28:07 <KyleMaas_Laptop> Digging through the Enyo code, it looks like Chrome is not detected as having multitouch support.  Wondering if that's fixed in a newer version of Enyo.
Jan 20 15:29:12 <Tofe> KyleMaas_Laptop: is the gesture event indeed sent down to the app?
Jan 20 15:32:15 <KyleMaas_Laptop> No.
Jan 20 15:32:40 <KyleMaas_Laptop> Looks like more of the app works if I enable Chromium's device emulation.
Jan 20 15:33:15 <KyleMaas_Laptop> Still doesn't handle multitouch correctly, though.  Chromium's built-in zoom kicks in, which means the touchMove event's default is not being cancelled within the app.
Jan 20 15:35:07 <Tofe> mmh
Jan 20 15:42:29 <Tofe> KyleMaas_Laptop: right now, I don't know where the pb would be; it would require more debugging I think
Jan 20 15:43:36 <Tofe> But I didn't see anything in Enyo really related to a specific engine like WebKit (which is still very present in Chromium anyway)
Jan 20 16:04:52 <Herrie|Veer> JaMa: Seems Mako unstable ran and failed
Jan 20 16:05:54 <Herrie|Veer> KyleMaas_Laptop: I recall trying the new Maps app on legacy and it worked there. So it's probably something in our implementation that's broken. It also didn't work with QtWebKit, so it's not QtWebEngine specific AFAIk
Jan 20 16:06:08 <JaMa> Herrie|Veer: I've see ICE while building libgcc, I've re-triggered build for tomorrow
Jan 20 16:07:16 <Herrie|Veer> OK thnx :)
Jan 20 16:11:14 <KyleMaas_Laptop> Herrie|Veer: So far it's failing pretty badly on Chromium, so I think it's an incompatibility with current WebKit/Blink.  I finally got it to detect multitouch.  Now I'm wrestling with the CSS3 transform differing from how the code was originally written (Chromium's ignoring the scale3d, preventing zooming).
Jan 20 16:12:33 <KyleMaas_Laptop> Actually...looking at it further, it's due to it feeding NaN into a translate transform.  Wonder why it's doing that...
Jan 20 16:14:50 <KyleMaas_Laptop> Cool.  Found it.  Pinch-to-zoom now works for in-process gestures but reverts once the gesture finishes.  Now to get it to stick.
Jan 20 16:17:27 <KyleMaas_Laptop> Got it to stick.  But now it pans quite far if you release one finger before the other.
Jan 20 16:33:01 <Herrie|Veer> KyleMaas_Laptop: Might be worth to check upstream Enyo repo seeing if they did anything. We're on Enyo 2.5.1 which is the latest official release, but could be they fixed things in the WIP 2.6.0 release
Jan 20 16:41:22 <KyleMaas_Laptop> I think I've got it.  The pan-while-zooming code's still got some bugs in it, but at least pinch-to-zoom works,
Jan 20 16:41:48 <Herrie|Veer> It's Enyo or the app?
Jan 20 16:47:26 <KyleMaas_Laptop> The app.
Jan 20 16:47:36 <KyleMaas_Laptop> Pull request that fixes it for me: https://github.com/webOS-ports/org.webosports.app.maps/pull/11
Jan 20 16:47:52 <KyleMaas_Laptop> Hope I formatted everything correctly.  First real code commit.
Jan 20 16:49:04 <Herrie|Veer> Will test it at home. Did you test legacy?
Jan 20 16:50:08 <KyleMaas_Laptop> No.  I've only tested it in desktop Chromium.  But the bug was a relatively obvious one.
Jan 20 16:50:38 <KyleMaas_Laptop> Also filed this bug, because while pinch-to-zoom works, from what I can tell panning during pinch-to-zoom doesn't look like it was ever smooth: http://issues.webos-ports.org/issues/1043
Jan 20 16:50:44 <Herrie|Veer> OK let me test it on LuneOS and Legacy tonight then :)
Jan 20 16:50:52 <KyleMaas_Laptop> Sounds good.
Jan 20 16:52:05 <KyleMaas_Laptop> Anyway, I should probably get going.
Jan 20 17:45:25 <Tofe> KyleMaas1: good work :)
Jan 20 17:49:44 <Tofe> KyleMaas1: do you know how it could have worked on Legacy ? it looks like the center of the pinch was quite wrong
Jan 20 18:12:25 <Herrie> Tofe: Checked PR doesn't work on legacy
Jan 20 18:12:51 <Herrie> Need to test code without PR on legacy but recall it worked
Jan 20 18:14:25 <Herrie> Quite sure we'll still need the webkit prefix there
Jan 20 18:16:59 <Tofe> Herrie: yes, Chromium should work with the prefix too, I think; but we can work out a condition like the one for Firefox
Jan 20 18:29:22 * HaDAk sighs
Jan 20 18:29:40 <HaDAk> yesterday i find out that both my job is at risk and my rent is increasing 50% in a month.
Jan 20 18:29:45 <HaDAk> i just can't get a break.
Jan 20 18:52:57 <Herrie> HaDAk: The more reason to emigrate :P ?
Jan 20 18:53:10 <Herrie> Ah wait the emigration was related to the job?
Jan 20 18:53:48 <HaDAk> custody
Jan 20 18:53:52 <HaDAk> if i had that, i'd leave today
Jan 20 19:07:05 <Herrie|Laptop> HaDAk: Hmmz :(
Jan 20 19:07:13 <Herrie|Laptop> Tofe: Managed to source a SIM?
Jan 20 21:10:24 <KyleMaas_Laptop> Herrie: Just pushed an update to that pull request.  Mind testing that on legacy to see if it works any better?  I don't have access to a legacy device.
Jan 20 21:12:28 <Herrie> KyleMaas_Laptop: Thnx let me give that a go in a minute
Jan 20 21:13:13 <Herrie> Still need to test it on a LuneOS device too :P
Jan 20 21:14:00 <KyleMaas_Laptop> Main reason it's needed is that the events being fed to the gesture handlers no longer contain centerX/centerY properties.
Jan 20 21:14:28 <KyleMaas_Laptop> Guessing it was removed from WebKit at some point in time between when Maps was written and now.
Jan 20 21:15:36 <Herrie> KyleMaas_Laptop: Yeah could be
Jan 20 21:15:43 <Herrie> It's been 4-5 years of evolution
Jan 20 21:15:56 <Herrie> But when we don't need to break legacy I prefer to keep it working ;)
Jan 20 21:24:04 <Herrie> KyleMaas_Laptop: It seems it scales (zooms) the whole app, not just the map on LuneOS
Jan 20 21:31:26 <KyleMaas_Laptop> Herrie: Well, let's try that same viewport setting I used for desktop, then.  Maybe that's a feature they included in WebKit itself rather than just Chrome.
Jan 20 21:31:40 <KyleMaas_Laptop> (I don't have a great way to test it in LuneOS just yet.)
Jan 20 21:32:50 <KyleMaas_Laptop> Herrie: Mind trying that?
Jan 20 21:33:47 <KyleMaas_Laptop> (I'll get a proper dev environment set up eventually.  Currently on a metered connection - not a great spot to try to download a new VM image.)
Jan 20 21:37:19 <Herrie|Laptop> KyleMaas_Laptop: Legacy seems to behave now
Jan 20 21:37:23 <Herrie|Laptop> Let me try LuneOS
Jan 20 21:37:31 <Herrie|Laptop> With the viewport stuff
Jan 20 21:37:48 <KyleMaas_Laptop> Excellent.
Jan 20 21:39:44 <Herrie> Seems Google Location API was broken on legacy not too long ago
Jan 20 21:39:45 <Tofe> Herrie|Laptop: yes, the viewport stuff is really needed for WebEngine/Chromium
Jan 20 21:40:06 <Tofe> Herrie|Laptop: and no, I don't have a SIM yet, I guess it should arrive tomorrow
Jan 20 21:40:20 <Herrie> Tofe: We have <meta name="viewport" content="initial-scale=1.0, minimum-scale=1.0, maximum-scale=2.0, user-scalable=yes, width=device-width, height=device-height" />
Jan 20 21:40:21 <Tofe> I wonder why I didn't simply buy one on the street
Jan 20 21:40:35 <Herrie> I'll change it to user-scalable=no
Jan 20 21:40:39 <Herrie> Tofe: That's what I did :P
Jan 20 21:40:46 <KyleMaas_Laptop> Herrie: I changed that in the latest version of Maps to user-scalable=no.
Jan 20 21:40:47 <Tofe> user-scalable=yes is a nonsense for LuneOS
Jan 20 21:40:52 <Tofe> (for any app)
Jan 20 21:40:56 <KyleMaas_Laptop> Also changed maximum-scale=1.0.
Jan 20 21:41:15 <Herrie> OK
Jan 20 21:41:18 <Herrie> Let me try
Jan 20 21:41:45 <KyleMaas_Laptop> Herrie: That's already in that latest commit (the one I think you tested on legacy).
Jan 20 21:41:48 <Herrie> Tofe: I just collected a bunch
Jan 20 21:42:08 <Herrie> KyleMaas_Laptop: Ehm not in index.html ;)
Jan 20 21:42:11 <Herrie> Maybe in debug.html
Jan 20 21:42:17 <Tofe> oops :)
Jan 20 21:42:19 <KyleMaas_Laptop> Update, then.  It should be in both.
Jan 20 21:42:39 <KyleMaas_Laptop> Yeah: https://github.com/KyleMaas/org.webosports.app.maps/commit/400c05063d8b0e1789dd56e40ef86794e1398215
Jan 20 21:43:19 <Tofe> yup, that should work
Jan 20 21:43:34 <Herrie> Yeah that seems better
Jan 20 21:44:15 <Herrie> Just need to see what that does on Legacy
Jan 20 21:44:40 <KyleMaas_Laptop> I'll note, again, that in a combined pan-and-zoom operation, the resulting pan after the gesture completes is wrong.  But I'm pretty sure that's due to faulty math that I'm going to need to correct, which is why I separated it out into another bug.
Jan 20 21:45:28 <Herrie> If I put maximum-scale to 2.0 it seems to work OK still
Jan 20 21:45:32 <KyleMaas_Laptop> Figured it's better to send in a partial fix and fix panning if I get time (or someone else does) than to stall out the whole thing on my sporadic time schedule.
Jan 20 21:45:34 <Tofe> KyleMaas_Laptop: yes, that's a good way to converge
Jan 20 21:45:38 <Herrie> Not sure we really need that change
Jan 20 21:45:48 <Tofe> Herrie: I would take the change
Jan 20 21:46:02 <Herrie> Need to see what it does on legacy
Jan 20 21:46:04 <Tofe> Herrie: just because it's cleaner to have max=max=1
Jan 20 21:46:06 <Herrie> Let me test that
Jan 20 21:46:16 <Tofe> max=min
Jan 20 21:46:35 <KyleMaas_Laptop> It shouldn't make much difference.  I just think it's cleaner.
Jan 20 21:46:47 <Tofe> Herrie: Legacy ignores viewport, I don't think it will have a lot of impact :p
Jan 20 21:47:12 <Tofe> But good to check anyway
Jan 20 21:47:17 <KyleMaas_Laptop> Heck, as long as user-scalable=no, we probably don't need min and max at all, but that'd need some testing on multiple devices.
Jan 20 21:48:01 <Tofe> KyleMaas_Laptop: I prefer have at least one of the two, just to be sure it takes 1.0 as default zoom value
Jan 20 21:48:49 <Tofe> But none should be needed, theoretically. Though we know how touchy reality can be when confronted to theory...
Jan 20 21:50:05 * KyleMaas_Laptop nods
Jan 20 21:50:05 <Herrie|Laptop> Tofe: It seems OK on legacy
Jan 20 21:50:11 <Herrie|Laptop> Let me merge this
Jan 20 21:51:50 <KyleMaas_Laptop> Awesome.  So, then, this can be closed?  http://issues.webos-ports.org/issues/957
Jan 20 21:52:45 <Tofe> We can close it and open one on the issue with pan tracking
Jan 20 21:52:58 <KyleMaas_Laptop> Tofe: Already opened one for that earlier.
Jan 20 21:53:13 <Tofe> ok, good :) then we can close 957 yes
Jan 20 21:53:31 <Herrie|Laptop> KyleMaas_Laptop: I put it to 100% and resolved now
Jan 20 21:53:39 <Herrie|Laptop> Awaiting new nightly. Once that's tested I'll close it
Jan 20 21:53:48 <KyleMaas_Laptop> Oops.  I closed it.  Sorry.
Jan 20 21:53:54 <Herrie|Laptop> Which is just a formality in general :P
Jan 20 21:54:01 <KyleMaas_Laptop> Go ahead and reopen if you want.
Jan 20 21:54:17 <KyleMaas_Laptop> Tofe: Panning bug: http://issues.webos-ports.org/issues/1043
Jan 20 21:54:33 <Tofe> great
Jan 20 21:54:54 <Herrie|Laptop> Yeah just do it to keep track of things to test in nightly ;)
Jan 20 21:55:28 <KyleMaas_Laptop> Awesome.  First bug fixed.  Be it ever so small, I helped!  :)
Jan 20 21:56:04 <Herrie|Laptop> KyleMaas_Laptop: I think my first PR was an extra . in Just Type ... :P
Jan 20 21:58:01 <KyleMaas_Laptop> Suppose I should probably get going again.  Thanks for the help and testing!  Hopefully I'll be able to get a proper testing environment set up soon.
Jan 20 21:58:37 <Herrie|Laptop> KyleMaas_Laptop: Once Tofe has his SIM, I'm sure we'll be able to make proper calls soon :P
**** ENDING LOGGING AT Thu Jan 21 02:59:59 2016