RAW image/Adobe issue. - Nexus 6P Q&A, Help & Troubleshooting

Every one of the RAW images I've taken with this device, regardless of the camera app, produces a dark line on the far right when viewed in Lightroom and Photoshop. Anyone else experience this? I've tried more than one manual camera app with the same result, but it does seem that the Snapseed app can see and edit the DNG on the phone without the green line present. Leads me to believe this is some kind of issue with Adobe so just wondered if anyone else had encountered it. I also tried disabling any import presets but that didn't change anything. Have a look at the attached samples to see what I mean.
{
"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"
}

I have encountered it, but I have not tried to fix it. Sorry.
I am also not convinced it is an Adobe issue. Open some of the DNGs in explorer, they should be around 25 megabytes give or take. But I often see them as low as 2 kilobyes, obviously that isn't right so there must be something else along the chain wrong.

staticx57 said:
I have encountered it, but I have not tried to fix it. Sorry.
I am also not convinced it is an Adobe issue. Open some of the DNGs in explorer, they should be around 25 megabytes give or take. But I often see them as low as 2 kilobyes, obviously that isn't right so there must be something else along the chain wrong.
Click to expand...
Click to collapse
Ok I don't seem to be having that issue luckily. But as a further test I downloaded a simple Windows conversion utility last night and used it to convert one of the DNG files to JPG and it worked fine. I mean, the colours and general processing were absolute crap, but there was no dark line so whatever problem I'm having certainly doesn't appear to be with the RAW file from the 6P. And as I said, Snapseed edits them without a problem.
After work today I'll post in the Adobe support forums and see if I get any information there.

evo5ive said:
Every one of the RAW images I've taken with this device, regardless of the camera app, produces a dark line on the far right when viewed in Lightroom and Photoshop. Anyone else experience this? I've tried more than one manual camera app with the same result, but it does seem that the Snapseed app can see and edit the DNG on the phone without the green line present. Leads me to believe this is some kind of issue with Adobe so just wondered if anyone else had encountered it. I also tried disabling any import presets but that didn't change anything. Have a look at the attached samples to see what I mean.
Click to expand...
Click to collapse
can upload sample raw file

defcomg said:
can upload sample raw file
Click to expand...
Click to collapse
Sure, try these. Just ran a few more tests and it seems Snapseed is in fact picking up the dark band. BUT, when I shoot either the standard camera app or output to JPG in the manual apps the resulting images do NOT show the dark band. Seems to be a problem that only occurs when the device saves the RAW file.
Uploaded from my PC
Uploaded from phone

evo5ive said:
Sure, try these. Just ran a few more tests and it seems Snapseed is in fact picking up the dark band. BUT, when I shoot either the standard camera app or output to JPG in the manual apps the resulting images do NOT show the dark band. Seems to be a problem that only occurs when the device saves the RAW file.
Uploaded from my PC
Uploaded from phone
Click to expand...
Click to collapse
The Problem is the Active Area DNG Tag the darker area should not be visible somehow Active Area Tag is conflicting with Default crop size tag http://www.barrypearson.co.uk/articles/dng/specification.htm. dcraw based apps seem to use active area tag and ignore the default crop tag so the band is not visible
6P DNG Header
Code:
ExifTool Version Number : 9.69
File Name : ProShot_20151126_143708.dng
Directory : C:/Users/GeorgeKiarie/Downloads
File Size : 24 MB
File Modification Date/Time : 2015:11:26 22:20:33+02:00
File Access Date/Time : 2015:11:26 22:17:54+02:00
File Creation Date/Time : 2015:11:26 22:17:54+02:00
File Permissions : rw-rw-rw-
File Type : DNG
MIME Type : image/x-adobe-dng
Exif Byte Order : Little-endian (Intel, II)
Subfile Type : Full-resolution Image
Image Width : 4080
Image Height : 3028
Bits Per Sample : 16
Compression : Uncompressed
Photometric Interpretation : Color Filter Array
Make : Huawei
Camera Model Name : Nexus 6P
Strip Offsets : (Binary data 25901 bytes, use -b option to extract)
Orientation : Horizontal (normal)
Samples Per Pixel : 1
Rows Per Strip : 1
Strip Byte Counts : (Binary data 15139 bytes, use -b option to extract)
X Resolution : 72
Y Resolution : 72
Planar Configuration : Chunky
Resolution Unit : inches
Software : google/angler/angler:6.0/MDB08L/2343525:user/release-keys
Modify Date : 2015:11:24 01:13:03
XMP Toolkit : Adobe XMP Core 5.6-c011 79.156380, 2014/05/21-23:38:37
Creator Tool : google/angler/angler:6.0/MDB08L/2343525:user/release-keys
Rating : 0
Metadata Date : 2015:11:26 14:46:24-04:00
Date Created : 2015:11:24 01:13:03
Document ID : E76921AC715FABD3C153F15B23AEEA74
Original Document ID : E76921AC715FABD3C153F15B23AEEA74
Instance ID : xmp.iid:42b35b1d-eeff-ea44-a7be-becf042fbc8c
Format : image/dng
Raw File Name : ProShot_20151126_143708.dng
Version : 9.3
Has Settings : False
Has Crop : False
Already Applied : False
Photographic Sensitivity : 100
History Action : saved
History Instance ID : xmp.iid:42b35b1d-eeff-ea44-a7be-becf042fbc8c
History When : 2015:11:26 14:46:24-04:00
History Software Agent : Adobe Photoshop Camera Raw 9.3 (Windows)
History Changed : /metadata
CFA Repeat Pattern Dim : 2 2
CFA Pattern 2 : 0 1 1 2
Exposure Time : 1/110
F Number : 2.0
Exif Version : 0221
Shutter Speed Value : 1/110
Aperture Value : 2.0
GPS Version ID : 2.3.0.0
GPS Latitude Ref : North
GPS Longitude Ref : West
GPS Time Stamp : 18:37:11
GPS Date Stamp : 2015:11:26
ISO : 100
Date/Time Original : 2015:11:24 01:13:03
Focal Length : 4.7 mm
TIFF-EP Standard ID : 1 0 0 0
DNG Version : 1.4.0.0
DNG Backward Version : 1.1.0.0
Unique Camera Model : Nexus 6P-Huawei-google
CFA Plane Color : Red,Green,Blue
CFA Layout : Rectangular
Black Level Repeat Dim : 2 2
Black Level : 52 52 52 52
White Level : 1023
Default Scale : 1 1
Default Crop Origin : 8 8
Default Crop Size : 4016 3008
Color Matrix 1 : 0.8125 -0.2265625 -0.125 -0.3203125 1.265625 0.0390625 -0.0390625 0.2265625 0.453125
Color Matrix 2 : 1.0078125 -0.2890625 -0.21875 -0.5625 1.6328125 -0.046875 -0.0703125 0.2109375 0.640625
Camera Calibration 1 : 1 0 0 0 1 0 0 0 0.9921875
Camera Calibration 2 : 1 0 0 0 1 0 0 0 0.9921875
As Shot Neutral : 0.46875 1 0.6328125
Calibration Illuminant 1 : D65
Calibration Illuminant 2 : Standard Light A
Active Area : 2 48 3026 4080
Forward Matrix 1 : 0.578125 0.21875 0.1640625 0.15625 0.84375 0 -0.015625 -0.2890625 1.1328125
Forward Matrix 2 : 0.6875 0.015625 0.265625 0.2109375 0.6796875 0.1015625 0 -0.5390625 1.3671875
Opcode List 2 : (Binary data 3908 bytes, use -b option to extract)
Opcode List 3 : (Binary data 4 bytes, use -b option to extract)
Noise Profile : 0.00020673168 1.8208447e-006 0.00020673168 1.8208447e-006 0.00020673168 1.8208447e-006
Aperture : 2.0
CFA Pattern : [Red,Green][Green,Blue]
GPS Date/Time : 2015:11:26 18:37:11Z
GPS Latitude : 13 deg 4' 13.48" N
GPS Longitude : 59 deg 33' 59.05" W
GPS Position : 13 deg 4' 13.48" N, 59 deg 33' 59.05" W
Image Size : 4080x3028
Shutter Speed : 1/110
Focal Length : 4.7 mm
Light Value : 8.8
Moto Nexus 6 DNG Header
Code:
ExifTool Version Number : 9.69
File Name : paraiso.dng
Directory : C:/Users/GeorgeKiarie/Pictures/DNG/other
File Size : 25 MB
File Modification Date/Time : 2015:08:04 02:07:42+02:00
File Access Date/Time : 2015:08:04 02:04:32+02:00
File Creation Date/Time : 2015:08:04 02:04:32+02:00
File Permissions : rw-rw-rw-
File Type : DNG
MIME Type : image/x-adobe-dng
Exif Byte Order : Little-endian (Intel, II)
Subfile Type : Full-resolution Image
Image Width : 4208
Image Height : 3120
Bits Per Sample : 16
Compression : Uncompressed
Photometric Interpretation : Color Filter Array
Image Description :
Make : motorola
Camera Model Name : Nexus 6
Strip Offsets : (Binary data 26769 bytes, use -b option to extract)
Orientation : Horizontal (normal)
Samples Per Pixel : 1
Rows Per Strip : 1
Strip Byte Counts : (Binary data 15599 bytes, use -b option to extract)
X Resolution : 72
Y Resolution : 72
Planar Configuration : Chunky
Resolution Unit : inches
Software : google/shamu/shamu:5.0/LRX21O/1570415:user/release-keys
Modify Date : 1970:01:22 17:47:12
CFA Repeat Pattern Dim : 2 2
CFA Pattern 2 : 2 1 1 0
Copyright :
Exposure Time : 1/1653
F Number : 2.0
ISO : 40
Date/Time Original : 1970:01:22 17:47:12
Focal Length : 3.8 mm
TIFF-EP Standard ID : 1 0 0 0
DNG Version : 1.4.0.0
DNG Backward Version : 1.1.0.0
Unique Camera Model : Nexus 6-motorola-google
CFA Plane Color : Red,Green,Blue
CFA Layout : Rectangular
Black Level Repeat Dim : 2 2
Black Level : 64 64 64 64
White Level : 1023
Default Scale : 1 1
Default Crop Origin : 8 8
Default Crop Size : 4200 3112
Color Matrix 1 : 0.6953125 -0.0859375 -0.09375 -0.4609375 1.296875 0.1328125 -0.109375 0.2578125 0.5390625
Color Matrix 2 : 1.21875 -0.4296875 -0.25 -0.4609375 1.5 0.015625 -0.046875 0.21875 0.609375
Camera Calibration 1 : 1 0 0 0 1 0 0 0 1
Camera Calibration 2 : 1 0 0 0 1 0 0 0 1
As Shot Neutral : 0.5390625 1 0.6640625
Calibration Illuminant 1 : D65
Calibration Illuminant 2 : Standard Light A
Forward Matrix 1 : 0.7578125 0.0859375 0.1171875 0.2734375 0.828125 -0.1015625 0.015625 -0.28125 1.0859375
Forward Matrix 2 : 0.6328125 0.046875 0.28125 0.1640625 0.7578125 0.078125 -0.046875 -0.640625 1.5078125
Opcode List 2 : (Binary data 3908 bytes, use -b option to extract)
Noise Profile : 0.00051471478 0 0.00051471478 0 0.00051471478 0
Aperture : 2.0
CFA Pattern : [Blue,Green][Green,Red]
Image Size : 4208x3120
Shutter Speed : 1/1653
Focal Length : 3.8 mm
Light Value : 14.0
when opening nexus 6 dng in PS /LR the image res is 4200 x 3112 but on dcraw based apps res is 4208 x 3120 now had moto added Active area tag i believe there would have been a dark area on pixels that go past 4200.
on lightroom pc DNG Recover Edge plugin should make it go away .
it would be interseting to see how the header of a 5x or 6p without that issue looks like

defcomg said:
The Problem is the Active Area DNG Tag the darker area should not be visible somehow Active Area Tag is conflicting with Default crop size tag http://www.barrypearson.co.uk/articles/dng/specification.htm. dcraw based apps seem to use active area tag and ignore the default crop tag so the band is not visible
when opening nexus 6 dng in PS /LR the image res is 4200 x 3112 but on dcraw based apps res is 4208 x 3120 now had moto added Active area tag i believe there would have been a dark area on pixels that go past 4200.
on lightroom pc DNG Recover Edge plugin should make it go away .
it would be interseting to see how the header of a 5x or 6p without that issue looks like
Click to expand...
Click to collapse
Very interesting, thanks for that. I'll look into that plugin for sure. So I'm assuming the problem lies in the RAW tag generated by the phone, and if that's the case it means it could be fixed with a simple software patch, correct? Just trying to get my info straight so I can submit a bug report to Google. (Bit embarrassed to admit that I'm a photographer by profession yet know very little about the technical workings of RAW formats )

evo5ive said:
Very interesting, thanks for that. I'll look into that plugin for sure. So I'm assuming the problem lies in the RAW tag generated by the phone, and if that's the case it means it could be fixed with a simple software patch, correct? Just trying to get my info straight so I can submit a bug report to Google. (Bit embarrassed to admit that I'm a photographer by profession yet know very little about the technical workings of RAW formats )
Click to expand...
Click to collapse
yeah its a simple software issue that can be rectified with a patch

Related

Newest camera 2.70.0.21104 and modified album

Hi,
Just wanted to share the latest camera app with you.
Originaly it was a german version but I made it english.
Also I changed album.exe and put a Exit command in the
menu.
First you need to install Camera_Wizard_Magician_T-Mobile_WWE_RC28_Customize.CAB
Then overwrite both camera.exe, album_res.dll and album.exe from camera_album.zip.
These 3 files are upx-ed to save memory.
The camera.exe is from Camera_Wizard_Magician_T-Mobile_GER_RC29_Customize.cab (version 2.70.0.21104)
One thing that still is bad is when the camera ambience is in Auto.
It still is not working as it should. Better operate the Ambience in
DayLight or Night mode.
The magician can have 2 kinds of image sensors. Mine uses hklm\drivers\builtin\camera_sensor1.
You can fiddle with the LightSensorHz a bit. Default it is set to "50" but you can try "0" or "100".
Could not find much difference.
You can check which camera_sensor driver is active by going into
hklm\driver\active and look for Name: CAM1: or CAM2: (CAM2: in my case at key 25)
Some other camera related tweaks (decimal dwords):
hklm\software\drivers\camera\Property\02 (or 01 in case of CAM1
brightness 6
contrast 5
hue 5
saturation 4
sharpness 6
hklm\software\HTC\Camera\AppDefSettings
country 2 determines the display rotation on camera start
flashlight 0 can be set to 1 but you don´t have one
hklm\software\HTC\Camera\AppDefSettings\common
fontcolor 00ff00 rgb values for osd
keycolor 080c08 rgb
hklm\software\HTC\Camera\AppDefSettings\general
brightness 6
contrast 5
hue 5
saturation 4
sharpness 6
EnableCallBack 1 some calibration value osd
EnableFrameRate 1 osd actual framerate
EnableDayTimePath 0 creates subdirs in my documents\my pictures if 1
EnableHopper 0 test/debug program called hopper.exe
EnableIPSM 0 enable IP Streaming Media, never got it workin anyhow
hklm\software\HTC\Camera\captparam
captureduration 60 force recording time to be 60 seconds
delaytime 10 dunno. 10 ms calibration time before recording starts?
savethesamename 0 for debugging, always save recording under same name (debugsometing)
hklm\software\HTC\Camera\general
brightness 6
contrast 5
hue 5
saturation 4
sharpness 6
hklm\software\HTC\Camera\RecParam\general
audiobufcount 30 nr of audiobuffers
enablemp4vdodupl 1 dunno
videobufcount 8 default is 4 (max is 8)
hklm\software\HTC\Camera\RecParam\3gpsmall
hklm\software\HTC\Camera\RecParam\3gpmedium
hklm\software\HTC\Camera\RecParam\avismall
hklm\software\HTC\Camera\RecParam\avimedium
hklm\software\HTC\Camera\RecParam\avilarge
hklm\software\HTC\Camera\RecParam\mp4small
hklm\software\HTC\Camera\RecParam\mp4medium
hklm\software\HTC\Camera\RecParam\mp4large
cachesize 8192 default is 4096, add to all 8 keys listed above
All settings for camera and album are stored in the key
hkcu\software\IA Style\IA CameraWizard(Pocket PC)
The camera app is version 2.70 the album is 2.51
You can remove the keys like preferences and strings or UI info to reset
the default values.
hklm\software\HTC\Album\DisableEditor
Disable 0
EDIT: 4 apr
Command line options for camera.exe, so you can make shortcuts yourself.
-c or /c perhaps assign to contact (if you have smartdial/iacontacts installed)
-i or /i switch to photo mode
-m or /m switch to mms video mode
-p or /p switch to contact photo
-t or /t switch to picture theme mode
-v ot /v switch to video mode
Still looking for a way to enable rotation and the paint appl in the editor.
In the resource file the images are there (see attachements)
EDIT 5 apr.
The UI interface mechanism is getting clear. If you put album_res.dll (a resource file) in ResourceHacker you
wil find the BMP section of the resources. The BMP i´m interested in is 920 (see attachement below).
If you count the number of icons in that picture you get 10.
Now goto the 241 section. There you will find a 920 resource too. It reads:
01 00 10 00 0F 00 0A 00 0C 91 0D 91 0E 91 0F 91 F9 8C 28 8D 29 8D 2A 8D 2B 8D 18 91
(there is a bug in resourcehacker that doesn´t show the last pair of digits of a 241 resource)
Look complicated at first look. But it isn´t. Lets try:
01 00 10 00 0F 00 = always the same in every 241 resource
0A 00 = 00A0 is 10, so then commands/function id´s follow
0C 91 = 910C = 37132, and is the command for PAN (remember the first icon
in the 920 BMP?)
So (see album_res_920_1033.bmp):
910C is PAN
910D is CROP
910E is RESIZE
910F is COLOR ADJUST
8CF9 is SAVE (dec 36089, and can be found with Resource Hacker in
resource 242 in the Menu section, named Save ;O)
8D28 is ROTATE CLOCKWISE
8D29 is ROTATE ANTI CLOCKWISE
8D2A is MIRROR HORIZONTALY
8D2B is MIRROR VERTICALY
9118 is goto PAINT menu
To be continued
Anybody found a newer version for wm2003se?
Happy tweaking!
Thanks for this
thanks
but IMHO coolcamera anyway is much better than a default one
hi shoonari... i agree, but can u help me find the latest ver. of coolcamera and its cr**k?
here it is
A bit late, But it works nicely.
Thnx

Camera tweaks?

hi guys!
browsing through the registry entries of the HD i found the folowing:
1. HKLM\software\HTC\camera\captparam\capture timer = 5000
2. HKLM\software\HTC\camera\general\macromode = 0
would it be possible to change those values in order to get faster shutter response (for 1st option) and enabling macromode (for 2nd option)
i've changed the values
capture timer = 50
macromode = 1
and nothing happened
but, maybe, someone with more skills can made a tweak out of these to get some improvements of the camera.
what do you think?

Decompiled Camera APK

hi Guys
Ive decompiled the Camera APK from the HONE and found something interesting as below;
Code:
# static fields
.field private static final synthetic $VALUES:[Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_13M:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_2M:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_3M:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_4M:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_5M:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_8M:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
.field public static final enum SENSOR_UNDEFINED:Lcom/android/camera/HTCCameraSensor$Sensor_Type;
Notice the different sensor types?
Plus i think ive found that the HTC One maybe able to take higher than 4 MP photos... Dependant on the sensor of course ^__^
Attached are 3 files;
Notepad ++
APKTool Decompiler
HTC One Camera APK.
So u mean that the camera sensor is capable of taking higher res pix ?
Can u share how to decompile the camera apk
Thnx
Sent from my HTC One using xda app-developers app
Perhaps they have a standard cross-platform HTC camera app and it just limits itself dependant on what hardware it finds.
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 5.6
Bulletproof 1.10
Can you find jpeg compression somewhere?
sallam5010 said:
So u mean that the camera sensor is capable of taking higher res pix ?
Can u share how to decompile the camera apk
Thnx
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Tetsumi06 said:
Perhaps they have a standard cross-platform HTC camera app and it just limits itself dependant on what hardware it finds.
----------------------o('_')o----------------------
Sent from an HTC One with using xda app:
TrickDroid ROM 5.6
Bulletproof 1.10
Click to expand...
Click to collapse
vegetaleb said:
Can you find jpeg compression somewhere?
Click to expand...
Click to collapse
There is that possibility , it depends though as mentioned above by Tetsumi06, if the software does not permit them because the sensor is truly a 4MP sensor... But knowing HTC and their history with cameras, i wouldn't be surprised if it was possible. back on earlier models, HTC never enabled 1080p & 720p recording and the community came together to get them enabled.
Im hunting now.... Tools i used to decompress are attached to the first post
fkofilee said:
There is that possibility , it depends though as mentioned above by Tetsumi06, if the software does not permit them because the sensor is truly a 4MP sensor... But knowing HTC and their history with cameras, i wouldn't be surprised if it was possible. back on earlier models, HTC never enabled 1080p & 720p recording and the community came together to get them enabled.
Im hunting now.... Tools i used to decompress are attached to the first post
Click to expand...
Click to collapse
EDIT:
Tetsumi06 said basically the same thing! Doh!
It could also be that the code is generic to all device types and models and so has a function to pickup the sensor size based on the hardware it sees. So there might be functions for other sensor sizes but they never get enabled because physically our phones are only 4M.
I would love to be wrong though! Good find!:laugh:
HTC is working with one !!! source base. So there are often parts inside a app which are handled differently regarding some build settings.
And same here for the camera sensor strings. The same camera.apk (build number will differ) will run on other devices like Butterfly, One X, One XL, ...
So there must be some checking in the source how to handle different sensors :laugh:
chrisch1974 said:
HTC is working with one !!! source base. So there are often parts inside a app which are handled differently regarding some build settings.
And same here for the camera sensor strings. The same camera.apk (build number will differ) will run on other devices like Butterfly, One X, One XL, ...
So there must be some checking in the source how to handle different sensors :laugh:
Click to expand...
Click to collapse
See what you say is very true, one source of android 4.2.2 for example, for all 2013 devices but they add and remove what is necessary to make those devices work... They develop one load of sense based firmware to then place with drivers for the individual devices ):
You can edit the media_profiles.xml to change the image compression, and video recording bitrate. Need to make the same changes in the camera apk and compile it again
cool worth keeping an eye on
HTC Uses a single base for all its phones so they all have the same encodings. This Apk would work on a phone with 8mpx camera and vice versa. You Cant Have More Pixelsssss.
I think our sensor has more abilities and functions but we need someone to hunt and edit it
Have a look here it's kinda long but interesting
BACK CAMERA (4.1 megapixel)
Ae Bracket Hdr: Off
Ae Bracket Hdr Values: Off, HDR, AE Bracket
Antibanding: Off
Antibanding Values: Off, 50hz, 60hz, Auto
Auto Exposure: Smart Metering
Auto Exposure Lock: False
Auto Exposure Lock Supported: True
Auto Exposure Values: Frame Average, Center Weighted, Spot Metering, Smart Metering
Auto Whitebalance Lock: False
Auto Whitebalance Lock Supported: True
Awb Calibration Check: Success
Camera Mode: 0
Camera Mode Values: 0, 1
Capture Burst Captures Values: 1
Capture Burst Exposures:
Capture Burst Exposures Values: 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12
Capture Burst Interval: 1
Capture Burst Interval Max: 10
Capture Burst Interval Min: 1
Capture Burst Interval Supported: True
Capture Burst Retroactive: 0
Capture Burst Retroactive Max: 1
Capture Burst Timeinterval: 0
Capture Burst Timeinterval Max: 1000
Capture Burst Timeinterval Min: 0
Capture Burst Timeinterval Supported: True
Capture Mode Values: Normal, Contiburst, Contiburst One Shot, Hdr, Panorama, Zoe, Contizoe
Contrast: 5
Contrast Max: 10
Contrast Min: 0
Denoise: Denoise Off
Denoise Values: Denoise Off, Denoise On
Effect: None
Effect Values: None, Mono, Negative, Solarize, Sepia, Posterize, Whiteboard, Blackboard, Aqua, Emboss, Sketch, Neon
Exposure Compensation: 0
Exposure Compensation Step: 0.166667
Face Detection: Off
Face Detection Values: Off, On
Flash Calibration Check: Success
Flash Mode: Off
Flash Mode Values: Off, Auto, On, Torch
Focal Length: 3.82
Focus Areas: (0, 0, 0, 0, 0)
Focus Distances: 0.100000, 0.150000, 0.170000
Focus Mode: Auto
Focus Mode Values: Auto, Infinity, Normal, Macro, Continuous Picture, Continuous Video
Hdr Supported: True
Hfr Size Values: 800x480, 640x480
Histogram: Disable
Histogram Values: Enable, Disable
Horizontal View Angle: 69.6
Iso: Auto
Iso Values: Auto, ISO_HJR, ISO100, ISO200, ISO400, ISO800, ISO1600
Jpeg Quality: 85
Jpeg Thumbnail Height: 384
Jpeg Thumbnail Quality: 90
Jpeg Thumbnail Size Values: 512x288, 480x288, 432x288, 512x384, 352x288, 0x0
Jpeg Thumbnail Width: 512
Lensshade: Enable
Lensshade Values: Enable, Disable
Lsc Calibration Check: Success
Luma Adaptation: 3
Max Exposure Compensation: 12
Max Num Detected Faces Hw: 10
Max Num Detected Faces Sw: 0
Max Num Focus Areas: 1
Max Num Metering Areas: 1
Max Zoom: 59
Mce: Enable
Mce Values: Enable, Disable
Metering Areas: (0, 0, 0, 0, 0)
Min Exposure Compensation: 12
No Display Mode: 0
Num Jpegs Per Shutter: 1
Num Queue Depth: 2
Num Snaps Per Shutter: 1
Ois Setting: True
Ois_support: True
Orientation: 90
Overlay Format: 265
Picture Format: Jpeg
Picture Format Values: Jpeg, Raw
Picture Size: 640x480
Picture Size Values: 2688x1520, 2592x1456, 2048x1520, 2048x1216, 2048x1152, 1920x1088, 1600x1200, 1600x896, 1520x1520, 1456x1088, 1456x880, 1456x832, 1440x1088, 1280x960, 1280x768, 1280x720, 1024x768, 1088x1088, 800x600, 800x480, 720x720, 640x480, 640x384, 640x368, 352x288, 320x240, 176x144
Power Mode: Normal_Power
Power Mode Supported: True
Preview Format: Yuv420sp
Preview Format Values: Yuv420sp, Yuv420sp Adreno, Yuv420p, Yuv420p, Nv12
Preview Fps Range: 1, 200000
Preview Fps Range Values: (1, 200000)
Preview Frame Rate: 120
Preview Frame Rate Mode: Frame Rate Auto
Preview Frame Rate Modes: Frame Rate Auto, Frame Rate Fixed
Preview Frame Rate Values: 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120
Preview Size: 640x480
Preview Size Values: 1920x1088, 1440x1088, 1280x720, 1088x1088, 960x720, 960x544, 800x480, 768x464, 768x432, 720x720, 720x480, 640x480, 640x384, 640x368, 576x432, 480x320, 384x288, 352x288, 320x240, 240x160, 176x144
Recording Hint: False
Redeye Reduction: Disable
Redeye Reduction Values: Enable, Disable
Saturation: 5
Saturation Max: 10
Saturation Min: 0
Scene Detect: Off
Scene Detect Values: Off, On
Scene Mode: Auto
Scene Mode Values: Off, Auto, Action, Portrait, Landscape, Night, Night Portrait, Theatre, Beach, Snow, Sunset, Steadyphoto, Fireworks, Sports, Party, Candlelight, Backlight, Flowers, AR, Text
Selectable Zone Af: Auto
Selectable Zone Af Values: Auto, Spot Metering, Center Weighted, Frame Average
Sharpness: 10
Sharpness Max: 30
Sharpness Min: 0
Single Isp Output Enabled: False
SkinToneEnhancement: 0
SkinToneEnhancement Values: Enable, Disable
Slow Motion Res: 768x432
Slow Motion X: 4
Strtextures: OFF
Time Cons Post Processing: Enable
Touch Af Aec: Touch Off
Touch Af Aec Values: Touch Off, Touch On
TouchAfAec Dx: 100
TouchAfAec Dy: 100
Vertical View Angle: 43
Video 720p60fps Supported: True
Video Frame Format: Yuv420sp
Video Hdr: False
Video Hdr Supported: True
Video Hfr: Off
Video Hfr Values: Off, 60
Video Mode: 0
Video Slow Motion Supported: True
Video Snapshot Supported: False
Video Stabilization: False
Video Stabilization Supported: True
Video Zoom Support: True
Whitebalance: Auto
Whitebalance Values: Auto, Incandescent, Fluorescent, Daylight, Cloudy Daylight
Zoom: 0
Zoom Ratios: 100, 102, 104, 107, 109, 112, 114, 117, 120, 123, 125, 128, 131, 135, 138, 141, 144, 148, 151, 155, 158, 162, 166, 170, 174, 178, 182, 186, 190, 195, 200, 204, 209, 214, 219, 224, 229, 235, 240, 246, 251, 257, 263, 270, 276, 282, 289, 296, 303, 310, 317, 324, 332, 340, 348, 356, 364, 373, 381, 390
Zoom Supported: True
Zsl: Off
Zsl Values: Off, On
Sent from my HTC One using xda app-developers app
They might make all their apps compatible with various hardware to allow easier updating of each device's Android version.
Sent from my HTC One using xda premium
I kinda doubt what u sayin cuz look at picture size values u will notice that it's limited to max 4mp which is for HTC one
Anyways am not looking to increase the megapixels there's much more options like jpeg quality is 85% ! I can see higher video frames ! More scenes !
Maybe we can increase the quality if slow motion video ! Or make it even slower than 4x
Am I right !
Sent from my HTC One using xda app-developers app
The one thing that caught my eye was the different metering options. Being able to choose different types of metering would be awesome, along with changing the jpeg compression
Galactus said:
The one thing that caught my eye was the different metering options. Being able to choose different types of metering would be awesome, along with changing the jpeg compression
Click to expand...
Click to collapse
Yeah it would be awesome if we could control that !
Sent from my HTC One using xda app-developers app
Ugh, the bane of having TMI.
Now scumbag brain wants.
Can someone tell me how to decomplile and re-compile the APK? I will play around with the settings and see what happens
eRajesh said:
Can someone tell me how to decomplile and re-compile the APK? I will play around with the settings and see what happens
Click to expand...
Click to collapse
Use virtuous studio.
Anyway from the code we can pretty much change anything the only issue is we don't know the sensor capabilities, what is max that it can do.
For example max exposure is 12 if I remember right from the code, so if the sensor is capable of doing 16 and we set it to 14 we would get better low light photos.
We could change metering distance but again we need to know sensor capabilities for example if minimum is 5 cm we could add 3 cm which would allows us closer macro shots.
We could boost the flash as well, Make the duration longer = more time for sensor to pick up the light = better pic.
Or we could increase zoom distance as well since we can assume HTC gave us short zoom since our pixel count sux , tho I'm sure 20/30% won't ruin that much the quality ( anyway not like anyone is ever using zoom lol)
Best of all would be adding touch focus flash @ night since we lack that option. Then set it to lock focus for let's say 4 sec and take a pic.
We could even add 60 fps1080p recording tho that would make 1 min clip 300 mb + lol.
We have sh1t load opportunities here all we need is either to test on blind some stuff or somehow get the hardware specs of our sensor
Sent from my HTC One using xda premium
anyone know how to enable the histogram?

Help!, Different Size Image But Same Result.

I am editing whole my question as it might not so clear for others to help.
I am modifying super jumper game (Mario Zacher's Beginning Android Game) , i've come to stuck on this issue:
if you look at my attachment image, you could see that my character image rendered in same size with the spring image.
i'm using texture atlas 1024x1024 px,
Code:
spring = new TextureRegion(items, 980, 90, 32, 40);
charJump = new Animation(0.2f,
new TextureRegion(items,charX+32, charY, 64,160),
new TextureRegion(items, charX+150, charY, 64, 160)); //char anim.
I am using photoshop and put all the texture region required in my Atlas.
For each character image frame has the size of 64x150
while the spring image only has the size of 30x40
the world class camera width and height = 11f x 14f
the world renderer class camera width and height also = 11f x 14f
Please give me some clue, what important knowledge i am missing here ? thank you.
ganero

G4 Camera Mods FPS [MM]

FPS Mod - Get More FPs in video
To install
Copy file to
/system/vendor/lib/
Click to expand...
Click to collapse
Code:
permissions rw-r-r
V2 Changes
39 fps UHD Video
tested by @pikachukaki
every video i capture in my computer its said 29fps
This is not flashable zip you need to repleace file menualy
Does this work on Lollipop?
datvu said:
This is not flashable zip you need to repleace file menualy
Click to expand...
Click to collapse
yeah i replace the so lib file manually
pikachukaki said:
every video i capture in my computer its said 29fps
Click to expand...
Click to collapse
run
Code:
adb shell dumpsys media.camera
with your device connected and developer mode enabled.
Click to expand...
Click to collapse
theres some config file that has the fps defined maybe try change that i think it was the file changed in the 60fps mod for g4
defcomg said:
theres some config file that has the fps defined maybe try change that i think it was the file changed in the 60fps mod for g4
Click to expand...
Click to collapse
take it
pikachukaki said:
take it
Click to expand...
Click to collapse
in system/etc/camera_config.xml
look for
Code:
<item name="video_size_rear_supported">
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
</item>
change it to
Code:
<item name="video_size_rear_supported">
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
</item>
in /system/etc/media_profiles.xml
look for
Code:
minFrameRate="15" maxFrameRate="120"
change that to 240
in camera id 0 look for 1080 change frame to 90 | look 4kuhd change that to 60 or raise value by like 5 like say 35 fps 40 fps till it maxes out somewhere
if you open the lib with hex editor like hex workshop search for int16 value 6144 it will show all the resolutions
6144 is the Number of horizontal lines the number next to it is vertical the 4 bytes before it are active pixels w x h
Capture res example
HEX
Code:
C014 AC0B 0018 E00B 402E7021 0018BF1E 01000000 00000040 713DF041 01
aW aH W H Pixel Clock Output Clock Binning Min Fps Max Fps Sensor Mode
DEC
Code:
5312 2988 6144 3040 561000000 515840000 1 2 30.03 1
Pixel Clock = W * H * Max Fps
Output Clock When Not in HFR Mode = Pixel Clock it limits actual fps. When in HFR mode = Pixel Clock / 2
Sensor Mode 1 = Normal 2 = HFR 3 = HDR
G4 Video Res runs at Full sensor res @ 30 fps reducing aW aH W H to say 3840 2160 6144 2190 would let the G4 Gain more FPS in UHD Mode thats how i got 32fps UHD on OG SD800 i reduced the H value from 2219 to 2170.
so if you want to achieve 240fps without pushing device a aW/8 aH/8 W H/8 Max FPS * 8
this would give a guaranteed 240fps
Code:
664 373 6144 380 561000000 515840000 1 2 240.24 1
All that is needed is a camera 2 app that lets you set custom res and fps for video then you can play with these values
Output Clock is what limits the fps i dunno what the SD808 maxes out it could be higher than the default 515K
Hopefully the camera_config.xml mod method works for the stock camera
defcomg said:
in system/etc/camera_config.xml
look for
Code:
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
change it to
Code:
3840x2160,
[email protected],
1920x1080,
1280x720,
[email protected],
640x480,
320x240,
176x144
in /system/etc/media_profiles.xml
look for
Code:
minFrameRate="15" maxFrameRate="120"
change that to 240
in camera id 0 look for 1080 change frame to 90 | look 4kuhd change that to 60 or raise value by like 5 like say 35 fps 40 fps till it maxes out somewhere
if you open the lib with hex editor like hex workshop search for int16 value 6144 it will show all the resolutions
6144 is the Number of horizontal lines the number next to it is vertical the 4 bytes before it are active pixels w x h
Capture res example
HEX
Code:
C014 AC0B 0018 E00B 402E7021 0018BF1E 01000000 00000040 713DF041 01
aW aH W H Pixel Clock Output Clock Binning Min Fps Max Fps Sensor Mode
DEC
Code:
5312 2988 6144 3040 561000000 515840000 1 2 30.03 1
Pixel Clock = W * H * Max Fps
Output Clock When Not in HFR Mode = Pixel Clock it limits actual fps. When in HFR mode = Pixel Clock / 2
Sensor Mode 1 = Normal 2 = HFR 3 = HDR
G4 Video Res runs at Full sensor res @ 30 fps reducing aW aH W H to say 3840 2160 6144 2190 would let the G4 Gain more FPS in UHD Mode thats how i got 32fps UHD on OG SD800 i reduced the H value from 2219 to 2170.
so if you want to achieve 240fps without pushing device a aW/8 aH/8 W H/8 Max FPS * 8
this would give a guaranteed 240fps
Code:
664 373 6144 380 561000000 515840000 1 2 240.24 1
All that is needed is a camera 2 app that lets you set custom res and fps for video then you can play with these values
Output Clock is what limits the fps i dunno what the SD808 maxes out it could be higher than the default 515K
Hopefully the camera_config.xml mod method works for the stock camera
Click to expand...
Click to collapse
@defcomg I edit the two xml files now i will see what it can capture...but i dont have the knowlage to edit the so file...you seem to have it so edit it if you want and have the time and release a flashable zip to test it if you dont have the device
{
"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"
}
Awsome Job! ant chance to get it for CM?
solokiller11 said:
Awsome Job! ant chance to get it for CM?
Click to expand...
Click to collapse
these are just test we need some G4 dev as i don't have a g4 to test
pikachukaki said:
@defcomg I edit the two xml files now i will see what it can capture...but i dont have the knowlage to edit the so file...you seem to have it so edit it if you want and have the time and release a flashable zip to test it if you dont have the device
Click to expand...
Click to collapse
might require apk mod or a camera app which lets you set fps i think L camera let you do that
defcomg said:
might require apk mod or a camera app which lets you set fps i think L camera let you do that
Click to expand...
Click to collapse
other fps mods edit the media_profiles.xml but i think if you want more fps than 60 and you edit the lib file you need to edit every file...tell me which files you need....
updated op
Im interested in testing this with my G4 but i am on LP 5.1 to get root without unlocking bootloader. I am still able to copy your file? or this file is different on LP and i need MM to test it?
Tomek33 said:
Im interested in testing this with my G4 but i am on LP 5.1 to get root without unlocking bootloader. I am still able to copy your file? or this file is different on LP and i need MM to test it?
Click to expand...
Click to collapse
i need libmmcamera_imx234.so from your rom then i can change the same values as on MM
also in theory if i kill UHD res i could make FHD run at 75 fps
defcomg said:
i need libmmcamera_imx234.so from your rom then i can change the same values as on MM
also in theory if i kill UHD res i could make FHD run at 75 fps
Click to expand...
Click to collapse
240 fps on HD resolution would be fantastic!!!
asce1992 said:
240 fps on HD resolution would be fantastic!!!
Click to expand...
Click to collapse
the 808 is unable to pull 240fps and yes the 5X is capable because it has to pull less Horizontal lines
Cap is 6.95 Gbps / 579,010,560 clock +/-
so
for 240 fps
12.92Gbps / 1,076,428,800 clock
so far ive seen g4 max out 124fps
Width : 1 280 pixels
Height : 720 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 124.035 fps
Minimum frame rate : 107.143 fps
Maximum frame rate : 127.841 fps
Click to expand...
Click to collapse
from another imx234 device it has 240 fps 640x360
Can you try recording in 4096x2160 24fps?
Today I tried FilmicPro and it managed to record video in 4096x2160 although it was buggy.
I tried modding media_codecs.xml media_profiles.xml and camera_config.xml so that the stock camera app does it however once I start video recording it crashes.
pepo930 said:
Can you try recording in 4096x2160 24fps?
Today I tried FilmicPro and it managed to record video in 4096x2160 although it was buggy.
I tried modding media_codecs.xml media_profiles.xml and camera_config.xml so that the stock camera app does it however once I start video recording it crashes.
Click to expand...
Click to collapse
buggy?

Categories

Resources