**** BEGIN LOGGING AT Thu Apr 19 03:00:06 2018 Apr 19 06:05:28 Morning! Apr 19 06:14:45 morning Apr 19 06:38:00 Tofe: Herrie: hammerhead, mako, tenderloin were built with Qt 5.9.5 now on jenkins if you want to test it Apr 19 06:38:12 qemu and others still in queue Apr 19 06:38:18 then unstable with Sumo Apr 19 07:10:41 JaMa: great! thanks Apr 19 09:47:43 Herrie: Tofe: I wonder why we don't have Anbox in LuneOS yet :) Apr 19 09:57:01 JaMa: It requires 3.10+ kernel at minimum Apr 19 09:57:09 And our targets all have 3.4 kernel Apr 19 09:57:14 3.18 kernel is even better Apr 19 09:57:28 But with MIdo and some of the other targets in the works it might be an option to try Apr 19 09:57:44 Mido uses 3.18 Apr 19 09:57:57 I see Apr 19 10:45:01 Also I'm not sure how much RAM it uses, but 2GB might be a minimum... We already have our own services, the ones from Halium, and then we start Anbox... and it still needs to load an app :p Apr 19 10:47:42 probably won't fly well on rpi3 then Apr 19 10:48:58 It's still worth a try, it might work Apr 19 10:51:22 yeah, once we get rpi UI working again :) Apr 19 17:29:36 JaMa2nd: I'm flash mako & hammerhead, more news will follow Apr 19 17:31:11 Tofe: My Mako is extremely flaky even with new battery Apr 19 17:31:24 So Hammerhead is my dedicated Android phone for work now :S Apr 19 17:31:35 I think I might have dropped the Mako once too often :P Apr 19 17:32:07 Anyway it's old and battered so well Apr 19 17:32:25 I guess I could still do some LuneOS testing with it but not a whole lot Apr 19 17:37:03 ok ; I've also changed my Mako's battery recently, let's see how this goes Apr 19 17:46:46 Mako isn't a big success... everything seems to start (luna-next etc) but the loading logo stays forever Apr 19 17:46:56 I guess we never reach the "firstboot" state Apr 19 17:47:06 s/Mako/Hammerhead/ sorry Apr 19 17:47:16 Mako is booting right now, we'll see Apr 19 17:51:02 Herrie: do you remember what triggers the state "firstboot" to load the cardshell with firstuse ? I can also look for it, somewhere in lunasysmgr's state machine Apr 19 17:58:33 ok it looks for org.webosports.luna (should be created by luna-next) Apr 19 18:03:51 huh ? "LunaSysService[1273]: [] [pmlog] LunaSysService LS_REQ_NAME {"FILE":"transport.c","LINE":2473} Invalid permissions for com.palm.systemservice" Apr 19 18:05:12 ah, exe path is invalid Apr 19 18:05:30 that might be one of Herrie's commits when integrating webOS OSE Apr 19 18:17:04 looks like we broke a few things lately... Apr 19 18:29:00 Tofe: Well I didn't really merge anything for OSE yet Apr 19 18:29:07 BEsides the class files Apr 19 18:31:01 Unless something made it into the image that shouldn't have Apr 19 18:33:29 Tofe: This is configurator & activitymanager that manage various boot states Apr 19 18:37:05 Tofe: Boot states are in luna-appmgr it seems? https://github.com/webOS-ports/luna-appmanager/blob/14007e05b6d8746f22cf18ce4bda47cdc5e52427/Src/base/BootManager.cpp Apr 19 18:41:52 OSE is in separate branch still Apr 19 18:42:03 Only OSE thing in Pyro is the new classes Apr 19 18:42:10 That shouldn't break anything really Apr 19 18:42:17 Unless some path changed Apr 19 18:56:21 Should be luna-appmanager Apr 19 18:56:27 That's where I fixed stuff previously Apr 19 18:56:35 I.e. https://github.com/webOS-ports/luna-appmanager/commit/abf9257bdff0de0d85edc3119409e2a59223da75 Apr 19 19:48:46 Herrie: no the issue doesn't seem to be in appmanager, it's more that the com.palm.systemservice LS2 json file didn't have the right path for the binary (/usr/bin instead of /usr/sbin for LunaSysMgr iirc) Apr 19 19:50:02 Tofe: Ah this could be due to the classes Apr 19 19:50:05 I had something similar Apr 19 19:50:15 With the new classes it started to push some old files Apr 19 19:53:09 That had the wrong path Apr 19 19:53:18 I ran into this for one of my OSE bits too Apr 19 19:53:22 Forgot which one though Apr 19 19:56:38 ah ok Apr 19 20:06:07 https://github.com/webOS-ports/buildhistory/commit/7a5ff5192858070957cfd0c451b12cc572c116cf images/mako/glibc/luneos-dev-image/files-in-image.txt doesn't show that many changes except manifest files being generated now Apr 19 20:06:16 maybe it was broken in previous build already? Apr 19 20:10:36 JaMa: that's very likely Apr 19 20:11:16 I was also testing Herrie's OSE branch lately so I didn't test the regular testing; maybe we broke something here recently without seeing it Apr 19 20:11:29 I'll try with qemux86 build as I have recent one and it was working fine Apr 19 20:13:14 blah wasn't rsynced yet, so after rpi3-64 build is finished **** ENDING LOGGING AT Fri Apr 20 03:00:01 2018