Active Topics

 


Poll: Do you think its possible to overclock the N900?!
Poll Options
Do you think its possible to overclock the N900?!

Reply
Thread Tools
Posts: 100 | Thanked: 18 times | Joined on Jan 2010 @ Bristol, UK
#5171
hi,

First of all. BIG THANKS to the people who have been working and assissting on this project! you guyz have made this community great

I am new to overclocking and linux but i am a good leaner I overclocked my n900 with the min and max frequencies set to 125 and 950 respectively. using conky i realised my frequency still never goes below the stock min frequency (250) even though i have set it to 125.. i did try kernel-config show in xterminal and it does say that the min frequency is set to 125 but according to conky its not.. is there anything that i am doing wrong?

btw can anyone advice me on which min and max frequencies are best for performance and even better battery life.

Thanks all

Saud
 
Posts: 43 | Thanked: 32 times | Joined on Jan 2010
#5172
Hi.

I've overclocked my phone and now I have a problem with the wiimote.

I play with DrNokNes with the GameGripper or the wiimote usually and never had a problem, until now.
Today I've tried to play with the wiimote but only could play for over a minute or two, after that a "lag" appears: for example in Super Mario World I press the left button and Mario moves to left ONE SECOND later, so it's impossible to play.
If I play with GameGripper or N900 keyboard all works fine, I can be playing for hours with no problem.
I've changed the maximum CPU speed between 250 and 900 MHz (250, 300, 350...) and the problem persists.
Finally I've uninstalled the power kernel and wiimote works fine again.

Could it be a bluetooth problem? I think not. I can send files via bluetooth with no errors.
 
Posts: 5,795 | Thanked: 3,151 times | Joined on Feb 2007 @ Agoura Hills Calif
#5173
Originally Posted by isorn View Post
Hi.

I've overclocked my phone and now I have a problem with the wiimote.

I play with DrNokNes with the GameGripper or the wiimote usually and never had a problem, until now.
Today I've tried to play with the wiimote but only could play for over a minute or two, after that a "lag" appears: for example in Super Mario World I press the left button and Mario moves to left ONE SECOND later, so it's impossible to play.
If I play with GameGripper or N900 keyboard all works fine, I can be playing for hours with no problem.
I've changed the maximum CPU speed between 250 and 900 MHz (250, 300, 350...) and the problem persists.
Finally I've uninstalled the power kernel and wiimote works fine again.

Could it be a bluetooth problem? I think not. I can send files via bluetooth with no errors.
If the problem was really due to overclocking, the pattern should go: overclock, you have the problem. Turn off overclocking, you don't have the problem. Turn overclocking back on, you have the problem. In other words, it's easy to stop overclocking, so it would be easy to test.

Unfortunately, you seem to really be saying that this has to do with the power kernel. At the same time, you seem to have been running with the power kernel before today (true? it's hard to tell from what you said) and just got the problem today. That would rule out the power kernel, if what I just typed is true.

The question to me is, does anyone else running with the wiimote have the same issue with the power kernel?
__________________
All I want is 40 acres, a mule, and Xterm.
 
Posts: 5 | Thanked: 0 times | Joined on Dec 2010
#5174
Originally Posted by woody14619 View Post
The auto-scaler is pretty well tuned on the N900 to adjust between 4 or 5 ranges.

Personally, I have a 4 tier setup: 500, 650, 800, 950 and battery tends to last me 30ish hours with normal usage, 50ish hours when mainly on standby (eg light texting, no major browsing, etc).
Hi, thanks for the reply, I am now using the IDEAL profile with 500mhz(Min) - 850mhz(Max) limits that goes with the ideal profile.

current freq: 850
min freq: 500
max freq: 850
avoid freq: 125, 250
active freq: 0:30,90 500:30,360 550:33,400 600:38,430 700:45,430 750:45,430 805:48,430 850:48,500 and so on...
SMARTREFLEX_VDD1=0
SMARTREFLEX_VDD2=0
GOVERNOR=ondemand
UP_THRESHOLD=75
SAMPLING_RATE=150000
IGNORE_NICE_LOAD=1
POWERSAVE_BIAS=0


As indicated on your post, you have a 4 tier setup with 500, 650, 800, and 950 as your only active frequencies? and the rest are in avoid freqs? am i right? My question is, are there any factors do you need to consider in choosing what frequency to skip and to be included in the avoid freqs? like in my case, running on a 500mhz-850mhz only with IDEAL voltages of titan, how would i know what freqs can be skipped and avoided? And lastly, what's the explanation for these skipping/avoiding frequency steps between your min and max preferred freq? what are the possible benefits of it? please enlighten me again once and for all.

Thanks again, and in advance.

Last edited by jothanan; 2011-01-08 at 10:15.
 
Posts: 43 | Thanked: 32 times | Joined on Jan 2010
#5175
Originally Posted by geneven View Post
If the problem was really due to overclocking, the pattern should go: overclock, you have the problem. Turn off overclocking, you don't have the problem. Turn overclocking back on, you have the problem. In other words, it's easy to stop overclocking, so it would be easy to test.
Well, Today I've flashed the phone and installed only the programs needed to play DrNokNes with the wiimote: DrNokNes and wiicontrol.

I've been playing Super Mari* W*rld for about half an hour with gamegripper, keyboard and wiimote without problems.

After that I've installed advanced power kernel and qcpufreq, shut down and reinit, configure qcpufreq witch CPU max speed = 900MHz and start to play.
One minute later the "lag" appeared. I could play with the keyboard and the gamegripper (no lag), but with the wiimote was impossible because of the lag.

Reboot, verify that qcpufreq hasn't modify the CPU max speed (600MHz) and try to play. The lag appears again.

Uninstall advanced power kernel, reboot and play: all works fine.

I've repeated all the steps with the nes emulator (iNes) and D*nkey K*ng: the same problem.

So I think that the problem only can be the phone, wiicontrol or the kernel.

Am I only the one who has this lag?
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#5176
I have different issues with power kernel. In the latest kernel 46, I get random shutdowns regardless of speed. The phone simply shuts down with no warning and then refuses to power up until battery removal. Always happens when phone is locked in pocket and moving around.

Another issue it developed at some point is incompatibility with some software. E.g., late kernels (don't know if 46 only) are allergic to alarmed (a python app). Installing it gets me the "telephony functions (including emergency calls) are disabled" on boot. Skipping alarmed did not yiels the error any more.

And, after installing some new software, I get the telephony error about 20 minutes or so after boot. Boots fine, I can call, text and link up to 3.5G, and after a while I get "telephony functions have been disabled due to a communication error". Needs reboot.

I was ready to return it, since it does it at 600 MHz, but after installing multiboot and backup menu multiboot I booted to stock kernel and it's rock solid for 48 hours straight. If slow.

Anyone else has any of these issues? What could possibly get me the telephony error? Can it b fixed without reboot? Is it a problem withthe modem driver equivalent?

I have seen this problem several times on the forum and they all result the same, reflash. Reflashing stock kernel fixes it but it's not really a fix, plus, it seems t indicate an issue with power kernel.

Help?
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 5,795 | Thanked: 3,151 times | Joined on Feb 2007 @ Agoura Hills Calif
#5177
Originally Posted by ndi View Post
I have different issues with power kernel. In the latest kernel 46, I get random shutdowns regardless of speed. The phone simply shuts down with no warning and then refuses to power up until battery removal. Always happens when phone is locked in pocket and moving around.

Another issue it developed at some point is incompatibility with some software. E.g., late kernels (don't know if 46 only) are allergic to alarmed (a python app). Installing it gets me the "telephony functions (including emergency calls) are disabled" on boot. Skipping alarmed did not yiels the error any more.

And, after installing some new software, I get the telephony error about 20 minutes or so after boot. Boots fine, I can call, text and link up to 3.5G, and after a while I get "telephony functions have been disabled due to a communication error". Needs reboot.

I was ready to return it, since it does it at 600 MHz, but after installing multiboot and backup menu multiboot I booted to stock kernel and it's rock solid for 48 hours straight. If slow.

Anyone else has any of these issues? What could possibly get me the telephony error? Can it b fixed without reboot? Is it a problem withthe modem driver equivalent?

I have seen this problem several times on the forum and they all result the same, reflash. Reflashing stock kernel fixes it but it's not really a fix, plus, it seems t indicate an issue with power kernel.

Help?
I don't know, but I can tell you that I'm running kernel 46 and Alarmed and I don't have the problems you describe.
__________________
All I want is 40 acres, a mule, and Xterm.
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#5178
It's truely a pain. I have no idea what I would have done without BackupMenu. I flash and I flash.

Odd thing is, it's predictable. I made a batch that restored my settings and installed my software and running it makes telephony fail.

I have since long lost hope of figuring it out, I was hoping for a cure to the symptoms? Say, reconnect with modem driver or somesuch?

Would a logging system help with my sudden death N900 sindrome? Maybe with my telephony problem?
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Posts: 1,729 | Thanked: 388 times | Joined on Jan 2010 @ Canada
#5179
@ndi

is your telephony problems occur after you restore settings via backupmenu?

-im no expert but my Galaxy S has the same problem after I flash and restore full settings and ROM. the way i was instructed to obliterate the problem is to reflash the modem.bin file which is kinda telephony file.

hope this gives relevant info....
__________________
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;
 
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#5180
Originally Posted by gabby131 View Post
is your telephony problems occur after you restore settings via backupmenu?

-im no expert but my Galaxy S has the same problem after I flash and restore full settings and ROM. the way i was instructed to obliterate the problem is to reflash the modem.bin file which is kinda telephony file.

hope this gives relevant info....
I can trigger it by restoring rootfs without restoring optfs under some circumstances. I don't see why, I was thinking maybe it's an alarm daemon issue.

After consulting a few gurus I realized that the alarms get registered with the hardware, so the phone can wake when off, so a corrupt alarm thing could be it. I haven't touched the alarms but with calendar and other stuff who knows.

It could be the source of my pain and why it's so unpredictable.

As for the telephony driver isn't that flashed with a normal flash?

Oh, and, Calendar is out of whack because when the phone powers down and I have to remove the battery 9/10 times it forgets date, time, area and so on so I jump time back and forth like nuts, on a daily basis. Data logging apps are destroyed. Battery eye has negative statistics.

Anyone know when all alarms are synced? Enable and disable all alarms and enter-exit calendar? Restart? Spy on alamque.ini or whatsitsname?
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 
Reply

Tags
cooking on gas, cortex-a8, faster, first to fry it wins!, hardware, its smoking, n900, need for speed, need for weed, nos, omap, omap3, omap3430, overclock, overclocking, soc, system-on-a-chip, the dogs, this thread got good!, vtec just kicked in y0!, warranty will be void, whooplah, zoom zoom


 
Forum Jump


All times are GMT. The time now is 04:04.