[HTC One V] olololosha:
Let me start a new thread dedicated to power saving problems of our amazing HTC ONE V device. Let's aggregate all knowledge about this together.

1. CPU Frequency settings.

How did you get these step frequencies? Is there explanation about rational voltage/freq settings, hardware SOC chip presets, or this was taken from mind? Why after 300MHz next freq is 800? where is step of 500MHz ? (for example)

2. do you know that ARM architecture has not only CPU freq/voltage tunings features? there is more then 10 hardware switchable timers and voltage control lines(regulators?) that used to be engaged in common powersaving routins. We have user-tuned CPU freqs, so what about GPU UV/OC? Sound subsystem? Heh, dunno, any clues?

3. as i noticed: fully charged ONE V(latest maxwen CM10 from 28/11 with HELLBOY kernel from 1/12) with screen off after 6 hours discharging did 50% discharge. And battery stats showed that 30% was consumed by phoneapp, and 30% by screen backlight. WAT??

a) screen was OFF almost all time, total time it was ON was less than minute, on a middle level of brightness.

b) I had phone conversation less then 5 minutes.

So, I guess, possible

a) there is something that do high load in phoneapp in background. That's ruined all idea of custom ROM. Possible inappropriate usage GSM tranciever? sound/mic hardware? failures in phoneapp routines with sound rendering?

b) there is incorrect backlight control behaviour. Wrong backlight voltage? Stay electrically enabled backlight/LED powerlines in offscreen? Higher power rates when screen is on? Overhead duty of light/proximity sensor?

and finally what I used to say:

a) on stock SENSE HTC ONE V ROM I had good battery saving results in standby 10% per 3-5 hours.

b) on stock ROM with TITANIUM KISS with OC/UV preset kernel I had better powersaving with 1.5GHz and lionheart/conservative governor 1-3 days of no-charge, even with wifi ON. (so as expected, lol)

c) on latest maxwen CM10 from 28/11 with HELLBOY kernel from 1/12 I had bad results: 50% in 6 hours(as I said earlier, with 5 min phone chat and 1-5 min of screen on, presets are: governor conservative, freq 200-800MHz, UV 700-950mV, wifi and 3g off)

Very possible, there were some optimal hardware(QUALCOMM/PRIMO) oriented powersaving algorithms in stock ROM, that allows to do fine voltage regulators tuning of LED, WIFI, GPU, sound subsystems. Stock kernel provides some PRIMO specific powersave API wich used by stock ROM, and CM10 does'nt know anything about it.

SO, I say CM10 & HELLBOY little bit inconvinient for everyday usage. We need more finetuning options in battery/screen/wifi chapters.

And second part of discussion:

1. Why voltages higher than 1.5GHz have so high voltage setting? Is there any hardware/datasheet explanations or it was just blind guess? What are minimal UV for these freqs?

2. What purpose of frequencies 24-122MHz? could we safely unlock them? Are they really used or just for lulz? Are they powersave effective?

3. Why freq steps are what they are? could we have more custom intermediate steps by kernel customizing, or they're hardware locked?

4. What is the problem with screen on amination?

5. What source of screen backlight flickering issue? Is HELLBOY flickering dirty hack safe enough?

Also share your UV/OC presets. My are: conservative/interactive/lionheart governor(wich give not much powersaving difference on CM10/HELLBOY as I told), SIO on disk and

24576-368640 700mV

768000 875mV //

806400 875mV // lower levels did unstable work and freezes on highload usage.

1024000 950 mV //

1200000 1150mV

1401600 1200 mV

1497600 1250 mV

1708800 1250 mV

1804800 1350 mV //

1900800 1450 mV // even -25 UV get 100% freeze after minute work.

2016000 1475 mV //

AnTuTu Benchmark v3.0.2 CM10/HELLBOY:

SIO, perfomance governor for full-time highest freq, no UV, 16bit transparency, antialiasing all disabled, developers features disabled.

245mgz 2637

1024mgz 4782

1500mgz 5599

2000mhz 6462 // 37.5 fps on knights, 8.1fps(max) on goblin fight scene