Related
I searched for camera mods to allow for capturing of RAW data from the sensor on the Charge.
As far as I can tell, nobody has been successful in getting any Android phone to capture the RAW data.
Does anybody know if this is possible? I know others who would love to have the ability. I didn't really want to start a discussion of RAW vs JPEG compression, etc. I know the drawbacks and advantages of RAW.
I think that this would require camera firmware modifications as well as Camera APK modifications. My development knowledge is very limited, hence my name.
Does anybody know if this would require a reasonable about of effort or if its far beyond being worth the trouble?
It looks possible, and the code is in the API to do this, but it has yet to be done as far as I know. It looks to be an issue with the "RAW callback function" always returning NULL. If I have some time I will to look into it.
Do Not ask Questions in the Development thread if it is not Development it does not belong in here
Moving to General
My apologies and thanks.
Bumping this, seems like an interesting feature, considering it has API support.
bcpk said:
Bumping this, seems like an interesting feature, considering it has API support.
Click to expand...
Click to collapse
I would plus one this
Sent from my Xoom using XDA Premium App
I don't know if its prohibitively difficult to mod, but I couldn't find any other phone which has been developed to shoot RAW. Perhaps people just haven't shown much interest.
I would love this feature, but I figure most people shooting in RAW already have a "real" camera. I would expect a decent increase in photo quality though. I have 32 GB on my phone waiting to store some RAW data!
I just wish someone would mod the camera APK to use +2 sharpness, which would result in better quality photos. The camera app applies a bad blur/denoise filter on the lower sharpness settings which reduces the quality of the picture. Worse, the camera does not save that setting, so it needs to be set each time I use it.
BeefJerky9 said:
I just wish someone would mod the camera APK to use +2 sharpness, which would result in better quality photos. The camera app applies a bad blur/denoise filter on the lower sharpness settings which reduces the quality of the picture. Worse, the camera does not save that setting, so it needs to be set each time I use it.
Click to expand...
Click to collapse
You know u can modify the frame work for the camera, I've done it before, search xda. I doubt remember the form
Sent from my DROIDX using XDA Premium App
xdadevnube said:
I don't know if its prohibitively difficult to mod, but I couldn't find any other phone which has been developed to shoot RAW. Perhaps people just haven't shown much interest.
I would love this feature, but I figure most people shooting in RAW already have a "real" camera. I would expect a decent increase in photo quality though. I have 32 GB on my phone waiting to store some RAW data!
Click to expand...
Click to collapse
Shooting raw will make the color correction possible which will significantly boost the image quality to...a 70 dollars' compact camera you can find on ebay, BUT, the best camera is always the one that is with you, so I always support anyone who like to improve android phone's shooting ability.
---------- Post added at 02:38 AM ---------- Previous post was at 02:26 AM ----------
The real issue isn't allowing the camera to shoot raw because they can be done but the raw format will not be recognized by any raw processing software on the market. The possible way is to use DNG format which will significantly increase the difficulty of modification because it means the programmer will put in hours to create a brand new application to understand and compress the raw file to the DNG file...unlike Canon, android does not have an official raw format...so everything will need to start from zero. This process could easily take 20 very experienced engineers up to a year to complete, and the result might not be very ideal and will need another year to modify and improve...so we are looking at a potentially five million dollars project here - and it will better be turning in to profitable application - and if so it will have to be the best selling android app ever.
xdadevnube said:
I don't know if its prohibitively difficult to mod, but I couldn't find any other phone which has been developed to shoot RAW. Perhaps people just haven't shown much interest.
I would love this feature, but I figure most people shooting in RAW already have a "real" camera. I would expect a decent increase in photo quality though. I have 32 GB on my phone waiting to store some RAW data!
Click to expand...
Click to collapse
Yes, most (like myself) probably do but since I'm carrying around a high quality 8 megapixel camera in my pocket I'd like to be able to shoot in raw for those times that I don't have my DSLR with me. There is so much more that com be done to a RAW photograph, not to mention not having any data loss form it being converted to a jpeg. Looking forward to seeing if anyone can make this possible.
desmalta said:
Yes, most (like myself) probably do but since I'm carrying around a high quality 8 megapixel camera in my pocket I'd like to be able to shoot in raw for those times that I don't have my DSLR with me. There is so much more that com be done to a RAW photograph, not to mention not having any data loss form it being converted to a jpeg. Looking forward to seeing if anyone can make this possible.
Click to expand...
Click to collapse
Just a reminder....this is a cell phone, not a camera!
buhohitr said:
Just a reminder....this is a cell phone, not a camera!
Click to expand...
Click to collapse
Just a reminder, anything is possible in the world of android!
Sent from my SCH-I510 using XDA App
desmalta said:
Yes, most (like myself) probably do but since I'm carrying around a high quality 8 megapixel camera in my pocket I'd like to be able to shoot in raw for those times that I don't have my DSLR with me. There is so much more that com be done to a RAW photograph, not to mention not having any data loss form it being converted to a jpeg. Looking forward to seeing if anyone can make this possible.
Click to expand...
Click to collapse
RAW does not equal improved quality if the camera is not capturing more image information prior to compressing to JPG. You're still working with a tiny fixed lens and dense, compact sensor with tiny photo sites. This is limiting the amount and quality of light. Shooting RAW will not change this. JPG compression is not a limiting factor for image quality. You won't be able to resolve significantly finer detail or shoot in lower light settings just because you're shooting RAW. Open a JPG as RAW with Photoshop, it'll provide a similar experience.
You'll end up with similar photo quality, a bit more flexibility in PP, and huge lag while the camera tries to handle transfering and saving the huge photo file 10x larger than what it was designed to handle.
These are the only mobile phone sensors I've seen that would support or justify shooting in RAW.
Another story on them: http://www.engadget.com/2011/04/14/omnivisions-new-12mp-cmos-sensor-shoots-raw-pics-and-1080-60p-v/
In other words, RAW will be here eventually. When it is, it'll be an improvement. To try and force it (if it were even possible) with the sensor and hardware limitations in the DC is pointless.
charlie_c said:
RAW does not equal improved quality if the camera is not capturing more image information prior to compressing to JPG.
Click to expand...
Click to collapse
true, but shooting raw does preserve more of the image, because its the raw/real image that sensors seems is not a jpg processed image the way camera applications decided the scene should look like.
basically would would be taking your camera off the auto mode.
with raw you would have greated control over white balance, shadows, highlights etc...
There is a question about how many bits of image data you got on mobile sensor. On DSLR there is 12 or 14 bits information that is compressed to 8bit JPG information - that's why there is plenty more information about the image in RAW format. If CMOS in your mobile phone deliver just strait 8bit - your RAW will not have much more data.
As I don't have slightest idea how many bits of data is served by mobile camera sensor I can't say if there is a reason for RAW.
i found this
http://stackoverflow.com/questions/14777953/how-to-capture-raw-image-from-android-camera
i am really looking forward for a raw file from android camera this will be a huge move forward to the mobile world and the abilities of android
and since its supported in the api means google wants it to happen
Edit:
Create this dir /data/misc/camera/RaW_PiCtUrEs case sensitive btw
Assuming the capture mode used is high-quality and not high-quality-zsl it should produce a raw image everytime you capture a jpeg image
Click to expand...
Click to collapse
try this maybe it will work i found it here : http://forum.xda-developers.com/showthread.php?t=1977654&nocache=1
Hello.
First of all, my compliments to everone that makes great things like custom roms, mods, and so.
I'd like to know if is there a way to mod/improve/change the camera app, so the shutter speed can be set.
Thanks.
Hello again. It seems this thread gained some interest, but no one could give an answer. What I asked was if is there any way to hack, develop, activate improved settings for htc chacha camera.
Videos are saved in 3gp format. Is there any way to make camera app to save them as mp4?
Pictures get blurry if the subject moves quickly, or you are not steady when shooting. Is there any way to set the shutter speed?
I don't know if the camera app can be disassembled or something, and hacked into make that things.
Maybe the camera app can be ported from another model that uses the same camera model, and can do that.
I asked HTC about this, and they answered "latest 2.3.5 version has many improvements", but none about the camera...
The camera is way better than Wildfire, which my wife owns, but I think it can be even better if the camera app is up to it.
Thanks for reading.
The big question revolving around this issue is if the cameras themselves are the same between the phones. It's not only the camera.apk that's connecting them, it's the hardware as well. Yes, there could be a possibility that the cameras are the same, between ChaCha and Wildfire (for example), but at the same time the proc or image sensor might be of a newer generation. Unfortunately I have no hardware specs on this, if anyone knows it would be nice to know.
Question: Do you know of any phone that has advanced settings inside the Camera.apk that allows you to set shutter speed? Would be interesting to compare them a bit.
In the camera.parameters public class there is a setting called scene_mode_sports that seems to be the only way to set a faster shutter speed.
I can't see it in my HTC Chacha/Status, and even lgcamera hasn't that option in the menu.
There is a profile.xml file that sets the limitations of the camera, but it seems people hack it to allow the camera to record movies in higher resolutions, because many times the limitations are imposed by the manufacturer and not the hardware.
Also, hacking the firmware and/or the drivers of a camera would allow to gain the full features of it.
This reminds me of people that upgraded the Nokia N900 to allow it to record movies in 720p, just by replacing binary files in the phone.
Is there an app that tells you what exactly hardware your phone has, and such drivers or modules it uses?
Thanks all.
Hello all.
I'm reviving this with some news. The camera module the ChaCha uses is a Samsung s5k4e1gx (http://www.samsung.com/global/busin...t/cmos-imaging/detail?productId=5622&iaId=220), the same found in several other HTC models: HTC Desire Z, HTC Mini and others.
It seems that in the Desire Z this camera is able to record 720p video.
I think this is determined by the firmware loaded for the camera, and the app itself.
I'd like to know if it's possible to port change the original ChaCha camera related modules and firmware from the Desire Z ones, so the camera can get taht 720p video shooting.
Also, I'm searching for a way to disable the auto light metering so a manual can be set. There are many 'better camera' apps in the market but they all seem to improve the original camera app itself, instead of getting the most of the actual camera sensor.
Thanks all.
This first post from me is going to be short. I welcome additional thoughts, of course. Sorry if this isn't the best place to drop this, but it's not a question and it's not anything in development!
First, an observation: the problem with 720p in CM10 is not bright light, it's the camera's ability to adapt to bright light from low light. In other words, the problem seems to be related to the light sensor. Although this is not completely new, what I noticed from playing around with LGCamera is that if I turn UP the video bitrate, the flickering is not as sever. The flickering will stop and stabilize when filming in consistent light. Any change in light quality will produce more sticking. This makes sense since 720p requires finer adjustments to light and dark than 420p. The other part of the equation is the h264 encoder. I'm guessing that certain values in the light sensor need to match up with the h264 encoder...
Second, I was playing around with these settings today: http://forum.xda-developers.com/showpost.php?p=17791551&postcount=20 I haven't had enough time to verify what makes a difference and what doesn't. I believe that some settings have helped a bit. Also, I felt that changing the ISO to 800 in camera and then switching to video improved the video, but that could be totally imagined! Essentially, what we need is ISO800 for the vidcam... I think!
Suggested fix that was here didn't work. I'm editing to see if I can correct the "Invalid User ID" error I keep getting on my XDA app. Started right after I went to correct this message.
if you think you have found a fix i'd suggest bringing it to the developer's attention, such as indeed posting this in the official thread.
Also your second post got chopped off lol
threi_ said:
if you think you have found a fix i'd suggest bringing it to the developer's attention, such as indeed posting this in the official thread.
Also your second post got chopped off lol
Click to expand...
Click to collapse
I'm just messing around right now. I don't think I've found a fix. A few things I've found: I can't find a way, using the included camera, to film above 25 fps. It doesn't matter what the settings are in media_profiles.xml, 25 is the cap. The cap should be a little above 30. I also can't force the camera to film above a bit rate of 6 Mbits/sec. I averaged around 8 Mbits on the stock camera and 10 in LG camera on GB. These settings will affect light responsiveness! Perhaps the oddest thing I've noticed is that the recording streams are inverted in JB. Everything I've filmed in GB has audio in stream 1 and video in stream 2. JB's streams are the other way around. EDIT: In fact, in GB 480p recordings use Stream 1 (or 0, depending on your player) for video and stream 2 for audio, but 720p recordings use Stream 1 for audio and Stream 2 for video. So, perhaps it's worth looking into the ways in which 720p recording is being "sent" to the codec.
In the process of sorting these things out, it would help if we could find out what the AVC h263 and MPEG4 profiles and levels were in GB. I'm not completely convinced that they are configured optimally for our phone.
[To Forum Mod: Is it possible to move this thread elsewhere? Possibly the Q&A section?]
I've spent more time on this than I intended today, so this will be brief(ish). I don't know if I've found a fix, but I may have discovered a good lead. This is definitely for people who can put together and test out kernel changes faster and more accurately than I can! The other day I thought I'd found something of use, a v4l2 driver modification for Crespo. I sent my findings over to Scotthartbti. The modification may still be of use, but there was an unanswered question: why is vidioc_dqbuf unable to to clear the buffer queue? If it's the preview screen size, the fix I discovered wouldn't repair everything. SO, when I read this morning that the kernel is actually based on a Rogers ROM with limited capabilities, I decided to run another diff on the JB kernel and the GB kernel from Samsung. What I discovered was that certain drivers s3c_bc.c and s3c_bc.h are absent from the JB kernel. These two files (?) contain information that sets screen and buffer size that I couldn't find replicated anywhere in the JB kernel. I don't think it's not there... so, in the process of trying to find out why these files might not be in the JB kernel, I discovered something better: the android exynos 3.4 Git. And surprise surprise! What is it that devs are fixing over there? Quite a few issues to do with s3c buffer size, particularly in s3c-fb, and the problem of the system ignoring preview frame size!
I suspect that some lingering bugs are being addressed here: https://android.googlesource.com/kernel/exynos.git/+/android-exynos-3.4
keep it up.
Thanks for working at this. I just learned how to pull a logcat and I nabbed one while barcode scanner was on. I'm running CM10 now and I ran CM9 until July. I wish I could help, but alas I am merely a padawan.
Thanks, reynaim. Yours looks pretty much like mine. It's useful to have that confirmation!
So, I've been working on this for awhile now, spending much more time than I ever thought I would. I'm not a developer. I taught myself html, css, and php and it looks to be following a similar route with c++ and python! I've learned a fair bit about how our phone works and I have some ideas about the problems with our camera. I'll list what I can here:
1. Google updated their camera code several revisions ago, but it appears Samsung either relied on aging code or has not released the actual code for the camera hal. Several commands that bind the driver layer to software are not up to date in our camera hal and may be part of the cause of the flickering. The way the camera works is that it calls up a preview, then dumps that information before it starts recording. I suspect that the camera is not clearing the buffer queue at that moment as it should. I am attempting to rewrite this portion of the driver, but it's laborious.
2. Let's be clear about what the problems actually are: Flicker in any transition of light conditions. I can get 720p to work in bright light if there are no shadows. The light sensor is not working with the camera correctly. Actually, the problem is the framerate. At the moment, the 720p stream is going through the wrong channel, as if it is running on a PAL device. Hence, not only is the datastream throttled, but the framerate is wrong. I tinkered a bit with the light sensor drivers - changed a few values here and there - but I haven't noticed a difference.
To note here: PAL = 25 fps, NTSC =30fps. Also, PAL = 50Hz, NTSC = 60 Hz. The Infuse may use a mixed mode that runs 30fps and 50Hz.
What you will notice as a user in addition to the flicker and stuck frames is that:
The video stream is stream 1. It should be #2 (you can check this most reliably in VLC on your computer or MX Player on your phone - VLC refers to the streams as 0 and 1).
FPS, despite media_profiles.xml demanding otherwise, will not rise above 25 and may drop to around 15.
Bitrate won't rise above 6Mbits/sec (interestingly, Android sdk has the bitrate capped at 8Mbits/sec). GB would ordinarily record at 10 - 11 Mbits/sec (there is a way to up the bitrate in JB, but it doesn't improve vid quality).
3. Some minor irritations can be corrected by adding the firmware packages back into the system folder. Add a directory called "firmware" to your system folder (so it should look like /system/firmware/), give it the permissions 754 (RWX,R-X,R-X), and add RS_M5LS_OI.bin, RS_M5LS_SI.bin, RS_M5LS_TB.bin (which you may find in an old GB backup). Give those the permissions RWX, R,R (or R-X, R-X for the last two - I'm not sure which is better!). Reboot. This gets rid of that odd lag you've probably noticed when you open up 3rd party cameras and they search for storage and sometimes crash as a result.
4. I don't think - I could be wrong! - that the problem is actually in fimc. Fimc is behaving normally. There are some curiosities in the current camera hal that fimc doesn't like.
5. In fact, it seems the camera hal was not written for an 8MP camera. Why doesn't Samsung release the camera hal? Does anyone know this? My best lead came when I bricked my phone and decided to take a couple of video logcats so I could at least pinch a few values and processes.
Its seems very long since update on this thread
Whizzpopper said:
Thanks, reynaim. Yours looks pretty much like mine. It's useful to have that confirmation!
So, I've been working on this for awhile now, spending much more time than I ever thought I would. I'm not a developer. I taught myself html, css, and php and it looks to be following a similar route with c++ and python! I've learned a fair bit about how our phone works and I have some ideas about the problems with our camera. I'll list what I can here:
1. Google updated their camera code several revisions ago, but it appears Samsung either relied on aging code or has not released the actual code for the camera hal. Several commands that bind the driver layer to software are not up to date in our camera hal and may be part of the cause of the flickering. The way the camera works is that it calls up a preview, then dumps that information before it starts recording. I suspect that the camera is not clearing the buffer queue at that moment as it should. I am attempting to rewrite this portion of the driver, but it's laborious.
2. Let's be clear about what the problems actually are: Flicker in any transition of light conditions. I can get 720p to work in bright light if there are no shadows. The light sensor is not working with the camera correctly. Actually, the problem is the framerate. At the moment, the 720p stream is going through the wrong channel, as if it is running on a PAL device. Hence, not only is the datastream throttled, but the framerate is wrong. I tinkered a bit with the light sensor drivers - changed a few values here and there - but I haven't noticed a difference.
To note here: PAL = 25 fps, NTSC =30fps. Also, PAL = 50Hz, NTSC = 60 Hz. The Infuse may use a mixed mode that runs 30fps and 50Hz.
What you will notice as a user in addition to the flicker and stuck frames is that:
The video stream is stream 1. It should be #2 (you can check this most reliably in VLC on your computer or MX Player on your phone - VLC refers to the streams as 0 and 1).
FPS, despite media_profiles.xml demanding otherwise, will not rise above 25 and may drop to around 15.
Bitrate won't rise above 6Mbits/sec (interestingly, Android sdk has the bitrate capped at 8Mbits/sec). GB would ordinarily record at 10 - 11 Mbits/sec (there is a way to up the bitrate in JB, but it doesn't improve vid quality).
3. Some minor irritations can be corrected by adding the firmware packages back into the system folder. Add a directory called "firmware" to your system folder (so it should look like /system/firmware/), give it the permissions 754 (RWX,R-X,R-X), and add RS_M5LS_OI.bin, RS_M5LS_SI.bin, RS_M5LS_TB.bin (which you may find in an old GB backup). Give those the permissions RWX, R,R (or R-X, R-X for the last two - I'm not sure which is better!). Reboot. This gets rid of that odd lag you've probably noticed when you open up 3rd party cameras and they search for storage and sometimes crash as a result.
4. I don't think - I could be wrong! - that the problem is actually in fimc. Fimc is behaving normally. There are some curiosities in the current camera hal that fimc doesn't like.
5. In fact, it seems the camera hal was not written for an 8MP camera. Why doesn't Samsung release the camera hal? Does anyone know this? My best lead came when I bricked my phone and decided to take a couple of video logcats so I could at least pinch a few values and processes.
Click to expand...
Click to collapse
Hi @Whizzpopper,
I was searching on Google for infuse 4g 720p recording on JB custom ROMs and found your thread,
it seems you had been gone throught very deep on this.
Have you found anything that help us on resolving this issue afterwards ?
yogi.306 said:
Hi @Whizzpopper,
I was searching on Google for infuse 4g 720p recording on JB custom ROMs and found your thread,
it seems you had been gone throught very deep on this.
Have you found anything that help us on resolving this issue afterwards ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=38355903
Sent from my Galaxy Nexus using xda premium
yogi.306 said:
Hi @Whizzpopper,
I was searching on Google for infuse 4g 720p recording on JB custom ROMs and found your thread,
it seems you had been gone throught very deep on this.
Have you found anything that help us on resolving this issue afterwards ?
Click to expand...
Click to collapse
Indeed, I did leave the Infuse. There are so many variables, it's hard to say. The problem could be in the codec or in the settings used to interact with the codec (the media_profiles.xml or media_codecs.xml) or it could be in the kernel as Scott Hart used to suspect (don't know what he thinks now!). As you know, Samsung did not provide an honest release of the source for the Infuse.
Sorry I couldn't be of more help!
Thanks
Whizzpopper said:
Indeed, I did leave the Infuse. There are so many variables, it's hard to say. The problem could be in the codec or in the settings used to interact with the codec (the media_profiles.xml or media_codecs.xml) or it could be in the kernel as Scott Hart used to suspect (don't know what he thinks now!). As you know, Samsung did not provide an honest release of the source for the Infuse.
Sorry I couldn't be of more help!
Click to expand...
Click to collapse
Thank you for your updates,
Now Scott made a lot of improvement and fixed all most all the bugs for the kernel we are using in infuse 4g,
the only 720p recording and HDMi are not resolved yet, and i guess its not possible due to samasung not provided the source.
Thanks for your efforts on infuse.
This was a buzz a few versions ago, but not a popular topic anymore it seems. I am looking to create an app that can take pictures and save them as fast as the hardware will allow. AFAIK the preview was made a mandatory part of using the camera back around 2.3.3. We are currently working on rebuilding a version of CM without this requirements, but want to make sure we are not duplicating work. I have found a few little nuggets around that have given us hints, but doesn't seem like anyone has cracked the nut on this one yet. The overall goal being an app that captures high resolution imagery at a slow frame rate (compared to video). I would be happy with 5-10 fps. With the preview requirement, we see anywhere from 1-3 fps, usually in the lower range depending on the device. The target device for us will be the Samsung Galaxy Camera, but it should work across multiple devices as it is just a tweak to the camera API and underlying services.
Hi All from Toronto, Canada!
I hope this is the right place to ask this. My question is as follows:
I have an Honor Note 8 with the Kirin 955 and the Mali T880. The camera on this phone is the Sony IMX278 RGBW sensor, which isn't the best as I hear, but is able to record 4k/UHD video.
From what I can gather, the Kirin 955 doesn't support hardware level UHD video encoding (only DECODING), and any phone with this SoC isn't able to record 4k/UHD video.
Would it be possible (albeit a lot of work) to record 4k/UHD video and either encode it at a software level (i gather this would be really slow), or even by using the GPU instead of the CPU to encode it? From what I can gather, the GPU is much more efficient as processing graphics and 2D video shouldn't be a problem at all for it. It seems like a solution to this would allow any user with this hardware configuration to be able to enjoy their phone cameras a lot more.
I know 4k/UHD video isn't really widespread yet, but I do have the necessary components at home including a 4k TV to be able to enjoy this resolution, so I am looking for a solution to this. Is it as simple as modifying the media_profiles.xml file and installing a different camera app?
I don't know a lot about android development, but I am making it a point to learn as much as I can, and I have put quite a lot of research into this idea before posting here, including searching on XDA. I work in Software Application Support for a small CRM, and I have years of experience doing mods and customization on android devices, so I am familiar with the landscape here and I should at least be able to understand any answer no matter how technical.
Thank you for your help!
jdantow said:
Hi All from Toronto, Canada!
I hope this is the right place to ask this. My question is as follows:
I have an Honor Note 8 with the Kirin 955 and the Mali T880. The camera on this phone is the Sony IMX278 RGBW sensor, which isn't the best as I hear, but is able to record 4k/UHD video.
From what I can gather, the Kirin 955 doesn't support hardware level UHD video encoding (only DECODING), and any phone with this SoC isn't able to record 4k/UHD video.
Would it be possible (albeit a lot of work) to record 4k/UHD video and either encode it at a software level (i gather this would be really slow), or even by using the GPU instead of the CPU to encode it? From what I can gather, the GPU is much more efficient as processing graphics and 2D video shouldn't be a problem at all for it. It seems like a solution to this would allow any user with this hardware configuration to be able to enjoy their phone cameras a lot more.
I know 4k/UHD video isn't really widespread yet, but I do have the necessary components at home including a 4k TV to be able to enjoy this resolution, so I am looking for a solution to this. Is it as simple as modifying the media_profiles.xml file and installing a different camera app?
I don't know a lot about android development, but I am making it a point to learn as much as I can, and I have put quite a lot of research into this idea before posting here, including searching on XDA. I work in Software Application Support for a small CRM, and I have years of experience doing mods and customization on android devices, so I am familiar with the landscape here and I should at least be able to understand any answer no matter how technical.
Thank you for your help!
Click to expand...
Click to collapse
I don't know much about Kirin SOC but with say QCOM to be able to encode via software using say FFMPEG the ISP would have to return preview frame with UHD Dimensions.
Its probably Capable of Encoding 4K maybe can check if it can be modded by understanding how everything works .
1st Check in /system/vendor/lib /system/lib/ lib64 for any file containing the word camera zip them attach them to your post
2nd download freedcam from play store in the menu scroll down and save camera parameters attach the file outputted to /DCIM/FreeDCam
Sent from my NX503A using XDA Free mobile app