**** BEGIN LOGGING AT Mon Aug 06 03:00:00 2018 Aug 06 05:34:16 saidinesh5: You will need to have luneos-components as well Aug 06 05:34:33 https://github.com/webos-ports/luneos-components Aug 06 05:35:07 We basically made a common component called luneos-components which contains reusable bits Aug 06 05:35:38 And dummy compositor ;) https://github.com/webOS-ports/luneos-components/tree/master/test/imports/LunaNext/Compositor Aug 06 07:21:38 Morning Aug 06 08:09:35 novaldex: ping Aug 06 08:11:48 Herrie|Laptop: pong Aug 06 08:11:52 morning! Aug 06 08:12:22 You know what happened to webos-ports.org earlier? Seems it was redirecting to an apache landing page somehow Aug 06 08:12:31 It seems OK now here, but it wasn't a few hrs ago when I checked at home Aug 06 08:12:50 i'm not aware of anything, but I had just read about webos-ports.org being down Aug 06 08:13:02 literally just tried it here & i'm getting the apache landing page too Aug 06 08:13:08 shall investigate! Aug 06 08:13:22 On phone I get apache landing page, office computer now Aug 06 08:13:23 not Aug 06 08:13:26 But could be caching Aug 06 08:14:57 we've had a few DNS problems recently, which i'm not happy with Aug 06 08:15:14 * novaldex really hopes he's not going to see a lot more of them.. Aug 06 08:16:37 Let me do some tracerts Aug 06 08:19:10 okay, DNS is correct, so it must be a mis-cache somewhere else Aug 06 08:20:02 I get bad results here & at home too Aug 06 08:39:41 i've refreshed DNS, hopefully it'll propagate properly & point everyone back to the right server again Aug 06 08:43:29 OK thnx Aug 06 08:43:49 Herrie: ahh interesting.. looking at the components now.. so any plans to move to qtquick controls 2.0? They're super nicer for performance.. or rather qtquickcontrols 1.0 was super bad for performance that i had to reimplement my own in two different jobs to improve start up speed and memory usage Aug 06 08:44:47 saidinesh5: we are already using them Aug 06 08:45:22 if there are still qtquick1 components, that's a mistake Aug 06 08:45:29 Ahh.. i see Aug 06 08:45:38 https://github.com/webOS-ports/luneos-components/blob/master/modules/QtQuick/Controls/Styles/LuneOS/SwitchStyle.qml Aug 06 08:45:56 The styles seemed to be done in 1.. so had to ask Aug 06 08:46:13 ah well, that was our 1.0 styling Aug 06 08:46:24 not used anymore Aug 06 08:46:31 Ahh.. i see Aug 06 08:46:45 2.0 style should be near Aug 06 08:47:06 Dialogs too.. Aug 06 08:47:26 https://github.com/webOS-ports/luneos-components/tree/master/modules/QtQuick/Controls.2/LuneOS Aug 06 08:48:16 Ahh interesting Aug 06 08:48:31 there's a bit of cleanup to do for old 1.0 Aug 06 08:48:32 Yeah the 1.0 were super bad so had to bring it up Aug 06 08:48:47 yep Aug 06 08:50:33 gotta go, I have a castle to visit Aug 06 08:50:39 May be I will refactor out my Dialogs JS api into a reusable plugin sometime next week, so thatshould help you guys ditch dialogs too.. a simple js callback based Dialog api: https://stackoverflow.com/questions/45939425/a-chain-of-modal-dialogs/46081882#46081882 Aug 06 08:50:43 Ah have fun Tofe Aug 06 09:56:39 * JaMa received A1 today, buying usb-c cable to charge it Aug 06 09:57:29 JaMa: there was type c cable in box included Aug 06 09:58:19 my contractors advantage was to receive just the phone without any accessories :) Aug 06 09:58:30 ah Aug 06 09:58:44 but I got 2nd box with more work (and more missing cables) as well Aug 06 09:59:13 :) Aug 06 10:37:53 JaMa: LOL Aug 06 11:42:51 nizovn: Had luck with your A1? Aug 06 11:45:17 well i managed to brick it a bit, not booting to both systems.. Aug 06 12:09:08 Hehe Aug 06 12:15:54 I'll have a go with mine in a bit Aug 06 12:44:28 Mine also seems to bootloop. What I've done so far: 1. Enable Developer mode. 2. Rebooted into fastboot with volume down+power 3. fastboot oem unlock 4. flash stock 7.1.2 image. 5. Boot TWRP with "fastboot boot recovery-3.2.1-1.img". 6. Formatted data to remove encryption. 7. Restarted TWRP with "fastboot boot recovery-3.2.1-1.img". 8. Flashed "luneos-dev-package-tissot.zip" via TWRP advanced, adb sideload. Aug 06 12:44:37 Tofe: ^ Aug 06 12:44:48 For when you're back from your castle visit Aug 06 17:17:24 is there any way to disable encryption? when i format data and reboot, i get "encrypting" screen, and then data is again encrypted Aug 06 17:21:44 nizovn: Hmmmz with me that seems to work OK I guess Aug 06 17:21:51 But I only booted back to TWRP Aug 06 17:21:54 I guess that's the trick Aug 06 17:22:03 Once you go to original bootloader it might re-encrypt Aug 06 17:22:11 I guess we'd need a few pointers from Tofe Aug 06 17:22:37 ok Aug 06 17:32:22 I read that you shouldn't flash TWRP, just boot it Aug 06 17:32:37 Normally you would flash TWRP to recovery partition, however not in this case it seems Aug 06 18:41:41 I believe Tofe is flashing TWRP to the b slot. Aug 06 18:43:27 Herrie: nizovn: After trying to flash luneos, if you adb shell into TWRP, do you have luneos-rootfs.tar.gz and the temporary folder it is untarred to lying around? Aug 06 18:43:40 (In /data) Aug 06 18:46:06 Meaning on the A1, of course. Aug 06 18:48:48 elvispre: Yeah I even have it unpacked in some data/tmp_luneos or something Aug 06 18:51:05 Herrie: Yes, that's what the webos_deploy.sh (inside our zip) does, but it looks like the tar command returns non-zero, so even the deployment does not work properly. Aug 06 18:53:40 I have completed the deployment (mv that folder to /data/luneos, etc.) at the adb shell command line, but that doesn't let me boot either. Aug 06 18:55:18 Well it could be Tofe forgot to push something somewhere Aug 06 18:55:24 I guess he'll chip in at some point :P Aug 06 18:55:36 But maybe he had too much good wine at the chateau :P Aug 06 18:55:49 I think he has solved more than one problem along the way! Aug 06 18:56:12 He did cover a lot already Aug 06 18:56:19 He's allowed a holday :-) Aug 06 19:02:29 For sure :D Aug 06 19:07:16 Herrie: Discovery - recovery-3.1.1-1.img deploys into data properly where recovery-3.2.1-1.img behaves as described above. Aug 06 19:08:46 ...and I have a booting A1. I am looking at First Use. Aug 06 19:09:25 Man, these TWRP recoveries are so random! Aug 06 19:11:01 Right enough, recovery-3.1.1-1.img is the one Tofe pointed me at when I was trying a really recent one. Aug 06 19:11:02 elvispre: Hmmz that's good to know :) Aug 06 19:12:01 Touch works. It reveals that First Use is unstable :-) Aug 06 19:12:52 adb is not working. But Tofe says it is but not the daemon. Does he start it from a terminal, I wonder? Aug 06 19:14:33 Uh oh! No wifi but a TXT from my SIM provider. My A1 is probably already spending my money. Aug 06 19:15:12 Anyway, the take home is - try flashing with recovery-3.1.1-1.img and you are probably winning. Aug 06 19:18:46 Well that was a good start to the evening, but now I have a few other things to do. Back later! Aug 06 19:22:48 Same here... Well the FirstUse crashing I had on Mido too. That's LunaSysService probably Aug 06 19:33:47 Novaldex: FYI The webOS Internals wiki is also down, so it may be a problem common to both sites... You have an email that had to go to the back up address. And due to the spamming, I had to get a lesson in IRC before I could reconnect! Aug 06 19:52:52 elvispre: interesting Aug 06 19:53:32 btw if you switch to the other slot, does android boot? Aug 06 20:04:57 nizovn: No. Bootloop on slot b. Aug 06 20:05:38 ok, thanks Aug 06 20:05:52 Worth trying a few experiments with that though. Aug 06 20:07:18 Herrie: First Use succeeded after a few attempts. Aug 06 20:07:58 Herrie: Do we build the A1 kernel with Tofe's latest defconfig? https://bpaste.net/show/9be0184fbfdd Aug 06 20:08:22 Wondering if that's why there's no adb. Aug 06 20:21:54 (Looks like we have that defconfig already.) Aug 06 20:24:47 elvispre: Ehm no.... Aug 06 20:25:15 WE need to update meta-smartphone for that Aug 06 20:25:21 I wanted to ask Tofe but forgot Aug 06 20:25:36 Seems JaMa is not around anymore, so he cannot merge it anywya Aug 06 20:25:41 I can PR it though Aug 06 20:26:26 The last two commits on your tissot kernel both replace the defconfig and at least one of them is from Tofe and says it is for adb? Aug 06 20:27:15 https://github.com/shr-distribution/meta-smartphone/pull/74 Aug 06 20:27:18 That should fix it Aug 06 20:27:27 It's good to do these things right away so they don't get forgotten :P Aug 06 20:27:49 Absolutely. I'll try it locally as I am impatient :-) Aug 06 20:28:26 Yeah LOL Aug 06 20:30:29 Oh, we're still point at e9c763e. Surprising it boots at all! Aug 06 20:48:32 Awesome! adb shell is available if we build with Herrie's latest kernel https://github.com/Herrie82/tissot/commits/tissot-o-oss commit 12c74e2 Aug 06 20:52:13 If you check the log, you'll probably see lunasysservice crashing on firstuse ;) Aug 06 20:52:16 That's what i expect Aug 06 20:52:22 That's what we had before on Mido as ewll Aug 06 20:52:32 It's a bit random, but in like 80% of cases Aug 06 20:53:39 I am taking my first look right now. It is a huge log file so it will take some reading. #niceproblemtohave Aug 06 21:03:33 Found one - "luna-sysservice.service: Main process exited, code=dumped, status=6/ABRT" Aug 06 21:13:01 YUp Aug 06 21:13:12 I remember I did a debug on that a while ago Aug 06 21:13:19 Was some weird low level code issue **** ENDING LOGGING AT Tue Aug 07 03:00:00 2018