Database Develop

install default camera instead of HTC one?

I love the speed of Cyan's Rom, but I hate the HTC camera. Video is always choppy. I don't think I had this problem with the default camera.
Is it possible to swap the cameras?

bittermormon said:
I love the speed of Cyan's Rom, but I hate the HTC camera. Video is always choppy. I don't think I had this problem with the default camera.
Is it possible to swap the cameras?
Click to expand...
Click to collapse
ADB commands to switch out the .apk's of the camera and camcorder with the "default" camera from another build (most likely JF's because that's all Google)

lukekirstein said:
ADB commands to switch out the .apk's of the camera and camcorder with the "default" camera from another build (most likely JF's because that's all Google)
Click to expand...
Click to collapse
ummm, thanks for the reply, but did you mean to list the ADB commands? have playd a little with this in the past but haven't had any luck, so any help would be appreciated. As for now I think I am going to reformat to ext2 and play with Haykuro's Ion r1 for a day or 2.

if you ALREADY HAVE the camera.apk you want to install...then good. IF NOT, go download JF1.51 and pretty sure it will have the Google version camera.apk...MAKE A NANDROID BACKUP BEFORE YOU BEGIN!! I AM NOT RESPONSIBLE FOR ACCIDENTS! This is a simple procedure, so please pay attention and do this carefully, Its not my fault if your phone gets bricked. That being said, i have done this more than once and never bricked my phone. THAT being said, I CANNOT GUARANTEE YOU THE SAME RESULTS, SO PLEASE! PLEASE! BACKUP YOUR DEVICE AND YOUR DATA BEFORE ATTEMPTING THIS!
First go into terminal on your device and type:
Code:
su
mount -o rw,remount -t yaffs2, /dev/block/mtdblock3 /system
rm /system/app/camera.apk
rm /system/app/HTCAlbum.apk
this removes the HTC versions from your phone. Then just go ahead and push the google version camera.apk. The adb commands are:
Code:
adb push /exact/path/to/your/camera.apk /system/app
remember, DO NOT type "/exact/path/to..." replace this line with the path on your computer where you have the camera.apk, for example,
/Desktop/Android/camera.apk is where mine would be...
then thats it. FYI, the HTC version has a separate gallery, the HTCAlbum.apk...THE GOOGLE VERSION DOES NOT HAVE A SEPARATE .APK FOR THE GALLERY. once you have pushed to google camera.apk you SHOULD have the camera and gallery and all...Good Luck!
-BMFC

bmfc187 said:
MAKE A NANDROID BACKUP BEFORE YOU BEGIN!!
Click to expand...
Click to collapse
Where's the fun in that??
bmfc187 said:
FYI, the HTC version has a separate gallery, the HTCAlbum.apk...THE GOOGLE VERSION DOES NOT HAVE A SEPARATE .APK FOR THE GALLERY.
Click to expand...
Click to collapse
I think that's what threw me off in the first place. Thanks for the help, I think I'll give it a shot after I get sick of Ion.

bittermormon said:
Where's the fun in that??
Click to expand...
Click to collapse
If you mess up sometimes you're screwed

bmfc187 said:
once you have pushed to google camera.apk you SHOULD have the camera and gallery and all...Good Luck!
-BMFC
Click to expand...
Click to collapse
Ok so here's the problem I have had in the past, and am still having. I backed up and remover the HTC CAmera and HTCAlbum, but even after I push Camera.apk from JF's ROM, it doesn't show up. No Camera and no Gallery.

Having the same problems. I'd also like to restore the stock camera application, but after replacing the apk and so files from the JF1.51 build (and rebooting), neither Camera nor Gallery appears in the app drawer.
Any thoughts?

rogers dream
hi!
does anyone know if this procedure will work fine on a Rogers Dream? Should replacing the apk files work okay?
Thanks!
silvrhat

silvrhat7 said:
hi!
does anyone know if this procedure will work fine on a Rogers Dream? Should replacing the apk files work okay?
Thanks!
silvrhat
Click to expand...
Click to collapse
Nandroid Backup, do it and if it fails just restore backup. There's no reason it shouldn't.

I'm running Cyan 4.0.2 and I'm trying to push the camera.apk from the rooted T-Mobile builds and when I push the files and try to install the apk it says it can't be installed on this phone. Do I need to push the .odex files also? Another thing, what are the commands for console to delete the data/data files for the htc stuff?

Anyone know why I can't push the stock camera to cyan 4.0.2?

How are you going about it? Are you using console or are you trying to use the package installer?

Copy the old camera file from an old rom. I found one with the JF1.5 build.
mount /dev/block/mtdblock5 /data
mount /dev/block/mmcblk0p1 /sdcard
rm -r /data/app_s/HTCCamera.apk
rm -r /data/app_s/HTCCamera.odex
mv /sdcard/Camera.apk /data/app_s
This will delete the HTC camera and put the old one back. The ODEX file should be created once the .apk file installs. Hope this helps!

it says HTCCamera.apk couldn't be found

What rom are you using?
EDIT: Try this -- Using Cyan4.0.1 (I assumed that you were using JacxHeroski1.5r2..my bad!)
[cpde]mount /dev/block/mtdblock3 /system
mount /dev/block/mmcblk0p1 /sdcard
rm -r /system/app/Camera.apk
rm -r /system/app/Camera.odex
mv /sdcard/Camera.apk /system/app[/code]

I'm using 4.0.2 (pretty much the same as 4.0.1) but shouldn't I have to remove the gallery.apk also? What about the folders in /data/data? Should I remove those too?

I'm looking at the file structure and can't find there is a /data/data. As far as the gallery you shouldn't need to (didn't realize that it was updated.) But if you'd like to push that it would be:
Code:
mount /dev/block/mtdblock5 /data
mount /dev/block/mmcblk0p1 /sdcard
rm -r /system/app/HTCCamera.apk
rm -r /system/app/HTCCamera.odex (may or not be there)
mv /sdcard/Camera.apk /system/app
I've been looking and cannot find anything regarding a Gallery/Album.apk. But it should be able to use the Gallery that's already installed. Let me know how it goes.

ThR1LL said:
I'm running Cyan 4.0.2 and I'm trying to push the camera.apk from the rooted T-Mobile builds and when I push the files and try to install the apk it says it can't be installed on this phone. Do I need to push the .odex files also? Another thing, what are the commands for console to delete the data/data files for the htc stuff?
Click to expand...
Click to collapse
They're folders i believe.
Try "rmdir foldername"

bmfc187 said:
if you ALREADY HAVE the camera.apk you want to install...then good. IF NOT, go download JF1.51 and pretty sure it will have the Google version camera.apk...MAKE A NANDROID BACKUP BEFORE YOU BEGIN!! I AM NOT RESPONSIBLE FOR ACCIDENTS! This is a simple procedure, so please pay attention and do this carefully, Its not my fault if your phone gets bricked. That being said, i have done this more than once and never bricked my phone. THAT being said, I CANNOT GUARANTEE YOU THE SAME RESULTS, SO PLEASE! PLEASE! BACKUP YOUR DEVICE AND YOUR DATA BEFORE ATTEMPTING THIS!
First go into terminal on your device and type:
Code:
su
mount -o rw,remount -t yaffs2, /dev/block/mtdblock3 /system
rm -r /system/app/camera.apk
rm -r /system/app/HTCAlbum.apk
this removes the HTC versions from your phone. Then just go ahead and push the google version camera.apk. The adb commands are:
Code:
adb push /exact/path/to/your/camera.apk /system/app
remember, DO NOT type "/exact/path/to..." replace this line with the path on your computer where you have the camera.apk, for example,
/Desktop/Android/camera.apk is where mine would be...
then thats it. FYI, the HTC version has a separate gallery, the HTCAlbum.apk...THE GOOGLE VERSION DOES NOT HAVE A SEPARATE .APK FOR THE GALLERY. once you have pushed to google camera.apk you SHOULD have the camera and gallery and all...Good Luck!
-BMFC
Click to expand...
Click to collapse
This is what I tried to do at first but it kinda failed
nolimit78 said:
I'm looking at the file structure and can't find there is a /data/data. As far as the gallery you shouldn't need to (didn't realize that it was updated.)
I've been looking and cannot find anything regarding a Gallery/Album.apk. But it should be able to use the Gallery that's already installed. Let me know how it goes.
Click to expand...
Click to collapse
i think i figured out the data command its like
Code:
rm -r /data/data/com.android.camera
rm -r /data/data/com.htc.album
or something like that

WTB HQ youtube option in JACH 2.6

I have JACHero 2.63, and I was wondering if it is possible and how I would go about using an older youtube app instead of the pre-loaded one. The ONLY complaint I have about this rom so far is the fact that youtube doesn't have the HQ video option that it had on stock cupcake and cyanogen's. I have a working youtube.apk that should support the HQ feature. It wouldn't let me install the app from the SD card like normal, and I think that's because it is protected or something. What is the best way to get the youtube feature I want? Other than that this new rom is heavenly

want to buy? lol.
move the youtube.apk to root directory of your sdcard (not in any folders)
su
cd sdcard
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cp youtube.apk /system/app

Ok I tried this and it did copy successfully, however it didn't change the default youtube app, I tried to install it again like before, I couldn't. I also couldn't delete/rename the youtube I want to replace. Would I need to do something else to make it work from here. I now have 2 youtube.apk's in my system/app folder. >.<

darkphoenix2012 said:
Ok I tried this and it did copy successfully, however it didn't change the default youtube app, I tried to install it again like before, I couldn't. I also couldn't delete/rename the youtube I want to replace. Would I need to do something else to make it work from here. I now have 2 youtube.apk's in my system/app folder. >.<
Click to expand...
Click to collapse
So if you go into /system/app with terminal and type
Code:
ls -al
you see two different youtube.apk files? Honestly, they really can't be identical.. There has to be some difference between the two file names for them to both exist in the same folder. Look at them carefully, then try renaming (use the mv command) the new one to overwrite the old one.

Ok now i think i screwed myself over. I used mv like you said and my youtube force closes >.< I'm going to need another youtube.apk that works for hero, hopefully one that has a working high quality feature.

You can unzip the hero update.zip that you're running right now to get the original youtube.apk -- Won't get you HQ, but fix your FC issues for now.

Ok I restarted the phone twice and youtube changed the appearance of the icon it had to the one it should have. Meaning it did copy correctly and overwrote the apk as it was intended. However I still do not have a HQ setting in youtube for hero. Am I the only one who has this issue in youtube??

What type of connection are you on? On EDGE I have no HQ option in YouTube. On WiFi it automatically goes to HQ. I assume 3G would let you select HQ.

I'm on 3G. It doesn't give me the option no matter what type of connection as long as I'm running Hero. On a android rom it was different

Another thing I can't figure out, how to reset what app opens with the sms widget on the desktop

htc camera

is it possible for me to replace my camera wit the htc camera app that is on the hero rom, and if so where can i get it??

not sure if possible, but it's easy to find out.
all you have to do is download the hero rom and extract the files. go into the system folder and look inside of the app folders and look for HTCCamera.apk OR Camera.apk.
take it and push it to your phone and reboot, it should work or not work you can test. it wont harm your phone. make sure you backup your current camera app first so you can revert if the hero camera dont work. Make a note of what file name your current camera is, and rename the hero camera to be the same thing. then push it.

NguyenHuu said:
not sure if possible, but it's easy to find out.
all you have to do is download the hero rom and extract the files. go into the system folder and look inside of the app folders and look for HTCCamera.apk OR Camera.apk.
take it and push it to your phone and reboot, it should work or not work you can test. it wont harm your phone. make sure you backup your current camera app first so you can revert if the hero camera dont work. Make a note of what file name your current camera is, and rename the hero camera to be the same thing. then push it.
Click to expand...
Click to collapse
you dont think i can jus install it as a normal app?? and if not, how do i "push it to my phone"??

gamefan231 said:
you dont think i can jus install it as a normal app?? and if not, how do i "push it to my phone"??
Click to expand...
Click to collapse
this is the exact steps you need to take.. first you need adb installed
adb remount
adb pull /system/app/Camera.apk
adb install directoryoffile/HTCCamera.apk
adb install directoryoffile/HTCAlbum.apk
adb shell remount
if it doesnt work or you get a FAILURE when pushing either one of these .apk files just push back your old Camera.apk

palosjr said:
this is the exact steps you need to take.. first you need adb installed
adb remount
adb pull /system/app/Camera.apk
adb install directoryoffile/HTCCamera.apk
adb install directoryoffile/HTCAlbum.apk
adb shell remount
if it doesnt work or you get a FAILURE when pushing either one of these .apk files just push back your old Camera.apk
Click to expand...
Click to collapse
where can i find "adb" and how do i install it?

gamefan231 said:
where can i find "adb" and how do i install it?
Click to expand...
Click to collapse
ay yi yi... look here... it will tell you exactly how to get ADB up and running... once you do, you will wonder how you ever lived without it...
ADB, Fastboot, Nandroid for n00bs
also, this write up is for the 1.5r2 SDK, the setup for 1.5r3, which is the newest one is exactly the same

IF YOU HAVE THE SDK INSTALLED, THEN YOU ALRREADY HAVE ADB. needed that in caps so you dont go installing stuff u might not need.
if you are on windows, hit start > run. then type CMD, then the dos box will pop up. here you can enter in the commands that palosjr gave earlier.

i was following the directions on the thread posted but when i tried to put the sdk folder in my c/ drive it told me i didnt have enuff space...would it be possible for someone to put the htccamera app into a theme for me?

I tried it but it resulted in following error:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
For either one (HTCCamera and HTCAlbum)

ya nm good luck im going to see how it turns out i would love to have HTC camera and Album seems nice.

abraxas_son said:
I tried it but it resulted in following error:
Failure [INSTALL_PARSE_FAILED_UNEXPECTED_EXCEPTION]
For either one (HTCCamera and HTCAlbum)
Click to expand...
Click to collapse
probably needing some other framework from hero to make this work... i will do some searching for you and see if i cant get it to work. if you guys want the HTC camera, why dont yall just flash jacheroski1.8 or 2.0? both are solid, and in case you didnt hear, all the SMS issues are fixed.

I have ran those roms and ya they are solid but i like to stick with cyanogen roms. Im only really after the ablum app with multi touch. Now that BFS has hit the scene I'm tempted to give a hero rom a look see but i want to see what cyanogen will do next lol.
I looked around in two hero roms and found in the lib folder two *.so files for the camera and one for album. Those are the only files that are named after the apps. On a side note, do the camera and ablum app rely on one another? The reason i ask is the thread was started about the camera app and then it is recommended to push both by adb. Getting album to work is what caught my eye to begin with all though htc camera app would be nice.

Any progress on this front? I tried a couple Hero roms and really liked the camera and gallery. I can't stay on Hero because it doesn't work right with Google Voice dial-thru. Is there a way to get them ported into Cyanogen 4.1.11.1?

Install_failed_already_exists
Interesting... trying to adb install HTCCamera.apk (taken from the Sprint Hero dump) into Cyanogen 4.1.11.1 fails with the message [INSTALL_FAILED_ALREADY_EXISTS]
Doing the same for HTCAlbum.apk gives the message [INSTALL_FAILED_MISSING_SHARED_LIBRARY]

[Q] Camera Force Close after OTA

Hello Everyone,
So I unfroze all of my apps in Titanium Backup and flashed the OTA that is posted in the development forum for the Droid 3 and it seems to have worked great other than one small problem. Every time I try to use the camera or camcorder they will open for about 2-3 seconds and then they close and I end up back at my home screen. Does anyone have any ideas on what I can try to make my camera apps work again?
EDIT: Sorry, forgot to mention that I did try rebooting the phone as well as clearing the cache for the camera app, no change. Also Camera Zoom FX stays open but just has black where the camera image would normally be.
Thanks!

Maybe you... forgot to unfreeze the camera app lol.
No but id check what you do have frozen, maybe there's a service the camera app is dependent upon you might have accidentally frozen (assuming you rerooted after update)
Sent from my DROID3 using Tapatalk

I did re-root after applying the OTA update and then I froze about 15 apps that I found to be annoying/un-needed, however even after unfreezing all of them, any app involving the camera still isn't working. I also just noticed that my flashlight app that worked before the OTA is not working either.

First thing I would try is "clear data" for the Camera app and reboot.

rtbrjason said:
First thing I would try is "clear data" for the Camera app and reboot.
Click to expand...
Click to collapse
Tried that a couple of times but no change. I just also noticed that the camera app flashes a small message up at the bottom of the screen really quickly stating that the camera is unable to initialize.

Uninstall any third-party app that uses the camera (if you have any) the try again.

kishin14 said:
Uninstall any third-party app that uses the camera (if you have any) the try again.
Click to expand...
Click to collapse
Thank you for the suggestion, I hadn't thought of that. Unfortunately that did not work either. No change, still getting the same message for about a second or two and then it closes.

Try re-uploading the camera apk and odex files, might need to set permissions the same as the other system apps.
Unzip and use something like rootexplorer, delete current BlurCamera.apk and BlurCamera.odex, set write access on system/app folder then copy these.
-smc

The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log

limaxray said:
The problem is the camera firmware, amongst other things, is first deleted and then replaced during the OTA update - if something happens, that firmware is never copied back causing the camera to fail.
The problem I had was too much stuff installed in /system and it simply ran out of space. This also caused my recovery to fail to update which then failed checksum if I tried to boot to recovery.
I had a bunch of binaries I installed in /system/xbin taking up several MB of space. I deleted them - including busybox - and reran the update. Now everything works fine.
If your recovery is hosed, I posted how to fix in the update thread.
If you need help and haven't wiped /cache yet, post /cache/recovery/last_log
Click to expand...
Click to collapse
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.

640k said:
also, one note, i'm seeing alot of people reporting issues with the stock apps AFTER they've removed bloat (any method). the first thing people should do is put the bloat back, or in worse case scenario, do a wipe to see if there's really something wrong.
i froze an email service and it cause my text messenger to stop working. you don't know what libraries are shared with what. freeze with caution.
Click to expand...
Click to collapse
I agree, and would suggest to anyone to use the script for removing and replacing the bloat - it makes it much easier to do (especially from adb when you foul it up) and keeps track of what you've done.
That said, I highly doubt that is the issue here. The update script first checksums everything that needs to be patched and deletes everything that is to be replaced. So if you have anything removed, it will either cause it to fail (if the file is to be patched) or not matter (if it is to be deleted or simply isn't touched). In other words, if you have anything missing that is needed, the update wouldn't touch anything.
Furthermore, I don't think any of the commonly removed bloatware serves as a dependency for the camera. At least not as far as I can tell.
I can tell you that /system is filled to the brim with all of the bloatware. The current ROM is just barely shoehorned in there. Many 'for-root-users' apps like to install stuff to /system and since the updater script doesn't check for free space, it may very well fail to extract in the middle of execution even though it already deleted a bunch of files.
So I think more importantly than restoring bloat, you should remove anything you added.

I tried your directions and re-ran the update after fixing recovery, however my camera still doesn't work because of the same basic issue, running out of space before the update completed. Upon re-rooting and going in to my system directory with root explorer I noticed that I now only have 195k free there. I checked the xbin folder and do not see busybox or anything else there that I recognize that I could delete to free up space. How can I tell what is safe to delete and what isn't so I can free up enough to fix my recovery again and hopefully get the update to work properly?

You can see a breakdown of disk usage with this command:
Code:
du -sh /system/*
Here's mine with busybox removed:
Code:
147.6M /system/app
7.5M /system/bin
11.0K /system/build.prop
5.5M /system/etc
5.1M /system/fonts
35.5M /system/framework
75.7M /system/lib
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
135.0K /system/xbin
And my free space is
Code:
$ df /system
Filesystem Size Used Free Blksize
/system 320M 317M 2M 1024
Other than su, the only files you need in xbin are (don't worry about the symlinks)
Code:
backup dexdump drm1_func_test run_backup run_restore ssmgrd
I think the only extra bits I now have on /system is su.
I also found the system dump from this post to be very helpful.

Whenever I'm trying du It's saying that the command wasn't found. What are you using for your terminal access?

Hmm it seems du isn't a standard binary even though I have it in bin. I sure don't remember putting that in there...
Anyway, I use adb or Better Terminal Emulator Pro, depending what mood on in.
To use adb, you'll need to install busybox to /data somewhere (I have mine in /data/local/bin) and use
Code:
$ /data/local/bin/busybox du -sh /system/*
BTEP has a fairly complete set of CLI tools included - such as du - so you don't need busybox.

I figured out how to do the command through busybox and have come up with some interesting results...
I am over yours on...
Code:
153.8M /system/app
1.9M /system/xbin
I am under yours on...
Code:
4.7M /system/bin
4.9M /system/etc
71.8M /system/lib
And I match yours on...
Code:
11.0K /system/build.prop
5.1M /system/fonts
35.5M /system/framework
1.0K /system/lost+found
19.2M /system/media
0 /system/preinstall
304.0K /system/recovery-from-boot.p
4.6M /system/tts
8.3M /system/usr
This is with busybox installed in the xbin folder so that is probably why I am over on that one, however the app folder is quite a bit over as well but I can't figure out why. The only file that I can find in there that doesn't seem to belong is Superuser.apk but it is only 191k.
UPDATE: I finally found a large app that wasn't present in the system dump that you had mentioned before. I backed it up to my sd card and removed it, went through the update, and now my camera is working. Thank you very much to everyone who helped, especially limaxray!

Glad I was able to help!

This is a great example for why we should always wipe data/cache before any rom update.

dsw361 said:
This is a great example for why we should always wipe data/cache before any rom update.
Click to expand...
Click to collapse
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.

limaxray said:
That wouldn't have helped here at all. If anything, it would have made it impossible to use adb in case of a boot loop.
These are not like community ROM updates and don't need anything wiped.
Click to expand...
Click to collapse
Exactly. the last thing I would do is wipe data/cache if we encountered a bootloop. Adb is so important to us right now because we don't have a custom recovery or an sbf.
Sent from my DROID3 using Tapatalk

Fix camera permissions in the market

So the Nexus 7 does not have a primary camera, so a ton of apps in the market that use a camera show up as Not Compatible. You can sideload them and they may or may not work. However, there's a fix.
I'm on rooted stock, but if your custom ROM is also having this issue in the market you can tell your ROM Chef what file to add.
Caveat: This IS working for me as of right now, but it did not immediately, so there might be some delay or something else needed to do to make it work immediately. I'll update this post based on feedback if it's working immediately for folks or there's some other way to speed things up.
Caveat: Just because you can install an app won't make it work. If an app crashes, you've been warned. All apps might not work, but at least some apps that can use camera and don't need the camera function can be installed (Grocery King works fine, barcode scanning crashes), some will work fine (Camera Zoom FX).
And just to be clear, you are modifying /system. If you do this wrong, you could cause yourself problems. You have been warned.
Pre-reqs
Rooted
Root file explorer app to copy a file into /system (I use Ghost Commander, use your favorite app)
--OR THE FOLLOWING--
ADB working
Busybox (does not need to be installed, but needs to be available for cp, or you can use cat if you know how to do that method instead)
Busybox might be needed to remount /system as read-write, or you can use some other method to do this
Pick the method you want to use, adb, or a file explorer that can mount /system and write files there. Pick one method or the other, I've hidden the content on both by default so fewer people think you need to do everything..
android.hardware.camera.autofocus.xml is a file inside of the zip attached to this post, all references to copying that file imply you open the zip file and extract or copy it directly over. NOT the zip file itself. And no, this is not "cwm flashable". If this is working for folks and someone wants to make a CWM Flashable ZIP file to use, I'll be happy to add it to the post and update instructions.
Instructions for using your favorite root explorer kind of app
Download the file attached to this post to your device
Launch your favorite root explorer type app and remount /system as read/write
Copy android.hardware.camera.autofocus.xml to /system/etc/permissions/
Remount /system as read-only
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Instructions for using ADB/Manually copying it
Download the file attached to this post
Connect to your device over adb (I use wifi adb personally)
Do the following commands to launch adb and inside of adb respectively
adb push android.hardware.camera.autofocus.xml /sdcard
adb shell
su
mount -o rw,remount /system
cp android.hardware.camera.autofocus.xml /system/etc/permissions/
mount -o ro,remount /system
Click to expand...
Click to collapse
Now we have to clear market data, do that in Settings->Apps, All tab, find Google Play Store and Clear Data
Reboot
Check the market for Camera related apps. Profit! If still not compatible, just give it a few days.
Thanks to bonks in #nexus7 for confirming for me that he cannot access a few Camera apps and validating some permissions files for me to verify my changes had worked on my end.
Works for 4.3 as well, but the same caveat... It took three days to show apps as compatible, so not sure what needs to "clear" for the permissions to be updated, but give it a few days and it'll be fine.

Reserving for any followup info, particularly around if the market permission doesn't clear "immediately".

A partial list of apps that work/don't work, but all will install now and previously would not. If anyone tries another app or has more input I'll update this post.
I've also started a list of apps I know of that have altered their permissions in the market so that they should show up natively on the N7 without the fix.
Work Perfectly (maybe mirrored)
Paper Camera - Mirrored
Google Translate - Mirrored, maybe upside down.. Wonky, but does work.
Work With Caveats
Grocery King - Barcode scanning crashes, otherwise completely usable
Don't Work at All
Google Goggles - Blank image, although you can load images you took with other cameras
Retro Camera - Can't find camera
Fixed market permissions
Camera FX Zoom - Use landscape, or things are mirrored and flippped

This worked great for me...thanks a bunch!
Sent from my Nexus 7 using xda premium

Ima give this a go when I get home, thanks

Nexus 7 camera permissions
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David

DavidTheBourne said:
Hi,
I have an app on the market that uses the front camera and sadly I cant get it working on the Nexus 7. Could someone please assist me in what permissions I need to change exactly to get it running?
From reading the posts above I now see that it's not the name of the camera (which I believe is 0) but it's permissions around that.
As a noob to the Nexus 7 permissions can anyone step me through it?
Thanks
David
Click to expand...
Click to collapse
http://stackoverflow.com/questions/...ort-for-android-application-manifest-assembly

Just wanted to bump this thread and let everyone know this still works for 4.3. However, I'm not sure what one would need to do to make it work faster.
I installed the XML file on my N7 about three days ago, cleared Market data, rebooted etc, specific apps still showed as not compatible.
Finally today I look, and compatible! Perhaps it's on Google's side, it only updates every so often.. I dunno.
Anyway, so it works, but it might take a few days for it to propagate