[Nexus 5X General] paul_one:
First off - thanks for replying.

I know I'm a bit of a d*-hole, but I'm a d*-hole with a purpose: trying to pinpoint what these/any issues are.

I would love nothing more than you being able to go "I've found out that the phone is doing X and that is causing it to lose battery, meaning I can't use it. Beware all those that do Y with their phones!".

This is what I'm saying.. You're doing many things and then trying to work backwards and attribute a specific thing (battery loss) to something which is probably lost in a mess of data. For example you've quoted the screen being below Chrome beta - which isn't a stock app.

You mention the OS being quite high on the list, which means it/you were doing something with the phone (it could have been syncing, I don't know what the situation was for that stuff).

You mention "using" the phone with the screen on, but I don't know what you were doing.

I know in my screenshots that the screen is the only thing listed in my test - the OS was doing nothing (as I hadn't even set up a google account at that time).

It does, I have 2 screenshots to prove it - I'll look at grabbing them off the phone and posting them up when I've finished typing.

I'll also look into doing a video if you're interested - it'll be rather boring for 30 minutes staring at the home screen on the phone, but I don't mind doing so.

This is a great bit of information here, although I think we need more info around it.

I personally don't like the idea of adaptive brightness for actual tests, as it is very dependent on the environment that phone is in and how it reacts to it - which is why I haven't enabled it yet. I would suggest any tests be done at a specific brightness.

I'm sorry but you can't generically say that 64-bit is "more efficient" (unless I'm reading that wrongly). All your comparison of 'using it similarly' is showing is that under unknown usage variances two different phones do different things.

I'm saying that your description and attribution of blame cannot be supported by such evidence.

My screen was on... for an hour. 10%.

I don't think I got screenshots of that as it wasn't actually 'scientific' (I did some random songs, I had to pause for about 2 minutes in the middle, I was moving the phone about, occasionally adjusting volume and switched the quality to "high" halfway through the first song, and changed some other settings to both wifi and network.. It wasn't a proper "test" since I was busy getting ready. I will try to perform an actual test tomorrow with settings recorded for comparison.

- I basically stated the results because it was a quick "it uses some wifi, uses the screen and speaker, and it only uses 10% of the battery" line.. So really I think you're looking at something which uses a fair amount of CPU time (causing lots of wakes possibly).

The key word we are disagreeing on here is "detailing" I think.

You're saying "I use it to do X, Y and Z through all these things, I'm looking at the battery monitor outputs of the stock android and GSAM and I don't know where the battery is going".

I haven't even properly used the phone yet - partly because I need to try and get a new SIM card (didn't realise everyone had started moving to 4FF already. It took people ~7 years to really move from 2FF to 3FF).

Another thing, you're talking about "experience", which is such a vague term that means very little and again you can't produce evidence for that as it's all personal. I'm talking about tests. Having the phone set up and executing a specific test to identify specific things.

Honestly, I'm not saying you aren't having this issue - whatever it is. I'm not saying that your phone isn't using up a lot of battery.

All I'm saying is that you don't have any idea why, and changing the phone without any idea what is going wrong means you will probably still experience the issue with a new device.

I would recommend you avoid flashing or unlocking the new device until you run some tests yourself and verify the problem exists in the normal handset. (Clarification: I'm not saying don't flash it after, I'm saying that unless you verify bits along the way then you don't know where the problem is).