**** BEGIN LOGGING AT Thu Dec 31 02:59:58 2015 Dec 31 07:04:45 morning Dec 31 07:04:47 Tofe: ping Dec 31 07:49:20 morning Dec 31 08:56:08 nizovn: morning Dec 31 10:07:49 Tofe: You around? Dec 31 11:09:03 nizovn: Can you have a look at https://github.com/webOS-ports/luna-next/pull/118/files ? Dec 31 11:09:45 Basically we're expecting launchParams (based on legacy) but our current implementation was for launchParam instead causing the launchParams never to be passed ;) Since we only use it on a few places decided to fix luna-next properly Dec 31 11:12:14 Morning Dec 31 11:13:48 Herrie: some comments about the PR: actually the only place where the "launchParam" name is visible from outside is in the call to LS2, probably in the cardshell Dec 31 11:16:58 Here we read launchParams: https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/LunaSysAPI/NotificationService.qml#L99 Dec 31 11:18:17 Or maybe I misunderstand the issue Dec 31 11:20:24 Tofe: Well in legacy it's called launchParams and it are usually multiple, so for consistency I suggest to keep it launchParams ;) Dec 31 11:21:19 We took our notification API from Jolla, so it was probably in theirs called launchParam without the s ;) Dec 31 11:22:46 but in this PR I only see C++ variable names, not "public" API names like DBus or LS2 properties names Dec 31 11:23:04 (expect for the QML property name, here, ok, it has impact on the cardshell) Dec 31 11:23:36 This PR seems a good idea, but I would like to understand why it fixes something Dec 31 11:24:02 Tofe: If you now do a LS2 call with launchParams it will never end up in LNC because Luna-next expects launchParam ;) Dec 31 11:24:23 I noticed it when testing the update notification, it would pass launchparams Dec 31 11:24:46 Then I checked the log and got: Dec 10 14:06:55 maguro luna-next[2163]: DEBUG: 14:06:55.213: Herrie arguments[0]{"objectName":"","ownerId":"org.webosports.service.update","replacesId":2,"launchId":"org.webosports.app.settings","launchParam":"[object Object]","title":"System update available","body":"New version body","iconUrl":{},"soundClass":"","soundFile":{},"duration":-1,"doNotSuppres Dec 31 11:24:46 s":false,"priority":0,"expireTimeout":5,"timestamp":"2015-12-10T13:06:54.385Z"} Dec 31 11:25:20 Of course it could be fixed with a 1 liner in LNC but this approach seemed more proper to me ;) Dec 31 11:25:28 https://github.com/webOS-ports/luna-next-cardshell/blob/master/qml/Notifications/NotificationArea.qml#L147 <-- this line uses launchParams, so it means it has to match the declaration here: https://github.com/Herrie82/luna-next/blob/LaunchParams/plugins/shell/notifications/notification.h#L33 Dec 31 11:25:35 for me, that's the real fix Dec 31 11:25:45 but I'm fine with the rest of the PR ;) Dec 31 11:26:40 Merged Dec 31 11:26:56 Tofe: Yeah that's where it started ;) Then I decided to just do it everywhere Dec 31 11:27:08 As a plus we get legacy compatibility syntax wise Dec 31 11:27:18 So that's worth the few minutes to fix it :P Dec 31 11:27:36 Yes, quite so. And you probably fixed a bug in the meantime! Dec 31 11:27:54 Yup ;) Dec 31 11:28:12 there is typo here https://github.com/webOS-ports/luna-next/pull/118/files#diff-51a4211d09878afa5b907b2f32dfadf7R105 Dec 31 11:28:15 Because my SMS notification wasn't going to the right thread ;) Dec 31 11:28:35 nizovn: Well spotted Dec 31 11:28:37 Let me fix that Dec 31 11:30:14 Done Dec 31 11:33:58 Tofe: How's your PR testing going? Dec 31 11:34:34 Herrie: here is another one : https://github.com/webOS-ports/luna-next/blob/9708bbf2b2649741d268c37efcca37d04478f72b/plugins/shell/notifications/notificationmanagerwrapper.cpp#L30 Dec 31 11:36:11 Herrie: My PR seems useless, looks like I don't know how to use a shared pointer :p Dec 31 11:37:55 nizovn: OK also fixed Dec 31 11:38:19 Tofe: OK Dec 31 12:32:55 Herrie: my new PR attempt looks better, I don't get any crash now Dec 31 12:33:11 I'll propose it upstream too Dec 31 12:42:14 oh, no need, looks like it has already been fixed upstream Dec 31 12:42:29 in a quite complicated way Dec 31 12:47:06 ah, well, no, maybe their way is a bit safer than mine. ok, anyway, it's in Qt 5.5 and 5.6. Dec 31 13:00:56 In the end, I cherry-picked the commit from upstream. It made much more sense that way. Dec 31 13:33:42 Tofe: OK I kicked off new nigthly now including this fix as well Dec 31 13:34:06 Were you ever able to replicate the semi transparent windows in Enyo apps? Dec 31 13:34:25 Like emial and accounts? They get stuck with me quite regularly while trying to add an account for example in email app Dec 31 14:15:34 no, never Dec 31 14:15:59 but I rarely think to go to account setup Dec 31 14:25:44 Tofe: Well you should try sometimes... It happens to me more often that I cannot finish setting up the account then that I'm successfull ;) Dec 31 14:26:04 But might be related to your fix already Dec 31 14:26:05 Will try Dec 31 14:58:19 It always used to work with QtWebKit so it must be something in the migration that needs a little fix somehow ;) Dec 31 17:49:02 When I go to file a new issue, I get a 403 error. Is there something I need to do to my account, or is that something that needs to be fixed? Dec 31 17:49:49 Was going to file a bug that https://github.com/webOS-ports/org.webosports.update does not seem to have a LICENSE file or license info at the top of source files. Dec 31 17:50:59 No LICENSE or COPYING file, I should say. Dec 31 17:55:11 Additionally, I think I figured out why I ended up downloading an out-of-date qemux86 VM - the main page of the wiki links to it as the latest version and doesn't mention the December release. Dec 31 17:55:14 KyleMaas_Laptop: At http://issues.webos-ports.org/projects/ports/issues? I just tried it and it is working OK here? Dec 31 17:55:15 I had seen the December release (part of what got me back into wanting to help with development), but didn't bother checking which version I was downloading the VM image. Dec 31 17:55:34 elvispre: Correct. This page gives me a 403: http://issues.webos-ports.org/projects/ports/issues/new Dec 31 17:57:12 Hmm. That works for me (following your link directly). I guess someone like Herrie needs to give your Issues account more access. Dec 31 17:57:13 Very well might just be my account. It is relatively new. Dec 31 17:59:18 KyleMaas_Laptop: I need to give you acccess ;) What's your username? Dec 31 17:59:27 Herrie: KyleMaas Dec 31 18:00:39 On the release: I did alll the bits on the Wiki, so qemux86 links to Marrochino December release, just main page doesn't have an article :S Dec 31 18:00:49 Was a bit busy must have slipped my mind LOL Dec 31 18:01:12 Other things I need to test once the new VM image finishes downloading: first use app's timezone setting didn't actually change the system timezone setting, updates app kept downloading packages past the number it said it needed to... Dec 31 18:01:14 download, and if you started a tap-and-drag operation during the animation from an app's minimized state to full screen, it would trap that app in a medium-sized window. Dec 31 18:02:02 Herrie: Might be good to have a newbie blundering around a bit. My first inclination was to click the "Read More" for the latest release, scroll down, and download from the link on there. Dec 31 18:02:03 Let me fix that ;) Dec 31 18:02:08 Ie the wiki Dec 31 18:02:43 Or I should say what I *thought* was the latest release. Dec 31 18:03:23 KyleMaas_Laptop: Yeah Dec 31 18:03:28 You're best taking latest nightly Dec 31 18:03:44 Timezone stuff should work really Dec 31 18:03:48 Also, somehow the other day I was able to get to webos-ports.org without being redirected to the Main_page link, which meant that all I saw was the Alpha3 announcement. Don't know how I got there. Haven't been able to reproduce it. Dec 31 18:03:49 It has been around for ages and works for me ;) Dec 31 18:04:07 Herrie: Where do I download the nightly? I haven't seen it documented anywhere I've read on the wiki. Dec 31 18:04:14 KyleMaas_Laptop: could've been some odd cache ;) Dec 31 18:04:24 Herrie: btw seems webos-ports.org page is a little hacked -- look on the left top corner Dec 31 18:04:54 nizovn: Screenshot + code from the page please. I don't see it here... I have seen it in the past. We couldn't find anything in our wiki source code.... Dec 31 18:05:09 KyleMaas_Laptop: Main page updated Dec 31 18:05:44 Herrie: Awesome. Title of the post still says "Caffé Latte", though. Dec 31 18:07:39 Sorted Dec 31 18:07:56 Much better. Dec 31 18:08:10 Now, where do I find a nightly image? Dec 31 18:08:26 http://webos-ports.org/wiki/Qemux86_Info Dec 31 18:08:31 There's a icon for nightly on top ;) Dec 31 18:08:42 Perfect. Dec 31 18:08:48 Then just take the luneos-dev-emulator-qemux86.zip which is always a symlink to the latest image Dec 31 18:08:53 I don't normally think of a VM host as a "device". :) Dec 31 18:08:53 There should be a new one shortly Dec 31 18:09:08 KyleMaas_Laptop: Well yeah we needed to do something ;) Dec 31 18:09:31 Newbie blundering around. Just sayin'. :) Dec 31 18:09:36 KyleMaas_Laptop: Made you "human" on the issue trakcer ;) Dec 31 18:09:42 So you can report stuffs ;) Dec 31 18:09:50 Got it. Thanks! Dec 31 18:10:21 Herrie: http://tinypic.com/r/29zo13s/9 Dec 31 18:11:20 Is this an okay report? http://issues.webos-ports.org/issues/1025 Dec 31 18:17:03 KyleMaas_Laptop: I'd suggest we'd just fix it, for these small things a bug report is not really that necessary Dec 31 18:17:06 Garfonso: ping ;) Dec 31 18:17:24 KyleMaas_Laptop: Garfonso did the update bits together with morphis Dec 31 18:17:35 So will just ask him what license he wants ;) Dec 31 18:17:43 Sounds good. Dec 31 18:18:49 Andolamin: Is your Raspberry Pi port for the ARM6 Pi 1 or the ARM7 Pi 2? Dec 31 18:20:14 KyleMaas_Laptop: Tofe did most of UI stuff, so any bugs there you can report and assign to him (Christophe Chapuis) is his name on issue tracker ;) Dec 31 18:20:53 I know a bit of QML too so might be able to tackle stuff but usually the low hanging things since I'm not a real dev ;) I'm good at copying, pasting & modifying, not so much as writing stuff myself :P Dec 31 18:21:01 Though Browser app I did mainly :P Dec 31 18:21:02 Okay. Thinking I'll probably want to just report bugs as unassigned until I get to know the team a bit better. Dec 31 18:22:06 KyleMaas_Laptop: Both, but I haven't tested on the Pi 1 and I would expect that it has performance problems. Dec 31 18:22:08 Also fine, I keep an eye on it anyway and assign where needed ;) Dec 31 18:23:34 Andolamin: Yeah, I wouldn't be surprised. We got a BeagleBone Black at work and were quite surprised at the lack of performance. Dec 31 18:23:59 Andolamin: But I was also thinking that LuneOS on a Pi 1 Model A+ with a touchscreen attached could make a nice little PDA. Dec 31 18:26:11 Looks like the timezone setting from the first use app does indeed carry through to the system timezone now. Dec 31 18:26:41 There does seem to be an index issue. It somehow selects Detroit instead of New York :P Dec 31 18:26:46 So need to look into that Dec 31 18:27:08 This whole timezone had quite some episodes already :P Dec 31 18:27:20 It's already a lot better compared to what it was before :P Dec 31 18:27:56 Also, when you launch an app, the placeholder "launching" screen and animation loads, the entire app disappears, then it redraws the full loaded app. Is there a bug for that already that I'm missing? Dec 31 18:29:02 KyleMaas_Laptop: This is one of the little drawbacks of the QtWebKit->QtWebEngine migration. Dec 31 18:29:10 1005 Dec 31 18:29:15 Shoudl cover that Dec 31 18:30:04 I added it there Dec 31 18:30:45 I don't see that behavior anywhere in the description. Also: does that bug tracker not support hierarchical linking of bugs? I'm used to seeing task lists like that ordered in a dependency tree. Dec 31 18:31:14 KyleMaas_Laptop: It does hierarchy somehow Dec 31 18:31:15 Don't see it in the comments, either. Dec 31 18:31:20 I just added it now ;0 Dec 31 18:31:22 ;) Dec 31 18:31:28 Tofe knows it exists Dec 31 18:31:34 Now it's properly documented Dec 31 18:32:02 Ah. :) Dec 31 18:32:20 It doesn't do anything functionality wise: But yeah it's confusing ;) Dec 31 18:33:13 Is there any support for non-default keyboards or switching between different languages' keyboards? Dec 31 18:33:50 I remember there was a locale selector in the first use app, but I don't see anything to change that locale in the Settings app. Dec 31 18:34:53 KyleMaas_Laptop: Press the globe on the VKB Dec 31 18:35:02 Some languages need a bit of work still, but most are OK already Dec 31 18:35:13 Italian, Hungarian and Polish need work AFAIK Dec 31 18:35:15 Rest I did already Dec 31 18:37:57 Ah, okay. Dec 31 18:38:48 It's not 100% 3.0.5/LunaCE VKB but it comes close ;) Dec 31 18:38:56 So, no Japanese keyboard yet. My Japanese is horrible, but I figured if Chinese rendering is broken (bug #997), there are likely other things broken regarding CJK input and display. Dec 31 18:39:11 KyleMaas_Laptop: No Japanese ;) Dec 31 18:39:21 There is some Chinese though I think Dec 31 18:39:25 Any effort yet to do internationalization of text throughout the system? Dec 31 18:39:29 Though that would need updating too ;) Dec 31 18:39:48 Not really yet... Though it's not that hard to do Dec 31 18:40:34 We're going to need it soon enough with the Contacts, Messaging & Phone app for formatting using i18n etc Dec 31 18:40:34 There is the ZH keyboard, but I don't know enough Chinese to properly use the keyboard for it. Dec 31 18:41:07 KyleMaas_laptop: Yeah that one ;) Dec 31 18:41:33 Enyo2 has https://github.com/enyojs/enyo-ilib Dec 31 18:41:45 Which should be easy enough to implement Dec 31 18:42:59 Not sure how to do things on QML side but I'm sure Tofe has some ideas on it as our resident QML expert :P Dec 31 18:43:24 I've seen Jolla and Ubuntu having some approaches that look similar to Enyo's. So I guess it shouldn't be too hard Dec 31 18:44:12 May have to see if I can figure out how to do a Japanese keyboard. Composition of kanji would be interesting to try to add, to say the least, but it'd be nice to have Japanese input on there. Dec 31 18:44:43 Are keyboards pluggable via an .ipk package, or are they baked into the system image? Dec 31 18:45:49 Oops, looks like I missed a QML question Dec 31 18:46:51 Oh, wow. Preware looks weird in the nightly. Dec 31 18:48:05 KyleMaas_Laptop: define weird ;) Dec 31 18:48:07 KyleMaas_Laptop: today they are backed in the system image Dec 31 18:48:11 KyleMaas_Laptop: It's QML ;) Dec 31 18:48:47 Basically: https://github.com/webOS-ports/webos-keyboard/tree/master/qml and then layouts for each language at https://github.com/webOS-ports/webos-keyboard/tree/master/plugins Dec 31 18:48:49 Herrie: Large vertical black band when you load the app. Categories are scrunched into a little space on the left. Once you click one of the categories, the right side fills the black band. Dec 31 18:49:07 Most of the keyboard are just a couple of qml files though, but for chinese/japanese it's possible that is would need a bit of C++; not sure though. Dec 31 18:49:26 Herrie: When you click from category to category, the category names toggle between two lines and one, but are in too small of a space to actually display. Dec 31 18:49:45 KyleMaas_Laptop: I need to check a bit ;) Dec 31 18:49:50 Tofe: Cool. I'll have to take a look at that. Dec 31 18:50:06 Herrie: May just be a qemux86 thing. Dec 31 18:50:36 There is already a beginning of chinese keyboard, taken from Ubuntu keyboard originally, but I think we never tested it Dec 31 18:50:47 Herrie: The left side is so small that the top has the Preware icon followed by "Pr". Everything to the right of it is overlapped or cut off or something. Dec 31 18:51:12 KyleMaas_Laptop: We switched the size of Qemux86 a bit recently, could be it needs some tweaking. Dec 31 18:51:16 Tofe: It *looks* like an English keyboard when you switch to it. But I don't know how Chinese keyboards are laid out. Dec 31 18:52:05 We use something called GridUnits for a device/resolution independent approach. So it doesn't matter if you have a 320 * 480 or a 4K screen, the amount of real estate it takes on the screen should be similar... Dec 31 18:52:51 For Touchpad this means that 10 pixels is 1 GridUnit, for N4, 18 pixels = 1 GridUnit. For the emulator we used to use 8 before, however since it's the same resolution as Touchpad it made sense to move it to 10. Dec 31 18:52:57 This could be one of the downsides ;) Dec 31 18:52:59 Tofe: The Japanese keyboard layout on my phone uses a QWERTY layout and then displays kana and kanji suggestions as you type so it can transliterate them from the romaji input. It very well may be that the Chinese keyboard's set up the same way. Dec 31 18:53:15 KyleMaas_Laptop: I think it's using that qwerty keyboard as a input for selecting the correct chinese character Dec 31 18:53:36 There's a bit of C++ coupled to that keyboard, exceptionnally Dec 31 18:54:13 KyleMaas_Laptop: looks like we're describing the same thing, yes :) Dec 31 18:54:25 https://github.com/webOS-ports/webos-keyboard/blob/master/plugins/pinyin/src/pinyinadapter.cpp Dec 31 18:54:33 Tofe: It wouldn't surprise me. From what I understand of it, Chinese input is even more difficult to handle than Japanese input due to the lack of kana. Dec 31 18:55:29 I think it uses the word prediction line to propose chinese selections Dec 31 18:56:20 I never really looked into that chinese keyboard Dec 31 18:56:38 Tofe: So the Chinese keyboard is an almost direct port of something from Canonical? Dec 31 18:56:53 Tofe: I wonder if their Japanese keyboard would be as portable. Dec 31 18:57:12 KyleMaas_Laptop: the whole keyboard has been initiated from Ubuntu's, a couple of years ago Dec 31 18:57:20 Herrie, KyleMaas_Laptop: width of the left side panel in preware is different with every launch, and seems related to the length of funny phrase. Dec 31 18:57:45 Herrie, nizovn: Is that worth me filing a bug for? Dec 31 18:58:06 We have rewritten a good deal of the QML layout, though Dec 31 18:58:34 Tofe: Ah, the prediction comes from libpinyin. Dec 31 18:58:55 Yes; is it capable of handling japanse kana too ? Dec 31 18:59:39 Tofe: Not that I know of. But there are other libraries for that. Dec 31 18:59:54 Ah, yes, I see libkkc Dec 31 19:00:29 Well; it would certainly look like the chinese plugin Dec 31 19:00:35 afk for a bit. Dec 31 19:01:11 KyleMaas_Laptop: yes, imho it's a bug in preware app itself Dec 31 19:13:07 KyleMaas_Laptop: FYI, If you need any help, adding Japanese support to the keyboard is on my personal backlog. Dec 31 19:15:43 Andolamin: It shouldn't technically be too hard really ;) Dec 31 19:15:50 If we can piggyback from Ubuntu guys ;) Dec 31 19:15:54 QML part = easy ;) Dec 31 19:16:00 Even I can help with that ;) Dec 31 19:16:22 Yeah, QML part would practically match the existing English layout Dec 31 19:16:31 Not much to change, there. Dec 31 19:17:04 It would be nice to not have to include the IME in my LuneOS release of Japanese Study Tools, though. Dec 31 19:21:30 KyleMaas_Laptop: Looks like there was some work on a Japanese keyboard layout at https://bugs.launchpad.net/ubuntu-keyboard/+bug/1290031 Dec 31 19:26:10 It's flick input, instead of a Romaji IME, but would probably be easy to port over Dec 31 19:36:55 Tofe: You still around? Dec 31 19:37:09 Seems that my launchParams stuff only partially solved things :P Dec 31 19:41:47 I get an [object Object] for my launchParams in LNC, seems we need to do something else in luna-next to get it working properly :P Dec 31 19:42:44 Not sure to what extend Qt can do JSON and has maybe a different type we require instead of QString for launchParams? Dec 31 19:47:28 Or we need to do a conversion .toString somewhere? Dec 31 19:48:20 When I put the object Object in a var testObject in QML and then do testObject[0],testObject[1] etc I get "o", "b" "j" so that seems wrong anyway ;) Dec 31 19:59:36 Herrie: maybe there's a JSON.stringify missing? Dec 31 19:59:52 Tofe: When I add it in LNC it doesn't seem to do much Dec 31 20:00:03 Anyway I'm beginning the newyear's meal, so I won't be around much :p Dec 31 20:00:04 So I guess it's somewhere in luna-next where we'd need to do somthing Dec 31 20:00:10 Tofe: Same here :P Dec 31 20:00:23 Wife & MIl been preparing all day LOL Dec 31 20:00:36 I'll look at that first hour tomorrow -- which isn't the same hour as yours, probably ! Dec 31 20:01:30 LOL yeah little one doesn't care too much about new year Dec 31 20:01:43 Though he's been getting up after 6 lately which is more bearable for me ;) Dec 31 20:04:23 Herrie: Is this for the messaging? Dec 31 20:11:37 Herrie: com.palm.applicationManager defines launchParams as a string, so the app expects launchParams to come in as a string. So, I would expect that we should add JSON.stringify to https://goo.gl/GAKMxG? Dec 31 20:14:34 Andolamin: Yes it is Dec 31 20:14:39 But there are other cases too Dec 31 20:14:48 I think we need to deal with this in C++ instead Dec 31 20:14:55 And not in every app that makes a call Dec 31 20:15:48 Herrie: I don't disagree that handling it in the C++ is a bad route, but the apps should be using launchParams correctly, too, so we should fix those issues where we find them as well. Dec 31 20:16:25 Err, I don't think that came out right. It should definitely be handled in the C++ as well as in the apps. Dec 31 20:16:48 First party apps should use the services correctly. The first party services should assume third party developers will probably use them incorrectly. Dec 31 20:17:16 We probably should add something like this in luna-next: https://github.com/openwebos/luna-sysmgr/blob/1393f0af5dd8d9f0e9cc79627f4acb226f8c8d45/Src/lunaui/notifications/BannerMessageHandler.cpp#L449 Dec 31 20:18:20 Just I really suck at C++ :P Dec 31 20:19:23 Yeah - I agree. I would do it but I'm working on my Chromebook right now, so C++ work is out. Can you link me to the source for org.webosports.notifications Dec 31 20:19:24 ? Dec 31 20:20:02 Andolamin: https://github.com/webOS-ports/luna-next/tree/master/plugins/shell/notifications Dec 31 20:20:05 It's in there ;) Dec 31 20:22:23 It should probably come somewhere after: https://github.com/webOS-ports/luna-next/blob/master/plugins/shell/notifications/notificationmanager.cpp#L90 Dec 31 20:24:28 Looking at that source, it looks like it expects a string for launchParams as well. I went ahead and opened a pull request to add JSON.stringify for the messaging service Dec 31 20:25:51 The "[object Object]" you're getting is probably because Qt is trying to be smart and cast the Object to the QString it expects, which probably involves toString() instead of JSON.stringify Dec 31 20:26:19 Andolamin: Probably yes Dec 31 20:34:53 Just pushed file to device, lets see what it does Dec 31 20:37:30 Andolamin; That looks better: Herrie arguments[0]{"objectName":"","ownerId":"org.webosports.service.messaging","replacesId":1,"launchId":"org.webosports.app.messaging","launchParams":"{\"threadId\":\"JaXYm5NzuGV\"}","title":"+31652044684","body":"Test 6","iconUrl":{},"soundClass":"","soundFile":{},"duration":-1,"doNotSuppress":false,"priority":0,"expireTimeout":5,"timestamp":"2015-12-10T Dec 31 20:37:30 13:34:59.786Z"} Dec 31 20:37:52 Still doesn't work in the app though ;) I.e. still doesn't open the thread Dec 31 20:38:27 That might be due to the escaping ? Dec 31 20:39:08 I wouldn't think so. Can you send me the ls-monitor logs for com.palm.applicationManager when it launches the app? Dec 31 20:40:28 Layout is a bit broken but wlel: https://bpaste.net/show/e3406924cbe2 Dec 31 20:41:31 It's only a dozen or so lines Dec 31 20:41:45 Layout for ls-monitor is always broken. Or I at least haven't figured out how to get it to save cleanly. Dec 31 20:44:07 That looks right... Got to be something simple missing... I'll look into it. Dec 31 20:44:37 Can you post the luna-send command you're using to generate the notification? Dec 31 20:44:48 Or are you just sending a text to yourself? Dec 31 20:48:46 Andolamin: I'm sending text to myself :P Dec 31 20:49:20 But you could try this one: luna-send -m org.webosports.service.update -n 1 palm://org.webosports.notifications/create '{"ownerId": "org.webosports.service.update", "launchId": "org.webosports.app.settings", "launchParams": {"page": "SystemUpdates", "needUpdate": true, "changesSinceLast": "Test" }, "title": "System update available", "body": "New version body", "iconUrl": "", "soundClass": Dec 31 20:49:21 "","soundFile": "file:///usr/palm/sounds/alert.wav","duration": -1,"doNotSuppress": false,"expireTimeout": 5}' Dec 31 20:49:37 Just the problem will be the launchParams due to luna-next ;) Dec 31 20:51:37 Herrie: Can you send me the results of luna-send -n 1 -f -a org.webosports.messaging luna://com.palm.db/find '{"query":{"from":"com.palm.chatthread:1"},"count":false,"watch":true,"subscribe":true}' Dec 31 20:53:09 https://bpaste.net/show/d5b74251fb46 Dec 31 20:58:28 Herrie: Ok, I'm at a loss, then. Works fine for me with my local generated IPK. Can you try again with the messaging IPK I just emailed you? Dec 31 21:22:06 IPK works Dec 31 21:23:32 Opens app & thread :D **** ENDING LOGGING AT Fri Jan 01 02:59:58 2016