yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Original Android Development] :
Yea, I'm downloading the 7.0 source to my build box now. We can actually pull the n blobs from the Sony dev preview ftf if we really wanna be crazy
[Xperia Z3 Original Android Development] nailyk:
i already use some N blobs in this build ;)
[Xperia Z3 Original Android Development] nailyk:
Nfc

I just start some reading about nfc and it will not be fun.

Seems our device (at least my z3) uses PN547 which had bugs....

MM patches , driver, sony kernel.

Some are recent so i will wait and see.

P.S.: in attachment the missing AP screenshot (pings between phone ok).
[Xperia Z3 Original Android Development] nailyk:
[MENTION=4311238]SuperLamic[/MENTION] just open a thread dedicated to camera.

Pictures about security updates i forgot. Left to right, cm-12.1, stock .575, cm-13.0.
[Xperia Z3 Original Android Development] Allexandre09:
Where is the link?:confuso::confuso:
[Xperia Z3 Original Android Development] nailyk:
Links for downloading the rom are into the first post, under Releases section.
[Xperia Z3 Original Android Development] sina_77_:
heeeeeeeeeeeeeeey

I have searched a lot but I couldn't find any patches for xperia z3 dual (d6633)

i need it

may you show me some patches????????????????????????????????????????????????????????????????????????????????
[Xperia Z3 Original Android Development] nailyk:
Maybe you can point me to the olds zip patches and I will tell you if it is ok. Basically you can flash this rom (ad: this twrp is now reported working on z3dual) and change modem files. It should do the trick.
[Xperia Z3 Original Android Development] nailyk:
No release, some news

Hi,

No release for a long time, sorry for that. Since this thread had been opened we manage to get two things:

- a test boot of cm-14.0 (we succeeded with the [MENTION=4675360]tomascus[/MENTION] kernel)

- a switch to 3.10 kernel, display & media HALs 1.3.3 branches.

Finally the 1.3.3 build succeed. One time I saw the blue CM guy so I know kernel & display are ok. But seems init or something like that is totally broken: now the device doesn't go after kernel splash screen and when I get an answer from adb it is:

/sbin/sh command not found.

dmesg show errors about missing /fstab.qcom

so i'm wondering if the initrd is extracted.

Anyway, at this point I think I will throw away all the done job with 1.3.3 branches, getting back to tomascus kernel to check my build tree and see whats happens.
[Xperia Z3 Original Android Development] yecomixer:
[MENTION=6979267]nailyk[/MENTION]

When solve these problems will update this post or do another with the new rom CM14?
[Xperia Z3 Original Android Development] Draiden:
Seems cam is fixed isn't it? [emoji16]

https://github.com/sonyxperiadev/kernel/pull/935
[Xperia Z3 Original Android Development] nailyk:
Probably open a new one, in dev section too as cm-14.0 is not ready yet, even more for z3 ;)

Nothing really sure atm but I am thinking about

- dropping cm-13.0, (just keeping up-to-date with tomascus kernel),

- automate the build it with a VPS, as soon as jenkins works on dockers.

Yes, I saw the picture and there is still work to do but it is working now, it is a huge step forward!

About my previous post I dropped all the done work with 3.10 yesterday, rebuild with 3.4 kernel and everything is fine. Nothing changed on cm side so I don't upload it.

I'm currently giving another try with the 1.3.3 kernel just to see ;)
[Xperia Z3 Original Android Development] Wooby:
Man you are a legend, you're our last chance to get a working cm13 keep the awesome work going. I will unlock my bootloader just for you to test the cm13.

Once again thanks! Hope z3 won't die soon.

Wysłane z mojego D6603 przy użyciu Tapatalka
[Xperia Z3 Original Android Development] nailyk:
New release

2016-11-02 release

Kernel upgrade for security patches. Dirty flash should work :D

Thanks, but this rom is not really usable as a lot of peripherals are not working and I'm not working on it for now ;)

And the sad new is the screen flickering issue is still present on 3.10 kernel....
[Xperia Z3 Original Android Development] :
I know that OnePlus One uses the AOSP device tree for the CM build, so I tried to use the AOSP trees for the Z3C as well. Build succeeded, but the phone wasn't booting for some reason. I think it's related to the vendor files.

Did you try building CM strictly with the AOSP trees for xperiadev?
[Xperia Z3 Original Android Development] nailyk:
I never tried with sonyxperiadev devices tree. As I work on z3 for a year now I upgrade my devices trees each time.

Which kernel are you trying to build? Which blob set do you use?

Do you have some logs?

When you said the phone isn't booting, do you have display or screen keep black with back-light? Does the screen display something, if yes have you tried the generated recovery?

Just in case you are building with 3.10 kernel, is your panel the original one?
[Xperia Z3 Original Android Development] :
I wasn't able to test due to my Z3C being in the service for that moment. I think the last time I tried to build I used the 1.2.2 blobs due to getting camera working (ParanoidAndroid for Z3C got it, with the fisheye effect though, but camera was working ok).

I got no logs, only posts by others.

It seems someone was able to boot AICP 12 for Z3 Tablet compact, we might get more info from him. He claims everything works apart from random reboots and camera recording crahsing: https://plus.google.com/112565168202160096230/posts/Faq8UjeDFbh

The panel is the original one, and yes I use the 3.10 kernel. My main concern about the build is the dependency of the sony-common repo of xperiadev.

https://github.com/sonyxperiadev/device-sony-common/blob/master/CommonConfig.mk

Row 73, 74:

# Include build helpers for QCOM proprietary
-include vendor/qcom/proprietary/common/build/proprietary-build.mk

The vendor/qcom/proprietary wasn't indeed in the folder of neither the RR/CM repo., so I suspect this might be the reason why the phone it wasn't booting. I tried a couple of substitutes or even deleting the line, but the compilation kept crashing.

There were also some issues with some of the libs that were in the vendor folder, but I managed to fix that with some commits.

I think building the ROM with AOSP device tree is worth a shot. Firstly because we can see what's working first handedly. And second because we don't have to fetch all those commits and then wonder what's wrong with it.

If I build it directly with the CM device tree, it boots and works. But the bugs that you mentioned in the OP are still present.

Regarding the camera, I did my research about reverse engineering (method that was used by the OnePlus One devs to fix the reverse fish-eye effect), but sadly I found little to no info, and the devs are not that talkative when it comes to this matter.
[Xperia Z3 Original Android Development] nailyk:
Afaik paranoid and cm are still 1.2.2 based. This kernel doesn't work really good for us and afaik Sony drop it anyway.

This is the actual status with the 1.3.3 on M! Lot of progress had been made :)

I doesn't work that way: will get it official so I keep asking cm dev what they want ;)

Depend on what you build but the proprietary files are on some repo and up-to-date (for 1.3.3). Take a look at my manifest for the vendor list and on the SonyCM git. They get honami & amami working on cm, all branch even with sonyxperiadev.

I am too slow. Another vm with another toolchain with other debug etc mean ~1 week of work for me. There is aosp builds on fxpblog and afaik they are done from sony howto. If you build aosp yourself I'm really interested by the results :)

Yes official cm trees are based on the bad 64.1.2.2 kernel and doesn't provide all the camera blobs.

Do you know we open a dev-thread about that?

Thanks for building roms, helping community and most of all: working with others!

I hope those information will help you.

edit
[Xperia Z3 Original Android Development] :
Myself5 is great. I got a poor Internet connection at the moment (max 500kbps, lol) so downloading a whole source is not possible.

So do we have now any idea what is working properly on 7.1 and what is not?
[Xperia Z3 Original Android Development] nailyk:
I tried to download fxpblog rom but last one is from september and uploaded.net refuse to work with me :s
[Xperia Z3 Original Android Development] yecomixer:
[MENTION=6979267]nailyk[/MENTION]

I think this can serve to operate the camera in the Sony AOSP which have improved according to this news

http://developer.sonymobile.com/201...-devices-with-new-aosp-device-configurations/
[Xperia Z3 Original Android Development] optimumpro:
If you read the article, it specifically says Xperia X and Xperia Z4/Z5. Z3/Z2/Z1 are explicitly and purposefully excluded, as Sony wants you to buy X or Z4/Z5.

Z3 and lower devices will never have a fully working camera...
[Xperia Z3 Original Android Development] :
http://xdaforums.com/showpost.php?p=69477538&postcount=17
[Xperia Z3 Original Android Development] optimumpro:
The latest camera doesn't focus and blobs for Z1/Z2/Z3 are not going to be calibrated, because Sony will not provide Nougat support for Rhine and Shinano devices...
[Xperia Z3 Original Android Development] blackhawk_LA:
I have tried latest build (11-2) and I have that brightness flickering issue. Here's a dmesg in case it's useful http://cloud.tapatalk.com/s/58296c9f131e4/Log-2016-11-14-08.35.08.csv.zip
[Xperia Z3 Original Android Development] nailyk:
Sorry but I doesn't agree with you. AFAIK Alin Jerpelea will release N blobs soon. I just try [MENTION=3816568]Myself5[/MENTION] Carbon rom and camera was working: http://xdaforums.com/showpost.php?p=69477538&postcount=17 it is obviously not perfect, for now, but it is working.

Thanks.

The problem is you are using the same panel as me. Is it the panel shipped with your device or do you get a service on your device? Anyway I will try to solve it but not on cm-13.0.

--------------------------

I have not updated this post from awhile because I was working on another rom, sorry for that.

Since the test of Carbon rom from Myself5 I now this project is possible so I can talk about it:

cm-14.1 built from my repo boot but every peripherals are not working at all (no wifi, no BT, no NFC, etc...) and the cm-14.1 built from SonyCM sources is not booting at all, with no ramoops logs.

I am totally running out of ideas. For the built from my repo it should be an old library inheritance from the olders trees and can't found it. As I know it is a PEBKAC and bury myself into this my guess is I miss something which will be evident for an external perspective (there is an expression but can't remind it), that is why I ask for help.

Any advice welcome :)

Thanks in advance!

P.S.: log of cm-14.1 built from my trees in attachment and the related rom is on androidfilehost iirc.
[Xperia Z3 Original Android Development] blackhawk_LA:
My screen has never been replaced, I bought the phone brand new and with its security seals.

I'm sorry but I don't know a thing about development, so I can only help testing a little and reporting. I hope other devs can have a look into the issues and bring some light
[Xperia Z3 Original Android Development] Myself5:
Get us a dmesg from right after the boot, with

dmesg | grep -i panel

There is a panel that is known to have issues, but none of the developers that have the skill and knowledge to fix it (as of those known atm) have a Z3 with that panel, so nobody can try to fix it.
[Xperia Z3 Original Android Development] nailyk:
The panel with problems is "auo novatek 1080p vid". AFAIK the 720p auo novatek had the same issue.

Small precision, only the half bottom of the screen is flickering. When parsing the driver history I notice there is something about 'dual roi'/'dual panel' (can't remember exactly) and had a related value into dt.

When I played a little with the dt file screen flickering was increase a lot (q&d replace by the 3.4 one). Now I try to learn how dt files works, are selected, etc...

This is blackhawk_LA dmesg and there is mine dmesg.

Edit: Dual panel

I also notice a 8bit 'regression' in multiples commit.

Will experiment on this as soon as this cm-14.1 will be a Little more functional.
[Xperia Z3 Original Android Development] blackhawk_LA:
For me, the whole screen is flickering. At least not the half bottom, but the upper. I usually look at middle - upper screen so maybe the half bottom is not flickering. lol what a mess! I don't have time right now to flash and look carefully
[Xperia Z3 Original Android Development] malacha:
Hi. Luck there. Maybe this will be helpfull? https://patchwork.kernel.org/patch/6837841/ [MENTION=6979267]nailyk[/MENTION] Rom, that you have sent link to me, is good. Camera focus is getting randomly ? (I used flashlight and it repaired focus for a while). Screen flickering is really, really low. Thanks for this rom. I will try to do my best to help/test/do something to help you :)
[Xperia Z3 Original Android Development] nailyk:
more blog than dev

I was ready to open the new cm-14.1 thread when I get some answer from github...

All my PR to add our z3 where rejected because they want use AOSP HALs instead of caf.

So I need to build the rom again with the AOSP HALs, getting something satisfying before opening the thread. Sleeping on it make me feel it is too bad to stop as close as something working.

Maybe some of you saw the pictures taken with my z3, if not here they are.

There is obviously a lot to fix but [MENTION=6063329]malacha[/MENTION] made promising reports.

Anyway, another month to trash and start again, but hope this time it will be easier as the Sony's dev already work on it for a while and the first shot with AOSP HALs (cm-13.0) was good.

In any case I'm still working on cm for our devices, for now, and Carbon roms are great if you want upgrade now.

Thanks for your support.

P.S.: if needed we hold a copy of the SonyCM caf variant repos, ask on IRC.
[Xperia Z3 Original Android Development] blackhawk_LA:
I think we are not thanking enough you and the few devs still working to keep our z3 alive!

You are great!
[Xperia Z3 Original Android Development] Draiden:
[MENTION=6979267]nailyk[/MENTION] please create PayPal account or give a link in your signature you deserve a donation ?
[Xperia Z3 Original Android Development] nailyk:
Those few days I produce nothing except grumbling :). I didn't add a donation because I have no fee for those projects atm. I only spend time, build rom, but don't improve code for now. And still dont rent the build server. Some other people need donation more than me (twrp/twrp for ex), that is why I didn't add a donation URL. Thanks a lot for your support!
[Xperia Z3 Original Android Development] :
Sorry to hear about your your rejection man. Which cm HALS were you using? Its kind of weird your request got rejected because of CAF hals. 3/4 of the cm devices use the cm hals.
[Xperia Z3 Original Android Development] jimmy123322:
Your build "cm-14.1-20161119-nailyk-SonyCM-caf-leo.zip" is great... Working Camera, even with bugs - is great... I test your build, and it seems have only one big bug with the screen... I hope you continue working at cm-14.1 for Z3... Thx man!!!?
[Xperia Z3 Original Android Development] nailyk:
Yes. A friend ask me to build copperhead for his N5 yesterday and afaik you also have a N5. I notice there is both HALs variant for this device, but is it still 3.4 based? Maybe it is the idea behind: CAF for 3.4 and aosp for 3.10 msm8974?

The HALs I used.

I will take advantage of this transition to try to update cm-12.1 and cm-13.0 roms.
[Xperia Z3 Original Android Development] drakonizer:
As far as I know, the Nexus 5 has only 3.4 kernel, but CM has trees for both caf and non caf HALs.

Personally, I've tried to use SonyCM caf HALs, and always ended with build errors related to the camera HAL. I don't understand why their removal is bad.
[Xperia Z3 Original Android Development] nailyk:
Really fun, I always get the opposite :)

I'm not enough experimented to say if one HAL is better than another. I only regret the way they do it.

So all others msm8974 are still 3.4 based. But maybe we will be able to use the same HAL. I notice the CM aosp had a good commit history. Do you tried it? With which one are you building?
[Xperia Z3 Original Android Development] drakonizer:
I haven't built anything since a week or so, but my cm14.1 builds were based on the cm14.0-aosp trees in SonyCM. But, I used the HALs from SonyAosp, particularly the android-7.0-test branch of the camera HAL, which was known to have the least issues at the time. Looks like alviteri took it down now, but I think most of those commits are now in the default branch. Camera crashed occasionally, but worked most of the time.
[Xperia Z3 Original Android Development] nailyk:
2016-11-23 release

Periodical build, nothing new.

Not tested.
[Xperia Z3 Original Android Development] Wooby:
Unlocked bootloader today ;) just for test your builds.

Tested Cm14.1 camera dark and fisheye, screen flickering (from half to down screen), a bit slow compared to cm12.1 (worse response)

Tested cm12.1 with today's build, fisheye bug rest ok.

Now i am downloading Cm13.1 :)

Thx for the roms, hope cm14.1 will be soon my daily driver [emoji14]

Edit.

Couldnt install cm13 error 7.
[Xperia Z3 Original Android Development] :
I tried to build CM13 with the AOSP sources, sadly I got here:

http://pastebin.com/nMF6JtwG
[Xperia Z3 Original Android Development] drakonizer:
Delete the msm8994 display HALs and use 8974 ones.
[Xperia Z3 Original Android Development] nailyk:
Removing the "xx_BF64_xxx := true" flag into you BoardConfigs makefile should change the HAL.

Full rebuild is needed on HALs changed. (rm -rf out/target/product/z3c)
[Xperia Z3 Original Android Development] :
After this i used some fixes by jerpelea posted on sonymobile forums

[url]https://android.googlesource.com/platform/hardware/qcom/display/+/master/Android.mk#7[/url]

-include $(call all-named-subdir-makefiles,msm8974)

+include $(call all-named-subdir-makefiles,msm8994)

And

You have to port

[url]https://github.com/sonyxperiadev/camera/commit/0f2f305009d1cf55bde02116696d262ffdc84609[/url]

to

[url]https://github.com/sonyxperiadev/camera/tree/aosp/LA.BR.1.3.3_rb2.14[/url]

I got no result. But I will try your suggestions when I get home
[Xperia Z3 Original Android Development] nailyk:
If you are building CM I think using SonyCM manifest could be a solution. All of this are already merged/included.
[Xperia Z3 Original Android Development] :
SonyCM has only 14.1 branches, while I am trying to compile CM13 here.

Edit: Sadly, I couldn't find the flag that you mentioned.
[Xperia Z3 Original Android Development] nailyk:
Which kernel are you trying to build with?

Can you join #xperia-dev on freenode?
[Xperia Z3 Original Android Development] :
https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BR.1.3.3_rb2.14

I'm using all the xperiadev repos for M.
[Xperia Z3 Original Android Development] nailyk:
On the sonyxperiadev there is a lot of problems to build for CM, path are not the right one. Take a look at the qcom_target.mk file into your cm toolchain... And they changed it recently (another time where I tear my hair out ;))

Now AOSP HALs switch is required so you need to remove both SONY_BF64_KERNEL_VARIANT & BOARD_USES_QCOM_HARDWARE flags.

Add this into a random make file will display all the HALs path when you build target 'toto'.

Then place the HAL into the right location with your manifest, it should build fine and will be as close as possible to official builds. Perhaps you will get some other missing include but they could be solved with grep and sed (maybe with the patches you linked earlier), but I doubt.

That is exactly what I have planned for this we and cm-14.1.
[Xperia Z3 Original Android Development] :
I know what you're saying, but to update the CM device trees with the AOSP changes is tiring as well.

msm8974 I think it's a similar repo with the sony-common from AOSP.

https://github.com/sonyxperiadev/device-sony-common/blob/m-mr1/CommonConfig.mk

Can't seem to find the flags you speak of.
[Xperia Z3 Original Android Development] nailyk:
Rom built successfully with AOSP HALs but bluetooth not working anymore and display is really laggy. I probably mess-up something.

I will try to PR the new manifest asap.

While testing I just figure something about camera: looks like the shutter didn't change is diameter (if it is possible on this kind of hardware). Maybe it is the cause of darkness?
[Xperia Z3 Original Android Development] nailyk:
New thread opened for cm-14.1

I think about closing this one in a few because the 14.1 seems to be fairly usable. Obviously there is problems to solve but I know some person used it as daily driver.

Tell me if you want to keep this one updated.
[Xperia Z3 Original Android Development] frabe8378910:
Just my 2 cent.... :D

I don't care about "the latest" Android or CM versions. I'd prefer a stable, secure and long term support CM version.

If all former CM features are working on a new Android (aka CM) version and a Dev has time to spend, then it's time to have a new CM version .... :laugh:

As CM 14.1 itself does not support the "theme engine" and maybe other stuff, why waste your time with that??

Keep your energy for a stable and further security fixed CM13 or even CM12.1 and provide a donation button ... :D

Thank you for your work.
[Xperia Z3 Original Android Development] nailyk:
Security are updates. I will not/I'm not able to maintain old version, backports all the security fixes into no more maintained roms. If you care about security, you are using linux and know what I mean by security are update ;) And there is no LTS in android world.

I switch to cm-14.1 for 2 reasons: security patches and getting official. If you check cm-12.1 and cm-13.0 gerrit they are not updating it as before. Some patches are backported, that's all.

And for now cm-14.1 is not mature, theme engine is on the way (not the same as cm-12.1 however) and some parts are broken (all the gamma things, btw that is why theme engine is not out afaik).

Also cm-14.1 is the only way to get camera on shinano devices....

I will do my best to upgrade olders rom but (I'm selfish) as soon as my 'all day' z3 will be updated to cm-14.1 (running cm-12.1 right now) I will drop them, sorry.

Also as soon as cm will became official I will be able to help paranoid devs as my final, goal is paranoid on my z3.
[Xperia Z3 Original Android Development] :
Do you really think we'll be able to make it official for z3/c?
[Xperia Z3 Original Android Development] nailyk:
Honestly I don't know but if I stop believing it I stop here...

Adam Faden doesn't say it will be impossible but will be hard. (he is a CM contributor).

The biggest problem is the SonyCM repos are unmergable. However when you pass the port checklist we are close to.

I try being in touch with some cm dev to stay aware of how we can merge but the old maintainer refuse to talk to me. So it is not done and not over atm. That all I know and why I'm slow, try to be as close as possible of the both repos.
[Xperia Z3 Original Android Development] :
I call bs on this. I'm sure there's a way bro. You can add some of the sony hals directly into the device tree.
[Xperia Z3 Original Android Development] frabe8378910:
Could you please explain it to me, as I don't understand CMs behavior:

1) The old Z3 maintainer did drop his Z3 support and so "nightly" development dropped. You are trying to help/take over that part, but the old dev do not support you.

2) Is CM willing to accept somebody else (i.e. you), if his code complies to their requirements or do they just decide, that a device is to old/whatever and nobody can support it officially then?

3) Is this dependent on the CM version, so a more recent version would be accepted?

---------- Post added 29th November 2016 at 12:03 AM ---------- Previous post was 28th November 2016 at 11:34 PM ----------

Yes, running Linux! :)

Debian (testing) as a rolling update on all my server / workstations since many years.... I'll miss that on Android!

Thanks for clarifying the CM14.1 hope.