yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] munjeni:
10-24 21:50:36.809 500 500 I CameraFlashlight: Opening camera 0
10-24 21:50:36.810 500 781 D QCameraStateMachine: static void* qcamera::QCameraStateMachine::smEvtProcRoutine(void*): E
10-24 21:50:36.961 500 500 I QCamera2HWI: [KPI Perf] int qcamera::QCamera2HardwareInterface::openCamera(hw_device_t**): E PROFILE_OPEN_CAMERA camera id 0
10-24 21:50:36.966 500 794 D QCamera2HWI: static void* qcamera::QCamera2HardwareInterface::defferedWorkRoutine(void*): start data proc
10-24 21:50:36.966 498 498 E audio_route: Control 'SLIMBUS_0_RX Port Mixer INT_BT_SCO_TX' doesn't exist - skipping
10-24 21:50:36.966 498 498 E audio_route: Control 'INTERNAL_BT_SCO_RX Audio Mixer Multimedia6' doesn't exist - skipping
10-24 21:50:36.966 516 516 E mm-camera-isp2: isp_resource_get_isp_id:3526 cannot open '/dev/v4l-subdev11'
[COLOR="Red"]10-24 21:50:36.966 516 516 E mm-camera-isp2: isp_resource_gen_hws_caps:3603 failed: subdev name /dev/v4l-subdev11 sd_num 0 invalid isp_id 2[/COLOR]

Isp only not working, everything other is ok! Idea???
[Sony Cross-Device General] davidteri91:
Really.... Really do you want put under conditionals a whole platform stuff?? Please help us to fix it in a proper way... It can be more easy than do what you have in your mind...

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
Whats a plan? I spent 15 days on stupid 1.3.3 camera! Enabled all possible debug logs, analysed and analysed and finaly got disapointed with it! I no want to spend a day on it anymore sorry. That camera branch is messed up with dualcamera, probably blobs too! Camera working on 1.2.2 kernel but since 1.2.2 is not stable, for example videos not working corectly, audio too, the rest not tried... I have plan to use cam 1.2.2 on 1.3.3 kernel, thats only my plan by now.

What whole platform man? If it goes to the new folder conditional would be only on few headers! I will move dtbs things to the new dtbs and call them 1.2.2XXXX and with Kconfig/Makefile make separate things in new folder, I don't see a problem there. You guys think you can get 1.3.3 camera working??? I don't think, if you realy think than good luck to you guys! Jerpelea and guys unable to fix that, what we can expect? Nothing! We have chance with 1.2.2
[Sony Cross-Device General] davidteri91:
Since 1.2.2 will not receive. More updates in camera (userspace) you will spend days of development for nothing....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
Even we will not receive since msm8974 is legacy. I don't see a reason why we don't start on a working branch aka 1.2.2! Camera 1.2.2 takes good pictures! Exposure is somehow low, I have tried it to max and realy gets a good and focused pictures! Updates on 1.3.3 will stop soon or very soon till after guys switch to the new branch, and things will be the same. Every new branches will produce more and more broken camera since 8974 is a legacy, so lets focus on latest one working camera branch! There is 3 options:

1. stay on almost stable 1.3.3 branch with "cant fix" cam

2. stay on unstable 1.2.2 kernel with bugs in video, audio..

3. stay on almost stable 1.3.3 but revert camera to 1.2.2

My choice is 3, hope you agree with me?
[Sony Cross-Device General] erikcas:
Option 4 is missing?

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] munjeni:
Ah, ok

option 4: fix camera on 1.3.3

Good luck to you and everybody!
[Sony Cross-Device General] erikcas:
Let's go for it

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] munjeni:
good luck!
[Sony Cross-Device General] erikcas:
You will need it [emoji12]

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] munjeni:
I will get 1.2.2 cam on 1.3.3 for 100 percent sure, but let see your next 15 days on camera 1.3.3 ;)
[Sony Cross-Device General] snaky90:
Great news !
[Sony Cross-Device General] m0d:
1.3.3 might already be a dead-end branch, as devs already started porting to new branch(es)

​

64-bit only at the moment:

https://github.com/kholk/kernel/tree/aosp/LA.HB.1.3.2-19600-8x96.0/arch/arm64/configs

https://github.com/kholk/kernel/tree/aosp/LA.HB.1.3.2-19600-8x96.0/arch/arm/configs

No devices for 32-bit (unless plan on using generic qcom_defconfig

Also, development is not truly open, as seen from above.

You want devs to join your development, but there might be chance of jumping to new branch soon.

So all work for nothing or can it be easily moved to the new branch?

Also, sony devs(or dev, I believe only jerpelea is contracted to sony) have not confirmed if problem is indeed the 1.3.3 blobs or not. If the blobs are the problem then everyone wasting time.

If you really want devs to join you need roadmap and information of current status of project.

Camera will probably never be solved, as it has been two years since z3 and z3c and the start of the open development commitment by sony,

and so far no stable base has been reached.

So working on 1.2.2 would seem to be better, unless sony dev can provide the magic that is missing.

Sony are able to provide a working set of blobs, but they do not want to. They do not seem to care if they sell devices or not, as many devs will get if they provide stable blobs.

Mobile business seems to be more of a hobby to sony they make all money from other projects so they do not care.

So far even the incall volume bug has not been fixed (another place which seems to be missing blobs: https://github.com/SuperBenevolent/aosp-vendor-qcom-extras).

Qcom provided sony all info to build on platform, so they should be able to provide barebones blobs (they will never provide their own mess of patches anyway).

If they do then development can truly commence.

Unless sony does commit on their open development project the best option for somewhat open camera would be the last best working case which is 1.2.2 blobs

or someone extremely bored and manage to port from latest stock image(which might be impossible).
[Sony Cross-Device General] erikcas:
[DEV-ONLY][Z1-Z3][3.10 kernel][MSM8974/SD800-1] Custom ROM camera development

100%. Wow will keep that in mind. Beware with promises.

Edit: but then again. Scoring with promises and kernelhacking / bloblotteries seems good for thanksmeters.

So good luck is in place for you here. On to your next 15 days. Good luck again
[Sony Cross-Device General] drakonizer:
You're absolutely right. 1.2.2 seems like the best bet. Fixing all the non camera issues on 1.2.2 would definitely be easier than getting camera to work on 1.3.3. I'm sure even if msm8974 gets added to the 3.18 kernel, there would be more issues than less. Our best bet right now is using the 1.2.2 kernel and hoping we get tuned userspace blobs (which I'm assuming we won't, so we'll be stuck with the slow laggy cam).

This whole thread started off with the aim to port cam from stock, but that hit a dead end for some reason.
[Sony Cross-Device General] erikcas:
Uh.. He *is* trying to fix 1.3.3 branch with copy-paste a driver from another tag.

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] Olivier:
Yes, because it seems to be impossible to get the camera stack from stock working on AOSP.
[Sony Cross-Device General] m0d:
The best would be for sony to actual fulfil their commitment on providing working blobs, but two years and counting... nothing yet.

And you want him to work blindly on 1.3.3 branch and blobs, when devs might be giving up on branch already?

Has it been confirmed that issue is definately not 1.3.3 blobs provided by sony?

If there is no confirmation then there is no point, as only sony dev can find solution if blobs is the problem.

Then probably best solution would work on device that can actually be worked on, meaning definatley not a sony, for now at least.

[MENTION=359497]jerpelea[/MENTION]

Does any of the newer, x-series, have working camera on AOSP or all suffer from same issue?
[Sony Cross-Device General] erikcas:
No he can work on anything he wants. I highly doubt the approach as I have experience with that approach.

About the 1.3.3 branch, the idea that it is dead is your conclusion not mine. That there is being worked on a new branch does not change that. I think our friends at Google are already working on a nougat successor which does not imply they did abandon nougat.

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] m0d:
Yes, probably true.

But without confirmation of where the problem lies, then there is no point in doing anything.

Can you rule out blobs?

The open development project is supposed to be open.

So when users/testers report problem there should be some kind of feedback from sony devs.

So far in regards to some issues no one reports where the issue lies. And in most cases it is due to missing blobs or non-functioning blobs

Audio in-call: might be blobs missing - https://github.com/SuperBenevolent/aosp-vendor-qcom-extras

Camera half green - blobs or code in 1.3.3 branch???

Video playback issues, pink-green issue, bad blobs - https://github.com/SonyAosp/vendor_qcom/commit/9ea0dc645d84fa09bf7a5b1df6b9d38e12828c53
[Sony Cross-Device General] drakonizer:
Well, in the end he effectively needs camera blobs for 1.2.2, which if we're able to obtain, we can just use it with 1.2.2 itself right?

And once 3.18 becomes stable, don't you think 1.3.3 would be abandoned just like 1.2.2 is now? It works with Nougat, yes, but the issues are not being worked on (yes, it's open source and we can work on it ourselves if we want to, but you're the big devs ;) ). With all of jerpelea's time invested in the 3.18 kernel (I assume), it won't be long before it starts to boot.

---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------

As far as I know, the kitakami platform has a pretty good camera without the lag and the exposure issues.
[Sony Cross-Device General] m0d:
No it is not open source!

Many of the issues are due to wrong blobs provided - apparently they can not provide proper working adreno blobs

Why not switch to freedreno ? https://github.com/freedreno/kernel-msm/tree/xperiadev

Also audio incall issue might be a blobs problem: acdb/missing blobs

And, camera also could be a blobs problem, only sony dev can solve it if that is the case
[Sony Cross-Device General] erikcas:
You are guessing a lot here I think

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] erikcas:
Anyway about abandoned branches. I just checked the log of the 1.3.3 and I still see activities almost daily

As I like to stick to facts on this I would say it is under active development

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] m0d:
But still no working blobs

Also, for adreno no proper solution other than fix it yourself by using blobs from qcom-dev which are no longer updated since 28th june.

At least separate it like modem for ease by adding new repo qcom-adreno with actually working blobs.
[Sony Cross-Device General] drakonizer:
That is because the 3.18 kernel hasn't booted yet. Once that boots and works on some devices, 1.3.3 will be abandoned/worked on rarely just like 1.2.2

---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------

Can you please correct me if I'm wrong?
[Sony Cross-Device General] erikcas:
You are guessing again.

Me saying you are wrong or not would be guessing.

Verstuurd vanaf mijn D5503 met Tapatalk
[Sony Cross-Device General] davidteri91:
Quoting [MENTION=985241]erikcas[/MENTION]... 1.2.2 was abandoned due to loire platform... Qcom has added 8952 support on 1.3.3 branch.... So 1.3.3 will still be used for M and 3.18 for N..... Devs know about they are talking.....

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] m0d:
Also 1.2.2 had critical iommu bug

Right now both N and M use same 1.3.3 branch and blobs

So, if 3.18 has working camera wouldn't they switch to that for both M and N, as now they both use same branch ?

[MENTION=985241]erikcas[/MENTION]

https://github.com/sonyxperiadev/device-sony-common/commit/90f5dc3941322c4d60e74d8f613c3ad259e8919c
[Sony Cross-Device General] davidteri91:
Nope because M has not msm8996 Hals so 3.18 only for N

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
You realy believe that reverting back kernel camera hal from 1.2.2 kernel to the kernel 1.3.3 is impossible? Let explain that, I want to know how you know that even without comparing kernel camera hal 1.2.2 with 1.3.3.

For info to you, I copy paste things from 1.2.2 since there is not so big diferencie in kernel camera dependencies! Reverting whole camera breaks nothing to rest of the kernel! Instead of making debate with me let compare that thing byself, I no want debate with you. Dmesg says that i need to fix some events, no other errors in camera! About camera dtb, it must be revert since 1.2.2 kernel camera hal not uses things which 1.3.3 camera dtb have. Instead of debating with me you can help since soon or pretty soon you will find that 1.3.3 camera have status "can't fix" and soon you will be back to 1.2.2 as me.
[Sony Cross-Device General] munjeni:
Got camera 1.2.2 on 1.3.3 kernel finaly!! Patch is in a post above! We are finaly one step forward! \0/ Enjoy guys!
[Sony Cross-Device General] m0d:
You have list of files copied from 1.2.2 blobs?

You using latest blobs for 6.0: SW_binaries_for_Xperia_AOSP_M_v05ab ?

Steps to test:

Switch blobs

Switch to camera branch: aosp/LA.BF64.1.2.2_rb4.7

Patch kernel

?
[Sony Cross-Device General] munjeni:
Yes, but I have used display hal from LA.BR.1.3.6 rb1.6 (probably things will work without it, if not try with display hal provided by me) , you can get it from this thread. Also you must compile kernel inline and export headers to sony/common-headers/kernel-header by overwiriting that things (delete newly created files and folders, you need only patched headers)
[Sony Cross-Device General] rcstar6696:
can you post the headers here ?? i think there are a lot of people who doesn't know how to get headers from kernel

including me and alist which blobs are needed from 1.2.2
[Sony Cross-Device General] jerpelea:
camera works fine on all other platforms
[Sony Cross-Device General] jerpelea:
have you tried to joyn our aosp hangout group?

from how it looks kernel misses the proper vfe config and since 8976 uses similar vfe40 and it works ......
[Sony Cross-Device General] munjeni:
Use this script

#!/bin/bash

apt-get install lzop

CURPATH=`pwd`

mkdir -p $CURPATH/out/target/product/amami/obj/KERNEL_OBJ

cd $CURPATH/kernel/sony/msm

make ARCH=arm CROSS_COMPILE=./prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- O=$CURPATH/out/target/product/amami/obj/KERNEL_OBJ aosp_rhine_amami_defconfig

make ARCH=arm CROSS_COMPILE=./prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- O=$CURPATH/out/target/product/amami/obj/KERNEL_OBJ

make ARCH=arm CROSS_COMPILE=./prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- O=$CURPATH/out/target/product/amami/obj/KERNEL_OBJ headers_install

cp -fr $CURPATH/out/target/product/amami/obj/KERNEL_OBJ/usr/include/* $CURPATH/device/sony/common-headers/kernel-headers/

cd $CURPATH/device/sony/common-headers/kernel-headers
for TT in `git ls-files --others --exclude-standard`; do rm -rf $TT; done
for TT in `git status | grep deleted | awk '{print $2}'`; do git checkout -- $TT; done

cd $CURPATH

exit 0

put it on top of the android tree and run, don't forget to change "amami" to your device name!
[Sony Cross-Device General] munjeni:
Hey, I have no that problems on display hal which I am using, display, video and things working realy good, only youtube when I rotate screen to horizontal after 5 secconds black display happens until I rotate to vertical! So probably display hal isue!? From that reason I switched to 1.3.3 kernel with 1.2.2 camera since I was unsure if youtube bug is 1.2.2 related so switched to 1.3.3 kernel, but the same problem happens on youtube, definitely not kernel related! I'm using that display hal on booth kernel branches and problem is the same with youtube
[Sony Cross-Device General] rcstar6696:
can you show us a diff which blobs did you change ?
[Sony Cross-Device General] m0d:
The following adreno blobs fixes the issue mentioned, maybe it will work for the other problem: https://developer.qualcomm.com/download/adrenosdk/user-mode-driver-binaries-adreno.zip

Yes, that would be great.

Even better would be to push into github your changes on top of clean repos for the following:

https://github.com/SonyAosp/platform_vendor_qcom (or https://github.com/SuperBenevolent/aosp-vendor-qcom-prebuilt)

https://github.com/sonyxperiadev/kernel

https://github.com/sonyxperiadev/device-sony-common-headers
[Sony Cross-Device General] rcstar6696:
i only need to know which blobs are used all other things are on github and ready for building

btw if you not build amami you need to change some dtsi files
[Sony Cross-Device General] munjeni:
You have already all needs and details in our thread, just follow them, I cant mess with git just for providing you diferencie, sorry do it yourself, I can only pack things into an archive so you can use them to overwrite your local tree and analyse diferencie byself, I have no free time for messing with git, I need free time to use for start working on camera android hal and remaining things. Im using SW_binaries_for_Xperia_AOSP_M_v05ab, added modem and mba firmware from cm11 rom, added libthermal and libthermaiioctl from stock rom, the rest untouched
[Sony Cross-Device General] nozz93:
Regarding the black screen error: I'm not sure if this is related but this happens on CM12.1 if you don't disable HW overlays in the developer settings. Might be worth a shot?

Anyway, thanks for your work!
[Sony Cross-Device General] Luncer:
Thanks for your hard work bro

Can we expect a test build for Honami and Amami in these future days?:o
[Sony Cross-Device General] munjeni:
For amami yes, tommorow if test gets succed on my phone
[Sony Cross-Device General] Luncer:
How about honami?

I think [MENTION=3403060]Darkoni[/MENTION]zer can if he has free time
[Sony Cross-Device General] munjeni:
yes it fixes a isue! Thanks for info!
[Sony Cross-Device General] m0d:
There is a group?

kernel headers should not be needed:

-include device/sony/common-headers/KernelHeaders.mk

I believe if you delete common-headers it should use inline kernel headers as per commit and changes to kernel makefile: https://github.com/sonyxperiadev/device-sony-common/commit/c83fc2fcfa1b44be520cc8eb2f429e8cc683a55b
[Sony Cross-Device General] nozz93:
Note that this is not a permanent setting, it needs to be set after every reboot. I'm not sure what causes this problem in the first place but it's pretty annoying.
[Sony Cross-Device General] rcstar6696:
hey does your device boot up every time ? mine often stuck on bootlogo but sometimes it starts
[Sony Cross-Device General] munjeni:
Never had any problem with boot, and also device never rebooted with unknown reason! Prety stable :)
[Sony Cross-Device General] munjeni:
Yes thats strange, when I get time for it I will look into source code to see where it stores property... anyway disabling "disable hw overlays" fixes all videos problems, I must say display and videos is smooth like a butter.
[Sony Cross-Device General] Wyzco:
When you select disable Overlay and restart the cell, do you have to re-select disable overlay once again?
[Sony Cross-Device General] munjeni:
Yes thats reset on reboot, anyway its not a bug! Its by default non-permanent, but I have done a hack for it

diff --git a/src/com/android/settings/DevelopmentSettings.java b/src/com/android/settings/DevelopmentSettings.java
index dbcb277..e4f9b72 100644
--- a/src/com/android/settings/DevelopmentSettings.java
+++ b/src/com/android/settings/DevelopmentSettings.java
@@ -1133,7 +1133,8 @@ public class DevelopmentSettings extends RestrictedSettingsFragment
updateSwitchPreference(mShowScreenUpdates, showUpdates != 0);
@SuppressWarnings("unused")
int showBackground = reply.readInt();
- int disableOverlays = reply.readInt();
+ //int disableOverlays = reply.readInt();
+ int disableOverlays = SystemProperties.get("persist.disable_overlays").equals("1") ? 1 : reply.readInt();
updateSwitchPreference(mDisableOverlays, disableOverlays != 0);
reply.recycle();

using that patch you need to add entry to build.prop:

persist.disable_overlays=1
[Sony Cross-Device General] davidteri91:
Seems a dev fixed cam in 1.3.3

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] erikcas:
https://github.com/sonyxperiadev/kernel/pull/935

what will be the road from here?
[Sony Cross-Device General] davidteri91:
now we can get a heineken ;)
[Sony Cross-Device General] munjeni:
Cam not fixed? If I not forgot I saw in diff some shifts few days ago, something like

1 + (blabla >> wm) & 0x1 but on newer isp there is no shift for example something like

1 + blabla & 0x1

you can look into my 1.2.2 patch for 1.3.3 kernel for complete diferencie between old 1.2.2 and new 1.3.3 kernel hal, I'm sorry I can't help i realy no want to back to that mess, spent allready 15 days for nothing. How we can be sure that blobs have no the similar mess?
[Sony Cross-Device General] davidteri91:
camera was fixed .... real fix for 1.3.3 kernel made by [MENTION=985241]erikcas[/MENTION]
[Sony Cross-Device General] munjeni:
Realy? Great news!!! How its working in comparation to old camera?
[Sony Cross-Device General] erikcas:
well, I flashed Z1C 15 hours ago first time after being almost 3 months on stock. No offense, but the "cameramess + build.prop and scriptworkaround" you created was a nice trigger for me. So it took me 15 hrs (minus 6 sleep and 6 working hours) to find the real issue in the 1.3.3 camera driver. Ofc with loads of help of fellow devs in the hangout group you could not find. Maybe you should join it after all
[Sony Cross-Device General] davidteri91:
as [MENTION=985241]erikcas[/MENTION] said .... on hangouts there are more brains to work in every single problem .... we talked about vfe today and erik fixes it ......
[Sony Cross-Device General] munjeni:
I used some things from old isp but didn't managed to get camera, was pretty sure that things is blobs related, now you fixed it and I can't believe how stupid part of code caused break in camera... Thats great realy!
[Sony Cross-Device General] m0d:
I guess we have munjeni to thank after all, his crazy quest inspired you,

Well, that is good news. Great work.
[Sony Cross-Device General] davidteri91:
Stupid part you said.... When camera was not working at all was due to typo on CPP from cpp_0 to cpp

Inviato dal mio F8131 utilizzando Tapatalk
[Sony Cross-Device General] munjeni:
Haha how stupid things can go wrong thats unbelievable
[Sony Cross-Device General] munjeni:
Here is Amami test build which I done 2 hours ago with using 1.2.2 camera and kernel 1.3.3 :( if smebody need to try :o now deprecated :D

In my case since it is latest aosp I must say i am supprised how stable aosp is, there is a few bugs but in general for daily usage can be used without a big problem. used it from yesterday and it was in my pocket almost 24 h, null reboots, mesaging (not tried calling) worked like a charm, battery is somehow also with good usage... Please share your opinion about rom! Jerpelea and guys done realy good and very hard job on unified things, thank you guys!
[Sony Cross-Device General] ahmedzetm:
can make one for z1 honmai
[Sony Cross-Device General] drakonizer:
Quick question, does deep sleep work for you? In honami it doesn't seem to be working at all, which is causing a noticeable battery drain.

And about the charging issue, I see a lot of "healthd: unknown power supply" in logs. That can't be it, can it?
[Sony Cross-Device General] broky:
for sure i ll try it and test it for long,cause i m watching the evolution on this almost every ten minutes:D,(unless it carries the other side hearing echo bug),that will force me to go back in stock, so my phone will work as it should..

anyway keep up the good work guys,you re all great:good:

and i wish you manage bring to our phones new life,everyone puts his bricks in the house:):)

peace,love and co-operation:)