Database Develop

WiFi Problem with LANIGHT

I've been through four roms and managed to try each one out successfully. I've had issues, but none too difficult to figure out. I tried this one:
http://forum.xda-developers.com/showthread.php?t=1867484
And am having the WiFi problem some of the other posters outlined. I can't post on the forum because I don't have enough posts. I'm coming from the lastest Helly Bean build (http://forum.xda-developers.com/showthread.php?t=1783064). I followed the instructions (as much as possible from my version of recovery). I wiped data 3 times, wiped cache, wiped dalvik cache, cleared init.d and NSTools then installed it. Wifi gets stuck on "turning on wifi" and remains there, even after restarting. I attempted to reinstall the rom 3 times, it had the same problem each time. Finally gave up and went back to Helly Bean.
Gonna check out a couple other JB roms in the meantime, but I was hoping that one would work since people attest to the speed!
UPDATE: Put RemICS JB v2.0 (http://forum.xda-developers.com/showthread.php?t=1625619) on it and it works like a charm now. Still wouldn't mind trying out LANIGHT, but did anyone ever figure out how to fix the wifi issue?

I have the same problem coming from the latest helly bean. I flashed LANIGHTv2 5 times already and still have problems with the wifi. I tried coming from X-bean, which the wifi works perfectly, but still no dice. I have not one clue on how to fix the wifi.

Blu3izzy said:
I have the same problem coming from the latest helly bean. I flashed LANIGHTv2 5 times already and still have problems with the wifi. I tried coming from X-bean, which the wifi works perfectly, but still no dice. I have not one clue on how to fix the wifi.
Click to expand...
Click to collapse
Spent very little time on LANIGHT but I was reading their thread earlier and they've done a different build with a different kernel. It seems the one persone with the wifi issue that stuck around the thread(or could post) had success with the new build using a different kernel.

Which kernel are you using? I flashed the devil kernel today and followed the 2nd set of instructions and flashed the Lanight v2 nodatadata version. Everything including wifi has worked for me.

I am having an issue with WIFI on my LANIGHT 6.0 NDD. Wifi works fine for me except when I use airplane mode. When using airplane mode wifi will not turn on unless I enable Bluetooth. This use to work correctly in 4.2 DD. Is this a known issue or is their a fix for this.
I am using the "stock" kernel which comes with 6.0 NDD.

Hoodlum7 said:
I am having an issue with WIFI on my LANIGHT 6.0 NDD. Wifi works fine for me except when I use airplane mode. When using airplane mode wifi will not turn on unless I enable Bluetooth. This use to work correctly in 4.2 DD. Is this a known issue or is their a fix for this.
I am using the "stock" kernel which comes with 6.0 NDD.
Click to expand...
Click to collapse
No wifi issues here on the latest v6.5_DATADATA. Using the Devil kernel.

[Q] SlimBean and SlimICS issue after upgrading from SlimBean 2.1 to 2.3?

This one is bugging me, because I can't figure out what is going on with this ROM on my captivate all of a sudden.
I've incremented through SlimICS 4.2, then SlimBean 2.0, then 2.1 and it was working fine. I figured 2.3 would be okay to go to to see if it helps further with speed/stability, but what is happening now is after it powers on, it works fine until the screen turns off. after that, I can't get any response from the phone, either by plugging in power, USB to Windows PC anything. I know it's still on because it runs warm, like some process has "run away" and I've even gotten some notification sounds from it, when the speaker volume was up. I've also tried re-flashing older 2.1, 2.0, SlimICS 4.2, but all versions of SlimRom have the same behavior. I thought maybe some file was not updating, so I downloaded CM10 (one off XDA with Devil Kernel), and that worked fine to turn off and on the screen. I was hoping I had overwritten whichever file is bad on Slim, and then re-flashed Slim, and the same behavior is occurring on all the Slim versions I've tested again. I prefer the toggle options of Slim, but would go CM10 if it's the only way. can anyone suggest anything regarding fixing an issue with the system not waking from sleep like this?
I know that in Recovery, the Power button works fine for presses, so the button itself is fine. Any help would be appreciated.
Thank you,
CaretakerThe

caretakerthe said:
This one is bugging me, because I can't figure out what is going on with this ROM on my captivate all of a sudden.
I've incremented through SlimICS 4.2, then SlimBean 2.0, then 2.1 and it was working fine. I figured 2.3 would be okay to go to to see if it helps further with speed/stability, but what is happening now is after it powers on, it works fine until the screen turns off. after that, I can't get any response from the phone, either by plugging in power, USB to Windows PC anything. I know it's still on because it runs warm, like some process has "run away" and I've even gotten some notification sounds from it, when the speaker volume was up. I've also tried re-flashing older 2.1, 2.0, SlimICS 4.2, but all versions of SlimRom have the same behavior. I thought maybe some file was not updating, so I downloaded CM10 (one off XDA with Devil Kernel), and that worked fine to turn off and on the screen. I was hoping I had overwritten whichever file is bad on Slim, and then re-flashed Slim, and the same behavior is occurring on all the Slim versions I've tested again. I prefer the toggle options of Slim, but would go CM10 if it's the only way. can anyone suggest anything regarding fixing an issue with the system not waking from sleep like this?
I know that in Recovery, the Power button works fine for presses, so the button itself is fine. Any help would be appreciated.
Thank you,
CaretakerThe
Click to expand...
Click to collapse
You could try flashing a devil kernel on top of Slim and see if that doesn't fix your problems. Typically when someone is having this sleep issue it's a result of enabling Deep idle in the kernel settings. But being that it's happening to you even after a clean flash I don't know if thats it. But considering that when you're on CM10 you don't have issues and when you go back to Slim, which is all Semaphore you have the issues I would say it's kernel related.

m1batt1 said:
You could try flashing a devil kernel on top of Slim and see if that doesn't fix your problems. Typically when someone is having this sleep issue it's a result of enabling Deep idle in the kernel settings. But being that it's happening to you even after a clean flash I don't know if thats it. But considering that when you're on CM10 you don't have issues and when you go back to Slim, which is all Semaphore you have the issues I would say it's kernel related.
Click to expand...
Click to collapse
Thank you Cappy m1batt1, that worked. I did have a Devil Kernel on my SD from a download link I found, and flashed that, it is working now. I have a Semaphore Manager app that came in the SlimRom, presumably with Semaphore Kernel. I found one for Devil Kernel from the Play Store just now. With any luck, I will not have to change or reinstall ROMs again before I can get a new phone...whenever that may be.
I would call this one resolved

Help regarding AOSP 4.2 Jelly Bean ROM

So as the title states, this is regarding the AOSP ROM 4.2 Jelly Bean, I installed it and it seemed to be working fine until I actually tried something, the wifi didn't work so I tried installing the fix, I plugged it to the PC and nothing happens, it doesn't even charge, tried 2 different laptops and 2 different PC's. So I sent the fix over through bluetooth and installed it, the wifi isn't working eitherway, so I guess that there is no point of using the phone since I can't really get a single app, I want to install a 4.1 or the default XXJW4 2.3.6 gingerbread version and I'm wondering how do I do that now when the usb isn't working, also note that I've done nearly 50 ROM installations and I have never ever had a problem before, this is the first time. What should I do? Is there a fix for this? If not, how do I downgrade? Please help, ASAP, my beloved SGS i9000 is useless atm and It's nearly making me cry (well not obviously, but yeah, I need help) Best regards, thanks in advance.

sunz1337 said:
So as the title states, this is regarding the AOSP ROM 4.2 Jelly Bean, I installed it and it seemed to be working fine until I actually tried something, the wifi didn't work so I tried installing the fix, I plugged it to the PC and nothing happens, it doesn't even charge, tried 2 different laptops and 2 different PC's. So I sent the fix over through bluetooth and installed it, the wifi isn't working eitherway, so I guess that there is no point of using the phone since I can't really get a single app, I want to install a 4.1 or the default XXJW4 2.3.6 gingerbread version and I'm wondering how do I do that now when the usb isn't working, also note that I've done nearly 50 ROM installations and I have never ever had a problem before, this is the first time. What should I do? Is there a fix for this? If not, how do I downgrade? Please help, ASAP, my beloved SGS i9000 is useless atm and It's nearly making me cry (well not obviously, but yeah, I need help) Best regards, thanks in advance.
Click to expand...
Click to collapse
your phone can go to download mode? if can should not have any problem for flash to 2.3.6 GB, if you wan to flash 4.1 JB you can copy the ROM to your ExtSDCard and boot to recovery and flash the rom for extsdcard or you can use filemanager to move the ROM(File) to you int.SDcard and flash from recovery.
BTW which AOSP 4.2 you are using? if from pawitp you can try this my one is working and i try it many time and having the same result .
if now your are on the same partition layout as CM10 stable, follow the step below
1) Flash the rom 4.2 (20121125) following all the step given by the guide
2) Flash Google Apps
3) reboot phone to normal (turn on wifi if not working then go to step 4)
4) Reboot to cwm and flash wifi fix without wipe
holp this will help. :good: enjoy

sunz1337 said:
So as the title states, this is regarding the AOSP ROM 4.2 Jelly Bean, I installed it and it seemed to be working fine until I actually tried something, the wifi didn't work so I tried installing the fix, I plugged it to the PC and nothing happens, it doesn't even charge, tried 2 different laptops and 2 different PC's. So I sent the fix over through bluetooth and installed it, the wifi isn't working eitherway, so I guess that there is no point of using the phone since I can't really get a single app, I want to install a 4.1 or the default XXJW4 2.3.6 gingerbread version and I'm wondering how do I do that now when the usb isn't working, also note that I've done nearly 50 ROM installations and I have never ever had a problem before, this is the first time. What should I do? Is there a fix for this? If not, how do I downgrade? Please help, ASAP, my beloved SGS i9000 is useless atm and It's nearly making me cry (well not obviously, but yeah, I need help) Best regards, thanks in advance.
Click to expand...
Click to collapse
Did you try to mount USB in recovery? mounts and storage --> mount USB storage

Nm

Juckie_ said:
Did you try to mount USB in recovery? mounts and storage --> mount USB storage
Click to expand...
Click to collapse
Thanks a loads, installed beast rom this way, love you so much man, http://forum.xda-developers.com/showthread.php?t=1687685 just installed, wifi works, will check other functions soon, I guess you can lock this topic, seriously thanks a loads.

[Solved] [4.2.2+] No Network Signal - Any fixes?

I have a S3 Mini I8190N, Baseband I8190NXXALL6, on Three Ireland.
I've tried all of Maclaw's CM10.2 roms for the last month, along with some of OliverG96's releases, and none of them show up any network signal for me, and won't let me search for networks, almost as if the rom can't use the hardware radio.
The stock 4.1.2 rom works perfect.
I've tried changing my baseband from I8190NXXALL6 to I8190NXXAMG1, and that made no difference.
(Stock still has perfect signal, Maclaws CM10.2 has no signal at all)
I've also looked through the build.prop files and compared them to the working stock build.prop, but I don't really think tweaks in there will fix this.
Seeing as this possibly could be a hardware issue, is there a file defining what radio hardware my phone has, like /proc/cpuinfo does for the cpu?
Anyone have suggestions on how i could fix (or help fix) this issue?
I can test suggestions and provide logcats if anyone requires?
EDIT:
Problem solved! seems there were some issues with my modemfs, and golden-guy's suggested fix here worked.

did you make a clean or dirty install?
if dirty try a clean install.

Same bug here and also Oliver96 has the same problem s.s
Sent from my GT-P3100 using xda app-developers app

JackoMJ said:
did you make a clean or dirty install?
if dirty try a clean install.
Click to expand...
Click to collapse
I've tried a dirty install, a clean (factory reset) install, and I've even went into ODIN, flashed a complete stock rom, TWRP, and then put CM10.2 on after that with a factory reset.
alexmarra3000 said:
Same bug here and also Oliver96 has the same problem s.s
Click to expand...
Click to collapse
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?

same problem
i have got the same problem too.
got back to original samsung firmware und stock recovery... nothing
i am from germany und tried out any available basebands... nothing
on any stock, theres no problem, but if i want to get some roms e.g. from maclaw.pl i cant get signal at all
greez

EccTM said:
Do you also have an I8190N? I'm trying to work out if its a hardware thing (like maybe we have a different hardware revision) or if its something we can actually fix. Is OliverG96 trying to solve this or is he just working on having a working rom for the majority?
Click to expand...
Click to collapse
No, I have the I8190 normal version like OliverG96, and I don't know if he is working on a fix.
The strange thing is some users have the bug and some users not.
Also I have this bug with paranoid rom, pac rom and aokp.
On the contrary with Dmod v6 I don't have any issue, probably because it is based on official firmware, I don't know sincerly.
Sent from my GT-P3100 using xda app-developers app

i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app

mausdefekt said:
i also think that the problem doesnt come up when u are using any rom which is based on stock firmware.
any custom rom which is using its own firmware doesnt get any signal
btw.: i am in the net of telco (o2)
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, i also use O2 (directly) and had never problems with any CM-ROM of Maclaw.
You checked the APN??? Maybe you have to use a different one.

build.prop tweaks
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
I did not try these myself, as I don't have any RIL issues, so use them at your own risk. Reboot afterwards for the changes to apply.
Source: http://geekyogi.tumblr.com/post/24692879082/android-build-prop-tweaks-root-only

Hi
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.

hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app

golden-guy said:
Did some of you already try adding/tweaking some attributes in /system/build.prop?
There are quite some available to get better signal:
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
Click to expand...
Click to collapse
I compared the maclaw 10.2 build.prop with my own functioning stock build.prop and changed most of the attributes about with no luck. I've also tried both those suggested options, but they seem to be more for improving signal strength rather than actually getting a signal, I didn't see any changes using them.
stenc55 said:
There was similar problem with SGS1 long ago, it was caused by wrong IMEI. Check your IMEI with stock ROM and then with CM rom.
Click to expand...
Click to collapse
Like mausdefekt, I get two slightly different results from *#06#.
My IMEI matches up, but when i'm running a non-stock based rom, my IMEI SV is 00 for some reason.

Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.

joelalmeidaptg said:
Guys, just back up your EFS partition and restore after you flash CM roms. You wouldn't have this kind of problems if you were using TWRP you know.
Click to expand...
Click to collapse
Ive tried that too, no difference. Also tried it with factorymode set both on and off.
I'm using Maclaw's TWRP 2.6.3.0 with kitkat support atm, I've never used any non-TWRP recovery.

mausdefekt said:
hey there, i looked up my imei with *#06# and got two different results.
the aokp custom rom shows me the same imei as the stock. but at stock, i get additionally "/ 01" at the end of the imei. the custom rom doesnt show this
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hey,
I am running CM-10.2 on my S3 Mini (Oliver's cm-10.2-20131116-UNOFFICIAL-golden) and RIL is working just fine. So I would not think that there is a general issue with RIL on custom ROMs. Rather, the way how you switch from stock to custom might have an impact on RIL...
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Since when I switched from stock to custom, I exactly did that. And I never had any issue with RIL on any custom ROM I have installed since then - which was basically all versions since the 20130928 release.
Cannot tell if that works out for you, but it's definitely worth a try
Btw, I did not check the additional "/01" in the IMEI output when I was still on stock. Running custom I get the very same output - just the IMEI, without this suffix. In the "about phone" section, the relevant IMEI SV entry does read "01" for me.

I wonder if your cellphone is SIM-locked...

hi
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
I've tried setcpu to raise min. cpu to 1ghz, nothing.
What's wrong? On AC all works fine!

golden-guy said:
You could try going back to stock, verify RIL is working again as expected and then start flashing anew following my approach using heimdall: http://forum.xda-developers.com/showthread.php?t=2537520
Click to expand...
Click to collapse
I factory reset, flashed back to complete stock I8190NXXALL6 (it's 4.1.2) using ODIN, and everything worked perfect. From there I followed your guide to flash CWM recovery, then flashed maclaw's cm 10.2 (20131123) but I still had the same RIL issue.
Then I tried flash the stock rom with heimdall instead of ODIN initially and then follow your guide, same result.
Then I downloaded the odin version of maclaw's CM 10.2 (20131122) and flashed it directly with heimdall. same result.
After that, I took apart both the stock and odin cm 10.2 versions, and tried use heimdall to flash a hybrid version of the two:
Stock: STEboot1.img, STEboot2.img, Modem.bin
CM10.2: boot.img, system.img, recovery.img
Still had no signal at all, so I flashed TWRP 2.6.3.0 recovery and restored back to my usual stock-based backup.
joelalmeidaptg said:
I wonder if your cellphone is SIM-locked...
Click to expand...
Click to collapse
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Timewolf said:
i've a similar issue:
tried all maclow roms (4.1 and 4.2), in standby no network signal.
When I plug the phone to AC all works fine, in standby without AC no network signal.
Click to expand...
Click to collapse
I just tried to see if i'd get any sort of signal on maclaw roms by plugging my phone into AC... no joy for me there either
Does it have signal if its plugged in then the phone is turned on, or can you get signal at any time just by plugging into AC? like:
*Turn on phone* > standby (on battery) - no signal > *plug into AC* > standby (on AC) - signal > *unplug AC* > standby (on battery) - no signal
Sounds like your problem could be more hardware based than mine? something to do with voltages possibly? I'm really not sure what to suggest.

EccTM said:
I checked (borrowed an o2.ie sim from a roommate) and it is network-locked to Three Ireland, but with my last phone (Samsung Galaxy Spica - I5700) it didn't affect using custom roms so I honestly didn't consider that... Do you think my problem could be that my device is network locked? Would that really cause this?
Click to expand...
Click to collapse
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?

joelalmeidaptg said:
The thing is, that operators and brands, on earlier devices, put some limitations on the devices. For example, if you buy a Sony smartphone from 2011 and forward that is SIM-locked, you won't be able to flash any custom kernel at all. Can someone with the same problem confirm that their phones are SIM-locked?
Click to expand...
Click to collapse
So assuming thats the issue, would getting a network unlock code allow me to use custom kernels and roms?

CyanogenMod WiFi problems

I have just flashed CyanogenMod for lb. The WiFi hangs on trying to turn on. I would appreciate any opinions is this a problem with the 201 kernel I came straight from 4.1.2 so I have no comparison as to whether my WiFi works on 4.3. I can't seem to find any threads/posts about this if there are any just redirect this. I have already tried reflashing the kernel. I can't access cwm to reflash CyanogenMod its supposed to be power&vol- but have tried all button combinations. I would like to sort this because everything else is working fine.
Sent from my C5303 using xda app-developers app

Wifi issue is a kernel problem. I think.. Some users are reporting the same problem with DoomKernel.
I suggest you went back to 4.1.2 > update to 4.3 to see if wifi has issues.
After this you can try CM for LB again.

mrjraider said:
Wifi issue is a kernel problem. I think.. Some users are reporting the same problem with DoomKernel.
I suggest you went back to 4.1.2 > update to 4.3 to see if wifi has issues.
After this you can try CM for LB again.
Click to expand...
Click to collapse
Thanks I managed to fix it I had to go back to 4.1.2 root it then tried 4.3 WiFi worked OK so back to CM again WiFi is working fine now. I don't think CM flashed properly because there were a few bugs and CWM wasn't working. It showed up in my system files but wouldn't boot into it even adb reboot recovery just got a normal reboot
Sent from my Xperia SP
If I've helped hit thanks

I had this issue, from recovery I wiped data and cache, rebooted and it works like a dream. All I need now is a way to get MSC back.
This CM11 rom is fast, smooth and a joy to use. Puts all other roms I've tried to shame!