Active Topics
-
Camera phone competition March 2023 "Endless" (35)
to General by Maemish - 2 days, 10 hrs ago -
TLS 1.2 for N9 is ready (28)
to MeeGo / Harmattan by smartblu9 - 2 days, 11 hrs ago -
Maemo repository (3)
to Community by torsen - 3 days, 3 hrs ago -
Error after installing Leste on sdcard (11)
to Maemo 7 / Leste by Maemish - 4 days, 1 hr ago -
Introducing ubiboot N9 (multiboot OS loader) (1,393)
to Alternatives by smatkovi - 5 days, 7 hrs ago - more...
| The Following User Says Thank You to sulu For This Useful Post: | ||
|
2012-02-05
, 18:11
|
|
Posts: 67 |
Thanked: 32 times |
Joined on Oct 2011
|
#2752
|
i'm not sure sulu, but i believe it's the only file you need to edit.
notice when you remove 700 and 750 freq from the list and add the 720 one, you have exactly one less in frequencies count, so guess what it means and remove correct one from vsel and rate lists...
am i smart enough ?
and sorry all (including pali, freemangordon, estel, vi_) about some stupid things i said once in history since i am an computer pro but rather linux noob so there is sometimes things got crazy i said as a result - well i can't guess all linux technicalies so while posing pro i may *sometimes* say very nooob things. And all people which I said sorry to, I hope you don't have me at blackilist/ignore_list, or whatever the forum delivers, yet.
EDIT: my concerns about changing KP versions and multiboot was really dumb, and most of it i could checked myself (there was just old entries invalidated by update). BTW (for pure curiosity though) is it possible install both newer and older version of KP obtainable through multiboot ? (I'm curious if there exist some package maintaining trick or if it is just impossible with same named packages and different versions of them). Of course all my problems regarding my actual multiboot config was easily fixed (it was just to remove entries for older KP and older KBFS from the list since upgrade of packages removed things needed by old entries - what a my derp... - i have written about 4 posts about it some time ago while it was pretty obvious)
Last edited by majaczek; 2012-02-05 at 18:30.
notice when you remove 700 and 750 freq from the list and add the 720 one, you have exactly one less in frequencies count, so guess what it means and remove correct one from vsel and rate lists...
am i smart enough ?
and sorry all (including pali, freemangordon, estel, vi_) about some stupid things i said once in history since i am an computer pro but rather linux noob so there is sometimes things got crazy i said as a result - well i can't guess all linux technicalies so while posing pro i may *sometimes* say very nooob things. And all people which I said sorry to, I hope you don't have me at blackilist/ignore_list, or whatever the forum delivers, yet.
EDIT: my concerns about changing KP versions and multiboot was really dumb, and most of it i could checked myself (there was just old entries invalidated by update). BTW (for pure curiosity though) is it possible install both newer and older version of KP obtainable through multiboot ? (I'm curious if there exist some package maintaining trick or if it is just impossible with same named packages and different versions of them). Of course all my problems regarding my actual multiboot config was easily fixed (it was just to remove entries for older KP and older KBFS from the list since upgrade of packages removed things needed by old entries - what a my derp... - i have written about 4 posts about it some time ago while it was pretty obvious)
Last edited by majaczek; 2012-02-05 at 18:30.
|
|
2012-02-05
, 19:17
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#2753
|
Originally Posted by majaczek
My thoughts exactly.
notice when you remove 700 and 750 freq from the list and add the 720 one, you have exactly one less in frequencies count, so guess what it means and remove correct one from vsel and rate lists...
But how do I do that (without adding evil hacks to the kernel-config script)?
|
|
2012-02-05
, 19:37
|
|
Posts: 1,680 |
Thanked: 3,685 times |
Joined on Jan 2011
|
#2754
|
Originally Posted by sulu
Then you need to make a patch for a new version of KP!
My thoughts exactly.
But how do I do that (without adding evil hacks to the kernel-config script)?
FWIW!
I do not use KP settings, I gave up on it a long time ago. There is some kinky bug that appears some times that makes the whole thing spazz out leading to massive battery drain leaving you no option but to power off and pull the battery.
I use 2 scripts:
/etc/X11/Xsession.post/80avoidfreqs:
Code:
#!/bin/sh
sudo /opt/scripts/avoid_freqs.sh
/opt/scripts/avoid_freqs.sh:
Code:
#!/bin/sh
##set some frequencies
#avoid frequencies
echo "125000 550000 600000 805000 950000 1000000 1100000 1150000" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
#up threshold
echo 75 > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/up_threshold
#nice load
echo "0" > /sys/devices/system/cpu/cpu0/cpufreq/ondemand/ignore_nice_load
##Set DSP freqs
echo "90 90 180 360 400 430 520 600 600 600 600 600 600" > /sys/power/dsp_opps_rate
##FS mods
#enable camera button
#echo "cam"
chmod 666 /sys/devices/platform/gpio-switch/cam_focus/disable
echo 0 > /sys/devices/platform/gpio-switch/cam_focus/disable
chmod 444 /sys/devices/platform/gpio-switch/cam_focus/disable
#FM boost/region
#echo "fmtx"
chmod 666 /sys/class/i2c-adapter/i2c-2/2-0063/region
echo 4 > /sys/class/i2c-adapter/i2c-2/2-0063/region
chmod 644 /sys/class/i2c-adapter/i2c-2/2-0063/region
#load injection drivers
/opt/wifi/load.sh
#setup wifi for all channels
iw reg set JP
exit
One day I will get around to bodging this into pmconfig, however it seems to run fine right now so uh f**kit.
__________________
N900: One of God's own prototypes. A high-powered mutant of some kind never even considered for mass production. Too weird to live, and too rare to die.
 |
|
2012-02-05
, 19:49
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#2755
|
It's quite funny, as I've never ever encountered any problem with kp settings, not to mention battery drain.
/Estel
/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
|
|
2012-02-05
, 20:28
|
|
Posts: 915 |
Thanked: 3,209 times |
Joined on Jan 2011
@ Germany
|
#2756
|
KPv49 works fine for me circa one week now and v42 has been working fine since I bought my N900. I never encountered any battery drain.
It seems like there are spare values for what might have been a 125MHz setting (the 2nd value in $vsel andf $rate doesn't belong there). I tried fixing it by adding a 125MHz setting to the FREQS line in my profile but the error didn't change.
My evil hack for now is to add these two lines to kernel-config just before $vsel and $rate are written to the files to delete the 2nd value of each line:
It works for me but it's really just an ugly evil hack, so it doesn't qualify as a patch at all.
Edit:
Can somebody who runs v49 and uses a profile file please post his file so that I can try to find any critical differences?
Last edited by sulu; 2012-02-05 at 20:36.
It seems like there are spare values for what might have been a 125MHz setting (the 2nd value in $vsel andf $rate doesn't belong there). I tried fixing it by adding a 125MHz setting to the FREQS line in my profile but the error didn't change.
My evil hack for now is to add these two lines to kernel-config just before $vsel and $rate are written to the files to delete the 2nd value of each line:
Code:
vsel=`echo $vsel | sed s/\ [0-9]\\\+//` rate=`echo $rate | sed s/\ [0-9]\\\+//`
Edit:
Can somebody who runs v49 and uses a profile file please post his file so that I can try to find any critical differences?
Last edited by sulu; 2012-02-05 at 20:36.
| The Following User Says Thank You to sulu For This Useful Post: | ||
|
|
2012-02-05
, 22:41
|
|
Posts: 638 |
Thanked: 1,692 times |
Joined on Aug 2009
|
#2757
|
@freemangordon
do you have any news about the voltage boost and regulation at 805/850 Mhz?
do you have any news about the voltage boost and regulation at 805/850 Mhz?
|
|
2012-02-06
, 07:03
|
|
Posts: 3,074 |
Thanked: 12,964 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#2758
|
Originally Posted by xes
What news do you expect? Something like that? Or I am missing something.
@freemangordon
do you have any news about the voltage boost and regulation at 805/850 Mhz?
| The Following User Says Thank You to freemangordon For This Useful Post: | ||
 |
|
2012-02-06
, 07:35
|
|
Posts: 1,583 |
Thanked: 1,203 times |
Joined on Dec 2011
@ Everywhere
|
#2759
|
Originally Posted by woody14619
Uh? What's that got to do with any of this?
The default N900 is like an oven without a dial, just a big "auto-cook" button. The K## packages provide lots of thin metal cylinders you can turn to change the settings, but most can't grip them well enough to use them directly. The settings package is "the big plastic knob" on the front that makes it easier to use. But if you turn the oven up to twice it's rated value and it catches on fire, it's not the plastic knobs fault.
Some devices simply can't operate at faster speeds. It has nothing to do with the tools that configure the system. It's a hardware limitation. Nokia/TI tested these to work up to 600Mhz. Some reboot at 605Mhz, some reboot at 1200Mhz. If your device explodes randomly going over 850Mhz, then don't set it above that. Done.
when use kp48 i never had trouble like THIS!!! done? what ur mean then?
__________________
~$
~#
~$
~#
 |
|
2012-02-06
, 07:41
|
|
Posts: 584 |
Thanked: 700 times |
Joined on Jan 2010
|
#2760
|
I did some testing. Made a clean reflash and can confirm what was said. If someone wants a fast, and saving battery N900 just launch DSP profile and that is it. Few months ago I've tested battery patch and comparing it with DPS from Freemangordon it just doesn't work.Batterygraph shows that at night the phone nearly doesn't use cpu. With BP it used a lot more. One other important thing. It is good to have a clean install with just the stuff you use. Unused crap made my phone act strange. Further more all the apps for battery stats showing, cpu saving, overclocking etc. didn't help. I can not explain it. Without them and just with DSP loaded the usage at night is close to zero.
__________________
per ardua ad astra
per ardua ad astra
 |
| Tags |
| battery-status, bq27x00_battery, kernel, kernel-power, misiak4king, noobs-cant-read, pali4president, patches, readdirections, revolverspinyou |
«
Previous Thread
|
Next Thread
»
| Thread Tools | |
|
All times are GMT. The time now is 21:08.
I recently upgraded from v42 to v49. My profile, looks like this (which is basically the old "ideal" profile and worked fine under v42) :
The problem is that when I load this profile I get the following error messages:
echo $vsel > $pwr/vdd1_opps_vsel echo $rate > $pwr/dsp_opps_rateLast edited by sulu; 2012-02-05 at 17:42.