Hey so my speaker phone is always on whenever I make or receive a call. I've gone through every single setting, made sure no apps are installed making it default to be on (voice recorders, GPS apps, ect) yet it is always on?
Anyone know how to fix this? Is there some app that I can install that can force it stay off unless I turn it on?
Some people say its the phone thinking its in dock mode. Is there any way to disable that?
This is driving me nuts. I've tried pulling the battery, rebooting and nothing is working.
Thanks for the help!
Is there some app that I can install that can force it stay off unless I turn it on?
Click to expand...
Click to collapse
You shouldn't need an app to do what the phone already natively "normally" does. More than likely, some app you installed is causing your problem. Even if you disable apps to not have speaker on by default, perhaps the app cache settings are still affecting your phone.
If you're still agonizing over this problem by the time you read this... I would clear all the app cache, clear data on each installed app, disable all installed apps (force stop), and if that doesn't work, back up your data and factory reset. More than likely a factory reset will get your phone working correctly again. A pain, I know, but... better than going nuts! Good luck!
Yeah I've gone through every conceivable app that would have anything to do with my speakerphone and it hasn't helped. I'm afraid to do a factory reset because I honestly don't think it is going to fix it. I'm starting to think more and more that it is a hardware issue with the USB port and not a software issue. I may have to go to a Verizon store and see what they say. I'm sure once the guy can't figure it out he will tell me that I have to factory reset it at which point I want to make say if it doesn't fix it, I'll need a new phone.
So annoyed it's not even funny.....
UPDATE:
Ok so I still can't figure out what it is, I've cleared all data and cache on all apps (including the phone app) but nothing seems to help.
For ****s and grins I wanted to see if I plugged in my headphones what it would do. When I plugged them in and tried to make a call, this time the speakerphone button is NOT illuminated BUT.........IT STILL PLAYS THROUGH THE SPEAKER PHONE AND NOT THE HEADPHONES????
I know, mind...blown.
Now if I push the speakerphone button, it turns green (on) and the sound still comes through the speaker phone but if I push it again, it turns off and now the sound plays through the headsets.
What on earth is possibly going on??? Can the phone dialer app be corrupted? What else can I try other than a hard reset? Is there a way I can reinstall the phone dialer app?
I know you stated you looked at all the apps you could, but did you look into the S Voice settings to see if Auto start Speakerphone is enabled? Supposedly it'll be used only when S Voice is used, but who knows when something might be corrupted.
Already tried that, didn't fix it. Even tried disabling Svoice.
I also booted up in safe mode and it still was doing it so I know it isn't any installed app that I have that is doing it.
At this point I think have no choice but to do a hard reset unfortunately. SO incredibly annoying.
Well, I hope you solve the problem. At least with the hard reset you'll get a clean start. Nah... nothing good about a hard reset! Damn annoying! Let us know how you solved it once you get it going.
Related
Ok so i did some searching and really didnt find an answer. With in the past few weeks my music will play fine on my way to work.. but on my way back it will pause everytime i open an app or do an action. I.e open settings, open dolphin browser, press home, open my txt msgs. Literally i cant do anything with out the music stopping. If i reboot it works fine again till the next morning when im on my way to work a d i have to reboot again. I have no idea why this is happening or how to fix it.
Im running task650 aokp4.1.2 with stock kernel
Power amp.
Monster turbine headphones.
Im not running any sound hacks or anything like that, and its getting kind of annoying. Any ideas???
No one??? I tried turning off start and stop when plugging in the head phones, also tried clearing data on power amp... only thing u can think of next us clearing cahce and dalvik... any one have any other ideas??
Bumped from the dead... so i wiped dalvik and cache stil same issue. Reinstalled the latest version of my rom, nothing. But i noticed that if i leave my phone on vibrate it doesnt do it. Its weird, when i put my ringer on by the end of the day i need to reboot. Putting it back to vibrate doesnt fix it. Any ideas wth is going on??
iLLdWes said:
Bumped from the dead... so i wiped dalvik and cache stil same issue. Reinstalled the latest version of my rom, nothing. But i noticed that if i leave my phone on vibrate it doesnt do it. Its weird, when i put my ringer on by the end of the day i need to reboot. Putting it back to vibrate doesnt fix it. Any ideas wth is going on??
Click to expand...
Click to collapse
Kinda weird for it to do that o.0 I'm on MA6 using power amp and i've never had that happening to me.
does your rom have ' Kill all processes on close / Don't keep activities ' under the dev options checked?
Do you have any task killers that shut poweramp or the poweramp service?
Do you have keep service checked marked under the poweramps Misc > Tweaks?
Try uncheckmarking the first option i suggested ( If it is even check marked )
and then check the second option.
it just seems like poweramp doesnt keep it's service running or it turns off when you're running
a ton of background apps reaching the background app limit.
This is my suggestion, I don't have any others.
Alright I have a problem with my N7.
Putting it here since more people see this thread
So I guess my N7 restarted sometime at night and when I turned it on, I noticed that first my password lock wasnt there, nor was there a lockscreen.
Then a notification came up saying:
"Unfortunately, Google partner setup has stopped.
My notification bar, wifi, and home buttons dont work. I can force stop apps in the settings, but anytime i click clear cache it reboots.
I tried to do a factory reset and when I enter my password lock and click ok, then settings force closes. I'm not sure what to do.
I forced stopped google partner setup and gallery, those two popups came when the N7 would turn on that it wouldnt work. Now they dont come up anymore but that didnt solve anything.
Any help??
I am stock and unrooted btw. The night before this happened all I did was watch netflix
some other things to add, if i uninstall an app, it reboots and the app wont uninstall.
The notification bar actually comes down, its the other one with the toggles that doesnt.
well I was able to get into recovery mode and do a factory reset that way. Didn't know that was possible without root haha. Everything seems to be ok for now...
tankmaster90 said:
well I was able to get into recovery mode and do a factory reset that way. Didn't know that was possible without root haha. Everything seems to be ok for now...
Click to expand...
Click to collapse
When stuff like that happens I get paranoid my nand or ROM is bad and do all sorts of tests lol.
I'm glad to hear that all is well again. Now root that puppy put twrp on it, make a backup and flash a good ROM lol.
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Eutility said:
Can you tell me if bluetooth is ON or OFF by default at startup after a factory reset? I swear that it was off the first time I booted up but now it is on. Makes me wonder if it was infected or changed. Anyone know if the default was changed? Thanks
Click to expand...
Click to collapse
Bluetooth may or may not be "on" but it should not be "connected" or "remember" any devices if you did a factory reset.
However, without wiping internal SD and data, you are subject to "potential weird things" that can happen.
It's why I never report a bug unless I made absolutely sure to wipe data and internal SD before trying to reproduce an issue.
Bluetooth has been turned on by default for all the software versions I've used.
Upon a factory flash or reset, Bluetooth will be enabled but no devices will connect/be remembered.
On a side note, No application can "infect" an android. Most of these antivirus applications are complete bullcrap. Dont get me wrong, there are some dangerous apps out there, but you would still have to give the app permissions and accessibility access For it to do any damage. even then, simply uninstalling them Will remove everything.
Thanks for your responses. I do appreciate it. Well, unfortunately I have had multiple phones infected by ex-neighbors. I literally would lose control over the phone and during calls they would make beeping sounds like I had hit a key. Once I flashed my phone outside of town and they kept messing with it. I had always thought they had a tool which enables persistence even through flashing, but it may be that they are using Signaling System 7 (SS7) and are just reinfecting them remotely. (you can watch a 60 minute special on SS7 if u like, available online) They were using an IMSI catcher when I lived next door to them. With the Pixel XL I was having ALOT of data use and reset the phone after some weird stuff happened that I had come to recognize as likely signs of being compromised, and I think put in a new SIM with a new phone #. It was much better after that. It was a nightmare with them and one of them even followed me home after work a month after I moved away. Not to mention steal things like laundry soap and put them on their side of the street in front of my house. Creeps. At this point it is just pathetic and weird. Just trying to take reasonable precautions now and live my life. If they want to waste their time that is sad.
Really glad to hear the bluetooth being there is not a deviance from default. Thanks
So this is driving me nuts. I just picked up an S7 Active, and restored my data from Samsung Cloud. Everything restored fine except for Settings. That part fails every time. No big deal, I thought. I just set it up again how I like it. As soon as I got everything how I wanted it, Do Not Disturb immediately started acting super-weird. It turns on by itself, and it takes 2-3 times of turning it off to get it to stay off. When I finally get it off, it resets the settings (stays custom, but turns off all alarms, calls, and messages). I want it to allow alarms and calls/messages from favorites, and as soon as I enable those, it automatically turns Do Not Disturb back on. Turning it off again starts the whole loop over. Clearly, my Do Not Disturb settings are corrupt. Is there a way to wipe those settings, without wiping the phone and starting fresh?
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Acinko said:
Not a super helpful response, sorry in advance, but i think you may have answered your own question. Sounds like something got corupt in the copy over.
With out manually looking at all of the settings and or alot of trial and error... you may just have to reset it and start fresh...
But when you say wiping the phone, i just want to confirm that your intentions arnt to go factory reset... just do a "reset settings" and "reset network settings" dont wipe your whole phone.
Click to expand...
Click to collapse
Yes, factory reset, or worst case, ODIN flash the firmware. I just wanted to see if it was something anyone else had run into. I'll tackle this over the weekend. Thanks for the response!
bug
I had turned facebook and gmail to silent notifications. DND has not turned on and media volume has not turned to zero since allowing these apps to show with sound again.
Think every time a notification comes in media volume is set to 0 and DND turned on.
My wife has a G7 Thinq that has been having this problem for a while now. She gets the debris/moisture error when the phone has had no exposure to water at all. There is nothing in the port at all. No amount of drying/cleaning makes any difference. When the error occurs, she gets frequent notifications and can only charge the phone wirelessly. The only fix is to factory reset the phone. Then, it's fine for a while (it was 2-3 months this last time), as long as she does not restart the phone. It often, but not always, recurs after a restart. Once the error occurs, it persists until a factory reset.
Because it goes away after a factory reset, I'm inclined to think it's a software issue, but I've had no luck in identifying an app responsible for it. Has anyone else seen this behavior, or know how to solve it? It has the stock ROM on it, and I've wondered if a custom ROM would fix the problem. However, she likes the stock ROM, so I'm not exactly eager to change that.
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
blackhawk said:
Try a hard reboot (not reset).
Clear system cache.
It could be an update causing it. Disable all auto updates. Try rolling the updated ones back to factory loads especially system apks.
Does it do it in safe mode? If so it's likely a system apk, firmware or a hardware failure.
Click to expand...
Click to collapse
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
drfarmkid said:
When I've done the factory reset before, I've just done it through the system settings menu and assumed that would also clear the cache. Is that not so?
When you say "hard reboot (not reset)", do you mean to do the factory reset with the hardware buttons, rather than through the settings menu? Does that do something different?
As for updates, auto updates are off. I'll try rolling back updates and see if that makes any difference.
I vaguely remember booting into safe mode back when this first manifested many months ago. I think the error was still there in safe mode, but it was so long ago I can't remember for sure. I'll check that, too.
Click to expand...
Click to collapse
If it didn't crop up right after the reload it indicates something that was added or a changed setting.
Clearing the system cache can only be done off the boot menu. This can cure many types of erratic behaviors.
For individual apks clearing their data can do the trick when clearing the cache doesn't.
A hard reboot simulates pulling the battery or pull the battery if it's removable.
I run many of my system apks as the factory loaded versions because of issues with their updated versions.
Next reload pay close attention to any updates.
If it's software caused it may prove a challenge to track down.
Could be an internal hardware failure. Try a known good cable and charger. Google the issue, others may have had the same problem and have a solution.
Clearing the cache, factory resetting the phone, etc. didn't work this time around. I was going to try putting a custom ROM on it, until I started looking into it and found out the bootloader can't be unlocked (it's the T-mobile version).
In the service menu (dial *#546368#*710#) there is a setting to shut off moisture detection. That also didn't fix it. However, I did find something in there that I don't understand that might be informative. My daughter has the same phone, so I looked through some things in there comparing the two. Under a menu called "Type-C checker" there is a table where the two phones differ. My wife's phone says:
Supported ModeUFP DFPMODEFAULTPOWER ROLEFAULTDATA ROLEFAULTVCONNN
My daughter's phone says "NONE" where my wife's says "FAULT". Does that mean anything?
I'm now suspecting some sort of hardware fault, perhaps a short in the charging port. I can buy that daughter board with the USB port for ~$15. What are the odds replacing that will fix it?
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
Hopefully it's a permanent change.
Androids wuv attention...
drfarmkid said:
Hmmm... That's interesting. After several days of the notification never going away, even after trying every fix for the problem, it went away on it's own about an hour after posting that last message. Out of curiosity, I looked in the service menu, and those three things that said "FAULT" now say "NONE", just like my daughter's phone without the problem. I have no idea what those things mean, but apparently it has something to do with the error. I don't know what fixed it either, but it wasn't anything I did.
Click to expand...
Click to collapse
hey, can you have found what was the issue because I have exactly same issue like your phone.