Monday, 2020-01-20

Danct13elros34 right, so do you think that qseecomd is the one causing this?04:22
Danct13since from the beginning of my port, i have never disabled it04:23
Danct13so it keeps working04:23
Danct13i may try to disable it and see if it does something later04:36
Danct13mal ^ do you think that too04:56
T42<picolopoco> @MarcoDS_bit [Yep the one from TheMuppets], hello06:59
T42Boris %lastname% was added by: Boris %lastname%07:46
T42庄生贵 %lastname% was added by: 庄生贵 %lastname%08:52
*** OhYash1 is now known as ohyash14:23
*** OhYash1 is now known as ohyash14:52
*** OhYash1 is now known as ohyash15:34
*** OhYash1 is now known as ohyash16:07
*** OhYash1 is now known as ohyash16:47
*** OhYash1 is now known as ohyash17:33
Danct12_back on hybris-16.0, can anyone help me with droid-hal-init: Failed to initialize property area?17:51
Danct12_selinux is disabled according to journalctl -b, however it still loads file_contexts17:51
T42<elros34> show journalctl17:51
T42<elros34> full17:51
T42<elros34> "Failed to initialize property area" its there only because droid-hal-init restarts17:57
Danct12_not some selinux related errors?17:58
*** OhYash1 is now known as ohyash17:59
T42<NotKit> (Voice, 1s)
T42<elros34> no, droid-hal-init can be started only once18:01
T42<picolopoco> @elros34 ["Failed to initialize property area" its there …], hello18:06
Danct12_right, but you have any idea about this?18:06
T42<elros34> have you checked that ueventd*rc is in your out/* directory. That is most common issue18:06
T42<picolopoco> @elros34 [have you checked that ueventd*rc is in your ou …], please check Inbox18:07
Danct12_ueventd.rc is in the root directory18:07
*** OhYash1 is now known as ohyash18:08
Danct12_so it's there18:08
T42<elros34> There were also devices which had different udevent*rc in vendor partition on device so check that also18:08
Danct12_yep, found one in /vendor18:10
Danct12_maybe it's because of this?
Danct12_nope, that patch was applied to hybris-16.0 so it's not18:14
T42<elros34> no, I told you "Failed to initialize property area" is only because droid-hal-init restart but it shoudnt. It start nicely at first time. Did you compare these uevent* files18:15
Danct12_they're different, the one in vendor contains fingerprint sensor18:17
Danct12_and kgsl, so on18:17
T42<elros34> I would advice you to copy it to out/*/root directory with different name so it will be picked up when you rebuild droid-hal18:18
Danct12_ueventd_qc.rc sounds good then18:19
T42<elros34> some name which will match:
Danct12_still the same issue though19:42
Danct12_you need logcat for the first stage?19:45
T42<elros34> you always grab fresh logs after you change something. logcat can be usuful to figure out why some services fails. First check whether new udev rules are generated /lib/udev/rules.d/999-android-system.rules and contains kgsl, ion and so on21:06

Generated by 2.17.1 by Marius Gedminas - find it at!