Related
Hello,
I need your help with the following problem:
I have been using my Jasjar for 5 days now and I have a problem with the battery.
As soon as it gets to 35-40% battery power the unit switches off without any notice.
The only way I can turn it on again if I put it on a charger, and than it turns on again like after a soft reset.
I installed the latest ROM from the clubimate but none 3rd party applications.
Please let me know what can be this problem.
Thanks,
Zsolt
same problem here
Hi Ronaldovic,
Have you tried with another battery or just the original?
I was advised to change the original battery as that might be faulty but I couldn't get a new one yet.
Zsolt
For the O2 XDA Exec the battery has a 6 month warranty. You should check the situation with the JJ
battery issues..
I had similar issue and also where on switch on the screen light goes off and back on. This seems to be linked to battery chargin "top-ups" therefore sometimes the supply from the battery is not continously smooth. Try fully draining your battery and charging fully
I have same problem with my Exec. Any solution ??
I buy new battery but...when it gets to 25%, still switch off. So I dont think it's error of battery, may be it's bug of ROM for Exec???
kzs70 said:
Hello,
I need your help with the following problem:
I have been using my Jasjar for 5 days now and I have a problem with the battery.
As soon as it gets to 35-40% battery power the unit switches off without any notice.
The only way I can turn it on again if I put it on a charger, and than it turns on again like after a soft reset.
I installed the latest ROM from the clubimate but none 3rd party applications.
Please let me know what can be this problem.
Thanks,
Zsolt
Click to expand...
Click to collapse
1 month ago I have same problem. I think is not battery.
I make upgrade by all the ROM (JAS JAR, QTEQ, MDA PRO ecc.) but the problem I have not resolution, and 2 week ago my pda (MDA PRO T-Mobile) go in htc warranty.
Sorry for my bad english.
I have also noticed this problem a few days back. My Jasjar switches itself Off when the battery goes down to 22%.
I never used to have this problem when my Jasjar was with the original factory installed ROM version which was 1.13.53 WWE, Radio 1.03, ExtRom 1.13.137 WWE. When this ROM was installed I used to get the first low battery alarm at 20% and when the battery went down to 10% the screen would dim out and the SD card would deactivate, but still the unit would not shut itself out.
I installed the updated ROM when it became available in March which is 1.30.76, Radio 1.09.00 and ExtRom 1.30.164 WWE.
I am not too sure if the problem is linked with this ROM as I usually never allow my battery to run that low. However a few days back when I forgot to charge my battery I noticed this problem. I repeated this deliberately a number of times and each time the Jasjar shuts itself off exactly at 22%.
Just wondering if there are any solutions yet.
Regards
Same here, device just dies @ 26%. Was going to buy a new battery, but that might not resolve it?? *sigh*
RE
This battery issue has been discussed in two other similar threads.
In my case I just changed the default battery to a OEM one and everything works fine :lol:
Isn't the default battery an OEM battery? I'm tempted to buy one of the 1750 mAh batteries off of ebay (original JasJar battery is 1650 mAh) - is that a bad idea?
Try overnight charging of the battery for one or two days..this will solve yr problems... :lol:
Hi,
hard reset to your device, don't forget to get backup contacts, sms and data.
battery issue
I've had similar issues. Screen goes blank when battery low, plug in to charger and all is ok. What I've found is sometimes, not always, the battery screen brightness has gone to 0, but on-mains is set for full brightness. I never changed it, so maybe the device is trying to save power itself.
MNB.
Same here. My Jasjar dies sometimes when the battery is on 60%, 50%, 30%, 20%. etc. If I use the internet or camera or something then it will go dead, but not everytime.
Sometimes I can use anything and it will last till about 10% when the SD Card disables, then I charge it.
Don't know what to do. I don't want to buy a new battery if I'm not sure that is the problem.
Yes the same on my O2 Exec. Crashes at around 32% no matter what. Only remedy is to put it on charging again.
This started after I upgraded to the lastest O2 Rom; prior to that there was no problem whatsoever and I could go down to single digit battery percentages without any issue.
Is it the new ROM? Is there any work around to this malady?
Thanks to all who reply, in advance.
Cheers.
Well judging by the number of threads on the subject this problem is very widespread, check out the threads below:-
Jasjar shut down when battery power remaining is less then 43%
http://forum.xda-developers.com/viewtopic.php?t=51567
XDA crashes at less than 25% power after ROM upgrade
http://forum.xda-developers.com/viewtopic.php?t=47764
My QTEK 9000 (Universal) blacks off at 38% battery power?
http://forum.xda-developers.com/viewtopic.php?t=52353&postdays=0&postorder=asc&start=0
Power button not always working.
http://forum.xda-developers.com/viewtopic.php?t=47535
Poor battery life after ROM upgrade please help
http://forum.xda-developers.com/viewtopic.php?t=54649
perhaps it is heat related?
XDA Exec keeps randomly soft-resetting
http://forum.xda-developers.com/viewtopic.php?t=54066
-----------------------------------------------
So can we say that downgrading does not fix it, or removing certain software combinations?
has anyone actually proved that replacing the battery works or not?
With the issue this widespread (and across carriers) has anyone tried to contact HTC about this? I still have my doubts that this is ROM related, seems more likely to me that many of the initial batch of batteries have gone bad.
My battery is on order with expansy. Expect it in the next 4 to 5 days and will definitely let you all know of my experience with the new battery
Regards
I have an XDA Exec and I have just upgraded my ROM to the newest QTEK version. Since then, I have noticed that it crashes and reboots when the power level showing on the power meter reaches about 25%. I don't believe this problem was occurring before the ROM upgrade.
Although it stops working when 25% power is showing, I do not think that the battery life is actually reduced at all. It seems to me that it is more like the guage is inaccurate now and the power is really near zero when it crashes.
I wondered if the power guage needs recalibrating in some manner after the ROM upgrade because the settings have been lost. I know that some laptop computers need their batteries to be calibrated on first use. Does anyone have any ideas or information on this?
Thanks
Mark
Mark,
did you ever solve this issue? I have the same problem. Thanks for anyone's help.
Have only just noticed but im having the same problem to so annoying
Bad news, I am afraid. It is a harware fault and needs a repair.
In the end I returned my Exec to O2 under warranty. I got it back last week but they had forgotten to return the battery. After a phone call they sent me a free brand new battery by next day delivery.
Unfortunatelyt this means that I can't say for sure whether it was a battery problem or the phone itself. The covering letter with the phone said they had found a fault and repaired the phone, but since it seemed to be a stock letter, I can't be sure.
Anyway, my Exec certainly works fine now. I can get down to less than 10% with no crashes. I definitely did not have anything to do with the ROM upgrade.
Mark
Bad news, I am afraid. It is a harware fault and needs a repair.
In the end I returned my Exec to O2 under warranty. I got it back last week but they had forgotten to return the battery. After a phone call they sent me a free brand new battery by next day delivery.
Unfortunatelyt this means that I can't say for sure whether it was a battery problem or the phone itself. The covering letter with the phone said they had found a fault and repaired the phone, but since it seemed to be a stock letter, I can't be sure.
Anyway, my Exec certainly works fine now. I can get down to less than 10% with no crashes. I definitely did not have anything to do with the ROM upgrade.
Mark
Mark,
Thanks for the reply. That was not what I wanted to hear! I am going to continue playing around with it; I can't believe we're the only ones to have this problem. Let me know if you get any more news. I'm getting tired of sending the HTC in for repairs.
i-mate crashes with battery in less then 43%
My i-mate continues to crashes with the battery is less then 43%, apparently the problem occurred when I make the upgrade to ROM Qtek WWE_13077_130176_10900, was looked like that this version has something that change the battery configuration, since Qtek 9000 comes with 1750 battery mAh? I reinstalled the i-mate ROM 1.30.82 and the problem persists?
I made a test leaving the i-mate on, without using the radio until the battery settings showed 23%, then I made a phone call, the i-mate crashes in seconds. Somebody could inform what is the true voltage of the battery in the i-mate when it is 100% and when it is 10%, at the Main Battery settings?
Battery problem...u ccan verify this by using a differrent one may b from yr friend...
I have the same problem, its only started happening after the ROM upgrade from o2, before it would run down to 0% no problem but now it gets to 25% crashes and i have to reboot it and turn the backlight of otherwise it crashes again. Are you sure its a battery problem because ive had the same battery for 6 months and the problem only started after the upgrade.
Thanks to all of you guys for adding comments. Good to see others with the same problem. Misery loves company.
Anyhow, I can't exactly say my problems started with a ROM upgrade. I have two used universals. Here's my story:
PDA#1. Upgraded with previous Orange ROM as soon as I bought it and started having the 25% crashing problem
PDA#2. Never had crashing problem, upgraded latest Orange ROM, down to nearly dead battery today and no crash.
Hmm, to test the bad battery theory, I will swap the battery in PDA#1 with the battery in PDA #2, and if I get a crash, I can blame it on the battery. Otherwise, it's the OS. Both PDAs have EXACTLY the same programs installed from fresh ROM upgrades.
Battery test
Hi PDAholic.
Which was the result of the test with the battery.
Hi
See my previous post in this topic. I can confirm that my problem seemed to start when I upgraded to the newest QTek ROM (from original O2 ROM). However after it has been returned to O2 for a repair, I have once again upgraded to the same ROM and now it works fine.
So, it must ether be a hardware fault on the Exec or a battery fault. My evidence is not consistent with it being something to do with the ROM version.
Anyone have definitive information on this problem?
Mark
Mark: I thank you for your post--but you have to admit, there is nothing wrong with a little experimentation!
Josedias: My experiment is still underway. I will say that taking out the nearly dead battery from non-crashing pda and putting it into the crashing pda did not result in the latter pda crashing. However, I am now waiting for the battery from crashing pda (which is now in non-crashing pda) to die. If it does, the problem is the battery. I actually have another theory if none of this pans out, which I will present with my next post.
Pdahollic
Will be good to hear what your fndings are.
I spoke to o2 today and told them about the problem with the battery they tried telling me that it was software related then i told him that i was using the latest software from there website and he was like hmmm ok let me put you through to returns. Got put through and the kind person that i spoke to there said just to pop it in the post with the returns number and will send you out a new one the same day.
So i should hopefully have a new 1 by the end of the week will let you know if i have any problems
Okay, interesting results here...
I was actually unable to reproduce the shutdown on either PDA, with either battery!
I have a theory why, and perhaps those of you with the problem could try and see if it fixes your devices.
When I started the experiment, I wanted both PDAs to be as equal (controlled variables!) as possible. So, I charged both overnight until the green light came on, then did a soft reset to both PDAs. I have a feeling this might have somehow reset the battery meters in both devices.
Pretty much all PDA manufacturers recommend when you first get a device to charge it to 100% then begin using it. I do know that when I did the ROM upgrade on the device that kept crashing, my battery was very low. So, I presume that when I started using the device, the battery calibration was way off. Say that the device thought the battery was at 100%, but it was actually only at 75%. When the battery discharged to 0%, the device thought it was at 25%, and thus did not issue any warning messages. Then, without warning, the device died and would not come on without charging (which is what mine did).
I don't know for sure if this is what has been happening, but it makes sense to me.
My next experiment would be to stick a near dead battery in a device with a fully charged battery and see what happens. Although, at this point I probably "ought to leave well enough alone."
Again, I suggest to all of you to charge the device overnight to 100% WITH THE GREEN LIGHT ON, then do a soft reset and see if your problem is solved.
I will keep you guys posted on any further problems. Good luck.
Hi everyone!
A bit out of topic but I could not find any other discusion that could relate to my problem which is also related to battery.
I've got this guy who bought a brand spankin new XDA EXEC straight from Taiwan and the lame ass used it for about 4 hours without preformating the battery until it seized on him. It happend at the time of Active Sync instalation.
It did not die out sooner because he had it connected all the time to PC via USB cable thinking that this will charge the battery.
Now all he can see is the O2 welcoming screen and the ROM initialization figures.
Any ideas guys? I feel sorry for him and am trying to help him somehow.
I presume he has tried to do a hard reset (both softkeys, reset button and power). If that doesn't work, he could put it in bootloader mode, disable USB, and try reloading the ROM. Make sure he realizes that it takes a LONG time to soft reset the Universals. A common nube mistake is to keep hitting the reset button thinking it has locked up on the splash screen. Not that I would ever have done that...
I received a T-Mobile MDA Pro on tuesday and it has the same problem - but, my battery seems to die at 50% and will only power back on when the charger is plugged (mains or usb) in?
Hi guys ive just been on the phone with o2 and i have been told that it is indeed a hardware fault and that i will be getting a new one back from them in the next few days.
Qtek 13077 ROM ????
Could somebody inform what is the true voltage of the battery in the i-mate at 100% and when it is 10%, in the miter?
I have charged the unit till 100% led = Green, then soft reset, the problem persist?
Now I am 100% certainty that the problem occurred when I made upgrade to Qteck, we needs to investigate what the the Qtek ROM this doing with the JasJar?
First off, I have seen many threads on the MDA PRO (and all its variants) cutting out at high battery power levels and from what I can see there doesn't seem to be any concrete resolution. But here is my situation.
I bought a new sealed MDA Pro and immedialy flasshed to the latest T-Mobile rom. Thats where the problems began. I seem to be plagued by the MDA cutoff at 60-70% problem.
The way it manifests is the radion loses signal and cannot locate the carrier at or below 70%. At this stage a reset of the device and it reboots but as soon as you use the phone or wifi it crashes .. black screen.
As with others if I connect the USB cable and charge by PC or mains everything returns to normal. Not a very mobile solution!!
I have tried every variant of ROM out there and the problem remains. I have charged the battery for 16 hours etc etc. I have tried phone in Auto, GSM modes .. same problem :!:
The only thing I haven't done yet is buy a new battery and hence my post.
Will the purchase of a new battery solve the problem? As with other threads it would seem this came along with the latest roms. Does flashing a ROM when the battery is less than fully charged cause problems?
On a final note, if after the radio loses signal it is turned off I have been able to run the device down to 20% running videos and MP3. Is this a probem with radio levels above1.09.00 (Just thinking out loud)
HELP: This device is perfect for my daily use and having purchased a less than mobile device I am now close to getting rid .. but I dont want to
Any advice greatly appreciated... expecially from those who have fixed the problem.
I had this problem and a new battery fixed it.
Thanks. Look slike a new battery
There seems to be different speculations on what causes the battery problem on the Universal: the power charge cable quality theory, one idea about the battery level stored inside the batter which some claimed to registry heck could change and another idea about the battery 500 charges limitations.
But if yours is brand new, then none of the above applies... So the refresh to a new Rom definately must have something to do with it. Wonder anybody who had bought a new replacement battery after the power drop had done another rom refresh and whether the same problem returns?
I have just bought a replacement battery (1800m Ah at standard size by MoMax which gives me another 30% more power everyday which is something good I got from paying for a new battery) yesterday to change the old one out for the same reason. Looks like until someone found the real cause, I am keeping the old one for my next rom refresh...
New Battery ... problem resolved.
Can someone please help me? I just bought a used MDA but it has several problems with it. Here are the problems:
1) The phone has been damaged which causes it to not switch the keyboard light or backlight off at times, and also, when returning from sleep or standby, unit reacts as if the dsown button is being pressed and continues to move down until the d-pad is pressed.
2) Phone depletes both the included battery, the spare battery AND another TESTED AND WORKING MDA battery much faster than normal(1% in 2 minutes or less while idle).
Does anyone have any ideas what could be wrong? Its not Windows because I already updated the version twice and it didnt fix the problem.
BklynHitman88 said:
Can someone please help me? I just bought a used MDA but it has several problems with it. Here are the problems:
1) The phone has been damaged which causes it to not switch the keyboard light or backlight off at times, and also, when returning from sleep or standby, unit reacts as if the dsown button is being pressed and continues to move down until the d-pad is pressed.
2) Phone depletes both the included battery, the spare battery AND another TESTED AND WORKING MDA battery much faster than normal(1% in 2 minutes or less while idle).
Does anyone have any ideas what could be wrong? Its not Windows because I already updated the version twice and it didnt fix the problem.
Click to expand...
Click to collapse
What ROM are you using?
What are your IPL/SPL?
What apps do you have installed?
Do you have your IR, bluetooth, Wi-Fi, or any other battery draining resources turned on?
If you did in fact do a ROM upgrade did you flash to a full carrier rom after your CID unlock prior to flashing to a custom rom?
Does the battery in fact go dead when it hits 0%?
Was your battery at 100% when you did your last flash?
When was the last time you calibrated your battery (let it fully discharge then recharge overnight before using device again)?
OK... I'm no expert but i'll answer these as accurately as possible.
If by ROM you mean windows version... then I just updated to the latest version from TMobile.com
I'm not sure what IPL/SPL is.
No apps are installed.
No WiFi, Bluetooth, etc.
Phone was not unlocked.
Battery has never hit 0% so I'm not sure. Will test that immediately.
Battery was at 65% and charging when last flashed.
Never calibrated the battery.
I'm sorry if any of these details are vague or inaccurate but, as I said, I am new to this. Thanks for any help in advance!!!
Well I'm new to this but I successfully CID and SIM unlocked my phone and now I'm running Titanium V2 (WM6) So I can at least tell you if you updated to the current tmobile rom your running IPL/SPL 2.26 Hope this helps.
BklynHitman88 said:
OK... I'm no expert but i'll answer these as accurately as possible.
If by ROM you mean windows version... then I just updated to the latest version from TMobile.com
I'm not sure what IPL/SPL is.
No apps are installed.
No WiFi, Bluetooth, etc.
Phone was not unlocked.
Battery has never hit 0% so I'm not sure. Will test that immediately.
Battery was at 65% and charging when last flashed.
Never calibrated the battery.
I'm sorry if any of these details are vague or inaccurate but, as I said, I am new to this. Thanks for any help in advance!!!
Click to expand...
Click to collapse
When you turn on the phone do you see a screen that says IPL 2.26 wiht SPL 2.26 right under it? If you don't then you may have a problem. You said you used a rom from T-Mobile.com so you should have the latest released WM5 build from them and this is good provided the flash was 100% successful.
2 things to try for keyboard light and battery drain:
1. Start -> Settings-> Personal -> Buttons -> Backlight tab
toggle this check box. (unchecked should light keyboard after first key press, checked would light keyboard after first key press only if sensor determines not enough light
2. Start -> Settings -> Connections -> Beam
Make sure the Receive all incoming beams box is unchecked. Otherwise your IR will always be on and looking for signals. Most Comm Managers no longer include the button to turn this off/on in Comm Manager. This can be a big cause of battery drain especially if you are moving around active IR signals that your phone can see quite frequently.
Other than that battery life tends to stabilize over time after the battery is calibrated. Of course you can always try a new radio rom as well as the one that comes with the rom you installed might be excessively searching for signal or switching between two competing towers as the signal strengths vary. The best radio for most users regardless of rom is the T-Mobile UK radio 2.19.11 (I am pretty sure there is a link to it in the wiki) You may have to CID unlock or use the shelltool to flash it though.
Probably the biggest bang for the buck is the radio. I would switch to the 2.19 radio, this is most likely your issue (as far as battery life goes) Of course each person's experience is different so you may have to try multiple radios to find which works the best in your particular coverage area.
Hope this helps.
Thanks for all the quick replies. I'll try the battery saving tips ASAP.
Does anyone have any idea why t could be geting stuck in a downward loop every time it wakes up?
Hi guys.
My wizard battery lasts less than a day. I hardly use it. Wifi and other radio are off most of the time.
I tried changing ROMs, radio roms etc. I even got a new battery but to no effect.
Any help ?
I had that problem until I found out that activesync was staying active even after I unplugged the cable. I never found a way to keep it from doing that though so now I just make sure activesync is shut off wheneve I disconnect it. Kind of a pain, but it beats the battery dying on me.
Well ill make sure Activesync is off.
But do you think the problem would persist even after I changed roms!
It did on mine. It's something to do with activesync itself apparently. It doesn't stay on as often as it did when I was using T-mobiles ROM, but it still does it occasionally.
make sure your extrom is ok, because a corrupt extrom is also a cause of battery drainage, better yet there was a rom floating that only erases your extrom (blankextrom), i forgot who made it but its from the wizard forums
found it, go to post number 7, look at the sig below there is a link for the blank ext rom, enjoy
http://forum.xda-developers.com/showthread.php?t=311225
guys, please take a look at here, i think we have the same issues, but i have the t-mobile wing (htc herald):
http://forum.xda-developers.com/showthread.php?t=319897
Maybe your battery is bad. Buy a new one on Ebay for small cost. I bought mine for like 7 euro`s including shipping (battery itself was € 3,5). Also disable mail fetching every few minutes.
GaMeR64 said:
Maybe your battery is bad. Buy a new one on Ebay for small cost. I bought mine for like 7 euro`s including shipping (battery itself was € 3,5). Also disable mail fetching every few minutes.
Click to expand...
Click to collapse
i tried two different NEW batteries straight from tmobile and the problem persists. and mail checking is on manual, which means only when I click send/receive
I'm pretty sure mine was caused by activesync running even though it wasn't connected because ever since I started making sure it wasn't running after disconnecting it from the cable my phone hasn't had that problem at all.
xeno1 said:
I'm pretty sure mine was caused by activesync running even though it wasn't connected because ever since I started making sure it wasn't running after disconnecting it from the cable my phone hasn't had that problem at all.
Click to expand...
Click to collapse
i end-tasked (closed) activesync from running in my phone when i went to sleep, and when i woke up i lost 50% battery again, (with all radios off)
Some programs can drain the battery. As an example, I really like PhoneAlarm, but it drains the battery tremendously, I think it's because it polls different system parameters. This polling causes the battery drainage.
Also, the way to stop activesync from turning on by itself it to create an exchange server account. I use mail2web, it’s free. After you set up the account on the phone, when you go to the activesync menu, hit schedule, then set it up for manual.
After I set this up, I never have a problem with activesync. You can do a Google search to get the step-by-step directions on how to set it up.
Also, charge the battery with the wall power cord, try not to use the USB power. Each one uses different circuits in the wizard. I also let the battery drop below 10% before I charge it. My battery lasts about 4 days.
nvgear said:
i end-tasked (closed) activesync from running in my phone when i went to sleep, and when i woke up i lost 50% battery again, (with all radios off)
Click to expand...
Click to collapse
Like calouro said, there are other programs that can drain a battery pretty quick, mine happened to be activesync. Since you shut it off and you still get battery drain then yours must be a different one, possibly a today plugin if you didn't have any other apps running in the background.
Just had a thought, you don't have any today plugins such as weather panel that are set up to update over gprs on a regular basis do you? If you're turning your radio off and it can't update it may be trying over and over to update and draining your battery.
no i don't have any today-addon or plugins, i have batterystatus installed but this problem persists even without batterystatus and it does this even after a fresh HARD reset, which tells me this is a manufacturer's program or hardware causing this flaw, i'm not the only one with this problem, there are others, look at our discussions here: http://forum.xda-developers.com/showthread.php?t=319897
Yah, I read that post. Did you try not turning off the radio over night and see if that sloved the issue?
I've changed batteries. Using a brand new one now.
No active today plugins or anything else. Dont even have activesync running. Made sure I exited that. Still no help!
how did you flash?
i think it may be extrom prob, as someone said earlier. if you are flashing with shelltool, extrom(corrupted or not) is not replaced, when its broken, shelltool rom change will not help.
second thing is "fake connection" for activesync to stop it from turning on and on in searching of sync.
third thing is using soft, that is waking up/keeps machine awaken somehow...
xeno1 said it all before...
i think it may be something installed from good extrom too(extrom holds programs which are installed after first boot)....
one more thing:
after >60 flashes i noticed, that level of battery while flashing may be reason of fast nrg loss.
If it was 50%, machine(even charged to the max after flash) drops fast to 50% then drop slows down - wise thing is to let it discharge to ~5-9%, then charge to the max. After 1-2 such operations battery is ok.
It is useful, even if battery was full(machine "learns" about battery as it is new - sth like that).
there are no miracles.
sorry for funny english..
HEre's something funny that happened.
Before flashin a blank extended rom I had 73% battery. Once the flash was over I had 100% battery.
Now I'm tryin to drain the battery with backlight and phone and wifi continously on. Once that is done, I hope things will get better. I'll keep posted with what happens.
Even after a full recharge, the battery now doesnt last even 12 hours. And this is me not using the phone at all. It's just been switched on and kept that way.
And no thebacklight doesnt stay on, or the phone doesnt stay on (it goes into the standby mode as it should)
xeno1 said:
Yah, I read that post. Did you try not turning off the radio over night and see if that sloved the issue?
Click to expand...
Click to collapse
yea if i don't turn off the cellular radio then the battery only loses about 1-2% overnight (9 hour sleep).