**** BEGIN LOGGING AT Fri Jun 17 02:59:58 2016
Jun 17 03:53:48 <DougReeder> I sent messages via some different routes to Jake Morrison and Taylor Kimmett, the developers of Apollo.
Jun 17 04:26:12 <Herrie> Morning
Jun 17 04:26:20 <Herrie> DougReeder: OK, not sure what's the issue
Jun 17 04:26:26 <Herrie> There might be a patch already somewhere
Jun 17 04:29:31 <Herrie> DougReeder: It should be broken on legacy as well then?
Jun 17 04:29:35 * DougReeder nods
Jun 17 04:29:41 <Herrie> I didn't try it... But I'd say it should be
Jun 17 04:30:17 <DougReeder> Well, the analytics XHR is probably not important
Jun 17 04:31:18 <DougReeder> Apollo still works fine on my TP
Jun 17 04:33:12 <Herrie> DougReeder: Hmmz
Jun 17 04:33:19 <Herrie> Strange that it doesn't on LuneOS then
Jun 17 04:36:23 <DougReeder> It might be one more call that never returns an erro under webOS, so Apollo doesn’t properly check.
Jun 17 04:37:03 <Herrie> DougReeder: Or a bug on QtWebEngine
Jun 17 04:37:13 <Herrie> Because on QtWebKit I do get the Apollo main screen
Jun 17 04:38:06 <DougReeder> Hrm
Jun 17 04:53:41 <Herrie> DougReeder: Trying to disable the analytics calls now see what it does
Jun 17 04:53:55 * DougReeder nods
Jun 17 05:06:28 <Herrie> Hmmz that doesn't work either
Jun 17 06:18:38 <Tofe> Morning
Jun 17 06:19:30 <Tofe> Herrie: from what I've seen so far, the issue with Apollo on WebEngine might be that the latter is more strict when QtWebKit on some aspects
Jun 17 07:11:16 <Herrie|Pre3> morning
Jun 17 07:11:23 <Herrie|Pre3> Tofe: Yeah could be.
Jun 17 07:19:41 <Herrie|Pre3> Tofe: It seems that custom url scheme handlers don't work. Macaw Enyo (Twitter client) uses macaw://twittercallback for the callback url.
Jun 17 07:20:28 <Herrie|Pre3> That should work but doesn't. Let me see what's the exact error msg. Maybe you can tackle it together with #1113 ?
Jun 17 07:31:32 <Tofe> Herrie|Pre3: I think custom url handlers is one of the big missing things so far on luneos
Jun 17 07:32:18 <Tofe> Wasn't there dedicated code in WebKit in WebOS for that, like for redirect?
Jun 17 07:43:59 <Herrie|Pre3> Tofe: I'm not sure, just installing latest nightly and will look what was the exact error code.
Jun 17 07:44:15 <Herrie|Pre3> It was quite specific, it might just be disabling a certain check
Jun 17 10:17:23 <Herrie|Pre3> morphis: ping
Jun 17 10:18:21 <Herrie|Pre3> Tofe: Got my full EUR 175 N4 refund. Now looking for a replacement N4 and seems I can get some for EUR 60/70 in decent shape and a N5 for EUR 120 in good shape. So might be able to get both and help HaDAk with N5 port :)
Jun 17 10:19:34 <morphis> Herrie|Pre3: pong
Jun 17 10:20:00 <Herrie|Pre3> morphis: For MTK, which Android versions work and which not?
Jun 17 10:20:11 <morphis> we have all working
Jun 17 10:20:15 <morphis> 4.x, 5.x and 6.x
Jun 17 10:20:31 <morphis> but as I said before its not the Android version which is the problem mostly
Jun 17 10:20:32 <Herrie|Pre3> OK so what would be the concerns?
Jun 17 10:20:37 <morphis> its the vendor specific stuff
Jun 17 10:20:48 <morphis> it will be different for each device
Jun 17 10:21:09 <Herrie|Pre3> Ah so the components they use you mean besides the MTK chipset?
Jun 17 10:22:24 <morphis> not only that but the whole BSP is different for each device, differnt compile time parameters, different combinations etc.
Jun 17 10:22:40 <morphis> so if you have one 5.x MTK device working that doesn't mean another is working the same way
Jun 17 10:22:51 <morphis> but MTK is normally just shit
Jun 17 10:23:02 <morphis> if you can get something better, take it
Jun 17 10:23:40 <Herrie|Pre3> morphis: OK, just talking potential stuff.... So when possible avoid MTK... Anything decent besides Qualcom ?
Jun 17 10:23:48 <Herrie|Pre3> Or Qualcomm the best choice?
Jun 17 10:23:55 <morphis> samsung exynos is also good
Jun 17 10:24:53 <Herrie|Pre3> OK I thought those were challenging before as well, that's why there was no CM for it? Or that changed?
Jun 17 10:25:22 <Herrie|Pre3> AllWinner, RockChip, HiSillicon are a no-go as well I assume?
Jun 17 10:28:06 <morphis> Herrie|Pre3: take something qcom based
Jun 17 10:28:10 <morphis> that is the safest bed so far
Jun 17 10:28:16 <morphis> you will run into problems too
Jun 17 10:29:32 <Herrie|Pre3> How much time you reckon it would take an experienced dev with hybris knowledge to get a new device working fully?
Jun 17 10:29:43 <morphis> puuh
Jun 17 10:29:56 <morphis> fully working means including all functionalities?
Jun 17 10:31:19 <Herrie|Pre3> morphis: Yeah well most, lets say display, touch, led, audio, nfc, bt, gps, camera, sensors, keys, vibra
Jun 17 10:31:35 <Herrie|Pre3> Rough estimate. 1 week, 1 month, 2 months :P ?
Jun 17 10:31:42 <morphis> > 2 months
Jun 17 10:31:50 <morphis> if its just in his free time
Jun 17 10:32:06 <Herrie|Pre3> morphis: And if full time paid?
Jun 17 10:32:09 <morphis> Herrie|Pre3: the best thing is you guys take something which already runs Ubuntu or SailfishOS
Jun 17 10:32:48 <morphis> Herrie|Pre3: see, there are teams of 5-10 people work for both Ubuntu/Sailfish on just a device and to get it fully production ready that takes something between 1-3 months
Jun 17 10:33:37 <morphis> this is real hard work, not said that you can't get first results quite fast
Jun 17 10:34:03 <Herrie|Pre3> morphis: Yeah I know, just want to have a guestimate
Jun 17 10:34:30 <morphis> and you will easily run into problems which will block you for a long time
Jun 17 10:36:43 <morphis> Herrie|Pre3: if you take somethign make sure it has >= kernel 3.10
Jun 17 10:37:31 <Herrie|Pre3> morphis: OK well everything now more or less has right?
Jun 17 10:37:50 <morphis> 3.4 still works fine
Jun 17 10:38:02 <morphis> but you 3.10 for something I have (personally) in work
Jun 17 10:40:31 <morphis> which I guess you really want to have :-)
Jun 17 10:41:16 <Herrie|Pre3> OK 3.10 makes BlueZ 5 a lot easier right?
Jun 17 10:44:44 <morphis> Herrie|Pre3: I would suggest for bluez5 you follow https://wiki.ubuntu.com/Touch/BluetoothEnablement
Jun 17 10:49:32 <Herrie|Pre3> morphis: Thnx
Jun 17 10:49:40 <Tofe> Herrie|Pre3: It would be quite nice yes! Maybe I should get one too, if we begin to tackle that one seriously
Jun 17 12:31:51 <Herrie|Pre3> Tofe: Seems some guy is getting Instagram working in QT :) He already made SFOS and Ubuntu app it seems. Pinged him about LuneOS :P
Jun 17 12:32:25 <Herrie|Pre3> http://github.com/neochapay/Qtinstagram
Jun 17 12:39:41 <Herrie|Pre3> Seems it doesn't use any Silica or the likes just standard QT :)
Jun 17 13:09:41 <Tofe> Yes, I've seen it in the Sailfish store
Jun 17 13:11:19 <Tofe> Looking at the app, it sems it could be packaged as-is
Jun 17 13:12:49 <Tofe> I could give it a try
Jun 17 13:13:54 <Tofe> But before that, i'll open an issue regarding the lack of license
Jun 17 13:17:50 <Tofe> Done I've opened Issue#1 :p
Jun 17 13:17:51 <Herrie|Pre3> Tofe: Yeah ;)
Jun 17 13:18:00 <Herrie|Pre3> License would be good :)
Jun 17 13:18:40 <Tofe> I guess it'll be BSD or GPL, but without a license we don't have any actual right
Jun 17 13:19:17 <Herrie|Pre3> Tofe: Yeah
Jun 17 13:20:02 <Herrie|Pre3> Instagram is a nice name to have as app :)
Jun 17 13:20:18 <Herrie|Pre3> Especially since the legacy Instagrio app got sandboxed
Jun 17 13:50:27 <Tofe> Ok, he answered: GPLv3
Jun 17 13:52:27 <Tofe> he added a license file, but it's empty :p I won't bother him for that though, I'll create a bb recipe and tell him about it
Jun 17 13:52:40 <Herrie|Pre3> Tofe: Hehe :)
Jun 17 13:55:51 <Tofe> Herrie|Pre3: fyi, I've created this: https://www.openhub.net/p/webos-ports
Jun 17 13:56:02 <Tofe> It'll give some fun stats, if nothing else
Jun 17 13:56:32 <Tofe> (the analysis is still in progress)
Jun 17 13:58:38 <Herrie|Pre3> Tofe: Nice :) Yeah seems it needs some updating still :P
Jun 17 15:19:02 <Herrie|Pre3> Tofe: Seems my replacement N4 will be picked up soon :) EUR 70 for lightly used one. It's in my brother's city so he'll pick it up for me :)
Jun 17 15:19:18 <Herrie|Pre3> N5 probably Sunday or early next week :)
Jun 17 15:19:31 <Herrie|Pre3> HaDAk: ^ :D
Jun 17 15:19:59 <Tofe> Great :)
Jun 17 16:42:54 <HaDAk> Herrie: ack
Jun 17 19:06:51 <Herrie|Laptop> Tofe: I'm getting ERR_UNKNOWN_URL_SCHEME on Macaw Enyo when it tries to call https://github.com/minego/macaw-enyo/blob/master/source/twitter.js#l106
Jun 17 19:07:20 <Herrie|Laptop> I guess we could make sure it doesn't identify as enyo.platform.webos by adding an additional check there to check for the enyo.platform.webos version
Jun 17 19:07:33 <Herrie|Laptop> So it'll work OK in legacy but that might be the wrong way of solving it
Jun 17 19:10:27 <Herrie|Laptop> Since I expect other apps to use something similar
Jun 17 19:11:23 <Tofe> Yes, we should make the custom url schemes work
Jun 17 19:11:46 <Tofe> It's just that I don't know how that stuff works :)
Jun 17 19:13:53 <Herrie|Laptop> Well there are 198 references to the word scheme in C++ code in open webos :P
Jun 17 19:14:00 <Herrie|Laptop> Going through them now
Jun 17 19:14:24 <Tofe> http://doc.qt.io/qt-5/qwebengineurlschemehandler.html
Jun 17 19:14:35 <Tofe> That should help us at some point, I guess :p
Jun 17 19:17:40 <Herrie|Laptop> Tofe: https://github.com/qtproject/qtwebengine-chromium/blob/b45f07bfbe74c333f1017810c2409e1aa6077a1b/chromium/net/url_request/url_request_job_manager.cc#L64
Jun 17 19:17:46 <Tofe> Looks like it would be fairly easy; but how does it work in webos ? it is something like <appName>://<relativeURI> ?
Jun 17 19:19:57 <Herrie|Laptop> Tofe: Not sure
Jun 17 19:20:39 <Herrie|Laptop> Tofe: Ah a clue....
Jun 17 19:21:08 <Herrie|Laptop> https://github.com/minego/macaw-enyo/blob/master/appinfo.json#L13
Jun 17 19:21:16 <Herrie|Laptop> I guess it should be provided in the appinfo.json
Jun 17 19:21:26 <Herrie|Laptop> ANd it should be parsed somehow so it's allowed as urlscheme
Jun 17 19:22:35 <Tofe> ok, so for each mimetype (why mimetype?) we should have an url scheme handler which would redirect it to the correction location
Jun 17 19:22:54 <Herrie|Laptop> https://github.com/openwebos/luna-sysmgr/blob/1393f0af5dd8d9f0e9cc79627f4acb226f8c8d45/Src/base/application/ApplicationDescription.h
Jun 17 19:23:00 <Herrie|Laptop> https://github.com/openwebos/luna-sysmgr/blob/1393f0af5dd8d9f0e9cc79627f4acb226f8c8d45/Src/base/application/ApplicationDescription.cpp
Jun 17 19:23:04 <Herrie|Laptop> I'm just checking OWO now
Jun 17 19:23:23 <Tofe> http://www.webos-internals.org/wiki/MimeTypes#URL_Pattern
Jun 17 19:23:47 <Tofe> looks like it is GREAT ;)
Jun 17 19:25:30 <Tofe> However, I'm not sure where we should redirect it to :p
Jun 17 19:26:53 <Herrie|Laptop> Tofe: I think to itself
Jun 17 19:26:56 <Herrie|Laptop> But I'm not sure
Jun 17 19:27:05 <Herrie|Laptop> DougReederG3: ^ any ideas?
Jun 17 19:27:19 <Herrie|Laptop> Garfonso: ^ You might know as well
Jun 17 19:28:04 <Tofe> Basically, it says it should redirect to the app, but I'm not sure which url to load
Jun 17 19:29:57 <DougReederG3> Urls and mime types are orthogonal.
Jun 17 19:30:32 <Tofe> well, looks like it's all mixed up in webos :p
Jun 17 19:31:03 <DougReederG3> We need to support custom schemes at some point.
Jun 17 19:31:24 <Tofe> I do agree, and I think we have the tools to do that with QtWebEngine 5.6
Jun 17 19:32:04 <Tofe> But where should macaw://stuff/page.htm be redirected to?
Jun 17 19:32:24 <Tofe> file://<path_to_app>/stuff/page.htm ?
Jun 17 19:32:41 <DougReederG3> Short term, it might be that Macaw should deal with a lack of custom scheme support - but that may be essential for validating with the provider.
Jun 17 19:33:07 <Herrie|Laptop> DougReederG3: It can do without it...
Jun 17 19:33:17 <Herrie|Laptop> It only uses custom one for enyo.platform.webos
Jun 17 19:33:19 <DougReederG3> Sorry, Im not familiar with the implementation
Jun 17 19:33:39 <DougReederG3> So theres hope
Jun 17 19:33:46 <Herrie|Laptop> It's a simple check: https://github.com/minego/macaw-enyo/blob/master/source/twitter.js#l106
Jun 17 19:38:41 <Tofe> Herrie|Laptop, DougReederG3: don't you think we should be able to implement something for the next release?
Jun 17 19:39:15 <Tofe> A basic implementation should be enough for Macaw, and is better than a temporary hack to make Macaw work
Jun 17 19:41:06 <Herrie|Laptop> Tofe: Yeah I agree
Jun 17 19:41:55 <Herrie|Laptop> Tofe: If I apply the hack it works though :P
Jun 17 19:42:09 <Herrie|Laptop> So that's possitive :D
Jun 17 19:42:13 <Tofe> :)
Jun 17 19:42:14 <Herrie|Laptop> A Twitter client ;)
Jun 17 19:42:24 <Tofe> I'm working on the Instagram one :p
Jun 17 19:42:27 <Herrie|Laptop> And probably also soon an Instagram one right :P ?
Jun 17 19:42:48 <Herrie|Laptop> I pinged Filmor for the messaging bits, maybe he'll chip in ;)
Jun 17 19:43:03 <Tofe> I've got a recipe, but bb is crashing on some appinfo.json checksum, I don't know why; certainly some stupid mistake from me
Jun 17 19:43:14 <Herrie|Laptop> HUH?
Jun 17 19:43:18 <Herrie|Laptop> Appinfo.json checksum
Jun 17 19:43:34 <Tofe> yes, like for fingerterm, we need to provide it ourself
Jun 17 19:43:46 <Herrie|Laptop> For fingerterm we don't provide it? https://github.com/webOS-ports/meta-webos-ports/blob/fido/meta-luneos/recipes-luneos/apps/fingerterm.bb
Jun 17 19:43:58 <Tofe> provide the file, I meant
Jun 17 19:44:07 <Herrie|Laptop> Yeah
Jun 17 19:44:18 <Tofe> the checksum is just a bb warning, but then it's crashing violently and it seems related
Jun 17 19:44:25 <Herrie|Laptop> I guess you need https://github.com/webOS-ports/meta-webos-ports/blob/fido/meta-luneos/recipes-luneos/apps/fingerterm.bb#l28
Jun 17 19:44:52 <Herrie|Laptop> And make sure your appinfo.json is flexible?https://github.com/webOS-ports/meta-webos-ports/blob/fido/meta-luneos/recipes-luneos/apps/fingerterm/appinfo.json#L4
Jun 17 19:45:38 <Tofe> ah, no, it was my git url which was badly set
Jun 17 19:45:46 <Tofe> As I said, stupid mistakes.
Jun 17 19:46:16 <Herrie|Laptop> :D
Jun 17 19:46:27 <Herrie|Laptop> Instagram & Twitter are important to have
Jun 17 19:46:37 <Herrie|Laptop> I think W10 still doesn't have Instagram :P
Jun 17 19:47:10 <Herrie|Laptop> Ah wait they do :P
Jun 17 19:48:57 <Tofe> while discussion, I now have an ipk  to test :p
Jun 17 19:49:05 <Herrie|Laptop> :D
Jun 17 19:49:13 <Herrie|Laptop> I'm happy to trial on my VBOX
Jun 17 19:49:19 <Herrie|Laptop> Just I have no account :P
Jun 17 19:49:32 <Tofe> neither do I :D
Jun 17 19:50:41 <Tofe> ah, doesn't work out-of-the-box, I may have missed something important
Jun 17 19:52:45 <Tofe> ahah, yes, it does
Jun 17 19:52:51 <Tofe> just my appinfo had a typo
Jun 17 19:55:06 <Tofe> Mmmh the font for the fields is really small
Jun 17 19:55:14 <Tofe> Let me test on desktop
Jun 17 19:56:34 <Tofe> yes, it's quite specific to the device
Jun 17 19:56:43 <Tofe> maybe a DPI thingy
Jun 17 19:58:11 <Tofe> Herrie: It's a bit too soon to push that on github, without having talked with the dev first, but if you want I can give you the recipe to build on qemu
Jun 17 20:04:05 <Herrie|Laptop> Tofe: Sure that would be nice
Jun 17 20:04:11 <Herrie|Laptop> Was collecting a package ;)
Jun 17 20:04:20 <Herrie|Laptop> I guess we'd need to use our GridUnit stuff
Jun 17 20:04:44 <Herrie|Laptop> smartwatermelon sent me a box full of HP/Palm goodies ;)
Jun 17 20:05:13 <Herrie|Laptop> A BNIB TP4G, a wifi TP Go, another TP (not sure it works) and a load of batteries for various phones it seems
Jun 17 20:05:22 <Herrie|Laptop> So I have a TP4G to test with again
Jun 17 20:05:24 <DougReederG3> I ahve have no idea how much work it will be. It should be worthwhile, though.
Jun 17 20:05:42 <Herrie|Laptop> DougReederG3: I'd say probably 10-15 mins :P
Jun 17 20:05:50 <Herrie|Laptop> Tofe: It's QML app right?
Jun 17 20:06:19 <Tofe> QML+cpp
Jun 17 20:07:10 <Tofe> Herrie|Laptop: I have a working eventual fix ready, which doesn't require GridUnit
Jun 17 20:07:18 <Herrie|Laptop> Tofe: OK :D
Jun 17 20:07:20 <Herrie|Laptop> Even better
Jun 17 20:08:13 <Herrie|Laptop> Well at least now you can register accounts online with Instagram, that wasn't possible Tofe when I checked (OK I admit that was a LONG time ago)
Jun 17 20:14:43 <Tofe> well well, it works pretty well
Jun 17 20:16:30 <Tofe> just the font size isn't DPI-aware
Jun 17 20:16:51 <Herrie> Tofe: Well that's why we have our own bits ;)
Jun 17 20:16:59 <Herrie> We could tweak those in later I guess
Jun 17 20:17:13 <Herrie> Make some LuneOS specific bits like we did for FingerTerm ?
Jun 17 20:19:24 <Tofe> There are some things already available within Qt
Jun 17 20:22:01 <Tofe> starting QT_SCALE_FACTOR=3 XDG_RUNTIME_DIR=/tmp/luna-session/ ProstoGramm gives an acceptable output
Jun 17 20:25:18 <Herrie> Tofe :D
Jun 17 20:25:38 <Herrie> For hw acceleration what takes care of that? I remember we needed Android 4.4 for it.
Jun 17 20:25:49 <Herrie> But not sure what does the actual acceleration?
Jun 17 20:27:34 <Tofe> It's via eglfs and libhybris
Jun 17 20:27:43 <Herrie> OK
Jun 17 20:27:48 <Herrie> Andolamin wanted to know
Jun 17 20:28:31 <Andolamin> Thanks - I picked up a OPX and am going to try to boot LuneOS on it
Jun 17 20:28:38 <Tofe> We don't need a specific version of Android, but we need a working set of Android drivers :)
**** ENDING LOGGING AT Sat Jun 18 02:59:58 2016