Try underclocking more. SZ uses the TI recommended thresholds, so it goes to max OPP pretty quickly.I was reading this in another topic:
is it supposed to do so now? I am on SZ 1.60 and it only shows e.g. OPP5/5 - I see no dmesg about OPP other than setting max now...dmesg | grep OPP | tail -n 1 and then some awk magic works well enough. The next sysinfo will give both the max and current OPP value, e.g. on my ReBirth unit it shows things like "250 MHz (OPP 2/5)" now...
it reports OPP5/5 at 600 mhz ??Try underclocking more. SZ uses the TI recommended thresholds, so it goes to max OPP pretty quickly.I was reading this in another topic:
is it supposed to do so now? I am on SZ 1.60 and it only shows e.g. OPP5/5 - I see no dmesg about OPP other than setting max now...dmesg | grep OPP | tail -n 1 and then some awk magic works well enough
Cool! Looks like you got the consumption below 0.1W -- that probably adds a day or so of standby time.I've found a way to save a bit more power in lid-close state:
The "middle mountain" is me issuing some register changes through serial.
Stay tuned for a firmware update. Hopefully it doesn't break anything..
Yes, this is a problem indeed. Writing only when logging stops or writing to /tmp/ has the disadvantage that all is lost when a crash happens. Is there an easy way to do write caching in RAM that is longer than the default writeback time? I guess not. I'll do it manually by writing to /tmp/ and only periodically do an append from /tmp/ to the actual log file.
Already suggested that long ago, nice that @_wb_ picks this up now
Disabling 26MHz clock in PMIC. Only can be done when idle, the clock is otherwise needed for almost everything on OMAP..Nice.. although can you tell us what it is you've found that saves a bit more?
You can try calling setvbuf() with _IOFBF and really large buffer, then call fflush() to write it out at will.
If you go on like this you will make the Pandora produce power by itselfI've found a way to save a bit more power in lid-close state:
The "middle mountain" is me issuing some register changes through serial.
Stay tuned for a firmware update. Hopefully it doesn't break anything..
_wb_: It would be nice if logging avoided writes to SD card, like do a write only when logging stops or at least every few minutes. Or write to /tmp/ and then move the file. Right now turning on the SD controller for the writes tends to screw up low power tests, even when interval is large, so I had to symlink logs/ to /tmp/ .
.
That's not really true, from my observations mA values tend to increase as the battery discharges, so it should be correct now.
GC needs new SD Cards anyways, so the faster the better 
