Quote:
Originally Posted by mswlogo
Trying to get to the bottom of bluetooth battery drain. I did a buch of tests.
I used the SAME 28014 SYS in V1.4 and V1.33
V1.33 no battery drain due to bluetooth (at boot) approx 50ma (30% brightness)
V1.4 has battery drain (about 3x normal) (at boot). approx 150ma (30% brightness)
Even though the Bluetooth is drain battery and may be in the builds SYS.
It's something else in the V1.4 Kitchen causing bluetooth to drain battery (on boot).
Again toggling bluetooth after boot clears it in all cases.
I'm gonna try 23518 in V1.3 kitchen.
In all cases I used Drivers - D3D - Xperia X2
So I was not crazy 28014 was good on battery, but when I ran it I built with v1.33. When I built 23518 and (and a 2nd 28014) that sucked battery down I used V1.4.
Could be something as simple as a reg tweak in V1.4 I don't know.
|
Finally, Finally, Finally, I think I got what I want.
I took 23518 and Opera Beta 2u from V1.4 Kitchen and put into v1.33 Kitchen and added XDA_UC.
And it works great.
I get the threaded email, Stable 23518 and BlueTooth that does not suck battery down. I've got my procedure to check battery down solid and I don't need to wait a day or two to know. I know instantly if the battery is gonna be crappy.
I also notice two other things that went away going back to V1.33.
I built like 8 times V1.44 and every time Exchange Quit in the middle on the first sync.
V1.33 did not.
When I paired my headset I had mention it was a fight to get it paired with it not finding it, prompting for password, then still failed. Now it found headset immediately and didn't prompt for password.
With bluetooth on, screen at 30% with data connection up but idle I'm at 45-50ma which is where you need to be for good battery life.
I can even answer the phone with the slider while opera 10 is running.
So all my issues were something that the V1.44 kitchen added (drivers? what ever) and it didn't matter what build you based it on they were all messed up. They were all 6.5.3 builds.