[ROM][Z3/Z3DUAL][deprecated] LineageOS 14.1 [CLOSED]

nailyk · Nov 27, 2016

Click here to get to the new post where we'll keep updating this rom

What it is

It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)

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 me for messing up your device, I will laugh at you.
*
*/

Who can use it

It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS

How to install

Rolling back to stock

What gapps to flash?

NEW RELEASE

2017-06-13:

Xperia Z3

Download
md5: 2d4ca5f88de0303575f2ab9c249d521f
TWRP 3.1.1 - 2017/06/09

Xperia Z3 Dual

See below
md5: 360fd6f9e0e22eb4ff0de72059c7de24
TWRP 3.1.1 - 2017/06/09 | Mandatory if coming from Z3 builds or new to the rom.

Temporal Z3 Dual rom (fixes SIM problems)

nailyk said:
Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
20170622 / b8a79c826ddf0a786010cc04b3943b2e
twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
Rom is tagged nailyk because I build it but everything on it is @xkeita work!
Many thanks everybody

What's new:

Code:

- Updated Camera profiles
- Reworked Z3 Dual RIL
- Updated Audio HAL flags
- BFQ I/O Scheduler
- Bluetooth aptX support
- Qualcomm Connectivity Engine support
- Imported audio ids from original .291
- ANC Headphones support
- Dual Mic config enabled for voice calls/audio recording
- Ok Google everywhere fixed (untested)
- Tweaked autobrightness  (again)

Release notes:

2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual

Older Releases

Based on Kernel 3.4
Some of these can be found here

Release History

Code:

2017-06-09:
- Tweaked a little bluetooth values (untested)
- Fixed Z3 Dual sim problems
- Latest Google source (7.1.2_r17) 
- June security updates
- Permission fixes for new PowerHAL
- Z3 and Z3 Dual code cleanup
- Forced camera modes to [email protected], [email protected], [email protected], [email protected]
- Fixed all of the device sensors (they're all online and working properly now)
- Latest LineageOS updates
- Smoother UI rendering with CPU

2017-05-17:
- Tweaked general audio output processing 
- Updated vendor audio libraries configs (enables qcom effects)
- Auto brightness/brightness changes
- New thermanager configs based on stock
- Changed deprecated Gello for Jelly
- Some device tree cleanup
- General radio/wifi tcp updates

2017-04-16
- Audio changes, 
- NFC fixes, 
- Brightness changes, 
- Verbosity increased for logs after night reboot + PERISTENT_TRACER
- No more vol- buton at boot time
- A lot more

2017-04-05:
- Enforcing selinux

2017-04-01:
- Audio fixes
- Encryption fix
- A lot more that I can't remember right now

2017-03-22:
- Full rework based on stock 3.4 kernel

Based on Kernel 3.10 by @nailyk

2017-01-23:

2017-01-15:

2017-01-01:

2016-12-02:

P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.

Sources
Manifest file.
Everything else is Lineage.
Contribute gerrit.

XDA:DevDB Information
LOS-14.1, ROM for the Sony Xperia Z3

Contributors
nailyk, xkeita
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS

Version Information
Status: Beta
Beta Release Date: 2017-06-09

Created 2016-11-27
Last Updated 2017-07-01

nailyk · Nov 27, 2016

Thank you!

Thanks to
@tomascus
@xkeita
@derf elot
@panzerox123
@Robot76
@gr8st
@mcgi5sr2
@rcstar6696
@yecomixer
@TheAvengingTITAN
@@AdrianDC
@@doriandiaconu
@SuperLamic
@DiscMan55
@drakonizer
@aclegg2011
@DevUt
@tomascus
@blackhawk_LA
@erickas
@malacha
@jimRnor
@optimumpro
@steadfasterX
@Myself5

All the members of the ivy team: @Quarx, @Olivier, @cdesai, @Myself5 and the one I miss.

TeamWin
LineageOS
All the dev who made the downstream kernel
All of you for testing rom and supporting me

nailyk · Nov 27, 2016

FAQ

How to post

I want to say thanks --> Thanks you. Gratitude is really important for us. Find some posts from us and hit thanks buttons. It will be most appreciated You can also use @tomascus donate link.
We are here into the dev thread, not user one. For now the rom is under development.
We wont talk here about not related to device problems (where is foo setting, how to flash bar).
Reports will simply be ignored if already answered.
Reports without logs or step to reproduce are useless (read contribute).
Substratum is officially not supported into Lineage.
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to post your unusual and not supported use-cases (like: "I have only ipv6 at home and the RA doesn't work without IPv4")
You are welcome to report any typo, error, etc...
No variant are supported now. Only D6603. You want support for variant? Consider help on porting or a hardware donate.
My device is screwed and I need it for my job interview in 1h --> go to IRC (how to report problem, #3)
I want say how SODP is bad --> Read this and above.

This is not against you but try to keep thread clean as a dev reference. Thanks in advance.

What is not working

BT headset calls --> pending. Detailed post.
~~OTG~~ --> 2017-04-16
~~Wifi auto connect (boot/deepsleep),~~
HW Encryption, --> 2017-04-16
~~Vibrator level~~
~~4k (unfixable without Sony camera app)~~
120 fps (pending)
~~Some volume loudness problem --> not reported~~
Microphone when ok google is installed (do not install gapps will fix! An app which constantly record your microphone is a malware!) -->Pending,
~~Slow charging~~,
Phone reboot at 3AM while plugged-in, --> Workaround disable "auto time" into settings.
~~NFC~~, --> topic
~~Wifi access point~~,
~~Adaptive brightness not good.~~ --> Fixed by @xkeita

How to report problems
To report problems there are multiples ways, depend on each person. The How to contribute section provide information on the way to do and should be applicable to everyone. The How to get logs section is the final touch on how to report problems.
Thanks wanting reporting, as, for an early development rom, reports are a necessary step to move forward

Some examples:

@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)

How to get logs
Here you have some info about how collecting log. It is always better to include reference to the Installed version.

How to contribute

Installed version
When reporting problems, specially for work in progress, it is good to provide the build version:
- 'uname -a' will give you the kernel version,
- 'getprop ro.cm.display.version' will give you the rom build version.

What is LineageOS
LineageOS is re-brand of CyanogenMOD. At the end of 2016 some bad things appends. Lineage is the same rom that CyanogenMOD so you can still dirty flash, etc... However as all *cyanogenmod.org services are down, OTA update will not work until you flash lineage one time.

malacha · Nov 27, 2016

Thanks for posting this rom. Thank you for your awesome developing.

jimmy123322 · Nov 27, 2016

Great work man!!! I hope you will continue you work on CyanogenMod for Xperia Z3!!! Thanks

zEminho · Nov 28, 2016

great work and z3 compact?

drakonizer · Nov 28, 2016

What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!

nailyk · Nov 28, 2016

drakonizer said:
What I don't understand is you seem to be having a whole bunch of issues with CM, whereas Rhine devices build perfectly well and all features work on them.
Have you tried building AOSP using Sony Xperia dev sources?
Back in the cm13.0 days, all I used to do to build cm13.0 was use all AOSP device trees and HALs and just make a cm.mk and include vendor/cm/common_phone.mk and everything used to work perfectly fine. Have you tried that?
Anyway, I love the way you develop and your determination. I hope to see you around here often!

Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now

The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.

We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?

Edit:

mcgi5sr2 said:
We are still getting echo on the line and a static in call volume issue on the d5803 with latest sources. rancidfrog has provided logs
https://github.com/sonyxperiadev/device-sony-aries/issues/49#issuecomment-263256754
is the issue isolated to the Aries or do Leo users have this issue as well? Similar question to Honami board devices?

Can you report me as I can answer please?

drakonizer · Nov 28, 2016

nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.

We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?

Edit:

Can you report me as I can answer please?

As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.

Shadow of Destiny · Nov 28, 2016

Hello, I dont get it, where is the download?

I want it sooo badly, but I am to dumb to find the download

mattia.bf · Nov 28, 2016

Shadow of Destiny said:
Hello, I dont get it, where is the download?

I want it sooo badly, but I am to dumb to find the download

As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.

Shadow of Destiny · Nov 28, 2016

mattia.bf said:
As you can see there are no releases in the opening post. I guess that if you really want to help testing you have to ask nialyk for a flashable version. Be aware though that, as stated by the developer, the ROM has still many bugs that harm usability.

Well, thanks then.

nailyk · Nov 28, 2016

Shadow of Destiny said:
Hello, I dont get it, where is the download?

I want it sooo badly, but I am to dumb to find the download

Link is not yet added because I'm dealing with weird GPU issues and I'm waiting for a feedback about a fix before adding it. It should be ok in some hours.

drakonizer said:
As far as I know, which is from my honami tests, deep sleep issue was present only in AOSP builds. A quick look at BBS revealed that it was the radio(ProxyServer) that kept the device awake, and using the phone without SIM would let it go into deep sleep.
When I got a chance to build and test cm14.1, there was no such issue with deep sleep.
In order to figure out whether we have the same issue, could you (or someone else in this thread) use BBS and tell me what the app says?
As for hardware issues: since you're using Sony HALs and device trees, I don't understand why you're having said issues.
AOSP doesnt need any new knowledge, in fact, it should be easier to build and test. If you can clear some space, I suggest you try it. It could rule out any issues with the device trees or Sony HALs, and then you can focus on finding the issue with CM.

IDK what BBS is but the /sys/kernel/debug/wake_lock table is really instructive. From the early experiments we have two issues: like you ril is one of them, and usb is the second one. If your reboot the device in airplane mode without usb attached wake_locks are a bit better.
Yes building AOSP is a good idea but @accleg2011 never get it working so I really doubt I can. Device was really fine on CAF display, game were really smooth, menu too. With SODP display menu are ok now but game are laggy and I don't know how to check if they are software or accelerated rendered. I tried to mimic hammerhead config.mk (it is the same device than z3 except for camera) but it doesn't provide results. I'm almost sure it is another PEBKAC with a missing flag.
I have a bunch of log to analyse and will post my results a bit later. Thanks for your advice, maybe I simply should buy another ssd.

If you have some time to waste, can you try frozen bubble on your device with SODP display, please? When balls pop, it is the most GPU intensive rendering. Is it laggy for you too? (from what I see ~5FPS)

mcgi5sr2 · Nov 28, 2016

nailyk said:
Thanks a lot but your are in a position to know that all the dev had been done by others and I am only porting for now
The biggest source of issue building CM was the codename change. Into sonyxperiadev and all other close to OEM codename is 'leo'. Historically cm rename the device to 'z3' because they already have leo (HTC hd2, IIRC). Here start the pain: as you build too you know a *bunch* of files are codename dependent. Also I wonder if a codename check isn't present into blobs.
I haven't tried to build aosp for now as I didn't have enough free space and wont learn another toolchain. But I test carbon rom which is really efficient.
I tried what you said and give me the best result. Now my branch are ~even with sonyxperiadev. The problem is those version can't be pushed to official CM repo.

We are now experiencing problems on hardware accelerated display, like FPS drop, but I'm not able to fix this. So next step is deep sleep. Are you experiencing this too? Can I ask you some points about this please? Like enabling debugfs, collecting logs after tests etc...?

Edit:

Can you report me as I can answer please?

Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees

nailyk · Nov 28, 2016

mcgi5sr2 said:
Hi I posted this in a different thread and am confused as to how it came up in your CM14.1 thread. I build using all the sonyxperiadev device trees

Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.

mcgi5sr2 · Nov 28, 2016

nailyk said:
Pardon my clumsy. I quote you here because thinking that cm can provide useful results for your question as we are using the same devices trees and blobs. Won't do it again.

Hey no problems, I'm actually battling just to get my latest CM build to install properly

nailyk · Nov 28, 2016

mcgi5sr2 said:
Hey no problems, I'm actually battling just to get my latest CM build to install properly

Do you take a look at Myself5 repos ? You can ask him a CarbonRom test but his repo where very helpful for leo. Also, maybe you can reuse mine and we can concentrate our efforts. I try to be as close as possible to SonyCM ones.
I will update the OP with the build instructions when XDA will work.

nailyk · Nov 28, 2016

2016-11-28 release

Rom link added.
I'm currently uploading screenshots.
A bunch of peripherals are broken. Since I test this PR bluetooth is broken.
Hardware accelerated part are missing or broken.
Camera is partially working, switching to video mode crash camera app.
Deep sleep still not working.
Gps seems to be broken too.

Don't forget we are into a dev thread please, so post comments with logs, faulty line or patches. Thanks.

This rom is not intended to be used as a daily driver and is unstable!

abbas9.4 · Nov 28, 2016

cm14.1 wowww :good:

nailyk · Nov 29, 2016

After a total mess-up with bluetooth, a full rebuild make it ~work again (still some crash).
And 3D apps seems to be working too.
Can you confirm/infirm difference please?

[ROM][Z3/Z3DUAL][deprecated] LineageOS 14.1 [CLOSED]

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Retired Forum Moderator

Senior Member

Retired Forum Moderator

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Attachments

Similar threads

Top Liked Posts