Active Topics
-
Porting apps to Leste (29)
to Maemo 7 / Leste by Arno_11 - 2 days, 23 hrs ago -
Install Fonts in N900 (68)
to Maemo 5 / Fremantle by teroyk - 4 days, 2 hrs ago - more...
 |
|
2013-09-09
, 05:01
|
|
Posts: 1,552 |
Thanked: 3,108 times |
Joined on Jun 2012
@ Russia, 96
|
#1482
|
ajalkane,
there is very long string in the time interval condition, any way to fix it?
there is very long string in the time interval condition, any way to fix it?
| The Following User Says Thank You to Ancelad For This Useful Post: | ||
|
|
2013-09-09
, 06:39
|
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#1483
|
Originally Posted by Garp
I don't see anything wrong with the script. And from ProfileMatic's logs it seems like it's being run.
Now recovering from bed, here is the script!
How have you come to the conclusion it doesn't work? It's good to remember that restarting bme does not always fix the battery level when 4% bug occurs. So if it didn't work once, you should try to reproduce the problem again to make sure. And you can try manually running the action also to make sure.
__________________
My N9/N950 projects:
My N9/N950 projects:
|
|
2013-09-09
, 06:51
|
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#1484
|
Originally Posted by Ancelad
Try and modify this file:
ajalkane,
there is very long string in the time interval condition, any way to fix it?
/opt/profilematic/qml/TimeDialog.qml
Add properties wrapMode, width, and horizontalAlignmnet like this:
Code:
Text {
id: header
text: root.titleText + " " + root.formatTime(timePicker.hours, timeP
wrapMode: Text.Wrap
width: parent.width
horizontalAlignment: Text.AlignHCenter
...
Thanks!
__________________
My N9/N950 projects:
My N9/N950 projects:
|
|
2013-09-09
, 07:38
|
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#1485
|
Originally Posted by ajalkane
Thanks!
I don't see anything wrong with the script. And from ProfileMatic's logs it seems like it's being run.
How have you come to the conclusion it doesn't work? It's good to remember that restarting bme does not always fix the battery level when 4% bug occurs. So if it didn't work once, you should try to reproduce the problem again to make sure. And you can try manually running the action also to make sure.
How to test manually when on this rule the "Run rule's action" and "Test" button dont work? - as it does on other rules ex. the one with 'Custom action' reboot device.
Last time 4% bugs occur about a week ago Blue bar show up on rule when battery level suddenly fall to 8% but else nothing happens and the battery level fall to 7,6,5,4% then I set the charger on and THEN something happens and suddenly the battery level was 41% - is that a correct action
__________________
OK
OK
Last edited by Garp; 2013-09-09 at 08:03.
|
|
2013-09-09
, 07:51
|
|
Posts: 1,552 |
Thanked: 3,108 times |
Joined on Jun 2012
@ Russia, 96
|
#1486
|
Originally Posted by ajalkane
Yes, it works
Try and modify this file:
/opt/profilematic/qml/TimeDialog.qml
Add properties wrapMode, width, and horizontalAlignmnet like this...
Thanks!
|
|
2013-09-09
, 13:17
|
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#1487
|
Originally Posted by Garp
It should work. And I saw in the logs that it did run when you manually ran it (those lines starting with BMEVENT indicate it). That script just might not show any visible indication. And one more thing, you must remember that it takes 20 seconds before the battery level is corrected. It doesn't happen immediately.
Thanks!
How to test manually when on this rule the "Run rule's action" and "Test" button dont work? - as it does on other rules ex. the one with 'Custom action' reboot device.
__________________
My N9/N950 projects:
My N9/N950 projects:
| The Following User Says Thank You to ajalkane For This Useful Post: | ||
|
|
2013-09-09
, 16:11
|
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#1488
|
Originally Posted by ajalkane
OK and thanks again!
It should work. And I saw in the logs that it did run when you manually ran it (those lines starting with BMEVENT indicate it). That script just might not show any visible indication. And one more thing, you must remember that it takes 20 seconds before the battery level is corrected. It doesn't happen immediately.
One more question and then peace - for a while at least I hope
Rule Update Network
Conditions: 'No net connection'
Custom action: /sbin/initctl restart xsession/icd2
Don't seems to work: close internet connections (set to manual) again Blue bar shown nothing else.
attached log: execute command line= success 1
but then initctl: Name "com.ubuntu.Upstart" does not exist
__________________
OK
OK
|
|
2013-09-09
, 19:01
|
|
Posts: 1,313 |
Thanked: 2,977 times |
Joined on Jun 2011
@ Finland
|
#1489
|
Originally Posted by Garp
You'll need to run that as root also. So invoke that script using execroot as you did for restartbme.
OK and thanks again!
One more question and then peace - for a while at least I hope
Rule Update Network
Conditions: 'No net connection'
Custom action: /sbin/initctl restart xsession/icd2
Don't seems to work: close internet connections (set to manual) again Blue bar shown nothing else.
attached log: execute command line= success 1
but then initctl: Name "com.ubuntu.Upstart" does not exist
__________________
My N9/N950 projects:
My N9/N950 projects:
|
|
2013-09-09
, 21:34
|
|
Posts: 697 |
Thanked: 137 times |
Joined on Jul 2012
@ Hillerød, DK
|
#1490
|
Originally Posted by ajalkane
Ups! I have no script so now be aware in Suomi there will come a really stupid question:
You'll need to run that as root also. So invoke that script using execroot as you did for restartbme.
Which script in this case?
__________________
OK
OK
Last edited by Garp; 2013-09-09 at 21:36.
OK