| 19 Nov 2024 |
 oak 🏳️🌈♥️ | I added instantnoodlep to the supported devices because in the other PR it was commented it would bring more comfort :) | 05:31:58 |
 Atemu | Cool, thanks :) | 05:32:19 |
| oak 🏳️🌈♥️ | I don't know how the boot time could be improved, maybe it didn't apply the usual optimizations it does when doing OTA update (which take long time). Maybe doing first OTA update fixes it | 05:34:17 |
| Atemu | Well, try a reboot and see whether it's still as bad | 05:34:38 |
| oak 🏳️🌈♥️ | Already tried couple of times | 05:34:55 |
| Atemu | And it's reproducible? | 05:35:04 |
| Atemu | Hm | 05:35:09 |
| oak 🏳️🌈♥️ | Yeah on LineageOS 19.1 the squid logo ball was only going over the line for like 3-5 times usually, now it takes 20 bounces | 05:35:51 |
| Atemu | You could have a look at logcat and perhaps get a glance of what's taking so long | 05:36:05 |
| Atemu | There isn't anything as nice as systemd-analyze on Android though that I know of | 05:36:26 |
| Atemu | FWIW it's not taking that long on my device | 05:36:40 |
| Atemu | Have you added a bunch of files to userdata in the process of updating by chance? e.g. to create a backup? | 05:37:23 |
| Atemu | I once had super long boot times and it was caused bu Android running some SElinux re-labelling or some shit | 05:37:59 |
| Atemu | And that scales poorly with the amount of files you have | 05:38:19 |
| oak 🏳️🌈♥️ | It looks like it is waiting forever for some sensor and then it timeouts and boots finally | 05:38:42 |
| Atemu | Huh | 05:38:53 |
| Atemu | I wonder if that's an upstream LOS bug | 05:38:58 |
| oak 🏳️🌈♥️ | 11-19 07:39:20.502 995 995 I sensors-hal: wait_for_mandatory_sensors:507, some mandatory sensors not available yet, will wait for 23 seconds... | 05:40:09 |
| oak 🏳️🌈♥️ | It waits until it goes to 0 seconds and then gives up I guess | 05:40:26 |
| Atemu | I hate this kind of error message with a passion | 05:40:58 |
| Atemu | "some" | 05:41:02 |
| Atemu | Gee thanks | 05:41:08 |
| Atemu | 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 |
| Atemu | 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 |
| Atemu | debug-enter-env | 06:29:30 |
