[DISCONTINUED] OMJ's HTC Sense Kitchen v2.1 | WM 6.x / WM 6.5.x | 21895 / 235xx

[O.a.T.]

Originally Posted by O.a.T.

Help!!! My problem is that I just found out that my camera (and my wife's - we're on the same custom rom) don't work. When I try to start using the icon, it briefly changes color, like its going to start, returns to the original color but nothing happens. If I execute camera.exe in windows manually, I get the message "The file 'Camera' cannot be opened. Either it is not signed with a trusted certificate, or one of it components cannot be found. If the problem persists, try reinstalling or restoring this file."

I have been using the same rom for some time which is a very lean 21877-based Titanium rom which I derived from the one in the kitchen. I know this used to work previously and I've searched quite a bit and tried several different things including some camera cabs, an skcerts cab, and activation some albums in the kitchen which I had deactivated. Again, I know this used to work in v1.6 of the kitchen. I only recently moved to v1.9 and as I don't use the camera very often, only discovered it in the last couple of days. The only other change, that I've largely discounted is that I am using LZX compression. I'm discounting because I was using that in v1.6 and I've seen no problems with anything else.

Any help, suggestions is greatly appreciated. If it helps, I can post my .erv file. LMK.

Couple new discoveries. Have also found that teeter and the calculator are also no longer working. These also definitely worked in v1.6. Next, saw in Amikam's thread that the above camera problem was also being observed, but fixed in his latest rom. This is what he said in regards to the cause and the solution... "in the oem folder... i added back some old mHub files back with their regedits... thats what did fixed it. hope it helps."

OMJ: Any chance that these same files either got removed or aren't getting loaded properly in a titanium only build in the kitchen v1.9? Could the titanium/sashimi error that was addressed with a change in the config_operator.txt file be causing this? Just grasping at straws here.