| rinigus | mal: 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 updated | 04: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 params | 06:31 |
| T42 | <adampigg> s/looked | 06: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 well | 06:55 |
| T42 | <adampigg> @dylanvanassche whats the identifier after the camera type? | 06:58 |
| T42 | <adampigg> ours is ov5648, similar to pine ov5640 | 06:59 |
| T42 | <DylanVanAssche> No idea, maybe camera ID or something, PiZZaMartijn knows more about the cameras | 07:00 |
| T42 | <adampigg> mal: gst plugins good is failing on native-common, cant see why as/no logs | 07: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 internally | 09:35 |
| masha11 | I 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 |
| masha11 | dmesg: https://pastebin.com/LWtwirjv | 10:52 |
| rinigus | mal 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 |
| masha11 | and journalctl: https://pastebin.com/4FtFvXL0 | 10:55 |
| mal | masha11: which android base? | 10:55 |
| mal | also any idea which bluetooth chip it is using? | 10:56 |
| masha11 | mal: android basa 7, cm.14.1. I'm looking for chip information. | 11:06 |
| r0kk3rz | boardconfig can have some clues | 11:08 |
| r0kk3rz | or bluedroid config | 11:09 |
| mal | also if the chip is rome or cherokee (both qcom chips) then there will be problems | 11:11 |
| masha11 | r0kk3rz: mal: thanks, I have rome chip looks like. "BOARD_HAS_QCA_BT_ROME := true" (from BoardConfig.mk) | 11:36 |
| r0kk3rz | lame | 11:37 |
| r0kk3rz | could we do rome with bluebinder? | 11:38 |
| mal | rome needs bluebinder which needs 15.1 and even in that case there has to be the binderized service (or the wrapper binder service) running | 11:42 |
| mal | there were several people who tried to get rome chips working in bluez5 directly without success | 11:43 |
| r0kk3rz | there was a big stack of bluez patches yeah | 11:48 |
| masha11 | mal: ok. did anyone manage to get rome to work with base 15.1? | 11:49 |
| mal | masha11: xa2 has rome or cherokee chip | 11:53 |
| mal | maybe x10 also | 11:53 |
| masha11 | mal: 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 https://pastebin.com/fxdtmH6d | 11:59 |
| masha11 | And /dev/block/platform/soc/74a4900.sdhci is missing in my SFOS: https://pastebin.com/V0R3VqUe . | 12:04 |
| mal | masha11: do you see mmcblk0p1 anywhere on the device? | 12:17 |
| masha11 | mal: yes. /sys/devices/soc/74a4900.sdhci/mmc_host/mmc0/mmc0:59b4/block/mmcblk0/mmcblk0p1, /sys/class/block/mmcblk0p1, /dev/block/mmcblk0p1, /dev/mmcblk0p1 | 12:19 |
| mal | masha11: is your root in /dev/sd* or something? | 12:34 |
| masha11 | mal: root is in all /dev/sd* except /dev/sda7 and /dev/sdsprpc-smd. There is system. | 12:42 |
| mal | masha11: the issue is in udisks2 udev rules, those assume mmcblk1* is sd card, not mmcblk0* | 12:59 |
| mal | masha11: so you probably need to add some custom udev rules based on the lines edited here https://git.merproject.org/mer-core/udisks2/blob/master/rpm/0005-Add-udev-rule-for-the-sda-drives.patch | 13:01 |
| mal | you can just add a new udev rule file to sparse/lib/udev/rules.d/ | 13:01 |
| rinigus | mal: have you managed to look into "build/make/core/combo/TARGET_linux-arm.mk:58: error: Unknown ARM architecture version: armv8-2a."? (from last night) | 13:06 |
| masha11 | mal: thank mal, I'll try. | 13:09 |
| masha11 | mal: 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 |
| mal | masha11: so settings->storage doesn't show it? | 13:37 |
| mal | rinigus: 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 https://github.com/mer-hybris/droid-src-sony-ganges-pie/tree/master/patches for your build, check https://github.com/sonyxperiadev/repo_update/blob/android-9.0.0_r46/repo_update.sh | 13:40 |
| mal | we'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 build | 13:41 |
| rinigus | mal: sure, I will. I wonder whether I should base then on r46 instead and somehow get hybris patches to apply to it | 13:41 |
| mal | rinigus: wait | 13:42 |
| mal | rebasing to r46 is needed indeed | 13:42 |
| rinigus | mal: although just adding patches is easier, but I am not sure what else is current hybris android missing | 13:42 |
| rinigus | ... waiting | 13:42 |
| rinigus | mal: ok, I will look into rebasing tonight | 13:43 |
| mal | rinigus: but that can break things in theory as the patches are on top of r46, maybe check which patches you really need to minimize issues | 13:43 |
| mal | I mean without rebasing it might cause issues | 13:43 |
| mal | rinigus: most likely hybris patches will apply cleanly on top r46 but not sure | 13:43 |
| rinigus | mal: I can see that you are as split as I am :). | 13:44 |
| masha11 | mal: here I see several directories (external memory usb,dsp,fsg,systemand others) and many "unsupported memory card" directories. sd directory no. | 13:44 |
| rinigus | regarding rebasing | 13:44 |
| mal | rinigus: split? | 13:44 |
| rinigus | mal: in the sense that whether rebasing will cause more issues than adding patches to the current base. | 13:45 |
| mal | rinigus: maybe just add these https://github.com/sonyxperiadev/repo_update/commit/d19e3cb70ffac5af461d6018e10485f4dba570c8 | 13:46 |
| rinigus | mal: thanks for finding it. without rebasing first, I guess? | 13:48 |
| mal | yes, you can try that first | 13:48 |
| mal | rinigus: so I would grab the art and build/make and build/soong patches from here https://github.com/sonyxperiadev/repo_update/blob/android-9.0.0_r46/repo_update.sh#L51 | 13:49 |
| mal | and only those | 13:49 |
| mal | not sure if art is even relevant for us | 13:49 |
| rinigus | mal: thank you very much! will look into it tonight and report back... | 13:50 |
| *** Piece_Maker is now known as Acou_Bass | 13:51 | |
| masha11 | mal: cd directory not in settings->storage | 13:56 |
| mal | check journal log | 14:04 |
| masha11 | mal: 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 |
| masha11 | is it critical? | 14:20 |
| mal | well you should check the filesystem with fsck but might not be critical | 14:27 |
| mal | PSA: 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 needed | 15:51 |
| vknecht | sound great :-) | 15:59 |
| mal | also h.265/hevc is available but disabled by default due to licensing issues | 16:01 |
| r0kk3rz | mal: vp9 encoding? | 16:56 |
| mal | r0kk3rz: not yet | 16:58 |
| mal | just decoding now | 16:58 |
| mal | I have code for encoder also but that is untested because of another bug | 16:59 |
| r0kk3rz | oh ok | 17:00 |
| T42 | <adampigg> Mmm, mpeg2, for those moments i want to play a dvd on my phone | 17:00 |
| mal | @adampigg or watch live tv-stream using a dvb-usbstick | 17:02 |
| mal | which is a valid use case | 17:02 |
| T42 | <adampigg> Was talking about usb dvbt today as it happens! | 17:02 |
| T42 | <adampigg> Reminiscing | 17:03 |
| mal | I have used a dvb-t stick for sdr in sfos | 17:03 |
| mal | which reminds I should check my gnuradio build | 17: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 |
| mal | vknecht: that is the plan | 17:05 |
| T42 | <adampigg> Mal, *cough camera *cough | 17:05 |
| vknecht | that's cool | 17:05 |
| mal | gnuradio can do a lot of stuff | 17:05 |
| mal | would just need qml UI | 17:05 |
| mal | @adampigg I'll check after I go for a walk first | 17:06 |
| mal | depends on how tired I am after that | 17:06 |
| r0kk3rz | citizen band? | 17:23 |
| r0kk3rz | oh, CB, duh | 17:23 |
| vknecht | these old 27MHz radio receivers/transmitters we had in cars, yes :-) | 17:24 |
| vknecht | not necessarily in cars, in fact (still have a ~6 meters aerial somewhere) | 17:25 |
| r0kk3rz | i realise now i never knew what CB actually stood for | 17:27 |
| vknecht | haha, there are bluetooth mikes now | 17:36 |
| vknecht | lame, doesn't seem to have echo effect | 17:38 |
| mal | @adampigg btw, pulseaudio-module-keepalive is now in devel common | 17:46 |
| Thaodan | r0kk3rz: afaik the issue that Google has moved away from bluez. I think chromeos doesn't use bluez any more. | 17:48 |
| Thaodan | https://chromium.googlesource.com/chromiumos/platform2/+/master/bluetooth | 17:48 |
| Thaodan | so we would need help from Qualcomm or get at least documentation | 17:48 |
| mal | Thaodan: interesting thing is that afaik some rome chips have mainline kernel support, just wondering how those drivers were tested | 17:49 |
| Thaodan | with this new daemon maybe? which would mean it uses hci too. | 18:04 |
| Thaodan | all socs starting with sdm630 have mainline support | 18:05 |
| piggz | mal: thats a nice improvement by splitting out the module | 18:12 |
| piggz | im gonna claim credit for that one ;) | 18:12 |
| *** agander_ is now known as agander | 18:15 | |
| mal | piggz: :) | 18:22 |
| mal | Thaodan: then we might want to check the initialization from there | 18:23 |
| mal | Thaodan: based on that they still use bluez for old bluetooth and that newblue for bt le | 18:25 |
| deathmist | mal: 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 192.168.2.15, but as soon as I restart it all breaks | 18:59 |
| deathmist | it properly worked even after a restart on my last 3.0.3.10 zip from 20190723 w/ usb-moded 0.86.0+mer33-1.3.2.jolla | 19:00 |
| deathmist | so it broke on my seemingly first 3.1.0.12 zip from 20190803 w/ current latest usb-moded (0.86.0+mer36-1.4.1.jolla) | 19:01 |
| deathmist | I found yet another Hossa zip from 20190727, same 1.3.2 version of usb-moded and telnet works after reboot | 19:12 |
| mal | deathmist: so have you tried to install that older usb-moded to your new image? | 19:15 |
| deathmist | mal: nope, but I'll definitely have to try now | 19:16 |
| jellypony | Hello everyone! getting this: https://pastebin.com/QTzvdi42 then rpm/dhd/helpers/build_packages.sh/ | 19:33 |
| jellypony | "%define community_adaptation 1" is set, solution for msm8996 from FAQ inapplicable for msm636 | 19:34 |
| jellypony | what's wrong? :C | 19:35 |
| jellypony | device is xiaomi nitrogen (Mi max 3). Device tree: https://github.com/kirillinda | 19:36 |
| deathmist | mal: 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 |
| deathmist | nvm 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 now | 20:23 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!