Database Users

Camera Hack

As I know, in the Registry
Hkey Local Machine\Software\HTC\Camera\RecParam\MP4Medium
Hkey Local Machine\Software\HTC\Camera\RecParam\MP4Small
I am able to change the factory FrameRate value from 10 to 19...
This is good news
Well, the Medium size is 176x144 pixel and Small size is 128x96 pixel by default.
But!
There is another Key :
Hkey Local Machine\Software\HTC\Camera\RecParam\MP4Large, but I am not able to select Large option in the Camera Settings page, just only Small and Medium.
What shell I have to change in the Registry to make Large videosize available in the Camera Settings page ?
(And what dimension should I use by selecting Large ? 320x240 ?)
THX
mesa

mesa said:
As I know, in the Registry
Hkey Local Machine\Software\HTC\Camera\RecParam\MP4Medium
Hkey Local Machine\Software\HTC\Camera\RecParam\MP4Small
I am able to change the factory FrameRate value from 10 to 19...
This is good news
Well, the Medium size is 176x144 pixel and Small size is 128x96 pixel by default.
But!
There is another Key :
Hkey Local Machine\Software\HTC\Camera\RecParam\MP4Large, but I am not able to select Large option in the Camera Settings page, just only Small and Medium.
What shell I have to change in the Registry to make Large videosize available in the Camera Settings page ?
(And what dimension should I use by selecting Large ? 320x240 ?)
THX
mesa
Click to expand...
Click to collapse
You can not. there is no 320X240 in Charmer's Video Camera application.
But you can use "CoolCamera" for even 640X480 in video mode.
download it from here: http://www.ateksoft.com/files/CoolCamera.cab

HTC Camera Burst Mode Hack

I found a hack, to change number of photos taken in burst mode.
Create new key in registry:
HKLM\Software\HTC\Camera\Image
New DWORD Key:
DefBurstMaxCount
And set value to:
60
(60 - in DEC)
Might be other value than 60 (Program default is 30). I even tried with 512 and it worked well.
Cheers!

Burst mode, what does it really do?
Is it usable on Universal?

Yes, this mode is usable in Universal
In burst mode you can take photos continuously.... such as slide show

HTC Burst mode
I would love to be able to get my Topaz to make time lapse photos, but none of the java apps seem to work for me. The Burst mode is almost exactly what I need, but I can't get the DefBurstMaxCount to go above 32, it just crashes after that.
Does anyone know the secret for taking a very large number of Burst photos?
Thanks
Ben

Will try it out. Sounds inteesting . Thanks for sharing...

Burst mode is awesome! Its set to 30 and this is a great hack. Thanks I am going to give it a try.

adexxx said:
I found a hack, to change number of photos taken in burst mode.
Create new key in registry:
HKLM\Software\HTC\Camera\Image
New DWORD Key:
DefBurstMaxCount
And set value to:
60
(60 - in DEC)
Might be other value than 60 (Program default is 30). I even tried with 512 and it worked well.
Cheers!
Click to expand...
Click to collapse
NOT working on my HD2
How do you enable this mode? In camera settings?

dragmark said:
NOT working on my HD2
How do you enable this mode? In camera settings?
Click to expand...
Click to collapse
Same here!

adexxx said:
I found a hack, to change number of photos taken in burst mode.
Create new key in registry:
HKLM\Software\HTC\Camera\Image
New DWORD Key:
DefBurstMaxCount
And set value to:
60
(60 - in DEC)
Might be other value than 60 (Program default is 30). I even tried with 512 and it worked well.
Cheers!
Click to expand...
Click to collapse
Hi,
I have changed the registry settings, so i have the options for burst, sports mode etc, but none of them works.
Could someone help?
Burst mode sais accesss to file denied, sports mode simply doesn't take pics.
Interesting in the top right corner it shows thousands of more photos can be stored on the card.
Is this in connection with resolution.
Does the burst mode take 5mp pics?
Thanks a LOT.

I think it's related to resolution. I use HD Tweak on my HTC Touch HD and this application enbales the hidden camera modes: burst and sports. The default setting for this modes is 1 mp and highest is 3 mp. I can't take pictures with a higher resolution on these modes

dragmark said:
NOT working on my HD2
How do you enable this mode? In camera settings?
Click to expand...
Click to collapse
same here too

Didn't have luck either with burst mode and sports but i found a cab file somewhere (can't remember where) that activates Picture Theme mode and it's working perfectly.

These keys all work on my diamond
To Enable 'Burst': HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P6 -> change the value "enabled" from 0 to 1
To Enable 'Sport': HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P8 -> change the value "enabled" from 0 to 1
To Enable 'Video Share': HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P9 -> change the value "enabled" from 0 to 1
To Enable GPS : HKEY_LOCAL_MACHINE\SOFTWARE\HTC\Camera\P10 -> change the value "enabled" from 0 to 1

Tip for browsing with Opera Mobile 9.7 on the HD

Adaptive Zoom
Don’t want to zoom to click a link? Try this..
1. Open opera’s preference editor by going to the following link:
opera:config
Note there is no http:// proceeding the link.
2. Click on Adaptive Zoom and try the following settings:
Browser Buffer Height = 4096
Browser Buffer Width = 800
Maximum Zoom = 100
Minimum Overview Zoom = 100
Minimum Zoom = 100
Virtual Screen Width = 800
Zoom Slider Maxinmum = 200
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.

Slothie said:
Adaptive Zoom
Don’t want to zoom to click a link? Try this..
1. Open opera’s preference editor by going to the following link:
opera:config
Note there is no http:// proceeding the link.
2. Click on Adaptive Zoom and try the following settings:
Browser Buffer Width = 800
Maximum Zoom = 100
Minimum Overview Zoom = 100
Minimum Zoom = 100
Virtual Screen Width = 800
Zoom Slider Maxinmum = 200
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.
Click to expand...
Click to collapse
Hi,
thanks for the Tip ... but,
In 9.7b1 I can't find:
- Maximum Zoom
- Maximum Overview Zoom
- Minimum Zoom
- Zoom Slider Maximum
in 9.5 they exist but not in 9.7

not sure if it's something i've done, but after making those changes i can't launch Opera any more!!
I get the htc loading page for about about 20 seconds and then it just closes - anyone else had this problem or know how to solve?

Slothie said:
Adaptive Zoom
Don’t want to zoom to click a link? Try this..
1. Open opera’s preference editor by going to the following link:
opera:config
Note there is no http:// proceeding the link.
2. Click on Adaptive Zoom and try the following settings:
Browser Buffer Height = 4096
Browser Buffer Width = 800
Maximum Zoom = 100
Minimum Overview Zoom = 100
Minimum Zoom = 100
Virtual Screen Width = 800
Zoom Slider Maxinmum = 200
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.
Click to expand...
Click to collapse
It also makes the text tiny.
Does anyone have the original settings please, stupidly I did not note them down.

MaskedMarauder said:
It also makes the text tiny.
Does anyone have the original settings please, stupidly I did not note them down.
Click to expand...
Click to collapse
In Opera 9.5 i have the following settings which allow me to open links without zooming. Min overview zoom is the only changed variable.
Browser Buffer Height = 1400
Browser Buffer Width = 960
Maximum Zoom = 200
Minimum Overview Zoom = 85
Minimum Zoom = 160
Virtual Screen Width = 960
Zoom Slider Maxinmum = 500

So will altering these settings change the width of text elements and reduce the amount of zoom? I'm running this on an HX4700 with a 4.0" screen (I know, I'm getting my touch HD in less than 30 hours). When the zoom action happens, it automatically zooms to the width of the column element (ingenious) so I can scroll throught he column without side scrolling. However the width of the elements are too narrow and as such causes the zoom to be too high. I'd like to use the 4" display and VGA rez to read smaller but more amount of text.

I've no idea mate sorry. I just copies and writes up what i sees

MaskedMarauder said:
Does anyone have the original settings please, stupidly I did not note them down.
Click to expand...
Click to collapse
Just noted these down from my new HD, here they are:
Browser Buffer Height = 1400
Browser Buffer Width = 960
Maximum Zoom = 200
Minimum Overview Zoom = 60
Minimum Zoom = 160
Virtual Screen Width = 960
Zoom Slider Maxinmum = 500

Thank you very much saad.salman & Freypal

i've been looking for that setting (minimum overview zoom) for a while - cheers!!

Riceburner said:
i've been looking for that setting (minimum overview zoom) for a while - cheers!!
Click to expand...
Click to collapse
it doesn't work in Diamond 2 Opera ><

nick666 said:
not sure if it's something i've done, but after making those changes i can't launch Opera any more!!
I get the htc loading page for about about 20 seconds and then it just closes - anyone else had this problem or know how to solve?
Click to expand...
Click to collapse
Get a hold of opera.ini >>windows>opera9
edit the file, the first few lines are the ones you will need to change.
Just copied this from mine..
[Adaptive Zoom]
Minimum Zoom=160
Minimum Overview Zoom=70
Browser Buffer Height=1400
Browser Buffer Width=960
Maximum Zoom=200
Virtual Screen Width=960
Zoom Slider Maximum=500
after changing back, having had the same problem you did...
Good Luck

Slothie said:
This should set your screen up so it no long needs to zoom to click a link but also makes the virtual page width the same size as the screen in landscape mode.
Click to expand...
Click to collapse
Just note that with this tweak you will lose the ability to trigger mouseover action for links.

Neville.Holland said:
Get a hold of opera.ini >>windows>opera9
edit the file, the first few lines are the ones you will need to change.
Just copied this from mine..
[Adaptive Zoom]
Minimum Zoom=160
Minimum Overview Zoom=70
Browser Buffer Height=1400
Browser Buffer Width=960
Maximum Zoom=200
Virtual Screen Width=960
Zoom Slider Maximum=500
after changing back, having had the same problem you did...
Good Luck
Click to expand...
Click to collapse
I had the same problem but I can't find the file I can't search my phone's files either...

Ekkoe said:
I had the same problem but I can't find the file I can't search my phone's files either...
Click to expand...
Click to collapse
I could only imagine it being in the one of the following
\Windows
\Windows\Opera
Possible \Application Data but unlikely I think.
I'm running the standard 6.1 HTC original ROM.

Forget all that. Everything is running. It didn't go as smooth and understandable as I might have hoped, but it works now. Thanks!

Opera: What is your "Zoom Slider Maximum" Set to?

I lost the default value for opers 9.7 Zoom Slider Maximum. Can someone tell me what it is?
It can be found under
HKLM > software > opera > pref > adaptive zoom.
The reason I am looking for this is because when ever I double tap to zoom in on a picture, the pictures get really pixellated. This means that I am going past the actually size of the picture's resolution.
Thank you.

rebump. 24 hr.

hklm/software/opera/prefs/adaptive zoom
Default Zoom - 175
Virtual Scr Width - 800
Zoom Max - 500

[Camera][MOD][2.2.2016][MORE DETAIL, MORE LIGHT][MM base][AROMA][ONLY OP DISCOUNTED]

First of all, I would like to thank all those guys from "Photos Taken With M9" thread.
HUGE GREAT BIG AWESSOME THANKS go to @starbase64 ; @defcomg ; @hamdir !!!
SO THANK YOU MATES!!!!​
{
"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"
}
Since HTC made a bad software, that compress data from chip and creates jpeg, many of us hoped for something new, something better. With every update we prayed for better noise control. Some prays were heard, some were not. Theese hard times a few heroes, that see thru codes and hacks found a way how to make our photos better. Enough talks, lets go for it!
DISCLAIMER: I AM NOT RESPONSIBLE FOR ANY DAMAGE YOU DO TO YOUR PHONE USING SOME OF THIS HACKS
SINCE I HAVE NO MORE M9 DEVICE AND NO TIME FOR TESTING AND SO, I AM FORCED TO DO LAST UPDATE HERE IN THIS THREAD. I WOULD BE PLEASED, IF SOMEONE TAKE THIS AFTER ME AND MAYBE START A NEW, CLEAR THREAD FOR MM. ANYWAY I ADD HERE NEWEST MOD FOR MM. THANK YOU GUYS, IT WAS A PLEASURE WORKING WITH YOU! YOU ARE THE BEST
CAMERA MOD LIBS FOR HTC ONE M9 ON MARSHMALLOW
FLASHABLE ZIP HERE!! HIT THANX OR DIE!
http://forum.xda-developers.com/showpost.php?p=65083400&postcount=458
DOWNLOAD HERE! DONE FORGET TO HIT THANX!!!:
http://forum.xda-developers.com/showpost.php?p=65075578&postcount=434
PREVIEW HERE! ALSO HIT THANX!!!:
http://forum.xda-developers.com/showpost.php?p=65037806&postcount=431
VIDEO HOW TO INSTALL VIA ROOT EXPLORER HERE!! HIT LIKE ON YOUTUBE!!! ITS FREE!!!
OLD MOD FOR LAST LOLLIPOP
HW DENOISE AND 9 SECONDS OF EXPOSURE TIME
COMPATIBILITY:
This mod is TESTED on base 2.10.401.1
and it works on that base
INSTALATION:
Download attached HTCOneM9_CameraMods_v1.04.zip attached below.
Reboot to recovery
FLASH the mods that you want.
Reboot
Enjoy!!!
@hamdirs HUGE TEST FOR DENOISE HERE!!!---->CLICK!!!
HIT THANX on his post
My camera settings:
10:7 ratio
big resolution
contrast +0,5
saturation +0,5
sharpeness -1
Since we have new awessome HW denoise mod, I dont use to use any of build.prop tweaks.
@defcomg THANK YOU FOR YOUR HUGE CODE RESEARCH!!!
@hamdir THANK YOU FOR YOUR HUGE TEST RESEARCH!!!
@starbase64 THANK YOU FOR YOUR OVERALL SUPPORT!!!
@jsaxon2 THANK YOU FOR CREATING AROMA INSTALLER FILE TO MAKE INSTALL MORE EASIER
THANK YOU GUYS. IT WAS A PLEASURE.​

@m4jkee great thread mate but are we sure we can disable both htc denoise and apply denoise persist in the same time?
actually i am not sure if these work at all on the 2.10 pure base

hamdir said:
@m4jkee great thread mate but are we sure we can disable both htc denoise and apply denoise persist in the same time?
Click to expand...
Click to collapse
I dont know exactly but I guess denoise persist dont aply on recorded videos. Disabling htc denoise made my lowlight videos more noisy. I will test it later today and post results. thank you for reply

Is that zip flashable?
Ok I see its not. Where do the files go?
Or could u even make flashable zip?

Huge thanks for your efforts mates @hamdir @m4jkee @starbase64 @defcomg :good:

Mostafa Wael said:
Huge thanks for your efforts mates @hamdir @m4jkee @starbase64 @defcomg :good:
Click to expand...
Click to collapse
Guys the settings all together create a conflict, especially the sub pixel setting
The persist.camera.snap.format = 1 creates terrible color noise in low light and destroys what we are trying to achieve here so I don't think this line should be added
I am doing some tests to figure out the best combo and will share my conclusion, but so far I am seeing very definite Improvement by simply removing the sub pixel line

hamdir said:
Guys the settings all together create a conflict, especially the sub pixel setting
The persist.camera.snap.format = 1 creates terrible color noise in low light and destroys what we are trying to achieve here so I don't think this line should be added
I am doing some tests to figure out the best combo and will share my conclusion, but so far I am seeing very definite Improvement by simply removing the sub pixel line
Click to expand...
Click to collapse
try this
Code:
persist.camera.HAL3.enabled=1
Dload
freedcam
Settings > camera api > camera2
check by info overlay if it says legacy , limited or full?

defcomg said:
try this
Code:
persist.camera.HAL3.enabled=1
Dload
freedcam
Settings > camera api > camera2
check by info overlay if it says legacy , limited or full?
Click to expand...
Click to collapse
Added the Line, camera and freedcam force close on me. Camera fv-5 viewfinder hang. Check on manual camera compatibility it says Full.

xunus said:
Added the Line, camera and freedcam force close on me. Camera fv-5 viewfinder hang. Check on manual camera compatibility it says Full.
Click to expand...
Click to collapse
install this version https://drive.google.com/file/d/0B5NJTB9bLPdsQmdKR2NIZkdEUEU/view?usp=sharing clear data
make a folder named DEBUG in /DCIM/FreeDcam it should log the crash alternative normal logcat should suffice then we can see why camera 2 api crash

defcomg said:
install this version https://drive.google.com/file/d/0B5NJTB9bLPdsQmdKR2NIZkdEUEU/view?usp=sharing clear data
make a folder named DEBUG in /DCIM/FreeDcam it should log the crash alternative normal logcat should suffice then we can see why camera 2 api crash
Click to expand...
Click to collapse
Here it is.

xunus said:
Here it is.
Click to expand...
Click to collapse
Crash todo with MF lemme disable it quick and rebuild
EDIT: Added updated apk @xunus try this apk

defcomg said:
Crash todo with MF lemme disable it quick and rebuild
EDIT: Added updated apk @xunus try this apk
Click to expand...
Click to collapse
I renamed to .apk due to file size.

xunus said:
I renamed to .apk due to file size.
Click to expand...
Click to collapse
what happend on last try apk from logcat it seems camera started

defcomg said:
what happend on last try apk from logcat it seems camera started
Click to expand...
Click to collapse
no preview for me, and crash on press shutter

starbase64 said:
no preview for me, and crash on press shutter
Click to expand...
Click to collapse
i see lets call @troopii to look at http://forum.xda-developers.com/showpost.php?p=63189969&postcount=12
i don't know much about camera 2 part of freedcam from the log seem to be looping on
Code:
Line 161680: 2015-10-08 08:41:15:E/freedcam.BaseCameraHolderApi2(25357): Couldn't find any suitable previewSize size
hopefully he will know whats up

defcomg said:
try this
Click to expand...
Click to collapse
my interest is currently focused on the HTC camera app and these tweaks, tested in low light on pure 2.10 base
persist.camera.qcwnr.enabled=0
This is essential if we want any control over the way the M9 deals with noise, if we don't use this line denoise will remain the same and the persist.denoise.process.plates below will not have any effect, this is the line with the most clear change, once we use it, HTC's famous smudging will disappear and will get much more detailed images instead at the cost of apparent color and luma noise especially in low light
camera.eis.enable=0
Well this will disable HTC's weird EIS effect and instead we will have motion blur, without OIS the M9 is very weak in getting stable shots in low light, so either way it's a loss, disabling EIS however can be beneficial for shots with better light
persist.camera.snap.format=1
This has little effect unless we disable HTC's denoise using persist.camera.qcwnr.enabled=0, once we do persist.camera.snap.format=1 will cause a clear change, however the results of the value 1 and disabled HTC smudging are terrible, it creates extreme color noise even in medium light plus unstable pixel patterns, we should not use this line, it also cause color damage to the thumbnails
persist.denoise.process.plates=0
once we disable HTC denoise using persist.camera.qcwnr.enabled=0, these controls will work but the change is minimal, naturally 0 or 1 are the better values since they prioritize quality but they do at the cost of speed which the M9 already suffers from in low light (the image will take a longer while to be saved in gallery), so i suggest going to 0 or 1 only if we are using locking at least ISO400 and not 200 (to keep the shutter a little faster), 0 seems to use Android's built-in general quality denoise, while 1 will only deal with the color components without touching the grey scale image more here, result is that you will have higher amount of dark noise but will look slightly more detailed, you can really use any of the values to your preference (quality vs speed, full denoise vs color denoise) but keep in mind Android's built-in denoise is not that great either, in extreme low light we will still see terrible color noise due to the tiny pixel nature of our sensor (which explains why HTC went so insane with their own smudging)
in fact the denoise plates are actually exaggerating the fine nature of the tiny pixel noise! does anyone know how to disable them completely?
currently this combo works:
persist.camera.qcwnr.enabled=0
camera.eis.enable=0
# persist.camera.snap.format=1 (not using this line)
persist.denoise.process.plates=0
but it still doesn't match Freedcam's pre 5.1 denoise disable (which gave us pure noise from the sensor like RAW), we need a way to disable both HTC denoise and the plates together if we want match that
finally we should remember both ISO and Sharpness settings have direct effect into the pixel quality as well, since the sharpness code also have some denoise of it's own and naturally the higher ISO the more noise, anything higher than 400 becomes crazy in noise, thankfully the M9 sensor is low ISO friendly (i mean you can take bright low light images even with ISO400)
my current settings are middle ground:
- Sharpness -1
- Max ISO400
essentially my recommendation is this:
persist.camera.qcwnr.enabled=0
camera.eis.enable=0
persist.denoise.process.plates=0
Sharpness -1
Max ISO400
Click to expand...
Click to collapse
DO NOT add the line persist.camera.snap.format=1 or persist.camera.snap.format=0
we end with something similar or even better than the OP2 auto mode
color noise is evident the higher the ISO (at 1600 it becomes extreme) but around ISO200/400 we will get great image with faint apparent noise, which is much better than HTC's default smudge fest
samples and comparison photos here
I still think @Almalence post process tech like the OP2 clear image is lot more beneficial than all this non sense:
http://forum.xda-developers.com/showpost.php?p=63176700&postcount=30248

I may be a bit rude with this request @hamdir
But can we have some comparing samples?!
EDIT: Never mind, i just applied the tweaks
Looking obviously improved already in daily light :good:

Mostafa Wael said:
I may be a bit rude with this request @hamdir
But can we have some comparing samples?!
Click to expand...
Click to collapse
the problem is that late night yest i did like a hundred test and i didnt organize them in any way for me today to use in a comparison
now that i know the results, i will try to take samples later tonight
---------- Post added at 10:46 AM ---------- Previous post was at 10:33 AM ----------
Mostafa Wael said:
EDIT: Never mind, i just applied the tweaks
Looking obviously improved already in daily light :good:
Click to expand...
Click to collapse
that's more like it
can you supply some samples
it basically saves you the bother of relying on RAW mode for better shots all the time, plus it actually improves HDRs the most (since the merge effect was most harmed by the smudging)

@m4jkee why did you improvise mate i said dont use the line, not set it to 0 originally this commit was added by Google for test reason
i tested it with 0 and it still does the same damage, without the line at ISO400 there is no color noise
can someone help here?
https://android.googlesource.com/platform/hardware/qcom/camera/+/1c6f92e
QCamera2: set snapshot format to YUV422 when system prop is set
Per test request, when system prop "persist.camera.snap.format" is
set to 1, snapshot format should be set to YUV422.
CRs-Fixed: 462490
Change-Id: Idd353f90338b595096622bebbeda59a46e578693
Click to expand...
Click to collapse
Change-Id: Idd353f90338b595096622bebbeda59a46e578693
diff --git a/camera/QCamera2/HAL/QCameraParameters.cpp b/camera/QCamera2/HAL/QCameraParameters.cpp
index 91f01cf..0b8c17e 100644
--- a/camera/QCamera2/HAL/QCameraParameters.cpp
+++ b/camera/QCamera2/HAL/QCameraParameters.cpp
@@ -4730,7 +4730,16 @@
if ( mPictureFormat == CAM_FORMAT_YUV_422_NV16 ) {
format = CAM_FORMAT_YUV_422_NV16;
} else {
- format = CAM_FORMAT_YUV_420_NV21;
+ char prop[PROPERTY_VALUE_MAX];
+ int snapshotFormat;
+ memset(prop, 0, sizeof(prop));
+ property_get("persist.camera.snap.format", prop, "0");
+ snapshotFormat = atoi(prop);
+ if(snapshotFormat == 1) {
+ format = CAM_FORMAT_YUV_422_NV61;
+ } else {
+ format = CAM_FORMAT_YUV_420_NV21;
+ }
}
break;
case CAM_STREAM_TYPE_VIDEO:
Click to expand...
Click to collapse

as i understood it, it returns then always a yuv frame.
--edit;
im wrong when that flag is set the output yuvformat is forced to yuv422 nv16. thats for preview
if not its set to nv21. but not sure whats the big difference is. only thing i know is that it must set to nv21 for 4kuhd on g3.
when its set to nv21 the thumb images returned from cam have crazy colors. but full size image is normal.
public static final int NV16
Added in API level 8
YCbCr format, used for video.
For the android.hardware.camera2 API, the YUV_420_888 format is recommended for YUV output instead.
Whether this format is supported by the old camera API can be determined by getSupportedPreviewFormats().
Constant Value: 16 (0x00000010)
public static final int NV21
Added in API level 8
YCrCb format used for images, which uses the NV21 encoding format.
This is the default format for Camera preview images, when not otherwise set with setPreviewFormat(int).
For the android.hardware.camera2 API, the YUV_420_888 format is recommended for YUV output instead.
Constant Value: 17 (0x00000011)
Click to expand...
Click to collapse