| T42 | <edp_17> @elros34 : Yes, correct. After fresh reboot (I tried to comment what was happening): https://paste.ubuntu.com/p/rZtdYmFTqQ/ | 06:12 |
|---|---|---|
| T42 | <edp_17> I hope this is the right place but I've defined the exec_timeout in /etc/firmware/bcm4330b1.conf: https://paste.ubuntu.com/p/tf9wNw5jYz/ | 06:17 |
| poetaster | piggz: should I be sideloading that sailfishos-gs290-release-4.1.0.24-devel-20210714.zip ? | 07:20 |
| T42 | <eriki73> poetaster: on that version lipstick seems to crash... But yes that is a sideloadable zip... | 07:23 |
| poetaster | piggz: thanks. ok I'll wait for the next run. | 07:24 |
| T42 | <eriki73> poetaster: build 20210826 works better but has no audio... | 07:24 |
| poetaster | eriki73: thanks | 07:24 |
| T42 | <eriki73> poetaster: And I am obviously not piggz but I know as I tried these builds out... | 07:25 |
| poetaster | eriki73: thanks ... I've been having no luck with installing those. just reverting to a Volla install now. | 07:26 |
| T42 | <eriki73> poetaster: from which android version is your vendor from? | 07:27 |
| poetaster | eriki73: was 10 (it's a GS290, not a volla). | 07:27 |
| T42 | <eriki73> poetaster: I had los17 and it worked... | 07:29 |
| T42 | <eriki73> poetaster: how does it fail? | 07:29 |
| T42 | <amyosx> Alfred has gone insane fixing it (re @eriki73: @fredldotme , I test...) | 07:30 |
| poetaster | I had eos installed (well, didn't boot to test if it was ok) and sideloading generated an error that it was'nt the correct device | 07:30 |
| T42 | <elros34> @edp_17 yes, this is right file as you can see in logs brcm_patchram_plus is killed if it can not finish withing 5 seconds. Something is different compared to your previous report when you just restarted rfkill service twice and bt started working. You need to find the difference, maybe compare udevadm monitor, maybe on timout some clean up is needed | 07:31 |
| T42 | <eriki73> poetaster: a wrong device? It probably expected Volla or maybe lineage would work... | 07:32 |
| poetaster | poetaster: nah something seemed to be missing from flashing eos. the device that's expected by piggz script is GS290 (it's the string he greps for) | 07:36 |
| poetaster | eriki73: I went through https://doc.e.foundation/pages/install_e_GS290_linux and https://doc.e.foundation/devices/GS290/install but that seemed to end in a boot loop | 07:37 |
| poetaster | eriki73: how did you install lineage 17? | 07:37 |
| T42 | <eriki73> https://build.lolinet.com/file/lineage/GS290/ | 07:39 |
| T42 | <eriki73> poetaster: there are images you can sideload... | 07:39 |
| poetaster | eriki73: a 17 image, then boot test, unlock, etc before the sfos install? | 07:43 |
| T42 | <eriki73> poetaster: yes | 07:47 |
| poetaster | eriki73: I'm actually impressed that ubports always manages to restore the phone to a know state. | 07:47 |
| T42 | <eriki73> Btw, any one knows how can I package custom bluebinder_post.sh? | 07:49 |
| T42 | <eriki73> Here is my current packaging which throws an error (conflict) https://github.com/sailfish-on-sargo/droid-config-sargo | 07:51 |
| vgnshlvnz | hi i am getting following error when running rpm/dhd/helpers/build_packages.sh --config | 07:56 |
| vgnshlvnz | mv: cannot stat 'RPMS/*.rpm': No such file or directory | 07:56 |
| vgnshlvnz | * Building successful, adding packages to repo | 07:56 |
| vgnshlvnz | warning: Macro expanded in comment on line 151: %{name} contains ssu.ini file which is needed to build kickstarts | 07:56 |
| vgnshlvnz | error: Unable to open patterns/patterns-sailfish-device-configuration-bullhead.inc: No such file or directory | 07:56 |
| vgnshlvnz | error: query of specfile /home/vgnshlvnz/hadk/hybris/droid-configs/rpm/droid-config-bullhead.spec failed, can't parse | 07:56 |
| vgnshlvnz | NOTICE: No tags describe the HEAD, will not fix package version. | 07:56 |
| vgnshlvnz | warning: Macro expanded in comment on line 151: %{name} contains ssu.ini file which is needed to build kickstarts | 07:56 |
| vgnshlvnz | error: Unable to open patterns/patterns-sailfish-device-configuration-bullhead.inc: No such file or directory | 07:56 |
| vgnshlvnz | error: query of specfile /home/vgnshlvnz/hadk/hybris/droid-configs/rpm/droid-config-bullhead.spec failed, can't parse | 07:56 |
| vgnshlvnz | warning: Macro expanded in comment on line 151: %{name} contains ssu.ini file which is needed to build kickstarts | 07:56 |
| vgnshlvnz | error: Unable to open patterns/patterns-sailfish-device-configuration-bullhead.inc: No such file or directory | 07:56 |
| vgnshlvnz | Building target platforms: armv7hl-meego-linux | 07:57 |
| vgnshlvnz | Building for target armv7hl-meego-linux | 07:57 |
| vgnshlvnz | No journal files were found. | 07:57 |
| vgnshlvnz | Failed to seek to cursor: Invalid argument | 07:57 |
| vgnshlvnz | mv: cannot stat 'RPMS.saved/*.rpm': No such file or directory | 07:57 |
| vgnshlvnz | * Check /home/vgnshlvnz/hadk/hybris/droid-configs.log for full log. | 07:57 |
| vgnshlvnz | !! Failed to deploy the package | 07:57 |
| T42 | <elros34> @eriki73 why do you need custom script? | 07:59 |
| T42 | <eriki73> Google decided to export bt address in a strange way... @elros34 | 08:01 |
| T42 | <edp_17> @elros34 : udevadm monitor -p: https://paste.ubuntu.com/p/DhTpDYXqt2/ | 08:01 |
| T42 | <edp_17> At the start the BT was on. Then the steps I've done: | 08:01 |
| T42 | <edp_17> 1. Turn BT off (turned off) | 08:01 |
| T42 | <edp_17> 2. Turn BT on (blinking) | 08:01 |
| T42 | <edp_17> 3. Turn BT off (still blinking) | 08:01 |
| T42 | <edp_17> 4. Restart rfkill | 08:01 |
| T42 | <edp_17> 5. Turn BT on (turned on) | 08:01 |
| T42 | <eriki73> I made also an issue on bluebinder | 08:02 |
| T42 | <elros34> @eriki73 yeah but original script allows you tu use custom without overwritting, read few first lines w | 08:02 |
| T42 | <eriki73> Ah, ok. Did not look closeluäy enough... | 08:03 |
| T42 | <edp_17> @elros34 : I've tried to repeat but now it required to toggle the Bluetooth more times and restart the rfkill more times. | 08:07 |
| vgnshlvnz | I am building image for bullhead aka Nexus 5X | 08:07 |
| vgnshlvnz | does anyone has prebuilt image? | 08:08 |
| T42 | <edp_17> Tried to capture and comment it in udevadm monitor but couldn't comment all the steps: https://paste.ubuntu.com/p/f2ZGVWMWfm/ | 08:08 |
| T42 | <edp_17> @elros34 ^^ | 08:08 |
| T42 | <elros34> @edp_17 silly idea: i think you should have patchram binary in /system. What about you try to use that one instead the one provided by sailfish? | 08:17 |
| T42 | <edp_17> How can I use it from /system? Should I define the path to that one in config? | 09:32 |
| T42 | <elros34> maybe, if not then create symlink or bind mount it temporary. For me it looks like brcm fails to bring hic0 sometimes after first turn on/off, it keeps running but nothing change, bluetooth.target is not started. If that not help then I will try build bcm driver as module. It's easy to load and unload module and code for it it's already partially in rfkill sources | 09:37 |
| T42 | <edp_17> Okay, I'll try that. | 09:50 |
| T42 | <elros34> or not kill patchram at all, just block it soft or hard: see 'rfkill list' command output | 09:56 |
| T42 | <edp_17> On my XA2, when BT off, the rfkill list says: hci0: bluetooth: Soft blocked: yes, Hard blocked: no | 11:25 |
| T42 | <edp_17> If I turn BT on, the Soft blocked became: no | 11:26 |
| T42 | <elros34> on i9100 I think it will be different. Only when you start patchram hci0 will be up, then you can unblock it via rfkill command or bluetooth switch in gui. | 11:46 |
| T42 | <amyosx> We are porting the galaxy s2 now what? (re @elros34: on i9100 I think it ...) | 11:47 |
| T42 | <TheVancedGamer> there's a port already (re @amyosx: We are porting the g...) | 11:48 |
| T42 | <elros34> yeah made by edp17 | 11:48 |
| T42 | <TheVancedGamer> the great man really | 11:48 |
| T42 | <amyosx> What the (re @TheVancedGamer: there's a port alrea...) | 11:49 |
| T42 | <TheVancedGamer> S2 bess (re @amyosx: What the) | 11:50 |
| T42 | <TheVancedGamer> also @amyosx the IRC guys don't like replies | 11:51 |
| T42 | <TheVancedGamer> it shows up as truncated text | 11:51 |
| T42 | <edp_17> Well, technically I made the port for the S2 but really I was only the hand who followed the instructions given by more experienced porters. :-) | 13:04 |
| T42 | <amyosx> Ah (re @TheVancedGamer: also @amyosx the IRC...) | 13:05 |
| T42 | <amyosx> Wait I did it again :( | 13:05 |
| T42 | <amyosx> @edp_17 shut up pro :P | 13:05 |
| T42 | <mintphin> hi. i'm on chapter 4.3.1 on the hadk and there's this line: | 13:47 |
| T42 | <mintphin> FIXME: to be removed when Sailfish OS 4.2.0 is out: | 13:47 |
| T42 | <mintphin> sudo sed -i 's/jessie/bullseye/g' /usr/bin/ubu-chroot | 13:47 |
| T42 | <mintphin> should i run this? | 13:47 |
| T42 | <mintphin> hi. i'm on chapter 4.3.1 on the hadk and there's this line: | 13:47 |
| T42 | <mintphin> # FIXME: to be removed when Sailfish OS 4.2.0 is out: | 13:47 |
| T42 | <mintphin> sudo sed -i 's/jessie/bullseye/g' /usr/bin/ubu-chroot (edited) | 13:47 |
| T42 | <amyosx> It wouldn't do any harm | 13:48 |
| T42 | <mintphin> Alrighty. | 13:48 |
| T42 | <edp_17> @elros34 : I've checked, there is no brcm_patchram_plus in /system/bin. I olny have one in /usr/sbin | 14:37 |
| T42 | <elros34> /system/xbin?:) If not then probably there is some other binary which send firmware to IC, maybe even hciattach do this | 14:38 |
| T42 | <edp_17> Nope, there is no in /system/xbin either. | 14:41 |
| piggz | mal: how many symlinks are typically required for /apex/com.android.runtime/ files ? | 17:33 |
| T42 | <edp_17> Yes, this is correct, I've just tested it. (Wanted to see the difference to the XA2) (re @elros34: on i9100 I think it ...) | 17:35 |
| T42 | <elros34> @edp_17 I have pushed some code if you want to test | 17:41 |
| T42 | <edp_17> @elros34 : Thank you! I'll do it but later. | 17:53 |
| poetaster | piggz: took a crack at it again today. appeared to get e os installed. but bootlooped. so, volla with android 10 is running on it again. | 18:19 |
| T42 | <adampigg> poetaster: not sure where you are going wrong, but @eriki73 has it going | 18:20 |
| T42 | <adampigg> also, i have fixed audio | 18:20 |
| poetaster | piggz: <eriki73> suggested going with los17 directly? | 18:21 |
| T42 | <adampigg> yeah, i installed los 17 | 18:21 |
| poetaster | piggz: It was probably that revert to vendor step. | 18:21 |
| poetaster | piggz: but how :) there must be a million ways to skin that cat. | 18:22 |
| poetaster | piggz: isn't the volla 10 stuff also los17? | 18:22 |
| poetaster | piggz: given a functioning android (10, volla) can I side load: lineage-17.1-20210723-EXPERIMENTAL-GS290.zip | 18:24 |
| poetaster | piggz: for instance? | 18:24 |
| poetaster | in any case, I've not succeeded once in installing eos. and each time I recovered to something else just to prove to myself that I'm not completely gaga. | 18:26 |
| poetaster | so, no back to tearing my apps apart for harbour/chum and co. | 18:26 |
| deathmist | mal: can I get a review on https://github.com/mer-hybris/droid-hal-device/pull/288? it's been another month :) | 19:55 |
| mal | deathmist: I forgot the whole thing | 19:56 |
| mal | deathmist: I just noticed today some PRs I had made which had been approved months ago but never merged | 19:57 |
| piggz | poetaster: volla now had working sound, camera and fingerprint..... about ready id say! | 21:02 |
| T42 | <edp_17> @elros34 : I've tried the new code. Unfortunately, it doesn't work. BT cannot be turned on at all as brcm_patchram_plus is not running: https://paste.ubuntu.com/p/7Yvqg8yPZ4/ | 22:23 |
| T42 | <edp_17> Even if I restart rfkill service, it doesn't start brcm_patchram_plus. | 22:24 |
| T42 | <elros34> looks like you forgot to change rfkill name to match your | 22:25 |
| T42 | <elros34> s | 22:25 |
| T42 | <edp_17> Oh, wait! I forgot to change the name. | 22:25 |
| T42 | <edp_17> Yes, I just realized. :) | 22:25 |
| *** amccarthy_ is now known as amccarthy | 22:26 | |
| T42 | <edp_17> @elros34 : Similar's happened. When I turned BT on, I found rkill service in failed status. I restarted but BT doesn't turn on, brcm_patchram_plus not started or doesn't stay running: https://paste.ubuntu.com/p/Rr8Ks27MfX/ | 22:35 |
| T42 | <elros34> did you reboot/ | 22:36 |
| T42 | <edp_17> Yes, I did. | 22:37 |
| T42 | <edp_17> When I ran brcm manually, BT turned on but when I turned off and on again I got this in log: https://paste.ubuntu.com/p/mp3kzX2mnv/ | 22:38 |
| T42 | <edp_17> Can't init device hci0: Connection timed out (110) | 22:38 |
| T42 | <elros34> maybe it was started too early, mask service reboot and start it | 22:42 |
| T42 | <edp_17> Do you mean mask rfkill? | 22:43 |
| T42 | <elros34> bluetooth-rfkill-event.service | 22:44 |
| T42 | <edp_17> That's how I meant. Okay. | 22:44 |
| T42 | <edp_17> rfkill service masked, rebooted, unmasked and started. When I turned BT on, rfkill service crashed. Manually restarted, then it stayed running but still no BT and there is no patchram running: https://paste.ubuntu.com/p/BGZSMrGSRS/ | 22:58 |
| T42 | <edp_17> @elros34 ^^ | 22:58 |
| T42 | <edp_17> When I manually run patchram, BT can turned on but when it is off, cannot be turned on again and there is the timeout error in log: bluetoothd[1849]: Can't init device hci0: Connection timed out (110) | 23:02 |
| T42 | <edp_17> If I start/end patchram every time I tiggle BT in Settings, on the second "turn On" attempts (it means the 4th toggle), BT turnes on. Weird. | 23:04 |
| T42 | <elros34> what a mess this works randomly... I can't understand why patcher doesnt work anymore after reboot for the first time | 23:06 |
| T42 | <edp_17> I don't understand either. 🤷♂️ | 23:07 |
| T42 | <edp_17> Probably that's why we had a conclusion to use that ugly udev rule last time (about year ago). | 23:08 |
| T42 | <edp_17> @elros34 : Would it help if I compile bluetooth driver into module? If I would like to do that, is it enough to change CONFIG_BT_BCM4330=y to m? | 23:21 |
| T42 | <elros34> maybe if you would reload module on every bt off. Please try last WIP3 code before that. If that doesn't work then.. | 23:24 |
| T42 | <elros34> CONFIG_BT_BCM4330 looks sane | 23:24 |
| T42 | <edp_17> Okay! | 23:25 |
| T42 | <edp_17> @elros34 : It is better but not perfect just yet. BT cann be turned on first but once it is off, it never turns on again. However, after I turned it off if I kill patchram and restart rfkill, BT can be turned on again! So, at least I bring back that ugly udev "fix" and do this magic in there, it will work. :) I know, it is not nice at all. | 23:37 |
| T42 | <edp_17> I am not sure what difference would it make if I put bt driver into module. | 23:37 |
| T42 | <elros34> ehh so nothing changed | 23:39 |
| T42 | <edp_17> Well, yes it changed because I don't need to kill/restart two times! :) | 23:40 |
| T42 | <elros34> so in theory adding free_hci(); here should do the same: https://github.com/elros34/bluetooth-rfkill-event/blob/master/bluetooth-rfkill-event/bluetooth_rfkill_event.c#L1303 but obviously nothing works like expected so only in theory | 23:45 |
| T42 | <edp_17> I am trying this now. | 23:47 |
| T42 | <edp_17> You know what is interesting? If I manually killed patchram and restarted rfkill after I toggled BT off, I was able to turn it on again. However, when I brought back the udev rule and did the kill and restart by a script, that didn't always worked. Even if I introduced wait 2 before each command. | 23:53 |
| T42 | <elros34> yeah it's random .. | 23:54 |
| T42 | <edp_17> Yep, it seems. With the latest change it is doing similar. The patchram sometimes stays running so requires to kill it manually. | 23:58 |
| T42 | <edp_17> Anyway. Thank you for your time and help trying to make it work. | 23:59 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!