• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Status
Not open for further replies.
Search This thread

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
lineage_logo_strip_onteal_500x120.png

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

%= Only needed at first flash
  1. % Update ROM to .291 with emma (or Flashtools)
  2. % When install is done go into fastboot mode (plug usb + vol down key = blue led)
  3. % Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
  4. Shutdown the device
  5. Unplug the usb cable
  6. Maintain volume down & power until you see twrp splash screen
  7. % Wipe system, cache and data
  8. Install rom zip (+ % gapps if you need it)
  9. Reboot


Rolling back to stock
  • Flash stock rom with emma or flashtool
    If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install

What gapps to flash?
Use f-droid :p
You can flash any gapps you want, our partition is 2GB and rom is 700MB:
Code:
z3:/ # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
Just take 'arm' and not 'arm64'
Gapps need to be flashed at first rom flash!


NEW RELEASE
2017-06-13:

Xperia Z3
Xperia Z3 Dual

Temporal Z3 Dual rom (fixes SIM problems)
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:
  • Download / 2
  • md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
  • sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
  • Use of the reworked device trees
  • Include some experimental kernel pull requests

2017-01-01:
  • Download
  • md5: 6c5abcbeda01c75344cd4296bb2358d1
  • sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
  • Switch to LineageOS
  • Bluetooth deepsleep fixed

2016-12-02:
  • Download
  • md5: 496de65608fd4236f5d451a4179e1ce8
  • sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
  • Bluetooth improvements

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
 

Attachments

  • Screenshot_20161128-143733.png
    Screenshot_20161128-143733.png
    142.5 KB · Views: 31,641
  • Screenshot_20161128-143854.png
    Screenshot_20161128-143854.png
    176.3 KB · Views: 30,726
  • Screenshot_20161128-213631.png
    Screenshot_20161128-213631.png
    90.7 KB · Views: 28,879
  • nfc.png
    nfc.png
    232.6 KB · Views: 25,417
  • battery.png
    battery.png
    94.4 KB · Views: 18,288
  • version.png
    version.png
    111.3 KB · Views: 18,339
  • FM.png
    FM.png
    55.6 KB · Views: 17,925
  • a2dp.png
    a2dp.png
    139.8 KB · Views: 17,685
  • front_cam.jpg
    front_cam.jpg
    132.2 KB · Views: 17,344
  • back_camera.jpg
    back_camera.jpg
    244.6 KB · Views: 17,985
  • hotspot.png
    hotspot.png
    123.6 KB · Views: 17,753
  • newpipe.jpg
    newpipe.jpg
    68.5 KB · Views: 16,461
  • vlc.jpg
    vlc.jpg
    92.8 KB · Views: 14,786
  • gps.png
    gps.png
    169.3 KB · Views: 13,986
Last edited:

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
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:
I cannot record videos with open camera.
Is useless on a dev thread and you probably won't get an answer.

Just wanted to report that this ROM doesn't support my 128gb sandisk SD card..and gives a message, unsupported SD card and asks to format.. this is the only bug which prevents me from using this ROM.. however the same card works perfectly fine on all other ROMs like 7.1 CM or AICP ROM and also all lollipop ROMs and stock ROM.
Is better as there is explanation, context and cross rom tests. With log this report used to be perfect.

This guide is really detailed and explained everything about bug reports. (deserve all bug-report cases, not specially this thread or xda)


@steadfasterX write a good guide about IRC, here you can get quick support (like when your device is totally broken, etc...)
You talked about using IRC to get support. What is this and how can I use that?
  • Meaning of IRC => Internet Relay Chat. A very good IRC client is this one here: hexchat <-- download it and read the quick intro to get started: Quick-Start
    --> when asked if you want to join a channel type in "#LineageOS" and after connected you will be in.
  • If you do not want to install anything you can simply use the webchat instead directly over here: Webchat
  • Howto communicate? IRC means many people talking the same time and there are some goods and bads to know about using IRC.
    So please read this mini and very quick overview (especially the good manners there): Good manners in IRC (matches for all OS not for fedora only)

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
  • I have c knowledge:
All the sources to build this rom are public and are provided into the manifest, in the howto build section. It means all the repository are from LineageOS github, except those mentioned into this manifest. Depending on where you find the bug/improvement there is different way to contribute: gerrit, github PR, etc... Contact me to test with you patch as everyone can try and give feedbacks then join IRC to discuss the best way to merge.
  • Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
  • Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.


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.
 
Last edited:

drakonizer

Retired Forum Moderator
May 10, 2013
1,126
2,340
Death Star
OnePlus 9 Pro
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

Senior Member
Oct 3, 2015
1,503
2,955
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:
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?
 
Last edited:

drakonizer

Retired Forum Moderator
May 10, 2013
1,126
2,340
Death Star
OnePlus 9 Pro
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.
 
  • Like
Reactions: nailyk

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
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.

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)
 
  • Like
Reactions: goosebickel

mcgi5sr2

Senior Member
Oct 15, 2012
1,058
1,810
Sheffield
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
 
  • Like
Reactions: nailyk

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
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.
 
  • Like
Reactions: goosebickel

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
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!
 

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
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?
 

Attachments

  • Screenshot_20161129-014359.png
    Screenshot_20161129-014359.png
    95.1 KB · Views: 439
  • Screenshot_20161129-015101.jpg
    Screenshot_20161129-015101.jpg
    115.6 KB · Views: 437
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 84
    lineage_logo_strip_onteal_500x120.png

    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

    %= Only needed at first flash
    1. % Update ROM to .291 with emma (or Flashtools)
    2. % When install is done go into fastboot mode (plug usb + vol down key = blue led)
    3. % Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
    4. Shutdown the device
    5. Unplug the usb cable
    6. Maintain volume down & power until you see twrp splash screen
    7. % Wipe system, cache and data
    8. Install rom zip (+ % gapps if you need it)
    9. Reboot


    Rolling back to stock
    • Flash stock rom with emma or flashtool
      If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install

    What gapps to flash?
    Use f-droid :p
    You can flash any gapps you want, our partition is 2GB and rom is 700MB:
    Code:
    z3:/ # df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
    Just take 'arm' and not 'arm64'
    Gapps need to be flashed at first rom flash!


    NEW RELEASE
    2017-06-13:

    Xperia Z3
    Xperia Z3 Dual

    Temporal Z3 Dual rom (fixes SIM problems)
    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:
    • Download / 2
    • md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
    • sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
    • Use of the reworked device trees
    • Include some experimental kernel pull requests

    2017-01-01:
    • Download
    • md5: 6c5abcbeda01c75344cd4296bb2358d1
    • sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
    • Switch to LineageOS
    • Bluetooth deepsleep fixed

    2016-12-02:
    • Download
    • md5: 496de65608fd4236f5d451a4179e1ce8
    • sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
    • Bluetooth improvements

    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
    50
    Why no news

    Not been here for a while because we where working on something new: a 3.4 tree (full stock) for our devices.
    And we finally get camera working.
    Now we need time to cleanup, fix useless things like wifi and ril but we will have good cam on Lineage :)

    Thanks all for support and patience.

    P.S.: xda crop picture, original one is 10MB.
    40
    2017-03-05: 3.4 port state

    Some progress on ril side for d6603.
    But still a lot of work to do:
    - thermal is not working need tuning (;)),
    - bluetooth is broken,
    - ril call doesn't really work withouth headset (acdb problem?),
    - wifi ok (untested @5Ghz),
    - lights ok,
    - camera ok (video recording too @ 1080p30 only),
    - deepsleep sometimes broke,
    - f2fs not working
    - and a lot more ;)
    33
    Game Over


    Time for an... Update.

    Maybe some of you already known but I don't have d6603 anymore.
    The first dev phone get a SMC pulled of (my bad) and doesn't work properly anymore.
    Right now all my reflow attempt failed.

    The other device is hardly software bricked because that great bootloader signature doesn't work anymore.
    Note: don't try to write junk into tz partition.
    It looks to be unsolvable because Sony made great things again and prevent normal msm8974 low level disaster recovery working, replaced by their useless own.

    So I doesn't have device anymore, fixing them will take a while and mostly will not work. Game over for me. Hopefully you have a lot of great dev working on this which wont leave you.
    @xkeita was ok to take the next of this thread. He now have full right here.
    @malacha will help him as much as he can but is now maintaining another rom.

    Was a pleasure to make my first android experience here.
    Many thanks to all of you.