Just got my Qtek 9100 today and I tried to tweak the date/time display on the top right corner of the display, ie. go to shell and create binary value TBOpt 13 00 00 00. And unfortunately... the time is fine, but the date is in BOLD format, so I couldn't see the year. That is, it looks like this:
25/11/0
18:05
-> only 0 in year part, 5 is missing. Any1 how to do it properly? Pls show me. thnx ^^
I've been searching for 2 days, but nothing so far. I think Universal users have this problem too.
spb pocket pc tips & tricks
Have you guys tried spb pocket pc tips & tricks? This will perform this tweak for you, although the value mentioned TBOpt 13 00 00 00 is the same on my magician.
I deleted the key TBOpt from HKLM/software/msft/shell, and the time is still there in bold.
I tried tweaking with battery pack pro, but they only add the 13 00 00 00 value into the TBOpt registry.
I haven't seen a fix for the bold font yet. I tried the Universal registry tweak, which allowed me to change the date to a M/DD format that was not on the regional settings list.
The problem is it also made the OK button go away. Made it a bit difficult to close my programs, so back to the bold.
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.
How do you change the color from the text on the today screen, my appointments are in white on a white background.
In the registry go to HKLM\Software\Microsoft\Color\4. Change the value to "00 00 00 00" for black or "00 00 FF 00" for blue. I try more colors without problems. I use FF FF 80 00 for yellow. this is well seen for quite a light background (photo)
notice: modify this registry key with memaid was weird. I try then total commander and there was no problem.
Martikn said:
In the registry go to HKLM\Software\Microsoft\Color\4. Change the value to "00 00 00 00" for black or "00 00 FF 00" for blue. I try more colors without problems. I use FF FF 80 00 for yellow. this is well seen for quite a light background (photo)
notice: modify this registry key with memaid was weird. I try then total commander and there was no problem.
Click to expand...
Click to collapse
thanx I'm gonna try it out.
where i found colour codes ?
where i found colour codes ? for all colours ?
maid3n said:
where i found colour codes ? for all colours ?
Click to expand...
Click to collapse
Try this:
http://www.colorpicker.com/
Copy the color from the upper text box, remove # sign and add "00".
If you want to understand what it means you can take a look here:
http://web.njit.edu/~kevin/rgb.txt.html
http://cloford.com/resources/colours/500col.htm
The first three groups of numbers (00 00 00) are standing for RGB (red green blue) in hexadecimal.
where can I find the registery using TCM? Thanks in advance
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?