Develop Bugs

[Q] G2 Camera Shutter Sound

As of right now, is there no way to disable the camera sound?
Does Temp Rooting -> Replacing shutter sounds with a 0kb file work on the g2, or does that revert after a reboot?

What about the old blackberry trick?
Lower volume, call voicemail, take a quick pic. I havnt tryed it, but that was the ez'est thing to do on my curve.
I'm wondering if xda is like other forums, getting a bunch of heat, people thinking you are taking up skirt pics or something. So retarded hahah

lol.
if you mute the phone, the sound goes away... but thats just retarded to do it for each time you want to take a picture
and no, its just an obnoxious sound, how am i supposed to take pictures without annoying everyone around me..

You use the camera so much that turning your phone to silent beore snapping a pic is a pain for you?

aedv said:
You use the camera so much that turning your phone to silent beore snapping a pic is a pain for you?
Click to expand...
Click to collapse
yes.
its sorta like.. why bother getting a remote fob for your car when you can just walk up and use your key to open the door....
its convenient, and something nice to have... and additionally, when its been hacked into the camera app a 1000x on windows mobile phones, android phones, and blackberries, don't you think people consider it a nice thing to have?
or are you so stuck up about it that you get up to change the channels by hand on your tv, because a remote is only going to save you 5 seconds anyways
god i hate people who just make assumptions like that

I must agree ... I too am looking for a fix for this.. not only can you not turn off the sound..that annoys me its also the fact that the g2 takes beautiful pictures withva super cheap sounding ear screaching click! Its not even a click more like a cliche type of sound it sucks definetly trying to find a way to shut it off without muting the entire phone everytime
Sent from my T-Mobile G2 using XDA App

no one has a fix for this yet?
no one ever anwsered my question if temp root will solve this problem permantly

I use tasker for this. Mutes phone sound when camera is launched. Works fine
Sent from my T-Mobile G2 using XDA App

Look for camera shutter in market, they have alternative cam apps that silent the shutter sound
Sent from my T-Mobile G2

Nearly every camera app in the market was crap or you had to pay. Id like to see devs come out with something for rooted devices.
Sent from my T-Mobile G2 using XDA App

Try this, it works for me from adb, but visionary.sh would be fine too:
su
mount -o remount,rw /dev/block/mmcblk0p25 /system
rm /system/media/audio/ui/camera_click.ogg
launch camera app, and .. wah-la!
edit: it obv reverts, but visionary.sh solves that

Why not just put the phone on vibrate when taking a pic? Works for me.

AreOh said:
Why not just put the phone on vibrate when taking a pic? Works for me.
Click to expand...
Click to collapse
Because that can get annoying.
Just put it in visionary.sh and never worry about it again, if you want the sound gone every time.

settings profiles the newest version can disable system sounds only ie:camera

^ can you elaborate on this? wat do u mean profiles?

Download the app "setting profiles" from the app store. The free one allows for one rule. Use thst rule to set just the system sounds to be whatever level or quiet dependant on certain conditions. The conditions can be set to something that is always true.

[TUT][S-OFF]Fix Dialer issue on 2.3.3/2.3.5

Not sure if anyone found a fix, but someone on the Google Code forum has found a solution. I am NOT taking credit for his fix, simply getting it out there as it is a huge issue.
1) Open up the .zip for your custom or stock Rom and look in the /system folder for a file called "build.prob". Copy this to your Desktop as you will be editing the file and then replacing the original on the Rom.
2) Open Notepad++ or any text editor of your choice and open the file. You are going to want to search for a line that says:
# try to disable proximity sensor in call by default
gsm.proximity.enable=false
Uncomment that line and make it equal to false.
3) Next, copy it back onto the /system directory of the Rom and then flash it. If it doesn't work for you, I am sorry. This is what worked for me so I just wanted to get another solution out there.
Again, I did not make this solution! I found it on Google Code forums.
Enjoy!

What problem does this fix ?

After making a phone call, there should be a process called Dialer. It gradually increases over time to 99% and kills the battery
Sent from my HTC Wildfire S A510e using XDA App

Small correction
Hey, small correction to your above post, hopefully this helps somebody out there
The file is actually build.prop
And the original commented line looks like the below WITH the hash in front
# try to disable proximity sensor in call by default
#gsm.proximity.enable=false
Instead of reflashing the ROM I booted the phone into recovery, then did
adb shell
adb mount /system
exited the adb shell, then
adb pull /system/build.prop c:\temp
edit c:\temp\build.prop, removed the comment hash
adb push c:\temp\build.prop /system/build.prop
rebooted, made a call, watching the battery usage, and dialer isn't at 98% after 30 minutes, in fact, it hasn't even shown its ugly face!
Awesome, thanks for that find!

Ah. Been reading posts all over and they all say to remove the hash tag. I'll give this a try later. You can for sure tell its not showing up after a reboot, power off, etc.? This really is an frustrating bug we have on our hands and I for one hate having a phone that lasts ~5 on a ful charge.
Sent from my HTC Wildfire S A510e using XDA App

Quick question. Dialer is already in my processes running. Will it still work or do I need to clear it first, cause I have no idea how to do that lol.
Sent from my HTC Wildfire S A510e using XDA App

Need your help. I'm trying to run these commands, but they aren't working for me. When I go to type adb shell mount /system, it keeps saying adb: not found. Any help with this? I used to be able to do this, but it's not letting me do it

Please clarify one thing for me...
I don't know for sure but this seems to disable the phone's proximity sensor during calls, so the screen will be always on while calls are being made (until the screen timeout activates).
Am I right? If so this fixes one bug and creates another problem.
I would be glad if someone that already tried this can confirm what I'm thinking.
Thanks a lot in advance.

Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)

aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
But it seemed to work for me. I did it and rebooted my phone and the Dialer process was gone. I then made a test call and while the call was on, the Dialer process was not there. Then, I kept checking and it still did not appear. I also applied the best battey tip you'll ever need.

aigaming said:
Confirmed,i used this long time ago and the display stayed on for whole time during call and also proximity was disabled for screen auto brightnes(probably more apps)
Click to expand...
Click to collapse
aigaming, thanks a lot for confirming what I already suspected.
This is a "fix" that creates an even bigger problem.
Last week I had a phone call with an Engineer that lasted more than 80 minutes.
If the screen was on during this period then instead of the Dialer draining the battery I would have the LCD draining the battery.
I don't need the proximity sensor for auto-brightness for example (like to set it on my own) but it shouldn't be turned off because it's probably necessary for the camera application (for example).
This Dialer battery drain is just a cosmetic bug IMO.
If we want to know what really eats our batteries then we should use *#*#4636#*#*, usage statistics instead.
There is info in miliseconds of usage by each app.

And what about fix for S-ON phones?

shaarky said:
And what about fix for S-ON phones?
Click to expand...
Click to collapse
If you edit the file, replace it on the ROM and flash it, then this method works on s-on phones. Be warned that the screen will remain on during calls.

miguelca said:
I guess that's off-topic here. This thread is about another problem.
Click to expand...
Click to collapse
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...

I also interested in fix for battery drain on s-on phones. Mine adb says permission denied.=(

shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
The method drzerog uses is for s-off phones. The method on the first post works with all, s-on included.
Sent from my HTC Wildfire S A510e using XDA App

shaarky said:
Well, I mean if there is some way to apply this on S-ON phone.I think it's not, so better to update name of the thread...
Click to expand...
Click to collapse
I updated my posts. Sorry for the mistakes but now info is correct. Please read again. Thanks.
Sent from my HTC Wildfire S A510e using XDA App

I can also confirm that, for me, during a call it does NOT leave the screen on. It turns it off on my device. Maybe it's different for each phone? But that can't be. Weird. Again, confirming it works on my device and my battery is now showing proper statistics, as well as Dialer process not appearing

Also wanted to make note that I have changed the topic title and noticed this thread is now in the rom/recovery/guides/kernal/root stickie!! VERY COOL!

Not work for my WS rom 2.3.5 stock/ S-OFF, the dialer process still keep 92%

Phone not playing sounds

Was trying to kill the sounds from the camera and came across a thread that said to copy volume.db to system\etc and in terminal emulator type kill all mediaserver
since i did that, i have no sound at all, phone doesn't ring and doesn't play media
how do i undo that command?

sinfony78 said:
Was trying to kill the sounds from the camera and came across a thread that said to copy volume.db to system\etc and in terminal emulator type kill all mediaserver
since i did that, i have no sound at all, phone doesn't ring and doesn't play media
how do i undo that command?
Click to expand...
Click to collapse
When you reboot, media server should be initialized again and everything should be fine again.

rebooting does not work, tried it several times
seems like everything is turned off, including vibrate...any other ideas?
i'm stock, but rooted

perhaps delete volume.db and then restart.
Or type mediaserver into terminal emulator
Worst case: titanium backup and then odin.

i think it's the phone...odin'd back to stock and still no sounds or vibrate
how annoying
taking to sprint store...thanks for trying to help

Try deleting.the db file to where u copied it to. then reboot phone and see what happens. if it doesnt work, reodin an check box reparttion, then try
Sent from my SPH-D700 using xda premium

LORDFIRE00 said:
Try deleting.the db file to where u copied it to. then reboot phone and see what happens. if it doesnt work, reodin an check box reparttion, then try
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
volume.db has since been deleted, in fact there never was one in that location, so there's no backup
reodin'd with repartition checked and still no good.
it's weird cause both the speaker and vibration is not working...how does a hardware issue break both at the same time? and why doesn't an odin work either

Can u send me the link to that thread about moving the db file please? i want to read the instruction...in every instruction there is a revert method... sometimes its just hard to notice it.
Sent from my SPH-D700 using xda premium

i found the link through google, and looking at it now, it is instructions for the s3 - http://forum.xda-developers.com/showthread.php?t=1722136
hence no original volume.db in the location specified, so technically all i really did was a killall task
i think it is coincidence that sounds/vibrate went out the same day i did this. i got a free replacement from sprint

Put AFTV to sleep with a button combo?

Is it possible to somehow put the AFTV to sleep with a button combo on the remote?
I would like to be able to do it from within Kodi/XBMC, Netflix. Hulu, etc without having to go into the settings.

An existing button combo is not known. If you have a rooted aFTV you could try to use LLama with a shell command:
Code:
input keyevent KEYCODE_POWER

A PC Power/sleep button on a USB keyboard, like the one on the Logitech K400, also works. You can also do it with a FLIRC. There is no way to do it with the standard remote.

AFTVnews.com said:
A PC Power/sleep button on a USB keyboard, like the one on the Logitech K400, also works. You can also do it with a FLIRC. There is no way to do it with the standard remote.
Click to expand...
Click to collapse
I have a similar question. I'm rooted. Is there a way to kill SPMC when it hangs vs going into managed installed apps find spmc and force stop? Something like longpress pause should help immensely.

navigates said:
I have a similar question. I'm rooted. Is there a way to kill SPMC when it hangs vs going into managed installed apps find spmc and force stop? Something like longpress pause should help immensely.
Click to expand...
Click to collapse
No, there's no way. You're only other option would be a full system restart by holding Select and Play.

AFTVnews.com said:
No, there's no way. You're only other option would be a full system restart by holding Select and Play.
Click to expand...
Click to collapse
That is surely another option but that is a trade off. Wait for the whole boot or navigate down. thanks aftvnews

Calibaan said:
An existing button combo is not known. If you have a rooted aFTV you could try to use LLama with a shell command:
Code:
input keyevent KEYCODE_POWER
Click to expand...
Click to collapse
Nice. Wish some one would make a FTV/FTVS app that can be trigger from the Recent/FiredTV/Kodi Apps to turn the screen off... That would help things...

Y314K said:
Nice. Wish some one would make a FTV/FTVS app that can be trigger from the Recent/FiredTV/Kodi Apps to turn the screen off... That would help things...
Click to expand...
Click to collapse
I did try this with ShellExecute and also with sending a KeyEvent programmatically from an app. It seems that this still needs root to be done. The only way I know it can be executed without root is via ADB.

Calibaan said:
I did try this with ShellExecute and also with sending a KeyEvent programmatically from an app. It seems that this still needs root to be done. The only way I know it can be executed without root is via ADB.
Click to expand...
Click to collapse
Guess there might be a different code that the keyboards power button use like on the K400...

No, the K400 does use exactly this KEYCODE_POWER code
The problem is that it seems that a default app isn´t allowed to shellexecute the /system/bin/input binary. Same problem for SendKey events. External ADB access seems to have more system rights.
Since I´m not an Android nor Java coder perhaps a more experienced app coder could tell details about this.

Calibaan said:
No, the K400 does use exactly this KEYCODE_POWER code
The problem is that it seems that a default app isn´t allowed to shellexecute the /system/bin/input binary. Same problem for SendKey events. External ADB access seems to have more system rights.
Since I´m not an Android nor Java coder perhaps a more experienced app coder could tell details about this.
Click to expand...
Click to collapse
yeah KEYCODE_POWER is exactly the same as the old (not-quite-deprecated) keyevent 26. and as people have mentioned, it's what the power/sleep/crescent-moon key on your keyboard is doing.
yep - adb shell input keyevent 26 'sleeps' the KFTV immediately (but remember, childrens of the world, KFTV NEVER SLEEPS. it is a lie. although if it makes your TV happier, cool.)
and you're right, the adb shell has a bit more rights than e.g. if you get an internal shell (from, say, terminal emulator) it is weaker. and probably also right, apps have diminished privileges too.
however... ok, this is an extremely stupid trick I came up with a while ago...
it's still possible to get an adb shell from a lesser shell (e.g. if you come in using sshdroid, or are typing on the terminal emulator app, etc.) - check out:
http://forum.xda-developers.com/showthread.php?t=2715315
sadly I was never able to find out a programmatic way to perform the above, so it's not terribly useful.

There are two ideas beside the keyevent I did not try.
1.) It is possible to switch manually "off" from menu Settings > System > Sleep. Maybe an app could set an intent action to this menu call.
2.) Probably an app could use the Android power manager in a way to change the system power state to force sleep: http://developer.android.com/reference/android/os/PowerManager.html

weird echo on receivers end only, both cell and voip calls but not skype

ive had this echo for a while now and not sure what can fix it. i just wanted to see if theres a better way i can troubleshoot to get to the root issue. ive used other apps with this phone like skype, etc and the echo doesnt seem to occur, only on calls using cellular or voip. its done it on the stock rom and lineage/carbonrom.. the only thing workaround is when i plug in my headphones. seeing if anyone has a solution or something else i can try.

shatheone said:
ive had this echo for a while now and not sure what can fix it. i just wanted to see if theres a better way i can troubleshoot to get to the root issue. ive used other apps with this phone like skype, etc and the echo doesnt seem to occur, only on calls using cellular or voip. its done it on the stock rom and lineage/carbonrom.. the only thing workaround is when i plug in my headphones. seeing if anyone has a solution or something else i can try.
Click to expand...
Click to collapse
Some phones have multiple microphones and use one for echo cancelling in calls. I've had to tinker with it on other phones, but I don't know for certain if the i747 actually has that or not. The fact that it is happening on both stock and custom roms makes me lean towards it being some kind of hardware issue.
There are some echo cancelling options you can change in /system/build.prop. I think they all have the word fluence somewhere in their line. You might try tweaking some of those lines, rebooting, and seeing if you can get an improvement out if it.
As with any build.prop edit, make sure you have a backup, and make sure the permissions are set right when you're done. It is easy to soft brick if you end up with the permissions set wrong or make a change the phone doesn't like, but it is easy to recover from with a TWRP /system backup or by dirty flashing your rom again.

jason2678 said:
Some phones have multiple microphones and use one for echo cancelling in calls. I've had to tinker with it on other phones, but I don't know for certain if the i747 actually has that or not. The fact that it is happening on both stock and custom roms makes me lean towards it being some kind of hardware issue.
There are some echo cancelling options you can change in /system/build.prop. I think they all have the word fluence somewhere in their line. You might try tweaking some of those lines, rebooting, and seeing if you can get an improvement out if it.
As with any build.prop edit, make sure you have a backup, and make sure the permissions are set right when you're done. It is easy to soft brick if you end up with the permissions set wrong or make a change the phone doesn't like, but it is easy to recover from with a TWRP /system backup or by dirty flashing your rom again.
Click to expand...
Click to collapse
well the phone definitely has noise cancellation, says it on the specs sheet and manual. i will look in build.prop and see what i can come up with.

shatheone said:
well the phone definitely has noise cancellation, says it on the specs sheet and manual. i will look in build.prop and see what i can come up with.
Click to expand...
Click to collapse
Maybe look around for the microphone holes and make sure they aren't plugged up solid with pocket lint or something too. I meant to look mine over last night, but I didn't get around to it.