Greetings!
I wanted to share my strange problem and ask if anyboby has and idea on how to solve it.
Recently I have been having trouble with my Wi-Fi. When I leave the phone with Wi-Fi turned on and it falls asleep, or when I push the power button to make the phone fall asleep, Wi-Fi crashes... I can still use the phone, I can still charge it... The Wi-Fi indicator in the status bar is active too... Another thing is, If I leave the phone charging, Wi-Fi never crashes, I can leave it for throughout the night, I usually do that when I watch a Twitch stream and fall asleep, Wi-Fi works perfectly there... Decided to dig around a bit, I read a lot of threads, tried deleting /data/misc/wifi; tried freezing the logic board in the fridge; tried BAKING the logic board (it survived perfectly); tried switching stock roms, custom roms, radios even and a bunch of other things I can't recall now... Then, I decided to look at the logs and there were a lot of errors (log attached below), I looked at dmesg, there was NO problem powering on the Wi-Fi chip at all (as it is with other people having problems)... BUT, I thought of something funny! Why not install Firefox OS, I've never tried it and guess what... Wi-Fi was perfect there, the phone was able to fall asleep, Wi-Fi turns off when the phone falls asleep, then it turns back on perfectly! I don't want to be stuck with Firefox OS though, hence creating my first ever thread in XDA!
What do you guys think, is the logic board screwing around and having fun with me (hw failure) or is it something software-related? I am at a total loss...
Best regards to everybody!
Related
I just upgraded my Droid X to Liquid 3.2 (full SBF to 602, ota'd to 605, rooted, then flash to Liquid). I love the ROM, but it appears that my wifi and GPS are now broken. Wifi tries to turn on but then turns back off after a second or two; GPS won't even attempt to come on. Anyone know a fix for this?
Edit: I rebooted into recovery, wiped cache and Dalvik cache, and tried again. Now the GPS appears to be working, and the wifi stays on. However, when I try to connect to my home network, it drops off after a second or two (once it connects, it keeps scanning, and then it disconnects). I logged into my router and saw that my phone was briefly hitting it, but all the router log showed was the transfer of an IP address, nothing useful for troubleshooting. Does anyone know of a log file on the phone somewhere that might indicate why it keeps dropping off of my wireless network (yes, I've double checked the password, and yes, the wireless network is functional right now).
I'm out of guesses at this point, so I'm hoping someone else can help me out.
Hm. It gets curiouser and curiouser...
I've been tinkering throughout the day, and if there is any generalization I can make, it's that between wifi, GPS, and airplane mode, one of them (occasionally two, but never all three) will work at any given time, but every time I reboot a different combination starts working. Go figure.
Help anyone?
you got same problem i got. let me know what you figure out. I will post if i figure it out
I could not figure out wifi, so I went to vortex. I like the liquid but the wifi is a big problem and I did not have a lot of time to mess with it right now. I may by another droid x just to mess with things of this nature. If anyone comes up with wifi solution please post.
I've tried a few Sense 4.0 ROMs based on the One S and with each I've had problems where the phone will become unresponsive. I can't unlock it, even though it's not dead (if I plug into my computers, the screen will show the lockscreen, adb works, if the kernel has sweep2wake the buttons light up, etc). I installed catlog a few days ago and when the phone locked up I reviewed the logs and noticed it happening around the time there was lots of WiFi activity (specifically, switching between WiFi and the T-moble data networks).
I next disabled WiFi and the phone was fine for a day; I enabled WiFi, went for a walk, and sure enough had the display freeze up again. It's become so predictable that it's very easy for me to reproduce now; turn on WiFi, leave my office, walk to a nearby building which has a access point on the same WPA2/PSK network (I'm on a university with campus-wide WiFi), spend about two minutes there (the phone network is weak in this building, so it may or may not be able to pick up the T-Mobile network in that building) , leave the building and walk across the campus. Within two to four minutes of leaving the building, the problem occurs.
I don't have the posting history yet to make posts in the dev sections, so I'm want to see here whether others who've had their phone become unresponsive can confirm that they have something similar happening. If so, think back to where you were when you noticed the problem. If you have left the vicinity of a WAP, try retracing your steps with WiFI on and see if it happens. Also, try turning off WiFi and using for a while to see if the problem still occurs or resolves itself.
Hi all,
I suppose I'm looking for advice on diagnosing the source of my problem, more than asking you to identify the problem specifically.
I'm running CM-11 with the latest nightly. (There's not much point in my pulling up the specific version number, as this problem has been persistent throughout many Nightly and Stable deployments.)
After a reboot, my phone will behave normally for a while, then start behaving very badly. In the past two hours, I've lost 70% of my battery life, while my phone was sitting next to me idle. The phone is very warm to the touch. I have no idea what it's been thinking about.
(This is with LTE off, Wifi on and connected, and a very 3G strong signal because I have a Sprint Airave sitting ten feet away from me. I also have Bluetooth turned on and paired to a laptop, though it isn't doing anything at the moment.)
Often when I receive an incoming call, the phone will ring, but will have so much lag, that the call drops to voicemail before the PQ gets around to displaying the incoming call dialogue and Answer button.
Similarly, when I finish a call, and take the phone away from my head, the screen often won't wake up, thus making it impossible to hang up the call.
Chrome has been crashing. So have various android processes. Maps (Navigation) has been crashing intermittently, which is frustrating when I've missed a turn because I was driving and waiting to hear the next voice direction.
I'm also having trouble keeping my external SD card mounted. I'll occasionally open my podcasting app (DogCatcher) only to be told that it doesn't have any podcasts to play. When I open ES File Explorer, I find that my external storage is unavailable. There's no error indicating that it was unmounted; it's simply not there. Manually ejecting the card and re-inserting causes it to mount, and work fine for a few days, until I discover it missing again.
(Dogcatcher is set to only download episodes when connected to power and wifi.)
This is getting frustrating. (As all of my Android devices eventually become) and I need help figuring out what my phone is hung up on at any given time. Is there a reliable Task Manager/Resource Monitor style app that I should be using? Anything else I can do?
Sorry for the long post; I've been putting up with it for a while hoping that the next CM-11 release will somehow solve the problem.
Thanks for your help.
Have you tried a clean flash lately?
Have you checked which app is keeping your phone awake? WakeLockDetector is a great app to check to see what is killing your battery. Obviously the built-in battery graph tool can be useful as well, but doesn't necessarily show you what is the cause.
arrrghhh said:
Have you tried a clean flash lately?
Have you checked which app is keeping your phone awake? WakeLockDetector is a great app to check to see what is killing your battery. Obviously the built-in battery graph tool can be useful as well, but doesn't necessarily show you what is the cause.
Click to expand...
Click to collapse
It HAS been a while since I've done a clean flash. I'd be happy to try that, but I'd rather figure out if a specific app is causing the problem, so I know not to install it again. I hadn't heard about WakeLockDetector; that sounds like a great start. Thanks.
Hi All,
I got the Lollipop 5.1 OTA 2 days ago and installed it - everything went smooth and the phone working fine...
But I noticed that if I reboot my router (or turn it off / on again) the Wifi don't reconnect unless I turn on the screen (the second I turn on the screen the wifi connect normally).
I didn't have this issue with Lollipop 5.0.1
P.S.
I know that this is happening because I have a led on my router telling me if any of my Wifi devices is connected or not. And to make sure I also entered the router settings to see if my phone is connected or not.
Anyone noticed that issue with the new lollipop 5.1 ?
Cheers,
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
skorzo said:
I think that your problem is not switching off the router. The problem is when your phone goes to suspension (screen off) and then it drops the wifi off.
My Nexus 5 with 5.1 is doing the same
Click to expand...
Click to collapse
I've got some similar behaviour here, both when updated from 5.0, and with a fresh install from the factory images. When I arrive at a place with known WiFi, the phone only connects once I turned on the screen. After that, it stays connected until I move out of range and back again.
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
That being said, I have my wifi set to always stay connected, and I've seen it not connected when I turned the screen on, then connect a couple seconds later. So, there's that. Curious how often it does that.
Aerowinder said:
It's probably a matter of responsiveness/battery life. The more it polls for networks, the more battery it uses. It should connect, even with the screen off, within a few minutes.
Click to expand...
Click to collapse
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
dadrc said:
That's what I suspected. Sometimes, the waiting game works, but I've had my N5 lying on my desk – where it usually gets full WiFi bars – for about 40 minutes the other day, still it did not connect until I turned the screen on.
Edit: Just now, my phone disconnected from WiFi when the screen turned off, which leads me to believe that this is all caused by the WiFi sleep policy. Could it be that Google messed up something there?
Click to expand...
Click to collapse
My "research" has led me to believe this is the case.
Anything in terms of a workaround?
I came across those settings in the developer options (see screenshot), especially the "Always allow WiFi Roam Scans" looked promising. Been playing with them, but so far no luck.
Hi All,
exactly the same issues as yours guys are happening since I received the OTA 5.1 and installed it !
I Guess something messed up with this new update in regard of the wifi... as you mentioned.
If you come across a workaround or a confirmation from "Google" please share.
Cheers,
(With almost everyone nowadays having data ..it is difficult to notice such a behavior due to the fast wifi/data switching)
I have seen this happen as well. My battery graph will even show a missing area for WiFi indicating it turned itself on and off twice within a few hours and then stayed on after that.
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Tasker will help you
OsBuilder said:
Tasker will help you
Click to expand...
Click to collapse
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
dadrc said:
Could you please elaborate on that? I'm familiar with Tasker, but I can't think of a way of dealing with this, since I'm not sure what actually happens with the WiFi. The settings appear untouched.
Click to expand...
Click to collapse
I'm sorry, but my phone is now in the service center , and press that I do not remember specifically . The idea is that when you disable wifi, a time interval is forced to connect to a particular network . Look presence on the internet , here is full of instructions.
dadrc said:
Google just now released LMY47I, has anyone had a chance to see if that version fixes our problem? Once I'm off work (in about 8 hours), I'll give it a whirl and report back.
Click to expand...
Click to collapse
http://www.androidpolice.com/android_aosp_changelogs/android-5.1.0_r1-to-android-5.1.0_r3-AOSP-changelog.html
Almost all of the changes on these different builds are SIM related for specific carriers.
LMY47I was only released to LGD821 devices with SIM cards from Indian and Australian carriers
Same problem here. I am slowly losing faith in Google. Get the frickin basics going guys!!!
Back to my 5.0.1 build.
I've gone back to 5.0.1, too. Pity, except for this I was pretty happy with 5.1. Maybe 5.1.1 will actually be usable.
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
fabiastik said:
Do you think it can be related to Issue 163350? code.google.com/p/android/issues/detail?id=163350
I have just reported that, but I'm still trying to understand if it just happens to me or what.
Click to expand...
Click to collapse
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
MindLeader said:
I think the solution is "use vibrate mode on". Get your device to vibrate mod and test it.
I am waiting for your feedback.
Click to expand...
Click to collapse
This trick didn't work.
I have this proble too
Hello everyone!
I've recently bought my s6 after killing my old s5 with salt water on a Mediterranean trip (after taking it apart I found out the previous owner had the screen replaced, probably didn't do a very good job of putting the seals back together), and I was hoping that the notifications issue was gone on the s6. Here's what happens: when I get up in the morning I usually start my phone routine by reading the news, maybe watching some videos on YouTube, check on my games, and so on. The WiFi is on all the time when I'm at home. The first time I unlock the screen I only see the default email app notifications, 2 or 3 new emails. Once the screen is unlocked, other notifications show up, like the Gmail app, WhatsApp, tapatalk, and so on. It does this 80 to 90% of the time, maybe once or twice a month I see all my notifications the first time I press the power button to unlock my screen. Going on, half an hour to one hour after reading my newspapers feeds and watching videos, playing my games, there is a noticeable lag whenever I try opening a new Internet tab, or a new YouTube video, or anything that requires the Internet connection. After this lagginess starts, usually within a few minutes my phone behaves like it's not connected to the Internet anymore. The WiFi signal is strong, it stays connected to the router, but I can't use the Internet, it just shows that it's loading whatever it is I've asked it to load at the moment (YouTube video, internet tabs and so on) and remains like that until I disconnect from the WiFi and reconnect. I have to do that for the Internet connection to work again. I've noticed that while on mobile data it doesn't exhibit this issue as much, maybe just the occasional WhatsApp notifications halt, other than that it seems to be working ok.
Before you answer you must know that I'm not using the"do not disturb" mode at all, the router is brand new and it gets a reset every few days . I experience this issue both at my place and at my girlfriend's place, we have different router manufacturers.
I used to get the same problem with the old s5 as well. At first I thought the router was the issue, got a new one, the issue is still there. I also did the wipe cache partition, factory settings reset, different Google account,all with the same end result.
Sorry for the layman terms, I was trying to present the facts as I experience them in hope that the more technologicaly educated of you will know where or why the issue happens.
If you have any ideas or advice that I haven't tried, please share and thank you for reading.
Sent from my SM-G920F using Tapatalk