Wednesday, 2019-10-23

xreactx[m]__TheKit: easy day... i'll try it now00:00
xreactx[m]__permission denied when i execute the busybox tar... command00:06
T42<BusterBg_18> did you chmod+x'ed the BusyBox binary?00:07
xreactx[m]__now its going (i feel dumb), thanks00:09
xreactx[m]__dang, did all of the steps but lineage boots instead00:29
xreactx[m]__what would using busybox tar in the "" look like?00:44
xreactx[m]__would that even work?00:44
T42<birdzhang> i assume you forgot flash hybris-boot.img01:39
xreactx[m]__nope, flashed it to the current boot slot02:58
xreactx[m]__in TWRP, clicked the "img" install button, picked hybris-boot, and flashed it to the boot partition02:59
rinigusmorning! state of sony xz2 aosp9-based port. in short, selinux and bootpartition kernel parameters didn't help. I am stuck on sony logo without any logs in host dmesg nor lspci06:23
rinigusas I don't have access to lvm filesystems in twrp, I don't have any boot logs either.06:23
rinigushowever, I doubt that there is any log as I expect lvm is not mounted due to this gem:
riniguson my device, all disk blocks are sda... I wonder where in the build scripts hybris/mw/initrd-helpers are pulled06:24
rinigusI will fix that find-mmc- script and try tonight. if it still fails, maybe moving away from lvm would be better for initial phase of the port06:24
rinigusvknecht & mal ^06:24
riniguslooks like initrd-helpers are pulled by build_bootimg_packages.sh06:26
T42<adampigg> Xreactx: doesnt.flashing the slot,.change the slot also so you have to change it back?06:57
Mister_Magister@adampigg flashing sfos doesn't change slot07:00
Mister_Magisteronly flashing /system07:01
T42<adampigg> Ok07:01
T42<adampigg> Monich: on tjc,user abandoned sfos becuase of no miband3 support.... You could pr that to me :)07:07
Mister_Magistermal: hi i'm porting using 15.1 base is there something special i need to do?07:32
Mister_Magisterguess i could port using  16.107:34
nitin03@mal I put ld.config.28.txt.mount file and also its symlink as you suggested10:53
nitin03still device not booting up but it is behaving differently now10:54
nitin03     here is dmesg is different device is switching up constantly between mer and android10:56
maldid you add everything else I mentioned, the .rc files11:00
malalso do you have selinux properly disabled11:01
nitin03@mal which .rc files?11:20
malI probably gave you a link to github where there are some .rc files you need add to config repo to correct place, check channel logs11:22
nitin03@mal i have disabled selinux...11:22
malin case you don't know there is a nice search engine for channel logs
malsupports regex and such things to make searching easier11:23
electro575mal, is it possible to have telnet access with windows ?11:25
nitin03@mal i checked it even logs from here
T42<BusterBg_18> electro575: you can use telnet on Windows either with putty or using Microsoft's own telnet client11:26
malnitin03: do you have those11:28
nitin03@mal yes11:28
nitin03i do have them11:29
electro575what is the debian package for ifconfig command ?11:37
electro575sorry but what is the password of su11:41
electro575in sailfishos11:41
electro575use su or devel-su ?11:42
malyou set that in Settings->Developer mode11:43
maldevel-su is the one used in sfos11:43
electro575i have developer mode11:44
electro575but i have no password for devel-su11:45
T42<adampigg> you set the password for devel-su in settings->developer mode11:48
electro575yes, thanks11:49
electro575and what is the password to update sailfish OS ? to install app from storeman11:49
electro575apt-get update ?11:49
electro575apt-get upgrade11:49
Mister_Magisterthere is no apt-get11:49
Mister_Magisteryou can set your password like adam said11:50
electro575but for gps, i need libpurple11:50
Mister_Magisterlol what11:50
T42<adampigg> libpurple is messaging isnt it?11:51
nitin03@mal what am i missing?11:51
Mister_Magisteradam it is11:51
Mister_Magisterso i'm like what11:51
Mister_Magisterfor car i need orange11:51
nitin03init log is same as before..but device is behaving differently on boot up11:52
T42<adampigg> you can use pkcon to refresh/install packages11:52
Mister_Magisteror zypper11:52
electro575puremaps, need libsailfishapp-launcher11:52
Mister_Magistermal: sorry for bugging but i'm porting using 15.1 base is there something special i need to do?11:53
electro575i need just zypper refresh ?11:54
vknechtuse wisely :-)11:56
Mister_Magisterdevel-su rm -rf /11:57
electro575lol, noob11:57
nitin03@mal as u can see in this dmesg...device is stuck at boot logo...but it is getting recognized as mer and android device in that boot logo..11:58
electro575Mister_Magister : be grateful we work for your society11:59
Mister_Magisterelectro575: who is noob here12:04
vknechtpiggz, hmm, does SettingsOverlay "lives" even when not opened, eg. should it be able to receive signals ?12:24
electro575in progress12:28
vknechttrying this but the emit doesn't trigger either onStorageModelChanged functions12:28
Mister_Magistervknecht: sure you got correct channel? apps stuff belongs to #sailfishos12:29
electro575How can i do the same connection on windows ?
Mister_Magisterelectro575: this is not windows powershell support group12:35
electro575is it possible to do this command with a virtualbox debian12:39
T42<adampigg> vknecht: yes, i think it should be alive all the time12:59
T42<adampigg> mister_magister, well, im not on sailfishos while otg .... is that even on telegram?13:00
malMister_Magister: 15.1 needs correct .rc files, some device also need some additional make commands in habuild to make sure fstab and ueventd*.rc files are build/moved to out/13:03
Mister_Magistermal: i read something about 15.1 needing surfaceflinger13:03
Mister_Magistermal: that sounds just like 16.0 :P13:04
vknecht@adampigg, ok thanks, have to dig deeper then :-)13:04
T42<BusterBg_18> Hi mal: quick question, is there any hybris16 based port that has gotten to GUI?13:13
malMister_Magister: no, 15.1 uses hwcomposer, 2.0 actually13:13
mal@BusterBg_18 not sure13:14
Mister_Magistermal: well k then13:14
malMister_Magister: of course depends on device and if the device has working hwcomposer in kernel13:14
malunlike those some devices with broken 32-bit hwcomposer13:15
Mister_Magistermal: if u were me and had both lineage 15 and 16 would you go with hybris 15 or 1613:17
malstill not sure if any 16.0 builds have gotten to UI13:18
Mister_Magistermal: lol fxtec is hitting release13:18
Mister_Magisterso like uhh13:18
Mister_Magisterat least one?13:18
Mister_Magisteralso my 5z so 213:19
Mister_Magisterso which one would u pick13:19
malI don't remember what device uses what13:19
Mister_Magistermal: so which one :P13:20
malI have no opinion, depends on if both have equally good hw support or not13:21
malwhich device?13:21
electro575an idea for no sound when i do a call13:26
electro575i have sound when i listen a music on my device and on youtube13:27
maldid you build audioflingerglue and related things as told in hadk pdf?13:27
malwhich android base13:27
electro575audioflingerglue i suppose13:30
electro575how can i check without the project ?13:30
electro575audioflingerglue yes13:32
malcheck what?13:33
electro575if it is on my device13:34
electro575i have again the time daemon spam13:35
T42<meierrom> @adampigg: to bring IRC channel #sailfishos to Telegram would be really cool. @thaodan is currently doing it for this channel. You are surely the best person to convince him. :)13:42
malelectro5751: for example "zypper se audioflinger" on device13:43
malor "ps aux | grep miniaf"13:44
electro5751state install13:44
electro5751State Sl13:44
malyou didn't tell which android base you are using13:44
electro575115-1 lineageos13:45
electro5751android 8 i suppose, because 16 is android 9 pie13:45
electro5751i have sound for music but not for call13:48
electro5751and no microphone13:48
electro5751how can i debug ?13:49
electro5751mal, is it possible to edit this file ? /system/vendor/etc/init/hw/init.qcom.rc13:55
electro5751be appear w for the user root13:55
electro5751but i can't edit it13:55
electro5751for time_daemon13:55
electro5751mal, i have always this SPAM :
electro5751is it possible to edit the file init.qcom.rc ?14:05
electro5751it's read-only14:05
malcould you please focus on some more important bugs first14:07
electro5751okey, sound for calling14:07
electro5751and microphone14:07
T42<adampigg> electro5751: your filesystem is readonly14:08
mal@adampigg /system is supposed to be readonly14:08
T42<adampigg> i know14:09
electro5751how can i debug the sound for calling14:09
T42<adampigg> just explaining why it doesnt work for him .... if hes desperate to edit file and get rid of error, he can mount it rw14:09
mal@adampigg but no point in doing that, he shouldn't edit /system partition14:11
malthere are other ways to work around that issue, like adding disabled time_daemon to some .rc file that is loaded before that file14:11
malwhich needs to be checked from .rc files and droid-hal-ini output to see which could work14:11
T42<adampigg> yup, the order of parsing is key there14:12
T42<adampigg> tho, while developing early stages, i often edit /system for quick workarounds14:13
mal15.1 was done in a bit stupid way because it doesn't load those in correct order14:13
mal"correct order" as in libexec first14:13
T42<adampigg> yeah, we have to load ours first if we have no ability to override until v1614:14
malmaybe it should be fixed14:15
electro5751what can i do to disable time_daemon so ?14:16
electro5751create a .rc file ?14:17
electro5751or write in a rc file before init.qcom.rc14:17
electro5751i can remount with rw option14:18
malstop that, I said look into other issues first14:18
electro5751okey, sound14:18
electro5751but what is the method to check the middleware used by ofonod for calling14:18
malif you want to time_daemon temporarily then just edit it in /system partition by first mounting rw and the edit and remount ro again14:19
electro5751i remove time_daemon so ?14:22
electro5751or add line with "disabled"14:22
T42<birdzhang> you can ignore time_daemon now, it's normal, not critical14:25
T42<birdzhang> for my device, i need pulseaudio-modules-droid-hidl 1.0 version14:26
electro5751birdzhang : what is your device ? and android base14:30
T42<Akatsu %lastname%> do pulseaudio screetching appears on sailfishOS when running on MSM8916?14:36
electro5751ok, good, no SPAM about time_daemon14:37
electro5751but now i have this spam14:37
electro5751sh[961]: /usr/bin/droid/ line 16: /sys/module/hci_smd/parameters/hcismd_set: No such file or directory14:38
electro5751rfkill[2866]: unblock set for all14:38
electro5751all the time14:38
electro5751mal, i have no smd14:39
electro5751is it normal to have all the time rfkill14:39
electro5751the file ->
electro5751vknecht, an idea about that ?14:44
malhave you even checked which bt chip your device has?14:45
electro5751in the past14:50
electro5751how we can check all chip of my device ?14:51
electro5751Qualcomm MSM8974AB Snapdragon 80114:52
electro5751htc one m814:52
electro5751mal, Qualcomm MSM8974PRO-AB exactly14:53
electro5751that's why msm897414:53
malthat tells nothing about bluetooth14:54
electro5751how can i check14:54
malI don't have time to help now14:55
electro5751mal, explain to me when you have more time14:56
maldid you read bluetooth part in the faq
electro5751yes, i have read this15:01
electro5751the .yaml is on the device or not ?15:02
electro5751i have no access to my directory hadk15:02
electro5751i will see this in 2 hour15:03
electro5751i have no wifi and no bluetooth yes15:03
T42<birdzhang> electro5751: vince(Xiaomi redmi 5 plus), 15.1 base15:07
Mister_Magister[15:21] <mal> which device?15:20
Mister_Magistergriffin aka moto z15:20
electro5751i have no device with "hciconfig hci0 up"15:20
electro5751mal, about bluetooth :
electro575how can i check my bluetooth chip ? r0kk3rz ?15:58
electro575i come back16:01
rinigusvknecht & mal: I made a new image with fixed storage path. now the phone doesn't hang on boot anymore, but reboots after a short while on sony's logo. still no debug info (dmesg, lsusb, pstore), unfortunately. looks like I have go for "regular" partitioning to be able to debug issues.16:36
vknechtrinigus, hmm, tried logging to sdcard ?16:37
rinigusvknecht: no, I haven't. does it log onto its /16:38
vknechtcan choose the path, I used this service file:
rinigusvknecht: also in xperia10 init I don't see much logging. its mainly into kmsg, if I am not mistaken16:39
T42<DylanVanAssche> mal: spiiroin: I tried to debug the IIO proximity sensor a bit further... If I run it from the command line instead of systemd, the debug prints are fine. They are returning the right scale and offset. However, Messwerk doesn't show the change in true/false for withinProximity. Just a heads up, I had a long day already, heavy d16:39
T42ebug work will be for the weekend16:39
vknechtguess what you want is mainly dmesg/journal, perhaps init log ? anyway, you can use the commands you want16:40
rinigusvknecht: now I wonder what would be sdcard path on this device... I guess I'll have to test it somehow16:41
vknechtgenerally /run/media/nemo/ followed by sdcard ID/volume name16:42
rinigusvknecht: maybe I should still try to get 'regular' boot going. I wonder how hard is it to switch between ext4 and lvm path.16:42
malrinigus: just curious, how much stuff did you take from ganges config repo16:42
maland from other repos16:42
malthere are some things there that might not work directly16:42
rinigusre sdcard: yeah, but you have this funky mmcblk1p1 in service. I have sda for main storage, no idea what for sdcard16:43
vknechtmainly rename the config repo kickstart dir so it's not used, and use "mic create fs" instead of loop16:43
rinigusmal: probably more than I should had16:43
Thaodanrinigus: does changing journald to persistent?16:43
Thaodanthe mmc device should be the sdcard16:44
rinigus(thank you thank you for help - I'll try to reply in order)16:44
Thaodanif it's ufs like on the Xperia 1 sda is the main storage16:45
rinigusmal: mainly tried to trim (sparse), but I may have missed something16:45
malrinigus: for example ganges has selinux partially enabled16:45
rinigusvknecht: but how do we build regular image boot? if we don't use separate repo as in aosp9 xperia10? can't find one that we used on onyx16:46
rinigusmal: I tried with selinux=0 as well. just let me find boot cmd16:47
rinigusmal: I have also androidboot.selinux=permissive ; full cmd at
rinigusThaodan: I cannot mount / as it is on LVM. not 100% sure if it gets mounted16:48
rinigusmal: should I change boot command or that looks OK?16:48
rinigusvknecht: will try with create16:49
Thaodanhm rescue target would be interesting but with telnet16:49
malrinigus: not as simple as that, it has one commit for system/core that changes how selinux works16:49
Thaodandid you try to boot the recovery and checked if that works?16:50
rinigusThaodan: twrp works, hybris-recovery doesn't (haven't tried last time, let me try)16:50
rinigusmal: was that commit in kernel? if that, then it should be in16:51
Thaodani meant hybris recovery,  because this has to bring up lvm too16:51
Thaodanrinigus: nope that's in hybris hak16:52
malrinigus: I mean you cannot have the new selinux commit in system/core if you want to disable selinux16:53
malalso other changes related to selinux like enabling selinux in systemd16:54
Thaodanmal: you mean that commit inside hybris patches that is used on the Xperia 10?16:55
rinigusThaodan: recovery is as busted as normal boot. reboots after some time16:55
Thaodanrinigus: you could try to debug from here. it has less features and should be easier to debug.16:56
rinigusmal: OK, so I can test image with selinux not set to zero and keeping the rest of xperia 10 base.16:56
Thaodanyou can edit Jolla-init to log to somewhere where  you can read the output16:56
rinigusThaodan: problem is that there is nothing to hang on to. no net, no root logs :) . maybe sdcard trick will work.16:57
Thaodanyeah you could add that to Jolla init16:57
malThaodan: yes16:57
malThaodan: also in config repo16:57
Thaodanmal: thanks  I'll look on that for the Xperia 116:58
rinigusmal, selinux: so that's a part we apply as `./ --mb` during a setup?16:59
rinigus... just to be on the same page16:59
malI think you should just go with hadk way and then add only certain parts from ganges17:00
malthen add more after you have it running17:00
rinigusmal: now I have to figure out how to do that specifically. I will look into it. we don't have lineage for that device, though. as far as I know.17:04
malrinigus: I mean hadk way but using aosp as usual17:05
malonly difference is branch17:05
maland editing patches to not have some new changes17:05
rinigusmal: thanks! I will try and will be back with more questions ...17:07
*** electro is now known as Guest3767417:11
electroomal, i have this chip -> bcm433417:14
electroohumm no, it's for t0lte samsung17:17
electroobluetooth work partially18:01
electroohow transfert to my device bluez5 package although bluez4 is installed18:09
jellyponyGood evening, mal! Are you here? Do you remember me? I remade hybrys-boot with new defconfig with minimal number of changes. I had fixed only settings which were provided as errors by mer kernel checker. Dmesg still broken >_<18:54
electroowith bluez5, bluebinder is necessary ?18:56
malbluebinder is only for devices with binderized bluetooth18:57
malwhich bluez version you use depends on kernel for example18:57
electroobluez4 is okey19:00
T42<NotKit> xreactx[m]__, do you have skip_initramfs neutralizing patch in kernel?19:00
electroobluebinder i suppose is not support19:00
jellyponymal: new defconfig. All changes I made is down "# for hybris 16" line.19:01
T42<DylanVanAssche> mal: I found a solution for the proximity sensor :) I have it working now. Need to clean up the code a bit before I can make a PR. I use the same workaround as Elros34 (setting the value to 0 or max instead of the real measured value)19:02
mal@DylanVanAssche what was the reason for the problems?19:03
T42<DylanVanAssche> If tou supply the real value (measured by the sensor), QtSensors won't report the proximity state. If you saturate the value between min and max, it works fine. Will check further if the code can be improved19:08
T42<DylanVanAssche> you*19:08
T42<DylanVanAssche> mal: ^^^19:08
malok, strange19:08
T42<DylanVanAssche> Will test if instead of 0 and max, 0 and value will work. The choice between both is the proximity threshold value.19:09
mal@DylanVanAssche how can the hybris prox sensor work, it assigns the value directly19:12
malalthough it things all smaller than max value are near19:12
T42<DylanVanAssche> mal: I don't understand it why that's the issue. I compared with the hybris prox sensor and nothing is different when it comes to writing the values to the buffers19:14
mal@DylanVanAssche does the prox iio sensor give some odd values, you have if(proximityValue >= proximityThreshold) { near = true; }, hybris sensor has the opposite19:14
T42<DylanVanAssche> Well the value is higher when near. If I put my hand above the sensor, Messwerk reports with that 'Proximity detected'19:15
T42<DylanVanAssche> Is this reversed in comparison to the behavior of the hybris prox sensor?19:17
T42<DylanVanAssche> Ooooh :O19:17
malI mean the raw data is opposite19:18
malnot the messwerk reporting19:18
T42<DylanVanAssche> ok19:18
mal@DylanVanAssche just to be sure, when you put hand near the device in messwerk the "Proximity detected" becomes highlighted and if you remove your hand then it is overwritten with a line19:19
T42<DylanVanAssche> mal: Yeah that's the behavior of Messwerk. I checked the IIO docs of the kernel and higher = closer19:20
malnot very logical :)19:21
T42<DylanVanAssche> mal: I know :P19:22
malalso not sure why it doesn't like the raw values, qtsensors code doesn't care about that
T42<DylanVanAssche> mal: Yeah it's strange, but I got the idea from @elros34. Elros mentioned it a while back in this chatroom.19:25
electroomal, have you an idea about wifi ?19:26
T42<elros34> and I give the link: qtsensors use raw value instead withinproximity_19:26
electroo@elros34 : hi, do you know how to debug wifi ?19:27
maldid you build the driver as module as told in faq19:27
electroonot again19:28
mal@DylanVanAssche hmm, I accidentially read the qml part of that which looked different19:32
malso is misunderstood how that works19:32
T42<DylanVanAssche> mal: I'm just happy that I have it working now :)19:36
electroomal, i have an error when i enable CONFIG_MODULES19:36
mal@DylanVanAssche now just cleanup the code and make a merge request19:46
T42<DylanVanAssche> mal: Will do :)19:47
malelectroo: some devices also have possibility to use builtin wlan driver but those usually need to do something like this but that depends on wlan chip what it needs19:48
spiiroinmal, @DylanVanAssche: proximity sensor = send ir pulse, measure how much of it is reflected back. something in front of the sensor = most of the pulse is reflected back; nothing in front = there is always glass/whatnot, but value is low19:49
electroomal, how can i check the wifi chip ?19:49
malelectroo: kernel defconfig19:49
T42<DylanVanAssche> spiiroin: Ok thanks for the clarification :)19:50
Thaodanelectroo mal those configs are often listed in like here19:51
Thaodanwill conman disable the device too when wlan is off?19:52
electrooi don't arrived to get the original defconfig19:53
electrooThaodan, i don't know19:53
electroomal, strange, i have this19:57
electrooi have PRONTO and PRIMA19:58
Thaodando you have something like device-$vendor-$device?19:58
electrooand with this chapter -> Build Wlan Driver as Module -> i have an error with enable CONFIG_MODULES19:58
electrooto do what thaodan ?19:58
electroodevice htc one m819:59
electroodevice m819:59
Thaodando your device the aosp module for your phone.20:00
ThaodanI know but the device git repo with the device definition etc.20:01
Thaodansomething like this but for your phone:
ThaodanThis sony platform uses the prima wlan driver too, maybe this can help you.20:01
electroookey, thank you20:02
electrooit exist a htc platform ?20:02
malelectroo: do you see "/sys/kernel/boot_wlan/boot_wlan" on your device20:08
electrooi will see20:08
electroono such file -> ls -al /sys/kernel/boot_wlan/boot_wlan20:10
Thaodanelectroo: this will help you maybe
piggzvknecht: have you tried the resolution PR ?20:12
piggzmal: does this PR have a future?
piggzlooks like its required on pro120:33
piggzsame case, after recording video, the message appears20:33
electroopiggz, how is it possible to check kernel version ?20:39
piggzelectroo: uname -a ?20:40
electrooon device ?20:40
electrooan idea to check why i have no sound during a call ?20:41
piggzbuilt audioflingerglue etc ?20:41
electrooi have sound during listening music20:42
electroobut not during a call20:42
electrooand no microphone20:42
piggzsounds audioflinger related20:46
*** jellypony1 is now known as jellypony20:46
electroorelated ?20:46
T42<Martensite %lastname%> @electroo section 13.2 and 13.3 and 13.4.1 in hadk20:50
malpiggz: did I forget to merge that PR :D21:01
piggzmal: so it would seem21:02
malpiggz: I will talk about that with others tomorrow21:02
malI use that code already on fp221:02
piggzmal: ok, im gonna build it for pro1 also21:03
piggzmal: if youre not doing that tonight, i can think of some camera PRs to test and i cen merge tomorrow ;)21:05
piggzbeen using the resolution one today, its great :)21:05
malpiggz: btw, did your change to cam app solve the issues I was trying to fix long time ago21:06
piggzwhich issues?21:06
malpiggz: cam switching21:06
piggzyes, that works fine21:06
piggzfor me atleast21:07
malok, wondering how you managed to handle the initial values21:07
malI had some odd issues with those21:07
piggzyes, i had trouble where the resolution couldbt be read for the front camera....21:07
piggzso, befroe switching, i set to a very low res, switch camera, load it, get the resolutions, then set21:08
malalso some timing issues that cam was not ready yet21:08
malpiggz: does your code update the supported features when cam is switched, based on what I saw no21:09
malI have support for that21:09
piggzmal: PRs welcome :)21:09
malneed to see how it works with the current code, it's quite old code21:09
malpiggz: hmm, did I forget to make PR for the code cleanup21:11
malmaybe tomorrow21:11
*** electro is now known as Guest9464421:23
Guest94644sorry but can i pass this line ? mk-cam-conf 1 /etc/gst-droid/gstdroidcamsrc-1.conf21:23
Guest94644in chapter -> 13.3 Camera21:23
malthose are not needed21:25
malmk-cam-conf is obsolete21:25
Thaodanany one used newer  gcc versions for building kernels?23:56

Generated by 2.17.1 by Marius Gedminas - find it at!