Does anyone know how to solve the telephone problem? The device does not make calls.
The ROM is great!
The ROM is great!
Last edited:
Use cm-14.0-20160923-UNOFFICIAL-odin.zip build.Does anyone know how to solve the telephone problem? The device does not make calls.
The ROM is great!
Thank you very much!Use cm-14.0-20160923-UNOFFICIAL-odin.zip build.
It's not good for daily use . Absent Xposed , working status bar & navbar settings and others. CM13 is more better now. But with time will be good rom.Thank you very much!
I did not even test this version was for the latest.
It is good for daily use?
Regarding sepolicy,@Chippa_a Do you have any hints on building CM14? I figured out thatcommenting out "MALLOC_IMPL := dlmalloc" in BoardConfigCommon.mkcherrypicking 164616 164618 is a necessity. Adding the muppets repo to local_manifests/roomservice.xml for the proprietary files doesn't seem to do much. I am currently trying to build. edit: i am having problems with sepolicy/platform_app.te currently i am using a hacky workaround (like this), how did you solve the problem? another edit: More hacky things for the sepolicies, i removed some neverallow checks, probably I am giving up on building it to test. I don't have access to the computer I am using to build cm starting tomorrow evening, and I am not too eager to build it on my 8gb ram day to day machine. edit: yes some ril stuff failed. Giving up for now, probably starting again when the nightlies start.
Other than that 97589 for fusion3 common and the corresponding commit (104958 for odin, 104960 for yuga) to the device could (/should) fix the issue with autobrightness. You can ommit the change to BoardConfigCommon.mk and have to change a few lines if patch doesn't do it automatically.
I got all the SELinux checks to pass and probably the device will at least boot fine even with enforcing as status. However I got stuck at some RIL stuff. I am not eager to dive deep into it, as this would just be double the work (with very low educational value I expect) as Chippa_a has already fixed those errors.Regarding sepolicy,
You're probably building with 'enforcing' kernel. Try building on 'permissive' kernel first. Delete all the sepolicy from fusion3-common first.
~/android/system/out/target/product/odin/obj/EXECUTABLES/rild_intermediates/rild.o:hardware/ril/rild/rild.c:s_rilEnv: error: undefined reference to 'RIL_onRequestAck'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
I think we should create a organisation on Github, I will ask Chippa to upload his nougat sources. I'm also going to build Nougat from next week so Chippa's sources will be a good way to start. Probably help Chippa with new patches too.I got all the SELinux checks to pass and probably the device will at least boot fine even with enforcing as status. However I got stuck at some RIL stuff. I am not eager to dive deep into it, as this would just be double the work (with very low educational value I expect) as Chippa_a has already fixed those errors.
The error is
Probably some ril wrapper stuff. Maybe the ZL uses the propriatary sony ril, and has to use a wrapper for Nougat, that's expecting a newer RIL version and different symbols.Code:~/android/system/out/target/product/odin/obj/EXECUTABLES/rild_intermediates/rild.o:hardware/ril/rild/rild.c:s_rilEnv: error: undefined reference to 'RIL_onRequestAck' clang++: error: linker command failed with exit code 1 (use -v to see invocation)
I already asked him, but he told what right now he won't upload sources, but if he do this, add me in this org too.I think we should create a organisation on Github, I will ask Chippa to upload his nougat sources. I'm also going to build Nougat from next week so Chippa's sources will be a good way to start. Probably help Chippa with new patches too.
It is without the autobrightness fix (97589), right? Not really good news imo.
now on tap not workingHow cool! Thank you, looking forward to testing this version.
Calls are running again? Some kind of annoying bug?