Database Users

wifi on cm10 and cm 10.1 not working at all

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

Sudden Signal Loss, not detecting SIM

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

Android L port - mobile data not working

I flashed my Nexus 4 at the beginning of the week and have been following the developers thread since then. Love it so far, great work devs. Problem I am having is (as the title states) my mobile data will not work what ever I do. Currently I am on Beta 3 Preview 5 with stock kernel and lastest TWRP. I have tried toggling the airplane mode and switching preferred network type to GSM/CDMA auto in *#*#4636#*#* and deleting the APNs and doing restore to defaults, but it still reverts to WCDMA preferred. MMS works (sending and receiving). My carrier is T-mobile, and the APN I have been selecting is the T-mobile US (epc.tmobile.com with no user, pass and server set, the rest of the settings I left on default). Any help on this would be much appreciated :laugh:

It's a preview version. It's kinda funky. I'd try reflashing. Took me awhile to get it so that I was Happy with it. Make sure it's a clean flash, wipe data, system, cache, and dalvik.
Sent from my Nexus 5 using XDA Free mobile app

I understand that, I actually fully wiped everything when I first flashed it and had to do it 3 times to get Beta 3 pre 3 to work and flashed Beta 3 pre 5 two times as well. New user so the system didn't allow me to edit my posts earlier. I will try to flash again and see if anything changes

have you checked your APN?

I have just re-flashed my phone again, tested and gone through the phone info thing, deleting and restoring the APNs again, and still is having the same problem

Here are my current settings and info. I am lost as to what else to check and change in the APN. This current setting is from T-mobile's kb article that I found dating 2013
To add, I only have 3G, but when I try to search anything in chrome it displays the T Mobile 4G page, picture is attached as well

5.9
try 5.9 stable and fast

Phone says dialing but never connects. Incoming calls don't ring either

Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.

SwimDrewid said:
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
Click to expand...
Click to collapse
I had something like this before on my Nexus 5. Clearing the cache from the 'phone' app did it for me. Worth trying

maarten08 said:
I had something like this before on my Nexus 5. Clearing the cache from the 'phone' app did it for me. Worth trying
Click to expand...
Click to collapse
Already tried that. Then clean flash. Then updated ROM with latest vendor and radio images. No luck

i have a similar issue when connect to my Huawei Watch. once i turn off bluetooth i can call correctly.

do you still have an IMEI under settings

Gytole said:
do you still have an IMEI under settings
Click to expand...
Click to collapse
Yeah. Att thinks it's hardware. Time to test my Google warranty

SwimDrewid said:
Yeah. Att thinks it's hardware. Time to test my Google warranty
Click to expand...
Click to collapse
What does your prl version say under your IMEI settings? I had this exact problem when I flashed the latest PN build. I tried everything to fix it. Flashing my EFS backup worked for a while but sometimes on a reboot I had the same issue again. Flashing EFS would fix it again but it was temporary. The permanent fix for me was a clean flash of Chroma ROM. Just curious but what carrier are you on? It seems like this issue has been affecting CDMA carriers like Verizon more than others.

murphyjasonc said:
What does your prl version say under your IMEI settings? I had this exact problem when I flashed the latest PN build. I tried everything to fix it. Flashing my EFS backup worked for a while but sometimes on a reboot I had the same issue again. Flashing EFS would fix it again but it was temporary. The permanent fix for me was a clean flash of Chroma ROM. Just curious but what carrier are you on? It seems like this issue has been affecting CDMA carriers like Verizon more than others.
Click to expand...
Click to collapse
On att
Emei sv: 61
Says not roaming but I have that set

SwimDrewid said:
On att
Emei sv: 61
Says not roaming but I have that set
Click to expand...
Click to collapse
When I had this problem the prl version in my screenshot said unknown as well as the MIN number. If you problem started after flashing an update I'll guarantee its software and not hardware. If you have an EFS backup I would try and flash that first if not I would do a backup in TWRP and then clean flash Chroma. If it doesn't work you can always just flash your backup and be back to where you are now.

murphyjasonc said:
When I had this problem the prl version in my screenshot said unknown as well as the MIN number. If you problem started after flashing an update I'll guarantee its software and not hardware. If you have an EFS backup I would try and flash that first if not I would do a backup in TWRP and then clean flash Chroma. If it doesn't work you can always just flash your backup and be back to where you are now.
Click to expand...
Click to collapse
Ah. I don't have that info. Didn't do update till after this problem. May not have efs backed up. But did full clean install of latest du weekly including radio and vendor this morning.
Will check if I have efs backed up

SwimDrewid said:
On att
Emei sv: 61
Says not roaming but I have that set
Click to expand...
Click to collapse
I'm sure you have already checked the APN settings but it would be a good idea to make sure they were not changed when you updated. Are you in a good LTE area? A lot of people with this issue could make and receive calls over LTE but when they didn't have it they couldn't even though they had service. That's why I think it affected CDMA carriers more. LTE goes over GSM and 3g goes over CDMA. Does your phone number show up under SIm info?

murphyjasonc said:
I'm sure you have already checked the APN settings but it would be a good idea to make sure they were not changed when you updated. Are you in a good LTE area? A lot of people with this issue could make and receive calls over LTE but when they didn't have it they couldn't even though they had service. That's why I think it affected CDMA carriers more. LTE goes over GSM and 3g goes over CDMA. Does your phone number show up under SIm info?
Click to expand...
Click to collapse
Checked APN. I have efs from November MDBO8M from when I first got phone

SwimDrewid said:
Checked APN. I have efs from November MDBO8M from when I first got phone
Click to expand...
Click to collapse
The EFS doesn't change. The original backup you have is all you need as long as you have a backup of just the EFS partition and nothing else with it. It might not fix your issue but it won't hurt anything. I tried Chroma after reading it fixed a lot of others problems with the same issue and that worked for me also. I'm still running it but others have said they were able to go back to their preferred ROM after flashing it and all was good.

SwimDrewid said:
Phone seemed to stop working yesterday. Last time I used it was via Bluetooth paired with my wife's car.
I get signal and can text, just not send/receive calls.
I was on dirty unicorns official and had not messed with anything in several weeks.
I just updated radio and vendor and installed latest weekly of dirty unicorns.
Anybody go through this before? Any advice?
Thanks.
Click to expand...
Click to collapse
Could it be a sim card issue? Have you tried remove and re-inserting the sim?

ckarrow2 said:
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
Click to expand...
Click to collapse
Yep. Removed / reinserted before coming here

murphyjasonc said:
The EFS doesn't change. The original backup you have is all you need as long as you have a backup of just the EFS partition and nothing else with it. It might not fix your issue but it won't hurt anything. I tried Chroma after reading it fixed a lot of others problems with the same issue and that worked for me also. I'm still running it but others have said they were able to go back to their preferred ROM after flashing it and all was good.
Click to expand...
Click to collapse
I'll transfer to my phone and try in a bit. Any known problems going from DU to chroma? I'll try that too

ckarrow2 said:
Could it be a sim card issue? Have you tried remove and re-inserting the sim?
Click to expand...
Click to collapse
SwimDrewid said:
I'll transfer to my phone and try in a bit. Any known problems going from DU to chroma? I'll try that too
Click to expand...
Click to collapse
As long as you clean flash their shouldn't be any issues. Just go to advance wipe and select system, data, cache and dalvic. Just make sure you don't check internal storage. Then flash chroma and the recommended gapps and you should be good to go. Make a backup first and you can always just flash back to the point where you are now if it doesn't work.

murphyjasonc said:
As long as you clean flash their shouldn't be any issues. Just go to advance wipe and select system, data, cache and dalvic. Just make sure you don't check internal storage. Then flash chroma and the recommended gapps and you should be good to go. Make a backup first and you can always just flash back to the point where you are now if it doesn't work.
Click to expand...
Click to collapse
I don't have an EFS backup on my google drive (like I thought I did). I think I have the backup in the office, but not available now.
No joy on the Chroma -- still no PRL data, no phone sound on dialing, no receiving calls
At this point, I figure it's hardware related
Thanks for your help

SwimDrewid said:
I don't have an EFS backup on my google drive (like I thought I did). I think I have the backup in the office, but not available now.
No joy on the Chroma -- still no PRL data, no phone sound on dialing, no receiving calls
At this point, I figure it's hardware related
Thanks for your help
Click to expand...
Click to collapse
Have you changed any settings in the test menu? Another option would be to swap sim cards out with another phone to see if yours works in theirs and vice versa. As a last resort before you RMA you should wipe everything and flash the stock images and start fresh. Even if that doesn't fix it I think you would have an easier time with the RMA process being completely stock and relocking your bootloader.

murphyjasonc said:
Have you changed any settings in the test menu? Another option would be to swap sim cards out with another phone to see if yours works in theirs and vice versa. As a last resort before you RMA you should wipe everything and flash the stock images and start fresh. Even if that doesn't fix it I think you would have an easier time with the RMA process being completely stock and relocking your bootloader.
Click to expand...
Click to collapse
So, uh, I forgot to mention a critical piece of data: I live in Georgia, but this occurred at one of the South Carolina beaches, over 300 miles away.
I had full LTE, but noticed the phone said Not Roaming (or roaming: false).
As soon as we got home today, boom -- could make and receive calls again.
So, I think I can close this thread and open a new thread on how to get roaming to stick.
Thanks for all your help! :good:

No Data on Verizon

So, I was using my phone at a mall. I stepped into a store and I noticed I had no more LTE. The signal was weak, so I thought it was just the building. So I got to a stronger area and restarted the phone, and still no data. I tried restarting several times and I tried selecting different APNs (I'm running 7/15 nightly of CM13). Eventually, I took the sim card out of my wife's iPhone 6S and the LTE worked fine. My sim card worked OK in here phone as well. But once I put mine back in, I have no data (not even 2g or 3g). I thought it was just my sim card, but then I can't understand why it works in my wife's iPhone 6S. Any ideas? I'm updating to the latest nightly of CM13.

ambig88 said:
So, I was using my phone at a mall. I stepped into a store and I noticed I had no more LTE. The signal was weak, so I thought it was just the building. So I got to a stronger area and restarted the phone, and still no data. I tried restarting several times and I tried selecting different APNs (I'm running 7/15 nightly of CM13). Eventually, I took the sim card out of my wife's iPhone 6S and the LTE worked fine. My sim card worked OK in here phone as well. But once I put mine back in, I have no data (not even 2g or 3g). I thought it was just my sim card, but then I can't understand why it works in my wife's iPhone 6S. Any ideas? I'm updating to the latest nightly of CM13.
Click to expand...
Click to collapse
My suggestion is to start fresh by fastboot flashing the latest 6.0.1 factory images. Verify that your mobile data/LTE are working. Then, install TWRP. I would also download a fresh copy if the CM13 ROM and verify the md5 is correct. Flash CM13 again and see if you have LTE again. If you don't have LTE after flashing CM13 again we know it is something that has changed in the ROM.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
My suggestion is to start fresh by fastboot flashing the latest 6.0.1 factory images. Verify that your mobile data/LTE are working. Then, install TWRP. I would also download a fresh copy if the CM13 ROM and verify the md5 is correct. Flash CM13 again and see if you have LTE again. If you don't have LTE after flashing CM13 again we know it is something that has changed in the ROM.
Click to expand...
Click to collapse
I think you're right. I'm going to have to do this. I got a new SIM card from Verizon and data was fine. Then once I went to work and entered into my office, which has a poor signal, I wasn't able to get data back (can still call and send/receive texts). It makes no sense as to why it won't reconnect after a reboot, but I guess this is the only option.

Yeah I agree. Fastboot flash the factory images to give yourself a fresh start. Confirm that everything is working on a fully stock build. Then root, recovery and flash. I would try a different ROM that is not CM based to see how your voice and data works. Let us know how it goes that way others in the forum who may run into this issue can read about what was performed on your device and know what to do to help themselves. Good luck.
Sent from my Nexus 6 using XDA-Developers mobile app

fast69mopar said:
Yeah I agree. Fastboot flash the factory images to give yourself a fresh start. Confirm that everything is working on a fully stock build. Then root, recovery and flash. I would try a different ROM that is not CM based to see how your voice and data works. Let us know how it goes that way others in the forum who may run into this issue can read about what was performed on your device and know what to do to help themselves. Good luck.
Click to expand...
Click to collapse
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. I like my screen to be a bit colder than what Huawei calibrates their displays to.

ambig88 said:
So I flashed the factory images back onto my phone and I got data back. I guess there is a strange bug in the latest nightly of CM13. Of course, I haven't been able to go to an area where I have poor reception. Now I have to find a ROM that offers the LiveDisplay feature CM13 offered. I like my screen to be a bit colder than what Huawei calibrates their displays to.
Click to expand...
Click to collapse
I knew there was something in the CM13 based ROM's that was causing you to lose data. Also, If you use a custom kernel like Elemental or Elite you can control the screen colors and make it how you like it. Give Pure Nexus a try. It's a super nice ROM. The dev is awesome. He does great work. Maybe give Chroma a shot. Also, you could try Resurrection Remix. It's a CM based ROM but it may not give you the data issues. It's worth a try. Lemme know what works. Good job on getting the factory images flashed and getting data back too.
Sent from my Nexus 6 using XDA-Developers mobile app