So, I'm facing a problem with my Samsung Galaxy s5 (sm-g900f). I can't receive push notifications for some apps (hangouts, whatsapp, gmail,..apparently all the apps using Google Cloud Messaging to push their notifications). I'm having this problem when I'm connected to my home Wifi only; when I turn off the wifi and switch to mobile data, all the delayed notifications arrive all at once. However, when I connect to other Wifis, everything seems to be working normal. Also note that, other phones work normally on my wifi (Samung galaxy s4 for instance). I've already done some troubleshooting:
1) I was using the stock android 5.0 (the Spain firmware) (I live in Lebanon) . I rooted my phone, the problem remained. I put a custom rom , didn't solve anything. Finally ,I unrooted the phone and I fully wiped it and installed the stock android kitkat (4.4.2) for Lebanon from sammobile.com, again with no luck.
2) I thought it was a router issue, so I changed my router.
3) I downloaded "push notification fixer".
4) I looked up the ports that GCM (google cloud messaging) uses, and I forwarded those ports to my phone's local IP.
Nothing of the steps mentioned made any difference. I'm sure there are still some troubleshooting I haven't tried; Can you help me? Thank you.
Same problem
I'm having a similar problem with a different phone, I have a Xperis E1
While running update with android 4.3 Jellybean it works fine
When i upgrade to android Kit kat 4.4.2 I get delays on my notifications, from a couple of minutes up to not receiving the notification until I unlock the phone manually.
So i've tried severral stock firmware and only when i use one based in 4.3 Jelly bean the problem never appears. My problem is this firmware has lots of bugs and misbehavior. So i Installed this one and hopped the best:
Xperia E1 D2004 official firmware Customized IL (Israel) 20.1.A.2.13 /R1B
Jellybean firmware with push notification working perfectly is:
Xperia E1 D2004 official firmware Customized GEL (Generic LAM) 20.0.A.1.21 / R3A
Related
Hi. I just received my Nexus 7 2013 Wifi today, and I´ve been testing it. The WiFi connects fine, I put in my google account, it showed me a bunch of new googleapps updates available ( maps, youtube, etc ), and so I´ve updated all of them. But then I´ve checked the version it´s running, and it´s JSS15J. I try to update the system, and it says "it´s up to date"...but shouldn´t be updated to JSS15R version within a few minutes after I powered it on?
I´ve checked today, and it seems kitkat is rolling out, so is it going to update to 4.4 from it´s current version, or is it something wrong with my tablet? I tried restarting, but no good.
Any help appreciated. Thank you very much.
Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Vector_Calculus said:
Folks,
I got an OTA update for the moto g. I'm on the Koodo network.
I downloaded the OTA update. Got the file from /cache.
Interesting the zip file i got has the name:
Blur_Version.173.44.9.falcon_umts.Telus.en.CA.zip
The OTA installer is telling me: 173.44.30.en.CA
The release notes had stated (can't find it now) that it has a fix for the OTG support and radio fixes like the UK and DE updates, PLUS a fix for Telus/Koodo customers that couldn't end their calls correctly.
Anyway i can't apply/update as i'm currently rooted. What are my options?
Be gentle, its my first android device.
------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
I just updated although I'm rooted but Im using the original ROM
See this thread too: http://forum.xda-developers.com/showthread.php?t=2648590&page=13
you have to unroot
You can unroot quite easily and apply the OTA then root again.
You shouldn't loose anything: download the original ROM you are currently running (the telus 4.3) and extract the 3 parts of the system image, then flash them using fastboot.
Let me know if that's not clear enough, I'll find the Step by step instructions for you.
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Vector_Calculus said:
It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
Click to expand...
Click to collapse
Yes, the naming scheme is quite confusing, but despite the fact that my German version is 176, US version is 174 and yours is 173 after updates, obviously they got exactly the same patches as you listed. No worries.
Vector_Calculus said:
Just an update on the Koodo/telus patch (8.5mb)
I was originally running at 4.4.2 but after backup critical files i jumped in and rooted to get the fixed the update provided.
It worked! No issues. Root was preserved after the update.
My phone prior to update was at 4.4.2 (173.44.9) and after the update it went to 4.4.2 (173.44.30). Don't know why its not called 174.xxx like the other countries. It would nice if we all had the same patch naming schemes. Very confused tracking all the versions out there.
The fixes included:
"Fixed an issue which caused temporary cellular network loss for small number of moto G customers.
-Fixed wallpaper cropping issue
-Resolved USB OTG support issue with USB Drives
-Fixed low call volume by some users
-Fixed an issue with ending calls originated from a moto G on Telus/Koodo.
I actually the last item happened to me as both my wife and I have the motog and are on the same network.
Click to expand...
Click to collapse
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
Battery drain is about the same as before. Maybe a factory data reset may help. I don't know if you lose root if you go this route..
xda127 said:
I applied the update as well. However, my phone battery starts draining very fast, 50%+ overnight, with WiFi off. The phone seems not go to idle but running always.
Click to expand...
Click to collapse
There is a camera bug on 4.4.2 that keeps the phone running after exiting the app. A fix is o the way...
Hi - downloaded the lollipop update on my N9005 (ver details below) and all works well except my moto 360 android wear device appears to lose connectivity.
The Android Wear app shows connected, the running notification says connected, but when I launch a voice command from the watch, very ocassionally i see 'Offline.'
Any ideas?
I have seen 'bluetooth fixes' that people have had to do after the Hong Kong update - not sure if I should do that anyway as bluetooth and wifi work, just that bluetooth is not as reliable as it used to be!!
ver details:
baseband : n005xxegbnl8
build number: LRX21.v.n9005xxugbnl8
bump
can someone please respond?
up
as above
My bluetooth to LG G watch also fails after about a day of connection, but a phone reboot always fixes it. Havent figured it out how to fix it other than that daily reboot
same issue
Same issue here. Would you happen to find a fix for it? I'm also googling.
khanbaloch said:
Hi - downloaded the lollipop update on my N9005 (ver details below) and all works well except my moto 360 android wear device appears to lose connectivity.
The Android Wear app shows connected, the running notification says connected, but when I launch a voice command from the watch, very ocassionally i see 'Offline.'
Any ideas?
I have seen 'bluetooth fixes' that people have had to do after the Hong Kong update - not sure if I should do that anyway as bluetooth and wifi work, just that bluetooth is not as reliable as it used to be!!
ver details:
baseband : n005xxegbnl8
build number: LRX21.v.n9005xxugbnl8
Click to expand...
Click to collapse
Hi I am having same issue! have you find solution?
Thanks!
I was on CM11 (snapshot) and I had connectivity drops between my 360 and N9005.
So I installed the Official Poland Lollipop ROM and thinks are good after that....
nijom said:
I was on CM11 (snapshot) and I had connectivity drops between my 360 and N9005.
So I installed the Official Poland Lollipop ROM and thinks are good after that....
Click to expand...
Click to collapse
Thanks will do the same!
On UK note 3 unbranded official lollipop and I have the same problem. Constant disconnects and the 360 telling me I am offline when in actual fact I am connected.. Even after a full factory reset of both devices the problem persists.. Not happy!
CONTACTMC said:
On UK note 3 unbranded official lollipop and I have the same problem. Constant disconnects and the 360 telling me I am offline when in actual fact I am connected.. Even after a full factory reset of both devices the problem persists.. Not happy!
Click to expand...
Click to collapse
I had same problem again and again. But now I gave my note 3 to my wife, I am using moto g2 with cm.
Am downloading the last kitkat rom I was on and reverting back.... Samsung suck atm... This update is 7 months late and is faulty.
Back on kit kat 4.4.2 and all works perfect again!
Are we expecting any updates soon or the 5.0.1/2 update to fix the bugs that were, presumably, introduced with 5.0?
For instance, the Pebble watch disconnecting constantly. Seems perfect on my M7 with 5.0.2.
Really hope this is done quickly, as it's pretty much unusable right now.
No one knows when 5.0.1 will come, but keeping in mind that 5.1 will be released later this month I guess there's chance that Sammy might go crazy and skip 5.0.1/2 altogether and jump directly to 5.1!
If you want this topic as some request kind then its better to create it in sammobile.
Thanks for the reply.
I just hope Samsung can push through some small bugfix update then in regards to the bluetooth then. It's a big shame I can't really use the Pebble anymore.
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
s1m4an said:
Just what I wanted to post. The lollipop update has been an nightmare for my Pebble watch. And I'm sure it's the phones software fault.
I still have not done a complete wipe using Odin, only upgraded, keeping my apps but I'm not convinced that would help.
One weird thing I noticed is that while I was on the N9005 Russian leak (the system nandroid) the Pebble/Note connection was much more stable... Could it be that Odin doesn't set some permissions correctly while flashing the system partition?
I'm thinking of doing a full wipe/repartition using Odin and the latest Polish update, or trying some touchwiz based rom, can someone recommend any good ones I should try out?
Click to expand...
Click to collapse
Hello
May I direct you here: http://forum.xda-developers.com/gal...-official-5-0-firmware-galaxy-t3029557/page79
dariox provided this workaround, which has been working very well for me and keeping my Pebble connected.
"Download BlueTooth auto connect (UniqTec developer)
Set:
"set last device" Flag
Profiles : select all
devices : select your device, and flag in the options "healt hdp" in case of smartband ecc...
Set flag on : Bluetooth on
Device Disconnected
Device Connected"
Unfortunately, it seems to come at the cost of a constant wakelock, and battery drain, but at the moment we don't really have any other choice apart from rolling back to kitkat, getting a new phone, or stop using the Pebble.
Hope this helps.
It's Lollipop's fault, I had the same problem when I upgraded, both the early version and the official version had the same result.
I downgraded back down to KitKat and it's fine now.
I installed CyanogenMod 12.1 Nightly previously on my Samsung Galaxy S4 (GT-I9500), the WIFI was working perfectly without any issues. After a period, an update has been available, so as every time I update my device, then the issue has shown. After a short days, an update has been available and in this update changelog, they say that the issue shortage of WIFI strings has been fixed, but unfortunately, it hasn't fixed for me. After CyanogenMod has closed, I return to the latest 5.0.1 official Rom India (INS) and I wide data/cache, but also it hasn't fixed . I downgrade to latest 4.4.2 official Rom India (INS) and I wide data/cache, but it hasn't fixed. I update again to the latest 5.0.1 official Rom India (INS) and I wide data/cache, but it hasn't fixed again . I searched for solution to the issue on google but I haven't found.
The issue is when the signal strength of a WIFI is Good (2 points), the connection stop (not the WIFI).
I have checked on other devices, the connection hasn't stopped and it works perfectly. I have checked by connecting to other routers in different places, the connecting still stopped.
Please help me get out of this issue :crying:
Another Issue
I have found another issue.
The GPS can't locate my device location offline (without WIFI or mobile data).
Please help me.
No solution??!!