Hey,
Just the other day my phone started doing the strangest thing. The time is not accurate, or at least it isnt for long. It is fine when you boot the phone and it auto-updates time from the network, but after a few hours it is off. For example, its current 2:10p, but my phone said 2:23. I enable\disable airline mode, which causes it to resync with the network, and it corrects itself.
I just applied JAC's OCv3 kernel 2 days ago, but I didnt notice any issues until today. Anyone else having a similar issue? It is quite annoying when you cant rely on your cell phones clock lol
Thanks!
Never seen that issue but I have the stock kernel, so maybe it is that. Anyone else have this problem with the kernel in the OP?
Thats SOOO strange, Ill post in the kernel thread as well to see if anyone else is having that issue.
No issues here, bud. Flashed OCv3 this morning and my clock has been spot on all day.
Sent from my SGH-T959 using XDA App
Okay, so I compared the clock to an "accurate" clock, and its only counting 57 seconds to each minute. WTF?!?!
I am flashing back to SC9 to see if it also has the issue. will report back
I've been running SC9 since yesterday morning and haven't had an issue yet. I also have a ext4 partition if that matters.
Sent from my SGH-T959
Related
I experienced a pretty nasty issue today with my galaxy s. As you know it's getting pretty hot these days, and prague is by NO means an exception.
Anyway my wifi stopped working on JM2, I've had JM2 for a few days and never previously experienced wifi issues.
So I basically tried everything, deleting apps, restoring settings, flashing firmware, the list goes on and on. Until I thought, perhaps it overheated?
Opened it up removed the battery and shoved it the fridge. 10 minutes later it was working perfect.
Perhaps JM2 has a problem with heat?
Sent from my GT-I9000 using XDA App
lordzebdeh said:
I experienced a pretty nasty issue today with my galaxy s. As you know it's getting pretty hot these days, and prague is by NO means an exception.
Anyway my wifi stopped working on JM2, I've had JM2 for a few days and never previously experienced wifi issues.
So I basically tried everything, deleting apps, restoring settings, flashing firmware, the list goes on and on. Until I thought, perhaps it overheated?
Opened it up removed the battery and shoved it the fridge. 10 minutes later it was working perfect.
Perhaps JM2 has a problem with heat?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Or maybe simply taking out the battery did the trick?
Your device should also give you a warning message if the battery gets too hot.
Mine did the other day while i was playing some robo defense while charing, two things that both seem to get me a bit hot...
Slacke said:
Your device should also give you a warning message if the battery gets too hot.
Mine did the other day while i was playing some robo defense while charing, two things that both seem to get me a bit hot...
Click to expand...
Click to collapse
This. Happened to me a few weeks ago.
Sure I did that before, left it for 2 minutes with the batery out,
while I made myself some coffee. That didn't do the trick.
I don't know what caused it to work again but it was consistently not working til I put it in t
he frige
Sent from my GT-I9000 using XDA App
I have a non-rooted stock NS on 2.3.3 and the phone was just sitting on my desk doing nothing when I felt it vibrate. I picked it up to check for a text or email, but the phone was instead rebooting.
Has this happened to anyone else on this build? I have had the phone reboot while in call before, but never just sitting there in standby.
This happens to me in 2.3.2. I will have the phone just sitting there and it will randomly just be rebooting. Its not frequently enough to bother me yet but it happens on and off.
Sent from my Nexus S using XDA Premium App
same here on 2.3.2.... thats why I wanted 2.3.3. Ill wait patiently for the nightlies to include it.
happened to me many many times on 2.3.2, but not 2.3.3. knock on wood
Happened to me...2 times already...never on 2.3.2...im rooted though
Sent from my Nexus S using XDA App
This happened to me like 2x a day with 2.3.2.
Hasnt happened once yet with 2.3.3.
I never got reboots in-call, though I did get them a couple times when I overloaded the phone's RAM.
Mine just rebooted in 2.3.3. I'm also getting "Can't connect to camera" anytime I use the Amazon barcode app which worked perfectly in 2.3.2.
Haven't tried the new update yet
Sent from my Nexus S using XDA App
I never had the in call rebooting, just overloading reboots on my nexus s. I have yet to have one since the update, but it has only been a little over 24 hours. Then again this has been happening to me since updating my nexus one be it stock, rooted, or CM6 FRF91 and FRG83D or any form of gingerbread I've used on it. The only thing I can say it it started in froyo for me.
Sent from my Nexus S using XDA App
on the new update havent had any issues.
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
MacGuy2006 said:
I had the random reboot in 2.3. 2 and thought the update had fixed it.
Unfortunately it did not - i noticed the phone rebooting yesterday.
The camera has crashed twice so far, requiring a battery pull.
I am stock, non-rooted.
I also get random failed downloads and failed market updates.
Starting to get frustrating.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
He's not rooted dude. Btw I get a reboot on every call. On cm nightly, no matter what I try/flash
Sent from my Nexus S using XDA Premium App
I just had reboot one time with 2.3.3 but I was running all processes 72 hours, without stopping and it suffered a lot !!!
deeren said:
With all the problems you stated, it is obvious that ur rom is corrupt. I suggest you to back up all your settings, wipe everything and then reinstall a rom .
Click to expand...
Click to collapse
Nope.
It happens to 2 Nexus S, both stock, not even rooted. One barely has additional apps, too.
I think a lot of people don't notice the reboot, because it is silent, so if you are not looking at your phone exactly at the particular time it reboots, you wouldn't know it.
The inability to dial at times is much more annoying, IMO: you punch in a number, the phone tries to dial, then hangs up. At the same time, there are 3-4 signal bars. When it happens, it normally takes several tries to get it to work.
The crashing camera also doesn't happen every time, but it is definitely a new bug in 2.3.3.
Just had my first random reboot on 2.3.3 while phone was sat on my keyboard while at my PC.
Rooted detoxed Rom stock
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
This dim reboot screen thing used to happen quite a bit on my g2 in its early days, got it launch day. OTA fixed it.
Sent from my Nexus S using Tapatalk
fchipm said:
My 2.3.3 phone went into the weird "Dim Screen Reboot Screen" reboot at some point during the night last night. I was late for work because the alarm clock didn't go off (I know, I know...don't depend on a cell phone alarm clock)
I'm about done with this phone. And Android. Anyone wanna buy my NS? Dead serious.
Click to expand...
Click to collapse
I am still hopeful, but I am losing some patience with Android.
The platform seems to be all about selling the newest hardware, but the user experience is definitely below that of the iPhone. I keep hoping that the next Android OS upgrade will close the gap, but....
The iPhone 5 will have 4" screen, with Apple's better screen aspect ratio. If it only did Flash....
Anyway, the Nexus S is really the best user experience Android has to offer, and it's overall fine. Except when it acts like WM6.
For some reason my EVO keeps restarting randomly on me, and all the time too.
I'm running CM7 7.0.3.1 and savaged zen 2.2.0, and I have an extended battery and I rum juicedefender.
Now I don't think its the battery because I've had it for month
Its most like savagedzen 2.2.0 but idk maybe its CM7 too.
I think this started after I started playing words with friends. Doesn't seem like a memory intense app and I never had this happen but lately its been rebooting randomly, like I'm download from the market. Internet, and even posting this thread!
Basically I'm thinking of switching to either virusrom or Mik, which is better?
Sent from my dope fly fresh EVO
my chick is having the same issue. hers just reboots at random after starting to use her pandora app about a week ago.
her evo is running:
Mod version: CyanogenMod-7.0.3.1-Supersonic
Kernel version: [email protected]#1
Ditto
I have same problem, and have tried various ROM's, most recently a complete wipe as per Mikroms instructions. Only pattern I can make out is it tends to start when the CPU is stretched a little, such as running Tango over 3G, or even Angry Birds for over ten minutes. Once it starts though, it reboots several times before it finally quits.
There was another thread on this, but no solutions, instead it turned into an argument over whether it is CM7 fault; not very constructive. I have tried different batteries and changed up CPU speeds, still to no benefit.
Like I said, if I don't tax the system I have no problems, and that so far has been my only solution, but a disappointing experience with my Evo.
My dad's kept rebooting too even after the gingerbread OTA. He is running a bone stock phone(not even rooted)
Wife is having the same issue on her stock EVO with the new OTA
same issue here, playing WWF,stupid zombies or surfing the web. on decks rom and on the gingerbread 2.3 stock.
Apparently, this is a common problem with the EVO. Mine started as soon as I accepted the recent OTA update. There is an XDA thread somewhere. Just do a Google search.
Same here & 2 of my other friends. I am on my 3 or 4 EVO (lost count) & everyone does it. This is only one I rooted as well. I noticed it does it less (once every few weeks to a month) with a custom non cm rom. Also restart your phone at least every couple of days (usually I did every day). It works out pretty well. What I tell my friends don't hesitate to tell sprint you have a issue so it gets documented. So you have proof to fall back on when you had enough. It's not like you pulling one over on them. They see if you have all these issues for so long why just now saying so. I have found that for some reason phone resets in middle of calls multiple times same day with certain Bluetooths. I drive truck for living so I on phone alot with customers/work/friends/family/etc. Always Bluetooth, and did up to 5 times a day. Then bought one top of line (jawbone icon &now Bose) and doesn't do it like that anymore. Hope this helps any of you. & again any issues you get tell sprint. Last time I got a new EVO in box, & they let me keep my old one. So gave it to my mother. Then had it replaced under her #.
Sent from my EVO using Tapatalk
Mine started out with a reboot
every so often. It finally got so bad it would reboot over and over until I pulled the battery for a few. Somewhere in the process, my GPS crapped out as well. It would work for a few minutes and then freeze. Not a good thing when you are not from Boston and trying to navigate 8am traffic to get somewhere.
I got a refurb as a replacement. It was in perfect shape and only had like 111 minutes of talk time. No telling why it was sent back but I've had no issues with it.
Mine is doing this too.. its annoying Ive restored backups and it just keeps rebooting, i dont know whats wrong. Im on avaFroyo 2.2
I don't remember where but there is a thread about this very topic. From what I read this was attributed to a corrupt data partition. My gf phone is starting to have this problem. Only fix I have read so far is to reroot phone and take it to sprint. I am waiting til they can root the ota. Then I will unroot her phone and get a new one.
Tim
Sent from my PC36100 using Tapatalk
The first time this happened to me I figured it was a fluke. Now I've had a third time where in mid phone call my Epic has "thought" it's battery was drained to 0 and hung up my call then proceeded to shut down. The first time was in a busy train station in Chicago, don't remember the situation the second, and today was when I got another call beeping in while I was on the line. Each time when I booted the phone back up it showed plenty of life left on the battery.
Has anyone else experienced this or could it be my phone? I wish I could remember specifics from the first two occurrences, but I believe it could have been a call waiting situation as well.
FWIW, I'm on the MTD CleanGB 1.0.3 rom.
Does it go through a shut down or is it just off? If it is just off may be loose battery connections. Oh you said it shut down on the call....maybe it was a modem crash. Try reflashing a modem.
Sent from my SPH-D700 using XDA App
Mine actually did this last night while I was on the phone
kennyglass123 said:
Does it go through a shut down or is it just off? If it is just off may be loose battery connections. Oh you said it shut down on the call....maybe it was a modem crash. Try reflashing a modem.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
It actually goes through the shutdown. Does the low battery double beep and pop up, then says shutting phone down.
Might need to wipe the battery stats then re-calibrate the battery. Mine has done this before, but I'm pretty sure it was from throwing the battery at my wall.
theduce102 said:
Might need to wipe the battery stats then re-calibrate the battery. Mine has done this before, but I'm pretty sure it was from throwing the battery at my wall.
Click to expand...
Click to collapse
Quite possible. I think I didn't bother calibrating the last couple of times I've flashed a ROM. Going to go ahead and do that and hopefully it doesn't happen again.
CapsLockKey said:
Quite possible. I think I didn't bother calibrating the last couple of times I've flashed a ROM. Going to go ahead and do that and hopefully it doesn't happen again.
Click to expand...
Click to collapse
Ya I've had the same issue I would have like 14% and while I'm in a call it would shut down
Just wipe status and calibrate it and it should be fine
Sent from my SPH-D700 using XDA App
I've had this happen, only on cm7 though.
Doesn't happen often so I've not been worried about it
Sent from my SPH-D700 using xda premium
This used to happen to me ALL the time. It was so frustrating, as soon as it hit 15% if I was talking it'd shut right down. Thankfully flashing the new GB roms seems to have fixed the problem. I sure hope it doesn't happen in CM7
I have this issue regardless of rom. Happens when on a call and low battery alert sounds.
Well, just did it to me again. I calibrated the battery after upgrading to the latest MTD cleanGB yesterday. I was in a building that had poor signal granted, but same thing dropped call, low battery popped up and it shutdown. I had 60% battery left.
Just wondering if anyone knows what these spikes might signify?
I had a Nexus for 2 weeks and the last few days it was turning itself off like the issue here every night:
http://forum.xda-developers.com/showthread.php?t=1830546
My post is there too. Previously, I only saw one spike with the old Nexus, now I see more.
I exchanged my Nexus 7 for a new one yesterday but does the battery still have issues? It doesn't turn off at night so far but my Battery Info graph shows even more spikes now.
Any engineer know if this is normal or safe?
Thanks!
Still happens
I exchanged the Nexus for a new one.
My NEW 32 tab worked out fine for a night and woke up today to the full battery indicator and tablet off again.
I have a new insight though, somehow the battery temp is rocketing to 100 and I'm guessing that is when it shuts off.
It may be because I am using SetCPU to limit my CPU speed to 300mhz when the screen is off. Maybe the tablet is trying to update all my apps while I am sleeping? It shouldn't use so much power though.
I'm going to try to create a new command to let it use it's whole CPU as long as it's on AC and screen off and see what happens tonight.
Some ppl reported that after official 4.2 update their battery drains while screen off. Issue was resolved with factory reset. I have same issue. Didn't had the time to do factory reset yet.
Sent from my Nexus 7 using XDA Premium HD app
For me, I'm not running 4.2 or have i upgraded on this Nexus. On the first one i had, I did update, and it seemed to slow down the tablet.
This one was stock and then I rooted, put CM10 on it and then Franco Kernel.
This problem worries me because it makes me think something is traumatizing my tab enough to shut it down at night and I can't figure out what it is.
I don't know if I want to keep it if it is going to keep doing this. But I do love this tablet.
I wonder if this could be a cyanogen mod problem? I've read about some people having a power problem with cyanogen,nobody has said anything about their tablet getting bricked yet though. That's what I'm afraid of.