[Phaded]

It was a old lib in the leak base, hence why everyone on the new leak has the issue.

Anyways, found the zip on team bamf, ignore my previous post.

 

[wraithdu]

Last part in adb didnt work for me says: mount: mounting /dev/block/mmcblk0p25 on /system failed: Device or resource busy

It's possible. I've had that issue after updating fonts sometimes too. It's not really necessary anyway since you're going to reboot regardless. I'll remove that step from the instructions.

 

[barcodelinux]

what i dont understand,is that file a phone file or a rom file? i was under the impression that after changing the file it would be bussiness as usual but it seems everytime i change roms {sense gingerbread)i have to apply the fix again. however aosp roms work perfectly. so i guess the phone is infected with the file not the rom or no? And why is it not happening to everybody? This issue crazy as it sounds showed up right after i formated the
system upon restore of gingeritisv1.3
Where did this happen?when when i installed the gingerbread leak? does that write a bad file to the phone somehow? If anyone can shed some light id really appreciate it
Thanks again

It has nothing to do with your Gingeritis install. I have the same ROM and had this issue. It was just coincidental.

Apparently that file had "expired" on August 31, 2011 and basically, everyone with that version of libOlaEngine.so, their camera stopped working on September 1st.

So....basically, what Phaded said.

 

[mike665]

Phaded, it worked for me without that step. I was in the same boat...

 

[mrreed2u]

It has nothing to do with your Gingeritis install. I have the same ROM and had this issue. It was just coincidental.

Apparently that file had "expired" on August 31, 2011 and basically, everyone with that version of libOlaEngine.so, their camera stopped working on September 1st.

So....basically, what Phaded said.

thanks buts its still not a complete answer
if that was the case everyone would have stoped at the same time
what im trying to understand is apparently the rom writes a file to phone and the fix does not work when switching roms

 

[auFan]

I have tried to follow the instructions twice using root explorer. Both times, the reboot resulted in being stuck at the HTC Boot white screen. Ideas?
Thunderbolt, Synergy Rom, rooted

 

[Droid DOES!!]

Anybody just tried flashing the camera patch? Worked for me and numerous others http://db.tt/MzMpofL

This thread has been Thunder struck!!

 

[snicklet]

Anybody just tried flashing the camera patch? Worked for me and numerous others http://db.tt/MzMpofL

This thread has been Thunder struck!!

Yeah, flash the fix it's easier.

 

[wraithdu]

I have tried to follow the instructions twice using root explorer. Both times, the reboot resulted in being stuck at the HTC Boot white screen. Ideas?
Thunderbolt, Synergy Rom, rooted

That's odd since the file comes FROM the Synergy ROM repo and is part of their build.

The camera flashable zip is a different fix. Does it work for the GTalk FC's as well? That one just seemed like a workaround to me, where as ziggy found the real source of the problem. Eh, I'm not a dev so I could be wrong on all counts.

 

[Droid DOES!!]

Does it work for the GTalk FC's as well?

Sure does

This thread has been Thunder struck!!

 

[Intoxikate]

Can someone please tell me how to run those ADB codes? I know I have ADB on my computer since that's how I rooted it, and I even got u to the cmd prompt and loading up ADB and having my TB show up. It's just from there I don't know what to do next or how to make use of those codes in the first post.

 

[Snow02]

Can someone please tell me how to run those ADB codes? I know I have ADB on my computer since that's how I rooted it, and I even got u to the cmd prompt and loading up ADB and having my TB show up. It's just from there I don't know what to do next or how to make use of those codes in the first post.

Then just flash the camera fix instead.

 

[Intoxikate]

Then just flash the camera fix instead.

I'm sorry, can you elaborate please? What file am I flashing? I didn't see anything about flashing a file. I didn't want to use the RootExplorer option since I have to pay for that app right? I just completely forgot how to use ADB.

 

[x02ssmarox]

thanks buts its still not a complete answer
if that was the case everyone would have stoped at the same time
what im trying to understand is apparently the rom writes a file to phone and the fix does not work when switching roms

You need a serious class in android. First, whatever ROM you flash, does not write files to the phone per say. The phone RUNS on the ROM. The ROM hold all the files the phone uses to function. Therefore, if a given file in a ROM is broken, then regardless of what you flash to fix, it will not retain because the next ROM you flash, will overwrite whatever you have on your phone now. If you flash ROM A, and it contains 123, flash a fix for 4, then wipe and flash ROM B which contains 123, than you will lose 4 unless you reflash the fix, or flash a ROM with the fix baked in.

 

[barcodelinux]

thanks buts its still not a complete answer
if that was the case everyone would have stoped at the same time

For everyone who had that particular version of that particular file in their ROM at 00:00:00 on 01 September 2011, their camera DID stop working at the same time.

what im trying to understand is apparently the rom writes a file to phone and the fix does not work when switching roms

It's NOT going to work when switching ROM's because you are writing over the fix that you just made by flashing the ROM. It's just like updating your anti-virus software, then wiping and reinstalling the entire system and then wondering why your anti-virus definitions aren't up to date. The bug is in the software, not the hardware.

I think that you might be confusing ROM and PHONE here. The PHONE is the hardware (microchips, circuit boards, screen, antennas, etc.) and ROM is the software (Operating System, kernel, theme, libs, etc.). The libOlaEngine.so file is overwritten everytime that you change the ROM because it is software.

Understand that this is a temporary fix just to hold you over until the dev's update that particular file in their ROM, repackage it, and release it to the world. But for right now, if you want Gingeritis on your phone WITH a working GTalk and camera, flash the ROM first then do the fix.

 

[barcodelinux]

Then just flash the camera fix instead.

You let that one go a lot easier than I would have.

 

[Droid DOES!!]

I'm sorry, can you elaborate please? What file am I flashing? I didn't see anything about flashing a file. I didn't want to use the RootExplorer option since I have to pay for that app right? I just completely forgot how to use ADB.

I linked it from my dropbox a few posts back just flash in CW like you would anything else but without wiping.

This thread has been Thunder struck!!

 

[Snow02]

You let that one go a lot easier than I would have.

What can I say. I like to keep things simple and results-oriented.

 

[SurfSwitch]

Hmm.. just stuck at the CM7 loading screen now. That didn't work. :sad:

 

[Navoj042175]

Hi I'm New here.

Just follow steps by root explorer and didn't work for me.

ROM Virus Synergy-Kingdom 8/25
Kernel ChopSuey 9.2.7

Sorry but I just realize it is the wrong device, but also mi EVO 4G has the sideways camera issue.