[ROM][FINAL][7.1.1] CyanogenMod 14.1 for Xperia ZL

Status
Not open for further replies.

NamenIos

Senior Member
Nov 26, 2010
473
243
63
@Chippa_a Do you have any hints on building CM14? I figured out that commenting out "MALLOC_IMPL := dlmalloc" in BoardConfigCommon.mk cherrypicking 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.
 
Last edited:

Daedroza

Inactive Recognized Developer
Jun 16, 2014
562
1,032
0
daedroza.github.io
@Chippa_a Do you have any hints on building CM14? I figured out that commenting out "MALLOC_IMPL := dlmalloc" in BoardConfigCommon.mk cherrypicking 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.
Regarding sepolicy,
You're probably building with 'enforcing' kernel. Try building on 'permissive' kernel first. Delete all the sepolicy from fusion3-common first.
 
  • Like
Reactions: NamenIos

NamenIos

Senior Member
Nov 26, 2010
473
243
63
Regarding sepolicy,
You're probably building with 'enforcing' kernel. Try building on 'permissive' kernel first. Delete all the sepolicy from fusion3-common first.
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
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)
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.
 

Daedroza

Inactive Recognized Developer
Jun 16, 2014
562
1,032
0
daedroza.github.io
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
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)
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.
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.
 

alex-gibson

Senior Member
Mar 14, 2015
144
368
93
Minsk
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 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.
 
  • Like
Reactions: ham5

k0nko87

Senior Member
Nov 12, 2010
87
14
0
Im running new build (20161023) from yesterday, and it looks like everything is working just fine (only autobrightness still not working).

I will be using this ROM like my daily driver and we will see.

I will report problem if i found any.

For now, thank you very much for this great ROM and for the contribution for our lovely Xperia ZL

Cheers, Tomas
 

fleflis

Member
Mar 14, 2013
17
2
0
Jundiaí
Nice rom! Working very well!
- Bug: every time I reboot, the arrows on navbar for text reappears , even if the option is disabled ( under Settings -> buttons )
- icons on navbar is outdated , need to get the new ones from Nougat
- Now on tap does not work, holding down home button opens recent
- Google now doesn't work on Pixel Launcher
 

ihsan123

Senior Member
Jan 25, 2012
127
44
0
wow,long time not come to this forum,really glad to see some1 still working on rom for this device, i see ur announcement about the upcoming 7.1 upgrade,will keep an eye on the updates,keep up the good work
 
Status
Not open for further replies.