Hi, yeah, this was just linked to #replicant IRC channel: <https://forum.xda-developers.com/droid-ultra/development/rom-cyanogenmod-13-obake-t3319958/page36>. So the patch was ifdef'd because it broke on one device. I think we might be using software audio/video decoding/encoding and in lineageos it might be hardware so they might use different libraries and not have come across this on other than that 1 device which was then not fixed.
Joonas Marcos Marado: > That ifdef is in there because this will happen to some devices but > not others (and we should investigate each replicant device to see > which of them are affected, it might be all as you assume, but it > might be none). Unfortunately, for the devices you see this happen, it > probably means that one of the propriatery files you are copying from > the device was depending on the old behavior. > > On Mon, Oct 14, 2019 at 9:38 PM Joonas Kylmälä <joonas.kylm...@iki.fi> wrote: >> >> Hi, >> >> we investigated today a system server crash: >> <http://paste.debian.net/plain/1106710>. It was bisected to commit >> <https://git.replicant.us/replicant/frameworks_av/commit/?id=19d12edc1aad955ecd2e2b1bc786f1e7acb5fe0c>. >> If anybody has suggestions how to fix this please let us know! >> >> This is causing most likely the audio issues people have reported >> happening on the dev branch and it causes the boot time to be much much >> longer and most likely other issues. It is blocking the 0004 we were >> planning to do this Sunday. >> >> Joonas >> _______________________________________________ >> Replicant mailing list >> Replicant@osuosl.org >> https://lists.osuosl.org/mailman/listinfo/replicant > _______________________________________________ Replicant mailing list Replicant@osuosl.org https://lists.osuosl.org/mailman/listinfo/replicant
