Why can´t any theme be black in top and bottom bar??
I make an black theme, but when I load it in to me 9100 it´s always light grey... I want it black!
Please help.!?
If you modify your theme with a cab editor,you just need to modify a value :
HKLM\Software\Microsoft\Color\
Modify value 5 (REG_BINARY) to hexa 00 00 00 00 (Black).
You can also look at this wiki page : http://wiki.xda-developers.com/index.php?pagename=WindowsMobile5Colors
Martinlbb
You could also send post your theme.
I'll modify it.
Martin
Could you post a very basic theme that uses registry key 5 to get the black bars?
I just tried again - and just setting key 5 does absolutely nothing on my Qtek 9100.
Here's what I did...
Opened PHM Regedit
Went to HKLM\Software\Microsoft\Color
Added a new Binary value labeled "5"
Set value to "00 00 00 00"
.. waited a while so that the registry could be written away ..
Performed a soft reset
.. waited for the PPC to start up ..
Top and Bottom bars are blue.
Opened PHM Regedit
Went to HKLM\Software\Microsoft\Color
Checked for Binary value labeled "5" - it's there, and set to "00 00 00 00"
So.. no luck with that registry setting here :|
I can only get purely black bars using:
HKCU\Software\Microsoft\Today\Theme.tsk::Color_SoftkeyFlatCenter = 00 00 00 00
HKCU\Software\Microsoft\Today\Theme.tsk::Color_TitleFlatCenter = 00 00 00 00
Where Theme.tsk is my theme's name.
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
Trying to figure out how to make a shortcut to settings. When you browse to the settings folder in file explorer and open it it's empty. I don't want to open individual .cpl's I would like to emulate what happens when you hit "settings" on the start menu and open the settings window. Thanks.
juiceppc said:
Trying to figure out how to make a shortcut to settings. When you browse to the settings folder in file explorer and open it it's empty. I don't want to open individual .cpl's I would like to emulate what happens when you hit "settings" on the start menu and open the settings window. Thanks.
Click to expand...
Click to collapse
i have been searching for this too, but i didnt find it
i dont know if its possibe
Done it but not certain how!
I have done this before - using VJKeypress you can simulate a keypress in a shortcut which takes you straight to Settings. I can't remember which it was (probably ctl+alt+something lol) but it did work.
Dig around and you'll have it working soon.
littld said:
I have done this before - using VJKeypress you can simulate a keypress in a shortcut which takes you straight to Settings. I can't remember which it was (probably ctl+alt+something lol) but it did work.
Dig around and you'll have it working soon.
Click to expand...
Click to collapse
Here's the keycode list. Any of these ring a bell?
VK_LBUTTON 1
VK_RBUTTON 2
VK_CANCEL 3
VK_MBUTTON 4
VK_XBUTTON1 5
VK_XBUTTON2 6
VK_BACK 8
VK_TAB 9
VK_CLEAR 12
VK_RETURN 13
VK_SHIFT 16
VK_CONTROL 17
VK_CTRL 17
VK_MENU 18
VK_PAUSE 19
VK_CAPITAL 20
VK_HANGEUL 21
VK_HANGUL 21
VK_KANA 21
VK_JUNJA 23
VK_FINAL 24
VK_HANJA 25
VK_KANJI 25
VK_ESCAPE 27
VK_CONVERT 28
VK_NONCONVERT 29
VK_ACCEPT 30
VK_MODECHANGE 31
VK_SPACE 32
VK_PRIOR 33
VK_NEXT 34
VK_END 35
VK_HOME 36
VK_LEFT 37
VK_UP 38
VK_RIGHT 39
VK_DOWN 40
VK_SELECT 41
VK_PRINT 42
VK_EXECUTE 43
VK_SNAPSHOT 44
VK_INSERT 45
VK_DELETE 46
VK_HELP 47
VK_0 48
VK_1 49
VK_2 50
VK_3 51
VK_4 52
VK_5 53
VK_6 54
VK_7 55
VK_8 56
VK_9 57
VK_A 65
VK_B 66
VK_C 67
VK_D 68
VK_E 69
VK_F 70
VK_G 71
VK_H 72
VK_I 73
VK_J 74
VK_K 75
VK_L 76
VK_M 77
VK_N 78
VK_O 79
VK_P 80
VK_Q 81
VK_R 82
VK_S 83
VK_T 84
VK_U 85
VK_V 86
VK_W 87
VK_X 88
VK_Y 89
VK_Z 90
VK_LWIN 91
VK_RWIN 92
VK_APPS 93
VK_SLEEP 95
VK_NUMPAD0 96
VK_NUMPAD1 97
VK_NUMPAD2 98
VK_NUMPAD3 99
VK_NUMPAD4 100
VK_NUMPAD5 101
VK_NUMPAD6 102
VK_NUMPAD7 103
VK_NUMPAD8 104
VK_NUMPAD9 105
VK_MULTIPLY 106
VK_ADD 107
VK_SEPARATOR 108
VK_SUBTRACT 109
VK_DECIMAL 110
VK_DIVIDE 111
VK_F1 112
VK_F2 113
VK_F3 (green key) 114
VK_F4 115
VK_F5 116
VK_F6 117
VK_F7 118
VK_F8 119
VK_F9 120
VK_F10 121
VK_F11 122
VK_F12 123
VK_F13 124
VK_F14 125
VK_F15 126
VK_F16 127
VK_F17 128
VK_F18 129
VK_F19 130
VK_F20 131
VK_F21 132
VK_F22 133
VK_F23 134
VK_F24 135
VK_NUMLOCK 144
VK_SCROLL 145
VK_OEM_FJ_JISHO 146
VK_OEM_NEC_EQUAL 146
VK_OEM_FJ_MASSHOU 147
VK_OEM_FJ_TOUROKU 148
VK_OEM_FJ_LOYA 149
VK_OEM_FJ_ROYA 150
VK_LSHIFT 160
VK_RSHIFT 161
VK_LCONTROL 162
VK_RCONTROL 163
VK_LMENU 164
VK_RMENU 165
VK_BROWSER_BACK 166
VK_BROWSER_FORWARD 167
VK_BROWSER_REFRESH 168
VK_BROWSER_STOP 169
VK_BROWSER_SEARCH 170
VK_BROWSER_FAVORITES 171
VK_BROWSER_HOME 172
VK_VOLUME_MUTE 173
VK_VOLUME_DOWN 174
VK_VOLUME_UP 175
VK_MEDIA_NEXT_TRACK 176
VK_MEDIA_PREV_TRACK 177
VK_MEDIA_STOP 178
VK_MEDIA_PLAY_PAUSE 179
VK_LAUNCH_MAIL 180
VK_LAUNCH_MEDIA_SELECT 181
VK_LAUNCH_APP1 182
VK_LAUNCH_APP2 183
VK_OEM_1 186
VK_OEM_PLUS 187
VK_OEM_COMMA 188
VK_OEM_MINUS 189
VK_OEM_PERIOD 190
VK_OEM_2 191
VK_OEM_3 192
VK_OEM_4 219
VK_OEM_5 220
VK_OEM_6 221
VK_OEM_7 222
VK_OFF (power off) 223
VK_OEM_AX 225
VK_OEM_102 226
VK_ICO_HELP 227
VK_ICO_00 228
VK_PROCESSKEY 229
VK_ICO_CLEAR 230
VK_PACKET 231
VK_OEM_RESET 233
VK_OEM_JUMP 234
VK_OEM_PA1 235
VK_OEM_PA2 236
VK_OEM_PA3 237
VK_OEM_WSCTRL 238
VK_OEM_CUSEL 239
VK_DBE_ALPHANUMERIC 240
VK_OEM_ATTN 240
VK_DBE_KATAKANA 241
VK_OEM_FINISH 241
VK_DBE_HIRAGANA 242
VK_OEM_COPY 242
VK_DBE_SBCSCHAR 243
VK_OEM_AUTO 243
VK_DBE_DBCSCHAR 244
VK_OEM_ENLW 244
VK_DBE_ROMAN 245
VK_OEM_BACKTAB 245
VK_ATTN 246
VK_DBE_NOROMAN 246
VK_CRSEL 247
VK_DBE_ENTERWORDREGISTERMODE 247
VK_DBE_ENTERIMECONFIGMODE 248
VK_EXSEL 248
VK_DBE_FLUSHSTRING 249
VK_EREOF 249
VK_DBE_CODEINPUT 250
VK_PLAY 250
VK_DBE_NOCODEINPUT 251
VK_ZOOM 251
VK_DBE_DETERMINESTRING 252
VK_NONAME 252
VK_DBE_ENTERDLGCONVERSIONMODE 253
VK_PA1 253
VK_OEM_CLEAR 254
littld said:
I have done this before - using VJKeypress you can simulate a keypress in a shortcut which takes you straight to Settings. I can't remember which it was (probably ctl+alt+something lol) but it did work.
Dig around and you'll have it working soon.
Click to expand...
Click to collapse
I tried this software but only the follo no. worked
223 Power Off
27 Escape
91 Start Menu
93 Context Menu
112 Left Soft Key
113 Right Soft Key
133 Device Lock (WM5 only)
I was looking also to get setting & Program menu shortcuts
Can some one help.
I looked
I looked at the list but can't remember which - I think I'd set up a macro and incremented by one each time with the number to see what they all did. It's a long time ago!
I do know for a fact that there is a keyboard shortcut to the Settings window and it works perfectly.
Bad news - there is no such way to get to the Programs screen. I did write a little app which could call it (thought the Start menu) but I can't find it.
Good luck.
maybe here are what you are looking for.................
medkid said:
maybe here are what you are looking for.................
Click to expand...
Click to collapse
Thankyou medkid
Anyone can help me with VJKeypress
I want to use FtouchFlo from Efrost to emulate keypress (from D-pad) right and left.
check here :
http://www.xs4all.nl/~itsme/projects/xda/xda-controlpanel.html
sudist said:
Anyone can help me with VJKeypress
I want to use FtouchFlo from Efrost to emulate keypress (from D-pad) right and left.
Click to expand...
Click to collapse
I PM Vj but no reply yet.
Thanks u guys 4 ur help,
I still do not know how to shortcut 2 Program & setting menu
ie Start - Program
Or Start - Setting
This needed 4 FtouchFlo 2 gesture from left to right - right to left.
I was looking for this for ages with no luck.
Recently installed Wisbar Advance 3, was playing about with linking up my desktop icons and found that it can be done...
hold tap on an icon, properties, set path to executable as:
\Program Files\Lakeridge\Wisbar Advance 3\Control.exe
this will bring up the Settings page as normal.
(another tip- in the same folder as that .exe is StartPanel.exe, check that one out if you want a funky looking full-page version of your regular Start menu)
not sure if this is the same in earlier versions of Wisbar, but i thought I'd mention it if any of you have the program, and there was also a way of doing the same thing in iLauncher. hope this helps somebody...
Dr J, thanks for the tip, I have pocket plus 4 and wisbar 3, so it is perfect for a shortcut to open the settings panel.
I have made my cube with 6 sides but now i want to make the sliding of the cubes with my new icons.
When i open my registery and when i look in HKLM - software - HTC - Biotouch - Boitouch -
i copied the values Cube 2 and renamed it to Cube 3 - Cube 4 and Cube 5.
The original Cube 3 i renamed as Cube 6.
When i now slide my cube and go from the phone screen to the mediahub screen it is ok, form the mediahub sceen to the 1ste app screen is ok, but form the 2° - 3° and 4° app screen i got the same pictures as form the 1ste app.
I look at the values in the Cube and i notice that in Cube 2 there is :
07 07 08 09 0A 0B 0C 0D
0A C8 C9 CA CB 18 19 1A
1B 1C 07
Since i copied Cube 3 - 4 and 5 with the same values as cube 2 the values are the same.
In my cube 6 (original cube 3) i have these values :
07 0D 0E 0F 10 11 12 01
0A C8 C9 CA CB 1D 1E 1F
20 21 0D
I have already figured out what the numbers 01 till 33 are (they are also in the same register and have values for moves of the cube)
I made new strings form 34 till 66 with the values for the moves of the other cubes.
I can't figure out what the other things will mean like 0A 0B 0C 0D
0A C8 C9 CA CB
Can someone help me to make my 6 cube slide with my new icons on it?
Thanks
This would be an interesting find... * bump *
hefi said:
I have made my cube with 6 sides but now i want to make the sliding of the cubes with my new icons.
When i open my registery and when i look in HKLM - software - HTC - Biotouch - Boitouch -
i copied the values Cube 2 and renamed it to Cube 3 - Cube 4 and Cube 5.
The original Cube 3 i renamed as Cube 6.
When i now slide my cube and go from the phone screen to the mediahub screen it is ok, form the mediahub sceen to the 1ste app screen is ok, but form the 2° - 3° and 4° app screen i got the same pictures as form the 1ste app.
I look at the values in the Cube and i notice that in Cube 2 there is :
07 07 08 09 0A 0B 0C 0D
0A C8 C9 CA CB 18 19 1A
1B 1C 07
Since i copied Cube 3 - 4 and 5 with the same values as cube 2 the values are the same.
In my cube 6 (original cube 3) i have these values :
07 0D 0E 0F 10 11 12 01
0A C8 C9 CA CB 1D 1E 1F
20 21 0D
I have already figured out what the numbers 01 till 33 are (they are also in the same register and have values for moves of the cube)
I made new strings form 34 till 66 with the values for the moves of the other cubes.
I can't figure out what the other things will mean like 0A 0B 0C 0D
0A C8 C9 CA CB
Can someone help me to make my 6 cube slide with my new icons on it?
Thanks
Click to expand...
Click to collapse
Why don´t probe this program: http://ww2.fatattitude.com/software/...?view=download and see??
v1zca1n0 said:
Why don´t probe this program: http://ww2.fatattitude.com/software/...?view=download and see??
Click to expand...
Click to collapse
Can't seem to get it work on my cruise. I tried to shut down the MediaHubMini.exe with SKTools but don't really know if it worked.. (don't really know how this tool works).
I think i got is shut down, but when i start the touchsetting programma i get error message.
hefi said:
Can't seem to get it work on my cruise. I tried to shut down the MediaHubMini.exe with SKTools but don't really know if it worked.. (don't really know how this tool works).
I think i got is shut down, but when i start the touchsetting programma i get error message.
Click to expand...
Click to collapse
Use to work with no problem. Install in Main Memory instead SD and try. If you can work is very intuitive and you are going to see very fast how to change the Cube. Say me something
v1zca1n0 said:
Use to work with no problem. Install in Main Memory instead SD and try. If you can work is very intuitive and you are going to see very fast how to change the Cube. Say me something
Click to expand...
Click to collapse
I tried it a different ways but i can't get it work on my cruise. I also tried the manual installation but it won't work.
hefi said:
I tried it a different ways but i can't get it work on my cruise. I also tried the manual installation but it won't work.
Click to expand...
Click to collapse
Very strange I have already install and working and I have a Cruise with spanish ROM cocked by Christonge and download in this forum I will try your trick for 6 sides and, after, try to work with the program and I will tell my experience
v1zca1n0 said:
Very strange I have already install and working and I have a Cruise with spanish ROM cocked by Christonge and download in this forum I will try your trick for 6 sides and, after, try to work with the program and I will tell my experience
Click to expand...
Click to collapse
ok thanks, let me know....
This thread is intended for (ongoing) developper discussion about the EXIF bug in the camera of cm 10.1. The discussion began in the official cm 10.1 thread, but we felt it would be better to continue in an own thread.
The subject is about to find how to fix the two last tags in the EXIF data of pictures shot with the camera from cm 10.1 which don't contain proper values, ShutterSpeedValue and ExposureTime. The other bugs in the EXIF were already fixed by ghepeu during the last days.
Let's begin right now:
beggar23 said:
Let me stick with it for a while. Seriously, lets take the first character as shutter speed value, it fits well with the formula. But which purpose might the other numbers have? Can someone have a look which other numbers occur, do they appear like random numbers or rather have re-occurring values?
Click to expand...
Click to collapse
Yes the values are re-occuring, for example I very often get 405 and 505. They are not random and they depend on how much light there is while taking the picture (which is logical for shutter speed). More light = higher value.
To see the values I inserted a log output statement in my local sources and use the app aLogcat to retrieve it (is this a noob method?)
tryptophane said:
Let's begin right now:
Yes the values are re-occuring, for example I very often get 405 and 505. They are not random and they depend on how much light there is while taking the picture (which is logical for shutter speed). More light = higher value.
To see the values I inserted a log output statement in my local sources and use the app aLogcat to retrieve it (is this a noob method?)
Click to expand...
Click to collapse
First of all: thanks a lot for starting a separate thread for this issue here!
What seems to be interesting is if the structure of the value for ShutterSpeedValue might indeed be like xyz, while x stands for the actual shutter speed and xy stand for something else.
So if someone can log a fair number of shutter speed values (gained while taking pictures in the dark, in the sunlight etc) and list them, we were able to have look
if the first digit x, after calculating with the help of the given formula, is in the reach of possible shutter speeds, like 1/8, 1/16, 1/32 and so on.
if the last two digits yz have re-occuring values, so that we could try to extrapolate their nature and maybe real purpose.
It is all just a guess and my possibly naive thoughts might lead to nowhere. But, anyway... :angel:
Looking at EXIF of old images taken with stock ROM:
Code:
$ exiv2 -u -pv print 20120126_121609.jpg
...
0x9201 Photo ShutterSpeedValue SRational 1 432/100
...
Maybe you need to use a fixed denominator of 100?
opaco23 said:
Looking at EXIF of old images taken with stock ROM:
Code:
$ exiv2 -u -pv print 20120126_121609.jpg
...
0x9201 Photo ShutterSpeedValue SRational 1 432/100
...
Maybe you need to use a fixed denominator of 100?
Click to expand...
Click to collapse
That's interesting, can you print the hex values too ('-h' flag)?
Could you do that for all the values? I'd like to see if there are other things that we're missing, I have no idea what most of them mean so I don't know if what we're getting is sane.
Thank you.
ghepeu said:
That's interesting, can you print the hex values too ('-h' flag)?
Could you do that for all the values? I'd like to see if there are other things that we're missing, I have no idea what most of them mean so I don't know if what we're getting is sane.
Thank you.
Click to expand...
Click to collapse
Hope this helps. Here are hex and plain values. I'm on the I777, which is almost identical firmware (US Exynos variant). The cameras are the same.
hex:
Code:
[email protected]:~$ exiv2 -u -ph print '/home/fc/Desktop/IMG_20130411_190618.jpg'
0x0100 Image ImageWidth Long 1 4
0000 c0 0c 00 00 ....
0x0101 Image ImageLength Long 1 4
0000 90 09 00 00 ....
0x010f Image Make Ascii 8 8
0000 53 41 4d 53 55 4e 47 00 SAMSUNG.
0x0110 Image Model Ascii 9 9
0000 53 47 48 2d 49 37 37 37 00 SGH-I777.
0x0112 Image Orientation Short 1 2
0000 01 00 ..
0x0131 Image Software Ascii 30 30
0000 45 78 69 66 20 53 6f 66 74 77 61 72 65 20 56 65 Exif Software Ve
0010 72 73 69 6f 6e 20 31 2e 30 2e 32 2e 30 00 rsion 1.0.2.0.
0x0132 Image DateTime Ascii 20 20
0000 32 30 31 33 3a 30 34 3a 31 31 20 31 39 3a 30 36 2013:04:11 19:06
0010 3a 31 39 00 :19.
0x0213 Image YCbCrPositioning Short 1 2
0000 01 00 ..
0x8769 Image ExifTag Long 1 4
0000 c9 00 00 00 ....
0x829a Photo ExposureTime Rational 1 8
0000 01 00 00 00 11 00 00 00 ........
0x829d Photo FNumber Rational 1 8
0000 09 01 00 00 64 00 00 00 ....d...
0x8822 Photo ExposureProgram Short 1 2
0000 03 00 ..
0x8827 Photo ISOSpeedRatings Short 1 2
0000 40 00 @.
0x9000 Photo ExifVersion Undefined 4 4
0000 30 32 32 30 0220
0x9003 Photo DateTimeOriginal Ascii 20 20
0000 32 30 31 33 3a 30 34 3a 31 31 20 31 39 3a 30 36 2013:04:11 19:06
0010 3a 31 39 00 :19.
0x9004 Photo DateTimeDigitized Ascii 20 20
0000 32 30 31 33 3a 30 34 3a 31 31 20 31 39 3a 30 36 2013:04:11 19:06
0010 3a 31 39 00 :19.
0x9201 Photo ShutterSpeedValue SRational 1 8
0000 95 01 00 00 64 00 00 00 ....d...
0x9202 Photo ApertureValue Rational 1 8
0000 19 01 00 00 64 00 00 00 ....d...
0x9203 Photo BrightnessValue SRational 1 8
0000 03 01 00 00 64 00 00 00 ....d...
0x9204 Photo ExposureBiasValue SRational 1 8
0000 00 00 00 00 64 00 00 00 ....d...
0x9205 Photo MaxApertureValue Rational 1 8
0000 19 01 00 00 64 00 00 00 ....d...
0x9207 Photo MeteringMode Short 1 2
0000 02 00 ..
0x9209 Photo Flash Short 1 2
0000 10 00 ..
0x920a Photo FocalLength Rational 1 8
0000 8d 01 00 00 64 00 00 00 ....d...
0x9286 Photo UserComment Undefined 21 21
0000 41 53 43 49 49 00 00 00 55 73 65 72 20 63 6f 6d ASCII...User com
0010 6d 65 6e 74 73 ments
0xa001 Photo ColorSpace Short 1 2
0000 01 00 ..
0xa002 Photo PixelXDimension Long 1 4
0000 c0 0c 00 00 ....
0xa003 Photo PixelYDimension Long 1 4
0000 90 09 00 00 ....
0xa402 Photo ExposureMode Long 1 4
0000 00 00 00 00 ....
0xa403 Photo WhiteBalance Long 1 4
0000 00 00 00 00 ....
0xa406 Photo SceneCaptureType Long 1 4
0000 00 00 00 00 ....
0xa420 Photo ImageUniqueID Ascii 7 7
0000 4f 4e 45 46 30 31 00 ONEF01.
0x8825 Image GPSTag Long 1 4
0000 67 02 00 00 g...
0x0000 GPSInfo GPSVersionID Byte 4 4
0000 02 02 00 00 ....
0x0001 GPSInfo GPSLatitudeRef Ascii 2 2
0000 4e 00 N.
0x0002 GPSInfo GPSLatitude Rational 3 24
0000 4d a5 49 18 80 96 98 00 00 00 00 00 01 00 00 00 M.I.............
0010 00 00 00 00 01 00 00 00 ........
0x0003 GPSInfo GPSLongitudeRef Ascii 2 2
0000 57 00 W.
0x0004 GPSInfo GPSLongitude Rational 3 24
0000 96 3a 1c 2c 80 96 98 00 00 00 00 00 01 00 00 00 .:.,............
0010 00 00 00 00 01 00 00 00 ........
0x0005 GPSInfo GPSAltitudeRef Byte 1 1
0000 00 .
0x0006 GPSInfo GPSAltitude Rational 1 8
0000 98 08 00 00 64 00 00 00 ....d...
0x0007 GPSInfo GPSTimeStamp Rational 3 24
0000 17 00 00 00 01 00 00 00 06 00 00 00 01 00 00 00 ................
0010 14 00 00 00 01 00 00 00 ........
0x001b GPSInfo GPSProcessingMethod Undefined 11 11
0000 41 53 43 49 49 00 00 00 47 50 53 ASCII...GPS
0x001d GPSInfo GPSDateStamp Ascii 11 11
0000 32 30 31 33 3a 30 34 3a 31 31 00 2013:04:11.
0x0100 Thumbnail ImageWidth Long 1 4
0000 40 01 00 00 [user=457974]@...[/user]
0x0101 Thumbnail ImageLength Long 1 4
0000 f0 00 00 00 ....
0x0103 Thumbnail Compression Short 1 2
0000 06 00 ..
0x0112 Thumbnail Orientation Short 1 2
0000 01 00 ..
0x011a Thumbnail XResolution Rational 1 8
0000 48 00 00 00 01 00 00 00 H.......
0x011b Thumbnail YResolution Rational 1 8
0000 48 00 00 00 01 00 00 00 H.......
0x0128 Thumbnail ResolutionUnit Short 1 2
0000 02 00 ..
0x0201 Thumbnail JPEGInterchangeFormat Long 1 4
0000 cd 03 00 00 ....
0x0202 Thumbnail JPEGInterchangeFormatLength Long 1 4
0000 24 e1 00 00
plain:
Code:
[email protected]:~$ exiv2 -u -pv print '/home/fc/Desktop/IMG_20130411_190618.jpg'
0x0100 Image ImageWidth Long 1 3264
0x0101 Image ImageLength Long 1 2448
0x010f Image Make Ascii 8 SAMSUNG
0x0110 Image Model Ascii 9 SGH-I777
0x0112 Image Orientation Short 1 1
0x0131 Image Software Ascii 30 Exif Software Version 1.0.2.0
0x0132 Image DateTime Ascii 20 2013:04:11 19:06:19
0x0213 Image YCbCrPositioning Short 1 1
0x8769 Image ExifTag Long 1 201
0x829a Photo ExposureTime Rational 1 1/17
0x829d Photo FNumber Rational 1 265/100
0x8822 Photo ExposureProgram Short 1 3
0x8827 Photo ISOSpeedRatings Short 1 64
0x9000 Photo ExifVersion Undefined 4 48 50 50 48
0x9003 Photo DateTimeOriginal Ascii 20 2013:04:11 19:06:19
0x9004 Photo DateTimeDigitized Ascii 20 2013:04:11 19:06:19
0x9201 Photo ShutterSpeedValue SRational 1 405/100
0x9202 Photo ApertureValue Rational 1 281/100
0x9203 Photo BrightnessValue SRational 1 259/100
0x9204 Photo ExposureBiasValue SRational 1 0/100
0x9205 Photo MaxApertureValue Rational 1 281/100
0x9207 Photo MeteringMode Short 1 2
0x9209 Photo Flash Short 1 16
0x920a Photo FocalLength Rational 1 397/100
0x9286 Photo UserComment Undefined 21 charset="Ascii" User comments
0xa001 Photo ColorSpace Short 1 1
0xa002 Photo PixelXDimension Long 1 3264
0xa003 Photo PixelYDimension Long 1 2448
0xa402 Photo ExposureMode Long 1 0
0xa403 Photo WhiteBalance Long 1 0
0xa406 Photo SceneCaptureType Long 1 0
0xa420 Photo ImageUniqueID Ascii 7 ONEF01
0x8825 Image GPSTag Long 1 615
0x0000 GPSInfo GPSVersionID Byte 4 2 2 0 0
0x0001 GPSInfo GPSLatitudeRef Ascii 2 N
0x0002 GPSInfo GPSLatitude Rational 3 407479629/10000000 0/1 0/1
0x0003 GPSInfo GPSLongitudeRef Ascii 2 W
0x0004 GPSInfo GPSLongitude Rational 3 740047510/10000000 0/1 0/1
0x0005 GPSInfo GPSAltitudeRef Byte 1 0
0x0006 GPSInfo GPSAltitude Rational 1 2200/100
0x0007 GPSInfo GPSTimeStamp Rational 3 23/1 6/1 20/1
0x001b GPSInfo GPSProcessingMethod Undefined 11 65 83 67 73 73 0 0 0 71 80 83
0x001d GPSInfo GPSDateStamp Ascii 11 2013:04:11
0x0100 Thumbnail ImageWidth Long 1 320
0x0101 Thumbnail ImageLength Long 1 240
0x0103 Thumbnail Compression Short 1 6
0x0112 Thumbnail Orientation Short 1 1
0x011a Thumbnail XResolution Rational 1 72/1
0x011b Thumbnail YResolution Rational 1 72/1
0x0128 Thumbnail ResolutionUnit Short 1 2
0x0201 Thumbnail JPEGInterchangeFormat Long 1 973
0x0202 Thumbnail JPEGInterchangeFormatLength Long 1 57636
I think I got it now, thanks to the hint from opaco23 Very useful params that you used for exiv2
with this in exynos_exif.c:
exif_attributes->shutter_speed.num = shutter_speed;
exif_attributes->shutter_speed.den = 100;
I get what seems to be proper values in the EXIF tag:
$ exiv2 -u -pv print IMG_20130507_221211.jpg
0x9201 Photo ShutterSpeedValue SRational 1 564/100
$ exiv2 -p a IMG_20130507_221211.jpg
Exif.Photo.ShutterSpeedValue SRational 1 1/50 s
564 is the value of the shutter_speed variable in exynos_exif.c. I think this should be correct.
ghepeu said:
That's interesting, can you print the hex values too ('-h' flag)?
Could you do that for all the values? I'd like to see if there are other things that we're missing, I have no idea what most of them mean so I don't know if what we're getting is sane.
Thank you.
Click to expand...
Click to collapse
Sorry for slow reply. Attached is output of "exiv2 -u -PExgnycvh print foo.jpg", and I also checked
my other photos (not many, I didn't use the camera often), and the ShutterSpeedValue
is always N/100.
Hmmm, still have no solution for exposure time... I don't understand the relation to shutter speed now... But we have to calculate exposure time from shutter speed value, as the camera always gives back zero for exposure time...
This is for an old picture I shot with stock samsung firmware before I switched to cm:
$ exiv2 -u -pv print 20120804_212207.jpg
0x829a Photo ExposureTime Rational 1 1/20
0x9201 Photo ShutterSpeedValue SRational 1 432/100
$ exiv2 -p a print 20120804_212207.jpg
Exif.Photo.ExposureTime Rational 1 1/20 s
Exif.Photo.ShutterSpeedValue SRational 1 1/20 s
In the second representation of the data, it's the same value for exposure time and shutter speed. But the interesting one is the first. I don't know how the 432/100 can be converted to 1/20.
ghepeu is right, we should also check all the other EXIF values for plausibility...
But now I'm tired and go to sleep
opaco23 said:
Sorry for slow reply. Attached is output of "exiv2 -u -PExgnycvh print foo.jpg", and I also checked
my other photos (not many, I didn't use the camera often), and the ShutterSpeedValue
is always N/100.
Click to expand...
Click to collapse
Thank you!
tryptophane said:
I think I got it now, thanks to the hint from opaco23 Very useful params that you used for exiv2
with this in exynos_exif.c:
exif_attributes->shutter_speed.num = shutter_speed;
exif_attributes->shutter_speed.den = 100;
564 is the value of the shutter_speed variable in exynos_exif.c. I think this should be correct.
Click to expand...
Click to collapse
Yes, I think that with that change the ShutterSpeedValue is ok.
I was looking to the other tags, and there are some differences in FNumber and the various SomethingAperture. As far as i can see, all those differences depend on the macros found in hardware/samsung/exynos4/hal/include/Exif.h, becase they round the value to int so soon that a big error is carried on to the calculations in exynos_exif.c.
The attached patches for Exif.h and exynos_exif.c change the macros, a few defines and some calculations to keep two decimal places of precision and the results i get seem ok. I don't know if we can modify that file, though, it seems it was originally samsung code and maybe it should be left as it is.
Incidentally this seems to have fixed the BrightnessValue too, now it gives me ~100 cd/m² on a picture of my monitor, before it gave huge values.
What do you think?
PS. the change for ShutterSpeedValue is included to, and a fix for a typo.
ghepeu said:
Thank you!
Yes, I think that with that change the ShutterSpeedValue is ok.
I was looking to the other tags, and there are some differences in FNumber and the various SomethingAperture. As far as i can see, all those differences depend on the macros found in hardware/samsung/exynos4/hal/include/Exif.h, becase they round the value to int so soon that a big error is carried on to the calculations in exynos_exif.c.
The attached patches for Exif.h and exynos_exif.c change the macros, a few defines and some calculations to keep two decimal places of precision and the results i get seem ok. I don't know if we can modify that file, though, it seems it was originally samsung code and maybe it should be left as it is.
Incidentally this seems to have fixed the BrightnessValue too, now it gives me ~100 cd/m² on a picture of my monitor, before it gave huge values.
What do you think?
PS. the change for ShutterSpeedValue is included to, and a fix for a typo.
Click to expand...
Click to collapse
Hey, nice work again!
Maybe you could change this (let's avoid magic numbers ):
- exif_attributes->shutter_speed.den = 100;
+ exif_attributes->shutter_speed.den = EXIF_DEF_APEX_DEN
Where did you take the number 265 from? I mean, why not 260?
-#define EXIF_DEF_FNUMBER_NUM 26 /* 2.6 */
+#define EXIF_DEF_FNUMBER_NUM 265 /* 2.65 */
As far as I can see here at work (with the rather bad app "Jpeg Exif Viewer") the values look ok compared to old pictures of mine. BrightnessValue looks plausible now.
As cm doesn''t use samsung's blobs anymore for writing the exif data, I guess it should be ok to modify exif.h...
Your patch for exynos_exif.c has an explicit path in the header, had to edit it in order to be able to apply it. Not shure if the exif.h patch would have worked, I edited its header without trying to apply it in the original version. It's better to have old and new file in the same folder before creating the patch, but you know it
We still lack a correct value for ExposureTime. Don't know if this could be of help (taken from the Exif 2.2 specs from exif.org):
ShutterSpeedValue (Tv) = - log 2 (exposure time)
Hey you have 76 thanks for 14 posts, that's not bad, almost as good as Codeworkx's ratio
tryptophane said:
As cm doesn''t use samsung's blobs anymore for writing the exif data, I guess it should be ok to modify exif.h...
Click to expand...
Click to collapse
Maybe I was a little bit hasty with this statement, I don't know which other samsung devices the changes could affect...
tryptophane said:
Hey, nice work again!
Maybe you could change this (let's avoid magic numbers ):
- exif_attributes->shutter_speed.den = 100;
+ exif_attributes->shutter_speed.den = EXIF_DEF_APEX_DEN
Click to expand...
Click to collapse
I thought about it, but since shutter speed is not directly related to the other values that use that constant I didn't want to tie it to them. Shouldn't be an issue, though.
Where did you take the number 265 from? I mean, why not 260?
-#define EXIF_DEF_FNUMBER_NUM 26 /* 2.6 */
+#define EXIF_DEF_FNUMBER_NUM 265 /* 2.65 */
As far as I can see here at work (with the rather bad app "Jpeg Exif Viewer") the values look ok compared to old pictures of mine. BrightnessValue looks plausible now.
As cm doesn''t use samsung's blobs anymore for writing the exif data, I guess it should be ok to modify exif.h...
Click to expand...
Click to collapse
It comes from opaco23 and stone_ship data. It make sense to use it, imho, if the camera blob used it instead of 2.6.
Your patch for exynos_exif.c has an explicit path in the header, had to edit it in order to be able to apply it. Not shure if the exif.h patch would have worked, I edited its header without trying to apply it in the original version. It's better to have old and new file in the same folder before creating the patch, but you know it
Click to expand...
Click to collapse
Thanks, that's what happen when you post things late at night... I replaced the patch on my previous post.
We still lack a correct value for ExposureTime. Don't know if this could be of help (taken from the Exif 2.2 specs from exif.org):
ShutterSpeedValue (Tv) = - log 2 (exposure time)
Hey you have 76 thanks for 14 posts, that's not bad, almost as good as Codeworkx's ratio
Click to expand...
Click to collapse
It could, I'll take a look this evening.
ghepeu said:
Thanks, that's what happen when you post things late at night... I replaced the patch on my previous post.
Click to expand...
Click to collapse
Yeah, saw it was very late What timezone are you in?
.
Excellent work being done here, keep it up
Idk if it helps, but in the old pics I have taken with early CM10 (with Samsung;s blobs, right?) the ExposureTime value range goes from ~1/5518 secs (value "0.000181225084816106" secs) to ~1/14secs (value "0.0714285746216774" secs) and additionally 1/2 or 0.5 secs for night mode.
The ShutterSpeed ranges from 12.4300003051758 to 3.82999992370605 (comment on the Exif Pilot prog: The unit is the APEX (Additive System of Photographic Exposure) setting.). Maybe the raw values rather refer to the Exposure than the Speed? Like 1/504?
There's a thing also that I dont know if it has some influence. Afaik, there are two camera models for the i9100, one made by Sony and the other by Samsung. I dont know if they may output different data, or since both are serviced by a Fujitsu chip, the output is the same. Just FYI.
http://forum.xda-developers.com/showthread.php?t=1765679
ghepeu said:
It could, I'll take a look this evening.
Click to expand...
Click to collapse
Hi ghepeu, has there been any more progress from your side? Did you submit your last changes?
tryptophane said:
Hi ghepeu, has there been any more progress from your side? Did you submit your last changes?
Click to expand...
Click to collapse
Had a couple of very busy days :/ I'll submit both patches later and we'll see if changes to Exif.h are allowed or not.
ghepeu said:
Had a couple of very busy days :/ I'll submit both patches later and we'll see if changes to Exif.h are allowed or not.
Click to expand...
Click to collapse
Hi ghepeu,
this fixes the ExposureTime bug:
in Exif.h, add:
#define APEX_SHUTTER_TO_EXPOSURE(x) (int) (pow(10, x /100.0 * log10(2.0)))
in exynos_exif.c:
exif_attributes->exposure_time.num = 1;
exif_attributes->exposure_time.den = APEX_SHUTTER_TO_EXPOSURE(shutter_speed);
Not shure if the function should be named APEX_* though...
People are reporting in the cm10.1 thread that EXIF-data is not shown well in Picasa... I'm not willing to test it, because I don't want to use all those google services. Don't even have a G+ account... But maybe this will be fixed anyway by the last modificatons...
tryptophane said:
Hi ghepeu,
this fixes the ExposureTime bug:
in Exif.h, add:
#define APEX_SHUTTER_TO_EXPOSURE(x) (int) (pow(10, x /100.0 * log10(2.0)))
in exynos_exif.c:
exif_attributes->exposure_time.num = 1;
exif_attributes->exposure_time.den = APEX_SHUTTER_TO_EXPOSURE(shutter_speed);
Not shure if the function should be named APEX_* though...
Click to expand...
Click to collapse
That's fantastic! Wouldn't pow(2, x / 100) work all the same, though?