**** BEGIN LOGGING AT Fri Nov 13 02:59:57 2020 Nov 13 05:40:27 can you guys create helium boot for redmii 5a Nov 13 05:42:13 Only the redmi 5a owners can do that Nov 13 07:39:16 @ianand007 [can you guys create helium boot for redmii 5a], Is it `pine`? Nov 13 07:39:29 Or `pine` is 4a... Nov 13 07:39:55 Its 4a.. I cant help. Nov 13 07:55:54 Hey there. LXC Android container starts fine at boot, but when I manually restart it, it'll fail. Is this normal or do I need to debug it? Nov 13 07:56:16 Also, the test_vibrate command works only when the container is not running. Nov 13 07:57:51 restart does not work on my phone either Nov 13 08:02:09 @Hulisen Mickey [restart does not work on my phone either], Does it start successfully on boot for you? Nov 13 08:03:01 No, restart lxc@android and reboot will not work Nov 13 08:04:41 @Hulisen Mickey [No, restart lxc@android and reboot will not work], It starts fine on boot for me. But, when I try to manually restart the container service, it fails. Nov 13 08:05:16 @Korko123 [It starts fine on boot for me. But, when I try to manually restart the container …], me too Nov 13 08:05:42 Oh ok... Anyway, managed to get vibrator working. Nov 13 08:05:51 [Edit] Oh ok... Anyway, I've managed to get vibrator working. Nov 13 08:06:22 It would be great if the graphics could work Nov 13 08:06:38 The test_vibrate command only works when LXC container is not running. Otherwise, I get the "Floating point exception" Nov 13 08:07:38 https://pastebin.com/MRyjVwRi … Here's my dmesg log. Nov 13 08:09:40 @Korko123 [It starts fine on boot for me. But, when I try to manually restart the container …], that's expected Nov 13 08:10:22 @NotKit [that's expected], What does "Floating point exception" mean? Nov 13 08:10:45 application crash, possibly somewhere in libhybris Nov 13 08:11:05 what is your device, Halium version and rootfs? Nov 13 08:11:11 @NotKit [application crash, possibly somewhere in libhybris], It only happens when LXC container is active Nov 13 08:12:15 @NotKit [what is your device, Halium version and rootfs?], asus_Z00ED, 7.1, Plasma mobile Nov 13 08:12:49 This device hasn't been ported to Halium yet. So, I'm the first one who did this. Nov 13 08:16:17 @NotKit [application crash, possibly somewhere in libhybris], Here's the output of strace test_lights: … https://pastebin.com/Ta0WMDB2 Nov 13 09:00:19 PEARL beaudry was added by: PEARL beaudry Nov 13 09:56:28 FERRO Tuominen was added by: FERRO Tuominen Nov 13 13:16:11 meloche cole was added by: meloche cole Nov 13 14:09:41 Dorsey annelies was added by: Dorsey annelies Nov 13 16:50:33 Any Halium 9 porter out there: Do you have long-term experience reports regarding telephony with ofono ready, and/or would you be willing to write up some report on how stable you feel it works on your device? We're having some trouble on the Pixel 3a and other devices with how well telephony works in general, so I'd like to get some i Nov 13 16:50:34 nput and pick your brains. Nov 13 18:16:16 @fredldotme [Any Halium 9 porter out there: Do you have long-term experience reports regardin …], I can give you some hints for H9 GSI on the OP3... unfortunatly I couldn't get further in troubleshoot as I'm not able to enable ril debug. Nov 13 18:17:14 It's interesting that ofonod seems to crash in the same way than the pinephone, while i've no issue with H7.1 (Except a wakelock that I've extended) Nov 13 18:17:48 @Ern_st [I can give you some hints for H9 GSI on the OP3... unfortunatly I couldn't get f …], `setprop persist.vendor.radio.adb_log_on 1` doesn't help? Nov 13 18:18:24 Nope, It doesn't create any log in the ril repertory. I was not having issue to enable it on H7.1 Nov 13 18:18:38 I don't know if it's GSI related Nov 13 18:18:44 it should log to the radio buffer of logcat Nov 13 18:19:07 @fredldotme [Any Halium 9 porter out there: Do you have long-term experience reports regardin …], Yes, two weeks ago it was freezing lomiri, but right now it seems to be working fine, I’ll flash a new build again to verify if it is still working good Nov 13 18:19:13 Yes but mainly ofonod ouptut Nov 13 18:19:32 @fredldotme [Any Halium 9 porter out there: Do you have long-term experience reports regardin …], [Edit] Yes, two weeks ago it was freezing lomiri when making or picking call + no audio being routed either side but right now it seems to be working fine, I’ll flash a new build again to verify if it is still working good Nov 13 18:21:02 @ItsMeShouko [Yes, two weeks ago it was freezing lomiri when making or picking call + no audio …], That would be helpful. Best case you test it over the course of a few days, try calls every once in a while to verify it still calls correctly Nov 13 18:28:02 @fredldotme, In the case of the OP3, modem or ril or ofono crash randomly and it's visible through the log by the loss cell signal strength (in ofonod debug mode), without restarting/recovering. … In this state, trying some ofonod scripts to play with the modem doesn't change anything, in the mean time the graphical interface shows a sig Nov 13 18:28:03 nal cell strength (due to the lack of update). So the user cannot realize the issue until he tries to call. On dbus due to ofonod crash there is a loss of id. … To overcome that, I've made a small watchdog looking into the log file, if signal cell is loss I force a restart of ofonod (to restart ril/ofonod) and telepathy-ofonod (to get the updated d Nov 13 18:28:03 bus id). … Very similar too: https://gitlab.com/ubports/community-ports/pinephone/-/issues/229 Nov 13 20:13:48 is it possible to use halium 9 for a port? Nov 13 20:18:03 @Ern_st [@fredldotme, In the case of the OP3, modem or ril or ofono crash randomly and it …], Could you point me to the log output you expect in that watchdog? Just to check if that's indeed the problem I'm having. Nov 13 20:19:44 @fredldotme [Any Halium 9 porter out there: Do you have long-term experience reports regardin …], If u mean powersaving bugs … I have an idea … In pre-halium9 canonical/ubports didn't address powerhal on platform-api … So repowerd wouldn't switch interactive mode on screen lock Nov 13 20:20:33 I think that cause some errors on the other parts of system at long time sleeping Nov 13 20:21:11 I'm not testing my phones with simcard usually … But i had wifi disconnecting bug Nov 13 20:22:11 @erfanoabdi [I'm not testing my phones with simcard usually … But i had wifi disconnecting bug], those telephony bugs seem to become noticeable and annoying exactly once phone is away from desktop Nov 13 20:22:52 Worth testing it without powerhal Nov 13 20:23:18 Just remove it from manifest.xml.. Nov 13 20:24:17 [Edit] I'm not testing my phones with simcard usually … But i had wifi disconnecting bug … Which is not happening on mobian Nov 13 20:29:51 @erfanoabdi [Just remove it from manifest.xml..], trying that right now, let's see if this changes anything. Nov 13 20:30:21 You mean commenting out the `android.hardware.power` right? Nov 13 20:32:47 @erfanoabdi also, could you point me to where that interfacing with the power HAL happens exactly? Nov 13 20:33:12 @fredldotme [You mean commenting out the android.hardware.power right?], yep Nov 13 20:34:12 @fredldotme [@erfanoabdi also, could you point me to where that interfacing with the power HA …], https://github.com/ubports/platform-api/blob/xenial_-_android9/android/hybris/ubuntu_hardware_booster_hidl_for_hybris.cpp … the old booster was broken Nov 13 20:36:02 https://github.com/ubports/repowerd/blob/5c9e02926e791a9eae54aff3a4b943fcad7ef0a3/src/core/default_state_machine.cpp#L794 Nov 13 20:36:32 I remember now, thanks. Let's see if this is working too well now lol … And if this really turns out to be a problem I guess adding some kind of property to not use the power HAL at all would suffice. Nov 13 20:36:52 yep Nov 13 20:36:56 Just wondering how to do it in a GSI friendly way Nov 13 20:37:41 it's good for powersaving and android does interactive mode switching too Nov 13 20:39:48 I guess so. I really would like to keep power savings up as much as possible. Just testing it as a last resort thing. Nov 13 20:45:36 yes, if it turns to be a problem, we can disable it as hotfix, but really need to understand what is actually wrong Nov 13 21:45:09 @fredldotme [Could you point me to the log output you expect in that watchdog? Just to check …], So: … the script comparing stable output : Upower Vs Cell signal strength : https://paste.ubuntu.com/p/KHS5DMNw3y/ … everything fine : https://paste.ubuntu.com/p/WPzSyx7CmT/ … rild/ofonod issue : https://paste.ubuntu.com/p/WgyXvdQhx7/ … For ins Nov 13 21:45:09 tance frequency of restart this afternoon : https://paste.ubuntu.com/p/zDydBsrHN7/ so far it's totally random. … With this bandage, so far I'm happy I can use the phone daily with the drawback to be without coverage couple of minute per day. Nov 13 22:09:36 (Photo, 1280x960) https://irc.ubports.com/H7rfzlMb.png I am following the online guide step by step but I have some problems with the complete compilation, what should I put between the two manifest? the official ones, those of Los or those of themuppets Nov 13 22:09:42 @CinicoDoc [], Bq x2 Nov 13 22:41:45 (Photo, 1280x960) https://irc.ubports.com/Nvv7MQhZ.png I think I understand, if not, I'll wait straight on **** ENDING LOGGING AT Sat Nov 14 02:59:56 2020