Something on the ascend is killing hangouts after the phones goes to sleep. Its not a hangouts issue, but the phones.
What apps can I freeze that manage phone background processes? (On stock rom)
webosFTW said:
Something on the ascend is killing hangouts after the phones goes to sleep. Its not a hangouts issue, but the phones.
What apps can I freeze that manage phone background processes? (On stock rom)
Click to expand...
Click to collapse
Check phone manager and see if hangouts is selected to be killed when the screen turns off to save battery.
Ya everything seems to be checked, its checked as a protected app and is allowed to run in the background, but something is still killing it.
Try uninstall and reinstalling Hangouts. It works fine on my XT .
webosFTW said:
Ya everything seems to be checked, its checked as a protected app and is allowed to run in the background, but something is still killing it.
Click to expand...
Click to collapse
webosFTW said:
Ya everything seems to be checked, its checked as a protected app and is allowed to run in the background, but something is still killing it.
Click to expand...
Click to collapse
have u went into hangouts settings of you user and set the allow incoming calls for your account?.https://support.google.com/hangouts/answer/6079064?hl=en&ref_topic=2944851&vid=0-613975714751-1490026771312
madvane20 said:
have u went into hangouts settings of you user and set the allow incoming calls for your account?
Click to expand...
Click to collapse
Ya ofc. I get calls and everything when the phone hasn't gone to sleep. The moment the phone goes to sleep, I do not get any notifications except the "Missed Call" notification.
webosFTW said:
Ya ofc. I get calls and everything when the phone hasn't gone to sleep. The moment the phone goes to sleep, I do not get any notifications except the "Missed Call" notification.
Click to expand...
Click to collapse
is ur wifi set to always stay on even when sleep
madvane20 said:
is ur wifi set to always stay on even when sleep
Click to expand...
Click to collapse
It sure is.
webosFTW said:
It sure is.
Click to expand...
Click to collapse
i found the feature to be hit and miss on phones i have had have u tried reinstalling like devine suggested or wiping all the cache partitions. also whats ur firmware version
madvane20 said:
i found the feature to be hit and miss on phones i have had have u tried reinstalling like devine suggested or wiping all the cache partitions. also whats ur firmware version
Click to expand...
Click to collapse
Yup, done that as well. Even installed older versions hoping it may fix it, but no luck so I am just going to try the bare rom and see if I have any luck.
webosFTW said:
Yup, done that as well. Even installed older versions hoping it may fix it, but no luck so I am just going to try the bare rom and see if I have any luck.
Click to expand...
Click to collapse
ok well hopefully i get a custom rom up and u wont have to worry bout it xd but its still in progress
madvane20 said:
ok well hopefully i get a custom rom up and u wont have to worry bout it xd but its still in progress
Click to expand...
Click to collapse
Ya I would love that. I will wait for your rom as I cannot even update to 150. Tried and it never boots up. Followed the directions perfectly.
webosFTW said:
Ya I would love that. I will wait for your rom as I cannot even update to 150. Tried and it never boots up. Followed the directions perfectly.
Click to expand...
Click to collapse
Sorry but the Update guide works fine .. you most likely didn't flash SuperSu after flashing the rom
no idea why people can't read and follow simple instructions
clsA said:
Sorry but the Update guide works fine .. you most likely didn't flash SuperSu after flashing the rom
no idea why people can't read and follow simple instructions
Click to expand...
Click to collapse
Thanks. Something you mentioned made me go back and redo it. In the tutorial(140-150) at the end you do not mention to reflash SuperSu. Reflashed and it started right up as 150.
Update:
Same issue.
Tried Bare_Naked Rom and same issue. Hangouts rings when display is on, I leave it idle for 15 min and it no longer rings when I call.
What happens if you wake up the phone by hitting the power button, then dialing your GV #? Does it ring in that case? Are you using any third-party apps for power management that may be contributing to the problem?
I'll have to try some testing on my phone to confirm what's happening with your phone - will post the results.
webosFTW said:
Thanks. Something you mentioned made me go back and redo it. In the tutorial(140-150) at the end you do not mention to reflash SuperSu. Reflashed and it started right up as 150.
Update:
Same issue.
Tried Bare_Naked Rom and same issue. Hangouts rings when display is on, I leave it idle for 15 min and it no longer rings when I call.
Click to expand...
Click to collapse
If I got the power button and call it rings with any problems. No power management apps, even did a clean install where the only thing installed was Hangoutsand voice.
I believe that if I disconnect from WiFi and leave it on just 4g it will ring if it goes to sleep. Need to do some more testing though.
All my testing is with WiFi on and mobile data off.
I had cases where I could kill Hangouts, put the phone to sleep, call it, and Hangouts would ring. Then sometimes it would ring for a fraction of a second, but the screen would show an incoming call was still in progress. Then other times it would not ring at all. Again, I preceeded each test by killing/force stopping Hangouts first. Weird inconsistent unexplainable results .
webosFTW said:
If I got the power button and call it rings with any problems. No power management apps, even did a clean install where the only thing installed was Hangoutsand voice.
I believe that if I disconnect from WiFi and leave it on just 4g it will ring if it goes to sleep. Need to do some more testing though.
Click to expand...
Click to collapse
divineBliss said:
All my testing is with WiFi on and mobile data off.
I had cases where I could kill Hangouts, put the phone to sleep, call it, and Hangouts would ring. Then sometimes it would ring for a fraction of a second, but the screen would show an incoming call was still in progress. Then other times it would not ring at all. Again, I preceeded each test by killing/force stopping Hangouts first. Weird inconsistent unexplainable results .
Click to expand...
Click to collapse
Ya I just tried with wifi off, leave phone for 15 minutes and call and it does call and ring through 4g no problem. Something on the phone is putting hangouts to sleep or terminating it when on wifi. I have all the setting enabled that force the app to stay awake but they arent doing anything.
Update:
Did some more testing and found out more information. If the phone is plugged in, it will ring without any issues. Even if its been sleeping for 30min+.
To summarize:
Hangouts when phone on wifi - Does not ring when sleeping
Hangouts when phone on wifi and plugged in - Rings when sleeping
Hangouts when on LTE/3G - Rings when sleeping
Makes me think there is a bug in the actual stock rom that kills apps when sleeping when it shouldnt?
Update2:
Installed Xposed and App Settings and enabled "Stay resident in memory" on hangouts. Left phone for a bit and called and it did ring. Leaving it alone for another 30 min or so and will test again.
Update 3:
I believe I have fixed the issue with the method in update 2. Been calling my phone randomly and it did ring 100% of the time. Glad I fixed it. Going to leave some tags for people googling this issue since it's pretty major(tons of posts about it on google forums). Will keep this post updated if the issue is not solved. Will keep testing throughout the day.
Tags: Google Hangouts not ringing, Hangouts not ringing
Yes sometimes it rings, sometimes doesn't, sometimes rings one time then stops. Seems random.
---------- Post added at 05:45 PM ---------- Previous post was at 05:26 PM ----------
webosFTW said:
Ya I just tried with wifi off, leave phone for 15 minutes and call and it does call and ring through 4g no problem. Something on the phone is putting hangouts to sleep or terminating it when on wifi. I have all the setting enabled that force the app to stay awake but they arent doing anything.
Update:
Did some more testing and found out more information. If the phone is plugged in, it will ring without any issues. Even if its been sleeping for 30min+.
To summarize:
Hangouts when phone on wifi - Does not ring when sleeping
Hangouts when phone on wifi and plugged in - Rings when sleeping
Hangouts when on LTE/3G - Rings when sleeping
Makes me think there is a bug in the actual stock rom that kills apps when sleeping when it shouldnt?
Update2:
Installed Xposed and App Settings and enabled "Stay resident in memory" on hangouts. Left phone for a bit and called and it did ring. Leaving it alone for another 30 min or so and will test again.
Update 3:
I believe I have fixed the issue with the method in update 2. Been calling my phone randomly and it did ring 100% of the time. Glad I fixed it. Going to leave some tags for people googling this issue since it's pretty major(tons of posts about it on google forums). Will keep this post updated if the issue is not solved. Will keep testing throughout the day.
Tags: Google Hangouts not ringing, Hangouts not ringing
Click to expand...
Click to collapse
Whenever i call it always rings. Doesn't matter if screen is on or off. May be just a coincidence. When others call sometimes it rings, sometimes, doesn't, sometimes 1 short ring then nothing. I thought it's my FIWI connection. I connect to xfinity hotspot directly. Sometimes quality of signal changes. Thought maybe when wifi signal degrades it interferes with the phone.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
divineBliss said:
All my testing is with WiFi on and mobile data off.
I had cases where I could kill Hangouts, put the phone to sleep, call it, and Hangouts would ring. Then sometimes it would ring for a fraction of a second, but the screen would show an incoming call was still in progress. Then other times it would not ring at all. Again, I preceeded each test by killing/force stopping Hangouts first. Weird inconsistent unexplainable results .
Click to expand...
Click to collapse
same here
guest_2011 said:
Yes sometimes it rings, sometimes doesn't, sometimes rings one time then stops. Seems random.
---------- Post added at 05:45 PM ---------- Previous post was at 05:26 PM ----------
Whenever i call it always rings. Doesn't matter if screen is on or off. May be just a coincidence. When others call sometimes it rings, sometimes, doesn't, sometimes 1 short ring then nothing. I thought it's my FIWI connection. I connect to xfinity hotspot directly. Sometimes quality of signal changes. Thought maybe when wifi signal degrades it interferes with the phone.
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
same here
Click to expand...
Click to collapse
Ya see for me, it doesnt matter if I call or someone else calls, if the phone is sleeping it doesnt ring. Hopefully this fixes it as I will try throughout the rest of the day. I know its not my wifi since I have multiple phones in the house and they work perfectly (hangouts) except this one.
Related
Not the main reason for this post, but first I'd like to mention that I've noticed I'm unable to send long texts when i'm in 1x. I think this is an EB01 issue because I vaguely recall seeing a post about that. Am I correct on this?
Anyways, the main point of my post. I use delivery confirmations, and typically I'll send a text, lock my phone, and a few seconds later the screen will come back on, show the delivery in the notification bar, and then go off again a few seconds later. But sometimes, often enough to notice, I'd say several times a day, I'll lock my phone, and I own't get the delivery report. Then say, 5 minutes later, when I push the power button on the phone to wake it up, the delivery report immediatly pops up, and whatever the person may have texted me back will then pop up too. I'm receiving no notification of the delivery, OR the sms I receieve from the person, until I wake my phone up.
Is anyone else experiencing this? Is this an EB01 issue, or something with Sc?
You disabled retrive option in message settings....
jenisiz said:
You disabled retrive option in message settings....
Click to expand...
Click to collapse
Huh? You mean Auto Retrieve for MMS? That's not even what the post is about. And if it were, I wrote that problem is intermittent, sometimes it happens, sometimes it doesn't, so changing a setting "on" or "off" probably wouldn't be the solution. But yes, MMS auto retrieve is, and always has been, on.
Did you clear your user data and cache after you loaded SC?
Dewmgaze said:
Huh? You mean Auto Retrieve for MMS? That's not even what the post is about. And if it were, I wrote that problem is intermittent, sometimes it happens, sometimes it doesn't, so changing a setting "on" or "off" probably wouldn't be the solution. But yes, MMS auto retrieve is, and always has been, on.
Click to expand...
Click to collapse
Actually that is what this post was about...often when people switch to another sms app they switch that off. When that is switched off, you will not receive texts (regular and mms) until the phone is "awake". I'd attempt downloading another sms app and seeing if the results are the same.
Yes, I wiped data AND cache. And auto retrieve is on. The problem doesn't happen all the time, maybe like once ever couple hours I'll notice it.
Dewmgaze said:
Yes, I wiped data AND cache. And auto retrieve is on. The problem doesn't happen all the time, maybe like once ever couple hours I'll notice it.
Click to expand...
Click to collapse
Dew, try go sms and see if it works any different. Only time I've seen this is when the settings I mentioned are turned off or when the phone loses all service in sleep mode.
jenisiz said:
Dew, try go sms and see if it works any different. Only time I've seen this is when the settings I mentioned are turned off or when the phone loses all service in sleep mode.
Click to expand...
Click to collapse
Just did it again today. Sent a text to my gf, locked my phone. Never got the beep for the delivery, or her reply. Soon as I unlock it a few min later, both come through. Also, the text will have the current time on it, which does make it feel like the phone is losing service while sleeping. However, the speed at which the delivery and subsequent text alerts come through is near instant, < 1 second after the unlock screen appears, so it's as if the phone recieved them, but choose to act as if it hadn't.
As for trying another SMS app, that's not really a solution for me, I'm pretty happy with, and used to, the stock msging app.
Im not suggesting you keep it...i'm saying to see if it's a continuous problem. you don't even have to use the other app...u just want to see if it notifies.
I have the eb01 with 2.4 and I dont have that issue. Try reflashing 2.4
Sent from my eb01 super fast fascinate
jenisiz said:
Im not suggesting you keep it...i'm saying to see if it's a continuous problem. you don't even have to use the other app...u just want to see if it notifies.
Click to expand...
Click to collapse
Giving it a whirl, will report back tomorrow sometime.
If you want to run a logcat, I can tell you if I have the same issue. I'm trying to hunt down a solution and I'm going crazy, but I know exactly what it looks like.
Okay, so I'm still having the same issues with Go sms. The phone will be locked, and when I unlock it say, 5 to 10 minutes later, the delivery reports pop up, the stock sms and go sms notifications pop up, and the times on the texts will be the current time, as if they were just recieved.
I too am having this issue. Any solution yet?
Is everyone who is having this issue running SC ????
Reason I ask is cause I'm not, and haven't seen this problem, at all, ever.
mexiken said:
Is everyone who is having this issue running SC ????
Reason I ask is cause I'm not, and haven't seen this problem, at all, ever.
Click to expand...
Click to collapse
I'm running sc 2.4 on a verizon modem using a custom sprint/cricket prl. No problems here. As stated before, I only received this problem when I accidentally toggled with the retrieve settings. I switched them back and have been using chomp happily.
mexiken said:
Is everyone who is having this issue running SC ????
Reason I ask is cause I'm not, and haven't seen this problem, at all, ever.
Click to expand...
Click to collapse
I'm running SC 2.4 and I have only seen this issue once so far, that being this morning. I rebooted and haven't had it happen since. I haven't ever had this happen before using SC 2.4.
So I've been using the Nexus S for about one month now, my very first smartphone. Discaimer: I'm a NOOB to the core. I never rooted my phone, never thought of it.
I'm pulling my hair out at the following long list (and counting) of bugs and glitches I've noticed with my phone:
1) Menu settings randomly change (including ringtones)
2) screen doesn't turn off automatically, even though I have set screen auto off to 30 seconds. (this one is somewhat "dangerous" as I leave my phone in the bag and don't check it for a while, and later notice that my screen has been left on the whole time, draining my battery)
3) cannot make outgoing calls. I don't get outgoing ringing when I try to make outgoing calls. Also, during this time, the phone did not ring when there was an incoming call
4) pictures in the gallery come and go
5) The list of apps I downloaded disappear from "my apps" list in Android market
6) when I select a call from the call log, the phone dials a different contact
7) after using airplane mode, turning off airplane mode does not restore signal and 3G data
What's very frustrating is that all of these bugs seem to come and go randomly, without any "patterns" or "triggers." I've restarted the phone, and the issue I was having seems to go away, only to lead to another one a while later. I am wondering if any of these issues are known problems. Also, are these problems more likely to be software or hardware issues?
I'm running
Android 2.3.4
Baseband version I9020AUCKD1
Kernel version 2.6.35.7-ge382d80
Build number GRJ22
on Fido network in Canada.
Thanks
I'm having difficulty taking you seriously because of your username.
SComp23 said:
I'm having difficulty taking you seriously because of your username.
Click to expand...
Click to collapse
+9000
Sent from my Nexus S 4G using Tapatalk
SComp23 said:
I'm having difficulty taking you seriously because of your username.
Click to expand...
Click to collapse
Lol
Sent from my Nexus S using XDA App
No. 3 alone will qualify for a refund or exchange.
Sent from my Nexus S using XDA App
Hahahahhahw
Sent from my Nexus S 4G using XDA Premium App
SComp23 said:
I'm having difficulty taking you seriously because of your username.
Click to expand...
Click to collapse
Hahahaha true that.
Sent from my CM7 powered Nexus S 4g using XDA Premium App
You know, half the time i wouldn't even take note of the OP username and just go ahead and try to help, but you caught on to something here. Oddball username, 1 post and very unusual (really far out) problems/issues...
hmmm
1) Menu settings randomly change (including ringtones) - Probably user error. Or you're using apps that keep conflicting with your setup.
2) screen doesn't turn off automatically, even though I have set screen auto off to 30 seconds. (this one is somewhat "dangerous" as I leave my phone in the bag and don't check it for a while, and later notice that my screen has been left on the whole time, draining my battery) - Manually turn screen off after a given set of time, chances are, your bag is pressing up against the phone when you place it in and the phone keeps pressing buttons (My guess).
3) cannot make outgoing calls. I don't get outgoing ringing when I try to make outgoing calls. Also, during this time, the phone did not ring when there was an incoming call - I had this problem before, are you using Google Voice with integration?
4) pictures in the gallery come and go - Depends on the size of the images, the phone can only read so much data from SD card at a time. I assume you're not giving it enough time to load everything or you have a .nomedia file somewhere that's hiding your pictures from being shown.
5) The list of apps I downloaded disappear from "my apps" list in Android market - It's a known bug with some Market builds. Downloading another app or giving it a minute will usually fix the problem.
6) when I select a call from the call log, the phone dials a different contact - This is weird. Do you have a custom dialer app from the market that may have this bug? I played with my phone out of box a few days and nothing like this happened.
7) after using airplane mode, turning off airplane mode does not restore signal and 3G data - If you're in a weak signal area, it can take longer to gain 3G back. If it doesn't come back within 2 minutes, I suggest a reboot. I also suggest doing a profile update, PRL update, and firmware update (as Google has sent an OTA with bugfixes) to see if these problems can be fixed.
The only bug I experienced since I've got my Nexus S is that the Screen won't respond for a little while after unlocking my phone.
I didn't had the time yet to analyze the problem more detailed, maybe this also happens due to a specific widget? I don't know. I got a lot of them all over my four different home screens.
No response from OP yet people continue to respond. I think the fecal fan has left the building.
Sent from my Nexus S 4G using Tapatalk
Judging by the quality of the posts in this thread, I find it rather ironic that I'm being accused of being a troll. First time posting and where is the love?
I will respond to pretty much the only useful reply I got in this thread so far.
Overstew said:
1) Menu settings randomly change (including ringtones) - Probably user error. Or you're using apps that keep conflicting with your setup.
Click to expand...
Click to collapse
Please define what you mean by "user error." I don't know of any apps that can change the global notification ringtone.
Overstew said:
2) screen doesn't turn off automatically, even though I have set screen auto off to 30 seconds. (this one is somewhat "dangerous" as I leave my phone in the bag and don't check it for a while, and later notice that my screen has been left on the whole time, draining my battery) - Manually turn screen off after a given set of time, chances are, your bag is pressing up against the phone when you place it in and the phone keeps pressing buttons (My guess).
Click to expand...
Click to collapse
Nope. The same thing happened when my phone was sitting face up on my desk.
Overstew said:
3) cannot make outgoing calls. I don't get outgoing ringing when I try to make outgoing calls. Also, during this time, the phone did not ring when there was an incoming call - I had this problem before, are you using Google Voice with integration?
Click to expand...
Click to collapse
No I'm not using GV.
Overstew said:
4) pictures in the gallery come and go - Depends on the size of the images, the phone can only read so much data from SD card at a time. I assume you're not giving it enough time to load everything or you have a .nomedia file somewhere that's hiding your pictures from being shown.
Click to expand...
Click to collapse
Nexus S does not have an SD card slot AFAIK. I gave it plenty of time to load everything. I wouldn't expect my phone to require 5 minutes to load pictures. I own a smartphone, not a 486. On reboot, some pictures show up that weren't in the gallery before. After subsequent reboot, some other random pictures disappear.
Overstew said:
6) when I select a call from the call log, the phone dials a different contact - This is weird. Do you have a custom dialer app from the market that may have this bug? I played with my phone out of box a few days and nothing like this happened.
Click to expand...
Click to collapse
No.
Overstew said:
7) after using airplane mode, turning off airplane mode does not restore signal and 3G data - If you're in a weak signal area, it can take longer to gain 3G back. If it doesn't come back within 2 minutes, I suggest a reboot. I also suggest doing a profile update, PRL update, and firmware update (as Google has sent an OTA with bugfixes) to see if these problems can be fixed.
Click to expand...
Click to collapse
I understand 3G can take longer, but it seems fishy that my cell signal doesn't come back. I waited more than 2 minutes and I ended up HAVING to reboot (twice in fact) to get both 3G and cell reception back.
Oh yeah, just yesterday, I experienced my first encounter with the mythical "search button of death" bug. Yay.
perform a hard reset and it should be fine
could just be u got a bad phone. i've never had or heard of any of those issues on the forums. your factory warranty is good for a year.
Dude what the f**k is up with your username??? god damn what the hell is wrong with people...
the only error that has been reported is the images missing. the rest are probably your fault or you're doing something wrong. if you love **** so much go buy the iPhone
derekwilkinson said:
Dude what the f**k is up with your username??? god damn what the hell is wrong with people...
the only error that has been reported is the images missing. the rest are probably your fault or you're doing something wrong. if you love **** so much go buy the iPhone
Click to expand...
Click to collapse
Watch out all gamer is going to give you an infraction for that one
Sent from my PC36100 using XDA Premium App
derekwilkinson said:
Dude what the f**k is up with your username??? god damn what the hell is wrong with people...
the only error that has been reported is the images missing. the rest are probably your fault or you're doing something wrong. if you love **** so much go buy the iPhone
Click to expand...
Click to collapse
Dude might just have a scat fetish. It is not up to us to judge one's idiosyncrasies. Heaven loves us all the way we are.
** goes into a corner and snickers uncontrollably in stitches **
ilovefeces said:
1) Menu settings randomly change (including ringtones)
Click to expand...
Click to collapse
Yes this happens. BUT.... only when you mount the phone via USB and do not disconnect it properly. The phone doesnt have time to scan for your set ringtones, and therefore defaults it to some random mp3 or whatever.
ilovefeces said:
4) pictures in the gallery come and go
Click to expand...
Click to collapse
Due to what i said above as well. This is a HUGE bug.
Every other problem you have is either user-error or an issue from your telco.
Have you done a factory reset of the phone? You may even have a virus. Just read somewhere that Android is the most targeted platform for them as of now.
Hi all, I have two Nexus 4 and I have this problem with both of them. I have got install Viber, Skype and Hangout and this happens with all of them. Basically if my phone is on standby and someone calls me on Hangout (lets say) then on the other person's phone it will show that its ringing but on my phone it wont ring until I wake the phone (by pressing the power button). This only happens if my phone is connected to wifi. My brother has HTC one x and I tried calling him on Hangout and it worked for him. This isnt an issue which occurs only a few times but it happens every time. Same story for Skype and Viber.
Any idea what can be going wrong? This issue is really irritating! I have a feeling this issue has something to do with power saving. The reason I say this is because if my phone is connected to the wall charger and is on standby, it still receives calls perfectly. The issue only occurs when on battery (not connected to wall charger).
Please help
saudkhan said:
Hi all, I have two Nexus 4 and I have this problem with both of them. I have got install Viber, Skype and Hangout and this happens with all of them. Basically if my phone is on standby and someone calls me on Hangout (lets say) then on the other person's phone it will show that its ringing but on my phone it wont ring until I wake the phone (by pressing the power button). This only happens if my phone is connected to wifi. My brother has HTC one x and I tried calling him on Hangout and it worked for him. This isnt an issue which occurs only a few times but it happens every time. Same story for Skype and Viber.
Any idea what can be going wrong? This issue is really irritating! I have a feeling this issue has something to do with power saving. The reason I say this is because if my phone is connected to the wall charger and is on standby, it still receives calls perfectly. The issue only occurs when on battery (not connected to wall charger).
Please help
Click to expand...
Click to collapse
This is a common issue for our beloved Nexus 4, when the screen is turned off , after a few minutes, WIFI will too, that's why we can't receive the call. Hope Android 4.3 will fix it. Or you can follow this topic http://forum.xda-developers.com/showthread.php?t=2102986, it fix temporally.
Just check the advanced wifi settings
put wifi always on.
Search... its there
---------- Post added at 08:27 PM ---------- Previous post was at 08:23 PM ----------
Settings -> Wi-Fi -> lower right menu -> Advanced -> Keep Wi-Fi on during Sleep = Always
nguyen47 said:
This is a common issue for our beloved Nexus 4, when the screen is turned off , after a few minutes, WIFI will too, that's why we can't receive the call. Hope Android 4.3 will fix it. Or you can follow this topic http://forum.xda-developers.com/showthread.php?t=2102986, it fix temporally.
Click to expand...
Click to collapse
Thank you so much! I tried what was mentioned in the link and it works now. I really hope google resolves this issue in 4.3. This makes me think how much is the OS actually tested before sending it out in the wild.
muldy said:
Just check the advanced wifi settings
put wifi always on.
Search... its there
---------- Post added at 08:27 PM ---------- Previous post was at 08:23 PM ----------
Settings -> Wi-Fi -> lower right menu -> Advanced -> Keep Wi-Fi on during Sleep = Always
Click to expand...
Click to collapse
I tried what you suggested but unfortunately it didnt work. nguyen47's suggestion worked
PS: i am not liking this new users restriction. Why do i have to wait 5 mins between posts!
I have a Canadian Rogers Galaxy Note 3 (SM-N900W8) running the latest software update (as of last night).
Any time I dial someone's number, there is a full 10 to 15 seconds delay/lag before the phone 'reacts' and starts to actually make the call. This lag/delay happens regardless if I am:
using speed dial (though it is especially obvious then)
manually dialling a number
sliding to the right on a person's contact (quick dial)
pressing and holding on a contact's number to dial
I've tried adjusting the Google Sync settings, turning on/off the "Sync People details" as well as my Samsung account's "Sync contacts". I've disabled Facebook/Linked In "Sync Contacts", based on my theory that there was some sort of hiccup being caused by these apps' attempts to pull data on the contact immediately upon me placing the call.
The other issue is that Contact photos/names are also severely delayed when receiving an incoming call, for example when my phone starts ringing, all that I can see is their phone number at the top of the screen (almost as if it's the 'raw' cellular data), and not their name or picture (as normally would immediately appear on say my Galaxy S 3).
I've searched all over but have yet to see this issue pop up. This seems really strange. Any ideas or solutions?? Thanks!
Edit: I tried a second battery pull and hard restart and this seems to have fixed the issue for now. Weird!
If it's any consolation, it's not just your Rogers Note 3. I'm having the same issue with the Note 3 made for T-Mobile USA. I'm going to try the battery pull like you suggested and see if that resolves the issue, as well as some alternate dialers. I'll post my luck once I've tried this.
kamandor said:
Edit: I tried a second battery pull and hard restart and this seems to have fixed the issue for now. Weird!
Click to expand...
Click to collapse
I have found this problem (delay dialing) for 2 weeks.
When I connect to internet, by wifi or mobile data, it is corrected. But whenever the internet connection is disconnected , it apears.
I'm disappointed from Note 3 because of lots of bugs that has got especially after update to kitkat
-delay dialing
-not working any auto call recording app.
-not working properly it's sensors.
And etc
Same bug here. 4.2.1. Phone was fine, never used to do it. randomly started doing this around the same time as I started getting multiple duplicate sms messages. Dialing delay goes away when wifi is on.
Very annoying. I'm open to suggestions!
Shaunuss said:
Same bug here. 4.2.1. Phone was fine, never used to do it. randomly started doing this around the same time as I started getting multiple duplicate sms messages. Dialing delay goes away when wifi is on.
Very annoying. I'm open to suggestions!
Click to expand...
Click to collapse
At least 150MB of phone memory should be free..
Else, it'll lag..
I removed a few apps and now am having 200MB of free space on my Phone Memory (internal), and there are no lags..
Phone is running smooth..
StaticBlaze said:
Atleast 150MB of phone memory should be free..
Else, it'll lag..
I removed a few apps and now am having 200MB of free space on my Phone Memory (internal), and there are no lags..
Phone.is running smooth.
Click to expand...
Click to collapse
Thanks for your reply! I have 1.1gb RAM free pretty much all the time, 1.18GB ROM free, and 20.99GB internal SD free.
Not sure this is the problem.
I got the same problem and i realized after i read this post that it doesnt happen if im connected with wifi. There should be a way to fix this, its a 500euro phone there shouldnt be such problems...
Had the same problem with a Samsung Relay, after a few updates. Had a chat with Samsung, after a hard cache clearing left me with the option to factory reset. Which I'm not very interested in. Uninstalled a lot of applications, then by chance connected to the wifi and sent an email. After that, it seems to be working now.
Didn't fix the problem for more than a few hours. Actually I believe hooking on wi-fi did it, because I connecting again this morning solved the problem again.
I installed a firewall and denied permission for all apps, let's see if this works...
No, the firewall doesn't work.
After connecting on wireless it works for about 3-4 hours. Then again bull**** happens. Don't know why, but this relation is interesting. There is no actual traffic sent form the device, since the firewall blocks a lot of the system bull**** apps from communicating, but after enabling it it works.
I see that enabling wireless even for a short while (3sec) is enough to get it back on track. Why might this be so?...
Prey
Factory reset, reinstall everything, then encryption. 4 hours. Tested during the procedure to see if it dials fast. It dialed, until the end, when it started to have the same problem again.
Then I got the wonderful idea from above to check if there is something wrong with Prey. A software to block your phone if it's stolen. And guess what, as long as it's not connected to the Internet, it hangs and won't open. Maybe this was creating the problem? Don't know, but for now I uninstalled it and it seems to be working. I remember it did an update before the problem occurred, maybe the update is the problem? Will write again if the problems persists.
Cross-referencing this thread on Prey:
https :// help.preyproject.com/topics/ android-call-delay-caused-by-prey
(sorry, as a new user I can't post outside links, so you must correct the URL above)
Seems I'm having the same issue on two of my Prey-enabled devices (HTC One X+ and HTC One X) after upgrading to latest version. Happens with Data-off.
norenendur said:
Factory reset, reinstall everything, then encryption. 4 hours. Tested during the procedure to see if it dials fast. It dialed, until the end, when it started to have the same problem again.
Then I got the wonderful idea from above to check if there is something wrong with Prey. A software to block your phone if it's stolen. And guess what, as long as it's not connected to the Internet, it hangs and won't open. Maybe this was creating the problem? Don't know, but for now I uninstalled it and it seems to be working. I remember it did an update before the problem occurred, maybe the update is the problem? Will write again if the problems persists.
Click to expand...
Click to collapse
Anyone else find that every once in a while you'll call someone and won't be able to hear anything and they won't hear you until you call them back? Happens when I call out from time to time. Very frustrating.
Tried wiping dialer data. Also tried reinstalling app updates from the play store, no change.
xxBrun0xx said:
Anyone else find that every once in a while you'll call someone and won't be able to hear anything and they won't hear you until you call them back? Happens when I call out from time to time. Very frustrating.
Tried wiping dialer data. Also tried reinstalling app updates from the play store, no change.
Click to expand...
Click to collapse
If you're on sprint I've been having the same issues.
Sent from my Essential PH-1 using Tapatalk
AxxPyrtlexx20 said:
If you're on sprint I've been having the same issues.
Click to expand...
Click to collapse
I'm actually on ATT, which means it's probably not carrier related. Wonder if anyone knows of any alternate dialers that would work? Could see if it's app related or driver related.
I've done this but found my phone was on mute. Next time it happens check to see if that's the case. I think maybe it is easy to hit with your face?
I had the same issue but it would work with some numbers and not with others. I found a setting under the caller that was turned on for hearing aid support. Once I turned that off, it seems that my issues have gone away.
10 hours into the phone (got mine this AM) and I like the device but still not a fan of the camera, even with the Google camera port. Some things essentially (intentional) seem half baked or not thought completely through.
I just downloaded the MS Launcher and I have to say, I like it a lot. I'm considering keeping that the stock launcher.b
Same issue, my face it's the mute button all the time.
Happened twice in a day, I had to reset everything and still same if I restore all apps from back and/or if I connect my phone to car bluetooth --> safe unlock.