**** BEGIN LOGGING AT Fri Oct 16 02:59:58 2015 Oct 16 05:17:35 Hey, is there an easy way to put a device under heavy processor load, to test how sluggish that makes the UI? Oct 16 05:21:29 DougReeder: we would have to start several heavy cpu things, to occupy all the CPU threads Oct 16 05:22:01 maybe a multithreaded compression thingy ? Oct 16 05:22:47 like, gzip < /dev/random > /dev/null , two times Oct 16 05:33:11 Herrie: I'm a bit surprised, because these variables are the ones that should be set in /etc/luna-next/environment.conf Oct 16 05:40:31 Tofe: Well maybe they aren't somehow Oct 16 05:40:35 I got the UI up ;) Oct 16 05:40:45 So that's already quite some progress right? Oct 16 05:40:57 yes, that's even very good Oct 16 05:41:19 now we just have to see why luna-next started from systemd doesn't have the correct environment Oct 16 05:41:49 Let me check etc/luna-next/environment.conf Oct 16 05:43:07 Tofe: https://bpaste.net/show/3d675d074c03 Oct 16 05:43:40 change eglfs to hwcomposer, and start luna-next via systemd? Oct 16 05:44:23 Tofe: Yeah when I change it to hwcomposer I can start luna-next again Oct 16 05:44:31 Let me push a modified file and reboot device Oct 16 05:44:41 ok, then the fix will be straight forward, hopefully ! Oct 16 05:44:53 gotta go to work now :D Oct 16 05:45:52 Booting now Oct 16 05:48:45 OK UI is up now :D Oct 16 05:48:49 Just no touch still Oct 16 07:18:35 Herrie: looks like the luna-next options isn't correct either: it should be LUNA_NEXT_OPTIONS=-plugin evdevtouch:/dev/input/event2 -plugin evdevkeyboard Oct 16 07:18:40 (from mako) Oct 16 07:18:59 maybe it's not event2 but event3, but you see the issue Oct 16 07:23:10 Herrie: the luna-next-conf recipe seems incomplete for gnexus Oct 16 07:28:00 I don't understand how this recipe works... Oct 16 07:32:41 Tofe: thnx for pointers. I'll dig a bit to see where this comes from Oct 16 07:33:13 This image hasn't been maintained forever (1 year +) so I'm surprised how little is broken actually :P Oct 16 07:34:00 https://github.com/webOS-ports/meta-webos-ports/compare/fido...Tofee:fido?expand=1 Oct 16 07:34:20 would that work ? The main doubt is about input/event0 Oct 16 07:34:41 Tofe: not sure :P Oct 16 07:34:47 Let me dig a bit. Oct 16 07:35:13 a quick test is to cat /dev/input/eventX and see which one outputs garbage when touching screen Oct 16 07:36:33 Tofe: Don't have adb here (at least not with N4) will try Nexus Oct 16 07:36:52 It's device dependant anyway Oct 16 07:37:35 Yeah I mean ADB doesn't work on my laptop with N4 Oct 16 07:37:43 Never tried with Nexus doing now Oct 16 07:40:12 Nah also doesn't work with Nexus Oct 16 07:40:41 But fixing it shouldn't be rocket science :P Oct 16 07:40:48 Seems rotation & audio work ;) Oct 16 07:40:56 So that aint bad :) Oct 16 07:45:54 Yes, surprisingly good :) Oct 16 07:46:05 with latest build ? Oct 16 07:46:15 Yeah :) Oct 16 07:46:19 Great Oct 16 07:46:28 Yup Oct 16 07:46:45 Seems one of LG guys got LuneOS running a bit on Raspberry Pi :) Oct 16 07:46:55 He put some pics on Twitter Oct 16 07:46:59 Invited him here Oct 16 07:47:05 Maybe we can have a build Oct 16 07:47:12 It's a nice entry level device Oct 16 07:47:30 Hey, I just remarked that we don't have the line "QT_QPA_EGLFS_HAS_ALPHACHANNEL=1" in the grouper of maguro... Could that explain the black keyboard window? Oct 16 07:48:07 Could be, I'm not sure what these do :P Oct 16 07:50:21 Ok with intermittedly working adb managed to push a new environment.conf, now booting Oct 16 07:54:53 event0 didn't work Oct 16 07:55:00 Trying event1 now Oct 16 07:56:04 Event1 it is! Oct 16 07:57:37 Can you modify & PR? Oct 16 07:57:43 Sim & wifi seem to work too Oct 16 08:02:24 Tofe: I don't see issues with VKB on nexus except for screen rotation taking a while. I.e. I see white after rotation for a short while before it adjusts content Oct 16 08:03:43 But VKB seems OK. It understandable that it's a bit slower due do dual core Oct 16 08:06:53 Not impressed with the screen on the Nexus. It's not very bright. Even my Veer has a nicer screen :P Oct 16 08:35:25 Tofe: NM fixed the environment.conf already and merged other 2 PR's. Oct 16 08:35:34 Will kick off some new builds Oct 16 08:43:46 Herrie|Veer: oh, I was too slow? Oct 16 08:46:42 ah, yes, I was :D Oct 16 09:02:39 Tofe: Yes but builds are running with everything Oct 16 09:02:52 You said 5.5.1 caused the issues? Oct 16 09:11:38 5.5.1 causes a crash when app tries to show up Oct 16 09:15:06 I'll have to look at commits between 5.5.0 and 5.5.1 to find some hints, because it isn't obvious Oct 16 09:15:38 Tofe: Hmmmz Oct 16 09:15:50 morphis: Maguro is back working :) Oct 16 09:15:59 Herrie|Veer: yeah!! Oct 16 09:16:08 I'll try to maintain it going forward but might need some help here and there :P Oct 16 09:16:19 what was the problem? Oct 16 09:16:23 Was a few lines to fix :) Oct 16 09:16:38 We were missing the environment.conf for luna-next ;) Oct 16 09:16:48 So it couldn't launch luna-next Oct 16 09:17:32 For the rest all seems OK :) Audio works though it crackles with higher volume. Could be my speaker is broken, not sure Oct 16 09:18:00 Rotation, touch, wifi, ofono, 3G, brightness all seem to work :) Oct 16 09:49:07 morphis: Seems one of the LG guys got LuneOS more or less up & running on the Raspberry Pi 2 as well :) Might be interesting to get a proper build for that. Trying to get him in here and participate ;) Oct 16 09:54:08 Herrie|Veer: really? Oct 16 09:54:09 where? Oct 16 09:54:32 Herrie|Veer: that is pretty nice for maguro Oct 16 09:55:47 morphis: Twitter @Andolamin Oct 16 09:56:02 He doesn't have touch working yet but gave him some pointers Oct 16 09:56:28 morphis: Yeah surprised to see how little broke in > 1 year :P Oct 16 09:56:30 interesting Oct 16 09:58:39 morphis: Yeah not sure to what extend he used OpenEmbedded etc so curious to find out. RP2 would be a nice target to attract some more devs :P Oct 16 10:17:08 Tofe: Just something odd I noticed. Font in settings app is "wrong" for Maguro while it's OK for Mako. Is there something we need to set elsewhere device specific for the fonts for QT? Oct 16 10:53:29 Herrie|Veer: for the fonts ? Not that I know of Oct 16 11:52:43 Tofe: I'll check a bit more with new nightly tonight on both devices. Just font used in Settings is not Prelude on Nexus somehow. It seems OK elsewhere (LNC etc). Oct 16 13:06:35 Tofe: http://tinypic.com/2/102la10/8 this is what I mean Oct 16 13:06:46 Looks like some Times New Roman or something :P Oct 16 13:34:01 JaMa: morning Oct 16 13:34:11 morning Oct 16 13:34:37 In case you have a Samsung Galaxy Nexus laying around: The image is working again :P Oct 16 13:35:30 So I enabled the builds for it again :) Oct 16 13:35:48 At least in testing. You might want to have a look for unstable Oct 16 13:36:07 You'd need to pick the luna-next configuration changes for maguro from fido Oct 16 13:39:46 cool Oct 16 13:39:49 thx Oct 16 13:45:26 iscgar: morning Oct 16 14:02:27 Herrie|Veer: morning Oct 16 14:03:29 JaMa: I think our qtwebengine-chromium is not based on the correct commit of corresponding upstream 5.5.1 Oct 16 14:03:51 iscgar: Any luck with your build? Oct 16 14:04:23 Hey Herrie when nice to see mako running! when your ready to work on doc for porting let me know i got two toro devices Oct 16 14:07:32 Herrie|Veer: unfortunately no. I had to initiate a rebuild after my environment got messed up, but changing SRC_URI of qtwayland_git to make it point to my repo didn't actually do anything. Not sure what I'm missing. Oct 16 14:15:46 Tofe: it's based on commit used by meta-qt5 Oct 16 14:16:01 which was selected before final 5.5.1 was tagged Oct 16 14:16:39 I plan to do another upgrade to latest revisions in 5.5 branches, but -ENOTIME Oct 16 14:19:46 JaMa: ok, but then it doesn't include my commits ? Oct 16 14:22:12 cobblemonster: The toro for Verizon? Oct 16 14:22:31 Or the Toro + for Sprint? I always mix them up. Oct 16 14:23:53 Tofe: your commits? it's _based_ on commit used by meta-qt5, but there should be all your commits on top of that Oct 16 14:24:29 OE @ ~/projects/qt-project/qtwebengine $ git log --oneline b5.5..webOS-ports/master Oct 16 14:24:32 ec0a2f7 Fix touch events coordinates when using custom devicePixelRatio Oct 16 14:24:35 a8d6e9d Make properties for some settings for PalmBridgeService management Oct 16 14:24:37 5667b56 Implement Sync IPC messaging through qt.webChannelTransport.sendSync Oct 16 14:24:40 52b3149 WebEngineNewViewRequest: provide the requested URL as a property Oct 16 14:24:43 7a80a57 WebEngineView: provide additionnal features from window.open on the Qt side Oct 16 14:24:46 21f9825 Add PalmSystemBridge feature Oct 16 14:25:03 OE @ ~/projects/qt-project/qtwebengine $ git log --oneline ccb373c4937777ce4af10918f7412c606cbd56ce..b5.5 Oct 16 14:25:06 55c5a15 Generate usable qmake_extras.gypi Oct 16 14:25:08 b7b5fa1 functions.prf: allow build for linux-oe-g++ platform Oct 16 14:25:11 3cdf1ff functions.prf: Make sure we only use the file name to generate it's moc'ed abbreviation Oct 16 14:25:14 f66dceb functions.prf: Don't match QMAKE_EXT_CPP or QMAKE_EXT_H anywhere in path, but at the end Oct 16 14:25:45 JaMa: I mean the commits in the chromium submodule Oct 16 14:26:13 (sorry if I miss somthing obvious, I'm trying to catchup on submodules knowhow :) ) Oct 16 14:27:11 I didn't rebase chromium Oct 16 14:29:42 I've just pushed rebased version to webOS-ports/master-next Oct 16 14:29:49 ah, know I understand, in the bbappend of meta-webos-ports, we explicitely setup the wanted commit Oct 16 14:29:54 now* Oct 16 14:30:20 and pushed TAG=webOS-ports/master-2015-10-16 Oct 16 14:30:47 yes we always do, floating revisions are bad for build reproducibility Oct 16 14:31:10 No, I mean we override the submodule commit that is setup in qtwebengine Oct 16 14:32:19 I was worried because on GH we don't see that, so the submodule still points to something other than webOS-ports/master Oct 16 14:33:12 cobblemonster: Appearantly there are only about a dozen differences between the maguro and torro. I think you might be able to use the maguro LuneOS image on the torro. Question would be how the kernel & ofono react to not having the gsm hardware. What I Oct 16 14:33:12 can see the different files are only related to radio, gps & wifi it seems and verizon APN. Oct 16 14:33:42 cobblemonster: Nothing that should really prevent the image from booting in theory Oct 16 14:36:59 In case it doesn't we can pull the log and work from there to solve the issues. Key is that you have Android 4.2.2 on it. Oct 16 14:39:23 Tofe: ah I see Oct 16 14:39:31 Tofe: in OE we don't use submodules at all Oct 16 14:41:31 JaMa: well, I understand why, I've been trying to update the submodule pointer for 20min now, without success :) Oct 16 14:44:02 hehe Oct 16 14:44:25 it's not so complicated once you get used to it, but it's still annoying to work with Oct 16 14:47:14 :) Oct 16 14:49:31 So Tofe: Next build will have a working browser again :P ? Oct 16 14:51:26 No Oct 16 14:51:56 Sorry, but there is still a crash issue behind this initialization issue Oct 16 14:53:45 ok i will give it a try later Oct 16 14:53:45 Tofe: Ah OK, I thought above might solve this. Oct 16 14:55:39 cobblemonster: Sent you some more info by email :) Oct 16 15:39:53 JaMa: You know if there's some device layer for RaspBerry Pi 2 already? Oct 16 15:42:08 JaMa: Ah seems there's a meta-raspberrypi Oct 16 15:42:22 Not sure that works for the Pi2 too but I guess it does ;) Oct 16 15:46:44 I guess the same, but I'm ignoring whole Pi world Oct 16 15:48:01 JaMa: OK :) Seems one of the LG guys got LuneOS more or less working on his Pi 2 ;) Will try and see if we can do something with that :) Oct 16 15:48:27 Would be nice as a target for attracting some more devs :P Oct 16 20:16:47 Tofe: Seems that Settings on Maguro somehow takes the body css font from Onyx Oct 16 20:16:57 https://github.com/webOS-ports/org.webosports.app.settings/blob/master/lib/onyx/css/onyx.css#L37 Oct 16 20:59:06 :) :) :) I HAVE WORK LUNEOS ON TORO !! Oct 16 20:59:16 Got WIFI Oct 16 20:59:39 Got Sound ( sound like mud tho) Oct 16 21:00:37 stright up margo to toro works Oct 16 21:20:44 Cobblemonster: Nice Oct 16 21:20:50 My sounds is also garbled a bit Oct 16 21:20:58 But only with higher volume levels it seems Oct 16 21:21:03 Do you have signal bars? Oct 16 21:21:24 That would be an indication oFono works properly with ConnMan as well Oct 16 21:24:46 If not Oct 16 21:24:50 Do: adb shell Oct 16 21:24:56 journalctl > /media/internal/log.txt Oct 16 21:25:12 and then: adb pull /media/internal/log.txt and paste it somewhere or email it to me Oct 16 21:25:30 THis is basically the whole system log and will have any errors odd things in there Oct 16 21:25:54 let me put in my sim Oct 16 21:28:08 booting screen rotates Oct 16 21:29:53 oh on on bars :( Oct 16 21:30:21 dial pad came up tho Oct 16 21:31:41 Yeah so probably need some oFono tweaks for that Oct 16 21:31:48 If you can pull a log would be great Oct 16 21:32:58 ok i see if i can get them wich and were Oct 16 21:42:59 C:\Users\johnm>adb pull /media/internal/journalctl.txt remote object '/media/internal/journalctl.txt' does not exist Oct 16 21:43:31 C:\Users\johnm>adb pull /var/log/messages remote object '/var/log/messages' does not exist Oct 16 21:43:57 ok were are they Oct 16 21:44:04 You need to create the file Oct 16 21:44:09 adb shell to login to device Oct 16 21:44:18 Then: journalctl > /media/internal/log.txt Oct 16 21:44:27 then: exit Oct 16 21:44:37 Then adb pull /media/internal/log.txt Oct 16 21:44:51 var/log/messages is gone Oct 16 21:45:40 ok Oct 16 21:46:48 got them hold on Oct 16 21:48:35 try this https://drive.google.com/open?id=0BzMzbC6rPutYNk9iWEdqQXNhNTg Oct 16 21:51:58 Oct 16 17:43:32 maguro ofonod[1220]: connect_rild: Connecting 0x7c1200 to rild... Oct 16 17:43:32 maguro ofonod[1220]: create_ril: can't connect to RILD: Connection refused (111) Oct 16 21:56:21 herrie get it also email it to you Oct 16 22:13:01 I'll have a look in the morning, bedtime here ;) Oct 16 22:17:16 ok Oct 16 22:18:09 i will be gone all day tomorrow **** ENDING LOGGING AT Sat Oct 17 02:59:58 2015