HOWTO: Disable Camera Sound (completely silent)
Without deleting anything.
Edit: As pointed out by nickbarbs, after you have completed one of the below methods, the Camera sound is controlled via "System Sounds". If you turn up, down, or off the "System Sounds", the Camera sound would be changed respectively.
This means that you can now control the camera sound at will via volume control functions.
METHOD 1
1. Create a file called "local.prop" in /data/ if it doesn't exist. Example: "/data/local.prop"
2. Open the file "/data/local.prop"
3. add the line to the file:
Code:
ro.camera.sound.forced=0
4. Reboot and all sound in the camera app is completely silent.
5. To recover the sound, you can either delete the local.prop file or change the code to:
Code:
ro.camera.sound.forced=1
METHOD 2: ADB
1. unrar the attached file "local.prop.rar"
2. copy the "local.prop" file to your ADB folder
3. ADB push local.prop /data/local.prop
4. Reboot phone.
5. To restore sound, just delete local.prop and reboot
-----
POSSIBLE BATTERY DRAIN FIX
In addition, for those who are having huge battery drains from Android OS, I also had it. On original KDD firmware, no problem at all, but after updating to KE2 with KIES, I had it all afternoon. I did a hard reset, and the battery drain seemed to go away, but I can neither guarantee or give a 100% confirmation (considering the fact that the Android OS battery usage is based on %, so if I constantly use the phone, Display goes up to 54% and Android OS drops to 10%)
Did a hard reboot by the following method:
WARNING: Will delete apps and all data; phone will boot like new phone.
1. Make sure phone is root first if you want root, and both SU and BUSYBOX installed
2. Shut down phone
3. Hold on the "UP" and "HOME" key, and press the "POWER" button for 2-3 seconds to turn on the phone (make sure to release the "POWER" key after the phone turns on, but continue holding "UP" and "HOME")
4. Select "wipe data/factory reset" and then "wipe cache partition" to remove both.
5. "Reboot system"
6. Once phone has rebooted, Root stays if properly installed, and phone starts off like new.
7. I have been using the phone since for 7 hours now, and seems better.
still have sound when focusing when taking pictures.
[email protected] said:
still have sound when focusing when taking pictures.
Click to expand...
Click to collapse
It needs to be disabled within Camera.apk
I'll look at that just now then.
Sorry; I live in Hong Kong and posted it at 2am in the morning and made a typo. It should be:
ro.camera.sound.forced=0
Will correct original post now.
kohiiou said:
Sorry; I live in Hong Kong and posted it at 2am in the morning and made a typo. It should be:
ro.camera.sound.forced=0
Will correct original post now.
Click to expand...
Click to collapse
Still not working...
mrfreddan said:
Still not working...
Click to expand...
Click to collapse
Did you reboot your phone? The changes doesn't persist till after a hard reboot.
Make sure it's also in:
/data/local.prop
And not
/data/data/local.prop
Double check to make sure you have it in the right place too and for example NOT in /sdcard/data/local.prop.
YES!! works great for me! not only that - but it follows the setting of you phone therefore
- Phone silenced = NO Camera sound at all (focus OR snap)
-Phone sound on = Camera sound with Focus AND snap
Thanks a lot dude. finally.
cheers
nick
by the way i extracted your .Rar file to my phone's SD card from my windows machine. Then i copied the file with Root Explorer to /data
= Profit
nickbarbs said:
YES!! works great for me! not only that - but it follows the setting of you phone therefore
- Phone silenced = NO Camera sound at all (focus OR snap)
-Phone sound on = Camera sound with Focus AND snap
Thanks a lot dude. finally.
cheers
nick
Click to expand...
Click to collapse
Confirmed - it's now related to the system volume.
Is possible to create tweak which enable digital zoom while recording 1080p video? Yeah, I know it is digital zoom but sometimes it would be usefull. Now zoom is possible only with 720p or less.
You need to have root for this, no?
Because I haven't rooted it yet and it doesn't work.
El Salvador said:
You need to have root for this, no?
Because I haven't rooted it yet and it doesn't work.
Click to expand...
Click to collapse
Unfortunately, yes you do.
kohiiou said:
POSSIBLE BATTERY DRAIN FIX
In addition, for those who are having huge battery drains from Android OS, I also had it. On original KDD firmware, no problem at all, but after updating to KE2 with KIES, I had it all afternoon. I did a hard reset, and the battery drain seemed to go away, but I can neither guarantee or give a 100% confirmation (considering the fact that the Android OS battery usage is based on %, so if I constantly use the phone, Display goes up to 54% and Android OS drops to 10%)
Click to expand...
Click to collapse
it works for me too! on KE1 rom, after 8 hours, battery is at 5%!
after hard reset, after 8 hours, i still have 50% battery left!
So far it looks like hard reset fixed my battery life problem too
yep same here hard reset, root still remains, all apps gone, but hey after 9hr used only 25% battery....thanks for the tip....may try the camera trick aswell later...
kohiiou said:
Did you reboot your phone? The changes doesn't persist till after a hard reboot.
Make sure it's also in:
/data/local.prop
And not
/data/data/local.prop
Double check to make sure you have it in the right place too and for example NOT in /sdcard/data/local.prop.
Click to expand...
Click to collapse
When you say hard reboot, do you mean reset back to factory settings or turn phone off completely then turn on again??
sheridan2000 said:
When you say hard reboot, do you mean reset back to factory settings or turn phone off completely then turn on again??
Click to expand...
Click to collapse
The latter - don't confuse hard reboot with hard reset
Summered said:
The latter - don't confuse hard reboot with hard reset
Click to expand...
Click to collapse
Thanks....just pushed the file...thought that it did not work but noticed that you have to turn off all sounds inorder for camera sounds to turn off as well. When sound is on then camera sounds are back.
Great.
works like a charm! both focus and snap sound are now disabled on silent mode. thanks=)
How do you detect if you have the Battery Drain Issue?
Battery Usage stats?
A developer contacted me to help him figure this battery issue and high Android OS usage out so he asked me to make a post regarding a test he would like us to perform. Please follow the instructions below to help out -- the first part everyone can participate in and the second part requires root, but even if you are not rooted please help out.
TEST INSTRUCTIONS
Reboot phone and charge to a set amount.
Turn on Wifi (make sure "Always On" is set).
Let the phone run idle with screen off (turn off background data if possible) for as long as you can. Even go watch a movie and leave your phone alone.
If you get an urgent text or call that needs answering, try to let the phone go back to sleep for at least another hour or so.
After this time has elapsed, please grab a screenshot of your Android OS usage (after clicked, showing Keep Awake time). Also note how much battery percentage you lost in this time.
ROOT INSTRUCTIONS
If you are rooted, please perform the following two steps after finishing the steps above:
Load adb shell
Run the following two commands as su:
cat /proc/kmsg > kmsglog.txt
cat /proc/interrupts > interlog.txt
cat /proc/net/netstat > netlog.txt
Grab these two log files and paste them into pastebin.com or attach them to your post.
Thank you for your help!
Edit: If you are rooted, you can run the commands above from a terminal emulator but just type "cd sdcard" first since the / directory is not writeable. The three text files will then be in your SD card for emailing or pastebin'ing.
I did a basic search of the GNex section of the forum and didn't find any conspicuous information, thus I wanted to see if anyone had any suggestions for dealing with the "debuggerd" system process.
I have a yakjuux 4.0.4ota with franco-kernel milestone3. I started with 4.0.1 and no mods, upgrading to the 4.0.x otas as they came out. I have had this phone about 4-5 months now. I have been rooted and unlocked since I have had 4.0.1.
Not exclusively to the 4.0.4 nor the franco-kernel I have noticed a process "debuggerd" running on my phone. rcently, twice in a day I found that process consuming 30+% of the cpu, causing a sudden drain in my battery. Prior to 4.0.4 I had not gathered any empirical data as to how much debuggerd was consuming, but did have times when the battery would radically drain, and I did notice debuggerd running.
I was able to launch a shell on my phone and kill the process-id for debuggerd at which point cpu load would drop instantly.
I tried freezing (via Titanium) many of my apps that would use data or were running at the time of the high cpu load (I wasn't sure if that would free up what triggered the process, just thought it was worth a try). I turned off a lot of software (eg. tasker, alarmapps, etc). As I froze/disabled apps en masse it was still using up the cpu. I tried killing apps from within watchdog. Still debuggerd would maintain a high cpu load. A reboot did get rid of it once, but in that session it did come back. Played with the USB debugging mode. I didn't reboot between many of these test.
I'll continue to kill it's pid if it shows, which the signs are really obvious in watchdog app (set my system warning low enough to catch it). I'm just familiar with the problem now.
* Any suggestions on tracing what's triggering debuggerd?
* Thoughts on alternative methods to prevent it from being used?
* I doubt deleting that bit of software is a good idea, right?
* Substitute it with something inert?
* Maybe I should create a button that gets it's pid and kills it?
Thoughts?
I found a shell script on http://en.androidwiki.com/wiki/Android_Shell_tips_and_tricks
It finds the pid by name - which is handy since pid's can be random.
I can run the shell script with SManager (which can provide the shell script any required arguments) from the phone desktop without having to go into the console.
It's a bandaid but it works. I can quickly and easily kill the (or any) errant processes that are not apps.
#!/system/bin/sh
# usage: kill "/full/command/line -with arguments"
for file in /proc/[0-9]* ; do
cmd=$(cat $file/cmdline)
iseq=${cmd%$1}
if ! ( (echo ${cmd:?}) > /dev/null 2>&1) ; then
continue
fi
if ! ( (echo ${iseq:?}) > /dev/null 2>&1 ) ; then
kill -9 ${file#/proc/}
fi
done
I share the same problem. debuggerd is cpu hog.
I dont want to kill it as it is not normal in my case. It has been lasting for more than an hour with high cpu usage.
I am using franco kernel 158 and Samsung GNexus ROM 4.0.4 IMM76K.
any help would be appreciated. Thanks.
mcdull said:
I share the same problem. debuggerd is cpu hog.
I dont want to kill it as it is not normal in my case. It has been lasting for more than an hour with high cpu usage.
I am using franco kernel 158 and Samsung GNexus ROM 4.0.4 IMM76K.
any help would be appreciated. Thanks.
Click to expand...
Click to collapse
McDull,
I'm not sure what you mean by you don't want to kill it. Regardless, you could kill the process (not via any task manager, since dubuggerd isn't an app to force-stop). If you do want to stop it you could manually one of a couple ways.
On the phone by hand:
I'm assuming you have root and su access.
From google-play download:
--- "Top" (by Junichi Uekawa).
--- "Android Terminal Emulator" by Jack Palevich.
Use Top to find out what the process id# for debuggerd is.
Open Terminal Emulator:
--- I can't remember if you need "su" powers, I always enter "su" mode tho.
--- Execute a kill of the pid: kill xxxxxx
Switch to Top, see if the debuggerd resets itself. Kill again if necessary
You can do all of the above via adb shell from your computer too.
Somewhat more automated:
From google-play download "SManager" (script manager) by devwom.
Write a shell kill script like in my first post.
Using smanager you can create a desktop icon that executes the kill command.
(I'm glossing over the details a lot because I'm at work and didn't have time to write in depth smanager instructions to do this. sorry!!)
I know my phone is deepsleeping, but for some reason, when i try to wake it, it would take up to a minute for any response, on top of that I found that android OS is using about 40% of my battery, used Android tuner( the one that requires xposed framework) to see, and it turns out that the battery drain was caused by the android os, "sh" thread.
Any ideas to fix this?
MinChains said:
I know my phone is deepsleeping, but for some reason, when i try to wake it, it would take up to a minute for any response, on top of that I found that android OS is using about 40% of my battery, used Android tuner( the one that requires xposed framework) to see, and it turns out that the battery drain was caused by the android os, "sh" thread.
Any ideas to fix this?
Click to expand...
Click to collapse
"sh" = shell
It seems that something installed on the phone is starting shell (it's a text terminal) in a background and not stopping it. It may be a broken script installed in /etc/init.d or some app that is broken. The worst case scenario is a malicious program that resides in background to do something (not very probable). It will be hard to find the cause as "sh" is a part of the system - please try to correlate the beginning of the problem to installation of some program. Try to use Teminal Emulator and issue the command "su", press enter, write "top -n 3" and enter, to list all tasks running in the system. Scroll up to check column headers, find CPU% and by that locate this rouge "sh" process. Look in column UID to find who has started it (user id). Post your search result.
Found it pid 32444 bu doesnt really help as i can lt find it activitymanager.runningappprocessinfo
Any idea what this is?
32444 2 24% R 1 896K 428K root /system/bin/sh
Rebooted, pid changed to 4790
Update:
After i killed this prpcess, swapoff takes over and causes an i/o storm for abour 2 mins then system ui and surfaceflinger uses about 30% and 20% cpu respectively it doesnt go down even after 5 hours.
Using agni kernel for 4.3 btw patched to fix network error
What cpu governor are You using?
Try to set ondemand.
Sent from galaxy n7105
My setup is a Oneplus 3 with OOs 5.0.1 with TWRP, Magisk and Franco Kernel. Naptime and Servicely are two other installed apps that interferes with the normal system behaviour.
My phone randomly reboots two to four times a day, whenever that happens sometimes the booting completes (with longer than usual times), other times it stay stuck at the boot animation and I have to manually shut it down and power it on repeating the whole process till I get a successful boot.
Some suggested to look at the logcat but from my understanding using a logcat viewer, the log starts from the boot so I can't tell what happened before the reboot.
Before proceeding with a trial and error approach by removing everything (the kernel, apps and magisk) is there a smarter and more efficient way to tackle down what's happening?
I will try to use a terminal emulator app to run in background 'logcat -f myfile.txt' but since I down know when the next reboot will happen the file might get HUGE.