I know there is a setting in build.prop "ro.camera.sound.forced", if it set to 0 or even removed it, the camera should be silent when taking photos.
But somehow I found that it's only works only some ROM, like it's working on the ICS ROM of MIDNOTE, but not TeamRocketRom, I checked both build.prop there were no ro.camera.sound.forced at all.
So do you guys know why is MIDNOTE can have no sound but not TeamRocketRom
It should work on all ROMs if you locate the sound that is played when you take a picture you should be able to do one of the following successfully:
1. Change the name/extension
2. Delete it
3. Swap the file with a custom made file which is just silence with the same name.
Im quite sure either of those should work (#1 worked for me)
Hope that helps.
novastorm17 said:
It should work on all ROMs if you locate the sound that is played when you take a picture you should be able to do one of the following successfully:
1. Change the name/extension
2. Delete it
3. Swap the file with a custom made file which is just silence with the same name.
Im quite sure either of those should work (#1 worked for me)
Hope that helps.
Click to expand...
Click to collapse
Thanks for your reply!
But I want the perfect solution, i mean the camera sound should be enabled according to whether the phone is silent or not.
Yeah, I agree. But I think that might be an issue, at least on the Stock ROM.
I believe they have strict rules in South Korea requiring a noise on a camera. So unless someone has addressed the issue in a custom ROM or app, you might be out of luck for the time being
novastorm17 said:
Yeah, I agree. But I think that might be an issue, at least on the Stock ROM.
I believe they have strict rules in South Korea requiring a noise on a camera. So unless someone has addressed the issue in a custom ROM or app, you might be out of luck for the time being
Click to expand...
Click to collapse
Agree. But in my case, I'm in Hong Kong, I've ro.camera.sound.forced added and set to 0, it worked. But later I restored it to stock rom (Hong Kong version), that setting not works anymore. That's why I wonder this strange behavior.
novastorm17 said:
It should work on all ROMs if you locate the sound that is played when you take a picture you should be able to do one of the following successfully:
1. Change the name/extension
2. Delete it
3. Swap the file with a custom made file which is just silence with the same name.
Im quite sure either of those should work (#1 worked for me)
Hope that helps.
Click to expand...
Click to collapse
This works for shutter sound but there is no sound file for AutoFocus.
lol its because of people taking unknown pics/videos in the asian counties mostly this law was enforces....
use a root explorer and goto /system/media/audio/ui and you will see the camera files just rename them.... that will silent camera
http://forum.xda-developers.com/showthread.php?t=1371755
anonymous572 said:
http://forum.xda-developers.com/showthread.php?t=1371755
Click to expand...
Click to collapse
that could cause a brick.... the S2 camera is diff from the Note camera... different features..... i'd be skeptical to try that route...
Related
I searched the forums for this and could not get any help on this. Is it possible to turn off the clicking sound for taking camera shots? I went to Settings, but there were no options for this. I am fine with the camcorder one, but find it irritating and noisy when more discretion is needed. Thanks
Two possible ways, although I have not tried either.
1. There are a couple apps in the market that are supposed to do this. Never used them and don't know about Donut compatibility.
2. Replace the actual shutter sound file with a blank sound file. I've seen this discussed in some old threads on here, so you should be able to find instructions with a search.
No 2 is your best bet.... quick and easy..
Also if you just put your phone on silent/vibrate mode that will shot the sound, at least it does for me.
Shrivel said:
Two possible ways, although I have not tried either.
1. There are a couple apps in the market that are supposed to do this. Never used them and don't know about Donut compatibility.
2. Replace the actual shutter sound file with a blank sound file. I've seen this discussed in some old threads on here, so you should be able to find instructions with a search.
Click to expand...
Click to collapse
Thanks so much for the advice. I think number 2 is the best answer I'll try to dig up the instructions.... hopefully it is searchable. Thanks again for everyone who chipped in
Instead of trying to keep up on the two CM threads that are already going and talking about the exact same things I figured I would start up a new thread and see if this fixes anything.
--------------
I will admit... I don't know jack about programming... but I am good at messing with stuff and seeing if it works. I got a little bored tonight and noticed there was a new change to the MIUI ROM that adds 720p recording. So being Halloween... why not Frankenstein a little!
I grabbed the camera.apk from the MIUI ROM (its an AOSP ROM.. so it should work right? lolz). Copied it over to my clean install of CM6.1 RC2 and boom... no crashing recording using 720p.
I have recorded about 30 videos now that are anywhere from 2 seconds in length to 5 minutes... one after another... without a crash.
There are a couple options missing that CM has... but I think this would be a good start to resolving the issues.
Please keep in mind.... there are a couple things you will need to do.
1. Download the following APK. (see below)
2. Using root explorer... browse to /system/app and check the current permissions for the existing camera.apk. It should be rw-r--r--.
3. Copy the downloaded camera.apk and replace the one in /system/app.
4. Change the permissions of the new camera.apk to rw-r--r--.
5.Close root explorer and reboot your phone.
6. Open the camera app, switch to camcorder. Using the onscreen menu, change the quality setting from high to custom.
6. Now select the top option to change the video quality. Select 720p.
7. Profit.
If you don't know how to change permissions... or know how to copy apks... please.. please.. please don't do this. If you are comfortable with it... let me know if it keeps crashing.
I know it doesn't have all the fancy settings the CM camera does... but I think this may be a very good step forward. So far.. It hasn't crashed out on me.
If you are going to do this and record one video and say its fixed... please dont bother. We need REAL testing.
The camera.apk can be downloaded here....
http://www.mediafire.com/?q9y8zst9aeqlgc7
Thanks all... if this ends up not working... I blame the to much beer.
If it does... we may be on a good start to getting this fixed. Cheers.
Oh yea... if you are using the camcorder.. you can turn of the screen and it wont force close when you turn it back on. Win.
Here's an update.zip for it. Flash via recovery. Also added the original CM camera from the Incredible build. I'll post a few cameras for you guys to test.
Thanks goes to the OP for getting this in motion.
touchpro247 said:
Here's an update.zip for it. Flash via recovery.
Click to expand...
Click to collapse
Thank you... I'll admit it... I fail. lol. Just trying to be of some help getting this fixed.
I have tried the Nexus camera.apk in the past... it had the same issue.
It seems that the 720p issue exists on most if not all of the CM builds.
The only difference I see from face value is that CM camera builds have the crazy auto focus. If you are in a quiet place, listen to the camera itself. It physiclly moves inside the housing.
If you ever happen to hear the camcorder app FC, you can hear a little "click" right before it force closes. That is the camera lens moving.
It appears that the auto focus is messing everything up. Without autofocus (the MIUI camera.apk)... everything appears to work as it should.
As soon as you throw in the fancy auto focus stuff... it causes crashes.
Food for thought. I don't know a lot about it... but progress is progress.
Thank you for a zip version, Root explorer doesn't work on AOSP roms for me, is this common across the board?
mikeymop said:
Thank you for a zip version, Root explorer doesn't work on AOSP roms for me, is this common across the board?
Click to expand...
Click to collapse
Works for me. Are you sure you gave it root access in SU with the remember button ticked?
Also, good to see that somebody took the initiative. I had posted in the CM forum this afternoon that the MIUI Rom had functioning cam but nobody seemed to notice and I don't have much skills - glad to see camalus did - going to try this right away...
http://forum.xda-developers.com/showthread.php?p=8931211#post8931211
I swapped the MIUI camera with root explorer and recorded 10 videos in 720p. The camera didn't fc on me at all. The videos looked good and playbacked smoothly on my phone and computer. The camera at times would get hung up for a second or two but I'm not complaining at all. Got a working camera now!
I just found that if you turn the focus mode to off in the camera settings with the camera that comes with cm6, this also allows you to record in 720p with no force closes. Funny its such an easy fix. As long as auto focus doesn't mean the world to you.
I have suspected for a while that the auto focus was causing issues.
I just loaded the patch on the newest nightly... no fc either.
I sent a message to koush on twitter. Hoping his intelligence can pinpoint this in more depth.
Here's to hoping!
Sent from my ADR6300 using XDA App
Anyone else testing this? Could use more help here.
Sent from my ADR6300 using XDA App
camalus said:
Anyone else testing this? Could use more help here.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Works perfectly for me. Taken 4 test videos in quick succession, no issues whatsoever.
Did not realize this was even an open issue. I believed this was already in the CM6.1 chain for inclusion in RC3 or whatever.
Ok. Just wanted to report my findings after flashing the zip file. The only settings I change in the camera was quality to custom in order to get the 720 resolution enabled.
Video #1: 1 min, 22 sec
I stopped recording of first video and without closing the camera app I started a 2nd video,
Video #2: Started recording and the camera freezed (FC would have been better) after 22 seconds. Had to pull out the battery to restart the phone.
In summary, is still not fixed. I'll revert back to the original Camera.apk.
Androidnite said:
Ok. Just wanted to report my findings after flashing the zip file. The only settings I change in the camera was quality to custom in order to get the 720 resolution enabled.
Video #1: 1 min, 22 sec
I stopped recording of first video and without closing the camera app I started a 2nd video,
Video #2: Started recording and the camera freezed (FC would have been better) after 22 seconds. Had to pull out the battery to restart the phone.
In summary, is still not fixed. I'll revert back to the original Camera.apk.
Click to expand...
Click to collapse
What version of CM are you running? What kernel? Did you do a full wipe before trying this?
camalus said:
What version of CM are you running? What kernel? Did you do a full wipe before trying this?
Click to expand...
Click to collapse
I did not flash the zip file and instead did it manually and it works for me.
Sent from my ADR6300 using XDA App
camalus said:
What version of CM are you running? What kernel? Did you do a full wipe before trying this?
Click to expand...
Click to collapse
I had a clean install:
1) wipe data/cache/dalvik
2) Install CM6.1 RC2
3) Install gapps
4) Wipe dalvik
5) Flash Adrynalyne's kernel: I have SLCD and the stock kernel does not work for me
6) Reboot until the homescreen
7) Go to recovery and flash camery fix
8) Reboot to homescreen and try camera
Which camera did you install the MIUI or CM6?
Sent from your mom's phone
masully1984 said:
Which camera did you install the MIUI or CM6?
Sent from your mom's phone
Click to expand...
Click to collapse
The CM6 one
Androidnite said:
The CM6 one
Click to expand...
Click to collapse
The MIUI camera has the fix, not the CM one.
Fretless said:
The MIUI camera has the fix, not the CM one.
Click to expand...
Click to collapse
LOL!!!! So why they posted a separate CM6 one? Are you saying you were able to use the MIUI one with CM6?
Androidnite said:
LOL!!!! So why they posted a separate CM6 one? Are you saying you were able to use the MIUI one with CM6?
Click to expand...
Click to collapse
Yes. The MIUI adds the 720p non-fc functionality, or at least it has so far.
I don't think I've actually seen this floating around anywhere, so I figured I'd share. Its the Camera Firmware updater from Samsung. I've had mixed results with its use on different firmwares. My only issue being FCing on an older Bionix build, as well as a few older Voodoo builds. I've had little to no problems with more recent voodoo builds, just used it on Trigger 2.9.2 with no problems, I've even used it on a phone running Gingerbread without issue. Yes I play with allot of phones...
http://www.multiupload.com/3JX5GPV9W6
Downloading now.. will test on stock and modded FFC version and report back.
Said I had the lastest version and then automatically gave me the option to uninstall
anything noticeably different on this over the standard stock FW?
I have an FFC so I doubt it's worth my time to test if there's no FFC support...
Does anyone know what this firmware is supposed to update?
pvspencer22 said:
Does anyone know what this firmware is supposed to update?
Click to expand...
Click to collapse
no idea however if you go into settings on the camera app, then go to firmware, then click on the second option firmware update
its downloadin and updating now on my phone i can report back later
I do not see any appreciable difference. granted i do not have an ffc so i cant comment on that. If you arent having any problems with your camera id say leave it alone.
Got this from Samsung apps. Nothing at all noticeable. Switched to captivate camera apk
Sent from my GT-I9000 using XDA App
Yea, no difference here either... or at least that I notice.
can you guys try the video recorder and see if it has the focus mode.
Sent from my SGH-T959 using XDA App
Anyone with a FFC (2nd gen) comment on this?
I've just installed it and tested it with the ffc (1st gen). There is not much different in my opinion. There seems to be a little less banding in low light condition and that's about it. 720p recording works well. I will test it with the 2nd gen camera tonight when I get home.
anthonys2r said:
Anyone with a FFC (2nd gen) comment on this?
Click to expand...
Click to collapse
Not chenge it all
Runing Toxicity_V2
wait maybe less yellow on the center of the screen on low light.
Spaming
I have tested the new firmware on FFC v2. Its having different issues with the camera. When I record on 720p I get a white screen. Its recording but I see nothing. Once I stop it crashes. I than go to gallery and my recording its there @ 720p or at least it seems that way.
I have been testing with different camera.apk files... some be have differently than others. All for the worst I am afraid so
wtf.now? said:
I have tested the new firmware on FFC v2. Its having different issues with the camera. When I record on 720p I get a white screen. Its recording but I see nothing. Once I stop it crashes. I than go to gallery and my recording its there @ 720p or at least it seems that way.
Click to expand...
Click to collapse
My camera is working without problem, Did u push or install the file?
solaresdonis said:
My camera is working without problem, Did u push or install the file?
Click to expand...
Click to collapse
I install the file.
Using Bionix-V 1.3.1
When I open the file it tells me I am running the latest firmware.
It didnt do anything for me.
Edit:
Which camera apk are you using?
Edit Again: Now it just reboots in 720p
Another Edit wtf!: lol ok If I set the permissions on the filr to -r- only the file crashes. If I set them to rwx-rwx- it gives me the white screen while it records.
Any ideas?
wtf.now? said:
I install the file.
Using Bionix-V 1.3.1
When I open the file it tells me I am running the latest firmware.
It didnt do anything for me.
Edit:
Which camera apk are you using?
Click to expand...
Click to collapse
I'm using 2.2.1 toxicity_V2 how can i check which camera apk is it?
Can you get the camera.apk file and upload it some where? And lets take it via PM I dont want to be tagged as spammer. This forum is some what very wacked.
wtf.now? said:
Can you get the camera.apk file and upload it some where? And lets take it via PM I dont want to be tagged as spammer. This forum is some what very wacked.
Click to expand...
Click to collapse
Ready check your PMs
I got my update right now through the camera app and it takes about a few minutes to update. Required for me to reboot. Really don't notice a difference but the annoying message of you need to update do you want to continue is gone now.
Hello guys. I had posted some months ago my question but all I was suggested was installing mods that I already had tried.
So, my 'problem' is that I find Stock Marshmallow's output(volume and bass) on headphones (3.5 jack) pretty low compared to Stock Kitkat. Especially the bass, it is really, really louder/heavier on Kitkat.
Is there any way to get/move Kitkat's sound enhancements right into Marshmallow?
Thanks in advance, have a happy new year!
The only way to try this would be decrypting the original KitKat files and recode them into MM, though you need some knowledge about how it works for it. As for now, I do not know any way to get back that feature from KK.
Mods are really great in this sort of situation, I myself use the A.R.I.S.E. mod and configured it for my in-ears.
devil188 said:
The only way to try this would be decrypting the original KitKat files and recode them into MM, though you need some knowledge about how it works for it. As for now, I do not know any way to get back that feature from KK.
Mods are really great in this sort of situation, I myself use the A.R.I.S.E. mod and configured it for my in-ears.
Click to expand...
Click to collapse
Unfortunately, I have no knowledge of coding etc.. I had tried arise sound mod but the sound was completely distorted(maybe I had installed something wrong,but all I did was install a .zip file and nothing more.)
Edit: could you message me and redirect me to the things you did and worked for you? I think I'll give a try tonight or tomorrow night! Thanks!
kwstas 13 said:
Unfortunately, I have no knowledge of coding etc.. I had tried arise sound mod but the sound was completely distorted(maybe I had installed something wrong,but all I did was install a .zip file and nothing more.)
Edit: could you message me and redirect me to the things you did and worked for you? I think I'll give a try tonight or tomorrow night! Thanks!
Click to expand...
Click to collapse
Well, installing the .zip is fine, but you ... gotta turn it on, too. When you flashed the zip, a new tool called Viper4Arise pops up in your app list. Open that and configure how you like to. In the app, you can change everything you like (and there's tons of stuff, trust me) but keep in mind to check if the module is active ( [≡] > Driver Status).
As of the settings I've done, I made the for my personal in-earphones (SoundMagic E10). There are things like ViPER-DDC which makes the sound of your head/earphones pretty nice if they're supported, if not, well then you gotta tune it yourself. Might plan to listen to a lot of different music and testing all the settings for your own preferences
devil188 said:
Well, installing the .zip is fine, but you ... gotta turn it on, too. When you flashed the zip, a new tool called Viper4Arise pops up in your app list. Open that and configure how you like to. In the app, you can change everything you like (and there's tons of stuff, trust me) but keep in mind to check if the module is active ( [≡] > Driver Status).
As of the settings I've done, I made the for my personal in-earphones (SoundMagic E10). There are things like ViPER-DDC which makes the sound of your head/earphones pretty nice if they're supported, if not, well then you gotta tune it yourself. Might plan to listen to a lot of different music and testing all the settings for your own preferences
Click to expand...
Click to collapse
Well, I'll maybe give a try and write you back... I didn't really understand whay you said there ' check if the module is active ( [≡] > Driver Status). '
Also, which one of these folders should I open and then,which version(file name) should I download?
I'm on Stock 6.0.1 with any other mod installed.
(yes,i'll make a nandroid backup before installing it)
Thanks in advance
Edit: I installed ViPER4Arise+2.5.0.5 and it worked fine,but still,the sound is quite,compared to Stock KitKat... Even after raising Master Gate (Limiter) to the max (6dB)... I don't know what to do
kwstas 13 said:
Well, I'll maybe give a try and write you back... I didn't really understand whay you said there ' check if the module is active ( [≡] > Driver Status). '
Also, which one of these folders should I open and then,which version(file name) should I download?
I'm on Stock 6.0.1 with any other mod installed.
(yes,i'll make a nandroid backup before installing it)
Thanks in advance
Edit: I installed ViPER4Arise+2.5.0.5 and it worked fine,but still,the sound is quite,compared to Stock KitKat... Even after raising Master Gate (Limiter) to the max (6dB)... I don't know what to do
Click to expand...
Click to collapse
Then it is probably limited by the ROM itself.. Well you can look up how to create your own custom rom with higher output at the audio jack, but aside from that, I don't have any other ideas how to raise it other than going back to kitkat.
Well the volume is loud enough for me, so sadly I can't help you with this
devil188 said:
Then it is probably limited by the ROM itself.. Well you can look up how to create your own custom rom with higher output at the audio jack, but aside from that, I don't have any other ideas how to raise it other than going back to kitkat.
Well the volume is loud enough for me, so sadly I can't help you with this
Click to expand...
Click to collapse
Exactly, KitKat allowed more output volume than Marshmallow does, I guess....I wish I knew how to increase the output levels and set them just as high as the Stock Kikat are.
kwstas 13 said:
Exactly, KitKat allowed more output volume than Marshmallow does, I guess....I wish I knew how to increase the output levels and set them just as high as the Stock Kikat are.
Click to expand...
Click to collapse
I might just randomly found a way to set the volume gain, but you need a unlocked bootloader + elitekernel (or any other) for that.
devil188 said:
I might just randomly found a way to set the volume gain, but you need a unlocked bootloader + elitekernel (or any other) for that.
Click to expand...
Click to collapse
Ah yeah, I found that too some months ago,forgot to mention that...but i don't want to unlock bootloader for now...thank you man!
Yes, I know that the filename is "Effect_Tick.ogg" located in /system/media/audio/ui. I also know that the 'setting' is in "Settings -> Sound and notification -> Other sounds". But for some reason, it just will not play.
Yeah, I like to hear that click when I press things on my phone(s). So much so, that I have kept the old ICS sound around to write it to my other phones since.
I'll try to make this short. I had my old Nexus 6 go into a bootloop about a year ago so I restored it with a factory flash and then re-rooted it and flashed my favorite Rom, Pure Nexus 5.1.1. It (the click) had worked before, but I do not know why it stopped working. There were other problems still on my phone so I finally bought a new one and flashed it to this ROM. I used MyBackupPro to restore my apps as I do not care for some of the newer version of apps that I use. I was also trying to flash the TBO market on my phone as well. When first I flashed my phone, the click was working, but somewhere along the line it stopped. If I use root explorer and go to the file's location and press on it, it will play just fine. So I'm just not sure what's up.
I did get a big hint. I installed "FP Click sound changer". Within that app, when I press on "Effect_Tick.ogg" I get the following message:
"java.lang.NullPointerException: Attempt to invoke virtual method 'void android.media.MediaPlayer.setAudioStreamType(int)' on a null object reference"
This leads me to believe that is is something inside of framework-res.apk or systemui.apk or something like that. I didn't see enough in build.prop to make me think it would be in there. Any ideas?
Thanks in advance.
The error you're getting with FP Click Sound Changer is because the app likely isn't properly initialized. Meaning a change in Android between when the app was last updated and now has broken the app. The error has nothing to do with either of the .APK files you mentioned. If I recall correctly, neither system app deals with media to begin with.
The most obvious question here is whether you have tried a new copy of the audio file, even if it appears to work perfectly. If you have done that and are still having issues, one of your apps that you are using is causing the problem. You're going to have to do some troubleshooting to resolve this, namely starting with a blank slate and reinstalling apps one at a time until you find the one that causes the problem. Before you protest, any answers without you attempting some troubleshooting on your own are merely guesses made off of inadequate data.
Thank you for the reply, however my ROM was 'cooked' up on Sept 2015 and FP Click Sound changer was released/updated on Dec 26 2015, so what you suggest cannot be the cause. Besides, it only throws the error on Effect_Tick.ogg and no other system sound. And yes, I do have fresh copy of the file from ICS days.
But you are correct, if nobody knows which system app would throw that error message, then I know a fresh start is in order.
On this forum, many people have updated their N6 to more up-to-date versions of Android than the version you had. However, I wouldn't have provided that answer had you told us which version of Android you were running in the first place as well as the fact you built it yourself.
In any event, I hope your fresh start works out for you. You may also want to consider building a newer version of AOSP for yourself as well.
Thank you again for the reply, however:
Strephon Alkhalikoi said:
However, I wouldn't have provided that answer had you told us which version of Android you were running in the first place as well as the fact you built it yourself.
Click to expand...
Click to collapse
teddyearp said:
I had my old Nexus 6 go into a bootloop about a year ago so I restored it with a factory flash and then re-rooted it and flashed my favorite Rom, Pure Nexus 5.1.1. <snip>
Click to expand...
Click to collapse
I am trying to do a Google search on the error message itself as well.
I missed that in your post. Oops.
Strephon Alkhalikoi said:
I missed that in your post. Oops.
Click to expand...
Click to collapse
Well, I certainly meant no offence. Some years back, I used to to help folks out with their Android phones/problems and would at times be about the same way as you. Many times the details were not there. However equally so sometimes, the OP did provide the answers but the others that would chime in did not seem to read all of them.
With that said, I was thinking about rewording my question to perhaps ask if anyone knew which system apps on Android 5.1.1 would call for Effect_Tick.ogg so I could try to find where it had been set to 'null', but I stumbled across my solution after all. File permissions. So for any readers:
Yes, using ES Explorer, I copied again my good Effect_Tick.ogg to /system/media/audio/ui and it still didn't work except in music player. So I thought since ES would allow me to see and change file permissions, let me take a look. Sure enough, the file permissions for Effect_Tick.ogg were different than all the other sounds in that location. It was set to rw,rw and group sdcard,s. All the others were rw,r,r and group root. Changed to match the others and problem solved. :highfive:
Thanks very much again for trying to help, at least someone (you) did and that does mean a lot to me on such an old(ish) device since as you said, many have moved on and/or flashed much newer versions of Android to the N6. :good::good:
I'm glad you solved your problem. Even better, you came back to tell us about it.
Too many find the solution and don't say anything.
Strephon Alkhalikoi said:
<snip>Too many find the solution and don't say anything.
Click to expand...
Click to collapse
How well I remember that fact.