Odds and ends - Page 26 - maemo.org

auouymous | # 251 | 2011-12-12, 22:11 | Report

Originally Posted by Addison View Post

Afterwards, Power Button, then I pressed the Full Screen button by accident.
I got nothing but a white screen.

Does power button open ASUI? If you press fullscreen key in ASUI it enters flashlight mode (white screen, full brightness). You just press needed to press fullscreen again or escape or power button if it unmaps ASUI.

If ASUI wasn't mapped then a white screen means hildon-desktop crashed. All of your apps would have also terminated, except for ASUI which you may have used to reboot.

Originally Posted by Addison View Post

I have two Desktops now.
Trying to kill the Desktop (40.3 MB) in ASUI only gives like one or two little blue pegs, like it's running your script, but then it suddenly stops doing this.

That is a really bad picture so I can't tell what your desktop looks like. Did you try stopping and then restarting the desktop service in ASUI? Did you try disabling all desktop and statusbar applets and then restarting the desktop?

Do you know how to SSH into your n800? If so try stopping the desktop service and then run the following via SSH.

Code:

AS ROOT:
su - user -c "maemo-summoner /usr/bin/hildon-desktop.launch"

OR AS USER:
maemo-summoner /usr/bin/hildon-desktop.launch

It should start the desktop and spew a lot of stuff to the console. The messages may contain the reason for it being broken.

The Following User Says Thank You to auouymous For This Useful Post:
Addison

Addison | # 252 | 2011-12-12, 22:20 | Report

Here is a pic of me running Xterm now.

Any chance you could meet me online somewhere auouymous?

Addison | # 253 | 2011-12-12, 22:26 | Report

I can't edit any of my desktop applets because I don't have a "Home" spot to bring this up.

Yeah, in my previous post, I tried restarting the desktop service in ASUI but it stops short and doesn't do anything.

The power button does open ASUI.

Sorry about not knowing that the Full Screen key does your flashlight feature.

I just tried that again and it works just fine. I'm even able to turn the flashlight off as well.

When I hit that button before, I thought I somehow crashed the tablet.

Anyway, I do have Open SSH installed on this little bugger but I don't know how to use it.

Sorry.

Addison | # 254 | 2011-12-12, 22:39 | Report

Never mind.

I killed hildon-desktop in your Task Manager thingy.

I then loaded it back up with your Desktop script.

I couldn't connect online so I did
root
reboot -n

It's all back to being good.

Lesson learned.

Addison | # 255 | 2011-12-12, 22:41 | Report

So........

Any other ideas on how to completely kill Modest?

Addison | # 256 | 2011-12-14, 22:19 | Report

I really would love for any suggestions on how to kill Modest completely.

Even when I'm not running the one minute notification script, it keeps popping up and pegging the CPU.

I've tried changing the notification interval to 500 minutes, sudo killall modest, etc.

Nothing that I do will stop it.

I'm fresh out of ideas.

Any help on this?

My videos are very intensive so I need every bit of CPU power to run them.

Addison | # 257 | 2011-12-14, 23:34 | Report

Right now, this is everything that I've been throwing at Modest.

gconftool-2 --type int --set /apps/modest/update_interval 5
gconftool-2 --type boolean --set /apps/modest/auto_update False
sudo /etc/init.d/mce restart
sudo start-stop-daemon --stop --name modest
sudo dsmetool -k /usr/bin/modest

The little bugger always rears back up after one minute.

I don't get it.

auouymous | # 258 | 2011-12-15, 00:09 | Report

Originally Posted by Addison View Post

gconftool-2 --type int --set /apps/modest/update_interval 5
gconftool-2 --type boolean --set /apps/modest/auto_update False
sudo /etc/init.d/mce restart
sudo start-stop-daemon --stop --name modest
sudo dsmetool -k /usr/bin/modest

I don't have modest so can't really help you out but have you tried setting interval to 0? You should also sleep before restarting mce and stopping modest. WIthout the sleep it might not work at all or only work sometimes.

You should also dig through gconf-editor and find other keys that might be related to the auto-update or interval. There are some keys that ASUI must set both instances for them to work.

Code:

const char *conf_screen_autolock1 = "/apps/osso/applet/osso-applet-display/lock_screen";
const char *conf_screen_autolock2 = "/system/osso/dsm/locks/touchscreen_keypad_autolock_enabled";
const char *conf_screen_stayslit1 = "/apps/osso/applet/osso-applet-display/display_charger";
const char *conf_screen_stayslit2 = "/system/osso/dsm/display/display_on_with_charger";

Does modest provide a UI to change the interval? If so, you could monitor dbus activity to see if it sends out anything that you could use.

The Following User Says Thank You to auouymous For This Useful Post:
Addison

Addison | # 259 | 2011-12-15, 02:41 | Report

Modest comes stock with Diablo. It's the default email app.

Yeah, there is a User Interface with Modest.

How can I monitor the dbus activity when using this?

Well, I'm back to square one because I no longer think that restarting MCE is necessary to update any changes made with the notifications.

How can I term this argument correctly?

sudo start-stop-daemon --start --name modest

sudo start-stop-daemon --stop --name modest
works correctly. But to start it though, I need to add some kind of an additional argument that I don't understand.

-S|--start -- <argument> ... start a program and pass <arguments> to it

Addison | # 260 | 2011-12-15, 02:46 | Report

I did find this in gconf

gconftool-2 --type bool --set /apps/modest/accounts/AccountID/enabled

and

#gconftool-2 --type int --set /apps/modest/update_when_connected_by

I'm getting closer to finally stopping this.

Modest will pop in just for a second now, once a minute, then disappear. So it's gotten much better.

Setting the interval to 0 didn't work but that was a nice idea though.