CPU Governor Menu (KUAL extension)

[knc1]

It looks more or less as expected.

I wonder why the max speed on the KT2 is less than on the PW3 -
unless it is maybe the different firmware versions.

I'll keep my eye on that value in reports to follow.

[rogerinnyc]

Well, I'm trying to help out here, but I need more hand holding, I think. I installed 1.3 on my KV by unzipping the file, getting a "gov-set" folder and putting that folder in my "extensions" folder on my KV. The "CPU Control" shows up in KUAL, so all good so far.

I get lost on generating a CPU report. I downloaded ONLY the Lua-Base-Penlight.zip from the other thread, unzipped it, got an "esys" folder and put that in "extensions". I get a "CPU Report" button within "CPU Control" in KUAL.

If I set "powersave" within CPU Control, everything slows down and I get a spontaneous reboot. If I click CPU Report after the reboot, I get....wait for it...another reboot. No personal document is generated.

So I'm sure I'm doing something wrong, but don't know what it is!

[knc1]

The top of your visible usb storage should look like:
/documents
/extensions
/esys
. . . .

If changing that governor settings on a KV makes that much difference, I really need to see that report.
(Your the second to report problems with changing the governor on a KV.)

[rogerinnyc]

OK, thanks. I can now generate a report before doing anything else with CPU Control, but I presume that's not the point? Unfortunately, if I enable powersave first, I'm likely to get into a reboot before I can get back to KUAL and generate a report. And, after a reboot, I'm back to default power. Or does just generating a report, without changing the governor settings first, still help?

[knc1]

The best information now is to run the report while using whatever is 'default' for your device.

Since all the people with battery run-time problems would have been running the 'default' governor.

For your device - 'ondemand' is probably the best choice.
And -
It can be 'tuned' - once I get enough information.

[rogerinnyc]

OK, this was run right after a reboot. Hope it helps.

[knc1]

Originally Posted by rogerinnyc

OK, this was run right after a reboot. Hope it helps.

Looks 'normal' to me.

I don't have a clue why the KV 'locks up' while running at low speed.
It will just have to be on my 'mysteries to solve' list.

[NiLuJe]

And here's a 4GB PW2 on FW 5.7.3 .

(Which has mostly been sitting asleep since its update a month ago, FWIW).

[knc1]

Thanks.

It looks 'as expected' -

Only the K5 so far has the 'conservative' governor included in the build.

I guess I will have to learn how to 'tune' the on-demand governor OR devise a usr-space governor driver.

[Gabbb]

Thank you guys, this is very interesting. Any idea how bad is the battery with performance mode on?

[knc1]

Originally Posted by Gabbb

Thank you guys, this is very interesting. Any idea how bad is the battery with performance mode on?

As bad as it can get.
Whatever that is.

'Performance': Locks device to the high frequency clock.

'Powersave:' Locks device to the low frequency clock.
Two reports so far that the KV will not operate properly on this one.

'Userspace:' Set by an external program (we don't have one yet).

'Ondemand:' This one is tunable with the report values marked (rw).
Documentation on its tuning is in the kernel.org source code tree.

On the K5 -
'Conservative:' Similar to Ondemand, but very aggressive about switching back to low speed.

= = = = =

Since the Kindle only uses power during page turns (or, that was the intent) - -
Keep track of your 'page turns per hour' - - -
Use the 'battery status' report add-in to get battery status in numbers rather than guessing at the icon position.

Let us know what you find out.
All new information and confirmation of old information requested.

# 98 98

[mergen3107]

Here is Kindle Touch 5.3.7.3 default mode report.

[knc1]

Originally Posted by mergen3107

Here is Kindle Touch 5.3.7.3 default mode report.

Thanks.

I have gotten a little bit side tracked from this project -
By bricking my own K2 - such things happen.
Plus, Amazon seems to have fixed the problem.

= = = =

There isn't a button for 'conservative' but you can edit one of the others if you want to try it.

I have my K5 set to 'conservative' - the battery run-time is most certainly longer, yet I don't notice any reduction in response.

None of the other models reported have a 'conservative' choice.
I do not know why Lab126 stopped including it in the kernel build.

[mergen3107]

knc1,
do you need more reports from various devices?
I can ask people on Russian fora like 4pda and the-ebook.org

[knc1]

It would be nice, but not urgent.