Active Topics

 



Notices


Reply
Thread Tools
Posts: 195 | Thanked: 16 times | Joined on Feb 2010 @ Switzerland
#41
Originally Posted by techie View Post
Update to 1.0.2 from devel that should fix it now
Which update ?!
__________________
(n900 _Switzerland)
 
Posts: 101 | Thanked: 30 times | Joined on Jul 2010
#42
Originally Posted by sacal View Post
Multiboot 0.2.5 and autoloading bq27x00_battery.

For those like me that are running OCCP widget and titan's power37 or 39 with multiboot 0.2.5, there is the need of loading bq27x00_battery module after every reboot.

As Jay-C, the author of multiboot stated here there are problems autoloading that module.

So for those interested i have added some lines of code to the /home/user/.OCCP file to autoload the bq2700_battery module so that the temperature is displayed in the OCCP widget:

Code:
QBW_REMEMBER_ME=${7}
if [ "$(cat /sys/class/power_supply/bq27200-0/temp)" == "" ] ; then
  sudo modprobe bq27x00_battery > /dev/null ;
fi
if [ "$QBW_REMEMBER_ME" -eq 3 ] ; then
Strange, i running OCCP widget and titan's power37 with multiboot 0.2.5 but i don't need to load bq27x00_battery module after every reboot.......
 

The Following User Says Thank You to gft2k1 For This Useful Post:
Posts: 101 | Thanked: 30 times | Joined on Jul 2010
#43
Originally Posted by PipoXtreme View Post
Which update ?!
Install Queen Beecon Widget 1.0.2 from Maemo Extras Devel and this should resolve your problem...........
 
Posts: 165 | Thanked: 78 times | Joined on Jun 2010
#44
Originally Posted by gft2k1 View Post
Strange, i running OCCP widget and titan's power37 with multiboot 0.2.5 but i don't need to load bq27x00_battery module after every reboot.......
Glad to know it is working with you. I really would like to know why.
I have tried everything i could and i also asked for help to the multiboot's author.
Adding those lines of code to the OCCP widget is a workaround so that i don't have to manually load the module every time the system boots.
 
Erazor's Avatar
Posts: 160 | Thanked: 33 times | Joined on May 2010
#45
hi its me again

i have the same issue like last night.
The CPU only goes down to 500MHz.
Now i edit the avoid frequencies in
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
and only write 125000 in there.
When this is done, all works fine.

BUT after a reboot the 250000 is in the file again......

Does anybody know this issue?
 
Posts: 101 | Thanked: 30 times | Joined on Jul 2010
#46
Originally Posted by Erazor View Post
hi its me again

i have the same issue like last night.
The CPU only goes down to 500MHz.
Now i edit the avoid frequencies in
/sys/devices/system/cpu/cpu0/cpufreq/ondemand/avoid_frequencies
and only write 125000 in there.
When this is done, all works fine.

BUT after a reboot the 250000 is in the file again......

Does anybody know this issue?
Do you use the "ideal" setting ?

Because the minimum frequency of ideal is 500 MHz.
If you edit the avoid frequencies the cpu goes down to 250 Mhz but after a reboot the system return to ideal default (500-850 MHz).

Try another setting ("lv", "ulv", "xlv" or "starving") who have the minimum frequency at 250 MHz(default).
 
Posts: 101 | Thanked: 30 times | Joined on Jul 2010
#47
Originally Posted by sacal View Post
Glad to know it is working with you. I really would like to know why.
I have tried everything i could and i also asked for help to the multiboot's author.
Adding those lines of code to the OCCP widget is a workaround so that i don't have to manually load the module every time the system boots.
If this can help you my multiboot menu is the follow:

1 - Maemo 2.6.28-omap1

2 - Maemo 2.6.28.10power37

3 - NITdroid on MMCp2 - 2.6.28.NIT.05
 

The Following User Says Thank You to gft2k1 For This Useful Post:
Erazor's Avatar
Posts: 160 | Thanked: 33 times | Joined on May 2010
#48
Originally Posted by gft2k1 View Post
Do you use the "ideal" setting ?

Because the minimum frequency of ideal is 500 MHz.
If you edit the avoid frequencies the cpu goes down to 250 Mhz but after a reboot the system return to ideal default (500-850 MHz).

Try another setting ("lv", "ulv", "xlv" or "starving") who have the minimum frequency at 250 MHz(default).
yes its the ideal setting

but now the strange thing
over the night it goes down to 250MHz
over the day it goes down to 500MHz

its very very strange

btw i use the power-kernel 40 from extra-devels

and

lv=low voltage
ulv=ultra low voltage
xlv= xtreme low voltage
starving=please give me MORE power

correct?
 
Posts: 165 | Thanked: 78 times | Joined on Jun 2010
#49
Originally Posted by gft2k1 View Post
If this can help you my multiboot menu is the follow:

1 - Maemo 2.6.28-omap1

2 - Maemo 2.6.28.10power37

3 - NITdroid on MMCp2 - 2.6.28.NIT.05
Thanks gft2k1

The issue isn't in multiboot menu. Mine is almost the same except that i now use power39. Anyway with power37 the problem was the same.
I am now waiting for a stable multiboot 0.2.9 to try it and see if the problem still remains.
 
Posts: 179 | Thanked: 49 times | Joined on Nov 2008
#50
Originally Posted by techie View Post
The edited image is better, I couldn't make sense of the original one.Also I think you should ideally be getting only the right half of ideal button responsive.
You cannot edit the area for button press.QBW divides it into an equal grid of 3x3, maybe in a future version it could be possible to define custom areas (send a request to QBW author).For now thats how it will work or you can reduce the width.
Why 3x3 when there is only 2 buttons on the bottom row?

Strangely, the left 3rd worked for STOCK, but the right 2/3rds worked for IDEAL.

P.S. Seeing as my attempts are failing, is there any chance you could edit this to be 400x110 and try to make it work as the original does?
 
Reply


 
Forum Jump


All times are GMT. The time now is 15:19.