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

Intro:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Disclaimer:
Code:
#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.
*
*/
About CyanogenMod:
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Screenshots:
Source Code:
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Notable Features:
CyanogenMod 12 also includes some quite interesting features for those who want full control of Android.
Theme Engine
UI Mods
Performance Options
OTA Updates via Settings
Built-in root access via Development Options
Download Links:
Nightly Builds: http://download.cyanogenmod.org/?device=z3
PA GAPPS Package: Click here!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Please note that I am not an official maintainer for the Z3. If there are any issues, mods or whoever responsible remove this thread.
XDA:DevDB Information
Official CyanogenMod 12.1 Nightlies Z3, ROM for the Sony Xperia Z3
Contributors
squabbi
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-01-22
Last Updated 2015-04-27

---

What's Working?
If you would like a more 'working' build, thanks to @Untouchab1e Right here. This includes fixes for numerous things!
Here is a list of items that are confirmed working and/or not working:
Working:
Screen
Camera
Microphone
RIL (Radio Interface Layer)
Speakers
NFC
Bluetooth
Video playback (Stock apps + Youtube playback)
Not Working:
Double-tap to wake (Try using another kernel)
Unconfirmed:
N/A
Other Issues:
Brightness fix is Here! Thanks @jdenman03
Camera video recording volume is very low.
4 Second delay on calls

---

Home button doesn't work me. Flashed PA Mini App Pack.

---

xnerdx said:
Home button doesn't work me. Flashed PA Mini App Pack.
Click to expand...
Click to collapse
This seems to be a moderate issue as well, have you tried wiping the system partition, completing a factory reset and then flashing the nightly and gapps.

---

I can't seem to figure out as to why this refuses to work for me.
After going to updater-script and changing z3 to leo (I use the CWM recovery), it begins the installation and then just gets stuck on it.
Same thing applies if I try to use anything beyond cm-12-20150120-UNOFFICIAL-z3 by David_Vaz while that particular version works fine; a few seconds and the installation completes.
Any ideas?

---

raptorjesus1337 said:
I can't seem to figure out as to why this refuses to work for me.
After going to updater-script and changing z3 to leo (I use the CWM recovery), it begins the installation and then just gets stuck on it.
Same thing applies if I try to use anything beyond cm-12-20150120-UNOFFICIAL-z3 by David_Vaz while that particular version works fine; a few seconds and the installation completes.
Any ideas?
Click to expand...
Click to collapse
Strange... It could be the recovery. Change back the recovery script to its default (z3) and give it a go in TWRP which worked for me. Both David_Vas and the official nighties of CM12.

---

I've been out of the 'loop' for a while and have no idea how to revert to stock recovery. Any tips?

---

raptorjesus1337 said:
I've been out of the 'loop' for a while and have no idea how to revert to stock recovery. Any tips?
Click to expand...
Click to collapse
You mean the stock sony recovery? Or just any recovery?

---

Oddily enough, I'm suffering with the same problem... Mine show "This package is for device: D6602, D6603, D6633, D6643, z3; this device is leo" .
It happens both with CWM and TWRP.
I'm clueless about what to do...
BTW, my device is D6633.

---

Warm welcome to the CM team. So happy to see you here.
I have a bug to report, if I may.
Methodology:
Make a call (I'm currently using the Google dialler, featured in PA Gapps).
During the call, while the screen is off, I attempt to turn the screen on, to end the call.
The screen won't turn on, however many times I click the power button, or try to communicate with the phone's gyroscope.
I end up having to hard reset the phone, to get it to reboot, otherwise the call cannot be ended, with the screen off.
Many thanks for your graciousness and hard work. I look forward to all further updates.
Regards.

---

radjan said:
Oddily enough, I'm suffering with the same problem... Mine show "This package is for device: D6602, D6603, D6633, D6643, z3; this device is leo" .
It happens both with CWM and TWRP.
I'm clueless about what to do...
BTW, my device is D6633.
Click to expand...
Click to collapse
All you need to do is edit the updater-script and change the device model it searches for. Instead of 'z3' replace it with 'leo'.
edit: It's something like this: But you should be seeing 'z3' instead of 'ST15i' change that to 'leo'. and you should be on your way!
now what is the updater-script and update-binary present in the META-INF>com>google>android in any flashable zip package?
1. updater-script - it is just a text file which contains all the commands which tells the clockworkmod what to do with the given
zip file. the updater-script is written in the edify scripting language.
2. update-binary - it is a binary which is requiered by the clockworkmod to translate the human readable format of the updater-
script to machine readable format for execution of the updater-script in our device.
exploring the updater-script:
now let's start exploring the updater-script !
1. open the updater script with notepad++ (strongly recommended)
2. now i will try and explain commands generally used in the updater-script,
assert(getprop("ro.product.device") == "ST15i" || getprop("ro.build.product") == "ST15i" ||
getprop("ro.product.device") == "ST15a" || getprop("ro.build.product") == "ST15a" ||
getprop("ro.product.device") == "smultron" || getprop("ro.build.product") == "smultron");
the above bunch of lines checks the device model to confirm that the zip file is flashed on the device
for which it is specifically created for. These bunch of lines are very important because it prevents
flashing of zip file which is not intended for the device hence avoiding any problems due to flashing
the wrong zip. for example the above lines checks for the value of "ro.product.device" and
"ro.build.product"in the build.prop file of the already existing rom in the device, if any of the three
defined values ST15i, ST15a, smultron are found it will continue with the next line of updater-script
otherwise flashing gets aborted with error in getprop.
Click to expand...
Click to collapse

---

Yeah, i found a link right after I posted. Sorry for bothering, and thanks anyway!

---

hospital349 said:
Warm welcome to the CM team. So happy to see you here.
I have a bug to report, if I may.
Methodology:
Make a call (I'm currently using the Google dialler, featured in PA Gapps).
During the call, while the screen is off, I attempt to turn the screen on, to end the call.
The screen won't turn on, however many times I click the power button, or try to communicate with the phone's gyroscope.
I end up having to hard reset the phone, to get it to reboot, otherwise the call cannot be ended, with the screen off.
Many thanks for your graciousness and hard work. I look forward to all further updates.
Regards.
Click to expand...
Click to collapse
Hi! Thanks!
Do you think there is something wrong with the proximity sensor? On mine it works perfectly, although I don't call enough to see if I can replicate it. I had a phone call just then and it went OK. The screen would turn back on.

---

radjan said:
Yeah, i found a link right after I posted. Sorry for bothering, and thanks anyway!
Click to expand...
Click to collapse
Don't sweat it! Enjoy your day with CM12!

---

squabbi said:
Hi! Thanks!
Do you think there is something wrong with the proximity sensor? On mine it works perfectly, although I don't call enough to see if I can replicate it. I had a phone call just then and it went OK. The screen would turn back on.
Click to expand...
Click to collapse
I'm not quite sure. I was using stock, previous to using CM12 and I always had to double tap the power button to activate the screen, during a call.
Does CM12 require a Z3 user to fo the same, or should it be automatic, as the user lowers the phone away from his/her ear?
I'm slightly worried that this is a hardware issue, on my side. That would be just my luck. Rubbish!
Thanks for your help.

---

hospital349 said:
I'm not quite sure. I was using stock, previous to using CM12 and I always had to double tap the power button to activate the screen, during a call.
Does CM12 require a Z3 user to fo the same, or should it be automatic, as the user lowers the phone away from his/her ear?
I'm slightly worried that this is a hardware issue, on my side. That would be just my luck. Rubbish!
Thanks for your help.
Click to expand...
Click to collapse
It could be a hardware issue if it happens on stock as well. Usually it is automatic when the user moves their phone away from their face. All other mobiles should do the same so I'm not sure why its not for you. Is there anything within the dialer settings or system settings that may have been changed?

---

squabbi said:
It could be a hardware issue if it happens on stock as well. Usually it is automatic when the user moves their phone away from their face. All other mobiles should do the same so I'm not sure why its not for you. Is there anything within the dialer settings or system settings that may have been changed?
Click to expand...
Click to collapse
I thought that as well and checked a little while ago. Nothing that I can see. Maybe it is the proximity sensor. Is there a way I can test my devices proximity functionality/calibration, or even recalibrate if necessary?
I really want to troubleshoot it and make sure that it's definitely a hardware issue, rather than a ROM/kernel problem.

---

hospital349 said:
I thought that as well and checked a little while ago. Nothing that I can see. Maybe it is the proximity sensor. Is there a way I can test my devices proximity functionality/calibration, or even recalibrate if necessary?
I really want to troubleshoot it and make sure that it's definitely a hardware issue, rather than a ROM/kernel problem.
Click to expand...
Click to collapse
Oh definately. I'm not too sure on the matter but I remember that on the Sony stock ROMs it had a service menu to test things out. There might be similar apps on the Play Store, but try this one out. I can't remember if it included the proximity check for it but it could test pressure (water tightness).
https://play.google.com/store/apps/details?id=com.cpuid.cpu_z

---

Ok, tried the ROM, it's awesome as I expected. But it has the same problem as David's one: the RIL doesn't seem to work for the dual sim version.
I know it's not a priority for you guys developing it, but could you let us know on the topic if something is done towards making it work for us with the D6633?
Once again, sorry for bothering. Don't want to come here asking for deadlines or anything. It's just that once you taste the lollipop, there's no going back. I'll miss it sorely for now.

---

squabbi said:
Oh definately. I'm not too sure on the matter but I remember that on the Sony stock ROMs it had a service menu to test things out. There might be similar apps on the Play Store, but try this one out. I can't remember if it included the proximity check for it but it could test pressure (water tightness).
https://play.google.com/store/apps/details?id=com.cpuid.cpu_z
Click to expand...
Click to collapse
An impressive app, if you ask me. It does look as if the proximity scales are moving, but that doesn't mean anything if the phone isn't registering my actions. I checked and service mode followed by calibration of proximity sensors, might fix it (according to some forums). I'm away from my PC and will have to revert to stock, to try this out.
So sorry if I at all hijacked the thread, for a while. I honestly thought that the issue may have been caused by a bug, at first.
Thanks for your insight and kindness.
Look forward to future iterations of CM12.
Regards.