|
2010-01-28
, 06:21
|
Posts: 1,427 |
Thanked: 2,077 times |
Joined on Aug 2009
@ Sydney
|
#92
|
|
2010-01-28
, 07:14
|
Posts: 112 |
Thanked: 122 times |
Joined on Dec 2009
@ London, United Kingdom
|
#93
|
Tried this out yesterday, just used one of the preconfigured battery level scripts.
It seems to work nice but later that night when I went to go charge my phone it would not charge. I noticed the widget meter did not match the phones icon in the status bar for battery level.
I started to worry my usb port was broken. Turning off the widget and rebooting the phone fixed it and it charged. I never had this problem before and this was my only new application so atleast a decent chance that the widget/script somehow lead to the phone not going into charge mode.
lshal | grep bat
|
2010-01-28
, 07:26
|
Posts: 112 |
Thanked: 122 times |
Joined on Dec 2009
@ London, United Kingdom
|
#94
|
With 0.7, I can no longer see the X button to close when I resize the widget. To reproduce the issue, add a new widget and resize the width to something like 0.25. The X is visible when width is increased to 1.0
|
2010-01-28
, 09:20
|
Posts: 61 |
Thanked: 13 times |
Joined on Jan 2010
|
#95
|
Ok.. I see that this bug seems really annoying =/
Some things I would try to checkif the problem really is my widget:
a) install desktop-cmd-exec, triggering the prob and then just reboot (without uninstalling).. is the prob still there?
b)Uninstall desktop-cmd-exec and try cycles of installing-uninstalling widgets like personal-ip-address or countdown-widget
Other thing that come to mind: try removing (by hand) ".desktop_cmd_exec" on your home folder which may got corrupted in some weird way..
Now changing the subject, thanks to qwerty12 multiple instances are experimentally working here =]
just one little glitch that took me one hour to find out:
"X-Multiple=True" != "X-Multiple=true" =]
|
2010-01-28
, 12:04
|
Posts: 1,427 |
Thanked: 2,077 times |
Joined on Aug 2009
@ Sydney
|
#96
|
df -h | grep ubi0 | awk '{print $5,"used",",",$4"B","free"}'
The Following 7 Users Say Thank You to jakiman For This Useful Post: | ||
|
2010-01-28
, 13:52
|
Posts: 123 |
Thanked: 33 times |
Joined on Jan 2010
@ Stockholm
|
#97
|
if `hal-device | grep is.charging | awk '{print $3}'`; then echo Charging; else hal-device | grep charge_level.percentage | awk '{print $3 "%"}'; fi
The Following User Says Thank You to Palleman For This Useful Post: | ||
|
2010-01-28
, 15:05
|
Posts: 42 |
Thanked: 16 times |
Joined on Jan 2010
|
#98
|
Hi all,
I believe I found an uptime command that is a little less error-prone than the awk-version in the current desktop command execution widget.
Try this for uptime command:
uptime|cut -d" " -f3-|cut -d"," -f-1
If you don't like the word "up" in the response, try this:
uptime|cut -d" " -f4-|cut -d"," -f-1
Franky
|
2010-01-28
, 16:36
|
Posts: 123 |
Thanked: 33 times |
Joined on Jan 2010
@ Stockholm
|
#99
|
In fact the best method would be parsing /proc/uptime and getting a string from there, but that would require at least a shell script ...
cat /proc/uptime | awk '{printf "%d days, %.2d:%.2d\n",int($1/86400),int($1%86400/3600),int($1%3600/60)}'
cat /proc/uptime | awk '{if (int($1/86400)>0){printf "%d days, ",int($1/86400)};printf "%.2d:%.2d\n",int($1%86400/3600),int($1%3600/60)}'
The Following User Says Thank You to Palleman For This Useful Post: | ||
|
2010-01-28
, 16:43
|
Posts: 42 |
Thanked: 16 times |
Joined on Jan 2010
|
#100
|
Or some awk:
Or, if you don't want "0 days":Code:cat /proc/uptime | awk '{printf "%d days, ",int($1/86400);printf "%.2d:%.2d\n",int($1%86400/3600),int($1%3600/60)}'
/PCode:cat /proc/uptime | awk '{if (int($1/86400)>0){printf "%d days, ",int($1/86400)};printf "%.2d:%.2d\n",int($1%86400/3600),int($1%3600/60)}'
It seems to work nice but later that night when I went to go charge my phone it would not charge. I noticed the widget meter did not match the phones icon in the status bar for battery level.
I started to worry my usb port was broken. Turning off the widget and rebooting the phone fixed it and it charged. I never had this problem before and this was my only new application so atleast a decent chance that the widget/script somehow lead to the phone not going into charge mode.