Database Develop

anyway to change the folder the camera saves pictures to?

right now im using Cyanogen v3.6.2 rom and the camera saves the pictures to "100MEDIA" instead of "Camera Pictures" and "VIDEO" instead of "Camera Videos"
any way to change it?

yeah those camera/camcorder apps are the HTC versions, IMO theyre better but if you want the old back you want the google versions, i bet you can get them outta JF 1.5 (not sure) or the dudes1.2b or earlier might have it, i dunno where else you could get it, lemme see if ive got a spare copy layin around...ill check back with ya if ive got 'em...meantime check JF1.5, i think Dudes current release (1.3RC2) has the HTC ones as well, but if you can find a link in his thread for earlier builds, anything earlier than 1.2b should have it...
-BMFC

oh okay I have JF 1.5 saved somewhere
so I have to push the camera / camcorder apk to my phone from JF 1.5 then?

fyi
Just realize that switching camera's your gonna lose zoom function and I think some functionality with wallpapers. Imho it worth getting used to the folders than sacrificing functionality.
You'll have to remove the camera.apk and htcalbum.apk, and replace and remove some library files. But it sounds like you just wanna change the save location. Which there is no option for. Maybe ill crack it open and see if it can be changed.

if you think you have the right ones, yeah...MAKE A NANDROID BACKUP BEFORE YOU START, JUST IN CASE. ...just go into a terminal on your device and do
Code:
su
mount -o rw,remount -t yaffs2, /dev/block/mtdblock3 /system
to remount /system as read/write, then:
Code:
rm /system/app/camera.apk
rm /system/app/HTCAlbum.apk
exit
this removes the camera AND camcorder (same .apk) and the HTC gallery. The google gallery comes with the camera.apk i think, you shouldnt hafta find a gallery app to replace it once you put the google camera.apk back.
push it with adb and reboot just in case...MAKE SURE YOU BACKUP EVERYTHING BEFORE YOU START. MAKE A NANDROID BACKUP. if you're not sure if youve got the right camera.apk, open up the archive for your JF1.5 update and go to /system/app directory and look for a HTCAlbum.apk...if it is not there then you probably have the correct one...THIS MAY NOT BE THE CASE IF YOU HAVE ALTERED OR MANIPULATED THE UPDATE...I CANNOT BE SURE OF THIS SO BE SURE WHAT YOU ARE PUSHING TO YOUR PHONE BEFORE YOU DO. NOT RESPONSIBLE FOR ACCIDENTS...IF YOU'RE STILL NOT SURE:
copy the camera.apk to your desktop and rename it, olny adding ".zip" to the end...DO NOT DELETE THE NAME...just add .zip to the end. then open it up and go to the /res/drawable folder and check to see if the icon is different from the one you have now. if its the same dont bother pushing it...hope this helps...be careful.
-BMFC

alright thanks soulife and bmfc187
i'll try it out and see how it goes, if it gives me problems i'll just get used to the folder names

well like i said (and soulife too) the HTC ones are better and def. worth getting used to the folder...but if you really want the old one back then have it at it and let us know how it goes...ive done this before, it shouldnt brick your phone...but backup ur stuff anyways...
-BMFC

Remove the album and the 3 camera library files and replace it with the camera librarys from the jf build too(I think its only 2 files, in lib folder, every *.so file with the word camera in it). The google album is built into the camera app.

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

[FIX] For 2.2 Market issues, use this mod - *Updated* with Stock Build.prop

For those of you having trouble seeing protected apps, I modified our fingerprint in the build.prop. What this does is spoofs the market into thinking its seeing a Droid 2 (with Froyo) It worked for me, let me know if it does for you.
1. Put build.prop into your AndroidSDK\TOOLS folder
2. Connect via USB.
3. CD (Navigate) in CMD to your tools folder
Mount your /system (adb remount) works for me
Copy and paste this
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
To test if you need this before you push the build.prop fix, search the market for Us Bank. If only 2 or 3 show up, you are not getting the full market. After this fix, you should see 10 items listed when you search for Us Bank.
Hope this helps.
2.2 Market Fix Build.Prop -- WITH STAGEFRIGHT=TRUE
This can also be done via Root Explorer.
Edit: Here is a "clean" build.prop for those of you who do not want the stagefright fix (which breaks video playback) Sorry, I was not aware it did that. Thank you.
Non Stagefright Build.prop -- WITH STAGEFRIGHT=FALSE
For everyone flipping out about Birdmans tweet and you want the stock build.prop, here ya go
Stock Build.prop -- WITH NOTHING! STOCK!
You only need the stock one if you ever plan on doing a factory reset. But, you also cant do a factory reset if you have removed or renamed apps so I feel that should be mentioned. If you've done any modding and you are planning on upgrading, your best bet is to always use the SBF anyway. I dont think birdman realizes the panic he sets in with one little tweet. Factory resets suck anyway. But then again... "you decide..."
Thanks to Jcase for giving me the original idea way back when. I just basically applied his Eris Market Fix to work with our phones.

This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions

Found a fix
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.

Zaphod-Beeblebrox said:
This created several problems for me.
First, the build.prop file is a read-only system file and doing a push did not work for me.
I had to copy it to my sdcard and then in shell:
su
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/build.prop /system/build.prop
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
This created some really fubar'd effects on my network as I couldn't access the market from 3g. It more or less disabled my 3g network.
When I activated wi-fi, it worked fine, and did let me into the market.
I'm trying to put my original build.prop file back on, but I still have no 3g connectivity.
Update:
restored my build.prop and still no go.
update2:
tried clearing the 'cache' from reboot mode and even did a factory reset ... still no go.
I'm starting over with SBF, update, FROYO, etc.
I don't know for certain that this file hosed me, but I had not yet done any other system file issues. Either way, I would not recommend you follow my above instructions
Click to expand...
Click to collapse
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html

elkniwcire said:
i must say i take no responsibility if this causes problems but this worked for me. Do a search in the market for "eris market fix." it was designed for the eris but works just fine on my droid x. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but i assume most everyone on froyo already is rooted.
Click to expand...
Click to collapse
yes this worked for me aswell thank you

Yes this method definitely works. I have market working now and can search for protected apps etc.

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.

he was just explaining where the idea comes from i think... You'd have to be crazy to use the eris market fix app on a droidx, just simply edit the build.prop fingerprint line.

I just used the root explorer meathod and now it wont boot.
I downloaded the file.
renamed my build.prob to build.prob/bak
placed the new build.prob in the system folder
rebooted and now after the M screen it just goes to a black screen with the backlight lit. Wont boot up. Im learning adb so this may be a noob question but can I access adb if the phone wont boot all the way up. That way I could change the build.prob back
Edit Delete Post: Im just retarted haha .prop not .prob :/

Could you plz give us some details on doing this with root explorer. Thanks
Prolly simple but I did try moving current build file then renaming and pasting yours without success doing us bank search. Also rebooted cleared cache and market history prior to search. Appreciate any help with doing this via root explorer.

LexusBrian400 said:
Firstly, I figured ppl would know how to use adb.
if you cant push the file, use "adb remount" and it will work.
Secondly,
Hmm... Sorry to hear that but I HIGHLY doubt it was the build.prop that did this.
I posted over at another thread, and it worked for everyone.
Check it.
http://www.droidxforums.com/forum/droid-x-hacks/4318-2-2-market-issues-use-mod.html
Click to expand...
Click to collapse
LexusBrian400 said:
I would not recommend this. I have talked to 2 people so far who said their phone have gone in to bootloops using the Eris Market Fix. After all, it is for an Eris. Read the comments on the app in market. Lots of people are using it on the wrong phone and having problems.
Do yourself a favor and just use the build.prop in this post as it has already been tested in numerous forums with no problems whatsoever, if done correctly.
Click to expand...
Click to collapse
I took a brief look at each file and I really don't understand how I got into trouble. As I said, I had not yet started doing any mods, just trying to install a few apps.
While I'm no computer or phone neophyte, I don't profess to be up to speed on Android yet. I do typically read through instructions pretty well, and search out multiple sources/explanations so I have a better 'understanding' of what I'm doing, rather than just "parrotting" the steps.
Having said that, I would like to know the difference between using 'adb remount' and the instructions I used in my first post. Is that just the difference in doing this via a shell command and not? ie, they perform the same action, just from a different starting point?
As for the Eris file, I did download that and all seems to be OK right now.

Sorry ahead of time for a possibly stupid question but I just wanted to be sure. Do you have to be rooted to do this fix?

Yes, it requires an edit to a file that you can only be edited when rooted

elkniwcire said:
I must say I take no responsibility if this causes problems but this worked for me. Do a search in the market for "Eris Market Fix." It was designed for the Eris but works just fine on my Droid X. I can see all the apps that didn't show up before. I haven't noticed any issues since applying this fix. You must be rooted for this to work, but I assume most everyone on Froyo already is rooted.
Click to expand...
Click to collapse
This works for me...thanks!

OP has been updated with original build.prop

Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input

will2live said:
Silly question but is the Non Stagefright file edit like the first one so the Market is fixed if you use either of the first 2 posted files. I realize the last file is just the stock build.prop but am a little confused on wah tis in the first 2 files. Obviously the first fixes the Market issue, so I guess I'm more question wha tis in the non stagefright file. TIA for any help/input
Click to expand...
Click to collapse
Just use the non-stagefright one.
Just like the post says, stagefright breaks HD video playback for SOME people. However some people dont care and just want higher quadrant scores, so they use the stagefright=true build.prop
Use the =false version for better stability.

Thanks for the reply.

[Q] fandango apk

does anybody have the Fandango apk? I flashed that new froyo update and now the market doesn't recognize my phone for some apps namely fandango

Try This:
(requires root and busybox and android SDK)
download the build.prop.zip file attached and remove the .zip (file should be named build.prop)
put the build.prop file in the same folder as adb.exe
open cmd and navigate to folder with adb.exe
Code:
adb push build.prop /sdcard/build.prop
adb shell
su
cd system
mv build.prop build.prop.old
busybox cp /sdcard/build.prop /system/build.prop
reboot
This should fix the missing apps market issues for all apps not just fandango ;-)
Let me know if it works or not

hmmm...so I would have to root my phone?...Uh I don't think i want to do that just yet. I think i can wait for official froyo 2.2 to come out then maybe it will be fixed. In the meantime Im using this app called "Date Night" i found in the market place. I uses the Fandango portal to buy movie tickets too, and it shows previews of upcoming movies and a lot more...to be honest it's even faster then that fandango app anyways, but thanks anyway. Upgrading my phone to the 2.2 was a job in itself. I don't want to take a chance and mess it up. I was so glad to see that it didn't root my phone in the process.

For anyone that needs it here it is.

Thank you so much... it worked!!!!! and i didn't have to root my phone! From what im hearing folks shouldn't hold there breath for att to release froyo for the captivate..and when they finally decide to release it they will have stripped the tethering feature from thr firmware, which is predictable. Do you have any other apk's or no where i can get more?

Glad to help. Shoot me a pm and I'll see what I got!

uh....whats a pm?

:facepalm:
Private message

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