Since we now have the LK8 leak, and no custom Roms, yet. I've seen the "how do I disable camera sounds" question asked a few times.
I'm sure your favorite developer will incorporate this feature, like they have in the past, as they update to the new base. This is mainly for us impatient noobs
You must be rooted. Using a root explorer, navigate to /system. Select build.prop. Scroll until you find this line:
# Camera sound play enforced for SPR
ro.camera.sound.forced=1
and change to:
# Camera sound play enforced for SPR
ro.camera.sound.forced=0
If you also want to be able to toggle the sound in the camera menu, navigate to /system/csc, and select feature.xml.
Scroll to the "Camera" section, and change this line from this:
<CscFeature_Camera_ShutterSoundMenu>false</CscFeature_Camera_ShutterSoundMenu>
to this:
<CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu>
Save, exit,
Make sure permissions are set to: rw-r--r--,
and reboot.
yes happend
Man, I must be doing something wrong.
I used ES file explorer to make the changes and rebooted twice but the sound is still there and the menu doesn't show the camera option either...
I am trying my hand at this instead of the apk I found.
scoobmd said:
Man, I must be doing something wrong.
I used ES file explorer to make the changes and rebooted twice but the sound is still there and the menu doesn't show the camera option either...
I am trying my hand at this instead of the apk I found.
Click to expand...
Click to collapse
Make sure ES has root permission, and also make sure you are saving the updated file, before exiting. I'll try to do it from ES File explorer, in a little while, to see if I can make it work.
Okay, I was able to follow this procedure, with ES File Explorer, also. I just made sure all of the "root" boxes were checked in settings.
Thanks for the help.
I confirmed the setting and everything where correct after a reboot, I wonder if installing that camera app to silence the sounds did something...
scoobmd said:
Thanks for the help.
I wonder if installing that camera app to silence the sounds did something...
Click to expand...
Click to collapse
Not sure, but I do know people reported that the app from that other post, killed Spen, and lock screen sounds, too.
Using Root Explorer, when I try to tap on "build.prop" nothing happens.
There is a tiny yellow icon in the shape of a shield with a star on it on that line. What does that mean? Why won't it let me go in?
Thank You OP for the instructions. It worked.
I used RomToolbox Pro toget it done.
slthree said:
Using Root Explorer, when I try to tap on "build.prop" nothing happens.
There is a tiny yellow icon in the shape of a shield with a star on it on that line. What does that mean? Why won't it let me go in?
Thank You OP for the instructions. It worked.
I used RomToolbox Pro toget it done.
Click to expand...
Click to collapse
Thanks for the feedback, I'm glad you got it working.
Thanks it works great on MA5 also thank u much
Galaxy Note 2
Thanks a million, works perfectly on my stock rooted!!
Sent from my SPH-L900 using Tapatalk 2
Worked great for me on stock rooted with exynos abuse and ES File explorer.
Still working strong! Thanks.
twoscomplement said:
Still working strong! Thanks.
Click to expand...
Click to collapse
Glad I could help.
Related
I love this phone.
But, I can't turn the camera shutter sound off.
I have seen the following solutions:
Edit build.prop and set the camera sound value to =0
or
Use Camera Zoom Fx app and delete the camera_click.ogg file
I would prefer to do the former.
I guess I need to root my phone to do this - or is there an easier way?
I have never rooted a phone and I don't have a need for a rooted phone other than to be able to r/w the build.prop file.
Can I root it, edit the build.prop file, and then unroot it and have the build.prop file keep my edits?
Does anyone have any straightforward steps on how to root and then unroot this phone?
Thank you for any guidance you can provide!
J-Ha
can't freaking delete this post... tried to edit it and since im a new member it wouldn't let me within 5 minutes...my full reply is farther down.
http://forum.xda-developers.com/showthread.php?t=1994626
I believe that you can unroot directly from the superuser app that is sideloaded via this rooting method. Once unrooted, the changes that you made should remain. If they don't for some reason, all you have to do is keep root and just deny apps that request superuser access.
jhaaaa said:
I love this phone.
But, I can't turn the camera shutter sound off.
I have seen the following solutions:
Edit build.prop and set the camera sound value to =0
or
Use Camera Zoom Fx app and delete the camera_click.ogg file
I would prefer to do the former.
I guess I need to root my phone to do this - or is there an easier way?
I have never rooted a phone and I don't have a need for a rooted phone other than to be able to r/w the build.prop file.
Can I root it, edit the build.prop file, and then unroot it and have the build.prop file keep my edits?
Does anyone have any straightforward steps on how to root and then unroot this phone?
Thank you for any guidance you can provide!
J-Ha
Click to expand...
Click to collapse
You would need to root it to edit the build.prop, as it is located in system. That other way to unroot might work to keep it but if you use lgnpst it would replace all the system files, giving you your stock build.prop again. If you wanted to delete the ogg file you would still need to root for that. At least on my phone the camera_click.ogg file is located it /system/media/audio/ui directory. You could just move it somewhere else as a backup. But....being rooted is awesome
is their a complete fix to this.?
HelloDominick said:
is their a complete fix to this.?
Click to expand...
Click to collapse
jat255 said:
HelloDominick, any reason my post above doesn't work for you? That fixed the sound issue for me.
Click to expand...
Click to collapse
You had to root the phone first right or no.?
This solution didn't work for me. I did all of it, and upon resetting permissions, it makes a new file" build.prop.bak and I still get shutter sound. Using es file explorer
Sent from my LG-LS970 using xda app-developers app
i rooted my device where is the location to edit the camera sound.?
I dont see this code "ro.camera.sound.forced=1" anywhere
NVM. I found it, im getting old now.
but tested it and it works like a charm
HelloDominick - I still haven't gotten around to rooting the phone, so I haven't done this yet. Do you really have to have the sound off on the phone in order for this to work?
Colonel Travis said:
HelloDominick - I still haven't gotten around to rooting the phone, so I haven't done this yet. Do you really have to have the sound off on the phone in order for this to work?
Click to expand...
Click to collapse
Yes. Even deleting the camera shutter sound and editing the build.prop result in this. I just did it myself
Sent from my LG-LS970 using xda app-developers app
Anyone try repackaging the camera apk wi th out the shutter sound. Its what we had to do with the evo 3d`s
Sent from my LG-LS970 using Tapatalk 2
jat255 said:
Hmm... That's interesting. Only thing I can think of is maybe set the permissions via adb? Maybe ES has some issue?
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Found the solution to be rebooting after the entire process. I forgot I hadn't done it, and decided to just reboot for the hell of it. No shutter sound
Sent from my LG-LS970 using xda app-developers app
I think (once rooted) is safest to just overwrite the click sound(s) with a silent one. Then it plays but you can't hear it. works for me and any camera proggy that defaults to the system will use it too.
thecolor said:
I think (once rooted) is safest to just overwrite the click sound(s) with a silent one. Then it plays but you can't hear it. works for me and any camera proggy that defaults to the system will use it too.
Click to expand...
Click to collapse
Where is the camera sound located in the filesystem? Thx!
hallucinate said:
Where is the camera sound located in the filesystem? Thx!
Click to expand...
Click to collapse
On the LGoG it's in: system > media > audio > ui > camera_click.ogg
It may be in a different location on other devices.
You have to be rooted in order to write over system files, but I just renamed the original to camera_click.ogg.bak and then copied the silent version in with the same original name "camera_click.ogg" less the quotes and making sure it's an ogg file too, so there is no system playback error.
Hope that helps.
thecolor said:
On the LGoG it's in: system > media > audio > ui > camera_click.ogg
It may be in a different location on other devices.
You have to be rooted in order to write over system files, but I just renamed the original to camera_click.ogg.bak and then copied the silent version in with the same original name "camera_click.ogg" less the quotes and making sure it's an ogg file too, so there is no system playback error.
Hope that helps.
Click to expand...
Click to collapse
Replaced the file but no love, same click sound... Any other path?
hallucinate said:
Replaced the file but no love, same click sound... Any other path?
Click to expand...
Click to collapse
I assume it's the LGoG you are attempting this with?
Mine is the first generation (incase there are other generations.)
You'll also want to verify it was overwritten. I'd try playing the sound once you do... just to be sure it's the write file.
Otherwise, you might search your device for the sound and see if it's listed elsewhere.
In case the program you are using does not have "system" write capability, I might suggest ES File Explorer.
Either way, you will have to access the settings to turn on the ability to "write" to root in order to "overwrite the file".
Additionally (if the file is changing back - or so it would seem)... be sure to check the permissions it has before you overwrite it and when you do (assuming success).. make sure to set the "new" files permissions to the same as what the old file had. Else, the OS might overwrite the "new" file with a tared (backed up) version... knowing that it's been screwed with.
It's kind of a form of protection from corruption (computer sees potentially bad file and replaces it with good file.)
Good luck and happy fourth!
Phantom camera_click.ogg
I beg your forgiveness for my ignorance, but I've never done much tweaking to file systems after a rooting... but my gf has the Sprint Optimus G and can't find the camera_click.ogg file at all using Astro File Explorer. Does anyone know any other location it may be at? As a computer technician, I'm embarrassed at my lack of know-how around the Droid OS!
Not sure if you looked at this thread: http://forum.xda-developers.com/showthread.php?t=2051384
Read the op then go to page 11 and you see there are 2 fields that need to be changed.
After you do that and reboot as it states, you will have sound when you have your volume on and no camera sound when you turn the volume down to vibrate or silent. At least that is how it is for me. I prefer it that way.
Hope this helps
Sent from my LG-LS970
Naturally
Per Murphy's law, after she and I both looked for around 30 min before giving up and me posting on the forums, I downloaded the ES file explorer and found both files within seconds.
Got it with the silent camera while the phone is on silent/vibrate. Now for a little tweaking to silence it with the volume up.
Thanks for your help, guys and gals. No wonder XDA-devs is one of, if not the, top-notch sites!
Regards,
Agnati
One of the biggest complaint I have with the Samsung keyboard is that it does not have auto correct and it drives me nuts when I type. I know I can d/l another keyboard but I happen to love the samsung keyboard with that exception. So after some googling, I found this:
http://forum.xda-developers.com/showthread.php?t=2101338
I really want to try but I do not see anywhere (I searched also) if this will work for the t-mobile version. Has anyone tried this before?
safeplayer22 said:
One of the biggest complaint I have with the Samsung keyboard is that it does not have auto correct and it drives me nuts when I type. I know I can d/l another keyboard but I happen to love the samsung keyboard with that exception. So after some googling, I found this:
http://forum.xda-developers.com/showthread.php?t=2101338
I really want to try but I do not see anywhere (I searched also) if this will work for the t-mobile version. Has anyone tried this before?
Click to expand...
Click to collapse
I tried it. Stuck at Samsung boot screen. Had to restore from back up.
Sucks, they have this for Sprint and Verizon.
Hope someone fixes this
Sent from my GT-N7105 using xda app-developers app
Sure. I took a look and replicated the smali edits using the UVALL4 SamsungIME.apk.
All credit goes to Adryn and those he kanged it from
Flash this and you should be all set.
md5: EF529E56018EECE84362F20AD6FF80FB
dwitherell said:
Sure. I took a look and replicated the smali edits using the UVALL4 SamsungIME.apk.
All credit goes to Adryn and those he kanged it from
Flash this and you should be all set.
md5: EF529E56018EECE84362F20AD6FF80FB
Click to expand...
Click to collapse
Confirmed working on XXDLL7. Thanks so much for this mod!
dwitherell said:
Sure. I took a look and replicated the smali edits using the UVALL4 SamsungIME.apk.
All credit goes to Adryn and those he kanged it from
Flash this and you should be all set.
md5: EF529E56018EECE84362F20AD6FF80FB
Click to expand...
Click to collapse
I know you said to flash this, but can I simply push the apk using es explorer and changing the permissions?
safeplayer22 said:
I know you said to flash this, but can I simply push the apk using es explorer and changing the permissions?
Click to expand...
Click to collapse
Yessir
safeplayer22 said:
I know you said to flash this, but can I simply push the apk using es explorer and changing the permissions?
Click to expand...
Click to collapse
What steps would you take to change the permissions so we can install the apk with es explorer?
As you may guess, when I try to straight install it with es explorer, I get a message stating "Application not installed".
Thanks.
Dawgneck said:
What steps would you take to change the permissions so we can install the apk with es explorer?
As you may guess, when I try to straight install it with es explorer, I get a message stating "Application not installed".
Thanks.
Click to expand...
Click to collapse
You need to push it to /system/app. Permissions for items there tend to be 644 or rw-r--r--
Dawgneck said:
What steps would you take to change the permissions so we can install the apk with es explorer?
As you may guess, when I try to straight install it with es explorer, I get a message stating "Application not installed".
Thanks.
Click to expand...
Click to collapse
You don't actually install the APK. First, make sure you save a copy of the original "SamsungIME.apk". then extract the APK from the zip file. copy and paste the apk into /system/apps, it'll replace the original file. Once you pasted the apk, long press the apk file and you should be able to change permissions to: rw-r-r, then reboot the phone.
Just remember, you must be rooted in order to change system files.
I posted this because surprisingly I have not seen this post for our nexus 4. Thank this awesome guy from xda for creating this for all devices!!! Here's the link to his post and also here's some snapshots
http://forum.xda-developers.com/showthread.php?t=2143860
Oh if you didn't know you can pinch to zoom to do this awesome zoom effect. Try it out!! You have to flash through twrp or cwm. It will install the xperia launcher as well so if you want that aligned perfectly you have to edit your build prop. How to do that?
Easy!!
1st download es file explorer (its free)
2nd when you open es file explorer hit the menu key and tap settings
3rd scroll all the way down and click root settings and check all the boxes.
Now that you've done that, hit back until you get to a sign that pops up and says "press again to exit" then don't exit obviously.. You've just got full access to your files!! Meaning be careful which system files you touch! You only need to modify one. Trust me. It sounds hard but is a lot less complicated. Simply navigate to system/ then go all the way down to build.prop. simply tap on it and click es note editor. Then locate " ro.sf.lcd_density=320" then simply change the 320 to 340 and save. It will automatically create a back up build prop for you. Here's where you really need to watch out. Make sure after your done editing and saving your build.prop you TAP AND HOLD build.prop and scroll all the way down to properties and tap it. Then tap change and check all the boxes on the left and below write tap the top middle box. If your confused I posted a pic below... What your are doing here is setting permission to the file you just modified. Then now that you just set permission your good to reboot!!! After you reboot you just flash jb gapps and clear cache and dalvik cache. And your launcher is perfectly set. If you did not fix permissions the way the pic looks you won't boot up at all you'll only be able to fastboot. That's why I say its important to follow step by step. Also the reason I say flash gapps is because if you don't you won't be able to install certain apps in the play store (it'll say device not compatible). No more misaligned launcher!! If your don't like the launcher simply use titanium backup to remove it or search through file explorer. Bye all!!
Sent from my Nexus 4 using xda app-developers app
Cool.
[NEXUS⁴] [CARBON1.6] [MATR1X8] [TWRP]
If I remember from the Nexus 7 forums correctly, changing your build prop will cause future Android update to fail during installation. This looks awesome though.
It may cause problems with installation with modified changes
But that would just require you to go back to stock with our recovery tool. I never update my ROM straight through a custom rom. Or simply use your "back up build.prop" that I mentioned es explorer does automatically for you and rename that back up back to build.prop then delete modified build.prop. Of course always make sure you set your permissions even on the back up !
Sent from my Nexus 4 using xda app-developers app
dEris said:
Cool.
[NEXUS⁴] [CARBON1.6] [MATR1X8] [TWRP]
Click to expand...
Click to collapse
Thanks
Sent from my Nexus 4 using xda app-developers app
I have flashed the Whompasaurus rom onto my galaxy note 2 (Sprint) and I cannot change my s-pen sounds. I have tried to use ES explorer and go into /system/media/ui and tried to rename the Pen_att_noti2.ogg to Pen_att_noti2.ogg.bak but every attempt has failed. I checked the properties of the file and it says that the file is readable and writable. I have even tried to copy the sound (that I want) into the file and overwrite it but that does not work as well. Is the whompasaurus rom interfering with this? Am I doing something wrong? Are there special settings I must have? Any help is greatly appreciated.
P.s.: I would have posted this in the whomp forum, but it seems that I do not have enough posts, "requirements" to post into the developers thread.
I am hoping someone would shed some light onto my situation
Please and thanks!
-Timmy
check to make sure you root permissions enabled in ES Folder. I have to enable it every time. Just hit the menu button, Root Explorer, Mount R/W, and change the appropriate properties. It took a few a time to figure out why names and properties we're changing. The fail message is really brief and easy to miss.
lovekeiiy said:
check to make sure you root permissions enabled in ES Folder. I have to enable it every time. Just hit the menu button, Root Explorer, Mount R/W, and change the appropriate properties. It took a few a time to figure out why names and properties we're changing. The fail message is really brief and easy to miss.
Click to expand...
Click to collapse
THANKS! that helped a lot. appreciate it.
Have you seen this?
klbjr said:
Have you seen this?
Click to expand...
Click to collapse
wow i did not see that haha. Btw is it possible to have more than 3 sounds? just curious.
thaittnguyen said:
wow i did not see that haha. Btw is it possible to have more than 3 sounds? just curious.
Click to expand...
Click to collapse
Looks like he just updated today and added some more sounds. Up to 20 from 3.
So I have successfully rooted my wife's TMobile D851, which was verified using joeyk root checker app from the playstore, but I am unable to edit the build.prop so I can hide the nav bar and install lmt launcher for pie control. Am I missing something? I have no issue with my Nexus 5 or any other phone I've tinkered with and I am drawing a blank on what the issue is.
I'm hoping it's something super obvious that I missed and I'll feel stupid after I'm told what I am doing wrong.
JeauxAdam said:
So I have successfully rooted my wife's TMobile D851, which was verified using joeyk root checker app from the playstore, but I am unable to edit the build.prop so I can hide the nav bar and install lmt launcher for pie control. Am I missing something? I have no issue with my Nexus 5 or any other phone I've tinkered with and I am drawing a blank on what the issue is.
I'm hoping it's something super obvious that I missed and I'll feel stupid after I'm told what I am doing wrong.
Click to expand...
Click to collapse
the build.prop is huge for the lg g3(to big for some apps) try copying it to your pc and editing it there with notepad++ end then placing it back and set permissions(important or you will brick)
suljo94 said:
the build.prop is huge for the lg g3(to big for some apps) try copying it to your pc and editing it there with notepad++ end then placing it back and set permissions(important or you will brick)
Click to expand...
Click to collapse
I had thought about that so before I made this post I did a adb pull /system/build.prop and edited it with notepad++, as you suggested, but then I am unable to actually push it back. Can I just put it into a folder on my phone and then use some root file browser like ES or whatever and set permissions that way?
JeauxAdam said:
I had thought about that so before I made this post I did a adb pull /system/build.prop and edited it with notepad++, as you suggested, but then I am unable to actually push it back. Can I just put it into a folder on my phone and then use some root file browser like ES or whatever and set permissions that way?
Click to expand...
Click to collapse
place it in /system then in es enable root explorer then click your newly added build.prop long click it then select properties then change permissions to
Code:
yes yes /
yes / /
yes / /
suljo94 said:
place it in /system then in es enable root explorer then click your newly added build.prop long click it then select properties then change permissions to
Code:
yes yes
yes / /
yes / /
Click to expand...
Click to collapse
Your description of the permissions is a little weird but I think I can figure it out. I imagine it's the same permissions the current build.prop has? My wife has now taken her phone and gone to bed so I will have to try this tomorrow. Thank you very much for your assistance!