Related
I recently flashed on cm7 on my aria. it is great but my data usage began shooting up. i realized it was due to the fact that everytime i lock my phone, it disables my wifi (i saw this because everytime i unlock im on 3g for a 1-2 seconds then i get on wifi so that means that the whole time my phone is locked it uses 3g data ) is there anyway i can prevent this from occurring??
Thanks,
Okachowwa
Menu -> settings -> wireless & networks -> wi-fi settings -> menu -> advanced -> wi-fi sleep policy -> never
I think that's it.
Sent from my Aria - CM7 Build 24
okachowwa said:
I recently flashed on cm7 on my aria. it is great but my data usage began shooting up. i realized it was due to the fact that everytime i lock my phone, it disables my wifi (i saw this because everytime i unlock im on 3g for a 1-2 seconds then i get on wifi so that means that the whole time my phone is locked it uses 3g data ) is there anyway i can prevent this from occurring??
Thanks,
Okachowwa
Click to expand...
Click to collapse
Have you checked the Wifi Settings to see which sleep option is selected? There is an 'Never' option which tells wifi to stay on even when the phone sleeps.
One thing I noticed its that if I leave my house I have to turn off wifi and turn it back on to find my router.
Sent from my Liberty using XDA App
klbmth said:
One thing I noticed its that if I leave my house I have to turn off wifi and turn it back on to find my router.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
yup...that's why you just turn your wifi off with the notification widget (very simple and painless might I add) if you know you're leaving the house...what's the point of having wifi enabled if you're not in range of your network? all it's going to do is drain your battery. i left my wifi enabled one day when i sent to work and within half the day i had ~12% battery life...definitely not good practice to leave it enabled that's my 2 cents, do as you wish though. to each his own.
klbmth said:
One thing I noticed its that if I leave my house I have to turn off wifi and turn it back on to find my router.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Yup, I have the same issue with CM7 nightlies. This worked flawlessly in CM6 and stock2.1. So far there isn't a viable solution.
from the CM6.1.1 thread...
Q. How do I keep my wifi from going to sleep every time the screen shuts off?
A. There is a hidden feature that disables wifi sleep.
menu > Settings > Wireless & networks > wifi settings > menu (again) > advanced > Wi-Fi Sleep policy > Never > menu > Save
However: although you can keep the wifi service from sleeping, the wifi driver will still sleep on it's own after detecting no bus activity for a period of time.
Click to expand...
Click to collapse
mattbollenbach said:
from the CM6.1.1 thread...
Click to expand...
Click to collapse
I've made sure to set Wifi Sleep Policy to "Never" but that did not fix my wifi problems. What I see when I open Wifi Settings is a cycle of:
Code:
Scanning --> Connecting --> Disconnected... Scanning, etc
When I look in logcat it shows it attemping (in vain) to authenticate against the last wifi network I was using -- even though it is no longer in range (and clear across town). In a nutshell it is refusing to recognize the actual nearby network UNTIL I toggle wifi settings.
I've had the same behavior on FR008 and the stock ATT 2.1 load as well. When Wifi is in that on but not really connected state some apps can wake it up...the default browser usually will, but Listen would not. I just gave up and only turn on wifi when I need it.
kinggrowler said:
I've made sure to set Wifi Sleep Policy to "Never" but that did not fix my wifi problems. What I see when I open Wifi Settings is a cycle of:
Code:
Scanning --> Connecting --> Disconnected... Scanning, etc
When I look in logcat it shows it attemping (in vain) to authenticate against the last wifi network I was using -- even though it is no longer in range (and clear across town). In a nutshell it is refusing to recognize the actual nearby network UNTIL I toggle wifi settings.
Click to expand...
Click to collapse
What is the point of having wifi set to ON when you are not in range of a network? Hence why, if you are using CM7 or CM6, you should utilize the notification widget and turn wifi off if you know you're leaving the area of your network. It's simple. Things aren't ALWAYS going to work how YOU want them to work. Thing will not always be automatic. I think I quote attn1 when I say this, just because it doesn't work how you want it to work, does not mean it is broken.
zervic said:
What is the point of having wifi set to ON when you are not in range of a network? Hence why, if you are using CM7 or CM6, you should utilize the notification widget and turn wifi off if you know you're leaving the area of your network. It's simple. Things aren't ALWAYS going to work how YOU want them to work. Thing will not always be automatic. I think I quote attn1 when I say this, just because it doesn't work how you want it to work, does not mean it is broken.
Click to expand...
Click to collapse
Well, just because people don't work exactly like you work, does not mean they are doing it wrong. If something is broken I'm going to call it out. I might be incorrect, but let's be clear: you aren't questioning that wifi in CM7 isn't working the way it did in CM6, you are questioning my behavior -- which is a weak argument.
I guess you don't understand the issue, so I'll spell it out:
Wifi worked flawlessly and automatically for me in stock 2.1 AND CM6. This automatic behavior does not work in CM7. Manually toggling something that simply "just worked" before is a regression, not a feature. Hence the reason I point it out -- the devs can't fix something unless they know it's broken, and I seriously doubt the devs are able to test all/every permutation. I have nothing but respect for the work they do, thus my very respectful tones in my earlier posts. I've had no indication that the devs are unwilling to get feedback about their work.
You asked a question though, and here is the answer:
I leave Wifi on all the time because I'm a consultant -- I work in many different locations throughout the week, travelling the country. I have dozens of wifi networks saved on my phone, and it is useful for me to have my phone automatically jump on the correct, nearest network. I'd rather use free wifi instead of paying AT&T for data charges. It is not always possible for me to remember I'm in a location with a known wifi network, or to remember to manually toggle wifi settings: it is useful for me to have this happen in the background. Sometimes I'm on a call, sometimes I'm heading into a meeting and I'd rather not mess with my phone. I want wifi to be on all time, scanning for the correct network, and jumping on it when it's in range.
Outrageous, right?! Not actually -- this is the existing behavior in CM6 and stock 2.1. From my standpoint, wifi just worked -- I didn't have to think about it, didn't have to manually toggle something to prevent AT&T data charges.
This is desired behavior for me, and I'm happy with rolling back to CM6 to get it. I understand that _you_ don't need this behavior, but that doesn't mean it's wrong. It just means the world is bigger than you realized.
And yes: wifi in CM7 (beta) is currently broken. Read the threads. Many people are having problems with it.
zervic said:
yup...that's why you just turn your wifi off with the notification widget (very simple and painless might I add) if you know you're leaving the house...what's the point of having wifi enabled if you're not in range of your network? all it's going to do is drain your battery. i left my wifi enabled one day when i sent to work and within half the day i had ~12% battery life...definitely not good practice to leave it enabled that's my 2 cents, do as you wish though. to each his own.
Click to expand...
Click to collapse
That's a good tip, I feel kind of dumb for not thinking about it lol and I also agree that it is good practice to do so. I just wanted to point it out in case a dev was going through this thread which is relevant to the topic.
Sent from my Liberty using XDA App
kinggrowler said:
Well, just because people don't work exactly like you work, does not mean they are doing it wrong. If something is broken I'm going to call it out. I might be incorrect, but let's be clear: you aren't questioning that wifi in CM7 isn't working the way it did in CM6, you are questioning my behavior -- which is a weak argument.
I guess you don't understand the issue, so I'll spell it out:
Wifi worked flawlessly and automatically for me in stock 2.1 AND CM6. This automatic behavior does not work in CM7. Manually toggling something that simply "just worked" before is a regression, not a feature. Hence the reason I point it out -- the devs can't fix something unless they know it's broken, and I seriously doubt the devs are able to test all/every permutation. I have nothing but respect for the work they do, thus my very respectful tones in my earlier posts. I've had no indication that the devs are unwilling to get feedback about their work.
You asked a question though, and here is the answer:
I leave Wifi on all the time because I'm a consultant -- I work in many different locations throughout the week, travelling the country. I have dozens of wifi networks saved on my phone, and it is useful for me to have my phone automatically jump on the correct, nearest network. I'd rather use free wifi instead of paying AT&T for data charges. It is not always possible for me to remember I'm in a location with a known wifi network, or to remember to manually toggle wifi settings: it is useful for me to have this happen in the background. Sometimes I'm on a call, sometimes I'm heading into a meeting and I'd rather not mess with my phone. I want wifi to be on all time, scanning for the correct network, and jumping on it when it's in range.
Outrageous, right?! Not actually -- this is the existing behavior in CM6 and stock 2.1. From my standpoint, wifi just worked -- I didn't have to think about it, didn't have to manually toggle something to prevent AT&T data charges.
This is desired behavior for me, and I'm happy with rolling back to CM6 to get it. I understand that _you_ don't need this behavior, but that doesn't mean it's wrong. It just means the world is bigger than you realized.
And yes: wifi in CM7 (beta) is currently broken. Read the threads. Many people are having problems with it.
Click to expand...
Click to collapse
fyi CM6 & 2.1 != CM7. Your argument is null & void.
Also, being a "consultant" and the very important man you are, flashing a rom that's not even in beta stages yet probably isn't the best idea you've ever had.
zervic said:
Also, being a "consultant" and the very important man you are, flashing a rom that's not even in beta stages yet probably isn't the best idea you've ever had.
Click to expand...
Click to collapse
Why do you remind us that the rom is in a beta stage? "Beta" implies it is not fully functional, but your argument all along has been that it works perfectly....
Look, it's clear you haven't actually understood any of my posts. I'm highlighting error messages or erratic behavior I see in logcat running CM7. I've posted what I've seen so the devs can take action, or not, as they choose. Since you aren't in that audience I don't understand what your beef is.
Oh wait! Straw man arguments; personal attacks; logical fallacies: I've been dealing with either a highschool student or a troll - not sure which.
zervic said:
fyi CM6 & 2.1 != CM7. Your argument is null & void.
Click to expand...
Click to collapse
...although I have a strong suspicion.
kinggrowler said:
Why do you remind us that the rom is in a beta stage? "Beta" implies it is not fully functional, but your argument all along has been that it works perfectly....
Look, it's clear you haven't actually understood any of my posts. I'm highlighting error messages or erratic behavior I see in logcat running CM7. I've posted what I've seen so the devs can take action, or not, as they choose. Since you aren't in that audience I don't understand what your beef is.
Oh wait! Straw man arguments; personal attacks; logical fallacies: I've been dealing with either a highschool student or a troll - not sure which.
...although I have a strong suspicion.
Click to expand...
Click to collapse
First of all:
attn1 said:
Just because something does not work they way you'd like it to doesn't mean you've discovered a bug.
Click to expand...
Click to collapse
That being said. Beta does NOT necessarily imply that thing are not fully functioning, it simply implies that it hasn't been put into RC or stable. You can have a fully functioning beta program. HOWEVER, it may not be working properly. But creating a thread about an issue that's been brought up 20+ times now is pointless. I'm PRETTY sure the devs know about the issue, should it actually be an issue. Now that I just wasted another 15 seconds of my life, i'm going to casually /part from this thread and I'll end my post with this quote again, in case you didn't catch it the first time.
attn1 said:
Just because something does not work they way you'd like it to doesn't mean you've discovered a bug.
Click to expand...
Click to collapse
This is for OP and very important man of the day, kinggrowler:
http://forum.xda-developers.com/showpost.php?p=11171075&postcount=1054
and i'll even quote it directly for you:
attn1 said:
There are no broad wifi issues to resolve, and I do not plan to change the wifi driver one iota. I am using the one that works right for most people, and flawlessly for me.
If you are not having such luck, then you need to look at your access point if you have already wiped data.
Really, the constant carping about wifi is absolutely pointless.
Click to expand...
Click to collapse
I believe the proper thing for me to say right now would be:
game. set. match.
Me too. I can't roam between networks, either. I have to disable and re-enable the wifi each time.
zervic said:
...what's the point of having wifi enabled if you're not in range of your network?
Click to expand...
Click to collapse
1) Because Google Maps uses known wifi hotspots to help establish your location.
2) So that you don't have to keep toggling wifi on and off when moving between hotspots (or home and work, for example).
3) To use the network notification feature (aka "notify me when an open network is available").
HTH
Edit: seems to be fixed in RC3!
zervic said:
What is the point of having wifi set to ON when you are not in range of a network? Hence why, if you are using CM7 or CM6, you should utilize the notification widget and turn wifi off if you know you're leaving the area of your network. It's simple. Things aren't ALWAYS going to work how YOU want them to work. Thing will not always be automatic. I think I quote attn1 when I say this, just because it doesn't work how you want it to work, does not mean it is broken.
Click to expand...
Click to collapse
i have try everything and still same issues with wifi. and i change the radio ( baseband ). still i am thinking of uninstalling it bc i dont have wifi
Sorry to tell you but that was with the old wifi stuff (every nightly up to build 25), which I had no problem with. The RC/nightlies have new wifi data made by jznomoney, which I have on and off problems with. Its working for most people but there are a handful who are having problems. I flashed ladios' kernel and my wifi is doing a lot better with the new RC/nightlies.
Signatures are fancy.
kinggrowler said:
I've made sure to set Wifi Sleep Policy to "Never" but that did not fix my wifi problems. What I see when I open Wifi Settings is a cycle of:
Code:
Scanning --> Connecting --> Disconnected... Scanning, etc
When I look in logcat it shows it attemping (in vain) to authenticate against the last wifi network I was using -- even though it is no longer in range (and clear across town). In a nutshell it is refusing to recognize the actual nearby network UNTIL I toggle wifi settings.
Click to expand...
Click to collapse
I've noticed something similar with CM7 on my Aria. When I leave the house and come back it doesn't always connect automatically and it will enter into this cycle of scanning, connecting, disconnected.
I had to reboot the phone to get it to stop the cycle and stay connected. I don't use a lot of data anyway but I still prefer to use wifi when available. Interestingly just now it wouldn't even see any of my neighbor's wifi networks at all which is odd.
Since upgrading to the EB01 Froyo leak (debinged/deodexed) I have wifi issues where every 3 or 4 times I attempt to enable it, it will fail, and show "Error" under the Wi-Fi settings (where it ususally says in blue text "Turn on Wi-Fi", "Connecting..." "Connected to <network>", etc). I finally got the log message associated with it, and was wondering if anyone has figured out a way to address this?
From what I gather insmod is the kernel's mechanism for (in this case) loading the wifi driver, so this would be an issue with the kernel? So now what?
E/WifiHW ( 2467): return of insmod (args:firmware_path=/system/etc/wifi/bcm4329_sta.bin nvram_path=/system/etc/wifi/nvram_net.txt dhd_watchdog_ms=10 dhd_poll=1) : ret = -1, Invalid argument
At first I thought a reboot was necessary to get it to attempt to reload the driver, but I've since found clearing level 2 ram in the task manager does the trick. Still a big PIA though.
Thanks for any help.
Kidd_Funkadelic
I had the same problem until I flashed the EC10 kernel, hasn't happened since.
AlgorithmX said:
I had the same problem until I flashed the EC10 kernel, hasn't happened since.
Click to expand...
Click to collapse
So, if I'm not mistaken I can just install the non-voodoo zip w/ Red CWM directly over EB01 with no wiping/cache clearing, etc, and be up and running with no data or configuration loss? Sounds like a pretty quick and easy way to fix my issue.
I haven't been following the EC10 thread, but I just took a look and looks like the static issue when the screen comes on during a call is fixed as well, the only other issue I've had.
Guess I may have to give it a shot! How long have you been using it?
KF
I've been using it for a couple days and have to say that it combined with SuperClean 2.9 has made my phone super smooth. I haven't found a single glitch so far.
Took the plunge and updated to EC10 last night. I've had only a brief time to play around with it, but so far so good with the wifi. Thanks for the help!
Could just be my mind playing tricks on me, but I could swear in general everything is more responsive as well... Not only loading apps, but when I brought up navigation this morning I've never once seen it lock on and start driving directions this fast.
Nevermind... Same problem still with EC10. Got my hopes up there for a minute.
I got the same problem with SC 2.9.2v and had with any other SC Froyo build. I'm using JuiceDefender so WiFi is turned on/off lot of times (every 15 minutes on schedule or when screen is unlocked). Usually once or twice a day I find that there is an error with WiFi and the only way to fix it is to wait couple of minutes and try turning it on manually or switch to airplane mode on/off.
I also use JuiceDefender w/ Wifi. If it doesn't occur less often with EC10 (too soon to tell still), I'll have to disable the wifi controls in JD so it's toggled on/off far less frequently.
Glad to see I'm not the only one seeing it. I bet the JD users will just notice it more since we are loading the wifi driver all the time.
Kidd_Funkadelic
And thanks for the airplane mode tip- I'll have to try that. I was clearing level 2 ram in task manager to do it. AM would be slightly more convenient.
jt1134's source build EC10 didn't help, still having same problem with WiFi. My log is showing the same thing.
At least the new kernel fixed the static issue. One thing at a time, right? I hope that this means there will be ED01 kernel drop
Actually, maybe April Fool's day is a bad choice...
What radio are you using? EB01?
Yes, I did the full Froyo update to EB01 over the stock 2.1 Verizon eclair, then installed the EC10 specifically for this issue. That's all I've done. Oh, went back into CWM after seeing the problem for a few days to clear the Dalvik cache. That's all I've done to date...
OK so it's not radio related but kernel/rom then. I'm on EA28 radio cause I had problems with missed calls with EB01.
Solutions? Bump?
Sorry for reviving this thread, but I have what I think is the same problem (on EB01).
My wifi always works after a reboot, but then if I turn it off and try and turn it back on, it gives me an error message until I either
A) reboot the phone
or
B) repeatedly turn it on and off again (usually takes 3 or 4 times to work again)
Anyone else having this specific problem or know how to fix it?
jbjcurly said:
Sorry for reviving this thread, but I have what I think is the same problem (on EB01).
My wifi always works after a reboot, but then if I turn it off and try and turn it back on, it gives me an error message until I either
A) reboot the phone
or
B) repeatedly turn it on and off again (usually takes 3 or 4 times to work again)
Anyone else having this specific problem or know how to fix it?
Click to expand...
Click to collapse
I was able to get rid if the problem by using Auto Killer Memory Optimizer. It turned out to be a memory issue. Use one of the preset profiles, like aggressive, and see how you do. I was having the problem several times a day and it never came back.
Or, upgrade to PWGB, which takes care if the problem too and doesn't require messing with memory mgmt settings...
After a few searches, I still can't find any posts about the exact issue I'm having with my WiFi.
Often my WiFi won't connect to my routers I have saved when I turn it on or leave one location and enter another. It will just sit at scanning until the moment I open the WiFi settings menu, then it suddenly finds routers. I can let it sit for a long time and it still won't find anything until I click the settings, then they pop up and connect automatically like they should.
Is this a common issue, or is i just my X2?
What ROM/android version number are you running? Need more data to tell you what is going on.
It's been no matter what ROM. CM9, Eclipse, stock, it's always done it. Not every time, but randomly hit and miss.
There is a known issue with CM7 not staying connected to wifi, but that was fixed with CM9.
That issue shouldn't happen on stock though. It almost sounds like a hardware issue in your case.
That's what I was wondering. It's been the same since I've had it, and has never gotten worse, so I've just lived with it.
Droid X2 > Eclipse 2.2.1 > Tapatalk
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Stuckinabox said:
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Click to expand...
Click to collapse
I have the same symptoms. Even with stock ROM 2.3.5.
Stuckinabox said:
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Click to expand...
Click to collapse
Exactly. I don't ever get disconnects on any ROM. Though while settings can't find any networks is pretty uncommon, it happens.
Stuckinabox said:
Yeah I can confirm this, mine does the exact same thing.
I don't get the disconnects that some people do (I may be using a patch related to the wifi sleep policy, I can't remember which roms that applies to), but it does the thing where it suddenly connects when you open settings, or the pulldown toggle only works half the time, or if you toggle it and then go to settings it can't actually find any networks.
Click to expand...
Click to collapse
Exactly. I don't ever get disconnects on any ROM.
DigitalMD said:
I have the same symptoms. Even with stock ROM 2.3.5.
Click to expand...
Click to collapse
Yup, even with stock. And every ROM I've ever tried.
It's kinda good to know it isn't just me.
I am using the HTC Amaze Energy ICS Rom latest 6/21 update without any modifications to the kernel etc. I love the rom but every now and then, the screen gets black after initiating a call. The only way to fix that is by taking off the battery and replacing it.
I tried looking for a fix around XDA but could not find a fix.
Any recommendations on how to fix this issue will be greatly appreciated.
Thank you.
Black screen
Try setting the lower cpu freq to 384. I found no frills cpu controller simple and works great.
There are quite a few posts regarding this issue.
Hi,
Sorry to jump aboard your thread with almost the same question.
I been using this rom since almost came out, I went throught all the different updates without any issues I installed the 8/6 version on that same date and not until now I'm experiencing this black screen issue but mine is not after a call, it's everytime the screen goes to sleep then it's a paint to get it awake again I'm starting to hate this phone.
The issue seems to have started after I travelled to a different country and I used a prepaid sim.
Came home and the phone started to act weird I re flashed the rom but since I was restoring data from a recovery (4ext) backup seems to drag whatever errors were there so since I didn't want to lose all my games scores and data I did a backup/restore with Titanium but even though all the other issues are gone the black screen stayed.
The CPU is already set @ 384 so that is not the issue and as I said it happens when the screen goes to sleep (not during calls) either by itself or if I do it myself.
When I press the on button (or the camera one) to wake it up only the four buttons on the bottom light up.
Any help?????
Thanks,
ferincr said:
Hi,
Sorry to jump aboard your thread with almost the same question.
I been using this rom since almost came out, I went throught all the different updates without any issues I installed the 8/6 version on that same date and not until now I'm experiencing this black screen issue but mine is not after a call, it's everytime the screen goes to sleep then it's a paint to get it awake again I'm starting to hate this phone.
The issue seems to have started after I travelled to a different country and I used a prepaid sim.
Came home and the phone started to act weird I re flashed the rom but since I was restoring data from a recovery (4ext) backup seems to drag whatever errors were there so since I didn't want to lose all my games scores and data I did a backup/restore with Titanium but even though all the other issues are gone the black screen stayed.
The CPU is already set @ 384 so that is not the issue and as I said it happens when the screen goes to sleep (not during calls) either by itself or if I do it myself.
When I press the on button (or the camera one) to wake it up only the four buttons on the bottom light up.
Any help?????
Thanks,
Click to expand...
Click to collapse
I had the exact problem.
I fixed this by reflashing my rom but there was another way i fixed this as well. A much easier way is just to download the Market App 'Pimp My Rom' . Theres a feature in that app, that fixes this exact problem.
Thanks a lot!
I got it. It looks good (and scary for a noobie)
Is there anything I need to tweak in there or just installing it would take care of it?
Thanks.
Edit: I found "no black screens after a call" under miscellaneous should I tick that one? even though my problem is not specifically after a call?
ferincr said:
Thanks a lot!
I got it. It looks good (and scary for a noobie)
Is there anything I need to tweak in there or just installing it would take care of it?
Thanks.
Click to expand...
Click to collapse
You have to do something specific inside the app.
I'll give you a step-through-step guide so you can fix this annoying problem!
1. Download the free app!
2. Open the app
3. you'll see tabs, "Main menu, tools, tweaks, Apps & mods, extras, and help center". go to the TWEAKS tab.
4. Then you'll see 7 categories. "Network & internet , multitasking,Dalvik VM, Kernel tweaks, Enable/disable features, Telephony, and Miscellaneous tweaks" SCROLL DOWN AND CLICK ON THE MISCELLANEOUS TWEAKS category
5. Scroll down till you see "No Black-Screen after a call" , then tick the little box to the left of it.
6. Scroll down and click on "Apply Selected Tweaks"
7. It'll ask to reboot, but unfortunately the reboot button the app gives you doesnt reboot the phone, so reboot your phone manually after you did step 6.
8. you're DONE
---------- Post added at 04:34 AM ---------- Previous post was at 04:33 AM ----------
ferincr said:
Edit: I found "no black screens after a call" under miscellaneous should I tick that one? even though my problem is not specifically after a call?
Click to expand...
Click to collapse
Yes, the fix worked for me , and mine wasnt after the call.
Thanks a lot Kevin!!!!!!
I' ll see what happens today, I don't know if it's psycological or what but the phone seems more lively already
Fernando
ferincr said:
Thanks a lot Kevin!!!!!!
I' ll see what happens today, I don't know if it's psycological or what but the phone seems more lively already
Fernando
Click to expand...
Click to collapse
Any time
ferincr said:
Thanks a lot Kevin!!!!!!
I' ll see what happens today, I don't know if it's psycological or what but the phone seems more lively already
Fernando
Click to expand...
Click to collapse
Have you succeed to resolve your problem. I have something similar on a Stock Rom. I have described my problem in this thread.
zandgreen said:
Have you succeed to resolve your problem. I have something similar on a Stock Rom. I have described my problem in this thread.
Click to expand...
Click to collapse
I think he did, the app basically does what your fix does
kevinrubio1 said:
I think he did, the app basically does what your fix does
Click to expand...
Click to collapse
It will sound stupid but I have found a simple solution:
I have just wiped the screen in the upper left corner where the proximity sensor is located and it started behaving normally. Though I don't use any protection tape on the screen it seem to have become less sensitive because of mud or sweat.
No I haven't solved it. But mine is not after a call it's when the screen been off for a while.
Yesterday after a total software corruption (it wouldn't even boot) I went to stcok (again) and started from zero. Worked well for few hours and this morning I was back with the spolied brat phone.
So, I'm testing stock RUU for a full day today and see what happens.
Try to catch some log when the phone begins to behave badly.
zandgreen said:
Try to catch some log when the phone begins to behave badly.
Click to expand...
Click to collapse
???
No idea how to do that.
But I'm very confused...
I read in few ocasions that if your bootloader is unlocked you cannot flash the stock RUU.
In my case is the other way around, actually now I'm running the stock Tmous rom with unlocked hboot, S-OFF and rooted (and so far the phone is working ok) no black screen so far.
What the hell is wrong with it. It has to be something I do when I flash ROM, Kernel or Hboot...
I'll stay like this until tomorrow to see if I do get black screens at any point.
ferincr said:
???
No idea how to do that.
But I'm very confused...
I read in few ocasions that if your bootloader is unlocked you cannot flash the stock RUU.
In my case is the other way around, actually now I'm running the stock Tmous rom with unlocked hboot, S-OFF and rooted (and so far the phone is working ok) no black screen so far.
What the hell is wrong with it. It has to be something I do when I flash ROM, Kernel or Hboot...
I'll stay like this until tomorrow to see if I do get black screens at any point.
Click to expand...
Click to collapse
You can't flash an RUU with a locked bootloader, UNLESS you are s-off. That's y u were able to
sent from my
NRGized amaze
powered by Faux
Ohhhh!
Ok Now I feel better. I didn't know what to make of that statement.
I thought I was either doing something wrong or totally misunderstanding the lingo.
ferincr said:
???
No idea how to do that.
Click to expand...
Click to collapse
Use aLogcat app from the Play store.
I been doing more tests and yesterday I run it on stock most of the day with no apparent issues, then I restored the NRG rom from a backup and still no issues so I started to think it was something I messed up flashing the JB Hboot,since the restore changed rom and kernel but not the Hboot.
I restored a backup of a bulletproof rom and decided to do another test.
I sat on the phone as to block signal and the issue came back.
Now I'll try the same with NRG, yep it seems like it's when the phone loses signal the screenwon't come back afterwards.
I'll look for that app
I upgraded my phone to KK back in late december and have been on it ever since but one problem has plagued me since then and I'm hoping to get some insight here. heres the problem...
When im connected to wifi (and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.Often i turn my screen on and get a barrage of notifications that i should have gotten hours ago. Ive tried all the sleep modes and Ive tried turning off wifi optimization.Nothing works and I know for fact it did not do this on JB.
I DO get text messages and phone calls instantly though but nothing else will wake my phone up. While i do enjoy the deep sleep, i would like to get my notifications in a reasonable amount of time without having to turn the phone on to check them.
Has anyone else had this "problem"?
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
SteveMurphy said:
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
Click to expand...
Click to collapse
Yeah i know and I've googled it to death for a few months now. I'll check g settings but idk why that would stop gmail. It's like when I'm on Wi-Fi w/ the screen off its just a plain old dumb phone. I turn the screen on and the notifications just flood in.
Edit: nothing in g settings is muted. The only thing i can think of is i don't have app data synced in accounts.
I think i figured it out. I had "sync app data" unchecked in accounts. So far I've been getting notifications screen on and off. Now if someone will just play back to me on wwf...
EDIT: i may have spoke too soon. It still doesnt wake up without turning on my screen
hey @SteveMurphy do you by chance use the active display?
razen_kain said:
hey @SteveMurphy do you by chance use the active display?
Click to expand...
Click to collapse
I did when I was using Omni and it worked great. I haven't used it since running RR, however.
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
razen_kain said:
[...](and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.[...]
Click to expand...
Click to collapse
cyril279 said:
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
Click to expand...
Click to collapse
No i never turn mobile data off. I just meant that notifications come as expected when I'm on mobile data but on Wi-Fi, once the phone hits deep sleep (<a minute) i won't get notifications unless i turn the screen on.
I ask about active display because i remember when on resurrection ROM i was using it and getting notifications then and kind of forgot about it but I'm on PAC 4.4 now and it's doing it again. However i was using the init.d scripts they have baked in but have them all turned back off now to see if that fixes it.
It's the strangest thing I've seen. It's like when I'm on Wi-Fi and turn the screen off it just disconnects from all data even though i can plainly see that it is not. Angela has the same phone with the same settings as mine but on RR 5.0.5 and she gets notifications fine.
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
razen_kain said:
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
Click to expand...
Click to collapse
cyril279 said:
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
Click to expand...
Click to collapse
Well all my testing so far has lead me no where with the exception of using that app. So far, I've not been able to reproduce the problem while using it. The question is,"what is it doing" to make it work....
EDIT: The app does not fix it....
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
razen_kain said:
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
Click to expand...
Click to collapse
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
Click to expand...
Click to collapse
Its 4.4 and I have faced this issue on every rom Ive tried since switching to KK. Im starting to wonder if it's not an issue with my wifi. Im wondering if maybe my wifi is suspending my connection when my phone goes quiet.
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms...
Click to expand...
Click to collapse
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
SteveMurphy said:
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
Click to expand...
Click to collapse
It's always good to have you around buddy.
[SOLVED] Not Receiving Notifications on WiFi
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Great news, glad it was an easy fix!
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
Great news! Now you just need to install DD-wrt on your router and turn it from a $40 router to a $400. I know you like to tinker but check it out. ITs free and its just firmware for certain routers. It turned my old wrt54g into a baus
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
I'm having the same issue with KitKat CM11 ROM on my HP Touchpad (which is WiFi only), and will have to try this. Notifications come in instantly on my iPhone/iPads, but my Touchpad gets some serious delays...sometimes right away, and sometimes delayed.
By the way, did "Sync App Data" setting for an account have anything to do with push notifications, or is that more for backup purposes?
---------- Post added at 02:32 PM ---------- Previous post was at 02:04 PM ----------
Oh darn, mine is still delayed even with the push notification fixer installed and WiFi heartbeat at 5min. Even after I've just rebooted my Touchpad, actively using it, and not even 5 minutes has passed. Delay was 8 minutes and then the notifications came streaming in.
With Android/KitKat, do you have to have the app open in the background for push notifications to go thru? Or run the app at least once after a reboot?