(MOD) FFC Development Clean Thread
- Thread starter orells
- Start date
Miui can use it.
just flash this from recovery.
http://xdaforums.com/showpost.php?p=15595377&postcount=6
And I'm done with android for the time being.
too many people that don't search and ***** about everything.
enjoy
just flash this from recovery.
http://xdaforums.com/showpost.php?p=15595377&postcount=6
And I'm done with android for the time being.
too many people that don't search and ***** about everything.
enjoy
Last edited:
So flashing this with v1 using CM7 should work too? Are the banding issues still present with the v1 version? Is anyone using the v1 version with CM7 and can tell about how good it is? Thanks!
I agree. $45 with free shipping & handling for the revised v2 camera is at mobiletechvideos.com.
Last edited:
After installing it seems like the camera quality went down a notch, but i'll get over it, my vibrant just became a little bit newer.
ok I put in the ffc v2 cam . Im currently running juwe v5 and the video ffc looks great and the pictures from rear are awesome! no banding etc. The video in "tango,qik,oovoo is sideways"
How ever, when making a video voice mail with qik as im recording..everything looks great, but on playback I now have colored bars [almost like a codec issue?]
heres the link http://qik.com/video/44831130.
not sure where to go from here. would really prefer to stay with a gingerbread rom if at all possible. But if the only way to use the ffc is to go back to a froyo ver then so be it.
would appreciate the best rom/kernal/ffc combo out there. I have looked at the versions listed on other thread here and either they don't exist or i cant find them, some the d/l links are no longer any good.
thanks again
How ever, when making a video voice mail with qik as im recording..everything looks great, but on playback I now have colored bars [almost like a codec issue?]
heres the link http://qik.com/video/44831130.
not sure where to go from here. would really prefer to stay with a gingerbread rom if at all possible. But if the only way to use the ffc is to go back to a froyo ver then so be it.
would appreciate the best rom/kernal/ffc combo out there. I have looked at the versions listed on other thread here and either they don't exist or i cant find them, some the d/l links are no longer any good.
thanks again
I'm on latest miui.us and use glitch kernel and I have wrong orientation...
Sent from my T959 using XDA Premium App
Sent from my T959 using XDA Premium App
Yah I wish the price is around 30 too, 45 is a little steep. Especially with sgs2 Tuesday and the new nexus around the corner.
Sent from my SGH-T959 using XDA App
Sent from my SGH-T959 using XDA App
Can I ask what you guys with the actual T959V cameras are running software-wise to support it without 90 degrees off issues?
Any way to buy FFC anymore or is this thread only for those who already own one?
It seems to be out of stock everywhere I looked; I would welcome any suggestions and/or if one of the members wish to sell his (he/she could PM me if that's the case).
It seems to be out of stock everywhere I looked; I would welcome any suggestions and/or if one of the members wish to sell his (he/she could PM me if that's the case).
lol 10 char
I have not been able to get FFC to work on CM7 stable
Some scripting error with the OP FFC.zip
Also tried the CM7 specific cwm flashable along with manually pushing libcamera.so and it just gets stuck at boot...
Any suggestions?
Some scripting error with the OP FFC.zip
Also tried the CM7 specific cwm flashable along with manually pushing libcamera.so and it just gets stuck at boot...
Any suggestions?
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
128So everyone begged for it and here it is, a beggining to end revamp of the ffc mod thread.
Original threads:
http://xdaforums.com/showthread.php?t=770854
http://xdaforums.com/showthread.php?t=804146
(note im doing this from my phone, so please let ne know of any typos, broken links, or missed topics)
This will be in Q&A form, so lets get started.
1) Where do I get an FFC?
Globaldirectparts.com sells them in bulk, shipping is slow, so now your best bet is ebay.
2) How do I install it?
Start here:
http://www.youtube.com/watch?v=gOvt6atrin8&feature=youtube_gdata_player
Then here:
http://xdaforums.com/showpost.php?p=8436475&postcount=375
Video removed...
3) I got it installed, but how do I use it?
Most custom roms include support for the ffc. If yours does not there is a flashable zip here:
http://xdaforums.com/showpost.php?p=11172683&postcount=1482
4) My FFC is blurry... wtf?
You need to focus it, there is a small ring on the FFC, play with it until you find the sweetspot for you.
5) There are red lines in low light, is there a fix?
Currently no, there has been signifigant progress on lowering the amount, but its not perfect yet. Be patient its coming.
6) How do I videochat?
First you need an app called sgstools, get it here:
http://www.mediafire.com/?xtw16417su40j7b
Next go into the .prop editor and select build.prop. Press menu, and then unblock. Now for every field that reads "SGH-T959" change it to "GT-I9000". Hit menu then save, now reboot. You can now go to tye market and download apps such as fring and Tango!
7) In the chat app, my image is rotated 90degrees.
Its an app problem. Ask the person you are chatting with if they see you sideways, if they say yes, uninstall the app and try changing your build.prop to SPH-D700.
8)What if I have more questions?
Ask them here, I vow to keep this thread flame free. (although there will be sarcasm)
9)What is SGStools?
Its a program used to install the i9000 cam, change build.prop, anf even access hidden features of your phone such as gps test and network status. You can find the latest version here:
http://www.mediafire.com/?xtw16417su40j7b
Thanks to Sirrial, Kellylewis, Scrizz, Master, Eugene, hell everybody, we've been working on this for 4 mos. and we are the reason the Vibrant 4g exsits.
Update: There is an update to sgstools. After you install, reboot then open your market. When you look at your apps list you will see an update, dont click it you'll get an error. Instead, long press it and select update.
(I didnt do this to step on toes. There was a huge demand for this. If you want faster production I highly advise on donating to Kellylewis, he is trying to juglle this project along with life and service to.his country, correct me if i'm wrong there. Also I purposefully left out the test kernals posted before because they aren't a full fix and have produced errors with kb1 roms)
Sent from my SGH-T959 using XDA App5Hey, connexion, if this thread is closed, you will probably be getting my business. I've waited patiently for months now. I'm not sure I would want to wait to find out the results of Kelly's hard work if that happens, so I'd just as well buy another cam. It would be a shame, if the thread was closed, that is.
If this thread is closed im done. I will go somewhere else and work on phones, I have had enough trolls for a lifetime. On a more positive note were making great progress on the kernel. I should be able to give an answer as to whether or not it fixes the old cams soon.
Sent from my SGH-T959V using XDA Premium App4I tried guys and gals and failed. The kernel dev never wrote me back to tell me if it was possible and I tried myself and it didnt work. I apologize everyone, I just dont know what else to do to help. Having said that unless something else comes about that I can try I believe this is done with.3
Its driver related. If i can get the drivers ported completely it may fix the banding altogether.
If your feeling generous.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=9LJGLQUYYDZR22Banding not due to voltage? Two camera drivers are in play.
I think that it's possible that the banding is *not* due to a voltage issue after all. Here's why: There are two different camera chip drivers in play in my Vibrant with FFC mod. They are being switched on and off separately already (Bionix-v-1.2):
This is in the kernel log after activating and deactivating the rear
camera.
[ 1596.088674] ce147_power_on
[ 1596.899428] fw M:5 m:15 |prm M:5 m:15
[ 1596.899480] y. m. d = 2010.9.7
[ 1596.899508] ce147_get_main_sw_fw_version Enter
[ 1596.899538] already read main sw version
[ 1596.899570] FW Version: 5.15
[ 1596.899599] PRM Version: 7.55
[ 1596.899630] Date(y.m.d): 2010.5.27
[ 1596.899657] Sensor version: 16
[ 1667.853820] ce147_power_off
This is in the kernel log after activating the FFC using the "Mirror app".
[ 1300.121338] ce147_power_off
[ 1300.166004] s5ka3dfx_s_fmt is called...
[ 1300.166108] s5ka3dfx_s_ctrl() : ctrl->id 0x08000070, ctrl->value 0
[ 1300.166120] s5ka3dfx_s_ctrl() : ctrl->id 0x08000030, ctrl->value 0
[ 1300.166160] s5ka3dfx_power_on
[ 1300.179877] camera initialization start, state->vt_mode : 0
[ 1300.179884] state->check_dataline : 0
[ 1300.193791] S5KA3DFX 0-0062: s5ka3dfx_init: register set failed
[ 1300.193800] S5KA3DFX 0-0062: s5ka3dfx_init: camera initialization failed. err(100)
[ 1300.199909] s5ka3dfx_enum_framesizes is called...
[ 1300.199916] s5ka3dfx_enum_framesizes is called...
[ 1300.199923] s5ka3dfx_s_ctrl() : ctrl->id 0x08000040, ctrl->value 1
[ 1300.199930] s5ka3dfx_power_on
[ 1300.212737] camera initialization start, state->vt_mode : 0
[ 1300.212744] state->check_dataline : 0
[ 1300.267748] s5ka3dfx_s_ctrl() : ctrl->id 0x08000040, ctrl->value 1
[ 1300.267781] s5ka3dfx_s_ctrl() : ctrl->id 0x08000048, ctrl->value 0
[ 1300.267788] state->vt_mode : 0
[ 1311.068267] s5ka3dfx_s_ctrl() : ctrl->id 0x0800005d, ctrl->value 0
[ 1311.208820] s5ka3dfx_power_off
So there's the ce147, for the rear camera, and the s5ka3dfx, for the FFC. I think that the NEC-MC-10170 must be some sort of i2c bridge circuitry. The ribbon on the dual camera module is marked with "M110S". There is a source tarball for the Korean M110S, a hardware version of the I9000. There are a few source differences in the ec147 driver there. I have not yet tried to build and run a kernel built with those modifications.
I think that the banding is either a low-light problem, and so due to amplification, noise-reduction, ISO settings... or that it's a framing problem, where the area of interest sent by the camera is different than what the software thinks it is, so that some scan lines sweep across, sort of like... I can't explain easily; like stepping through an array when you assume the wrong dimensions.
