Sorry if this has been discussed before, but i checked some performance related threads and nobody mentioned it.
After hanging up a call, why does the entire device hang for about 10-13 seconds before I can use any other function (including making another call) ??
Anything that can be done to fix this?
Thanks for the help!
hello? I'd really appreciate someone to reply to this, just so at least I know I'm not the only one with this problem. Thanks!
did you do any radio changing?
It seems to be an issue with some radios on some phones. I have a list of radios that I use that will crash the phone after so many calls.
No, no radio changing. In fact I don't even know what that means.
The phone doesn't crash, it just hangs after a phone call for about 13 seconds like it's trying to process something. Doesn't anyone else experience this?
have you downloaded a bunch of app to run in the background of your phone?
it does sound redundant, but if you take a look at your task manager it'll show you how much of your ram is being used up. if it's somewhere high like 75% then you need to close whatever program is taking up the most memory.
another possible thing might be active sync. I heard that when active sync tries to sync while not connected it can cause slow downs and that might happen during or when you hang up a call.
good luck
Just tested it. Active directory was not on, and neither was there any background processes working according to Task Manager, and it still took 10 secs after I hung up the call before I could reuse the phone.
How long is it supposed to take for the rest of you?
a second or less. Active sync is the usual culprit for bad battery life, but it looks like something is running in teh background and making your phone calls take longer to quit.
download and install advanced config, and look in one of the settings which is called "hangup delay" or something like that default is 1500 mS (1.5 seconds) change it to 500 mS or what ever you want and see if that makes a difference
BlackAccord said:
download and install advanced config, and look in one of the settings which is called "hangup delay" or something like that default is 1500 mS (1.5 seconds) change it to 500 mS or what ever you want and see if that makes a difference
Click to expand...
Click to collapse
I've done that now, and all I've done is improve the "hang time" by the number I've reduced the "hangup delay" by. The hang-up delay was originally 3000, and I reduced it to 1000, so my "hang time" is reduced by 2 seconds, but I still have to wait around 9-10 seconds before the phone is usable again.
How come no-one else is experiencing this? There's nothing special running on my phone.
I have the Telus device and have the ' hang' problem as well. I have seen updates on the HTC website for different carrier versions that may correct this problem. None for Telus yet though.
do you have any sort of battery meter running at the top of your screen? ie tnt battery meter?
that app KILLS KILLS KILLS performance on the TP for some reason...
Yes I have a battery meter at the top of the screen, but it's the stock one. I don't know what a "TNT" battery meter is. Should I disable it, and if so how? And after I do, how would I know how much power I have left? And are you saying that those of you who did not turn of the battery meter had performance problems when hanging up?
Thanks!
monkeychucker said:
I have the Telus device and have the ' hang' problem as well. I have seen updates on the HTC website for different carrier versions that may correct this problem. None for Telus yet though.
Click to expand...
Click to collapse
Thank-you! I am also with Telus! If anyone has any suggestions - please help! This is the number one problem with the phone, as well as dropped calls on occasion. I like all the non-phone (ie. PDA) functions though (except that all my outdoor photos turn blue)
Found this which seems to help:
Dealt with HTC for the same issue you're talking about. Turn the "Auto save contact" off and make sure you wipe you call history and the issue will go away.
ajy101 said:
Yes I have a battery meter at the top of the screen, but it's the stock one. I don't know what a "TNT" battery meter is. Should I disable it, and if so how? And after I do, how would I know how much power I have left? And are you saying that those of you who did not turn of the battery meter had performance problems when hanging up?
Thanks!
Click to expand...
Click to collapse
im talking about a meter that runs across the very top of your screen so that if it's halfway across your screen you ahve 50% battery left. if you don't have any idea what i'm takling about then ignore this lol
On more than one occasion, my NS4G has not given me a voice direction when it was supposed to. I noticed that my screen was off in all these cases, so I tried a simple test:
1) Navigate to a destination that I know how to get to on my own
2) Turn off the screen
3) Most turns ARE given as voice directions, but if I am getting very close to a turn (less than 50ft) and never got the 1/2 mile alert, etc... turn on the screen
4) As SOON as I turn on the screen, the voice immediately says "turn right" (I am now like 10ft from the turn... whereas if the screen had been on all along it would have given me a much earlier warning... proving that the screen being off was delaying/suppressing it)
Has anyone else noticed this? I rarely have my screen on when navigating, and I never once had this bug happen on my old POS phone (Moment). This phone is awesome, and the maps/nav app is available for all phones, so I'm not sure why I'm only getting the bug now?
When I get into my car and my bluetooth headunit connects with my Z3, the screen decides to turn on... for no reason whatsoever. I've disabled apps, tried setting up tasker to turn the screen on after a few seconds... yet nothing seems to work.
Why is this happening? I never had this with my Z2, it really sucks when my phone is in my pocket and I just want to drive, instead I get random actions, and even at one point pocket dialed people.
I hate to reply with anything but a solution, but this is an ongoing issue for me as well. It doesn't seem like it's solvable without a custom kernel. After I rooted my Z1C and installed SlimKat, it stopped happening. Since I got my Z3 I haven't been able to figure it out at all. The closest I got was to install a custom lock screen and have Tasker check for BT Connected and [custom lockscreen] started then wait 1 ms and turn the screen off. That used a ton of battery. I guess it's a solution if you find a way to stop the battery drain. Went from 5+ SoT to less than 3 in a day.
Bumping the topic.. exact same problem. Very very irritating. Battery drains out without even my knowing it. Seems like a serious bug.
Hi folks!
My OPO is with OxygenOS and I experience 2 strange things since I am in 5.0 (was the same when OTA brings me CM12):
My sound profile change randomly: when I put the OPO in "None" mode before going to bed, most of the time when I wake up it is in "Priority" mode or even in "Always" mode... It also happens sometimes in the day... which can be quite annoying when you think your phone is silent and begin to ring loudly at work for instance... or when you want to sleep and then a notification arrives at 2.00 am...
The other thing is linked to the app "Night Clock" that I use. I activate the app before going to bed with a nice soft red display of the time and at random hours, every night, the app is closed and I have in front of me a bright screen making the bedroom looks like night club... (at least from a luminosity point of view... especially for my wife... :angel: )
It is as if something was "playing" with my phone settings/notifications...
So, is it a known issue (haven't seen any thread on that, so i dont think so...) and do you have some sort of brilliant ideas to get back those 2 pesky points to normal?
Thanks a lot in advance!
I'm not sure I've actually identified the problem so let me start at the beginning.
I have a new Gear S3 Classic. It randomly will beep and vibrate for no apparent reason. If I look at the watch the only difference I can detect is a watch icon in the 12 o'clock position on the face. If you swipe on it, it will display the word 'standalone.'
The problem is that it should not be in standalone mode since this always seems to happen when the watch is in close proximity to my phone. What's worse is that it doesn't just happen once but 2 or three times in close succession before it finally gives up.
I think I can defeat the notifications by putting the watch in do not disturb mode but that has other obvious disadvantages.
So is my watch defective? Do I need to pursue a warranty claim? Am I doing something wrong, do I need to reconfigure my watch somehow? I have no idea how to proceed from here. Any help is appreciated.
I think the vibrations are BT disconnection alerts. This can be disabled in settings CONNECTIONS -> ALERTS.
In terms of addressing the underlying problem of why the watch and phone aren't able to maintain a solid BT. Have you tried pairing to a different phone, to rule out a problem on that end?
afblangley said:
I think the vibrations are BT disconnection alerts. This can be disabled in settings CONNECTIONS -> ALERTS.
In terms of addressing the underlying problem of why the watch and phone aren't able to maintain a solid BT. Have you tried pairing to a different phone, to rule out a problem on that end?
Click to expand...
Click to collapse
Thanks for the tip. I set it to turn of the alerts. That will be very helpful since it could be seriously distracting at times not mention annoying for other people with me.
My guess is that it's an issue with my phone - Alcatel Idol 4. It probably doesn't send out an "I'm here" signal or whatever the technical term is, often enough for the S3 to realize that it's in range. The last time this happened, I swiped the icon and looked at the watch face and within about 10 seconds it reported that it was connected again.
As long as I don't have to listen to the watch and phone work out their marital differences though and they can manage to stay connected when I need them to be, I'm not going to worry about the watch going standalone periodically.
Thanks again.