First time poster, all, so be please be gentle!
I've got a problem that I've not seen anyone else ask about or reference. For some time now, my Captivate has not been ringing when I receive a regular phone call. However, it does: play media files with sounds as normal; play notification sounds; play game sounds; alarm sounds when the alarm goes off. In fact, the only sound-type application it has any problem with is ringing on an incoming call.
I'm not a complete noob, so please assume that I've checked all the usual suspects (silent mode, vibrate mode, using stock ringtone vs. custom, physical volume up/down buttons, rebooting, etc.) However, if you know of a more esoteric setting that could be missed, I'm dying to hear about it.
I'm running Cognition 2.3b1 or 2.3b2 at the moment, but I'm going to go out on a limb here and say that this problem began before upgrading, although I've been using Cognition before the Froyo update; I really don't think it's an issue with Cog, especially as I haven't seen anyone complain of the same symptom.
Is there perhaps some system level directive along the lines of incoming_call_ring=NEVER that I've somehow, someway triggered and just don't know how to undo?
Anyway, thanks in advance for any help! I enjoy these forums and the sense of community, even though I generally just lurk
If it really has been going on since before you flashed I think you know the answer to your question
Sorry to hear that.
Have you tried master clear? If it persists then flash to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
I haven't tried master clear yet, good suggestion. By this weekend I should probably be at just the right ratio of desperation vs time to give that a try. I'll post back here after.
Not just me!
It would seem that this is affecting a small number of Captivate owners. The solution was suprisingly simple and effective: push in the 'speaker' with your thumb. Guess the speaker isn't locked in as tightly as it should be, or is prone to short-circuiting. Haven't had any more problems since pushing it in, go figure!
Anyway, see this thread for more details:
hxxp://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Sound-not-working-over-loud-speaker/td-p/1996034
Related
Hello XDA Members,
I have an odd issue on my hands.
Description:
I get a call, from either a landline or cellphone, the ringtone plays just fine. After I end the call, the ringtone then plays again on its own. There is no way to silence it or get rid of it. The phone is fully responsive, I can open apps, and use it normally aside from my ringtone playing in the background until it reaches the end of the song.
My question to you guys, has anyone ever experienced this, and if so how did you resolve it?
NOTES:
Running stock AT&T ROM with the latest update and Voodoo lagfix. Never flashed any other ROM's.
My wife is using the impression and sometimes her text message notification does the same thing, plays after reading text restart fixes for a while but it always comes back, I havent seen this on my captivate or read of it happening to any others. maybe a master clear?
I too have had it happen with text message notifications, I am using Handcent.
I'm thinking a master clear may resolve the issue because it seems software related, but I was hoping to do it without clearing things out. I was thinking some app, out of the hundred or so installed may have something to do with it.
If doing a master clear is the only resolution, I might as well just flash a new ROM, I already have everything I possibly could back up all backed up.
I have resolved this issue without a factory reset or flashing another ROM.
I was playing around with where the ringtone MP3 file was located and I had moved it into the phones internal storage. I moved it back out onto the root of the SD card and all seems to be ok. I cannot believe I didn't think to remove or move the file that was getting played after a call.
Just after I power on my phone it makes a loud, annoying noise like: "beep-beep beep-beep beep-beep beep-beep"
It started when I set a custom ringtone and notification sound.
The only cause I can think of is that maybe the phone is trying to play my custom sounds files before they have been scanned by the media scanner, which is resulting in a system notification sound being played instead.
Is that likely to be the case?
My custom sounds are stored in: /mnt/sdcard/media/audio/notifications and /mnt/sdcard/media/audio/ringtones
Thanks.
Delete or move your custom sounds to test your theory .
No mention of firmware .
jje
Sorry, I was sort of seeing if anyone had a similar problem first. Anyway:
Firmware: 2.2.1
Baseband: I9000XXJPY
Build: FROYO.XXJPY
(Not rooted)
I think I am meant to get Gingerbread any day now, and I plan to root after that - so maybe one of those will fix it.
I think I am meant to get Gingerbread any day now,
Dusty Springfield .
Wishing and a Hoping .
What I noticed on mine is this only happens when there is a voice mail left when phone was off. I get this annoying, almost non-stop beeping when the phone boots up, and about the only way to stop it is too check notifications asap. I have no tone that sounds like this beeping, and have no clue why it does this on boot. I thought it was stock ROM issues, but I have flashed auxora and trigger 3.2, and get the same annoying beeping. It is only when there is a voice mail in the notifications, when booting up phone.
Thanks jman!
I had the same problem, hours of searching 'android boot alarm' and endless variations on google found nothing on this. I googled 'android beeping at boot', found this thread and you were 100% correct. I cleared my voicemail and no more beeps! Seems like an odd bug, anyone know a way to prevent this from happening any further? I was minutes away from a hard reset before I found your advice. Thanks!
Same here on I9000B Froyo 2.2 JPA
I hate this beep. Its so loud.
This is apparently a common enough thing from what I've seen on line, but every solution I find involves the person having used a profile switcher or their calender to signify being unavailable. I do not use either type of program. I almost never silence my phone. (in the movie theater or similar, yes, but otherwise never) Does anyone have any idea what it could be? It;s only been happening since the OTA update to .217 ICS. It's getting thoroughly aggravating missing calls and texts, as I'm sure you can imagine... Thank you to anyone with ideas/suggestions.
Check your settings in both the system settings as well as each individual app. I think after the update the messaging app is set to silent by default, or at least the vibrate is turned off.
If the system is messed up I recommend that everyone install the ota factory reset. Clearing out your old GB data and letting the ICS run "fresh" solves a lot of problems.
Sent from my DROID4 using Tapatalk 2
Could it be a Smart Actions setting?
Settings are all fine yet it does randomly put itself on silent mode no vibration and you have to turn it back to vibration via settings volume rocker just puts it back on silent....
Sent from my DROID4 using xda app-developers app
The Magician Type 0 said:
Check your settings in both the system settings as well as each individual app. I think after the update the messaging app is set to silent by default, or at least the vibrate is turned off.
If the system is messed up I recommend that everyone install the ota factory reset. Clearing out your old GB data and letting the ICS run "fresh" solves a lot of problems.
Sent from my DROID4 using Tapatalk 2
Click to expand...
Click to collapse
The Kraken! said:
Could it be a Smart Actions setting?
Click to expand...
Click to collapse
If it keeps happening tomorrow, I will do a full factory reset. Hoping I won't have to though. It's a pain in the rear to restore everything... It isn't a smart action thing because I have that app frozen, good thought though. Thank you all for the responses.
I tried a fr from recovery menu never froze apps nor rooted this d4 didn't help...
Sent from my DROID4 using xda app-developers app
Update
I've found that it is only doing it with phone calls now. I cannot find a setting in the phone app or the system settings that is set to mute, but it keeps happening. Also, after using the lock screen to unmute it, I have to turn up the volume manually. The lock screen thing only bumps it up to the minimum volume level... Anything else come to mind before i do a full FR? I'd really rather avoid it if I can... Thanks again.
Now I've got one worse. Did a FR, no go. Tried to update to Eclipse, and messed it up. Had to .sbf back to factory. EVEN AFTER the .sbf, still having the same issue with it muting while recieving a call.... (i.e. goes on vibrate instead of ringing....) Any ideas ANYONE???!!?!?!?
Honestly, this sounds like a hardware issue to me. If I understand correctly, it sounds like the phone keeps going to silent (or vibrate after ICS)?
My guess after all your software troubleshooting is that your volume down key is either physically or electronically damaged, and periodically decreases itself. You might want to try remapping the volume button or something to see if that solves the problem. Of course, after that you don't have any volume buttons, which stink.
Aside, the physical buttons (power, volume) on the D4 really stink. They are very mushy and almost flush with the case, poor design if you ask me.
That thought crossed my mind also, but it only happens on an incoming call, and I can adjust the volume up and down in every app. If I don't receive a call all day, there is no problem, texts & emails work fine. I've even had a friend sit with me and text me (sound worked) then call me (muted as it received the call) and all it did was vibrate, no ringtone. I have who is it and thought it might be that, but un-installed it and no change... I'm totally out of ideas...
Thank you for the ideas, unfortunately nothing has worked so far. Any further ideas will be much appreciated. Thanks again.
Finally figured it out. Apparently it had to do with some stetting that Who Is It made. I had it set to announce the caller, which apparently doesn't work now. When I un-installed who is it nothing changed, so I re-installed it and on a whim disabled the announce feature, and it's been ringing fine since. I believe it was some sort of setting because after disabling the announcement, I un-installed who is it again, and the phone would ring without a problem. No Idea what setting it was. Thanks to veryone for the help.
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
tadees said:
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
Click to expand...
Click to collapse
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Flying_Bear said:
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Click to expand...
Click to collapse
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
tadees said:
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
Click to expand...
Click to collapse
oh well, it seems that our problems, even though they have similar simptoms, aren't caused by the same thing. i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Flying_Bear said:
i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Click to expand...
Click to collapse
ah well, thanks for trying. :cheers:
My phone randomly talks something about the time, I'm not getting what she saying (woman voice).
Talkback option is off, I checked that one.
What is this, this is so annoying and creepy.
This is not the first bug, since I bought this phone.
Anyone can help me?
Something put into clock settings?
I found this similar problem, I have exactly the same:
"A couple days ago I started hearing a womans voice at random times, like I had butt dialed someone, but I could Identify where it was coming from. Then while I was scrolling on my phone I hear something something "time". Finally in the middle of the night when everything else was quiet I hear it clear as a bell. A robotic female voice saying "it is time". No notification. No background apps running. I've done a few things to check those things and can't find anything. It is slightly annoying. But more so, creepy AF. Any help would be appreciated."
It's Big Brother sending you subliminal messages
Don't see what it could be other than a notification related thing...something you already forgot that you enabled. There are SO many settings, I doubt I could bring my phone to the same exact config after a factory default.
Try using the notification history feature to track this ghost down.
This sounds like an accessibility setting turned on to me
mpore14 said:
This sounds like an accessibility setting turned on to me
Click to expand...
Click to collapse
Ah, yes. That must be it. Good thinking.
I'm betting that you will find the culprit in Bixby Routines. It's under Advanced features.
your question is your phone talks about time, for that u will have to search on google ..
I tried everything, but couldn't helped. I did a factory reset. I always hate to do that, because It takes to much time to put back everything and set up, but at least it helped.
Thanks to everyone.