My rooted NC 1.1 has stopped reconnecting automatically to my wifi network after sleep. It had been working fine for a while so I am not sure what changed. To get it to reconnect I either need to toggle the wifi on/off or select the network using wifi settings. After that it is fine. If I just put it to sleep and turn it back on after a minute or so it connects fine. The problem occurs after several minutes (say 10) of sleep.
I have deleted all my network connections, rebooted and then connected to my network with no change. Again this had been working fine in its current state.
I then reimaged it to a known working 1.1 image using CWR but the wifi issue remains.
This is more nuisance then anything else but it sure is annoying.
Look forward to any suggestions since I dont know what else to try.
Bob Silver
NC 1.1 rooted 1.1ghz
Ipad 3g 4.2.1
Iphone 4 IOS 4.1 jailbroken
same problem here, sometimes it works but after waiting too long it doesn't reconnect. I think after being asleep so long it just fails to refresh/rescan. Kind of silly they dont have a rescan/refresh button in the wifi settings...
You can try going into Settings/Wireless/Wifi Settings/hit the menu again and go to Advanced, set the sleep option to Never. This helps but it still shuts off the wifi after being locked for a few minutes.
The fix I use is called "SoftLocker Free" in the market. This basically prevents it from sleeping, but still allows the screen to turn off. It draws more power from the battery since the wifi stays on, but I've had good luck with it.
Strange question, but do you have AT&T? I've seen a ton of folks with non-rooted nooks have this issue on the official Barnes and Noble forum, all with Uverse.
No i am not using att.
Thanks for the tips so far.
Bob
ZTE blade has a similar issue, there's a couple of workarounds.
1. Keep the device awake when screen is off (holds wifi connection but uses battery power)
2. Automatically toggle wifi when you turn the screen back on.
I've made an app that does (1.) when you leave wifi on and turn the screen off. (similar to softlocker, but it automatically grabs the lock when wifi is left on and has other features). Search for "Advanced wifi lock"
If you want (2.) grab "Blade wifi fix".
This seems to be common among Android devices judging by the sheer volume of WiFi fix and Wifi lock applications in the market. Now, we just have to figure out which one works better with NookColor. Free would be better of course
Mine does it as well - WiFi on after waking up. Can stay awake for 10 minutes not connecting, bus as soon as I'll go to wireless settings, I can see it obtaining IP immediately. I also noticed it goes away from time to time and comes back by itself.
I know that there are random reboot/freeze issues with this phone but I have noticed that my issue seems a bit different.
My phone goes into reboot loops and freezing only when I turn on the WiFi. I'm patiently waiting for the LG "update fix" but wanted some advice from the experts.
Im in afghanistan and only have until next week to return the phone. If it is a software issue then I dont mind waiting but if it is hardware then I dont want to get stuck with a 600.00 paperweight.
I know Im shooting in the dark but I really would appreciate some thoughts or advice.
BTW - I have had the same issues on custom ROM's and stock ROM's. I think I damn near flashed the phone with every possible thing i found on this board, haha.
well it seems like my issue is still isolated to wiFi. The phone has almost no reboots and very little freezes when WiFi is off. any ideas on if this is a possible hardware or software issue?
was it with every ROM you tried the same ?
It happens with every rom but I hate to get my hopes up but it seems to have start happening not as often. right now Im using this
[ROM][21/4-11]TK-ROM Vanilla + LG = true. v0.5.7 (Fr12)
couple of hours so far and it is better but not perfect.
Mine has just recently been randomly rebooting but was fine when I first got it. It never seems to reboot when I'm stationary only when I'm in the car or riding my bike. Twice it happened in the same location on the drive home from work which got me thinking it could be location related. The gps wasn't active at the time so I tried turning off wifi/cell tower location in the options. I managed a two hour bike ride with no reboots today whilst using gps tracking and listening to music. Yesterday the phone wouldn't go more than 10 minutes without rebooting.
Could it be bad location data in some mobile phone masts are making the phone crash due to a bug in the software?
Sent from my LG-P990 using XDA App
Best phone i've owned build wise but i'm getting some strange problems that only restarting the phone sorts out.
I completely lose my signal and even turning airplane mode on and off, When you drag down i usually get EE as im on orange UK but it will say 0000.
Also i've had it when its constantly searching for gps even though i have no apps open or anything that would require GPS in the running apps tab.
The losing the signal is more annoying as i went a full day without realising so when i restarted my phone ide missed out on important texts and phone calls.
Other niggles is that it gets bloody hot when playing games and its got sense but i can live with the latter lol
But still the best phone i've owned.
Anyone else having any of these issues?
Haven't had any GPS problems, but I generally have it switched off unless I'm planning on using maps. The signal thing is weird - I haven't experienced it on the One myself but I have had similar problems in the past on other phones with Orange/EE, almost like the phone gets confused when it has no signal for a long time (which always happens at my parents' house when I'm visiting). Usually took a hard reset to sort out on my Desire HD, but not sure if it's the same as what you're talking about.
The one thing that does worry me is how hot the phone gets playing games, have to admit it's put me off a bit and I've been finding I've been playing games more on my iPad as a result. I prefer this new version of Sense to stock Android though hehe so no complaints about that!
Also Google now *****es about location services switched off yet when i go into it its on, this might be why my GPS seems to be always on.
UPDATE:
Seems im not the only one having GPS issues and it seems google now is the culprit: http://forums.androidcentral.com/an...now-keeps-saying-my-location-service-off.html
sorry for linking to another forum.
I am having really bad issues with GPS too. Sometimes it takes ages to get a signal and when it does it looses it again just when I'm getting to a difficult area to navigate....
Likewise I'm on T-Mobile (EE) uk and I too loose the signal where I have to reboot the phone. I just think its T-Mobile being crap in my area. Mostly it's ok though.
M.
After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.
Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.
Maybe try a new sim card,only thing I can't think of
holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.
Attached a screen with battery info, from testing it's pretty accurate.
After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.
Try flashing a different modem?
dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.
Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.
Yes, this time old issue still exists for me, and it makes it where I cannot trust the phone. I've wanted to use my Nexus 6 as a daily carry, but have to use my LG G3 instead.
The N6 completely drops cellular signal after the screen turns off and goes into deep sleep. After waking the phone, it requires a reboot 90% of the time to get it to reconnect to cellular service. Rare occasions I can leave it for a few minutes, toggle airplane, and get it to reconnect, but by then a reboot is faster. Obviously, a phone that drops cell service when the screen is off is no good.
The fun thing is not ONLY is it dropping cell service, it maxes out the cell radio searching. If I don't notice it dropped service, the phone gets hot and the battery dies very quickly, this also happens in AIRPLANE MODE. Yes, even when airplane mode is on, I turn the screen off, cell service "dies" and the radio kicks on and searches for signal, gets hot, kills battery, all while in airplane mode. The battery information page shows blank for the signal meter while in airplane mode screen on, but turns red and shows indication the radio comes on when the screen is off.
The only "solution" I have is to constantly play music, or have it plugged in. Currently I have an 8 hour mp3 of pure silence playing on repeat. Naturally this keeps the phone locked at 300Mhz while the screen is off and never sleeps, but the cellular radio works as normal, stays cool, and battery drain is minimal, never disconnects. The problem is: doing anything that causes said silence to pause and not noticing/remembering. Watching a video, casting something, rebooting, etc. Also the phone never sleeping is generally not good, but I can't trust the media player not to sometimes stutter and then the signal drops out. You see my trust issues. While the phone is plugged in, which also prevents deep sleep, the phone is fine as well.
Oddly enough SOMETIMES the phone does as it should. I might check the phone and notice music is *not* playing, but the signal is fine, and the device has been in deep sleep with no problems. I've yet to isolate what causes it to stabilize, but after a reboot, it's back to its old ways.
Things I've tried:
Flashed ALL the official images. (Problem exists across them all.)
Tried a few custom roms
apps that hold a wakelock. (trying to keep it from sleeping, which worked, but signal still disappeared)
Removing, downgrading, upgrading, etc Google Connectivity Services.
Different basebands
Different carriers.
Other things I can't think of now.
Current Setup:
Pure Nexus (latest)
System mode root + Xposed system mode
Bootloader: moto-apq8084-71-21
Baseband: D4.01-9625-05.39+FSG-9625-02.113
Attached a logcat of it dropping signal after screen off, and luckily caught it regaining signal as well in the same logcat.
EDIT: Alright, can I get a moderator to move this threat to Q&A. I posted in Q&A and it appeared in General... Guess that's what I get for having multiple tabs open.
sim issue
yes, this seems to be issue with N6.. (issue is somewhat related to SIM card). Can you try without SIM card inserted?
Just sell the phone. Dont waste nerves trying to devug it.
I had similar issues, but switching to 2G helped.
To be honest, these smartphone issues have been things i have experienced with all brands.
From random reboots with samsung, cellular issues with LG to phantom clicks with sony. Not acceptable given the price.
So far, every smartphone has caused issues.
shadowcore said:
Just sell the phone. Dont waste nerves trying to devug it.
I had similar issues, but switching to 2G helped.
To be honest, these smartphone issues have been things i have experienced with all brands.
From random reboots with samsung, cellular issues with LG to phantom clicks with sony. Not acceptable given the price.
So far, every smartphone has caused issues.
Click to expand...
Click to collapse
I'm not the type of person to sell something with a known issue, that's as bad as selling a car that you know the transmission is about to go out. Since it's not my main phone, I don't let it really get my nerves, instead I use it as a brain teaser. Finding new and interesting ways to get it to keep working, but at the same time I would like to find an actual fix. In case I ever want to... y'know... sell it. I'm not going to sell a defective product. I have the experience and knowledge to actually use it, and on Fi it's a good backup. The wifi doesn't cut out so it still works if I'm around wifi.
Also, replying with "Meh just sell it" is a very unprofessional and indecent response on a large forum dedicated to helping people and making their lives with their phones easier, and learning new things along the way.
Skreelink said:
Also, replying with "Meh just sell it" is a very unprofessional and indecent response on a large forum dedicated to helping people and making their lives with their phones easier, and learning new things along the way.
Click to expand...
Click to collapse
I never said that you shouldnt disclose that the phone is defective.
I assume that goes without saying.
Secondly, my experience has been that such issues are unfixable.
When i had an LG phone with issues, the solution was to sell it as scrap/defective device.
From the looks of it, your issues are unique. I also have issues with connectivity and the solution was to switch to 2G.
However, it only happens with one network operator.
Also, this is a forum, you asked for advice, i gave it to you. You dont have to like it.
Oddly enough without any system changes or anything and with how long the problem has stood... It seems to be acting correctly now. Doing some tests with reboots, etc and it seems to be going to sleep fine and not losing signal. Will continue to monitor this oddness and if I figure anything out, I'll update this thread for any of those who might still have this issue.