The Following 7 Users Say Thank You to Gusse For This Useful Post: | ||
|
2011-09-01
, 04:54
|
Posts: 915 |
Thanked: 57 times |
Joined on Jun 2011
|
#1453
|
|
2011-09-01
, 07:49
|
|
Posts: 168 |
Thanked: 206 times |
Joined on Apr 2010
@ Finland
|
#1454
|
sudo gainroot dpkg -i kernel-power_2.6.28-10power47_armel.deb dpkg -i kernel-power-modules_2.6.28-10power47_armel.deb dpkg -i kernel-power-flasher_2.6.28-10power47_armel.deb
The Following 2 Users Say Thank You to Gusse For This Useful Post: | ||
|
2011-09-01
, 08:42
|
Posts: 915 |
Thanked: 57 times |
Joined on Jun 2011
|
#1455
|
|
2011-09-01
, 13:12
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#1456
|
Anyone else noticed that connecting to internet fails many times after kernel48, n900 connects like after 10 tries. i would like to revert back to 47 how can i do that ?
It will, the default value set on system startup should be 112(the same as stock). You should change that in event.d script to the value you want it to be. The default can be changed too (to max of 120), it was me who insist on using 112 as default during installation.
While I fully agree that overlapping features is silly what about us not using the above mentioned binary?
fmtx .ko module exposes ioctls to userland for reducing and increasing power. Stock fmtxd uses those ioctls to manage fmtx power every time a charger/usb cable is connected to the device. The previous patch (the one from KP46) simply disables locking of sys/.../power_level , but does not prevent fmtxd to set power_level via ioctl.
Just for clarity - fmtx patch makes all fmtx power applications unneeded - once set, fmtx power level remains constant until reboot.
TBH i was not sure that fmtx patch should be included, but future maintainer's words were "release early, release often"
|
2011-09-01
, 13:27
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#1457
|
I got no problems with connecting to any network with kp48.
Thanks for clarification. I see your reasons and agree, that it's much "wanted" approach Ho ever, jacekowski's binary also allow us to use full 76-107,9 mhz range. Is there a way You can implement it using Your method?
If not, can we use your method + event.d script to fix power to 120 + jacekowski.s binary to get exact same result as with jacekowski.s binary, but with additional benefit of ioctls exposed for userland applications (i.e. for program/widget to dynamically switch power alongside with frequency etc.)?
---
On the other hand, I'm bumbing problems with (segfault related?) crashes via leafpad (or, as one user reported, fmms) "save as". As it was - IMO correctly - said before, userland apps should not be able to so easily crash whole system. It definitely never happened with kp47. People less clueless ( ) than me, do you have any ideas?
|
2011-09-01
, 14:13
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#1458
|
|
2011-09-01
, 14:23
|
Posts: 3,074 |
Thanked: 12,960 times |
Joined on Mar 2010
@ Sofia,Bulgaria
|
#1459
|
The Following User Says Thank You to freemangordon For This Useful Post: | ||
|
2011-09-01
, 14:48
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#1460
|
Tags |
battery-status, bq27x00_battery, kernel, kernel-power, misiak4king, noobs-cant-read, pali4president, patches, readdirections, revolverspinyou |
|
Last edited by Gusse; 2011-08-31 at 18:20.