[Xperia Z3 Original Android Development] nailyk:
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 [MENTION=4675360]tomascus[/MENTION] 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 [MENTION=4550727]xkeita[/MENTION]

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:

Is useless on a dev thread and you probably won't get an answer.

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)

[MENTION=5545101]steadfasterX[/MENTION] 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

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.