Is anyone having problems turning on the wifi? Tethering isn't working, nor is normal WiFi operation. Settings page says "Error" when wifi is clicked.
Welcome to CyanogenMod
![]() |
Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
|
Guest Message by DevFuse
3 replies to this topic
#1
Posted 20 August 2011 - 03:38 AM
#2
Posted 09 September 2011 - 05:34 AM
I used to have this problem quite a bit. I thought it was a kernel issue, but then all kernels started doing it. It turns out that it was being caused by the cpu frequency profiles i had setup in "setcpu". Turned all of the profiles off and haven't seen that error again. Other bugs that were seemingly being caused by the cpu profiles were frequent loss of 3g, freezing upon receiving a call, freezing upon plugging in. The freezing on charging and call only happened if the screen was off when plugging it in, or getting the call. The profiles i had setup were "in call" "charging" "screen off" "battery < 35%" "temp > 44 C". The wifi was the first thing that happened, then probably a month later the other things started happening rapidly (in the order listed above). I disabled all cpu profiles and all issues disappeared immediately. That was oh idk sunday or monday and i haven't had a single one of these issues happen since.
#3
Posted 29 September 2011 - 03:16 AM
I don't have any problems with Wifi, but the CM7 stock tether app absolutely doesn't work for me. However Barnacle does. Not sure why, but that's my workaround, for what its worth.
#4
Posted 03 October 2011 - 03:06 PM
I just happened upon this thread once again, and i thought i would say that i still have not had this wifi problem since disabling cpu profiles in setcpu. I still have an occasional drop of 3g for a few minutes every few days, but i believe it is due to low cpu voltages.












