Related
I have a problem where the clock / time will lag behind by a few minutes over time on EB01-based ROMs? I know that there were a few people that posted about this in the custom ROM threads, but I couldn't find any potential solutions.
I have tried auto-syncing the time off of the Verizon network, as well as manually setting the time - same problem in both cases. If it is relevant, I'm using a Blackhole 4.2 ROM.
(1) Does anybody else have this problem? It might help to see how widespread this is.
(2) Does anybody know of a solution to this?
I've had time issues with all of the EB01 roms I've tried. I think it has something to do with not having the original kernal or something (if I was a dev, I could fix it myself, lol). Anyway, the best solution I've found is to install "clocksync" from the market. It's free and you can set it to update every 30 seconds or so.
Hmm I keep hearing about clock lag on Froyo but I haven't had it on any of my roms. I've used stock, deodexed, super clean 2.3, and now black hole 4.21. No clock lag on any of them, my kernal has been switched off and on between voodoo and normal so idk. It's on auto sync from the network too so I'm not sure what the problem is. Maybe try the EB01 Odin package?
I have been running different EB01 releases since it leaked, and I did not have this problem at all until yesterday. It doesn't seem to just slowly drift behind, but it does end up falling behind anywhere from 9-18 minutes from what I have seen so far. Then, it will just sync fine, as it is currently reporting the correct time.
I had the problem for a day and it seemed to go away when I reprogrammed my towers with the *228 function. If you haven't done that already, you should try that.
Never had this issue. Is this happening with the clock in the status bar or a widget? If its a widget it could be a task killer killing the widget and its not restarting. But if its the status bar clock I suggest you use eb01 clock remove.zip. ;-)
I'm with all the others never had batt issues, clock issues, or the infamous sleep of death.
Used my fascinating voodoo powers
I too am having problems. But I also have problems if I turn auto time sync off, so it leads me to believe it is some kernel issue? I've had this issue with Super Clean and Vanilla.
Is that *228 command 2 that you're suggesting?
This is certainly very annoying..
JJRocker said:
I had the problem for a day and it seemed to go away when I reprogrammed my towers with the *228 function. If you haven't done that already, you should try that.
Click to expand...
Click to collapse
Excellent! I'll give this a whirl once wife is back with her phone! Thanks!!!
No issues as stated here. SC2.2.
good day.
Never had any of the EB01 issues till the clock lag. I just did the *228 since going to SC 2.6 so time (HeHe) will tell.
It's not enough to make me go off SC 2.x. It's only my 2nd day on SC 2.6 so I'm still watching the issue.
Have SC 2.7. I had the clock issue once, but it was fine after I restarted the phone and never had it again.
Only rooted/flashed once with Odin with EBO1 Debl/Deodex. Also using PhoneWeaver auto profiling.
I lose about a hour overnight when I let PW turn off the phone at 11:30 PM and back on at 6 AM. Last night, I tried turning OFF Automatic (use network provided values), and the phone lost 45 minutes in 2 hours. Turning Automatic back on manually didn't let the phone catch up until after a reboot.
My temporary solution is to let PW turn the phone back on an hour or 2 early so it will be sure to catch up before I need the alarm to go off, but it is a bit alarming to depend on it so looking forward to more complete Kernels/ROMs that I know are being diligently worked on as we speak.
I have to say, the random reboots sucks. I am running Bamf 1.6 remix. I wiped two times, and keep getting reboots every so often. I wish someone could figure out what the heck is going on
Nobody is going to figure out what the heck is going on without any information. What are you doing when it reboots? Overclocked? If it rebooted when u are using the browser make sure you have flash installed.
dirtyfingers said:
Nobody is going to figure out what the heck is going on without any information. What are you doing when it reboots? Overclocked? If it rebooted when u are using the browser make sure you have flash installed.
Click to expand...
Click to collapse
I did over clock . Over clocking can cause that huh? I did put it back down to 1ghz and have not have any more reboots
Mine runs steady at 1.5ghz. Any higher and I get random reboot.
Sent from my rooted Bolt running VirusROM + leankernel extreme 1.92
Each phone is different. Some can handle 1.9ghz oc and others can't handle any. Also undervolting makes a processor less stable as you are running higher speeds with less power.
No, thats not a storm. Its just my Thunderbolt layin down this post.
Are you on the newest Radio? Some people are reporting that the Leaked Radio is causing the problems. I did notice that after I flashed the leaked radio. I started having random reboots.
Leaked Radio.
I for one can second that comment about the leaked radio. I've noticed a lot more reboots since flashing the new radio... especially after the 4G outage last week and changing my phone over to Rev.A. I just turned Rev.A off after the third reboot of the morning... Hopefully that will get rid of some of them. If not, I'll have to flash back. I like the better GPS locks, but they don't do much good when my phone is rebooting itself sitting on my desk.
EDIT: Didn't help. Just rebooted again. Guess I'm going back to the old radio.
herbiehusker2608 said:
I did over clock . Over clocking can cause that huh? I did put it back down to 1ghz and have not have any more reboots
Click to expand...
Click to collapse
Yes it definitely can, hopefully that fixed your problem and bamf 1.6 is a sweet ROM you should really like it.
I have had the new radio since it was released and never had a single reboot so that must not be affecting everybody. Maybe it is another factor causing reboots?
please check out my post http://forum.xda-developers.com/showthread.php?t=1094355
Newbie here.
My CM7 phone turns itself off while idling (screen off) once in a long while. It seems to do this when the phone is overclocked, even mildly at 710MHz.
However, I can't make it crash by running stabilitytest at 787MHz for a few hours.
I have also stripped the phone down to only running K9, GV and Missed Message Flasher with wifi on, BT off, GPS off, and 3G data off.
I'm about to hand the phone over to someone and want to make sure that it's really caused by overclocking.
No it isn't because the overclock... i was having the same problem...
Oh ****, I can live without overclocking or any fancy apps, but having the phone turn off by itself without knowing about it is a nightmare.
Does anyone know what the likely cause is?
Have you tried any different kernels or stuck only with what came with cm7? Ive heard of the problem but never experienced what you have...since i really dont have the tools to figure it out, try combinations of clean wipes and reflashing or switching different .32 kernels ie.19.4 cfs / bfs or goldenleaf kernels
Sent from my LG-P500 using xda premium
If this the android version of BSOD, can't they at least make the screen blue?
Oh wait, I forgot Microsoft has a patent on that ;(
So i have a verizon fascinate and am currently running cm7. (first tried the stable release but niw a nightly). Im eeally liking cm, but since i got it my battery life is garbage. Basically the drain seems to come from either the android os sercice or cell standby. Whenever i leave my phone inactive for a while, when i wake it up the battery has dropped a lot and tge phone is very warm. I have been modding this phone for a while, but im no android programmer. Purely based on the forum searchi. G ive done on the issue, it seemsblike cm7 has an issue with my modem or radio.
Extra info: my 3g/2g signals seem fine (always 0% time without signal). Wifi connectivity seems fine. Im also running glitch's kernal altho the problem has persisted with and without it (i did do a kernel cleaning first). I used the "go from anything to jb vanilla" guide cuz i was having issues switching to mtd at first (sry dont have a link rite now but it was on xda) . I get occassional force closes, but not really a problem. When i did a titanium back up, the very first time i flashed cm7 i Did restore system settings, but i did not do that every time since then. Ive done a fresh flash of the stable mod around 3 times trying different stuff, but this one is niggtly as i said, and each has had this issue.
If looked around a lot, and wgile this seems common, no one has posted a consistent solution or explanation to the problem, so thats what im looking for.
Sent from my SCH-I500 using XDA App
Hellomello13 said:
So i have a verizon fascinate and am currently running cm7. (first tried the stable release but niw a nightly). Im eeally liking cm, but since i got it my battery life is garbage. Basically the drain seems to come from either the android os sercice or cell standby. Whenever i leave my phone inactive for a while, when i wake it up the battery has dropped a lot and tge phone is very warm. I have been modding this phone for a while, but im no android programmer. Purely based on the forum searchi. G ive done on the issue, it seemsblike cm7 has an issue with my modem or radio.
Extra info: my 3g/2g signals seem fine (always 0% time without signal). Wifi connectivity seems fine. Im also running glitch's kernal altho the problem has persisted with and without it (i did do a kernel cleaning first). I used the "go from anything to jb vanilla" guide cuz i was having issues switching to mtd at first (sry dont have a link rite now but it was on xda) . I get occassional force closes, but not really a problem. When i did a titanium back up, the very first time i flashed cm7 i Did restore system settings, but i did not do that every time since then. Ive done a fresh flash of the stable mod around 3 times trying different stuff, but this one is niggtly as i said, and each has had this issue.
If looked around a lot, and wgile this seems common, no one has posted a consistent solution or explanation to the problem, so thats what im looking for.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You could flash jt's vanilla gb rom. That has good battery life.
Sent from my SCH-I500 using XDA App
Plus do you have an overclock?
Sent from my SCH-I500 using XDA App
I have had the standby battery drain on every CM7 version and Kernel tried so far including 7.1 stable,7.0 nightlies,JT's Vanilla,and PoolParty. It's even worse if I shut phone down and don't plug in. It will drop 50 to 75% overnight with phone not on?
Has done it with undervolting,overclocking,and voltage control not even installed. This is first time I have seen others having similiar issues.
I think this is a known issue for all MTD roms on the fascinate, if I'm not mistaken.
Sent from my SCH-I500 using xda premium
TheBDub said:
I think this is a known issue for all MTD roms on the fascinate, if I'm not mistaken.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I lose only 5% to 10% overnight on CM7 never really notice how much on MIUI cause I never ran it long enough. I guess every phone would behave differently for MTD's or maybe you have an app or mulitple ones that refreshes frequently(Fancy Widget comes to mind).
Well that really sucks, because i do enjoy cm7. But this also means if i go back to a touchwiz configuration like stock dl09 i shouldnt have these issues right?
But before that, has anyone who had these issues tried anything (ie kernels or maybe standby mode power conservation setting, etc... ) that have at least noticeably improved your battery life? Right now mines pretty unbearable (im talking 8hrs while on but totally inactive), but if i can get it up a little i might b able to manage.
Sent from my SCH-I500 using XDA App
I am also experiencing poor battery life. I just flashed 7.1.0 yesterday and absolutely love it. Was using com rom for a few months, but a friend said to try out cwm 7. I used to get about 6 - 8 hours of Pandora while at work and today I only got about 4 before my phone shut off. I'm going to try completely killing battery and charge with phone off tonight an see if it's any better tomorrow.
Any other suggestions? I'm not a noob when it comes to custom roms and flashing (I used to flash the **** out of my G1) but there may have been something I over looked when switching to cwm7. I wiped everything a few times before flashing including battery stats and dalvic.
My battery life is actually really good. Running latest nighty, undervolted -75 across the board,stock kernel, and no overclocking.
Just can't figure why I lose 50-75% of battery overnight when phone is shut down and not charging?
I have the same issue with CM7.1, turning phone of at 80% battery at night to find it at 25% at morning
Is there knows solution?
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
brando56894 said:
I've only had this happen a few times and was wondering if anyone had this happen to them also. I'm rooted and run custom roms, it doesn't seem to be rom or kernel dependent.
For example, I had my phone on since noon and haven't really used it since then except a few times to check the time. I just pulled my phone out of my pocket and hit the power button... nothing. I held it down and it started to boot up. When this happens the battery is never dead (it was at 68% with the ext. battery this time), it just wants to turn itself off. It seems to happen when the phone is "sleeping", it's never done it when I'm actively using the phone so it's not an overheating issue.
It's not really annoying since it doesn't happen often, it just confuses me.
Click to expand...
Click to collapse
still you might want to check the rom and kernel just in case, either re-flash or change.
if the problem still happens, use your warranty and get a new phone.
what rom, kernel, and recovery are you using?
I actually just happened earlier again. Got a text from a friend that she was here, so I went down and let her in, came back up and went to check my phone a few minutes later and it was off. WTF.
I'm currently using Nils newest business sense with the OC'd ICS kernel and the latest Amon Ra recovery. This used to happen on GB also so it's not a rom/kernel problem IMO.
It happens so sporadically (except for tonight apparently) that it's maybe happened 5 times since I got it on release day.
Maybe I have the governor in cpu master set too low? I have it at the lowest of 384 MHz, I've always wondered this: whats the difference between conservative and powersave?
did it happen while you were on stock GB or on a custom rom and kernel? maybe try relocking and running stock for a while and see what happens?
I honestly don't remember, it's been too long lol. It's not worth it to go back to stock and relock considering I like ICS too much.
brando56894 said:
I actually just happened earlier again.
I'm currently using the OC'd ICS kernel
Click to expand...
Click to collapse
that's the issue right there, run the stock kernel at stock speeds.
How could it be the ICS kernel when it's happened on GB also?
Which OC? I've read that the 1.8 causes random stuff like this, but 1.7 doesn't.
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
3.0.16-g4a9c8a3 SebastianFM #1 is what the kernel info says
The zip name is Overclocked_kernel_v1.20_1836_MHz_by_sebastianFM.zip
Not all phones can handle overclocking.
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
brando56894 said:
Mine is stable about 98% of the time, it may actually be the extended battery that is causing the issue.
Click to expand...
Click to collapse
9x out of 10 random reboots are from either undervolting too low or overclocking too high.
I went back to the stock kernel since it seemed to be a little choppy with the oc'd kernel. That may have been the problem after all.
Sent from my Transformer TF101 using Tapatalk