droll | # 1551 | 2011-09-12, 01:34 | Report

thanks estel. i'm one of the users with kernel power + speed and battery patch. i'll try removing those patches, reverting back to nokia kernerl then upgrading to CSSU and finally reapplying power kernel. i've seen one user report that his device is stable with kernel-power + speed and battery patch. so it's a bit difficult to nail down at this point.

thanks for the information.

reinob | # 1552 | 2011-09-12, 07:57 | Report

I don't think I can help you much, but in http://wiki.maemo.org/Overclocking_N900 it says:
"the telephone app is closed-source and broken. After a phone call it sets the maximum to 600 Mhz and the minimum to 250 MHz (or 125 MHz if available) irrespective of what you have set before. The are some workarounds in the Kernel-power kernel."

Don't know what those workarounds may be. I have KP47 and use 125-900 but avoid { 125, 500, 550, 700, 750 } so I have effectively { 250, 600, 805, 850, 900 }

I haven't noticed my N900 going down to 125Mhz ever (not even after a phone call, but I only use GSM, not SIP).

Can you post your kernel config? (don't want to watch a video just for that) - before doing any call - and then after having made a call?

Morku | # 1553 | 2011-09-12, 12:05 | Report

@droll
I don't have any problems with CSSU 16.8, kp48 and speed patch. The latest battery patch makes reboot for me. I hope he can improve.

@rajil.s
Thank you but I don't know how to use dbus-script. The poster seems to have problems, too.

@reinob
Thats sad Do you mean this configuration?
My phone doesn't try to set frequency to 600. Just changes the minimum frequency to 125MHz after (or by incoming) calls.

---

Last edited by Morku; 2011-09-12 at 12:14.

reinob | # 1554 | 2011-09-12, 12:50 | Report

The above file is your "initial" configuration, but who knows what your speed patch may be doing.

I suggest you first run "kernel-config show", then receive a call, and then do "kernel-config show" again.

Post both outputs exactly as they are.

As a bonus point, you might try to disable any tweaks (speed/battery patch or whatever it's called), as this may be dynamically changing the kernel parameters..

droll | # 1555 | 2011-09-12, 15:04 | Report

i've fixed my stability issues. this is what i did:

1. remove speed patch and battery patch.
2. revert back to stock nokia kernel (remove kernel power v48)
3. upgrade to latest CSSU
4. reapply kernel power v48
5. reapply speed and battery patch.

the device no longer suffers from random reboots. it's been stable for the past 6 hours. as a downside, i can no longer enable smartreflex (it used to be stable for my device). that's a small matter really.

Morku | # 1556 | 2011-09-12, 15:07 | Report

The Speed Patch doesn't affect this issue. Its still the same with and without.
This is exactly what I am showing in my video

Now I am on ULV with "kernel-config load ulv". Changed limits to 500 and 750 again and enabled Smartreflex and made this profile as default. Here the result:
http://img6.imagebanana.com/img/ychk...0912170257.png
Now I received a call:
http://img7.imagebanana.com/img/gzxd...0912170423.png
Maybe interesting point: It still says 'avoid frequencies 125 and 250' but minimum frequency is set to 125...

J4ZZ | # 1557 | 2011-09-12, 18:08 | Report

If someone's interested, because appearently I'm not having any issues with kp48, speed and battery patches, smart reflex or whatnot.

Here's my kernel config:
If someone wants other config files too, just ask...



Greetz,


J4ZZ

reinob | # 1558 | 2011-09-12, 21:19 | Report

OK, sorry for not watching the video, but I prefer text-only (besides the pain of watching a youtube video over a crappy proxy at work.. makes you wish they would just block it

Can you "prove" that your N900 is actually going down to 125Mhz? (with conky or, better, by ssh'ing into your N900 from a PC?).

I mean, it could be that you don't have a problem after all. In theory the phone will not enter the frequencies which are listed as avoided, so what you have in the minimum is, in your case, irrelevant.

In any case, it may be that the phone app actually requires (by design) to jump back to 125/250 (whatever is available), so you might want to set your minimum limit to 250Mhz (as I have), and see if that's OK with you.

toxaris | # 1559 | 2011-09-12, 21:34 | Report

Hello.
A question about batterystatus.
I have searched the thread, but its alot of battery discussions and its hard to find.

Well. I have KP48 and CSSU installed and it works good.
But the batteryindicator in StatusArea does not report correctly.
I have a QBW that reports the battery percentage. That way I know when the batteryindicator in statusarea are supposed to change image to indicate whats left.

But at 88% left the indicater are supposed to change picture for 88% left, but the picture isnt changed untill its below 75%, its like its one picture behind.
Take a look at the batteryimages at this page and I think you will understand what Im tryng to say.
http://www.developer.nokia.com/docum...atus_area.html

Is there a way to get the batterystatus to update correctly?
Or is it a known issue?
Its a bit annoying that you might think you phone is almost fully charged when you actually only got 76% left, in the worst case.

I also want to add that I havnt installed any of these so called speedpatches or messed around trying load different batterymodules and so on.

Thanks.

peterleinchen | # 1560 | 2011-09-12, 21:35 | Report

reinob pointed it out, I think.

I have just checked it on my N900.
On activating a call the min is set to 600
during a call it is limited to min 250
and after a call min is set to 125

BUT as this freq is avoided, I did not see my N900 using 125 ever.

So. where is Your problem at all?