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.
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
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.
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
A few days ago, I started having an issue with my Moto X's audio. I noticed after waking up my alarm hadn't gone off. After that, I realized that my phone wouldn't play any audio at all, through the speaker or headphones. However, I'm not entirely sure whether this is a software or hardware problem. When I attempt to play any video or audio I tend to get a general error from the app I'm using. For example, trying to play a song through Play Music results in a "Couldn't play the stream you requested." error. Attempting to play a Youtube video through the app gives me "There was a problem while playing." error. Trying to play a video through Chrome will actually make Chrome close. So, my audio problem doesn't seem to just be a speaker problem, because if it were I would expect videos to play without a problem, there would simply be no sound, unless I'm misunderstanding how that would work. I'm also not sure whether or not it's hardware related, because, as I said, the issue occurs with both the speaker and when I plug in earbuds or headphones.
I've already attempted some general solutions I had hoped would fix my problem. I've checked the sound setting and ensured the three volume sliders are set correctly. The next thing I tried was the general turn it off, and on again approach. I've also cleared the cache (multiple times), and even resorted to a factory reset, none of which has helped. I also uninstalled any recently installed apps, just in case. The fact that a factory reset did not help makes me assume it has to be a hardware problem. However, I'm not certain, because of the aforementioned errors I get from apps, as opposed to the behavior I would expect if there was a problem with the speaker. Again, please correct me if this is, in fact, what a speaker problem would be like.
Note: I'm running stock 4.4.4 Android and the phone was indeed bought used. I had a problem with my old phone and was not eligible for an upgrade yet, so I bought this phone. I got the phone about a week ago and, until yesterday, it worked perfectly. Unfortunately, I'm still not able to get an upgrade so that's not an option.
I'd really appreciate any guidance with this problem. Unfortunately, after the factory reset, I kind of ran out of things to try to hopefully fix it. Also, I apologize if this post has any formatting issues. This is the first time I've posted. If there's anything I could have done to make my question more clear, please alert me to it.
Tl;dr No audio from stock Moto X running current update. Apps give error or close when attempting to play video or audio. Already tried clearing cache partition and factory reset with no results.
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
Try a factory reset. Ive had it fix many a strange bug before.
Jansy said:
Hello there, I have a frustration with my Nexus 6 running 6.0.1
While there is similar probs around, none seem to explain mine.
When using Google Music on Bluetooth/Headset I get normal operation and then randomly (sometimes immediately, sometimes up to about 5 minutes) the volume drops down. The Volume slider still shows 100% volume.
I thought at first it was the ear-saftey thing we used to have where it does this, but then allows you to change it back to full volume. But I didn't get any message around that or cannot find a way to override it.
Then I thought it was another system process stealing focus and the phone getting confused, eg dropping volume for a notification and then just not returning it.
Tried rotating phone to see if it was a portrait/landscape bug
Everytime. I restart the phone, it's fine again before the random volume drop occurs 1 sec-5 mins after playing a song. Once it does it, it gets stuck that way.
I've lived with it for a long time but it's doing my head in now so hopefully someone can help it advise?
Not even sure if a factory reset will fix.
Cheers
Click to expand...
Click to collapse
I've had the same problem, running N developer preview 1 listening with wired headphones. I've learned that I just kind of have to wait for it to pass, try force stopping play music, or restart the phone.
Are you streaming your music, or is it downloaded onto your device? I manually copy music onto my phone from my computer, and this is when I've got the issue, as I stream with Spotify fairly often and never have the problem. I've always thought it was just some bug reading all of these crazy 3rd party audio files in the storage.
Hasn't been much of a problem for me... Just jumped at the opportunity to share when I saw this thread. If it bothers you that much, try a full wipe of internal storage and reinstall everything. Cheers! Hope I helped.