Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 1 day, 2 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 1 day, 3 hrs ago -
Maemo repository (3)
to Community by torsen - 1 day, 18 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 2 days, 16 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 3 days, 22 hrs ago - more...
| The Following User Says Thank You to magick777 For This Useful Post: | ||
|
2012-02-06
, 22:14
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#2
|
Originally Posted by magick777
Have you just stepped out of a time machine from 2010? With kernel power49 smart relex is now fixed and working up to 900MHz. Why not just compromise with 900MHz? Read the KP stable v49 thread for details. Also, no need for undervolting anymore, SR does it for you better than your empirical tests show.
Over the years, I've messed with various kernel-power settings and reached the conclusions (valid only for my particular device), that
- any voltage profile less than "ideal" seems to introduce problems when accessing microSD
- using SmartReflex on VDD1 and VDD2 results in better battery life, but precludes overclocking beyond 805MHz
- the phone is stable at 250-805MHz with SmartReflex on VDD1 and VDD2 and has been running that way for a year
Now, without SmartReflex on either VDD and using the ideal voltage profile, the phone is perfectly happy at 1000MHz and this provides a noticeable speed boost to the interface. I wouldn't have chosen to do this two years ago, but warranty is no longer relevant and I have a spare N900 anyway. So, fine, we'll overclock the hell out of it. When we need to, that is. Battery life is still a concern, so I'd still like the phone to spend most of its time in 250-805MHz with SR, but to toggle SR and give me 1000MHz (preemptively) when I require it.
I don't want to do this by issuing a "kernel-config load xxx" on every lock/unlock as that takes upwards of half a second to complete, introducing a degree of lag and arguably defeating the purpose of the exercise. But, it has only just dawned on me that I can avoid this by setting the "ideal" voltage profile as default, then overriding clock speed and SmartReflex settings using sysctl. For instance:
/usr/local/bin/smartreflex:
#!/bin/shIt seems to work, so, is there any good reason not to do this? The logic I am thinking of employing here is not completely decided yet, but my thinking is that every time I unlock the phone, it'll be to load some sort of application and therefore, that I will benefit from full speed, briefly at least, every time I unlock the phone.
case $1 in
"on")
echo "805000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1" > /sys/power/sr_vdd1_autocomp
echo "1" > /sys/power/sr_vdd2_autocomp
;;
"off")
echo "0" > /sys/power/sr_vdd1_autocomp
echo "0" > /sys/power/sr_vdd2_autocomp
echo "1000000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "250000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
;;
esac
Maybe it needs to be coupled with a timer when we're on battery, because one of two situations will be true. If I unlocked the phone for short-term use, i.e. to read a message or check when my bus is coming, then it'll be relocked again after a minute or two, in which case that relocking can be used as the trigger for reenabling SmartReflex. The problem comes if I unlocked the phone to listen to music or take a phone call, and it perhaps remains unlocked for an hour or two. In this case, we'd want battery life over responsiveness of the user interface and should probably reconfigure accordingly.
So, I guess the logic that I am proposing can be described as:
- on phone unlock, disable SmartReflex and boost to 1000MHz. If on battery, set a timer to revert after five minutes.
- on phone lock, restrict to 805MHz and enable SmartReflex
and the rationale this is that it should improve the responsiveness of the phone / browser / etc. when first unlocking it and selecting or using an application. It is anticipated that this will not improve battery life as compared with leaving SmartReflex enabled, but that it will do a limited amount of harm. Am I making sense, or have I missed something? Comments, suggestions and improvements to this logic are invited...
The whole switching profiles thing is the basis for batterypatch. Go read the sources to find out more. Whether it works...well that is a major point of contention.
__________________
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.
| The Following 6 Users Say Thank You to vi_ For This Useful Post: | ||
|
|
2012-02-07
, 02:04
|
|
Posts: 167 |
Thanked: 204 times |
Joined on Jul 2010
|
#3
|
Originally Posted by vi_
Ahem. To all intents and purposes, yes. I did what I was going to do as far as overclocking was concerned and have left it alone since, well, 2010. Guilty of upgrading to KP49 and not reading the fine manual until I wondered why it had lost a few speeds. The shipped configs with SR enabled defaulted to a max of 805, so this was what I presumed remained the safe limit. I'll play with SR and 900MHz. :-)
Have you just stepped out of a time machine from 2010? With kernel power49 smart relex is now fixed and working up to 900MHz. Why not just compromise with 900MHz? Read the KP stable v49 thread for details.
Still, my reason for doing this was not to reopen the debate about battery life, for which SR wins. Mostly I just want more responsiveness and I am starting feel less conservative about overclocking to attain it (never even actually tested 1100, I just might). There's also the point that if I'm going to buy a microSDXC and load it up with media, I'd like all the speed I can get when it comes to dealing with larger volumes of files/artists/whatever. I haven't undergone a scientific testing process of testing, but I did recently manage to get it to crash at 900MHz with SR enabled on VDD1, I think, and only tried 1000MHz without SR on a whim. If I can use 900MHz with SR that *may* provide a solution, but, I'm becoming tempted to say if I can have 1000, 1100, 1150... what by now is the compelling reason not to?
Battery life remains a concern, but I now carry a USB power brick and most people have microUSB chargers, so it's less of a worry than it was. Doesn't mean that I don't benefit from SR most of the time, but, I'd ditch it for 30 seconds for a 200-250MHz boost if I could sensibly identify circumstances in which to do so. Device life is less of a concern; I won't do anything that causes more than a couple of crashes. If I really do fry it, which I doubt, I have good backups and spare hardware. Warranty is no longer relevant. The only real concerns (to me) are stability, performance, and not wasting battery for the sake of it.
Thank you though for your input, I was not aware of this and will RTFM and do some further testing with SR at 900MHz.
|
|
2012-02-07
, 08:34
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#4
|
If you want performance...
1. Do a complete reflash (unless you are convinced your setup is healthy)
2. Don't use widgetz
2. Install CSSU.
3. Install KP49.
4. Enable SR.
5. Change CPU speeds 500 low, 900 high.
6. Put swap on your SD card.
7. Apply some virtual memory tweaks.
8. Investigate compcache
9. Investigate swap reset script with cron/alarmd.
Do the above and your device will be as someone said, 'snappier than a crocodile at a penguin parade'.
// EDIT
Above is more or less my setup (except the swap on SD) and I see around 2 days battery life, and christ knows I am a serious fiddler.
Last edited by vi_; 2012-02-07 at 08:41.
1. Do a complete reflash (unless you are convinced your setup is healthy)
2. Don't use widgetz
2. Install CSSU.
3. Install KP49.
4. Enable SR.
5. Change CPU speeds 500 low, 900 high.
6. Put swap on your SD card.
7. Apply some virtual memory tweaks.
8. Investigate compcache
9. Investigate swap reset script with cron/alarmd.
Do the above and your device will be as someone said, 'snappier than a crocodile at a penguin parade'.
// EDIT
Above is more or less my setup (except the swap on SD) and I see around 2 days battery life, and christ knows I am a serious fiddler.
__________________
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 08:41.
| The Following 6 Users Say Thank You to vi_ For This Useful Post: | ||
|
|
2012-02-07
, 09:25
|
|
Posts: 1,523 |
Thanked: 1,997 times |
Joined on Jul 2011
@ not your mom's FOSS basement
|
#5
|
Originally Posted by vi_
How do you connect to WiFi APs w/ hidden SSID without ConnectNow Widget? "Browsing" from the statusbar plugin certainly doesn't work.
2. Don't use widgetz
|
|
2012-02-07
, 09:36
|
|
Posts: 560 |
Thanked: 422 times |
Joined on Mar 2011
|
#6
|
Originally Posted by vi_
Once device is reflashed, does the order of above operations matter?
If you want performance...
1. Do a complete reflash (unless you are convinced your setup is healthy)
2. Don't use widgetz
2. Install CSSU.
3. Install KP49.
4. Enable SR.
5. Change CPU speeds 500 low, 900 high.
6. Put swap on your SD card.
7. Apply some virtual memory tweaks.
8. Investigate compcache
9. Investigate swap reset script with cron/alarmd.
Do the above and your device will be as someone said, 'snappier than a crocodile at a penguin parade'.
// EDIT
Above is more or less my setup (except the swap on SD) and I see around 2 days battery life, and christ knows I am a serious fiddler.
Where can one find information for 7, 8 & 9?
| The Following User Says Thank You to demolition For This Useful Post: | ||
|
|
2012-02-07
, 09:50
|
|
Posts: 212 |
Thanked: 66 times |
Joined on May 2010
@ India
|
#7
|
Recently,I wanted to create a dedicated partition for easy debian.Got lot of helpful members around.Even then I could not mount it to that partition.while going through this ,I had to flash my device.But I learnt how to use gparted,created a swap space of 384 MB on sd card.After that I have edited /etc/pmconfig enabling smartreflex,cpu to 900 following vi's advice.Believe me my device became too fast.I stopped caring about battery long ago ,though smart reflex gives me best battery life of approximately 8 hours(my battery is old).
Thank you.
Last edited by udaychaitanya16; 2012-02-07 at 09:55.
Thank you.
Last edited by udaychaitanya16; 2012-02-07 at 09:55.
|
|
2012-02-07
, 10:13
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#8
|
How do you connect to WiFi APs w/ hidden SSID without ConnectNow Widget? "Browsing" from the statusbar plugin certainly doesn't work.
Once device is reflashed, does the order of above operations matter?
Where can one find information for 7, 8 & 9?
Compcache here.
As for the swap script, you will have to be a bit creative, I am sure Estel can chip in on that one.
__________________
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.
| The Following User Says Thank You to vi_ For This Useful Post: | ||
|
|
2012-02-07
, 10:33
|
|
Posts: 1,523 |
Thanked: 1,997 times |
Joined on Jul 2011
@ not your mom's FOSS basement
|
#9
|
Ok, so you actually also USE WIDGETS.
| The Following User Says Thank You to don_falcone For This Useful Post: | ||
|
|
2012-02-07
, 11:13
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#10
|
Originally Posted by don_falcone
I think you will find I quite specifically typed "widgetz".
Ok, so you actually also USE WIDGETS.
__________________
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.
| The Following User Says Thank You to vi_ For This Useful Post: | ||
- any voltage profile less than "ideal" seems to introduce problems when accessing microSD
- using SmartReflex on VDD1 and VDD2 results in better battery life, but precludes overclocking beyond 805MHz
- the phone is stable at 250-805MHz with SmartReflex on VDD1 and VDD2 and has been running that way for a year
Now, without SmartReflex on either VDD and using the ideal voltage profile, the phone is perfectly happy at 1000MHz and this provides a noticeable speed boost to the interface. I wouldn't have chosen to do this two years ago, but warranty is no longer relevant and I have a spare N900 anyway. So, fine, we'll overclock the hell out of it. When we need to, that is. Battery life is still a concern, so I'd still like the phone to spend most of its time in 250-805MHz with SR, but to toggle SR and give me 1000MHz (preemptively) when I require it.
I don't want to do this by issuing a "kernel-config load xxx" on every lock/unlock as that takes upwards of half a second to complete, introducing a degree of lag and arguably defeating the purpose of the exercise. But, it has only just dawned on me that I can avoid this by setting the "ideal" voltage profile as default, then overriding clock speed and SmartReflex settings using sysctl. For instance:
/usr/local/bin/smartreflex:
It seems to work, so, is there any good reason not to do this? The logic I am thinking of employing here is not completely decided yet, but my thinking is that every time I unlock the phone, it'll be to load some sort of application and therefore, that I will benefit from full speed, briefly at least, every time I unlock the phone.
Maybe it needs to be coupled with a timer when we're on battery, because one of two situations will be true. If I unlocked the phone for short-term use, i.e. to read a message or check when my bus is coming, then it'll be relocked again after a minute or two, in which case that relocking can be used as the trigger for reenabling SmartReflex. The problem comes if I unlocked the phone to listen to music or take a phone call, and it perhaps remains unlocked for an hour or two. In this case, we'd want battery life over responsiveness of the user interface and should probably reconfigure accordingly.
So, I guess the logic that I am proposing can be described as:
- on phone unlock, disable SmartReflex and boost to 1000MHz. If on battery, set a timer to revert after five minutes.
- on phone lock, restrict to 805MHz and enable SmartReflex
and the rationale this is that it should improve the responsiveness of the phone / browser / etc. when first unlocking it and selecting or using an application. It is anticipated that this will not improve battery life as compared with leaving SmartReflex enabled, but that it will do a limited amount of harm. Am I making sense, or have I missed something? Comments, suggestions and improvements to this logic are invited...