Active Topics
| The Following User Says Thank You to auouymous For This Useful Post: | ||
 |
|
2011-09-21
, 09:40
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#822
|
Yeah, I have DT now.
I'll be your biggest tester on whatever new features you attempt with ASUI...
Just not at this moment.
I've been drinking.
I'll be your biggest tester on whatever new features you attempt with ASUI...
Just not at this moment.
I've been drinking.
|
|
2011-09-21
, 16:44
|
|
Posts: 1,101 |
Thanked: 1,184 times |
Joined on Aug 2008
@ Spain
|
#823
|
Originally Posted by auouymous
Moving the ASUI window doesn't generate enough load to make the governor jump when in ondemand mode.
Yes, it will launch xmms if it not running, starts playing and opens playlist. You can remove the "play_list 1" if you don't want playlist to open. You could also add "main 0" if you want to minimize the main xmms window.
That is a good use for the first value. It could be used to set the governor to powersave and restore it upon exiting audio lock. Only problem is that powersave no longer seems to work on my device. Try setting powersave, then drag the ASUI window up and down and tell me if it stays at 165. Not sure if this is a DT kernel problem because it worked in the pre-DT days.
A better method to test is to open a xterm and run a loop "while :; do :; done"
When I do this in powersave mode the device stays at 165 MHz, while in ondemand mode it jumps to 400 MHz. But, if I play a mp3 with mplayer, it jumps to 400 MHz if the governor is in ondemand, powersave or conservative mode, but it doesn't change frequency with the null governor, staying at whatever frequency it was when I changed the governor.
I haven't touched the governor code at all, so this behavior should happen in the old kernels too.
| The Following User Says Thank You to maacruz For This Useful Post: | ||
|
|
2011-09-22
, 09:05
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#824
|
Heya auouymous!
Okay, I think I'm getting weirdness on my end with ASUI.
Nothing serious, but still, I'm not seeing any pattern to it's behavior.
When unlocking the screen, many times, my touch screen no longer works.
With your new audio feature, it usually works, it's awesome by the way, but for some reason, the hardware keys stop being responsive as well.
I seem to constantly be locking and unlocking my tablet to get it all back again.
Not sure what's going on with this.
Maybe after the 2 minute lock that I have in my Application Manager-->Settings-->Control Panel-->Display is messing something up.
I don't have the "Lock screen and keys" checked so I have no idea what might be happening here.
Is there any kind of test you would like me to try in narrowing this issue down?
Thanks!
Okay, I think I'm getting weirdness on my end with ASUI.
Nothing serious, but still, I'm not seeing any pattern to it's behavior.
When unlocking the screen, many times, my touch screen no longer works.
With your new audio feature, it usually works, it's awesome by the way, but for some reason, the hardware keys stop being responsive as well.
I seem to constantly be locking and unlocking my tablet to get it all back again.
Not sure what's going on with this.
Maybe after the 2 minute lock that I have in my Application Manager-->Settings-->Control Panel-->Display is messing something up.
I don't have the "Lock screen and keys" checked so I have no idea what might be happening here.
Is there any kind of test you would like me to try in narrowing this issue down?
Thanks!
|
|
2011-09-22
, 09:38
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#825
|
Originally Posted by Addison
What do you mean by "unlocking your screen many times"?
When unlocking the screen, many times, my touch screen no longer works.
With your new audio feature, it usually works, it's awesome by the way, but for some reason, the hardware keys stop being responsive as well.
I seem to constantly be locking and unlocking my tablet to get it all back again.
The unresponsive audio lock keys might be related to the hack I use to turn off the screen. When DSME detects a screen off event while in audio lock mode it sleeps for 500ms and then unlocks the keys. This is because MCE relocks the keys when ASUI tells it to blank the display. If MCE takes longer than 500ms then the unlock happens before MCE relocks them. I need to poll until MCE locks the keys and then unlock them.
Whenever you have a problem just install the debug binary with "asui dd;asui id". Reproduce the problem and then run "asui it" to restore the test binary. Then send me the newest /root/asui-debug-* file and delete it.
| The Following User Says Thank You to auouymous For This Useful Post: | ||
|
|
2011-09-22
, 09:47
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#826
|
What do you mean by "unlocking your screen many times"?
I usually have to hit the Power Button (this brings up ASUI), Center D-Pad (tablet is then locked), Power Button again, then Center D-Pad to unlock the tablet, many times I have to do this more than once, actually, several times until the touch screen and hardware keys finally all work again.
Oh, and I don't think this has anything to do with the whole two minute setting in the Display Control Panel thingy.
The new audio feature sometimes stops working after only a few seconds.
All I can say is that I haven't found a pattern to this yet.
|
|
2011-09-24
, 08:30
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#827
|
Whenever you have a problem just install the debug binary with "asui dd;asui id". Reproduce the problem and then run "asui it" to restore the test binary. Then send me the newest /root/asui-debug-* file and delete it.
Give me a day or two and I'll give you the test binary restore newest deleted file debug reproduced problem thingy upload whatever bobber for you to enjoy.
I honestly don't get it.
Sometimes it will work for an hour straight.
Tonight and even a few days back, it will only work for a few seconds.
It's so weird that I haven't caught on to the behavior on this.
I'm just not seeing a pattern to it all.
Anyway, many cheers auouymous. I still love what you've done with this and there is not enough thank you buttons to show my gratitude on your work.
|
|
2011-09-24
, 18:57
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#828
|
I haven't been able to lock the screen now for 12+ hours. 
I keep getting these messages.
"An application may have paused screen blanking"
"Screen is unlocked and should dim in a minute..."
I'll pick up your debugging floober bobby later and post whatever is on this.
It's so weird since I'm not even running anything as far as I know.
I keep getting these messages.
"An application may have paused screen blanking"
"Screen is unlocked and should dim in a minute..."
I'll pick up your debugging floober bobby later and post whatever is on this.
It's so weird since I'm not even running anything as far as I know.
Code:
PID USER STATUS VSZ PPID %CPU %MEM COMMAND 801 root SW< 12488 343 10.5 9.8 Xomap 20811 user SW 36276 1003 6.6 28.5 maemo-launcher 1038 user SW< 33452 1003 5.6 26.3 maemo-launcher 845 user SW< 9044 343 3.3 7.1 matchbox-window 1086 user SW< 61348 1003 2.5 48.3 maemo-launcher 20815 user RW 4028 20812 2.1 3.1 top 79 root SW 0 6 0.9 0.0 OMAP McSPI/0 878 root SW 4836 343 0.3 3.8 multimediad 20791 user SW 69840 1003 0.0 54.9 maemo-launcher 14145 user SW 67348 1387 0.0 53.0 browserd 1414 user SW 60888 1 0.0 47.9 gnome-vfs-daemo 1387 user SW 40568 1 0.0 31.9 browserd 1212 user SW< 33188 1003 0.0 26.1 maemo-launcher 1003 user SW< 21292 1 0.0 16.7 maemo-launcher
|
|
2011-09-24
, 19:28
|
|
Posts: 875 |
Thanked: 918 times |
Joined on Sep 2010
|
#829
|
Originally Posted by Addison
Go into asui-settings : services, is "alarm dispather" running? There is a known problem with ASUI and alarmd keeping the screen on. If you don't use alarms then you should uncheck and stop it, then restart MCE. If you use alarms then try restarting alarmd and then mce. If that doesn't work try stopping alarmd, restart MCE and then start alarmd. One day I will find a fix for this.
I keep getting these messages.
"An application may have paused screen blanking"
"Screen is unlocked and should dim in a minute..."
|
|
2011-09-24
, 19:34
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#830
|
Yeup. Alarm dispather is running, stopping it now.
Does this include the built in alarm feature or just something with ASUI?
Because yeah, I'm a fat lazy mammal who requires an alarm to wake myself up.
Does this include the built in alarm feature or just something with ASUI?
Because yeah, I'm a fat lazy mammal who requires an alarm to wake myself up.
 |
| Tags |
| bada blows, bada rox |
«
Previous Thread
|
Next Thread
»
|
All times are GMT. The time now is 04:41.
That is a good use for the first value. It could be used to set the governor to powersave and restore it upon exiting audio lock. Only problem is that powersave no longer seems to work on my device. Try setting powersave, then drag the ASUI window up and down and tell me if it stays at 165. Not sure if this is a DT kernel problem because it worked in the pre-DT days.