**** BEGIN LOGGING AT Wed Feb 28 03:00:02 2018
Feb 28 05:13:54 <Herrie|Laptop> Morning!
Feb 28 05:13:58 <Herrie|Laptop> bshah: You around?
Feb 28 05:33:56 <bshah> Morning..
Feb 28 05:34:01 <bshah> yeah I am around
Feb 28 05:39:15 <Herrie> bshah: I'm getting close with my mido
Feb 28 05:39:21 <Herrie> I sent some PR's you might have seen
Feb 28 05:39:39 <Herrie> I was missing ip, iptables and ip6tables in my halium android bits
Feb 28 05:39:42 <bshah> not really... I've messages piled up in two days
Feb 28 05:39:49 <Herrie> So added those now
Feb 28 05:39:50 <bshah> or rather 1 day
Feb 28 05:40:00 <bshah> I'll get to it eventually though
Feb 28 05:40:05 <Herrie> I know :)
Feb 28 05:40:24 <Herrie> Still don't have my sensors working though :S
Feb 28 05:40:32 <Herrie> Bit at a loss here on what I could still do
Feb 28 05:41:13 <bshah> is qti process running?
Feb 28 05:41:27 <bshah> (typically in /vendor/bin/qti or something)
Feb 28 05:46:18 <Herrie|Laptop> Seems so: https://bpaste.net/show/cb7f1bf1128e
Feb 28 05:48:40 <bshah> hm
Feb 28 05:49:06 <bshah> do you get any output in logcat when you run test_sensors?
Feb 28 05:49:19 <bshah> and also is sensorservice running?
Feb 28 05:49:39 <Herrie|Laptop> Yes it is
Feb 28 05:50:02 <Herrie|Laptop> However I do have a lot of the following in logcat: NetlinkListener: recvmsg failed (I/O error)
Feb 28 05:50:12 <Herrie|Laptop> Not sure what causes that and if it's harmful
Feb 28 05:50:32 <Herrie|Laptop> I have this in logcat: Sensors : sns_debug_mr.c(366):Sensors DIAG Init: Waiting for diag service timed out
Feb 28 05:50:39 <Herrie|Laptop> And Sensors : sns_main.c(447):Timeout waiting for SMGR service. Exit sensors daemon!
Feb 28 05:50:50 <Herrie|Laptop> Could be I need to add some more service to init.rc but not sure which one
Feb 28 05:51:53 <Herrie|Laptop> Already updated android_hardware_libhardware for sensor 1.4 api just in case
Feb 28 05:51:55 <Herrie|Laptop> But no luck
Feb 28 05:52:43 <bshah> the both of sensors logcat message sounds important..
Feb 28 05:52:49 <bshah> but no clue what they means yet
Feb 28 05:53:00 <bshah> I'll try to look it up bit later
Feb 28 05:56:14 <Herrie|Laptop> In my strace for test_sensors I also have openat(AT_FDCWD, "/etc/qmi_fw.conf", O_RDONLY) = -1 ENOENT (No such file or directory)
Feb 28 05:56:29 <Herrie|Laptop> Though qmi_fw.conf doesn't seem to be provided for my target
Feb 28 06:11:36 <Herrie|Laptop> Tofe: FYI the persist bind-mount solved my WLAN firmware issues!
Feb 28 06:37:47 <Herrie|Laptop> bshah: My oFono also isn't happy (using 1.19 from Mer guys from 4-5 months ago). Though I suspect it might be init? On Halium 5.1 you have https://github.com/Halium/android_system_core/blob/ubp-5.1/rootdir/init.rc#L572
Feb 28 06:37:57 <Herrie|Laptop> However there's no rild in Halium 7.1 init.rc
Feb 28 06:38:26 <bshah> in halium 7.1 rild is in /system/etc/init/rild.rc IIRC
Feb 28 06:38:55 <Herrie|Laptop> Ah ok
Feb 28 06:39:04 <Herrie|Laptop> It looks more or less OK but doesn't work :S
Feb 28 06:39:05 <Herrie|Laptop> Feb 12 03:53:54 mido ofonod[3009]: RILDEV detected modem type ril, 2 SIM slot(s)
Feb 28 06:39:10 <Herrie|Laptop> Feb 12 03:53:54 mido ofonod[3009]: Using /dev/socket/rild as socket for slot 0.
Feb 28 06:39:30 <Herrie|Laptop> Then followed by Feb 12 03:53:54 mido ofonod[3009]: create_ril: can't connect to RILD: Connection refused (111) and Feb 12 03:53:54 mido ofonod[3009]: g_ril_new() failed to create modem!
Feb 28 06:39:38 <Herrie|Laptop> I guess it could be permissions somehow
Feb 28 06:41:10 <Herrie|Laptop> I can see the sockets got created
Feb 28 06:59:14 <bshah> logcat -b radio please
Feb 28 07:12:09 <Herrie|Laptop> https://bpaste.net/show/bbc213c33cf0
Feb 28 07:13:11 <Herrie|Laptop> bshah: ^
Feb 28 07:57:16 <Tofe> Morning
Feb 28 08:12:00 <Herrie|Laptop> Tofe: Morning!
Feb 28 08:12:41 <Herrie|Laptop> Tofe: YGM
Feb 28 08:16:24 <Herrie|Laptop> I wasn't sure about some of the android bits
Feb 28 08:32:46 <Tofe> Herrie|Laptop: I integrated your changes; but why not directly editing the text ? :)
Feb 28 08:34:57 <Tofe> I'll propose the questions to #halium
Feb 28 08:36:58 <Herrie|Laptop> Tofe: Well it doesn't really have track changes feature? Not sure you would be happy with me directly changing
Feb 28 08:37:05 <Herrie|Laptop> Might be good to add it to their github
Feb 28 08:37:07 <Herrie|Laptop> For discussion
Feb 28 08:38:37 <Herrie|Laptop> Tofe: I mean here https://github.com/Halium/projectmanagement/issues
Feb 28 08:48:21 <Tofe> Herrie|Laptop: that's a good idea
Feb 28 08:48:36 <Herrie|Laptop> Tofe: That's easier for discussion
Feb 28 09:05:37 <Tofe> done https://github.com/Halium/projectmanagement/issues/61
Feb 28 09:06:23 <Herrie|Laptop> Tofe: Great
Feb 28 10:22:18 <Herrie|Laptop> Tofe: Seems that our patches in android_luneos_hal are prone to error like you already pointed out
Feb 28 10:22:25 <Herrie|Laptop> If upstream changes, patches break
Feb 28 10:22:33 <Herrie|Laptop> This happened with my mido patches for example
Feb 28 10:28:01 <Herrie|Laptop> I think the repo command doesn't allow to specify a specific commit, only tags? Though this seems to suggest you could pass a commit ID as well with -b or even in the manifest: https://stackoverflow.com/questions/10818758/repo-init-a-particular-commit
Feb 28 10:28:13 <Herrie|Laptop> I guess I'd need to test that
Feb 28 10:31:29 <Tofe> yes this patching is far from ideal
Feb 28 10:31:44 <Herrie|Laptop> If specifying commitid works, I suggest we do that
Feb 28 10:31:51 <Herrie|Laptop> We anyway mainly patch TheMuppets
Feb 28 10:32:27 <Herrie|Laptop> Ah wait we also patch device....
Feb 28 10:37:22 <Tofe> Yes, we remove the background images and so on, which make the build fail
Feb 28 10:42:47 <Herrie|Laptop> Tofe: It doesn't on 7.1
Feb 28 14:45:21 <Herrie|Laptop> JaMa: Hi :)
Feb 28 14:45:47 <Herrie|Laptop> I added https://github.com/webOS-ports/meta-webos-ports/blob/pyro/meta-luneui/recipes-qt/qt5/qtbase/0002-Add-additional-Adreno-targets-for-needsWorkaround.patch but you might want to have it in your meta-qt5 instead
Feb 28 14:45:59 <Herrie|Laptop> Since it's unlikely it'll be fixed upstream for 5.9/5.10
Feb 28 14:46:20 <bshah> it's bug fix, it can be included in 5.10.1
Feb 28 14:46:26 <bshah> or .2
Feb 28 14:46:40 <Herrie|Laptop> bshah: Well, but we're comfortable on 5.9 for now ;)
Feb 28 14:47:30 <Herrie|Laptop> And there are others using meta-qt5 so it would be good if they don't need to reinvent the wheel :P
Feb 28 14:47:42 <bshah> hm right
Feb 28 14:52:08 <Herrie|Laptop> bshah: Had any idea on my logcat for radio?
Feb 28 15:08:52 <JaMa> Herrie|Laptop: I'll will wait for upstream
Feb 28 15:09:13 <Herrie|Laptop> JaMa: OK
Feb 28 15:09:14 <Herrie|Laptop> It
Feb 28 15:09:20 <Herrie|Laptop> I submitted it there as well
Feb 28 15:10:00 <Herrie|Laptop> https://codereview.qt-project.org/#/c/221471/
Feb 28 16:13:10 <Herrie|Laptop> Tofe: Seems that there's a new electrablue kernel for mido, v10 vs v8 I'm using now. Piggz did some fixes in his eb v8 that might be the cause of some of my graphics glitches (or not). I'll give the eb v10 kernel a try to see if that works any better
Feb 28 16:13:44 <Herrie|Laptop> And I guess I'll upstream some of our patches to the electrablu kernel maintainer (i.e. export si_swapinfo, gcc patches etc)
**** BEGIN LOGGING AT Wed Feb 28 16:15:33 2018
Feb 28 16:32:00 <Herrie|Laptop> I.e. Piggz did a hacky fix for graphics with https://github.com/Herrie82/android_kernel_xiaomi_msm8953/commit/bb9f3475e29e4fab404dbc3c634ce9b76f284538
Feb 28 16:33:09 <Herrie|Laptop> Seems there's 1,5 page of commits to video driver since eb8
Feb 28 16:33:16 <Herrie|Laptop> So worth a try to see if it solves stuff
**** ENDING LOGGING AT Thu Mar 01 02:59:59 2018