Thread: Switching SmartReflex on the fly?
View Single Post
vi_ is offline vi_
2012-02-07 , 15:23
Posts: 1,680 | Thanked: 3,685 times | Joined on Jan 2011
#15
I shall stop being flipant for once...

Originally Posted by demolition View Post
@vi_ Thanks for your tips. From what you say there's no need to activate/deactivate SmartReflex because of the way KP-49 is set up? Info on all of this seems quite dispersed and if someone misses a thread (or sometimes a mere post) or two on TMO, he/she is none the wiser (OP is good example). I think we all* need to have a good read of recent developments and the new "ideal" setup. I saw one post of your's in the KP-49 thread saying don't bother with xulv etc. but I'm sure there's more to know for optimal basic setup.
*we all - those of us not actively involved in creating or regularly commenting on system development.

You are right, my comments are a little confusing and subtly rude. Information is all over the place and a combination of things moving at rapid speed with no documentation means it is easy for a new person to become lost. I just assume everyone is like me and will devour the facts presented all over the place to create a coherent 'whole' understanding of the subject at hand. There literally is no more too it.

Enable smart reflex, either by kernel power settings or some shell script and never load an undervolt profile again. Job done. That is all. The smart reflex values for your own personal CPU are calculated from values internal to your CPU giving you your own personal PERFECT undervolting profile that tweaks itself depending on load. I know, incredible! Thank you freemangordon, we have the beerfund, now tell us where to send it.


Originally Posted by demolition View Post
I have found even "hidden" networks are visible to the N900. Surely if you've got the password, connecting is the same as to those networks that announce their SSID?
I was suggesting that to connect to a network which does not broadcast it's SSID is to use xterm and connect by the stations BSSID. Again I was being flipant. I am sure connect now works perfectly well for this task.


Originally Posted by demolition View Post
You said remove "widgetz". what do you mean by this term? Isn't QB for preparing widgetz? Or do you simply mean the pre-installed ones like the amazon etc.?
Clearly, an item that doesn't poll isn't quite the same level of a juice-drinker as one that does poll or auto-connects. All the same, it seems some desktop items are more hungry than others.
- what's you're differentiating factor b/w widgets and widgetz? (following comment to don_falcone)
The difference between widgets and widgetz is an ideological one. Here I was making a wry reference to the dirth of badly programmed junk that some users love to install on their machines, usually just before they start a 'why is my battery life so short thread'. It is not as simple as to whether the widget polls hardware or not. Python stuff requires you to load in a stack of python libs, QT stuff requires me to have a bunch of QT libs in memory. All this affects performance. Take callnotify for example, it appears to be a well made and useful piece of software. It is not. It is a python script that causes over 400 wakeups/S. While it's function is semi useful it is not worth pulling my CPU out of C4 for.

Queen beecon widget is different. It has been very well coded by a skilled programmer. With smart scripting its performance impact is quite small. The performance cost to benefit ratio is very much in its favor. Thus it has passed the test and shall be classed as a 'widget'.

Marmistz post above is a prime example. WTF is qcpufreq with a modified helper script? (ok, I already kind of know but that spoils the point). The fact is you do not need any more junk to overclock/underclock/tweak/mod/hax than you already have with just a basic setup. The more of this trash you install the worse your system gets. Of course you are free to customise your n900 how you see fit, that is the beauty of this computer, but just understand that it has finite battery life and every computer cycle burned through chores your juice.

Consider my case, I evolved over the series of several months from the original setup to 9 desktops with the ideas behind batterypatch (swapping junk around using dbus-scripts( before batterypatch was even conceived of)) and over 30 QBW. Then one day my hardware failed and I had to get a new n900. I now have 3 desktops and 4 QBW total. Now the system is fast and has good battery life. The system is complete, not when there is anymore to add but when there is no more to take away.

I do not wknow where I am going with this rambling nonsense, damn I wish I was as eloquent as mentalist_traceur.


Originally Posted by demolition View Post
From experience, I've found the order of installing/uninstalling can make a difference. I suppose that if nothing else is installed except CSSU and KP, on a "fresh" system, there's no difference in outcome, whichever is installed first. And, as much of the system set up should be done at this point?
The stuff I have highlighted above is 'order agnostic'. The order in which you install things SHOULD have little effect on the final system.

Also, do not use any voltage profiles anymore.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
Last edited by vi_; 2012-02-07 at 15:30.
 

The Following 3 Users Say Thank You to vi_ For This Useful Post: