This is one I havent encountered before but apologies if its been reported already. I couldnt find an obvious thread.
I have noticed recently that my Kaiser is not keeping time - quite dramatically so!
When I turn my device on from standby, the clock is often 20, 30 mins or even hours behind.
I have tweaked the hell out of it recently so I am quite sure it is related to something ive done as it hasnt happened on previous builds.
I am using synchrotime almost everytime i turn it on just to make sure the clock is right (hope this doesnt clock up too much data :-( ).
Anyway just wondered if anyone else had come across this?
Try turning the auto time setting in the phone settings to OFF, early on we found this to cause random time problems as well as causing active sync to run all the time.
Thanks. I'll give it a go.
Mine did that last night - 40 minutes slow. Never had that problem since i first got it a couple of months ago. Once it got coverage again, it syn'd back up.
Did that fix your issue?
I've got another interesting one. My clocks are right, but my text-messages show as an hour ahead (received one at 3pm PST and it shows as 4pm PST in the list). I do have the 2007DST patch from Microsoft and everything else is configured right. Is there another setting somewhere for txt-msgs?
this happens for me too. i dont no what is causing the delay. when i have my phone on device lock, whatever time it was when i locked it, it stays like that until i unlock. i noticed it recently, almost missed an appointment because of it!
tried turning off that auto time thing that dont have any effect.
worked perfectly thanks
After updating to FRF91, I notice two things.
1) My phone froze at least 3 times since the update when I tried to make a phone call. I had to remove the battery and restart it.
2) My calls are now less clear even with my blue-tooth. When I call someone, they and I will hear static. Sometimes the static is really bad. (no, I am not holding it the wrong way )
Anyone have similar issues?
My Nexus One is NOT rooted.
stock 2.1 to FRF50(manual install)->FRF83(manual install)->FRF91(OTA install)
No issues here. Clean install.
I would agree it seems buggy to me also; it could be the manual update path of updating, but im def getting some wonkyness.
When im on edge at my house, it always seems like WIFI is on demand and not connected (This differs from what my phone used to do and i also have wifi to never sleep); so when i try to access something intially i get a network error then the Wifi connects; then i connect even though im on edge which used to connect albeit slow.
A slight jerkiness when I longpress to remove widgets; don't remember that one previously.
Very erratic battery life; seems to be due to network switching from 3g to edge to wifi; can't really confirm that though; not real rogue apps on my device that are running, but who knows.
Car dock has been giving some force close issues from time to time which didn't really occur previously.
FRF83 more stable
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Falen said:
I was thinking of trying to go back to FRF83 as that seems more stable.
I will first try to do a factory reset and see what happens after that.
Click to expand...
Click to collapse
let me know how that works out; I may do the same. Maybe go back and ota update.
I applied the full FRF85B when I did mine, and wiped cache / format user data from the boot loader. That cleared up issues.
gmail stopped working properly for me.
I have had some issues with my phone freezing up too but my trackball would still flash when i got alerts. I think it might be related to trackball alert because now that I have uninstalled it i haven't gotten any freezes.
I did the factory reset and I no longer have any problems. I am still waiting to see if my dialing still freezes randomly though.
Sent from my Nexus One using XDA App
I'm still on frf83 and found that flashing the frf91 gapps has somewhat reduced the freezes/reboots.
My XDA app freezes for a couple of seconds before it responds. Is this app up to date for frf91?
Sent from my Nexus One using XDA App
1. Going into Gmail it takes forever to display emails (usually shows the "loading icon" for 10-20 seconds) as if it is only then connecting to the server and downloading new/old emails.
2. Caller ID still does not keep settings when rebooting.
3. Task Managers don't actually seem to kill tasks anymore. Have tried multiple with settings to auto-kill 10 minutes after the screen goes off ... 5 hours later the programs are still running. Obviously just KILLS battery life.
nexusdue said:
Obviously just KILLS battery life.
Click to expand...
Click to collapse
Yeah, obviously, you're using auto-kill, it probably tries over and over and over when they don't actually close.
Stop using auto-kill. Even if it worked you will get less battery life by killing tasks. Read up about it. Only reason to EVER kill something is if it isn't acting nicely and has a bug that keeps using CPU or keeps the phone awake.
Factory Reset works almost all the time
If you got problems after update you should allways wipe (factory reset)
Hey guys, my nookcolor has been randomly rebooting since i rooted it. Never while i was using it, i just sometimes hear the bootup sound, and look to find that my book is now on.
Im just concerned this will affect my battery, and i also don't want it rebooting while im using it.
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Divine_Madcat said:
I noticed it doing this one time, but right after i powered it off. In use, it has never rebooted on me (yet)..
This is why we so desperately need a custom ROM. Remove the B&N bloat, and start with a clean 2.2 (or even 2.3 now) base, and really open her up..
Click to expand...
Click to collapse
I still want to use the B&N stuff. Any rom that emits them, I will not be installing.
I think it likely that there are NC users in both camps-
Those who want the B&N stuff and those who don't.
I am one of those who don't; the Nook for Android software does better for reading ePub, imo and I am rarely near a B&N store.
Right now we have root and Market plus B&N and I would guess (could easily be wrong) that the first custom roms will be pure Android with no B&N.
We will probably end up with an option to set while flashing: retain B&N customizations or straight Android.
I base this guess on what I have seen in the other roms for various devices (mainly Droid) I have looked at.
Same here. If I want to read B&N books, I could still use their Android app on a custom ROM.
After switching to Cyanogen on my phone, it's been quite relaxing to not have to worry about provider updates bricking the thing or otherwise screwing up the rooted customizations (or just randomly resetting the thing back to factory defaults because I started up one of their apps and it got confused). Not to mention that the CM team does a far better job supporting the device than the manufacturer and my service provider does.
And yes, like other Android devices, there will probably be ROMs in both categories: completely built from scratch with no B&N portions at all, and improvements on the B&N system to add more functionality.
Fair enough for those that are interested in the reader portions - i have to admit, i bought this as a tablet, with literally 0% in it as an e-reader; i already have a Sony 505 for that. I may use it on occasion, but only as an afterthought.
However, this topic is really drifting - perhaps we should just bring it back to the rebooting issue?
Yeah, I installed the Uptime Widget on my NC today and picked it up a few ago and its uptime was 1:30; max 15h (from before it rebooted 90 minutes ago). I'll keep running it.
What we need to do is get a logcat when it happens.. So maybe overnight I'll leave it running or something. It just rebooted on me and I was semi-watching it, didn't even notice but Uptime Widget was reset to 7m up, 15:30 max..
I have started up a logcat and I'm going to leave it running while I get ready to go out for the day.. Although I just installed and fiddled with Google Earth, which failed badly, so I wonder if it caused some problem. Also saw it happen after playing with Google Maps, so I wonder about Location stuff maybe doing it.. Dunno. I just launched Maps a few ago and it's been up since. Hopefully a logcat will capture some info.
I have noticed that I've seen some crashes that don't show the Crash dialog.... TweetDeck is particularly bad about crashing viewing some Facebook posts, and in this case it just goes black for half a second then back to the list of posts. A logcat shows it crashed. But I don't know the two are related (not having the crash dialog stuff and the reboots that is).
I had it reboot on me twice last night, one time I didn't know about it until I picked it up later and noticed the uptime widget was down to some 30 minutes, and another time right before bed I hit the power button and about 10s later I saw the boot up text and a reboot happen.
Still haven't caught it on logcat.
My doesn't reboot spontaneously, but it does "lock up" and won't turn on with the power button from standby occasionally. If I remember to use the Nook Button to wake from standby, I don't seem to have this issue. If I use the power button, and it won't wake, I need to hold it down for ~15 seconds and it reboots.
AFIAK, it has done this since I purchased it (I rooted after about 1 hour with the NC in my hands).
Mine has never reboot WHILE I'm using it, it's sneaky about it. But I suppose I'd much prefer it reboot while I'm not using it than while I'm using it; I have yet to have it do a full reboot while using it.
Trying to set up a Delicious account.. yeah, that rebooted the Java VM. But only time I've made it reboot at all.
Hahah, damnit, it just rebooted after it went to sleep. I seriously think it has something to do with going to sleep. I've been sleeping it and waking it repeatedly on adb logcat and it won't crash. Figures.
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
isolated_epidemic said:
I had this same issue a while ago. I don't have the logcat from it, but from what I could tell is was some sort of error coming from the system dimming the brightness before turning the screen off. I had Extended Controls installed and was using the widget to adjust my brightness. Whenever the screen would dim before turning off I would get a reboot. I have since uninstalled it and have had no issues with reboots. I'm not sure if this is the issue youre facing but thats my story.
Click to expand...
Click to collapse
Actually not using any of those on mine.. I have Beautiful Widgets in ADW and Beautiful Widgets + Note Widget in WidgetLocker.. Not adjusting the backlight at all either, in fact I don't think I have at all since getting it now that I think about it.
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
mastroiani said:
I have the same issue: rooted Nook Color reboots occasionally and it does seem to do it whenever I put it to sleep or it goes to sleep by itself (when the screen dims). It hasn't rebooted while in use, but it does reboot occasionally when left alone. Have no idea why.
From apps that control dimming I have Advanced Task Killer installed besides the stock app that controls dimming... Could it be the issue? I will uninstall Advanced Task Killer and see if that help.
Otherwise I love my rooted NC. It's fast, beautiful and works great as an E-reader and an Android tablet.
to summarize: Do you think it's the hardware issue or software. I've heard of people who have non-rooted (stock) Nook Color having the same rebooting problem, but apparently it doesn't have to do with rooting. Do you think it will adversely affect the Nook?
If anyone finds a solution please post here. It would be tremendously appreciated.
Thanks and have great holidays.
Click to expand...
Click to collapse
I suspect it's a software thing, as it doesn't randomly reboot in use, it ONLY seems to happen going into standby, and I have YET to make it happen connected USB for adb.
You know actually, I think alogcat can log automatically now, maybe I should try that.. but it'd have to run for a day or so, as I only see this happen like twice a day at most.
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
wvcachi said:
Do you have setcpu installed? I was getting random reboots when I had it on conservative. Switched to ondemand for all profiles, and no more reboots!
Click to expand...
Click to collapse
I myself had not played with SetCPU at all. So had you in the past and set it to conservative, and switched it back, or you switched it from its defaults? Reminds me, per my observation that it never has rebooted while on AC or USB, was there a default profile when plugged in that it's set to ondemand vs conservative? This could start making some weird kind of sense. I'll try it, but using something called CPU Tuner since it's free..
EDIT: I looked on USB and on Battery, both times was conservative, so looks like that's the default... Does the Nook have an automatic switching utility like cpuspeed in it? Hmm.. /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor is the file if anyone else wants to look.
BTW, has anyone on 1.0.1 auto-nooted etc not seen these random sneaky ninja power-off reboots? I swear mine waits until I'm not looking and reboots. I've only SEEN it do it once or twice, but in the last 5 or so days it's rebooted at least 10 times while powered off. Again NEVER while I'm using it, so I'm at least thankful for that. If it were rebooting while using it that would not be acceptable.
I have the Uptime Widget, kinda wished I had an uptime graph to see if there is a pattern.. I'm about 99% sure it never happens when plugged in AC or USB.
EDIT2: IT IS CLEARLY MOCKING ME. It just rebooted after I peeked at the governor files and let it idle to sleep.
I have the same random reboot problem since I upgraded to 1.0.1 and used auto-nooter. I only see it when it goes to sleep...or so I thought. This morning I heard it reboot and i hadn't touched it since last night. FYI, it was not plugged in when it happened. Thankfully it never reboots while in use.
Oh...ad i havent used any CPU clocking tools. Also...never saw this on 1.0. So weird but I am sure someone smarter than I will figure it out.
UPDATE- Just got out of the shower and while getting dresses...heard the Book reboot twice within a minute or two.
Wondering if its an app that is causing a fatal crash when it tries to update.
Sent from my Nooxus One using Tapatalk
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
rckymtnrfc said:
I haven't had a random reboot in 3.5 hours and i have used the Nook on and off. I did remove my email account from the Google email app (not gmail) and its been good for awhile now. I will update if this changes but I am feeling confident this fixed the random reboot.
Sent from my Nooxus One using Tapatalk
Click to expand...
Click to collapse
I've had one unexpected reboot today that I know of, I think this has helped, although I keep finding my Wifi turned off, even though this program I installed is only set to turn it off when the battery is extremely low. So I changed that profile and it hasn't turned itself off since, so seems to me maybe the battery reporting is a little wonky sometimes.
I've been watching, and I'll keep an eye out, but I think wvcachi is onto something.
BTW, the Nook has been primarily idle for the last 5 hours, just popped it on a few times to read an email, check on something, or see if it reboots so I haven't used it a bunch but it's lost a whopping 2% battery in that time. I also disabled the Phone stuff too, per this thread:
http://forum.xda-developers.com/showthread.php?t=883908
I am at 6.5 hours now....no rebooting so far.
Sent from my Nooxus One using Tapatalk
My clock has been keeping quite accurate time on Android 2.2.1 and 2.2.2 (not sure about 2.1, since it's only recently that I am saddled with a network provider that does not do NITZ). Since Gingerbread OTA, though, it seems that it's losing about 30 seconds or so per day.
Has anyone else seen this? There are previous reports of this issue for Galaxy S and MDA but not for Nexus One, and all the other threads predate Gingerbread.
Thanks!
yes, I can confirm this. The clock lags 30 seconds or more per day. I put it in the dock when I go to sleep to charge overnight.
I also confirm this.
I can also confirm this is happening on my nexus one running stock 2.3.3
My clock has been almost useless since Gingerbread and the switch to daylight savings. Before daylight savings, it worked perfectly when set to get the time from the network. Last summer on daylight savings it also worked fine, and Froyo handled the switch to standard time with no problem.
Now, if I leave it set to get the time from the network, it will eventually go way off. The time zone changes at some point to Western Argentina Time, when it should be Atlantic Daylight Time. The time will go behind by an hour, and then drift away more and more. The lock screen and clock app will show one time while the status bar shows another, and one or the other of these will not update as the minutes go by. These issues make alarms unreliable and worthless.
Rebooting the phone puts it all back the way it should be. Time zone goes back to Atlantic Daylight Time and the clock is set correctly. Then at some point later in the day, it'll go stupid again. If I turn off setting the time from the network, these problems don't happen, but then the clock will drift and be behind by 10+ minutes after a couple weeks.
So far, my solution has been to leave network time off, and occasionally turn it on just long enough for the clock to sync, then shut it off again. This is extremely frustrating.
Yeah, I have this on the latest stock N1. But, mine is slightly different. The time set from the network is 2mins behind GPS time. If I set the time manually, then hit the network time button it will drop 2 mins back. Doesn't do this on a Blackberry I have on the same network.
I thought I'd come back to this thread to report that my clock issues so far appear to be resolved after updating to 2.3.4 (manually via amon_ra + su zip to keep root).
I changed it back to set the time from the network yesterday, and have yet to experience any of the weird behaviour or lagging I mentioned in my previous post. Normally I would've seen something by now. I didn't see this mentioned in any of the bug fixes for 2.3.4, but so far so good...
I hope the update helps you guys out too.
Hi,
I have been on JVQ since it was leaked (have KC1 modem though) and I haven't noticed any major issues vs the older KC1; rather, JVQ seems to be a lot better. One thing which I have just had happen to me was that my phone seemed to have restarted w/o actually restarting. That is, all apps seemed to have been restarted and media scanning was occurring as well. I have noticed that the phone itself didn't restart since it shows uptime as being a few days and counting.
This is the first time that this has happened, afaik, and occurred as I was trying to unlock/wake the screen. Nothing was responsive but after the screen woke up, the behaviour was that of a restart/boot (media scanning, looking for radio/provider sigal, apps staring up, etc...)
My question: is there anyone else that has experienced this and is this a known issue? Also, is there a solution?
Thanks
I get this too. JVQ from Kies
Also wake to find phone is off, but has battery life still.
Solution would be nice
I've had it a couple of time on JVQ via Kies but also had it on JVO. No apparent cause.
I have actually observed the phone apparently shut down and restart but the system uptime appears to contradict this.