**** BEGIN LOGGING AT Sat Feb 24 03:00:01 2018 Feb 24 07:49:46 Herrie|2: it does work for hammerhead; and it tries (and fails silently) for tenderloin Feb 24 07:50:23 Herrie|2: check the content of tmp-glibc/work/mido-webos-linux-gnueabi/android-tools-conf/1.0-r0/android-gadget-setup* Feb 24 08:58:52 Tofe: IPK looks OK now Feb 24 08:58:59 Could be I had wrong artifacts locally Feb 24 09:01:56 ok, well, good Feb 24 11:12:15 Tofe: So far untested, but shouldn't cause havoc: https://github.com/shr-distribution/meta-smartphone/pull/59/files Feb 24 11:12:39 I noticed that Mer, UBPorts & Halium prefix the device specific udev rules with 70- Feb 24 11:12:58 This way they're always loaded with the same priority and not depending on their name. Feb 24 11:13:06 Thought this made sense so applied it here too Feb 24 11:13:35 Updated Tenderloin & Hammerhead rules based on our sources Feb 24 11:13:52 Seems Hammerhead ones were never updated and TP only had one for the touchscreen Feb 24 11:14:02 Next step is to add the users & groups that we're missing Feb 24 11:14:39 Of which I'm not sure we need the one for the touchscreen, we should test that Feb 24 11:14:41 Could be legacy Feb 24 12:06:22 ok, yes, sounds like a good idea Feb 24 15:26:55 Herrie|Laptop: I think I'll give up on bluetooth for TP... Feb 24 15:28:20 We would need to update tenderloin-bluetooth-utilities, and that means pick up and remix new sources from Android 5.1 and bluez5. However, both have changed quite a lot. Feb 24 15:37:03 Tofe: OK I guess it doesn't hurt to stash the work you've done already somewhere Feb 24 15:37:10 So someone could pick it up Feb 24 15:37:53 Yup, will do; it's mainly the kernel backport though, so not necessarily related to blue5 migration Feb 24 16:02:01 done: https://github.com/Tofee/meta-smartphone-1/commit/df93a9448d0550fc6be776f66ccf5473b89c8984 Feb 24 16:04:12 Tofe: Can you check if power menu works on your hammerhead? Feb 24 16:04:24 It doesn't seem to work on mine, but could be my local build somehow Feb 24 16:04:39 it did two days ago Feb 24 16:05:03 but, sometimes I have to tap the screen once or twice to make it appear Feb 24 16:05:36 I don't know why, maybe the event loop isn't checked otherwise, due to some bug Feb 24 16:06:48 Tofe: OK Feb 24 16:06:53 Could be just my build somehow Feb 24 16:06:56 It's quite franken Feb 24 16:07:09 Once JaMa merges meta-smartphone will clean up layers Feb 24 16:07:44 :) Feb 24 21:26:06 elvispre: Didn't forget about you, here's a new one to try: http://www.vve-goudenleeuw.nl/luneos-dev-package-onyx-20180224194346-0-0.zip Feb 24 22:02:40 Herrie|2: Oh, I didn't think you had. I have been distracted setting up my new PC in several ways anyway. Feb 24 22:04:13 Herrie|2: I'll give that a try now. BTW, building from the current sources makes an image that does not boot with adb available. Is everything configured? Feb 24 22:06:35 elvispre: I tried what I could on this one Feb 24 22:08:06 No guarantees but we'll see Feb 24 22:08:20 We'll see shortly... :) Feb 24 22:13:22 Herrie|Laptop: I am in with adb shell. What do you hope to see? Feb 24 22:15:13 Herrie|Laptop: Neither /firmware nor /persist are mounted still. Feb 24 22:20:30 Herrie|Laptop: Boot log: https://pastebin.com/YS4vb6cj Feb 24 22:30:49 Both /firmware and /persist mount fine if I issue the commands in adb shell. **** ENDING LOGGING AT Sun Feb 25 03:00:04 2018