Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 12 hrs, 3 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days ago - more...
| The Following 19 Users Say Thank You to tonism For This Useful Post: | ||
calvin_42, cb00, cheve, DrWilken, eerde, elstupidos, esthreel, Fötus, gabby131, Gusse, jakiman, jurgel, Mr. Incredible, NokiaRocks, patlak, titan, todor_tsankov, vi_, woody14619 | ||
|
2010-05-06
, 09:20
|
|
Posts: 1,729 |
Thanked: 388 times |
Joined on Jan 2010
@ Canada
|
#102
|
Originally Posted by tonism
is that already available?
New starving conf is ready! Looks like everything is okay and stable now from the frequency range from 125 - 1150 MHz
__________________
if i did help you, just click "Thanks" on the lower right of my post. thanks!
"The best way to break a Spell is to prevent it from being cast in the first place"
N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;
if i did help you, just click "Thanks" on the lower right of my post. thanks!
"The best way to break a Spell is to prevent it from being cast in the first place"
N900: 1000/1150mhz; sampling_rate 15; up_threshold 150000;
|
|
2010-05-06
, 09:23
|
|
Posts: 284 |
Thanked: 320 times |
Joined on May 2010
@ Peterborough, UK
|
#103
|
Is nobody else experiencing the same bug as me, where the frequencies seem to get "shifted" one along in kernel-config show?
 |
|
2010-05-06
, 09:42
|
|
Posts: 20 |
Thanked: 37 times |
Joined on May 2010
@ Estonia
|
#104
|
Originally Posted by Tigerite
Yes, I'm having that same strange shifting. It seems to me that the value for 0 MHz is ignored and therefore all the settings get shifted.
Is nobody else experiencing the same bug as me, where the frequencies seem to get "shifted" one along in kernel-config show?
Hopefully titan can shed some light on that matter and now, if all, does it effect anything. But it looks to me as if it just gets incorrectly reported because, as I've stated before, when I increased the voltages, the stability issues went hand-in-hand of what was written in the conf, not what was reported.
Last edited by tonism; 2010-05-08 at 23:17.
|
|
2010-05-06
, 09:51
|
|
Posts: 284 |
Thanked: 320 times |
Joined on May 2010
@ Peterborough, UK
|
#105
|
That's what I thought too regarding 0 Mhz, however the 500 Mhz setting shown for me was completely different to any in FREQS which is rather perplexing (almost as if it isn't overwriting the previous setting)? As you say, I do hope titan can shed some light and/or fix the bug..
 |
|
2010-05-06
, 09:52
|
|
Posts: 415 |
Thanked: 161 times |
Joined on Apr 2010
@ San Francisco, CA
|
#106
|
How low do you think I can set 250mhz voltage? Titan's ULV 250mhz voltage is lower than your setting do you think I could make it even lower? Like set it to 22? or even 20 lol
|
|
2010-05-06
, 11:38
|
|
Posts: 20 |
Thanked: 37 times |
Joined on May 2010
@ Estonia
|
#107
|
Tigerite, my values are exactly shifted so every freq gets previous value when I look with kernel-config show. It shows "500:28,180" for me - this setting should belong to 250 MHz. But let's wait for titan regarding with that matter.
automagic68, sure! The voltages that N900 tolerates are varied. What might be stable for me can be unstable for someone else. Maybe you are really lucky with your device and can have 100% stable with even lower voltages. But be sure it actually is stable. titan's ULV and XLV values seemed stable and I could even lower my values, but in further investigation it turned out to be wrong and I suspect that ULV and XLV values are improperly tested. Just look at the graph -- they look odd to my due following reasons:
1) ULV's 250 MHz doesn't follow the pattern of all other profiles -- it should be closer to 500 MHz voltage than 125 MHz in order to be totally stable as my experiments showed to me (and is seen by other profiles as well)
2) XLV's 0-125 MHz voltage seem to be insanely low when compared to rest of the graph. I believe it was tested "stable at idle" (the error I did)
3) My starving conf has lower values throughout the spectrum except for ULV & XLV beginning. That doesn't follow the general trend. You would expect the ULV & XLV to excell in medium or higher frequencies as well then. The ideal, which seemed to be the best titan's conf, sadly doesn't go below 500 MHz, but even 500+ shows that this is where titan's conf stops. How can it be then that I can have even lower voltages in 500+ MHz but cannot get even to same level with ULV/XLV lower frequencies?
Last edited by tonism; 2010-05-06 at 11:42.
automagic68, sure! The voltages that N900 tolerates are varied. What might be stable for me can be unstable for someone else. Maybe you are really lucky with your device and can have 100% stable with even lower voltages. But be sure it actually is stable. titan's ULV and XLV values seemed stable and I could even lower my values, but in further investigation it turned out to be wrong and I suspect that ULV and XLV values are improperly tested. Just look at the graph -- they look odd to my due following reasons:
1) ULV's 250 MHz doesn't follow the pattern of all other profiles -- it should be closer to 500 MHz voltage than 125 MHz in order to be totally stable as my experiments showed to me (and is seen by other profiles as well)
2) XLV's 0-125 MHz voltage seem to be insanely low when compared to rest of the graph. I believe it was tested "stable at idle" (the error I did)
3) My starving conf has lower values throughout the spectrum except for ULV & XLV beginning. That doesn't follow the general trend. You would expect the ULV & XLV to excell in medium or higher frequencies as well then. The ideal, which seemed to be the best titan's conf, sadly doesn't go below 500 MHz, but even 500+ shows that this is where titan's conf stops. How can it be then that I can have even lower voltages in 500+ MHz but cannot get even to same level with ULV/XLV lower frequencies?
Last edited by tonism; 2010-05-06 at 11:42.
|
|
2010-05-06
, 12:26
|
|
Posts: 415 |
Thanked: 161 times |
Joined on Apr 2010
@ San Francisco, CA
|
#108
|
What is the best combination of applications to run to test if a voltage is "stable"? After setting a kernel as the default do you completely shutdown your N900 or just do a reboot? Would it be better to completely shut the phone down for 5-10mins then boot it up?
|
|
2010-05-06
, 13:06
|
|
Posts: 20 |
Thanked: 37 times |
Joined on May 2010
@ Estonia
|
#109
|
Originally Posted by automagic68
I've basically ran every app and menu corner I found from my phone for every voltage currently being tested per clock. That's what made it so time consuming, but that is how I found out what is absolutely stable and what isn't. So I advise you to do the same.
What is the best combination of applications to run to test if a voltage is "stable"? After setting a kernel as the default do you completely shutdown your N900 or just do a reboot? Would it be better to completely shut the phone down for 5-10mins then boot it up?
There are, however, programs that tend to show your instability best:
1) Media player MUST be able to show at least 2-3 music videos without problems (lockups, freezes, dropouts etc).
2) Micro B MUST be able to start up and render webpages without problems (lockups, freezes etc) for AT LEAST 15 min
3) Random apps that stress your CPU to 100% MUST NOT cause restarts, freezes, rendering problems etc.
4) And then the usual small things must be able to run in background too
5) Idling (allowing your CPU to rest) MUST NOT cause restarts, freezes etc
The reason why I used SO extensive testing was that I DID NOT wan't my conf to be stable just at Pi calculation etc, but to be able to run all scenarios without problems. So I just tested everything!
So my last 3 days were pretty sleepless, running constantly every possible app again and again and again.. :P
But as for loading new kernel conf, you don't need to shut down or restart your phone. New values are loaded "on the fly" (actually on the kernel-load command
) and you're good to go. The only situation, where I needed to restart my phone was, when video player told me that video format was not supported. That problem persisted until I restarted my phone. Maybe I could just kill and relaunch it, but restart solved it too. But be aware that, unless you symlink it to your def conf, every restart boots up with your default conf and not the conf you ran last time. But I assume you already know how to test or set default kernel confs.
Last edited by tonism; 2010-05-08 at 23:24.
| The Following 8 Users Say Thank You to tonism For This Useful Post: | ||
|
|
2010-05-06
, 13:59
|
|
Posts: 209 |
Thanked: 44 times |
Joined on Jan 2010
@ Austria
|
#110
|
Dear tonism
Thanks for your intensive testing of the voltages!
I have titan's experimental kernel maemo25 and tried to load your starving settings. But my N900 immediately restarted after applying your settings. x-terminal said somthing like "script is obsolete" and "sucessfully loaded" before it restartet. It was to fast to note it right.
I copied your starving settings in "kernel1.txt" and loaded it with "/usr/sbin/kernel-load /home/user/MyDocs/kernel1.txt"
Thanks for your intensive testing of the voltages!
I have titan's experimental kernel maemo25 and tried to load your starving settings. But my N900 immediately restarted after applying your settings. x-terminal said somthing like "script is obsolete" and "sucessfully loaded" before it restartet. It was to fast to note it right.
I copied your starving settings in "kernel1.txt" and loaded it with "/usr/sbin/kernel-load /home/user/MyDocs/kernel1.txt"
See the details, as usual:
default LV ULV XLV ideal starving
0 0,9750 0,9750 0,9125 0,8500 0,8750
125 0,9750 0,9750 0,9125 0,8500 0,8750
250 1,0750 1,0750 0,9125 0,9750 0,9500
500 1,2000 1,2000 1,0125 1,0125 0,9750 0,9625
550 1,2750 1,2000 1,0750 1,0750 1,0125 1,0000
600 1,3500 1,2750 1,0750 1,0750 1,0750 1,0250
700 1,3500 1,2750 1,1625 1,1625 1,1625 1,1125
750 1,3500 1,2750 1,1625 1,1625 1,1625 1,1250
805 1,3500 1,2750 1,2000 1,2000 1,2000 1,1625
850 1,3500 1,2750 1,2000 1,2000 1,2000 1,1750
900 1,3500 1,2750 1,2750 1,2750 1,2750 1,2125
950 1,3500 1,2750 1,2750 1,2750 1,2750 1,2375
1000 1,3500 1,3500 1,3500 1,3500 1,3500 1,2875
1100 1,5000 1,5000 1,5000 1,5000 1,5000 1,3875
1150 1,5000 1,5000 1,5000 1,5000 1,5000 1,4625
250 - 550 MHz conf: http://tonism.2bit.ee/N900/starving550
Default speed conf: http://tonism.2bit.ee/N900/starving
250 - 700 MHz conf: http://tonism.2bit.ee/N900/starving700
250 - 900 MHz conf: http://tonism.2bit.ee/N900/starving900
250 - 1150 MHz conf: http://tonism.2bit.ee/N900/starving1150
The default speed conf has voltage profiles for all speeds. Other confs skip some speeds.
The problem that I found was with the lower end frequencies. As you can see, ULV and XLV have some pretty strange lower end when comparing to the rest of the graph. I was able to get it stable while idle too with so extremely low voltages, but when I increased the workload there was just no way I could do anything. So my guess is that ULV & XLV low frequency range is not properly tested.
But this is my lowest stable conf for titan kernel. As always, use at your own risk and if they aren't stable for you, your N900 probably won't tolerate so low voltages. In that case try some of the titan's confs. But ULV & XLV voltages at the low frequencies seem little odd to me.
starving configuration for titan kernel
Last edited by tonism; 2010-06-25 at 23:25.