Had it at about 70% battery (around) last night, after 12 hours or so today, it refused to turn on.
I got it to turn on finally with a soft reset, and the battery showed 28%!!
I have no idea how it could have run down so fast, though it could have been something I left on (maybe wifi?).
I'm still surprised it would refuse to turn on at 28% though...
My Dopod 818 Pro is having this problem ever since I bought it. If I turn off the screen using the power switch or let it go to standby automatically, most of this time I can't turn it on again and have to do a soft reset.
I do not see a lot of Dopod users complaining about this problem so I am wondering if I have a faulty set. Other than this problem, everything else works fine.
i'm having the same problem. Do you think there will be a rom fix?
I just found an interesting observation regarding this sleep-to-death (STD) issue. If I left my Dopod overnight and got the STD problem the next day, the battery had drained considerably. It was fully charged the night before, but after 8 hours, the battery is only at 40 percent.
But since more than one person is having this issue, is it still a hardware problem?
This is not a hardware issue, its more like an unoptimised ROM issue. I suppose it will be fixed with an update in the future.
Leaving WiFi on does not matter because your device automatically goes into standby mode after a pre-defined time (3 minutes by default). In that case, even if you leave 10 apps running in the background, it won't make a difference for the aforementioned reason.
With the HTC Universal, what happened was that people would leave apps running in the background and once they are done using the device, they would just close the device thinking that it would shut off, but it wouldn't because the standy-mode was disabled by most people to get a snappier device. In such a situation, battery would drain rapidly overnight as the device hasn't gone into standby mode.
This situation will occur on the JAMin too IF there is no default standy-by mode set.
I have an HTC Universal (O2 XDA EXEC) and had the same thing happen to me two nights in a row. The battery was at 100% when i went to bed and i woke up and realized i was late as the alarm i had set didnt wake me up.
I had to soft reset the phone and the battery was down to 24% and then the alarm starting going off, a bit late though. I have had this phone for three days, and im not happy about this failing twice on me.
The only thing i have changed is running a coporate install (0506) so that o2 active wasnt on the phone.
Is there any fix for this??
Rom version: 1.13.82 WWE
Radio version: 1.04.02
Protocol version: 42.37.P8
ExtROM version 1.13.188 WWE
Go to Settings>System>Power and check the "switch off device after x minutes" option. By default it is 3 minutes, but i have set it to one minute as that serves my purpose. You will notice the drastic difference immediately .
It kind of sounds like an issue I've seen on my m600. It's a wm5 bug where activesync will try to connect all the time, randomly, even if your device is off. It can cause STD (sleep to death) and will. It's a simple fix. Just install the autosyncschedule.cpf and run it. It's a simple little .cab that will change some settings. Hope it helps
http://us.f1.yahoofs.com/bc/59d707c...amin/DisableSyncSchedule.cpf?bftVi9DBC7gsZI7r
If that link to my yahoo briefcase doesn't work, you can get this file at eten-users.net in the download section under /utilities/wm5. It solved all STD's with the eten and so far with my jamin. 8)
You can also fix the Active Sync bug manually.
To do so open ActiveSync on your WM5 device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right.
Slept to death- I've sussed out why my device was doing this
I had an SD card from my i-mate Jam inserted, and after taking this out, the situation stopped happening. So if you've got an SD card in try running the device without for a while to see if that helps...
Related
Hi Guys,
was wondering if any of you had seen this happening, or knew how to fix it..
occasionally, like once every two days or so, my pda2 will just not turn on again after it's turned off (put in standby). the only way to turn it back on is to press the reset button. it still seems that the radio is working when its in this state, as if i make a call to the pda, the phone im ringing from rings and rings, but the pda just stays silent, and if i put the pda up to a speaker i can hear the "da dada da da" noises that mean phone radio activity. also if i put the pda in a cradle when its in this state, the battery indicator light on the pda will turn on as if its charging..
i can almost live with the short battery life, but the phone freezing when its turned off i can't. i've tried a hard reset.. to no avail.
any ideas?
Hey ow, what have you got running that could cause it? Any 3rd party bits and pieces?
Kevin
hi kevin.
thats exactly the path im taking now. i have hard reset my device again, and have loaded NOTHING on to it, i reset it before it could install the extRom stuff, and i've only changed settings like vibrate on ring, and regional settings, etc. i haven't even active sync'd it. so far so good (touch wood)
programs i had loaded before:
intellisync (automatically connected to grps if not cradled)
small menu
kbattery
tAgenda (not fully compatible with 2003 SE, but seemed to generally work ok)
worldmate 2004 pro v1.0 (not fully compatible with 2003 SE, but seemed to generally work ok
and thats all i think. i have my suspicions with intellisync..
Hi there
Mine did the very same thing a few times but i just reset it and carried on ...
id recommend upgrading to the newer I-Mate ROM as its more stable, just be prepared to fart about a bit to sort the country code errors and such.
In fact ... i camt remember the last time mine crashed after ive installed the new ROM.
my device came with the rom dated 1/27/05, which is the latest i believe... ?
well, i think i've figured out what causes the problem, thought i might as well give an answer incase anyone else has this prob.
for me appears to happen when GPRS is enabled and i turn the phone off. gprs is turned on in the first place by intellisync, which sync's my email, calander, todo's and contacts with lotus notes. however i tried enabling gprs manually, waited until intellisync sync'd itself, then turned the pda off and went to lunch. after lunch it was frozen again.. i did turn it on at the start of lunch to check the time, and i assume at that point it hadn't tried to do an update, but probably sometime after that and before it froze i would assume it had tried to sync itself.. i guess the next thing to test is if i can just leave gprs on (making sure it doesn't try to do anything) and see how things go.
Dear All,
I wanna have some quick facts: Who have WM5 alarm not wake up issue?
The issue is- when you have scheduled an alarm (e.g. a morning wakeup call) and then suspend your unit, it fails to launch the alarm. When you turn on the unit, usually the unit realize the missing alarm and then re-sound the alarm for you. (Which is too late :evil: )
For people who encountered such issue, please enclose the following details:
1. Hardware (e.g. Qtek 9100, Dopod 838, i-Mate K-Jam, O2 XDA Mini S, etc.)
2. Firmware distribution and version:
a. IPL
b. SPL
c. GSM (hehe not quite related I think though)
d. OS
For me:
Hardware: Dopod 838
IPL: Qtek 1.01
SPL: Qtek 1.01
GSM: MDA 1.12.10
OS: O2 Mini 1.5.4.2
i have this issue only using spb time.
The internal alarm works without problems.
ROM 1.6.7.1 WWE
CPU OMAP850
WIZA200
OK, not all fact, but what i thought (until today) from reading many many posts.
1) Bad app design, no fix, wait for new ROM (possible, probable infact but maybe not)
2) When you change the alarm and standby the device before the alarm settings were saved properly (thus, when the device wakes it finishes the save and realises its past the alarm time) this is my fav answer!
I've had the problem in the past using my O2 mini-s UK with ROM 1.5.4.2 WWE. I started leaving the device for 2 min from setting an alarm to entering standby - no more problems.
Til today..
Yesterday i set the alarms like normal, used the phone for over 2 mins then entered standby with the mains charger plugged in.
At 4 am my 5 am alarm woke me, i turned it off, realised the time, almost threw my wizard out the window & went back to sleep for an hour. For info - the alarm WAS set for 5 am, the clock WAS right. Even when the alarm was going off it told me it was a 5am alarm & the clock was saying 4. The alarm then worked properly at 5.
Until there is a real fix for this i cant trust my phone to wake me, my old nokia's could manage the time & alarm, but the Wizard seems to find it too challanging
my 9100 does this all the time now. bugs the hell out of me.
i haven't heard of any other wm5 devices having this problem which might mean it's a wizard issue rather than a wm5 issue ?
:-(
It is a very common problem:
http://forum.xda-developers.com/viewtopic.php?t=31895
Please read through that thread first - and if at all possible, reply there.. unless your reply would be specific to the information requested by the poster here.
For what it's worth, I stand by my recommendation in that thread: just don't let your PPC go to standby, and use any of the freeware apps out there to turn the display (not just the backlight) entirely off. Your battery will drain only a *slight* bit more, but you will not run into the issue discussed here.
not sure where to reply. Probably here, it is less crowded and it is more of a WM5 topic here than a hardware topic there.
Anyway, just to let you know I have a MDA Compact 2 (aka HTC Charmer) which runs WM5. The alarm seems to worked fine so far. I have it set to 7am all day, using a the standard WAV sound. Works well.
I'm not sure if this matters, but the alarm works when it is in standby mode (aka one button will switch it on instantly) BUT it doesn't work if I had the device switched off (aka needs to bootup upon switch on).
And, the only problems that I had with the alarm is when I have a VERY big WAV file in it. The last time I had a 3.0MB WAV file as my alarm sound, the 'Reminder' failed to pop up and the alarm keep sounding. And if you had another alarm on it will still sound it together. Bit like a mixed up WAV in the system. Other than this, the alarm works well in Charmer.
I recently have a Dopod838 (I think) ROM (WM5) flashed into it and the alarm still works alright. Hopes this info helps.
Heya,
Yeah, if the device is entirely off (i.e. needs boot-up), then no alarm/etc. will run at all. In that mode, there is only enough power for the device to react to the button press to turn it on. This is similar to switching a regular mobile phone completely off. You'll miss any calls as well
I get the same problem, I just leave my phone on all the time.
ZeBoxx said:
just don't let your PPC go to standby, and use any of the freeware apps out there to turn the display (not just the backlight) entirely off.
Click to expand...
Click to collapse
If this helps, I use Pocket Candy as a screen saver and change the default s/saver to 'blank screen'. (Unsure if this completly turns the display off) but my phone fully charged with regular use (camera & vids as well) will last around 36 hours...
Pocket Candy can be found HERE:
I don't know how much people have been thru the same problem in wm2003;the reason why I have started this thread is to find out if there is an OEM secretly fixed the bug already. The time when I am using wm2003, OEM never really admitted the bug is fixed, but in fact the bug is gone after certain version of rom.
so hope everyone could post if you have the problem or not, as well as the detail rom version, so we could know if we could avoid this problem.
after I tried Menmaid and most all the solution on the internet out there, my alarm still not wake up from standby mode...
But yesterday, I found if i enable "voice commend" (which I disabled previously), the alarm will wake up from standby mode.
Hope that helps, my is MW 6.1
Everyone,
I have a strange problem with my prophet, I have tried about 3 diff wm6 roms so far from this site.
And once flashed my phone randomly seems to wake up.
The screen will flash and turn on for now apparent reason.
Any thoughts?
My mate who has a wizard has the same problem.
cheers,
Mike.
Could it simply be the active sync error (it keeps automatically starting up)?
If so, just do this:
Open Activesync on your device and tap on Menu>Add Server Source. Add any info to create a fake server sync. After that is complete go to Menu>Schedule and change the two dropdowns to "Manual" and tap "ok" at the top right. You can now go to Menu>Options and delete the Exchange Server setting you just added.
I have the same problem since I installed WM6 Underground yesterday.
I've tried your solution but it doesnt work (it still occurs after a soft reset).
Anyone else has a solution? This is so annoying
Try locking the device
I have noticed the same thing but it's going away if I'm locking the phone (only the power button remaining enabled).
yes this is happening for me using the ASERG 3.12 WM5 ROM.
It's really irritating as it seriously drains the battery. Went down about 30% last night.
Also waking up means running all sorts when the phone is in my pocket.
Short battery life causes me big problems as I travel a lot......
I'm thinking of going back to one of the less troublesome WM5 ROMS. I gave up with WM6 due to the loss of BT, GPRS and Wifi settings after a soft reset.
I'm sure one of the geniuses will fix all these issues soon.
cheers!
this has been fixed - http://forum.xda-developers.com/showthread.php?t=299069
Your waking up problem could be an faulty radio side-effect, it thinks it is receiving a call or sms and wakes up.
The most reliable radio rom right now is 2.61.21. You can upgrade to that without losing any data, and it fixes all call and sms, BT and Wifi issues. I applied that to a Jester's WM5 and solved all my problems plus got a better battery life.
I don't know much about anything but I noticed that I don't the sleep of death problem unless someone calls me when in standby mode. Most of the time everything is OK but a bout once a day here it comes. Now, I'm in Israel and the radio version seems to be ancient so it might not be the problem for everybody but who knows?
Ermmmm
My money is still on ActiveSync running as a schedule..... not likely to be Radio stack related I'm afraid.
are you using spb mobile shell??
elivne said:
are you using spb mobile shell??
Click to expand...
Click to collapse
I'm using SPB Mobile Shell. Mine randomly freezes and I get the SOD all the time. Think it's related?
ThaiM said:
I'm using SPB Mobile Shell. Mine randomly freezes and I get the SOD all the time. Think it's related?
Click to expand...
Click to collapse
yup.
upgrade to 1.5 - it's much more stable.
Personally, I think it's related to the battery. More specifically, how the battery charges.
If I perform a soft reset after charging the battery, I never get the 'sleep of death' problem and never have sudden battery drainoffs. If I don't do a soft reset after charging, within an hour I'll be unable to wake it up again. If I for some reason don't touch it for 8-9 hours, I can find the battery has drained.
The device is also a lot hotter after charging it. During the charging cycle the device doesn't get warm, only afterwards. This says to me that there's some problem where the device still thinks it is plugged in and ends up putting too much of a drain on the battery.
It's a good idea to perform a soft reset after every charge cycle. If you do this I think you'll see this problem disappear.
Interesting idea Doom Tints
This battery problem would explain some people's problems with leaving the phone charging overnight (i.e. halfway through the night the battery finishes charging and then the problem occurs), but other's observations (including mine) wouldn't fit this explanation.
SOD is happening across all ROMs, both WM5 and WM6 - but not predictably. The fake-server trick works for some people, but not for others. Some people say SPB software is the culprit, but there are plenty of people without SPB software who get SOD.
Could it perhaps be not the radio exactly, but the radio and how it works with the OS? For example, maybe people who flash to WM6 but leave an older radio version on their machine...?
Or could we perhaps be dealing with multiple problems that have the same symptom?
I'm not sure that you understood what I said judging by your response. It doesn't lock up WHILE charging, but sometime AFTER charging.
Just for giggles, try what I suggested -- perform a soft reset after the next time you charge it and report back the results.
I dont have the problem and this is what i have installed:
herm200(tytn)
all black versions and now majik.
radio 1.41(and had all the older versions since 1.27 - never froze).
i charge it over night and no freeze.
I used push mail and stopped(no change in freezes - none!)
once a day i SR to get leaked memory back.
spb shell 1.5
htc home plug
o2plus
sktools
resco file explorer(without the today plug)
spb time
all are working - had no freeze months.
Yes, but you are soft resetting every day.
I don't have any spb programs and in fact all I have is VC, PI and some medical programs. Don't have any battery issues and have not tweaked the phone at all - have all original ROM and radio. Left to charge for the night without any problem but then again nobody called me
I don't know
My Opinion
been running through threads all over, just found out that there is no solution, because when a program pushes the unit to wake up from standby it freezes, this program can be weather, alarm, mail, active sync, and even a CALL can cause this, so it's a permanent bug in wm6 and PPC :-(
nickbei said:
I don't know much about anything but I noticed that I don't the sleep of death problem unless someone calls me when in standby mode. Most of the time everything is OK but a bout once a day here it comes. Now, I'm in Israel and the radio version seems to be ancient so it might not be the problem for everybody but who knows?
Click to expand...
Click to collapse
Yes you were right;
I had the Standby of Death SOD this is when the phone fails to come out of standby with a power button press. This issue only affects some people on some networks. I'm not sure if its a network problem or a software problem but as only a minority of people have it, I suspect its mainly a network problem there is a software solution.
The solution is to change the phone settings band option from auto 3G/2G to either 3G Only (WCDMA + UTMS 2100 in Europe) or 2G Only (GSM + AUTO) depending on your requirements.
Also read this thread http://forum.xda-developers.com/showthread.php?t=540943&highlight=standby&page=2 where the resolution was to get a new SIM.
Obviously this only solves the problem when the crash is because of the sim and/or settings which impact the sim. To rule out a software cause its best to start with a hard reset.
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