**** BEGIN LOGGING AT Mon Feb 10 02:59:58 2020 Feb 10 07:42:10 Good morning! Feb 10 07:42:34 windknecht: o/ Feb 10 07:42:50 [08:26] [17:57:22] windknecht: if you read this: I have tissot_images_7.12.19_7.1 and Twrp-recoveryInstaller-3.2.1-2-oreo.zip Feb 10 07:49:15 Here again, had a connection issue Feb 10 07:57:26 @Tofe Did you find out what exact versions you use both for twrp and 7.1.2? Feb 10 08:06:26 I have tissot_images_7.12.19_7.1 and Twrp-recoveryInstaller-3.2.1-2-oreo.zip Feb 10 08:06:52 so it should match N2G47H.7.12.19 for the image Feb 10 08:08:20 Tried this one, but no success. Are you sure you use official TWRP 3.1.1-0? They say official doesn't work, and provided a patched one 3.1.1-1 which works with Nougat. Feb 10 08:09:22 I got that twrp from xdadevelopers to download, but maybe this one is improper for installing Luneos... Feb 10 08:13:14 @Tofe maybe you could somehow send me the twrp image you use, if it's not bothering too much. Big Thank you! Feb 10 08:17:03 @Tofe Maybe to my E-Mail adress: patrick.gollob@protonmail.com Feb 10 08:17:24 Thank you! Feb 10 08:25:22 Oh sorry I missed a line. need new glasses Feb 10 08:26:49 well I'll try! Thank you! Feb 10 08:26:52 Bye! Feb 10 08:48:05 Morning! Feb 10 09:37:37 Hi I flashed now with exactly that versions, latest stable release, but I always get a black screen after rebooting into LuneOs Feb 10 09:37:45 Could you help please? Feb 10 09:38:09 I did a format data and everything Feb 10 09:41:43 mmh do know the 'adb' tool ? Feb 10 09:41:47 +you Feb 10 09:41:51 yes Feb 10 09:42:03 do you see the device with adb ? Feb 10 09:44:13 Damn connection today Feb 10 09:44:29 @Tofe I don't see it in adb Feb 10 09:45:27 note that we install luneos in boot_a, not in boot_b Feb 10 09:45:44 setactive a? Feb 10 09:45:48 so make sure you reboot in the A system Feb 10 09:45:58 either with fastboot or with recovery Feb 10 09:46:05 ok Feb 10 09:46:10 let's try Feb 10 09:47:59 @Tofe now I see it in adb, but no screen Feb 10 09:49:34 ah, but that's already much better Feb 10 09:50:06 @Tofe can I somehow get screen working? Feb 10 09:50:41 it should already be working :) let's see where it booted to Feb 10 09:50:44 can you adb in? Feb 10 09:51:05 adb shell? Feb 10 09:51:08 yes Feb 10 09:51:12 oops one moment, brb Feb 10 09:51:35 @Tofe Shell deployed Feb 10 09:53:52 In Feb 10 10:01:55 @Tofe ? Feb 10 10:02:59 windknecht: Do: journalctl > /media/internal/log.txt Feb 10 10:03:02 Then "exit" Feb 10 10:03:12 Then "adb pull /media/internal/log.txt" Feb 10 10:03:20 Open the log.txt and paste it to paste.ubuntu.com ;) Feb 10 10:04:27 @Herrie it says read only filesystem Feb 10 10:05:36 Hmmz, this one I haven't seen before Feb 10 10:05:46 "/media/internal" shouldn't be read-only Feb 10 10:06:29 Maybe I'll try flashing a nightly, switch slot to A there, maybe it at least shows screen Feb 10 10:08:00 @Herrie what you mean? Feb 10 10:09:21 I think the problem was we booted to B first and things messed up. I will do a clean install again, switch properly to A before booting and let's see. Feb 10 10:09:48 Tell you later what was going on, need that cable now... Feb 10 10:09:52 Thank you! Feb 10 10:29:46 Herrie: there should be a file at the root of the data folder that tells halium to mount it as rw Feb 10 11:51:05 Tofe: Yeah I've never seen it as read-only before Feb 10 13:11:54 Herrie: new attemps at fixing scaling: https://github.com/webOS-ports/luna-webappmanager/pull/81 Feb 10 13:11:59 attempt* Feb 10 13:12:24 it fixes the poweroff alert dashboard, but breaks Messaging UI Feb 10 13:13:24 The rest looks ok, so I guess we should try to fix Messaging, or the Enyo component that doesn't handle scaling correctly Feb 10 13:13:40 Tofe: is this scaling fix worth trying on Qt 5.15 first use issue? Feb 10 13:14:08 JaMa: not at all, no... First Use is QML, and I only changed the webapps Feb 10 13:14:47 JaMa: also, I never could start the last testing qemu build -- but I reused a previous machine, so maybe that's the problem Feb 10 13:16:39 but I'm not sure to see what "the scalling issue of First use is still reproducible " means graphically speaking Feb 10 13:17:15 if you ever get to screenshot it, I'll be glad to have a look Feb 10 13:17:58 Tofe: Well Messaging might be Enyo issue. I assume you mean the org.webosports variant, not the legacy one right? Feb 10 13:28:49 Tofe: https://ibb.co/WyvwtVd Feb 10 13:28:51 right Feb 10 13:31:11 JaMa: it's just the "Next" button that is absent ? or is there also a scaling issue ? Feb 10 13:31:44 Tofe: the continue button is outside the screen, if I maximize the VBox window then it will render the same part in the middle, but if I reboot it as well with the window maximized, then the scren gets resized to that size and then FirstUse is rendered in left upper corner, but the screen is big enough to show "continue" button Feb 10 13:35:58 Tofe: scaling issue of the whole app, in both cases (regular testing build from jenkins and local 5.15 build) the VBox window gets resized to 800 x 600 during boot, but with 5.15 the rendered app doesn't fit in Feb 10 13:36:44 with the maximized VBox, the screen is 3440 x 1347, let me measure how big the first-use size is Feb 10 13:37:54 with 5.15 the first-use is 1024 x 768 Feb 10 13:38:57 that's peculiar... we're not even in hidpi there Feb 10 13:40:09 so I'd say we have 1024x768 quite hardcoded (like in luna-platform.conf or something) but it's a smaller output screen than expected Feb 10 13:40:42 JaMa: vbox shouldn't resize to 800x600 in the first place, isn't it Feb 10 13:41:42 do we still use meta-luneos/recipes-webos/luna-sysmgr-conf/luna-sysmgr-conf/desktop/luna-platform.conf somewhere? This one defines 1024x768 Feb 10 13:42:13 qemux86 config doesn't set DisplayWidth/DisplayHeight at all Feb 10 13:42:35 it's read by LunaSettings, which is used a bit, yes -- though I'm not sure exactly if it's used by our compositor Feb 10 13:43:17 I wonder what should resize vbox, with uvesafb we had it in kernel params, but not sure how it's now Feb 10 13:43:33 I'll check the file in the image Feb 10 13:44:39 /etc/palm/luna-platform.conf is the file from qemux86-64 directory (not desktop one) Feb 10 13:47:19 adding DisplayWidth=800 Feb 10 13:47:20 DisplayHeight=600 Feb 10 13:47:31 resizes the FirstUse correctly Feb 10 13:48:46 so either we need to change VBox to use bigger window by default, or add DisplayWidth/DisplayHeight in meta-luneos/recipes-webos/luna-sysmgr-conf/luna-sysmgr-conf/qemux86*/luna-platform.conf or find out what changed in Qt that now it uses 1024x768 instead of 800x600 as it did before Feb 10 14:00:23 800x600 might be just the default for VBox, after first boot it gets stored in GUI/LastGuestSizeHint and GUI/LastNormalWindowPosition https://paste.ubuntu.com/p/zTmV6sGZqN/ which aren't included in ovf files we have in meta-webos-ports Feb 10 14:03:57 JaMa: I thought we specified 1024x768 in our boot options for qemu ? Feb 10 14:07:38 "git grep 1024" in meta-webos-ports shows only these luna-sysmgr-conf files Feb 10 14:08:22 for uvesafb it was in kernel parameter, vboxvideo seems to be resized based on the VBox window size automatically, but I don't see how to define it from the VM Feb 10 14:09:19 ah yes, it was the UVESA_MODE that I had in mind Feb 10 14:09:53 https://www.virtualbox.org/wiki/Guest_resizing Feb 10 14:10:41 modinfo vboxvideo shows only one param modeset Feb 10 14:15:27 MODULE_PARM_DESC(modeset, "Disable/Enable modesetting") Feb 10 14:17:59 the module seems to set "1024x768" as the preferred mode Feb 10 14:18:05 but 800x600 is also accepted Feb 10 14:18:58 maybe we aren't specifying our preferred resolution clearly enough when initializing luna-next compositor Feb 10 14:21:01 should be related to https://doc.qt.io/qt-5/qwaylandoutput.html#addMode Feb 10 14:22:26 https://github.com/webOS-ports/luna-next/blob/master/plugins/compositor/compositor.cpp#L76 maybe it's a lead: we just take the current output; in case there are multiple possibilities, we don't say which one we prefer Feb 10 14:24:32 and here, https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/main.qml#L45 forces the window size. But maybe, in the previous compositor link I pasted, the size wasn't known yet... Feb 10 14:25:36 https://github.com/webOS-ports/meta-webos-ports/commit/551ea0be261d7460a358c382abb0d3fe9700c00f Feb 10 14:26:23 that'll work too :) Feb 10 14:27:22 checking what the default in luna-sysmgr is when it isn't specified in the .conf file Feb 10 14:29:18 martin@jama:/OE/projects/webos-ports/luna-sysmgr$ git grep DisplayWidth Feb 10 14:29:18 conf/luna.conf:DisplayWidth=1024 Feb 10 14:29:18 martin@jama:/OE/projects/webos-ports/luna-sysmgr$ git grep DisplayHeight Feb 10 14:29:18 conf/luna.conf:DisplayHeight=768 Feb 10 14:29:29 ok Feb 10 14:31:50 so it looks like it started to work correctly? if compositor started 800x600 because of screen size, then the window size was set to 1024x768 from luna-sysmgr-conf Settings Feb 10 14:43:18 @Tofe @Herrie Thank you again for your help this morning. I tried journalctl later, it displayed errors from the very beginning till the end : ( I'm sorry, but I need that device to be at least as reliable as 'stable build' suggests. But thank you a lot for your work! Feb 10 14:44:33 Other question: Could you tell me where to obtain images for the Pinephone? I will get me this one for using it with LuneOS as soon as it is available. Feb 10 14:47:50 windknecht: for pinephone there are only "testing" images so far, here: http://build.webos-ports.org/luneos-testing/images/pinephone/ Feb 10 14:48:33 It's still very WIP though. No sound, no calls... A bit rough. Feb 10 14:49:50 @Tofe Oh it was I heard somewhere it was the most stable OS for Pinephone. Well probably it is, as all the Pinephone is WIP. Feb 10 14:50:27 But I'll buy the Pinephone anyway : ) Feb 10 14:50:38 Thanks! Feb 10 14:50:42 windknecht: Well some things in journalctl you can ignore really ;) Feb 10 14:50:46 It logs every single thing Feb 10 14:51:11 Pinephone is very much WIP, calls are working on some other OS-es. In general LuneOS itself is pretty stable from the ground up ;) Feb 10 14:51:20 But it's all very much WIP ;) Feb 10 14:51:34 And we're a small team. We don't have the resources a Ubuntu etc have ;) Feb 10 14:51:51 @Herrie Continue that work, it would be fancy to have it stable one day! Feb 10 14:53:01 @Herrie Do you know an OS for Pinephone where calls, messages, and Internet are currently working? Feb 10 14:53:48 @Herrie It's just March will have come soon ; ) Feb 10 14:53:56 I think Mer/SFOS Feb 10 14:54:05 At least going by my Twitter feed Feb 10 14:54:40 @Herrie you know where to get this? Jolla? Feb 10 14:55:54 Not 100% sure, I know this is the dev: https://github.com/neochapay?tab=repositories Feb 10 14:57:53 @Herrie found the Wiki Feb 10 14:58:11 https://wiki.pine64.org/index.php/Project_Don%27t_be_evil#Software_and_OS_Image_Downloads Feb 10 14:58:20 ah, too slow Feb 10 14:59:37 @Tofe perfect! Wiki with images! Feb 10 15:01:20 @I really want to thank you for your kind help! With your permit I will stay around, just to stay up to date... Have a nice evening and go on like this! Feb 10 15:02:49 About evening: Where is your team located at? Europe? I guess something like Eastern Europe? Feb 10 15:07:09 @Herrie @Tofe Well anyway: Good evening and bye! Feb 10 23:50:02 I have followed the steps laid out on https://webos-ports.org/wiki/Install_LuneOS_for_Tenderloin for installing LuneOS on a HP Touchpad. The multi boot menu comes up and I can choose LuneOS but it does nothing after the initial screen. Is this normal for a LuneOS boot? How long should it take to start up? Feb 10 23:51:39 It says booting..... then the screen flashes blue and goes blank. Don't think I missed a step. Feb 10 23:58:01 Is there a log someplace which may tell me what is going on? **** ENDING LOGGING AT Tue Feb 11 02:59:57 2020