[ROM][OFFICIAL][5.1.x] CyanogenMod 12.1 Nightlies for the Xperia Z3

[nailyk]

2016-12-23 release

Here it is.
md5: https://www.androidfilehost.com/?fid=457095661767124819
sha1: 8befa4036f16803b475362f0dbf0956906a1714f

Thanks to Tomascus this release is patched against dirty cow.
All the functions are tested and working (Im using it since yesterday), including gps.

Now building with jenkins, you can follow each changes here.
@frabe8378910 sorry I mix all the thread :s

 

[akincakiner17]

Tap to wake works for me. Not sure if it was working in the build I posted this morning, but Ill post a new one in a few minutes that has double tap to wake working just fine. It probably didnt work due to the selinux context changes done earlier this month and my aforementioned "fix" was more of a workaround. But Ive changed the necessary SELinux policies so tap to wake works fine and language settings no longer crash.

---------- Post added at 08:26 PM ---------- Previous post was at 08:08 PM ----------

New build available for download here.

the file isn t avaible anymore. do you have a link where i can download it?

 

[frabe8378910]

Here it is.
md5: https://www.androidfilehost.com/?fid=457095661767124819
sha1: 8befa4036f16803b475362f0dbf0956906a1714f

Thanks to Tomascus this release is patched against dirty cow.
All the functions are tested and working (Im using it since yesterday), including gps.

Now building with jenkins, you can follow each changes here.
@frabe8378910 sorry I mix all the thread :s

THANK YOU a lot for your work!
I just installed that new baby and all tested things (wifi, bt, gps, rotation, spotify, video play, camera) works well, except radio. Using Telekom Germany I don't get any service. Opening radio it shows. "Kein Dienst, Telekom.de" (kein Dienst => no service). Going to search for providers, it finds a lot of them and choosing select "best provider" logs into network Telekom, but still no service.
Tested:
1) Flashed with wiped cache
2) Reflash => no improvement
3) wiped system, reflash => no improvement
I haven't done wipe data (factory wipe) as I don't expect it to change things in this case and Z3 is my daily driver ....
4) will now test to reflashed cm-nigthly-20161016

 

[nailyk]

THANK YOU a lot for your work!
I just installed that new baby and all tested things (wifi, bt, gps, rotation, spotify, video play, camera) works well, except radio. Using Telekom Germany I don't get any service. Opening radio it shows. "Kein Dienst, Telekom.de" (kein Dienst => no service). Going to search for providers, it finds a lot of them and choosing select "best provider" logs into network Telekom, but still no service.
Tested:
1) Flashed with wiped cache
2) Reflash => no improvement
3) wiped system, reflash => no improvement
I haven't done wipe data (factory wipe) as I don't expect it to change things in this case and Z3 is my daily driver ....
4) will now test to reflashed cm-nigthly-20161016

As usual, I install and use roms at least one day before publishing them. I used it since. You can see the LTE connectivity and some phone calls. My device is f2fs encrypted too.
Was you prompted for your sim pin? Did you collect some info from *#*#4636#*#* menu or some logs?
Yes it is intended to be used as dirty flashing. However this build doesn't integrate the N modem blobs.
If you are experiencing issue to revert into your old version (or anything else) fell free to join #freexpria on freenode.

Edit: wrong N modem blobs where included too. The only difference between earliest version I post here is only kernel and shouldn't affect ril :s

 

[frabe8378910]

As usual, I install and use roms at least one day before publishing them. I used it since. You can see the LTE connectivity and some phone calls. My device is f2fs encrypted too.
Was you prompted for your sim pin? Did you collect some info from *#*#4636#*#* menu or some logs?
Yes it is intended to be used as dirty flashing. However this build doesn't integrate the N modem blobs.
If you are experiencing issue to revert into your old version (or anything else) fell free to join #freexpria on freenode.

Edit: wrong N modem blobs where included too. The only difference between earliest version I post here is only kernel and shouldn't affect ril :s

Don't get me wrong, I'm not complaining about quality of your work and I know that your stuff is well tested. Keeping that older, but stable and functional perfect CM alive on the z3 is outstanding in my eyes! :good:

Yes, SIM pin was requested and correctly entered.
From my former post:
4) dirty flashed cm-nigthly-20161016 on your version let radio work again. So there must be something different.

So next, I'd flash your version again and do the following steps for debugging:
1) *#*#4636#*#*
2) Any logs you want, but please let me know which and roughly how to get them.
3) Anything else?

 

[nailyk]

Don't get me wrong, I'm not complaining about quality of your work and I know that your stuff is well tested. Keeping that older, but stable and functional perfect CM alive on the z3 is outstanding in my eyes! :good:

Yes, SIM pin was requested and correctly entered.
From my former post:
4) dirty flashed cm-nigthly-20161016 on your version let radio work again. So there must be something different.

So next, I'd flash your version again and do the following steps for debugging:
1) *#*#4636#*#*
2) Any logs you want, but please let me know which and roughly how to get them.
3) Anything else?

Sure I don't took it like that
I will triple check all the changes I made between october release and december release in case I found something useful before.
@frabe8378910 can you confirm the known working version is one of my build please?

 

[frabe8378910]

Sure I don't took it like that
I will triple check all the changes I made between october release and december release in case I found something useful before.
@frabe8378910 can you confirm the known working version is one of my build please?

The version I used before yours (cm-12.1-20161223-nailyk-z3.zip) was "CM 12.1-20161016-NIGHTLY-Z3". This version is now working again, with functional radio.
Sorry, I did not use any CM12.1 ROM other then the CM nightlies before "cm-12.1-20161223-nailyk-z3.zip". So I can only confirm the CM nightlies for radio.

 

[blackhawk_LA]

Are there any changes in the latest builds related to the screen flickering issue? Or will it be to much work considering that stable Nougat will eventually come? Thank you and sorry forc always asking about the same issue! [emoji28]

Sent from my D6603 using Tapatalk

 

[nailyk]

Are there any changes in the latest builds related to the screen flickering issue? Or will it be to much work considering that stable Nougat will eventually come? Thank you and sorry forc always asking about the same issue! [emoji28]

No changes related to this. However this rom shouldn't have screen flickering issue
I want not spend to much time as this rom will became deprecated soon but if you plan to use it as a daily driver we can check how to fix. (Except if someone else using it as a daily driver experience the same issue obviously )
In case, for debugging purpose I need the rom installed, a full dmesg when screen flickering had append, and I really like if you can provide me a video of the flickering please.

 

[blackhawk_LA]

No changes related to this. However this rom shouldn't have screen flickering issue
I want not spend to much time as this rom will became deprecated soon but if you plan to use it as a daily driver we can check how to fix. (Except if someone else using it as a daily driver experience the same issue obviously )
In case, for debugging purpose I need the rom installed, a full dmesg when screen flickering had append, and I really like if you can provide me a video of the flickering please.

Thank you very much I'll see if I can do it tonight.
Oh, and happy new year for everyone!

Sent from my D6603 using Tapatalk

 

[blackhawk_LA]

Here are the logs. I've also made a video, it has not the best wuality but more or less I think you can see the flickering. Sorry for my really bad "stabilization"!
optimumpo tried to build a kernel with your fix for 3.10, but it didn't work. You can see it here https://forum.xda-developers.com/showpost.php?p=70093853&postcount=75
I am thankful for your efforts, but don't take too much time: It seems difficult and although I want to use a CM rom and Lollipop ones are the closest to the stability I need (only bug is that screen flickering) there are not many users in the same situation. And I believe that we will have a perfectly stable Nougat rom sooner or later.
https://drive.google.com/open?id=0B1r3IiDMSm40RHZHYXdfdndqbzQ

 

[nailyk]

Here are the logs. I've also made a video, it has not the best wuality but more or less I think you can see the flickering. Sorry for my really bad "stabilization"!
optimumpo tried to build a kernel with your fix for 3.10, but it didn't work. You can see it here https://forum.xda-developers.com/showpost.php?p=70093853&postcount=75
I am thankful for your efforts, but don't take too much time: It seems difficult and although I want to use a CM rom and Lollipop ones are the closest to the stability I need (only bug is that screen flickering) there are not many users in the same situation. And I believe that we will have a perfectly stable Nougat rom sooner or later.
https://drive.google.com/open?id=0B1r3IiDMSm40RHZHYXdfdndqbzQ

Thanks for reuploading the video.
Sadly xda attachement are broken right now:

cat logs.zip
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

I didn't see flickering on your video but guess what it is now.
Does it happen only when the backlight is close to dark or even with full light flickering is present?

The flickering solved a few weeks ago was this one (panel was initiated into command mode and used into video mode). Your look like a backlight PWM issue.

Edit: @blackhawk_LA does, some custom roms, have not this issue? If yes can you point me which one please.

 

[blackhawk_LA]

Thanks for reuploading the video.
Sadly xda attachement are broken right now:

cat logs.zip

301 Moved Permanently

301 Moved Permanently
nginx

I didn't see flickering on your video but guess what it is now.
Does it happen only when the backlight is close to dark or even with full light flickering is present?

The flickering solved a few weeks ago was this one (panel was initiated into command mode and used into video mode). Your look like a backlight PWM issue.

Edit: @blackhawk_LA does, some custom roms, have not this issue? If yes can you point me which one please.

I can try to make a better video. It only happens when it is at low backlight; I tried to show it on the video when rising brightness. And it happens on every non stock rom, but your latest CM14 didn't have it. I could try it again to provide some logs if you want.

Here are the logs from previous post, in case attachment isn't working https://drive.google.com/file/d/0B1r3IiDMSm40anBHUUg2MmZEcmc/view?usp=drivesdk

Sent from my D6603 using Tapatalk

 

[nailyk]

I can try to make a better video. It only happens when it is at low backlight; I tried to show it on the video when rising brightness. And it happens on every non stock rom, but your latest CM14 didn't have it. I could try it again to provide some logs if you want.

Here are the logs from previous post, in case attachment isn't working https://drive.google.com/file/d/0B1r3IiDMSm40anBHUUg2MmZEcmc/view?usp=drivesdk

Sent from my D6603 using Tapatalk

CM12.1 use a 16bit value for setting the brigthness level (and for all the screen values), the new kernel (cm-14.1) use 8bit values. Two case:
1. there is a bug with your panel and values are not read correctly
2. value is too low and setting it to an higher value will solve.

Will look at this and the modem problem at the same time.

 

[blackhawk_LA]

CM12.1 use a 16bit value for setting the brigthness level (and for all the screen values), the new kernel (cm-14.1) use 8bit values. Two case:
1. there is a bug with your panel and values are not read correctly
2. value is too low and setting it to an higher value will solve.

Will look at this and the modem problem at the same time.

Actually, I feel (can't compare directly) that in stock Sony roms brightness can be set to a lower value than in non stock roms. But surely is not higher. So I wouldn't think that the problem is setting the brightness too dark.

Sent from my D6603 using Tapatalk

 

[nailyk]

2017-01-14 release

download / md5 : 39411a9043a23b8810809bf6934bced4
This release is official one (no changes) except kernel upgrade.
Official backlight settings, official modem blobs, etc...
@tomascus patch kernel for january android security updates (included qcom bootloader vulnerabilities)

cc: @blackhawk_LA @frabe8378910

 

[frabe8378910]

download / md5 : 39411a9043a23b8810809bf6934bced4
This release is official one (no changes) except kernel upgrade.
Official backlight settings, official modem blobs, etc...
@tomascus patch kernel for january android security updates (included qcom bootloader vulnerabilities)

cc: @blackhawk_LA @frabe8378910

@nailyk:
I had a day off, so I flashed your latest ROM. I did a dirty flash, only cache was wiped.
Looks very good: I checked all basics like wifi, SIM (german Telekom), camera, sdcard (format as ext4), ... and everything worked!
As my Z3 is encrypted, this works too.

So thank you a lot your work to keep the Z3 a perfect daily driver!

 

[nailyk]

@nailyk:
I had a day off, so I flashed your latest ROM. I did a dirty flash, only cache was wiped.
Looks very good: I checked all basics like wifi, SIM (german Telekom), camera, sdcard (format as ext4), ... and everything worked!
As my Z3 is encrypted, this works too.

So thank you a lot your work to keep the Z3 a perfect daily driver!

Glad your SIM problem are fixed now

For security updates thanks @tomascus (who still doesn't have donate button :s)
However only kernel is security updated. Android patches are not merged anymore. Maybe someone could take care of this?

 

[lynxeon]

So if in this ROM it works the camera, why in 14.1 it doesn't work it?

 

[nailyk]

So if in this ROM it works the camera, why in 14.1 it doesn't work it?

Short: no the same kernel, too much DRM, no way to shim.
Long version (Example isn't camera but is applicable anyway as our blobs are DRM protected and there is no way to reuse 4.2 blobs with 3.10 kernel)

Please my frend z3 dual 6633 patch

I have not dual device :s
Mostly you can try to replace all the /system/vendor/firmware/modem.* file from a working CM-12.1.
Keep me informed