After updating to the latest Franco Kernel (r150) earlier today, I found that my wifi no longer works:
i.imgur.com / 6LmniGC.png <-- sorry, low post count.
The wifi switch has been disabled, and I cannot turn wifi on.
I tried reverting to an older revision of the kernel, going back to r134 which I was previously using with no problems, and found that I still could not turn on wifi.
Does anyone have any brilliant ideas?
Thanks in advance.
You can try fixing permissions and wiping the dalvik/cache from recovery mode. That probably wont fix it though, it seems like your wifi config is screwed up. Franco does not mess with the wifi in his kernel so it was probably caused by something else.
Holcomb227 said:
You can try fixing permissions and wiping the dalvik/cache from recovery mode. That probably wont fix it though, it seems like your wifi config is screwed up. Franco does not mess with the wifi in his kernel so it was probably caused by something else.
Click to expand...
Click to collapse
Thanks for the suggestion, but unfortunately neither wiping dalvic/cache nor fixing permissions resolved the issue. Wifi is still unavailable.
I don't know for sure that it was the kernel update that caused the issue, but wifi was working before the update, and then wasn't available after I updated, and I didn't do anything else in between.
I don't suppose you know how to 'unscrew' a wifi config?
I had that problem awhile ago, sadly the only way I could fix it was to restore a Nandroid. If you don't have one and can't wait, I suggest you wipe the phone and reflash everything.
Perhaps someone else here has a fix though
Sib3lius said:
Thanks for the suggestion, but unfortunately neither wiping dalvic/cache nor fixing permissions resolved the issue. Wifi is still unavailable.
I don't know for sure that it was the kernel update that caused the issue, but wifi was working before the update, and then wasn't available after I updated, and I didn't do anything else in between.
I don't suppose you know how to 'unscrew' a wifi config?
Click to expand...
Click to collapse
I pulled the wifi config files from AOKP and packaged them as a zip. Install in recovery. Hope it works.
mega. co.nz/#!E1YRRa5R!JeH_UVS-SaaPGGdj5R7bHnxU4DtGm3iq5yiaypnNEVE
remove the space after "mega." I cant post links yet.
Related
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
typci said:
Updated to official 2.3.5 rooted, added back the pink screen, not done much else except installed a few apps.
Getting random reboots while phone is sleeping. Never happens while actively using phone. My phone will be on my desk and next thing I know it restarts.
Anybody else have this problem or found a solution?
I need to find out if it is the rom or something else causing the problem so I can start to troubleshoot it.
Click to expand...
Click to collapse
Turn OFF wifi when you're not using the phone. problem solved
If not work try this :
Goto CPU menu -> smartass v2 and make low and high cpu speed settings to 1 ghz.
This will also increase Battery life and must fix random rebooting.
Other way is clear caches and install rom again.
Loureiro:
I'll try turning off the wifi. It sounds like a highly likely solution since: 1) I've only seen my phone at home 2) I always turn wifi on at home.
Is there a specific reason why wifi is causing reboots? Maybe something I can find a fix for?
technogod:
Don't have custom kernal installed, so I can't alter the CPU parameters. Wanted to make sure the phone was stable at stock before changing the kernal.
Speaking of which, what's the most stable kernal for overclocking the 2.3 stock rom?
I'll try clearing the caches as well.
Thanks.
The wifi bug is known fault with the .35 kernel found in the official upgrade. hopefully it will be fixed next week fingers and toes crossed. I am not sure if any of the kernel dev's have found a fix yet.
Without cpu parameters, only way i am found that : clear three caches with clockwork and reinstall your rom. It's working on stock roms or custom roms. I think, this is not rom problem. There is different something. Cache clearing solves problem. Resetting problem started on my phone when i start to try other roms.
I am using miui 2.2.3 now and i will setup 2.2.10 version today. While using stock rom, i have some resetting problem. But now, my phone working without self-reset.
Hi, maybe someone has a clue:
I seem to be the only one who can't use cm10 because wifi is just not working. On cm10 it's dropping out all the time as soon as data gets transfrerred (i.e. app download) and on cm10.1 its not even dropping. there is no data throughput whatsoever.
If you need more info, just tell me which one and I'll post it. I'm desperate.
Any ideas?
Assuming you have made a clean install, with system and data wiped as well, you should check your router configuration, try changing channel and/or security parameters
Sent from my MB526 using Tapatalk 2
thanks for the suggestion. I don't have access to all the routers settings but I tried to use one even without security and the drop outs still appeared. Working well on m7.
I just realise: At the beginning of a fresh build it sometimes happens that wifi works for a couple of MB and suddenly starts dropping.
Is the Wi-Fi network used by many persons at a time? More than a couple of devices connected may cause problems because the new Wi-Fi drivers starts jamming devices, and sometimes as a result the Wi-Fi network is unable to deliver data.
Sent from my MB526 using Tapatalk 2
I wouldn't say so. Not to many and it didn't work with the old wifi driver on cm10 either. The wifi keeps working for other parties in the network - so it is not jammed.
I might try again with a new build but I'm pretty hopeless...
Here is a long post about what I tried so far:
http://forum.xda-developers.com/showpost.php?p=38869441&postcount=915
measel said:
Hi I'm sorry to bother again.
I tried to figure out whats wrong with the wifi bug I'm having: constant drop outs while using any kind of wifi traffic.
Good news:
it worked well at home with my fritzbox router. (only tried 3-4 app downloads) > after a short while it stopped working
Bad news:
in my studio we got a different router and there I got the drop outs.
What I tried so far without luck (always a reboot in between):
disable Draft-N in wpa_supplicant
compared wpa_supplicant but it's the same as in cm7
delete rgnt from system/bin
change build.prop to use all 14 channels > ro.wifi.channels=14
tried changing PowerSavePowerLevel = 0 to 1
copied tiwlan.ini from cm7 backup because a few settings are different
tried 12-12-05 Quarx build
tried 12-10-18 build (but got a bootloop and stopped trying)
tried newest 13-03-07 build
ADDED tried 13-04-09 build
tried newest build and did another factory reset AFTER installing the ROM.
searched the web and found that maybe it might have something to do with wpa2, but the router at home uses wpa2/wpa (which means it's wpa2 as well or not?) and NO I cannot change the routers settings and I don't think it is a solution because i can use but not access like a dozen routers.
checked dmesg: in the TIWLAN section after the wifi connection it says: "iface_stat: stat_update() tiwlan0 not found
is it in any way possible that some settings change because I plugged usb "charge only" in while trying to download from Playstore? because it seems that dmesg spits somthing out regarding usb... (I'm can't really read/understand the output though)
oh and btw. first connection was fine in my last try: I could update Gmail, then I connected my usb and drop outs began. but I don't think it's related.
ADDED change to static IP
ADDED change regional code in wifi settings (w/o knowing what that actually does)
ADDED tried factory reset from stock, flash sbf and start from scratch.
Things I didn't try (and don't know if it would make any sense):
replace tiwlan_drv.ko
change vsel
[...]
Click to expand...
Click to collapse
It may be something elementary, but I presume Wi-Fi optimization is configured properly right?(IT MUST BE DISABLED)
I have had this issue but setting channel manually fixed it for me. This issue I had only on jb and with a specific router only. All others work properly on every channel.
Sent from my MB526 using Tapatalk 2
Damn I can't just change all the channels in all the wifi networks I'm allowed to use... but I will try that with my own one.
I did not try to change channels, yet but I tried once more to start from scratch: wipe from stock / flash sbf / install cm10 and so on..
Reason: Someone hinted the stock wipe could help. But here is the problem:
Everytime I try to wipe from stock (before or after flashing sbf) I get the old "E:can't mount cache:recovery/..." ERROR. Something seems to be wrong and I wonder if that could prevent my wifi from working (maybe data is still unwiped...)
Any more ideas?
Stock recovery can't handle ext4, hence the read errors.
Stock recovery wipe will not help if custom recovery data wipe does not help. You can also try manually deleting the Wi-Fi folder in the data partition.
You'll have to try changing channels eventually, I think.
Sent from my MB526 using Tapatalk 2
thats a misunderstanding:
I know that stock recovery can't handle ext4. My working system is cm7 so I stockwiped from cm7 and still couldn't get rid of the errors. I even checked the filesystem with e2fsck but everything seems to be ok. And I can install everything so... I don't know.
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
And what misunderstanding are you talking about?
Sent from my MB526 using Tapatalk 2
thekguy said:
If your current rom is cm7 then you shouldn't get the error messages in stock recovery. I assume you've flashed a sbf and still gotten this error. You can try enabling the blank flash option from rsdlite.
Click to expand...
Click to collapse
That does sound pretty scary.
You can verify whether data is wiped or not by wiping in custom recovery, and then cross checking with aroma file manager(flashable) to ensure data is wiped. If not then you have some kind of hardware eMMC problem which somehow triggers the Wi-Fi problem probably because of leftover Wi-Fi files and modules.
Click to expand...
Click to collapse
I can't waste another day on hunting the /cache problem right now because of work, but as soon as I have more time I'll try a little more.
Here is some news from me: I had the chance to try it on another wifi router last night and behold: It worked nearly flawless.. a few hickups I think, but it worked. That means WIFI is not broken, but there must be some software-related problem/ or some network weirdness.
Also, couple of people have had luck flashing a newer sbf like dfp 231(with higher bl version), which seems to work in some cases for similar problems. Beware of the no downgrade issue in these recent sbfs.
Click to expand...
Click to collapse
This I will not do!
thekguy said:
And what misunderstanding are you talking about?
Click to expand...
Click to collapse
Just that stock over ext4 thing. Nevermind.
Thank you for helping. I wonder if there is a way to find the problem.
Did you check the channel that particular Wi-Fi router operated at? Same as or different than the problematic routers ? Because if so then we have narrowed the problem down
Sorry for the scary part
Sent from my MB526 using Tapatalk 2
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Joharnis said:
Hi Guys,
I have a problem with my nexus 4. I wanted to use cyanogenmod instead of the stock rom, so i rooted my device yesterday and flashed the latest stable build of cm (10.1.2).
Everything worked fine, except for the wifi; it won´t turn on. It get´s stuck on the "turning on wifi"-page, wtih the button in off-position and saying "turning on wifi".
I´ve read some threads were people had the same problem, but nothing seems to fix it. I made a factory reset, wiped cache and dalvik, fixed permissions, but in didn´t work on cm 10.1.2.
So i tried a different build, cm 10.1.1 stable, but the problem persisted. I tried the same things I did on the 10.1.2, but it did not help. So I tried using the latest nightly, but that didn´t help either.
I thought i go back to the stock build to fix it, because it still worked after I rooted the device and still had the stock on it, but unfortunately that did not fix it. I made a factory reset, and wiped cache and dalvik again, but it just won´t work.
Long story short, i don´t know what to do now I rooted and flashed several devices before and never had a problem that did persist even nafter i tried multiple buidls of cm and wiping everything everytime; so if anybody has any idea where this problem comes from and how i could fix it that would be really great
Click to expand...
Click to collapse
Im having a similar problem, i think we have to flash a different radio ?
Still nothing
Flash a different radio? What excactly does that mean? I must admit I have not heard of that :laugh:
By the way, I just unrooted my device and relocked the bootloader, but that didn´t fix the problem either.
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
sigma392 said:
Stock CM Kernel? If so, try flashing kernels with prima drivers. If the problem persists, I guess it may be hardware. On another note, do you have bluetooth or GPS on? Try turning those off and try connecting.
Click to expand...
Click to collapse
I just tried the franco R163 with prima drivers, that did not fix it. But, speaking of the bluetooth, i´ve just noticed that the same problems occurrs with that. I trie to turn it on an it stays at "turning on bluetooth" without actually turning on. Maybe that helps to know what the problem is.
What other kernel with prima drivers would you recommend?
Edit:
I´ve read through a few threads on that bluetooth-issue, which apparently is more common than my wifi issue. I was wondering if my wifi-issue could have something to do with the bluetooth, because other users who have said bluetooth issue found their bluetooth temporarily on after reboot; then after a while the bluethooth issue appeared again.
In my case the bluetooth doesn´t appear to be on, but i was thinking that maybe it is, but the software fails to display that and that that is interfering with my wifi.
Could that be a possibility?
Out of the box my nexus 4 refused to connect to my TPLINK wr941ND router, wifi was set months ago, nexus 7 works as charm same with evo 3d and others. I thought wtf and turned on wifi on broadband modem, it showed up on nexus 4.... And suddenly network from router poped up as well. I switched off wifi on modem and nexus lost wifi from router. At this moment I went for a walk... When I come back done factory reset, reboot the router, no effect. Changed settings from WPA2/QSS to WPA without QSS - no change, then I changed channel from #13 (best in my location, all my neighbours using #1 and #6) to #1 and instantly nexus found network.... So it seems that sumthing is apparently with wifi, when I changed channel back to #13 it drops the connection and says that networtk is out of range. So finally I checked all the channels from 1st to 13th and it works from #1 to #10, 11 till 13 dunt work. Maybe this info will help sumone with simillar problems.
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
Basically yesterday I had the same problem, flash after flash didn't help. Can tell you exactly, what I did:
Found factory version of my firmware in my region (SEB Baltics for me, MGA). Then I reinstalled TWRP recovery through ODIN, wiped everything I could, after that flashed stock firmware 2 times consecutively (no reboot in odin, reboot manually after first flash and flash again).
After that everything went fine, and Wi-Fi started working again. MH1 custom ROM right now, going ok.
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
No. WiFi drivers are in the kernel, not the modem. If you were going to flash anything, you'd flash a kernel/rom.
nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
I suggest you use titanium backup to bakup your apps, it's not a tough job as you thought. that might be the easiest way, although some data can't be backup.
nwsk said:
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
Click to expand...
Click to collapse
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Gh0stR1pp3r said:
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Click to expand...
Click to collapse
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
bofff said:
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
Click to expand...
Click to collapse
Welp, bluetooth had no problems whatsoever. It was only the wifi, which didn't want to turn on. Now everything is ok.
Well, finally got around to reflashing stock as Gh0stR1pp3r suggested, which worked. Thanks
Nandroid, kernel flashing, and modem flashing all didn't work. No clue why. I flashed the ausdim kernel again and it worked this time around, so it's just weird I guess? :S
And unfortunately I seem to have messed up the titanium backup somehow, I can't seem to find any of the stuff I thought I backed up Oh well
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
whoiswes said:
I had the same problem after dirty flashing from 13.1. I did a factory reset and reflashed and all was well.
Click to expand...
Click to collapse
thanks for the reply. i did a clean flash. didnt work.
i flashed the boostack, rebooted back to recovery, flashed the rom and gapps, wiped cache and rebooted. it boots fine. but then i still dont have auto rotate. seems like the drivers werent installed or something
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
MiMtnBiker said:
Obvious questions, but did you check the rotation settings inside the display menu? Also, is Adaptive brightness toggled on?
Click to expand...
Click to collapse
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
crazynitro said:
i did. i installed an app that checks the phones sensors. they are all undetected. i think its a driver issue. i'm at my wits end
Click to expand...
Click to collapse
Check the md5 on your download to make sure it is not bad Install twrp 3.0.4.0 you could also move everything you want to keep to a sdcard so you can do a total wipe. Now install rom and gapps only and check to see how everything works before adding root or apps.
crazynitro said:
Just as the title says, after flashing the bootstack, rom and gapps countless times, i still dont have auto rotate or auto brighness. all the sensors seem to be dead except for wifi, gps and mobile network. did anyone else experience this? how did you resolve it??? please help!!
Click to expand...
Click to collapse
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
lkiefer said:
This is an old thread, but I am hoping you found a fix for these issues. I am having the same issue. If you have a solution to share I would greatly appreciate it.
Click to expand...
Click to collapse
I lost my phone so i currently have another one. i can t remember what i did to fix it though
crazynitro said:
I lost my phone so i currently have another one. i can t remember what i did to fix it though
Click to expand...
Click to collapse
That's a drag. Thanks for the quick response though.
Hello, I also have an issue with the accelerometer (and by consequence the auto rotate function).
I am on full stock Nougat B09 (no root) and the issue was also present on B06.
Rebooting the device solve the issue, and factory reset does not make this bug disappear.
That being said, I think I located the root cause.
The magnetometer seems to be never working, even after a reboot. When an app wants to use the magnetometer (like Google map, or the compass), it make the accelerometer crash....
Anyone else having this issue ?
Does you magnetometer works flawlessly ?
Thanks.
@arachneon,
Hi, you can change it in the tools---compass, and in that compass you can waggle the phone in the way of "8", if all that cannot fixed you can also seek help in the nearby ZTE after sales service repair center. Thanks!