| T42 | <elros34> @edp_17 I don't know why this symbol is not exported. I wonder what happen if you write nvram/firmware_path manually https://github.com/edp17/android_device_samsung_trelte-common/blob/cm-14.1/board/wireless.mk#L8. Another way could be: copy nvram_net and bcmdhd_sta.txt to /lib/firmware and change default path for them in defconfig. | 00:22 |
|---|---|---|
| T42 | <edp_17> Yeah, I am not sure either. I have tried to comment out #ifdef CUSTOMER_HW4, then together with #ifdef SUPPORT_LINKDOWN_RECOVERY, then all three with #if defined(CONFIG_MACH_UNIVERSAL5433) || defined(CONFIG_MACH_UNIVERSAL7420) | 00:24 |
| T42 | <edp_17> but didn't make any difference. | 00:24 |
| T42 | <edp_17> Now I am checking whether I can force to write the mac address back to /efs/wifi/.mac.info | 00:25 |
| T42 | <edp_17> But I don't really like to idea to hardcoding the mac address. | 00:25 |
| T42 | <edp_17> I check what you sent. | 00:25 |
| T42 | <elros34> I built this kernel but for some reason I coudn't export any symbol from dhd_linux.c | 00:26 |
| T42 | <edp_17> What should be the value to write in nvram/firmware_path? | 00:29 |
| T42 | <elros34> I guess WIFI_DRIVER_NVRAM_PATH and WIFI_DRIVER_FW_PATH_STA | 00:30 |
| T42 | <elros34> but with /system prefix | 00:30 |
| T42 | <elros34> same as default values in defoncig | 00:31 |
| T42 | <edp_17> Can I change these on the device? | 00:32 |
| T42 | <edp_17> And should I change WIFI_DRIVER_FW_PATH_AP too? | 00:33 |
| T42 | <edp_17> You are right, on device /etc/wifi/ doesn't exist but /syste/etc/wifi/ does. | 00:34 |
| T42 | <elros34> What do you mean? changing it in wireless.mk doesnt make sense. Use: https://pastebin.com/A06x0k3g or copy these files to / nad change default paths in kernel defconfig | 00:35 |
| T42 | <edp_17> I have done this on the device: https://pastebin.com/A06x0k3g | 00:40 |
| T42 | <edp_17> And I changed the CONFIG_BCMDHD_FW_PATH="/sys/module/dhd/parameters/firmware_path" and CONFIG_BCMDHD_NVRAM_PATH="/sys/module/dhd/parameters/nvram_path" | 00:42 |
| T42 | <edp_17> I recompile the kernel. | 00:43 |
| T42 | <elros34> I assume these paths are just a typo | 00:46 |
| T42 | <edp_17> Oops, the device is kept rebooting pretty much instantly. | 00:46 |
| T42 | <edp_17> I have pushed the defconfig to github (branch cm-14.1-treltexx-v2) | 00:48 |
| T42 | 秦蒋豪焰 %lastname% was added by: 秦蒋豪焰 %lastname% | 00:50 |
| T42 | <elros34> yeah so not a type, basically you tell dhd modules to load firmware from itself. | 00:51 |
| T42 | <elros34> typo* | 00:51 |
| T42 | <elros34> so again: CONFIG_BCMDHD_FW_PATH is default path to firmware which is used when your wifi driver is loaded. If its build as module then /system partition is mounted and it can find firmware there but if it's builtin /system is not yet mounted | 00:53 |
| T42 | <edp_17> I've flashed the previous boot.img and now the device started. | 00:53 |
| T42 | <edp_17> I understand, thanks for explaining. | 00:54 |
| T42 | <elros34> I am not sure, your changes are not correct. Copy /system/etc/wifi/bcmdhd_sta.bin to /lib/firmware/ and set CONFIG_BCMDHD_FW_PATH=/system/etc/wifi/bcmdhd_sta.bin (simillar for nvram) | 00:55 |
| T42 | <edp_17> Okay, I try this. | 00:56 |
| T42 | <elros34> to CONFIG_BCMDHD_FW_PATH=/lib/firmware/bcmdhd_sta.bin | 00:56 |
| T42 | <ankaos> I ask to learn. how will you write? | 00:57 |
| T42 | <edp_17> @elros34 : Nope, the same result. The device is rebooting constantly. | 01:01 |
| T42 | <elros34> show your changes, did you revert config_modules and your other changes? | 01:03 |
| T42 | <edp_17> I pushed the latest defconfig to github. | 01:04 |
| T42 | <edp_17> I didn't remove config_modules=y | 01:05 |
| T42 | <edp_17> What is the /preload partition? Can I try to use these files from? | 01:11 |
| T42 | <edp_17> Or do you know the first partition what is mounted before the wifi starts? | 01:12 |
| T42 | <edp_17> I see that is /. That's why you suggested to put the files into /lib which is on /. | 01:14 |
| T42 | <elros34> first is initramfs then /data. All other partitions are mounted by systemd which is probably too late. BTW It's unlikley that changin these 2 paths cause kernel reboot | 01:14 |
| T42 | <edp_17> Hmm. then there is something else what caused that. | 01:16 |
| T42 | <edp_17> What about if I put those files somewhere in /data? | 01:16 |
| T42 | <edp_17> I see. | 01:18 |
| T42 | <edp_17> Okay, I go back to an earlier commit and re-built the kernel, once it works, I'll try to change those two paths and see whether it reboots. | 01:19 |
| T42 | <edp_17> @elros34 : You were right, those two lines didn't cause reboot. The root cause was my stupidity. I flashed the boot.img instead of hybris-boot.img. | 01:36 |
| T42 | <edp_17> However the wifi doesn't work. | 01:36 |
| T42 | <edp_17> With the files in /lib/firmware/ and with this in defconfig, it doesn't find any network. Only the circle is going round and round. | 01:37 |
| T42 | <edp_17> I need some sleep now. Thanks for you help! Good night. | 01:41 |
| T42 | <Amber %lastname%> hey guys i am having issues with sdk manage command can you please check below and help me about this | 03:47 |
| T42 | <Amber %lastname%> https://paste.ubuntu.com/p/XsdXP428QX/ | 03:47 |
| T42 | <Rodrigosolari> @Amber %lastname% [https://paste.ubuntu.com/p/XsdXP428QX/], Try in the sailfish-sdk | 03:49 |
| T42 | <Rodrigosolari> Not in the Systems root | 03:49 |
| T42 | <Amber %lastname%> how do i run sailfish sdk | 03:50 |
| T42 | <birdzhang> follow the HADK | 03:50 |
| piggz | rinigus: reckon we can port this to sfos? https://github.com/erfanoabdi/biometryd/blob/xenial/src/biometry/devices/android.cpp | 09:18 |
| rinigus | piggz: that's for fingerprint, right? | 09:21 |
| piggz | it is | 09:21 |
| piggz | ubports support for FP | 09:21 |
| rinigus | piggz: interesting. | 09:24 |
| piggz | yup | 09:24 |
| piggz | that gives us an example implementation, ust need to figue how to mash it with sfos | 09:25 |
| rinigus | piggz: ideally, we should join them in its development. if it is a daemon then it could run probably as it is on sfos | 09:26 |
| rinigus | and then we have to see how to add it into lockscreen unlocking... | 09:26 |
| piggz | rinigus: looking at the commit history, nothing since 2018, then added FP support | 09:31 |
| piggz | really, no development since 2017 | 09:32 |
| rinigus | piggz: but is developed now. like you could take popcorn, sit back, and follow | 09:33 |
| rinigus | we could ask in ubports channel regarding it. | 09:34 |
| piggz | yup ... all the new stuff is for FP support, just need to figure out how to utilise it | 09:34 |
| rinigus | piggz | 09:35 |
| piggz | i guess we start with trying to build | 09:35 |
| rinigus | (hitting enter before message) | 09:35 |
| rinigus | piggz: that's a good start. also need to figure out how to plug any kind of extra authentification into sfos. | 09:36 |
| rinigus | but I guess some developed patches can help - like maze login... | 09:37 |
| rinigus | ... I'll still continue with compass. want to use rotation_vector (or its geo form) as provided by android devices. changed sensorfwd accordingly, but something is still struggling with it. debugging / working on it | 09:38 |
| T42 | <Sid127> I have a question - how do I work with a prebuilt version of Lineage OS for my device? | 10:11 |
| T42 | RILuse was added by: RILuse | 10:36 |
| T42 | SilY@n %lastname% was added by: SilY@n %lastname% | 10:37 |
| T42 | <SilY@n %lastname%> Good afternoon! Please help me understand. I can't fix these configurations. https://pastebin.com/80FVqTyz | 10:39 |
| rinigus | mal: just got compass working using SENSOR_TYPE_ROTATION_VECTOR and going to test SENSOR_TYPE_GEOMAGNETIC_ROTATION_VECTOR | 11:25 |
| rinigus | that way it is using android-provided sensors, possibly done in hardware. sensorfw will get a new orientationadaptor(s) that use the rotation vector to calculate azimuth | 11:26 |
| rinigus | then the path is similar to what we have: orientationadaptor=hybrisrotationadaptor in sensorfw; qt Sensors.conf will use sensorfw.compass. | 11:27 |
| rinigus | so, we could add generic.compass for devices that don't have rotation vectors provided and use rotation vectors in hybris devices | 11:27 |
| rinigus | I presume that the rotation vector and its geo variant should be there for newer devices | 11:28 |
| mal | rinigus: I did try rotation vector before but had some issues | 11:33 |
| rinigus | mal: it looks to be working very well on tama | 11:33 |
| rinigus | geo option haven't tried yet, its building now | 11:34 |
| rinigus | mal: do you remember which issues were there? | 11:34 |
| mal | the values didn't make sense, maybe I did something wrong | 11:35 |
| mal | please push some code somewhere so I can test it | 11:35 |
| rinigus | mal: as I have to build at obs (some tech issues @home), its all out there, with every typo I made: https://git.sailfishos.org/rinigus/sensorfw/commits/rotation-dev | 11:36 |
| rinigus | adaptor at https://git.sailfishos.org/rinigus/sensorfw/tree/rotation-dev/adaptors/hybrisrotationadaptor | 11:37 |
| rinigus | if all works, I will clean up and make new branch with merged commits | 11:37 |
| rinigus | mal: ^ | 11:37 |
| mal | I will need to implement the binder side because that is used on x10 | 11:38 |
| rinigus | but, as you mentioned earlier, we need generic.compass for native ports | 11:38 |
| rinigus | mal: that will just require the corresponding data vector access. | 11:38 |
| mal | yes, I still think having sensor fusion sensorfw might also make sense, probably easier to maintain | 11:40 |
| rinigus | mal: there is info regarding calibration (see https://developer.android.com/reference/android/hardware/SensorEvent#sensor.type_rotation_vector:) | 11:40 |
| rinigus | but its not used currently. will have to figure that out too | 11:40 |
| mal | do you mean the values[4] is -1? | 11:41 |
| mal | to determine the accuracy | 11:41 |
| rinigus | mal: I am not using that value at all. as d->level_ is int, not sure how to convert that and what's expected radian accuracy to pass levels test in csd | 11:44 |
| mal | I think we can figure out some guess what is a good accuracy in degrees | 11:45 |
| rinigus | exactly! right now, its a dirty implementation and have to clean up a lot. but it is good for testing. | 11:45 |
| mal | did it give better values than generic.compass? | 11:46 |
| mal | rinigus: I think sensorfw has some filtering already for compass value so it might give ok-ish reaction | 11:47 |
| mal | of course assuming the values are correct | 11:47 |
| rinigus | mal: the end values were very close on tama. but note that the values were already before close to what physical compass would show | 11:48 |
| rinigus | mal: but response time with rotation_vector was very good. I could move phone fast and it would be able to follow with rather small delay | 11:49 |
| mal | yeah, well I consider 20 degree error a quite big one | 11:49 |
| mal | rinigus: generic.compass had a bit slow response, maybe the coefficient you modified affected that | 11:50 |
| rinigus | mal: for me, the angle was <10 degrees | 11:51 |
| rinigus | mal: generic.compass should be faster with smaller filter_coeff, at least with gyro. well, will have to test it later | 11:53 |
| rinigus | mal: but maybe I wrong. ignore it regarding generic compass. | 11:55 |
| T42 | <SilY@n %lastname%> WARNING: CONFIG_AUDIT is invalid | 11:55 |
| T42 | <SilY@n %lastname%> Value is: y | 11:55 |
| T42 | <SilY@n %lastname%> Allowed values : n, ! | 11:55 |
| T42 | <SilY@n %lastname%> Comment says: This will disable SELinux! That's ok, because hybris adaptations must not have SELinux, but if your device needs its support in kernel, set AUDIT=y and SELINUX_BOOTPARAM=y. Then disable them via kernel cmdline: audit=0 selinux=0. You can also leave audit enabled, if you don't plan to use systemd's containers: h | 11:55 |
| T42 | ttp://cgit.freedesktop.org/systemd/systemd/commit/README?id=77b6e19458f37cfde127ec6aa9494c0ac45ad890 | 11:55 |
| T42 | <SilY@n %lastname%> WARNING: CONFIG_MODULES is invalid | 11:55 |
| T42 | <SilY@n %lastname%> It is unset | 11:55 |
| T42 | <SilY@n %lastname%> Allowed values : y, ! | 11:55 |
| T42 | <SilY@n %lastname%> Comment says: optional, required for module support (Such as WLAN for example) | 11:55 |
| T42 | <SilY@n %lastname%> WARNING: CONFIG_CGROUP_MEM_RES_CTLR is invalid | 11:55 |
| T42 | <SilY@n %lastname%> It is unset | 11:55 |
| T42 | <SilY@n %lastname%> Allowed values : y, !, <=3.5 | 11:55 |
| T42 | <SilY@n %lastname%> Comment says: systemd (optional): http://0pointer.de/blog/projects/cgroups-vs-cgroups.html, only valid if kernel version <= 3.5 | 11:55 |
| T42 | <SilY@n %lastname%> WARNING: CONFIG_CGROUP_MEM_RES_CTLR_SWAP is invalid | 11:55 |
| rinigus | mal: SENSOR_TYPE_GEOMAGNETIC_ROTATION_VECTOR also works quite well and should be fine for compass. | 12:02 |
| T42 | <ankaos> Fwd from ankaos: 426/427] including vendor/xiaomi/msm8953-common/Android.mk ... | 12:02 |
| T42 | <ankaos> build/make/core/base_rules.mk:260: error: vendor/xiaomi/msm8953-common: MODULE.TARGET.SHARED_LIBRARIES.libantradio already defined by external/ant-wireless/ant_native. | 12:02 |
| T42 | <ankaos> 11:55:16 ckati failed with: exit status 1 | 12:02 |
| rinigus | I guess there would be Geo and plain rotation_vector adaptors allowing porters / users to select the favorite one | 12:02 |
| T42 | <ankaos> how fix this error? | 12:02 |
| mal | rinigus: there is some note in sensor docs about geomagnetic being more noisy in some cases | 12:16 |
| mal | rinigus: yes, I think both should be supported and porters can select which one works better | 12:17 |
| mal | rinigus: please make a branch with both so I can do some testing easily | 12:17 |
| rinigus | mal: will do. question is now how to reuse the code. looks like I will have to make separate folders, one per adapter. | 12:19 |
| mal | rinigus: good question, wondering if there could be some way to reuse things | 12:20 |
| rinigus | mal: the code is the same, just constructor will have to get rotation vector source. I'll see how to do that taking into account the build system | 12:21 |
| T42 | <ankaos> ı used to https://github.com/mer-hybris/hadk-faq#hybris-16-0 | 12:22 |
| T42 | <ankaos> what else? | 12:22 |
| mal | @ankaos remove the conflicting sources (maybe the one in external) and see if it builds | 12:24 |
| mal | rinigus: those hybris adaptors are all quite the same so maybe just different folders | 12:26 |
| mal | rinigus: some redesign of that might make sense, although the whole sensorfw is a bit overly complicated system | 12:27 |
| mal | so maybe doesn't make sense to do it now | 12:27 |
| T42 | <ankaos> okey testing your say | 12:27 |
| rinigus | mal: OK, will put something together... | 12:28 |
| mal | rinigus: so just different folders for now and we can think of other ways later | 12:29 |
| T42 | <ankaos> ninja: error: '/home/enes/hadk/out/target/product/tissot/obj/STATIC_LIBRARIES/libawk_main_intermediates/export_includes', needed by '/home/enes/hadk/out/target/product/tissot/obj/EXECUTABLES/recovery_intermediates/import_includes', missing and no known rule to make it | 12:29 |
| rinigus | mal: OK, will do | 12:29 |
| T42 | <ankaos> O.o | 12:29 |
| mal | add the missing dependency to manifest, check the lineage manifest for the line you need | 12:30 |
| T42 | <elros34> you had one mount unit (systemd.mount) to fix to get droid-hal-init working but instead you switched whole base to 16? | 12:43 |
| T42 | <ankaos> @elros34 [you had one mount unit (systemd.mount) to fix …], System.mount error not fix. I dont fint answer | 12:48 |
| T42 | <elros34> what do you mean? Does it fails to bind mount or droid-hal-init still fail? | 12:51 |
| rinigus | mal: https://git.sailfishos.org/rinigus/sensorfw/tree/rotation-dev has the both adaptors. | 12:58 |
| rinigus | mal: names are hybrisgeorotationadaptor and hybrisrotationadaptor | 12:58 |
| T42 | <ankaos> @elros34 [what do you mean? Does it fails to bind mount …], both | 13:28 |
| T42 | <elros34> you need to be more verbose: show journal, cat system.mount system_root.mount | 13:29 |
| T42 | <elros34> in a way that is clear which file do you show, not like in your previous paste | 13:33 |
| rinigus | mal: that constant in generic.compass should play a role iff you have gyro available. to me, it looks like the value which I used earlier is a reasonable balance. | 13:41 |
| T42 | <ankaos> @elros34 [you need to be more verbose: show journal, cat …], https://paste.ubuntu.com/p/FQF6ZbqVX5/ | 14:23 |
| T42 | <ankaos> https://paste.ubuntu.com/p/rDqcJ6ccRz/ and cat system.mount system_root.mount | 14:24 |
| T42 | <elros34> yeah that is wrong, you should not edit system_root.mount at all | 14:27 |
| T42 | <elros34> not sure if I gave you correct options earlier but system.mount should be like: https://paste.ubuntu.com/p/BMPdb3T5yr/ | 14:32 |
| T42 | <ankaos> @elros34 [yeah that is wrong, you should not edit system …], https://paste.ubuntu.com/p/RbSkdVJCtS/ | 14:32 |
| T42 | <ankaos> this is system_root | 14:32 |
| T42 | <elros34> yes that looks correct | 14:32 |
| T42 | <ankaos> @ankaos [https://paste.ubuntu.com/p/FQF6ZbqVX5/], this is journal | 14:40 |
| T42 | <ankaos> system.mount correct? | 14:40 |
| T42 | <elros34> no it's not I just gave you the correct one few minutes ago | 14:41 |
| T42 | <ankaos> @elros34 [no it's not I just gave you the correct one fe …], https://paste.ubuntu.com/p/FDVcKxWRTM/ | 14:42 |
| T42 | <ankaos> @elros34 [no it's not I just gave you the correct one fe …], this is system.mount | 14:43 |
| T42 | <ankaos> and only system | 14:44 |
| T42 | <elros34> like I said it's incorrect, use this: https://paste.ubuntu.com/p/BMPdb3T5yr/ | 14:44 |
| T42 | <ankaos> you sait this https://paste.ubuntu.com/p/8btqnBjYS8/ | 14:45 |
| T42 | <elros34> no, I gave 2 days ago wrong one with swapped Type and Options but for sure not that | 14:47 |
| T42 | <ankaos> @elros34 [no, I gave 2 days ago wrong one with swapped T …], https://paste.ubuntu.com/p/Xb5Z7Fsz5G/ | 14:48 |
| T42 | <elros34> focus, still incorrect | 14:49 |
| T42 | <ankaos> https://paste.ubuntu.com/p/Xb5Z7Fsz5G/ line? | 14:49 |
| T42 | <elros34> 6 ... | 14:50 |
| T42 | <ankaos> What=/system/system -> What=/system_root/system | 14:50 |
| T42 | <ankaos> ? | 14:50 |
| T42 | <ankaos> (Photo, 960x1280) https://irc.thaodan.de/.imgstore/kF8cUNIEpG.png | 14:53 |
| T42 | <ankaos> Than devire reboot | 14:53 |
| T42 | <elros34> after it reboot itself, try cat /proc/last_kmsg, and journalctl -f | 14:54 |
| T42 | <ankaos> I can't enter the terminal. | 14:57 |
| T42 | <elros34> in TWRP: 'touch /data/.stowaways/sailfishos/init_enter_debug2' Next time it will stop booting system until you use: 'echo continue > /init-ctl/stdin' | 15:01 |
| rinigus | mal: cleaned up and added level calculations. on tama, it returns heading accuracy as zero. adjusted level calculations to make csd happy if the accuracy is smaller than 10 degrees | 15:19 |
| rinigus | mal: all changes squashed at https://git.sailfishos.org/rinigus/sensorfw/tree/rotation | 15:20 |
| rinigus | now we need binder part and then it should be ready for upstream | 15:20 |
| rinigus | or do I miss something? | 15:20 |
| mal | I'll have a look | 15:41 |
| T42 | <ankaos> telnet not open | 15:53 |
| T42 | <ankaos> slot a install sailfish os b slot install recovery. | 16:02 |
| T42 | <ankaos> but not see sailfish os. | 16:02 |
| T42 | <ankaos> in twrp 'touch /data/.stowaways/sailfishos/init_enter_debug2' than reboot system. | 16:39 |
| T42 | <ankaos> @elros34 all right? | 16:42 |
| T42 | <ankaos> `'echo continue > /init-ctl/stdin'` in twrp or telnet? | 16:45 |
| mal | rinigus: seems like x10 has the same issue on rotation sensors than it has on orientation sensor, both only get couple of values and then it gets stuck | 17:04 |
| T42 | <ankaos> @ankaos ['echo continue > /init-ctl/stdin' in twrp or t …], because ı used this touch /data/.stowaways/sailfishos/init_enter_debug2 command . telnet not open Elros. | 17:05 |
| rinigus | mal: and it is not due to the binder, right? as it is expected to be the same as hal | 17:05 |
| mal | I can test hal version also | 17:06 |
| rinigus | mal: probably it is some hw issue then... on tama it works nicely | 17:06 |
| mal | or some bug in firmware | 17:06 |
| mal | or blobs | 17:07 |
| rinigus | yes, that's most probable | 17:07 |
| mal | rinigus: same with hal plugin | 17:12 |
| rinigus | mal: which is good as we can trust results from any of them... | 17:13 |
| mal | rinigus: the direction I get looks good but the problem is that it just won't update after couple of values | 17:13 |
| rinigus | mal: xperia10 can then use the generic.compass | 17:13 |
| mal | we had similar issue in the past with compass but that was fixed, not sure if this is related or not | 17:14 |
| rinigus | mal: I can keep it on for a while, no problem with that here | 17:14 |
| mal | rinigus: for example in orienteering compass app if I minimize the app and toggle the pause button in cover it updates the value | 17:15 |
| rinigus | mal: do you know whether xperia 10 compass works in aosp? | 17:15 |
| mal | not sure, would need some testing | 17:15 |
| mal | based on some info it might be broken in aosp also | 17:16 |
| rinigus | mal: I think that aosp apps are using rotation vectors for it. | 17:16 |
| rinigus | so it could be an indicator. well, if generic works, it should be ok as well | 17:16 |
| rinigus | but it is strange that it just stops and needs restart | 17:17 |
| mal | yes, the sensor does send data though, it just sends the same value over and over again | 17:17 |
| mal | which does suggest blob/firmware issue | 17:18 |
| rinigus | mal: what should we do now with the code? do I submit sensorfw for merge and you add binder part later? also I would like to submit qtsensors generic compass as well | 17:19 |
| rinigus | is there some specific MER# or JOLLA# bug for compass? | 17:20 |
| mal | you should cleanup the code a bit, some whitespace issue and some unused commented code | 17:24 |
| mal | also the binder codes are ok so just fix those | 17:24 |
| rinigus | mal: will do. | 17:29 |
| rinigus | mal: cleaned up and submitted for review - sensorsfw and qtsensors | 17:56 |
| mal | rinigus: a tiny nitpick, in other parts of the sensorfw code the { after if is in the same line, not on the next line | 18:07 |
| mal | rinigus: also please squash the commits into one in sensorfw | 18:08 |
| T42 | <ankaos> @elros34 [in TWRP: 'touch /data/.stowaways/sailfishos/in …], not work | 18:21 |
| rinigus | mal: re { - those seem to be mixed up in the code. I used the same as in hybrisorientationadaptor. looking at it, I don't think I have added any { }. but I don't mind to change it in that `if` | 18:23 |
| mal | rinigus: ah, interesting, I just happened to check the hybrisadaptor.cpp | 18:24 |
| mal | I'll grep the code a bit | 18:25 |
| rinigus | well, its a small thing, I have changed it already | 18:25 |
| mal | looks like the code is a bit of a mess | 18:27 |
| piggz | mal: ive installed the latest tooling and target locally.......but | 18:28 |
| piggz | when I try and install dbus-cpp-devel from you anbox repo, it fails with | 18:28 |
| piggz | Problem: nothing provides libstdc++.so.6(GLIBCXX_3.4.21) needed by libdbus-cpp5-5.0.0-1.1.15.jolla.armv7hl | 18:28 |
| piggz | have the hadk tagets not been updated yet with the new compiler etc? | 18:29 |
| rinigus | mal: change submitted and its rebuilding for testing at OBS | 18:30 |
| piggz | mal: yes, the latest is Device release is currently: 3.2.1.20 | 18:42 |
| piggz | atleast the target exists | 18:43 |
| piggz | http://releases.sailfishos.org/sdk/targets/ | 18:43 |
| piggz | just the lastes is pointing to the wrong one | 18:43 |
| mal | seems like latest is not updated yet | 18:45 |
| piggz | yup | 18:54 |
| T42 | <elros34> @ankaos this might be useful if you can't telnet: http://docs.halium.org/en/latest/porting/debug-build/early-init.html | 19:17 |
| T42 | <ankaos> @elros34 [@ankaos this might be useful if you can't teln …], http://docs.halium.org/en/latest/porting/debug-build/early-init.html#the-device-reboots-after-leaving-hybris-recovery use | 19:23 |
| T42 | <ankaos> and ~ # echo continue > /init-ctl/stdin | 19:24 |
| T42 | <ankaos> /sbin/sh: can't create /init-ctl/stdin: nonexistent directory | 19:24 |
| T42 | <elros34> I don't get, so now you were able to telnet? Which port? | 19:28 |
| T42 | <ankaos> telnet 192.168.2.15 2323 | 19:28 |
| T42 | <elros34> so now grab logs ask previous. last_kmsg will be available only after kernel crash so it might be missing | 19:30 |
| T42 | <ankaos> @elros34 [so now grab logs ask previous. last_kmsg will …], telnet 192.168.2.15 not work | 19:37 |
| T42 | <ankaos> `touch /data/.stowaways/sailfishos/init_enter_debug2` not open telnet | 19:37 |
| T42 | <elros34> sorry I don't get you at all. You should already learn how to check whether sailfish starts at all(host dmesg) | 19:41 |
| T42 | <ankaos> dmesg https://paste.ubuntu.com/p/SVwj2PhyP2/ | 19:45 |
| kalube | @ankaos are you building on an external drive? | 19:47 |
| T42 | <elros34> don't show me it, just tell whether it 's correct then use instruction from hallium: enp*: renamed from usb0 in dmesg | 19:49 |
| T42 | <ankaos> Building sailfish for a1 | 19:51 |
| piggz | mal: string link error in dhd build regardin img2simg... | 20:36 |
| piggz | https://paste.mozilla.org/gHF9mN2h | 20:37 |
| piggz | the function is in the included sources | 20:37 |
| piggz | so not sure why its not linking | 20:37 |
| T42 | <elros34> @ankaos could you answer kalube question. It could be quite important because external drive can be mounted with nosuid,nodev options. Did you have any /dev/ errrors when creating sfos image? | 20:44 |
| T42 | <ankaos> where will I look at it? | 20:44 |
| mal | piggz: why didn't you have the issue before? | 20:52 |
| T42 | <elros34> @ankaos in mount output, mic output | 20:52 |
| piggz | mal: i dont know ... all ive done is update the tooling/target | 20:52 |
| T42 | <ankaos> @elros34 [@ankaos in mount output, mic output], is this https://paste.ubuntu.com/p/9QvRyfC9wC/ | 20:57 |
| mal | piggz: could it be that you have some old leftover things in system/core repo from the previous builds | 20:59 |
| piggz | i already tried deleting some object files, ill try some more | 21:00 |
| piggz | mal: yes, deleting obejcts from base/ helped | 21:04 |
| T42 | <ankaos> Sorry for not knowing as much as you. | 21:06 |
| piggz | mal: why would a new target create these errors tho! https://paste.mozilla.org/zVkOEOHF | 21:09 |
| mal | piggz: I think the detection of unpackaged files was fixed | 21:15 |
| T42 | <elros34> rpm fix was finally merged in 3.3.0 | 21:15 |
| mal | piggz: it used to be broken for some time | 21:15 |
| piggz | ok | 21:15 |
| T42 | <ankaos> @ankaos [is this https://paste.ubuntu.com/p/9QvRyfC9wC/], @elros34 Did you see it? | 21:18 |
| T42 | <elros34> sure but how this is related to question whether you use external drive or 'mount' command output, mic errors? | 21:19 |
| T42 | <ankaos> I still couldn't figure out how to take care of it. | 21:19 |
| T42 | <elros34> just type mount | 21:20 |
| T42 | <ankaos> @elros34 [just type mount], https://paste.ubuntu.com/p/gHkjvKcVbs/ | 21:21 |
| T42 | <elros34> on your host system | 21:22 |
| T42 | <ankaos> @elros34 [on your host system], device or pc? | 21:23 |
| kalube | > host | 21:30 |
| kalube | that would be the one with the keyboard on it | 21:30 |
| piggz | unless its a pro1 :D | 21:31 |
| kalube | I don't think we need any more complication here -_- :P | 21:32 |
| T42 | <ankaos> @elros34 [on your host system], https://paste.ubuntu.com/p/BfJvSvNPfk/ @elros34 and Kalube | 21:35 |
| T42 | <elros34> does 'df $ANDROID_ROOT' returns /dev/sda3? | 21:38 |
| T42 | <ankaos> @elros34 [does 'df $ANDROID_ROOT' returns /dev/sda3?], https://paste.ubuntu.com/p/SNkrz5RCT6/ | 21:39 |
| T42 | <elros34> that variable is valid in sdk, so just answer whether you are using /media/enes/1E8C40128C3FE2C71 to build sailfish? | 21:41 |
| T42 | <ankaos> https://paste.ubuntu.com/p/3hGK9RTsfQ/ maybe. | 21:44 |
| T42 | <ankaos> https://paste.ubuntu.com/p/MdPscYMyqT/ | 21:46 |
| T42 | <elros34> ok so you are not using external drive so forget about it | 21:47 |
| T42 | <ankaos> there are only internal drive | 21:48 |
| T42 | <ankaos> Another reason may be due to restart? | 21:54 |
| T42 | <elros34> no more guesses, you need to get logs | 21:55 |
| T42 | <ankaos> how? | 21:55 |
| T42 | <ankaos> journalctl -f etc. | 21:56 |
| kalube | @ankaos you should be reading and re-reading the hadk and any other documentation you can find to get an understand of what's going on before asking so many questions over here, we can only help so much but if you can't figure it out for yourself you'll end up getting stuck | 21:56 |
| T42 | <ankaos> then i will wait. If someone says, I use it. | 22:08 |
Generated by irclog2html.py 2.17.1 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
