Thursday, 2019-10-10

rinigusmal: thanks! As far as I understand, sony patches are integrated into droid-hal-sony-ganges-pie via one of the submodules. I guess that needs to be updated04:45
T42<adampigg> @eugenio_g7 pinephone is using an ov* camera, and we can take pics with ffmpeg/gstreamer.  we have to configure the camera with metia-ctl... any ideas what the params would be for latte?06:30
T42<adampigg> i looed up the video format but keep getting an error -22 when settng params06:31
T42<adampigg> s/looked06:31
T42<DylanVanAssche> @adampigg Have you checked the supported resolutions of the Latte camera? Besides the resolution, the data format needs to be configured as well06:55
T42<adampigg> @dylanvanassche whats the identifier after the camera type?06:58
T42<adampigg> ours is ov5648, similar to pine ov564006:59
T42<DylanVanAssche> No idea, maybe camera ID or something, PiZZaMartijn knows more about the cameras07:00
T42<adampigg> mal: gst plugins good is failing on native-common, cant see why as/no logs07:23
T42<DylanVanAssche> @adampigg fails on our repo too, manually building it works, but not on OBS.09:10
mal@adampigg yes, very odd, something wrong in OBS, I asked about it internally09:35
masha11I could not start bluetooth on my device (griffin, kernel - qcom msm8996), although I did point 5.11 of FAQ HADK. I get a message in log:  hcismd_set_enable 1.Bluetooth: 0000000000000000.10:51
rinigusmal and others involved in xperia 10 port: what's a general advice regarding handling of sparse when using it for sony xz2 - should I remove most of it and then refill on need-to-be basis or stick to xperia 10 sparse and later remove few bits?10:53
masha11and journalctl:
malmasha11: which android base?10:55
malalso any idea which bluetooth chip it is using?10:56
masha11mal: android basa 7, cm.14.1. I'm looking for chip information.11:06
r0kk3rzboardconfig can have some clues11:08
r0kk3rzor bluedroid config11:09
malalso if the chip is rome or cherokee (both qcom chips) then there will be problems11:11
masha11r0kk3rz: mal: thanks, I have rome chip looks like. "BOARD_HAS_QCA_BT_ROME := true" (from
r0kk3rzcould we do rome with bluebinder?11:38
malrome needs bluebinder which needs 15.1 and even in that case there has to be the binderized service (or the wrapper binder service) running11:42
malthere were several people who tried to get rome chips working in bluez5 directly without success11:43
r0kk3rzthere was a big stack of bluez patches yeah11:48
masha11mal: ok. did anyone manage to get rome to work with base 15.1?11:49
malmasha11: xa2 has rome or cherokee chip11:53
malmaybe x10 also11:53
masha11mal: ok. I still do not see my SD card. it must be registered in udev? sd card is here in CM: /dev/block/platform/soc/74a4900.sdhci/mmcblk0p1
masha11And /dev/block/platform/soc/74a4900.sdhci is missing in my SFOS: .12:04
malmasha11: do you see mmcblk0p1 anywhere on the device?12:17
masha11mal: yes. /sys/devices/soc/74a4900.sdhci/mmc_host/mmc0/mmc0:59b4/block/mmcblk0/mmcblk0p1, /sys/class/block/mmcblk0p1, /dev/block/mmcblk0p1, /dev/mmcblk0p112:19
malmasha11: is your root in /dev/sd* or something?12:34
masha11mal: root is in all /dev/sd* except /dev/sda7 and /dev/sdsprpc-smd. There is system.12:42
malmasha11: the issue is in udisks2 udev rules, those assume mmcblk1* is sd card, not mmcblk0*12:59
malmasha11: so you probably need to add some custom udev rules based on the lines edited here
malyou can just add a new udev rule file to sparse/lib/udev/rules.d/13:01
rinigusmal: have you managed to look into  "build/make/core/combo/ error: Unknown ARM architecture version: armv8-2a."? (from last night)13:06
masha11mal: thank mal, I'll try.13:09
masha11mal: sd card mounted in /run/media/nemo/SD... This is normal? Through the console I can go to the SD card, but on the phone screen I can’t see where it is.13:31
malmasha11: so settings->storage doesn't show it?13:37
malrinigus: it seems the issue is that our droid-src patches are behind sony branches, the support for your device came later, you can add the patches manually to for your build, check
malwe'll have a look about updating to patches and base to latest but for now you can manually download the patches mentioned there and add to proper places under droid-src/patches to fix your build13:41
rinigusmal: sure, I will. I wonder whether I should base then on r46 instead and somehow get hybris patches to apply to it13:41
malrinigus: wait13:42
malrebasing to r46 is needed indeed13:42
rinigusmal: although just adding patches is easier, but I am not sure what else is current hybris android missing13:42
rinigus... waiting13:42
rinigusmal: ok, I will look into rebasing tonight13:43
malrinigus: but that can break things in theory as the patches are on top of r46, maybe check which patches you really need to minimize issues13:43
malI mean without rebasing it might cause issues13:43
malrinigus: most likely hybris patches will apply cleanly on top r46 but not sure13:43
rinigusmal: I can see that you are as split as I am  :).13:44
masha11mal: here I see several directories (external memory usb,dsp,fsg,systemand others) and many "unsupported memory card" directories. sd directory no.13:44
rinigusregarding rebasing13:44
malrinigus: split?13:44
rinigusmal: in the sense that whether rebasing will cause more issues than adding patches to the current base.13:45
malrinigus: maybe just add these
rinigusmal: thanks for finding it. without rebasing first, I guess?13:48
malyes, you can try that first13:48
malrinigus: so I would grab the art and build/make and build/soong patches from here
maland only those13:49
malnot sure if art is even relevant for us13:49
rinigusmal: thank you very much! will look into it tonight and report back...13:50
*** Piece_Maker is now known as Acou_Bass13:51
masha11mal: cd directory not in settings->storage13:56
malcheck journal log14:04
masha11mal: FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Mounted /dev/mmcblk0p1 at /run/media/nemo/SD7DUMP3SS3 on behalf of uid 100000.14:17
masha11is it critical?14:20
malwell you should check the filesystem with fsck but might not be critical14:27
malPSA: there was just a moment ago an update to gst-droid which requires also updated droidmedia, this brings hardware-accelerated mpeg2 and vp9 decoding on devices which has required hardware support, detection is automatic and no configuration is needed15:51
vknechtsound great :-)15:59
malalso h.265/hevc is available but disabled by default due to licensing issues16:01
r0kk3rzmal: vp9 encoding?16:56
malr0kk3rz: not yet16:58
maljust decoding now16:58
malI have code for encoder also but that is untested because of another bug16:59
r0kk3rzoh ok17:00
T42<adampigg> Mmm, mpeg2, for those moments i want to play a dvd on my phone17:00
mal@adampigg or watch live tv-stream using a dvb-usbstick17:02
malwhich is a valid use case17:02
T42<adampigg> Was talking about usb dvbt today as it happens!17:02
T42<adampigg> Reminiscing17:03
malI have used a dvb-t stick for sdr in sfos17:03
malwhich reminds I should check my gnuradio build17:04
vknecht\o/ citizen band receiver on sfos ? :-)17:04
T42<adampigg> About 15years ago, i had an unsupported usb dtb stick... I allowed the dev to ssh into my machine and he wrote a driver!17:04
malvknecht: that is the plan17:05
T42<adampigg> Mal, *cough camera *cough17:05
vknechtthat's cool17:05
malgnuradio can do a lot of stuff17:05
malwould just need qml UI17:05
mal@adampigg I'll check after I go for a walk first17:06
maldepends on how tired I am after that17:06
r0kk3rzcitizen band?17:23
r0kk3rzoh, CB, duh17:23
vknechtthese old 27MHz radio receivers/transmitters we had in cars, yes :-)17:24
vknechtnot necessarily in cars, in fact (still have a ~6 meters aerial somewhere)17:25
r0kk3rzi realise now i never knew what CB actually stood for17:27
vknechthaha, there are bluetooth mikes now17:36
vknechtlame, doesn't seem to have echo effect17:38
mal@adampigg btw, pulseaudio-module-keepalive is now in devel common17:46
Thaodanr0kk3rz: afaik the issue that Google has moved away from bluez. I think chromeos doesn't use bluez any more.17:48
Thaodanso we would need help from Qualcomm or get at least documentation17:48
malThaodan: interesting thing is that afaik some rome chips have mainline kernel support, just wondering how those drivers were tested17:49
Thaodanwith this new daemon maybe? which would mean it uses hci too.18:04
Thaodanall socs starting with sdm630 have mainline support18:05
piggzmal: thats a nice improvement by splitting out the module18:12
piggzim gonna claim credit for that one ;)18:12
*** agander_ is now known as agander18:15
malpiggz: :)18:22
malThaodan: then we might want to check the initialization from there18:23
malThaodan: based on that they still use bluez for old bluetooth and that newblue for bt le18:25
deathmistmal: okay I did more testing about the telnet stuff, seems during the initial boot any of my zips (even latest from a few days ago) get working telnet etc via, but as soon as I restart it all breaks18:59
deathmistit properly worked even after a restart on my last zip from 20190723 w/ usb-moded 0.86.0+mer33-1.3.2.jolla19:00
deathmistso it broke on my seemingly first zip from 20190803 w/ current latest usb-moded (0.86.0+mer36-1.4.1.jolla)19:01
deathmistI found yet another Hossa zip from 20190727, same 1.3.2 version of usb-moded and telnet works after reboot19:12
maldeathmist: so have you tried to install that older usb-moded to your new image?19:15
deathmistmal: nope, but I'll definitely have to try now19:16
jellyponyHello everyone! getting this:   then  rpm/dhd/helpers/
jellypony"%define community_adaptation 1" is set, solution for msm8996 from FAQ inapplicable for msm63619:34
jellyponywhat's wrong? :C19:35
jellyponydevice is xiaomi nitrogen (Mi max 3). Device tree:
deathmistmal: downgrading already installed usb-moded* packages on a recent image on the device to v1.3.2 built on OBS (couldn't on my host due to some unresolvable conflics with dcd) it didn't change anything :(  would I have make a new image or is the issue more likely somewhere else?20:19
deathmistnvm seems it got built wrong, I'll have to clean my SDKs and try again tomorrow with it built properly, device still shows 1.4.1 on zypper info but says the 1.3.2 RPMs are already installed when I try again now20:23

Generated by 2.17.1 by Marius Gedminas - find it at!