D
dave_or_did
Guest
I've got an LG G3 which was working fine. I got a new 128GB SD card though and after I transferred my data from my old 16GB card to this as well as a load of music, the battery life on the phone became ridiculously poor. It only lasts maybe 5 hours if I'm lucky when it used to last all day, sometimes 2 if I didn't use it much.
I tried reformatting the SD card and left it empty for a while and the phone worked fine. When I went back and added my music again though (not the old Android files I'd added before) the battery went crazy again. The top of the phone gets warm too.
I've looked at the Battery Usage and when I've got the problem the biggest battery use is coming from Android OS, with Android System not too far behind and Screen, which is as usual.
I tried SD Card monitor which was supposed to detect SD problems, but that didn't show anything.
I know people have had this problem before, but the answers have always been a bit all over the place, so I thought I'd open a new one specifically for my problem.
On other similar posts people have suggested that there's a corrupt file causing Android to get caught in a loop indexing it, but is there any way of finding out which file(s) is corrupt? I've got about 100GB of music so it'll be a nightmare to work out what might be broken through trial and error.
Thanks
I tried reformatting the SD card and left it empty for a while and the phone worked fine. When I went back and added my music again though (not the old Android files I'd added before) the battery went crazy again. The top of the phone gets warm too.
I've looked at the Battery Usage and when I've got the problem the biggest battery use is coming from Android OS, with Android System not too far behind and Screen, which is as usual.
I tried SD Card monitor which was supposed to detect SD problems, but that didn't show anything.
I know people have had this problem before, but the answers have always been a bit all over the place, so I thought I'd open a new one specifically for my problem.
On other similar posts people have suggested that there's a corrupt file causing Android to get caught in a loop indexing it, but is there any way of finding out which file(s) is corrupt? I've got about 100GB of music so it'll be a nightmare to work out what might be broken through trial and error.
Thanks