**** BEGIN LOGGING AT Wed Aug 23 03:00:01 2017 Aug 23 08:36:00 Morning! Aug 23 08:38:00 Morning! Aug 23 08:38:55 bshah, Herrie|Pre3: I just tried N5 with a Halium 5.1 build: it works :) (wiki, sound & graphics at least) Aug 23 08:39:12 s/wiki/wifi/ Aug 23 08:39:24 yay Aug 23 08:39:47 Tofe: Oooh nice! Aug 23 08:39:48 no init.rc change, I used our kernel and your device tree + muppets Aug 23 08:39:51 How is the backlight? Aug 23 08:40:02 When screen is off :P Aug 23 08:40:02 Herrie|Pre3: I didn't try yet :p Aug 23 08:40:19 still on; but that on our side, no surprise here Aug 23 08:41:48 Tofe: Yeah. Seems that the Ubuntu fix or similar might work. I.e. put brightness to 0 before powering off and restoring brightness when turning on (at least that's what I understood). We should have the brightness stored and accessible via ls2 anyway Aug 23 08:42:15 Tofe: yeah well. android is crap weird Aug 23 08:42:27 you need to put brightness to 0 to turn it off Aug 23 08:42:37 just "blank" is not enough Aug 23 08:42:49 let me try that by hand, just to check Aug 23 08:42:54 when we discovered that.. first reaction was WTF Aug 23 08:43:10 echo 0 > /sys/class/leds/lcd-backlight/brightness Aug 23 08:43:21 and to restore .. Aug 23 08:43:24 echo 200 > /sys/class/leds/lcd-backlight/brightness Aug 23 08:44:05 mmh it still on, in our case Aug 23 08:44:16 I think we may have missed a step here Aug 23 08:44:42 Tofe: does brightness actually gets changed? Aug 23 08:44:45 yes Aug 23 08:44:54 mm Aug 23 08:45:14 could be our code to blank is faulty Aug 23 08:45:26 Tofe: you are using hwc->blank right? Aug 23 08:45:31 I think so Aug 23 08:45:38 let me find it again Aug 23 08:45:41 should work (tm) Aug 23 08:45:42 bshah: Nasty! Aug 23 08:45:55 Tofe: try #2 Aug 23 08:46:00 don't blank device Aug 23 08:46:06 but just set brightness to 0 Aug 23 08:46:35 ah, that works Aug 23 08:46:44 WTF, as you said... Aug 23 08:46:51 :P Aug 23 08:47:15 your blank code sounds suspicious Aug 23 08:47:32 ... and useless Aug 23 08:48:13 there, there Aug 23 09:07:57 Herrie|2: the N5 display turns off if we go through the Dim state first Aug 23 10:03:54 Tofe: OK :) Aug 23 10:04:22 Herrie|Pre3: I thnk I've found the culprit in DisplayManager Aug 23 10:04:27 let me try a little fix Aug 23 10:04:38 Tofe: OK :) Aug 23 10:06:50 Tofe: The issue is only on N5 it seems, but a fix would be nice :) Aug 23 10:07:56 yup, it works Aug 23 10:09:36 https://github.com/webOS-ports/luna-sysmgr/pull/35 Aug 23 10:16:46 Tofe: Will review in a bit. Aug 23 10:18:03 Tofe: note from a bore: i don't like hwcomposer specific behavior as displaymanager is general Aug 23 10:18:21 Tofe: am i right that displayOffCallback will be executed twice if wasDisplayOnBefore=true? Aug 23 10:18:56 nizovn: mmh that's true, I should have set the callback to NULL Aug 23 10:23:16 fixed Aug 23 10:25:56 May I also introduce the shortening of the powermenu timeout ? let's say 1.5s ? Aug 23 10:27:19 I can put it on the same PR Aug 23 10:27:26 It's currently 4-5s? Aug 23 10:27:32 3s Aug 23 10:27:39 but feels 4 :) Aug 23 10:27:42 OK seems longer on Pre 3 Aug 23 10:28:03 But could be they reduced already on TP :P Aug 23 10:28:24 1.5 seems OK to me. Aug 23 10:28:30 it comes from here https://github.com/webOS-ports/luna-sysmgr/blob/webOS-ports/master/Src/base/DisplayManager.cpp#L188 Aug 23 10:28:32 nizovn: ^ Aug 23 10:29:28 yes, i'm ok with it :) Aug 23 10:29:46 ok, I've put it in the same PR Aug 23 10:30:20 easy to rollback anyway Aug 23 10:34:16 Tofe: I also noticed that power menu is not on right position on my N5 Aug 23 10:34:29 i.e. Bottom item doesn't show Aug 23 10:37:11 Herrie|Pre3: yes, it's an issue with the height not being set correctly, I don't know yet where it gets lost Aug 23 10:45:50 bshah: for Halium, do I still need to mount /persist and /firmware ? I don't see how it could work without that Aug 23 10:46:25 Tofe: yes, you'd need to mount them and also bind them in container Aug 23 10:47:01 ok, yes that's already done Aug 23 10:49:00 Tofe: Also in LNC I noticed that on N5 on lockscreen the launcher icons + lock are visible while it should be only lock. I think it might be N5 specific and related to the issue that PR fixes? Aug 23 10:49:34 Also when in First Use and screen goes off we don't get padlock when turning screen back on. Aug 23 10:51:08 Which seems to be on all targets. Seems to be related to condition when PadLock should show. Aug 23 11:09:36 Tofe: I think I'm 95+ % done with the 5.9 migration. Just one bit of the GYP->GN I'm not sure of yet Aug 23 11:14:46 great :) Aug 23 11:18:27 Tofe: Trying a build now with updated Chromium patch for our integration but might need a little help with remaining 5% Aug 23 11:18:39 Since it's c++ specific bits with libs etc it seems Aug 23 11:21:42 Will have some more detailed look myself first to see if I can figure it out... If not I'll reach out Aug 23 11:23:10 Btw, since you guys talk about qtwebengine.. you guys ever hit something like this? https://bugreports.qt.io/browse/QTBUG-62673 Aug 23 11:27:04 bshah: Nope doesn't ring a bell Aug 23 11:27:21 hm ok Aug 23 11:28:34 But Tofe has done a lot more qtwebengine Aug 23 11:29:00 JaMa does a lot of the cross compilation stuff and maintains meta-qt5 for us. He might have some ideas... Aug 23 11:29:10 JaMa: ^ Aug 23 13:09:24 Herrie|Pre3: github wowes again :/ Aug 23 13:09:25 Connecting to raw.githubusercontent.com|151.101.112.133|:443... connected. Aug 23 13:09:25 HTTP request sent, awaiting response... 500 Internal Server Error Aug 23 13:09:25 2017-08-23 15:10:50 ERROR 500: Internal Server Error. Aug 23 13:09:40 14:40 CESTWe're investigating reports of problems fetching raw and release content. Aug 23 13:10:55 JaMa : hmmz... Aug 23 13:11:15 Well the Mer GitLab doesn't allow us to send MR's for certain repo's :P Aug 23 13:11:25 But that's a GitLab bug it seems :P Aug 23 13:14:30 bshah: nope, never seen this. But it does look like an issue with gcc or stdlib; knowing the gcc version used for that build would make sense... Aug 23 13:19:50 bshah: looks like a difficult area: https://bugs.chromium.org/p/chromium/issues/detail?id=539781 (not really the same issue, but we can see there is a struggle...) Aug 23 13:38:29 why cannot use mouse on virtualbox? Aug 23 13:39:15 is it a bug? Aug 23 13:40:05 Guest77263: Yes bug since latest release: We're looking into it Aug 23 13:40:20 Might be solved with our upgrade to qt 5.9 we're now working on Aug 23 19:12:05 Tofe: Backlight is fixed on N5 :D Aug 23 19:32:48 :) Aug 23 19:41:06 I think I've reached as much as I can do for QT 5.9 ;) Aug 23 19:46:34 Seems to get quite into c++ bits now :P Aug 23 19:47:59 One critical bit left it seems: https://github.com/webOS-ports/meta-webos-ports/blob/herrie/qt59/meta-luneui/recipes-qt/qt5/qtwebengine/chromium/0001-Add-PalmServiceBridge-to-WebEngine.patch#L134 Aug 23 19:48:11 And maybe some cleanup here and there for other bits Aug 23 19:48:33 luna-webappmanager will need some work for the headers it seems Aug 23 21:19:45 Herrie: ok, if I can help please ask - I'll try my best. Though you probably know more about gyp and gn than me ! Aug 23 22:28:46 Great to read about the progress with QT 5.9 ! :) **** ENDING LOGGING AT Thu Aug 24 03:00:00 2017