Reply
Thread Tools
overfloat's Avatar
Posts: 486 | Thanked: 173 times | Joined on Apr 2008
#11
Originally Posted by lpph View Post
Also, overclocking will increase power consumption. Battery life will decrease and may heat with all the n810.

BUT, I'm not an expert and I'm talking of my experience with a Ipaq. There are apps for windows mobile that can downcloak CPU to increase battery life. An app like that may exist for n810 and also can be modified to do both over and downcloak, but I say it again I am not an expert. Also, I don't own a N810, but I think I will have one soon.
It should be done automatically on an on-demand basis. If you want to force one of the preset speeds (up to 400mhz) the easiest way is to use the advanced power applet.
 
Benson's Avatar
Posts: 4,930 | Thanked: 2,272 times | Joined on Oct 2007
#12
Actually, IIRC, Igor said that most devices probably could take some CPU overclocks, or potentially a DSP overclock with the CPU fixed at 400, but that any overclocking-induced crash related to DSP/CPU communications could leave the system in a state unrescuable with tools available outside Nokia.

Basically, before you start overclocking, you want a cold-flashing setup, which to my knowledge nobody outside of Nokia has actually done -- there's a lot of information out there, though, so with a little work that should be doable. (Flasher-3.0 supports it, you just need to make a cable and get everything talking right...)
 

The Following 2 Users Say Thank You to Benson For This Useful Post:
Posts: 1,101 | Thanked: 1,185 times | Joined on Aug 2008 @ Spain
#13
Originally Posted by Benson View Post
Actually, IIRC, Igor said that most devices probably could take some CPU overclocks, or potentially a DSP overclock with the CPU fixed at 400, but that any overclocking-induced crash related to DSP/CPU communications could leave the system in a state unrescuable with tools available outside Nokia.

Basically, before you start overclocking, you want a cold-flashing setup, which to my knowledge nobody outside of Nokia has actually done -- there's a lot of information out there, though, so with a little work that should be doable. (Flasher-3.0 supports it, you just need to make a cable and get everything talking right...)
What about this?
http://www.bu3sch.de/joomla/index.ph...serial-console
Would it work for a cold flash?
 

The Following 2 Users Say Thank You to maacruz For This Useful Post:
Posts: 4,030 | Thanked: 1,633 times | Joined on Jul 2007 @ nd usa
#14
Originally Posted by overfloat View Post
I wish my n800 ran at 400GHz
Did you call Nokia for a waranty replacement? I would,

bun

Last edited by bunanson; 2009-05-22 at 21:18.
 
qole's Avatar
Moderator | Posts: 7,109 | Thanked: 8,820 times | Joined on Oct 2007 @ Vancouver, BC, Canada
#15
In my own personal curmudgeonly opinion, the CPU speed is not the problem with the N8x0. The lack of hardware graphics acceleration is the problem. They're playing Quake 3 on our chipset (the OMAP2) over in Symbian world.

Also, in my own grouchy little opinion, the poor read-write speeds of the available storage technology (the built-in flash and the current crop of affordable [mini]SD cards) is also a huge factor in the apparent sluggishness of the system, overshadowing the CPU speed like an apartment building beside a bungalow.
 
Munk's Avatar
Posts: 229 | Thanked: 108 times | Joined on Oct 2007 @ Sacramento, California
#16
I remember the thread a long time ago with Igor talking about this. However, I always have been one to overclock all of my PDA's and desktop CPU's, GPU's. If someone here is able to make a kernal that theoretically would run the CPU/DSP at 433/166 or whatever it mathematically ends up being, I wouldn't mind being a guinea pig.
 
Posts: 1,224 | Thanked: 1,763 times | Joined on Jul 2007
#17
Originally Posted by qole View Post
In my own personal curmudgeonly opinion, the CPU speed is not the problem with the N8x0. The lack of hardware graphics acceleration is the problem. They're playing Quake 3 on our chipset (the OMAP2) over in Symbian world.
They are using smaller screens - the OMAP was designed with a maximum screen size of 640x480 in mind, so this is all the video ram available on board. If you use system ram for video ram you get a huge performance hit (about 33% on OMAP1 in my tests), due to the low memory bandwidth of the OMAP.

About your second suggestion - my guess is that it is more about low amount of ram than storage speed. Of course, faster storage means faster swap, so it will certainly improve the situation.
 

The Following 2 Users Say Thank You to Matan For This Useful Post:
Posts: 4,030 | Thanked: 1,633 times | Joined on Jul 2007 @ nd usa
#18
Originally Posted by Matan View Post
...If you use system ram for video ram you get a huge performance hit (about 33% on OMAP1 in my tests), due to the low memory bandwidth of the OMAP.
....
This is a start....Mind to show us more, like how to do it, UH?
bun
 
Posts: 1,224 | Thanked: 1,763 times | Joined on Jul 2007
#19
You can't do it, since it is an hardware issue. It was up to Nokia to do it, and they decided to use an external video controller, instead of the internal OMAP one. Thus gaining system performance, but losing on video performance.

I know about this, since the company I worked for designed an OMAP based 800x480 device, and we faced the same dilemma.
 

The Following 4 Users Say Thank You to Matan For This Useful Post:
Posts: 24 | Thanked: 0 times | Joined on May 2009 @ Washington State
#20
Originally Posted by Benson View Post
Actually, IIRC, Igor said that most devices probably could take some CPU overclocks, or potentially a DSP overclock with the CPU fixed at 400, but that any overclocking-induced crash related to DSP/CPU communications could leave the system in a state unrescuable with tools available outside Nokia.

Basically, before you start overclocking, you want a cold-flashing setup, which to my knowledge nobody outside of Nokia has actually done -- there's a lot of information out there, though, so with a little work that should be doable. (Flasher-3.0 supports it, you just need to make a cable and get everything talking right...)
I thought the bootable flash from computer (what I did to update my FW when I first recieved my N810) basically rendered the N810 unbrickable since you could reflash by connecting USB to PC and then holding the home button down while powering up. Would a CPU related crash prevent this from happening or something?
 
Reply


 
Forum Jump


All times are GMT. The time now is 14:44.