Related
Hey,
Iam getting my phone tomorrow, but i have been doing some reading in the different topics.
I found this link in one of the topics postet by "xdadroid88"(thanks to him
http://code.google.com/p/android/issues/detail?id=15057
i have read through it and this is the tips i found.
1. Set the wifi policy on "always on"
2.Location & Security -> Use wireless networks / Use GPS satellites. I've disable both options
3. switch off Latitude
Seems like this is a issue in Gingerbread 2.3.3 and is resolved in 2.3.4
Try this and post the results
So disable wifi/gps and battery is better? That's news!
Dont need to be rude, just trying to help, it can be a different problem on the sgs 2, just telling people what they can try and maybe maybe it works for some
Sent from my GT-I9000 using XDA App
CEPi said:
So disable wifi/gps and battery is better? That's news!
Click to expand...
Click to collapse
LOL.......
That's not even what he said, those settings are for letting your phone track your location. :-/
I'll give this a go OP and post tomorrow. Thanks.
the OP actually meant to say "wifi sleep policy". and yes the issue was with wifi. ironically setting wifi sleep to NEVER is better for battery life than letting it go to sleep, because when it switches back to 3g it uses more power. leaving on wifi always uses less power than leaving on 3G because of latency and other factors. counter intuitive but true.
Are there any UK Desire Z owners out there who are successfully running Cyanogenmod 7? I'm running v7.0.3 and it keeps rebooting spontaneously.
???
I have ran CM7 with no problems other as an issue (actually a "feature") with wifi not working with the screen off,
You could try nightlys if you are set on CM7, in fact I think there is a new stable version coming out soon.
Do you overclock?
I have the Canadian version and in the US (if that helps) and have ran Cyanogen 7.0.3, 7.1.0 RC1 and all the nightlies without reboots..
You should try re-downloading and re-flashing to see if that fixes your problem.
I'm currently trying Virtuous G-Lite to see if it helps. So far so good after 7 hours (i.e. no reboots).
I've also noticed that I can now get access to data roaming services (I'm away in Portugal). With CM7 I was unable to access the local GPRS service. Does this maybe suggest a compatibility issue between CM7 any my radio?
May I ask which radio version you are running bombadier?
itm said:
I'm currently trying Virtuous G-Lite to see if it helps. So far so good after 7 hours (i.e. no reboots).
I've also noticed that I can now get access to data roaming services (I'm away in Portugal). With CM7 I was unable to access the local GPRS service. Does this maybe suggest a compatibility issue between CM7 any my radio?
May I ask which radio version you are running bombadier?
Click to expand...
Click to collapse
Aye 04.12 its the latest i think, its in my sig .30 seems to be a good un, try unity its a cool sense rom if u are into that sort of thing,
Sent from my HTC Vision using xda premium
I've been using MIUI for the last 2 days, and Virtuous G-Lite for a day before that, and have had no recurrence of the rebooting problems that I had with CM7. I guess there was a compatibility problem with CM7 and the DZ
bombadier said:
I have ran CM7 with no problems other as an issue (actually a "feature") with wifi not working with the screen off,
You could try nightlys if you are set on CM7, in fact I think there is a new stable version coming out soon.
Click to expand...
Click to collapse
Menu > Settings > Wireless & Networks > Wi-Fi Settings > Menu > Advanced > Wi-Fi sleep policy > "Never".
Fixed!
itm said:
I've been using MIUI for the last 2 days, and Virtuous G-Lite for a day before that, and have had no recurrence of the rebooting problems that I had with CM7. I guess there was a compatibility problem with CM7 and the DZ
Click to expand...
Click to collapse
You probably just had a bad flash. There are thousands of people in the UK using CM7 on their DZ
martonikaj said:
Menu > Settings > Wireless & Networks > Wi-Fi Settings > Menu > Advanced > Wi-Fi sleep policy > "Never".
Fixed!
Click to expand...
Click to collapse
Try it, makes no difference
bombadier said:
Try it, makes no difference
Click to expand...
Click to collapse
Sure you don't have any other settings that would contradict that? That's the only system wide setting to make Wi-Fi stay on when the screen is off. Are you using a different kernel than stock by chance?
martonikaj said:
Sure you don't have any other settings that would contradict that? That's the only system wide setting to make Wi-Fi stay on when the screen is off. Are you using a different kernel than stock by chance?
Click to expand...
Click to collapse
Yip,noticed on quiet a few ROMs that wifi sleep policy is broken and doesnt do what its ment to.
Bug report
http://code.google.com/p/cyanogenmod/issues/detail?id=4232
bombadier said:
Yip,noticed on quiet a few ROMs that wifi sleep policy is broken and doesnt do what its ment to.
Bug report
http://code.google.com/p/cyanogenmod/issues/detail?id=4232
Click to expand...
Click to collapse
Interesting. Seen some complaints in the Nightly thread but I personally have never had the issue.
Definitely not kernel/setting related, a fresh flash of any flavour of CM 7,broken out of the box,which is a shame as I really like it.
When you say you have never had the issue,is that because you have never tried to stream anything with the screen off ?or that that wifi sleep policy actually works?
bombadier said:
Definitely not kernel/setting related, a fresh flash of any flavour of CM 7,broken out of the box,which is a shame as I really like it.
When you say you have never had the issue,is that because you have never tried to stream anything with the screen off ?or that that wifi sleep policy actually works?
Click to expand...
Click to collapse
My Wi-Fi sleep policy works fine. My battery status page shows my Wi-Fi is on 100% of the time, even when the phone isn't awake and the screen is off.
martonikaj said:
My Wi-Fi sleep policy works fine. My battery status page shows my Wi-Fi is on 100% of the time, even when the phone isn't awake and the screen is off.
Click to expand...
Click to collapse
Yeah but does it actually stay on? A good way to test is to try streaming internet radio,I am still connected but after a couple of minutes playback becomes choppy,phone still claims to be connected.
bombadier said:
Yeah but does it actually stay on? A good way to test is to try streaming internet radio,I am still connected but after a couple of minutes playback becomes choppy,phone still claims to be connected.
Click to expand...
Click to collapse
yep works fine
martonikaj said:
yep works fine
Click to expand...
Click to collapse
Ok then I am at a lose to explain this then,could you run a logcat when you are streaming and send it to me? Would like to see how your output differs to mine.
Downclocking.
bombadier said:
Yeah but does it actually stay on? A good way to test is to try streaming internet radio,I am still connected but after a couple of minutes playback becomes choppy,phone still claims to be connected.
Click to expand...
Click to collapse
The Fact That The Radio Continues To Play Means You're Still Connected.
The "Choppiness" Will Be Due To The CPU Down-clocking While The Screen Is Off.
I'm A UK User Running CM7 And All Is Well. WiFi Sleep Policy Is Set To Never And I Always Receive E-Mail Notifications On My Phone Before My PC Notices So It Does Work! I'm Running One Of The Newest Nightly Builds.
Try Running SetCPU And Setting Up A Screen Off Profile To Up The Clock-speed Above Standard As It Goes Very Low When The Screen Is Off.
This Will Impact Your Battery Life But If You Find The Minimum Frequency Required To Eliminate The Choppy Playback You Can Live With It.
OllieD said:
The Fact That The Radio Continues To Play Means You're Still Connected.
The "Choppiness" Will Be Due To The CPU Down-clocking While The Screen Is Off.
I'm A UK User Running CM7 And All Is Well. WiFi Sleep Policy Is Set To Never And I Always Receive E-Mail Notifications On My Phone Before My PC Notices So It Does Work! I'm Running One Of The Newest Nightly Builds.
Try Running SetCPU And Setting Up A Screen Off Profile To Up The Clock-speed Above Standard As It Goes Very Low When The Screen Is Off.
This Will Impact Your Battery Life But If You Find The Minimum Frequency Required To Eliminate The Choppy Playback You Can Live With It.
Click to expand...
Click to collapse
Just to clarify my problem once more, doing anything over wifi with screen on is fine,streaming, uploading to dropbox,etc but after a couple of minutes with the screen off my transfer rate crashes,the wifi is going onto a power save as I am still connected(wifi connected icon still there), CM7 is the only ROM that I have this problem with,I use Unity and with screen off there are no problems,dont see how underclocking affects this as on Unity my screen off clock is 245Mz. I know you use the example of email notification,have you tried uploading files with screen off or streaming?
If that works then could you please send me a copy of your logcat to compare to my output?
I tried it no problems. But i prefer htc sense with android 2.2.
If ive was to choose a different rom apart from sense stock roms then it has to be miui.
Its fast and ui is superb.
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
jeff.p said:
... if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
That *is* the SOD. It's not caused by an app so much as meeting those conditions. For a quick fix set wifi to turn off when the screen turns off. Search is your friend for more info/fixes.
jeff.p said:
is there a list of known apps that cause the sleep of death?
i'm using the 7/30/12 mirage kang. the fresh install doesn't have SOD problems but after i restore my apps, if i let the screen go dark for ten minutes while wifi is running, i'm pretty much guaranteed SOD.
Click to expand...
Click to collapse
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
leapinlar said:
Like MISRy said, it is not a specific app causing it. It is the fact that you leave wifi on with the screen off. And not just specifically screen off, but in deep sleep. But it is not consistent and not everyone gets it. Some of the devs could never make it happen. Usually it is when wifi is on with screen off and an app is using it that is the problem. So if wifi is on and being used, and at the moment you try to turn it on it is in deep sleep, bingo SOD. As I said in the other thread, look at my tips.
Click to expand...
Click to collapse
i thought the fixed wifi module was included with all recent kernels
jeff.p said:
i thought the fixed wifi module was included with all recent kernels
Click to expand...
Click to collapse
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mrg666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
leapinlar said:
No, the kernel and wifi kernel module are two different things. The wifi kernel module has to be matched to the kernel (it is a kernel module), but is a separate piece of software. It is in /system/lib/modules/twlan_drv.ko. No SOD patches have been used in any stock CM7 kernels or modules. I think Mr666 uses a patched kernel for his Mirage build and sometimes it is enough, but SOD does not really stop until the patched module is used.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
jeff.p said:
ok. thanks for the info. i'll try the module at http://d01.megashares.com/?d01=8VPCE7N and report back
Click to expand...
Click to collapse
no SOD yet. awesome!
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
purpleurkle said:
Can u set wifi to go off in settings somewhere or do u need an app like green power? I only ask because that was what I did but after awhile, it won't let the wifi come on at all until I remove the app and reboot
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
Yes there is a setting. Go to wifi networks and select menu and advanced. There should be a wifi sleep policy setting.
I think there is no specific app which causes SOD
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
nauman_waheed said:
Dear all my friends who facing the SOD Sleep of Death issue with their Android devices...
i found that it is totally related to Wifi Sleep policy related... i just changed the setting last night n now after 8 hours it is running absolutely without SOD... i will also be inform u later if i will get my device out of SOD issue... all of u just have to do one thing.
Go to settings>wifi settings>
from the options go to advanced settings
there is one option: Keep wi-fi on during sleep (go to this option)
there is 3 options: 1. Always, 2. Only when plugged in, 3. Never (increases data usage)
u just have to change ur option from 1 to 2 or 3, then i hope u will find that u will get ur device out of SOD issue...
Regards,
Nauman
(sorry for the poor english)
Click to expand...
Click to collapse
it's not working on my s6 sprint
Sprint network having any problems here
Sent from my QMobile i12 using Tapatalk
It's been very bothersome. I did look on the web and found this thread about it, but there hasn't been an all-encompassing answer yet.
http://forums.androidcentral.com/go...lay-music-stopping-when-screen-turns-off.html
I don't appear to be running into this issue. Used Note 3 to start a freebie song on Google Music to play on Chromecast and it continues to play when Note 3 screen times out or when I hit the power button manually. If you've rooted/modified your Note 3 then you probably want to reflash back to stock to rule out any issues that were introduced.
This might be a really pointless suggestion, but as I don't use any of those I'll take a shot in the dark:
Does this setup use WiFi? If so, is WiFi set to disable during sleep?
Bump bump
Anyone a clue? (Evident causes are already ruled out). Regpon wifi KeepAlive app is a solution but it pretty much drains the battery.
Ha!! Just installed a new MK2 firmware ROM (Polish). Runs like a charm now. No issues.
EDIT: forget it. Worked the first time . A bit later .... crap, crap, crap....
With the faulty bluetooth connection with my carkit this is the worst device I've ever had... Next big thing turns out to be the next crappy thing for me...
appelflap said:
Ha!! Just installed a new MK2 firmware ROM (Polish). Runs like a charm now. No issues.
EDIT: forget it. Worked the first time . A bit later .... crap, crap, crap....
With the faulty bluetooth connection with my carkit this is the worst device I've ever had... Next big thing turns out to be the next crappy thing for me...
Click to expand...
Click to collapse
Check under Wi-Fi -> Menu -> Advanced if you have "Keep Wi-Fi on during sleep" set to Always. That (and the resulting Note 3 behavior and power consumption) might also be heavily influence by some of the power-saving / special broadcasting done in your WiFi router/AP.
xclub_101 said:
Check under Wi-Fi -> Menu -> Advanced if you have "Keep Wi-Fi on during sleep" set to Always. That (and the resulting Note 3 behavior and power consumption) might also be heavily influence by some of the power-saving / special broadcasting done in your WiFi router/AP.
Click to expand...
Click to collapse
Interesting, power-saving option in my router. What kind of parameters are you thinking about.
But do you have it working? Take a look at this forum thread http://forums.androidcentral.com/go...0-google-chromecast-note-3-disconnecting.html . This is a pain in the ass for a lot of users.
appelflap said:
Interesting, power-saving option in my router. What kind of parameters are you thinking about.
But do you have it working? Take a look at this forum thread http://forums.androidcentral.com/go...0-google-chromecast-note-3-disconnecting.html . This is a pain in the ass for a lot of users.
Click to expand...
Click to collapse
I have no Chromecast yet, so I can not test that, but when those WiFi settings are set badly you either don't go to full sleep with the phone (and power consumption is large) or you go without the correct wake-up wifi stuff and then you miss radio packets.
xclub_101 said:
I have no Chromecast yet, so I can not test that, but when those WiFi settings are set badly you either don't go to full sleep with the phone (and power consumption is large) or you go without the correct wake-up wifi stuff and then you miss radio packets.
Click to expand...
Click to collapse
Let's assume for simplicity that I literally tried everything on the Note when it comes to tweaking the WiFi setting (there's even a hidden settings menu, accessible by dialing *#0011#, in which you can set the WiFi Power saving off. That didn't work either).
So I know, theoretically you can speculate a lot but it won't help. There's something wrong with the Note or the play music app.
Sometimes the Play Music app force closes with a IllegalArgumentException, saying that a messagestream with namespace Ramp is already registered (that is definitely related to the chromecast API) . It happened a few times (very rarely though) when waking the device up when casting music via Chromecast.
But what was that about the Wifi router? What kind of parameters did you have in mind?
Same issue. All the settings on my phone are fine. Any other Chromecast supported app works regardless of my screen being on or off. WiFi on during sleep. Router configured properly... If I run Google Play Music from my desktop, and stream to my Chromecast I can play entire albums without a problem. On the phone, I can not. This is definitely a Note 3 problem.
Sent from my SM-N900V using Tapatalk
Now that I've got the Moto X Pure Edition activated, I've been able to work out some of the kinks inherent using it as a daily driver. One noteworthy issue that remains is an odd bug where the device will completely lose connection to the Internet on both a WiFi and cellular data connection, usually after transitioning between types of connections. When this happens, an exclamation point is displayed next to the icon representing whichever connection is currently active and nothing is able to transmit data to or from the Internet or even my local network.
Rebooting the device always fixes the problem, but this issue is materializing a bit too often for my liking, which is usually once every time that I return to a WiFi network after being disconnected from one for some time (more testing may have to be done to confirm exactly what triggers it).
The device is running the stock rom (rooted) and the stock kernel along with the usual tweaks (ad-blocking, Xposed framework, audio fixes, etc.). Anybody seen this before or know what might be causing it?
UPDATE (3/1/2017)
Figured it out! The problem appears to have been caused by my failure to whitelist certain applications in PowerNap. After following the instructions found in the Moto X Pure Edition power optimization thread, the problem appears to have vanished. I don't know if it was the Google Services Framework, JavaTcmdHelper, Android System, or some combination of those that needed to be whitelisted, but the problem has vanished. At least one of those must be responsible for verifying the validity of an Internet connection in sleep mode, which would cause the device to become confused when it would wake up with a different connection that it hadn't verified (that's my theory at least).
At any rate, it is no longer an issue.
Update (Later on 3/1/2017)
Well, it looks like it might not be fixed so well after all. A couple hours after arriving home today, I went to use the device and saw the dreaded "!" next to the network indicator. Still, two days is longer than it's ever lasted before. I've cleared the cache and dalvik/ART cache to see if something in there might be gumming it up and will add another post to this thread if the problem returns.
Still an issue
Looks like it might not be fixed after all. I lost connection again the other day in a parking lot and once more today after getting home. Any ideas as to what could be causing this?
I just recently got my x pure. I've seen this issue on mine too.
Another one!
inkdaddy66 said:
I just recently got my x pure. I've seen this issue on mine too.
Click to expand...
Click to collapse
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Bill720 said:
Interesting. Are you running the stock Rom? Rooted? Amplify/Greenify/PowerNap?
Click to expand...
Click to collapse
I'm unlocked and rooted. Running validus 7.1.1 ROM.
does your configuration look anything like this?
inkdaddy66 said:
I'm unlocked and rooted. Running validus 7.1.1 ROM.
Click to expand...
Click to collapse
That too is interesting. I'm running the stock Rom, (rooted) so we can probably eliminate that as a potential cause. Given how little reference there is to this on the web at large, the problem is probably caused by a common app or setting (or some kind of unfortunate combination) running on both of our phones.
All we need to do is figure out what kind of "unusual" stuff our devices have in common. I'll rattle off a list of software and settings that might be out of the ordinary or network-related; you tell me if you're running anything like it on your phone.
AdFree
A.R.I.S.E. audio
FolderSync
Ice Box (Motorola Update Service is the only frozen app)
TOTAL Wireless My Account App
Pebble, MyTracks, and Pebble MyTracks
SlingPlayer (this one sometimes wakelocks)
Titanium backup (I tried restoring some WiFi access points once, but it didn't work)
Xposed Framework with Amplify, Greenify, and Power Nap installed and configured as instructed in the Moto X Pure Edition battery life guide thread OP. I've also got MinMinGuard and YouTube AdAway.
As far as settings go, I've not got much in the way of unusual configurations. I enabled the system UI tuner to get the battery percentage and the extended developer options to try out multi-window, (and to change the animation scales to .5X) but everything in there is still pretty much stock.
Does your configuration have anything in common with mine?
Close, but no cigar
It got almost 8 days this time before it happened again. I thought that maybe switching to the legacy DHCP client had done the trick, but that was apparently not the case. Any ideas as to what could be causing the issue or how to fix it?
Or, if you're having the same problem, can you look at my list in the previous post and tell me if any of the software or settings are similar so that we can narrow down the cause?
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Anything familiar?
aybarrap1 said:
I have had this problem appear about three times over my 13 months of ownership and all three times was when my bootloader was still locked (obviously running stock not rooted). Never found a solution except to reboot.i only unlocked and rooted my device about a month ago.
Click to expand...
Click to collapse
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Bill720 said:
Interesting. Between that, my findings, and the fact that @inkdaddy66 was having the problem on a non-Motorola Rom, I want to think that we can eliminate the Rom software as a cause. Did you see any familiar software on my "potential troublemakers" list up in post 6? I'm thinking that if we can find a common program or workflow, then we'll be able to narrow down the cause of the problem.
In the meantime, I'll try posting in the general Android troubleshooting forum here on XDA and see if anybody there has seen the problem or has any troubleshooting tips.
Click to expand...
Click to collapse
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Cause and effect differential diagnosis
aybarrap1 said:
Nothing used from your list except system UI tuner when I experienced the problems. That would leave either a ROM and/or hardware issue IMO.
Click to expand...
Click to collapse
Hmmm... That's also interesting, but I just don't see how system UI tuner could be harming anything. Do you have any other apps or settings at all that you think could be causing the issue?
If this were anything other than my primary, I'd hard reset and troubleshoot that way, but I don't exactly have the time to pull the rug out of an otherwise-working setup right now, so this is going to have to be done the hard way (or, in the case of hardware glitch, lived with).
At any rate, I discovered a new symptom earlier in the week. This time, Internet connection was lost, but only for WiFi, so the connection would actually fall back to Cellular and still continue to work. As before, toggling the connection had no effect, but rebooting the device "fixed" it. I thought maybe it was a fluke, since we'd had an AP hiccup over the weekend, (I refuse to reboot that thing because I'm going for an uptime record) but it happened again on Wednesday, so I'm not sure what to make of it.
Side-issue aside, I'm beginning to wonder if it's some kind of combination of network behavior and usage pattern that brings the issue about. It seems like if I stay within range of the WiFi network, no issue develops, but if I move out of its coverage and don't touch the phone for a while, that allows for ideal conditions under which to replicate the problem (sometimes). I haven't nailed down a consistent pattern yet, but the problem does emerge more often when I'm returning home than at other times. Any thoughts?
Update (3/24/2017; 12:32PM)
Scratch that last part about the issue only being triggered upon "arriving home." The problem happened again this morning, in the same general area. First, no WiFI, then, after resetting the connections, no cellular either. I captured a LogCat before rebooting this time though. Anyone want to take a crack at sifting through that to see if it offers any clues?
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Possible fix
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
pizza_pablo said:
I lose cellular data, from time to time, I don't kow if I'm losing WiFi capability also, because I'm on the road when this happens.
It takes a reboot or switching in and out of airplane mode to regain data.
I have had this happen on TruPureXMM ROM and stock-rooted Marshmallow.
I have not spent much time on stock-unrooted, so i don't know if it would happen then, also.
Click to expand...
Click to collapse
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Bill720 said:
Just to follow up on this again, I have finally reached the eighth day of uptime without the problem materializing, which is the longest that I was able to go before without it happening. This time, I went in to the developer options and disabled "Cellular data always active." I'd give it another couple days to know for sure, but if this sticks, then I think we might've found the fix!
If your trouble is isolated to just one connection and/or cycling the connection brings it back, then the issue you are experiencing is unrelated to the one described in this thread.
Click to expand...
Click to collapse
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Always on is not necessarily a good thing. Reality is that when you lose or turn off WiFi, mobile data should only be delayed only by a second or two. There is no real benefit to having it on except for maybe VOLTE.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
Actually, it's a battery killer more than anything else... It keeps cellular data active even when on WiFi.
It is possible it's a tower thing though. I have noticed at this one hotel I stay at frequently people tell me they call and it rings or just goes to voicemail even though I have good signal. After investigating it a bit, I'm in a spot that has nearly identical signal strength from 3 towers and it's a metro area so there are 4+ bands accessible... I've seen times watching LTE Discovery where it keeps switching bands and towers for 30 to 120 seconds or so, like it can't make up it's mind what to talk to because it's confused, then it locks on for a while before it starts it's cycle again. During those cycles I think is when people can't call me, can't really say if it affects internet or not since I tend not to use my phone too much in the evenings when I'm on the road (usually on laptop).
Uptime record, but... it's back
acejavelin said:
Cellular data always active should never be on (it's disabled in stock rom), except if you have VoLTE only with no fallback to 3G or 2G (Jio is the only provider that comes to mind, but this phone doesn't support their service anyway) or otherwise unusual scenarios I can't really think of.
Click to expand...
Click to collapse
Interesting. I thought for sure that I had the default settings checked in there, but maybe I did change it early on and just forgot. Either way, waiting an extra five seconds to establish a data connection isn't that huge of a deal for me, so I'll leave it off anyway in exchange for battery life when the signal's poor.
At any rate, however, the problem has returned. I was just a few hours short of 9 days of uptime and really thought that I was out of the woods with this problem, but it has returned once again upon returning into range of the home access point. Looks like we're back to the drawing board on this one.
pizza_pablo said:
Huh, and CELLULAR DATA ALWAYS ACTIVE (for faster network switching) sounds like such a good thing.
Mine was selected on.
My loss of data happens in the same spot, usually, but is not leaving wifi. Perhaps it is a tower to tower handoff spot.
I turned it off. Time will tell.
Thanks, fellas!
Click to expand...
Click to collapse
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Bill720 said:
So you're having the same problem too? That makes at least four of us now. Do you mind sharing what Rom and flashed tweaks (Xposed Framework, A.R.I.S.E. audio, root, etc.) you're using as well as any unusual software or settings? Anything in common with my list on page 1?
Click to expand...
Click to collapse
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
*another* new strategy (sigh)
For this week's shot in the dark, I'm going to try manually switching WiFi off before I leave anyplace covered by an access point. Since the problem seems to occur most often when connected to WiFi or when connecting to it, maybe this will make some kind of a difference.
pizza_pablo said:
I think we've established that my issue is different, but it has occurred on TruPureXMM and stock but rooted Marshmallow, both with Substratum, Xposed (Gravity Box only) and Viper Atmos.
Same as you =Titanium Backup
Click to expand...
Click to collapse
I see now; my mistake.