The clock on my wizard keeps resetting to Feb 2006, but not when its low on power.
It just seems to do it randomly and I have no idea why.
Its more of a pain than you would imagine, as if it happens and I miss calls, the calls are added to a fairly random list of calls all showing as Feb 2006 and based on the time the call came after the clock reset, so if there are a few calls, and it has reset a few times, they are entirely all mixed up, and included with previous calls that fell into the same category.
Any ideas, please?!?!
I'm wondering if the battery is making a solid connection. Does it do this completely randomly, even when the phone is on? For example, can you be browsing the web on with the clock set to the correct date, and when you close IE it's February 2006?
If it only does this when the phone is off (soft-reset kind of off, I mean), then I'd look into how solid a connection the battery is making inside the case. Perhaps try wedging something (paper, something non-conductive ) inside the battery case to ensure a proper connection is being made.
If it's doing this randomly and even when the phone is on and active, however, I'm afraid I'm of little help.
go to HTC web site and download a patch that fixes that bub.
if you disconnect the battery from your wizard, he will start with is factory made date
Thanks guys.
It can happen even when the phone is charging - and also always happens if i swap sims.
It also does happen if the battery is removed - which I need to do to restart it sometimes if it crashes. My first phone in 1997 would restart at the right time if you swapped the battery, so to think I have firmware that needs patched to do this eleven years later is freaky.
Have you a link to the patch, and can it be downloaded directly to the phone?
wizardragon said:
The clock on my wizard keeps resetting to Feb 2006, but not when its low on power.
It just seems to do it randomly and I have no idea why.
Its more of a pain than you would imagine, as if it happens and I miss calls, the calls are added to a fairly random list of calls all showing as Feb 2006 and based on the time the call came after the clock reset, so if there are a few calls, and it has reset a few times, they are entirely all mixed up, and included with previous calls that fell into the same category.
Any ideas, please?!?!
Click to expand...
Click to collapse
Install this to your device. It might solve your problem.
Hello All:
This is my first post here but just reading around has solved many problems for me already. However, my phone (sprint mogul 8600) has been misbehaving and even a hard reset did not solve this problem.
My problem is that the stupid thing won't stay asleep, ruining my battery life and sanity. Is there a way to set it so that it will only wake on active decisions (incoming text, incoming call) and me pushing the power button? I've cruised option after option but I haven't been able to find anything useful.
It still functions properly when it should wake up, it just seems to wake up every few minutes on my desk and i think i have an incoming something to deal with. In the end I have just stopped paying attention and have missed lots of calls because of it.
My apologies if there is a faq that goes over this already, I looked but could not find.
Thanks in advance
Battery life goes down approximately 50% per 10 hrs because the phone turns on as if someone hit the power button at irregular intervals. Is the phone SUPPOSED to be able to turn on for reasons other than incoming messages or using the power button? Its driving me crazy, I can't even go out for a day because it will run out of battery.
Are you running a custom rom or stock rom? If stock, is the most up to date from your carrier? After you did the hard reset, did you test it before installing any cab files? It's possible one of the apps you are installing may cause this.
If it's the stock rom and you are installing nothing, I would say it's a defective phone.
I know on an old PDA I had years back at midnight every night it would turn on, it would do maintenance on my scheduler and then turn back off, but haven't seen my phone ever do this during normal hours.
BTC
It has to be software on that rom or additional installed by you. If you haven't installed any software you might want to try flashing a custom rom and see if that takes care of it.
i have had the same problems with my ppc6800 and blackjack 2, i think it has to do with the changing networks... on my drive home from mass to maine it will do it in about 5 spots anyways consistantly. in my hotel in mass i get crappy reception and itll do it every now and then. this has been an issue with both phones. bugs the hell outta me on my trip home cus itll light up, then i grab it to figure out why and theres nothing... learned to live with it
I performed a hard reset after continued trouble with this. It will come on at least 1 time per hour, and as often as every 5 minutes, with absolutely nothing done to it short of initial calibration/data entry. It will also do this sitting on my desk, not moving or anything.
I suppose I could try a custom rom, but I fear I am opening pandora's box, as I am told these phones are on backorder if i happen to brick mine. Any recommendations for a new ROM to try?
This is normal.
Is this sufficient problem to get it replaced? A hard reset and nothing else and problem persists.
It's a win mobile "feature" since the early WinCE days. Every Palm-size/WinCE/WinMO device I've owned turned itself on from time to time. Now, it's blamed on network changes, mostly going in and out of EVDO coverage. When these were simple PDA's, it was blamed on internal housekeeping. If you corner a MS rep on the issue, they will blame the hardware and outside software vendors. I never believed them. Either get used to it or buy a device other than a WinMo based, it will never ever be fixed!
BTW, I'm in my basement where I get less than an ideal signal and my Mogul has turned on and off 3 times while I was typing this.
I have my phone sitting next to me in the cradle all night long, 2-3 hours before I go to bed I turn out the lights to either view my laptop easier or watch TV, if my phone was turning on I would know it because I would have bright light in my eyes.
So I would say it's not as common as you described in the 2-3 times while composing the email. Mine might turn on at midnight, tho I am usually asleep by then, so I can't say for sure, but the only time it turns on (that I know of) is when I receive a text message or a phone call. Emails don't wake up my phone. And I get 20-30 emails a day.
I am on a 1X only network, no EVDO here yet, so it could be an issue with EVDO, in my phone settings I have an option for Service Tone, that makes a beeping sound when I lose or regain service, might try turning that on and see if it's beeping when the phone is turning on. If so, it's a signal issue.
BTC
I have this problem too and hate it. Every time I come out of the subway the phone turns on in my pocket. I cant drive at night with the phone facing up on the dash because it turns on every couple of mins. It's completely annoying, kills the battery and launches tons of programs, every once in a while it makes calls too. I would be very happy to get this "feature" taken off my phone!
B
WinMo devices turning on all by themselves is the reason there are so many screen lock programs available. If you've got a WM device and plan to carry it in a confined pocket (like your pants) check out S2U2 or throttlelock. Your phone turns on when leaving the subway because it's aquiring a signal, it probably turned on while in the train while searching for signal too. While driving, you're probably passing in and out of 3G coverage which will also turn the device on. If you stay in a solid signal area, the phone will stay off for the most part, but that does negate the whole mobile thing a bit. The center of my basement where my home theater is gets a inconsistant 3G signal. My Mogul will turn on and off and kill the battery in a few hours. My wifes Palm, my friends BB's and iphones won't turn on once. Once again, the issue of WM/PocketPC/WinCE turning on for no apparent reason has been a c ommon complaint for years, at least to the Casio E105 days when I started on my WM journey. Since MS has never addressed the issue, I doubt they ever will.
I have never had the phone random come on from sleep. Leaving and entering coverage doesn't change that. I say you have something in the rom causing the problem or a program running in the background
drewcam888 said:
I have never had the phone random come on from sleep. Leaving and entering coverage doesn't change that. I say you have something in the rom causing the problem or a program running in the background
Click to expand...
Click to collapse
You've never taken the phone out of a pocket or holster to find it already on? My 6700 on VZW did and I think I ran every ROM developed for it at one time or another, each of my 3 Moguls running various OEM and custom ROM's did/does. I've heard similar complaints from coworkers running various
WM devices. A friend I take the train with daily complained about this with his AT&T Tilt too. Both my non phone Axims (x5 & x51) occasionally turned on as did my Toshiba E805, Casio e100, e105 and e115. Every WinCE based device forum I have participated in over the years has featured complaints about WM turning on with no user interaction. Obviously, it's not a deal breaker for me, but it does happen...a lot. The issue in my basement is the extreme of the problem, move the phone towards the exterior walls and the phone reverts to only turning on and quickly off occasionally. Another example. When traveling by LIRR to Penn Station the phone will stay off even when entering the river tunnel ad traveling under Manhattan. At some point when I exit the station, the phone turns itself on. Since I'm walking in rush hour crowds, I've never tried to find at which exact point my Mogul turns on, but it's always on when I get my coffee in Borders Cafe.
I have never taken it out of my pocket and have it been turned on. It is always in sleep mode.
This also happens to me, i own a mogul, and this is really and extremely annoying.
i have test it for few months and this is my conclusion.
As you guys said already just wait for few min and it will turn on the screen, but also when i shake it and when you hit it.
it really is a battery killer.
lepapirriky said:
This also happens to me, i own a mogul, and this is really and extremely annoying.
i have test it for few months and this is my conclusion.
As you guys said already just wait for few min and it will turn on the screen, but also when i shake it and when you hit it.
it really is a battery killer.
Click to expand...
Click to collapse
If it's turning on when you shake it, you probably have a hardware issue.
I checked Spare Parts and notice that my Dialer has the most partial wake up use. Why is that? Each time I get a call, does that trigger it to wake up? Because I barely even user the Dialer at all so I don't see why it would be waking my phone up for.
Thanks for any insight!
I'd like an answer to this question as well. I'm currently running meXdroid V2, and I've noticed a lot of Dialler partial wake usage - even when I've not even made or received any calls. I wasn't sure if it was a problem with the rom, but I guess if you're having the issue too, then maybe something else is causing it.
What rom you running?
I'm running CM7, forgot which version, possibly 7.0.2
Just seems weird to me because I usually don't make calls or receive calls until night, but the partial wake amount that dialer uses is still high before the calls are even made.
I've been using my Nexus 4 since Friday and must say that it's the best phone that I've ever used (especially coming from an Xperia ray).
Anyways, I have one problem (well, more of a minor issue). I dial a phone number, hangup tone immediately happens and a quick nano second CALL ENDED, then the phone automatically redials and it goes through.
I think it looks like I've cut up my SIM too short (will take a photo later when I get home from work) because the SIM does not full take up the whole space in the SIM tray. The SIM contact is intact though, just some white plastic parts that were cut up too much.
Another possible issue causing this problem is that I'm using a $20 Telus corporate (data is blocked cause I don't really have real need at this moment, using a MiFi from WIND) and the signal bars are grey instead of blue.
That hangup tone prevents me from using apps like Call Timer which worked perfectly on my Xperia ray. I can still call and make text messages.
Should I buy a new microSIM or even worry about this at all?
Bump
Sent from my Nexus 4 using Tapatalk 2
Just started getting this on mine too... gonna flash to some CyanogenMod later to see if that does anything. I am 100% sure it wasn't happening when I first got my phone, i cut down my old SIM to fit and that worked fine for a few days. Not sure when but think it was before i got a brand new MicroSIM to replace the old one but i could be wrong. I've put the same SIM in my SGS2 and it doesn't do that issue, i also just did a factory reset and it did it right away too.
Calls still go through but it's just annoying as hell, lol. Makes me look like I called 6 times or something when it's only 2-3 sometimes.
I've also tried switching to EDGE just incase it was a 3G issue and no dice.
Add me to that list. When I press send button phone starts calling and miliseconds later it says ended call and other miliseconds later starts the call again.. So annoing because i use a call recorder and its saving 2 calls (and empty one and the real call) and apps like call timer works bad with this issue
My friend has a new stock s5 and can not answer calls if the phone is asleep(screen off)
The phone rings and the screen turns on with the answer slider.
He slides the answer call and then it just sits there for a few seconds like it is frozen, but never answers the call.
He can then call the number back and everything works fine, or if the person who called calls back while the screen is still on then he can answer just fine.
We live in a village in alaska (phone company is GCI) which only has edge data.
When he is in anchorage he can answer calls just fine even when the phone is asleep.
He has put his sim card in his old iphone and it works fine.
His wife got an S5 at the same time and both of their phones have the same exact issue.
I have no problems in the same area with my old S2 or my newer S4.
Any idea on what he can change in order to answer calls the first time?
NarfiWillem said:
My friend has a new stock s5 and can not answer calls if the phone is asleep(screen off)
The phone rings and the screen turns on with the answer slider.
He slides the answer call and then it just sits there for a few seconds like it is frozen, but never answers the call.
He can then call the number back and everything works fine, or if the person who called calls back while the screen is still on then he can answer just fine.
We live in a village in alaska (phone company is GCI) which only has edge data.
When he is in anchorage he can answer calls just fine even when the phone is asleep.
He has put his sim card in his old iphone and it works fine.
His wife got an S5 at the same time and both of their phones have the same exact issue.
I have no problems in the same area with my old S2 or my newer S4.
Any idea on what he can change in order to answer calls the first time?
Click to expand...
Click to collapse
No thoughts or ideas on this issue?
I also have this same issue. It does it when its asleep and it also does it when its awake. For some reason it just wont slide over to answer its weird. Mine doesnt do it every time it does it 3 out of 4 times though.
Sent from my Sexy Samsung S5
There have only been a very small number of reports across several phone models of this behaviour.. and AFAIK no one has elucidated a pattern that would elucidate a cause with any certainty. I can tell you that my 900T with the Phoenix ROM does not have this issue.
Unfortunately, no one who has posted with this issue has provided nearly enough details about their configuration to narrow anything down but as pure speculation it may just be a delay in waking up that effectively misses the window in which you could answer the call. If so, then debloated ROMs, faster data connections and those utilizing less power saving features i.e. typically throttling the active processor would likely see the problem less or not at all.
.
Perhaps try reducing the proximity sensor delay time. In theory that may reduce the transition time from screen saver to dialer /home screen.
Edit (or add if not present) build.prop
Code:
mot.proximity.delay=0
ro.lge.proximity.delay=25
ro.telephony.call_ring.delay=0
ring.delay=0
.
.
fffft said:
Unfortunately, no one who has posted with this issue has provided nearly enough details about their configuration to narrow anything down
Click to expand...
Click to collapse
NarfiWillem said:
My friend has a new stock s5
Click to expand...
Click to collapse
Stock. Not rooted and no new roms.
Both his and his wifes phones are new and stock and have the same problem.