T42 | <birdzhang> kalube: add libglib-2.0 to cflags and libs | 00:05 |
---|---|---|
T42 | <birdzhang> CFLAGS +=` pkg-config --cflags libglib-2.0` | 00:06 |
T42 | <birdzhang> LIBS += `pkg-config --cflags libglib-2.0` | 00:06 |
T42 | <birdzhang> oh, formatted on telegram side | 00:07 |
spiiroin | piggz: fresh eyes etc. mce uses real info for evdev probing -> if event mapping is significant enough that device type interpretation needs to change, it needs to be done explicitly in config | 03:04 |
spiiroin | printf '[EVDEV_TYPE]\nff_key=KEYBOARD\n[EVDEV]KEY_F12=KEY_POWER\n' | 03:04 |
spiiroin | should make f12=power key, using TOUCH instead of keyboard -> should make f12=double tap (due to implicit "power key in touch input device is double tap" rule) | 03:06 |
T42 | <Verevka86> @Verevka86 [Hello, help me. | 05:55 |
T42 | <Verevka86> This command corrects the sou โฆ], https://github.com/SailfishOS-sagit/droid-config-sagit/commit/3c3efd91f2f78b11acba902f10d81e17517832f6 | 05:55 |
T42 | <Verevka86> Tell me why this does not work? :-( | 05:55 |
T42 | <Frankie A. Preuss %lastname%> Earn From Home | 07:02 |
T42 | <Frankie A. Preuss %lastname%> ๐๐๐ | 07:02 |
T42 | <Frankie A. Preuss %lastname%> https://t.me/joinchat/AAAAAESxgTuHRbxC9Mn2Pw | 07:02 |
piggz | spiiroin: thx, lets try | 07:17 |
piggz | spiiroin: yeah, that works, cheers | 07:23 |
T42 | <Coltor %lastname%> sb2: Error: Invalid target specified, aborting | 07:42 |
T42 | <Coltor %lastname%> how should i solved this problem? | 07:42 |
T42 | <Coltor %lastname%> PlatformSDK wxos@ubuntu:~$ sdk-assistant list | 07:42 |
T42 | <Coltor %lastname%> SailfishOS-latest | 07:42 |
T42 | <Coltor %lastname%> โโSailfishOS-latest-armv7hl | 07:42 |
T42 | <Coltor %lastname%> โโSailfishOS-latest-i486 | 07:42 |
r0kk3rz | you didnt call your target the right name | 08:03 |
T42 | <Coltor %lastname%> PlatformSDK wxos@ubuntu:~$ sb2 -t $VENDOR-$DEVICE-$PORT_ARCH gcc main.c -o test | 08:04 |
T42 | <Coltor %lastname%> sb2: Error: Invalid target specified, aborting. | 08:04 |
r0kk3rz | yes | 08:04 |
T42 | <Coltor %lastname%> PlatformSDK wxos@ubuntu:~$ sb2 gcc main.c -o test | 08:04 |
T42 | <Coltor %lastname%> success | 08:04 |
r0kk3rz | the -t specifies the target | 08:04 |
T42 | <Coltor %lastname%> PlatformSDK wxos@ubuntu:~$ echo $VENDOR-$DEVICE-$PORT_ARCH | 08:05 |
T42 | <Coltor %lastname%> sony-i4113-armv7hl | 08:05 |
T42 | <Coltor %lastname%> if i dont use -t specifiles, sb2 build success. | 08:06 |
T42 | <Coltor %lastname%> but if i follow SailfishOS-HardwareAdaptationDevelopmentKit-3.1.0.0.pdf Chapter 6 | 08:07 |
T42 | <Coltor %lastname%> will be failed | 08:07 |
T42 | <Coltor %lastname%> PlatformSDK wxos@ubuntu:~$ sb2 ./test | 08:08 |
T42 | <Coltor %lastname%> Hello, world! | 08:08 |
T42 | <Coltor %lastname%> I have fixed it | 09:15 |
T42 | <Coltor %lastname%> No provider of 'pkgconfig(libnciplugin)' found. | 09:15 |
T42 | <Coltor %lastname%> Setting version: 1.1.1 | 09:15 |
T42 | <Coltor %lastname%> error: Failed build dependencies: | 09:15 |
T42 | <Coltor %lastname%> pkgconfig(libncicore) is needed by nfcd-binder-plugin-1.1.1-0.armv7hl | 09:15 |
T42 | <Coltor %lastname%> pkgconfig(libnciplugin) is needed by nfcd-binder-plugin-1.1.1-0.armv7hl | 09:15 |
T42 | <Coltor %lastname%> pkgconfig(nfcd-plugin) >= 1.0.20 is needed by nfcd-binder-plugin-1.1.1-0.armv7hl | 09:15 |
T42 | <Coltor %lastname%> Building target platforms: armv7hl-meego-linux | 09:15 |
T42 | <Coltor %lastname%> Building for target armv7hl-meego-linux | 09:15 |
T42 | <Coltor %lastname%> this error how can i fixed ? | 09:16 |
piggz | jusa: hi, on this mtk device im porting, i can hear other side of call audio, but they dont hear me....sound-recorder from openrepos does record from the mic though .... any suggestions? using audiosystem-passthru and hidl driver | 09:17 |
T42 | <ankaos> how to use sailfishos application sdk? | 09:31 |
T42 | <ankaos> designer not use :( | 09:39 |
T42 | <naive17> @ankaos [designer not use :(], designer is unavailable | 10:07 |
T42 | <naive17> You must write your qml by hand | 10:07 |
T42 | <naive17> It's not that bad tho | 10:07 |
*** Oksana_ is now known as Oksana | 12:09 | |
T42 | <edp_17> @elros34: Thanks, with what you suggested I could build broadcom-bluetooth and bluetooth-rfkill-event for bluez5. | 12:44 |
T42 | <edp_17> My question is can I use bluez5 instead of bluez4 on the other device, S2 (CM-12.1 base)? Is there a limit or something that makes bluez5 unusable on old devices? | 12:46 |
T42 | <elros34> AFAIK it's about kernel version. 3.4 can't use bluez5 unless you backport drivers (hadk-faq) | 12:47 |
T42 | <edp_17> Thanks, this answers to my question. That device uses kernel version 3.0. So I am not trying to use bluez5. | 12:51 |
T42 | <edp_17> Do you know where to look for the solution if the audio is not forwarded to a connected, Bluetooth device? | 12:53 |
T42 | <edp_17> (On the device it says connected, but the bt speaker is still blinking (waiting for connection) and when I start playing music, the sound is coming from the device rather than the bt speaker.) | 12:54 |
T42 | <elros34> as usually search for any failure in journal, then maybe pulse audio | 12:57 |
T42 | <edp_17> Okay, thanks. | 13:46 |
T42 | <adampigg> @edp_17 try this | 13:53 |
T42 | <adampigg> dbus-send --print-reply --address='unix:path=/run/user/100000/pulse/dbus-socket' --dest=org.PulseAudio1 /org/sailfishos/audiosystempassthrough org.SailfishOS.AudioSystemPassthrough.set_parameters string:"BT_SCO=on" | 13:53 |
T42 | <adampigg> out of interest | 13:53 |
T42 | <edp_17> @adampigg : Thank you. I got: "Error org.freedesktop.DBus.Error.UnknownMethod: Method "set_parameters" with signature "s" on interface "org.SailfishOS.AudioSystemPassthrough" doesn't exist" | 14:05 |
T42 | <edp_17> Might it be that this time I couldn't pair the device with the bluetooth speaker? | 14:05 |
T42 | <edp_17> @elros34: Here is the log. It seems not the pairing doesn't work either ๐ : https://paste.ubuntu.com/p/zVCMMJB6mG/ | 14:06 |
T42 | <edp_17> or the full log: https://paste.ubuntu.com/p/ThzXxvsnpy/ | 14:06 |
T42 | <elros34> do you even use audiosystem-passthrough? | 14:08 |
T42 | <edp_17> I don't know. How can I check? | 14:10 |
T42 | <elros34> then you don't | 14:14 |
T42 | <edp_17> ๐ | 14:14 |
T42 | <elros34> about these dconf permission issues, did you also have them in mic output? | 14:15 |
T42 | <elros34> or maybe you use some start as root patches for gui apps which might also cause issues | 14:16 |
piggz | dconf permission issues are usually down to not building the image correctly | 14:19 |
piggz | ie, using the kickstart from 3.2 to build a 3.3 image, there is some slight difference | 14:19 |
T42 | <edp_17> If this helps: I use patchmanager 3 and 2 patches: more folder icons and silica mail. I don't remember that I have these issues in the mic output because I built this image a long time ago. | 14:23 |
T42 | <elros34> Did you follow http://collabedit.com/kr9xx? | 14:24 |
T42 | <edp_17> As far as I am aware, yes, I did follow that. | 14:28 |
T42 | <ankaos> (Photo, 1080x1920) https://irc.thaodan.de/.imgstore/c4UvcvZHeV.png | 14:33 |
T42 | <edp_17> First I upgraded the platform to 3.3.0.16 (zypper ref and zypper dup) Then I removed and added from scratch the toolings and targets. Then I updated the submodules as previously used the upgrade-3.2.1 branch. Then I got the issue regarding "/boot/boot-initramfs.gz;5eab9756", so I applied the workaround. Then there was no other error an | 14:33 |
T42 | d the image built. | 14:33 |
T42 | <ankaos> Why not open browser? | 14:33 |
T42 | <ankaos> Ooo ss problem :( | 14:34 |
T42 | <edp_17> @ankaos: Please don't post images/screen shots. Use pastebin or ubuntu pastebin. | 14:34 |
T42 | <ankaos> Not open browser. So ฤฑ dont read log | 14:35 |
T42 | <edp_17> @elros34: @adampigg : I have managed to get the accept/reject button appear when pairing. I accepted and the device showed as connected but on the bt speaker side it is still not connected. Here is the relevant log: https://paste.ubuntu.com/p/4TFdv7NVmz/ | 14:48 |
T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/k3mfpTdmfU.png | 15:21 |
T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/1FCF8u2Sl3.png | 15:21 |
T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/vdKBDIySAm.png | 15:21 |
T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/cIBoznd1Eq.png | 15:21 |
T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/7BRWisBU4G.png | 15:21 |
T42 | <Verevka86> (Photo, 720x1280) https://irc.thaodan.de/.imgstore/0J10eUj1j7.png | 15:21 |
T42 | <KernelPanix> @Verevka86 [<reply to media>], :( | 15:21 |
T42 | <Verevka86> Nemomobile ๐ | 15:21 |
T42 | <KernelPanix> @Verevka86 [Nemomobile ๐], Mer Hybris ? | 15:21 |
T42 | <Verevka86> @KernelPanix [Mer Hybris ?], Yes, Sailfish | 15:21 |
T42 | <elros34> @edp_17 About dconf erros I said patches but it's about setuid wrappers from openrepos | 15:21 |
T42 | <elros34> just out of curiosity why do you use custom ofono/noplugin.conf? | 15:30 |
T42 | <elros34> this could also be important: obexd[2570]: bluetooth: unable to listen in channel 9: socket(STREAM, RFCOMM): Operation not permitted (1) | 15:39 |
piggz_ | spiiroin: i think there is a problem with that config you gave me .... i think the phone now thinks there is a keyboard attached so doesnt use the OSK | 20:57 |
piggz_ | this seems to work: | 21:14 |
piggz_ | [EVDEV_TYPE] | 21:14 |
piggz_ | ff_key=INPUT | 21:14 |
T42 | <edp_17> @elros34: I got that ofono/noplugin.conf from hadk-faq from the bluetooth section. I asked about that and I was told needed, so I copied that into all of my devices. Doesn't it require? | 21:54 |
T42 | <elros34> dunno that is why I ask | 22:03 |
T42 | <edp_17> I think r0kk3rz advised that I needed that plugin. I don't know either. | 22:06 |
r0kk3rz | edp_17 that file is created automatically | 23:45 |
r0kk3rz | you dont need to copy it manually | 23:45 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!