[Desire General] th3:
There's a simple script that allows inverted colours but there's no bookmarklets or extensions as such like for Firefox. All you do is tap and colours can be set as desired on a web page (pun): https://www.squarefree.com/bookmarklets/color.html

And yes, I had previously also found idle black image/browser page equated to 112-119mA while idle on my Kaloer clock screen equated to 92-98mA. The difference being the button backlight off in the latter. The OSMonitor/Current Widget values from battery calcs for the screen seem rough approximations within a margin of error since using big bright blue text comprising ~5% of the screen, compared to all black screen, compared to big green text or big white text on-screen made no difference whatsoever in the values it returned, which is not reality. Nor did turning down OLED subpixel luminance from 1000 to 500, which again is far from the actual physics. An absolute basic fundamental: OLED luminance is directly related to the RGB subpixel power draw.

BTW, uninstall any old PT version before installing the new one, reboot and then open it or it won't work as it should IME as it needs root permission to gain pixel power information.

Andycted: I had wrote about a week ago but not finished to post that I think you'll be surprised to see the 3G interface power draw once the PT app picks the correct phone and chips. Every latest research shows it consuming heavy power draw compared to the rest of the device chips and this is the known measured case on the N1. Assuming the hardware is the same on the N1, PT now does correctly identify the chips. Compare HSPDA to WiFi... the biggest negative for it by far is, for instance, loading a TechReport webpage my HSPDA with full reception takes 34s whilst WiFi at 2 bars takes 4s. The latency on my HSPDA connection is 110-300ms on average compared to 20-50ms with WiFi.

As to silicon power whilst at 0v; negligible, obviously until an app wakes the CPU up when you don't want - which shouldn't happen with any properly functioning app and it doesn't with any of the 138 apps I use, unless the app keeps a useful partial wake lock that it requires for its specific functioning (like browser downloads).

Edit: AOSP ROMs are definitely 'faster' as in smoother in functioning than Sense IME, and much more rigorous at maintaining a high level of free memory. But this smoothness with heavier tasks is to do with memory management more than anything else in my understanding. I'm not sure of benchmark differences or what they measure and are influenced by - it isn't something I've partaken in. The browsers and apps themselves I don't find any difference in until the Sense ROMs fall below 55MB whereas this AOSP ROM is always >90MB unused. Sense on 2.2 starts at 90MB free for me and quickly trickles down to 50MB free whilst after hours of many apps open and used, AOSP is still at 161MB free. And as you might have known from 2.1 Sense, it suffered from this regular perceived slowness and stuttering whenever the free memory fell below ~45MB, hence how HTC now fixed that.

FlatEric83: Yep, I remember such battery data amassed on the N1 forums some time back. Like: http://xdaforums.com/showthread.php?t=669497

http://xdaforums.com/showpost.php?p=7811883&postcount=87

There were many discussions on the N1 forums about it all, most wrong as either they just spoke without having anything to say, relied too much on making up their own understanding from elementary Web/Wiki or didn't understand the basics of silicon/battery electrics to arrive at correct conclusions. Eerily, a lot like the majority of online fora :P

-----------------------------------

- Sent via my HTC Desire -