Thursday, 2022-05-05

T42<MargaretMWilliam> Forwarded from Good News: 𝐂𝐫𝐲𝐩𝐭𝐨 𝐜𝐮𝐫𝐫𝐞𝐧𝐜𝐲 𝐦𝐚𝐫𝐤𝐞𝐭𝐢𝐧𝐠 𝐡𝐚𝐬 𝐜𝐡𝐚𝐧𝐠𝐞𝐝 𝐦𝐲 𝐥𝐢𝐟𝐞 𝐈 𝐢𝐧𝐯𝐞𝐬𝐭𝐞𝐝 £4,5𝟎𝟎 𝐢𝐧 𝐣𝐮𝐬𝐭 5 𝐝𝐚𝐲𝐬 𝐨𝐟 𝐭𝐫𝐚𝐝𝐢𝐧𝐠 𝐈 𝐫𝐞𝐚𝐥𝐢𝐳𝐞𝐝 £51,60𝟎 𝐚𝐧𝐝 𝐞𝐱𝐭𝐫𝐚 𝐛𝐨𝐧𝐮𝐬07:43
voidanix[m]how does one check if sensors are present in kernel? chip is sm8150/snapdragon 85509:01
voidanix[m]sensor multihal 2.1 is reporting 0 sensors, sensorfwd goes crazy because of it09:02
*** ggabriel is now known as Guest19718:52
voidanix[m]nvm fixed my sensors issue by flashing stock android to create /persist/sensors/registry20:09
T42<edp_17> Thanks. I think the adaptation-community-i9100 is correct in in Jolla-@RELEASE@-i9100-@ARCH@.ks file. I have this in there:20:47
T42<edp_17> repo --name=adaptation-community-i9100-@RELEASE@ --baseurl= (re @elros34: @edp_17 not sure wha...)20:47
T42<edp_17> When added only what you suggested, I got this error:
T42<edp_17> So it looks like droid-config-i9100-bluez4 is the missing one.20:50
T42<edp_17> Although, this is weird because I have "droid-config-i9100-bluez4-1+sfos44.20220504054700.fba95b4-1.11.1.jolla.armv7hl.rpm" package on OBS repo.20:51
Solrac[m]Hello, is anyone maintaining the one plus 5 port?20:51
T42<elros34> @edp_17 looks like not missing but it can't be installed similar to previous package. Maybe missing bluez4?21:08
T42<edp_17> Missing bluez4 in where?21:10
T42<edp_17> I meant, how do you mean? :)21:11
T42<edp_17> I've checked _service file in droid-config-i9100 and it point the correct commit.21:12
T42<edp_17> *points21:13
T42<edp_17> @elros34 : I think found it.21:21
T42<elros34> I meant that if bluez4 is not provided anymore and droid-config*bluez requires it then this  can cause your issue. I am just guessing, my obs repo stuck in "dod" so didn't check 4.4.0 yet22:06
malbluez4 is still in 4.4.0, but will be removed after that, devices which need it will need to either build their own or use the backported kernel drivers with bluez522:29
malwhen building for 4.4.0 anyone needing bluez4 need to to be careful not to update droid-config submodule to too new version which has bluez4 config removed22:30
T42<edp_17> Yeah, I've just done that. :)22:32
malusing backported drivers with kernel version 3.4 is quite easy in case that is preferred later, I have been using those on fp2 for years now22:33
malwith those drivers bluez5 can be used with 3.4 kernel22:33
T42<edp_17> @elros34 : The issue was that I updated droid-config submodule and tried to hard reset back to the previous version but seemingly something went wrong. I'll try checkout the last version that I used to build 4.3 and re-try.22:33
T42<edp_17> mal: This device has a kernel 3.0 :)22:34
maloh, not sure how easy backporting the drivers would be for that22:34
malthis is the submodule revision I use on 4.4.0 fp2
T42<elros34> this commit "should" bring bluez4 back on top of latest submodule: You can't blindly apply it. It doesn't include audio.conf which I have added earlier, have some device specific changes at least for pulseaudio quirks and maybe something else which I do not remember22:40
T42<edp_17> Can I use the bluez4 branch from github?
T42<edp_17> Or I should go back to the last commit before the bluez4 removal. To this: 1d38d62d0223477a9fb630795a6a029eaffa629822:51
T42<edp_17> I think the latter because the bluez4 branch is a bit old. The last commit happened in Dec 2016.22:52
malthe commit I linked earlier is the one used on official devices in 4.4.0 release and it still had bluez4 configs22:58
T42<edp_17> Thanks. I'll try this.23:15
T42<edp_17> Still no luck. Now it is moaning about missing 'patterns-sailfish-device-adaptation-i9100' package:
T42<edp_17> I've done for now, will continue later.23:49

Generated by 2.17.1 by Marius Gedminas - find it at!