battery drain is awful and frustrating

Haalcyon

Banned
Jul 19, 2013
7,662
0
0
Visit site
Have you disabled the AT&T bloat? I always do and am very satisfied with the battery life:
 

Attachments

  • 1426190808549.jpg
    1426190808549.jpg
    59.5 KB · Views: 30
  • 1426190907250.jpg
    1426190907250.jpg
    62.1 KB · Views: 30
  • 1426190925704.jpg
    1426190925704.jpg
    58.1 KB · Views: 31
  • 1426190942347.jpg
    1426190942347.jpg
    57.1 KB · Views: 29
  • 1426190955620.jpg
    1426190955620.jpg
    60.1 KB · Views: 29
  • 1426190969757.jpg
    1426190969757.jpg
    55.3 KB · Views: 29

sparksd

Well-known member
Aug 20, 2010
1,098
9
0
Visit site
All of those things need to be indexed. One bad ID3 tag on a song or one corrupted picture can cause a loop in the indexing service that may cause indexing to run at 100% until the bad file is removed.

If you take the card out and the problem persists, then it's not the card.

If you take the card out and the problem goes away, then either you got a bad card (even new ones can be bad sometimes) or one of the files you copied to it has a problem that Android just does not like at all.

The hard part about tracking something like this down is simply that the service covers a great many tasks, and any one of them could be causing it. Simple things like pulling the card allow you to narrow down the problem quickly.

This indexing issue with damaged files has been around a long time - I ran into it with an older device and a PDF file. I would have thought that the OS would do a couple of tries then give up on the offending file and move on, having tagged that file with an ignore flag or something similar. A corrupt user file like that should not lead to continuous poor performance like it does.
 

mlbyanks11

Well-known member
Dec 27, 2011
642
4
18
Visit site
All of those things need to be indexed. One bad ID3 tag on a song or one corrupted picture can cause a loop in the indexing service that may cause indexing to run at 100% until the bad file is removed.

If you take the card out and the problem persists, then it's not the card.

If you take the card out and the problem goes away, then either you got a bad card (even new ones can be bad sometimes) or one of the files you copied to it has a problem that Android just does not like at all.

The hard part about tracking something like this down is simply that the service covers a great many tasks, and any one of them could be causing it. Simple things like pulling the card allow you to narrow down the problem quickly.

Believe it or not I do have a few ringtones that don't play..now that you mention it

Posted via the Android Central App
 

muzzy996

Well-known member
Feb 3, 2011
1,087
0
0
Visit site
Try installing Better Battery Stats and see if it can shed some light on wakelocks.

I'm not sure why but rather than improve battery use statistics google has reduced the usefulness of battery stats in Android. It's much easier to determine what's wrong with root but without it it's next to impossible sometimes.
 

mlbyanks11

Well-known member
Dec 27, 2011
642
4
18
Visit site
This indexing issue with damaged files has been around a long time - I ran into it with an older device and a PDF file. I would have thought that the OS would do a couple of tries then give up on the offending file and move on, having tagged that file with an ignore flag or something similar. A corrupt user file like that should not lead to continuous poor performance like it does.

Now look at it..better but still shouldn't drain this bad while I'm sleeping

Posted via the Android Central App
 

Attachments

  • Screenshot_2015-03-13-07-24-24.jpg
    Screenshot_2015-03-13-07-24-24.jpg
    21.4 KB · Views: 49

z06mike

Well-known member
Jan 31, 2011
795
0
0
Visit site
Yeah something is not right. I would say you either 1)take it back to the carrier and get them to swap the battery and/or 2)do a factory reset and see if it helps.

It's not likely, but there is a chance you have a bad battery.
 

clevin

Well-known member
Nov 12, 2010
1,769
2
0
Visit site
I can't seem to figure out why this battery is draining so fast it's awful I have to charge it three times a day...it drains two percent every ten minutes or so..it's brutal...I'm not even using it..it sits on my desk all day at work except to check texts and what not...anyone have an idea why this is happening..it's a brand new unlocked ATT phone...only two weeks in...I don't get why it's happening and it's aggravating...any help appreciated...thank you

Posted via the Android Central App

If that's what you use it for, disable sync and data when not in use, clear running app from time to time. My battery drains 1-2% overnight.

@T-Mobile GN3
 

mlbyanks11

Well-known member
Dec 27, 2011
642
4
18
Visit site
If that's what you use it for, disable sync and data when not in use, clear running app from time to time. My battery drains 1-2% overnight.

@T-Mobile GN3

Well you also have a different carrier as well..not sure if that matters...

Posted via the Android Central App
 

clevin

Well-known member
Nov 12, 2010
1,769
2
0
Visit site
Well you also have a different carrier as well..not sure if that matters...

Posted via the Android Central App

not as much as one may think. I had experiences same battery drain before, overnight drop 20-30%. Everything stops when I turn off data when not in use and turned off sync.

There are just too many services in android sneaking in the background, and its pretty well-established that data transmission kills battery.