search

mstaz / backup_android_device_fairphone_fp3

Android / LineageOS 16 device tree for Fairphone 3
4 stars 0 forks source link

Errors in adb logcat while booting #2

Open dk1978 opened 4 years ago

dk1978 commented 4 years ago

Just did my first complete build. There were issues with vbmeta and AVB as described in README.md. Also flashed userdata to eliminate some error messages due to missing files there.

I noticed these errors in the adb logcat dump, which seem to be serious: 02-01 02:40:43.680 455 455 E QSEECOMD: : Init dlopen(libsecureui.so, RLTD_NOW) is failed.... dlopen failed: library "libsecureui.so" not found

Will try to fix this by editing device/fairphone/fp3/proprietary-files.txt.

Regards, Daniel (dk1978)

mstaz commented 4 years ago

Hi Daniel, Nice to hear. Yes, I also saw this and trying to fix it with copying the stuff via proprietary-files.txt. However I guess QSEECOMD is not that important for the start. As far as I know this is just the secure environment stuff, e.g. for securely storing keys etc. I'm still trying to get the display running. To me it seems like the hardware/qcom/display stuff may miss support for some hw part. Also trying to fix it with the binaries from the stock firmware. BR, Max

dk1978 commented 4 years ago

I just noticed that I had a messed up vendors partition, possibly due to a prior attempt of running extract-files.sh with incorrect mounts set up. Anyway, extract-files.sh still complained about missing sources for "cneapiclient.xml" and "com.quicinc.cne.xml". Managed to eliminate that by supplying correct paths.

Concerning the display stuff - the boot animation appears to be running, so things do not look that bad to me. I will keep examining error messages in the adb logs.

mstaz commented 4 years ago

Which boot animation do you mean? For me only the black screen with Fairphone logo appears. Then the screen turns black and after few seconds it seems to switch off. In logcat I can see these messages:

04-26 02:00:22.526 590 666 I SDM : HWCSession::UEventHandler: Uevent FB0 = change@/devices/virtual/graphics/fb0 04-26 02:00:22.528 590 713 W SDM : HWCSession::ValidateDisplay: panel is in bad state, resetting the panel 04-26 02:00:22.528 590 713 I SDM : HWCSession::ResetPanel: Powering off primary 04-26 02:00:22.528 590 713 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 0

I already added several display/graphics related proprietary files that may be related and also added several properties that I missed as well. Unfortunately without success so far.

mstaz commented 4 years ago

Ah, forgot to perform a factory reset. Now the error is gone and screen doesn't turn off anymore. However still nothing is shown on display.

mstaz commented 4 years ago

It seems like I simply missed to flash the dtbo partition. I'll give it another try and will update the README accordingly.

dk1978 commented 4 years ago

I made some progress. A lot of the error message due to missing binaries are gone from the adb logcat output.

I also configured the device to use a dedicated product partition - this is what the stock system does, and is probably what we should be doing as well. See my latest commit.

I will pull your changes to the audio kernel stuff and see how far that get us now. I expect there will still be more problems, and the device will likely reboot without showing a lock screen.

Tomorrow I am going to have a more systematic look at what is going on. 1) I will look at the running (Magisk-rooted) stock system and examine all devices, permissions and running native processes/daemons, especially all the stuff coming from the vendor partition.

2) I will deactivate the Android services in the current lineageOS-build from the init.rc files and try to stop the system from automatically rebooting. This should give us the opportunity to log in with adb and do the same thing as in 1).

3) If 2) works, then I will have a look at what happens when individual vendor services or daemons are started manually.

mstaz commented 4 years ago

Nice, I'll give that a try. Maybe this solves the issues I face currently.

Did you try the audio kernel modules you added in your branch? The problem I see currently is that although modules are loaded, the audio devices are not available after booting (/dev/snd/...). And it seems that this prevents AudioFlinger from starting what causes the reboot after some time. I just added some more audio configs, which seem to be necessary anyway.

I also catched a logcat and dmesg from stock firmware to be able to compare. I'll try to share it here. I can recommend to mount the system and vendor image on PC. This makes it easy to check for configs and files in stock fw. I guess you already do that 😉

What about an IRC channel #fairphone3 on freenode or similar?

dk1978 commented 4 years ago

I just pulled in your new branches to the device and kernel trees. Will look at the results now.

Also created a #fairphone3 channel on freenode!

On 12.03.20 19:49, Max wrote:

Nice, I'll give that a try. Maybe this solves the issues I face currently.

Did you try the audio kernel modules you added in your branch? The problem I see currently is that although modules are loaded, the audio devices are not available after booting (/dev/snd/...). And it seems that this prevents AudioFlinger from starting what causes the reboot after some time. I just added some more audio configs, which seem to be necessary anyway.

I also catched a logcat and dmesg from stock firmware to be able to compare. I'll try to share it here. I can recommend to mount the system and vendor image on PC. This makes it easy to check for configs and files in stock fw. I guess you already do that 😉

What about an IRC channel #fairphone3 on freenode or similar?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/mstaz/android_device_fairphone_fp3/issues/2#issuecomment-598359041, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABHZVU7GTD267U65ZAR34STRHEVCDANCNFSM4LCSODUA.

danascape commented 4 years ago

Which boot animation do you mean? For me only the black screen with Fairphone logo appears. Then the screen turns black and after few seconds it seems to switch off. In logcat I can see these messages:

04-26 02:00:22.526 590 666 I SDM : HWCSession::UEventHandler: Uevent FB0 = change@/devices/virtual/graphics/fb0 04-26 02:00:22.528 590 713 W SDM : HWCSession::ValidateDisplay: panel is in bad state, resetting the panel 04-26 02:00:22.528 590 713 I SDM : HWCSession::ResetPanel: Powering off primary 04-26 02:00:22.528 590 713 I SDM : DisplayBase::SetDisplayState: Set state = 0, display 0

I already added several display/graphics related proprietary files that may be related and also added several properties that I missed as well. Unfortunately without success so far.

You fixed this log by performing a factory reset ?

danascape commented 4 years ago

Seriously ?