**** BEGIN LOGGING AT Fri Oct 31 02:59:59 2014 Oct 31 06:07:21 Herrie|2, DougReeder_: merged it Oct 31 07:11:35 morphis: thnx :D Oct 31 07:40:56 morning Oct 31 07:43:20 Herrie|2: no, that wouldn't help, the top-tow issue is that it needs a transparent background and we had issues with that part (iirc) Oct 31 08:16:05 morning Oct 31 08:19:57 morphis: curious about your firstuse password solution, I might want to implement it for browser too because current solution with bg images is nasty :P Oct 31 11:30:48 * JaMa broke his TP Oct 31 11:31:13 doctor doesn't seem to help, any other idea (it keeps rebooting just after hp logo is shown) Oct 31 11:31:30 I cannot even charge it reliably, because of the constant reboots Oct 31 11:39:25 Can you get big USB on screen? Oct 31 11:39:39 Holding the volume up or down? Oct 31 11:42:37 With USB symbol on screen you should be able to charge it properly I think :) Oct 31 12:12:54 I got it to 25% and then restarted doctor which is now stuck :/ Oct 31 12:29:04 looks like I need older doctor 300 Oct 31 12:41:13 JaMa: back from lunch :) 3.0.0 or TPToolbox can sort it for you :) Oct 31 12:41:41 Will rebuild all partitions (TPToolbox that is). 3.0.0 as well afaik :) Oct 31 12:46:52 me trying to find 3.0.0 for att version Oct 31 12:47:13 but maybe better to learn tptoolbox way :) Oct 31 12:54:10 AT&T has 3.0.2 as minimum afaik Oct 31 12:54:39 TpToolbox is the way to go then. Can simply recreate the partitions with it :) Oct 31 12:59:21 done, now trying doctor on top of it Oct 31 12:59:27 thanks for help Oct 31 13:00:16 No pb :) Oct 31 13:00:40 If you could only help us get a working kernel :P Oct 31 13:00:51 LuneOS one boots but wifi doesn't work :P Oct 31 13:01:12 Got a 4G myself too :P Oct 31 13:07:32 heh, it doesn't reboot now, but still stuck showing hp logo :) Oct 31 13:17:02 Be patient :) First boot is slow Oct 31 13:27:51 Good morning Oct 31 13:30:49 morning Oct 31 13:37:06 So I think I'm missing something trying to debug the luna-next-cardshell qml. I've got the LUNA_NEXT_DEBUG=1 set in /etc/luna-next/environment.conf and restarted but I can't seem to get any kind of messages to show up Oct 31 13:37:53 It could be that I just haven't had enough coffee yet this morning too... Oct 31 13:38:51 Hmmz I think that did work for me on my N4 for it to appear in journalctl... Oct 31 13:38:51 Need to check again Oct 31 14:30:04 thrrgilag: it seems to appear rather late Oct 31 14:30:06 no sure why Oct 31 14:30:29 thrrgilag: quick workaround is to do cp /etc/luna-next/environment.conf ~/env.conf Oct 31 14:30:35 prefix every line with a export Oct 31 14:30:43 then . ~/env.conf Oct 31 14:30:47 systemctl stop luna-next Oct 31 14:30:54 luna-next $LUNA_NEXT_OPTIONS Oct 31 14:34:40 yay, thanks morphis! now i can see what i'm screwing up with the system menu :) Oct 31 14:38:29 :) Oct 31 14:38:47 thrrgilag: if you find the problem why the log output turns up so late in the journal feel free to fix it :) Oct 31 14:39:30 propably http://lists.freedesktop.org/archives/systemd-devel/2013-December/015433.html Oct 31 14:40:34 morphis: i'll take a look at that once i'm done hacking on the system menu Oct 31 14:41:30 btw, i've branched from morphis/systemmenu to thrrgilag/systemmenu in my github and rebased on master Oct 31 14:42:13 what's pushed up is just the menu dismiss what tapping outside, i'm working on the mute and rotation lock elements hooked up Oct 31 14:42:52 the dimiss needs the inversemousearea plugin which i submitted the pull request for the other day Oct 31 14:43:35 once i have a more or less behaving system menu i can submit a pull request for that Oct 31 15:00:08 morphis: do you think the logs are filtered out by using systemd, somehow ? Oct 31 15:00:34 I can't see how that could be, but well, there must be a reason Oct 31 16:29:26 I nuked the webos-ports-env directory, rebuilt, and now I see the changes to Enyo-1.0. Oct 31 16:41:03 thrrgilag: We're now in feature freeze for this month's Black Eye release. Once release is out we'll merge it for next month's Black Tie release :) Oct 31 16:41:59 Herrie: ah okay no worries, gives me a little more time to work out the kinks Oct 31 16:43:06 Yeah just a heads up. We have one major release blocker, once that's solved, test images will be made, tested and if OK, release pushed and we'll start working on next months release :) Oct 31 16:46:01 question, is screen rotation supported on the Mako? or is that just something that's on the todo list across the board? Oct 31 16:47:04 On to-do, we'd need to get some of the sensor stuff working for that first Oct 31 16:47:22 gotcha Oct 31 16:47:23 morphis can tell you more about what would be needed for that :P Oct 31 16:57:02 Did the Enyo fix make it into the Black Eye release? Oct 31 17:03:18 DougReeder: Release is not final yet, but I suspect it will, quite trivial fix :P Oct 31 17:03:48 Our not working back swipe needs to be fixed first before final test image before release can be made Oct 31 17:03:57 But should be in there afaik Oct 31 17:04:12 Since we're still building off daisy branch Oct 31 17:04:19 And it's in there now ;) Oct 31 17:15:28 * DougReeder_ nods Oct 31 19:28:09 DougReeder_: it did Oct 31 19:28:27 we're now on the final steps for the release after the back gesture back has fixed Oct 31 19:28:52 Yay! (I tweeted that developers of Enyo 1 apps should test them on LuneOS, and that it’s stable enough for development) Oct 31 19:30:15 yeah Oct 31 19:30:30 release should be there tomorrow Oct 31 19:32:03 JaMa: btw. can you sync dizzy with the latest state from daisy? Oct 31 19:36:05 Tofe: ping Oct 31 19:36:18 morphis: pong Oct 31 19:36:28 Tofe: you still have free time today? Oct 31 19:36:57 I'll have a guest tonight, but she's not here yet; so, shoot :) Oct 31 19:37:07 ok Oct 31 19:37:21 we have to rework luna-next to use the latest qtwayland APIs Oct 31 19:37:28 lipstick already did Oct 31 19:37:29 https://github.com/nemomobile/lipstick Oct 31 19:37:33 ok Oct 31 19:37:34 https://github.com/nemomobile/lipstick/commit/7166047c16224b665fa78bb946537aa5ca4bb402 Oct 31 19:38:01 maybe you can start with it Oct 31 19:38:06 even if you can't test yet Oct 31 19:38:25 I can do that on monday and also continue where you stopped Oct 31 19:39:18 I can start it yes Oct 31 19:39:58 but if the qtwayland-native recipe would be building with daisy, that would help :) Oct 31 19:43:55 :) Oct 31 19:45:37 Tofe: just leave me a note how far you came Oct 31 19:47:05 sure Oct 31 20:27:24 morphis: yes, just a sec Oct 31 20:36:00 morphis: there's already a start on the tofe/qtwayland_latest branch on luna-next Oct 31 22:43:35 hi guys Just got myself a nexus 4 to play around with. Looks like I might have killed it already trying to get CWM on it ........ I think I finally figured out how to get stock factory android image back on after a lot of digging around......... I tried installing the latest stable version of LuneOS with CWM, but it seems to error out ... can anyone help ? Oct 31 23:36:11 ok looks like I cant find anything in the zip file itself ..... Does anyone know what the md5sum or the sha-1 hash of the lune-OS stable image for make should be ? Oct 31 23:39:40 sorry I meant mako Nov 01 00:31:56 k I managed to download the file webos-ports-dev-package-mako-20141001193100-stable-026-56.zip and this time I was able to unzip the contents on this one to see what the contents were . Managed to untar it and saw that it had busybox on it along with bash and a few other bits and bobs. Tried to flash it in ...... the flashing worked out correctly. and I rebooted. Nov 01 00:32:32 got to the initial google screen on the nexus 4 and then bang ...... it rebooted and started doing the same thing. Nov 01 00:32:41 Anything Im missing ? Nov 01 00:33:06 is there any way to extract the kernel logs and see what on earth it is doing ? Nov 01 01:51:41 ichthys , are you sideloading (using ClockworkMod Recovery) the whole zip, or just part of it? Nov 01 02:03:27 The whole zip .... Nov 01 02:03:50 I didnt want to extract anything and make a mess of it. Nov 01 02:06:50 It sounds like you did the right thing. Nov 01 02:07:31 Where does your experience diverge from the instructions? Nov 01 02:08:19 You might try sideloading the Android 4.2.2 ROM using ClockworkMod Revcovery. Nov 01 02:08:47 …to check that ClockworkMod Recovery is working correctly. Nov 01 02:08:54 I was just in the process of doing that..... Just about 5 mins ago realized that the phone I had , had 4.4.4 Nov 01 02:09:18 And saw the wiki entry that said it needs 4.2.2 .. Nov 01 02:09:27 Just flashed in 4.2.2 now .... Nov 01 02:10:10 Easy to get thos numbers confused Nov 01 02:10:13 Thanks for the help again Doug ..... is that still valid , the part about it needing 4.2.2 ? Nov 01 02:11:38 That’s what I was told. Nov 01 02:13:43 I’m for bed. Goodnight, all! Nov 01 02:13:57 Cheers thanks for the suggestion and help Doug Nov 01 02:21:27 ok thats what the issue was ... I started out with android 4.4.4 instead of 4.2.2 ........facepalm ...... teaches me to read and re-read the wiki before doing something silly ...... I would still be interested as to why , it should have this quirk, unless the boot.img for 4.2.2 is somehow different and puts things in different places compared to 4.4.4 **** ENDING LOGGING AT Sat Nov 01 03:00:00 2014