Database Develop

[MOD] FFC for the Vibrant development

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

Port the Extra Available RAM and Full 1080p HD playback from Galaxy Tab?

Reading around, I have found that the Galaxy Tab has the same amount of ram as the Galaxy S, however, when you read the available ram it says it has 444 mb (somewhere around there) compared to the 304 mb of the galaxy S (343 mb of you use the speedmod)
So my first question is if we can look at the Galaxy Tab, and just port over the code to allow more available ram to the Galaxy S?
My second question is that the Galaxy Tab supports Full 1080p HD playback. Since both the S and the Tab have the same GPU chip, I was wondering if we can also port that to the Galaxy S.
Now i know i know, 1080p playback on a phone is useless, but its not useless for ppl who have DLNA-capable TV's and for who-knows-when Samsung will get that microUSB to HDMI cable working.
UPDATE (11/7/10): Another thought came to mind last night. Reading through the Speedmod thread, there were certain amounts of ram before 720p recording and playback stopped working. Well, can we create some kind of script where we only had the allocated the ram of one of them? IDK how to really put this into words, but I don't think anyone will ever record 720p and watch a 720p video at the same time, so can we have it so that the ram is only open for one or the other, and it switches depending on whether you are recording 720p or watching it? Instead of having both of them take up ram, like have only one of them, at a time, taking up ram. Not sure of that really made sense :/

And port the large screen too.

Ya I agree I'd love a bigger screen.
10 billion dollars to have someone who can turn my screen into 5 inches.
Another 5 billion if they can do it without taking up extra space.
I'm sorry about that I just couldn't help myself

opcow said:
And port the large screen too.
Click to expand...
Click to collapse
michael.seltzer said:
Ya I agree I'd love a bigger screen.
10 billion dollars to have someone who can turn my screen into 5 inches.
Another 5 billion if they can do it without taking up extra space.
I'm sorry about that I just couldn't help myself
Click to expand...
Click to collapse
Whats even funnier is how your sarcasm doesn't even make sense because what I am suggesting is actually possible because the hardware is identical in both aspects, and since both devices run android, it should not be a hard port. Thats why I'm asking if an experienced developer or anyone with skill in programming to take a look in it.
If you aren't going to contribute an educated answer or a helpful one, please don't comment. I'm just someone asking a question, and sarcastic answers like this aren't necessary.

Ya sorry abou thatt. I see you question vut this has all already been discussed that the rest of the ram is used for system apps and stuff so you probably wouldnt want to change that.
Sent from my SAMSUNG-SGH-I897 using XDA App

michael.seltzer said:
Ya sorry abou thatt. I see you question vut this has all already been discussed that the rest of the ram is used for system apps and stuff so you probably wouldnt want to change that.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yeah... but you're saying the Galaxy Tab doesn't have system apps....I'm pretty sure it does...
I'm pretty sure even the firmware are very similar because of the identical hardware, other than the screen and camera.

crazililazn said:
Yeah... but you're saying the Galaxy Tab doesn't have system apps....I'm pretty sure it does...
I'm pretty sure even the firmware are very similar because of the identical hardware, other than the screen and camera.
Click to expand...
Click to collapse
He says system apps because of the video playback. If you go to the i9000 developtment section youll see a kernel thread called speed mod. (This is what setirons kernel is based off of) in there youll see the that certain amount of memory is needed to playback videos in 720p.
Thats what i think hes talking about system apps.
Now if you want 1080p playback AND more ram youll see why its not currently possible
Sent from my GT-I9000 using XDA App

tytdfn said:
He says system apps because of the video playback. If you go to the i9000 developtment section youll see a kernel thread called speed mod. (This is what setirons kernel is based off of) in there youll see the that certain amount of memory is needed to playback videos in 720p.
Thats what i think hes talking about system apps.
Now if you want 1080p playback AND more ram youll see why its not currently possible
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah but you aren't getting my point. The Galaxy Tab has the same amount of ram as the Galaxy S.... So how can the Galaxy S use less ram for playing 1080p...
That is what I want ported.

crazililazn said:
Yeah but you aren't getting my point. The Galaxy Tab has the same amount of ram as the Galaxy S.... So how can the Galaxy S use less ram for playing 1080p...
That is what I want ported.
Click to expand...
Click to collapse
Did someone took apart Galaxy S to confirm that it does indeed have everything identical ?
If not , for all we know it might have way more ram and or updated media hardware guts.

crazililazn said:
Yeah but you aren't getting my point. The Galaxy Tab has the same amount of ram as the Galaxy S.... So how can the Galaxy S use less ram for playing 1080p...
That is what I want ported.
Click to expand...
Click to collapse
I'm pretty sure somebody discovered the Galaxy Tab actually has 768 MB of RAM. It's just that Samsung didn't disclose that.

Disgustipated said:
I'm pretty sure somebody discovered the Galaxy Tab actually has 768 MB of RAM. It's just that Samsung didn't disclose that.
Click to expand...
Click to collapse
Nope, just searched through google and xda galaxy tab section and I can't find anything stating that.

crazililazn said:
Nope, just searched through google and xda galaxy tab section and I can't find anything stating that.
Click to expand...
Click to collapse
Not to mention from what I understand the hardware might br similar but is not close to identical. If the galaxy s phones were identical then roms would be interchangeable etc. But it isn't. I think ports of features would be nice, but I wouldn't get my hopes up if I were you. The ram issue has been worked on and from what I understand 340 I'd all they have been able to unlock.
I think the most important thing captivate devs could do right now is aosp because that will open a whole world of possibilities bit even that is amazingly difficult because of the way samsung built their system and all of the wonderful hooks and links.
Sent from my SAMSUNG-SGH-I897 using XDA App

provoked said:
Not to mention from what I understand the hardware might br similar but is not close to identical. If the galaxy s phones were identical then roms would be interchangeable etc. But it isn't. I think ports of features would be nice, but I wouldn't get my hopes up if I were you.
I think the most important thing captivate devs could do right now is aosp because that will open a whole world of possibilities bit even that is amazingly difficult because of the way samsung built their system and all of the wonderful hooks and links.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
The hardware is the same, other than the screen and camera. They both have a Hummingbird 1 ghz CPU and a SGX540 GPU chip, same amount of ram.
Btw, has anyone tried flashing a Galaxy tab rom on a Galaxy S? Since most of the hardware is the same, i would predict that the camera wouldnt work, and the screen MIGHT work, but the icons would be way larger than normal, but for everything else, it should work cuz the hardware is identical.

crazililazn said:
The hardware is the same, other than the screen and camera. They both have a Hummingbird 1 ghz CPU and a SGX540 GPU chip, same amount of ram.
Btw, has anyone tried flashing a Galaxy tab rom on a Galaxy S? Since most of the hardware is the same, i would predict that the camera wouldnt work, and the screen MIGHT work, but the icons would be way larger than normal, but for everything else, it should work cuz the hardware is identical.
Click to expand...
Click to collapse
Run a diff on the roms. I'm guessing there are a lot more differences than screen and camera.
Sent from my SAMSUNG-SGH-I897 using XDA App

provoked said:
Run a diff on the roms. I'm guessing there are a lot more differences than screen and camera.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Wait, can you type this again? I didn't get what you meant.

crazililazn said:
Wait, can you type this again? I didn't get what you meant.
Click to expand...
Click to collapse
I'm no developer but I know you can take 2 sets of rom files and run scripts that compare differences. I don't how to do it. But I know the devs were using this to try to get diffs between aosp and the leaked froyo to try to fill in gaps.
Sent from my SAMSUNG-SGH-I897 using XDA App

provoked said:
I'm no developer but I know you can take 2 sets of rom files and run scripts that compare differences. I don't how to do it. But I know the devs were using this to try to get diffs between aosp and the leaked froyo to try to fill in gaps.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Is there a dev thread on this? I would like to read through it. Might be a good read :]

Don't know if there is a direct thread. I wish there was. I would like to get more in-depth with the captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App

provoked said:
Don't know if there is a direct thread. I wish there was. I would like to get more in-depth with the captivate.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hmm, interesting. where did you read about this? in the galaxy tab section?

crazililazn said:
Hmm, interesting. where did you read about this? in the galaxy tab section?
Click to expand...
Click to collapse
Look for gdankos post "any brave volunteers" about aosp. Its definitely in there.
Sent from my SAMSUNG-SGH-I897 using XDA App

Should i buy this phone: g2 vs nexus s

Hello fellow xda members, im visiting from the p500 section, and I'm in the market for a new phone. So i have the choice Between this and the nexus s. Can you all. Demystify the issues I've heard? The hdmi out is really selling me, but people tell me about various issues. So can yall help me?
Thanks!
Sent from my P-509 using tapatalk

well to be honest this device has had a fair share of problems i luckily didnt face any of them from my experience it beats nexus s in all ways, processor camera hdmi speed display built quality, all aspects are better. There are a few thing though u should look before getting this device if u get a used one from the market
1- Put on a black wallpaper or image and see the corners for lcd bleeding
2- Load couple of system apps like camera and stuff see if it looses responsiveness or restarts, finally look closely at lcd if there are dead pixels if it passes those test ill buy the g2x no doubt about it

rukhi said:
well to be honest this device has had a fair share of problems i luckily didnt face any of them from my experience it beats nexus s in all ways, processor camera hdmi speed display built quality, all aspects are better. There are a few thing though u should look before getting this device if u get a used one from the market
1- Put on a black wallpaper or image and see the corners for lcd bleeding
2- Load couple of system apps like camera and stuff see if it looses responsiveness or restarts, finally look closely at lcd if there are dead pixels if it passes those test ill buy the g2x no doubt about it
Click to expand...
Click to collapse
Oh, ok. Well I'm getting it new on my provider (wind mobile) so i hopfully won't run into those problems
Sent from my P-509 using tapatalk

Oh, ok. Well I'm getting it new on my provider (wind mobile) so i hopfully won't run into those problems
Click to expand...
Click to collapse
welcome m8 to o2x users!!! hope that you will get a good one. even though you get a bad one, you can still exchange it right???

Yes, if i don't use 30 minutes. Is there a problem with quality control? How will i know i got a bad one?
Sent from my P-509 using tapatalk

Yes, if i don't use 30 minutes. Is there a problem with quality control? How will i know i got a bad one?
Click to expand...
Click to collapse
usually when you get a bad one, there is problem like BSOD(Suddenly your hp shutdown it self), SOD(Sleep Of Death = when it goes to standby, you cannot turn it on again)
or maybe example like another users the device so hot

joeyxl said:
Yes, if i don't use 30 minutes. Is there a problem with quality control? How will i know i got a bad one?
Sent from my P-509 using tapatalk
Click to expand...
Click to collapse
O you will know
Sent from my LG-P990 using XDA App

Get s2.. ram matters In android
..512 mb is low for high end...
Sent from my LG-P500 using XDA App

But with roms, kernels, etc...is this a better device than the nexus s?
Sent from my P-509 using tapatalk

I know this thread is old but...
Just have to say... If you didn't get it, I bet you wish you did Nexus S is first phone after gn to get ics! This phone is the ISH! It is now clear why google chose this phone over the g2- the gpu still beast enough to handle ICS, while none of the other phones (except gs) of the time(not event g2) can compete. I will never buy anything but Nexus.
Nexus FTW!

[LOG] Droid 3 Camera Log -- This is how close we are

Hi Guys,
I know I'm VERY quiet these days as I continue my personal vendetta against the Gingerbread/ICS hw codecs... but I thought I'd share with you a log sample from the Droid 3.
http://pastebin.com/raw.php?i=aLeLSu6y
That's the entire camera init:
- All of the camera properties are setup
- 6 preview buffers are allocated and registered
- followed by a few seconds of blank preview frames being loaded to/from the 6 buffers
- and then I "back" button out of the Camera UI near the end of the log
You can see the blank preview frames in the log by searching for "Buffer was never with Ducati!! 0x45d65000"
Those blank preview frames are what's holding up the show right now.
I know a lot of what you see me doing is working on RAZR and other projects, but in reality I spend at LEAST 2 hours every night troubleshooting and trying different techniques to get our ICS buffers to be recognized by our Gingerbread hw codec system.

if it isnt one thing its another eh?
is this the ICS camera software or the blur camera?

ssinisterss said:
if it isnt one thing its another eh?
is this the ICS camera software or the blur camera?
Click to expand...
Click to collapse
On twitter he said hes working on both. It's a matter of which works first.

ssinisterss said:
if it isnt one thing its another eh?
is this the ICS camera software or the blur camera?
Click to expand...
Click to collapse
This log uses the ICS camera. You can see some of the ICS stuff being setup in the beginning.
Sent from my XT912 using XDA App

Hashcode said:
This log uses the ICS camera. You can see some of the ICS stuff being setup in the beginning.
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
Hey Hash... Just to ask but did you get the email I sent you a couple days ago? I can send it again if you would like.

Hashcode said:
This log uses the ICS camera. You can see some of the ICS stuff being setup in the beginning.
Sent from my XT912 using XDA App
Click to expand...
Click to collapse
everythingwentbetterthanexpected.jpg
are these previews going to be tied into something that needs to be re written? or are they little independent executions?

ssinisterss said:
everythingwentbetterthanexpected.jpg
are these previews going to be tied into something that needs to be re written? or are they little independent executions?
Click to expand...
Click to collapse
The camera preview frames are processed asynchronously (very fast) by the ducati processor, which triggers a callback to display them to the screen (30 times a second).
So the fix for this would be the same fix that needs to happen for the hw video playback codec where buffers are allocated and handed off to the ducati to decode a Netflix movie, etc.

Hashcode said:
The camera preview frames are processed asynchronously (very fast) by the ducati processor, which triggers a callback to display them to the screen (30 times a second).
So the fix for this would be the same fix that needs to happen for the hw video playback codec where buffers are allocated and handed off to the ducati to decode a Netflix movie, etc.
Click to expand...
Click to collapse
ok, that was making sense, basically as you move forward with fixing the codecs it will get handled versus the memory tiler where you had to take steps back to clean up.
are the codecs also responsible for sound recordings and the hdmi output? i noticed i wasnt able to listen to mms'd soundclips.

Dude...you forgot a comma on line 1278457659308493702761257357 of the module source. Easy fix. LOL! Seriously...let me know if you run out of beer.

I noticed this
I/Thumbnail(1392): Fail to load bitmap. java.io.FileNotFoundException: /data/data/com.android.camera/files/last_thumb: open failed: ENOENT (No such file or directory)
I hope it helps
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Hashcode gave me some Ice Cream)

gVibeR said:
Dude...you forgot a comma on line 1278457659308493702761257357 of the module source. Easy fix. LOL! Seriously...let me know if you run out of beer.
Click to expand...
Click to collapse
its really missing a comma?

ssinisterss said:
its really missing a comma?
Click to expand...
Click to collapse
I think he was joking
Sent from my DROID3 using xda premium

yea i got it after looking at the log again

I'm sure you saw this, but it looks like there are too many derefs of the the frame buffer:
02-08 11:21:21.934: E/CameraHAL(221): hardware/ti/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:2945 OMXCameraAdapterFillBufferDone - pBufferHeader->nOutputPortIndex == 2
02-08 11:21:21.934: D/CameraHAL(221): hardware/ti/camera/BaseCameraAdapter.cpp:1226 __sendFrameToSubscribers - Empty Frame Queue
02-08 11:21:21.934: D/CameraHAL(221): hardware/ti/camera/OMXCameraAdapter/OMXCameraAdapter.cpp:3135 OMXCameraAdapterFillBufferDone - sendFrameToSubscribers error: -22
02-08 11:21:21.934: D/CameraHAL(221): hardware/ti/camera/BaseCameraAdapter.cpp:302 returnFrame - Frame returned when ref count is already zero!!
Click to expand...
Click to collapse
Stock D3, eagerly awaiting CM9 cam support. (Thanks for your work!)

Dude...you rock.
Sent from my XT862 using XDA App

I know that I'm not contributing anything here, but I would like to express my gratitude to you.
All of the work that you've put into porting ICS to the Droid 3 is greatly appreciated by so many of us here; and now that the Chrome for Android beta is now out, since it only works on ICS, I'm definitely not going to switch to any other rom on the D3!
Thanks so much for your hard work and for your hasty replies to anyone who asks you questions, and the best of luck to you in regards to the camera!

wgoeken said:
I know that I'm not contributing anything here, but I would like to express my gratitude to you.
All of the work that you've put into porting ICS to the Droid 3 is greatly appreciated by so many of us here; and now that the Chrome for Android beta is now out, since it only works on ICS, I'm definitely not going to switch to any other rom on the D3!
Thanks so much for your hard work and for your hasty replies to anyone who asks you questions, and the best of luck to you in regards to the camera!
Click to expand...
Click to collapse
Yep the Chrome for Android beta is yet another reason I keep banging my head against the hw codecs.

You can do it!

i was screwing around with the CM9 rom from the photon that has a working camera, and putting files into our CM9 last night and the camera UI fired up for me but there was nothing on the viewfinder. i dont even remember what i did since i did a clean flash after

ssinisterss said:
i was screwing around with the CM9 rom from the photon that has a working camera, and putting files into our CM9 last night and the camera UI fired up for me but there was nothing on the viewfinder. i dont even remember what i did since i did a clean flash after
Click to expand...
Click to collapse
lol, try it again maybe? =)

Only 720p video available on YouTube app?

Has any found a video that even plays in 1080p, let alone 2k on the YouTube app?
No matter what video I watch 720p seems to be the highest option available.

Same here. YouTube recently pushed an update earlier this week that removed the other resolutions. 1440p works on desktop via phone browser but is very choppy.
Sent from my SM-N910T

Why did they remove them? Do you know?

Interesting, I've just noticed that myself. Probably Google doing some tests again like they did before. As soon as the ROM's start pumping out we'll also get a modded YouTube app at the least.
busab said:
Why did they remove them? Do you know?
Click to expand...
Click to collapse

http://www.mediafire.com/download/b7098m98nlm49qb/youtube-5.10.1.5.apk
Use this .... it was from the previous , before they took 1440p ... working fine with me .... also after installing disable auto update from google playstore....

JUSMEJOSE said:
http://www.mediafire.com/download/b7098m98nlm49qb/youtube-5.10.1.5.apk
Use this .... it was from the previous , before they took 1440p ... working fine with me .... also after installing disable auto update from google playstore....
Click to expand...
Click to collapse
Thanks this worked. Although not at first. I had to unistall the current youtube update for it to install. Afterwards i still needed to clear cache and data and reboot my phone to get 1080p and 1440p to show up.
Sent from my SM-P600 using Tapatalk

aznmode said:
Thanks this worked. Although not at first. I had to unistall the current youtube update for it to install. Afterwards i still needed to clear cache and data and reboot my phone to get 1080p and 1440p to show up.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Anytime ... yeah and make sure you disable auto update from playstore ....

While I have been able to select 1080 & 1440 using your methods, it appears the resolution is now stuck on 720 regardless.
Take a closer look and see if your selections of high resolution actually are, because mine are not. Looks like YouTube/Google put the gabash on high resolution for now.

xero187 said:
While I have been able to select 1080 & 1440 using your methods, it appears the resolution is now stuck on 720 regardless.
Take a closer look and see if your selections of high resolution actually are, because mine are not. Looks like YouTube/Google put the gabash on high resolution for now.
Click to expand...
Click to collapse
Mines fine. Usually if I change resolution, I select it during a video playback but I have to exit out ouf what's playing and restart for the resolution to stick.
And it sticks no matter what, even if I restart my phone.
Sent from my SM-P600 using Tapatalk
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
JUSMEJOSE said:
Anytime ... yeah and make sure you disable auto update from playstore ....
Click to expand...
Click to collapse
Thanks. Already done.
Sent from my SM-P600 using Tapatalk

Mine plays 1440p with no problem .... Im able to change resolutions with no problem ....

It doesn't make sense, the Phone is totally capable of doing 1080p and 1440p but Youtube won't allow we viewing it. My iPhone 6 Plus does 1080P without problem, I think event Google is admitting iPhone is better, so I will agree with Google to sick with my iPhone, Google made the App for both, and their own App on their own operation system do less feature, unless they have hard time to deliver that video, otherwise it makes no sense. Google makes me think Apple is better now.

I'm not sure why google went this route for android either. All my devices defaulted to 720p. Although on the note 4 the 720p is actually sharper than the 720p on my note 3. I'm assuming it's due to the better screen on the note 4.
Sent from my SM-P600 using Tapatalk

I just tried the earlier mentioned method but I still don't get 1080p or 1440p. Weird thing is even after installing the youtube .10 version it still shows me .9.13 I don't know why I have disabled auto update and I clear cached and Data before and after and did two reboots no luck. I do have the latest update for my tmobile note 4 though. Any suggestions or help?

Virusbetax said:
I just tried the earlier mentioned method but I still don't get 1080p or 1440p. Weird thing is even after installing the youtube .10 version it still shows me .9.13 I don't know why I have disabled auto update and I clear cached and Data before and after and did two reboots no luck. I do have the latest update for my tmobile note 4 though. Any suggestions or help?
Click to expand...
Click to collapse
I was having the same issue ... this is what I did .... I personally use Root explorer Pro .... go into app or pri-app and delete youtube reboot your device and uninstall all updates from youtube .... reboot one more time ... Now install the App that I uploaded reboot ... go to youtube and see the differences .. weird is that I didn't had to delete cache, Just reboot the device .....

JUSMEJOSE said:
I was having the same issue ... this is what I did .... I personally use Root explorer Pro .... go into app or pri-app and delete youtube reboot your device and uninstall all updates from youtube .... reboot one more time ... Now install the App that I uploaded reboot ... go to youtube and see the differences .. weird is that I didn't had to delete cache, Just reboot the device .....
Click to expand...
Click to collapse
Do i need root to use root explorer? i don have root and i don't plan on rooting it yet seeing all the people are experiencing lag on there phones after rooting it.

root has absolutely nothing to do with any sort of "lag"; its what you install or delete/freeze after rooting that could be contributing to any "lag"

Virusbetax said:
Do i need root to use root explorer? i don have root and i don't plan on rooting it yet seeing all the people are experiencing lag on there phones after rooting it.
Click to expand...
Click to collapse
I Rooted my Note4 and I haven't had no lag or what so ever ....

JUSMEJOSE said:
I Rooted my Note4 and I haven't had no lag or what so ever ....
Click to expand...
Click to collapse
The thing is my device is new just came out. There could be warranty issues along the way. I really don't want to trip Knox flag. Anyways I bought this phone full price at a tmobile store attached to my line. Would I be able to call tmobile for warranty exchanges?
Do they care about Knox flag tripping?

Virusbetax said:
The thing is my device is new just came out. There could be warranty issues along the way. I really don't want to trip Knox flag. Anyways I bought this phone full price at a tmobile store attached to my line. Would I be able to call tmobile for warranty exchanges?
Do they care about Knox flag tripping?
Click to expand...
Click to collapse
You should worry .... I never had ... I have had so many phone rooting since the G1 and never had device issues .... Just pay attention to what your doing to your device and you will be ok ... Because you can kill a phone less than 5 seconds ... Its simple .... Its up to you if wanna take the chances on Rooting .... Also rooting the phone doesn't make the phone slow its the Apps that you delete ...

im gonna give it a week. if all goes well with the device and no warranty issues i will root the phone. i understand the concept of rooting but with other phones you can return to stock. with this phone it sticks which creates a little caution with me naturally.