i have my brand new N4 and its only rooted with stock recovery (used tool kit to temp boot into TWRP) and all I flashed was the Motley Experimental kernel and thats it nothing else has changed.
when ever i am connected to WIFI and i leave the WIFI area, my HSPA keeps disconnecting and reconnecting over and over and i have to toggle AIRPLANE mode to get it to stop.
wasnt sure if this was a kernel issue or a known issue with N4's?
I had this same issue before I flashed a new kernel, just try flashing a different kernel.
Sent from my Nexus 4 using xda app-developers app
i have the same issue on the stock kernel!! and i notice it drains your battery fast while it does this!
Related
After i flashed HCDR.Kernel v4.1, the connection drop randomly when my wildfire try connect to Win7 Access Point(Connectify).
However, issue seems to be gone if i revert back to HCDR.Kernel V3.
I wonder if anyone facing same problem. Is there a way to fix this with V4.1 kernel?
Try v4.2. Although that has the issue of the clock speeds being set at 19 - 768 by default. But, if it boots for you, you can use SetCPU or something to change the clock speeds back to normal.
4.2 changed the Wi Fi Driver over 4.1, so, it should fix the issue.
If it still doesn't, some member modified the kernel so that it is stable and with the new Wi Fi driver. That thread should be there somewhere in the Wildfire Android Development Forum.
unfortunately, kernel v4.2 won't work on DK custom for wifi. kernel v3 is unstable even it booted, wildfire reboot occasionally even if cpu set at 518max.
I found the mod kernel with fixing wifi sleep (http://forum.xda-developers.com/showthread.php?t=967746). Yet no luck. Reverting back to original kernel atm.
seems like it is the compatible problem with my connectify host on wifi N mode.
It works fine after it flashed the homemade kernel from HCDR source with N mode disable.
Another issue is the connection drop, should be due wifi sleep issue. It goes away after i use wifi fixer.
This problem has plagued me both on stock EI22 and on the CleanGB rom.
Several times a minute, while using wifi for any activity (internet, im, market) the wifi will drop for a few seconds and then reconnect.
I have also had both 3g and wifi simultaneously on (at least both icons are showing in the notification bar) until I turn one of them off.
This is very frustrating and I don't know what to do. I have tried assigning a static IP and no improvements thus far. Wifi sleep policy is set to never. I have tried the EI22, EH17, and EC05 modems and the problem persists. The problem only appeared when I upgraded to EI22 (odin to EC05 and applied update). Wifi worked perfectly under EC05. I have other devices that are connected to wifi and they work perfectly.
I would appreciate any help or advice.
Try the kernel from IAP in my signature.
You can also boot into recovery and wipe data, partition cache and dalvik and then setup your apps again. I know that has helped other with the same issue.
Its a pain, but often if you restore data it causes strange issues.
I had that problem and flashed a new kernel and it fixed it I think I'm using the samauri overclock kernel now , I'm not using the overclock or undervolt but its working great for me
Sent from my SPH-D700 using xda premium
jdelano said:
Try the kernel from IAP in my signature.
You can also boot into recovery and wipe data, partition cache and dalvik and then setup your apps again. I know that has helped other with the same issue.
Its a pain, but often if you restore data it causes strange issues.
Click to expand...
Click to collapse
I tried booting into recovery, wiping data, partition cache and davlik cache, and upon rebooting and connecting to wifi, the problem immediately persisted.
I tried odin to EC05, update to EI22, and immediately connecting to wifi and it still has the problem.
I don't understand. From a fresh EC05, there is no problem with wifi. Upon upgrading to EI22, it breaks.
I would really like to stay as stock as possible without having a different kernel. But this problem makes doing anything over wifi very frustrating.
Edit: I have tried your kernel and yes it has solved the problem, but do you have any idea on why this solves it? What does it change that is different from the stock kernel that fixes the problem with wifi? Thanks.
I'm having this issue with nubekernal v2. Pretty annoying
Sent from my HP Touchpad using Tapatalk
I'm having the same problem. First under stock EI22 and now ACS ICS v5. It works fine though when I'm at work with a G router but constantly drops at home with an N router. Worked fine on stock Froyo. Sure would be nice to track this down.
Dave
The only thing I have found that thus far fixes the problem is by running the IAP Kernel. I'd prefer not to be running it and would rather stay stock, but I cannot live with the wifi disconnecting all the time.
On the plus side though, I really have not noticed any changes by running the IAP Kernel on top of CleanGB. That is, it has fixed the problem and everything still looks the same.
I think it isn't really the kernel's fault, but rather wifi flakes out when running your first ei22 kernel after flashing from ec05. It seems that flashing any kernel after upgrading to ei22 fixed it here. I can't explain it.
Sent from my SPH-D700 using XDA App
wtogami said:
I think it isn't really the kernel's fault, but rather wifi flakes out when running your first ei22 kernel after flashing from ec05. It seems that flashing any kernel after upgrading to ei22 fixed it here. I can't explain it.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
The problem returns if I flash the CleanGB Kernel back. Like you, I'm not saying there is anything wrong with the CleanGB Kernel, but it is a mostly stock kernel (from what I've read) and thus it behaves like the stock kernel in that I still experience the problem.
Hey there guys, I apologize if this has been covered, as I feel its related to an "efs" folder type of issue. I'm just not quite sure where the hell to even begin searching.
I've been on 4.3 since the leak and have been using Cataclysm 4.3 JWR ROM for a while now, problem free. All was running great until yesterday I was downloading some media and transferring it to my laptop (~10gb of traffic before I noticed the problem), and my WiFi shut off and restarted itself. My mobile data kicked in at that point for all of 10 seconds until the WiFi reconnected and within 30 minutes my signal bars suddenly dropped to zero and calls couldn't be made. "Mobile network not available." message appears. So I figured i'd pull the SIM, replace and reboot. When that didn't work I tried rebooting without the SIM, to see if it would detect no SIM card and prompt me to put one in and reboot to be able to connect to mobile network. Well nothing was detected. A full wipe, reflash of identical ROM, reflash of updated ROM, reflash of original JWR deodexed & rooted backup, all with the same outcome. I have tried everything short of downloading the stock image and flashing that but I haven't got around to it since I haven't had time to backup my internal SD before losing all data. I should note that I'm on baseband .84/4.3 bootloader and have been since Google pushed JWR & JSS. I haven't tried flashing a new modem, I figured that wouldn't been an issue. I suppose I'll try flashing .48 and update.
Edit: I forgot to mention that yes, WiFi is in fact working. Mobile signal seems to be the only thing affected.
Edit: Reflashing baseband .84 and .48 didn't work.
I really appreciate any ideas guys, I'd like to sort this out rather than having to flash stock and RMA it or something :/
All settled, it was an issue with the frequency band my provided operates on. Mod can lock/delete thread thanks.
Sent from my Nexus 4 using xda app-developers app
I wiped the system .. Installed the stock rooted rom then installed the kernel with wifi fix right away... Everything works perfect for about 24 hours exact and then the wifi breaks and stops working so I have to restore my phone and lose everything every 24 hours... Is there a better way to do this cuz it's kinda sucking
Restore your phone why? WiFi is a kernel controlled thing, odds are a complete restore is never necessary with connection issues. I know of nothing in a ROM that directly affects your WiFi connections. I would say worst case scenario reflash your kernel when it "breaks". Note importantly, I would get a fresh download of your kernel and baseband and re install.
Sent from my SPH-L720 using XDA Premium 4 mobile app
I wiped the system .. Installed the stock rooted rom then installed the kernel with wifi fix right away...
Click to expand...
Click to collapse
??What??
What recovery?
What 'stock rooted' ROM?
What Kernel?
What WiFi Fix?
and HOW on each of those?
Then why reflash whole ROM.
What baseband (radio/modem) are you on?
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
CoinCoin88 said:
Hi XDA,
As there ar eno recent thread about 'no deep sleep' (aka on CM13/13.1) I'm opening one here inh ope someone can help me troubleshoot what's wrong...
I've had my OPO for 1.5 yr now, and overall it's doing great. Except since CM13.0, I've been having troubles with deep sleep and therefore my battery time hardly make it through the day.
It all began after the April upgrade, when I decided to encrypt my phone. I did a clean full wipe and installed the zip from TWRP recovery, then proceeded to encrypt the phone... Turns out the boot.img patched by SuperSU is incompatible with the encryption process so I reverted the boot.img ti the original and encrypted my phone, then flashed SuperSU back. Since then, the phone would never enter deep sleep mode, except when data connexion and wifi are disabled.
I've since flashed the latest build (ZNH2KAS1KN) in hope that would solve the problem. The flash was the cleanest I ever took (wipe data, system, dalvik, cache ; reboot to recovery, flash full zip, boot to system and restore all app through the 'play store restore' function, reboot to bootloader, flash TWRP with AtAm fix for CM13 encryption support). Yet, my battery keeps drainign blazing fast and I have no deep sleep at all even with the phone sitting indle on a table for hours. See screenshots.
The only strange thing I see are those 'fd440000.qrypto' kernel wakelocks. Any ideas ? I'm assuming it has something to do with the phone being encrypted, but why would deep sleep be achievable when the phone has no data/wifi ?? It's really puzzling and I can't figure out what to do. I had exactly the same problem on the previous 13.0 release (including the qcrypto wakelock).
edit: the only slight deep sleep period is because my SIM card was not detected for a short period of time (probably bad contacts, I took it out, wiped it a bit and everything was back in order)
Any help appreciated, thanks!
Click to expand...
Click to collapse
looks like you are having weak or no signal. this is likely to cause this issue!
Bac0nator said:
Strange. I haven't had much battery drain issues on Sultan's build. Are you using the official cm13 builds or unofficial builds?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
hellcat50 said:
looks like you are having weak or no signal. this is likely to cause this issue!
Click to expand...
Click to collapse
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
CoinCoin88 said:
Only the official builds for CM13/13.1, and with the cleanest install as possible... Never tried Sultan's build, is that a kernel, a full rom...?
Definitely not the cause. This happens every day, everywhere, independently of signal strength (i.e. color of bar in graph). I've confirmed with a friend of mine who also encrypted his phone a while ago and he also never goes to deep sleep.
Click to expand...
Click to collapse
sultan's rom is cm13 with caf kernel. it is known to be very battery friendly.
Here is the link: http://forum.xda-developers.com/one...m-kernel-unofficial-cyanogenmod-13-0-t3242700
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Sultan's builds are optimized for battery on the one plus one. They tend to be better than official cm13 builds, most of the time.
Another option is downloading an app called nap time on the play store, which forces your phone to go into deep sleep the moment the screen shuts off.
CoinCoin88 said:
and here I was hoping not to have to full wipe/reflash/restore again.... I've also posted on CM jira in hope of a comment on whether there is a known bug on ecnrypted devices or not. If nothig comes from there I'll try sultan's rom...
Click to expand...
Click to collapse
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
I have the same issue on Sultan's Rom. First 20 days battery life was awesome and now all the time phone is awake. I am reflashing sulatn build again
Thanks for this info, this is going in the same direction I observed and somewhat reassuring. Are you talking about CM nightlies then ?
edit: that was inteded for @tiny4579
Sent from my A0001 using XDA Free mobile app
tiny4579 said:
Steve included some kernel commits recently that address the crypto wakelock. They should be fixed on current nightlies.
I know it fixes it as I had that fd000.crypto kernel wakelock until very recently and I'm encrypted.
Click to expand...
Click to collapse
By any chance, would you happen to have SuoerSU as root binary/manager? I recall it patches boot.img which prevented encryption from being run in the first place (to encrypt, I had to reflash the stock boot.img, encrypt, then reflash SuoerSU). I'm wondering if the altered boot.img couldn't be part of the problem.
Sent from my A0001 using XDA Free mobile app
Some heads up: there was indeed a wakelock issue that has been fixed by a commit on the 4th of June.
See associated bug on JIRA: https://jira.cyanogenmod.org/browse/BACON-4987 (and appreciate how it's easier to blame the user than to try to replicate a bug). Hopefully we'll have a 'future OTA' before the end of the year...
I still have this wakelocks issues right now...