**** BEGIN LOGGING AT Mon Aug 15 02:59:58 2016 Aug 15 07:10:46 morning Aug 15 07:13:48 Herrie|Pre3, morning Aug 15 07:14:20 send me a ssh key so I can get you into the area of your builds so you can manage them. Aug 15 07:14:30 (and clean up old dailies) Aug 15 07:14:49 ka6sox: OK let me sort that tonight :) Aug 15 07:14:59 Herrie|Pre3, sounds good! Aug 15 07:15:03 g'night Aug 15 07:16:48 ka6sox: g'night! Aug 15 09:09:46 Morning! Aug 15 09:10:16 Tofe: morning! Aug 15 09:22:13 Herrie|Pre3: I'm testing an alternative way of enabling password echo Aug 15 09:22:32 Tofe: OK :) Aug 15 09:22:38 We'll see the result in a couple of minutes Aug 15 09:30:30 https://github.com/webOS-ports/qtwebengine/pull/23/files works Aug 15 09:30:41 And is pretty clean Aug 15 09:33:36 I guess it's more future proof then my PR for qtwebengine-chromium :P Aug 15 09:35:39 but you said it didn't work ? Aug 15 09:36:07 Tofe: Did I really? It does work... Aug 15 09:36:41 oh. well, good, because it should :p Aug 15 09:37:25 let's take mine, if you don't mind Aug 15 09:38:39 Tofe: Sure no problem. Both do the same essentially. Aug 15 09:38:53 yup Aug 15 09:39:06 I checked the logs. What didn't work was me trying to fix 1113 Aug 15 09:39:18 The file access issue DougReeder reported Aug 15 09:39:22 we could even set the password echo duration here and drop the corresponding commit in qtwebgine-chromium Aug 15 09:39:39 ah ! yes, ok, I misunderstood Aug 15 09:42:06 Tofe: I think we only changed the Settings.in for enabling the echo. The duration is 1 by default it seems. Aug 15 09:58:27 Ok, then we'll drop that commit at next rebase Aug 15 09:58:49 Will it work without that one? Aug 15 09:59:30 yes, in my commit here we override the default settings from the Qt side Aug 15 10:00:05 OK :) Aug 15 10:00:27 I also updated my FirstUse PR yesterday based on your & nizovn's comments :) Aug 15 10:01:32 looks good Aug 15 10:02:05 I didn't look carefully at nizovn's remarks, do you want to wait for his review? Aug 15 10:02:36 No just my function names for the callbacks were wrong :P Aug 15 10:02:41 Fixed those now. Aug 15 10:09:22 merged Aug 15 10:11:38 thnx Aug 15 16:04:08 so i was curious if the build system would work on the Bash-on-Windows thing.. and it fails instantly, because pyinotify can't work because the apis for watching file system changes aren't implemented. i don't imagine anyone has any ideas if there's some workaround that might be able to get through that? Aug 15 16:05:46 I doubt anyone played with it yet.... Aug 15 16:06:00 Beste bet would be JaMa but he's *nix only afaik :P Aug 15 16:06:40 Herrie|Pre3, I'll be in and out all day today...please send the key when you have time. Aug 15 16:11:28 ka6sox: Will try to find it when home in 30-60 mins Aug 15 16:11:44 Herrie|Pre3, very good Aug 15 17:25:35 ka6sox: Any preference for SSH-2 RSA or SSH-2 DSA and the number of bits in the key? Aug 15 18:14:38 ka6sox: 2048 or we want higher already ? Aug 15 18:19:38 2048 and either one... Aug 15 18:19:46 Herrie, ^^ Aug 15 18:26:21 ka6sox: YGM Aug 15 18:27:27 Herrie, got it...I'm on the road right now but will add it (and send back email of how to access it) in a bit Aug 15 18:28:08 ka6sox: Sure no rush :) Aug 15 18:30:33 Tofe: Looks what I got in the mail today :P http://www.gearbest.com/screwdriver-screwdriver-set/pp_252426.html Aug 15 18:30:40 Should be good for all kinds of repairs :D Aug 15 18:32:16 Herrie: :D Aug 15 18:33:58 Got a Nexus display/mainboard transplant to do ;) And a Go screen to swap and maybe N4 USB port to fix further :P Aug 15 18:37:42 Herrie: I was thinking, how is it going with the N5 port? Aug 15 18:40:27 Tofe: Tbh didn't have much time yet to tinker with that Aug 15 18:40:41 I need to do a lot of legwork first it seems, making sure we have all bits Aug 15 18:41:44 Since they're using CM 12.1 as basis for the N5 port Aug 15 18:41:56 I would need to add the 12.1 branches to all our repos and make the needed changes Aug 15 18:42:10 For which I didn't find time yet... Shouldn't be rocket science, just need time :P Aug 15 18:44:46 I was planning to buy a N5 too, but right now my schedule is already a bit tight, so it would be no use Aug 15 18:45:32 Tofe: Yeah let's focus on getting OS things working first. They should be usable in any target and later worry about porting to additional devices. Aug 15 18:45:43 I might have a look at the RPi though. Aug 15 18:45:54 Could be we need to update gstreamer just Aug 15 18:46:10 Since we're using 1.6.x and upstream seems to use 1.8.x Aug 15 18:46:55 We may have some work to do on the wakelocks, too; I remarked that my N4 woke up here and there when the screen was off Aug 15 18:47:10 I didn't manage to trace it to the source yet Aug 15 18:47:28 Tofe: COuld be some notification? Aug 15 18:47:34 Those should turn on the screen... Aug 15 18:47:39 But could be bug too :P Aug 15 18:48:07 I'm looking into optimizing the notifications bit a bit.... I.e. Making sure we have all proper options for sounds, vibrations, leds and the handling Aug 15 18:48:22 Then hook up led, vibrations a bit more Aug 15 18:48:31 So they work as expected Aug 15 18:49:58 or it could be something stupid, like the battery level changed, and so on Aug 15 18:50:23 I might need a little help with some QML or C++ part of things later on, but will let you know ;) Aug 15 18:50:30 Tofe: Or GSM signal :P Aug 15 18:50:31 of course, no pb Aug 15 18:50:59 Seems that currently we get 2 notification icons instead of 1 when you get 2 SMS for example. I'll first see if we already have something to cater for that Aug 15 18:51:03 Didn't look in detail yet Aug 15 18:52:28 we have an "update" capability Aug 15 18:52:47 though I'm not sure we really tested it Aug 15 18:54:00 (using "replacesId" in the "create" notification) Aug 15 18:54:02 Tofe: Yeah... Will play a bit... Aug 15 18:54:37 Will have a look at Settings first to see what's missing there. Seems we need to extend audio service a bit for different volume levels. I'll document that Aug 15 18:55:11 ah yes, that reminds me I didn't check if the guys answered my little quesiton on the forum Aug 15 18:55:35 They did Aug 15 18:56:58 ok I'll test that Aug 15 18:57:04 Was indeed an unanswered call Aug 15 18:57:11 I already expected that based on the code tbh Aug 15 18:59:41 well, it should have worked :p I'll check that, it must be something obvious I forgot. Aug 15 18:59:43 I think it would be better to check for a VoiceCallMgr status or something Aug 15 18:59:57 Instead of relying on the incoming call dialog? Aug 15 19:00:40 Yes, that may be a better design Aug 15 19:01:34 Ok, yes, you're definitely right :D Aug 15 19:02:21 Just when I saw the report, I checked the code and I thought relying on the dialog looked wrong to me Aug 15 19:02:31 Though in theory it SHOULD work ;) Aug 15 19:03:00 Yes, but relying on the UI to do a controller thing is totally wrong Aug 15 19:03:23 I'll fix that today or tomorrow Aug 15 19:04:38 :D Aug 15 19:20:46 Ok, I've got a first version, but I don't know yet if it works :p Aug 15 20:26:01 having a modern device would be nice .. considering that i converted my sim over to micro a couple of years ago, so even if i do get my N4 running, I can't really use it with my regular sim .. :| Aug 15 20:26:55 EricBlade: N4 uses micro Aug 15 20:27:06 and i do happen to have a n5 that has a cracked display .. i can't donate it Aug 15 20:27:09 i'm sorry, Gnex Aug 15 20:27:21 oh, so i could get a N4 Aug 15 20:27:31 anyway, i can't donate my n5.. but i can use it as a secondary Aug 15 20:27:39 as soon as i get a replacement n5 Aug 15 20:28:00 i had received one but it had a busted power switch :| Aug 15 20:28:56 anyone know if there's any option to provide some kind of a visual status indicator as to if the "fetch" phase of a recipe is actually doing anything, or if it's just hanging around waiting? Aug 15 20:30:39 EricBlade: I have a working N5, just we didn't get around making a build for it... Aug 15 20:30:50 You can use the micro with adapter in Galaxy Nexus Aug 15 20:31:00 Just audio is garbled on Galaxy Nexus :S Aug 15 20:31:14 Similar to what happened on TP sometime where you needed to restart pulseaudio Aug 15 20:31:18 oh geez i forgot there was an adapter Aug 15 20:31:19 But on Nexus it seems always. Aug 15 20:31:30 We probably just need to bump the kernel a bit sometime Aug 15 20:35:47 so, i need to get some understanding of how the system works cleared up. If basically, we can theoretically run on anything that ... CM12 ? works on ... what specifically prevents us from running LuneOS basically on everything that CM12 runs on? Aug 15 20:36:12 I'm not making a complaint, just trying to understand where my knowledge of the stack is lacking Aug 15 20:37:52 EricBlade: In theory anything with a working CM build. Aug 15 20:37:58 EricBlade: because even tho' you can, you still need phone-specific tweaks for each one, just like CM12 does. Aug 15 20:38:17 We often look at sister projects like Mer/Sailfish/Jolla/Ubuntu and see what ports they have Aug 15 20:38:24 So we can piggyback on that a bit Aug 15 20:38:32 still waiting on that OPO LuneOS port :P Aug 15 20:38:55 EricBlade: This is a good reference: https://wiki.merproject.org/wiki/Adaptations/libhybris Aug 15 20:39:11 It tells you which kernel version is working with libhybris with which device Aug 15 20:42:34 GodGinrai: what sort of specific tweaks Aug 15 20:43:07 Herrie: ok, so, we also need libhybris to be working on the device .. any other qualifications? Aug 15 20:43:27 EricBlade: Not really I think... Spec wise: 1GB Ram minimum. Aug 15 20:43:34 I doubt anything less will work Aug 15 20:43:38 2GB+ is preferred Aug 15 20:43:48 It's not exact science.... Aug 15 20:44:02 You can do without libhybris when you have proper drivers like the Rpi ;) Aug 15 20:44:10 EricBlade: As someone who has not done any of the ports himself, I'm not sure I'd be able to answer that question appropriately. Aug 15 20:44:22 But any phone/tablet device is likely to need libhybris Aug 15 20:44:40 "proper drivers"? Aug 15 20:45:01 EricBlade: I.e. proper linux, not Android ;) Aug 15 20:45:10 ah, right Aug 15 20:45:13 We need libhybris because we only have Android binary blobs that we need to use Aug 15 20:45:21 So we need libhybris in between Aug 15 20:48:37 ... and so .. libhybris is tied to particular kernel versions? or particular CM versions? Aug 15 20:50:27 A combination it seems... I haven't done a port myself, but I've been told that CM 10.1, CM 11.0, CM 12.1 should work. CM 13 too. Aug 15 20:50:31 I don't know if CM versions can have more than one kernel version Aug 15 20:50:34 Probably CM 13 too Aug 15 20:51:09 We haven't ventured past CM 11 ourselves, but the Mer/Sailfish guys have Aug 15 20:51:15 CM 12.1 for some targets Aug 15 20:51:21 And CM13 for others even I think Aug 15 20:51:46 We use a lot of similar fundamentals (I.e. stripped Android build, libhybris, QT etc) Aug 15 20:51:57 Just we use openembedded, they have their own build system Aug 15 20:51:59 libhybris is compatible with multiple CM versions at build time, and is fairly independant of the kernel version; however, you'll need a kernel with the Android bits inside so that the drivers aren't completely lost Aug 15 20:53:08 EricBlade: We have written this up: http://webos-ports.org/wiki/Porting_Guide Aug 15 20:53:59 Should get you started in general. Problem currently is that we'd need some newer CM 12.1/CM13 branches in https://github.com/webOS-ports/android for example Aug 15 20:54:19 And pretty much in all these repos too: https://github.com/webOS-ports?utf8=%E2%9C%93&query=android Aug 15 20:54:23 It's on my long to-do list ;) Aug 15 21:00:29 so.. if we need libhybris, which we need for Android driver support, we are tied then to something like 3.2+ ? and if we don't, we're likely tied to whatever the min kernel version is that the entire chain of software could be built for Aug 15 21:02:36 3.2+ for what? Aug 15 21:02:37 Kernel? Aug 15 21:03:01 yea Aug 15 21:03:03 There are with 3.0 kernels as well Aug 15 21:03:13 Like the Galaxy Nexus and other old devices :P Aug 15 21:03:18 Most have 3.4 though Aug 15 21:03:42 3.0 does have some more challenges from what I understood on bluetooth etc Aug 15 21:03:57 i thought the android stuff wasn't in until later in the 3 series Aug 15 21:05:28 Well it was always in older versions as well, just not native Aug 15 21:05:42 older versions of what? Aug 15 21:05:46 Official support came somewhere in 3.x when stuff got merged Aug 15 21:05:58 You could have a 2.6 kernel running on Android, quite sure Aug 15 21:06:08 Just it was not supported out of the box afaik Aug 15 21:06:12 But I'm no kernel guru :P Aug 15 21:07:10 pretty likely if one were building a full system one would probably run into other components that balked going back that far. Aug 15 21:07:41 Yeah somethign more recent is better of course Aug 15 21:07:52 Also with BlueZ 5 support etc Aug 15 21:09:19 Anyway bedtime for me for today ;) Aug 15 21:15:13 yeah overall i'm just trying to understand what the specifics are to how widely available it's possible to be Aug 15 22:24:47 also trying to understand the dependence on Android, and specifically CM versions. Yes, I know the drivers, and such, but i'm trying to understand what creates a certain dependence on a specific CM, and why it's CM and not some other Android **** ENDING LOGGING AT Tue Aug 16 02:59:58 2016