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!
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?
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
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