Skype has never before supported the ability for us to listen to voicemails from our Skype phone #'s on mobile phones(always had to check your vm's from your PC). Now on this Nexus, the Skype app will actually notify me if i have a voicemail and actually allow me to listen to them! (cannot delete them though)
Also, with past phones i was never able to get Skype calls to work via bluetooth... only the standard phone dialer would work. I just tried today for the hell of it with Skype and it's actually working now!... once a call connects though it'll temporarily switch back to phone audio for about 1 second & then correct itself and continue via bluebooth.
I just can't believe these things are actually working finally. No idea if it's because of the Nexus(ICS) or just some Skype update that fixed it, but either way i'm happy.
Yes, but does Skype still drain the battery like nobody's business? I used to have it on my Galaxy S but it would cut battery life in half. Haven't bothered putting it on my GN yet.
ianwood said:
Yes, but does Skype still drain the battery like nobody's business? I used to have it on my Galaxy S but it would cut battery life in half. Haven't bothered putting it on my GN yet.
Click to expand...
Click to collapse
Not since they fixed the issue, I had it running 24x7 on my old SGS, plus you can log out without losing your login details so restarting it is even easier if you really don't want it running all the time.
Skype is working fine. No battery drain here.
. 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!
Hi all,
Posting this here because it's the device in question and no one answered over at general Android Q&A and Reddit hasn't been able to help.
Long time since I posted here but I'm at the limit of what I can effectively do so I'm looking for some help here and I believe this is a problem with the OS itself and how it handles shared settings and even with the Maps application, rather than being device specific.
First, specs:
Samsung Galaxy Nexus (UK HSDPA+) running Jelly Bean 4.1.1, completely stock and unrooted.
Asus Nexus 7 (also UK, though I'm not sure this makes a difference as the N7 has no GSM radio), Jelly Bean 4.1.1, completely stock and unrooted.
All apps are the latest versions.
Background: This problem has only existed as long as I have had the Nexus 7 in addition to the Galaxy Nexus. I'm 90% sure that the issue relates to the fact that I have location reporting enabled on the GNex and NOT on the Nexus 7. I'm signed into both devices with the same Google account. Occasionally one or the other will pick up the opposite one's settings with regards to location sharing, a PITA.
The problem: Ridiculous amounts of wakelocks caused by the Play Store, Maps and the Launcher. As you can see here (BetterBatteryStats pic included). imgur . com/ a/yz83J (I can't post the hyperlink because I've not posted 10 times yet.) This only seems to cause a problem on the Galaxy Nexus. I haven't noticed wakelocks or battery drain on the Nexus 7.
This absolutely drains my battery. If I kill off Play Store and Maps and clear all cache data then the wakelocks stop for a while.
Two days ago I was forced to uninstall all updates to Maps and return it to the default version and update it again as killing the process or even rebooting the phone failed to stop the wakelocks. This didn't stop the wakelocks but out of curiosity I just told the device to completely stop updating my location on it's own. This has completely stopped the wakelocks and the resulting power drain..
The catch: I'd really rather not have to leave location updating off to resolve this. It's only been happening since I got the Nexus 7 and I'm trying to get that to NOT report my location and the GNex to report. The reason I have it turned off is that I have it on train WiFi a lot, which displays my location as wherever the connection terminates. E.g. for an entire journey from London to the north, my history for that day shows that I travelled the distance between every point on the route that my phone reported and London Euston station where the Nexus 7 was connected, in about 1 second. This led to my location history being an utter mess!
The question: Any ideas on getting this working as intended? If I can provide any more data let me know. I've already run an ADB output of my alarm manager stats and it's showing the same as the BetterBatteryStats info.
The apps will constantly try to refresh maybe because it's trying to receive data like notifications.
You can try JuiceDefender or Greenpower or apps like that in order to limit how often a certain app syncs. Some ROMs also have such a feature if i'm not wrong.
If all else fails try a factory reset and see if the problem is fixed. Did you do a full wipe before changing to jb from ics? Maybe that could cause problems.
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
JamesInsights said:
The apps will constantly try to refresh maybe because it's trying to receive data like notifications.
You can try JuiceDefender or Greenpower or apps like that in order to limit how often a certain app syncs. Some ROMs also have such a feature if i'm not wrong.
If all else fails try a factory reset and see if the problem is fixed. Did you do a full wipe before changing to jb from ics? Maybe that could cause problems.
Sent from my Galaxy Nexus (AOKP JB | Popcorn Kernel)
Press the thanks button if my post was helpful
Click to expand...
Click to collapse
Thanks for the reply.
No I did not do a full wipe because the update to JB was delivered OTA when Google released them, these devices are completely stock. I believe the issue is that the GNex is attempting to update the location, the Google account is reading the Nexus 7 setting of not updating the location, then the response is bouncing back to the GNex, which insists it does need to update the location, etc.
As I said, I've temporarily solved this by stopping the phone updating it's location at all, however this isn't the best solution and since I've found the cause, I'm not convinced a factory reset or even reflashing the stock ROM will help. I'm pretty sure this is a deep OS issue, using the same Google account across 2 devices is great, until you want them to have different settings.
I'm probably gonna report it on code.google.com, but I very much doubt I'll get a response.
Stock T-mobile S6 Edge, AOCG. I have disabled I think 21 bloatware apps. I'm also leaving WiFi off full-time right now because of the cell standby bug.
However, in addition to the cell standby bug and, perhaps the real reason I refuse to turn WiFi back on at all, is that my phone fails to receive any push notifications while connected to a WiFi network.
I'll leave my phone on the table for a while, come back, hit the home button, and a flood of notifications will pop up (I use groupme a lot so in extreme cases my phone will buzz and make noise for about 30 seconds to catch up with ~50 missed notifications).
Has anyone else experienced this issue? Any ideas at fixing it?
I haven't rooted or played with the recovery yet. I've been on the sidelines waiting for an official TWRP build and a debloated custom ROM.
Just a quick bump here...
I have since rooted and installed the 5.1.1 ROM available in the T-mobile S6 Edge Android Development Forum.
I still don't get push notifications while on WiFi. My girlfriend's phone (stock AT&T moto x 5.0) is on the same network and gets push notifications just fine, so I know it's not a problem with my router's TCP heartbeat settings (or maybe I should say I don't think that is the problem).
This is super annoying and frankly just baffling. If anyone has any insight into this issue or any steps I might be able to take to try and troubleshoot it further I'd really appreciate it.
I'll bump again. I have this issue on my home network, but when I connect to another network, I'm able to receive notifications fine. So in my case, it may be some sort of router setting that my phone doesn't like. I'll keep digging around.
I called T-mobile with this issue and they are sending me a new Edge and one of their Asus built routers. Both are on their way to me now, I will update with my findings.
I should also note that I have since done a full and complete wipe of my phone and ODINed back to fully stock. It seemed like it fixed the issue at first, but now it's back to the same behavior: phone sitting quietly on the table at home connected to WiFi, hit the home button, flood of buzzes and noises for 10-15 seconds while it registers all the notifications that have been pushed since it went screen off.
kswa1987 said:
I called T-mobile with this issue and they are sending me a new Edge and one of their Asus built routers. Both are on their way to me now, I will update with my findings.
Click to expand...
Click to collapse
I have the same issue with mine.
Its a crap shoot. Sometimes it will work fine and sometimes it wont.
I turn the screen on and the flood of notifications come in.
If you dig around the web this problem is happening to a bunch of people with the S6.
Keep us updated.
How did you get the T-Mobile Asus router? A friend was telling me about that over the weekend and I'm definitely interested, since I read another thread (for a Note Edge and Note 4 that had the same issue) and they claimed that older routers had issues with GCM/Samsung push notifications.
Strange enough, last night I was receiving them fine, even during deep sleep, so it seems like a really random, sporadic issue. Still utterly annoying, however.
Yup, it's hit or miss for me on WiFi.
As for the router, they pushed it pretty hard from the start of my service call. They claim it's totally free, I will report any deposits or hidden fees that I encounter once I get my next bill.
As for why T-mobile wants to give us free routers, this Engadget article should answer your questions:
http://www.engadget.com/2014/09/11/t-mobile-personal-cellspot/
I am thinking more and more it has something to do with Samsung software and lollipop.
I have the S6 Edge and the Note Edge and a Nexus 9..... Note Edge was working perfectly until yesterday when updated it to lollipop now its having the same problem as the S6 not as bad but still misses at times.
I have all 3 devices side by side connected to the same router, the Nexus 9 doesn't miss a beat notifications are instant while the screen is off. The S6 i have to turn the screen on to get them and the Note Edge is hit or miss.
New edge got here today. So far it's a champ with WiFi notifications while the screen is off.
Although I fully expect the new phone to promptly resume the odd behavior now that I've made this post.
Haven't received the T-mobile router yet, still using the same one as before.
kswa1987 said:
I called T-mobile with this issue and they are sending me a new Edge and one of their Asus built routers. Both are on their way to me now, I will update with my findings.
I should also note that I have since done a full and complete wipe of my phone and ODINed back to fully stock. It seemed like it fixed the issue at first, but now it's back to the same behavior: phone sitting quietly on the table at home connected to WiFi, hit the home button, flood of buzzes and noises for 10-15 seconds while it registers all the notifications that have been pushed since it went screen off.
Click to expand...
Click to collapse
kswa1987 said:
New edge got here today. So far it's a champ with WiFi notifications while the screen is off.
Although I fully expect the new phone to promptly resume the odd behavior now that I've made this post.
Haven't received the T-mobile router yet, still using the same one as before.
Click to expand...
Click to collapse
Cool. Keep us updated.
I did a full reset yesterday and the phone worked perfectly for half the day and then started acting up again at night.
I just spoke to T-mobile, they are also sending me the Tmo asus router, but before they replace the phone they want me to try keeping it on wifi calling for an entire day to see what happens. I dont know what that will do but we will see.
I am curious about this t-mobile router what thats going to do. I already have a top notch router and anywhere in my house i am getting over 24mbps download speeds. SO i dont even know if i am going to use it. I have read that they are giving these things out like bread to promote them.
who knows
Well, it was working great... until it wasn't. Called T-Mobile again and they're sending the report to Samsung. I urge anyone else having this issue to call T-Mobile so that they can continue to push (pun!) the issue with Samsung.
spridell said:
Cool. Keep us updated.
I did a full reset yesterday and the phone worked perfectly for half the day and then started acting up again at night.
I just spoke to T-mobile, they are also sending me the Tmo asus router, but before they replace the phone they want me to try keeping it on wifi calling for an entire day to see what happens. I dont know what that will do but we will see.
I am curious about this t-mobile router what thats going to do. I already have a top notch router and anywhere in my house i am getting over 24mbps download speeds. SO i dont even know if i am going to use it. I have read that they are giving these things out like bread to promote them.
who knows
Click to expand...
Click to collapse
I can say, however, that the Asus built router is really great. Over 200Mbps download speeds over 802.11ac 5GHz
Just a quick note, after ONE HOUR AND FIFTEEN MINUTES on the phone (finally got pushed to samsung tech support after tmobile confirmed it was a manufacturer issue), I ended up hanging up with the issue unresolved.
Samsung had me download an app that allowed the tech to remote in to my phone to try and diagnose the problem.
I was able to recreate the issue by leaving the call live, locking the screen, sending myself an email from a different account, waiting five minutes, and then hitting the home button. Lo and behold, the notification popped up after the phone had been awake for 3-5 seconds, clearly demonstrating the issue. She then says, I'm glad we have resolved the issue, you see the notification on your lock screen. Uhhhhh, have you been listening at all? It didn't register until I woke the phone... you just saw it! Incompetence.
The tech then relentlessly went through each app's notification settings to make triple sure I didn't turn off notifications by accident. Not the issue. Then she asked if it was only with downloaded applications... yes, those are the only applications I use? Not using the garbage built-in email client and I can't think of any other pre-installed app that would get push notifications on the reg.
Anyway, she then says, oh well if its only downloaded apps you'll need to get in contact with the app developers for each app. What? how could? what?
Worthless.
For the record, tmobile was great... the tech was very knowledgeable and helpful. Samsung... worthless. Couldn't understand the issue (I think there was a language barrier to some extent) and then after she suggested I contact each app dev, I hung up. Might try again tomorrow, maybe get a different tech.
Still, no solution!
Thanks for the update.
I am waiting on the ASUS modem but I know that wont do anything. Since your new phone is doing the same thing i guess I am not going to ask for a new phone since it wont matter.
This problem is occurring on Verizon models as well if you do a google search.
I really think its a software problem with Samsung and lollipop. MY Note Edge was perfect before Lollipop now its acting exactly like the S6. My Nexus 9 is perfect and doesnt skip a beat.
Maybe the issue will be fixed with 5.1.1
spridell said:
Thanks for the update.
I am waiting on the ASUS modem but I know that wont do anything. Since your new phone is doing the same thing i guess I am not going to ask for a new phone since it wont matter.
This problem is occurring on Verizon models as well if you do a google search.
I really think its a software problem with Samsung and lollipop. MY Note Edge was perfect before Lollipop now its acting exactly like the S6. My Nexus 9 is perfect and doesnt skip a beat.
Maybe the issue will be fixed with 5.1.1
Click to expand...
Click to collapse
Let's hope! It's quite frustrating but I will hold out hope.
I have exactly the same problem.
When the screen is off and the phone is connected in a WiFi network, I stop receiving push notifications after a while.
I do not receive notifications from GMAIL, E-mail app, WhatsApp, etc.
Then, when I turn the screen on, everything is received.
I have a Brazilian S6 Edge with Stock ROM.
I have tried everything: Wipe cache, factory reset, etc. Nothing has helped... :crying:
---------- Post added at 03:24 PM ---------- Previous post was at 02:28 PM ----------
Guys, I think I solved my problem, at least temporarily.
I realized that I had enabled in my router DHCP with IPV6 and the Edge was using it.
When I entirely disable the IPV6 in my router and restarted it, I let the screen off for almost 30 min. and I still receive notifications from WhatsAPP, Facebook, and Gmail. Thus, I really think it must be the lollipop problem with IPV6 that people are reporting.
Maybe you should try this.
I have Comcast and unfortunately they wont let you disable the IPV6.
I am getting my T-mo Asus router today, I am going to hook that up and disconnect the IPV6. I will report back what I find.
I think the IPv6 fix has solved it for me.
I am hesitant to say for sure because of so many moving pieces and the hit-or-miss nature of the issue, but ever since I turned off IPv6 on my T-mobile Asus router, I have had perfect WiFi push notification behavior (... I think).
You are not alone check this out, me specifically, this happens when im using wireless charging and the phone sits.
http://forum.xda-developers.com/galaxy-s6-edge/help/push-notifications-stop-screen-off-t3071248
Well I have been going a full day now on the T-mo Asus router with IPV6 TURNED OFF, and the notifications have been instant.
It does seem that IPV6 is the culprit.
On a side note, I can not believe how fast the Asus router is. I have a 3,000 sq foot house and I am getting over 90mbps download speeds all over the house.
Very very impressive.
If anyone has Comcast you MUST get your own router. Put the Comcast router in bridge mode and use your own router. Its night and day