first cycle and already posting battery issues :O give it at least 10 cycles.
my first cycle, while turned off, the first batt wouldn't go pass 92% even after 12hrs, had to turn on phone and charge and then turn off and charge more, that fixed it. maybe resets the battery calibration or something.
I suggest you go through cycles fast and if any issues, you can complain to seller asap instead of months after purchasing.
I think panicking for nothing. Just use the phone a lot over the next few days and recharge a few times. My battery life has just gotten better and better. First few cycles wasn't so great though. Now it's stellar.
Did you check gsam to see if its being held awake?
Now my external battery is at 50%, I have 2:30 hours screen on since I charged batteries and held awake is 45 minutes. Yes, very much time, but considering awake time takes as much energy as screen, I would have now 3:15 hours of screen on, and you when your external battery reached 50, had 5 hours. That is the worrying thing. But if you are saying that in your first cycles your battery was also lasting little, lets think that with mine is happening the same and that in the next cycles I will obtain a duration as good as yours.
But I don't understand why does the battery need a few cycles to reach its maximum capacity.
In the past, when I bought Samsung Galaxy S3 Neo, I think that the first cycle of the battery held for 4 hours of screen on, and all of the following lasted the same, duration did not get bigger when I took more cycles.
Also understand that just having the phone on in deep sleep will use some power. Now at least 24 hours, right? So that is a bit of juice also. Figure about 10% or so.
You're also on the oldest ROM. That shouldn't make a big difference, but it might matter some.
You're also on the oldest ROM because we use the same phone model, don't we?
The only thing I want is that my phone has the same duration as yours and as the phone of the review whose link I posted in the first message of current thread.
(2015-11-19, 22:46)maykelbembibre Wrote: [ -> ]You're also on the oldest ROM because we use the same phone model, don't we?
The only thing I want is that my phone has the same duration as yours and as the phone of the review whose link I posted in the first message of current thread.
No. I'm on the newest ROM. v2.5.
You've had it on and using it for 24 hours and you haven't even used half the first battery. Not too shabby. At least do a full cycle or two and then show your results.
It's **extremely** unlikely you got some bad copy of the phone that uses battery worse than other people's D6000. Just do as several people have suggested and use it hard for a week with several cycles and then see how it goes and let us know.
If you want to compare your phone to the review, charge it to full and run a long video from YouTube until the batteries are drained.
Thank you very much for all you information. For the moment in this first discharge cycle, external battery died with 7 hours screen on. I think it should be 8. The good thing is that when playing video, my external battery loses 12% per hour, which is very good. But with that statistic external battery would have died at 8 hours screen on an mine died at 7, so I think that the thing that gets to me is the held awake time. When the external battery died, GSam shown a huge 5 hours awake time. How could I reduce it? I have disable all unnecessary apps which I think have daemon services and I have been aware of killing unnecessary processes in Settings > Apps > Running. What more can I do? Apps like Wakelock Detector do not work for me because I deny to root my device.
try the app called Greenify, it should help heaps even without root.
it auto kills apps that you dont want to be running too often.
Thank you, I will try it.
The greenify app only allows me to stop VLC and Quickpic background services. But in Settings > Apps > Running I can see there are a lot of processes and services called "Google Services" or "Google Play Services". When I stop them several apps stop working, but if I leave running these processes I lose a lot of battery. Each 24 hours I have about 2 hours of held awake time and I think those Google Play Services are guilty.
Probably the kernel, not Google Services. This is the problem with most D6000. Specifically PowerManagerServices (ironic, no?) And qpnp-vm-bms.
BTW...currently at 50% on both batteries and 5 hours 30 minutes. Not stellar like my last run, but good enough.