Related
MODDING THE SAMSUNG VIBRANT TO HAVE A FRONT FACING CAMERA (FFC)
DISCLAIMER: It is NOT my fault if this Breaks your Device, or if you screw it up trying to do it. blah blah you know the drill. XDA is also not responsible. This WILL void your warranty. Luckily it is easy to do.
***THIS IS ONLY FOR THE VIBRANT***
Other phones are slightly different inside
Required:
-Compatible rom (Bionix fusion or eugene's froyo or any rom that the dev specifically says ffc compatiable)
-JAC's OC/UV Kernel. Stock kernel will not work, period. Voodoo should also work KK's kernel also does not work.
-An FFC, of course (see below for where to get it)
HOW TO DO IT:
1. Open your phone
2. Remove the 7 screws or so
3. Remove the internal battery cover.
4. Remove your Vibrant camera... it is snapped in under the cam chip.
5. Using Goof OFF! or denatured alcohol or something similar, dip a q-tip in the chemical, and slightly dab the whole where it is to go.
6. Let it sit for 10-20 minutes, and repeat (or if you are anxious, don't wait...)
7. Using something plastic for the safety of the digitizer glass, and scrape out the gunk.
8. Now, definitely let everything dry before putting your phone back together, and MOST definitely before you put the battery in and turn it on. Give it 20-30 minutes to be safe... depends on the chemical used.
I used a flat head screw driver, which is metal, but if you choose this USE EXTREME CAUTION!!
For more info, go to my thread in the General section as I may have missed something/got something wrong in this post. It has been a while since I first did this mod...
Useful tidbits:
If you get force closes when trying to use a the cam, then you did not read instructions. Use the proper kernel.
Banding is present in low light conditions. This looks to be a software issue. Popular belief is that the phone is powering both cameras at the same time when either is called, and is basically confusing itself. This is a work in progress.
Software that is known to work is Fring, various lame mirror apps, etc. Android video calling is only available in Froyo, but I have not tested it recently since Eugene's R3, so I cannot confirm that it working ATM. Tango may also work.
Attached the mach.aries file for those of you that wanna chip in and do some digging. Looks like most of the things we need are in there. Attached a .rar and a .zip file... for some reason I had both? It's been a loooong couple weeks.
Epic camera: thanks to KellyLewis3985 for the dl.
http://db.tt/0DEkw9X
How to Flash:
1. Download the ZIP and put it on the root of your INTERNAL SD Card.
2. Open ROM Manager and boot into ClockWorkMod (DO NOT use Stock Recovery) or boot into recovery the manual way.
3. Navigate down to "apply sdcard: select zip" and locate the .zip file in your internal SD card. Push the power button, navigate down to "YES" and push the power button once more.
4. Let it do its thing, and reboot. First boot *may* take an extra second... Play with new cam app.
To get a cam:
Just got some more cams ordered... should have them by the weekend, so any orders now will start shipping 11/8 in the order they are received.
Go here: http://bit.ly/8ZEPW4
UPDATES:
So, now my desktop is totally dead... makes noises it shouldnt right when i turn it on... have to replace... grrr
-----------------------------------------------------
Got some donations recently, just wanted to say thanks, but the good people here on XDA do not need to pay for one kid's dooschery. I returned the donations back to you. Here is the response sent with the refunds:
Hey man, I appreciate the donation... but the overwhelming support I received the other day on xda was more than enough. This one guy got me down for a night, and you guys picked me up. No one else on xda should pay for his dooschery. Again THANKS
Click to expand...
Click to collapse
I feel that there are some things more valuable than money. I wasn't pissed about losing $30 as I was about the principle and that someone would have the audacity to rip someone off that is trying to help. Again thanks.
-----------------------------------------------------
Well, due to over whelming support, i'm not done. Last batch has sold out, and some new options have presented themselves. Also, with the help of a few others, they are getting mad progress on diving through source code working on the banding issue... Keep following this thread for progress.
-----------------------------------------------------
So.... An ebay user who is also an xda member deliberately screwed me out of a camera and the money for it, so after this batch is gone, i'm done. He never updated his address with ebay or paypal, and of course i sent it to the address i had... and he got ebay to not only refund the full price but keep the fees for the sale and money transfer. Way to say thanks to the guy that got this started... asshole. oh! i get it. he is just out of high school and is a little slow to how the world works. probably because he "works on a farm with 70 dairy cows." <- quote from him.
-----------------------------------------------------
Next batch of ffc cams are coming in for those of you who do not have one yet. New listing, donating some of the process to breast cancer research/awareness...
eBay listing here SOLD OUT
Still settling in after the move and new job... Still w/o internet at my house too... So I am limited in what else I can do right now... Hopefully getting these out will help some of you.
-----------------------------------------------------
Breaking news available via my twitter feed of #vibrantFFC. my original thread here: http://forum.xda-developers.com/showthread.php?p=7941083
-----------------------------------------------------
This thread is for android/software development of the FFC for the Vibrant. Software and ROM support is insufficient atm, so let's get that fixed.
To see how to add the FFC, check this thread: http://forum.xda-developers.com/showthread.php?t=804142
To get a camera check this thread: http://forum.xda-developers.com/showthread.php?t=804122 or hit up my ebay listing here. buying cams from the wholesaler in large quantities to provide them to you individually... Wholesaler had minimum order requirements.
Currently, I have only tested the FFC in JP3 and Bionix. Mirror app works fine, but is useless.
Video calling is doable, but not available in Bionix. Is available in JP3, but is broken.
Have not had a chance to test Tango, but Fring looks to be coded to use the rear camera...
UPDATE: there has been a lot of progress recently. Halfway through reading all of the threads... Seriously have note had much time, but should be able to finish compiling all of the info into this post soon.
-----------------------------------------------------
siirial said:
Currently, I have only tested the FFC in JP3 and Bionix. Mirror app works fine, but is useless.
Video calling is doable, but not available in Bionix. Is available in JP3, but is broken.
Have not had a chance to test Tango, but Fring looks to be coded to use the rear camera...
Any more ideas?
Click to expand...
Click to collapse
Hi, Siirial. Is that Bionix 1.7? I can't get Mirror app to work.
Tango doesn't work yet but I emailed the developers and they said it will be included in their next release
memorito said:
Hi, Siirial. Is that Bionix 1.7? I can't get Mirror app to work.
Click to expand...
Click to collapse
Ok, I am a little confused as to which thread I should be posting in. But here goes.
My FFC wont load in Mirror App using Bionix 1.8 Stock Kernel.
Here is the logcat. http://pastebin.com/biJmEhPr
----------- Edit -----------
Ok, so I finally got around to installing a Rom with a modified kernel. (Specifically Bionix 1.8 w/ Jacs)
The Mirror app now loads the FFC and the image is actually better than the rear cam at the moment.
So, it looks like whatever is going on in the kernel makes a huge difference. Perhaps someone can
take a look at the i9000 and Bell SGS Kernel's.
Posted this in the other thread and it was recommended that I post it here:
Just a thought to kick around some ideas, has anyone looked at this?
http://developer.android.com/reference/android/hardware/Camera.Parameters.html
Looks like there are a few options that could be tweaked, including 'antibanding' for 50 and 60hz
memorito said:
Ok, so I finally got around to installing a Rom with a modified kernel. (Specifically Bionix 1.8 w/ Jacs)
The Mirror app now loads the FFC and the image is actually better than the rear cam at the moment.
So, it looks like whatever is going on in the kernel makes a huge difference.
Click to expand...
Click to collapse
i believe the above it true, i am running bionix 1.8 with the kk kernel, and i cannot get the mirror app to work, will load in the jacs kernel and see the difference.
edit:
i reloaded Bionix 1.8 with Jacs oc/uv without voodoo, and can now confirm the front camera working with the mirror app, albeit grainy
Could not get FFC to work on Bionex 1.7 Stock kernel. Third the kernel info.
paradox4286 said:
i reloaded Bionix 1.8 with Jacs oc/uv without voodoo, and can now confirm the front camera working with the mirror app, albeit grainy
Click to expand...
Click to collapse
Grainy or blurry?
If blurry, you can rotate the focus ring on the actual camera. That's what Cobra did to fix his.
Received camera, installed and confirmed that mirror app works on Bionix 1.7 with JAC voodoo kernel(voodoo activated). Unfortunately, the rear camera problem still exists. Tweaking focus now via outer ring of FFC.
Just installed the new camera. Still on stock JI6 ROM. Banding happens. I recorded some video and can post it if people are interested. Might check if there is any logging that happens when the camera starts up.
memorito said:
Grainy or blurry?
If blurry, you can rotate the focus ring on the actual camera. That's what Cobra did to fix his.
Click to expand...
Click to collapse
ahh gotcha, i'll try that when i get home after work.
when using the rear camera in vignette, the area where the camera chip is gets very warm after not very much use.
maybe the stock vibrant camera data files don't place nice with the i9000 camera
Does any dev have a cam yet?
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
orells said:
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
DO IT! LOL
Um, I would try it but I am on a Mac... so even worse, should it brick.
orells said:
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i dont think fring works on the i9000 either...
I read in another post that a person flashed the captivate Rom on to the vibrant and it worked..everything works good...what if we try to flash the i9000 Rom on to the vibrant...won't.that work perfectly since the settings for the camera is already set up...we should try it.
Sent from my SGH-T959 using XDA App
Video Calls
orells said:
So here's a thought, can I use sgs tools-prop.editor and change the info there to mimic the i9000? I nelieve it will trick fring (and all other apps) into thinking my phone is an i9000, but I dont wanna brick my **** as my laptop is not with me to odin.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I used SGS tools as you suggested and changed the ro.product.model to GT-I9000, rebooted, and the FFC works on the test call. I have yet to try it on Tango, because it is early in the morning and it takes two to tango. (Sorry could not resist)
Thats the ****! Where can I find the info to change it to?
Sent from my SGH-T959 using XDA App
Requirements: Android
Overview: The speaker itself isn’t of the highest quality but the Android Community wanted to squeeze as much as possible from it. A project then came along to improve the audio quality and volume and hence AudioHack was born.
* NO NEXUS SUPPORT EVER
v3.6
* Now includes Widgets!
* Please run app before widget
* App may require a restart
Nice idea. I installed it, tried IC2 and IC3 and neither seam to show a difference. Perhaps a more detailed guide needs to be created? Aside from your color chart, the rest is kind of foreign to me.
TheRomMistress said:
Nice idea. I installed it, tried IC2 and IC3 and neither seam to show a difference. Perhaps a more detailed guide needs to be created? Aside from your color chart, the rest is kind of foreign to me.
Click to expand...
Click to collapse
+1 - or just get Audio Booster, pull all adjusters to the right (full volume) and voila!!
matt
Not working
not working... Nothing happens
Interesting concept, care to explain a bit more about how this works (some have said they have noticed no difference) ?
100% working just flash the rom one more time and chk
cool man,I need sth like that for my subwoofer
Ill try it
Thanks, I'll be trying this out shortly.
Always wanted a louder speaker on Android. WM7 seemed louder with same mp3 as ringtone then Android.
This doesnt work for me. Any alternative??
matthew33 said:
+1 - or just get Audio Booster, pull all adjusters to the right (full volume) and voila!!
matt
Click to expand...
Click to collapse
Looked for "Audio Booster" in the Market. Nada. Does it have another name? Or should I look somewhere else?
Thanks.
-Bob-
any chance for some version for Nexus?
What a shame no nexus support :s
Does not work for me. I get an error message that tells me to restart the app, I do and i get the same message.
Working fine on SD Desire HD
I know this is posted in the HD2 section but when you say "NO NEXUS SUPPORT" are you referring to the Nexus One phone, or Nexus based builds?
sbryan12144 said:
I know this is posted in the HD2 section but when you say "NO NEXUS SUPPORT" are you referring to the Nexus One phone, or Nexus based builds?
Click to expand...
Click to collapse
They are saying Nexus builds are not supported and never will be. There must be something in those that is incompatible with this .
produces no effect on desire HD :-(
for those who have a phone with which it works, there is an update 4.1
--> http://androidaudiohacks.com/home/
Borisdm said:
100% working just flash the rom one more time and chk
Click to expand...
Click to collapse
I think that emoticon tells me that something smells fishy here.
not working on hd2 android nand
Uhm... Louder Volume Hack v3.6 is a PAID app on the market. Is this even legal to post here?
Mods?
Hi All. Long time follower on XDA for the G1 (9 months after the G1 debut) but first time posting. I just recently did the 2708+hboot hack for the 14mb to flash and test the lastest ROMs. I've tried everything that is currently available for download on XDA development and found that Laszlo 5.2 to be the smoothest and fastest (just as fast as Super CSDI).
I read through the entire post to see if anyone has experienced the same thing as I did, but no one really did. This ROM is amazing and everything is working great, but one thing. My question is--The Audible selection and screen lock sound do not work. One person ask about the screen lock sound not working, but no one answered. Is anyone else getting this problem besides me and is there a fix. I flash it several times and on 3 different G1s and get the same results. Maybe the download of the ROM I'm flashing is slightly corrupt. Any thoughts??? Thanks everyone for all your help through these years keeping the G1 alive and still amazing.
Rick SJ said:
Hi All. Long time follower on XDA for the G1 (9 months after the G1 debut) but first time posting. I just recently did the 2708+hboot hack for the 14mb to flash and test the lastest ROMs. I've tried everything that is currently available for download on XDA development and found that Laszlo 5.2 to be the smoothest and fastest (just as fast as Super CSDI).
I read through the entire post to see if anyone has experienced the same thing as I did, but no one really did. This ROM is amazing and everything is working great, but one thing. My question is--The Audible selection and screen lock sound do not work. One person ask about the screen lock sound not working, but no one answered. Is anyone else getting this problem besides me and is there a fix. I flash it several times and on 3 different G1s and get the same results. Maybe the download of the ROM I'm flashing is slightly corrupt. Any thoughts??? Thanks everyone for all your help through these years keeping the G1 alive and still amazing.
Click to expand...
Click to collapse
im not sure exactly what it is your talking about but i know besides what your saying i have no complaints about this rom... buuuuuuut it is getting old and hasn't had an update since i remember.. so im sure **** will be hitting the fan soon... all we can do is hope a better rom comes out or hope somebody has the balls to try messing with lazlo rom to improve on its minor bugs and issues
wish i could help you more but i have no idea what that is haha
Well do u get the sounds he's asking about. I wonder if the ogg files are present. I'm not on fbl atm so I'm not sure
sent from my transparent xda app by the impaler747
johnson8cyl said:
Well do u get the sounds he's asking about. I wonder if the ogg files are present. I'm not on fbl atm so I'm not sure
sent from my transparent xda app by the impaler747
Click to expand...
Click to collapse
im not using that rom at the moment but as far as i know the sounds were working.. is he using a kernel with it? maybe its messing with it..
Don't know what you mean by "Audible selection", but I would guess for the lock/unlock sound you need to install the audio from addons (since it contains the file). Type "addons" in terminal and follow the on-screen prompts.
The Audible selection and screen lock sound
what is this?
edward0119 said:
The Audible selection and screen lock sound
what is this?
Click to expand...
Click to collapse
Sounds when u unlock
sent from my transparent xda app by the impaler747
Hi Adam, your the Man!
Thank you so much. Your suggestion fixed it. I was playing with Super Aosp 6.0 when you made the suggestion and I was very hesitant to flash again to find out that it might do nothing. But the speed of Laszlo was just to good to not find out, so I did and I'm glad I did.
I'm surprised that hardly anyone knew what I was talking about. So to clarify, if you go into Setting>Sound and then scoll down a bit you will see Audible selection and Screen lock sound options. The Audible selection is when it makes a 'Click' type sound when you select something. That extra audible feedback is very helpful.
I was going to just put up with Laszlo 5.2 even without sound if I had too, but I'm glad I don't.
Now I can finally stay with this for awhile to see if it is stable as well as fast.
Thanks again.
Rick
For all ppl who are also annoyed by missing MP3-tags over bluetooth.
Please star following issue on code.google.com:
http://code.google.com/p/android/is...id&colspec=ID Type Status Owner Summary Stars
Thanks!
AOSP doesn't support AVRCP 1.13 which is the version that introduced metadata support. Until it does, custom ROMs the devs have added it to are the only one's that'll display song/album/artist.
Audio/Video Remote Control Profile (AVRCP)
This profile is designed to provide a standard interface to control TVs, Hi-fi equipment, etc. to allow a single remote control (or other device) to control all of the A/V equipment to which a user has access. It may be used in concert with A2DP or VDP.
It has the possibility for vendor-dependent extensions.
AVRCP has several versions with significantly increasing functionality:
1.0—Basic remote control commands (play/pause/stop, etc.)
1.3—all of 1.0 plus metadata and media-player state support The status of the music source (playing, stopped, etc.)
Metadata information on the track itself (artist, track name, etc.).
1.4—all of 1.0, 1.3, plus media browsing capabilities for multiple media players Browsing and manipulation of multiple players
Browsing of media metadata per media player, including a "Now Playing" list
Basic search capabilitieshttp://en.wikipedia.org/wiki/Bluetooth_profile
https://www.bluetooth.org/Building/HowTechnologyWorks/ProfilesAndProtocols/AVRCP.htm
As far as I know, no n4 custom rom supports it until today. Google will most likely never update it, don't know what the heck they are thinking.
it's such an elementary feature. Can't believe it's not integrated....This really makes me mad.
Lownita said:
As far as I know, no n4 custom rom supports it until today. Google will most likely never update it, don't know what the heck they are thinking.
Click to expand...
Click to collapse
What do you mean no custom ROM supports it?
I was waiting for someone to confirm if AVRCP 1.3 was going to be added in android 4.2.2 but now I'm planning on rooting and getting a ROM that does support this...
This is my most wanted bug fix for android 4.2.2, and I can't believe they missed it. Shame on Google.
jc monkeyballs said:
This is my most wanted bug fix for android 4.2.2, and I can't believe they missed it. Shame on Google.
Click to expand...
Click to collapse
I completely agree
Does anyone know of a stable mod that does have AVRCP 1.3?
I'm glad that I am not the only one^^
Please share this bug report as often as possible in other forums. Maybe if enough ppl will star this google will react - MAYBE^^
main reason
This was the main reason I was looking forward to the update...now, I'm sad. Guess I'm going to be forced to root now...anyone know when any of the ROMs will add this much needed feature?
alternetconcept said:
What do you mean no custom ROM supports it?
I was waiting for someone to confirm if AVRCP 1.3 was going to be added in android 4.2.2 but now I'm planning on rooting and getting a ROM that does support this...
Click to expand...
Click to collapse
There is no rom that supports it! If you find one, let me know
sarasotaguy said:
This was the main reason I was looking forward to the update...now, I'm sad. Guess I'm going to be forced to root now...anyone know when any of the ROMs will add this much needed feature?
Click to expand...
Click to collapse
That's all I was looking forward to also.
Its no wonder companies ignore their users when they needlessly and wrongly report bugs for something which is clearly not a bug.
If I was Google I'd ignore every single bug report which was actually reporting a missing feature.
For whatever reason, Google left it out, probably because its a niche requirement. It's not a bug.
thank god ur not google
maybe it's not the right category but at least I did something to point out that there's a problem and gave other ppl the chance to express their madness about this problem aswell.
And a niche? C'mon this is absolute standard nowadays and we can expect this from a 2012 smartphone when even my 2010 i9000 had it!
Lownita said:
There is no rom that supports it! If you find one, let me know
Click to expand...
Click to collapse
cm10 has it.
AnonymousPenguin said:
cm10 has it.
Click to expand...
Click to collapse
Is it possible for anyone to confirm this?
I was about to root when looking at CM but thought they didn't have it?
alternetconcept said:
Is it possible for anyone to confirm this?
I was about to root when looking at CM but thought they didn't have it?
Click to expand...
Click to collapse
I dont have NEXUS but CM10 M2 for Galaxy S III has it. 100% working. keep in mind, its 4.1.2 though !
It is funny how google is missing this very important feature.
bump. Which ROM has it?
Bump Anyone know if any of the custom ROMs for Nexus are putting this feature in? I've search...but didn't see a mention. Please link. Thanks!
sarasotaguy said:
Bump Anyone know if any of the custom ROMs for Nexus are putting this feature in? I've search...but didn't see a mention. Please link. Thanks!
Click to expand...
Click to collapse
Same here, don't understand it
i can confirm it works in cm 10. i use it on my car all the time. the cover art doesnt work but the tags work perfect.
Which ROM?
Sent from my Nexus 4 using Tapatalk 2
Hi!
Newbie here,
I've got a problem with cany crush saga on a CM10.1, latest kernel from Kowalski and the full nonneongaps from Tonyp (excellent rom by the way).
When i start the game, no problem. But when i hit the play button the screen starts flashing, the music starts and the touchscreen responds. The phone keeps on working as supposed to. I can shut the game with the home button.
It's not a big problem for me, but the kids are playing this very often on my phone.
Is there a fix for this?
I tried also the 10.1 Rom from avatar, same problem. Went back to ICS with NVFlash and candy crush saga is working fine.
Thanks in advance
if the same behaviour shows with different roms/kernels, then obviously the game have major problem with p990's hardware.
when the P990 is running on ics (stock or nv flash recovery there's no problem with the app. For me that rules out hardware.....
Same thing here, exact same kernel. The top line and bottom line of the screen flicker black on and off, the game responds but the graphics don't update.
Lent the phone to a friend so I'm not sure when I'll be able to try this, but I hope to update when I do.
sastraxi said:
Same thing here, exact same kernel. The top line and bottom line of the screen flicker black on and off, the game responds but the graphics don't update.
Lent the phone to a friend so I'm not sure when I'll be able to try this, but I hope to update when I do.
Click to expand...
Click to collapse
this happened to me but in my sony tablet. i was using it normally but suddenly when i start the game around 1 hour after not playing it its flickering. any help?
I am having the same problem :crying:
efmoraes said:
I am having the same problem :crying:
Click to expand...
Click to collapse
The problem is kernel related. Try a different kernel, and with reduced ram hack value if available.
I had been sent a private message by someone 3 weeks ago regarding this, asking how to fix it. I suggested him a different kernel, even tried it myself and it worked
So its either got to do with the high ram hack value or some other tweak in the kernel that causes the issue in this game.
rugglez said:
The problem is kernel related. Try a different kernel, and with reduced ram hack value if available.
I had been sent a private message by someone 3 weeks ago regarding this, asking how to fix it. I suggested him a different kernel, even tried it myself and it worked
So its either got to do with the high ram hack value or some other tweak in the kernel that causes the issue in this game.
Click to expand...
Click to collapse
yeah! im that bothersome person who ask many developer about that... hehe
just use AIOtool, and duat boot.. u can use avator rom or temasek(without flashing the kk), and a daily driver w/ kk...
don't worry i think spica1234 will help us, if he gets some free time! ^__^
thanks for all the developers here, temasek. pengus77, spica1234, tonyp, sreeprajay, bippi79..
hoping benee, jordanrulz, civato, stefan see this! & the members of Hackfest )
goood day, i have same problem with candy crush please help me how to fix candy crush
heres my ROM
cm-10-1-NIGHTLY-su660-fixed.zip
kowalski-kernel-100p5-oldbl_CM10.1.zip
please please help me how candy crush work
There has been written a lot about this app in the development section. Try to search in kernel or ROM threads (but don't reply with your issue as it doesn't belong in this sections and people got sick of it). As I remember, changing to latest Kowalski stable without ram hack (KK M1 norh) could help...
Sent from my LG-P990 using xda app-developers app
thank you for the reply
but im using su660 phone