I am on the latest cyanogenmod nightly and wifi drops whenever I turn the screen off , wifi off during sleep is set to never. I would have posted this in the nightly thread but apparently I don't have enough posts.
Probably an issue with the latest CM nightly
Just to clarify you are not running anything such as tasker where it would turn wifi off right?
mistahseller said:
Probably an issue with the latest CM nightly
Just to clarify you are not running anything such as tasker where it would turn wifi off right?
Click to expand...
Click to collapse
Nope not using tasker, I thought it might be the nightly too but people are usually pretty quick to point out when something as big as wifi breaks in the nightly thread
I rebooted my router and the problem seems to have gone away for now. Strange that it only happens during. Sleep though.
Related
Am I the only one whose Wifi disconnects on sleep even when set to NEVER under Wifi Settings? Got this with BAMF 2.0 AND Gingervitis VIII
Annoying as hell...
Any fixes?
I noticed that it does it when tethering haven't used wifi that much.
I had the same problem on BAMF 2.041 but have not noticed it on Gingeritis VIII, however I have not tried to download anymore roms, since this one is working so well.
Will test to see now...
Hmm. I've never seen that before. I've been on both of those roms and many others. I have wifi on all night, every night.
Is it on the whole time or is it turning off when screen is off, then turning on when you wake it up. I haven't messed with the wifi. I do know when tethering my ipad, I have to wake up my phone to connect every time.
I am finally at 10 posts
I have not changed any WiFi settings in bamf 2.0.4 and the WiFi never goes to sleep on me. I had it happen when I flashed the plain Jane GB Rom using cmw. I just booted into recovery and manually installed it and it stopped the WiFi issue.
Sent from my ADR6400L using XDA Premium App
gordon84
I had the same issues with BAMF 2.xxx but flashing Gingeritis VIII seemed to fix the issue.
gordon84 said:
I had the same issues with BAMF 2.xxx but flashing Gingeritis VIII seemed to fix the issue.
Click to expand...
Click to collapse
It fixed mine too
I've searched high and low for this issue, and I've found hits, but nothing that seems to help me or fully answer my questions.
I flashed CM10 nightlies straight away when I got my new Galaxy Tab 2 10.1 last week. Whilst it's a great ROM like with all official CM's, the tab sporadically doesn't wake up after a sleep.
Now the known issues from http://teamhacksung.org/wiki/index.php/CyanogenMod10:GT-P5100:Nightly:Known_issues says:
Code:
The screen many a times does not respond to touches for unlocking, needed to reboot the tablet.
Which seems to be what I'm experiencing. All I would like to know if I'm the only one experiencing this issue and if not, do people know if the issue is being actively worked on and is there a workaround in the mean time?
Thanks in advance.
Are you overclocking?
Posted from my Fascinate using XDA Premium
MultipleMonomials said:
Are you overclocking?
Click to expand...
Click to collapse
Thanks for the response. I'm not overclocking running at the default 300MHz to 1008MHz from the stock CM kernel settings on the interactive govenor.
I did however install the kernel from the AOKP thread. Ran that over the weekend and never saw the screen wake problem again. As soon as I installed the latest CM nightly the screen wouldn't wake from sleep again so I re-installed the AOKP kernel and everything was working again.
(I also noticed that the AOKP kernel came with CPU settings of 300MHz to 1200MHz on the interactive govenor - I put that back to 300MHz to 1008MHz for safety but didn't see the screen wake problem during my testing with the higher clock speeds).
Has anyone got any info on this screen wake issue?
The amount of times I was having to reset the tablet when I was using the stock CM kernel meant it wasn't usable as a daily device until I installed the AOKP kernel. How can I get in touch with the CM guys to see if I can help with this screen wake issue?
You'll need to find a proxy to post for you in the dev forums in Codeworkxx's thread. You'll need a logcat of the issue.
Posted from my Galaxy Tab with CM10
MultipleMonomials said:
You'll need to find a proxy to post for you in the dev forums in Codeworkxx's thread.
Click to expand...
Click to collapse
Or you could just go to their irc channel #teamhacksung-support @freenode
ok thanks, will try to get a logcat and post is in the DEV forum
My POWERAMP, I did buy the unlocker. Keeps skipping like there's some major app usage going on. But I check and memory and CPU usage is MINIMAL! Any ideas? Going flash to most updated see what happens but wanted to let the community know deuces! EggyT
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Did you try clearing data?
The only issue I have with pa is the lock screen function is a bit wonky.
Im on ... TY I will reply with an answer ASAP Cheers
Well it is not happening as freq but it is just a matter of time before the data levels are where they were at again.
This is the first Nightly build this has happened on... I was planning on updating to 1211 right now let's see how that effects it.:laugh:
Ok so I did a clean everything and Flashed the most recent nightly and well Power Amp was Rocking I was waiting to see if something happened like last time and nothing... so then I went to multi tasking and still nothing so I am not sure what the problem was... let's give it 2 of 3 days on this nightly and see what happens.Cheers all. If any of this is helpful hit thanks
Good. I'm not a fan of dirty flashes myself. I also check the BBQ for nightly changelog and install accordingly. I'm still rocking 11-30. Issues = none
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
tmar89 said:
I recently got the Blaze4G and it is stock, but in the past I had the Samsung Fascinate and I would flash CM and AOKP onto it and the camera flash and torch apps didn't work with the camera LED. I read on the CM 10 development thread that there is also an issue with the camera flash. Are there any non-stock roms that do not have issues with the flash/torch working well?
Click to expand...
Click to collapse
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
anactoraaron said:
You could just install an app from the play store that would give you that functionality. Power toggles is one that comes to mind that works on stock that has a working torch toggle.
Click to expand...
Click to collapse
No, I mean with the aftermarket ROMs, do any others besides CM 10 have issues with the flash or toggle? I have no problems with the stock Blaze 4G torch
I'm on the latest CM10 Nightly and the included Torch works fine.
LBN1 said:
I'm on the latest CM10 Nightly and the included Torch works fine.
Click to expand...
Click to collapse
Thanks, I'm going to try the stable CM10
tmar89 said:
Thanks, I'm going to try the stable CM10
Click to expand...
Click to collapse
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
dammit.. and I just flashed and loaded my apps and settings..
anactoraaron said:
No. Don't use the 'stable' build. It's not that stable. Use the latest nightly 3/18.
Click to expand...
Click to collapse
Why do you say that the stable build isn't that stable? I've been running it and it works fine for me. It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
keiichidono said:
It's randomly rebooted on me a total of 2 or 3 times though, and I feel like the battery should last longer so I'm keen to hear what you have to say.
Click to expand...
Click to collapse
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
anactoraaron said:
That's why I say it's unstable. Random reboots are no longer present and battery life is improved among other things.
Random reboots = unstable lol
I don't fully recall but I believe the SoD was present on the 'stable build' too.
Click to expand...
Click to collapse
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
keiichidono said:
2 random reboots in a few months isn't so bad in my opinion. It's not completely rock solid stable but at least I've never gotten a screen of death. I'm thinking of trying out the nightly but while better battery life does sound very enticing, the screen of death seems like a show stopping problem. It seems safer to just flash the lightning zap kernel to see if it'll improve my battery life. When you say you get the screen of death in the nightly, how often do you get it? How often do others say they get it?
Click to expand...
Click to collapse
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
anactoraaron said:
I don't get the SoD in the nightly. Didn't say I did. But I think the issue surrounding the SoD is present in the 'stable' build.
I believe the SoD had something to do with the BLN but I'm not 100% on that. I know a lot went into getting rid of the SoD and I don't think those efforts started until after the 'stable' build. I also had issues (what seems like) back in the day where when I would receive a call the phone would freeze and hot boot (reboot to cyanogenmod bootanimation). I also recall having major battery drain compared to previous nightlies with the stable build and posted my results somewhere - maybe in the CM10 thread. Something like an additional 20-40% faster drain even in standby compared to the nightly just before the stable release - using the same kernel too. Something in the stable release seemed to be the cause, and the very next nightly the issue was addressed (which I think I pointed out in the CM thread also).
I also believe that the 'default' kernel with CM10 has added the interactive governor since the stable build. I don't remember having that before either.
You can flash the LZ kernel (it's awesome) but I think there is or may be an issue with the davlik. I do believe Thomas is already on this - read the LZ thread for more info. I was getting reboots quite often using it with both PA and CM10 - sometimes immediately after boot. That doesn't mean you won't run it just fine 100%, just something to be aware of. Make sure you nandroid before flashing in case you run into any instability.
Click to expand...
Click to collapse
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
keiichidono said:
Ah, the way you worded it I thought you got the SoD. I definitely notice the battery draining quite fast, even on standby just as you said. Sometimes I fully charge it before I go to sleep and unplug it; I wake up and the battery is at 90% (Estimate off the top of my head). Other times I fully charge it to 100% and unplug it, only to have it immediately drop down to 99% and within minutes go down even lower. I'm using the default kernel in the CM10 stable build and I have the Interactive governor (It's default), and my scheduler is CFQ (Also default).
You've certainly convinced me to try out the nightly, I'll have to flash it soon. I'd also like to try out the LZ kernel as it does seem really cool. In what areas did you see an improvement and was it a big difference?
Click to expand...
Click to collapse
Racings unofficial AOKP + lightning zap = WIN
Snappy snappy, stable(no reboots period), best battery life for any jelly bean ROM I've tried, and the built-in toggle torch works perfectly.
just my 2 cents
Sent from my AOKP Blaze
I've only been noticing this since 2 weeks, and I've found other threads on oneplus forums/reddit that have the same problem, but appearantly nobody knows a fix. When I have bluetooth enabled on my OPO the WIFI speeds on 2.4ghz go down to 100-200 kB/s max. 5Ghz seems to be unaffected, but I don't have that everywhere. I was using CM12.1 official when I first noticed it happening. When I turn off my bluetooth the wifi speed goes back to what it's supposed to be, but I have a Pebble so permanently disabling bluetooth isn't really an option for me... I've installed Sultanxda's [ROM+KERNEL][5.1.1] Unofficial CyanogenMod 12.1 with CAF 3.4.0 kernel [Oct. 11, 2015] today but the problem persisted. I then tried the newest AK CAF kernel but again to no avail. What else could I try? Or has anyone found a fix by now?
Thanks for your time!