Monday, 2023-05-29

*** Danct12 is now known as Guest165008:17
*** Danct12 is now known as Guest165711:43
T42<Papoucifle> Hello again ! I read hadk-hot to understand more about system-as-root, but I a bit confused. I had the advertised strange behaviors on /system (like /system/etc link pointing to itself), so I changed my /usr/lib/systemd/system/system.mount file to make system partition mount on /system_root, and created a /usr/lib/systemd/system/system_root.mount to bind /system_root/system to /system, but none of them works after a reboot (both directorie12:11
T42<adampigg> @b100dian hows nfc going?13:43
T42<elros34> @Papoucifle Did you enable system_root.mount? Fix your fstab and build hybris/droid-hal then check how it's done automatically inside droid-hal-device*.rpm15:01
UmeaboyHi! As Samsung Galaxy devices of the newer kinds cannot easily be downgraded to Android 11 or 12, what AOSP revision number do I use for the repo init part?15:04
UmeaboyI see it's recommended to use Android 11 or 12, but my Galaxy S21 5G is using Android 13.15:05
UmeaboyCan I use android-13.0.0_r16 ?15:05
UmeaboyI also see that the instructions to add the repo binary to ~/bin is missing or not linked properly. This makes the repo init command not working.15:12
*** amccarthy is now known as Guest169117:02
*** amccarthy_ is now known as amccarthy17:02
T42<b100dian> @adampigg sorry I am clueless. I installed nfcd and nfcd-binder-plugin but slava's NFC logger says it can't connect to the service. The service is "running" but I don't know how to add extra logging as we speak19:00
T42<adampigg> systemctl stop nfcd19:00
T42<adampigg> nfcd -vvvvv (re @b100dian: @adampigg sorry I am...)19:00
T42<b100dian> heh. ngfcd the letters are like next to each other. thanks19:01
T42<adampigg> also try this version, 1 line change
T42<adampigg> if regular doesnt work for you19:02
T42<b100dian> thanks!19:02
T42<b100dian> So with default jolla/adaptation-common nfcd/nfcd-binder-plugin there was not much logged, with one-line power-up-the-adapter change the same, but with 1.1 interface there is "life"in the logs but it ends up in "RF_DISCOVER_RSP error 1"19:33
T42<b100dian> nfcd logcat
T42<adampigg> @b100dian try setting protocols to only A and B19:44
T42<b100dian> what is that sorcery:) Now it is polling and vibrates on rfid touch19:47
T42<b100dian> Thanks! But what is it useful for? NFC logger doesn't seem to connect to the service still19:47
T42<adampigg> well, if you have an ndef tag, it can read text from them ... or if you have a yubikey, slava made an app for that19:48
T42<adampigg> @b100dian so for you, does it work with just the AB config ... or do you need my nfcd patch too?19:49
T42<b100dian> let me first revert the binder to the adaptation-common one and see19:50
T42<adampigg> yeah, im using the common binder-plugin, + patched nfcd19:50
T42<b100dian> `zypper in --oldpackage nfcd-binder-plugin-1.1.8-1.2.1.jolla` and then there's nothing19:53
T42<b100dian> It just stays at the line with `neard_handover_agent` when starting nfcd -vvvv19:54
T42<adampigg> means the service is running19:54
T42<b100dian> But it doesn't work. When it works it outputs more, like from line 43 on
T42<adampigg> what version of nfcd do you have?20:03
T42<b100dian> right now is the one with the one-line change. Let me revert that too, but with the new binder version20:04
T42<b100dian> nope, that doesn't work either20:05
T42<b100dian> So the only pair that works is the custom nfcd + custom nfcd-binder-plugin you kindly provided20:05
T42<b100dian> this is on the android 11 -base phone20:06
T42<adampigg> hmm, im sure just nfcd should work ... it tells the binder plugin to power up, which is what the binder-plugin hack does20:09
T42<b100dian> hmm do you think a reboot instead of a service restart is needed?20:11
T42<adampigg> try it20:12
T42<b100dian> ok, so nfcd one-liner, vanilla nfcd-binder-plugin20:12
T42<adampigg> yes ... if that doesnt work .. try the setting20:13
T42<adampigg> did you toggle off/on on settings?20:13
T42<b100dian> yes, settings installed, it's on20:13
T42<adampigg> but did you toggle?20:14
T42<b100dian> have you tried to turn it off and on again? not yet:)20:15
T42<b100dian> Hmm it works if I toggle it even with `zypper in --oldpackage nfcd-binder-plugin-1.1.8-1.2.1.jolla` but let me check nfcd20:16
T42<b100dian> Yes, vanilla nfcd doesn't work. But one-liner nfcd + vanila nfcd-binder-pluginm after cycling the setting works ("works" == "vibrates")20:18
T42<adampigg> ok ... then, the final piece you need is the setting to power on on startup20:30
T42<adampigg> @b100dian20:30
T42<adampigg> [root@PhoneX23 nfcd]# cat /var/lib/nfcd/settings20:30
T42<adampigg> [dbus_neard]20:30
T42<adampigg> BluetoothStaticHandover=false20:30
T42<adampigg> 20:30
T42<adampigg> [Settings]20:30
T42<adampigg> Enabled=true20:30
T42<adampigg> AlwaysOn=true20:30
piggzmal: ^^ another device not powering on20:31
T42<b100dian> `rpm -qf /var/lib/nfcd/settings` "is not owned by any package" means I can add it to sparse?20:46
T42<adampigg> @b100dian wait a day or so, lets see if there is any reply to my issue/pr20:49
T42<b100dian> ok.20:49
T42<b100dian> (on the other hand, the binder changes seem not to require cycling the on/off toggle)20:50
T42<adampigg> the settings change should do that also20:50
T42<adampigg> settings + nfcd should do everything20:50
*** phlixi is now known as Guest170222:56
*** phlixi_ is now known as phlixi22:56

Generated by 2.17.1 by Marius Gedminas - find it at!