Active Topics
-
Camera phone competition March 2023 "Endless" (30)
to General by Wikiwide - 3 hrs, 14 mins ago -
Maemo repository (3)
to Community by torsen - 12 hrs, 39 mins ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 1 day, 10 hrs ago -
TLS 1.2 for N9 is ready (27)
to MeeGo / Harmattan by smatkovi - 1 day, 15 hrs ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 2 days, 16 hrs ago - more...
| The Following 10 Users Say Thank You to Lehto For This Useful Post: | ||
|
2010-04-08
, 19:44
|
|
Posts: 23 |
Thanked: 17 times |
Joined on Dec 2009
|
#1802
|
Titan,
I have been running your kernel for a day and a half and run into an issue.
In those 36 hours, my device's screen has become unresponsive 3 times. Twice while listenting to a podcast via Panuchi and once where I don't remember what I was doing.
By unresponsive I mean that I cannot close or switch out of the app, and in one instance, I closed Panuchi, went to a desktop and couldn't click on any application shortcuts nor on any bookmark. The only thing I could do was restart the phone.
I do not know if this is related to overclocking, or if it is an issue with your kernel (could it be related to the screen calibration issue?). But, I did want to make you aware of the problem, and maybe get some feedback.
Thanks again for all the work you're doing on the Community Kernel, as aside from the screen becoming unresponsive (which frankly scares the crap out of me), it has been awesome.
Best regards,
Phono
I have been running your kernel for a day and a half and run into an issue.
In those 36 hours, my device's screen has become unresponsive 3 times. Twice while listenting to a podcast via Panuchi and once where I don't remember what I was doing.
By unresponsive I mean that I cannot close or switch out of the app, and in one instance, I closed Panuchi, went to a desktop and couldn't click on any application shortcuts nor on any bookmark. The only thing I could do was restart the phone.
I do not know if this is related to overclocking, or if it is an issue with your kernel (could it be related to the screen calibration issue?). But, I did want to make you aware of the problem, and maybe get some feedback.
Thanks again for all the work you're doing on the Community Kernel, as aside from the screen becoming unresponsive (which frankly scares the crap out of me), it has been awesome.
Best regards,
Phono
|
|
2010-04-08
, 19:46
|
|
Posts: 126 |
Thanked: 327 times |
Joined on Nov 2009
@ Finland
|
#1803
|
Originally Posted by PhonoN900
I dont think its the problem of titans kernel, however if you had too fast clock rate set the SGX gpu might of crashed as a side product leading to such odd behaviour (happened to me a few times when I was finding maximum speed for stock voltage).
Titan,
I have been running your kernel for a day and a half and run into an issue.
In those 36 hours, my device's screen has become unresponsive 3 times. Twice while listenting to a podcast via Panuchi and once where I don't remember what I was doing.
By unresponsive I mean that I cannot close or switch out of the app, and in one instance, I closed Panuchi, went to a desktop and couldn't click on any application shortcuts nor on any bookmark. The only thing I could do was restart the phone.
I do not know if this is related to overclocking, or if it is an issue with your kernel (could it be related to the screen calibration issue?). But, I did want to make you aware of the problem, and maybe get some feedback.
Thanks again for all the work you're doing on the Community Kernel, as aside from the screen becoming unresponsive (which frankly scares the crap out of me), it has been awesome.
Best regards,
Phono
__________________
My OC kernel collection
My OC kernel collection
|
|
2010-04-08
, 19:50
|
|
Posts: 2 |
Thanked: 10 times |
Joined on Apr 2010
|
#1804
|
[B][Friends/B]
I'm using kernel 930mhz 500DSP What got here http://www.farahfa.com/n900-custom-k...rnelslehto-oc/
I'm using the 48 hours already! All right on the device, the temperature in Use this Normal.
not present any problem in CLOCK to make and receive calls,
After receiving calls him a 125MHZ Being Idle, and using the device if it rises to 930Mhz Ate!
That is, the kernel works perfectly with me, With an Excellent performance!
I wanted a kernel ready Like this, So what with Clock 1000Mhz.
tanks
I'm using kernel 930mhz 500DSP What got here http://www.farahfa.com/n900-custom-k...rnelslehto-oc/
I'm using the 48 hours already! All right on the device, the temperature in Use this Normal.
not present any problem in CLOCK to make and receive calls,
After receiving calls him a 125MHZ Being Idle, and using the device if it rises to 930Mhz Ate!
That is, the kernel works perfectly with me, With an Excellent performance!
I wanted a kernel ready Like this, So what with Clock 1000Mhz.
tanks
|
|
2010-04-08
, 19:53
|
|
Posts: 72 |
Thanked: 5 times |
Joined on Apr 2010
@ Finland
|
#1805
|
Excuse me for not reading through all the 181 pages for the second time, but can someone tell me the x-terminal command to run those pi-tests?
Just want to do some calculations myself aswell, and ofcourse, to test stability.
Just want to do some calculations myself aswell, and ofcourse, to test stability.
 |
|
2010-04-08
, 19:55
|
|
Posts: 658 |
Thanked: 117 times |
Joined on Jan 2010
|
#1806
|
Originally Posted by Lehto
Im glad to be able to test your lower voltage kernel soon
Yes ofcourse!
I've noticed that the phone downscales very well with voltage. I can basically run 800mhz with less voltage than it normally runs on 500mhz mode. I noticed this today in battery life. The phone seemed to just keep going without battery depleting at normal crazy fast rate. Basically I concluded that it was due the 800mhz didnt need to be ran all that much and the undervolting saved lots of power. I will release an undervolting kernel for all this later on my site (maybe today), which is made for my device.
|
|
2010-04-08
, 20:00
|
|
Posts: 8 |
Thanked: 3 times |
Joined on Apr 2010
|
#1807
|
|
|
2010-04-08
, 20:03
|
|
Posts: 388 |
Thanked: 842 times |
Joined on Sep 2009
@ Finland
|
#1808
|
Originally Posted by PhonoN900
Every time a crashing/freezing/weird behavior/corruption problem is encountered on an overclocked device, the obvious reaction should be to lower the clock frequency (or even return to stock clocks for verification)...
I do not know if this is related to overclocking, or if it is an issue with your kernel (could it be related to the screen calibration issue?).
| The Following User Says Thank You to hqh For This Useful Post: | ||
 |
|
2010-04-08
, 20:05
|
|
Moderator |
Posts: 7,109 |
Thanked: 8,820 times |
Joined on Oct 2007
@ Vancouver, BC, Canada
|
#1809
|
Originally Posted by titan
Holy smokes. If that's true, that's one of the biggest bombshells in this thread; on the one hand, the Nokia folks tell us that we will "fry" our N900s if we lock the CPU at 600mHz, and on the other hand, they're doing themselves every time you make a phone call!
I noticed that during the call both min and max are set to 600Mhz (using console via ssh).
after the call the minimum is reset to 250MHz.
can someone confirm that during extended phonecalls, even with the stock kernel,
scaling_min_freq, scaling_max_freq and scaling_cur_freq are 600000?
it would mean that Nokia keeps your device at the dangerous 600MHz during an entire extended phone call!
Calling is overclocking!
Not only that, but I have strong reasons to believe that the phone call app "renices" itself to be the highest priority task running on the CPU, so it really could be driving that poor chip hard.
Originally Posted by titan
Does this mean that the processor is dropping back down during a phone call? Or is it de facto staying at 600 for long periods of time? I honestly hope it is dropping down to "safe" values...
after some tests I learned that:
1. phone call ring (outgoing) sets range [>=600,>=600]
2. during the phone call [250,>=600]
3. after the phone call [min,>=600]
>=600 means smallest available frequency >= 600MHz
__________________
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
qole.org --- twitter --- Easy Debian wiki page
Please don't send me a private message, post to the appropriate thread.
Thank you all for your donations!
| The Following User Says Thank You to qole For This Useful Post: | ||
|
|
2010-04-08
, 20:17
|
|
Posts: 23 |
Thanked: 17 times |
Joined on Dec 2009
|
#1810
|
Originally Posted by hqh
I am running at stock speed currently, and it has just happened again. Within 10 minutes of writing the post referenced above...
Every time a crashing/freezing/weird behavior/corruption problem is encountered on an overclocked device, the obvious reaction should be to lower the clock frequency (or even return to stock clocks for verification)...
Letho,
The highest clock speed I've been to was 900mhz. I've been running 800mhz almost exclusively (also 700, 750 and stock).
Again though, I changed it back to 600mhz before writing my last post, and in that time, my homescreen has become unresponsive once again.
Phono
| The Following User Says Thank You to PhonoN900 For This Useful Post: | ||
 |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 06:23.
I've noticed that the phone downscales very well with voltage. I can basically run 800mhz with less voltage than it normally runs on 500mhz mode. I noticed this today in battery life. The phone seemed to just keep going without battery depleting at normal crazy fast rate. Basically I concluded that it was due the 800mhz didnt need to be ran all that much and the undervolting saved lots of power. I will release an undervolting kernel for all this later on my site (maybe today), which is made for my device.