| 19 Nov 2024 |
 atemu12 | And it's like in the best position to tell you because the function logging this error likely has all the devices it's waiting on readily available. | 05:41:41 |
 oak 🏳️🌈♥️ | There is sensors list file needs to be updated otherwise it will delay boot for 30 seconds in /vendor/persist/sensors/sensors_list.txt | 05:43:34 |
| oak 🏳️🌈♥️ | It actually gives useful error message in the end: ```
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:531, some mandatory sensors not available even after 30 seconds, giving up.
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:533, 3 missing sensor(s)
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, mag
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, mag_cal
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, rotv
| 05:45:29 |
| oak 🏳️🌈♥️ | * It actually gives useful error message in the end: ```
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:531, some mandatory sensors not available even after 30 seconds, giving up.
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:533, 3 missing sensor(s)
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, mag
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, mag_cal
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, rotv | 05:45:42 |
| oak 🏳️🌈♥️ | * It actually gives useful error message in the end:
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:531, some mandatory sensors not available even after 30 seconds, giving up.
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:533, 3 missing sensor(s)
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, mag
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, mag_cal
11-19 07:44:52.903 992 992 E sensors-hal: wait_for_mandatory_sensors:536, rotv | 05:45:48 |
| atemu12 | Now the question is whether it actually doesn't have those sensors or whether the HAL/BLOBs are broken | 05:47:23 |
| oak 🏳️🌈♥️ | Is there easy way within Robotnix to just get access to the extracted Android source tree? | 06:29:08 |
| atemu12 | debug-enter-env | 06:29:30 |
| oak 🏳️🌈♥️ | Just found it from the documentation | 06:31:04 |
| oak 🏳️🌈♥️ | That sensors-hal error is coming from binary file :( | 06:43:50 |
| oak 🏳️🌈♥️ | I tried to ask questions in the #lineageos iRC-channel but luk1337 answered me "if you upgrade to 21/22 this year, ask me again" x) | 16:43:55 |
| oak 🏳️🌈♥️ | * I tried to ask questions in the #lineageos IRC-channel but luk1337 answered me "if you upgrade to 21/22 this year, ask me again" x) | 16:44:41 |
| oak 🏳️🌈♥️ | I'm wondering should I try upgrading to 21, then I could at the same time test Atemu's open PR | 16:45:26 |
|  countoren joined the room. | 19:46:58 |
| countoren | Hi all, I have a small staticlly linked cross compiled server that runs on propitiatory AOSP, it works nice with libusb, and rxcpp but now I would like to have write logs to logcat, any of you have something to point me too for liblog for a nix statically linked executable ? | 19:49:43 |
| countoren | * Hi all, I have a small statically linked cross compiled server that runs on propitiatory AOSP, it works nice with libusb, and rxcpp but now I would like to have it write logs to logcat, any of you have something to point me too for liblog for a nix statically linked executable ? | 19:50:22 |
| atemu12 | In reply to @oak:universumi.fi
I'm wondering should I try upgrading to 21, then I could at the same time test Atemu's open PR I've been meaning to give it a go on my daily driver but I need to verify that my backup procedure still works first | 22:21:31 |
| atemu12 | In reply to @countoren:matrix.org
Hi all, I have a small statically linked cross compiled server that runs on propitiatory AOSP, it works nice with libusb, and rxcpp but now I would like to have it write logs to logcat, any of you have something to point me too for liblog for a nix statically linked executable ? I don't think this is the right channel for that. Robotnix concerns building AOSP itself using Nix. I'd recommend an Android programming forum instead as this has little to do with Nix; we don't do anything magical for libraries | 22:24:39 |
| oak 🏳️🌈♥️ | I'm also trying if I can use my old OnePlus 5T as a test phone | 22:27:58 |
| atemu12 | Cheeseburger hi-five | 22:33:47 |
| countoren | In reply to @atemu12:matrix.org
I don't think this is the right channel for that. Robotnix concerns building AOSP itself using Nix. I'd recommend an Android programming forum instead as this has little to do with Nix; we don't do anything magical for libraries thanks Atemu I think I will rollback to something alot simpler and just add spdlog and use it instead | 23:28:01 |
| 20 Nov 2024 |
|  Inayet removed their profile picture. | 00:59:41 |
| 22 Nov 2024 |
| oak 🏳️🌈♥️ | I've been also having a look at upgrading to lineage-21, it's mostly ok but there are few things, mostly related to signing again | 19:51:58 |
| atemu12 | Yeah I had to refactor some things | 19:52:33 |
| atemu12 | Feel free to PR a fix | 19:52:57 |
| oak 🏳️🌈♥️ | I rebased your lineageos-21 branch from the PR, on top of my development branch, and then I did some modifications already on top of that | 19:54:39 |
| oak 🏳️🌈♥️ | I also noticed that my previous PR for adding support for Android 13 signing is incomplete, it lacks some of those new APEX keys, because on LineageOS builds we were doing something called APEX Flattening which basically skips the APEX signing step | 19:55:35 |
| oak 🏳️🌈♥️ | but the APEX flattening has now been completely removed in Android 14 and LineageOS 21, so the issue became apparent | 19:55:57 |
| atemu12 | Just open PRs, I will cherry-pick or merge | 19:56:38 |
|  👉@crystallinefire:chat.solarpunk.moe changed their profile picture. | 20:26:30 |
