So far,i got this device i noticed the huge compression on photos ( and better dont talk about that noise reduction )
and the lower and "limited" bitrate on videos, that cant be higher than 24.9mbps dont care about any kind of video resolution or format.
The phone uses h264 in high at level 4 that in theory allows us to.
Encode video at [email protected](max stored frames)
Code:
[email protected] (9) ( wich only works the display framerate at 60fps, but encoding doesnt )
[email protected] (4) ( the same with 720P )
[email protected] (4) ( obviously not supported )
And the maximum bitrate allowed.
Code:
Max. video bit rate (VCL) 25 Mbit/s
Also jpeg compression is limited by someway at 85% quality, and extra postprocessing filters.
IT CAN'T BE REMOVED BY MEDIA PROFILES, cuz there is nothing to do, so
media profiles mods, wont work, there will still compression on it.
Click to expand...
Click to collapse
FPS capability, its "locked" up to 30fps, this phone can do so far 60fps, not sure if the Qualcomm supports 1080p at 60
but 720p by so far ( my razor managed it that ) and few test on this one, something tells me that its posible with some modding.
On my own tests i noticed modifying some files like media profiles that:
- Preview framerate can go up 120fps ( maybe even higher, noticeable preview speed with camera open )
- Framerate locked up by kernel maybe, because H264/[email protected] allows 720p 60fps. ( actually not working even with modding build.prop and media profiles )
- Bitrate limited maybe because [email protected] ( not sure at 100% ), we should use 4.1 or 5 instead, and try higher bitrates. ( also higher the profile = better the quality and file size )
but i dont know where should be specified what kind of level should be used.
Click to expand...
Click to collapse
UPDATE 02/08/13
I found a file on kernel ( the one i downloaded from sony ) that maybe has something to do, about the compression rate, ill
let all the information here, so maybe can be usefull for kernel modders.
Located in: external/jpeg/cjpeg.c ( it can be found on other locations, not sure if used )
Code:
/* Set up default JPEG parameters. */
/* Note that default -quality level need not, and does not,
* match the default scaling for an explicit -qtables argument.
*/
[COLOR="Red"]quality = 75; /* default -quality value */[/COLOR]
q_scale_factor = 100; /* default to no scaling for -qtables */
force_baseline = FALSE; /* by default, allow 16-bit quantizers */
simple_progressive = FALSE;
is_targa = FALSE;
outfilename = NULL;
cinfo->err->trace_level = 0;
Maybe that is the thing who forces compression? dont know, i need to compile but i dont know where or how to start ( not so good with linux )
^ Nothing to do here ^
In video, i found this one. ( still testing, dont know if works )
Located in: kernel/drivers/video/msm/vidc/ddl/720p/vcd_ddl_properties.c
Code:
(encoder->codec.
codec == VCD_CODEC_H264) &&
(level->level >= VCD_LEVEL_H264_1) &&
(level->level <= VCD_LEVEL_H264_3p1)
) ||
(
////
static void ddl_set_default_enc_profile(struct ddl_encoder_data *encoder)
{
enum vcd_codec codec = encoder->codec.codec;
if (codec == VCD_CODEC_MPEG4)
encoder->profile.profile = VCD_PROFILE_MPEG4_SP;
else if (codec == VCD_CODEC_H264)
encoder->profile.profile = VCD_PROFILE_H264_BASELINE;
else
encoder->profile.profile = VCD_PROFILE_H263_BASELINE;
In almost same folder, there are other profiles like 1080p
Code:
case VCD_CODEC_MPEG4:
status = (profile->profile ==
VCD_PROFILE_MPEG4_SP) &&
(level->level >= VCD_LEVEL_MPEG4_0) &&
(level->level <= VCD_LEVEL_MPEG4_6) &&
(VCD_LEVEL_MPEG4_3b != level->level);
status = status ||
((profile->profile ==
VCD_PROFILE_MPEG4_ASP) &&
(level->level >= VCD_LEVEL_MPEG4_0) &&
(level->level <= VCD_LEVEL_MPEG4_5));
break;
case VCD_CODEC_H264:
status = (level->level >= VCD_LEVEL_H264_1) &&
(level->level <= VCD_LEVEL_H264_4);
break;
case VCD_CODEC_H263:
status = (level->level >= VCD_LEVEL_H263_10) &&
(level->level <= VCD_LEVEL_H263_70);
break;
here defined the level of encoder, and also the "profile" used (guess im not wrong at all im just speculating)
if you compare to the used by the device, 3.1 for 720p and 4.0 for 1080p.
UPDATE 12/08/13
Ive tested adding some profiles and modules to default config, but stills doesnt work, values remains the same.
UPDATE 26/08/13
After hard research on kernel, just i managed how it works a part of the encoding system ( my knowledge stills limited )
i unlocked MPEG4 (m4v) h263 codec bitrates ( up to 80mbps but default at 40 ), the kernel still not ready, but ill be launching
the first version when i got something solid to share with you :fingers-crossed:
Now im trying to raise the FPS value to 60 or more, and unlock MPEG4/AVC h264 codec bitrates, up to 80mbps ( for now only 25mbps )
DEFAULT 40mbps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MAX 80mbps
ANY HELP OR IDEAS WILL BE GREATLY APRECIATED
ANY HELP OR IDEAS WILL BE GREATLY APRECIATED
My knowledge stills limited, also my time to research on it, so i guess out there is people who can help on this,
we can make much better this device with a small thing like this, the device is aleardy fast, and optimized, only lasts the camera.
I know not so much people cares about this, but i guess actually is a lack on almost every device, and almost no one, try to improve it.
Thanks to everyone who read the whole post, and excuse my bad english.
PD: This topic isnt development at all, but here comes almost all users and developers so i guess is the better place to place it, and
share knowledge about it.
I would be interested in development in this area. I use Camera FV-5 for all of my android phones including the Xperia Z. Since I've only had the phone since yesterday I haven't been able to tell if there is any improvement in picture quality. It seems that some people used the honami camera app and there were improvements but since Sony freaked out I haven't seen ports of the software available. Good luck with this project, I'll be watching this thread.
|ErosizeD| said:
ANY HELP OR IDEAS WILL BE GREATLY APRECIATED
My knowledge stills limited, also my time to research on it, so i guess out there is people who can help on this,
we can make much better this device with a small thing like this, the device is aleardy fast, and optimized, only lasts the camera.
.
Click to expand...
Click to collapse
Theres a developer by the name of "Rizal Lovins" , he has/ still is working on improving sony camera apps for previous sony phones , maybe you could get intouch with him, I dont think he has a xperia z so hence why he isnt as active here but he has dramatically improved the app for old sony phones .
|ErosizeD| said:
So far,i got this device i noticed the huge compression on photos ( and better dont talk about that noise reduction )
and the lower and "limited" bitrate on videos, that cant be higher than 24.9mbps dont care about any kind of video resolution or format.
Also jpeg compression is limited by someway at 85% quality, and extra postprocessing filters.
ANY HELP OR IDEAS WILL BE GREATLY APRECIATED
My knowledge stills limited, also my time to research on it, so i guess out there is people who can help on this,
we can make much better this device with a small thing like this, the device is aleardy fast, and optimized, only lasts the camera.
I know not so much people cares about this, but i guess actually is a lack on almost every device, and almost no one, try to improve it.
Thanks to everyone who read the whole post, and excuse my bad english.
PD: This topic isnt development at all, but here comes almost all users and developers so i guess is the better place to place it, and
share knowledge about it.
Click to expand...
Click to collapse
Firstly the phones jpg photo compression is not that high out of the box in fact better than most, the default from photoshop and pretty much all applications and probably cameras when you save a jpg for the first time which is 80%, I think you are referencing jpg compression to what is actually issues related to high levels of noise reduction.
Secondly, which firmware are you running, because the latest has huge improvements for the photo quality, much less noise reduction, same jpg compression ratio
If you want 100% jpg quality, root your phone and edit the properties file, if you do a search you will find this.
Or if you do not want to root your phone, then there are apps that can do this also, a good one has been mentioned in the posts above.
As for unlocking video stuff, I have seen some people have unlocked bit rates etc with various levels of success. Typically it ends up the application level controlling this if the processor doesn't have the support at the hardware level, which has a performance impact on the device.
Seriously look under the themes and apps section there are loads of discussions on all the things you have mentioned, including probably a lot of answers to your questions
danw_oz said:
Firstly the phones jpg photo compression is not that high out of the box in fact better than most, the default from photoshop and pretty much all applications and probably cameras when you save a jpg for the first time which is 80%, I think you are referencing jpg compression to what is actually issues related to high levels of noise reduction.
Secondly, which firmware are you running, because the latest has huge improvements for the photo quality, much less noise reduction, same jpg compression ratio
If you want 100% jpg quality, root your phone and edit the properties file, if you do a search you will find this.
Or if you do not want to root your phone, then there are apps that can do this also, a good one has been mentioned in the posts above.
As for unlocking video stuff, I have seen some people have unlocked bit rates etc with various levels of success. Typically it ends up the application level controlling this if the processor doesn't have the support at the hardware level, which has a performance impact on the device.
Seriously look under the themes and apps section there are loads of discussions on all the things you have mentioned, including probably a lot of answers to your questions
Click to expand...
Click to collapse
your answer is very well written, but I did not find how to increase the jpg quality 100% and I can not find anywhere a tutorial on how improved the camera as root, and I have not I find either application who can do ...
you just might deepen this, for the sake of the ignorant community xda
VSTmoTP2 said:
I would be interested in development in this area. I use Camera FV-5 for all of my android phones including the Xperia Z. Since I've only had the phone since yesterday I haven't been able to tell if there is any improvement in picture quality. It seems that some people used the honami camera app and there were improvements but since Sony freaked out I haven't seen ports of the software available. Good luck with this project, I'll be watching this thread.
Click to expand...
Click to collapse
There is no improvement because camera is limited by jpeg libs ( .so files in system/libs folder ) so there arent any program that can
really unlock 100% true jpeg, because that libs cant be avoided.
danw_oz said:
Firstly the phones jpg photo compression is not that high out of the box in fact better than most, the default from photoshop and pretty much all applications and probably cameras when you save a jpg for the first time which is 80%, I think you are referencing jpg compression to what is actually issues related to high levels of noise reduction.
Secondly, which firmware are you running, because the latest has huge improvements for the photo quality, much less noise reduction, same jpg compression ratio
If you want 100% jpg quality, root your phone and edit the properties file, if you do a search you will find this.
Or if you do not want to root your phone, then there are apps that can do this also, a good one has been mentioned in the posts above.
As for unlocking video stuff, I have seen some people have unlocked bit rates etc with various levels of success. Typically it ends up the application level controlling this if the processor doesn't have the support at the hardware level, which has a performance impact on the device.
Seriously look under the themes and apps section there are loads of discussions on all the things you have mentioned, including probably a lot of answers to your questions
Click to expand...
Click to collapse
The same thing i told you, not even the apk, there is nothing todo with it, need kernel, and libs development, and libs are locked by sony, and heavly encripted up.
So i guess, we cant do much more about it.
I can confirm what was said in the previous post, Camera FV-5 is unable to alter the jpeg compression ratio... I did notice from my tests that the focus algorithm is better on Camera FV-5, resulting in sharper photos due to more accurate focus. I have T-Mobile's stock firmware .166. I will look into newer firmware, hopefully I'll see an improvement. So far the images from my LG G2X with Camera FV-5 is better than the output from this Xperia Z.
ey ,not exaggerating either heun, I had the X2 and the picture has nothing to do with that of xperia z ... but I think that may be a small improvement would still be welcome,
VSTmoTP2 said:
I can confirm what was said in the previous post, Camera FV-5 is unable to alter the jpeg compression ratio... I did notice from my tests that the focus algorithm is better on Camera FV-5, resulting in sharper photos due to more accurate focus. I have T-Mobile's stock firmware .166. I will look into newer firmware, hopefully I'll see an improvement. So far the images from my LG G2X with Camera FV-5 is better than the output from this Xperia Z.
Click to expand...
Click to collapse
Yep, optimus looks better "maybe" because it has 0% compression ratio, but in terms of color reproduction, the Z is much much better actually.
alessa said:
ey ,not exaggerating either heun, I had the X2 and the picture has nothing to do with that of xperia z ... but I think that may be a small improvement would still be welcome,
Click to expand...
Click to collapse
I guess, with the libs locked up, we cant modify that compression, so i dont know how we can work this out.
sony and they say what? he does not want to release the code?
I used now camera fv-5 and take photos in png(raw) format, the picture have more details,size increase from 2mb to 15mb but my device it getting wery hot,almost 80c and disabled my radio, This is not wery safe?!
poczesaniec1 said:
I used now camera fv-5 and take photos in png(raw) format, the picture have more details,size increase from 2mb to 15mb but my device it getting wery hot,almost 80c and disabled my radio, This is not wery safe?!
Click to expand...
Click to collapse
I'll test
alessa said:
your answer is very well written, but I did not find how to increase the jpg quality 100% and I can not find anywhere a tutorial on how improved the camera as root, and I have not I find either application who can do ...
you just might deepen this, for the sake of the ignorant community xda
Click to expand...
Click to collapse
As mentioned by rezzsha. http://forum.xda-developers.com/showthread.php?t=2221351 covers pretty much all of this within the thread.
From what I understand you have to mod it in three places, the build.properties, media_profile.xml and SemcCameraUI.apk
---------- Post added at 03:35 PM ---------- Previous post was at 03:31 PM ----------
poczesaniec1 said:
I used now camera fv-5 and take photos in png(raw) format, the picture have more details,size increase from 2mb to 15mb but my device it getting wery hot,almost 80c and disabled my radio, This is not wery safe?!
Click to expand...
Click to collapse
Interesting, I have used this application for a long time and never found these issues you mention
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
|ErosizeD| said:
Yep, optimus looks better "maybe" because it has 0% compression ratio, but in terms of color reproduction, the Z is much much better actually.
I guess, with the libs locked up, we cant modify that compression, so i dont know how we can work this out.
Click to expand...
Click to collapse
Please read above what I wrote, the thread and this developer has been improving Sony phones camera quality for a long time, and can probably tell you anything you need to know.
I am not certain that the compression is in the kernel level driver, all the driver should be doing is interpreting the information from the image sensor and then passing that through to the camera app to apply white balance, saving of the file...
Your still didn't answer which firmware you are using, because Sony significantly reduced the excessive noise reduction in the later ROMS.
And I would say that photos from the phone now in good light would be as good as most point and shoot cameras.
I have uploaded an un-altered photo from my Xperia Z, using the standard camera app in 4.2.2 OS. http://www.flickr.com/photos/dan-wilson/9407288542/ please tell me if you can not see the full size copy
the alternate is also asking the user "doomlord" he is the main guy creating modded kernels , so he should be your guy for kernel level. or looking into the s4 dev place ,since they have the same sensor , only difference is the lens i think
danw_oz said:
As mentioned by rezzsha. http://forum.xda-developers.com/showthread.php?t=2221351 covers pretty much all of this within the thread.
From what I understand you have to mod it in three places, the build.properties, media_profile.xml and SemcCameraUI.apk
---------- Post added at 03:35 PM ---------- Previous post was at 03:31 PM ----------
Interesting, I have used this application for a long time and never found these issues you mention
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
Please read above what I wrote, the thread and this developer has been improving Sony phones camera quality for a long time, and can probably tell you anything you need to know.
I am not certain that the compression is in the kernel level driver, all the driver should be doing is interpreting the information from the image sensor and then passing that through to the camera app to apply white balance, saving of the file...
Your still didn't answer which firmware you are using, because Sony significantly reduced the excessive noise reduction in the later ROMS.
And I would say that photos from the phone now in good light would be as good as most point and shoot cameras.
Click to expand...
Click to collapse
MOD but it is useless on 4.2.2!
alessa said:
MOD but it is useless on 4.2.2!
Click to expand...
Click to collapse
Remember, it is a phone with a camera. Not a camera with a phone. Small sensor due to size limitations = bad image quality. Bigger sensor typically = better image quality, less noise... even at much less resolution regardless of image compression without getting ridiculous.
For a phone, this is one of the best I have used since the upgrade.
Have tested my link above, it does show the image only about half the pixel count of the original, but I still think that it shows that the photo quality is very acceptable. I think it does still lack a little texture, in say the likes of the tree leaves again due to image noise removal algorithms, but at print size you would even notice this
danw_oz said:
Remember, it is a phone with a camera. Not a camera with a phone. Small sensor due to size limitations = bad image quality. Bigger sensor typically = better image quality, less noise... even at much less resolution regardless of image compression without getting ridiculous.
For a phone, this is one of the best I have used since the upgrade
Click to expand...
Click to collapse
frankly, the photo days are excellent, just a little ameglioration for night photography would be welcome ... but I'm still happy with my xperia z
danw_oz said:
As mentioned by rezzsha. http://forum.xda-developers.com/showthread.php?t=2221351 covers pretty much all of this within the thread.
From what I understand you have to mod it in three places, the build.properties, media_profile.xml and SemcCameraUI.apk
---------- Post added at 03:35 PM ---------- Previous post was at 03:31 PM ----------
Interesting, I have used this application for a long time and never found these issues you mention
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
Please read above what I wrote, the thread and this developer has been improving Sony phones camera quality for a long time, and can probably tell you anything you need to know.
I am not certain that the compression is in the kernel level driver, all the driver should be doing is interpreting the information from the image sensor and then passing that through to the camera app to apply white balance, saving of the file...
Your still didn't answer which firmware you are using, because Sony significantly reduced the excessive noise reduction in the later ROMS.
And I would say that photos from the phone now in good light would be as good as most point and shoot cameras.
I have uploaded an un-altered photo from my Xperia Z, using the standard camera app in 4.2.2 OS. http://www.flickr.com/photos/dan-wilson/9407288542/ please tell me if you can not see the full size copy
Click to expand...
Click to collapse
Not just those 3 levels, also libs and kernel its locked... ( actually jpeg enc libs )
rezzsha said:
the alternate is also asking the user "doomlord" he is the main guy creating modded kernels , so he should be your guy for kernel level. or looking into the s4 dev place ,since they have the same sensor , only difference is the lens i think
Click to expand...
Click to collapse
yes i asked to him, but it seems to be too bussy for answer me :\
alessa said:
frankly, the photo days are excellent, just a little ameglioration for night photography would be welcome ... but I'm still happy with my xperia z
Click to expand...
Click to collapse
Yea, anyway its a good device, but that compresion ****s up somethings, and same to the video bitrates, that "limitation" is a bit shame and i dont feel i have a high end
device at all with those limitations.
|ErosizeD| said:
...i dont feel i have a high end
device at all with those limitations.
Click to expand...
Click to collapse
have you tried pro capture app ,takes pretty good photos and pics are usually bigger??
First post updated! this is getting interesting
rezzsha said:
have you tried pro capture app ,takes pretty good photos and pics are usually bigger??
Click to expand...
Click to collapse
No, external apps only re-encode the output JPEG, just making it bigger, but not with better quality.
Related
hi folks
as you all might know, sony's camera drivers for XZ are ridiculously poor quality due to vast image compression & lossy noise-cancelling/bluring mechanism.
on the contrary, we all know that SGS4's camera is the SAME chip and brand/manufacturer etc, even though pictures (and videos!) taken with SGS4 are in brilliant quality in comparison to our XZ. in addition, picture average size @ 12.8MP with SGS4 is around ~6MB while on XZ is around ~2MB in bright conditions.
just a lilttle thought i have - if those camera chips above are IDENTICAL, than why not implement SGS4 camera drivers on our FW?
it's all about the drivers right? could someone (perhaps developer) can do some effort and try to import those drivers?
if that was a n00b question - please don't judge me. it's just a logical assumption i have made.
cheers
I agree with you, hope someone can help on this, also if possible to add one more thing - Power shutter ( why waste such a beautiful button )
Well, i found this information VERY interesting:
http://www.androidauthority.com/new-android-camera-api-317878/
Google is working on a new camera API that will bring new features and possibly improved image quality to Android devices, including the Nexus line.
Many reviewers have panned the camera experience on the Nexus 5 as inconsistent and mediocre, with some going as far as to call the product unfinished. Google acknowledged the problems and said that a software update could alleviate some of them. Indeed, code discovered in the publicly available Android source code suggests that a new Camera API is in the works that could improve image quality and give access to new features.
Android developer Josh Brown first spotted the code, and Ron Amadeo of Ars Technica broke the news. According to the dates on the commits in the code repository, the API was in the works for about 10 months, but Google didn’t finish it in time for the KitKat release, which shipped with the old API.
Here’s a summary of what may be coming to the Android camera experience once the new API is implemented:
Support for Camera RAW format – RAW is a format that preserves most of the information captured by the camera sensor, allowing for more in-depth editing, either on the device (e.g. with Snapseed) or on a PC with software like Photoshop. JPEG and other similar formats, in contrast, are compressed for smaller size, and a lot of the original info is lost in the process.
Face detection – the API will allow camera apps to detect the faces of people in the frame, and assign each face an ID for manipulation purposes. This is a feature that many Android manufacturers have implemented on their own, but the new API will make it available in stock Android.
Burst mode – another feature present on popular devices from Samsung, HTC, and others is burst mode – keeping the shutter button pressed will take a series of shots in quick succession. This feature will go very well with the new photo enhancement capabilities of Google Plus.
Support for removable cameras – possibly something similar to Sony’s QX10 and QX100 Wi-Fi cameras.
General “improved capabilities” and “fine grain control” that may (we hope) bring improvements to image quality.
It seems that the new Camera API was in an advanced stage of development when Google decided to cut it out of KitKat. A last moment change of plans could explain why the Nexus 5’s camera feels a bit unfinished. When the new API lands, it will be backwards compatible, but for now we can only guess when we will see the update.
Click to expand...
Click to collapse
AS fas as I know, to support RAW mode not only the app, but also the camera driver should support RAW mode... Do you think possible to have RAW in our Nexus? It would be awesome!
Yes RAW would be a fantastic feature, but I'll be happy just to see a focus enhancement and a better interface, more user friendly.
I don't care about raw on phone, but this seems to confirm that a software solution may be coming.
Sent from my Nexus 5 using Tapatalk
I guess we have to wait for the nexus 7 launch..... I highly doubt a completely revamped camera is coming out any time soon especially after the kit Kat launch.
Sent from my Nexus 5 using xda app-developers app
Isn't raw a huge file size? Correct me if I'm wrong.
davwman said:
Isn't raw a huge file size? Correct me if I'm wrong.
Click to expand...
Click to collapse
Yeah it is. I highly doubt I would go and edit raw files with paint shop pro coming from my N5.
Please Read Comment 675
http://forum.xda-developers.com/showthread.php?t=2471900&page=68
Thanks
I could be mistaken but I think Google finally separated the Gallery from the Camera apk in Kit-Kat. This might imply Google is planning on updating the camera app in the Play Store. I really hope they do something soon because the camera app is pretty terrible.
I'll start giving a rat's ass about RAW once they fix the shutter lag...
I agree with most of you. I just want shutter and focus lag out of the way, then we can talk save formats. :good:
i can see it now
"why are all my photos so full of noise when i shoot in raw?"
Bad, bad idea on a phone.
---------- Post added at 12:03 AM ---------- Previous post was at 12:01 AM ----------
Dragooon123 said:
I'll start giving a rat's ass about RAW once they fix the shutter lag...
Click to expand...
Click to collapse
If you let the phone get an exposure and focus lock you will see the photo is taken instantly, there is no shutter lag.
MrBelter said:
If you let the phone get an exposure and focus lock you will see the photo is taken instantly, there is no shutter lag.
Click to expand...
Click to collapse
True - but for the end user, the result is the same - miss the shot while the phone gets the exposure lock and focus lock, followed by instant shutter.
In bright daylight, it should not take that long to get exposure/focus lock/etc. Camera should be able to determine the subject, focus on it, lock exposure right after the user starts the camera app and points at the subject, and grab the picture as soon as the user clicks the shutter button.
Almost all cameras on other smartphones can do this, so no reason why N5 can't do this
Its beyond idiotic to be adding features to a camera app that sucks at the simple task of taking a photo. Adding raw support should come WAY after the camera app can focus quickly, correctly expose an image and has a usable simple interface. After that is mastered, then simple basic features should be added like burst mode and slo mo video. Only then should RAW support be even thought about. What good is RAW support when the camera can't correctly focus and expose images and the interface is wonky and annoying to use and the preview image is an interpolated mess?
Jishnu Sur™ said:
Please Read Comment 675
http://forum.xda-developers.com/showthread.php?t=2471900&page=68
Thanks
Click to expand...
Click to collapse
Excellent for G2, but what for N5? Are you working on it? (both 100% JPG Quality and 60fps woul be extellent!)
Yakandu said:
Excellent for G2, but what for N5? Are you working on it? (both 100% JPG Quality and 60fps woul be extellent!)
Click to expand...
Click to collapse
100% jpg is billions milles away from raw floating point format like *.hdr, *. exr...
And for those that claim that raw is useless, then they must simply don't catch what's raw offers.
bleuxeon said:
100% jpg is billions milles away from raw floating point format like *.hdr, *. exr...
And for those that claim that raw is useless, then they must simply don't catch what's raw offers.
Click to expand...
Click to collapse
I totally agree
Jishnu Sur™ said:
Please Read Comment 675
http://forum.xda-developers.com/showthread.php?t=2471900&page=68
Thanks
Click to expand...
Click to collapse
thanks for your work.. but please add an advice, for flashaholic like me, to read thread title.. cause flashing a G2 camera app does bootloop on a N5...
how noob I feel now...
I for one am extremely happy about the idea of RAW shooting. Would love to see it on the Nexus 5.
Sent from my HTC One using Tapatalk
bleuxeon said:
100% jpg is billions milles away from raw floating point format like *.hdr, *. exr...
And for those that claim that raw is useless, then they must simply don't catch what's raw offers.
Click to expand...
Click to collapse
Considering that XDA is about 90% noobs asking stupid questions, RAW wont be a big deal to most people out there
walie said:
...XDA is about 90% noobs asking stupid questions...
Click to expand...
Click to collapse
[Citation Needed]
Would it be possible to get higher resolution recording than 1080p, as in 2K, QXGA, WQXGA? I know it's not just the software issue. Naturally, the HW must be capable, so let's see first if the camera module could do it.
UsernameWasTaken said:
Would it be possible to get higher resolution recording than 1080p, as in 2K, QXGA, WQXGA? I know it's not just the software issue. Naturally, the HW must be capable, so let's see first if the camera module could do it.
Click to expand...
Click to collapse
Theoretically, I sure do think so (if there's no hardware cap or something we cannot alter). However, you'd most likely have to tweak some stuff, in order go get the required performance from the hardwareside.
The hardware is capable of taking higher resolution photos, but processing would be slow I think. Also, the camera HAL must support it and we can't alter that.
Sent from my OmniROM-powered LG Optimus 4X HD
@Adam77Root @laufersteppenwolf
I've seen this in news.I guess we'd need updated libs but since you guys got camera working with old/new libs, why not give it a shot?
http://www.xda-developers.com/android/add-4k-and-120-fps-to-your-stock-lg-camera/
Even if the hardware is not capable of giving out good fps, I think we could still be able to record 4 k videos at very low FPS.
If you guys can't get this to work, could you atleast tweak the camera to widen ISO values so we get better pictures in the dark? Pretty sure our camera is capable of it and seen some guy doing it for stock ICS camera.He tweaked ISO values and I had tested it.It looked far better compared to stock camera.Unfortunately it's only compatible with ICS.
Even general mobile discovery can take better pictures in the dark and doubt it has a better camera than ours.We just need a few tweaks.
Adam77Root said:
The hardware is capable of taking higher resolution photos, but processing would be slow I think. Also, the camera HAL must support it and we can't alter that.
Sent from my OmniROM-powered LG Optimus 4X HD
Click to expand...
Click to collapse
That's my thinking, too. If it were possible, the processing would almost certainly not be handled by camera's hardware. I think it would have to be offloaded to phone's CPU. But, who knows? G2 got 4K with a relatively simple apk modding which means the camera module was hardware-capable to begin with. G Flex, too. Luckily, 4X has the same CMOS as the Nexus 4, Sony's IMX111PQ, and that can be very helpful. Perhaps a new driver is required or just a modded apk, like G2. I'm no dev, so I can't tell or make.
@ottomanhero Sadly, we can't get 4K rec coz CMOS hasn't enough vertical pixels. There's also a problem with encoding the vid on phone's hardware as it would probably be a soft encoder which means the CPU would process it (but that's a huge bite even for the top desktop CPUs). But 2K or 1440p vid might be feasable. Tegra 3 can output up to 2560x1600 meaning we could play it, too, with a normal bitrate.
Well atleast we could improve the ISO range to get better shots under low light conditions.I used to have a phone that's 2 MP and even that one had better pictures in low light conditions.It is proven our cam can handle higher/lower ISO values.We just need some software tweaks.
ottomanhero said:
Well atleast we could improve the ISO range to get better shots under low light conditions.I used to have a phone that's 2 MP and even that one had better pictures in low light conditions.It is proven our cam can handle higher/lower ISO values.We just need some software tweaks.
Click to expand...
Click to collapse
Do you mean this mod?
If someone can give me original V10f camera.tegra.so and libnvmm_camera.so I could take a look at it for JB+.
Adam77Root said:
Do you mean this mod?
If someone can give me original V10f camera.tegra.so and libnvmm_camera.so I could take a look at it for JB+.
Click to expand...
Click to collapse
I think I've got an ICS system image somewhere on my HDD sec
BTW, gotta talk to you later regarding cam, 'cause I'm not too sure whether or not my idea can even work...
EDIT: Here you go
Hello. So, there has been a confusion on how to capture better photos and videos on Nexus 5. With the introduction of Android Lollipop we have the option to shoot RAW photos (which is basically the same as before, with the difference being that the image is not compressed or processed), and also we got a great app which is called L Camera..
L Camera was a great alternative for those who wanted to squeeze out as much as Nexus 5's camera has to offer. We even got to shoot at 1080p/60fps(although it was never fixed to work properly) and a resolution very close to 4K.
I hoped that since Google unlocked all this power for us with Lollipop, Marshmallow was going to bring even better stuff on the table. This does not seem to be the case though.
So, right now we are basically stuck in terms of camera options. The L Camera has been outdated, problematic and unsupported for quite some while now and Google's stock camera is still really bad.
How do you feel about all this guys? Have you found any better camera app than L Camera that works on Marshmallow? Are you building something yourselves? (maybe and improved version of L Camera)
Let's discuss this!
There is this "Manual Camera", "Camera FV-5", and "Open Camera"
This may sound strange, but the Marshmallow stock camera app (which has been updated via the play store after M was released) is far better than that of Lollipop. I have found that it is far faster to respond (both focusing and the shutter), and handles low light much better (including with HDR). The auto white balance is much improved, too. The controls are more convenient than they were on Lollipop. This was a big surprise. One day, after routine updates, the camera just became much better!
True, it is no SLR, but whereas the photos I got from the Nexus 5 on Lollipop were mostly unusable except for viewing on another phone, now I get decent shots that I am not embarrassed to post online.
I use Proshot, really great camera app.
Skickat från min Nexus 5 via Tapatalk
jshames said:
This may sound strange, but the Marshmallow stock camera app (which has been updated via the play store after M was released) is far better than that of Lollipop. I have found that it is far faster to respond (both focusing and the shutter), and handles low light much better (including with HDR). The auto white balance is much improved, too. The controls are more convenient than they were on Lollipop. This was a big surprise. One day, after routine updates, the camera just became much better!
True, it is no SLR, but whereas the photos I got from the Nexus 5 on Lollipop were mostly unusable except for viewing on another phone, now I get decent shots that I am not embarrassed to post online.
Click to expand...
Click to collapse
Got to agree. I notice especially low light performance has improved greatly on the stock camera app on marshmallow. Not sure what Google has done but good job on them for doing it. It still responses like crap and lags some times but if the pictures are better I am all for it.
Stock app is much better its what I call serviceable now. I always knew the Nexus 5s camera was capable but poor software always held it back. Sad to see it took almost 3 years after it launched to become capable.
Open camera is also a great app and 100% free and open source
The best choice is to shoot DNG and then use lightroom for android
I'm a Brazilian without English Course, sorry and be comprehensive
The lens is prone to gather grease from you fingers causing a hazy streaky look. I always bring a microfiber cloth to clean it off before shooting.
There isnt a proper RAW color profile available so it takes work to get images to pop like the JPEGs do. One of these days I'l generate one, it requires shooting a colorchecker chart outside in clear mid-day.
I haven't taken much pictures with it but this one.
I have a 6S and iPhone 5, I had lost my iPhone 5 out of stupidity. I wanted a cheap replacement and heard good things about the nexus, I had already tried the Galaxy s5 and htc one m8 so might as well kill 2 birds with one stone a good cheap phone and a chance to try out the nexus 5. Very impressed so far, very smooth. Runs much smoother then the galaxies I had. Ran me $160 CAD and it's unlocked
I decided to take a picture last night with the nexus. Came out amazing, took some other low lighting shots in my room and compared it to my 6s and it isn't that bad to be completely honest much better then my s5, Note edge and htc in low lighting.
The N5 is terrible for general photography esp low-light. Only my iPhone 5S is worse in low-light situations lol.
RazorMC said:
The N5 is terrible for general photography esp low-light. Only my iPhone 5S is worse in low-light situations lol.
Click to expand...
Click to collapse
It's even worse than a dedicated camera. But you can improve things by processing RAWs:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 07:15 PM ---------- Previous post was at 07:07 PM ----------
Here's a daylight example of a processed RAW:
RoadToNever said:
It's even worse than a dedicated camera. But you can improve things by processing RAWs:
---------- Post added at 07:15 PM ---------- Previous post was at 07:07 PM ----------
Here's a daylight example of a processed RAW:
Click to expand...
Click to collapse
RAW and post-editing kind of defeats the entire purpose of point-and-shoot. The first pic is really amazing with the amount of detail and clarity. The second one has too much grain for my liking. Takes me back to those Nokia cameraphones from yesteryears lol
But MM has really improved cam quality if the user knows how to use the manual settings. I've got better results with Camera FV-5 than with any other app.
RazorMC said:
RAW and post-editing kind of defeats the entire purpose of point-and-shoot. The first pic is really amazing with the amount of detail and clarity. The second one has too much grain for my liking. Takes me back to those Nokia cameraphones from yesteryears lol
But MM has really improved cam quality if the user knows how to use the manual settings. I've got better results with Camera FV-5 than with any other app.
Click to expand...
Click to collapse
Yes, RAW isn't user friendly, but this is thread about camera quality The second pic is really pushing it. It was a very dimly lit venue, a challenge for any camera. But offline processing allows much more sophisticated algorithms. Normally that shot would either be underexposed or at best a smoothed out, waxy-looking mess.
RoadToNever said:
Yes, RAW isn't user friendly, but this is thread about camera quality The second pic is really pushing it. It was a very dimly lit venue, a challenge for any camera. But offline processing allows much more sophisticated algorithms. Normally that shot would either be underexposed or at best a smoothed out, waxy-looking mess.
Click to expand...
Click to collapse
True, but that means instant sharing is out of the question. And many people would be uncomfortable processing pics just so some distant grandma "Likes" it on Fb.
Everytime i take low-light shots, I remember my trusty N73 with its huge LED flash and N82 with xenon.
How would you say we can make the best use of HDR on our N5 with 3rd party apps? And does it really work?
RazorMC said:
True, but that means instant sharing is out of the question. And many people would be uncomfortable processing pics just so some distant grandma "Likes" it on Fb.
Everytime i take low-light shots, I remember my trusty N73 with its huge LED flash and N82 with xenon.
How would you say we can make the best use of HDR on our N5 with 3rd party apps? And does it really work?
Click to expand...
Click to collapse
I have a simple checklist I go through when processing raw photos: exposure, white balance and NR if needed. I rarely need anything else so for a single shot I'm normally done in less than a minute. Raw converters offer many options which can seem overwhelming for the novice, but there's nothing to it if you stick to the most important ones. OTOH if you are working on an uncalibrated monitor there's a small chance are you might be making things worse color-wise. I don't do HDR, sorry.
Snap camera? I threw it under system/apps, changed the name to camera2.apk and even the power button hot key works.
Sent from my Nexus 5 using Tapatalk
"A better camera" super mode do the job very well in any light conditions.
But going manual pays it in certain situations.
https://flic.kr/p/v3nAd3
I'm a Brazilian without English Course, sorry and be comprehensive
prog19 said:
"A better camera" super mode do the job very well in any light conditions.
But going manual pays it in certain situations.
https://flic.kr/p/v3nAd3
I'm a Brazilian without English Course, sorry and be comprehensive
Click to expand...
Click to collapse
I'm enjoying "A Better Camera" too. It's really simple to use and produces nice photos. But I still prefer Camera FV-5 over it when I need manual setings.
prog19 said:
The best choice is to shoot DNG and then use lightroom for android
I'm a Brazilian without English Course, sorry and be comprehensive
Click to expand...
Click to collapse
lightroom can now take raw pictures with our N5
onesolo said:
lightroom can now take raw pictures with our N5
Click to expand...
Click to collapse
And output any dng to full resolution.
The sad thing about LR is the import picture method
I'm a Brazilian without English Course, sorry and be comprehensive
Hi.
I want to ask, if theres any way, to get the phone to just save the RAW Sensor output with 108MP without compressing or altering
the image in any way?
I also ask myself already all the time, why the 108MP setting is only possible in the stock camera app.
If you use for example open camera, its not possible to set a resolution bigger than 12MP. Is this a error, or why does
this happen?
Regards
The 108 mp is hype. The top Canon pro cam is 24.1 mp on a sensor many times bigger. It delivers much sharper, higher resolution images than any smartphone can. It also uses lens that have exponentially more light gathering ability.
Bigger pixels mean more light gathering ability and a higher signal to noise ratio. The noise floor is constant and you need a strong enough signal to overcome it even in digital data sampling.
The highest reasonable mp size for a phone cam sersor is 20mp but 12mp is probably ideal. Sound familiar?
At 108mp that sensor's light gathering ability is almost nothing especially with a lense that size.
Maybe in bright light stills but even then it may lack the bandwidth and processor power to accommodate that amount of data.
How many raw 108 mp images would you even want to store if it was possible?
ME20001 said:
Hi.
I want to ask, if theres any way, to get the phone to just save the RAW Sensor output with 108MP without compressing or altering
the image in any way?
I also ask myself already all the time, why the 108MP setting is only possible in the stock camera app.
If you use for example open camera, its not possible to set a resolution bigger than 12MP. Is this a error, or why does
this happen?
Regards
Click to expand...
Click to collapse
If you are on stock MIUI, there's the possibility to make 108 but if you compare with a gcam app like Shamim V12 you'll see that the 108 of MIUI is not as good as gcam pixel binning, further more more storage is needed
Laptapper said:
If you are on stock MIUI, there's the possibility to make 108 but if you compare with a gcam app like Shamim V12 you'll see that the 108 of MIUI is not as good as gcam pixel binning, further more more storage is needed
Click to expand...
Click to collapse
They had been far better off using larger pixels with better microlense quality/design than doing the binning garbage. Binning only screws up the signal to noise ratio more by increasing the noise floor. A smartphone is already a warm, electronicly noisy device as it is... the enemies of cmos sensors.
Binning is effective to a point at the cost of resolution for low light performance. 108mp binning on a sensor of the size used on smartphones seems counterproductive. Binning can introduce artifacts to the image.
Yes yes yes, I know about the disadvntages of this high resolution, I am into DSLR photography,
but I want to see how the RAW picture from the sensor at full resolution the sensor can deliver looks.
It seems to be impossible to get on a real RAW photo on Stock MIUI ROM?
(I Want to install another ROM anyways, but still waiting for bootloader unlock permission)
Do you have a rom to suggest, that is able to make real 108MP RAW photos, and probably 8k Video (The sensor A Samsung
Isocell HM2 supports that, the ROM doesnt)
blackhawk said:
They had been far better off using larger pixels with better microlense quality/design than doing the binning garbage. Binning only screws up the signal to noise ratio more by increasing the noise floor. A smartphone is already a warm, electronicly noisy device as it is... the enemies of cmos sensors.
Binning is effective to a point at the cost of resolution for low light performance. 108mp binning on a sensor of the size used on smartphones seems counterproductive. Binning can introduce artifacts to the image.
Click to expand...
Click to collapse
You're right.
But 108 stock isn't good as 12 in gcam, or what you think?
Which cam and settings you're using?
GCAM Doesnt allow 108MP, the stock camera APP seems to be the only one that allows 108, but only as JPG, not
as RAW10 the sensor can output native.
I want to see, how a photo in 108MP looks straight out of the sensor, but it seems not that easy to get
your hnds on one, without the device modifies it before...
Laptapper said:
You're right.
But 108 stock isn't good as 12 in gcam, or what you think?
Which cam and settings you're using?
Click to expand...
Click to collapse
Don't have this phone. It's likely optimized at or near the best ratio.
At higher brightness levels and if digitally zoomed in it may deliver higher resolution (for that given area).
It's seems these manufacturers now have a rather pointless pixel race in progress.
So to say it short: No one here knows how to get RAW 108MP Photos out of the sensor?
ME20001 said:
So to say it short: No one here knows how to get RAW 108MP Photos out of the sensor?
Click to expand...
Click to collapse
No such thing is my guess. The hardware has to support that method of output. The best you can do is whatever the lowest binning rate is. If has provisions to access individual pixels on a hardware level it be possible.
The Hardware (Sensor) can do RAW 10 at full 108MP resolution, see here:
108MP ISOCELL HM2 | Mobile Image Sensor | Samsung Semiconductor Global
Samsung ISOCELL HM2 mobile image sensor brings every detail of your scene to life. It delivers 108MP, 0.7um pixel size and Real-time HDR.
semiconductor.samsung.com
It also can record at 8k 24fps or 4k 120fps, but the device doesnt allow 8k at all, and 4k recording only at 30fps...
It seems that they have locked down the software, for what reason ever, probably because its a mid class phone, to prevent
it come too near to the upper class devices...
Its camera also makes already very good photos, if you know what you have to set in the settings. I really would
like to see how this would look in 10Bits uncompressed RAW at 108MP, I tried to upload here one of the 108MP JPG Photos,
but it broke the forum:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Heres a Dropbox Link for the Picture:
IMG_20220328_153250.jpg
Shared with Dropbox
www.dropbox.com
Best is to download it and then take a look on it, the Previev on Dropbox seems to have some issues to handle that resolution.
affirmative it's possible as of today, previously the sensors full potential wasn't accessible due to the extensive os and system feature lock downs but even after the phones themselves were capable of being unlocked the sensor still remained unavailable because it has it's own dedicated chipset that has a dedicated partial operation and algorithm system which meant that it couldn't be modified or accessed unless you had very specialized equipment. there's a lot of technical complexity that i've forgoed elaborating upon to keep this response less lengthy lol, at any rate after roughly a year of effort i've finally found a way to bypass all of the restrictions and i'll be potentially publishing the results of the code named C.I.A.R.A. project once my tests are complete and furthermore i may be able to make such feature functionality commercially available and distributable once the project has been thoroughly and fully completed in all of it's entirely lol.
^_^
nosidamXumres said:
affirmative it's possible as of today, previously the sensors full potential wasn't accessible due to the extensive os and system feature lock downs but even after the phones themselves were capable of being unlocked the sensor still remained unavailable because it has it's own dedicated chipset that has a dedicated partial operation and algorithm system which meant that it couldn't be modified or accessed unless you had very specialized equipment. there's a lot of technical complexity that i've forgoed elaborating upon to keep this response less lengthy lol, at any rate after roughly a year of effort i've finally found a way to bypass all of the restrictions and i'll be potentially publishing the results of the code named C.I.A.R.A. project once my tests are complete and furthermore i may be able to make such feature functionality commercially available and distributable once the project has been thoroughly and fully completed in all of it's entirely lol.
^_^
Click to expand...
Click to collapse
Welcome to XDA.
Pictures or it never happened.
The individual pixels are so minuscule their sampling capture is pathetic and is further exacerbated by the noise floor/noise cancellation errors. Good pixel lens at this microscopic size... no such thing especially at this price point.
A good 26mp even 20mp sensor can capture a sufficient amount of detail for even poster size blowups. These are full frame sensors with precision pixel lens.
Samsung knows this... you'll get a mushy raw image with a hugh file size. Perfect.
blackhawk said:
Welcome to XDA.
Pictures or it never happened.
The individual pixels are so minuscule their sampling capture is pathetic and is further exacerbated by the noise floor/noise cancellation errors. Good pixel lens at this microscopic size... no such thing especially at this price point.
A good 26mp even 20mp sensor can capture a sufficient amount of detail for even poster size blowups. These are full frame sensors with precision pixel lens.
Samsung knows this... you'll get a mushy raw image with a hugh file size. Perfect.
Click to expand...
Click to collapse
that's a bit of an impolite thing to say although rest assured once it's finished i'll have to find a platform to upload it to so that it can be accessed and viewed without compression, one individual recommended google photos or documents or something like that lol and indeed i usually enjoy the benefits of high resolution capture for forest and nature based photography as of such i usually utilize it during the daytime so the pixel light collection area size isn't a concern for me personally lol also affirmativ the standardized twelve to twenty four megapixel resolution of most modern camera's likely work for the majority of individuals lol.
^_^
nosidamXumres said:
that's a bit of an impolite thing to say although rest assured once it's finished i'll have to find a platform to upload it to so that it can be accessed and viewed without compression, one individual recommended google photos or documents or something like that lol and indeed i usually enjoy the benefits of high resolution capture for forest and nature based photography as of such i usually utilize it during the daytime so the pixel light collection area size isn't a concern for me personally lol also affirmativ the standardized twelve to twenty four megapixel resolution of most modern camera's likely work for the majority of individuals lol.
^_^
Click to expand...
Click to collapse
Not impolite, blunt.
I don't think it's capable of much greater resolution than it's getting as is.
Grabbing a good sample per pixel is more important than number of pixels.
16mp is a lot.
As is the file size you're going to get with a raw...
nosidamXumres said:
affirmative it's possible as of today, previously the sensors full potential wasn't accessible due to the extensive os and system feature lock downs but even after the phones themselves were capable of being unlocked the sensor still remained unavailable because it has it's own dedicated chipset that has a dedicated partial operation and algorithm system which meant that it couldn't be modified or accessed unless you had very specialized equipment. there's a lot of technical complexity that i've forgoed elaborating upon to keep this response less lengthy lol, at any rate after roughly a year of effort i've finally found a way to bypass all of the restrictions and i'll be potentially publishing the results of the code named C.I.A.R.A. project once my tests are complete and furthermore i may be able to make such feature functionality commercially available and distributable once the project has been thoroughly and fully completed in all of it's entirely lol.
^_^
Click to expand...
Click to collapse
We look forward to your project.
So the code , I take it directly interfaces with the camera or not ?
any elaborations there ?
NEWTINGZ said:
We look forward to your project.
So the code , I take it directly interfaces with the camera or not ?
any elaborations there ?
Click to expand...
Click to collapse
affirmative that is correct traditionally the only information that comes from specifically the one hundred and eight megapixel sensor with moderate exceptions to the others is the data that has been processed by it's onboard algorithm to compress and save space with and roughly the only information going to that sensors chipset is traditionally update and diagnostic information but now that's been technically bypassed utilizing a code and language that unfortunately can only be emulated which makes it very inefficient because it was designed for completely different custom hardware but nonetheless the project is complete, where can i find a compressionless platform to upload and share my photos? also the image's on average are roughly almost a hundred and fifty megabytes including various metadata lol.
^_^
nosidamXumres said:
affirmative that is correct traditionally the only information that comes from specifically the one hundred and eight megapixel sensor with moderate exceptions to the others is the data that has been processed by it's onboard algorithm to compress and save space with and roughly the only information going to that sensors chipset is traditionally update and diagnostic information but now that's been technically bypassed utilizing a code and language that unfortunately can only be emulated which makes it very inefficient because it was designed for completely different custom hardware but nonetheless the project is complete, where can i find a compressionless platform to upload and share my photos? also the image's on average are roughly almost a hundred and fifty megabytes including various metadata lol.
^_^
Click to expand...
Click to collapse
Hey there!
i have been waiting for some update on the project.
This might help-
READ THIS FIRST - Development Rules
I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier Only the following topics are allowed in DEVELOPMENT area: [DEV] - Development for any special...
forum.xda-developers.com
You can create a new thread for the development of the project you have made and store the images in a .zip file and share the file with dropbox, gdrive or mega etc.
(Remember to attach the code, and some information about it in the thread you make.)
M0nK_101 said:
Hey there!
i have been waiting for some update on the project.
This might help-
READ THIS FIRST - Development Rules
I know we all have busy lives and don't have time to go through a list of long winded rules, so here's a shortened version to make your life easier Only the following topics are allowed in DEVELOPMENT area: [DEV] - Development for any special...
forum.xda-developers.com
You can create a new thread for the development of the project you have made and store the images in a .zip file and share the file with dropbox, gdrive or mega etc.
(Remember to attach the code, and some information about it in the thread you make.)
Click to expand...
Click to collapse
thanks for the suggestions i appreciate it, i created a post attaching images and sharing a google drive link lol.
^_^
Thread 's21 ultra 108mp raw' https://forum.xda-developers.com/t/s21-ultra-108mp-raw.4589163/
nosidamXumres said:
thanks for the suggestions i appreciate it, i created a post attaching images and sharing a google drive link lol.
^_^
Thread 's21 ultra 108mp raw' https://forum.xda-developers.com/t/s21-ultra-108mp-raw.4589163/
Click to expand...
Click to collapse
I read your new post and it's amazing
Hopefully, you'll make the new project available to the public soon.
If you want help, there are many individuals on the internet, you don't need to disclose the language used or anything confidential.
All you need to do, is explain the concept of how you made it possible, and probably there will be someone who'll come for the rescue.
one more suggestion -
you can open a github repo, and add the code which you are trying to make (the latest one), there might be someone who could help....
(ty for mentioning me, it's fine ^_^)
also, both communities of rn10pro and s21_ultra can help you, just gotta mention the working and goal of your idea, and it'll work.