Notices


Reply
Thread Tools
casper27's Avatar
Posts: 844 | Thanked: 521 times | Joined on Jan 2009 @ UK southampton
#61
Originally Posted by Swirnoff View Post
How can I tell which ver of kernel I have installed?
xterm

Code:
uname -a
 
jaeezzy's Avatar
Posts: 664 | Thanked: 160 times | Joined on Jul 2008 @ Australia
#62
Hi, I'm using fcamera 0.1.6. Last time I was using and the picture got stuck after taking it and the only way I could get rid of it was closing the app.. Now, I can't open the app at all. I reinstalled fcam-drivers, fcamera but no success then I completely uninstalled all the fcam-drivers, fcamera, hdrcapture, lowlight but still the same problem persists. I did restart and all...I'm using enhanced kernel v37.
 
Harick's Avatar
Posts: 140 | Thanked: 369 times | Joined on Jun 2010 @ Ituzaingo, Argentina
#63
Originally Posted by jaeezzy View Post
Hi, I'm using fcamera 0.1.6. Last time I was using and the picture got stuck after taking it and the only way I could get rid of it was closing the app.. Now, I can't open the app at all. I reinstalled fcam-drivers, fcamera but no success then I completely uninstalled all the fcam-drivers, fcamera, hdrcapture, lowlight but still the same problem persists. I did restart and all...I'm using enhanced kernel v37.
turn off, remove battery, put it in, turn on again, hdr and lowlight should work now, till next time you execute fcamera

Last edited by Harick; 2010-08-28 at 02:06.
 

The Following User Says Thank You to Harick For This Useful Post:
Posts: 5 | Thanked: 0 times | Joined on Mar 2010
#64
Originally Posted by jean2323 View Post
fcam drivers are the problem ... i installed blessn900 that uses the same drivers and i get the same results
- application won't load
- LEDs not working

how can i install the old drivers?
Different symptom for me: BlessN900 works fine, but FCamera does not start.
 
jaeezzy's Avatar
Posts: 664 | Thanked: 160 times | Joined on Jul 2008 @ Australia
#65
I'm recently experiencing this problem: after continuously taking ~7 pictures it slows down and the device becomes useless. Anyone else experiencing similar problem? thanks
 
Posts: 46 | Thanked: 392 times | Joined on Apr 2010 @ Stanford University
#66
Hi all,

We uploaded fcamera-0.1.7 to extras-testing on Friday. No new features, just bug fixes to the LED and a few fixes inherited from FCam itself.

Please let us know if anything isn't working right, otherwise we'll hopefully get this version into extras.
 

The Following 5 Users Say Thank You to ETalvala For This Useful Post:
Posts: 46 | Thanked: 392 times | Joined on Apr 2010 @ Stanford University
#67
Originally Posted by jaeezzy View Post
I'm recently experiencing this problem: after continuously taking ~7 pictures it slows down and the device becomes useless. Anyone else experiencing similar problem? thanks
Do you have 'save as JPEG' enabled? We've seen some phones where the background indexer goes nuts and makes the whole phone chug when you're saving JPEGs all the time.
 
jaeezzy's Avatar
Posts: 664 | Thanked: 160 times | Joined on Jul 2008 @ Australia
#68
Originally Posted by ETalvala View Post
Do you have 'save as JPEG' enabled? We've seen some phones where the background indexer goes nuts and makes the whole phone chug when you're saving JPEGs all the time.
Oh yes I'm. So you saying its the tracker indexer causing the trouble? Is it possible to be able to save those pics in JPEG later without having to use computer?
 
Posts: 1,378 | Thanked: 1,604 times | Joined on Jun 2010 @ Göteborg, Sweden
#69
see http://fcam.garage.maemo.org/download.html and the app "fcamDngUtil". It converts DNF to jpg on the n900 I believe but it is command line only.

Another approach is to install tracker-cfg and bring tracker to order....
 
Posts: 515 | Thanked: 259 times | Joined on Jan 2010
#70
Has anyone gotten the fcamDngUtil script to work? My system is Windows 7 64-bit and no matter what I do, I get no output. Anyone else run into the same?

Code:
V:\Pictures\2010\2010>fcamDngUtil -i photo2010.07.05_19.52.11.41.dng
  Reading input DNG photo2010.07.05_19.52.11.41.dng
        Dump of FCam::DNGFrame photo2010.07.05_19.52.11.41.dng at cd1878:
          Source file name: photo2010.07.05_19.52.11.41.dng
          Number of calibration illuminants: 2
          Illuminant 1: 3000 K, conversion matrix:
                [ [ 1.730 -0.275 -0.455 -42.611 ]
                  [ -0.377 1.092 1.786 -37.731 ]
                  [ -0.237 -2.045 7.620 -27.045 ]
         Illuminant 2: 6500 K, conversion matrix:
                [ [ 1.893 -0.362 0.082 -39.532 ]
                  [ -0.324 1.299 0.025 -26.969 ]
                  [ -0.090 -0.755 2.476 -20.953 ]
        ** Dump of cached DNGFrame thumbnail image data follows
        Image DNGFrame::thumbnail at cd19c0 with dimensions 640 480 type 0
          bytes per pixel 3 bytes per row 1920
          data 7e50b1ea buffer 7e500000
          refCount ce4670 = (2), mutex ce4680, memmapped true, holdingLock false

        ** Dump of base Frame fields follows
        Dump of FCam::Frame base frame at cd1878:
          Exposure start time: 2010.08.05_19.52.11.41 end time: 2010.08.05_19.52
.11.52
          Processing done time: 2010.08.05_19.52.11.52
          Exposure: 40011 us, Frame time: 77412 us
          Gain: 2.906250, White balance: 4257 K
          Histogram details:
                Valid: no
                Buckets: 0, Channels: 0
                Region: (0, 0) - (0, 0)
          Sharpness map details:
                Valid: no
                Channels: 0, Size: 0 x 0
          Camera RAW to sRGB(linear) conversion matrix at current white balance
setting:
                [ [ 1.362 -0.242 -0.120 -40.922 ]
                  [ -0.260 0.903 0.614 -31.829 ]
                  [ -0.117 -1.002 3.593 -23.704 ]
          Sensor bayer pattern: GRBG
          Min raw value: 0, max raw value: 959
          Camera Model: Nokia N900, Manufacturer: Nokia
          Tag map contents:
           Key: "lens.maxZoom" Value: 5.19999981e+00f
           Key: "lens.wideApertureMax" Value: 2.79999995e+00f
           Key: "lens.apertureSpeed" Value: 0
           Key: "lens.minZoom" Value: 5.19999981e+00f
           Key: "lens.wideApertureMin" Value: 2.79999995e+00f
           Key: "lens.finalZoom" Value: 5.19999981e+00f
           Key: "lens.initialZoom" Value: 5.19999981e+00f
           Key: "lens.focusSpeed" Value: 0.00000000e+00f
           Key: "lens.zoomSpeed" Value: 0
           Key: "lens.aperture" Value: 2.79999995e+00f
           Key: "lens.focus" Value: 3.14999998e-01f
           Key: "lens.initialAperture" Value: 2.79999995e+00f
           Key: "lens.finalFocus" Value: 3.14999998e-01f
           Key: "lens.zoom" Value: 5.19999981e+00f
           Key: "lens.finalAperture" Value: 2.79999995e+00f
           Key: "lens.initialFocus" Value: 3.14999998e-01f
          Requested shot contents:
                ID: 1, wanted: yes
                Requested exposure: 39996, frame time: 0
                Requested gain: 2.921173, requested white balance: 4257 K
                Requested histogram configuration:
                        Enabled: no, buckets: 64
                        Region: (0, 0) - (0, 0)
                Requested sharpness map configuration:
                        Enabled: no, size: 0 x 0
                Requested actions:
        **  Dump of requested image object follows
        Image Frame::Shot::image at cd1930 with dimensions 0 0 type 5
          bytes per pixel 0 bytes per row 0
          data 0 buffer 0
          refCount 0 = (0), mutex 0, memmapped false, holdingLock false
        **  Dump of frame image data follows
        Image Frame::image at cd187c with dimensions 2592 1968 type 4
          bytes per pixel 2 bytes per row 5184
          data 7e5f0008 buffer 7e5f0000
          refCount ce4218 = (2), mutex ce4228, memmapped true, holdingLock false

  Done!
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 15:04.