Update 2: I've had requests for links for the parts I used. I purchased the battery, a back cover, and all the additional accessories they suggested for removal.
Battery:
http://www.witrigs.com/oem-battery-for-sony-xperia-z1-compact
Back cover (this comes in different colors, but the link is for the black one):
http://www.witrigs.com/custom-back-cover-for-sony-xperia-z1-compact-black
---
Updating the OP. Thus far the only reliable way that myself and others have fixed their batteries has been by replacing them or having the phone repaired by Sony. Fixing it yourself involves purchasing a replacement from witrigs (or another parts supplier).
Flashing stock roms, custom roms (aosp or cm based), or factory firmware may temporarily give the illusion of being fixed. Battery repair apps don't do anything either (you can test this by 'fixing it', clearing app data and then 'fixing it' again).
I'm back to KitKat levels of battery life, using stock 5.0.2. Here's a recent screenshot for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-------
Original post:
So for the past few weeks my phone has really been acting up. I'll try and make this an organized question/post.
Here's the symptoms:
-Phone drops from 30ish % down to 1%, then powers off and wont turn back on due to low battery.
-Phone occasionally reports fully charged at different levels (such as 80% or 50%), upon reboot, it is listed as 100%.
-Some days I can watch it drop 1% every few seconds once it reaches 35%, literally like it's counting down.
-Other days it just works fine, I can use it to 5% and then charge with no problems.
Phone information:
-Z1 Compact
-Problem persists between ROM flashes and android versions. Have experienced issues on stock 4.4.4, stock 5.0.1, AOSP 4.4.4 and AOSP 5.1.
Really, any sort of help or places to start would be greatly appreciated. I don't even know what to try anymore and I'd really like to avoid trying to replace it (warranty expired already).
Attached a screenshot illustrating it happening. I unplugged my phone last night after charging it to full. Made it to work, put it in airplane mode, turned wifi on. Updated some apps and restarted it. Rebooted to about 10%. Charging again now.
HI There,
i got the same problem with my z1 compact. its all start when upgrade to lolipop...
some say our battery are dying...or got problem. are they ?
downgrade to kitkat, wipe everthing, battery calibration also still the same problem appear...
I've tried the same thing. Wiped data system etc and nothing helped.
Sent from my D5503 using Tapatalk
Same problem here. 4.4.4 stock rooted. It started about two weeks ago. I had done nothing except some play store upgrades. Haven't found a solution and I don't even know how to diagnose the problem. Various battery calibrations and/or deleting that battery data file haven't helped. Did a factory reset from recovery (almost accidental swipe while a bit drunk, gah...) - nothing. Battery level drop and shutdown occurs in random situations. Sometimes while taking a picture, sometimes with data on, sometimes off, gps on/off or whatever. Sometimes from 70% to 0, sometimes from 50%. Sometimes I can restart without charging after waiting a while and then it stays of for some time.
Yesterday I just did a reboot myself and when it came back on, the battery had dropped from 70 to 20% and then it stayed like that for some hours. Then I let it run to 0, charged without turning on to 100%. Then, when I turned the phone on, the battery level dropped to about 80% really fast and after that I got 20+ hours until it died again at 55% battery. I do see some small temperature spikes on Gsam battery monitor graph during those sudden drops, but never above 35 degrees Celsius and I don't think overheating is the issue here.
Again, I hadn't flashed any roms, updated android or messing around with the system or system settings before it started. Just normal everyday use, some websurfing, listening to music, taking occasional photos, reading blog feeds, taking notes.
Now I don't know what to do and I would greatly appreciate any help.
Haven't tried software repair yet, but what software could be still left broken?
Should I try unrooting via flashtool (does it lose all traces of root?) and taking it to warranty repair?
Right now the phone is practically unusable.
Hey, did u checked the Service menu Batterie test?
*#*#7378423#*#*
*#*#SERVICE#*#*
What does the test say?
I did check that yesterday and it was good.
And at the moment batt health status is "good, no need to replace it".
(Actual batt uAh: 2407000. Battery gauge at 74%.)
Yesterday after recharging and watching the battery plummet to 83%... It stayed there for some time despite data and GPS being on, using camera and an app. Should have dropped by a couple of % at least during that time.
13+ hours uptime now, very little use at night and at work.
That's what I'm afraid of. If the service test is good and at a glance everything seems to be fine then I won't get any help from warranty.
when test mine also in good condition. but the problem still happen. it kind makes me to conclude possible a battery hardware problem. need to change it, but it aint that cheap...
I've also checked my battery in the service menu. It reports good/healthy with the actual uAh being 2407000. I plan on wiping everything on the phone later today (system, all data, caches) and seeing if that helps at all, but I'm not very hopeful. Like you guys this pretty much just started happening for no discernible reason. Phone doesn't appear to be overheating either. Could the SD card being messing with it somehow? It seems implausible, but at this point I'm willing to try anything.
SOLVED (for me at least)
So I bit the bullet and wiped everything except for my SD card about 2 hours after my last post. Installed the most recent KK version of DstrikerZ1s ROM with the Doomlord v22 kernel. Ran it hard all day till now. Still at 50% and I've rebooted to check and make sure it's accurate multiple times. I'll report back if it happens again, but the performance thus far seems much more consistent than what I had before.
crimson12 said:
So I bit the bullet and wiped everything except for my SD card about 2 hours after my last post. Installed the most recent KK version of DstrikerZ1s ROM with the Doomlord v22 kernel. Ran it hard all day till now. Still at 50% and I've rebooted to check and make sure it's accurate multiple times. I'll report back if it happens again, but the performance thus far seems much more consistent than what I had before.
Click to expand...
Click to collapse
So need to format sdcard?
Sent from my D5503 using XDA Free mobile app
Yeah, I backed up both my internal storage and SD card and then formatted both.
wow, i have the same problem and i don't want to go back to KK. doees anyone have any solution that keeps lolli on?
I've been having the same problem since February. First it turned off at around 14% (when the warning pops up), but it's already been turning off at 20+ and finally 30-something percent, which wasn't bearable. No amount of wiping or up/downgrading would help so I bit the bullet and got a battery exchange (not directly from Sony who wanted to charge ~160€). Problem is fixed for the time being.
As much as I love this phone, it'll be the last one I get without a user-replacable battery.
Unfortunately my "fix" didn't work forever. I'm back to the same problem. Might as well suffer through it on lollipop. Where did you get the battery replaced?
crimson12 said:
Unfortunately my "fix" didn't work forever. I'm back to the same problem. Might as well suffer through it on lollipop. Where did you get the battery replaced?
Click to expand...
Click to collapse
I'm beginning to wonder our battery going to die... Maybe need to change, from my place, Sony center way to expensive need 3rd party battery maybe.. Or other than service center...
Sent from my D5503 using XDA Free mobile app
albuah said:
I'm beginning to wonder our battery going to die... Maybe need to change, from my place, Sony center way to expensive need 3rd party battery maybe.. Or other than service center...
Sent from my D5503 using XDA Free mobile app
Click to expand...
Click to collapse
i bought my replacement battery from witrigs and installed it myself. battery life has been good since then.
eumanoid said:
i bought my replacement battery from witrigs and installed it myself. battery life has been good since then.
Click to expand...
Click to collapse
So it was relatively easy to do yourself? I'm relatively nervous to try it. Shipping is killer to the states too :/
crimson12 said:
So it was relatively easy to do yourself? I'm relatively nervous to try it. Shipping is killer to the states too :/
Click to expand...
Click to collapse
Yeah. It's pretty straight forward. I used my wife's hair dryer as a heat gun and followed witrigs guide. I was surprised to see a 30$ tax on my items though. But thats due to customs so i had ni choice.
need to unscrew 1 skrew only right?
Sent from my D5503 using XDA Free mobile app
exactly the same problem only since Lollipop update.
it'll just shut down about 30% battery now, no going into battery saving mode or anything, i'll just be messaging and get "shutting down". Also I've had 53% battery, rebooted and then have 80%ish, its completely messed it all up.
I've factory reset and cycled the battery (run down, charge full etc) more than once. I'm suprised peoples batteries actually need replacing, how can a software update damage the battery?
I remember with a previous rooted samsung phone you could delete a battery data file with root explorer or something, is there a similar non-root way to fix this problem?
Related
My wife dropped her phone while getting the youngest out the bath.
She brought it to me and I left it in a warm place to extract any water.
The phone now powers, surprisingly but only gets to the HBOOT menu page, I cant select anything like up / down / power etc, so seems stuck.
I suspect the ROM has been fried, at a minimum. Is the phone recoverable?
Thanks
Strip the whole phone down. (There is a tear down guide with pictures somewhere on these forums for it)
Then clean it/ leave it to try for a few hours and then put it back together and see if it boots up.
Thanks. I dont have the tools to open it and it voids any warranty that 'may' still be available.
Ive left it overnight above my PC's exhaust fan which seems to have worked. Will be trying to boot it soon enough.
If its 'stuck' at the HBOOT screen, what are my options? Seems like the hardware still works but the software may be corrupted.
Its the same as before - stuck on the HBOOT screen. The power button works, it switches on, but even once in the menu on the default which is Fastboot, it doesnt allow me to select that. The power button seems not to work in this menu.
was everything completely dry? best thing was probably not to turn it on for a day or 2.
maybe try stick it in a rice bowl or something for a least 8 hrs.. (rice can absorb water very well).
failing that send it back to htc?
dingdong3000 said:
was everything completely dry? best thing was probably not to turn it on for a day or 2.
maybe try stick it in a rice bowl or something for a least 8 hrs.. (rice can absorb water very well).
failing that send it back to htc?
Click to expand...
Click to collapse
I think she had powered it when it was still wet, this is probably where damage could have happened.
I believe it to be dry now - there was little sign of water and the vapour around the screen area is now gone too since sitting over my PC's warmish fan.
Question is, almost forgetting about how the damage occurred, what are my options for getting a new BOOT loader or similar loaded, knowing that the phone does not boot. Can I make a gold card and update the phone, anything else?
Many thanks.
The volume up button has started to work, I can scroll through the options - what now?
Seems if I take the memory card and make a gold card, I may be able to recover the phone or am I missing something?
It seems to be working OK again. Im not sure what I did, I tried 'recovery' a few times without much luck, it hung on the O2 flash screen.
I then got frustrated and was pushing the power button a few times, it vibrated and came back to life, complaining of a low battery.
Its charging now, running as a phone - Ill put the Sim Card in later. The only thing is why it seems to go to the HBOOT menu, even if not prompted at the start ...
Perhaps a reflash is still worth looking at, wanted to get 2.2 on anyways.
Edit - I suspect the vol down button is screwed, hence why it goes to boot screen at start and also it doesnt work when the phone is now on. Hopefully it will be fixed as the phone dries out - perhaps Ill venture opening up the phone to sort it.
Unfortunately I had a similar mishap while on vacation, I was carrying my phone while crossing a stream and slipped and fell down, phone got wet...
After a few days phone would power up and "work" but I noticed a few things that I could not fix:
1) Phone runs very hot - always close to 40 degrees celcius where normal phone is around 30.
2) battery will not last for more the 6 to 8 hours with almost no use. High usage / low usage makes no difference anymore.
3) If turned off battery still dies in about 6 to 8 hours.
4) The worst thing for me was the phone thought the headphone was always plugged in even when it wasn't so it was impossible to get sound out of the normal speakers making the phone unusable as a phone without a headset.
It seems if your Desire has the water sensors red under the battery your warranty is void from what I read on the forum and around the net - HTC will not fix or they will charge you the same price as a new one to fix it.
So I decided to buy a new Desire and now use the old one to test custom roms before putting them onto the other phone. I was afraid to Root before but being I had a toy phone I had nothing to lose anymore and now I am addicted
And as a bonus the Headphone / sound issue disappeared when I applied a new Radio and custom rom so that even works now. Only remaining issue is the poor battery life (replacing battery does not fix the issue).
Just thought I would share my story, I hope you have better luck then me...
schalmers said:
Unfortunately I had a similar mishap while on vacation, I was carrying my phone while crossing a stream and slipped and fell down, phone got wet...
After a few days phone would power up and "work" but I noticed a few things that I could not fix:
1) Phone runs very hot - always close to 40 degrees celcius where normal phone is around 30.
2) battery will not last for more the 6 to 8 hours with almost no use. High usage / low usage makes no difference anymore.
3) If turned off battery still dies in about 6 to 8 hours.
4) The worst thing for me was the phone thought the headphone was always plugged in even when it wasn't so it was impossible to get sound out of the normal speakers making the phone unusable as a phone without a headset.
It seems if your Desire has the water sensors red under the battery your warranty is void from what I read on the forum and around the net - HTC will not fix or they will charge you the same price as a new one to fix it.
So I decided to buy a new Desire and now use the old one to test custom roms before putting them onto the other phone. I was afraid to Root before but being I had a toy phone I had nothing to lose anymore and now I am addicted
And as a bonus the Headphone / sound issue disappeared when I applied a new Radio and custom rom so that even works now. Only remaining issue is the poor battery life (replacing battery does not fix the issue).
Just thought I would share my story, I hope you have better luck then me...
Click to expand...
Click to collapse
Thanks for the info. I can see a red 'tag' inside the phone but on the battery itself there is a white sticker, is it either of these?
Ive gone ahead and bought a card reader and also a spare card - hopefully I can extract some value from it.
Chazaxl said:
Thanks for the info. I can see a red 'tag' inside the phone but on the battery itself there is a white sticker, is it either of these?
Ive gone ahead and bought a card reader and also a spare card - hopefully I can extract some value from it.
Click to expand...
Click to collapse
Both of those are water detectors.
Sounds like your phone has become water damaged but the battery didn't.
Your phone will now not have a warranty as a result and unless you have some sort of insurance that covers water damage (most don't) then there is nothing you can do.
Excuse the crappy pics, taken with iPhone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See the two tags, one red, one white, that them?
Lennyuk said:
Both of those are water detectors.
Sounds like your phone has become water damaged but the battery didn't.
Your phone will now not have a warranty as a result and unless you have some sort of insurance that covers water damage (most don't) then there is nothing you can do.
Click to expand...
Click to collapse
Ok, thanks - see pics above :-(
Chazaxl said:
Ok, thanks - see pics above :-(
Click to expand...
Click to collapse
yeah its what I thought, the water obviously got onto the phones tag but not the battery. Your lucky as usually when the battery tag goes the battery stops working.
Phones are often programmed these days to stop working when water is detected even when the phone is actually fine (easy way to get more money I guess). So I would be quite happy its still working if I was you
I need to figure out if its the software thats screwed or if its the volume buttons. They partially worked earlier, now nothing, back to boot screen.
Going to try and create a gold card to allow me to upgrade HBOOT and take it from there.
This is one of the first phones, so should be AMOLED screen, less risk for HBOOT upgrade?
easiest and best way to sort it out would be between the two options:
-buy insurance online, wait a few weeks then claim
- try and fix it, then fail miserably and wish you just bought insurance
paprkut said:
easiest and best way to sort it out would be between the two options:
-buy insurance online, wait a few weeks then claim
- try and fix it, then fail miserably and wish you just bought insurance
Click to expand...
Click to collapse
Dont sound like good options - ....
Dont want to curse it but its running again, down volume also working.
Ive got some of the updates on a gold card, got an error with it, not sure why but less tempted to fiddle if the phone works as normal.
I got the same problem about a week ago when i cycled and it started raining really hard. so my desire got half drowned because i didn't have a rain jacket.
At first it appear as if my phone would work normally again, because the power buttons didn't work when i wanted..
However, a week later, it feels as if nothing has happened. so keep on praying ;p
Sounds to me you really should let it dry even longer because of the fact its seems to be still coming back to life. Take off the cover, battery, sim and sd card, stick it in a rice bowl or hang it in your pc fan airflow for 1~2 more days.
Sent from my HTC Desire using XDA App
Hi everyone,
I have been lurking the better battery stats thread to see what was killing battery life of my verizon nexus and trouble shot what everyone recommended.
uninstalled facebook, google+, turned off gps/location, signed off google talk/voice etc i didnt even know i was signed into.
ran this last night for a total of 8 hours fully charged and still noticed a 20% drop from 100-80 same as BEFORE!
I observed alarm manager and lightflow were killing my battery. I can uninstall lightflow, but what is alarm manager? I don't have my alarm clock turned on.
Attached is the text log if anyone can help. It will be greatly appreciated =(
According to your log only 0.3% was drained due to your alarm, and that seemed to be the largest drain in terms of partial wakelocks...which compared to my 10% for RILJ AND 8% FOR AudioOut_1 on 4.0.3 looks like you should be doing excellent in terms of battery life as long as your screen was off.
Could you send a screenshot of your battery screen and battery history screen?
I didn't save it sorry but when I observed it. I noticed there were 3 times during the night there was awake activity so something woke up my cdma nexus. I am thinking it is probably my Google backup services and sync.
I have been reading other users only getting 1% drain every 2 hours and I don't think its possible unless they are on probably the GSM version.
I'm quite disappointed in the idle drain so far since I'm experiencing about 2% every hour.
Sent from my Galaxy Nexus using XDA App
While we are on the subject.....I have uploaded mine too
Is 4.4% alarm normal?
I'm still trying to troubleshoot my CDMA Galaxy Nexus in terms of what's eating its battery. The Android OS has been consistently higher than anything else (even the screen) and I usually see about 2-3 hours of awake time because of it, when I'll only use between an hour or two of screen time.
It's looking like an ICS thing more than anything else at this point. I can't really say that for sure since I'm still trying to cancel things out one by one to see any noticeable difference.
On the topic of alarms my AlarmManager only took about .3% today as my actual alarm clock took about .4%, whether what's normal or not I'm not sure anyone can say with the devices being so new and little information about that specifically.
its my understanding that alarmmanager has nothing to do with the alarm clock, but instead it is related internally to the OS that tells apps to wake up and perform some function. basically a scheduler for any app to tie into to perform an event, i.e. update the battery percentage, synch an account, etc.
i could be totally wrong on that though. and yes i think you guys with CDMA version have more trouble with idle. i still get dead flat idle drain on my gsm version...it loses 1% every 2 hours or so give or take. fall asleep with 95% and wake up with 91%!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does this look pretty normal
What's this mean
Sent from my Galaxy Nexus using Tapatalk
No one replies? Would like help here also
Sent from my Galaxy Nexus using Tapatalk
I'm also having similar problems with my LTE Galaxy Nexus. I can't figure out what is eating up the battery, but just now I had it sitting next to me in bed, unplugged, for about an hour and when I went to pick it up just now the back was really hot.
I'm not sure if I'm reading it correctly, but it looks like NotificationService is triggering a lot more wakelocks than it should be. I don't know what AudioOut_1 is, but I can't imagine it should be that active, either, since I'm not playing any music or getting a lot of notifications with sound appearing, but maybe that's not what it's for.
Any way I can pinpoint this problem any further?
guys, I am actually in a rather helpful mood today..
http://bit.ly/zuLGu5
s2d4 said:
guys, I am actually in a rather helpful mood today..
http://bit.ly/zuLGu5
Click to expand...
Click to collapse
If that was helpful (which it isn't), I wouldn't be here right now. That goes full circle right back to this thread, and other threads with people asking similar questions about how to read the BBS data.
Something is keeping my phone awake nonstop, and I can't pinpoint it at all. Something registering as Android OS in the stock battery stats is eating up a large chunk of my battery and is preventing any sleep (which is, in turn, preventing wifi from disabling itself).
There was about 8 hours worth of data here before I plugged it back in, but Awake was a solid blue bar all the way across, along with WiFi, indicating that something is keeping it awake 24/7.
I'm sure that NotificationService is part of the problem, since it's giving me 1500+ partial wakelocks with over an hour's worth of time, however I have no clue what exactly is triggering NotificationService.
If there's any way I can pull the log file (I don't know where it saved to) and read the data somehow, is there any way that this can tell me what app would be causing this? I've already uninstalled several apps that I thought could be problematic and disabled sync on most of them (or set them to push), and I'm left with no answers at this point.
If there's something painfully obvious that's posted from the other threads, then I apologize for not understanding, however I can't seem to find any real answers anywhere; only the same questions and some speculative answers with no real conclusion.
well, there are plenty of ppl there that will help you read it since it is the app thread. The developer is also there and provides good suggestions.
Amazing though, lmgtfy failed even this time...
"you can lead a horse to water, but you can't make it drink"
Xel'Naga said:
If that was helpful (which it isn't), I wouldn't be here right now. That goes full circle right back to this thread, and other threads with people asking similar questions about how to read the BBS data.
Something is keeping my phone awake nonstop, and I can't pinpoint it at all. Something registering as Android OS in the stock battery stats is eating up a large chunk of my battery and is preventing any sleep (which is, in turn, preventing wifi from disabling itself).
There was about 8 hours worth of data here before I plugged it back in, but Awake was a solid blue bar all the way across, along with WiFi, indicating that something is keeping it awake 24/7.
I'm sure that NotificationService is part of the problem, since it's giving me 1500+ partial wakelocks with over an hour's worth of time, however I have no clue what exactly is triggering NotificationService.
If there's any way I can pull the log file (I don't know where it saved to) and read the data somehow, is there any way that this can tell me what app would be causing this? I've already uninstalled several apps that I thought could be problematic and disabled sync on most of them (or set them to push), and I'm left with no answers at this point.
If there's something painfully obvious that's posted from the other threads, then I apologize for not understanding, however I can't seem to find any real answers anywhere; only the same questions and some speculative answers with no real conclusion.
Click to expand...
Click to collapse
He's being a smartass
Sent from my Galaxy Nexus using Tapatalk
I thought mine was awake to much. You have a problem.
Sent from my Galaxy Nexus using Tapatalk
bendirkss said:
I thought mine was awake to much. You have a problem.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm thinking I may have a more severe problem than I once thought.
I've left my GNex sitting on the charger for about an hour now, to let it run its course and maybe give me some new data to work with. It's acting as if it's been on the battery for only ten seconds (which is closer to how long it's been since I turned the screen back on, but still charging), and then only gives me a graph for 11 minutes' worth of time.
One thing I'm seeing here which is probably a major problem is that the Awake, Screen On, and Charging meters all completely stop together at the same time for a moment, and then come back on. Even though the phone had been charging for well over an hour with no interruption, it looks like the device lost track of the charging status or something.
I'm not sure if the rest of this is relevant, but about an hour ago when I last put it on to charge, the phone app stopped working. Any call I'd make would immediately say "Call ended" without attempting to dial, even though I had a signal. After struggling with it for a few minutes, the phone crashed completely and reboot. Once it booted back up, the phone app would simply close itself and go back to the homescreen any time I'd try to dial a number, and was randomly adjusting the volume of the DTMF tones. It took about five minutes for it to actually allow me to make a call again, which doesn't seem normal.
So now I'm wondering if there's something else wrong with this device, or if this is all just a part of some bigger, underlying problem.
Worth mentioning, this is the LTE version, non-rooted, running stock 4.0.2.
Xel'Naga said:
I'm thinking I may have a more severe problem than I once thought.
I've left my GNex sitting on the charger for about an hour now, to let it run its course and maybe give me some new data to work with. It's acting as if it's been on the battery for only ten seconds (which is closer to how long it's been since I turned the screen back on, but still charging), and then only gives me a graph for 11 minutes' worth of time.
One thing I'm seeing here which is probably a major problem is that the Awake, Screen On, and Charging meters all completely stop together at the same time for a moment, and then come back on. Even though the phone had been charging for well over an hour with no interruption, it looks like the device lost track of the charging status or something.
I'm not sure if the rest of this is relevant, but about an hour ago when I last put it on to charge, the phone app stopped working. Any call I'd make would immediately say "Call ended" without attempting to dial, even though I had a signal. After struggling with it for a few minutes, the phone crashed completely and reboot. Once it booted back up, the phone app would simply close itself and go back to the homescreen any time I'd try to dial a number, and was randomly adjusting the volume of the DTMF tones. It took about five minutes for it to actually allow me to make a call again, which doesn't seem normal.
So now I'm wondering if there's something else wrong with this device, or if this is all just a part of some bigger, underlying problem.
Worth mentioning, this is the LTE version, non-rooted, running stock 4.0.2.
Click to expand...
Click to collapse
Sound to me like you need AOKP
Sent from my Galaxy Nexus using Tapatalk
bendirkss said:
Sound to me like you need AOKP
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I've been thinking about it, but holding off because I don't want to reconfigure all my apps/widgets all over again.
What advantages are there to AOKP over other ROMs?
Xel'Naga said:
I've been thinking about it, but holding off because I don't want to reconfigure all my apps/widgets all over again.
What advantages are there to AOKP over other ROMs?
Click to expand...
Click to collapse
Setting back up takes a min. Tweaks, for me its smoother. And a pink unicorn upon bootup
Sent from my Galaxy Nexus using Tapatalk
bendirkss said:
He's being a smartass
Click to expand...
Click to collapse
No, listen to instruction to help yourself.
Follow the previous link because of the reason below.
Otherwise you are just being stupid.
s2d4 said:
well, there are plenty of ppl there that will help you read it since it is the app thread. The developer is also there and provides good suggestions.
Amazing though, lmgtfy failed even this time...
"you can lead a horse to water, but you can't make it drink"
Click to expand...
Click to collapse
Hi.
I've had the D855 model from 3UK since Thursday I am noticing that the phone gets very hot at the top on the back around the camera and button area. This is not even through particularly heavy use either. I've not ran games or watched any video on it yet. Whilst typing this post for example with no other apps open I can feel this area is really hot.
I've had other phones that have gotten warm after gaming etc. But this is bloody ridiculous
I have also just switched to ART & after the phone rebooted there was 200 apps to optimise & the handset was burning up.
Doesn't seem to be coming from the battery though which seems to be lower down.
Anyone else had this problem?
I haven't had this issue at all, but I haven't loaded it up with a bunch of stuff yet. It sounds like you have a runaway program of some sort. I have used my phone for very long periods of time without interruption and haven't experienced any heat that's more than my Note 3. I'd unload everything and add things one at a time, or check your memory usage and see if you have anything that's taking far more than it should.
My phone gets warm in that area but nothing that has concerned me yet, but it's usually when I have had the screen on for a lengthy period of time.
Sent from my LG-D855 using Tapatalk
brightness set at ?
I've not really loaded it up with apps. Just google stuff, bbci player, Chromecast (not working) Im gonna try removing stuff & see if it makes any diference .Screen brightness is set to 40% auto brightness ticked.
Is there a recommended app to monitor rogue apps or wakelocks?
I've also just had it charging for about 2 hours on the official plug & its red hot again.
jusumgeezer said:
I've not really loaded it up with apps. Just google stuff, bbci player, Chromecast (not working) Im gonna try removing stuff & see if it makes any diference .Screen brightness is set to 40% auto brightness ticked.
Is there a recommended app to monitor rogue apps or wakelocks?
I've also just had it charging for about 2 hours on the official plug & its red hot again.
Click to expand...
Click to collapse
BetterBatteryStats is good to monitor wakelocks ect..... debloating you're phone should help a bit too, I made a list of things i've done away with if it helps you
Find it here http://forum.xda-developers.com/showthread.php?t=2800293
sure there will be more than that that can be removed, hopefully others will test and contribute soon It should help you get a good start tho. Good Luck
Same issue but with US T-Mobile version
jusumgeezer said:
Hi.
I've had the D855 model from 3UK since Thursday I am noticing that the phone gets very hot at the top on the back around the camera and button area. This is not even through particularly heavy use either. I've not ran games or watched any video on it yet. Whilst typing this post for example with no other apps open I can feel this area is really hot.
I've had other phones that have gotten warm after gaming etc. But this is bloody ridiculous
I have also just switched to ART & after the phone rebooted there was 200 apps to optimise & the handset was burning up.
Doesn't seem to be coming from the battery though which seems to be lower down.
Anyone else had this problem?
Click to expand...
Click to collapse
Hello, I am having exactly the same issues you described. It happens just out of the blue. The phone starts getting superhot until the battery is drained. If I try to charge it, it does not get charged. It has happened to me randomly.
Did you find the cause for your troubles?
jusumgeezer said:
Hi.
I've had the D855 model from 3UK since Thursday I am noticing that the phone gets very hot at the top on the back around the camera and button area. This is not even through particularly heavy use either. I've not ran games or watched any video on it yet. Whilst typing this post for example with no other apps open I can feel this area is really hot.
I've had other phones that have gotten warm after gaming etc. But this is bloody ridiculous
I have also just switched to ART & after the phone rebooted there was 200 apps to optimise & the handset was burning up.
Doesn't seem to be coming from the battery though which seems to be lower down.
Anyone else had this problem?
Click to expand...
Click to collapse
I've had this exact issue too ... and for those wondering just how hot it gets, it's in the rough area of "wtf" degrees. I've lost 85% of my battery in 3 hours. It normally happens when I'm not charging and on WiFi, but what I've noticed is that the 3G/4G/LTE (whatever radio connection I have at the time) starts turning on. Now if it was an App misbehaving, I doubt an App would have the ability to bypass WiFi and use the data connection.
I'm about to do a full wipe and see if that fixes it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
... and as I was writing this post, I noticed the damn thing rebooting itself. LG makes great hardware, but their software just sucks. Why won't they unlock the damn bootloaders so I can put CMMod on it or something that doesn't suck?
Overheating
im having the same issue its getting hot for no reason did you fix this issue
---------- Post added at 04:44 PM ---------- Previous post was at 04:40 PM ----------
did you comeup with any fix cause i'm sick and tired of this issue
I've had this twice both caused by different ota updates. A full wipe and install fixed for me. Now I'm in 10m, no over heating and better life is much much better
To further my last comment, if you've hardly got anything installed, then do a quick backup and then install something like 10m (which world perfectly for me) and do a full flash wiping everything.
If I didn't do that, then it got so hot then I couldn't keep the phone in my pocket and had to turn it off !! The heat comes from very close to the volume buttons, and it worried me how hot it was getting.
Mine is burning up in use or on charge, i just checked temps with cpu z and temps were at 81c, 79c, 75,c
81c, etc etcvery warm indeed, yes i have a lot of apps installed and i did have a few running at the time but Jeezz this thing is like a portable radiator, i have a case on it with the quick circle cover but it's the slim model that replaces the rear part of the original case so not packed inside extra plastics, ive never had such a hot phone.
I have tried a few things to try and tackle the problems but with no joy, i'm also constantly running out of space on the internal memory despite moving all the movable apps to Ex SD card, my phone is routed and running fulmics 5.1 rom
Same here, using D855 from Hong Kong, I have already done a factory reset/wipe.
Unmounting the SD card does help a bit in my case, still, it does not solve the problem.
As long as I turn on the screen and make some touches, it will start overheating for no reason.
Same for me. When I watch 3d sbs 180 videos, after around 25 mins the phone has given a warning and then shortly afterwards shut itself down.
I replaced the circle case with a more common style back cover that I bought from aliexpress and put a new battery into it, but the problem remains.
10M is an earlier android built from 2014, right? Will the problem be solved if downgrading? I wouldn´t mind really.
Thanks
jazzl said:
Same for me. When I watch 3d sbs 180 videos, after around 25 mins the phone has given a warning and then shortly afterwards shut itself down.
I replaced the circle case with a more common style back cover that I bought from aliexpress and put a new battery into it, but the problem remains.
10M is an earlier android built from 2014, right? Will the problem be solved if downgrading? I wouldn´t mind really.
Thanks
Click to expand...
Click to collapse
So, I´ve been trying to downgrade using LGUP. The new version of this keeps telling me that my phone is unknown, and old version gives an error after 4%.
On some of the pages I found about how to do it, it´s saying that I need to change the LGE port to 41 in Windows. When doing that, my windows (10) freezes and I have to reset the computer.
Any ideas about what I may be doing wrong or suggestions to other methods?
Thanks
jazzl said:
So, I´ve been trying to downgrade using LGUP. The new version of this keeps telling me that my phone is unknown, and old version gives an error after 4%.
On some of the pages I found about how to do it, it´s saying that I need to change the LGE port to 41 in Windows. When doing that, my windows (10) freezes and I have to reset the computer.
Any ideas about what I may be doing wrong or suggestions to other methods?
Thanks
Click to expand...
Click to collapse
Allright, I´ve done it!
I used the old 2014 LGupgrader, but instead of running it via a network mounted drive, as I´d done it up till this point, I did it directly from C:/Temp. This was the key to success for me. I had it stuck for a couple of mins at 9 %, but it suddenly continued. This may have to do with the available internal mem. Some ppl say there should be 2 GB free, but I had only 1.51 GB free.
Temp is now 12 C less than before at similar operations.
The excessive heat has been reported as an issue across all models of the G3. The best solution is to use a thermal pad on the SoC. That helps spread the heat to the metal chassis, reducing your temps from 10-15 degrees Celcius. Get any 0.5mm thick thermal pad, cut it down to 14x14mm, clean both the SoC and the surface on the chassis with alcohol, apply pad and be sure to tighten screws as much as possible without stripping. I've been using this mod on both of my G3's for almost 2 years, and it does not void your warranty. Good luck!
AlwaysLucky said:
The excessive heat has been reported as an issue across all models of the G3. The best solution is to use a thermal pad on the SoC. That helps spread the heat to the metal chassis, reducing your temps from 10-15 degrees Celcius. Get any 0.5mm thick thermal pad, cut it down to 14x14mm, clean both the SoC and the surface on the chassis with alcohol, apply pad and be sure to tighten screws as much as possible without stripping. I've been using this mod on both of my G3's for almost 2 years, and it does not void your warranty. Good luck!
Click to expand...
Click to collapse
Do you have a link to such a thermal pad and maybe a link to a vid showing how it´s done?
I was a bit too quick saying that my problems are now solved. I still get much nicer temperature, but VR videos skip frames alot, where they´d go smooth before. I´m wondering if Lollipop is throttled so it won´t get too hot, and does not have the power to play the vids, where Marshmallow pushes the hardware to the max, and then it gets hot.
Would anyone disagree with this?
Also, when did the overheating get introduced? If it´s not there in 10m, maybe there´s a build closer to Marshmallow that will let the hardware work a bit more, without heating too much up.
Ok, I found a pretty decent solution:
http://www.androidauthority.com/lg-g3-problems-517832/
The part about amending the High Temperature Property OFF setting seemed to do the trick. Now VR vids play more smoothly and though it - obviously - gets hotter, it won´t get as hot as with Marshmallow.
With Marshmallow I´d get a warning at 57 C, and then it´d shot down a few mins later. Now, after about the same amount of time using the phone with a VR vid, it shows 49 C, which is acceptable.
jazzl said:
Do you have a link to such a thermal pad and maybe a link to a vid showing how it´s done?
Click to expand...
Click to collapse
Use this video for disassembly.
And this is an example of a thermal pad you can use.
The heat issue is a hardware design flaw. The issue can be minimized with software, but the only way to truly solve it is a thermal pad or some other way to allow the heat to escape faster. It's easy to do, just take your time and use the right tools.
AlwaysLucky said:
Use this video for disassembly.
And this is an example of a thermal pad you can use.
The heat issue is a hardware design flaw. The issue can be minimized with software, but the only way to truly solve it is a thermal pad or some other way to allow the heat to escape faster. It's easy to do, just take your time and use the right tools.
Click to expand...
Click to collapse
Allright, thanks. Maybe a dumb q, but how do I recognize the SoC?
hello guys,
lately I noticed that my battery has been discharging way too fast for my liking! I'm suspecting the cheap magnetic charger I bought online to be the cause of this, but I'm not sure.
Here's what happened:
I put the device to charge during the night, and when I woke up I found out that the device has been drained. I put it to charge again, and waited. It took about 30 minutes for the device to power on again!
Oh and before that thing happend (about a week before) I noticed that the device reboots when it reaches a % between 5-10
After that I noticed that the battery life has been greatly shortend.
Is there anything I can do about that, to try and recover some of the battery (leave it on a wall charger for a day etc..) ?
I finally found the fix for my battery drain: http://forum.xda-developers.com/showpost.php?p=55257984&postcount=21
Seems like the magnetic charger was not to blame at all
Hello @oshmoun;,
I use one of those cheap docking stations as well. However I've not had any issues with the battery life like you.
Try to recalibrate your battery, this sounds like a misscalibrated battery.
If that does not work, restore your phone back to stock and send it in for service.
"Can it wait for a bit? I'm in the middle of some calibrations"
Best regards,
GethPrime
GethPrime said:
Hello @oshmoun;,
I use one of those cheap docking stations as well. However I've not had any issues with the battery life like you.
Try to recalibrate your battery, this sounds like a misscalibrated battery.
If that does not work, restore your phone back to stock and send it in for service.
"Can it wait for a bit? I'm in the middle of some calibrations"
Best regards,
GethPrime
Click to expand...
Click to collapse
Thanks for the info.
Do you know how to best calibrate the battery? I see a lot of methods online but judging by the look of them they seem to only be placebos.
Get me a reliable method to calibrate the battery or I'll let Tali dissect you piece by piece
oshmoun said:
Thanks for the info.
Do you know how to best calibrate the battery? I see a lot of methods online but judging by the look of them they seem to only be placebos.
Get me a reliable method to calibrate the battery or I'll let Tali dissect you piece by piece
Click to expand...
Click to collapse
Hello @oshmoun,
This tutorial have some different methods you can try out:
http://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
I would suggest you to try out the method for rooted users first, if that does not help you can try the others out if you want to.
Keelah se'lai,
GethPrime
oshmoun said:
Thanks for the info.
Do you know how to best calibrate the battery? I see a lot of methods online but judging by the look of them they seem to only be placebos.
Get me a reliable method to calibrate the battery or I'll let Tali dissect you piece by piece
Click to expand...
Click to collapse
did the calibration work?
notwigga said:
did the calibration work?
Click to expand...
Click to collapse
no it didn't
I guess I'll wait till .133 is out to see if stock solves my issue.
I had the exact same problem with my Samsung phone.
I suspected that it was a software problem since I had just flashed a new version.
It turned out that the battery was damaged, even though it was not that old. I had to replace the battery.
Just to let you know.
LupoSpeed said:
I had the exact same problem with my Samsung phone.
I suspected that it was a software problem since I had just flashed a new version.
It turned out that the battery was damaged, even though it was not that old. I had to replace the battery.
Just to let you know.
Click to expand...
Click to collapse
Well I've still not ruled everything out, but i had considered replacing the battery. Unfortunately this is not a Samsung device. The battery is not replaceable, which means I'll have to send it to a Sony repair center
I'd rather first try out everything i can before it comes to that
Go fully stock and try and replicate the rebooting issue, then get it sent to Sony.
Is it possible, that you connected your device reversed left to right. (+ on - of the magnetic charge and - on +)
It would explain why your device battery was empty, after you "charged" it.
It can kill your battery, if your unlucky and you do this once....
zeus2602 said:
Is it possible, that you connected your device reversed left to right. (+ on - of the magnetic charge and - on +)
It would explain why your device battery was empty, after you "charged" it.
It can kill your battery, if your unlucky and you do this once....
Click to expand...
Click to collapse
The charger doesn't fit the other way around, so i would say that didn't happen
I'm noticing that the battery is slowly improving by itself. Yesterday i got about 4.5 screen time!
Maybe the battery calibration worked after all
Did you solve the problem with battery or it is still not good?
Sent from my Xperia Amami using Tapatalk 2
OyyO said:
Did you solve the problem with battery or it is still not good?
Sent from my Xperia Amami using Tapatalk 2
Click to expand...
Click to collapse
It still happens once in a while. Yesterday my battery dropped about 10% after rebooting the device [emoji33]
Let's hope that that means the device has found some of the lost battery charge
Thanks for your interest in my problem
I experience the same error after upgrading to .108. If I downgrade, everything works fine. Seems like a bug to me..
now i start use magnetic cable for Z1 (by Yida.com). after charge i'll post how is my battery
Hi @oshmoun ,
I was using .681 FW by munjeni until two days ago, my battery was good until the last few days of using it (5 days ago I guess)
then the battery started draining crazily and I didn't know why (didn't do anything unusual), I tried several things like battery recalibration and reducing CPU clock and using powersave governor but had no luck.
So I decided to update to a newer Sony FW, so I flashed .108 (old) FW I had without wiping data,
and that restored the battery life, actually it is much better now!
Also I flashed DooMKernel for .108 and played a little with its settings, and now I'm feeling victory:victory:
Hope this helps
Best Wishes,
Omar.
OmarEinea said:
Hi @oshmoun ,
I was using .681 FW by munjeni until two days ago, my battery was good until the last few days of using it (5 days ago I guess)
then the battery started draining crazily and I didn't know why (didn't do anything unusual), I tried several things like battery recalibration and reducing CPU clock and using powersave governor but had no luck.
So I decided to update to a newer Sony FW, so I flashed .108 (old) FW I had without wiping data,
and that restored the battery life, actually it is much better now!
Also I flashed DooMKernel for .108 and played a little with its settings, and now I'm feeling victory:victory:
Hope this helps
Best Wishes,
Omar.
Click to expand...
Click to collapse
Thanks for the hint. I guess I'll have to switch to stock at some point to figure this out (yuck! )
Do you have a link to the .108 you used? Also, is it rooted?
oshmoun said:
Thanks for the hint. I guess I'll have to switch to stock at some point to figure this out (yuck! )
Do you have a link to the .108 you used? Also, is it rooted?
Click to expand...
Click to collapse
Here it is: http://forum.xda-developers.com/son...stock-d5503-14-4-0-108-customized-sa-t2804381
this is the old .108 customized (Saudi Arabia:cyclops
it isn't rooted as it is a stock ftf, but I rooted it as soon as I flashed it :angel:
This happened to me when I tried using one of the Chinese magnetic chargers on eBay. I fixed it by turning the device off for ten minutes, then plugging it into a USB port on my computer. It stopped the rapidly draining and overheating and trickle charged it back up. Happened about 2 weeks ago and hasn't happened since (and I stopped using that charger).
Sent from my D5503 using Tapatalk
After switching to stock .108
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is very very interesting!
I sure hope CM based ROMs will reach this level of battery performance soon.
Hi guys, my tablet has been showing some significant battery drain lately. When idle, it drains around 5-10% per hour. At first I thought something was preventing it to go to sleep (according to GSAM the battery is mostly drained by the kernel), but then I started noticing that also when I was using the device the battery drained significantly (20-25% per hour).
I tried the common fixes such as wiping the device, turning off any energy-consuming apps and services (e.g. Google Now, GPS, etc.), battery recalibration and reseating the battery; nothing helps.
I'm running a stable nightly from CM13.0 (I asked in the CM13.0 thread if anyone else has this problem but it just seems to be me), but the issue was also present in other nightlies and in 12.1.
The last option I can think of right now is buying a new battery, but since that would be pretty costly and since I'm not sure that would solve my problem I wanted to run this by you to see if anyone here would have an idea of what could solve it.
Thank you very much in advance for your help!
SeveralBunnies said:
Hi guys, my tablet has been showing some significant battery drain lately. When idle, it drains around 5-10% per hour. At first I thought something was preventing it to go to sleep (according to GSAM the battery is mostly drained by the kernel), but then I started noticing that also when I was using the device the battery drained significantly (20-25% per hour).
I tried the common fixes such as wiping the device, turning off any energy-consuming apps and services (e.g. Google Now, GPS, etc.), battery recalibration and reseating the battery; nothing helps.
I'm running a stable nightly from CM13.0 (I asked in the CM13.0 thread if anyone else has this problem but it just seems to be me), but the issue was also present in other nightlies and in 12.1.
The last option I can think of right now is buying a new battery, but since that would be pretty costly and since I'm not sure that would solve my problem I wanted to run this by you to see if anyone here would have an idea of what could solve it.
Thank you very much in advance for your help!
Click to expand...
Click to collapse
Not ROM related. I am running CM13 and was having the same issues. Take apart the tab, and lift the battery connector vertically. There might be some tape, take that off first. Let tab sit for 5 min, then reconnect. Fixed my issues
ReyDelGuaguanco said:
Not ROM related. I am running CM13 and was having the same issues. Take apart the tab, and lift the battery connector vertically. There might be some tape, take that off first. Let tab sit for 5 min, then reconnect. Fixed my issues
Click to expand...
Click to collapse
Thanks for your reply! Although I did try dis- and reconnecting the battery, I've tried your advice. It's too soon now to tell now whether it works, I'll check back with you once I know more.
Hello,
Same problem for me: bootloop near 15% battery charge and she never charge more than 90%. I'm sorry but i'don't understand the method to fix this problem.
Thanks
jemsgaelle said:
Hello,
Same problem for me: bootloop near 15% battery charge and she never charge more than 90%. I'm sorry but i'don't understand the method to fix this problem.
Thanks
Click to expand...
Click to collapse
This battery connector should be re solder due to hairline cracks, you need a microscope to see it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Someone just disconnect and reconnect the battery to fix the problem, the white connector has loose connection,
this one needs to be fixed too by adjusting the opening tip of battery cables
Samsung fix the issue of loose battery connection by using this silver conductive glue
This is a repair from Samsung center, they soldered battery cables directly to the connector to fix loose connection,
without knowing this, an average user will damage the mainboard and battery connector while trying to remove the battery.
jemsgaelle said:
Hello,
Same problem for me: bootloop near 15% battery charge and she never charge more than 90%. I'm sorry but i'don't understand the method to fix this problem.
Thanks
Click to expand...
Click to collapse
What you need to do is take the back cover off the tablet and look for the battery connector, it's basically a few bundled wires that connects the battery to the tablet. You need to disconnect these (I used a pencil to wiggle it a bit, make sure you do it carefully) and let it rest for about 5 minutes. After that, reconnect it and turn your tablet on. That should fix the issue that you're having.
Beut said:
This battery connector should be re solder due to hairline cracks, you need a microscope to see it
*Image*
Someone just disconnect and reconnect the battery to fix the problem, the white connector has loose connection,
this one needs to be fixed to by adjusting the opening tip of battery cables
*Image*
Samsung fix the issue of loose battery connection by using this silver conductive glue
*Image*
Click to expand...
Click to collapse
Stupid question maybe, but could this loose connection also be a solution for the drain I'm having?
ReyDelGuaguanco said:
Not ROM related. I am running CM13 and was having the same issues. Take apart the tab, and lift the battery connector vertically. There might be some tape, take that off first. Let tab sit for 5 min, then reconnect. Fixed my issues
Click to expand...
Click to collapse
Your fix does seem to improve battery life a little bit, but unfortunately I'm still stuck with a pretty big drain. When totally idle it drains 5% per hour, so it dies after about 18 hours of being totally idle.
It should be able to last longer than that right? Any suggestions from anyone are welcome!
You should fix both battery connectors: black male connector needs to be re soldered, white female connector with 6 wires needs to be adjust the opening of battery cables.
Some may need to fix one, not both, but for sure, both need to be fix, the same procedures Samsung repair center will do: fix both connectors.
Regardless what model you have, the same fix applies to Samsung 10.1 and 12.2.
I have been fixed Samsung Note 2014 10.1 ( LTE and Wifi ), Samsung Note Pro 12.2 ( LTE and Wifi ) and Tab Pro 12.2 tablets, they all have the same problem of battery connectors.
Beut said:
You should fix both battery connectors: black male connector needs to be re soldered, white female connector with 6 wires needs to be adjust the opening of battery cables.
Some may need to fix one, not both, but for sure, both need to be fix, the same procedures Samsung repair center will do: fix both connectors.
Regardless what model you have, the same fix applies to Samsung 10.1 and 12.2.
I have been fixed Samsung Note 2014 10.1 ( LTE and Wifi ), Samsung Note Pro 12.2 ( LTE and Wifi ) and Tab Pro 12.2 tablets, they all have the same problem of battery connectors.
Click to expand...
Click to collapse
how does it cost to fix it without warranty at samsung
It may cost you over $100 for a round trip to Texas.
Anyone or shop who can do the rework can help you with little charge as much as $60. It takes only 5 to 10 minutes to get it done.
Just outta interest, which 'Mode' are you using?
I've found the stock 'Balanced' Mode (cm-13.0), drains my T325 alarmingly fast.* Unless I switch over to the 'Efficiency' Mode, which seems (for me), to work like the old 'Balanced' Mode from cm-12.1 had.
*Alarmingly fast here would be a compleat drop from ~100% to Dead with in 90 minutes. Note I'm less sure if that's the nature of that Mode , or if it's just the stress of coming off a clean install, and the rebuilding the OS up again. But, since moving to cm-13.0 I've been sure to change up to the 'Efficiency' setting. And, so have been enjoying upwards of +7H of use.
Ichijoe said:
Just outta interest, which 'Mode' are you using?
*Alarmingly fast here would be a compleat drop from ~100% to Dead with in 90 minutes. .
Click to expand...
Click to collapse
Battery connector problems are not related to software or firmware; quick discharge, battery capacity fluctuations, long charging or never get full charge are all common problems of Samsung tablets regardless whatever you're running or settings
Ichijoe said:
Just outta interest, which 'Mode' are you using?
I've found the stock 'Balanced' Mode (cm-13.0), drains my T325 alarmingly fast.* Unless I switch over to the 'Efficiency' Mode, which seems (for me), to work like the old 'Balanced' Mode from cm-12.1 had.
*Alarmingly fast here would be a compleat drop from ~100% to Dead with in 90 minutes. Note I'm less sure if that's the nature of that Mode , or if it's just the stress of coming off a clean install, and the rebuilding the OS up again. But, since moving to cm-13.0 I've been sure to change up to the 'Efficiency' setting. And, so have been enjoying upwards of +7H of use.
Click to expand...
Click to collapse
I was really hoping that that would've been the problem but unfortunately I had already set it to efficiency mode thanks for your reply though!
Although I trust my software capabilities more than my hardware know-how, the issue is getting so frustrating that I'll try Beut's solution. I will report back after I tried it!