44k hours is still 5 years and its not going to be running at that speed 100% of the time unless you use your phone maxed 24/7 and dont sleep!
One thing is for sure in my case. I wont be using this phone in 2 years. there will be something better about.
Id be happy with 20,000 hours cpu lifetime so overclocking isnt a problem for me.
Hopefully i wont burn it out until Q4 when something better will be available
If these are real numbers - indeed 20K does seems enough time But I think, even in this case, the lifetime of the CPU could be prolonged if we find a way to read the actual CPU temp sensor and limit the max freq above certain temperature values through
This might sound nooby, and somewhat stupid... But surely if you're overclocking you are just changing the limit the chip can run at? Meaning that just because it is overclocked to X it doesn't mean it will be running at that speed all the time? Only when high cpu usage programs are run? I would very much like to speed my N900 up a little becuase I watch alot of films but the films run just below perfect, like 0.01 fps 2 slow and its noticeable, but I am a noob and have no idea how to use a flasher or use a kernel flasher file lol, from what I've read it seems this isn't doing so bad with the tests. Pretty cool that it can be overclocked lol, well done to everyone who has done it, you're the people that make the world go round.
Edit, I was on page 28.. There are over 120! Lol. Amazing.
This might sound nooby, and somewhat stupid... But surely if you're overclocking you are just changing the limit the chip can run at? Meaning that just because it is overclocked to X it doesn't mean it will be running at that speed all the time? Only when high cpu usage programs are run? I would very much like to speed my N900 up a little becuase I watch alot of films but the films run just below perfect, like 0.01 fps 2 slow and its noticeable, but I am a noob and have no idea how to use a flasher or use a kernel flasher file lol, from what I've read it seems this isn't doing so bad with the tests. Pretty cool that it can be overclocked lol, well done to everyone who has done it, you're the people that make the world go round.
Edit, I was on page 28.. There are over 120! Lol. Amazing.
Run X Term and become root, then type fiasco-image-update /home/user/MyDocs/zImagexxx.fiasco
Replace the xxx with correct mhz number, e.g. if your flashing the 800mhz you need to type fiasco-image-update /home/user/MyDocs/zImage800.fiasco
Remember X Term is case sensitive.
Once done please reboot.
This worked for me running PR1.1
If you want to return to the stock kernel then open X Terminal and become root, then use the following command apt-get --reinstall install kernel kernel-flasher and reboot.
What about previous steps, like getting a flasher, or similar?
What about previous steps, like getting a flasher, or similar?
For noobs that is, like myself lol.
Thanks,
Ryan
I used the on device fiasco method to clock it up to 900mhz, it took seconds to do and it also retained the 'about' info. Foolproof method, and running nicely so far.
I ran Conky on my stock N900, watched it idle at 250MHz, plugged in the cable, and after it jumped up to 600MHz until I dismissed the connection choice menu it settled on 500MHz. After I disconnected the cable it dropped right back down to 250MHz.
This seems like it could be troublesome with OC, since I usually tend to charge my phone overnight, probably for longer than it needs.
Then use the AC Adapter instead of plugging it in your computer...
Flashed mine to 900MHz, and adjusted /etc/pmconfig (with SmartReflex on)... after the reboot I've got corrupted animation and reboot loop. USB flash to 800 remediated the issue :-) Great stuff!
"SmartReflex on" could be maybe the reason for unexpected reboot... At least many person has such issue even with stock kernel.
Question to the Overclocker's community:
what is your experience with any OC kernel + "smartreflex enabled"?
is it working fine somewhere?
But I think, even in this case, the lifetime of the CPU could be prolonged if we find a way to read the actual CPU temp sensor and limit the max freq above certain temperature values through