[Captainbob767]

Have had Kitkit for about 20 hours and I noticed this afternoon, that Wifi is not turning on automatically when I get home. I went to settings menu, and it shows that it is off and the switch to turn it on is grayed out. I have to reboot the phone to get Wifi on. Has anyone else seen this. By the way, I use Juice defender Ultimate, and even tried to get it to force wifi on, and nothing happens. Disabling juice Defender Ultimate, and Wifi turns on.

[B. Diddy]

Might be an incompatibility issue with KitKat. I've had a number of minor glitches with apps that aren't completely compatible. Have you contacted Juice Defender support? Feedback and support

[Captainbob767]

Might be an incompatibility issue with KitKat. I've had a number of minor glitches with apps that aren't completely compatible. Have you contacted Juice Defender support? Feedback and support

I went through all the settings in Juice Defender Ultimate, and found a few that had changed when the app was updated for Kitkat. Now everything is working normally.....

[Mark Gibbons1]

Hi
I am seeing exactly the same behaviour i.e. with JD enabled I end up with the wi-fi disabled and I'm them unable to reenable it without rebooting the phone.

Regards
Mark

I went through all the settings in Juice Defender Ultimate, and found a few that had changed when the app was updated for Kitkat. Now everything is working normally.....

[chau084]

Hi, I have the same problem. After downloading kitkat, wifi is turned off when the screen is off. And the only way to get it on again is to reboot. As mentioned above, Juice Defender seems to be the cause. I turn on "force reconnect" under wifi in juice defender. I'm not sure if this is the right way to go about this, or if there's more to do. So far, seems like it works

[marks7389]

Yes, exactly the same here both with KRT16O and KRT16S on my 2012 wifi Nexus 7.

I stopped it re-enabling wifi periodically as a work-around. Definitely a fault with Kitkat 4.4 on this hardware; it's not happening on my Nexus 5, nor was it an issue with Jellybean 4.3.

I'm in the process of raising a bug report with Google as I can't see anything relevant currently.

Edit: I've raised a bug report at https://code.google.com/p/android/is...etail?id=62818. You can star the issue to get email updates on it.

[marks7389]

I've also reported the issue to Juice Defender Support.

[Citizen Coyote]

Yes, exactly the same here both with KRT16O and 1RT16S on my 2012 wifi Nexus 7.

I stopped it re-enabling wifi periodically as a work-around. Definitely a fault with Kitkat 4.4 on this hardware; it's not happening on my Nexus 5, nor was it an issue with Jellybean 4.3.

I'm in the process of raising a bug report with Google as I can't see anything relevant currently.

Edit: I've raised a bug report at https://code.google.com/p/android/is...etail?id=62818. You can star the issue to get email updates on it.

Out of curiosity, why do you think Google can fix this issue? It sounds unique to Juice Defender, seems like the app dev would be the most likely source for a fix.

[Gareth Bowen1]

I too have noticed this on my 2012 nexus 7 since updating to Kit Kat

[marks7389]

Out of curiosity, why do you think Google can fix this issue? It sounds unique to Juice Defender, seems like the app dev would be the most likely source for a fix.

For one thing it affects only the Nexus 7 running Kitkat. If it were a problem with JD, or an incompatability with KitKat I would expect to affect other devices such as my Nexus 5 which it doesn't.

Furthermore on the assumption that JD uses a published API to control the WiFi that should clearly never cause it to enter a state where a reboot is required to restore connectivity.

I don't think we can necessarily assume it is unique to JD. If the problem is a bug that relates to enabling WiFi in the background on this device and Android version it wouldn't show for most people unless using JD or something similar.

That said I have raised it with JD support as well.

[Citizen Coyote]

Fair enough. Good to cover all the bases.

[bmixalos]

Also happens with my nexus 10.

[marks7389]

So in summary seems to affect the Nexus 4, 7 (2012 model at least) and 10 but not the Nexus 5 which is working fine for me...

I'm not sure what the JD Wifi Force Reconnect option is supposed to do, but on my Nexus 7 it seems to stop the wifi from being periodically re-enabled. That resolves it (in the same way as disabling the wifi schedule resolves it) at the expense of not getting any incoming emails or similar until you turn the screen on.

Are others seeing similar?

Edit: It's just hung on me with Force Reconnect enabled, so it seems I spoke too soon... Back to disabling the WiFi schedule again.

[oerelithe]

Same problem here with N4. Maybe reporting here at JD community/support(and voting) can speed up the fixin'.

[ziggy29]

Same problem here with N4. Maybe reporting here at JD community/support(and voting) can speed up the fixin'.

Misery loves company... same problem here, N4 on KitKat. I'm not sure the devs are even supporting this any more -- the most recent released "production" version (3.9.4) was released almost two years ago, and each new 4.x version of the Android OS seems to break it a little bit more.

[billdz]

Anyone not using JD having this problem? I am. Have never used Juice Defender. What other app could be causing my problem?
Thanks,
b

[John Verpeleti]

Glad I found this thread and keen to see outcome. Same problem with 2012 Nexus 7 and I have Juice Defender. Interesting to see later posts suggesting problem may not be unique to the N7(2012)- JD combination.

[oerelithe]

Misery loves company... same problem here, N4 on KitKat. I'm not sure the devs are even supporting this any more -- the most recent released "production" version (3.9.4) was released almost two years ago, and each new 4.x version of the Android OS seems to break it a little bit more.

Yeah, just noticed. Bummer. I bought JD just a month ago. Should've checked b4 purchasing.

[marks7389]

Anyone not using JD having this problem? I am. Have never used Juice Defender. What other app could be causing my problem?
Thanks,
b

Under what circumstances is the issue occurring for you and on what hardware/Android version?

[billdz]

It appears my problem has been resolved by deleting an app. Maybe Easy Battery Saver, not sure, I just started deleting apps and did not notice exactly when the wifi came back on. The issue was occurring under the same circumstances as those described by people using JD -- wifi disabled and not possible to enable except by rebooting on my N4 since upgrading to 4.4. All has been fine now for almost 24 hours.

[serret2000]

Anyone not using JD having this problem? I am. Have never used Juice Defender. What other app could be causing my problem?
Thanks,
b

Yeah, over here! N4 and never had JD installed. Wifi disabled (and greyed out), and not even able to enable after reboot.

I have AVG AntiVirus installed, Llama (now disabled, but makes no change) and Wifi Analyzer (for what I guess might influence wifi...)

Never had troubles with 4.3!

[Word of Reason]

I have 2013 Nexus 7 with Easy Battery Saver by 2Easy Team (Not Juice Defender) and my Wi Fi is turning itself off and graying out requiring a reboot as well, just after loading Kit Kat. I do not think it is Juice Defender. I think Google...googled it again and pushed Kit Kat out with compatibility issues. Don't they do beta testing?? Shame on Google. Any fixes or patches to fix this new problem?

[billdz]

@serret2000, @Word of Reason - It looks like Easy Battery Saver was causing the wifi problem in my case. I read that 2x Battery Saver was also causing wifi problems for some. Try uninstalling any battery saver app you have installed. If that does not restore wifi, start uninstalling other apps that have any relation to wifi. In my case, the wifi came on by itself the moment the suspect app was uninstalled.

[Captainbob767]

I have 2013 Nexus 7 with Easy Battery Saver by 2Easy Team (Not Juice Defender) and my Wi Fi is turning itself off and graying out requiring a reboot as well, just after loading Kit Kat. I do not think it is Juice Defender. I think Google...googled it again and pushed Kit Kat out with compatibility issues. Don't they do beta testing?? Shame on Google. Any fixes or patches to fix this new problem?

If you think about it, there are over 800,000 apps for Android. It would take them forever to test a updated OS with each app. It is up to the app maker to come out with an update to fix any compatibility issues which sometimes takes awhile.

[serret2000]

@billdz
thanks, but I have got not battery saver apps!
Even worse: I just did a factory reset and STILL NO WIFI AVAILABLE (no apps installed, just plain Android 4.4 (build number KRT16S) on my 5 months old Nexus 4.
This is getting annoying. Anyone any ideas?

Thanks!