I flashed Weapon v3.0 a few weeks ago (and wiped everything in CWM) and regardless of the WiFi sleep policy, I constantly need to disable and re-enable WiFi to get it to work after my phone's been inactive for a while. If I don't anything using the internet just times out. I came from xboarder's rooted GB OTA and didn't have this problem, and I didn't have this problem with CM7 either. Any help?
Use cm7 then its way better
Sent from my LG-P999 using XDA App
I liked CM7, but I had that stupid APN issue so data wouldn't work, both on the RC and 7.1.0.1 stable. The APNs Backup/Restore app works temporarily, but I don't want to reboot my phone every time I do that. I'm probably going to try nightly 201 next, but I still would like to know why Weapon has this WiFi problem while I don't see anyone else having it.
Happens to me on cm7 regardless of sleep policy.
Didn't experience that problem, maybe try flashing an older weapon over it (2.8 or 2.7) and see if that works. I had 2.8 but was having a bluetooth problem and 2.7 is working fine for me.
LuponX said:
I flashed Weapon v3.0 a few weeks ago (and wiped everything in CWM) and regardless of the WiFi sleep policy, I constantly need to disable and re-enable WiFi to get it to work after my phone's been inactive for a while. If I don't anything using the internet just times out. I came from xboarder's rooted GB OTA and didn't have this problem, and I didn't have this problem with CM7 either. Any help?
Click to expand...
Click to collapse
I had this from a battery management app. Uninstall any you have and reset any other wifi related timed management to not managing wifi. See if that helps. If it does, reinstall the battery management app and don't set it to manage wifi. If that doesn' t work, reflash the kernel and rom
Related
I am S-Off, and rooted
I had this problem with the ICS which I flashed after S-Off, so I rooted and flashed eleganza, SAME PROBLEM?!
Here's what happens-
WiFi connects with Router and shows correct strength, connects and downloads or surfs web or whatever then just stops dead! The device obviously thinks its connected to Wifi as it doesnt let the mobile signal kick in. If I disable WiFi it then connects to mobile network. If I reconnect to Wifi it works for a bit then disconnects as before.
This is driving me insane! any suggestions?
Tried changing Router channel and security encryption.
i never had the same problem, but the most common solution when wifi is not working on ICS is that you should do a complete wipe, dalvik and cache and format all partitions except SD-card.
that usualy helps, let me know if it worked for you...
Did a superwipe before I Flashed the custom Rom, which should have done all that I think, cheers for the reply
Do you have installed custom kernel, I seem have bit problem with my signal when using faux123 beta kernel. So my suggestion is try install and using other's kernel like the final version faux123, sebastianFM or stock kernel. If you using cpu control application try not to set the lowest to low.
On the Advanced Wi-Fi try to set "Keep Wi-Fi on during sleep" to Always.
If you have set "wifi.supplicant_scan_interval" on build.prop try to decreased it.
I am using sebastianFM , "Keep Wi-Fi on during sleep"is already set to Always
Now tried new rom and new kernel and have now supercid. Any ideas?
Search for WiFix in this forum, it's an app, it might help ?
http://forum.xda-developers.com/showthread.php?t=1445766
I had a similar problem with all the Elegancia versions that I tried (3.4.1 and 3.5.0).
It recognised my neighbours' routers by not mine, I did not have wifi signal at all.
No problem with any other ICS rom such as ARHD, InsertCoin and CoreDroid.
My router is the O2 Wireless Box (which is actually Thomson ST780). If yours is the same there might be compatibility issues between Elegancia and this specific router.
I had a similar problem with ARHD few months ago... Did a superwipe, flashed the same rom again, flashed radio other than was used in a rom and didn't do any backup restore... I think some wifi application messed with crucial wifi settings but I flashed other radio because I wanted to find solution faster... So don't know exactly what helped..
I've always had this issue with ARHD since ICS leaked. I could always get connected to other WiFi connections, but not my own at home which uses WPA2. The phone does actually show full WiFi signal and thinks it's connected, but can't really get out to the internet.
I could get it to work by either a) flashing another ROM that worked for me like InsertCoin then flashing ARHD directly over it without a wipe, or b) just wiping and going with InsertCoin from the beginning haha.
I used mostly IC anyway during Gingerbread times, so it wasn't a big deal for me to stick with IC for ICS. But I still wonder what causes this issue. I read in the ARHD thread that there are WiFi-related files that can be replaced to make things work, but I figured that would eventually get annoying for me since I flash often.
I found the same problem with two different Android phones after rooting.
Connects, works for a short while then no traffic gets through. Disconnect, then reconnect usually works for a few seconds more?
My solution was to reconfigure the router...it had maximum speed settings that allows 75, 150, 300. When I set it down to 75 it started working reliably.
Same as above...I was using WPA2 and it only affected my home router.
Not sure if same issue, but worth a try!
______
Sent from my HTC Sensation XE with Beats Audio using Tapatalk 2
I'm running Hellfire 2.1 and I have a strange issue. The wifi randomly won't disconnect after going way out of range for a long time(like I drive away from house and check phone 30 min later). Accessing the net results in connection timeouts etc, but wifi still says "Connected to XXX". The only way to fix is to manually disable wifi and reenable.
I tried both faux and trinity kernesl. Same thing. Tried fix permissions/clean re-flash with all the wipes, same thing.
Any advice? Thanks.
ilovecats said:
I'm running Hellfire 2.1 and I have a strange issue. The wifi randomly won't disconnect after going way out of range for a long time(like I drive away from house and check phone 30 min later). Accessing the net results in connection timeouts etc, but wifi still says "Connected to XXX". The only way to fix is to manually disable wifi and reenable.
I tried both faux and trinity kernesl. Same thing. Tried fix permissions/clean re-flash with all the wipes, same thing.
Any advice? Thanks.
Click to expand...
Click to collapse
Never heard of the issue I'm on the same rom what was the install process?
Sent from my LG-P999 using xda premium
1.Flashed latest CWM via NVFlash
2. Ran Nullifier dual wipe
3. Installed Hellfire 2.1 Rom via CWM
4. Installed GApps as provided in the HF 2.1 post
5. Rebooted, didn't touch anything for 10 min
6. Set up Google account, set various settings etc
7. Rebooted again. Waited another 5 min
First noticed the problem soon after I started using the new rom. A day later, I flashed 0.48CM faux kernel. Same thing happened once. Flashed to Trinity ELP, experienced a couple of application crashes, flashed again to Trinity T15. (didn't encounter the problem during the very short period of ELP). Did a couple of intentional tests on T15, wifi disconnected OK. But one day later, the issue randomly came back.
ilovecats said:
I'm running Hellfire 2.1 and I have a strange issue. The wifi randomly won't disconnect after going way out of range for a long time(like I drive away from house and check phone 30 min later). Accessing the net results in connection timeouts etc, but wifi still says "Connected to XXX". The only way to fix is to manually disable wifi and reenable.
I tried both faux and trinity kernesl. Same thing. Tried fix permissions/clean re-flash with all the wipes, same thing.
Any advice? Thanks.
Click to expand...
Click to collapse
I believe it's just a known G2X bug.
Happens to me on EVERY ROM. Custom kernel or stock. Minor inconvenience in my opinion.
I've had the same issue from time to time on stock ROM as well as various builds of cm7 with stock kernel and with morfic's ELP kernel. Doesn't happen too frequently though so I just toggle the wifi when I have to. I reboot the phone a few times a week and I get the problem less now than I used to.
It only happened to me when I used public networks, like at university for example. I think the phone tries to connect the network with a very weak signal and as you walk it receives signal or not depending on where you are. Powering off the wifi fixes the problem
Thanks to all the replies. Glad to know it's not a software issue and I'm not alone.
Basically this is a WiFi issue with all CM10/AOKP fresh installed after Sep the 11th.
I said Sep the 11th because that is the best refference I can find.
If I flash any CM10?AOKP based ROM released after that date I lose wifi on 1st reboot after initial setup. To get the wifi working I have to toggle on the wifi manually, or toggle off and then on or reboot. I could not find a pattern. At the end the problem is that the wifi does not start on boot by itself. Let me be very clear here. Fresh flash.
Now here is the strange thing. I have several nands for Paranoid, CM10, SlimBean (unfortunately none for AOKP), taken pervious to that date and if I dirty flash to the last release everything works fine. No problems with the wifi.
The stock ROMs all of them work fine, fresh or dirty flashed.
I googled the internet and checked xda and other forums. I found just couple of similar situations but with no working solution .
One of them says that you have to odin back to stock, connect to wifi and then flash CM10. I did that and no go.
I tried different routers in different wireless configurations, same problem. Static ip and stuff.
Sometimes I get the wifi network "not in range" or the toggle for wifi in setting semi off or on.
If this is a wifi driver problem then:
1. can I get an old CM10/AOKP driver injected to the new releases?
2. why when I dirty flash the old driver (present in nand) does not get overwritten?
3. did you see anywhere a similar problem or it's only me.
Thanks in advance for your help.
same issues here on any build of aokp. wifi works until after a restart. i get the out of range error or wps failed. i have to shut off wifi and turn it on to connect. really annoying. funny thing is on ics i have no issues with wifi auto connecting.
ideas? Kinda weird only a small handful of people have this going on.
I've noticed WiFi issues also while on cm10. Lately I've noticed WiFi becoming better in more recent nightlies. However I've been doing clean flashes, and not restoring any system settings from backups. Even unclicking the boxes from the initial startup that allows Google to backup and restore settings on the phone. I'm assuming that possibly some setting/config is being restored causing the issue... just a thought
MyndMayze said:
I've noticed WiFi issues also while on cm10. Lately I've noticed WiFi becoming better in more recent nightlies. However I've been doing clean flashes, and not restoring any system settings from backups. Even unclicking the boxes from the initial startup that allows Google to backup and restore settings on the phone. I'm assuming that possibly some setting/config is being restored causing the issue... just a thought
Click to expand...
Click to collapse
Nope i dont restore anything and always do a fresh clean install. If i had to guess its a buggy wifi driver that causes issues with certain routers. That would explain why very few have our issues. I guess for now ill stick to beans rom and wait for the jb ota.
Its worse than i thought as i have this issue on all the aosp varients. I just tried cm10, all aokp, liquid and slimbean. Same wifi error. I nandroid back to beans ics rom and everything is fine. Its got to be a wifi driver issue. There has to be more than myself and the op having this issue.
Hi,
I have problem with my data connectivity on my Sensation for a long time. If I turn on my phone and mobile data (mostly I choose "UMTS only" mode), I have internet connection without any problems, but after some time (usually few days, but if I'm driving and using phone as my navigation it can be hours) phone can't connect to internet, but 3G icon is still there. If I reboot the phone everything comes back to normal. Turning off and on radio/mobile data and switching between 2G and 3G doesn't work, only reboot works.
bluepawel said:
Hi,
I have problem with my data connectivity on my Sensation for a long time. If I turn on my phone and mobile data (mostly I choose "UMTS only" mode), I have internet connection without any problems, but after some time (usually few days, but if I'm driving and using phone as my navigation it can be hours) phone can't connect to internet, but 3G icon is still there. If I reboot the phone everything comes back to normal. Turning off and on radio/mobile data and switching between 2G and 3G doesn't work, only reboot works.
Click to expand...
Click to collapse
You're using stock ROM? Try to flash radio module. Maybe it'll help you to solve this problem...
bender19911 said:
You're using stock ROM?
Click to expand...
Click to collapse
Nope, ARHD 7.2, stock kernel, 11.76A... radio
Hi all,
I don't have the same problem as you but I couldn't find another thread with a similar theme.
When I turn on my mobile internet (O2 UK) it takes a few minutes to turn on, then stays on for about 1 second then off again for about 30 seconds This just keeps repeating and never stays constantly on.
I have no idea what happened or what I've changed.
This has been happening for a couple of months now. It used to work fine all the time everywhere.
I've tried changing the radio and RIL files (they are currently matching according to GetRIL app).
I'm using Viper 1.6.3 with Firmware 3.33, RIL 4.0.0037HMQ(2), Radio 11.76A.3504.00P_11.24A3504.31_M
I've tried different kernels too. Currently using Pacha kernel (not PYD-X)
I have included a logcat if anyone can help me.
Many Thanks In advance.
https://www.dropbox.com/s/gghmtxkqgxxezt3/logcat.2013-04-06-03-26-21%2B0100.txt
Hello OP,
Don't worry, you're not going crazy. I have (had) the same problem with ARHD 6.7 and 6.8
When I first started using ARHD 6.6x - I NEVER had this issue, only when I moved to ARHD 6.7 I noticed the same strange issue you have. I couldn't find anything in the forums at the time with similar reports. The only thing that would fix the "no throughput" issue on UMTS was to powercycle or a full reboot or a "hot reboot" when using the advanced power menu - the hot reboot would just reboot the shell - but that was enough to fix the "problem". I even manually upgraded faux123 kernels to the rule out a kernel issue triggering the problem.
I then upgraded to 6.8 when it came out in the hope that would fix but not luck.
So far I am running ARHD 7.2 and not yet (touch wood) seen the issue. However I have taken the chance to do a very clean install and use Titanium Backup to only restore what I really needed, like call logs, SMS/MMS and for most of everything re-entered settings manually.
We shall see how it goes....
bender19911 said:
You're using stock ROM? Try to flash radio module. Maybe it'll help you to solve this problem...
Click to expand...
Click to collapse
That won't help. I also had tried rolling back to different RADIOs and none helped. So it's not a RADIO img issue or a kernel issue. It's something else.
ok, so this might seem kinda obvious, but i want to know for sure. wifi calling has been running even when i'm NOT on wifi... is this right? and will i be able to make calls while connected to wifi if i uninstall it? only because "cell standby" has been eating up battery for some reason for the past couple days. i'm rooted running cm7 / mazout360's 2.6.32.60 kernel / wolfscript on this g2x. i'm pretty sure that the 'omdaclient' apk isn't here anymore as well... any input would be much appreciated!!! :fingers-crossed:
I'm sorry, just to clarify....you're using wifi calling while NOT connected to wifi?
when i'm using mobile data and not wifi, wifi calling is still running and every time i try and force close it or even when i terminated it with the task mgr in wolfscript, it keeps coming back...! :silly: :crying:
OffTheTimeline said:
when i'm using mobile data and not wifi, wifi calling is still running and every time i try and force close it or even when i terminated it with the task mgr in wolfscript, it keeps coming back...! :silly: :crying:
Click to expand...
Click to collapse
Don't mess with it if you use it. Cell standby has nothing to do with it. Use an app to determine who is eating up battery. Sometimes dirty flashing CM7 would help.
-- The noob says:
Believe you me... Apple suggested LG for Nexus 4
OffTheTimeline said:
when i'm using mobile data and not wifi, wifi calling is still running and every time i try and force close it or even when i terminated it with the task mgr in wolfscript, it keeps coming back...! :silly: :crying:
Click to expand...
Click to collapse
I never experienced that, I presume you are seeing it in the notification bar?
Mine would go off if Wi-Fi got weak or network dropped which was not unusual.
Sent from my Nexus 4 using xda app-developers app
@MANSA: to dirty flash would I just go into recovery and flash the same cm7 I'm running? And what about the kernel n wolfscript? Then can I use titanium backup to restore all apps n data?
@pmorrsn: when I'm in mobile data wifi calling is running in the bkgrnd and the icon is NOT in the notification bar...
Sent from my arrrrrgh.....
OffTheTimeline said:
@MANSA: to dirty flash would I just go into recovery and flash the same cm7 I'm running? And what about the kernel n wolfscript? Then can I use titanium backup to restore all apps n data?
@pmorrsn: when I'm in mobile data wifi calling is running in the bkgrnd and the icon is NOT in the notification bar...
Sent from my arrrrrgh.....
Click to expand...
Click to collapse
Dirty flash is as the name suggests... flash the ROM over existing installation without any wipe out formatting. Then apps stay as data is not wiped. If it doesn't work for you (bootloop or frozen) you can wipe cache and dalvik and see if it would help, but usually you don't have to.
Today I dirty flashed CM7 over Mokee IS.
-- The noob says:
The g2x works best if you chant "humba lumba humba" while standing on one leg!
That's kinda what I figured as when I first started flashing I pretty much dirty flashed about 3-4 times before I figured maybe its a good idea to actually wipe the cache lol... but I didn't know whether or not apps n data would still be there. Maybe I'll try that in the next couple days if this wifi calling BS persists. Thanks!
Sent from what I started thinking might be a decent device but then THIS started happening....