Friday, 2019-08-30

qiangong2[m]Is anyone else having issues accessing the faq-hadk and hot-hadk pages?00:43
qiangong2[m]or am I the only one?00:44
qiangong2[m]hmmm. It's not on the web archive either00:45
qiangong2[m]unfortunately00:45
T42<birdzhang> rip01:11
T42<birdzhang> there is a old backup https://wiki.merproject.org/wiki/Adaptations/faq-hadk01:14
qiangong2[m]Yeah, unfortunately, the latest it seems to be updated is for 2.101:30
qiangong2[m]Rip. So I'm guessing mozilla etherpad has been retired then?02:23
T42<birdzhang> 1 year ago, they said etherpad will be EOF02:24
qiangong2[m]Yeah, but you think they'd send out a notice when it was officially dead02:25
T42<birdzhang> yeah02:27
r0kk3rztheir wiki says theres no official end date07:31
r0kk3rzso... yeah, maybe ded07:31
electro575hi all07:56
electro575Who have an idea with the bluetooth problem ? https://dpaste.de/uiWF08:02
r0kk3rzwhat bt do you have?08:18
electro575bluez408:18
electro575but by defaut bluez5 was build08:19
r0kk3rzthats not what i mean08:21
r0kk3rzwhat bt device08:21
electro575how can i check this ?08:21
electro575obex08:21
r0kk3rzobex is a protocol08:22
electro575o okey08:22
electro575i have check this link : https://github.com/mer-hybris/android_kernel_samsung_smdk4412-sfos08:22
electro575maybe it's better for my device ?08:23
r0kk3rzcommonly kernel flags are missing for bluez to work, so you need to figure out which ones08:23
electro575okey08:24
electro575but i must know the bluetooth device in my samsung t0lte ?08:24
electro575r0kk3rz : i have this link but maybe it's not really good -> https://dpaste.de/WBDR08:26
electro575maybe i can replace this kernel (LineageOS/android_kernel_samsung_smdk4412) by this one08:27
electro575android_kernel_samsung_smdk4412-sfos08:27
electro575r0kk3rz: by kernel flags, do you mean CONFIG_... in defconfig file ?08:29
r0kk3rzyeah08:29
electro575o, okey08:29
electro575easy08:30
electro575r0kk3rz, i have just to build hybris-boot and flash it only ? after modify defconfig !08:58
electro575r0kk3rz : this is it no ? CONFIG_BT_HCIUART_H4=y09:02
r0kk3rzif your bt is connected that way09:05
r0kk3rzit may not be09:05
electro575it's not that, already done y09:05
electro575if you have an idea : https://dpaste.de/zWuR09:07
r0kk3rzshow the whole kernel repo09:08
r0kk3rzand device repo09:08
electro575https://github.com/LineageOS/android_kernel_samsung_smdk4412/tree/cm-14.109:09
electro575https://github.com/LineageOS/android_device_samsung_t0lte09:09
r0kk3rzyou havent forked them?09:10
electro575what ?09:11
electro575i don't create a fork no09:11
r0kk3rzyou should09:12
electro575my file is this : https://dpaste.de/B9Qm09:12
r0kk3rzok, you've got a broadcomm CONFIG_BT_BCM4334 based bt hanging off /dev/ttySAC009:15
electro575where do you see this ?09:15
r0kk3rzso you probably want to follow this, but ignore the part about ttyHS009:16
r0kk3rzhttps://wiki.merproject.org/wiki/Adaptations/faq-hadk#Bluetooth_for_Broadcomm_devices09:16
electro575cypress semiconductor09:16
electro575i must add this ?09:17
electro575CONFIG_BT_BCM4334=y09:17
r0kk3rzits already there09:17
electro575okey, i come back, i go to do anything, afk09:18
UmeaboyJust curious, I built Sailfish for the Sony Xperia 10 (i4113) and I built it to be named i4113 instead of kirin, will that make it unbootable?11:20
Umeaboysonyxperiadev calls it kirin as there are two models in that serie.11:21
Umeaboyi3113 and i4113.11:22
malthe naming of sony devices is a bit confusing11:22
UmeaboySo, it will install regardless?11:22
malthe instructions should provide an image that works11:22
malso they have simple name for device type like kirin and then variants under that with some other codename like those i3113 and i411311:23
electro575why sony devices is more easely to port sailfishOS ?11:48
electro575the link for FAQ is dead mal ?11:51
malseems like it11:55
Umeaboyelectro575: Because unlike Samsung they like their customers.12:01
electro575sailfish has sony as customer ?12:01
r0kk3rzno12:02
electro575okey, i see12:02
electro575i understand12:02
r0kk3rzthey just have their own sony aosp12:02
r0kk3rzwhich we use as a base12:02
electro575okey12:02
r0kk3rzsamsung do their own weird things, as you've noticed12:02
electro575yes12:03
r0kk3rzsony definitely do not like their customers though12:03
r0kk3rzno other device wipes core features on unlocking12:04
electro575and htc ?12:04
r0kk3rzwhat about them?12:05
electro575it's easy to port sailfish ?12:05
r0kk3rzwe dont have that many htc ports12:06
r0kk3rzthe leader board is sony, motorola, and xiaomi12:06
electro575okey12:06
UmeaboyHTC used to be fairly open.12:06
UmeaboyDon't forget Huawe, or am I mistaken there?12:07
UmeaboyHuawei12:07
UmeaboyGotta go.12:07
r0kk3rzas per usual, you're talking nonsense :p12:08
benclark06i'm getting a bunch of udev errors during boot, is that normal? https://bin.disroot.org/?0a387e688c0a6fe1#5YxXXRehwOO9CCkOqLvsYOnvxvhHuthRkLv36Bl8N8w=12:16
benclark06oh and also i'm getting Failed to initialize property area if that tells anyone anything12:17
r0kk3rzthats bad12:20
T42<elros34> benclark06: does the paths printed by udev exist? If no apply this https://github.com/mer-hybris/droid-hal-device/pull/226/commits/7bd1020f65ac8ae25ecfabf847517d8bf8569242 and rebuild droid-hal.12:20
r0kk3rzyou should fix that12:20
benclark06@elros34 looks as if that's the problem12:23
T42<elros34> it's just cosmetic change so focus on getting droid-hal-init, Failed to initialize property is common issue12:23
benclark06alright12:25
T42<elros34> what android base you are using?12:26
benclark06lineage 14.112:26
benclark06oh i think i found something12:29
benclark06https://bin.disroot.org/?b12d7d52e561193e#UjbC2ktvDsjNDf5QxC5feQwe+FcS+uPYa4AyZHjQs6w= bin because kiwi irc won't let me send it like a regular person12:30
malbenclark06: that is not a problem, normal message, droid-hal-early-init.sh is optional and used only on devices which need some special initialization before droid-hal-init12:31
benclark06ah ok12:32
benclark06i will keep on searching then12:32
malFailed to initialize property area is the problem12:32
malbenclark06: and that is often caused by missing *_context files in straggler files12:32
electro575r0kk3rz : for the firmware of my chipset, i just have this file12:33
electro575 /home/sailfish-dev/hadk/hardware/broadcom/wlan/bcmdhd/firmware/bcm4334112:33
electro575it seems to be more for wlan than bluetooth12:34
r0kk3rzsounds normal12:34
r0kk3rzthere should be a bt one as well12:34
electro575this ?12:35
electro575 /home/sailfish-dev/hadk/vendor/samsung/n7100/proprietary/system/vendor/firmware/bluetooth/bcm4334.hcd12:35
r0kk3rzyeah thats it12:35
electro575okey, i link it to /etc/firmware or /vendor/firmware ?12:35
electro575 /system/etc/firmware be appear12:35
r0kk3rzetc/firmware12:36
benclark06mal: i didn't get any errors that required me to define them though12:36
benclark06or at least i think so12:36
electro575okey12:36
electro575just a link or copy all file in etc/firmware ?12:37
malbenclark06: there is a "bug" that build_packages.sh doesn't complain about unpackaged files for droid-hal anymore12:37
benclark06ohhh12:37
benclark06how do i find the ones i need to add then?12:37
malbenclark06: you need to manually check the out/.../root folder for those context files12:37
benclark06on it12:37
maland any other things like symlinks that might be there12:38
benclark06mal: does that include the .rc files?12:42
benclark06or is it just contexts and symlinks12:42
T42<elros34> Should be safe to add to straggler all files/symlinks which are not already included in droid-local-repo/*/droid-hal-$DEVICE.rpm12:48
malbenclark06: no, rc files are automatically handled12:50
malyes, checking that droid-hal rpm will tell what is already included12:51
electro575r0kk3rz : what is the correct path for etc/firmware in my device ?13:07
electro575 /data/.stowaways/sailfishos/firmware ?13:07
electro575i don't have /data/.stowaways/sailfishos/etc/firmware13:07
r0kk3rzwhat on earth are you trying to do13:08
electro575do scp of the firmware13:08
electro575firmware/bluetooth/bcm4334.hcd13:08
electro575do all modification on my device only13:08
r0kk3rzjust link it13:08
r0kk3rzand you should be fixing things in your config repo13:09
electro575i don't have this file on my device i suppose -> bcm4334.hcd13:10
r0kk3rzyou should13:10
r0kk3rzunder /system13:10
electro575 /system/bin/bcm4334.hcd13:11
electro575ln /system/bin/bcm4334.hcd /data/.stowaways/sailfishos/etc/firmware ?13:12
electro575ln -s /system/bin/bcm4334.hcd /etc/firmware ?13:12
electro575okey so i do modification on my computer and port this to my device13:13
T42<DylanVanAssche> I added a new repository to the Pine project on OBS (https://build.merproject.org/project/repository_state/nemo:devel:hw:pine:dontbeevil/sailfishos_3.1.0.12_armv7hl_latest). Nothing is build in that repo yet, is there a way to trigger a complete build of all the packages for this new repo?13:16
electro575r0kk3rz : i'm totally lost in all folder, where are you when you are here on github "r0kk3rz/droid-config-scorpion_windy ?13:19
r0kk3rzconfig repo13:20
electro575this ? /home/sailfish-dev/hadk/hybris/droid-configs/13:20
electro575because here i have just folder : usr, var13:21
electro575no etc13:21
r0kk3rzso make it13:27
electro575hi vknecht13:37
vknechthello13:43
electro575you're good ?13:43
vknechtdoing fine... and you ?13:46
electro5751crash13:49
electro5751for this error : https://dpaste.de/aJFk14:03
electro5751i need to do zypper or apt-get install ? in SDK-platform env14:03
electro5751but i want to keep bluez414:04
electro5751r0kk3rz, if you have an idea about this14:05
r0kk3rzok maybe you cant use that14:08
r0kk3rzjust link the firmware and reboot14:08
r0kk3rzsee what happens14:08
electro5751okey14:08
electro5751this update too is needed r0kk3rz -> https://github.com/mer-hybris/droid-config-f5121/commit/afa01bdf4bdb8a0d16bbd34996ec7cac34bbbc5514:10
r0kk3rzthat config is for the package14:10
r0kk3rzso ignore that14:10
electro5751ok14:10
electro5751r0kk3rz : the equivalent of this path     "hadk/hybris/droid-configs/sparse/etc/firmware/bcm4334.hcd"14:12
electro5751on the device is what ?14:12
electro5751this ? /system/etc/bluetooth/14:12
electro5751i have already two files on this path -> bt.did.conf and bt_stack.conf14:13
electro5751no sorry14:13
electro5751this ? /system/vendor/firmware14:14
r0kk3rzon your pc the link will be broken14:15
r0kk3rzso no 'equivalent path' as such14:16
electro5751r0kk3rz : so when you say -> just link the firmware -> what can i do ?14:17
r0kk3rzlink it?14:18
electro5751on my device i have the firmware under : /system/bin/bcm4334.hcd14:19
r0kk3rzok14:19
electro5751so link it on /system/etc/14:20
electro5751or ?14:20
electro5751https://dpaste.de/t1Zt14:21
r0kk3rzso you not understand the problem or somethong?14:21
electro5751the firmware is not loaded by the device14:21
electro5751?14:21
r0kk3rzand why is that14:22
electro5751because this config is already set -> CONFIG_BT_BCM4334=y14:23
r0kk3rztry again14:24
electro5751sailfishOS don't see the firmware ? because it is located in /system14:24
electro5751and not in /data/.sto ...14:24
r0kk3rzits not looking in stowaways14:25
electro5751i don't know14:25
electro5751no folder here : /system/etc/firmware/BCM43xx.hcd14:26
electro5751r0kk3rz : must i change the  sparse/var/lib/environment/ofono/noplugin.conf for bluez4 rather than bluez5 ?14:29
electro5751r0kk3rz : because it's propietary of samsung ?14:35
electro5751if you don't can install the package, hciattach is not possible ? with bluez414:36
electro5751so i need to use bluez 5? but i have kernel 3.0 !14:36
electro5751r0kk3rz, it's that the problem ?14:42
r0kk3rzhciattach is part of bluez, its there already14:56
electro5751the symlink is not done14:56
electro5751it's that the problem no ?14:56
electro5751r0kk3rz : with what edit this proprietary file "bcm4334.hcd", this is it the problem ?14:59
electro5751what is the problem r0kk3rz ?15:02
electro5751with this15:02
electro5751mal maybe15:03
electro5751@elros34 : do you know the problem maybe ?15:04
T42<adampigg> mal: whats going on here...15:04
electro5751do you have already port a samsung device adampigg ?15:04
T42<adampigg> https://build.merproject.org/package/live_build_log/nemo:devel:hw:xiaomi:latte/sensorfw-qt5/sailfish_latest_i486/i58615:06
T42<adampigg> a long time ago, but incomplete, modem issues15:07
electro5751yes, what are problems ?15:07
electro5751for me it's bluetooth15:08
electro5751r0kk3rz, so you can't port for all people easely the project ! it's that ?15:12
electro5751adampigg : what do you understand for this chapter : https://wiki.merproject.org/wiki/Adaptations/faq-hadk#Bluetooth_for_Broadcomm_devices15:14
electro5751r0kk3rz : i have this path /home/sailfish-dev/hadk/hybris/droid-configs/sparse/etc/firmware/bcm4334.hcd15:17
electro5751what is the problem so ? i don't understand !!15:18
T42<adampigg> what dont you understand? naming the fw?15:20
electro5751this : https://dpaste.de/aJFk15:21
r0kk3rzmoo piggz15:21
electro5751i am on kernel 3.0 and cm 14.1 with samsung galaxy note II t0lte15:22
T42<adampigg> oink r0kk3rz15:23
electro5751en fran├žais ?15:23
electro5751hug15:23
T42<adampigg> choose op 1 if you want bluez 5 .... but with old kernel u might want 415:25
electro5751yes15:25
electro5751but be appear it's not that the problem, maybe ask at r0kk3rz15:26
electro5751he let me guess ^^15:26
r0kk3rzyou cant use bluez515:26
electro5751i know15:27
electro5751so ? it's not possible to use bluetooth services ?15:27
r0kk3rzwhat? just uae bluez415:28
electro5751why you said : do you understand the problem ?15:28
r0kk3rzbecause you clearly havent the foggiest15:29
electro5751the link on my pc will be broken, so i do the link on my device ?15:30
riniguskimmoli: today I haven't had any hiccups as yesterday. Rebooted few times for testing, all was ok. Pinging as a reminder with update test15:31
kimmolirinigus thanks for ping... updating.15:31
7GHABLW38how do you know if your chipset is correctly taking account ?16:08
7GHABLW38chipset bluetooth, do you use dbus ?16:08
7GHABLW38yeah : mkdir: cannot create directory `/system/etc/firmware': Read-only file system16:09
electro5751@elros34 : do you know where the firmware bluetooth must be located ? on device16:18
T42<elros34> "Symlink your firmware file to /etc/firmware/ " from faq16:19
electro5751it's what i've done :16:20
electro5751mkdir /etc/firmware16:20
electro5751ln -s /system/bin/bcm4334.hcd /etc/firmware/bcm4334.hcd16:20
T42<elros34> looks good16:20
electro5751look's not, i give you my log16:20
electro5751@elros34 : https://dpaste.de/axuj16:23
T42<elros34> have you finished all instruction from faq or just created symlink :P16:24
electro5751how do you check if the firmware is correctly taking account16:24
electro5751just create symlink because of this error16:24
electro5751@elros34 : https://dpaste.de/aJFk16:25
electro5751i can't choose the solution in this installation16:25
T42<elros34> so build bluetooth-rfkill-event.spec instead, looks like it has bluez 4 dependecies16:26
electro5751but with solution 2 ?16:26
T42<elros34> no, check once again command you are using to build package16:27
electro5751yes16:27
electro5751this is written16:29
electro5751rpm/dhd/helpers/build_packages.sh --mw=https://github.com/mer-hybris/bluetooth-rfkill-event --spec=rpm/bluetooth-rfkill-event-hciattach.spec16:29
electro5751so i must do this command ?16:29
electro5751rpm/dhd/helpers/build_packages.sh --mw=https://github.com/mer-hybris/bluetooth-rfkill-event --spec=rpm/bluetooth-rfkill-event.spec16:29
electro5751@elros34 : i don't know what to do, really16:32
T42<elros34> can't you just try the command you paste, is it too hard?16:33
electro5751i obtain the same issue16:34
electro5751i will paste it to you16:34
electro5751@elros34 : https://dpaste.de/1Lov16:35
benclark06so i've defined the straggler files, but i'm still getting Failed to initialize property area16:35
T42<elros34> are you kidding me?16:35
electro5751it's not me who deviced to do cancelled16:36
electro5751no16:36
T42<elros34> so focus, and try again with correct command16:36
r0kk3rzthis is a fun game hey elros16:37
T42<elros34> I see16:37
electro5751are you serious16:37
electro5751i'm loosing my time that's all16:37
electro5751thanks16:37
electro5751what's the command so, it's written on FAQ16:40
electro5751rpm/dhd/helpers/build_packages.sh --mw=https://github.com/mer-hybris/bluetooth-rfkill-event --spec=rpm/bluetooth-rfkill-event-hciattach.spec16:40
electro5751here -> https://wiki.merproject.org/wiki/Adaptations/faq-hadk#Bluetooth_for_Broadcomm_devices16:40
electro5751see it16:40
electro5751very fun game yes :)16:42
electro5751what is so different as this -> build_packages.sh --mw=https://github.com/DeadSquirrel01/ofono16:45
electro5751nothing16:45
electro5751vknecht, can you help me just one minute ?16:48
electro5751the link of FAQ is not ready ?16:52
electro5751@elros34 : i'm not kidding you but i'm block16:55
T42<elros34> so read again what you write: http://www.merproject.org/logs/%23sailfishos-porters/%23sailfishos-porters.2019-08-30.log.html#t2019-08-30T16:29:4316:56
electro5751this is this good command ?16:57
electro5751rpm/dhd/helpers/build_packages.sh --mw=https://github.com/mer-hybris/bluetooth-rfkill-event --spec=rpm/bluetooth-rfkill-event.spec16:57
electro5751@elros34 : i can read this and search again, i don't don't don't don't know what about again once16:59
electro5751sorry but, ...16:59
electro5751...17:01
electro5751https://dpaste.de/rnST17:02
electro5751@elros3417:02
electro5751good but no17:02
electro5751Problem: nothing provides broadcom-bluetooth needed by bluetooth-rfkill-event-1.0.6-1.armv7hl17:03
electro5751r0kk3rz, now i can laught, it's your turn -> broadcom-bluetooth17:04
T42<elros34> so build it first17:04
electro5751https://dpaste.de/rnST17:04
electro5751don't forget it, all things seems to be an obviousness for you, it's not so easy for other guys ! r0kk3rz17:13
r0kk3rzchill dude, chill17:43
electro5751it's you the dude17:43
benclark06hi again, in the manual it says to define droid-hal-hammerhead-detritus (with the appropriate substitutions for your device) in your patterns but what do i substitute detritus as?17:57
benclark06i hope that makes sense17:57
r0kk3rz its the hammerhead bit you substitute18:00
benclark06oh ok18:01
benclark06but when i run mic i get repo problem: nothing provides droid-hal-scale-detritus needed by pattern:jolla-hw-adaptation-scale-1-1.noarch,18:01
r0kk3rzdid you build it?18:10
benclark06packages or rootfs?18:11
benclark06or configs?18:11
benclark06i've rebuilt everything and it still gives that error18:31
electro5751@elros34 : how add a textline in firmware binary file ? the link here https://github.com/mer-hybris/droid-config-f5121/commit/afa01bdf4bdb8a0d16bbd34996ec7cac34bbbc5518:52
electro5751by example here :  sparse/etc/firmware/BCM4345C0.hcd18:52
electro5751 /system/etc/firmware/BCM43xx.hcd18:53
electro5751i have build the new image r0kk3rz, but nothing change, same issue18:54
T42<elros34> sparse/etc/firmware/BCM4345C0.hcd is symlink to /system/etc/firmware/BCM43xx.hcd18:54
T42<elros34> you don't add or change antythingin  firmware file18:55
electro5751@elros34 : okey but how do symlink of this file ? on device or in computer ?18:55
T42<elros34> you already did it18:56
electro5751@elros34 : on my device i had : /system/bin/bcm4334.hcd /etc/firmware/bcm4334.hcd18:56
electro5751that's all18:56
electro5751no /system/etc/bcm4334.hcd18:57
T42<elros34> it's just example from xperia, you need to adapt it18:59
electro5751yes19:00
T42<elros34> I guess you need to change "patcher = hciattach" to brcm_patchram_plus and also uart_dev in config file19:01
electro5751@elros34 : patcher = brcm_patchram_plus ? or just brcm_patchram_plus19:52
electro5751what can be uart_dev ?19:53
T42<elros34> that one which r0kk3rz told you19:56
electro5751uart_dev=/dev/ttyHS0  , no ?20:04
T42<elros34> doubt, but maybe such a path exist in your device. use ctrl+f /dev/tty in this channel20:08
electro5751okey20:09
electro5751@elros34 : ok, you've got a broadcomm CONFIG_BT_BCM4334 based bt hanging off /dev/ttySAC020:10
T42<Donreddy> Hi is there any way we could install android apk or anbox on sailfish op3 ???20:12
T42<adampigg> @eug20:13
T42<adampigg> @eugenio_g7 around?20:14
r0kk3rzanbox yeah20:18
piggzr0kk3rz: im flumoxxed .... whats the deal here https://build.merproject.org/package/live_build_log/nemo:devel:hw:xiaomi:latte/sensorfw-qt5/sailfish_latest_i486/i586 ?20:18
electro5751@elros34 : patcher = brcm_patchram_plus ?20:21
r0kk3rzpiggz, this is breaking really early20:23
r0kk3rzlike obs is screwed20:23
piggzr0kk3rz: yeah, i know!20:23
piggzhence, "whats the deal" :D20:24
piggzbut its repeatable20:24
r0kk3rzwell the deal is bad20:24
piggzdoes not compute20:24
r0kk3rztell lbt20:24
T42<elros34> electro575: sure20:24
T42<elros34> piggz: I guess it's because of grep and busybox-grep conflits. I had it few monts ago but coudn't fix20:25
piggzhmmm20:26
electro5751@elros34 : https://dpaste.de/bLgZ i have no /system/etc/firmware20:30
electro5751i have created it on my computer /home/sailfish-dev/hadk/hybris/droid-configs/sparse/system/etc/firmware/bcm4334.hcd -> /home/sailfish-dev/hadk/vendor/samsung/n7100/proprietary/system/vendor/firmware/bluetooth/bcm4334.hcd20:31
T42<elros34> wrong, just go to sparse/etc/firmware and run ln -s  "path to firmware in your device"20:33
electro5751okey sorry20:33
electro5751@elros34 : path to firmware can be different of /system/etc/firmware on my device ?20:35
T42<elros34> it's device specific20:35
T42<elros34> what's the difference where it is?20:36
electro5751okey, my device firmware path i suppose is : /system/vendor/firmware20:37
electro5751https://dpaste.de/Vu6Z20:38
electro5751maybe /firmware20:38
electro5751@elros34 : what can be the right path ?20:38
electro5751@elros34 : what do you think about this https://dpaste.de/UBzv20:40
electro5751be appear it's -> /system/vendor/firmware20:40
electro5751no ?20:40
T42<elros34> oh c'mon, the right path is the path where your firmware is. i though you already found it if no just use find /system -name "firmware name"20:41
electro5751it's this so : /system/bin/bcm4334.hcd20:42
electro5751okey, so on my computer it's https://dpaste.de/WpHF20:45
electro5751/home/sailfish-dev/hadk/vendor/samsung/n7100/proprietary/system/vendor/firmware/bluetooth/bcm4334.hcd20:45
T42<elros34> piggz: as a workaround I just created new repo with package I wanted to build instead building it in device repo20:45
T42<elros34> electro: your pc doesn't matter20:47
electro5751i don't know where is the right path20:47
electro5751@elros34 : https://dpaste.de/UBzv20:48
electro5751what can be the right between this two20:48
T42<elros34> sorry, I can not help you20:48
electro5751ok20:49
electro5751@elros34 : how can i do ln -s if the system is in read-only ? ln: creating symbolic link `/system/vendor/firmware/bcm4334.hcd': Read-only file system20:53
piggz@elros34: r0kk3rz: dunno if its 'correct' but adding this to the project config gets it building:20:53
piggzIgnore: busybox-symlinks-grep20:53
benclark06when i build with mic i get repo problem: nothing provides droid-hal-scale-detritus needed by pattern:jolla-hw-adaptation-scale-1-1.noarch, despite rebuilding packages, configs and whatnot20:56
T42<elros34> you only need to build droid-hal, then detritus package will be in your droid-local-repo21:11
benclark06ohhhh okay21:12
benclark06i was building the wrong stuff21:12
T42<adampigg> @eugenio_g7 sensors working now with built config21:27
benclark06@elros34 i've built droid-hal, but it's still nowhere to be found in the repo21:29
benclark06https://imgur.com/a/wVDNpPJ21:29
electro5751too : ofonod[10944]: Register Profile interface failed: /bluetooth/profile/hfp_ag21:47
electro5751have a good night21:48
T42<linusdan> What happened to the HADK FAQ on etherpad?22:02

Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!