Odds and ends - Page 25 - maemo.org

Active Topics

Maemo repository (8)
to Community by Maemish - 1 day, 3 hrs ago
Porting apps to Leste (44)
to Maemo 7 / Leste by norayr - 1 day, 8 hrs ago
List of well performing apps on Leste (35)
to Maemo 7 / Leste by smatkovi - 4 days, 5 hrs ago
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (13)
to SailfishOS by edp17 - 5 days, 3 hrs ago
Sailfish OS for the Samsung Galaxy Note 4 (SM-N910C) - (treltexx) (79)
to SailfishOS by edp17 - 5 days, 3 hrs ago
U-Boot for Nokia RX-51 with BootMenu (updated version 2012.10-rc3-1) (843)
to Alternatives by Arno_11 - 5 days, 8 hrs ago
more...

Page 25 of 30

Thread Tools

auouymous	2011-12-08 , 22:20
Posts: 875 \| Thanked: 918 times \| Joined on Sep 2010	#241

Originally Posted by Addison

Real quick, is it possible to go a little beyond 100% of this master volume control setting?

I doubt it, try setting the gconf /apps/osso/sound/master_volume key above 100. Let me know if it works.

Quote & Reply |

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

	Addison	2011-12-08 , 22:29
	Posts: 3,811 \| Thanked: 1,151 times \| Joined on Oct 2007 @ East Lansing, MI	#242

So, like this?

gconftool-2 --type int --set /apps/osso/sound/master_volume key 6000000

I wanted to run this by you first before trying it.

How can I echo this variable to make sure it took the value I set?

Quote & Reply |

auouymous	2011-12-08 , 22:38
Posts: 875 \| Thanked: 918 times \| Joined on Sep 2010	#243

Originally Posted by Addison

So, like this?

gconftool-2 --type int --set /apps/osso/sound/master_volume key 6000000

I wanted to run this by you first before trying it.

How can I echo this variable to make sure it took the value I set?

Remove 'key' and maybe try something more reasonable like 150. And if you install gconf-editor you'll have a nice GUI to modify the value and see changes.

Quote & Reply |

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

	Addison	2011-12-08 , 22:44
	Posts: 3,811 \| Thanked: 1,151 times \| Joined on Oct 2007 @ East Lansing, MI	#244

I just tried

gconftool-2 --type int --set /apps/osso/sound/master_volume 120

No error, but no noticable difference either.

How can I print the value of master_volume in Xterm?

Quote & Reply |

auouymous	2011-12-09 , 00:23
Posts: 875 \| Thanked: 918 times \| Joined on Sep 2010	#245

Originally Posted by Addison

How can I print the value of master_volume in Xterm?

gconftool-2 --get /apps/osso/sound/master_volume

Quote & Reply |

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

	Addison	2011-12-09 , 00:28
	Posts: 3,811 \| Thanked: 1,151 times \| Joined on Oct 2007 @ East Lansing, MI	#246

Thanks.

I'll try that later at night when I'm not getting any messages.

I think that setting the volume over 100 broke Modest somehow so I stopped receiving notifications.

It could just be a weird coincidence though. Not sure.

Thanks for the follow up on this.

Quote & Reply |

	Addison	2011-12-12 , 18:23
	Posts: 3,811 \| Thanked: 1,151 times \| Joined on Oct 2007 @ East Lansing, MI	#247

How can I kill Modest?

This is my current script to turn off one minute notifications.

Code:

blank=`gconftool-2 -g /system/osso/dsm/display/display_blank_timeout`
gconftool-2 --type boolean --set /apps/modest/auto_update False
killall modest
sudo /etc/init.d/mce restart
/usr/bin/set-backlight `gconftool-2 --get /apps/adv-backlight/brightness`
sleep 4 
restore_value()
{
  gconftool-2 --type $1 --set $2 `gconftool-2 --get $2`
}
gconftool-2 --type int --set /apps/osso/applet/osso-applet-display/turn_off_display 30
gconftool-2 --type int --set /apps/osso/applet/osso-applet-display/brightness_period 30
gconftool-2 --type int --set /system/osso/dsm/display/display_dim_timeout 30
gconftool-2 --type int --set /system/osso/dsm/display/display_blank_timeout 30

I've typed in Xterm killall modest.

In the Email app, I've made sure the notification box is unchecked and I hit Okay.

I've even killed it in the task manager feature in ASUI.

But still, one minute later it pops back up, sometimes pegging the CPU at like 50%.

Any ideas?

Last edited by Addison; 2011-12-12 at 18:36.

Quote & Reply |

auouymous	2011-12-12 , 20:20
Posts: 875 \| Thanked: 918 times \| Joined on Sep 2010	#248

Originally Posted by Addison

Why are you still using the old matchbox swipe? Follow the instructions at http://talk.maemo.org/showpost.php?p...3&postcount=52 to upgrade to the bug fixed package. You should see a blue "matchbox-window-manager" instead of a white "matchbox-window-manager-swipe" in the process viewer when correctly installed.

Originally Posted by Addison

How can I kill Modest?

Try sleeping after you disable auto_update to give modest time to see the setting before you kill it.

Quote & Reply |

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

	Addison	2011-12-12 , 20:23
	Posts: 3,811 \| Thanked: 1,151 times \| Joined on Oct 2007 @ East Lansing, MI	#249

Okay.

I'll try both.

Thanks.

Quote & Reply |

	Addison	2011-12-12 , 21:50
	Posts: 3,811 \| Thanked: 1,151 times \| Joined on Oct 2007 @ East Lansing, MI	#250

Yikes.

I need help! *lol*

So I went ahead with your suggestion...

Code:

blank=`gconftool-2 -g /system/osso/dsm/display/display_blank_timeout`
gconftool-2 --type boolean --set /apps/modest/auto_update False
sleep 4
killall modest
sudo /etc/init.d/mce restart
etc...

I ran this from Personal Menu.

Afterwards, Power Button, then I pressed the Full Screen button by accident.

I got nothing but a white screen.

Waited about 10 minutes and decided to reboot.

I have two Desktops now.

I can bring up ASUI and it shows hildon-desktop maxed out at 98%.

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.

I've rebooted twice now so I think I might be hosed. *lol*