![]() |
Re: overclocking,,it is dangerous??
Quote:
D-o-n-t a-d-v-o-c-a-t-e b-u-l-l-s-h-i-t like saveCPU as *any* mean of protecting CPU. Our SoC [big-red-flashing-exploding-whatsnot-letters]doesn't have a temperature sensor[/bigetc]. So, only one thing, that saveCPU or other similar stuff check, is *battery* temperature sensor (precisely, BMI temperature sensor). Which is completely irrelevant to CPU temperature - You can literally fry CPU on gas oven, while battery sensor not going higher than 30 Celsius degrees for quite a time. --- Other for some posts that make me to do facepalm festival (for some reason, they grouped on last page), I totally agree that this thread was very educational. It's funny, cause on 8 pages, there was put much more useful info, than on 300+ pages "main" overclocking thread. I think it should be made into wiki article, cause current wiki things about overclocking are terrible wrong at some matters (or at least link to terrible wrong assumptions - I'm basically looking @ some wiki articles/threads by jakiman - no offense - but I don't remember if it was inside wiki or just linked). I'm quite busy ATM, but if no one get hands dirty before, I'll certainly summarize it in wiki, then ask freemangordon and other for audit. As always, when You need to summarize something You don't understand 100% - better safe than wrong ;) |
Re: overclocking,,it is dangerous??
Correct.
OMAP3 does not have an accessible thermometer inside the CPU core. So there is no way to tell how hot our N900 CPU is via some API. Only one we have access to is the battery temperature as mentioned., So these apps which rely on that is unreliable and just plain WRONG. |
Re: overclocking,,it is dangerous??
when i install savecpu my batterygraph shows cpu always have bar
|
Re: overclocking,,it is dangerous??
Quote:
|
Re: overclocking,,it is dangerous??
Hmm in the last hour my CPU was stuck at 900 MHz and turned quite hot unfortunately (NB: USB was connected). Conky indicates 'browserd' consuming 90% of CPU. Then i remembered previously starting the stock browser by clicking on a link in an email and closing the browser. Apparently the browserdaemon continued in the background for some reason. By starting and closing the browser again, the process was killed and situation back to normal: 250 MHz. I use kernel power48 and qCPUfreq
|
Re: overclocking,,it is dangerous??
Nice story, but what's the point?
|
Re: overclocking,,it is dangerous??
I'm using it at 250-500-1000 for 6 months and I didn't see any bad effect .
|
Re: overclocking,,it is dangerous??
Quote:
|
Re: overclocking,,it is dangerous??
Quote:
|
Re: overclocking,,it is dangerous??
Quote:
|
All times are GMT. The time now is 10:30. |
vBulletin® Version 3.8.8