. I'd like some help to try and find a solution to this problem. It seems all instant messenger apps have very delayed messages most of the time.
Gtalk & Google+ messenger- are extremely unreliable for me. Up until about 3 months ago they worked flawless, I'd get notified of a message as soon as it was sent, be it on 4G or Wi-Fi. Now, 90% of the time I'll only get the message if I go into the app. And yes all settings and notification settings are turned on to sync. Sending is never an issue. And if I stay in the application messages are pretty reliable although not 100% reliable. I will get instances where it won't receive messages even when I'm in the app. My cell reception and router is always near perfect reception.
Whatsapp messenger more reliable in that messages will come through within a half hour if they aren't coming through. Although if I'm in the app its quite flawless. This app is much more unreliable when on Wi-Fi. With 4G its actually reliable. What I do notice though when going into the app with Wi-Fi and its not syncing up is that the up arrow on Wi-Fi will be flashing but no down arrow. Once the down arrow begins turning on everything works.
To note is that I have tried switching to a stock rom to no help, same things happen. Tried uninstalling all these apps, and done a clean install, still no help. I have other phones in the house, a galaxy S, and these apps all work the way they should on both 4G and Wi-Fi. So I know it should and can work. All my emails from Gmail come through just fine as do my Google+ notifications from people replying on posts. So any help will be greatly appreciated as I want to get to the bottom of this. Currently running on CM9 stock kernel, with uglc1 modem and newest boot loader.
Anyone? I can't be the only one with this issue...
I am having this problem on the stock radio, UGLC1, and XXKK6 too
I think its something updated within the Google Talk apps?
I started having the same issue after the OTA 4.0.4 came out.
Has anyone resolved this?
from what i have seen, its the google push service (used from gtalk, gmail, whatsapp, and every push app) that sometimes do some sleep..had this on my previous device also sometimes
when people say "before was working" "now is not working well anymore" it depends from how much attention u give to it...
the push service require a constant connection to the google services, sometime this connection hang or stops, usually after 10 minutes i can see this connection is restored and chat messages, mails, etc, come all together (or if u dont want to wait, disable and enable the conenction again, or disable/enable synch)
edit: SOLUTION here http://forum.xda-developers.com/showthread.php?t=2142503
I've had this problem for almost a year now.. Ever since I went from iOS to Andriod.. On my HTC.. What I noticed is when my phone goes into sleep it's all over, I guess it falls into a deep sleep.. When I awake it all message from all messengers comes flooding through. I thought maybe it was a software problem and all problems would disappear after upgrading to android 4.0 from 2.3.. But still the same.. Same as you everything works fine when the phone is alive, wifi or 3G.. So I was thinking its HTC and about to upgrade to Samsung S111 so touch wood that works ok..
online4yourmind said:
I've had this problem for almost a year now.. Ever since I went from iOS to Andriod.. On my HTC.. What I noticed is when my phone goes into sleep it's all over, I guess it falls into a deep sleep.. When I awake it all message from all messengers comes flooding through. I thought maybe it was a software problem and all problems would disappear after upgrading to android 4.0 from 2.3.. But still the same.. Same as you everything works fine when the phone is alive, wifi or 3G.. So I was thinking its HTC and about to upgrade to Samsung S111 so touch wood that works ok..
Click to expand...
Click to collapse
My nexus 4, does the same thing.. ANNOYING!
Just got the Samsung Galaxy S3 for T-mobile and have been experiencing a few strange issues with general call quality. About 2 or 3 mins into a call via wifi-calling, sound from the other side will just cut out. The call is still connected and I am then forced to hang-up and redial. This has happened already on 3 separate occasions. Calls off wifi-calling did not experience this issue albeit I could hear an echo of myself =(. Redialing and asking the other party to call me did not resolve the echo issue. The other party did not hear the echo.
Anyone else experiencing these types of issues or know of any fixes? Since it's only my first day with the phone, I'm hoping these are only fluke occurrences...
Yeap has happened to me calling out of town and in town numbers. Sounds like a dead line, and then when u talk u get an echo. I was advised by the people on the other line that they could hear me. This has happened while on the network due to I don't use Wi-Fi calling.
Sent from my SGH-T999 using xda premium
Anyone else have any wificalling issues?
My issue is more on loosing connection to the server while the phone is in asleep. the wifi connection is not lost just the connection to the server is lost and then my battery gets lost on locating connection.any ideas on that ?
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
moonfire711 said:
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
Click to expand...
Click to collapse
word for word same issues im having, also 2 different routers.:crying:
Although I am not certain if this problem exited before rooting and flashing my phone, my WiFi Calling has not been working. I can place the call, but I cannot hear it ring or hear anything when calling. I can receive calls, but once I answer, I cannot hear anything. I am able to receive text messages normally.
I have resorted to switching to the cellular preferred only option. I hope there will be a remedy for this issue.
I'm on the FreeGS3 R3 rom with stock kernal.
d0gan said:
Just got the Samsung Galaxy S3 for T-mobile and have been experiencing a few strange issues with general call quality. About 2 or 3 mins into a call via wifi-calling, sound from the other side will just cut out. The call is still connected and I am then forced to hang-up and redial. This has happened already on 3 separate occasions. Calls off wifi-calling did not experience this issue albeit I could hear an echo of myself =(. Redialing and asking the other party to call me did not resolve the echo issue. The other party did not hear the echo.
Anyone else experiencing these types of issues or know of any fixes? Since it's only my first day with the phone, I'm hoping these are only fluke occurrences...
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
justice26 said:
Yeap has happened to me calling out of town and in town numbers. Sounds like a dead line, and then when u talk u get an echo. I was advised by the people on the other line that they could hear me. This has happened while on the network due to I don't use Wi-Fi calling.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
moonfire711 said:
I normally use wifi calling, but today at work and at home (so two different connections and two different routers) I tried to answer an incoming call, but the caller could not here me. I pressed the end button, and the dialer froze for about a minute before saying the dialer stopped responding and requested me to close it. Tested several more times before wiping my phone and reloading my rom fresh. Did the same thing afterwords. Then I turned off wifi calling and the normal network calling worked fine. Maybe a tmo server issue?
Click to expand...
Click to collapse
What Rom are you using? Im trying to conclude that the issue might be with the [ROM][GSM]{7.8.2012} Team Sonic Presents FreeGS3 R3 (Special FiveOhFox Edition).....I have noticed a few people in this thread have the issue using that ROM
I am running Whitehawks STOCK TVALUEM999 ROM with none of these issues. I am only on wifi as thats all I have available and I do not have an issues. It's possible that the removal of all the T-Mobile Bloatware, or some Mods done could be causing this. I have great battery life on that ROM and everything works fine. I am excited about this ROM, but am waiting to see another release come out and see how that works. ALSO, get ROM Manager, update to the newest CWM and try a data/dalvick cache, factory reset and install from zip from internal SD. Let me know how that works out
I use Wi-Fi calling exclusively when I'm at home. I'm rooted but still using Touchwiz.
I haven't had any echo problems. I think the quality overall is pretty bad though. For lack of being able to think of anything better atm, I'll just say it sounds rough. It was something that really bothered me at 1st, but I guess I'm kind of getting used to it. There are times I've thought the call was lost bc the call becomes so silent (clear and empty), but after a moment, I can hear them again and the call continues.
My husband switched over to T-Mobile about two weeks before I got the S3 and switched over from Verizon. While using the Wi-Fi calling, I've lost a call or two so far. My husband, who has an HTC One S, has also lost a call or two and he thinks the quality of his calls are fairly poor also.
I'm wondering if it's not necessarily a S3 thing, but perhaps a T-Mobile thing???
That being said... There are times he has full Wi-Fi bars and I have barely anything, and when I check the signal my laptop is getting, that's full as well. When I check the Battery from Settings, I always only have a yellow bar that is frequently dotted with sections of red.
The Wi-Fi issue, whatever the hell it is, is really the only bummer about the phone for me.
rowan fire said:
I use Wi-Fi calling exclusively when I'm at home. I'm rooted but still using Touchwiz.
I haven't had any echo problems. I think the quality overall is pretty bad though. For lack of being able to think of anything better atm, I'll just say it sounds rough. It was something that really bothered me at 1st, but I guess I'm kind of getting used to it. There are times I've thought the call was lost bc the call becomes so silent (clear and empty), but after a moment, I can hear them again and the call continues.
My husband switched over to T-Mobile about two weeks before I got the S3 and switched over from Verizon. While using the Wi-Fi calling, I've lost a call or two so far. My husband, who has an HTC One S, has also lost a call or two and he thinks the quality of his calls are fairly poor also.
I'm wondering if it's not necessarily a S3 thing, but perhaps a T-Mobile thing???
That being said... There are times he has full Wi-Fi bars and I have barely anything, and when I check the signal my laptop is getting, that's full as well. When I check the Battery from Settings, I always only have a yellow bar that is frequently dotted with sections of red.
The Wi-Fi issue, whatever the hell it is, is really the only bummer about the phone for me.
Click to expand...
Click to collapse
I am not sure if what to tell you, but I am in Afghanistan with the Samsung GS3 rooted, and I do not have a single issue with call quality with some of the crapiest internet connections you can ask for.. No echo, no dropped calls. Your internet connection quality can make a difference, when you make phone calls, any downloads going on can hinder the quality, also the type of router u have makes a difference. A wireless N router with 300MBS per second would be ideal...
It doesnt matter if your are using Touchwiz, the rom you are using matters, no other threads are stating this issue. I suggest you try another rom like redruM cause he just released a new update today, or Whitehaws STOCK. It performs great and has CIQ removed, zipalign on boot, some T-Mobile bloat removed, no force closes on any apps and good battery.. It doesn't have the crazy scripts and 4 in 1 reboot, however, if u dont care about that and you want stable and root, its a good option
According to T-Mobile technical support, they have escalated the issue of wifi-calling and wifi connectivity issues to Samsung and supposedly there is a team working on this. Supposedly they will be doing an over the air update.
it doesn't seem like a lot of us is having this problem, could it be the phone itself? i was fine until a couple of days ago. now i am having the same problems as some in this thread; i can hear them but they can't hear me. sometimes it freezes when i answer the call. now i'm thinking if rooting (phone is rooted only) was a probable cause, and if i should do a nandroid restore or system reset??
No wi-fi calling
MMakoto said:
it doesn't seem like a lot of us is having this problem, could it be the phone itself? i was fine until a couple of days ago. now i am having the same problems as some in this thread; i can hear them but they can't hear me. sometimes it freezes when i answer the call. now i'm thinking if rooting (phone is rooted only) was a probable cause, and if i should do a nandroid restore or system reset??
Click to expand...
Click to collapse
TMo - GS3
My phone is and has not ever been Rooted. I'm having the same issue that when wi-fi calling is active, if I receive a call, the caller cannot hear me, and then the app. hangs for a minute when I hit end or the caller hangs up. I tried it on a couple networks. I thought I was able to make wi-fi calls, but that seems to not work all the time, either.
I believe this is the first TMo ICS phone, right? I had a 4.0.3 custom (Passion) ROM on my Vibrant (GS1), but since there wasn't ICS TMo phone, there was no wi-fi calling app. on it.
I called T-Mo support and told them I found this thread with other users with the same problem, but they didn't say anything was in the works. Samsung support gave me their usual answer, of doing a factory reset, reinstalling and reconfiguring everything (yeah right).
I get the hang sometimes and I also get the problem of people not being able to hear me when I pick up. Annoying. I got rid of my amaze after the ICS update because it screwed up wifi calling(delay in voice 5-10sec). Piss poor. Wish it worked better because I don't get a cell signal in my house.
To get rid of the voice echo - disable the noise cancelation during a phone call in the in call menu. The noise cancelation uses two mics but unfortunately picks up the noise of the speaker as well, causing the echo effect.
when i first got my s3 i had the wifi calling on and i'd miss calls. people said that it didn't even ring just went right to voice mail. on the occasion that a call actually went through people couldn't hear me and for me they cut in and out. i gave up and stopped using it.
when i bought the phone i was told that when on wifi calling the minutes didn't count against my plan, but reading the manual i got the impression that they did. which is correct?
jknakes said:
when i first got my s3 i had the wifi calling on and i'd miss calls. people said that it didn't even ring just went right to voice mail. on the occasion that a call actually went through people couldn't hear me and for me they cut in and out. i gave up and stopped using it.
when i bought the phone i was told that when on wifi calling the minutes didn't count against my plan, but reading the manual i got the impression that they did. which is correct?
Click to expand...
Click to collapse
You have to have them add the free WiFi calling feature to your plan and then they don't count. Just tell them you want your minutes on wifi to be free. There is no extra charge after they add that code.
Sent from my SGH-T999 using xda app-developers app
I'm having the same issue, wifi calling does not work. No one on the other end when I answer incoming calls. Can't connect out.
For me it works sometimes and sometimes it doesn't I just turn it off, I use 200 minutes so far this month and today is the last day so I'm good with 500 minutes plan
Sent from my SGH-T999 using Tapatalk 2
Did any of you with the wifi calling problem install Skype? My first phone had the problem of no one hearing me and freezing when hanging up. I ended up returning it to Tmobile for another phone.
Right before I returned the old phone I did some testing. I flashed it back to stock and it didn't fix the problem, but when I wiped the data and cache in download mode, it seemed to help with the wifi calling, not sure how consistent it worked, but at least for the first call I can hear them and vice versa.
So I'm thinking something I installed may have played a factor, and right now my suspicion is that it's skype. I haven't installed it on my new phone since I don't want to screw the wifi calling on there.
I upgraded to the Galaxy S III from the Vibrant. I had no problems with my Vibrant making or receiving WiFi calls on the secured WiFi networks at home and at the office. However, I am having serious problems with WiFi calling on the S III.
I can make calls (most of the time) and can send and receive texts in WiFi but I cannot answer a call. The phone either does not ring and the call goes straight to voicemail or I hear the phone ring, answer the call and can hear the other party, but they cannot hear me.
I called tech support who had me do a factory reset. That worked briefly, but within 24 hours, I was back where I started. My 911 location situation is sorted, so that is not the problem. I am also close enough to the routers that I do not believe that is the problem either.
My first suspicion was a bad sim card but another co-worker of mine who also has an S III cannot answer WiFi calls in the office either. Now, I suspect some network security issue is causing the problem on both networks I regularly use, but do not understand why considering my Vibrant had no problems at all.
I, too, cannot hear the other party when answering on Wi-Fi. It worked fine at first but now it doesn't. Anyone know of a fix?
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue running Stock ROM
tiisai44 said:
I, too, cannot hear the other party when answering on Wi-Fi. It worked fine at first but now it doesn't. Anyone know of a fix?
Sent from my T-Mobile Samsung Galaxy S3 16gb Pebble Blue running Stock ROM
Click to expand...
Click to collapse
The other thing that happens when people call me is that the phone will ring once and then go to a busy signal.
I went to a T Mobile store and replaced the sim card. They also made some test calls to my phone without success. I also upgraded the firmware on my home wireless router. In the end, nothing worked and Tech Support is sending me a replacement phone.
My replacement phone arrived and it initially did not work either. After several hours of experimenting and getting results that weren't always easy to duplicate I have reached the following conclusions:
1. There was indeed something wrong with the original phone.
2. Both phones could answer WiFi calls straight out of the box, but as soon as I altered the Setup or downloaded apps, they wouldn't.
3. I strongly suspect that either the power saving settings or the voice cmd for apps settings are incompatible with receiving WiFi calls. I could not determine that any individual app caused a conflict. When I ran into troubles with the replacement phone, I could restart it and get it to work after altering the phone's settings. I never could get the original phone to do so, however.
4. WiFi calling is still wonkier than it should be compared to my Vibrant. I am still getting calls that go straight into voice mail without the phone ringing, or the caller will hear my phone ring once or twice before it goes to a fast busy signal. I at least feel comfortable that if I hear the phone ring I can answer it, where I couldn't do so before.
Hello,
I got an s4 mini about a month or two ago and I had been having a lot of issues. at first I couldn't send mms (noticed this day 1 with the phone) then later on my bluetooth stopped working. I rooted the phone, this is when i lost bluetooth, then about a week later i got the play store connection error. At the time i was using superbeam and apps from other sources as a work around but then adaway was telling me it couldn't reach any sources and i couldn't navigate past google on the internet. This is when I decided to just update my firmware, this solved my internet and playstore connection problem and even mms was working for the first time!(never checked about bluetooth, still using beam). But I still wanted root access for adaway so i followed this guide to install CWM and CM11.
http://forum.xda-developers.com/showthread.php?t=2696260
I was successful and everything is still working well, i can make calls and texts, but for some reason my battery is draining in about half the time it was before, When i look at my locksreen on the bottom most of the time it says "emergency calls only (ROGERS)". Looking at the battery under setting cell standby is right at the top of the list usually at about 34% consumption with 69% time without a signal. So obviously this is where the battery drain is coming from, the weird part is if i go to make a call or send a text or something it picks the signal up as if it had always been there..? I have great cell coverage but the phone is pretending i don't 70% of the time.
does anyone know whats going on with my phone?
Sorry for the long story but I am just looking for some help on this confusing issue, the xd forums seems pretty friendly, please prove me right!
Hello all, I have been using the d2spr for quite some time... without mobile. I have no service on the phone and have no problems using it as an esspresso device like my p5113 tab 2. On my tab two there was a thread about removing the cell from the device, which I will more than likely have to look up again for that device. Is this possible for this phone? Anyone have any experience removing cell from the phone. I have read that searching for signal reduces the battery life, and I have yet to try it on the phone. If anyone can give me any pointers on this would be great. Also if you know which files to delete would save me a crap load of time searching for it.... thanks in advance...
Wizzdome
are you basically trying to use it as a galaxy player? (i.e. an android version of an ipod touch?) if so, ive just put mine into airplane mode and turned wifi on manually. It greatly improves battery life as its not using the cell radio.
youdoofus said:
are you basically trying to use it as a galaxy player? (i.e. an android version of an ipod touch?) if so, ive just put mine into airplane mode and turned wifi on manually. It greatly improves battery life as its not using the cell radio.
Click to expand...
Click to collapse
not exactly I use it as a voip phone and remote control as well as play various games, though there is no service on it, it shows the mobile connection. With the tablet it was a wifi only tab so removing cellular feature from android really increased battery life. Though I was not sure if it would work the same on the d2spr... not quite sure where to start though so thought I would ask, but thanks for the alternative, I am not sure about using airplane and wifi together as I have not tried that before.
wizzdome said:
not exactly I use it as a voip phone and remote control as well as play various games, though there is no service on it, it shows the mobile connection. With the tablet it was a wifi only tab so removing cellular feature from android really increased battery life. Though I was not sure if it would work the same on the d2spr... not quite sure where to start though so thought I would ask, but thanks for the alternative, I am not sure about using airplane and wifi together as I have not tried that before.
Click to expand...
Click to collapse
gotcha. well, if youre using strictly voip, then the airplane mode and then turning wifi back on separately will work very well. like i said, ive done that with other devices and it substantially increases the battery life. Give it a whirl, what can it hurt?
Just an update with the steps on what I did.. as well as the results. With rooted device I deleted the 3 folders telecom, telephone, and another that starts with a tele that I can not think of. They are located in system/priv-app folder on root of system. (Using root explorer) After that I reboot, and all is working fine with no cellular at all. I have been letting it sit just to see how long the battery lasts on standby. So far I am at 28 and a half hours... I still get notifications and wifi works smooth. In the battery section in settings it currently reads charge remaining 8 days. Anyone with no service like me might want to give it a try... if something does not work all you have to do is re-flash what ever rom you had and that will put the folders back. and install cellular on the phone again... I would say that is the number one battery drain of the phone next to the display...
Day seven of my battery test and So far it appears that without cellular on the d2 you can get up to 10 days of standby charge. I did not use the phone at all for anything but to check status. Also, If you notice the small change in the curve, it is because it downloaded updates. It was connected to the internet the entire time...