Active Topics
-
The N900 is now 15 years old! (8)
to Nokia N900 by whayong - 12 hrs, 13 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 5 days, 8 hrs ago - more...
|
2010-04-07
, 18:07
|
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#1572
|
Originally Posted by ticktock666
Try post http://talk.maemo.org/showpost.php?p...postcount=1484
I thought it had something to do with the lowered min speed limit from 250 to 125.
I'm thinking of flashing back to the stock kernel, then either use Titan's kernel and the trick to make changes stick and not disappear after a reboot, this will get me the 250 lower limit and a boost on the upper clock speed.
Edit : I've flashed back to stock kernel then installed Titan's version (big thanks to him) and set the Min/Max scale limits to 250 / 750 (by editing the /etc/pmconfig file) instead of 800, now the "dmesg | grep WARNING" command doesn't return anything and things are running smoothly enough, the "about" page is fine and will be testing with the Audio books later on to see if I'm over the stuttering problem.
if someone from the gurus can confirm and explain the messages returned by the "dmesg | grep WARNING" to just simply be warnings and not a sign of something much worse, I think I'll up the speed to 800 back again, but until then 750 is good enough for this trooper, like they say "just because you can doesn't always mean you should"
It accelerates CPU frequency switching and may help.
| The Following User Says Thank You to egoshin For This Useful Post: | ||
|
|
2010-04-07
, 18:08
|
|
Posts: 105 |
Thanked: 15 times |
Joined on Dec 2009
@ Baltimore, USA
|
#1573
|
So ive been successfully running at 900mhz/125mhz since yesterday afternoon.
I really wanted to get a temp widget working before i tried it.
I tried the Desktop CMD widget, but i always get "-40" for my temp
no matter what the load is or how warm its running.
my cmd is
has anyone else experienced this?
Last edited by madmaze; 2010-04-07 at 18:11. Reason: wrong slash
I really wanted to get a temp widget working before i tried it.
I tried the Desktop CMD widget, but i always get "-40" for my temp
no matter what the load is or how warm its running.
my cmd is
Code:
cat /sys/devices/platform/omap34xx_temp/temp1_input
Last edited by madmaze; 2010-04-07 at 18:11. Reason: wrong slash
|
|
2010-04-07
, 18:09
|
|
Posts: 36 |
Thanked: 8 times |
Joined on Apr 2010
|
#1574
|
Originally Posted by dimkit
Same here after loading.
i face the same problem too.
|
|
2010-04-07
, 18:14
|
|
Posts: 86 |
Thanked: 10 times |
Joined on Nov 2009
|
#1575
|
I am using the same kernel with 900/125. and desktop widget. i do get -40 after a reboot but it updates after some time.
|
|
2010-04-07
, 18:15
|
|
Posts: 105 |
Thanked: 15 times |
Joined on Dec 2009
@ Baltimore, USA
|
#1576
|
Originally Posted by new_bee
hmm mine has been giving -40 since last night =/
I am using the same kernel with 900/125. and desktop widget. i do get -40 after a reboot but it updates after some time.
|
|
2010-04-07
, 18:16
|
|
Posts: 946 |
Thanked: 1,650 times |
Joined on Oct 2009
@ Germany
|
#1577
|
Originally Posted by dimkit
I cannot reproduce your problem with the maemo19 kernel (250-700MHz).
i face the same problem too.
charging, usb cable, display lock etc - nothing changes the upper limit if its specified in pmconfig. I see no warnings in dmesg.
mikhmv also seems to have no problems over >24h.
are you using the 125Mhz kernel? which firmware version?
what steps are necessary to reproduce the problem?
I think the 125Mhz level only leads to problems...
|
|
2010-04-07
, 18:17
|
|
Posts: 992 |
Thanked: 995 times |
Joined on Dec 2009
@ California
|
#1578
|
Originally Posted by tissot
The reason is simple - battery.
There's a reason why Droid is running at 550mhz and N900 at 600mhz.
Stability is too but it is not for underclocking like Droid.
Frying has nothing with it - CPU was designed by ARM and basing on common technology licensing practice I guess TI didn't change anything in it's design because ARM did all work - thermal, radio emmision, delay propogation etc. So, TI got ARM design which can run on max freq from 600MHz to 1GHz.
However, the TI production line quality limits an effective max frequency and for stable run use 600MHz. But your mileage varies...
(usual disclaimer: anything here is for education purpose only and is not intended to convince you for overclocking or doing something bad).
| The Following User Says Thank You to egoshin For This Useful Post: | ||
|
|
2010-04-07
, 18:22
|
|
Posts: 362 |
Thanked: 113 times |
Joined on Feb 2010
|
#1579
|
Hi, I have been using 900/500dsp since a few days, and I just installed the kernel from app manager.... then did 1000000 echo etc command ...
it seems to idle at 250 now ?? no more 125....
id the dsp still 500 or has it changed back to normal??
it seems to idle at 250 now ?? no more 125....
id the dsp still 500 or has it changed back to normal??
|
|
2010-04-07
, 18:24
|
|
Posts: 36 |
Thanked: 8 times |
Joined on Apr 2010
|
#1580
|
Originally Posted by titan
I did not use the 125mhz-kernel. max-freq set at 900, min-freq at 250. Phones has been loaded a couple of times using the normal charger (no usb-connection made!). Used the phone to make a call and had a terminal-session open to my server upstairs... nothing special I think...
I cannot reproduce your problem with the maemo19 kernel (250-700MHz).
charging, usb cable, display lock etc - nothing changes the upper limit if its specified in pmconfig. I see no warnings in dmesg.
mikhmv also seems to have no problems over >24h.
are you using the 125Mhz kernel? which firmware version?
what steps are necessary to reproduce the problem?
I think the 125Mhz level only leads to problems...
Removed the m19-kernel since.
| The Following User Says Thank You to miwalter For This Useful Post: | ||
 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 13:44.
i face the same problem too.