I using a S710 with Dr Gonzo's WM6.1 v1.1
I've set the Profile options as "Vibrate and sound" for messaging, emails, and Calls.
But whenever there's a missed call, the phone vibrates about 25-30 seconds after the missed call, multiple times.
Same goes with SMS, the sound notification comes first, then sometime later, the vibrations.
Sometimes it vibrates for no apparent reason, even after checking the missed calls list.
It's kinda irritating now. I've put off the vibration option for all except voice calls for now.
Is it fine after you put off the vibration?
I think its not the phone which gives the late vibrations, but the reminder script. it keeps notifying untill you check the missed calls.
You should remove the script notify.mscr from the startup. It will resolve your issue.
yes, its ok after vibration i turn1ed off,
I'll get rid of the script. Thanks !
On incoming calls, my Fuze does not ring. I have it set to 'vibrate and ring' and it only vibrates. I have changed ringtones, ring settings, turned it off and back on, soft reset, pulled the battery out, etc and nothing will make my phone ring. All other notifications work (alarms, text messages, etc) and it will work on speaker phone once a call is connected. Is there any advice? I am trying to avoid a Hard-reset because I have the device set-up perfectly to my tastes...
jimmynotch said:
On incoming calls, my Fuze does not ring. I have it set to 'vibrate and ring' and it only vibrates. I have changed ringtones, ring settings, turned it off and back on, soft reset, pulled the battery out, etc and nothing will make my phone ring. All other notifications work (alarms, text messages, etc) and it will work on speaker phone once a call is connected. Is there any advice? I am trying to avoid a Hard-reset because I have the device set-up perfectly to my tastes...
Click to expand...
Click to collapse
What format is the ring tone in?
My ringtone is the 'Oldphone2' and it is set at'vibrate and ring'. It just spontaneously started this non-ringing thing this morning prompted by no changing of settings. As I said, I tried messing around with the setting after it stopped ringing, but to no avail. And the frustrating thing is that everything else seems to work fine. Argh!
This may seem silly, but have you checked your ring volume? I've had a situation a few times, for no apparent reason after disconnecting from Activesync, where my ring volume was down to 0. Just a thought.
I HAVE SAME PROBLEM, when you turn all to vibrate only and turn it back up . the ring stop working
Yes. all volume settings are up. ringer volume, call volume, media player volume.... Any other suggestions?
i had the same problem just now.. but changing the ringtone back to the ATT default one fixed it. I also use S2U2 and changing the setting for "vibrate when answered" or something like that seems to have fixed it as well.
Hope that helps.
what is S2U2? I have tried changing the ringtone back to ATT default and fiddling with the settings... No help there. This is frustrating. I have to keepmy phone on my desk in front of me so I dont miss any calls. I miss them if the phone is in my pocket.
jimmynotch said:
what is S2U2? I have tried changing the ringtone back to ATT default and fiddling with the settings... No help there. This is frustrating. I have to keepmy phone on my desk in front of me so I dont miss any calls. I miss them if the phone is in my pocket.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=412418
this happened to me too and i hard resetted. that fixed it , then it started again. come to find out th eproblem was when i hit the volume key on the side i turned system valume up and didnt click on ringer volume to turn it up . i had to smack myself
do texts ringer still work?? if so then im pretty sure you have the same problem i had, check it. good luck though
Do you have the unit face down? It has an auto mute when face down.
I also have an alarm problem, although lights go off, the alarm doesn't ring. I also have problems with ringing on incoming calls. The speaker otherwise works fine. Volumes are turned on appropriately. I have Natfv4.0 installed. Do any of the roms fix this problem?
So somehow the problem fixed itself. Dont know how as I didnt even touch my phone for two days. I just turned it on and -BOOM- it rang a few minutes later. Totally spontaneous issue. Really strange this phone is sometimes...
Boy, do I feel dumb.....Never even noted the un hi-lighted RING volume TAB...
I guess I can't use THAT excuse for not answering calls...
Thanks
Ron
I've been having the same problem. It's very baffling to say the least. I believe it was caused by the newer versions of S2U2. Don't know if it's been discussed in that thread or not. Both times this ringer 'glitch' has occurred, it's been when I've password protected S2U2 in settings. The issue was fixed by turning the password protection off, restarting S2U2, soft resetting my Fuze.
I am having the same problem with incoming calls not playing the ring tone and missing calls. I can guarantee you that the system/ring volume controls are at maximum. I have switched ring tones to no avail. It seems to have something to do with changing the ring type from ring to increasing ring and or visa versa. When I change ring type the problem exists. If I turn system/ring volume to silent and then back to maximum it plays the ring tone just fine. There is a bug in there somewhere! I also see a 'send text' lower left of screen and I hear a blurp sound or two in the background wihile the ringtone is playing when the phone is ringing. Anyone else have any issues like this? If so or you have a fix please send it to [email protected] I'm new to this forum stuff and don't really know how to use it. Hope I didn't break any rules.
Thank you,
Trent Alexander
I just have the callers complaining that I take too long to answer the phone. I called myself, and it took 3 1/2 rings for my Fuze to ring...anyone else?
Great PPC, Lousy Phone
Mine too. I just tried it and it does not ring until seven seconds after the light starts flashing. Not only that, it will not retain a custom ring tone. I try to use Old Phone 2 but it reverts to the default on its own.
My vario iv also suffers from the missing ring tone- reboots sometimes help but not always.
I too have had to learn not to rely on the alarm- goes off some days and then not on others.
Just now I thought that I would try to play an mp3 to see if that works- I pressed play and then waited for the track to start- no sound- seconds later the screen changed and touchflow launched itself (again) went back to the home tab and the sound is back?????
Same problem... it stopped ringing...
one thing I notice is that if the number calling is private or block it will only light up (no ring) but from a caller with Caller ID open the phone will ring...
strange...
I've noticed that, for some reason, during the day my notifications won't sound. The phone will vibrate but I have missed calls, SMS, emails, etc. because of this. The phone is DEFINITELY on loud and I am NOT changing the volume in pocket (it happens with or without case). Everytime it happens, I checked my volume and it is all the way up.
Any ideas? PS - happens on any ROM
hah2110 said:
I've noticed that, for some reason, during the day my notifications won't sound. The phone will vibrate but I have missed calls, SMS, emails, etc. because of this. The phone is DEFINITELY on loud and I am NOT changing the volume in pocket (it happens with or without case). Everytime it happens, I checked my volume and it is all the way up.
Any ideas? PS - happens on any ROM
Click to expand...
Click to collapse
I had a similar issue that turned out to be due to my own mis-setting of CyanogenMod's quiet hours <.< 12PM is different than 12AM.
In your case it sounds like there is a setting somewhere that is preventing there from being a notification sound. Do you use stock messaging and gmail? Go into the settings for those applications (stock or non) and check to make sure its set correctly. Has this always been true? Have you tried doing a full factory reset? It sucks but its the best way to gauge whether or not you are experiencing a setting issue or if its really a hardware issue. Do your calls ring?
kenvan19 said:
I had a similar issue that turned out to be due to my own mis-setting of CyanogenMod's quiet hours <.< 12PM is different than 12AM.
In your case it sounds like there is a setting somewhere that is preventing there from being a notification sound. Do you use stock messaging and gmail? Go into the settings for those applications (stock or non) and check to make sure its set correctly. Has this always been true? Have you tried doing a full factory reset? It sucks but its the best way to gauge whether or not you are experiencing a setting issue or if its really a hardware issue. Do your calls ring?
Click to expand...
Click to collapse
I appreciate the help; I'll check quiet hours. As I stated, calls have the same problem. Notifications are definitely properly configured in their respective apps because I get the sounds sometimes.
Bump
Sent from my Nexus S using Tapatalk
hah2110 said:
I've noticed that, for some reason, during the day my notifications won't sound. The phone will vibrate but I have missed calls, SMS, emails, etc. because of this. The phone is DEFINITELY on loud and I am NOT changing the volume in pocket (it happens with or without case). Everytime it happens, I checked my volume and it is all the way up.
Any ideas? PS - happens on any ROM
Click to expand...
Click to collapse
In your Sound -> Volume Make sur ethe "Use incoming call volume for notificatons" radio is ticked. Turn ringer all the way up and see if you can hear your notifications.
I can't figure this one out. I have a H830 running 20i non rooted.
Sometimes incoming text messages don't trigger the vibration. The screen comes on and shows the pop up message. It just doesn't trigger the vibration. I have no problem receiving messages. They just don't always give the vibration alert.
It's intermittent with no pattern. Sometimes it'll work while the phone is in a deep Doz sleep. Sometimes it won't. Sometimes it'll work when the phone is active with the screen on and sometimes it won't.
I have the problem on the stock messenger, Chomp SMS and Next SMS. (Not running them simultaneously.. Stock SMS is disabled. Only one 3rd Party SMS installed at a time. Same thing happens on stock with no 3rd party SMS apps). The settings in the apps are properly set to send a vibration alert. It just don't work every time.
Occasionally it'll even give me a super short single vibration, almost like a keypress vibration. That's instead of the 3 long vibrations pattern I have set.
I don't believe it's a hardware issue. The vibration motor works 100% of the time if I purposely trigger it by turning out 'vibrate on keypress' or turn the system volume to vibrate or run any vibration test. So the motor is fine. The controller is fine. It's just SMS's that don't seem to send the alert to the system to trigger the vibration motor.
I cannot figure this out. I've made the SMS apps persistent and allowed them to be ignored in the battery optimizations in case the app wasn't waking in time.
Any ideas?
I posted yesterday about the facebook app being unable to retain any notification sound I've set for it once the app has been stopped. Well, there is another issue on the same phone. It may be related - I'm not sure. This OS is Android 7.0 (Nougat). The symptoms are below.
Two-symptom issue:
1) The 'call end tone' (which sounds like a pingy "bloop") cannot be disabled. The toggle slider can be turned off at Dialer > Settings > Call Alerts > Call end tone, but the tone still fires after each call disconnect.
2) The 'call end tone' not only fires after every phone call disconnect. But strangely, it also fires after any notification sound from another app has fired. For example, when Tapatalk or Facebook fire off a new message alert notification sound, the call end tone fires immediately afterwards. I also notice that each time the call end tone fires, a slash mark momentarily appears through the speaker icon on the notification strip.
I've tried wiping the cache partition and, as mentioned, toggling off all call alert settings. But none of that has worked. And by the way, this is the installation of Nougat that was on my S7 edge when I received it back from Samsung's repair center a few weeks ago. I'm hoping to avoid doing a factory reset. It looks like that may be the next step, though. Any thoughts?
Okay, I was wrong. It's not the 'call end tone' that I'm hearing at all. Instead, it's the same sound that fires when you change from silent or vibrate mode to audible mode. That little "bloop" is what's firing after every notification sound. I've checked and it's the following file: /system/media/audio/ui/TW_Silent_mode_off.ogg ... I'm not rooted so I can't remove or rename it.
So that's why the 'call end tone' toggle slider under Call Alerts has no effect on the little "bloop" sound. I only thought it was the 'call end tone' because it always fires when a call disconnects. But it's apparently just doing the same thing it does when each notification sound fires. Whatever the root cause, upon each sound event it seems to send a signal to briefly mute the speaker (hence the slash mark across the speaker icon for a split-second) and then immediately un-mutes it again. But I have no clue why. I thought it might have something to do with SoundAssistant -which I installed several days ago- but uninstalling it makes no difference. So I'm stumped.
I'm open for any ideas. The 'bloop' after every notification sound and call disconnect is driving me nuts. I'll probably do a factory reset if no one can think of anything else.
I've identified the cause. It's an app that normalizes the ringtone level, called 'Disable Increasing Ring.' When I toggle off its normalization mode, the problem is gone. The reason I even installed the app is because of the forced ascending ring volume for incoming calls that's imposed by Android 7.0. In my view, there's simply no excuse for Google/Samsung not to provide users an option of whether or not they want ringtone streams to ascend from weak to a normal volume level. Forcing that sort of thing upon everyone seems ridiculous. And of course it caused this headache for me. But it's their system... so oh well.