maemo.org - Talk
Page 3 of 9 12 3 45 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing! (https://talk.maemo.org/showthread.php?t=64170)

Mentalist Traceur 2010-10-24 19:32
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Actually it looks pretty simple to me personally. If you want to make it truly newb friendly, hide all the code and package it into a .deb. That way the truly-newb people won't have to think about how it works, and it' won't scare them at all.

Just like swappolube vs manually making a script yourself.

Anyway, I wouldn't make it "simpler", unless there's something in the code that could truly use simplifying. It looks pretty simple enough. I just don't have the knowledge to figure out if the simple looking stuff is actually good.

One thing I HAVE figured out from looking at the script, is you understand DBus. And I just so happen to have a particular shell command that I would like to know, that I know uses DBus.

So, if you don't mind telling me: How do I fetch device orientation (portrait vs landscape) using dbus? Not with python/C/C++/Qt - just from the command-like (so I can stick it into my Conky.conf file for something I've been trying to do). I have this tidbit of python code from the wiki:

Code:
$import dbus
bus = dbus.SystemBus()           
accel = bus.get_object('com.nokia.mce',
        '/com/nokia/mce/request',
        'com.nokia.mce.request')
orientation , stand , face , x , y , z = accel.get_device_orientation()
This is where I hit a wall, because I know nothing of what to put into the command line (or even if I need to use dbus-send, or dbus-monitor, or some other command), or what options to use, etc. So, while this is off topic, any chance you could help out?

retsaw 2010-10-24 19:58
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
What is the benefit to dynamically changing the OC profile?

Surely if one profile gives improved battery life over another why not just keep it on that one. I do see what you are doing with the switching to the starving profile when the battery gets low, but that won't work for me since my n900 reboots after about a minute on the starving profile. I normally run the ideal profile with limits 500 and 850, I don't really see where your script would save my battery since I can't safely switch to the starving profile. Since this script certainly won't provide stable operation on all phones (there is a reason the default profile is what it is), I wouldn't go recommending this to those who would normally be afraid to OC their n900.

Mentalist Traceur 2010-10-24 20:19
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Note that me thanking retsaw (or anyone else) doesn't necessarily mean that I agree with them - just that I find the post informative or think it brings up a good question/point.

On another note, isn't there an application in the repos that basically works like cron-jobs? Allowing you to make this script run occasionally without the need for a QBW?

Couldn't we somehow adapt this to work with not just battery level but also with current being drawn and processor demand? Or would that require the script to run too often?

Also, one thing I wanted to say, for public notice: Advanced Power, BME, and the bq27x00_battery module do not play well together (It's something about that combination as a whole, since I haven't seen anyone report it when just using BME and bq27x00, though it's possible everyone just doesn't notice). So when you have bq27x00 enabled to fetch temperature, it will make the values BME reports for battery be lower than they actually are.

Best way to test this is install conky, and in the conky.conf file, stick in one line to fetch the BME reported battery left percentage, and one to fetch the bq27x00 reported battery left percentage. Save the conf file, launch conky, and compare. If they don't report the same thing, problem.

- Edit -

I'm stupid - best way to test the above is to just run the two queries in command-line - less effort is needed. The two I use are:

hal-device bme |grep "percentage" |awk '{print $3}' <-- to get BME's battery percentage, and:
cat /sys/class/power_supply/bq27200-0/capacity <-- to get the bq27x00_battery's battery percentage.

RenaldoTT 2010-10-25 00:36
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Yea, I noticed bakuurs plan from day one, if people don't actively show an interest that's them, let them do things the hard way, I read the hard way, I understand it but in life if you get an easier way to achieve the same task take it. So I'm going to test this now... creating QueenBeeCon Widget as we speak

K I made the widget, clicked it, limits are now set to 125 600, interval to run script
every 1hr.

is the limit at 8bars supposed to be 125 600 because this is what I'm getting here when I run oc-script and view my current freq settings
Lets see what happens now

Mentalist Traceur 2010-10-25 01:46
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
I'd still like people to report the differences, if any, that you notice between

hal-device bme | grep "percentage" | awk '{print $3}'
and
cat /sys/class/power_supply/bq27200-0/capacity

Meanwhile [sarcasm]thanks so much to everyone who read my request for dbus help and actually knew dbus enough to knows how to do what I asked.[/sarcasm]. I get that most people don't know dbus that well, and some might not have had time or had something impostant to do instead - but if you knew how to help and didn't bother, middle finger to you.

For anyone who cares, I figured it out, I would like to say that the script on the first page actually helped, so an indirect sincere thanks for that. So to all those who'd like to know how to use the command line to get accelerometer values and device orientation (as well as two other things) through DBus (which as far as I know is the only way to get device orientation directly):

dbus-send --system --print-reply --dest=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.get_device_orientation

From there, I've figured out how to combine grep and awk to get just the device orientation returned (though it's not exactly right for what I want, but I can figure that out a lot easier).

- Edit -

To the OP (who's name eludes me and I can't see because the edit mode doesn't show you previous posts), I'll try this script, or some tweek of it, in the near future. I will definitely be implementing the "lower-clock if temperature is critical" thing eventually - at least if I have what appears to be overheating problems.

RenaldoTT 2010-10-25 03:38
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Well right now I'm not sure if the script is working. First time I made the widget and checked my freq it was set to 125 600 I removed the widget and set my freq back to normal using the "easy overclock" script and replaced the SmartClocker Widget and now my freq is set at 250 600. It's running now and updating every hour so lets see what happens, battery doesn't seem to have improved for me though.

Ok I went into "Advanced" and paste the script, saved and ran it, limits now set to 500 900 ideal profile

bakuur 2010-10-25 04:09
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Quote:
Originally Posted by retsaw (Post 849806)
What is the benefit to dynamically changing the OC profile?

Surely if one profile gives improved battery life over another why not just keep it on that one. I do see what you are doing with the switching to the starving profile when the battery gets low, but that won't work for me since my n900 reboots after about a minute on the starving profile. I normally run the ideal profile with limits 500 and 850, I don't really see where your script would save my battery since I can't safely switch to the starving profile. Since this script certainly won't provide stable operation on all phones (there is a reason the default profile is what it is), I wouldn't go recommending this to those who would normally be afraid to OC their n900.
Yes since Your phone can't handle low voltages then isuggest laying off the script as why is it useful? Well friend the titLe says it all

bakuur 2010-10-25 04:12
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Quote:
Originally Posted by RenaldoTT (Post 850026)
Well right now I'm not sure if the script is working. First time I made the widget and checked my freq it was set to 125 600 I removed the widget and set my freq back to normal using the "easy overclock" script and replaced the SmartClocker Widget and now my freq is set at 250 600. It's running now and updating every hour so lets see what happens, battery doesn't seem to have improved for me though.

Ok I went into "Advanced" and paste the script, saved and ran it, limits now set to 500 900 ideal profile
Ahh dear friend am currently outside my house as soon am home ill show you how to create the widget

THanks a lot for your support

bakuur 2010-10-25 04:15
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
Quote:
Originally Posted by Mentalist Traceur (Post 849972)
I'd still like people to report the differences, if any, that you notice between

hal-device bme | grep "percentage" | awk '{print $3}'
and
cat /sys/class/power_supply/bq27200-0/capacity

Meanwhile [sarcasm]thanks so much to everyone who read my request for dbus help and actually knew dbus enough to knows how to do what I asked.[/sarcasm]. I get that most people don't know dbus that well, and some might not have had time or had something impostant to do instead - but if you knew how to help and didn't bother, middle finger to you.

For anyone who cares, I figured it out, I would like to say that the script on the first page actually helped, so an indirect sincere thanks for that. So to all those who'd like to know how to use the command line to get accelerometer values and device orientation (as well as two other things) through DBus (which as far as I know is the only way to get device orientation directly):

dbus-send --system --print-reply --desk=com.nokia.mce /com/nokia/mce/request com.nokia.mce.request.get_device_orientation

From there, I've figured out how to combine grep and awk to get just the device orientation returned (though it's not exactly right for what I want, but I can figure that out a lot easier).

- Edit -

To the OP (who's name eludes me and I can't see because the edit mode doesn't show you previous posts), I'll try this script, or some tweek of it, in the near future. I will definitely be implementing the "lower-clock if temperature is critical" thing eventually - at least if I have what appears to be overheating problems.
yes my friend i found a diffrence between the two battery levels
can you futher explain why is that?
And I'm glad you found the dbus commaNd you were looking fOr

EDIT:sorry for the miss types in the post i was using a black berry and god it!!! :@

smartypants 2010-10-25 05:22
Re: [ANNOUNCED] SmartClocker - save up battery and stop worrying about OCing!
 
i can haz userfriendly?


All times are GMT. The time now is 07:44.
Page 3 of 9 12 3 45 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8