Originally Posted by wolke

I CANT FIGURE OUT HOW TO CHANGE THE GODDAM SYSTEM VOLUME.

tried with built-in clis:
pulseaudio-utils, alsamixer, amixer

tried with c libraries and all audio APIs i found in the developer api:
qmediaplayer, phonon.audiooutput.

this should SO not be difficult. anybody know how to do this? {programmatically adjust the system volume, such that the slider in the status bar also moves with it}

Originally Posted by wolke

key features are missing, like music-control and HtheB-style-volume-control, and its a ***** to install and run because it needs super-privileges.

Originally Posted by HtheB

Never heard of inception before? You have super priviliges if you incept the package. You can make a special version for inception users, so we can activate this.

Inception

Originally Posted by wolke

thanks, but i know about inception;
'
this will be the first one that will work out of the box {maybe just for inception-users and open-moders, but ill do my best to make it work for anybody that can use a terminal and follow instructions in it once}.
'

the thing is that you currently need to use a terminal, and set up an upstart file that manages your path depending on how you have it set up. power users will have it set up differently, and non-power users will have know idea how to do it at all.

im hoping to make this app-store-able, which inception makes impossible. also, even using inception, i make a lot of privileged shell calls so im going to need to use aegis-ctl as well.

n9-button-monitor works very nicely out of the box, but just for open-moders right now, and anyone who knows how to use aegis-ctl when permission errors occur. {i dont know what permission errors youd get, because i havent run it on a non-hacked kernel yet}

Originally Posted by GuSec

Hi there, I'm not succeeding with your script.
....
Permission denied: opening file /home/user/.omap3cam

Nothing happens... What am I doing wrong?

Originally Posted by wolke

first, thanks! youre the first person to try it out in the wild and tell me about it.

so, thats a root permission that i didnt realize that aegis didnt give you by default.
ive been testing it mostly on open mode, and i forgot to test the camera flash on closed mode since i changed it.

for a solution, it is probably sufficient to just run develsh first.
i.e.:
# devel-su
PASSWORD: {rootme}
# develsh
# python /usr/bin/n9-button-monitor

please lemme know if that does it, and ill update the instructions. thanks again!

Originally Posted by GuSec

Now it worked just fine and did exactly what it was supposed to do! It's a bit slow though, which matter most with the camera, but it may be affected by a simultaneous execution of the non working start script.

So how do I rewrite the start script to grant the correct permissions?

Originally Posted by wolke

just do devel-su -c "develsh -c 'CMD'".

try this to get it to auto-start at boot {i havent tested it on closed mode}.

/etc/init/apps/n9-button-monitor.conf

Code:

description "Startup script for n9-button-monitor"
author "elliot.wolk@gmail.com"
console none
respawn
exec bash -c 'source /etc/profile; PATH=$PATH:/usr/local/bin; develsh -c n9-button-monitor'

Originally Posted by GuSec

This did not work out (chmod 755 /etc/init/apps/n9-button-monitor.conf)! The strange thing is that "source /etc/profile; PATH=$PATH:/usr/local/bin; develsh -c n9-button-monitor" works out just fine in the terminal, it does exactly what it's supposed to. So what's up with autostart?

Extremely useful script though! I love the way I can just pull up the phone and hold one button to get a flashlight!