#include <std_disclaimer.h> /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at us for messing up your device, we will laugh at you. * */
Official builds can't include some changes that are included in unofficial builds. Also official maintainer should continue to support and improve builds for supported device...
Not all changes can be included in device trees. Some patches are picked from gerrit. I've already answered similar question here.@z3DD3r I am trying to compile LineageOS 17.1 with your sources and the build runs through successfully.
But I am always facing the same issue after flashing (clean, factory reset and no additional zips) the image: The boot animation is displayed very slowly (~1 frame per second). Only the animation seems to be affected, as you can hear the screen locking sound after a couple of minutes while the animation is still running. Once the animation is finished after 5+ minutes, the screen is black, since the device locked itself in the meantime. If you turn the screen on, unlock it and interact with the device, it runs just fine. Snappy and quick, as you would expect. It seems to be just the boot animation, that is flawed in my personal builds, but not in your builds.
Is there anything I am missing or doing wrong? Are you building from exactly the same sources that you published? Have you also seen this issue?[/code]
Did some further investigation. Had a Whatsapp call yesterday and had the logging running while the call was going on. Found the following lines before the camera was not showing new frames anymore:
[05-10 10:13:43.765 383:22238 E/mm-camera]
module_faceproc_port_event_func:886] MCT_EVENT_MODULE_BUF_DIVERT 131074, Cannot start FD, active 20003, frameid 22715 0, native 1, mapped 1 1
[05-10 10:13:43.784 306:22245 E/Parcel]
fcntl(F_DUPFD_CLOEXEC) failed in Parcel::read, i is 0, fds is -1, fd_count is 1, error: Too many open files
[05-10 10:13:43.790 306:22245 E/Camera3-OutputStream]
getBufferLockedCommon: Stream 0: Can't dequeue next output buffer: Invalid argument (-22)
[05-10 10:13:43.790 306:22245 W/Camera2Client]
notifyError: Received recoverable error 3 from HAL - ignoring, requestId 10000001
So it seems filedescriptors remain open? Most likely something in the ROM somewhere?