Related
....if this specific question....very specific question....was already answered...
I can't stay connected to a 4g network. My evo will connect to 4g, stay on for 10 secs, and then disconnect. Then I have to manually reconnect, and the entire process repeats. Before you go passing judgement please read the following:
- I've used terminal emulator to make sure my WiMax Mac is correct.
- I'm using radio 2.15.00.09.01
- Installed a stock version of the OTA 3.29.651.5 and rooted it using this thread: [Guide] How to apply the new OTA 3.29.651.5 when you have clockwork and s-off (sorry can't post links yet)
- WiMax radio is 26023
- PRI is 1.77_oo0
- PRL is 60670
I read something about increasing the timout reconnect from 10 to 300 in another thread that I have bookmarked.
My question is this
Is this the normal function of the WiMax code or does this have something to do with the rooted rom I installed?
Is the only way to fix this done by changing the timeout value mentioned before?
Once again, I will blow my head off if this has been answered before.
Thanks
Shouldn't have anything to do with the rom. Have you ever been able to connect (and stay connected) to 4g? Are you in an "official" 4g area? from what I've seen, the disconnect issues you're describing are normal in areas where they're still rolling out 4g, but it isn't fully up and running yet.
You can also try renaming the xxxx.tree.xml file in /data/misc/wimax/ while the wimax is off, and letting it rebuild the xml file again the next time you turn 4g on - but I think this only helps for the constantly scanning issues. Note that you're renaming that file (instead of deleting it completely) so you can go back to it if you run into any issues.
Sent from my blah blah blah blah
there is a thread in the dev sectin on how to change your 4g connection timeout. One simple thing you can try is to update your profile in software updates.
If people had more useful thread titles, don't you agree that it would be easier to search them?
Might have to blow my head off......
rutter9 said:
there is a thread in the dev sectin on how to change your 4g connection timeout. One simple thing you can try is to update your profile in software updates.
Click to expand...
Click to collapse
Thanks for responding....I've already updated my profile and I know about the 4G connection timeout thread.
I mentioned in my original question I already have that thread bookmarked (not tyring to be a ****, didn't know if you caught that).
fachadick said:
Shouldn't have anything to do with the rom. Have you ever been able to connect (and stay connected) to 4g? Are you in an "official" 4g area? from what I've seen, the disconnect issues you're describing are normal in areas where they're still rolling out 4g, but it isn't fully up and running yet.
You can also try renaming the xxxx.tree.xml file in /data/misc/wimax/ while the wimax is off, and letting it rebuild the xml file again the next time you turn 4g on - but I think this only helps for the constantly scanning issues. Note that you're renaming that file (instead of deleting it completely) so you can go back to it if you run into any issues.
Sent from my blah blah blah blah
Click to expand...
Click to collapse
I have never been able to connect and stay connected to 4G.....but I'm not really aware of any official 4G areas around here. I live in north jersey as well.
I picked up a strong 4G signal by coincidence while near the border of two towns (Clifton and Passaic....not sure if you're familiar with them) and that was when I started experiencing the disconnect/manual-reconnect issues.
I never connected to a 4G network before I rooted my phone because I could never get a signal. It was only until recently, after I rooted, that I've only been able to connect semi-successfully. I tried a good 10 times with the same results.
i.e.
I'd get a strong signal, do a speed test (which was blistering at 8577/1049 on the first try and 7699/1020 the second), and then let the phone sit idle. It will always disconnect, but I have no problems whatsoever manually reconnecting.
My confusion was whether or not this was common for people who have stock, non-rooted, clean as your baby sister's "you know what" Evos when trying to connect to a non-official 4G network, or is something wrong with how I rooted/the rom I used/whatever. Should I have to manually reconnect? Should the phone automatically disconnect from the 4G and go to 3G after a certain idle time? Should the phone automatically use 4G as the main connect if I have the WiMax radio on and the signal is really strong?
I assume I'm connecting to a non-official 4G signal.
Don't get me wrong I enjoy modding anything that has a circuitboard, but keeping up with all the issues can be a little annoying. Being a novice coder, this platform (new to Android) doesn't seem to be to complicated and I'm learning quickly. I have a spare PS3 sitting in my closet still running YDL. You used to be able to install an addtional OS on the PS3 before Sony got pissed because people were f***in up their PS3's. Sony "forced" an update that removed the ability to install another OS on the system, and the update actually wiped-out any other OS you had already installed. I put YDL on the PS3 so I could run NES/SNES/Genesis roms.
Back on topic, and to make a long story short (waaaaaaaaaaayyyyyy to late for that I guess), I'm just wondering whether or not my phone is working as it should.
Like I said, the phone connects...I do some stuff like a speed test....then disconnects automatically. Then I get a 4G notificiation in the main Android notification pull-down menu....and re-connect manually. The 4G signal is really strong, not sure if it's official.
Thanks for responding btw, I really appreciate your comments and I'll check out what this tree.xml file is all about. I understand the annoyance though. Not only is it annoying to have multiple threads all talking about the same thing, programmatically it's extremely inefficient and redundant.
Hence, if this question has been asked, I'll blow my head off with a 12 guage.
yes...agreed....but
Minjin said:
If people had more useful thread titles, don't you agree that it would be easier to search them?
Click to expand...
Click to collapse
sometimes getting good advice comes with grabbing attention from the right person. I've elicited an informative response from a couple other members. I thank them for being helpful to someone new.
can't I change the title of my own thread later on?
EDIT: An as soon as I changed the title, views dropped dead...cause I knew a title with good keywords would get no attention.
And you've ensured that while YOU may get advice and a solution, no one in the future will be able to use that same advice because this thread isn't likely to show up in a proper search.
Also, how many people know the answer but don't click on threads with titles as useless as this one? I would bet far more than who would click on it.
This is just basic forum etiquette, not anything unique to XDA.
Minjin said:
If people had more useful thread titles, don't you agree that it would be easier to search them?
Click to expand...
Click to collapse
This.
10char
Minjin said:
And you've ensured that while YOU may get advice and a solution, no one in the future will be able to use that same advice because this thread isn't likely to show up in a proper search.
Also, how many people know the answer but don't click on threads with titles as useless as this one? I would bet far more than who would click on it.
This is just basic forum etiquette, not anything unique to XDA.
Click to expand...
Click to collapse
......you are correct....I understand....that is why I'm going to change the title of the thread. Are you looking for me to say I'm sorry or something?
correct me if I'm wrong, but the site also indexes the content of the message as well. I'm very familiar with SEO and understand that a lot of indexing logic places heavy emphasis on the title of the thread, but the keywords in the content of the page also have a lot to do with how the thread pages get indexed. It doesn't solely rely on the title.
Just to put this to an end, I'm sorry for titling this thread as such?
Now, any thoughts on the actual question that I posted or are you going to stay mad at me forever?
I've got a two part question for some issues I'd like to address while on 4G (some I've called Sprint about, others I know you guys will have the answer since I'm rooted) that I hope to resolve.
My issues with Sprint is that if I'm on 3G and looking at images via websites, pics obviously load slower, but they're always nice and crisp. I notice that when I happen to be on 4G and go look at images, suddenly they load super grainy. I spoke to someone else who is also on Sprint w/ an LTE 4G phone (not a Note II, something else) who experiences the exact same problem. I've called Sprint about it, but I get the usual run around saying they're addressing the issues, fixing towers, etc. When I first started getting 4G in my area about 3 months ago, it was BLAZING fast, connected the second I came off the freeway and stayed on strong. I realize over time that I'm sharing the same signal with others, but damn.
My issues that I'm hoping you guys can assist with is in regards to the phone staying connected to to 4G more via changing thresholds. As I id before, it was awesome. Now it's gotten to the point where I or the phone have to be near a window, or occasionally I can leave it on the top edge of my couch...but if I happen to handle the phone to answer a text messages, it'll often drop back into 3G. The problem is that I use my phone tethered to my laptop for watching TV....Top Gear, Family Guy, etc that I stream. On 4G it's great, but once it drops to 3G it turns into a buffering nightmare and some shows/sites can't handle jumping around for time frames, so lets say if I'm 15 min into a show, go into 3G and come back into 4G, the show never recovers and I've got no choice but to restart the show. I'm just curious if there's a way to change at what point/signal strength that the phone wants to swap back and forth and basically ask it to stay on 4G more often than not when I'm at home where I actually get 4G.
As for tethering, I'm a stock rooted ROM using TrevEMod tethering because the stock tethering app won't stay turned on, I'm assuming due to using the stock ROM. What I'm curious about is a way to have the phone automated in that once I plug it on, the tethering app turns itself on and then back off again once unplugged from a power cord. At one point I'd used some app where it had me enter parameters to do this, but it only worked to turn on the stock tethering app which won't work.
Bottom line is I'd like my phone to stay connected to 4G more often than not, turn on tethering when plugged in and turn it off when not.
as for the tethering, if you are running the stock deodexed rom, there is a mod you can flash to make the native hotspot work then you will be able to use Tasker or however you automate it turning on. if you are running stock odexed you could always flash stock deodexed, if you were intent enough on making it work.
here is the hotspot mod: http://forum.xda-developers.com/showthread.php?t=2232553
I truly don't know if the stock ROM is odexed or deodexed, I just did a simple rooting procedure and nothing more so I could install a tethering app. Maybe I'm just being naive, but coming from my Epic days where I rooted, ROM'd, kernal'd, OC'd, etc days where I removed tons of apps, added others, etc I never was able to get battery stats/calibration to work correctly, which in turn wrecked havoc on that phone...phone would get super laggy, bog and stumble, then I'd reset the phone and I'd go from 20% battery life to 3%, then realize why the phone was freaking out. Now that I've got this Note II, it works great, I've never felt the need to OC or anything (I wouldn't mind removing stock apps but the SDX Stock App Removal Tool doesn't work), so I'm kinda hesitant in flashing any sort of ROM for fear of reliving past experiences...right now the phone simply works great, I'd just like a few simple features. Any input to sway my decision?
i hear ya, i too like a nice stable setup with everything working. your system is probably odexed if al you did was root, but if you have a file explorer app, when you go into /system/app, you will see each .apk also has an associated .odex file. the deodexed rom has the odex part added back into the apk, but otherwise is exactly the same, no tweaks or anything, every bit as stable, and with nothing removed, but it is easier to make mods for a deodexed rom, such as the hotspot mod!
the decision is yours. it is always a bit of work to flash a rom, but this is defintiely a way to keep the stabilty and reliability, and have the hotspot working the way you want it to! the rom is here: http://forum.xda-developers.com/showthread.php?t=2241930, if you choose to go this route. this is exactly my setup, with the hotspot mod, and it runs great.
I'll read the thread, thanks for the link. Any suggestions for something that will enable the tethering app automatically based on being plugged in, and I've had no luck finding anything in regards to people changing thresholds for the 4G connectivity.
m5james said:
I'll read the thread, thanks for the link. Any suggestions for something that will enable the tethering app automatically based on being plugged in, and I've had no luck finding anything in regards to people changing thresholds for the 4G connectivity.
Click to expand...
Click to collapse
no problem. the app Tasker from the market does things like that, i think it costs a few bucks but it's well worth it. and perhaps there are others.
for the 4G thing, i don't see any setting for that. there are other people who know a lot more about network stuff than i do. there might be a dialer code menu where you can set to receive LTE only, but sorry i can't be of more help there. good luck and have fun!
Read this thread
http://forum.xda-developers.com/showthread.php?t=2407286
In HDR menu there is a LTE only mode..... beware you wont receive calls or texts so if you have google voice set up then perfect
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
The newest firmware from the latest OTA can be found in the 2nd post in this thread: http://forum.xda-developers.com/showthread.php?t=2485319
If you've already flashed the latest firmware then I'm not sure what to tell you... maybe ask your favorite rom developer to take a look at the latest OTA in regards to this issue?
If it has the stock rom and OTA update why not take it to the store and let them look at it. Something might be wrong with your account.
movieman999 said:
Hey guys,
I think I've reached the point where it's time to call in the cavalry and see if anyone around here is having the same issue; there appears to be a plague going around on the Verizon network, specifically in the Pennsylvania area, preventing people from sending SMS, but still receiving fine (and 4G works fine too, for the record). MMS still sends / receives fine, but I'm unable to send SMS. There are tricks to allowing a single SMS message to go through which involves toggling Airplane mode on / off every. Single. Time. People have also had success with turning 4G off completely, using the CDMA band after a reboot at which point they can send *several*, but still end up with the same issue.
The only solution I've read about that FIXED it is by reverting back to complete stock from VZW. Performing factory resets, using other ROMs, etc etc...doesn't work. I'd REALLY rather not do this and, frankly, would rather use 3G / toggle Airplane mode for texts than use Sense and get off of my ROM (http://forum.xda-developers.com/showthread.php?t=2560831).
People from other device forums on XDA are having the same problem; the ones I've seen that are active discussions are the Samsung Galaxy S III & IV. They're mostly CM ROMs *as well as* AOSP ROMs in general.
http://forum.xda-developers.com/showthread.php?t=2532414
http://forum.xda-developers.com/showthread.php?t=2658572
SIM card replacements are a no-go, and the recorded instances seem to be in the 717 / 570 area codes, mostly. Now I DO know that VZW released an OTA update for the One recently, and I'm relatively confident that would fix the issue, but I've no idea why. I'm thinking perhaps they dispatched new radios? I looked around a bit and couldn't find any flashable zips of radios extracted from the latest OTA, that's the next step I'll be trying once that download finishes.
So is anyone else having this issue? Any word on fixes?
Click to expand...
Click to collapse
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
DreamFX said:
Those area codes for all phones on aosp roms are not working right now. Since 2/20/14. Has nothing to do with HTC or their firmware. I'ts a bizarre Verizon 4G issue. I am in the 717 area code with a Note 2 with the issue. I have seen others with S4 and S3. Verizon is aware of the issue and is working with another XDA member to fix it. To date it's not resolved.
Click to expand...
Click to collapse
movieman999 said:
Thanks DreamFX; I've been following this thread (http://forum.xda-developers.com/showthread.php?t=2658572&page=6) lately as they seem to be the most on top of it. I can't believe Verizon has let this issue go on for so long, but given that it seems to only be relevant to those of us with AOSP ROM's, I guess it makes sense. At least I'm still able to send texts, if not only through a silly process of toggling airplane mode on / off. Hopefully it gets resolved soon...
Click to expand...
Click to collapse
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
dickenam said:
I'm getting this too, just started for me today from what I can tell. Driving me bonkers but, Airplane mode toggle totally works for me. :cyclops:
VZW SGS4 running AOSPA with 804 area code operating in Oregon.
Click to expand...
Click to collapse
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
movieman999 said:
Whoa, that's weird. I really thought it was isolated to the 717 area code. It's getting pretty crazy...I've been dealing with this for a few weeks now and my patience is running thin. Unfortunately it's not like we can just report this to VZW because all anyone would tell us to do is "restore to factory", which simply isn't a solution.
Click to expand...
Click to collapse
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
dickenam said:
Yup, I thought so too. Just cropped up between 10a and 11a PDT. Like you said MMS is fine, simply affects SMS. And yes, restoring stock is simply not an option. Going to TMobile, however, is totally an option that I'm considering more and more often......
EDIT: AND SMS began sending properly (without workaround) for me around 8p PDT last night, just tested and still ok. RESOLVED!
EDIT EDIT: Issue now persists....sadface =[
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
IM getting it now. but not exactly the same. phone freezes without warning and I have to toggle airplane mode and restart to get it to unfreeze. this happened after the last OTA update. I am going to a custom ROM until I don't read anything about this for a while
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
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
NeatAndClean said:
Hello, I would like to preface this post by saying I'm a complete noob to XDA Forums and custom ROMs as well. I've know about XDA Developers for years, just never been much of a tinkerer when it comes to Android, I just prefer stock.
Well recently, I bought a used LG G3 because the deal was just to good to pass up. It was my first time using a ROM other than stock and it was utterly disgusting in comparison. I hated it so much I installed my first ROM ever, and it was Candy5 for I heard CynogenMod stopped supporting the LG G3 is some capacity. Well, I've been using it for a while now and made it look as close as I could to stock, there's just one problem.
I recently enabled Wi-Fi calling on Ting. The device was a Verizon model, but I purchased it unlocked, and activated it on the MNVO Ting. Well, it wasn't working so I was wondering what's up. I read that you had to enable it within the devices settings, but all guides were not specific to the custom ROM I had installed, and even following along as closely as I could, the option for Wi-Fi calling wasn't there. I've read that if Wi-Fi calling doesn't appear, your device doesn't support it. But, everywhere I've read, has been consistent that Wi-Fi calling is supported on the LG G3.
So, I ask you long time tinkerers, do you know how to enable Wi-Fi calling within the Candy5 ROM? Does it just not support it? I even used the neat search feature within the settings app and couldn't find a switch for it. Please help!
Click to expand...
Click to collapse
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
yanowman said:
Yeah WiFi calling won't be an option on AOSP ROMs... Its cooked into the stock software (for at least t mobile) and only works on stock based ROMs. There was a developer that tried to use the code from I BELIEVE the nexus 6 and adopt it to our devices but it never got pushed through. If you want WiFi calling/VolTE, stick with stock ROMs.
Click to expand...
Click to collapse
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
NeatAndClean said:
Ah, I see. Hopefully some day it would be available on custom ROMs. Using the stock ROM is not even worth the gloriousness of Wi-Fi calling, and that's really saying something, because my room is a complete dead zone for reception. I have to walk out on my porch every time I want to place / receive phones calls or SMS texts.
Click to expand...
Click to collapse
Yeah I completely feel your problem. Over at my house (which is in the maybe 10 minutes from the main bay area) there is NO reception, only when you walk down the street is there reception. When I was on Verizon I got their WiFi booster thing... Now that I'm on T mob, I use WiFi calling bakdd info their ROMS