yashsingh1/xdaforums huggingface dataset:
[Xperia Z3 Original Android Development] nailyk:
It took me a while and some mistakes but i finally give a try with the stock (not a random ftf file) rom. Now i can confirm:

z3 had a wide-angle camera: picture taken with z3 (every days d6603, cm-12.1) m4aqua (full stock, locked). Phone side by side.

For the 'revert-fisheye-bug' in fact, i always call that 'fisheye-bug' ;) and you are right, it was only present on 4K recording (at least on preview) as i can't view the recorded movie, because my my old laptop refuse to open the 4K movie :(

Source image dimensions are too high: 3840x2160 (maximum is 2048x2048)
FATAL: Cannot initialize video driver.

Also in the attachment, i took some picture in 8Mpx and 21Mpx and the view field is not the same. In 2k and 4k too.

(btw i made some ta mistake (phew phone not bricked) and i'm not sure everything was fine because i was not able to set iso on an higher level than 3200. )

In my case i'm a dev-trainee. I will not put the cart before the horses so i will stop here this off-topic discussion about fisheye bug until we got a working camera. But i like to think i am able to write q&d functions to implement this kind of libs (graphicsmagicks, imagemagick, matlab) to implement a correction.

From the readings of this thread what i understand is: the rom is working, except the camera, the fm radio, and the nfc (only for the d6533 variant? As you see here i not really trust my nfc antenna ;) ). I don't know if those non working peripherals are blocking for an official CM request.

For now i'm trying to contact the officials CyanogenMod developpers to get the right guideline about the kernel, the version on which we should start, etc... Next step will be clean the whole tree to 1. be able to build on others shinano variants, 2. make pull-request.

Next i need to learn how the hal world works. I guess i will try to implement more basics peripherals like fm radio, the camera light, maybe try to make a fake camera for hal to learn the full process.

But atm i need to find more doc, and a way to improve my vim: i need completion working on structures and functions!

Here is how i see future of this rom :silly:

edit: if qcom had abandoned our snpadragon 801 they don't plan to make more money on it isn't it? So.... why they are not simply releasing the source code of all the hardware stuff?
[Xperia Z3 Original Android Development] nonperson:
Thanks again.

D6653, not dual, single SIM and same as D6603 except for bands (Asia-Pacific variant). Specs:

D6603

UMTS HSPA+ 850 (Band V), 900 (Band VIII), 1700 (Band IV), 1900 (Band II), 2100 (Band I) MHz

GSM GPRS/EDGE 850, 900, 1800, 1900 MHz

LTE (Bands 1, 2, 3, 4, 5, 7, 8, 13, 17, 20)

D6653

UMTS HSPA+ 850 (Band V), 900 (Band VIII), 1900 (Band II), 2100 (Band I) MHz

GSM GPRS/EDGE 850, 900, 1800, 1900 MHz

TD-LTE (Band 40)

FD-LTE (Bands 1, 3, 5, 7, 8, 28)

As to RIL, yes seemed to be working fine, calls and data.
[Xperia Z3 Original Android Development] okij:
The reason for the different view of field in the pictures you made is just that you took the 21Mpx picture in 4/3 format (5248x3936 pixels) and the 8Mpx picture in 16/9 format (3840x2160 pixels), so in the 8Mpx picture the top and bottom are cut off. If you look at your pictures, you can see that horizontally they have the same view of field. :)

So if you take pictures in 4/3 8Mpx mode (3264x2448 pixels), the view of field is the same as in 21Mpx mode (5248x3936 pixels) and the full sensor area is used in both pictures.

Also when recording videos, the view of field actually is the same in 2k and 4k. However, if you turn on image stabilization (which apparently you had turned on for your 2k video, but not your 4k video), the view of field becomes smaller, since the camera software needs some border area of the sensor to compensate for vibrations and movements of the camera (that's how software image stabilization works).

Yes, indeed we need to have a working camera first. :fingers-crossed:

As a guess: ... because they can make even more money with their new SOCs this way. :silly:

But I don't know: Did they probably release their source code for some older SOCs after abandonding them? Then we still could hope for their source code for the Snapdragon 801.
[Xperia Z3 Original Android Development] ILikeBubbles:
Running the most recent version.. it's fantastic except the contacts sync keeps crashing so I don't have any of my contacts.. that's the only problem I've has though! Thanks for the hard work!
[Xperia Z3 Original Android Development] nailyk:
Oh d6653, my eyes cheats on me, i read d6633! If i remember correctly, modems blobs are the same but the difference is in modemst[12] partitions between D6603 & D6653. Thanks for reporting a working variant.

Sorry about that. Can you tell me more? What sync app are you using? Can you isolate the logcat part of app crashing or providing me a full logcat?
[Xperia Z3 Original Android Development] ILikeBubbles:
Uh.. how do I get a logicat xD I've only ever rooted and flashed haha
[Xperia Z3 Original Android Development] nailyk:
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat

Basically, if you are able to crash the app when you want: adb logcat -c (clear logcat), adb logcat | tee -a /tmp/logcat_crash_contact_20160912.log, crash your app, ctrl+c to end the logcat session.
[Xperia Z3 Original Android Development] blackhawk_LA:
Or use logcatx from play store ;)
[Xperia Z3 Original Android Development] Swidilator:
I tested the ROM this last weekend, one thing that I do have to say is that I never got more than edge at any time. I'm from South Africa so maybe the included bands are missing the South African set, or maybe it's something else...
[Xperia Z3 Original Android Development] nailyk:
Is your device d6603? Can you tell me the baseband version? Also, in the phone app, dial *#*#4636#*#*, phone information, check the 'set preferred network type' setting, go to menu (upper-right), Select radio band, and tell me what choice you have or take a screen shot please.

can you check if, in the rom you flash, the modemst[12] partition where updated?
[Xperia Z3 Original Android Development] Swidilator:
I will do so this weekend, at the moment I need my phone :).
[Xperia Z3 Original Android Development] nailyk:
Totally. I edit my post with another question. Also, getting the information of the band selection/version from a working rom could be useful ;)
[Xperia Z3 Original Android Development] ILikeBubbles:
Ok maybe I just had a bad Gapps... I was talking to my husband and he said it was weird for a Google service to crash in a rom. So i downloaded another Gapps and it was line 4mb larger than yesterday's (openGapps.org) and after flashing that and wiping dalvik it seems all my contacts are here! Thank you!

I did try to recreate the problem but couldn't make it give the warning pop up again.. and for some reason couldn't find logicatx in the play store either..

Thank you both though for your extremely quick responses!! So far I think this is definitely stable enough for me to use as a daily driver. :)
[Xperia Z3 Original Android Development] nailyk:
[MENTION=5075064]optimumpro[/MENTION]

is the screen flickering issue also present on others devices than z3 with 3.10 kernel?
[Xperia Z3 Original Android Development] nailyk:
q&d test release with 3.10 kernel added (2016-09-14)

Screen flickering is present and in a global way i miss configure the kernel.
[Xperia Z3 Original Android Development] optimumpro:
Yes. As I say, Sony AOSP version of 3.10 kernel has Down Syndrome...
[Xperia Z3 Original Android Development] drakonizer:
Are you sure about that? My Z1 has been running N (3.10 kernel, 1.3.3 branch) for quite a number of days now, and it has no screen flickering issue.
[Xperia Z3 Original Android Development] nailyk:
Have you replaced your lcd panel on your device?
[Xperia Z3 Original Android Development] yecomixer:
[MENTION=6979267]nailyk[/MENTION] I sent my panel LCD replace the original and still does not work with 3.10 Kernel know if it worked before could be the problem? Only it works with Kernel 3.4
[Xperia Z3 Original Android Development] nailyk:
Which rom & device isn't working with 3.10 kernel?
[Xperia Z3 Original Android Development] yecomixer:
CyanogenMod 13 ROM you are doing with the new Kernel 3.10 and 7.0 AOSP Nougat with 3.10 kernel do not work in my Z3 D6603, only it worked when used in your rom CyanogenMod 13 Kernel 3.4
[Xperia Z3 Original Android Development] nailyk:
Really interesting. Someone on the paranoid 6 thread had same problem. I also bought a replacement panel on amazon which refuse booting on my other d6603 (locked bootloader) and i can't display twrp (kernel 3.10) with the D6603 motherboard with cyanogenmod. I send the panel back and order another one from another seller. New one is perfect (except they send me a white one :( )

Does the twrp display is ok when booting it from bootloader (volume down + power)? Do you 'upgrade' the cm-13.0 3.10 kernel? If it is the case, can you send me adb shell dmesg | grep panel please? I guess only the display/touch is not working, the rom should boot 'fine' otherwise.
[Xperia Z3 Original Android Development] drakonizer:
Yes I have. It's funny how an aftermarket display that doesn't work well with LP custom ROMs work properly on MM and N.

I also wanted to know...do you guys have any issues with charging? In honami, the phone always charges with USB speeds even when plugged into an AC input.
[Xperia Z3 Original Android Development] nailyk:
In fact, its seems to be a driver problem. Some lcd are no more included in the 3.10 kernel.

For the cm-13.0 charging it is on the todo list :s I don't check that for now as i still don't know on which kernel we start the port. The official maintainer should answer me soon. (depending on the kernel, the drivers had different names for the same device. So we have to correct some files to change them according to the right kernel path. )

New weird behavior for me: with the new white panel+touchscreen i had a white circle which act like a mouse (on the 3.10 kernel, not tested with the 3.4). Maybe an .idc problem.
[Xperia Z3 Original Android Development] drakonizer:
I remember having the same exact weird issue when I tried to use newer AOSP blobs on the old cm device trees for cm13. I fixed it by switching to sonyxperiadev trees and using the latest blobs.

Can you check your vendor directory and verify all the blobs are there?
[Xperia Z3 Original Android Development] nailyk:
o0 i am currently using the sonyaosp blobs and have a lots of issues with those. (don't look at logcat with the 3.10 version :p )

I give a try with the Muppets, thanks!
[Xperia Z3 Original Android Development] drakonizer:
Are you building with the 3.10 kernel? If so, Muppets blobs won't work. You should use sonyxperiadev ones for that.

What I meant was to check the vendor directory in your ROM/phone and make sure all the blobs are there. Those blobs don't work with CM device trees.

Edit: I see you're using the 3.4 kernel. You should be better off using the Muppets blobs. If that doesn't work, try reverting a few commits in the project, because if I remember correctly, there was a time (before the unified kernel) when cm13.0 booted using the old android_kernel_sony_msm8974 kernel source from cm, which was 3.4

Edit 2: Regarding camera: this commit message seems promising. He says they got the camera working once with newer (4.3+) blobs, but never again. A deeper investigation into this can be fruitful.
[Xperia Z3 Original Android Development] nailyk:
in fact, both. I start to regress the build tree with 3.4 kernel to make a proof-of concept with this old kernel. The rom sounds pretty stable from the feedback on this thread but, the kernel i use is not viable (last commit on jan 2015). One of the CyanogenMod maintainer i'm in touch with told me the 3.10 kernel is a better option. So, now, on my phone, there is a 3.10 kernel.

From the begging a use the Muppet repo for the 3.4 kernel but i figure out the blobs on this repo are extracted from a running stock rom and are drm protected (thanks optimumpro). Plus, the official maintainer told me to keep as close as possible to the sodp sources, so i am currently experiencing with the 3.10 kernel and the sonyaosp blobs but this 3.10 kernel is a pain for me...
[Xperia Z3 Original Android Development] drakonizer:
If you're using the 3.10 kernel, just double check whether all the blobs in the vendor repo are present in the final compiled build, because when I had this issue before, it was due to messed up blobs.

Personally, I feel the 3.10 kernel is the most straightforward to build with, with almost no chance of errors. But when compared to the 3.4 kernel, it's buggier. I'm starting to think optimumpro's opinion that stability will only come from the 3.4 kernel is the best hope we have.

I don't think all the stock blobs are drm protected, just the ones for camera. Take a look at my previous post for an interesting commit.
[Xperia Z3 Original Android Development] nailyk:
I check the blobs and you are right, some are missing. But it didn't change anything for the touchscreen.

In fact the new touchscreen name was 'clearpad'. I follow this process and now the touch screen work fine.

Thank for all your help, opinion and links. Now i have a working touchscreen, i can take a further look at this :)
[Xperia Z3 Original Android Development] yecomixer:
[MENTION=6979267]nailyk[/MENTION] The rom starts but the screen goes dark and the touch if it works but you can not see anything or everything the TWRP recovery with Kernel 3.10 and for Paranoid Android ROM does not work for what you use the same Kernel 3.10
[Xperia Z3 Original Android Development] yecomixer:
[MENTION=6979267]nailyk[/MENTION] Not if I'm already testing but here are the files open source Kernel Xperia Concept lagoon hope you serve helps | http://developer.sonymobile.com/dow...hives/open-source-archive-for-mob30m-z1-3636/
[Xperia Z3 Original Android Development] tomascus:
Nailyk, what issue are you having with 3.4 kernel? Only issue i've seen is I haven't got camera working yet
[Xperia Z3 Original Android Development] nailyk:
I need to know what panel is on your device. with

adb shell dmesg | grep panel

we should see the lcd name and maybe a can add it back to the 3.10 kernel.

I already test this kernel, but it is fairly different from others and need a lot of work to get a fully working rom. As i still don't know if the cm maintainers would go on 3.4 or on 3.10 kernel i stop for now with this one.

You are right. For end user the only issue is this one. btw I don't know if we will be able to have a working camera with this one. Also this kernel is really old, no more up-to-date since jan 2015, so no security patch. It is a real problem. That is why i test other kernels to found one viable.

Today i will take a tour on other shinano (and sony) devices xda thread and see what kernel they uses.
[Xperia Z3 Original Android Development] tomascus:
You can just cherry pick security patches yourself, other than that I posted my kernel on the Nougat thread.

I spent the whole of today trying to figure out the camera, no luck at all.

Also, what do you mean the concept kernel is different? It's pretty close to AOSP
[Xperia Z3 Original Android Development] nailyk:
Thanks. Your git with concept 3.4 could be interesting. In fact cm13 is most close to caf than sodp.

I guess we should really open a freenode channel. It is too sad that everyone do the same on this own. Together we will go faster!

What about a sony-dev or xperiaZ-dev ?
[Xperia Z3 Original Android Development] tomascus:
Haha, I only see like a very small handful of us here, Hangouts usually works fine if things need discussing :p
[Xperia Z3 Original Android Development] Cirra92:
Now it's time to unite Z3 and Z3c devs to fix the crap out of that camera :D
[Xperia Z3 Original Android Development] nailyk:
sad for IRC. I try to keep as far as possible from google....

After my tour to the other devices thread and on the cm github (amami/honami/scorpion/siruis/castor), seems those devices are deserted. I already ask on cm-dev but don't get answer. That is why i need your help:

Does someone know on which state are the others xperia Zxx devices? Are they abandoned? Someone is working on it? Which kernel & hardware variant they use if cm-13 or 14 exist?​

Sure but before the camera, we should unit before to get every device working on cm-13.0, then pull to gerrit ;)

btw camera will be.... difficult
[Xperia Z3 Original Android Development] :
https://github.com/AdrianDC/android_device_sony_huashan

AdrianDC seems to know a lot about the sony stuff.

---------- Post added at 11:25 PM ---------- Previous post was at 11:14 PM ----------

C:\Users\Aren Clegg\Desktop\Minimal ADB and Fastboot>adb shell

leo:/ $ dmesg | grep panel

[ 1131.996376] mdss_dsi_panel_on: ctrl=f2f35810 ndx=0

[ 1145.383529] mdss_dsi_panel_off: ctrl=f2f35810 ndx=0

[49072.042461] mdss_dsi_panel_on: ctrl=f2f35810 ndx=0

[49107.469884] mdss_dsi_panel_off: ctrl=f2f35810 ndx=0

[50626.769201] mdss_dsi_panel_on: ctrl=f2f35810 ndx=0

[50660.226226] mdss_dsi_panel_off: ctrl=f2f35810 ndx=0

leo:/ $

Im running the android developer preview N 3 (rooted), which actually uses the 3.4 kernel. Of course, no screen glitches.
[Xperia Z3 Original Android Development] nailyk:
Thanks. He also don't answer me on the cm chan. Seems he is the maintainer for older devices (also msm8974 based) and only use 3.4 kernel.

For the glitches i guess it is a dtsi problem. I try to build with a 3.10 kernel but ran into a lot of problem. Plus as i have totally broken my original lcd it will be more difficult to test for screen glitches :s
[Xperia Z3 Original Android Development] :
I dunno how big of a deal it really is, but was comparing https://github.com/sonyxperiadev/ke....14/arch/arm/boot/dts/qcom/dsi-panel-leo.dtsi vs https://github.com/tunturn/z3concept/blob/master/arch/arm/boot/dts/dsi-panel-leo.dtsi

in the 3.10 kernel (sonyxperiadev) they have this code:

dsi_novatek_auo_1080_vid: somc,novatek_auo_1080p_video_panel {

qcom,mdss-dsi-panel-name = "auo novatek 1080p vid";

qcom,mdss-dsi-panel-controller = <&mdss_dsi0>;

qcom,panel-supply-entries = <&shinano_panel_power_supply>;

qcom,mdss-dsi-panel-type = "dsi_video_mode";

qcom,mdss-dsi-panel-destination = "display_1";

qcom,mdss-dsi-panel-framerate = <60>;

qcom,mdss-dsi-virtual-channel-id = <0>;

qcom,mdss-dsi-stream = <0>;

qcom,mdss-dsi-panel-width = <1080>;

qcom,mdss-dsi-panel-height = <1920>;

qcom,mdss-dsi-h-front-porch = <104>;

qcom,mdss-dsi-h-back-porch = <56>;

qcom,mdss-dsi-h-pulse-width = <20>;

qcom,mdss-dsi-h-sync-skew = <0>;

qcom,mdss-dsi-v-back-porch = <46>;

qcom,mdss-dsi-v-front-porch = <6>;

qcom,mdss-dsi-v-pulse-width = <2>;

qcom,mdss-dsi-h-left-border = <0>;

qcom,mdss-dsi-h-right-border = <0>;

qcom,mdss-dsi-v-top-border = <0>;

qcom,mdss-dsi-v-bottom-border = <0>;

vs. z3 concept 3.4 kernel

dsi_novatek_auo_1080_cmd: somc,novatek_auo_1080p_cmd_panel {

qcom,mdss-dsi-panel-name = "auo novatek 1080p cmd";

qcom,mdss-dsi-panel-controller = <&mdss_dsi0>;

qcom,mdss-dsi-panel-type = "dsi_cmd_mode";

qcom,mdss-dsi-panel-destination = "display_1";

qcom,mdss-dsi-panel-framerate = <60>;

qcom,mdss-dsi-virtual-channel-id = <0>;

qcom,mdss-dsi-stream = <0>;

qcom,mdss-dsi-panel-width = <1080>;

qcom,mdss-dsi-panel-height = <1920>;

qcom,mdss-dsi-h-front-porch = <56>;

qcom,mdss-dsi-h-back-porch = <8>;

qcom,mdss-dsi-h-pulse-width = <8>;

qcom,mdss-dsi-h-sync-skew = <0>;

qcom,mdss-dsi-v-back-porch = <8>;

qcom,mdss-dsi-v-front-porch = <233>;

qcom,mdss-dsi-v-pulse-width = <2>;

qcom,mdss-dsi-h-left-border = <0>;

qcom,mdss-dsi-h-right-border = <0>;

qcom,mdss-dsi-v-top-border = <0>;

qcom,mdss-dsi-v-bottom-border = <0>;

qcom,mdss-dsi-bpp = <24>;

qcom,mdss-dsi-underflow-color = <0x0>;

qcom,mdss-dsi-border-color = <0>;

some of the variable are WAY different. I dunno if it's just because one kernel is 3.4x and one is 3.10 or what, but I have a feeling the glitches *might* have to do with this. Comparing the JDI (which seems to be the screen replacement people get that has no screen glitch, the variables are *the same* in both 3.4 and 3.10 kernel.
[Xperia Z3 Original Android Development] ILikeBubbles:
Oh no! You're the one whose been saving my z3! There hasn't even been a real official cm12.1 update in months... Is there anything we can do to help? I see you're in France right... Have you checked Swappa? apparently no z3 on swappa.. and doesn't seem to be a Swappa france. What do you intend?

http://m.ebay.com/itm/New-Unlocked-...oid-Smartphone-Black-/272237542795?nav=SEARCH

I don't mean to assume you have money... I just... You seem to be the last person keeping the z3 alive that I can tell and I'd hate to lose your support :(
[Xperia Z3 Original Android Development] tomascus:
Are you guys experiencing this issue with both MSM8974 and MSM8994 display HALs?

Documentation: https://android.googlesource.com/ke...ion/devicetree/bindings/fb/mdss-dsi-panel.txt

Still confusing..
[Xperia Z3 Original Android Development] :
android N preview 3 boot.img:

https://www.androidfilehost.com/?fid=24723757092307431

android N preview 3 system dump:

https://github.com/aclegg2011/android_vendor_sony_leo_n-prev3

---------- Post added at 02:32 AM ---------- Previous post was at 02:18 AM ----------

yea, both. Only on 3.10 kernel. And only on the aou/sharp displays, not JID.
[Xperia Z3 Original Android Development] nailyk:
Thanks,

Thanks! Also others variables are missing, especially some about timing and clearing. I'm trying a q&d patch to see if y can get changes on the glitches. Perhaps the auo protocol implementation is in cause. Thanks tomascus for the dtsi doc! Now i need to find the panel datasheet to check if everything if ok ;)

For cm12.1 you are right, i totally forget to make my pull requests :( I also still need to clean my twrp branch to request official support. Why days are only 24h long :s

No worries :) about the screen! I order i new one which arrive but it is white instead of black. The seller will replace it soon.

With the old screen (now broken) i try to split the digitizer and the lcd to replace only the digitzer.... My process was not really good :( The fact is the screen glitches only appears with the original sony screen (which is now broken for me).

Anyway i will not abandon now ;)

Edit: i have the begging of an answer from the cm dev! Seems they heading for using 3.10 unified kernel as it is the only one maintained by sony devs. And only with this one we will be able to have a working camera.
[Xperia Z3 Original Android Development] nailyk:
official kernel answer

[MENTION=3771760]aclegg2011[/MENTION] [MENTION=4675360]tomascus[/MENTION] [MENTION=5075064]optimumpro[/MENTION]

Official answer is arrived: cm devs will go on 3.10 kernel. We are looking if we go on BF64 or on BR variant (build instructions for nougat are on BR.1.3.3).

For now the BF64 is in place now up-to-date and almost working.
[Xperia Z3 Original Android Development] drakonizer:
See, now that's the problem. 3.10 kernel is not stable yet. Camera is broken for all msm8974 devices, and there are a bunch of other bugs as well, charging being the second biggest. I thought the whole point of this thread was to somehow get the 3.4 kernel to work well with 6.0+ ROMs.

You could've built cm13 almost 7 months ago, if you were planning to use 3.10. I myself had built cm13 for honami back in march. And nothing much has improved since then.

Also, the newer blobs work only on 1.3.3 branch, so I don't understand how you'd use BF64, even if you wanted to.