Wednesday, 2020-10-07

*** rubdos_ is now known as rubdos11:29
T42<edp_17> @elros34: Are you aware of any bluetooth related changes for 3.4? My recent 3.3 build the bluetooth (also) stopped working. I have checked my notes how we solved this before and it seems nothing changed in there. The log (verbose with -d) is here:
T42<elros34> @edp_17 no, nothing comes to my mind13:12
T42<edp_17> Thanks.13:14
T42<elros34> IIRC you used bluetooth-rfkill-event so at least you should have some output from it13:17
T42<edp_17> The other strange thing is that on the previous build I was able to run a desktop distro in lxc. On this one, the file /opt/bin/Xwayland has one line 'Not found' (I think this should be a binary or a script at least).13:18
T42<edp_17> Yeah, I am using that bluetooth-rfkill-event .13:18
mal@edp_17 maybe test setting Channels = 1 in [GATT] section of /etc/bluez5/bluetooth/main.conf13:18
mallike here
T42<elros34> @edp_17 I don't see any output from it in your journal13:19
T42<edp_17> Thanks mal, I try that.13:24
T42<edp_17> @elros34: You are right. None of the bluetooth-rfkill* package is installed!?!?13:25
malbut you said also 3.3.0 failed for you so probably some other issue13:25
T42<edp_17> No, it finally we made it working on 3.3 (few months ago) and yesterday I created a new 3.3 build to add some extra stuff in there and bluetooth, gps, sensors, all gone. Now I am trying to make them working again to be able to build a 3.3 image that works as it worked before.13:27
malwas 3.4 build similar to that latest 3.3 build?13:28
T42<edp_17> I never built 3.4 (yet)13:28
T42<edp_17> I didn't want to move to 3.4 until all what we fixed is working fine on a 3.3 image.13:29
malI thought you had somehow tested 3.4, the stuff I mentioned is only for 3.413:29
T42<edp_17> I see, I remove it then. Thanks.13:29
malonly for some devices and should not be used unless needed13:30
T42<edp_17> Okay, thanks. I add it to my notes. :)13:30
T42<edp_17> None of the 'broadcom-bluetooth-bluez5' and 'bluetooth-rfkill-event-hciattach' packages were included in the build. However they do exist in droid-local-repo and were built in june.13:35
T42<edp_17> I have installed both on device and now bluetooth works. How can I include them into the build? (they were there, I am sure)13:38
deathmistmal: sorry that I keep bugging you about this but I'd really like to play around with it; any update on the W.I.P hybris-17.1 sources you were going to push somewhere?13:39
malah, forgot about that again13:40
malalso I hate pushing untested probably not working code13:41
T42<edp_17> @elros34: I spoke too soon. Bt can be paired but the sound is not forwarded to the bt device. (I don't remember that I had this issue on this device.)13:43
deathmistmal: you could put them in one repo in different folders, label repo (prob under own account) as untested experimental and probably not working and call it a day :p13:44
T42<Anton %lastname%> Hello everyone, I'd wish to continue porting sfos to my device, but couldn't help to notice rolling out. Considering I haven't gotten to fix a few hardware parts, should I switch to it, or rather stay at
mal3.4.0.22 is not yet publicly available14:31
malwhat issues do you have on the device?14:32
T42<Anton %lastname%> At the time of my leaving I still had sensors dead, camera unconfigured and fp untouched, everything else seemed fine14:34
malmaybe you had too new sensor middleware package built14:35
malor some configuration missing14:36
T42<Anton %lastname%> Not quite sure. I can recall trying to hook up hw-settings.ini to no avail. I'll try it again nevertheless. Also, could someone throw me a link to a shared notepad with common troubles, I lost it long ago14:41
malwhich version of hybris-libsensorfw-qt5-* package do you have?14:43
mal3.3.0.16 needs 0.11.9, newer version don't work14:43
T42<edp_17> Anton : I had problem with sensors on recently. I needed to downgrade sensorfw to
T42<edp_17> For me that was this commit 89ed1ef63e080b1097477f4a687201ce3683c22214:44
T42<Anton %lastname%> Really can't remember. I'll keep that in mind though14:44
T42<edp_17> Anton : Try what I did, it helped me: 1. git fetch 89ed1ef63e080b1097477f4a687201ce3683c22214:45
T42<edp_17> 2. git reset --hard 89ed1ef63e080b1097477f4a687201ce3683c22214:45
T42<edp_17> 3. (within sdk) rpm/dhd/helpers/ -D -o -b hybris/mw/sensorfw -s rpm/sensorfw-qt5-hybris.spec14:45
T42<edp_17> 4. install the packages to device14:45
malnumber 3 depends on android base version probably i.e. hybris vs binder14:46
T42<edp_17> mal: Thanks! 👍 I was not aware of that.14:49
T42<Anton %lastname%> I think my device should be using binder, it's hybris-1614:50
malby default builds binder version for android 9 or newer so hybris-16.0 uses that also14:56

Generated by 2.17.1 by Marius Gedminas - find it at!