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

leesiangcheng · Jul 5, 2012 80 15 0

Sure but not adb problem. Is window 10 always crash. I think I must reformat the whole window.thanks again for supporting our z3.

nailyk · Nov 12, 2016 at 12:33 PM

cm-12.1 dropped

Official cm-12.1 dropped.
I will keep a copy of the last two.

blackhawk_LA · Nov 12, 2016 at 11:21 PM

And much older HTC One M7 already has CM13... Too bad, Sony!

Sent from my D6603 using Tapatalk

DaniellaPB · Nov 13, 2016

Ended with Error 7 during install.

Hi all,

Having a problem installing CM on my Z3 D6603.

When installing CM a message comes up: "This package is for devices: D6602, D6603, D6643, D6653, z3; this device is sirius. Updater process ended with ERROR: 7."

I'm using TWRP and I have followed all the steps like Wipe > Slide to Factory Reset.

Any help is greatly appreciated. Thanks x

----------------------------------------------------------
Not to worry, I found the fix by googling TWRP error 7 and edited the updater-script file.

Thanks for all the great work with CM xx

bigo72 · Nov 13, 2016 at 8:26 AM

DaniellaPB said:
"This package is for devices: D6602, D6603, D6643, D6653, z3; this device is sirius. Updater process ended with ERROR: 7."

Are you sure about your phone model? I'm sorry, I know it looks like a stupid question, but we had problems in the past when 6603 was identified as Leo by CyanogenMod. Well, Leo was an "alias" of Z3, so it was just a matter of understanding how to name the same device .... but Sirius is a Z2's alias! Dunno, too strange.

DaniellaPB · Nov 13, 2016

bigo72 said:
Are you sure about your phone model? I'm sorry, I know it looks like a stupid question, but we had problems in the past when 6603 was identified as Leo by CyanogenMod. Well, Leo was an "alias" of Z3, so it was just a matter of understanding how to name the same device .... but Sirius is a Z2's alias! Dunno, too strange.

Yeh it's D6603, I even got the original box for the phone out of my cupboard to check as well as looking on the device info in settings. I saw that sirius was a alias of the z2 when I googled the error, that's what made me check but I pretty sure I bought a z3 when I took the phone out on contract.

I've fixed the problem now by editing the updater-script file.

Thanks for replying though x

blackhawk_LA · Nov 13, 2016 at 4:07 PM

@nailyk I've installed your latest ROM and it has the screen flickering issue in low brightness. I haven't replaced my panel so it must be due to some driver. Thanks for your hard work!

nailyk · Nov 13, 2016 at 5:49 PM

blackhawk_LA said:
@nailyk I've installed your latest ROM and it has the screen flickering issue in low brightness. I haven't replaced my panel so it must be due to some driver. Thanks for your hard work!

Is the screen entirely flickering or just the half bottom?
This cm-12.1 is based on 3.4 kernel which shouldn't have the (half) screen flickering issue. But when tuning device configuration I was pretty aggressive and the back-light PWM can be really slow and under eye persistence when set to really low level.
Can you please explain if the screen is flickering or the backlight?
Also can you please try to set to a higher value?
(IIRC the original cm had value between 0 and 15 and mine are between 0 and 30, try to set to maximum, then zero, then the value you would use).

Thanks for feedback. As CyanogenMod stop producing official builds I think to unsubscribe this thread and trash my cm-12.1 vm (no way to get this rom updated now

)...

blackhawk_LA · Nov 13, 2016 at 8:03 PM

nailyk said:
Is the screen entirely flickering or just the half bottom?
This cm-12.1 is based on 3.4 kernel which shouldn't have the (half) screen flickering issue. But when tuning device configuration I was pretty aggressive and the back-light PWM can be really slow and under eye persistence when set to really low level.
Can you please explain if the screen is flickering or the backlight?
Also can you please try to set to a higher value?
(IIRC the original cm had value between 0 and 15 and mine are between 0 and 30, try to set to maximum, then zero, then the value you would use).

Thanks for feedback. As CyanogenMod stop producing official builds I think to unsubscribe this thread and trash my cm-12.1 vm (no way to get this rom updated now )...

OK, sorry if I didn't explain it good, as English is not my primary language. Actually what I tried to describe could be more "backlight flickering". In low brightness, the whole screen flickers, like changing brightness very little and very very quickly. It happens in auto and manual brightness, and only above certain point (maybe at higher values is still there but i don't notice it).

BTW, I probably won't use cm12 as my daily driver, I was just trying it and reporting in case it helps with cm13 development.
Greetings

Sent from my D6603 using Tapatalk

nailyk · Nov 13, 2016 at 8:16 PM

blackhawk_LA said:
OK, sorry if I didn't explain it good, as English is not my primary language. Actually what I tried to describe could be more "backlight flickering". In low brightness, the whole screen flickers, like changing brightness very little and very very quickly. It happens in auto and manual brightness, and only above certain point (maybe at higher values is still there but i don't notice it).

BTW, I probably won't use cm12 as my daily driver, I was just trying it and reporting in case it helps with cm13 development.
Greetings

Sent from my D6603 using Tapatalk

English is hard for me, pardon my clumsiness.
Your are right some CM-12.1 can be present into CM-13.0 but I will only secure update them now and it will not improve new projects projects as they are based on the same kernel.
What you explain happens sometimes on my device too but I'm always able to solve it by changing the brightness value (cm-12.1 is my daily driver, I need a (fast) working camera). Do you notice the same back-light flickering with CM-13.0?

If you can join IRC, have a spare z3 and would help me I have a bunch to do

Thanks a lot for your support.

P.S.: CyanogenMod maintainers answers me they won't enable cm-12.1 builds again.

blackhawk_LA · Nov 13, 2016 at 10:39 PM

nailyk said:
English is hard for me, pardon my clumsiness.
Your are right some CM-12.1 can be present into CM-13.0 but I will only secure update them now and it will not improve new projects projects as they are based on the same kernel.
What you explain happens sometimes on my device too but I'm always able to solve it by changing the brightness value (cm-12.1 is my daily driver, I need a (fast) working camera). Do you notice the same back-light flickering with CM-13.0?

If you can join IRC, have a spare z3 and would help me I have a bunch to do
Thanks a lot for your support.

P.S.: CyanogenMod maintainers answers me they won't enable cm-12.1 builds again.

I turned on my pc to transfer a few things to the phone and to answer you that I can only test a few things cause I have very little time and... boom my hard drive seems to be dead. Now I have even less time lol. What a bad day, man.

I haven't tried Cm13 yet so I can't tell you if the bug is present. But it is on official cm12.1 and Jaguar rom. And it's there after changing brightness as you suggested.

I can try cm13 and tell you but also my download speed is very slow so I'm afraid I won't be the perfect tester xd

Sent from my D6603 using Tapatalk

nailyk · Nov 13, 2016 at 10:52 PM

blackhawk_LA said:
I turned on my pc to transfer a few things to the phone and to answer you that I can only test a few things cause I have very little time and... boom my hard drive seems to be dead. Now I have even less time lol. What a bad day, man.

I haven't tried Cm13 yet so I can't tell you if the bug is present. But it is on official cm12.1 and Jaguar rom. And it's there after changing brightness as you suggested.

I can try cm13 and tell you but also my download speed is very slow so I'm afraid I won't be the perfect tester xd

Sent from my D6603 using Tapatalk

Really interesting to know the issue you are encountering is also present on official. You should have the other panel variant and will not be affected by the 3.10 flickering bug. If you can, post the output of 'dmesg | grep panel'. The interesting line is where the name is present, like "mdss_panel_parse_dt: Panel Name = default video 1".

blackhawk_LA · Nov 13, 2016

nailyk said:
Really interesting to know the issue you are encountering is also present on official. You should have the other panel variant and will not be affected by the 3.10 flickering bug. If you can, post the output of 'dmesg | grep panel'. The interesting line is where the name is present, like "mdss_panel_parse_dt: Panel Name = default video 1".

This is the output 2016-11-14 01:23:09,INFORMATION,mdss_dsi_panel_on: ctrl=ecb15810 ndx=0
Is taken while using existenz 5.6.5 and Elite kernel.

Sent from my D6603 using Tapatalk

DaniellaPB · Nov 13, 2016 3 0 0

Track info via Bluetooth not changing

Hey, loving CM but I've found that track info doesn't update from song to song on my car stereo. It'll show the track info for the first song played and then only display that information despite the song changing. It worked fine when I was using vanilla android before I changed to CM.

It's not a problem for me really but I thought I'd mention it.

Phone model: Z3 D6603
CM build: cm-12.1-20161016
App: Spotify

Thanks,
xx

Draiden · Jan 10, 2009 84 30 0

nailyk said:
New test release. Feedback welcome =)

kernel: https://github.com/nailyk-fr/android_kernel_sony_msm8974/commits/cm-12.1_staging
blobs: https://github.com/nailyk-fr/proprietary_vendor_sony/tree/cm-12.1_work
CM patches: https://review.cyanogenmod.org/#/c/159441/, https://review.cyanogenmod.org/163254, https://review.cyanogenmod.org/157413

Works fine nailyk thanks

Sent from my Xperia Z3 using XDA-Developers mobile app

nailyk · Nov 23, 2016 at 8:24 PM

2016-11-23 (unofficial) release

Download
md5: d01e1d7a0a9ca61be578ef8ef8191b96
sha1: 5478c55bb5b6654f9ce15701d4e12d02a180f67e

blackhawk_LA · Nov 23, 2016 at 10:57 PM

nailyk said:
Download
md5: d01e1d7a0a9ca61be578ef8ef8191b96
sha1: 5478c55bb5b6654f9ce15701d4e12d02a180f67e

Is there any important change? Something we should try and test?

Sent from my D6603 using Tapatalk

nailyk · Nov 24, 2016 at 8:27 AM

blackhawk_LA said:
Is there any important change? Something we should try and test?

Forget to mention it, sorry.
Nothing changed, only periodical rebuild and I have a real doubt if dirtycow patch is included, purpose of this build :s

attachsnow · Nov 26, 2016 at 9:52 AM

Hello, is there Camera Distortion bug fixed?
Or any method can fix it?

zeravince · Nov 29, 2016 2 0 0

my gps is not working , is it a bug?

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

Senior Member

Senior Member

Senior Member

New member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

New member