yashsingh1/xdaforums huggingface dataset:
[Sony Cross-Device General] munjeni:
Yes thats what I talked 7 days ago about "is split 1" which we found in kernel mdss headers. But what mean dual vfe?? Is that mean 2x vfe0 + 2x vfe1 ??

10-15 21:05:40.152 541 541 E mm-camera-isp2: isp_resource_query_mod:145 num_isp_preallocate 1 num_session_opened 1 [COLOR="Red"]dual_vfe_enabled 0[/COLOR]

As I found we have YUV + mono camera?

Edit:

Curently I am playing with display hal from branch release-2.0 + nexus 5 latest adreno (not tried but will try), have problem with:

#include <linux/msm_mdp_ext.h>
#include <linux/mdss_rotator.h>

need to find kernel which allready have implemented these curently missing headers. I am using camera from LA.BR.1.3.6_rb1.3 (using it for more than 2 veek, it have things for mono camera and also have native handles in comparation to 1.3.3 which have something diferent, its working) but there is a new branch booth kernel and camera on LA.BR.1.3.6_rb1.6, a ton of work need to be investigated and tried :) I'm paused now on stock kernel and things, thats realy hard work without group development :(
[Sony Cross-Device General] tomascus:
I will never understand why you look at display drivers when is_split is reference like 6 times in camera drivers.... https://github.com/sonyxperiadev/ke...dia/platform/msm/camera_v2/isp/msm_isp.h#L708

I thought dual vfe was just vfe0 and vfe1
[Sony Cross-Device General] muzadull:
Maybe we should look at Sony z3 Nougat preview kernel source?
[Sony Cross-Device General] tomascus:
We're working with the 3.10 kernel, completely different implementation here
[Sony Cross-Device General] munjeni:
I told about display hal things... I found very smooth and stable video things, screen off/on, etc using LA.BR.1.3.6_rb1.3, so probably (in most case) LA.BR.1.3.6_rb1.6 will be more clean! New camera from LA.BR.1.3.6_rb1.6 is better than LA.BR.1.3.6_rb1.3 (which I'm using for 2 weeks) since android now have no java crash related to NULL blabla, for example see one part of detail in diff (there is a ton of similar details!):

char* QCamera2HardwareInterface::getParameters()
{
char* strParams = NULL;
- String8 str;
+ String8 str("");

int cur_width, cur_height;
pthread_mutex_lock(&m_parm_lock);
@@ -5156,7 +5162,7 @@ char* QCamera2HardwareInterface::getParameters()
mParameters.m_reprocScaleParam.getPicSizeFromAPK(scale_width,scale_height);
mParameters.getPictureSize(&cur_width, &cur_height);

- String8 pic_size;
+ String8 pic_size("");
char buffer[32];
snprintf(buffer, sizeof(buffer), "%dx%d", scale_width, scale_height);
pic_size.append(buffer);
@@ -5174,7 +5180,7 @@ char* QCamera2HardwareInterface::getParameters()
if(mParameters.m_reprocScaleParam.isScaleEnabled() &&
mParameters.m_reprocScaleParam.isUnderScaling()){
//need set back picture size
- String8 pic_size;
+ String8 pic_size("");

Manegaed to build display hal release-2.0 and new camera, lets see status.
[Sony Cross-Device General] munjeni:
Forgot to say... last time when I conpared camera aosp app with one on LA.BR.1.3.6_rb1.3 it was excatly the same, identic! So definitely right match for our camera is hal from codeaurora, in my case I will use camera hal from LA.BR.1.3.6_rb1.6
[Sony Cross-Device General] tomascus:
And you believe this will totally be compatable with our closed source blobs for what reason?
[Sony Cross-Device General] munjeni:
I am prety sure since LA.BR.1.3.6_rb1.3 worked
[Sony Cross-Device General] munjeni:
http://pastebin.com/6KeZ7RqD

10-16 19:26:02.623 524 4474 E mm-camera-intf: mm_camera_event_notify: Camera Event DAEMON DIED received
10-16 19:26:02.623 524 2920 E mm-camera-intf: mm_camera_query_capability: cannot get camera capabilities, rc = -1
10-16 19:26:02.623 524 2920 E QCamera2HWI: static int qcamera::QCamera2HardwareInterface::initCapabilities(uint32_t, mm_camera_vtbl_t*): failed to query capability
10-16 19:26:02.624 524 2920 E QCamera2HWI: initCapabilities failed.

Patch from working rb 1.3 to not working rb 1.6 -> http://pastebin.com/2zvh1NsG

Ideas? What might cause camera to fail to get capability? Maybe because SIGSEGV happened? Its worked on rb 1.3

Edit:

Seems mutex changes?

Edit:

This probably cause sigsegv

10-16 20:49:50.650 6382 6382 E mm-camera: module_sensor_query_mod:5277fatal init config done fail 0

10-16 20:49:50.674 6382 6682 D mm-camera: mct: Cam 0: FPS range selection complete. Publishing 3 ranges.
10-16 20:49:50.675 6382 6682 F libc : Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb1a89028 in tid 6682 (CAM_MctServ)
10-16 20:49:50.675 433 433 W : debuggerd: handling request: [COLOR="Red"]pid=6382[/COLOR] uid=1006 gid=1006 tid=6682
[Sony Cross-Device General] munjeni:
This is what I talked about memory for camera

10-16 20:49:50.438 6631 6631 D CAM_MemoryManagerImpl: Max native memory: 358 MB

is that possible?
[Sony Cross-Device General] Hazou:
nah, don't think so. Have a look at the kernel log. Maybe it gives some more info
[Sony Cross-Device General] munjeni:
Fixed new hal! Camera is no more on 3 parts of the screen, its now on 2 parts! :) First part (half is green) but seccond is normal camera preview! Hope I get some more good news tommorow :)

Edit:

Hal 3 is allso working but no preview! And somehow it opens camera more faster than on hal1
[Sony Cross-Device General] p@to:
[emoji122] [emoji122] [emoji122] [emoji106] [emoji106] [emoji106]

Awesome!!!!
[Sony Cross-Device General] rcstar6696:
Wait do you use 3.10 or 3.4 base?

We were at this step too but it was due uncalbirated blobs for the actual hal
[Sony Cross-Device General] davidteri91:
also AOSP has cam on this state but is still under development

http://imgbox.com/CqueLDRV
[Sony Cross-Device General] munjeni:
I'm on 3.10. What I found, we need to use dual camera, what mean dual camera? Dual camera mean vfe0 + vfe1, we curently have only one vfe working! Problem which we need to resolve is: blobs detects things as a single camera (which you can see in logcat as a dual camera = 0 which mean dual camera = disabled which mean single vfe only), if you enable property: setrpop persist.camera.dual.camera 1 camera working on 2 half screens, one half is green seccond one is camera preview, but stil camera blobs detects things as a dualcamera = 0. No problem at all if there is no another problem caled "is_split = 0", is_split 0 can be seen in logcat too! I think we need to somehow enable is_split (more info on mdss kernel header which we mentioned earlier)... Curenly I'm trying to patch libmmcamera_isp_scaler_encoder40.so in func scaler40_config there is is_split detection, I need to force enable is_split flag and try :) If you have better idea let me know! Probably we can ask jerpelea to make us new libmmcamera_isp_scaler_encoder40.so with force enabled is_split just for test, or at least fix blobs things related to dualcamera detection which ignores hal configuration persist.camera.dual.camera 1
[Sony Cross-Device General] davidteri91:
munjeni tablets msm8974 are single vfe and they actually are not working
[Sony Cross-Device General] rcstar6696:
David tablets will be fixed in v5 blobs
[Sony Cross-Device General] jerpelea:
I have fixed the tablets which have 1 vfe and now the sensor starts (the fix will come in libs V5)

the problem is that it does not matter if we have 1 or 2 vfe we will have only half screen

during preview you have a full spam indicating what is wrong on all 8974 devices

01-01 00:45:57.202 356 3643 E mm-camera: iface_util_buf_divert_notify: HW error! frame id reverse!! sessid 1, hw streamid 10002

01-01 00:45:57.202 356 3643 E mm-camera: iface_util_buf_divert_notify: curr: frame 507, sec 78 usec 409722

01-01 00:45:57.202 356 3643 E mm-camera: iface_util_buf_divert_notify: prev: frame 507, sec 78 usec 396494

Regards

Alin
[Sony Cross-Device General] munjeni:
Is_split is used from that reason! See https://github.com/sonyxperiadev/ke...3.3_rb2.14/include/uapi/linux/msm_mdp.h#L1143

1. source split is enabled: l_roi = roi and r_roi = 0

Curently we have 2. (and i think 2.1 part of comment)!

2.2 is the same like 1. (l_roi = roi and r_roi = 0) which mean it will work on vfe0 only in not split thing! Thats what I curently want to do.
[Sony Cross-Device General] jerpelea:
msm_mdp as the name says!!!
[Sony Cross-Device General] davidteri91:
as I know that's display header .....
[Sony Cross-Device General] munjeni:
Jerpelea, camera starts working corectly when property persist.camera.dual.camera is 1 but still on half screen! You have idea what might cause that? Is not our camera mono camera???
[Sony Cross-Device General] davidteri91:
when cameraHAL refer to dualcamera is not dual HW camera ? like new targets even on kernel you can see commits saying dual vfe / dual camera
[Sony Cross-Device General] munjeni:
Alin no! I have fixed that in cameraservice (if I am not wrong), I have nothing in logcat related to that, camera is stil on half screen (on 2 halfs in case dual camera property enabled || 3 halfs if not)

Edit:

You are right! Found it now:

mm-camera: iface_util_buf_divert_notify: HW error! frame id reverse!! sessid 1, hw streamid 10002

going to check if I can get it when dual camera property is set to 1

Edit:

no hw error when dualcam property is set to 1 !!!
[Sony Cross-Device General] munjeni:
Alin do you can make libmmcamera_isp_scaler_encoder40.so with is_split forced to 1 , for test, I want to test something, if possible?
[Sony Cross-Device General] davidteri91:
can you upload a dmesg?
[Sony Cross-Device General] munjeni:
In next hour for sure! Going to install aosp now
[Sony Cross-Device General] munjeni:
dmesg (property dualcam 0) https://paste.ubuntu.com/23343957/

dmesg (property dualcam 1) https://paste.ubuntu.com/23343961/

logcat (property dualcam 0) https://paste.ubuntu.com/23343964/

logcat (property dualcam 1) https://paste.ubuntu.com/23343971/

Edit:

dmesg says no error in kernel camera

logcat says sometimes SIGSEGV on cameraservice (when dualcam is 1) but not all times, its related to fps things, I can see nothing more strange about camera
[Sony Cross-Device General] munjeni:
Max native mem from logcat 358M but on dmesg:

cma: CMA: reserved 100 MiB at 0x52800000 for camera_mem
[Sony Cross-Device General] munjeni:
Here is stable camera and displays hals (LA.BR.1.3.6_rb1.6) which I modified for msm8974 (curently using it). Also I'm using nexus 5 latest adreno blobs with it. Display things fly!!! Almost complete nougat. Some few things need to be fixed before rom be ready for daily usage:

1.camera (urgent)

2. mhl (it connects to tv but no picture, sometimes can't see tv)

3. leds fixed (just rename all amami_HALS.so to msm8974_HALS.so)

4. charging its working

5. auto backlight

6. fm (sometimes can't start tuning), videos, youtube...things, working perfectly good, screen off/on is smooth, things related to video flys!

7. if i forgot something

In general nougat is ok, can be used without big problem for daily usage!
[Sony Cross-Device General] drakonizer:
About charging, is the charging indicator broken? And when you're charging from AC through the micro USB port, does Android detect it as an AC input or does it say charging through USB? (In battery settings)

The last time I tried Nougat, charging indicator was broken, charging speeds were reduced, AC input through micro USB was detected as charging through USB. Has this changed?
[Sony Cross-Device General] munjeni:
Led charging indicator working, but I can't see battery stats in *#*#4636#*#* can't tell you about charging source indicator , in logcat there is also something about "BatteryNotifier: batterystats service unavailable", in general it charging, I am satisfied :)

1. BatteryStatsService: Timeout reading modem stats (thats first line about battery)

2. BatteryNotifier: batterystats service unavailable!

3. BatteryStatsService: power: Missing API

4. BatteryStatsService: no controller energy info supplied
[Sony Cross-Device General] munjeni:
Camera hal3 takes picture :eek: (stil the same half screen on picture) but no preview http://pastebin.com/dmGeCHd7 , camera opens very fastly :eek:
[Sony Cross-Device General] mkdmc:
Right.

(I had tested 1 month ago)
[Sony Cross-Device General] jerpelea:
self explanatory

https://github.com/sonyxperiadev/ca...1.3.3_rb2.14/QCamera2/QCamera2Factory.cpp#L84
[Sony Cross-Device General] jerpelea:
it will crash the camera in the worst mode possible
[Sony Cross-Device General] munjeni:
Ok thanks, as per camera sensor capability:

module_sensor_init:6274
Sensor SDK capabilities:

Bayer,
YUV and mono sensor,
short and long exposure-gain control,
in-sensor VHDR with AE stats,
PDAF with Phase difference or PD Pixel stats,
HAL3,
support common apis for gain calculation,
filling integration time,
fll and gain,
and PDAF HW stats parsing

so we can't use dual camera since we have mono camera, right?

What about this:

10-18 16:23:12.448 538 538 E mm-camera-sensor: sensor_init_probe:492failed: to oribe eeprom bin sensors
[Sony Cross-Device General] jerpelea:
mono is BW

eeprom is not needed and can be ignored
[Sony Cross-Device General] jerpelea:
you dont have to rename the libs

it is enough to use the proper bootparameter
[Sony Cross-Device General] munjeni:
What mean BW? Since nobody have idea what cause camera bug and nobody with 100 percent sure have idea which part of camera thing (hal, blobs, app, kernel = 4 things) cause bug we have happy end with camera?
[Sony Cross-Device General] munjeni:
What mean BW? Since nobody have idea what cause camera bug and nobody with 100 percent sure have idea which part of camera thing (hal, blobs, app, kernel = 4 things) cause bug we have happy end with camera probably. Is there any way to take raw picture from kernel camera? Any native app for testing kernel hal?
[Sony Cross-Device General] Masterblop:
I think "black & white"
[Sony Cross-Device General] jerpelea:
reppace in the build guide

https://github.com/sonyxperiadev/kernel/tree/aosp/LA.BF64.1.2.2_rb4.7

https://github.com/sonyxperiadev/camera/tree/aosp/LA.BF64.1.2.2_rb4.7

https://github.com/sonyxperiadev/device-sony-common-headers/tree/aosp/LA.BF64.1.2.2_rb4.7

to get a functional device you need to

revert

https://github.com/sonyxperiadev/device-sony-common/commit/27d7d8d40d915c68240fe3a058e257ee01d6b91f

and to cherry-pick

https://github.com/sonyxperiadev/device-sony-common/commit/ca4f68477e40ed6737cfd53e502693e51343dd40

so that it matches the release

and download the matching blobs

http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-m-android-6-0/
[Sony Cross-Device General] drakonizer:
Can we get calibrated blobs for 1.2.2 if 1.3.3 is too hard to fix? I think the iommu issue will be easier to fix/live with compared to no/low quality camera.
[Sony Cross-Device General] munjeni:
Alin 1.2.2 branch doesn't boot on nougat, thats a first thing, new selinux and some more things need to be implemented in order to boot on nougat, ok we have managed to boot it! Next thing, I have played 3 times getting 1.2.2 camera to work on nougat, its not working! Even camera app is missing on nougat using that hal and blobs! I am getting erros for something blobs side (if I not forgot it was mct), so no cam on N. We would be already on 1.2.2 if that was possible, not possible since errors comes from blobs and we can do nothing on closed source blobs! Our last hope is 1.3.3
[Sony Cross-Device General] p@to:
Sad

Damn it
[Sony Cross-Device General] jerpelea:
can i have a log of N with 1.2.2?

i fear that you have not switched the camera HAL to the proper branch

can you try the same on the latest M tag

regards
[Sony Cross-Device General] munjeni:
Have no log I'm on stock rom curently but is this enought ? ...from folder camera/.git/HEAD 5424150db09918cb15b548632fade406e1c1b93e

blobs used with it SW_binaries_for_Xperia_AOSP_M_v05a.zip

kernel 1.2.2 (previously patched since without patch it can't boot on nougat), patch is in attachment

Can't try on M since I'm on aosp 7.0 ...
[Sony Cross-Device General] munjeni:
Anybody... What is a status of the kernel 1.3.3 and camera hal 1.3.3 with blobs 1.3.3 on android M? Anybody tried?
[Sony Cross-Device General] SuperLamic:
It's the same as on N. Cam is also half green.
[Sony Cross-Device General] munjeni:
Ok, so this confirm that thing is not android side. One thing eliminated, 3 remains, kernel, blobs and hal. :)
[Sony Cross-Device General] jerpelea:
you have a nice time marking error on frames :)
[Sony Cross-Device General] munjeni:
I will continue marking errors thats not problem, problem for me is I dont have idea what mean BW. Even I don't know if we have dual camera or not, even don't understand what mean dual camera. Vfe0 & vfe1 mean dual camera? Do our cam need to have booth vfes working?
[Sony Cross-Device General] aquaboy11:
[MENTION=4120742]munjeni[/MENTION] how did you get the LA.BR.1.3.6_rb1.6 kernel working?
[Sony Cross-Device General] munjeni:
Kernel? I have used only camera hal and display hal from that branch!
[Sony Cross-Device General] aquaboy11:
Alright. I am working on getting that kernel branch to boot now and see how it works. By the way, does you simcard get detected?

Edit: kernel didn't display anything, when booting the screen was black and frozen. I don't think I have enough experience to make it work. I will, however, try to get some of the drivers working on LA.BR.1.3.3_rb2.14.
[Sony Cross-Device General] munjeni:
Yes sim is working.. you need modem and mba firmware to get sim working
[Sony Cross-Device General] p@to:
Hi!

I would like to try your rom!

It's possible?

Thanks for all!!![emoji106]
[Sony Cross-Device General] tomascus:
Can we keep this discussion strictly about camera related matters? [MENTION=4120742]munjeni[/MENTION], I've tried enabling dual camera property as well and did notice it kind of fixed the preview on the non green side of the screen.

Furthermore, in logcat it shows that it's using "single vfe mode" just like in 1.2.2 instead of "dual vfe mode".
[Sony Cross-Device General] munjeni:
Yes I told that! Blobs/kernel whatewer, ignores dualcam property from android, I told that too! I stil not understand one thing... waiting jerpelea to explain about do we have single or dual cam on z1 and z1c and what mean that dual cam... do we need booth vfe working... etc
[Sony Cross-Device General] tomascus:
I believe we have single cam, in 1.2.2 camera HAL dual camera doesn't even appear to be supported yet camera works fine.

Could dual cam refer to actual physical 2 back cameras like some phones have..? https://www.qualcomm.com/news/snapd...meras-capture-photos-first-adjust-focus-later
[Sony Cross-Device General] munjeni:
Lets see what Alin says about that.

Edit:

I have found in kernel camera isp a lot of new things related to axis and dualcam things in comparation to 1.2.2, probably we are messed up with dualcam in case we have "singlecam"

Edit:

I'm curently done N build with 1.2.2 things mentioned by Alain, lets see if camera working. I will provide logcat and dmesg

Edit:

In the same time I have merged usb, media and camera from kernel LA.BR.1.3.6_rb1.6, will try
[Sony Cross-Device General] tomascus:
Well camera has worked without dual cam on 1.2.2 so I don't believe we need it.
[Sony Cross-Device General] munjeni:
Got camera on Nougat using 1.2.2 !!! \0/ \0/
[Sony Cross-Device General] tomascus:
Yeah okay but we are working on fixing 1.3.3!
[Sony Cross-Device General] munjeni:
Yes ofcourse!
[Sony Cross-Device General] ahmedzetm:
PLz bro make beta Rom for Hnomai z1
[Sony Cross-Device General] munjeni:
First thing which I noticed on 1.3.3 camera is requested preview size 1280x720 and requested picture size is 160x120

but see how it is on 1.2.2

01-01 07:28:17.814 451 2169 I QCameraParameters: Requested preview size 640 x 480

01-01 07:28:17.815 451 2169 I QCameraParameters: Requested picture size 5248 x 3936

I will analyse log tommorow, going to build now with 1.3.3 modified kernel things...
[Sony Cross-Device General] niaboc79:
I think that the dual camera means the ability to use front and back camera in the same time. This have been introduced with the Z2. If it's that, there's some related things inside the kernel too.

Envoyé de mon D6503 en utilisant Tapatalk
[Sony Cross-Device General] munjeni:
logcat, dmesg and patch
[Sony Cross-Device General] aquaboy11:
Could you try this kernel with your patch?
[Sony Cross-Device General] munjeni:
Whats that kernel?
[Sony Cross-Device General] aquaboy11:
It is AOSP with camera kernel drivers from LA.BR.1.3.6_rb1.6. I tried it along with the files from "make Camera2" in AOSP source tree, but it can't connect to camera.

Edit: the initialization of pincrtl seems to be failing. I've included the dmesg and logcat (grepped camera, that's good right?)

[ 19.579375] msm_camera_pinctrl_init:1260 Getting pinctrl handle failed
[ 19.588785] msm_camera_power_up:1301 Initialization of pinctrl failed

Also, it can't find libthermalclient.so, so I guess I will have to build more than just Camera2.

10-21 01:02:52.250 446 446 E QCameraThermalAdapter: int qcamera::QCameraThermalAdapter::init(qcamera::QCameraThermalCallback*): dlopen failed with error dlopen failed: library "/vendor/lib/libthermalclient.so" not found
[Sony Cross-Device General] tomascus:
Those errors seem to both be normal, camera should still start up despite them. Looks like you have another issue somewhere. Why don't you guys stick with 1.3.3 branch that actually starts up?
[Sony Cross-Device General] munjeni:
Yes, pinctrl is not used and need to be ignored, Alin toold about that earlier.
[Sony Cross-Device General] munjeni:
Hi, that hal giving wrong booth picture size and preview size, for example it gives preview 1280x720 and picture 140x160 which is wrong. Yesterday I have updated camera driver from rb 1.6 and now camera can't start (giving SEGFAULT to something about FPS) but good thing it choses right preview & picture size! Probably bug lives in kernel hal?

Edit:

I'm now on aosp 7.1.0 r4

Edit:

I will enable all possible loging features in camera_v2 kernel hal, lets see what kernel says
[Sony Cross-Device General] munjeni:
10-21 01:02:12.105 446 3606 E QCamera2HWI: uint8_t qcamera::QCamera2HardwareInterface::getBufNumRequired(cam_stream_type_t): ***ERROR Case*** minUndequeCount(2) != hardcoded value(1)

Probably somebody hardcoded it to 1, you can check that in QCamera2HardwareInterface.cpp ?
[Sony Cross-Device General] aquaboy11:
I will check when 7.1.0_r4 gets done building.
[Sony Cross-Device General] tomascus:
https://github.com/sonyxperiadev/ca...3.3_rb2.14/QCamera2/HAL/QCamera2HWI.cpp#L2308
[Galaxy Note 4 Q&A, Help & Troubleshooting] uskuri18:
Hi,

I was charging my note 4 and suddenly my charger exploded. I continue to charge the phone but after it stopped charging. I bought a new charger but when I plug it, it shows me the charging animation, but its not charging. Its like its trying to be charged but cant take the power. Somehow, it charged to 10% but it didn't had any signs of charging. I think the problem is battery. The phone turns on then shuts down because of no battery.

Any ideas?
[Galaxy Note 4 Q&A, Help & Troubleshooting] ithehappy:
Jeez! How loud was that explosion, or how fierce? Really scary news. Anyway, always use a good power surge protector when charging phones and stuffs. Other than that, you already know, buy a new battery and see, or borrow one of friend's if you could.
[General Questions and Answers] achraf_tahir:
Hi everybody, I rooted my device then went back to stock (no root) now i can't use samsung my knox app, whenever i open the app it says "cannot be installed because unauthorized software has been installed on your device".

Can anybody help ?