Touch sounds keep coming back!?! - Sprint Samsung Galaxy S III

Does anyone know how to keep this off? It keeps coming back on, I believe when i go from silent to volume again with the volume rocker. I'm not rooted and don't want to be.
posted from my GS3

monkeefied said:
Does anyone know how to keep this off? It keeps coming back on, I believe when i go from silent to volume again with the volume rocker. I'm not rooted and don't want to be.
posted from my GS3
Click to expand...
Click to collapse
Not sure being rooted or not has anything to do with it. Mine has done this once (rooted) and not sure why yet. After disabling it hasn't come back and done it yet.
When in sound settings screen does the option recheck itself when you toggle the volume rocker?
Also, how long has it been since you rebooted the device? Might try unchecking and then rebooting and see what happens. Just a thought.

Just stating the rooting thing in case someone had some funky way to fix it that required rooting. And yes the option re-checks itself every time.
posted from my GS3

monkeefied said:
Just stating the rooting thing in case someone had some funky way to fix it that required rooting. And yes the option re-checks itself every time.
posted from my GS3
Click to expand...
Click to collapse
Might read through this thread if you haven't seen it already: http://forums.androidcentral.com/sprint-galaxy-s-iii/204714-touch-sounds-turning-back-itself.html

So from that thread it seems there are 2 possible causes for this glitch:
-switching camera modes (unrooted)
-turning off camera snapshot noise (rooted)
I'm not rooted and have no option for turning off the snapshot noise, so i toggled my camera from vid to pic and it did immediately re-check the touch sound option but only the first time. For several tries after it didn't do it, only the first. I did change my camera mode earlier which if it is the cause of this glitch then that kind of proves it. I will be mindful of it if I change camera modes for verification, but It seems weird to me the camera is tied to the touch sound option.

I can confirm that the camera will cause this to happen when you switch between still to video mode. I know that I have seen (heard) it happen under other circumstances as well but I have not been able to pin it down.
I do not know of a solution for the unrooted phone. I am rooted so I went in and replaced the sound files with a silent file to permanently disable the sounds.

Please read forum rules before posting
Questions go in Q&A
Thread Moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Related

[Solved] Random Max In-Call Volume & Max In-Call Volume on each reboot

Whenever I make or receive a call, I see my in-call volume at maximum level! I don't understand why it keeps doing this? I noticed this problem on all 3 of note 2. I keep adjusting to low but randomly just gets reseted to max again. Anyone else having the same issue with T-Mobile Note 2?
Update: finally found the culprit of this problem. The app "Tango" video chat messes with the in-call volume. Once account & app was uninstalled even after the reboot in-call volume setting never changed. Everything stayed as I left it and no more random MAX in-call volume.
Video to show what Tango is doing to my in-call volume.
Nobody has this issue? how come all 3 of my Note 2 has this issue =/
Anyone?
Sorry, this doesn't help but I usually keep my in-call volume at max so I haven't noticed this.
amujee said:
Sorry, this doesn't help but I usually keep my in-call volume at max so I haven't noticed this.
Click to expand...
Click to collapse
Thanks for the reply. I don't know how you keep the volume at max.. maybe it's just my phones but it's too painfully loud for me.
Would you mind trying to lower the call volume to lowest setting and restart the phone? See if the call volume goes back to max, I would really appreciate that.
For whatever the reason, the volume setting is not getting saved. So annoying since everytime i answer a call, it's trying to blow my eardrums out!
I'm guessing nobody has this in-call volume issues on their T-mobile Note2? Should I be considering an exchange....??
Just FYI multiple post saying anyone? Anyone? Pple just find annoying. Not trying to be rude. But from what I noticed from posts from other forums. Is when pple do that. They will never receive help or a reply from someone. Especially when the OP keeps doing that all in the same day.
Sometimes if you want help. You need patience. Especially here on xda. Pple here don't live there lives to help you. Right when you make a new post. Sometimes it could take days or even a week or two. But I'm positive if you don't do multiple post like this. And wait or even search the web. Even user a different phone. You will find ur answer. Remember google is ur best friend.
Anyways I don't no if its because of my rom or not but mind keeps going to vibrate and I have to keep turning it back to sound + vibrate
Oh ya you also have to be detailed when asking questions. Are you rooted or not. Stock or flashed a rom. Which rom. ...you get the point. The more you tell use the more likely a chance someone will help you. If you choose not to look it up urself
My bad, wasn't trying to be annoying or anything. I searched around in many different forums but still no answers and didn't get any replies on this issue, even the t-mobile support didn't know what was causing this issue. I guess I was running thin on patience.
I'm running all on stock and all 3 devices does this. T-Mobile sales rep said maybe it's part of the feature.. But we all know that's b/s. Changing in-call volume randomly doesn't sound much like a great feature to me....
zen0s said:
My bad, wasn't trying to be annoying or anything. I searched around in many different forums but still no answers and didn't get any replies on this issue, even the t-mobile support didn't know what was causing this issue. I guess I was running thin on patience.
I'm running all on stock and all 3 devices does this. T-Mobile sales rep said maybe it's part of the feature.. But we all know that's b/s. Changing in-call volume randomly doesn't sound much like a great feature to me....
Click to expand...
Click to collapse
Ya unfortunately that sucks. If you were rooted I would say try to flash a different rom. But since ur not my best guess would be to search around for an app that has something to do with volume/ in call volume. There's an app for everything these days. Ur just gunna have to read all the details in every volume app you can find. I'm sure there's something. Good luck. If you happen to find something. Post it hear in case others run into the same problem as you in the future.
Am I the only one with this problem? I wish some of the same device/carrier users would give me some feedbacks so I can figure out what to do....
you talking about in call volume or ringer volume? if its in call volume im pretty sure that if i lower it during a phone call it stays that volume even on the next call
im not 100% sure though...and im not sure if it stands through a reboot but i am pretty sure...cause i dont leave my in call volume on max because it is quite loud and distorted...if it always went back up to max i probably wouldve noticed..again not 100% sure
jdiddy_ub said:
you talking about in call volume or ringer volume? if its in call volume im pretty sure that if i lower it during a phone call it stays that volume even on the next call
im not 100% sure though...and im not sure if it stands through a reboot but i am pretty sure...cause i dont leave my in call volume on max because it is quite loud and distorted...if it always went back up to max i probably wouldve noticed..again not 100% sure
Click to expand...
Click to collapse
It's the in-call volume. I have no idea what's causing this... When I lower the volume it will stay that way only for that call and next call or sometimes even during the call volume goes up to max randomly. It's driving me nuts cause it's so loud and I can't even answer the call without worrying its gonna blow my eardrums!
I tried restoring factory but that didn't help and all three of my Note 2 do this so I'm lost here. Not like I rooted and modified anything, all is in stock.
Would you mind trying to put in-call volume to lowest and rebooting the phone? See if it goes back to max by default. That's how mine is set to every reboot.
zen0s said:
It's the in-call volume. I have no idea what's causing this... When I lower the volume it will stay that way only for that call and next call or sometimes even during the call volume goes up to max randomly. It's driving me nuts cause it's so loud and I can't even answer the call without worrying its gonna blow my eardrums!
I tried restoring factory but that didn't help and all three of my Note 2 do this so I'm lost here. Not like I rooted and modified anything, all is in stock.
Click to expand...
Click to collapse
i just tested it...called myself...i put the volume to 50%...hung up..called myself back..volume was still at 50%...idk if it will randomly go up...we'll see lol
if it does..that would be an annoying bug...one i probably wouldnt have noticed if i didnt read this thread...so if i start noticing it i blame you!
jdiddy_ub said:
i just tested it...called myself...i put the volume to 50%...hung up..called myself back..volume was still at 50% so i dont have that issue
Click to expand...
Click to collapse
Try rebooting, see if that setting sticks.
It does this all randomly. Setting will stay that way for awhile and all of sudden max volume.
zen0s said:
Try rebooting, see if that setting sticks.
It does this all randomly. Setting will stay that way for awhile and all of sudden max volume.
Click to expand...
Click to collapse
yeah..volume went back to max after reboot
try this
go to dialer -> call settings -> my call sound...there are 2 options that might help you...one for sound settings (maybe choosing one of them will help you) or personalize call sound..that one asks you to plug in ear phones..im not sure what happens after you run that test and if it only applies to earphones but you can try it
jdiddy_ub said:
yeah..volume went back to max after reboot
Click to expand...
Click to collapse
Why would it do that... It's not suppose to. I never had that issue with ATT Note, N7000 and i9300... I get the feeling many people just don't pay too much attention to it and when it does go up, people just lower the volume and forget about it.
Whatever the reason setting of the in-call volume isn't being saved. And something is making it to go back to default. Just don't know what though...
Keep your eye on that volume, and check if it goes up randomly.
P.S. I really appreciate the replies, been waiting for awhile.
zen0s said:
Why would it do that... It's not suppose to. I never had that issue with ATT Note, N7000 and i9300... I get the feeling many people just don't pay too much attention to it and when it does go up, people just lower the volume and forget about it.
Whatever the reason setting of the in-call volume isn't being saved. And something is making it to go back to default. Just don't know what though...
Keep your eye on that volume, and check if it goes up randomly.
P.S. I really appreciate the replies, been waiting for awhile.
Click to expand...
Click to collapse
lol i saw...i figured i'd post since you have been asking and asking and asking...............
jdiddy_ub said:
lol i saw...i figured i'd post since you have been asking and asking and asking...............
Click to expand...
Click to collapse
Yeah, I really didn't want to annoy anyone but this little bug was driving me insane. Spending hours with T-Mobile tech supports weren't even helpful either. I hope it isn't a defective unit... Please let me know if you notice this issue! Thanks again =)
I think I found the culprit. Seems like "Jays headset control" app was causing this issue. It was never an issue on any other device but not sure why it's causing on note2. I uninstalled the app yesterday and so far problem hasn't come back yet. Time will tell but so far so good.
Thanks for looking and replying to my post. I can finally relax!
Update: wasn't jays app... Still having issue.
zen0s said:
I think I found the culprit. Seems like "Jays headset control" app was causing this issue. It was never an issue on any other device but not sure why it's causing on note2. I uninstalled the app yesterday and so far problem hasn't come back yet. Time will tell but so far so good.
Thanks for looking and replying to my post. I can finally relax!
Click to expand...
Click to collapse
i dont have that app so explain to me why its happening to me now?

[Q] touch key lights bug

hello everyone , so i use to have this bug back to kitkat also but it wasn't happening as often as it doesnt now that i have lollipop rom installed on my galaxy tab s T705 , the issue is with touch key lights which stays on even when i have them always off from settings , they act super weird when they are in that mode , they go off few sec after screen is off and if i shake the device they go on again as it looks like they are connected to accelerator sensor or something lolz ,the solution is super easy tho just hit the power saving on and then off again and they work normally again i heard some other ppl dealing with same issue but i wanted to know if there is a perma solution for it or not , im sure its a software issue but is there a way to fix it ?
Install a custom rom like cyanogen or something stock based.
I have the same problem. I usually have it set to turn the lights off after 6 seconds, but after a couple of days they don't work anymore. I would change the setting to off, then on, then back to 6 seconds, and it'll work again. After a few more days, they stop. I haven't seen a permanent fix for this.
Sent from my SAMSUNG-SM-G925A using Tapatalk
Same for me. Would usually opt to have the buttons backlight always off, but randomly it starts actin like always on, although the settings remains 'always off'. Toggling the setting to anything else and back to always off fixes the problem temporeraly.
Im running stock swiss lollipop on my t700.
Yes, this is driving me nuts too! I hope they resolve this in the next update and soon!
Sent from my SM-T700 using Tapatalk
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
Me too have the touch key settings to always off and found the same problem.
In my case I think it only happens when I plug the Tablet to AC.
Did this happen to anyone under another circumstances?
Thanks in adavance!
LakersDroid said:
Same problem with the lights on after a while even though set to always off. Seems to work properly under 1.5 sec setting option. I would love for the lights to be always off though.
Click to expand...
Click to collapse
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
TLAgnesB said:
I have the same problem as everyone else, which I am very "happy" to hear because I am not the only one apparently dealing with it. I purchased the tablet a couple weeks ago and noticed that even though the setting for the touch key backlight is "always off", it goes on when I open the case, and sometimes goes on and off and goes weird. I contacted Samsung and they requested that I send in the tablet for repairs, so I did. At the same time, I contacted Amazon and they sent me another Tab S tablet. I have a month to return the other one so I figured I'll try this second one and see if I continue to have the same issues like the first one. Sure enough, I had the second tablet for less than a day and it's doing the exact same thing! So far the 1.5 second setting seems to keep the darn lights off. Sometimes doing a soft reset will fix the issue temporarily, but not permanently. If anyone figures out how to fix this, let us know! I'll be following this thread. I hope there's a software update to fix this.
Click to expand...
Click to collapse
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
TLAgnesB said:
Is there a way to get it back to the stock ROM? I'd rather avoid this light issue until an update to correct this comes out. Thoughts?
Click to expand...
Click to collapse
Yes but you will need root.
LakersDroid said:
I believe this is a software bug so all tab s running the 5.0.2 lollipop will have this issue.
And to reply to the other poster: The problem will occur after a while, the lights will just turn on and stay on when you wake the tablet. Changing the setting and choose Always Off will fix it but it will come back after a while.
Click to expand...
Click to collapse
I heard that there's a new update available for the Tab S. (I already returned my tablet before my 30 days to get a full refund.) Did any one get the new update, and if so, did it fix the issues like this touch key light?
Hey,
I had this problem on the original KK software - upgraded to Lollipop a few days back and I still have the bug... in fact, it is even worse! Occurs more frequently than on LP.
I wouldn't mind leaving the lights on all the time, but they're so damn BRIGHT, and there's no way to adjust the backlight intensity!
Cheers,
Su
I found this solution on another forum...
If you enable smart stay, the touch key light duration will work properly.
Any further movement on this?. I've found that if I take my tab out of the book case the problem goes away. Seems like it's a bug with the case sensor.
No movement that I'm aware of. I'm really frustrated that there hasn't been a fix after all this time. I'm holding out hope that if there is ever an update to Marshmallow, that the issue will go away. Interesting observation about the case -I have a book case on mine. I'll remove it and see what happens...

Volume Control is bugging on my OP3

Hey guys,
atm I'm facing towards a problem like on the screenshots
<---https://goo.gl/photos/UQXesg48QwZLZTyy5--->
I'm not sure how this could happen but i think this is from an xposed module. Someone maybe know what i have to modify to put it right. Atm my minimum volume is 14%. Can't lower the volume from that point.
I tried formatting userdata, system or better said, I clean flashed my phone but this changed nothing actually.
Greetz
Diezano
Diezano said:
Hey guys,
atm I'm facing towards a problem like on the screenshots
<---https://goo.gl/photos/UQXesg48QwZLZTyy5--->
I'm not sure how this could happen but i think this is from an xposed module. Someone maybe know what i have to modify to put it right. Atm my minimum volume is 14%. Can't lower the volume from that point.
I tried formatting userdata, system or better said, I clean flashed my phone but this changed nothing actually.
Greetz
Diezano
Click to expand...
Click to collapse
If you're on Open Beta 8 it's a feature of the ROM. I'm not sure why its the case but many people are reporting this, only way to get to vibrate is silent mode.
yakob97 said:
If you're on Open Beta 8 it's a feature of the ROM. I'm not sure why its the case but many people are reporting this, only way to get to vibrate is silent mode.
Click to expand...
Click to collapse
You can be right, since I'm not sure when this issue started. At OOS3.2.7 i tuned my volume with some xposed modules and after that I flashed the CB3.5.5. Maybe its because I'm using the beta. Can you refer me some points where ppl reporting this? I haven't found anything yet on xda or on the oneplus forums. At the moment I'm using your suggested way for turning the phone into vibrate. Sometimes I want to silent my phone completely and have to go into settings to turn the lever to silent. In some cases really annoying.
kind regards
Diezi
Diezano said:
You can be right, since I'm not sure when this issue started. At OOS3.2.7 i tuned my volume with some xposed modules and after that I flashed the CB3.5.5. Maybe its because I'm using the beta. Can you refer me some points where ppl reporting this? I haven't found anything yet on xda or on the oneplus forums. At the moment I'm using your suggested way for turning the phone into vibrate. Sometimes I want to silent my phone completely and have to go into settings to turn the lever to silent. In some cases really annoying.
kind regards
Diezi
Click to expand...
Click to collapse
https://forums.oneplus.net/threads/oxygenos-open-beta-8-nougat-for-oneplus-3.476660/
It is quite annoying, happening to me too.

Proximity sensor issues?

Hey everyone. I'm enjoying this phone but I do have a few small issues which I'm hoping I can forget about once custom ROMs start to come out
(Come on and release factory images already Razer!!!)
One of them is the proximity sensor which I find incorrectly thinks I've taken my head away from the earpiece during a call and then starts spamming commands with my cheeks.
I have this issue on like every second phone call and it's a bit irritating. Especially when I still haven't received (other than the first one when I first got the phone) any more updates.
The other main gripe is the lack of a pocket sensor/script. Probably related. As in, if you have double tap to wake enabled, good luck putting this in an awkward pocket (inside motorbike jacket pocket) without waking the screen and spamming commands again with your fingers.
Lastly. I wish they had just put the fingerprint sensor somewhere else. I have turned the screen off so many times while watching YouTube it's actually starting to really annoy me
Just wondering, even if you like this phone overall, and I do, if anyone else had these gripes?
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Handaloo said:
I'm having the same issue with a Razer phone I picked up this week. It's a pain.
I've tried using this as advised on another thread and it seems to be working fine, so I'm totally lost.
https://play.google.com/store/apps/details?id=ru.andr7e.sensortest
Click to expand...
Click to collapse
I'm just glad to hear someone else is noticing this. Does nobody else make phone calls on their phones??
Had the issue with the proximity sensor on a phone call again last night. Realllly annoying.
At least factory images are out now, unfortunately, it took so long, developers etc don't look too bothered about this device - I may be wrong and would be delighted to start seeing some custom stuff out there. So long as they can keep the 120Hz functionality!
Yeah I would definitely be tempted if a good Rom was released. You're probably right about it though, not a HUGE demand for these.
I've had it several times with calls and it will be super annoying if it doesn't get fixed with an update soon. I'll give you a shout if I get anywhere with it outside of this thread.
EDIT:
And yet, I just took two calls this morning back to back with ZERO issues.
anyone any more luck on this?
nk33 said:
anyone any more luck on this?
Click to expand...
Click to collapse
Nope. I still get these issues from time to time.
I even switched to global ROM and they exist there too.
Hi all.
This issue was resolved on my phone with a hard reset (volume up + power button), then a factory reset (in settings -> system -> reset options ). The proximity sensor now works as it is supposed to.
Hope this helps.

Question OnePlus 11 not ringing when receiving phone calls?

I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2451 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Edited: Fat fingered the model #. Fixed.
simplicityy said:
I am not entirely sure if I'm tripping, but I seem to be missing phone calls pretty damn often. I think I recall at one point I randomly grabbed my phone to have it by me and noticed that someone was calling me but it wasn't ringing at all, though the screen did light up. I made sure my settings do have have "Do Not Disturb" mode on. I have the CPH2541 and running stock with latest OTA A.10 update. After doing a brief Google search, I see that OnePlus has had issues in the past but those are from the OnePlus3 and OnePlusNord so I am not sure if that's still relevant in this day and age.
Anyone experiencing something similar or have any clues as to what might be going on?
Click to expand...
Click to collapse
This might be obvious to you, so just ignore if you know this.
When holding your phone in your hand like you're texting in portrait mode, there's a switch top right and on side of phone.
Adjust the switch so it's down.
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
kevp75 said:
Ive experienced this, even after swapping to 2449.
Seems theres a couple settings that revert on reboots for some odd reason.
Just go into the phone app settings, notifications and reset thr ring tone and all set after 2 times doing it ... annoying?? damn right!... but at least its fixable ....
Click to expand...
Click to collapse
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
simplicityy said:
That's so dumb... The more I use this phone, the more I get buyer's remorse.
I haven't restarted my phone since I got it I think but I'll try that and see if the issue persists. Thanks!
Edit: Any word if OnePlus is aware of this and plans on fixing it? If not, perhaps I should forward this to them.
Click to expand...
Click to collapse
don't know if they are aware. just to add to the weirdness of it... for me... after the second time, the setting sticks...
i have this problem with my 8 pro, the phone doesn't ring and i think it goes straight to VM? seems like something broke with one of the latest OP updates?
There's no such version as CPH2541.
And here it works perfectly. Factory reset and try again.

Categories

Resources