Sunday, 2021-08-29

T42<elros34> not sure, do you still have pgrep -af bluetoothd running after first bt turn off?00:27
T42<TheVancedGamer> Hi, I'm trying to port Sailfish OS to my Huawei P8 Lite, I've installed the HABUILD_SDK but trying to use sudo in it gives this error:05:02
T42<TheVancedGamer> sudo: account validation failure, is your account locked?05:02
T42<TheVancedGamer> fyi, I'm on the focal sdk05:02
T42<TheVancedGamer> How can I overcome this? The trusty sdk is too old for my usage05:03
T42<TheVancedGamer> Did somebody have this sort of error?05:05
T42<eriki73> @fredldotme , I have not tested that yet and I haven't packaged these changes yet only tried them on-device. After packaging them, I'll push my files on GitHub.06:03
T42<gischpelino> brewdog, very nice. 🍻 (re @adampigg: )07:43
T42<edp_17> @elros34 : I haven't checked bluetoothd but I will and let you know.08:04
T42<elros34> probably that is not the issue. Maybe you could check whether this always work: bt on/off, restart rfkill and again bt on/off, restart... If that fails sometimes then maybe patcher should be started only once per boot08:12
T42<edp_17> 'pgrep -af bluetoothd' returns with '1837 /usr/bin/bluetoothd -n' when bt off, when it is turned on and when it is off again.08:15
T42<edp_17> Okay, here it is how it "works" now:08:27
T42<edp_17> 1. tap on Bluetooth in Settings (BT turns on)08:27
T42<edp_17> 2. tap on Bluetooth in Settings (BT turns off)08:27
T42<edp_17> 3. Restart rfkill08:27
T42<edp_17> 4. tap on Bluetooth in Settings (blinking - should turn BT on)08:28
T42<edp_17> 5. tap on Bluetooth in Settings (blinking - shuld turn BT off)08:28
T42<edp_17> 6. Restart rfkill08:28
T42<edp_17> 7. tap on Bluetooth in Settings (BT turns on)08:28
T42<edp_17> So it works similarly when I killed patchram. I need to restart twice to able to turn BT on.08:28
T42<elros34> hmm so assuming logs looks similar for every on/off attempt then for me it looks like problem is with brcm_patchram_plus itself08:32
T42<elros34> @edp_17 do you have by any chance your bluetooth built as module?08:45
T42<edp_17> I am not sure but will try later.08:52
T42<elros34> Just asking it will not automatically help, just wondering whether unloading/loading module would help, sorry I am out of ideas08:55
T42<elros34> another idea for workaround is adding to settings exec_timeout=3 or 5 (seconds)09:54
vgnshlvnzHi I am trying to port Sailfish OS for Nexus 5X10:59
vgnshlvnzI am following this document
vgnshlvnzin chapter 6 I am unable to test the sb211:00
vgnshlvnzit says invalid target specified11:00
T42<eriki73> @fredldotme , I tested the call audio volume control. It stays on max vol...11:18
T42<eriki73> I guess that is the same as on Droidian and UT?11:18
T42<eugenio_g7> droidian doesn't support call audio volume yet so no bug there :D :D11:25
malvgnshlvnz: are you sure you named the targets correctly, show output "sdk-assistant list"12:04
vgnshlvnzI got it already, it goes by this: the sdk-assistant's output is the target12:05
vgnshlvnzdid some googling to find out12:05
T42<eriki73> I tried building wifi inbuilt to my kernel again... It works! It seems even more stable...14:09
T42<TheVancedGamer> good job14:09
T42<TheVancedGamer> good job! (edited)14:09
T42<eriki73> I am now pushing the kernel to github.14:16
T42<eriki73> @TheVancedGamer14:16
T42<TheVancedGamer> alright14:16
T42<eriki73> @TheVancedGamer14:16
T42<TheVancedGamer> it's empty14:17
T42<eriki73> I know, I said I am pushing...14:18
T42<TheVancedGamer> ah ok14:18
T42<eriki73> The kernel sources are quite large...14:19
T42<TheVancedGamer> well one way to fight that is to fork the original kernel repo and push your changes14:19
T42<TheVancedGamer> that way you just have to push your changes14:19
T42<eriki73> Doesn't look good, it got stuck...14:19
T42<TheVancedGamer> yeah limit14:20
T42<TheVancedGamer> only some organizations have bigger push limits14:20
T42<TheVancedGamer> @eriki73 fork a kernel and push your changes14:24
T42<eriki73> @TheVancedGamer ,
T42<TheVancedGamer> That's it14:30
T42<adampigg> @eriki73 what was the wifi fix, be good to have details in the logs14:43
T42<eriki73> Forwarded from erfanoabdi: also one hack14:44
T42<eriki73> Forwarded from erfanoabdi: remove this line14:44
T42<eriki73> Forwarded from erfanoabdi:
T42<eriki73> Forwarded from erfanoabdi: oh i see 2 wait_for_props there14:44
T42<eriki73> Forwarded from erfanoabdi: getprop vendor.qcom.time.set14:44
T42<eriki73> getprop vendor.sys.listeners.registered14:44
T42<eriki73> Forwarded from erfanoabdi: remove vendor.qcom.time.set line too14:44
T42<eriki73> Forwarded from erfanoabdi: Line 24714:44
T42<eriki73> @adampigg14:44
T42<eriki73> That did fix modem , wifi and sound...14:45
T42<elros34> so bunch of mkdir/chown which were already started if you booted previosuly lineage?14:51
T42<elros34> or just removing wait_for_props was critical?14:55
rinigusdoes someone remember where is fstab generated as it is on the device? for LVM (aka official) ports?16:54
T42<eriki73> Forwarded from eriki73:
T42<eriki73> Can you see anything about sensors here? I do not know anything about sensor stuff...17:37
T42<eriki73> Got them working now...18:22
T42<edp_17> I've tried this but unfortunately none of the values helped. :-( (re @elros34: another idea for wor...)18:49
T42<elros34> so patcher also stuck even after 3/5s timeout?18:58
T42<elros34> unless this parameter is not what I think it is19:04
T42<edp_17> Yes.19:07
T42<elros34> if i get code right after second bt on you should get "timeout exceeded, killing it"19:21

Generated by 2.17.1 by Marius Gedminas - find it at!