Related
My phone has a very noticeable delay on incoming calls. I'll see it light up and flash for a bit, take a few seconds to get caller ID, then it will finally ring once before going to voicemail. All the while the caller is hearing the phone ring but I'm not...I tested it. Since I don't stare at my phone all day I have a high volume of missed calls because many times I only get the last ring. Any ideas what's going on? I tinkered with settings in Advanced Config and DiamondTweak. No dice. I'm using the stock Fuze Rom.
Isn't this normal behavior?
I've set my Kaiser on GSM mode and I can hear calls coming in on my computer's speakers a full 2-3 seconds before the phone actually rings.
diar said:
My phone has a very noticeable delay on incoming calls. I'll see it light up and flash for a bit, take a few seconds to get caller ID, then it will finally ring once before going to voicemail. All the while the caller is hearing the phone ring but I'm not...I tested it. Since I don't stare at my phone all day I have a high volume of missed calls because many times I only get the last ring. Any ideas what's going on? I tinkered with settings in Advanced Config and DiamondTweak. No dice. I'm using the stock Fuze Rom.
Click to expand...
Click to collapse
I have the same problem (htc org. rom)
Maybe this will work
I noticed that when someone calls my phone, they get two rings before my ringtone turns on.
After a second, my Fuze's LED starts flashing, then my ringtone starts playing after another second.
I have an idea:
1. Go into "Start > Settings > Phone"
2. Go to the "Services" tab
3. Highlight "Call forwarding" and then click the "Get Settings..." button.
4. Change the "Forward after:" dropdown box to something higher (e.g. "30 seconds")
It won't help the ring delay, but I think this will give you a little more time before the call is sent to your voicemail. I haven't tried it, but let me know if that helps
NuShrike said:
Isn't this normal behavior?
I've set my Kaiser on GSM mode and I can hear calls coming in on my computer's speakers a full 2-3 seconds before the phone actually rings.
Click to expand...
Click to collapse
I wouldn't call this normal. This is the first mobile phone that I've had that has had delays that long. If I didn't keep my phone next to me for most of the day, I'd probably miss more of my calls as well.
adamantypants said:
I wouldn't call this normal. This is the first mobile phone that I've had that has had delays that long. If I didn't keep my phone next to me for most of the day, I'd probably miss more of my calls as well.
Click to expand...
Click to collapse
I agree with you, this lag is very big problem, I missed a lot of calls, most of people must call me again because they are forwarding to voicemail at first time before I find TP (I cannot change in forwarding to 30 sec.
I'm wondering how it is in Diamond.
This is very frustrating. Nothing seems to fix this problem. I've reduced the call ID match to five digits instead of eight. I've made sure that Ring Time is set to "without delay" in DiamondTweak. I'll try the idea to change the call forwarding time but this seems to be a major problem in the OS itself. With this issue, Voice Command problems, the GPS lag and other issues I might have to jump to another phone.
Do cooked ROMS have these same issues?
I've got the same issue.. using T.I.R. V8R ROM, so yes, this delay is present also on custom ROMS. It has to do with the dialer skin?
This was discussed in a thread on an app that causes the vibrate pattern to match the ring pattern in hacks & discussions (I think called VAlert). The vibrate pattern starts immediately and the ring is delayed so the app isn't perfect (unless you build a delay into the vibrate but that's separate). The solution seems to be an app from tweaks2k2.net that I hear removes the delay. This is an issue with all WM phones. I haven't tried tweaks2k2 but I hear it works.
the tweaks2k2 fix - to eliminate the 3 second ringer delay - didn't work for me. so i went into the network phone settings and set the call forwarding to 25 seconds (it was 10). that didn't fix the ringer delay but now at least my phone rings three or four times before going to voicemail. i guess that will have to do for now.
diar said:
the tweaks2k2 fix - to eliminate the 3 second ringer delay - didn't work for me. so i went into the network phone settings and set the call forwarding to 25 seconds (it was 10). that didn't fix the ringer delay but now at least my phone rings three or four times before going to voicemail. i guess that will have to do for now.
Click to expand...
Click to collapse
it don't work sorry
Doing some debugging, on the Fuze at least the ringer delay seems to be tied to the bloatedness of the dialer.. it has a whole bunch of imports so its loading alot of stuff up every time you get an incoming call.. I'm afraid the only solution for this will be a dialer that does not bring in those kind of dependancies (PTT, Video Share, G-Sensor, etc)
The fastest way to go would be using the default windows dialer, but you'd lose all that functionality.. but hey. It would ring instantly!
I'll look into stripping the dialer from my clean ROM and providing a cab..
Confirmed. Removed the AT&T dialer skin from my rom and called my phone, rang as fast as any other phone would.. So the dialer skin is indeed the culprit.
Dang AT&T. Dang them and all their bloatware.
I'm going to corporate store to complaint. To all of them within a 10 mile radios.
I've posted my Beta 1.5 with the dialer removed. It's not an official fix by AT&T, but it is a fix..
I'll see if I can whip up a .cab to stop the dialer from loading in the stock AT&T ROM, that should help there too.
i like this dialer...but not that much. how do i disable it? in advanced config, i saw an option to enable the phone dialer skin or the default windows mobile dialer. would switching to the default fix it without causing any other problems?
EDIT: switched to default dialer and that fixed it. it also seems to have fixed the problem of having to re-enter the data connection password after a soft reset.
This set of cab's should do the job for anyone who doesn't want to install Advanced Config (it's a single registry entry HKEY_LOCAL_MACHINE\Security\Phone\Skin - Enabled=0/1)
Wow it really is about two seconds before the phone rings. Hm I never missed a call yet on this phone. where do you keep your phone that it takes so long to answer it?
AT&T's network lets you set the number of seconds before the call rolls over to voicemail, as do others, I believe the default on AT&T is 20 seconds, with a minimum of 5 and a maximum of 30, so if someone has it set to 5, that leaves only 3 seconds..
Of course they could just set it higher, but that's a different issue
So then a simple fix would be to go into your voicemail and set it to 22 seconds and then you still have the same time to pick up that phone. But still how does the 2 second dely really make you miss all them calls?
Does this happen to any one or is it just me?
I have an ordinary case for my Touch Pro. Almost 10 out of 10 times when the phone rings and I reach out to my phone, try to take it out - boom - the call becomes a missed call. I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call. It is very annoying and how to avoid this????
Thanks
kmahesh said:
Does this happen to any one or is it just me?
I have an ordinary case for my Touch Pro. Almost 10 out of 10 times when the phone rings and I reach out to my phone, try to take it out - boom - the call becomes a missed call. I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call. It is very annoying and how to avoid this????
Thanks
Click to expand...
Click to collapse
there is a key disabler cab look for it
There are many options how to disable the touchscreen.
There was a topic not long ago about this.
Answerkey Disabler
PocketShield (I currently use this one)
TouchProLock
Sensorlock
Throttlelock
S2U2 (not recommended for TP, drains the battery for unknown reason)
All these deal with locking the TP.
Sorry for not posting links but I don't have much time. All of them are available on XDA though.
You do have the option of extending the time it takes for a call to go to voice mail, it can be extended up to 30 seconds. The option is under settings > phone > Services > Call Forwarding
There is also a lot of lag on between the time the caller's phone is ringing and you get a ring on the Fuze
I guess this is not because of the keys. Just keep the phone in front of you and try to call your phone and see your self, first you will see the incoming call indicator light, and after some time you will start hearing the ring tone. Now by the time you take the phone from the case - it's a miss call. I tried to search all over XDA but didn't find a way to start ringing immediately when call comes, I read some where that this is due to the dialer skin and by using default WM dialer this can be fixed. I didn't try this.
kmahesh said:
Does this happen to any one or is it just me?
I guess what is happening here is that once the phone rings, the screen is active and either your finger accidentally touches the volume key or any other key or even the screen, it makes it a missed call.
Click to expand...
Click to collapse
I think he was talking about the touchscreen being active on incoming calls.
If however the problem is in the delay, then the dialer skin is the key.
You have to change it to the WM default (it does work, the lag is almost gone) and have the ringtone in WAV format (not tested, I didn't bother to put any wavs).
if you get rid of the dialer and switch to WM
you will lose functionality including the symbol to show bluetooth being on or off
I downloaded and installed disableanswerkeys and it works fine. It took a while for me to understand the cryptic question it asks in the beginning - i get stumped if there are two negatives in a sentence So It is on and i tried and it works ok. I also downloaded sensorlock and throttlelock. Yet to try these ... will post my comments.
the lag in answering the call - i believe there is a separate thread about that, right?
Thanks for the help
lbhocky19 said:
if you get rid of the dialer and switch to WM
you will lose functionality including the symbol to show bluetooth being on or off
Click to expand...
Click to collapse
LOL, that's what happened to my bluetooth......thanks
This is very annoying to me and a few other people that have the captivate but during a call and you get a txt the phone vibrates. Is there anyway/trick to turn this off and have it beep during a call?
If you get Locale and a plug-in for determining if the phone is on a call or not, you can have it automatically disable vibration when on a call and then re-enable it when the call is ended.
Why would you want to turn it off? I am pretty sure you do not get more than 1 or 2 text while on the phone. I think its a very useful feature. Well back to your question as far as I know there is no way to do this unless you want to dig around your database folder and see what you can find??
Go to settings-call settings-all calls-alerts on call Off
you can turn it off, but every phone does this...i mean how else are you supposed to know if you got a text if you're on a call?
V DidDy 210 said:
you can turn it off, but every phone does this...i mean how else are you supposed to know if you got a text if you're on a call?
Click to expand...
Click to collapse
My point exactly. I would just put my phone down and never notice the missed message/call/whatever since we do not have LED notifications.
My Blackberry would give me a little audio indicator in my ear if I received a text while speaking on the phone, even if my phone was set to vibrate. It was a nice feature. I wish this phone would do the same because it vibrates so loudly I can't hear what person I'm speaking to is saying.
if you're using the headset, it gives an audible sound.
I dunno I guess I don't mind as much, if I notice anything then I will defiinitely pass it along
Open the Messaging App.
Hit the Menu Button.
Go to Settings.
Scroll Down.
Uncheck Vibrate.
Hey guys.. your getting a misunderstanding... I want it to vibrate when im not talking on the phone but when im talking on the phone like was said above... it vibrates so loud when your talking. I was asking if there was a way to turn the vibrate off during the call and get a beep sound instead like the dudes blackberry does.
Hi all,
I am having an issue with my Galaxy S6 Edge+ with Bluetooth forcing the speakerphone when I am making a call and driving. This has just starting occurring since the Nougat update. If someone calls me I can still answer from the head unit and the Bluetooth works perfectly. The issue is when I make a call and press the steering wheel Bluetooth button. When I do this and say the name of the person to call I get the voice command saying "Calling so and so mobile...ON SPEAKERPHONE". It says it's calling the person but then says ON SPEAKERPHONE.
What is interesting is I played around with different settings, reset my phone, unpaired and repaired, and still the same issue since the Nougat Update. But what is interesting is that I found if I make a call while my screen is active (screen is on), and I make the same Bluetooth call, I can see the google voice icon pop up on my phone, the call is made CORRECTLY, through Bluetooth. However, if my screen is off and I make the call, it ALWAYS reverts to speakerphone. So as long as I touch my phone to make the screen active for 5 or 10 seconds or whatever I have the screen set to, as long as the screen is on the Bluetooth always performs correctly. I can not figure out how to prevent the speakerphone from being the primary source when the phone screen is off and I make a Bluetooth outbound call.
Again, if someone calls me, it doesn't matter if my phone is locked, screen is off or on, the Bluetooth always works fine. Any suggestions on how to fix this? Any help is very much appreciated. Thank you.
ItzTime said:
Hi all,
I am having an issue with my Galaxy S6 Edge+ with Bluetooth forcing the speakerphone when I am making a call and driving. This has just starting occurring since the Nougat update. If someone calls me I can still answer from the head unit and the Bluetooth works perfectly. The issue is when I make a call and press the steering wheel Bluetooth button. When I do this and say the name of the person to call I get the voice command saying "Calling so and so mobile...ON SPEAKERPHONE". It says it's calling the person but then says ON SPEAKERPHONE.
What is interesting is I played around with different settings, reset my phone, unpaired and repaired, and still the same issue since the Nougat Update. But what is interesting is that I found if I make a call while my screen is active (screen is on), and I make the same Bluetooth call, I can see the google voice icon pop up on my phone, the call is made CORRECTLY, through Bluetooth. However, if my screen is off and I make the call, it ALWAYS reverts to speakerphone. So as long as I touch my phone to make the screen active for 5 or 10 seconds or whatever I have the screen set to, as long as the screen is on the Bluetooth always performs correctly. I can not figure out how to prevent the speakerphone from being the primary source when the phone screen is off and I make a Bluetooth outbound call.
Again, if someone calls me, it doesn't matter if my phone is locked, screen is off or on, the Bluetooth always works fine. Any suggestions on how to fix this? Any help is very much appreciated. Thank you.
Click to expand...
Click to collapse
Seems to me that the wakelock for Bluetooth calling is set to be inactive while screen is off. See if you can find that wakelock or some other wakelock that would disable Bluetooth calling and switch it so that screen off does not interfere.
Sent from my SM-S903VL using Tapatalk
@ droidriven, thank you for your reply. I have never heard of wake lock before, is this an option within settings on my Galaxy S6 Edge+? I never had this issue with prior OS's but with Nougat this issue immediately became present. If you could lead me in the right direction where I might find the wake lock setting for Bluetooth, I would greatly appreciate it. Thank you again.
it looks like you are on to something. I checked this again and anytime I make a call via Bluetooth voice command and where my screen is off, I hear the automated voice command say calling so and so....on speakerphone....but when it says this, the screen stays locked and does not activate on the voice/Bluetooth command to call. I am using google voice and see no settings for wake lock or anything similar but I have pinned this down to anytime the screen is off, the voice command/Bluetooth always go to speaker phone. If someone calls me, it always works correctly, but that is because when someone calls me, my screen automatically engages/turns on.
Anyone else have this issue? It's definitely a problem and dangerous to have to grab my phone to turn it on or unlock it before making a voice/Bluetooth call. Any help to fix this would be appreciated. Thanks in advance.
ItzTime said:
it looks like you are on to something. I checked this again and anytime I make a call via Bluetooth voice command and where my screen is off, I hear the automated voice command say calling so and so....on speakerphone....but when it says this, the screen stays locked and does not activate on the voice/Bluetooth command to call. I am using google voice and see no settings for wake lock or anything similar but I have pinned this down to anytime the screen is off, the voice command/Bluetooth always go to speaker phone. If someone calls me, it always works correctly, but that is because when someone calls me, my screen automatically engages/turns on.
Anyone else have this issue? It's definitely a problem and dangerous to have to grab my phone to turn it on or unlock it before making a voice/Bluetooth call. Any help to fix this would be appreciated. Thanks in advance.
Click to expand...
Click to collapse
Go to PlayStore and do a search for:
Wakelock Detector
Wakelock are system processes and don't have a "setting" to manage them.
Use this app to find the running wakelocks, if you track it down you can then look for a way to manage it the way you need it to work. It works with root and without, instructions for without root are in the link.
https://forums.androidcentral.com/showthread.php?t=571286
Then read this to understand wakelocks
http://www.guidingtech.com/45384/android-wakelocks/
Sent from my SM-S903VL using Tapatalk
Droidriven,
I have a little more info on this issue. I did more research and realized somehow my "S VOICE" app was disabled so I enabled it and right away this issue was fixed! With S VOICE enabled, anytime I use the voice recognition button to make a call the screen on my phone immediately activates and the call works without going to speaker phone. With S Voice I can at least use the voice recognition button to make a Bluetooth call while driving and not have to worry about the call going to speakerphone.
The only issue I have noticed is it appears S VOICE isn't as accurate as google voice and google voice worked perfectly for me before the Nougat update. Now that I've isolated this issue to google voice where the screen will not activate when using the voice recognition button on my steering wheel to make a Bluetooth call and which causes all calls to go to speakerphone.....is this still something this wakelock detector may fix? My phone is not rooted and I have downloaded the non-rooted version of wakelock detector, I just don't know if it's going to help or not. It's odd that google voice worked fine prior to the Nougat update, whether my screen was off or locked when using Bluetooth and now all of a sudden this issue is present.
Any suggestions on this now that we know it's only google voice that has the problem and not S VOICE?
ItzTime said:
Droidriven,
I have a little more info on this issue. I did more research and realized somehow my "S VOICE" app was disabled so I enabled it and right away this issue was fixed! With S VOICE enabled, anytime I use the voice recognition button to make a call the screen on my phone immediately activates and the call works without going to speaker phone. With S Voice I can at least use the voice recognition button to make a Bluetooth call while driving and not have to worry about the call going to speakerphone.
The only issue I have noticed is it appears S VOICE isn't as accurate as google voice and google voice worked perfectly for me before the Nougat update. Now that I've isolated this issue to google voice where the screen will not activate when using the voice recognition button on my steering wheel to make a Bluetooth call and which causes all calls to go to speakerphone.....is this still something this wakelock detector may fix? My phone is not rooted and I have downloaded the non-rooted version of wakelock detector, I just don't know if it's going to help or not. It's odd that google voice worked fine prior to the Nougat update, whether my screen was off or locked when using Bluetooth and now all of a sudden this issue is present.
Any suggestions on this now that we know it's only google voice that has the problem and not S VOICE?
Click to expand...
Click to collapse
According to this and many other links I checked out, this is a common issue due to G Voice and S Voice incompatibility.
https://www.androidpit.com/ok-google-is-not-working-here-s-how-to-fix-it
Sent from my SM-S903VL using Tapatalk
Hi,
I've just got a watch 2 sport and when I've dialed someone off the watch and they are engaged I cannot see how to end call as icons disappear, I then have to get phone out my pocket , same when I'm on a call and want to end it off watch without getting phone out, unlocking it, then ending call, how do you?
Thanks.
Would like to solve the same problem.
u can set in option to ends call by pressing power button
I've tried wear dialer and that does what I want, ie there is an answer and a end call icon on the watch itself, it's not perfect because once in a call you can't see anything on the watch bar the dialer, if you want to see the time by pressing the home button it ends the call.
not sure if i understand good (my english is not very well )
if u have a call and wanna see for example time, just swipe dialer like u would close any app, call will remain and you will be able to see what u want and at the end of call press power button
DM* said:
not sure if i understand good (my english is not very well )
if u have a call and wanna see for example time, just swipe dialer like u would close any app, call will remain and you will be able to see what u want and at the end of call press power button
Click to expand...
Click to collapse
Not my situation.
I cant see the call informations on my watch.
Once I pick up the call, call UI on the watch dissapear.
Kind silly if you are driving car and speaking to your bluetooth and you are not able to end call without picking phone out of your pocket.
MiBan82 said:
Not my situation.
I cant see the call informations on my watch.
Once I pick up the call, call UI on the watch dissapear.
Kind silly if you are driving car and speaking to your bluetooth and you are not able to end call without picking phone out of your pocket.
Click to expand...
Click to collapse
That's what I can't understand, I call a number from my watch through my Bluetooth, the call ui disappears, the number is say engaged, I then have to go back to my phone to end call as the watch won't do it, the only way the watch will do it is by taking the call solely through the watch itself, the call ui then stays.
Not the best but I've stuck with wear dialer even though once on a call the watch only shows the call ui, if you want to know the time while on the call, you can't.