Related
Hi all,
I've just spent a good amount of time browsing these forums - lots of good info here!
I've got my hands on a free i-mate jasjar from work as it is having battery issues and they just upgraded the user.
The issue is that it drains the battery in about 3-4 hours - thats with no sim in, phone / wireless / bluetooth turned off, very minimal use. We got a new battery for it in case that was the issue but it still loses it...
The other ones we have at work get at least a day / day and a half depending on usage.
I've reflashed it to the latest i-mate firmware (1.30.76 WWE) but stilll no luck....
Aside from sending it off for an expert to look at - does anyone have any suggestions on what i can do to diagnose / fix the problem?
Cheers
Sam
disable activesync checks
in wm5 activesync checks every 10 minutes or so for new data even if you do not have a server installed.... so.... here are the steps.....
with the device disconnected from the computer !
1. click "start"
2. click "programs"
3. click "activesync"
4. right soft button "menu"
5. click "add server to source"
6. fill in "1" in every field clicking "next" as you go through the proccess! (or any other fake data you want)
when you get to choosing what to sync, uncheck everything and click "finish"
7. right soft button "menu" again, now you'll have "schedule" lit
8. click "schedule"
9. change both drop down menus to "manually" and uncheck s"end outgoing items immediately"
10. click "ok"
11. right soft button "menu" again
12. click "options"
13. select the "exchange server", click "delete" and "yes"
14. click "ok"
YOUR DONE !
the device should last a lot longer !
have fun !
p.s.
don't forget to disable IR so the device won't try syncing with the sun ....
Great - I've set it up and will test it out over today - thanks for the reply
Make sure your infra red is also off, receive all beams is unticked.
Presumably you're not using any over clocking software? They disable the idle mode detection so make the battery less efficient, even at slow clocked speeds.
V
Infrared is off, currently its got fresh firmware as off yesterday, charged overnight - no sim, every conceivable option turned off, no extra s/w installed.
Since 9am its now down to 85% - roughly using 10% per hour with zero use....
I have the Same Issue ,the battey use very fast .
at the first I think may be is the net lock make that, But yesterday ,I try to use the unlock tools ,but same as it.
the charge complete. close all function ,can't use more than 8 hour's.
I've the same issue,...change a batery with a new one, BUT when it goes les than 70% all the problem start, loose the phone signal, shot down....I've a official Qtek 9000 ROM of febr. '06
Andrea
Andre77ab said:
I've the same issue,...change a batery with a new one, BUT when it goes les than 70% all the problem start, loose the phone signal, shot down....I've a official Qtek 9000 ROM of febr. '06
Andrea
Click to expand...
Click to collapse
I think That's the Radio or Hard device error.
If other Rom have not This issue. I think that's this rom make it .
There are a number of threads regarding batteries and new ROM versions and I think the concensus is that its the battery and it is just coincidence about the new ROM.
I have had my device for about 8 months and it has behaved well until a few weeks ago when it started to shut-down at 70-80% battery. The shutdown only occured when I had a heavy drain on the device e.g. when using GPRS or phone and I started to think that the battery was dying and the heavy current drawn by the radio caused the battery voltage to drop below a sustainable threshold for powering the device - hence the shutdown. £20 later I have a new battery (from eBay) and can go 1-2 days without charging. I am leaving the old battery on charge for several days to see if it can be salvaged
weasel said:
There are a number of threads regarding batteries and new ROM versions and I think the concensus is that its the battery and it is just coincidence about the new ROM.
I have had my device for about 8 months and it has behaved well until a few weeks ago when it started to shut-down at 70-80% battery. The shutdown only occured when I had a heavy drain on the device e.g. when using GPRS or phone and I started to think that the battery was dying and the heavy current drawn by the radio caused the battery voltage to drop below a sustainable threshold for powering the device - hence the shutdown. £20 later I have a new battery (from eBay) and can go 1-2 days without charging. I am leaving the old battery on charge for several days to see if it can be salvaged
Click to expand...
Click to collapse
Thank you help, But I return to the old version ROM. the batteries is OK. I don't know how to explain them
Try measuring the power consumption with acbPowerMeter and post your results so that we can see your device indeed has problems or not. See my related articles for more info (cross-posted to the General forum in here).
My Universal power consumption
With BT on and Wifi off power is at 642 mA...
Is it bad or good?
durius said:
With BT on and Wifi off power is at 642 mA...
Is it bad or good?
Click to expand...
Click to collapse
What that's mean?
it means that the device has bt turned of, and also wifi turned of and acbmeter indicates a power consumption of 642
I also seem to have started incurring a problem with battery, it is shutting down the device at 50%, and yes there was a slight draing GPRS and Push Email running, and trying to make a phone call.
It only really happened today, and am at a loss as to the cause. I would guess, the battery is 1 year old and probably needs replacing.
i have been using two different 3.2 roms ltcmdr, then jw's for a while now and no problems until today.
I suspect its the age of the battery. I am in the process of trying to suck the battery down as far as I can, then recharge it.
It appears to do a complete shutdown every 2% from 50% to 40%, I am now trying to get it to less than 40%.
My original battery lasted me for about 8 months when I started experiencing the shutdown / hanging problem whenever the charge would drop to 35%. I replaced the battery with a new original battery and all went okay. Unfortunately my second battery is only 5 months old and I have started experiencing the same problem again although this time the problem is occurring at a charge level of 15%. When the battery reaches this level and I try to connect GPRs or make or receive a call the unit hangs. If I try to soft reset I cannot do so till I connect the external charger.
I think such a low battery life is simply unacceptable.
Regards
Ever wonder how a battery tells the system that it is full and to stop charging?
If you get a new battery, take the old one down to somewhere below 100% -then install a new ROM and see what the battery meter reads after the hard reset.
The system must recognize a point which would be monitored and recognized as "full battery". When installing new ROM's, the system takes the battery power at the time of the install as 100%. This is why it is reiterated in almost all ROM upgrade instructions:
"Your device battery must be fully charged before installing this ROM".
However, I'm not so keen as to have a fix; but I've noticed that when the battery is fully charged and the device is then unplugged, turned on and then off, then plugged back in...it seems to charge alot longer than what I would expect necessary to reach 100% once again.
dhob187 said:
in wm5 activesync checks every 10 minutes or so for new data even if you do not have a server installed.... so.... here are the steps.....
with the device disconnected from the computer !
1. click "start"
2. click "programs"
3. click "activesync"
4. right soft button "menu"
5. click "add server to source"
6. fill in "1" in every field clicking "next" as you go through the proccess! (or any other fake data you want)
when you get to choosing what to sync, uncheck everything and click "finish"
7. right soft button "menu" again, now you'll have "schedule" lit
8. click "schedule"
9. change both drop down menus to "manually" and uncheck s"end outgoing items immediately"
10. click "ok"
11. right soft button "menu" again
12. click "options"
13. select the "exchange server", click "delete" and "yes"
14. click "ok"
YOUR DONE !
the device should last a lot longer !
have fun !
p.s.
don't forget to disable IR so the device won't try syncing with the sun ....
Click to expand...
Click to collapse
Will still be able to browse with my device? thx
Hello all,
Let me start off the message by mentioning that I have been a (altogether) very happy user of cyanogen mods with my last 3 android phones.
The last and current (but it seems not for long) is an HTC One X, which is over 2 years old.
This poor thing has gone through so many ROMs that I have lost count.
It is currently running on a stable cm10.2.1, upgraded from cm10.1.3.
I have experienced sudden power offs when there were obvious battery drain, battery overheat, weird app installation issues, especially since moving to cm 10.2.1, which also caused the GPS to stop getting any satellite signals.
However, the phone has recently (a couple of weeks) leveled up into a bizarre mode:
It will power off all of a sudden, the battery levels are not low 65-75%, so I would assume it was just some process in the background, and go ahead and start the phone up again to go and check through the logs, or even disable/cleanup dodgy overreacting apps. But to my surprise, the phone passes the quietly brilliant screen, as well as the CM logo with the circling arrow and as soon as you can see the background it shows Powering off - the phone is shutting down.
For those brief couple of seconds I can see the battery indicator (top right corner) showing a small part of it in red, letting me believe the battery's status is critically low. So I let the phone charge for half an hour, and start it up again, with the same result, once the device goes past the logo and the background shows, the Powering off message appears again. The battery indicator is still showing a small red circulating section of the whole.
The next step was to go and check in recovery mode. The battery on the TWRP screen shows almost 70%, and this leads me to assume there is something wrong with the battery. But the phone is not turning off for as long as in recovery mode. I still haven't ruled out the battery issue, and will test it when I get delivered and replace the spare one I have ordered.
Reading through forums and other threads, there were people complaining that they had the same issues when the phone was trying to change from 2G to 3G and the other way around, so I removed the sim card and have restarted the phone, still the same result, powering off after boot.
I also reflashed 10.2.1 thinking that a clean installation will help getting rid of some new app/processes that might be causing this, but exactly the same powering off occurs after booting. The same happens even after a factory reset.
Usually, after half an hour of inactivity the phone would start up normally, but today it has been several hours and the behavior is not improving.
At this point I can't get into the phone other than on recovery, I can't copy from/into its storage anything, not even the nandroid backups I regularly do (and which stupidly I haven't copied over to an external storage). I could try reflashing some stock image, but even that I don't have on the internal storage.
So as you see, I am bit stuck. Phone will not stay ON long enough for me to connect to my machine and save my backups, or load any new stuff.
If you have any other suggestions other than this, or perhaps a workaround to what I have already tried, I would extremely appreciate it.
Cheers,
Mad
I have the same problem..
I have tried everything, but nothing helped me.
Now my battery is 0% and i cant do nothing - cant charge it, cant boot in bootloader.
Something heppened when you changed the bettery?
I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
manderson8898 said:
I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
Click to expand...
Click to collapse
Have you tried a factory reset? I'd make tmobile replace it
was hoping to avoid the reset button. Tried it and still giving trouble it rebooted while restoring apps. I bought the tablet on ebay, I don't think TMO will take it back. oh well I'll keep poking about.
thanks,
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Wall-E said:
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Click to expand...
Click to collapse
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
manderson8898 said:
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
Click to expand...
Click to collapse
Have you considered rooting and using root apps to stop the apps from being able to do such things?
Some people might have experienced a battery issue after the latest update. It can be solved quite easily. Even If you don't believe you have an issue with your battery, you should try this as it seems baked into the update process.
Just to describe my experience first. After update my battery was going from 100 percent to 20 percent in about 8 hours while idle. It wouldn't charge while it was on. I would have to turn off the phone to charge it. I could not figure this out, until I found similar issues on different phones in the forums. It seems that when an update gets pushed to your phone, and your battery is low, your current battery charge is cached as 'max'.
First I thought the connector on my charger was broken. Then I thought maybe the charge port on the phone was somehow damaged. Then I thought there was possibly a foreign object in the charge port. It is actually none of these things. It's a software issue. Here is the resolution.
You want to boot into recovery mode. This is taken directly from Lenovo's website on the Turbo 2, but please read my caveats at the end.
Power off the device and unplug it.
Press and hold the Power and Volume Down buttons until the device turns on.
From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Power button to select it. The device will restart.
An image of an Android robot with a red exclamation mark will appear.
Press and hold the Power button, while still holding Power, press and release the Volume Up button, then release the Power button.
Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
Press the Power button to select Reboot System Now.
This is basically the process, but you have to change up a couple things. After you wipe the cache, select 'turn off' rather than 'reboot'. Give the phone a minute to be sure it is entirely off. Plug the phone into a charger in the off state and let it charge fully. Once you are certain that the phone has been charged to 100 percent, you can reboot phone. Voila, back to almost 2 days worth of battery life.
It doesn't work for me, anyway thanks for sharing this info.
Wysłane z mojego XT1580 przy użyciu Tapatalka
I wrote this for X Style but it can be aplied to Moto x Force in the same way:
https://forum.xda-developers.com/mo...ide-improve-battery-life-performance-t3647155
I am having this issue, and sometimes Ampere shows the current draw at 2A even though the only thing I've done since power-on is run the Ampere app. I also have the green lines but that's been for much longer, so maybe there's a short but the issue started after an update not with the green lines. I'm suspecting something like a radio bug but unfortunately BetterBatteryStats requires root to do any real useful analysis (not possibly yet that I've seen with the VZWDT2). The only thing showing under usage is screen-on.
Wouldn't be ironic if it were an as-yet undiscovered crypto-miner? That hacker would be able to earn a huge bounty if they found permanent root.
Same problem here, any other solution? What's the best app to diagnose what's draining the battery?
I have done every thing with my turbo 2 , all given your tips i implemented on my mobile,
but still my phone battery not working well like working before update nougat. after updated nougat my mobile battery draining fast and after full 100 charge my mobile battery just work 3 and max 4 hours.
please launch any new update to resole this battery issue or give me some best tip to improve the battery work same work as before update nougat.
We are motorola users and we love this but company not support our users to actual solve this bad issue, really bad.
hope i hear from you with good news for users.
thanks & Regards,
I have tried multiple ways that I've found on the web, but still, my Turbo 2 has at best 3 to 4 hours of running time. Several months ago, I had the battery changed out. New battery behaved the same way. I'm convinced that Nougat is the culprit here.
Fully charged
Within an hour it went down to 68% and then shut down down. Any other fixes?
Just got a new battery fro the Droid Turbo 2
And it's working as it should. Apparently, the battery installed this past September was faulty.
After charging phone to 100 it will only work for short time and then it will randomly shuts down (usually the moment u use it, like unlocking the screen or getting a call). And then it wont turn on until u start charging. Sometimes when u plug it back in battery is at ~90%, sometimes it goes back to 0. I was thinking it was battery's fault but almost every time this happens my phone does some kind of soft reset, sometimes my themes reset back to stock, sometimes my saved wifi dissapear, notification settings reset, etc. Phone has the screen replaced a year ago too if that could add to it.
You can try to revert it to stock, but most probably is a battery problem.
I've been using my phone for 3 years already and a half year ago I noticed that id didn't hold a charge when the battery went below 30 % . it randomly shut down below 30 % epsecially when I tried to take photos or use flash (that require high Amperage) . Sometimes it restarted itself after unexpected shut down and as I noticed dalvik cache was formatted/deleted. so I had to login to my google account set themes and etc. after I upgradet to 7.0 every unexpected shut down began to worry me becaouse even app data began to dissapear. So a week ago I ordered a new battery and now I am relieved . in my opinion it's 100% battery problem .
Definitely a dead battery. 3 years is a long time for these batteries. You did well to get that long from it!.
Thank you for this thread. I was starting to go loopy because I thought it may have been some app. Same issue and I need to find a battery guy.
Sent from my HTC One M9