Develop Bugs

Wifi issue on AOSP Roms

Hi guys,
I have had the s2,s3,galaxy nexus,original note and i am used to flashing and modifying,but i have a serious issue with the note 2.
The problem is whenever i flash AOSP rom(cm,aokp,pa) my wifi would not connect.It shows the name of the network and when i click conenct nothing happens.Flashing back TW rom fixes it,wifi works like a charm. I've done full wipes but it doesn't seem to resolve the issue.I tried different kernels,but that doesn't help either.
So I am stuck at TW roms and i hate that.Anyone has any ideas?

You can try options 2 and 3 from this thread.

Thanks for your reply,but i tried this and it didn't solve my problem.

Anyone?

spookhc said:
Anyone?
Click to expand...
Click to collapse
I Have the same problem...

Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.

Primokorn said:
Not sure that it will help you but I read something yesterday about this issue.
The solution was to NOT restore your Google profile during first boot so you should full wipe and try again.
Click to expand...
Click to collapse
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.

With my Note2 this is not the solution. I've tried everything. What you said, move file "pit" ..... but nothing. I can not connect wifi. The connection does not appear region Spain, and have opted to choose europe, but neither. I do not know to do. CM 10.1 also does not work WIFI. In Stock ROM or Custom ROM works fine fine, but in ROM CM 10.1, 10.2, AOKP don't work.
spookhc said:
This actually has nothing to do with the problem.
After a few days I finally found the cause ,and therefore,a decision to the problem.
It is the bootloader from 4.3 sammy leaks.It seems that this new leaks(probably the reason being KNOX) cause malfunction of wifi in aosp roms.What i did was ODIN flash stock MG1 from sammobile .This brought back stock recovery so i had to flash TWRP again and it solved the issue for me.
Before that i had tried changing roms,kernels,recovery,modems and nothing worked so I am pretty sure it is the new 4.3 leaks bootloader.
Some people will say that it can\t be the issue because they are using 4.3 sammy and do not experience the same problem on aosp roms,but i think thats because they flash it through CMW ,which doesn't change bootloader,while flashing through ODIN does.
Click to expand...
Click to collapse

Help: The wifi doesn't work, and the mac address is 00:00:00:00:00:00

my device is e980, I flash some roms (carbon, beanstalk BS_homony)and found that the wiif doesn't work except on the stock rom and the slimbean rom, the mac address is 00:00:00:00:00:00. I google it and changed the /data/misc/wifi/config file with modify the cur_etheraddr=23:dd:88:99:c2:e4. When I reboot, the wifi still doesn't work and the cur_etheraddr=00:00:00:00:00:00. I don't konw how to fix it, anyone who can help me, thanks a lot!!!!

http://forum.xda-developers.com/showthread.php?t=2419802
First try to flash the stock rom
And then try again with custom roms.

meow-xda said:
my device is e980, I flash some roms (carbon, beanstalk BS_homony)and found that the wiif doesn't work except on the stock rom and the slimbean rom, the mac address is 00:00:00:00:00:00. I google it and changed the /data/misc/wifi/config file with modify the cur_etheraddr=23:dd:88:99:c2:e4. When I reboot, the wifi still doesn't work and the cur_etheraddr=00:00:00:00:00:00. I don't konw how to fix it, anyone who can help me, thanks a lot!!!!
Click to expand...
Click to collapse
I ran into this same problem and after many attempts at after market ROMs, C10.1 and 11, I had to go back to stock. Was never able to figure this out and it seems like not too many people ran into it.

Hey, I was able to get it working with the latest nightly CM build. The way I did it was to do a dirty flash on top of the LG stock Rom and then do a Data/Cache Reset. Now I'm not sure if it's been fixed in the CM build itself or if it was the dirty flash, but it's been running great so far.

I did not have the 0.0..... mac address problem in the latest CM11 nighlies but the wifi would not work.
After many reflashes I found that if in settings>wifi>advanced>region code I checked any country, the wifi would start working immediately.
Although the setting did not stick on reboot.

[Q] no signal and data when installing latest pacman rom

Please help noob here and I'm having problems with the latest ROM from pacman 4.4 build. Every time I install I do not get any data or signal. Also when I try to sign into Google even with WiFi on I get message saying unreliable connection or I'm not signed up for data if issue persist to contact customer service any help will b appreciated.

What build are you trying to install, have you tried re-downloading the ROM also if you're trying to flash a different kernel with the ROM you have to let it boot once before doing so.

xBkKx said:
What build are you trying to install, have you tried re-downloading the ROM also if you're trying to flash a different kernel with the ROM you have to let it boot once before doing so.
Click to expand...
Click to collapse
I have tried downloading all the updates that pacman released in august. I also downloaded the 20140825 and 20140819 twice and still not working. everything works fine with the 4.3 pacrom. Thanks for reply.

Found solution to no data or signal on 4.4 here is a link if anyone else runs into this problem http://forum.xda-developers.com/showthread.php?p=52754863. Big thanks to ducter

Interesting, never had that issue myself but glad you found a solution!

xBkKx said:
Interesting, never had that issue myself but glad you found a solution!
Click to expand...
Click to collapse
Yea its weird reading the thread it only happens to some phones. I guess I just had one of those phones.

Help Needed Bluetooth Issues

I have a S4 M919N on CM12 Nightly and my Bluetooth is acting up. It will connect to my car and disconnect by itself and when I try to go into the settings of the phone it doesn't let my turn the Bluetooth on anymore. I restart the phone and it connects again but when I make a call or play music, my phone says Bluetooth has stopped working. It used to work fine on Stock. All i've done so far is just root and flash CM12. I'm really inexperienced with this stuff so any help will greatly appreciated. Thank you in advance.

Don't know for sure, but could be a cm issue at the moment. Try reflashing fresh cm12 or latest nightly

serio22 said:
Don't know for sure, but could be a cm issue at the moment. Try reflashing fresh cm12 or latest nightly
Click to expand...
Click to collapse
I ended up flashing to stock and re flashing CM12 and it was working, but didn't get to really test it because I ended up selling it. Thanks for the help.

GPS not working on SlimKat 4.4.4

Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo

drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
Hi, the link you provided points to build 4. You can find build 9 which is the latest slimkat here http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1183-d2lte
This is the one I have for my Koodo I747M. *note camera seemed a little buggy in some instances, so I installed open camera. Seemed to work a lot better.

I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?

drakemiller40 said:
I'll give it a try, thanks for the help. Quick question, will this work on my phone model without bricking? I only tried the at&t not the d2lte.
Also can you send me the link for this open camera you were talking about for my device as well?
Click to expand...
Click to collapse
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?

serathe said:
I'd imagine it should be ok, since we have the same phone pretty much I'm on koodo which is pretty much telus without the customer service hehe. for kitkat at the end of development they basically lumped a d2att, d2tmo etc together. (this has reverted for the lollipop builds out there).
The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course.
It's a google play app open source, the slimkat one I had seemed to lockup when switching from front to back camera and from camera to video. https://play.google.com/store/apps/details?id=net.sourceforge.opencamera&hl=en
What are you using to flash them?
Click to expand...
Click to collapse
Im not very experienced lol and got lost on:
"The last OTA I got was FOB1, so you may want to go to stock to ota to the latest updates from telus. Just so you have the latest bootloader/firmware. But that's up to you of course. "
I'm using TWRP

Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.

serathe said:
Ah, ok I just keep a backup in case anything goes bad flashing roms. If you use TWRP to flash them it only affects the boot image, data and system. So if you have problems you can restore from backup nice and easy.
I'm swapping between a few right now. So far my only uh oh experience was when I tried to upgrade TWRP, no problems with roms. But I use TWRP as well, works great.
Basically the baseband version on our phone, it's the radio and bootloader. Before I had rooted it I had gotten the latest updates by checking for updates. It downloaded and upgraded to FOB1 (Baseband I747MVLUFOB1), then I rooted and played with flashing. Not sure if you made a backup of your original install before trying another rom. But it's not a necessity for slimkat, I don't believe.
Click to expand...
Click to collapse
Yeah I always create a nandroid and backup my IME.

drakemiller40 said:
Hello,
So I've flashed before Slimbean, but had problems with the "can't connect to camera" problem, so I decided to flash Slimkat 4.4.4 which fixed the camera problem.
New problem now is that i can't get any gps signal. I can turn it on, but no signal. Anyone have a solution to this, or is experiencing the same problem?
Downloaded from here: http://www.slimroms.net/index.php/downloads/dlsearch/viewcategory/1074-d2att-d2tmo
Click to expand...
Click to collapse
First thing to try for GPS problems is taking off the back cover and snugging up all the little screws around the phone. Sometimes they work their way loose and the GPS antenna seems to be the first thing to suffer from it.
If that doesn't cure it you might need to flash a stock or at least stock based ROM and rebuild the nvram. Here's a link that describes how to do that if you need to.