| Qiangong2[m] | Can you build sailfish 3.1 with cm-11? Or is that too old? I've found that cm-13.0 doesn't work for my device when building | 01:56 |
|---|---|---|
| T42 | <elros34> Qiangong2[m]: cm11 is fine, you can use it. There is small issue with libhybris but only when you are building in build.merproject.org so you don't have to worry about it now | 07:12 |
| sledges | @adampigg, 21st is the only day for me to come to London (brought some jolla gear from .fi); enjoy the apollo! | 07:34 |
| piggz_ | sledges: hmmm, you;ll need my address for free jolla gear then!! | 08:11 |
| piggz_ | sledges: i have to dress christmassy cos its the xmas special :D | 08:12 |
| piggz_ | mal: that error comes from failed to open /dev/video32 | 08:12 |
| r0kk3rz | sledges: i think im busy that weekend :( | 08:31 |
| piggz_ | r0kk3rz: he'll need your address for the freebies too then! | 09:00 |
| r0kk3rz | any new ones? or just the same old ones ive already got :P | 09:00 |
| piggz_ | r0kk3rz: i reckon an x10 minimum | 09:03 |
| piggz_ | mal: oo, found something | 09:03 |
| piggz_ | mal: https://bpaste.net/show/VJDd | 09:13 |
| piggz_ | sh-3.2# cat /sys/module/firmware_class/parameters/path | 09:14 |
| piggz_ | /vendor/firmware_mnt/image | 09:14 |
| piggz_ | sh-3.2# ls /vendor/firmware_mnt/image/ven* | 09:14 |
| piggz_ | /vendor/firmware_mnt/image/venus.b00 /vendor/firmware_mnt/image/venus.b02 /vendor/firmware_mnt/image/venus.b04 | 09:14 |
| piggz_ | /vendor/firmware_mnt/image/venus.b01 /vendor/firmware_mnt/image/venus.b03 /vendor/firmware_mnt/image/venus.mdt | 09:14 |
| mal | piggz_: so I was correct when I said some initialization is missing, in this case firmware loading | 09:40 |
| piggz_ | mal: aye | 09:41 |
| piggz_ | trying to figure out why! | 09:41 |
| mal | why doesn't the firmware loading script work for you? | 09:42 |
| piggz_ | this line | 09:42 |
| piggz_ | drivers/soc/qcom/peripheral-loader.c: pil_err(desc, "Failed to locate %s(rc:%d)\n", fw_name, ret); | 09:42 |
| piggz_ | mal: what is "the firmware loading script" ? | 09:42 |
| mal | in config repo, needs the fw loader support in kernel to be enabled | 09:42 |
| mal | afaik it's mentioned in kernel checker | 09:42 |
| piggz_ | mal: | 09:52 |
| piggz_ | CONFIG_FW_LOADER=y | 09:52 |
| piggz_ | CONFIG_FW_LOADER_USER_HELPER=y | 09:52 |
| piggz_ | CONFIG_FW_LOADER_USER_HELPER_FALLBACK=y | 09:52 |
| mal | maybe add the path to the script? | 09:52 |
| piggz_ | mal: how is the script called? | 09:53 |
| mal | check 8mmit history, it's quite new thing | 09:54 |
| mal | *commit | 09:54 |
| piggz_ | mal: aaaaaand......big buck bunny is playing :) | 09:57 |
| piggz_ | mal: what is preferred, modify script or add symlink? | 10:09 |
| piggz_ | i nearly had it ... i added a sylink for /firmware, but linked it to /vendor/firmware_mnt_image/ instead of /vendor/firmware_mnt !!!! | 10:09 |
| piggz_ | symlink it is | 10:19 |
| mal | piggz_: depends on how common that path is on devices | 10:21 |
| piggz_ | mal: the script looks in "/system/etc/firmware/ /odm/firmware/ /vendor/firmware/ /firmware/image/" | 10:22 |
| piggz_ | i needed /vendor/firmware_mnt/image | 10:22 |
| piggz_ | i also have a /vendor/firmware btw | 10:23 |
| mal | piggz_: of course symlink is the simpler one for you but wondering if it's common to have those files in that folder | 10:27 |
| piggz_ | sure | 10:28 |
| piggz_ | i was just giving u the info needed to make that decision ;) | 10:28 |
| piggz_ | mal: GPS next ...... interesting is the messwerk shows a button for position, but not for gnss satelites like mido | 10:33 |
| mal | piggz_: actually interesting why it didn't find those files when you had /sys/module/firmware_class/parameters/path correctly set | 10:37 |
| mal | piggz_: just to be, do you have latest submodule? | 10:41 |
| mal | *to be sure | 10:41 |
| T42 | <adampigg> Ill check..... | 10:41 |
| mal | check that you have the loader fix in there | 10:42 |
| mal | looks like you have it | 10:42 |
| piggz_ | mal: yes, aug 1 | 10:45 |
| T42 | <adampigg> mal: logcat prints | 11:02 |
| T42 | <adampigg> 09-10 11:59:32.597 3604 6930 I LocSvc_ApiV02: <--- globalEventCb line 124 QMI_LOC_EVENT_POSITION_REPORT_IND_V02 | 11:02 |
| mal | that seems ok | 11:05 |
| T42 | <adampigg> Mal: but no position in pure or messwerk | 11:36 |
| mal | @adampigg no satellite info either? | 11:37 |
| T42 | <adampigg> mal: no, i dont think so | 11:38 |
| mal | anything from geoclue in logs? | 11:42 |
| piggz_ | mal: zip in journal | 11:48 |
| piggz_ | mal: i dont think it find the provider | 11:50 |
| mal | piggz_: nothing really? not even that it's starting it? | 11:50 |
| piggz_ | yes, i got a log after rebootint.... | 11:51 |
| piggz_ | Sep 10 12:50:13 Sailfish org.freedesktop.Geoclue.Master[5219]: Found providers: | 11:51 |
| piggz_ | Sep 10 12:50:13 Sailfish org.freedesktop.Geoclue.Master[5219]: geoclue-hybris.provider | 11:51 |
| piggz_ | Sep 10 12:50:13 Sailfish org.freedesktop.Geoclue.Master[5219]: geoclue-mlsdb.provider | 11:51 |
| piggz_ | no binder provider | 11:51 |
| mal | it's that hybris one | 11:51 |
| piggz_ | oh | 11:51 |
| mal | I was lazy and didn't rename it :D | 11:51 |
| mal | you can check the package list to see binder package is really installed | 11:51 |
| piggz_ | it is... | 11:52 |
| piggz_ | prints this on startup then https://bpaste.net/show/lAGQ | 11:52 |
| mal | that seems correct | 11:54 |
| mal | you have tried outdoors? | 11:54 |
| piggz_ | yes, ive just been repairing a lawn mower, and left it outside for 3 minuts looking | 11:54 |
| piggz_ | 30 | 11:55 |
| Mister_Magister | piggz_: gj o7 | 11:58 |
| Mister_Magister | would help but i'm outta time | 11:58 |
| krnlyng | hi saidinesh5 | 12:41 |
| Mister_Magister | <3 | 12:42 |
| piggz_ | mal: that QMI_LOC_EVENT_POSITION_REPORT_IND_V02 indicates it is reporting position? | 12:42 |
| mal | piggz_: not sure but it might | 12:49 |
| piggz_ | mal: https://github.com/sonyxperiadev/vendor-qcom-opensource-location/blob/master/loc_api/loc_api_v02/LocApiV02.cpp#L2457 | 12:50 |
| mal | piggz_: do you see any other ones similar to that? | 12:50 |
| mal | piggz_: wondering if there is some way to check if the device uses gnss 1.0 or 1.1 interface? | 13:10 |
| mal | although I would assume it should work with both | 13:11 |
| piggz_ | mal: no, i saw on startup that 1.1 fails so it falls back to 1.0 | 13:11 |
| mal | piggz_: where did you see that? | 13:11 |
| mal | so that means it should have only 1.0 support? | 13:12 |
| piggz_ | 09-10 13:46:00.611 3623 3623 E LocSvc_HIDL_vendor.qti.gnss@1.0-service: Could not get passthrough implementation for android.hardware.gnss@1.1::IGnss/default. | 13:12 |
| piggz_ | 09-10 13:46:00.611 3623 3623 W LocSvc_HIDL_vendor.qti.gnss@1.0-service: Failed to register IGnss 1.1 service: 1, try IGnss 1.0 | 13:12 |
| piggz_ | 09-10 13:46:00.614 3641 3641 D vendor.qti.hardware.soter@1.0-service: soter: svc service starting. | 13:12 |
| piggz_ | 09-10 13:46:00.614 3641 3641 I ServiceManagement: Removing namespace from process name vendor.qti.hardware.soter@1.0-service to soter@1.0-service. | 13:12 |
| piggz_ | 09-10 13:46:00.615 3556 3556 D sound_trigger_hw: load_audio_hal: ahal is using proprietary API version 0x0101 | 13:13 |
| piggz_ | 09-10 13:46:00.615 3556 3556 I sound_trigger_platform: platform_stdev_init: Enter | 13:13 |
| piggz_ | 09-10 13:46:00.625 3641 3641 E vendor.qti.hardware.soter@1.0-service: Registered SOTER HAL service success | 13:13 |
| piggz_ | then just laster | 13:13 |
| piggz_ | 09-10 13:46:01.182 3623 3623 I LocSvc_HIDL_vendor.qti.gnss@1.0-service: Registration complete for vendor.qti.gnss@1.0::ILocHidlGnss/gnss_vendor. | 13:13 |
| mal | so 1.0 should be fine | 13:16 |
| piggz_ | yes, i think so | 13:16 |
| mal | maybe try running geoclue hybris in debug mode, not sure if it needs to be build with some debug flag or will runtime work | 13:17 |
| piggz_ | mal: suggestion..... in bluebinder, there is a Pre script, bluebinderwait.sh ..... that script checks for the address being set by another script at the start ..... you could check for a device supplied script, and run that, instead of everyone having tp create a script+service to run before bluebinder | 14:11 |
| piggz_ | i might PR that | 14:11 |
| mal | piggz_: what? | 14:12 |
| mal | ah | 14:13 |
| mal | krnlyng: ^ | 14:13 |
| T42 | <DylanVanAssche> mal: Did you had already some time to check the OBS logs for the `gst-plugins-good` build? https://build.merproject.org/package/live_build_log/nemo:devel:hw:pine:dontbeevil/gst-plugins-good/sailfish_latest_armv7hl/armv8el | 14:59 |
| mal | @DylanVanAssche I can't access any logs, I need to ask again for someone else to fix the build logs | 15:01 |
| T42 | <DylanVanAssche> mal: Oh I didn't know that... No hurry :D | 15:02 |
| piggz_ | mal: krnlyng: you understand? :) | 15:12 |
| mal | yes | 15:14 |
| rinigus | kimmoli: ping regarding testing of the release | 15:45 |
| vknecht | rinigus, just curious, does usb connection sharing work for you ? | 15:47 |
| rinigus | vknecht: never tried and even not sure how | 15:47 |
| vknecht | when plugging usb, there's an "internet sharing" option (if usb-moded-connection-sharing-android-config is present in pattern) | 15:51 |
| mal | afaik that usb connection sharing has always been a bit problematic which is why it's not enabled by default | 16:07 |
| vknecht | I've been using it from the start, and it only started failing with 3.1.0.12 so I suppose it's due to some usb-moded change between 0.86+mer33 and 0.86+mer36 | 16:19 |
| vknecht | here's a log with usb-moded in debug mode, with connection sharing option selected at 13:59:00 https://pastebin.com/EB0i9SNF | 16:20 |
| vknecht | ^ spiiroin, any idea ? :-) | 16:21 |
| mal | did you check the commit history for anything that could cause that? | 16:23 |
| vknecht | yes, but nothing obvious ; maybe mode=ask handling | 16:24 |
| vknecht | here's my config https://github.com/vknecht/droid-config-idol3/blob/master/sparse/etc/usb-moded/usb-moded.ini | 16:25 |
| rinigus | vknecht: hard to say. when plugging onto onyx with internet sharing on under usb, I do get notification on sharing on phone. nothing on linux pc though. | 16:26 |
| rinigus | never tested it before => cannot say if it started failing now | 16:26 |
| vknecht | rinigus, should add an interface on pc, much like developer mode | 16:26 |
| vknecht | ok :-) | 16:26 |
| vknecht | for me, when it fails, since the process is restarted again and again, the notification also pops up again, this waking up the screen regularly | 16:28 |
| vknecht | s/this/thus/ | 16:28 |
| rinigus | it doesn't wakeup regularly over here - but I don't see any interface on pc either. not sure it works and I don't think I'll ever use it :) | 16:42 |
| vknecht | thank you for taking the time to try it :-) | 16:47 |
| rinigus | vknecht: you are welcome! | 16:50 |
| spiiroin | vknecht: 1st observation: looks like usb-moded chokes while trying to parse some dbus message -> aborted from within libdbus & gets restarted | 18:44 |
| spiiroin | vknecht: one thing that could cause problems is connman side firewall rules (relatively new thing) | 18:47 |
| spiiroin | then there is that unsolved "gadget" vs "ethernet" interface confusion, ref https://git.merproject.org/mer-core/usb-moded/merge_requests/43 | 18:48 |
| spiiroin | the latter should not cause breakage i.e. if things worked, it should still work - but some devices do not work without config file changes | 18:49 |
| spiiroin | btw, if I understand correctly the dbus fault happens at connman_wifi_power_control() which looks like dragons be here territory | 18:55 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!