So my ear piece is not putting out any sound, speakerphone works but not reg ear. I've tried turning sound all the way up before calling and while, nothing. Was wondering if anyone had a suggestion or two before I replace it. I haven't installed any new apps or altered anything since the last time it was working fine.
Though: all my app updates seem to return an invalid package error and system status (for updates) seems ****ed up.
And no I haven't made any nandroid backups yet to attempt to go back to.
Edit:
Also I haven't done anything but metamorph notification bar, and battery icon aside from root.
Sent from my DROID3 using XDA App
Guess I'ma return it to stock and call verizon, lol
Related
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
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.
=======================================================================
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<SOLVED>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
I found this thread (http://forum.xda-developers.com/archive/index.php/t-1052796.html) which indicates that a voicemail alert, prior to the media scanner completing, causes this issue.
=======================================================================
So this morning I rebooted my phone. After it loaded into the home screen (but, before it connected to the network or finished media scanning) it began beeping, loudly. I was only able to silence it by turning the phone to silent mode. This beeping continued for roughly two minutes then stopped.
At no point was there any alert or message to indicate that the system had booted up in a manner that was abnormal. After repeated tries, the device makes this noise upon boot, religiously.
What the hell is it, and how do I stop it?
Seriously? Anyone? This is obnoxious.
Maybe if you gave more info...like rom...kernel...stock...recent apps...
Sent from my GT-I9000 using XDA Premium App
bulletproof1013 said:
Maybe if you gave more info...like rom...kernel...stock...recent apps...
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Well, my ROM info is in my signature and I am running the default Serendipity kernel (hardcore speedmod). There have been no recent alterations to system settings, setup, or applications. No new apps installed, or uninstalled, in the past week. And nothing is open on the device when the beeping occurs (as the phone is still starting up).
Let me take a stab...might work, might not
Do you use Google Voice?
I was having an issue last month where the phone would give the odd old G1 beeping sound as soon as it reached the homescreen after reboot. Found it was a rogue google voice email message that was trying like hell to give me a notifier, but was failing miserably. Check your web console for GV and see if you have a new message waiting to be read (or listened to), open t so it doesn't eed to notify. That stopped my crazy beeping.
pbclst said:
Let me take a stab...might work, might not
Do you use Google Voice?
I was having an issue last month where the phone would give the odd old G1 beeping sound as soon as it reached the homescreen after reboot. Found it was a rogue google voice email message that was trying like hell to give me a notifier, but was failing miserably. Check your web console for GV and see if you have a new message waiting to be read (or listened to), open t so it doesn't eed to notify. That stopped my crazy beeping.
Click to expand...
Click to collapse
I do not use Google Voice. It is, however, installed on the device. When I open it I am given a series of setup questions, so I don't imagine that it is telling me that I have a message waiting.
I originally thought that it was a message alert from some program. The problem with that is that it goes on for nearly one-hundred and twenty seconds and does not give me any visual indication of what it is attempting to alert me to.
My main concern is that it is some sort of hardware warning and that I am ignoring it out of ignorance.
Does the beeping stop when you pull down the notification bar as it would to silence an actual notification?
Sent from my Cappy.
DaveyBB said:
Does the beeping stop when you pull down the notification bar as it would to silence an actual notification?
Sent from my Cappy.
Click to expand...
Click to collapse
It does not.
conundrum768 said:
It does not.
Click to expand...
Click to collapse
Can you identify which file on the phone is the actual beep sound? I'm just wondering if something is specifically calling the sound file, or if it is random. If you could identify the file and delete or rename it, it might help troubleshoot to see what your phone would do/attempt to do.
Captivate beeping
DaveyBB said:
Does the beeping stop when you pull down the notification bar as it would to silence an actual notification?
Sent from my Cappy.
Click to expand...
Click to collapse
My beeping stops when i pull down the notification tray. I have been tethering for about a week without paying AT&T extra money with PDANet. Have they caught me?
This ringtone, for lack of a better word, is buried in the rom somewhere. It is called something like unresolved. Maybe reinstall kernel. this has happened to me before... I just can't remember how I fixed it.
Sent from my GT-I9100 using XDA App
Found another thread (http://forum.xda-developers.com/archive/index.php/t-1052796.html) which seems to have answered, but not solved, this problem.
I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.
Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.
activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.
I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App
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.