Monday, 2020-05-11

rinigusedp_17: should be something like -e 's block/bootdevice/by-name/BOOT mmcblk0p9 ' \ per each link06:11
rinigusI guess I missed some submodule update with zic complaining during obs builds. any tips regarding update that could have caused it?
T42<elros34> rinigus: my tips for 3.3.0: or but this will not work for fresh local target06:41
riniguselros34: thanks, I'll go through them06:42
T42<Verevka86> Hello everyone, tell me how to make debug sensors better?  The screen rotation and proximity sensor stopped working.  hybris 15.1, 16.0.06:47
T42<edp_17> @rinigus: Thanks. I ended up adding the device to the same place where the n7000 was.06:47
T42<elros34> @Verevka86 first check test_sensors then messwerk/csd06:50
T42<edp_17> Now I am having serious problems with building hybris-hal. Lots of error and if I fix one, I get others. Like an endless loop. I am using this kernel:
T42<edp_17> But I might should use this one?:
r0kk3rzwhat errors06:51
T42<Verevka86> @elros34 [@Verevka86 first check test_sensors then messw …], You can read more or an example of which, I do not understand 😇06:54
T42<edp_17> @r0kk3rz: This is the last one(s):
r0kk3rzif you're chasing errors its good to remove the -j param06:59
T42<edp_17> Thanks! I should have thought about running it in only one thread.07:03
T42<edp_17> Now I got this:
T42<edp_17> This is because the CONFIG_EXYNOS_CLUSTER_POWER_DOWN is on in defconfig. However if I turn this off I get other issues. So, I am not sure whether I need this on or off.07:11
r0kk3rzyeah multithreading mangles the output so its not always obvious where the error is07:12
r0kk3rzit sounds like a thing that should be on07:13
T42<edp_17> It is on, at the moment.07:13
r0kk3rza sanity check would be to put the defconfig back to stock and see if it builds07:14
r0kk3rzif it doesnt, id find a better source07:14
T42<edp_17> For this base (cm-14.1) there is no stock rom.😳07:14
r0kk3rzthats not what i mean07:15
r0kk3rzhave you changed the defconfig at all?07:15
T42<edp_17> I have tried to find a los15.1 kernel, but couldn't, then I though should have used an earlier base.07:15
r0kk3rzimo i wouldnt expect any fixes from a newer base07:16
r0kk3rzespecially for such an old device07:16
T42<edp_17> No, but the developer whose kernel I am using modified that. The defconfig didn't even have the proper header stating the kernel version.07:17
r0kk3rzso with no changes of your own, the kernel doesnt build07:17
T42<edp_17> That's why I think should use the second kernel I linked. (I have tried that defconfig too by the way but got different errors so I came back to the first one.)07:17
r0kk3rzignore the config at this stage07:18
T42<edp_17> I have not tried it to build without amending.07:18
T42<edp_17> Okay, I'll go back to the beginning and start over.07:18
T42<edp_17> I have put back the original defconfig and tried to build hybris-hal. I got this error:
T42<edp_17> Should I use this kernel or better to find a CM/LOS-13 base (stock Marshmallow 6.0.1)?08:04
T42<elros34> you should use same kernel version as your android base. Have you tried to install missing app (lzop)?08:05
riniguselros34: was sufficient to fix boot image build. let's see what else from your list will be needed. have to update droid-hal-configs as well, those I forgot.08:06
T42<elros34> yes it's enough for obs but not for localt target08:07
T42<edp_17> @elros: (I can find an android image cm/los-13 for the device.) Thanks for the tip! I have installed lzop, and the hybris-hal build completed. Wow. Now I do the mer-kernel-check and try to fix the errors.08:13
rinigusI wonder, who should be pinged to get merged? mal?08:37
r0kk3rzlooks fairly reasonable08:40
r0kk3rzim not entirely sure its necessary though08:41
rinigusr0kk3rz: details are fuzzy now, as its a while ago... but I have a feeling that I could not do without it. as is, it allows to have obs and local builds using metapackages only, no patterns08:42
r0kk3rzwell it fixes the .ks08:43
T42<elros34> I guess it's required if you want to use --mic08:45
r0kk3rzrinigus: comment on the PR with an example metapackage sapec08:46
rinigusr0kk3rz: ok, will do08:47
r0kk3rzi just wonder if you could add a Summary: directive with the right name and maybe it would work08:47
r0kk3rzor maybe it would just get confused with the pattern08:47
rinigusr0kk3rz: I am not sure I follow. but I can surely add example use in the comment later tonight08:50
T42<adampigg> what about the r0kk3rz PR of a similar nature?08:52
T42<adampigg> does that need dropped or merged too08:53
r0kk3rzyeah should probably get those merged08:53
piggz_i see an abranson PR that is accepted byt not merged also08:54
rinigusfor some reason, I am getting now errors in gst-droid build
rinigusdroidmedia is updated to 0.20200424.008:55
piggz_jusa: lo, wondering if youd like to PR your pinephone branch?09:06
deathmistrinigus: udpate your `gst-droid` commit hash to `95a19dc5f1fa03873db011e7145553a9810d5b30`, that's the latest one and the only difference I can see between our packages, otherwise the problem is somewhere else09:32
rinigusDeathmist : have a feeling I tried, but will do again when I get back to PC09:38
rinigusDeathmist: the last version went through - so I remembered wrong10:14
T42<Verevka86> The time and time zone are not set, hybris15.1.  Does anyone know a solution?10:23
T42<edp_17> @Elros, @R0kk3rz : Big thanks! Going back to the original defconfig has worked! Then I only needed to add a few configs about the bootparam and now the is running! 😊10:24
T42<KernelPanix> @Verevka86 [The time and time zone are not set, hybris15.1 …], hey10:25
deathmist<T42 "<Verevka86> The time and time zo"> if you've booted 3.3.0 this is now apparently expected (for whatever reason), you can fix it by checking the "New issues" text under or following the 2nd bullet point under10:38
deathmistoh and since the caps will be wrong for your "timed-qt5" package (I fix this during builds for now; MR here by elros) you'll also have to "zypper in --force timed-qt5" to fix manually settings time in system settings10:43
T42<Verevka86> @deathmist [oh and since the caps will be wrong for your " …], Thanks 🤝 Did you have any problems with the sensors?10:58
deathmistno problems, I just need and afaik, you can look through the repo yourself for stuff especially if you have MSM8998 SoC as well11:01
T42<Verevka86> @deathmist [no problems, I just need …], I added this, but the problem was not solved, before the sensors worked 😔11:03
deathmistwhat sensors are not working? any? I only had problems with vibrator due to group permission changes with the new release, nothing else changed from
T42<Verevka86> @deathmist [what sensors are not working? any? I only had …], my vibrator doesn't work either. Mobile Internet started working in hybris-15.1 as you said 😊11:08
deathmistI asked what sensors, is vibrator the only thing that doesn't work? does everything else work? for vibrator there is a hybris-15.1-vibra branch on mer-hybris/android_system_core with 2 new patches for now that you need ->
deathmistyou can test the patches by simply editing /init.rc on your SFOS device and see if they work (they should)11:14
deathmistmal: may want to consider pushing hybris-15.1-vibra to hybris-15.1 and the same for other branches on android_system_core there, I could prepare the PR for hybris-patches on 16.0 if you haven't started yet11:15
T42<Verevka86> @deathmist> I asked what sensors, is vibrator the only thing that doesn't work? does everything else work? for vibrator there is a hybris-15.1-vibra branch on mer-hybris/android_system_core with 2 new patches for now that you need - [ …], rotation sensor and proximity sensor11:16
T42<Verevka86> Ofono also behaves strangely, at the first start the network works, after rebooting it does not see the network, but imei are detected11:17
maldeathmist: oops, forgot about those11:21
deathmistshall I create the 16.0 hybris-patches PR? :p11:22
T42<edp_17> Guys, I would need a little support. 😊 Device: Galaxy Note 4 (SM-N910C - treltexx), base CM-14.1.11:23
T42<edp_17> It boots up but stuck on the boot screen with a message: KERNEL IS NOT SEANDROID ENFORCING. It doesn't have IP address but I can assign and go in with telnet. Soon later it disconnects but doesn't reboot.11:25
T42<edp_17> It looks like has /system mounted.11:25
deathmist@edp_17 "zcat /proc/config.gz" output?11:25
deathmistfrom the device obviously11:26
T42<edp_17> @deathmist: here it is:
deathmisttry to leave "journalctl -f" or "dmesg -w" running until it disconnects, in worst case enable persistent journal logging and look at the logs after a reboot to get a clue on why it would just disconnect11:28
mal@edp_17 which telnet port?11:31
malah, based on /system being mounted I assume 232311:31
deathmistI don't believe SECURITY_SELINUX_DISABLE should be =y, set that to =n; also is SECURITY_SELINUX_PERMISSIVE=y by default? BOOTPARAM_VALUE=0 should take care of disabling it on boot instead (though I've only disabled SELinux myself from BoardConfig*.mk files by including "selinux=0" in CMDLINE there)11:32
deathmistmal: so should I do the 16.0 vibrator patches?11:33
maldeathmist: nobody is preventing you from doing it, just grab the patches from the sony branch there and adapt if needed11:39
T42<edp_17> @deathmist: These are flooding the konsole:11:44
T42<edp_17> journalctl -f: May 11 11:43:48 localhost kernel: [c6] power_supply max77843-fuelgauge: driver failed to report `status' property: -2211:44
T42<edp_17> dmesg -w: [   49.002695] [c4] power_supply max77843-fuelgauge: driver failed to report `status' property: -2211:44
T42<birdzhang> you can disable the spam logs11:45
deathmistdefinitely go silence the fuelgauge driver and others that constantly spam the log, these android kernels are just absolute garbage sometimes (:11:47
T42<elros34> I woudn't do it like that, if it print's that error several times per second like on some other devices some time ago. Maybe mce triggers it.11:49
T42<Verevka86> @deathmist> I asked what sensors, is vibrator the only thing that doesn't work? does everything else work? for vibrator there is a hybris-15.1-vibra branch on mer-hybris/android_system_core with 2 new patches for now that you need - [ …], Vibra work 👍12:15
T42<edp_17> Because didn't find the CMDLINE in any *.mk file.12:24
deathmistnot even with grep -rnw $ANDROID_ROOT/device/ -e ".*CMDLINE.*" ?12:26
T42<elros34> I believe the point was that you set SECURITY_SELINUX_DISABLE=y which for sure is wrong12:27
deathmistnice it made CMDLINE italic in my message instead of rendering the 2 *'s (at least on Matrix)12:27
T42<edp_17> I have not tried this way. 😊 I only checked the and Plus all *.mk file in the board sub folder (as there was a reference in
T42<edp_17> @elros: I unset SECURITY_SELINUX_DISABLE. 👍 and retry.12:29
T42<edp_17> @deathmist: Nope, even the grep -rnw $ANDROID_ROOT/device/ -e ".*CMDLINE.*" doesn't find it anywhere. :)12:31
T42<elros34> what device codename?12:32
deathmistyour device tree is very strange, never seen that before12:32
T42<edp_17> trelte or treltexx I am not sure.12:32
T42<edp_17> @deathmist: I know, but this was the latest working cm-14.1 android version I could find.12:33
T42<edp_17> @Elros: Yeah, I have seen that but that was 12.1. In that repo the latest was cm13, I wanted 14.1.12:34
T42<edp_17> However it might was a bad decision. 😊12:35
T42<elros34> I doubt anything changed if bootloader provides own cmdline to kernel12:35
T42<edp_17> I try to adapt all your suggestions and re-try. I'll be back! 😎12:40
T42<edp_17> Thanks. 😊12:40
T42<birdzhang> what about vibrator on hybris-16.0? i applied vibrator patches from hybris-patches sony branch, this makes vibrator works, but broken volume buttons.13:03
maldid the buttons work before the fix?13:05
T42<birdzhang> yeah, i revert and buttons are working13:06
T42<Verevka86> I delete
T42<Verevka86> And ofono began to work fine.13:17
T42<birdzhang> mal: btw, i don't have /sys/class/timed_output/vibrator, even /sys/class/timed_output, is that the reason?13:18
T42<Verevka86> @Verevka86 [I delete …], Perhaps this is due to disabled extra services?13:18
mal@birdzhang which android base?13:18
T42<birdzhang> 16.013:19
malyou probably have vibrator in the led side13:19
malin /sys/class/leds/vibrator13:19
T42<birdzhang> i changed /sys/class/leds/vibrator/activate to system group and reboot, volume buttons work, and change back to input group, reboot, vibrator and volume buttons are working now13:23
malso some temporary issue?13:25
T42<birdzhang> not sure, i need do more tests, before the first reboot i upgraded droidmedia, previous droidmedia was build with old kernel.13:29
malit would be odd why that would in any way affect volume buttons13:31
T42<徐沐淦 %lastname%> (Photo, 1280x720) ✨Telegram群,微信群,potato拉人,增粉,10万个群群发广告,私发广告.13:52
T42<徐沐淦 %lastname%> ✨出售微信号,查不到IP,无需实名手机卡,水军群内聊天吹捧.13:52
T42<徐沐淦 %lastname%> ✨非小号,Mytoken关注,排名,四件套,支付宝出售.短信营销.13:52
T42<徐沐淦 %lastname%> ✨各大APP交易所代实名认证,国外实名认证,KYC出售.13:52
T42<徐沐淦 %lastname%> ✨币圈朋友圈广告,币圈推广增粉,上币投票.币圈各种业务.13:52
T42<徐沐淦 %lastname%> ✨电报自动聊天软件,管理群软件. 请咨询  @Eunun13:52
T42<edp_17> The situation is better as now the device stays on and it gets IP address. However the gui is still not starting and both the journalctl and dmesg is flooded with the same 'KNOX: The mark is out of range' message.14:19
T42<ankaos> elros please look me :)14:20
T42<ankaos> or miklos14:20
T42<ankaos> how build arm64?14:20
T42<edp_17> I think you should build arm32 even for arm64.14:21
T42<elros34> it tells you what to add to spec file14:21
T42<ankaos> @elros34 [it tells you what to add to spec file], xiaomi-tissot-aarch64 ??14:23
T42<elros34> line 2614:23
piggzjusa: mal: im having trouble routing audio to car/bt .... i need some pulseaudio magic....14:24
piggzMay 11 15:20:58 Pro1 pulseaudio[6123]: E: [pulseaudio] sink-ext.c: failed to set sink 'sink.primary_output' port to 'output-bluetooth_sco'14:24
T42<elros34> @ankaos like here:
T42<elros34> @ankaos I wonder why do you keep changing devices instead providing journalctl. Isn't that 3th now? Trust me, that new device will also require journalctl to debug why it fails to show gui14:31
T42<ankaos> ı have 3 device.14:32
T42<elros34> uff good:)14:34
T42<ankaos> @elros34 [uff good:)], :D14:35
T42<ankaos> but not solved this problem :(14:35
T42<elros34> what do you mean, show where did you add that define14:36
T42<ankaos> I couldn't find where to add.14:37
T42<ankaos> I don't have that file there.14:37
T42<elros34> to rpm/droid-hal-$DEVICE.spec14:39
T42<ankaos> @elros34 [to rpm/droid-hal-$DEVICE.spec], not work14:39
T42<elros34> oh c'mon so show your changes14:41
T42<ankaos> @elros34 [oh c'mon so show your changes],
T42<elros34> check once again example, you are missing '1'14:42
T42<edp_17> Does anyone familiar with knox?14:45
T42<ankaos> @elros34 [check once again example, you are missing '1'],
T42<ankaos> latformSDK enes@enes:~/hadk$ ls out/target/product/tissot/14:52
T42<ankaos> android-info.txt  build_fingerprint.txt  gen              hybris-recovery.img       kernel  obj_arm                   ramdisk.img  symbols  utilities14:52
T42<ankaos> boot.img         hybris-boot.img  obj  root         system14:52
T42<ankaos> @elros3414:53
T42<elros34> does make hybris-hal finished without issues?14:54
T42<ankaos> yes14:54
T42<ankaos> ls out/target/product/tissot/ hybris-updater-unpack.sh14:55
T42<elros34> can you show output of make hybris-hal?14:57
T42<ankaos> @elros34 [can you show output of make hybris-hal?],
T42<elros34> you said no issues15:23
T42<elros34> It's hard to help if I can't believe anything you say15:24
T42<ankaos> @elros34 [you said no issues], Where problem?15:25
T42<elros34> first: [fs/f2fs] Error 2. Disable it in defconfig unless you really need it15:26
T42<ankaos> Line?15:26
T42<elros34> use search function15:27
T42<elros34> 2: 'Skipping build of hybris-updater-script since HYBRIS_BOOT_PART is not specified'. I guess you need to define boot in your fstab15:28
T42<ankaos> @elros34 [first: [fs/f2fs] Error 2. Disable it in defcon …], f2fs disable15:35
T42<ankaos> @elros34 [2: 'Skipping build of hybris-updater-script si …], Fix it16:05
T42<ankaos> @elros34 [2: 'Skipping build of hybris-updater-script si …], thanks.16:25
T42<ankaos> @elros34 [It's hard to help if I can't believe anything …], is there a forum?16:25
T42<ankaos> @elros34 how fix this error?17:20
T42<ankaos> `zypper update` fix this error?17:23
T42<ankaos> @elros34 thank you. build sailfish os rootfs now17:31
T42<ankaos> I recorded the errors.17:32
T42<ankaos> I want to extract it to all three devices. I have a contribution to sailfish os.17:32
T42<ankaos> [199703.082394] usb 2-1.1: Product: QUSB__BULK18:05
T42<ankaos> [199703.082396] usb 2-1.1: Manufacturer: Qualcomm CDMA Technologies MSM18:05
T42<ankaos> [199703.082397] usb 2-1.1: SerialNumber: 4b2b69f118:05
T42<ankaos> [199743.193760] usb 2-1.1: USB disconnect, device number 6318:05
T42<ankaos> [199753.247546] usb 2-1.1: new high-speed USB device number 64 using ehci-pci18:05
T42<ankaos> [199753.358714] usb 2-1.1: New USB device found, idVendor=05c6, idProduct=900e18:05
T42<ankaos> [199753.358716] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=318:05
T42<ankaos> [199753.358718] usb 2-1.1: Product: QUSB__BULK18:05
T42<ankaos> [199753.358719] usb 2-1.1: Manufacturer: Qualcomm CDMA Technologies MSM18:05
T42<ankaos> [199753.358721] usb 2-1.1: SerialNumber: 4b2b69f118:05
T42<elros34> Looks like android not sailfish.Please use pastebin for such a long output. Show your kernel and device repo18:24
T42<ankaos> @elros34 [Looks like android not sailfish.Please use pas …], kernel and device repo.18:28
T42<ankaos> @elros34 send repos. where am i making a mistake?18:29
T42<elros34> I already told you that for other device: do not remove existing cmdline arguments:
T42<elros34> Is that a/b device with system as root partition?18:32
T42<ankaos> @elros34 [Is that a/b device with system as root partiti …], yes a/b device18:34
T42<ankaos> delete or not delete18:35
T42<elros34> revert this
T42<elros34> again you disabled audit, how many times I told you to leave it enabled? 5 or more... I am done18:37
T42<ankaos> @elros34 [again you disabled audit, how many times I tol …], no. enable audit.18:38
T42<ankaos> @ankaos [ …], @elros34 edit file18:49
T42<ankaos> @ankaos [ …], edit file18:49
T42<ankaos> open telnet thank you elros 😊19:55
T42<smatkovi> Has anyone tried apkenv on sfos?19:58
piggzmal: ah, ive got my PA outputs back!21:28
piggzi had been messing with symlinks, and had a symlink for /odm/etc to /vendor/etc ... and that was impacting PA21:32
piggzthis made me realise21:33
piggzMay 11 22:24:28 Pro1 pulseaudio[7142]: D: [pulseaudio] config-parser-xml.c: Read /odm/etc/audio_policy_configuration.xml ...21:33
T42<Verevka86> Its work?21:36
piggzand the readme here states /odm is checked first
malpiggz: ah, symlinks are important :)21:40
T42<adampigg> Mal, in this case yup21:45
T42<Verevka86> @deathmist [@Verevka86 …], Sorry 😇22:36
T42<smatkovi> @Verevka86 [ …], Cool I will try that23:02
T42<ankaos> dmesg output
T42<ankaos> telnet open device. but not open sailfishos logo23:21
T42<ankaos> ls -lh /usr/libexec/droid-hybris/system/etc/init/23:25
T42<ankaos> sh-3.2# ls -lh /usr/libexec/droid-hybris/system/etc/init/23:26
T42<ankaos> total 8.0K23:26
T42<ankaos> -rw-r--r— 1 root root  52 May 12  2020 hybris_extras.rc23:26
T42<ankaos> -rw-r--r— 1 root root 893 May 12  2020 servicemanager.rc23:26

Generated by 2.17.1 by Marius Gedminas - find it at!