Related
My sensation currently has a power drain that I can't seem to find the cause for. I'm using InsertCoin 3.4.2 with bricked kernel 1.5, using SPB shell 3D launcher, got an Anker battery, running tasker to cut data, wifi, gps, etc whenever the screen is off, setCPU running ondemand with max at 1536mhz and minimum 192mhz, etc, etc.
I fully charged my phone to 100% about two or three hours ago, and it's been pretty much left alone since. It's now down to 68%.
I've got BetterBatteryStats and SystemPanel, both showing nothing untoward, no active tasks, no wakelocks from what I can tell, etc. And according to the standard app for battery monitoring, it shows the various connections have indeed been turning off as intended, and the phone has been asleep nigh on all the time it's supposed to be.
Any ideas what's going on, or how I could look into it deeper?
I've just been playing with the phone pretty much non stop since I started this thread an hour ago, and the battery level is now at 60%. So that means it's actually consuming MORE power when it's not even in use!
StuartTheFish said:
I've just been playing with the phone pretty much non stop since I started this thread an hour ago, and the battery level is now at 60%. So that means it's actually consuming MORE power when it's not even in use!
Click to expand...
Click to collapse
Hi,
There is a lot of talk about battery consumption,and it's causes.
Most people will suggest trying a different kernel,or downclock it to 1.2 GHZ.
I've tried different kernels already, and underclocking the cpu seems to make little difference. As I say, setCPU should be knocking it down to 192mhz whenever the screen is off anyway!
StuartTheFish said:
I've tried different kernels already, and underclocking the cpu seems to make little difference. As I say, setCPU should be knocking it down to 192mhz whenever the screen is off anyway!
Click to expand...
Click to collapse
Hi,
Is your ROM a 2.3.4 base or 2.3.5 ?
2.3.5 mate. It's InsertCoin 3.4.2, with sense 3.5 (which I'm not using in favour of SPB).
StuartTheFish said:
2.3.5 mate. It's InsertCoin 3.4.2, with sense 3.5 (which I'm not using in favour of SPB).
Click to expand...
Click to collapse
Hi,
I was going to suggest bricked 0.9.1 with a 2.3.4 ROM,because my son has had great results on his Sensation.
I do not know IC well enough to help.
Sorry.
No problem, thanks for your input anyway.
StuartTheFish said:
No problem, thanks for your input anyway.
Click to expand...
Click to collapse
1)Try his new test version of bricked(beta4).
http://code.google.com/p/bricked/downloads/list
2)Charge to 100
3)Turn off, wait till green, unplug and plugin(bump charging)
4)Boot to recovery thru bootloader and wipe battery stats and then reboot unplugged
Drain you battery to 1, then charge up and repeat for a few days. And you can lower the clockspeed since you're using ondemand, you won't see a speed difference with 1.2 and higher. Oh and use ultra smooth rosie so the home will be faster...And see which apps are open in B/G.
http://forum.xda-developers.com/showthread.php?t=1302914
With the exception of trying the beta bricked kernel, I've already done all that when I first got my anker battery. It's not a calibration issue, it's that something is actually draining the battery even when it should be asleep.
And that rosie change isn't needed, as I'm not even using sense in the first place. I've got no real issues with how the phone actually performs as everything is already perfectly smooth. The only slight issue I have is since flashing the amaze camera, on rare occasions it can lock up when exiting it, requiring a battery pull to get going again.
StuartTheFish said:
With the exception of trying the beta bricked kernel, I've already done all that when I first got my anker battery. It's not a calibration issue, it's that something is actually draining the battery even when it should be asleep.
And that rosie change isn't needed, as I'm not even using sense in the first place. I've got no real issues with how the phone actually performs as everything is already perfectly smooth. The only slight issue I have is since flashing the amaze camera, on rare occasions it can lock up when exiting it, requiring a battery pull to get going again.
Click to expand...
Click to collapse
Oops missed the part about SPB, I have been having similar issues but with Faux's kernel after using Amaze cam, but I doubt that could cause sleep drain. I think you drain is caused by the phone not entering "Deep Sleep", some rogue app is keeping the phone partially awake and sucking up juice. I'm gonna go on a hunch and say the phone is running around 1.x GHz while screen if off due to the app.
StuartTheFish said:
With the exception of trying the beta bricked kernel, I've already done all that when I first got my anker battery. It's not a calibration issue, it's that something is actually draining the battery even when it should be asleep.
And that rosie change isn't needed, as I'm not even using sense in the first place. I've got no real issues with how the phone actually performs as everything is already perfectly smooth. The only slight issue I have is since flashing the amaze camera, on rare occasions it can lock up when exiting it, requiring a battery pull to get going again.
Click to expand...
Click to collapse
Hopefully mine can help you. I also noticed HUGE battery drain issues in the past using Bricked Kernel, so I then reverted to stock. Battery was GREAT, but the stock kernel blows. So yeah, I went back to bricked and using the 3rd? beta right now. My battery started dropping like crazy again, so I thought it was the kernel. Before, I used bricked and it was fine so again, I couldn't really blame the kernel. What I tried after that is deleteing my OC app (I've used both SetCPU and System Tuner) and since then, battery is great again! You can try this and hopefully it'll help!
Tried that already as I too suspected the OC app a few days ago. Made no improvements to battery life, so I've put it back on today. Not tried a different kernel yet though, as I'd read that the bricked kernel was the best choice with InsertCoin? I used faux123's kernel first of all, but found it ran hot and kept crashing...
Down to 30% now by the way.
Ace42 said:
I think you drain is caused by the phone not entering "Deep Sleep", some rogue app is keeping the phone partially awake and sucking up juice. I'm gonna go on a hunch and say the phone is running around 1.x GHz while screen if off due to the app.
Click to expand...
Click to collapse
That's what I'm suspecting too, but I don't know how to go about finding it. I've looked with SystemPanel and BetterBatteryStats and haven't spotted anything, but that could just be because I'm not 100% on what to look for. And why would setCPU not be overriding it and making it clock down to 192mhz whenever the screen is off anyway? Isn't that it's job?
Then try the stock and see if it's still draining. When I tried stock and everything was great, I just simply assumed that it wasn't an app. It was the kernel!
I'm not convinced it's the kernel though, as if it was then battery life would have been crap ever since I flashed it. It hasn't been, it's only been bad for the past few days. Are there any links to the stock kernel just in case I can't find anything else?
- mine is 24 hrs
- heavy use 16 hrs
. Used some aninations only
. Turn off wifi when not in use
. Used only 20% brightness
. Used juice defender
. Downclock to 1.2 ghz intellideman
And ofc my kernel and rom that im using right now!
Thank me if I helped
I use bricked and i actually got better batter out of it but itsn still not up to par.. However fauxs ran faster but my phone was getting up to 47C... Way too hot.. I don't know why mines running so hot.. Using coredroid 2.6. 1.5 bricked kernel. wiped dalv and cache and battery stats... blah.. any input? i had setcpu and deleted it.
SetCPU is uninstalled again now to see if it was causing anything, and there's still a drain on the battery when it should be sleeping. Does anyone have any tips on how to find what's keeping it awake? It's been fully charged again, been unplugged for just one hour and it's down to 80% battery. Not even been using it apart from me flashing the InsertCoin Bravia addition onto it, making it 3.4.3.
One thing I have noticed though, is that BetterBatteryStats says the RILJ dialler has been running for 5m 33s since it was last charged, 775 times, 8.9%. This is on the partial wakelocks screen, whatever they are. Everything else listed is under 1%, with the only exception being the alarm at 1.6%. What does this mean?
i seem to be experincing a bit of an odd problem. its happened a couple times now. when i left for work yesterday morning i simply locked my transformer and left it on my desk. got home and it was off. when i locked it before work it was ~90% battery. turned it on and its at 65%?? after being off / sleeping for 10 hrs? also did it again last night . locked it and left it charging and again off this morning. anyone know whats going on? its rooted and running revolver 3.11.1 i also have it set to downclock when locked and wifi turns off after 3 min via revolver parts. running pandatest 1.2 kernel with an interactive daemon from 1.2 - 760 when unlocked and a conservative daemon when locked from 216 - 456
It's most likely the Kernel. Try running stock. that's what I use and really...the little over clocking doesn't help a great deal...and the little undervolting (which is most likely the culprit), doesn't help noticeably with the battery.
With stock kernel...my TF only loses ~1% in over 9 hours of idle.
ya thats what i was being to think and finally realised after it crashed in my hands. back to stock kernel for now. are the clemsyn kernels or the roach kernels any better?
SiNJiN76 said:
It's most likely the Kernel. Try running stock. that's what I use and really...the little over clocking doesn't help a great deal...and the little undervolting (which is most likely the culprit), doesn't help noticeably with the battery.
With stock kernel...my TF only loses ~1% in over 9 hours of idle.
Click to expand...
Click to collapse
I lost 26% over a 16 hour period yesterday. My transformer was fully charged at the beginning & sat idle for that entire time. I am rotted & Stock. I am at a loss as to what is going on. I should also note that airplane mode was also turned on & that I have tried the Auto Airplane mode app to resolve help remedy this.
(Just Read your other thread...you are stock stock)
Are you using any apps that are set to auto refresh at certain intervals? Is your Android OS one of the things listed in Battery stats that has a pretty high usage?
edit: try a custom ROM...
Swyped using my Pinky
went back to stock kernel and my device was still on when i got home from work but i lost 20% battery in idle again. i made sure all apps were killed and cpu spy says it spent the the time i was at work in the 216mhz state, but the thing thats using all my battery seems to be wifi. on battery usage its at 80% of my battery life so im thinking the radio isnt turning off like i set it to. android os is only 2%. i have the wifi disconnect policy set to dc when the screen goes off and then via revolver parts set to turn off the radio at 3min after lock.
pyro_teknic said:
went back to stock kernel and my device was still on when i got home from work but i lost 20% battery in idle again. i made sure all apps were killed and cpu spy says it spent the the time i was at work in the 216mhz state, but the thing thats using all my battery seems to be wifi. on battery usage its at 80% of my battery life so im thinking the radio isnt turning off like i set it to. android os is only 2%. i have the wifi disconnect policy set to dc when the screen goes off and then via revolver parts set to turn off the radio at 3min after lock.
Click to expand...
Click to collapse
How about making a nandroid...then using the superwipe lite script...try a fresh flash of the whole rom...and not mess with any of the settings. That would be the only sure fire way to see if it's just your tablet that has gremlins or the ROM settings are causing it to go mad.
I use revolver the way it came except wifi was changed to 2 minutes after screen off...and I installed an ICS theme that I manually downloaded. I haven't used revolver parts to download and install anything.
ill give it a go tomorrow. got another 12hr shift toady
SiNJiN76 said:
(Just Read your other thread...you are stock stock)
Are you using any apps that are set to auto refresh at certain intervals? Is your Android OS one of the things listed in Battery stats that has a pretty high usage?
edit: try a custom ROM...
Swyped using my Pinky
Click to expand...
Click to collapse
I my case when I looked at battery usage tablet idle was 76%
i actually think i found my gremlin. it was a combo of upnplayer and mxvideo. both were staying active and eating battery. softmedia and dice player with codecs seem a far better combo. thanks for all the help
Howdy folks. I have a major problem with my t769, and was hoping someone could help me figure it out. This problem began quite some time ago and has gotten worse. My battery stopped accepting a full charge (according to the meter.)
I had been running PA (racing port) for quite a while without a problem. The problem may have cropped up due to charging the phone while off at some point. When the problem first appeared, it would only charge up to 98%. I chalked it up to the fact that some phones apparantly don't trickle charge (for battery longevity?). Then the phone would only get to ~90%, then 83%... etc.
I have tried all three kernels available to us, nothing changes. Tried several different basebands. Tried reinstalling PA, no dice. Tried changing roms. Currently on Provision rom. The battery will not charge beyond 48 percent.
My issue does not appear to be a faulty battery; I recently purchased a couple new batteries and they do the same thing. Even after charging with an external charger - the phone still misreports the battery capacity. This has the effect of reaching a battery level of 0% (according to the meter) long before the actual battery capacity is exhausted. Further to that end, the android battery stats are never automatically wiped since the phone's battery meter never actually reaches 100%. The android battery stats page currently shows 4days on battery. I suppose this is because I last manually wiped the battery stats or pulled the battery 4 days ago.
Some more odd tidbits...
When the phone's battery meter reports 0%, the phone will automatically shut off ONLY if the display is ON. If the phone reaches the 0% mark while the display is OFF, it will continue to run and sometimes readjust the battery meter in 4-5% increments. i.e. if I turn off the screen when it hits 1%, and turn back on the screen some time later and the meter will report 4%. Other times it seems it will not readjust the meter while the screen is off and will remain at 1%. When the phone reports 1%, the battery is still outputting at least 3.5v. From what I understand, most 3.7v lithium ion batteries have an approximate safe operating range of between 3.2v-4.2v.
Really odd:
It seems that once the battery is pulled, the meter will revert to 0% once the phone is booted regardless of what the meter showed before the battery pull. I have not done this in the last couple days but it has happened several times and appears to be a repeatable issue.
All of my problems could logically be caused by a battery miscalibration, save the last point.
I have tried several calibration apps in the market that don't seem to do anything. I recently stumbled on this huge thread:
http://forum.xda-developers.com/showthread.php?t=765609
I have not read through all 200+ pages but it seems this has worked for many people. Unfortunately, I've been unable to get it to report values with the lightningX2 or CM10 kernels though. It states that the CM kernel should be supported, so I don't understand why it doesn't want to spit out values.
Any help would be greatly appreciated. I've grown quite attached to this phone and would like to continue using it!
Charge your phone overnight. Reboot to recovery (leave the phone plugged in). In cwm navigate to the advanced menu. Then in that menu wipe battery stats. Then let your battery drain down as much as possible before charging it again.
That should fix it.
Sent from my SGH-T769 using xda app-developers app
Many thanks for the reply. I'm currently using TWRP and I dont believe there is a section to wipe the battery stats.
I have removed the batterystats bin manually once android has booted both when the battery is in a near-dead state and in a near-full state and neither seemed to change the meter level. Perhaps I will see a different result by removing this file through recovery before Android boots?
I may install CWM to give this a shot soon but from what I understand, and please correct me if I am mistaken, the removal of this file has no bearing on the actual battery calibration. It was said that this file only affects what is displayed in the android battery stats page. There does appear to be a lot of confusion and controversy across the forums regarding whether or not this file is indeed responsible for actual calibration between true battery capacity and the state of the battery meter.
Not sure if this is important but when charging the phone (while turned off) the bootloader charging animation seems to report a value that is consistant with what the booted meter reports. (i.e. the animation will show ~50% battery left when the meter inside android will report 48%)
anactoraaron said:
Charge your phone overnight. Reboot to recovery (leave the phone plugged in). In cwm navigate to the advanced menu. Then in that menu wipe battery stats. Then let your battery drain down as much as possible before charging it again.
That should fix it.
Sent from my SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
kmem said:
Many thanks for the reply. I'm currently using TWRP and I dont believe there is a section to wipe the battery stats.
I have removed the batterystats bin manually once android has booted both when the battery is in a near-dead state and in a near-full state and neither seemed to change the meter level. Perhaps I will see a different result by removing this file through recovery before Android boots?
I may install CWM to give this a shot soon but from what I understand, and please correct me if I am mistaken, the removal of this file has no bearing on the actual battery calibration. It was said that this file only affects what is displayed in the android battery stats page. There does appear to be a lot of confusion and controversy across the forums regarding whether or not this file is indeed responsible for actual calibration between true battery capacity and the state of the battery meter.
Not sure if this is important but when charging the phone (while turned off) the bootloader charging animation seems to report a value that is consistant with what the booted meter reports. (i.e. the animation will show ~50% battery left when the meter inside android will report 48%)
Click to expand...
Click to collapse
Just out of curiosity, does this happen across all roms? Does it do it for stock as well? Maybe return to stock and check? I gave up on TWRP not because I didn't like the recovery, but it seemed to be... off... somehow... The 2.4 wouldn't restore backups (and would randomly reboot), and the 2.3.3 wouldn't reboot when plugged in (it would just power off). I also had some issues with my sd card with one of them (2.3.3 I think but not sure) on one of the JB roms and I lost all of my data. After going back to CWM 5.5.0.4 I haven't had any issues.
Both TWRP versions are built on the default CM10 kernel (correct me if I'm wrong here). I went back to stock about 2 weeks ago and am getting 4-5 days on battery life (light usage) where on ANY JB kernel the most I could get was a day and a half. Perhaps there's something missing/wrong with the JB kernel, and as such, TWRP isn't working properly because of it.
Perhaps the battery isn't getting read properly... have you tried cleaning the contacts with iso alcohol?
Sorry I couldn't be more help...:crying:
It happens for the two JB roms I have tried. I've not tried to return to stock yet but if you are getting 4-5 days of light usage that is incentive enough for me to give it a whirl! I never was able to squeeze more than about a day and a half out of a JB rom on my blaze either, even before these battery problems cropped up. I started using TWRP on my last phone mainly due to the fact that it can compress the backups but I've also become more accustomed it's UI. I think I'm currently using 2.4, but I vaguely remember both the SD issue and the power off instead of reboot issue you describe with the previous rev.
I can't speak to if the recoveries are built from CM. Now that you mention it, both JB roms that I have tried on the blaze show higher than normal battery usage by media and android system processes. Are you running a complete stock ICS or GB rom, or is it some debloated one? Can you tell me which one it is?
I've cleaned both the internal battery connector and micro usb connector to no avail. You have been a great deal of help, thanks again!
One other quick Q... After returning to stock, do you still have the black and white colored (powered off) charge animation? Ever since I rooted this thing, the power off charge animation starts up with the stock color (green filled battery) but quick flashes off and changes to the black and white one. Perhaps this is part of my problem, remanants of the stock bootloader mixed with the rooted one?
anactoraaron said:
Just out of curiosity, does this happen across all roms? Does it do it for stock as well? Maybe return to stock and check? I gave up on TWRP not because I didn't like the recovery, but it seemed to be... off... somehow... The 2.4 wouldn't restore backups (and would randomly reboot), and the 2.3.3 wouldn't reboot when plugged in (it would just power off). I also had some issues with my sd card with one of them (2.3.3 I think but not sure) on one of the JB roms and I lost all of my data. After going back to CWM 5.5.0.4 I haven't had any issues.
Both TWRP versions are built on the default CM10 kernel (correct me if I'm wrong here). I went back to stock about 2 weeks ago and am getting 4-5 days on battery life (light usage) where on ANY JB kernel the most I could get was a day and a half. Perhaps there's something missing/wrong with the JB kernel, and as such, TWRP isn't working properly because of it.
Perhaps the battery isn't getting read properly... have you tried cleaning the contacts with iso alcohol?
Sorry I couldn't be more help...:crying:
Click to expand...
Click to collapse
kmem said:
It happens for the two JB roms I have tried. I've not tried to return to stock yet but if you are getting 4-5 days of light usage that is incentive enough for me to give it a whirl! I never was able to squeeze more than about a day and a half out of a JB rom on my blaze either, even before these battery problems cropped up. I started using TWRP on my last phone mainly due to the fact that it can compress the backups but I've also become more accustomed it's UI. I think I'm currently using 2.4, but I vaguely remember both the SD issue and the power off instead of reboot issue you describe with the previous rev.
I can't speak to if the recoveries are built from CM. Now that you mention it, both JB roms that I have tried on the blaze show higher than normal battery usage by media and android system processes. Are you running a complete stock ICS or GB rom, or is it some debloated one? Can you tell me which one it is?
I've cleaned both the internal battery connector and micro usb connector to no avail. You have been a great deal of help, thanks again!
One other quick Q... After returning to stock, do you still have the black and white colored (powered off) charge animation? Ever since I rooted this thing, the power off charge animation starts up with the stock color (green filled battery) but quick flashes off and changes to the black and white one. Perhaps this is part of my problem, remanants of the stock bootloader mixed with the rooted one?
Click to expand...
Click to collapse
I'm running stock rooted uvmb1 (ics), which I've debloated and customized a bit (nothing special). Stock roms have the stock battery charging animation.
The battery drain is just one of those things I can't fully explain, as I have a few other devices running CM10 or 10.1 and they have great standby/light usage battery life
hello ppl,
I have this issue with my battery:
This afternoon my battery indicated 82%. the phone shut down and after a reboot it indicated around 27% battery left.
Later in the afternoon, after a reboot, I charged it for like 2 mins. it indicated 12%
I unplugged it and rebooted into recovery (4EXT) and it indicated 60% battery lvl.
I rebooted the ROM again and this indicated 34%
this event (reading 3 different battery lvls) took place in 1 minute, and the phone was not charger connected. It went from 12, to 60 and to 34%.
This really looks like a battery stats issue but what I can't help to wonder about is the following; do recovery and the ROM use different battery stats? this particular story sure gives that impression.
I plan to wipe battery stats after a full USB charge. U guys got any pointers I could consider? I have a stock batter for about 2 years now.
ROM: CM10.1 by Albinoman
Kernel: 3.0.67 ChronicBruce Linaro
Governor: ondemand
clockspeed: MIN 384 MAX 1728
I/O schedular: SIO
note: I did not experience any battery issue with this setup for at least 4 months prior to this problem, while using this setup.
attached a SS of the battery levels after reboot and shutdowns.
Seems like you're experiencing the same issues. The battery percentage was also way higher in recovery mode than Android showed me. Never noticed that before, so I'm not sure if that's normal, or both our phones / batteries are malfunctioning.
Wiping battery stats does nothing. 2 years is quite long for a battery, get an Anker?
onemanshow85 said:
hello ppl,
ROM: CM10.1 by Albinoman
Kernel: 3.0.67 ChronicBruce Linaro
Governor: ondemand
clockspeed: MIN 384 MAX 1728
I/O schedular: SIO
note: I did not experience any battery issue with this setup for at least 4 months prior to this problem, while using this setup.
attached a SS of the battery levels after reboot and shutdowns.
Click to expand...
Click to collapse
Before buying a new battery, did you attempt to flash a new ROM? becuase you seem to run a (very) old version of CM10.1 (I believe since March?), and although it's weird this popped up after four months, it is possible to be a problem in the ROM, especially with all the bugs fixed along the way. I believe updating the ROM should be the thing to do, before trying to change hardware parts (even battery), and if it won't work, you can always buy a battery (don't ofrget to back up your current ROM first).
astar26 said:
Before buying a new battery, did you attempt to flash a new ROM? becuase you seem to run a (very) old version of CM10.1 (I believe since March?), and although it's weird this popped up after four months, it is possible to be a problem in the ROM, especially with all the bugs fixed along the way. I believe updating the ROM should be the thing to do, before trying to change hardware parts (even battery), and if it won't work, you can always buy a battery (don't ofrget to back up your current ROM first).
Click to expand...
Click to collapse
I'm a mediocre XDA visitor and phone tweaker, so I didn't realize ROM's would get obsolete that quick (in my opinion). I will try to flash a updated CM, see if that works.
ok I updated my ROM. But there's no change in my batterie's behavior: shutdowns at high battery lvls and drops from enar full to near empty after the reboot.
I'm plannign to buy an Anker. but if anyone has some pointers that would be mint.
I already did the paper between battery trick.
Another update, today i noticed that the battery is a little bit swollen. The battery casing doesn't close properly anymore. When looking closely i notice the battery being slightly thicker. I don't trust it and don't use it anymore untill i got the anker
I am running mokee open source 4.4.2 roms and am constantly having trouble with battery.
It shows vague levels...i charge it from 10% onwards...and it gradually goes to 60% or so and then suddenly jumps to 100% showing battery is full.
The recovery sometimes shows the original level as 60%..but rom shows 100%.
Then the rom discharges at 1% per 2 minutes or so and i just cant get any backup as in reality it never gets fully charged. :-/
I have tried callibrating it after numerous factory resets via various playstore battery callibration apps.
I have wiped the system everytime i have flashed a rom.
I have tried discharging it and then charging it while ita off.
I have tried bump charging.
Still it gives 7-8 hours backup while people get 3-5 days of backup on idle mode.
On idle mode even..my tab loses 10-12% in 2-3 hours.
Tab is 7 months old so i think battery doesnt needs to be replaced or any hardware issue.
Can anyone...anyone please help me..?
Please Suggest any method other than the ones i have tried.
Thanks
Edit:
I have even tried Greenify to check the background apps..but in reality the battery goes down on even very light use such as messaging or checkin xda updates.
Anyone..?
This meight help if you are on P51XX : http://forum.xda-developers.com/showpost.php?p=50677996&postcount=788
Else:
Got into advanced wifi-settings and disable wifi to be on all the time, also disable networknotification if you don't need them.
Thanks but i have a P3100.
I have already disabled wifi when sleeping.
Running powersave and noop on 300-1008 mhz.
raamishmk said:
I am running mokee open source 4.4.2 roms and am constantly having trouble with battery.
It shows vague levels...i charge it from 10% onwards...and it gradually goes to 60% or so and then suddenly jumps to 100% showing battery is full.
The recovery sometimes shows the original level as 60%..but rom shows 100%.
Then the rom discharges at 1% per 2 minutes or so and i just cant get any backup as in reality it never gets fully charged. :-/
I have tried callibrating it after numerous factory resets via various playstore battery callibration apps.
I have wiped the system everytime i have flashed a rom.
I have tried discharging it and then charging it while ita off.
I have tried bump charging.
Still it gives 7-8 hours backup while people get 3-5 days of backup on idle mode.
On idle mode even..my tab loses 10-12% in 2-3 hours.
Tab is 7 months old so i think battery doesnt needs to be replaced or any hardware issue.
Can anyone...anyone please help me..?
Please Suggest any method other than the ones i have tried.
Thanks
Click to expand...
Click to collapse
Try flashing new kernel for your device.
Did you overclock the processor?
I once extended the preload with the help of a kernel., and when I restarted, cwm was unable to mount preload.
so I resetted the default settings of the kernel tweak app and den everything went fine like before.
Thanks for the reply.
I had once tried agni PureCM any rom kernel and i think that the issue was gone but i dont remember exactly and moreover i want to remain on stock mokee to get OTA.
People are gettin 3-5 days backup on stock.
I am running stock 300-1008 mhz on powersave and noop.
Also i just wiped preload once..could that be an issue.?
And wouldn't formattin the whole device and flashing the rom from scratch would reset the kernel settings to default..?
Here's a logcat if its of any use.
https://www.dropbox.com/s/ai1yxarc89frj0n/logcat.2014-03-03-08-16-39+0530.txt
raamishmk said:
Thanks for the reply.
I had once tried agni PureCM any rom kernel and i think that the issue was gone but i dont remember exactly and moreover i want to remain on stock mokee to get OTA.
People are gettin 3-5 days backup on stock.
I am running stock 300-1008 mhz on powersave and noop.
Also i just wiped preload once..could that be an issue.?
And wouldn't formattin the whole device and flashing the rom from scratch would reset the kernel settings to default..?
Here's a logcat if its of any use.
https://www.dropbox.com/s/ai1yxarc89frj0n/logcat.2014-03-03-08-16-39+0530.txt
Click to expand...
Click to collapse
I don't think wiping the preload will cause a battery issue.
Yes formatting the whole device should reset the kernel to its default settings.
Are you sure it is not a hardware problem?
Try to check it on any other similar device if you have.
Okay mate.
So i dont have any other tab 2...but my bro has it and he doesnt has this issue as far as i know.
But even i didnt have this issue until 2-3 weeks.
The only real culprit i can think is it might be the cable.
As yesterday pc gave me a code 43 error and i could not connect the tab howsoever i tried.
On 4.4.2 mokee..what should i do with such stats..?
Running greenify...and wifi sleep is enabled..completely formatted the tab and still this issue.
Since battery didnt dropped while it was on sleep..i dont think there is any hardware problem.
Any idea mates..?
@raamishmk same happens with mobile data turned off? can you tell me when it started?
Mobile data is always turned off mate..that stat is for sim network only.
And it started almost 3-4 weeks ago.
Also..i bought a new factory cable and the issue remains..so the faulty cable was not an issue.
Tab is 8 months old now..maybe the battery has possibly died..?
It's a battery issue.. Happen with me as well.. Replace ur battery under Warranty otherwise it will cost u 1600 INR rupees..
Sent from my GT-P3100 using Tapatalk
Well warranty is of 1 year so i can..
Thanks.