Related
Hello,
I have a O2 Xda Neo that works nice, does the Activesync with no problems, etc. But for unknown reasons it changes by itself the time zone in time settings to +1 hours from mine, and it's really anoying having to change it back, and making sure it's all set when i go to sleep so that the alarm won't wake me up one hour earlier. I suspected that the activesync is doing that so i unchecked the "sync date and time" option on all the PC i am syncing and i also checked that on those PC the time zone is correct. I also istalled some "daylight saving" patch on it but the problem remained the same. Weird is that it changes even with the device not connected to the PC (WiFi off, Bluetooth off, USB unplugged). Any ideea why it does this? Any solution?
HI, i had no problem with Wifi. Since last time I got to the hostel and have a weak access point I have a bug with Wifi : when I activate it, it says "connecting... ". But nothing happens, it doesn't list access point around me too.
I found a way to make it work: I uncheck Wifi, check airplane mode then check wifi again. It works but I have to do it every each boot or wifi deactivation..
Is there a parameters or cache file stocking the weak ap I was trying to connect when the bug appears at first?
Thank you
Problem not solved but changer: now it work but wifi is never activated at startup.. can't force it to auto activate. Strange...
Anyone else have this problem? I just started having it, first on Phiremod 6 and now just updated to 6.3 hoping for a fix, but no dice.
I have sent back 2 nooks to BN for exchange because of this issue. I didn't know doing the airplane mode thing would temporarily fix the issue. I even did the 8 hard reset and restore and the nook would get stuck on finding wifi window - turning on wifi but nothing would happen. My nook was manualnooted 1.2. Strange?
I'm on nightly-87, Dal's 1.2GHz OC Kernel 5/23, and I'm experiencing something very similar. I went from 7.0.2 to N87 without a hitch, but I immediately started to see the WiFi icon go gray and lose it's connection. I was forced to restart WiFi as a remedy. As of today I'm getting something closer to what you're talking about; when WiFi turns on, the nook will infinity cycle through: disconnected->connecting->disconnecting->scanning. I've wiped Cache, Delvik-cache many times to no avail. Also tried re-flashing N87 and the OC Kernel, which did not work. I'm still not able to connect to my home network(netgear, WPA). But, after enabling/disabling airplane mode, I was able to connect to my LG vortex and obtain the interbuttz.
The last time I did a fresh install was around N20 something. As far as possible causes to this erratic and ethereal bug, my money is on certain update paths for both the OS and Kernel having different remnants. Example: with 87 different experimental OS installs and, to a lesser degree, the three different stable OS installs. There are technically !90 different upgrade paths. Compounded by being paralleled by kernel installs, but I believe when a kernel is updated the former is completely replaced instead of merged. I'm not calling out the Dev's, it would be nearly impossible to foresee and head-off all of the permutations of merging 87+ releases.
I'm no expert, just my two-cents. I'm not really concerned about this as a long term bug. There are fine people hard at work, and unfortunately have far more pressing issues to contend with. It's a sad reality that community driven projects, notably the nook Color, rarely reach maturity or complete/efficient hardware-software integration before the allure and newness of a product wares off.
As a consumer of .rockbox, a Linux based OS for G5.5 ipods and below, Of which I've been using for years and years. And, I would say it's just now becoming 'perfect', even with it's lack of support for many peripheral devices. I'm long term with my gadgets.
I'm rambling now.
Hope this helps to narrow down symptoms and possible causes.
It seems that my problem is a known issue of cm7 (when you click airplane it stay on forever but the checkbox remains unchecked). Try a tool from market that shown me the airplane mode and unchecked it from here. Since I didn't reboot from that test I don't know if it's solved for now.
my NC on CM7 just stopped connecting too
I turned on my NC this morning and my WiFi no longer works either.
All of my hotspots say 'not in range'.
I tried all of the tools I have to turn off 'airplane' mode (just in case it was on)
but, nothing seems to get me 'out of the mode.
What can I try next?
Wifi miraculously auto-fixed itself, and then broke itself again
fulko said:
I turned on my NC this morning and my WiFi no longer works either.
All of my hotspots say 'not in range'.
I tried all of the tools I have to turn off 'airplane' mode (just in case it was on)
but, nothing seems to get me 'out of the mode.
What can I try next?
Click to expand...
Click to collapse
While researching potential solutions... CM7 auto-fixed itself after about 15 minutes.
I didn't touch it.
All of a sudden I heard the Gmail tool beep at me with new messages and the market with a few apps updates that were available.
Now it seems to be working fine.
I spoke too soon, I just powered off and on again to see if the problem was fixed
permanently, and its not... its back to the 'not working' state.
(I hate when that happens, because I don't know what caused it, and I don't know what fixed it!)
This happened (WiFi not hearing any APs) to me a few times with nightly 87, but hasn't happened since I upgraded to n94.
fulko said:
While researching potential solutions... CM7 auto-fixed itself after about 15 minutes.
I didn't touch it.
All of a sudden I heard the Gmail tool beep at me with new messages and the market with a few apps updates that were available.
Now it seems to be working fine.
I spoke too soon, I just powered off and on again to see if the problem was fixed
permanently, and its not... its back to the 'not working' state.
(I hate when that happens, because I don't know what caused it, and I don't know what fixed it!)
Click to expand...
Click to collapse
SAME! Bump.
Same issue.....latest nightly on VG SDcard solution. Never had a problem until recently. Was runnning 7.03(flawlessly) then suddenly started experiencing the issue, flashed the latest nightly (113)...worked for a bit, rebooted and now nada..... just sits at connecting..... then goes to disconnected. Cycles every couple of minutes.....
Any suggestions on what to look at?
**** Note ; WIFI works fine when I boot to EMMC (Nook 1.2) . So I do not believe this to be a hardware problem.
I was just looking for this issue also.
I was doing great with nightlies and the OC 6/18 kernal, this morning I updated to the Nightly 114, and I received no wifi connection on booting up.
So I did all the normal things (1. turn on/off the airplane mode - No change, 2. fixed permissions - no change, 3. restarted multiple time (aft all the prior changes) - no change) Ok I thought, I will go back to my previous nights backup (Nightly 113). But I still get no wifi. The widget says trying to connect, but none of my networks are showing up within range. I run wifi analyzer and I see NO networks (normally I would see about 5 to 7 of them).
So I begin stepping back, I reinstall the Nightly 113, with No OC, and while the wifi is off on bootup, once I 'turn it on' now I see my networks.
I'm cooking with gas now, so I install the OC 6/18 - No Wifi
So I install the OC 6/13 - Still no Wifi
Both times, the Nook boots up with the wifi 'off' so I turn it on, but no connection or sensitivity.
I again reflash the Nightly 113 only and while it again boots up with wifi 'off', I am able to turn it on and it actually sees my networks.
So strange, I am stuck without my OC kernal, but as least the nook works again.
Does anyone have an idea why this is happening to people?
Thanks
onclebob said:
It seems that my problem is a known issue of cm7 (when you click airplane it stay on forever but the checkbox remains unchecked). Try a tool from market that shown me the airplane mode and unchecked it from here. Since I didn't reboot from that test I don't know if it's solved for now.
Click to expand...
Click to collapse
The issue in the OP isn't related to the one you're talking about. Try deleting one or more of your remembered wifi access points with wifi on. Let it rescan and, if it's not some other issue, it should find your access points and connect.
Suffering this same issue as well on my Nook Color. I believe the problem lies under /data, and here's why. First, I made a backup of /data, and then wiped everything:
* I restored my device to factory 1.2: Wifi works
* I flashed CM7 nightly 113: Wifi works
* I flashed dalingrin's OC'd 6/18 kernel: Wifi works
* I restored /data from my backup: Wifi is stuck at "Connecting..."
I thought it might have something to do with the settings.db file under /data/data/com.android.providers.settings/databases/, but when I deleted that file and rebooted, it made no difference with the Wifi problem.
Something under /data might have a problem with the latest CM7 builds, but I couldn't say what exactly. I'm not an expert at this stuff, so I can only share what I've observed and tried for myself.
Hi. I have the same problems with Wifi since this morning. Is there any other solution then turning on and off airplane mode? thx
Formatted /system and /cache, and wiped the Dalvick cache, then flashed only CM7 nightly 143.
The problem still exists. Wifi is stuck at "Connecting..." Has anyone found a solution to this? It's obviously something to do with a setting/file under /data, because if I format /data, Wifi works like normal. But when I restore my backed up /data, Wifi is stuck at "Connecting..."
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
You can also watch if airplane mode is really off using Android assistant:
https://market.android.com/details?id=com.advancedprocessmanager&feature=search_result
it helped me with this problem
flansuse said:
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
Click to expand...
Click to collapse
That worked for me, thanks a ton!
flansuse said:
I think I found a solution. This worked for me, so I hope it works for others.
Shortly after writing my previous post above, I decided to play around with my NookColor, to see if I could get the Wifi to work normally again. Here's what I did, which fixed the "stuck at connecting" problem for me:
1) Go to Settings > Wireless & networks > Wi-Fi settings
2) Check to enable Wi-Fi, if it's not already enabled
3) Click every wireless network in your list and choose "Forget"
4) Make sure every wireless network is forgotten
5) Check to disable Wi-Fi
6) Check to re-enable Wi-Fi
Instead of "Connecting..." I now see "Scanning" and it picks up the routers around me! I selected my router, and it connected! I am now able to browse the web, update my apps, and all seems to be working normally now!
Click to expand...
Click to collapse
Man, you really had my hopes up with this one. You're the first person I've seen say every remembered network needs to be forgotten. But I followed your steps exactly, and my NC still will not connect. It sees all wireless networks available. It knows which ones are open and which ones are secured. I can go so far as to enter the password and click Connect. It says "Obtaining IP address from...", then quickly flashes "Unsuccessful", then "Scanning...", then loops indefinitely. I even took your steps one step further and rebooted before turning WiFi back on. Still doesn't work.
This is the fourth time this has happened to me. And every time, the only way I've been able to fix it is to completely reinstall CM7. That's not a fix, that's a wrecking ball. I'm pretty desperate to find a fix because my NookColor has become a joke, almost unusable. Right when I get it to the point of enjoying it and getting it set up just the way I want it, this happens. And the damn thing is useless without WiFi.
I also installed the latest nightly build, which was from last night. Nothing.
As I write this, my Nexus 7, Samsung Galaxy Note 2, Apple IPod Touch and other WiFi connected devices in my house are all showing 1145
My nexus 10 is showing 1140.
All these devices have "automatic date time" in Settings and are connected to the same WiFi network.
I have also set the time manually but it will still lose time over a few hours.
This isn't a big issue, just an annoyance really. Has anyone else noticed this? Any ideas for a solution?
Mike
Sent from my Nexus 10 using xda premium
I can confirm that I'm having the same issue, it was off by over 10 minutes using the time servers after the first night and right now is slow by around 8 after setting it manually yesterday morning. No idea as to a solution yet.
My Nexus 10 32gb is keeping perfect time.
I have the 32gb Nexus 10. I installed the OTA, I'm currently on JOP40C.
Sent from my Nexus 10 using xda premium
I have the same problem. It is now 16:52 in Germany, but my Nexus shows 16:47. I wonder what could cause this strange behaviour
10 minutes behind. 32gb USB in usa
I dont have this problem. maybe in date & Time settings, tick "automatic data&time" will solve it?
Same problem here, ticking "automatic data&time" on and off does not solve it. In fact setting the correct time manually and ticking automatic back on "corrects" the time to the wrong time instantly.
A reboot helps most of the time, but sooner or later it jumps back to a wrong time (usually 3-10 minutes off).
My Nexus 7 on 4.2 does not show this bug.
Could be a wonky timeserver (unlikely?) or a bug that only manifests on the N10. Set the time manually for now.
Valynor said:
Same problem here, ticking "automatic data&time" on and off does not solve it. In fact setting the correct time manually and ticking automatic back on "corrects" the time to the wrong time instantly.
A reboot helps most of the time, but sooner or later it jumps back to a wrong time (usually 3-10 minutes off).
My Nexus 7 on 4.2 does not show this bug.
Could be a wonky timeserver (unlikely?) or a bug that only manifests on the N10. Set the time manually for now.
Click to expand...
Click to collapse
This is strange. I got my nexus on friday and never had to set up the time manually. The time is correct al the time. Will keep watching this.
Submitted a bug report, please star and comment so Google will fix this quickly:
http://code.google.com/p/android/issues/detail?id=39951&colspec=ID Type Status Owner Summary Stars
I threw my info up there. I called Google and they're sending me a replacement.
Added: It seems that when you reboot it forces a time sync. That sync is OK, but the hardware is keeping time slower than it should I found most of the time it was 5 minutes per hour off, but sometimes it's fine.
Every time I rebooted with a Wi-Fi connection it was OK, but slowly drifted.
The Google rep I spoke with confirmed that I had done a factory reset and then did a replacement.
I am having the same problem with all of my Android devices, but not that badly. However, time starts to drift around 10-30 seconds over time.
I tend to blame Android for this behaviour, because it synchronizes time not often enough, and depending on the accuracy og the integrated clock, it starts to drift. Does anyone know how often Android actually sets the correct time? And why does it not always use the GPS clock as a reference, if GPS is available?
The worst thing about it is that you cannot use NTP servers to automatically set the time without rooting a device. I have an app installed called clock sync, which measures time and gives a hint if it differes by a user defined threshold from the current time, but if yu want to make that app sync your clock, you have to root your device
Time does not drift on my device. I have set it to manual ~12 hours ago and it's accurate within 1 second.
The automatic time&date update via network makes it jump to the incorrect time, so this is not a matter of precision but clearly a different kind of (software) bug.
I just checked mine again...still locked in on the correct time...Automatic settings.
My Nexus is updated, unlocked bootloader, flashed recovery (CWM) and rooted. I got the tablet Friday night, played with it for a while after setting it up but never checked the time to see if it was off.
I unlocked/flashed/rooted it Saturday and then saw this post on time drift/errors. Since Saturday the tablet has been on and time has been correct.
Maybe the system is trying to compensate the lack of december, as it would reach january too early
http://www.androidcentral.com/santa-s-going-be-mad-google-forgot-about-december
As Valynor said, automatic time&date update via network making it jump to the incorrect time makes it seem like a software problem.
There is a free app in the market called ClockSync, works great. Personally I'm having no time issues with mine though.
clocksync requires root to actually sync so it works for some but not everyone. I'd personally rather not be forced to use the app for something the tablet should be doing anyway.
The time bug is even weirder:
-went to bed with time set to manual, Nexus 10 was running for about 12 hours, time was accurate within the second
-9 hours later: switched N10 on (from standby), time was 2 minutes off
-rebooted (with automatic time&date still set to OFF!): time is correct again (1 second off) after the reboot
Conclusion: something is messing with the display of the system time, alas the internal clock seems to keep the correct time nevertheless.
Great news! Your replacement order on Google Play has shipped. Track the status of your package UPS #********************9. Note that it may take 24 hours for your tracking number to return any information.
potatoboyjs said:
Great news! Your replacement order on Google Play has shipped. Track the status of your package UPS #********************9. Note that it may take 24 hours for your tracking number to return any information.
Click to expand...
Click to collapse
Good for you, but I don't think it's likely that the whole time bug thing is a hardware issue.
Hello
I have my G2 for 3 days now, and I keep having the same weird problem every morning when I turn it on: the clock "looses" one day, and either advances or loses a few minutes.
Yesterday I checked as the hour went past 00h and the date changed to day 19, thursday ('I'm on GMT 00). The phone and computer had the same time.
I left my phone off during the night, and today when I turned it on I found it at 10.00 o'clock (8 minutes in advance of my computer). It also switched back to the 18th, wednesday. The weather/time app still detects it was last updated on the 19th.
I have automatic date-time-timezone switched off. If I turn it on, it will sync with the Internet and correct the hour, but that does not fix the problem.
Any ideas on what's happening? Any suggestions?
I'm on Android 4.2.2
Kernel 3.4.0
Software D80210b-EUR-XX
Yesterday (after midnight) I switched the phone off for more than 10 minutes, switched back on: all ok
Restarted the phone: was ok - up till 3 am the date/time was correct.
Turn it off, woke up this morning, turned it on: 5 minutes delayed, date went back to the 19th.
It seems what is happening is not really a lost of time. Today as I turned the phone on, it was showing 10:24, 20th (yesterday). This was over half an hour ahead of correct time. This happened after I had the phone off for 3 hours, so it's not a delay that increases as proportional to the time the phone is off. It must have something to do with some date/time on the settings, that override actual date/time.
I think this is like a "return to last settings", in this case, I believe this was the date/time set when I turned the phone on yesterday morning.
I already went by all apps I think could be related, but I can find no relevant option to prevent this.
That is indeed strange, maybe someone else around here can help you with that.
I don't think many people turn their phones off during the night.
Hi i think this is the same for all g2, my phone does the same thing once you turn it off the device is literally off. I am sure if you check the battery time it will show only from the time you rebooted it and not from last full charge. At the beginning i reported this issue but didn't get any reply but with further investigation i reached to the conclusion it wasn't an issue with device.
Any way regarding date time issue, you can simply make sure its automatically synchronized with network that way no matter whether its on or off it will be correct.
Sent from my LG-D802 using xda app-developers app
its probably cmos battery if phone has one, try warrantee
Thank you for your input
I've done a few more tests. I've flashed a different firmware, but it still does the same. This originally came with 10B-SEA, and I flashed it to 10B-EUR (UK open). Now it's back to SEA.
I've contacted LG about this, and they told me it's under analysis.
The phone will not loose date and time if it's powered off for one hour. After two hours it will happen and it will go back to the last time the phone was powered on and the clock was set.
I've been keeping it synced with the network time, and that way it works fine, but that's not a permanent fix. Yesterday I unchecked the automatic time, left it powered off for two hours, and it went back to monday.
I've read this post http://forum.xda-developers.com/showthread.php?t=2580974, and it seems to be related.
Same problem with date and time
I do have the same problem. My phone model is D802 (international variant). But as far as I remember, this issue did not start from the day one. I purchased the phone some 2 months back. It was fine on the JB. It remained fine even after the KitKat update. But one day, my phone did show some weird problems. Serious lag coupled with overheating and battery drain. I did a factory reset because the phone was hardly usable at that point. After the reset, lag + overheat and battery issue was gone, but I remember that after that incident, it started this weird date/time sync issue. There is something which I wish to highlight by the attached screenshot. There is always a broken curve of battery usage whenever the date/time reverts which happens whenever you keep the phone switched off for a few hours. I am not a technical person, but this might be related to the battery.
Anyone have any luck with this? The main problem that this is causing is that when emails, texts, messages come in whilst the clock is incorrect (before it updates), these items get put out of sync with when they did actually arrive.
I contacted LG and they said...
If you have both options ticked, I would advise you to try and perform a hard factory reset. Before doing the reset, please ensure that you back up all of your files as all data will be lost during the reset. The details of the reset are as follows:
Turn the phone off
Press and hold the power key and the volume down key together
Release the power key only when the LG logo appears and immediately press and hold it again
Release both keys when the hard factory screen shows up
Select yes (use the power key to select yes)
Select yes again
This will then take you through the set up of the phone, and the issue should be resolved. I hope this helps you.
I haven't yet tried this, as from what I've read elsewhere, this wont fix it, plus it is a bit of a hassle to copy everything off and then reset, then et everything back on the way it was and all apps, etc.
Hi,
I've the same problem.
Can you tell me if Hard factory reset or LG support had resolved this issue?
I'm currently using ClockSync app that sync time every 3h and at boot.
The clock seems not to be very accurate : 1.139s of local offset in 2h...
I've tested the Clock_offset_fix. I'll update this post when I'll be sure that this solution is ok for me or not...
pbenoit said:
Hi,
I've the same problem.
Can you tell me if Hard factory reset or LG support had resolved this issue?
I'm currently using ClockSync app that sync time every 3h and at boot.
The clock seems not to be very accurate : 1.139s of local offset in 2h...
I've tested the Clock_offset_fix. I'll update this post when I'll be sure that this solution is ok for me or not...
Click to expand...
Click to collapse
This is not an issue per say. It's just that the device is built this way..... So as far as I know there is no fix to this. Except you can have accurate date and time if you have a sim card in the device and auto date&tme option is ticked in settings. You see the device doesn't have a pc like cmos rom to store basic info like date and time. So when u turn off the device that info isn't maintained and becomes corrupted after some time but it is corrected when synchronized with the cell network provider at boot.
Hi, I have the same problem. is there any way to solve this problem? I have stock lolipop.
გიორგი said:
Hi, I have the same problem. is there any way to solve this problem? I have stock lolipop.
Click to expand...
Click to collapse
Same problem for me, date and time are wrong for some seconds after boot.
Than it switch correctly to the current date and time.
Make sure you have setting > date and time > automatic sync for all options...
On my phone it start wrong than it correct itself if internet is enabled.
The problem ia when mobile data is OFF. :'(
4Freedom said:
Same problem for me, date and time are wrong for some seconds after boot.
Than it switch correctly to the current date and time.
Make sure you have setting > date and time > automatic sync for all options...
On my phone it start wrong than it correct itself if internet is enabled.
The problem ia when mobile data is OFF. :'(
Click to expand...
Click to collapse
Yes, I have automatic sync on, but the problem is when I can't access internet. What if I install Cyanogenmod?
გიორგი said:
Yes, I have automatic sync on, but the problem is when I can't access internet. What if I install Cyanogenmod?
Click to expand...
Click to collapse
I am on Temasek now, same problem.
I'll try Cyanogen CM13 M1 this night or tomorrow.
Hoping
I am having some problems after an update today. Build number is NRD90M.G935FXXU1DQE7.
The first thing I noticed is that it no longer connects to my WPA Enterprise (EAP-TLS) network. I was told the log on the RADIUS server is saying the client rejected the server's certificate. When I manually click on the network to force it to connect, the "Settings UI" would sometimes crash.
I then rebooted the phone and each time it would reboot itself seconds after unlocking, but just before doing so, you notice the top bar does not show up or stop rendering half way so I think some part of the system is crashing and causes the reboot.
I then then disabled wifi before unlocking which stopped the auto-reboot. (You have to click on the "Wifi" label in the drop down to get to the details page which shows you a wifi toggle switch. Click that switch and then unlock.) If I leave Wifi on and reboot then the boot loop returns so it's pretty clear it's Wifi-related.
I then "forgot" the WPA Enterprise network and subsequently the phone no longer crashes after reboot. Unfortunately, it still cannot connect to that network.
Another thing I notice with this update is constant CPU usage. If you enable "show CPU usage" in developer options, you notice the load average is constantly >6. This is very high for a mobile device and indicates something is probably stuck in a loop.
Is anyone else having similar issues?
Do a factory reset and set up as new phone do not restore our use backup settiings do install everything fresh this is what fixed multiple issues i had
Sent from my SAMSUNG-SM-G935A using Tapatalk