maemo.org wiki - Recent changes [en]

Community Council/Council election Q1/2 2012

andre — Wed, 16 May 2012 11:03:29 GMT

fix last change

←Older revision		Revision as of 11:03, 16 May 2012
Line 23:		Line 23:
	The election processes are described in detail at [[Community Council/Election process]].		The election processes are described in detail at [[Community Council/Election process]].

-	'''In order to vote''', a community member must have had maemo.org account for over 3 months,'''(NOT ~~Talk~~.maemo.~~com~~ account)''' and have [[karma]] of 10 or above. Candidates need to have a [[karma]] of 100 or higher. [[/Eligible candidates \| List of potential candidates]] Karma is earned through a variety of mechanisms, but to earn points for contributions on [http://talk.maemo.org/ talk.maemo.org], you need to [[link talk.maemo.org account with maemo.org profile]].	+	'''In order to vote''', a community member must have had maemo.org account for over 3 months, '''(a maemo.org account is NOT a talk.maemo.org account)''' and have [[karma]] of 10 or above. Candidates need to have a [[karma]] of 100 or higher. [[/Eligible candidates \| List of potential candidates]] Karma is earned through a variety of mechanisms, but to earn points for contributions on [http://talk.maemo.org/ talk.maemo.org], you need to [[link talk.maemo.org account with maemo.org profile]].

	== Election material ==		== Election material ==

Community Council/Council election Q1/2 2012

41.233.75.167 — Wed, 16 May 2012 07:43:37 GMT

Eligibility:

←Older revision		Revision as of 07:43, 16 May 2012
Line 23:		Line 23:
	The election processes are described in detail at [[Community Council/Election process]].		The election processes are described in detail at [[Community Council/Election process]].

-	'''In order to vote''', a community member must have had maemo.org account for over 3 months, and have [[karma]] of 10 or above. Candidates need to have a [[karma]] of 100 or higher. [[/Eligible candidates \| List of potential candidates]] Karma is earned through a variety of mechanisms, but to earn points for contributions on [http://talk.maemo.org/ talk.maemo.org], you need to [[link talk.maemo.org account with maemo.org profile]].	+	'''In order to vote''', a community member must have had maemo.org account for over 3 months,'''(NOT Talk.maemo.com account)''' and have [[karma]] of 10 or above. Candidates need to have a [[karma]] of 100 or higher. [[/Eligible candidates \| List of potential candidates]] Karma is earned through a variety of mechanisms, but to earn points for contributions on [http://talk.maemo.org/ talk.maemo.org], you need to [[link talk.maemo.org account with maemo.org profile]].

	== Election material ==		== Election material ==

SMSCON

yablacky — Wed, 16 May 2012 06:51:27 GMT

Wiki access history:

←Older revision		Revision as of 06:51, 16 May 2012
Line 1,041:		Line 1,041:
	This page has been accessed 42,375 times. --[[User:yablacky\|yablacky]] 15:30, 28 April 2012 (UTC)<br>		This page has been accessed 42,375 times. --[[User:yablacky\|yablacky]] 15:30, 28 April 2012 (UTC)<br>
	This page has been accessed 43,315 times. --[[User:yablacky\|yablacky]] 00:14, 13 May 2012 (UTC)<br>		This page has been accessed 43,315 times. --[[User:yablacky\|yablacky]] 00:14, 13 May 2012 (UTC)<br>
		+	This page has been accessed 43,675 times. --[[User:yablacky\|yablacky]] 06:51, 16 May 2012 (UTC) wow, 10.000 :))

	[[Category:Software]]		[[Category:Software]]
	[[Category:N900]]		[[Category:N900]]

Community Council/Council election Q1/2 2012

luiscesjr — Wed, 16 May 2012 00:23:39 GMT

Fixed timetable, as from latest received mail.

←Older revision		Revision as of 00:23, 16 May 2012
Line 15:		Line 15:
	* April 30: Nominations close		* April 30: Nominations close
	* May 1: List of candidates announced		* May 1: List of candidates announced
-	* May 15: Voting opens [http://maemo.org/vote/vote.php?election_id=20]	+	* May 16: Voting opens [http://maemo.org/vote/vote.php?election_id=20]
-	* May 22: Voting closes	+	* May 23: Voting closes
	* May <fixme>: Results announced		* May <fixme>: Results announced

User:Mr pingu

mr_pingu — Mon, 14 May 2012 21:27:32 GMT

Setting up the device:

←Older revision		Revision as of 21:27, 14 May 2012
Line 52:		Line 52:
	swapon /dev/mmcblk1p2		swapon /dev/mmcblk1p2
	swapoff /dev/mmcblk0p3		swapoff /dev/mmcblk0p3
		+	echo 5 > /proc/sys/vm/page-cluster
		+	echo 256 > /sys/block/mmcblk0/queue/nr_requests
		+	echo 512 > /sys/block/mmcblk1/queue/nr_requests
		+	echo 7 > /sys/block/mmcblk0/queue/iosched/slice_idle
		+	echo 7 > /sys/block/mmcblk1/queue/iosched/slice_idle
		+	echo 4 > /sys/block/mmcblk0/queue/iosched/quantum
		+	echo 4 > /sys/block/mmcblk1/queue/iosched/quantum
		+	echo 125 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync
		+	echo 125 > /sys/block/mmcblk1/queue/iosched/fifo_expire_sync
		+	echo 250 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async
		+	echo 250 > /sys/block/mmcblk1/queue/iosched/fifo_expire_async

	end script		end script

Task:Maemo OBS

jeremiah — Mon, 14 May 2012 21:08:52 GMT

Goals:

←Older revision		Revision as of 21:08, 14 May 2012
Line 3:		Line 3:
	This project enables the following:		This project enables the following:

-	*~~To provide e~~ a single community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.	+	*Provide a single, community OBS that includes Harmattan, Fremantle and Diablo as targets to faciliate the development of applications that work on all platforms.
-	*To collaborate with Mer/Nemo to share the costs of maintaining and operating community OBS.	+	*To collaborate with Mer/Nemo to share the costs of maintaining and operating the community OBS.

	== Weekly meetings ==		== Weekly meetings ==

Community Council/Council election Q1/2 2012

woody14619 — Mon, 14 May 2012 17:03:31 GMT

Election timetable:

←Older revision		Revision as of 17:03, 14 May 2012
Line 15:		Line 15:
	* April 30: Nominations close		* April 30: Nominations close
	* May 1: List of candidates announced		* May 1: List of candidates announced
-	* May ~~<fixme>~~: Voting opens	+	* May 15: Voting opens [http://maemo.org/vote/vote.php?election_id=20]
-	* May ~~<fixme>~~: Voting closes	+	* May 22: Voting closes
	* May <fixme>: Results announced		* May <fixme>: Results announced

SMSCON

yablacky — Sun, 13 May 2012 17:45:11 GMT

Remove (now) superfluous sub header.

←Older revision		Revision as of 17:45, 13 May 2012
Line 227:		Line 227:
	* 'COM_CUSTOM': Command to run a predefined [[#Files intended to be edited by user directly \| user script]]. The script runs asynchronously until it terminates itself.<br>Version 0.9.18 supports definition of command text that accepts one or more arbitrary text parts. This parts are extracted and passed to the user script. This indirectly adds support for multiple, unlimited number of user scripts. See [[#Variable text parts in command definitions \| below]] for details.		* 'COM_CUSTOM': Command to run a predefined [[#Files intended to be edited by user directly \| user script]]. The script runs asynchronously until it terminates itself.<br>Version 0.9.18 supports definition of command text that accepts one or more arbitrary text parts. This parts are extracted and passed to the user script. This indirectly adds support for multiple, unlimited number of user scripts. See [[#Variable text parts in command definitions \| below]] for details.
	* 'COM_CUSTOMLOG': Command to ask for output of last COM_CUSTOM command.		* 'COM_CUSTOMLOG': Command to ask for output of last COM_CUSTOM command.
-	* 'COM_SHELL': The command text must be a unix shell command. It is directly passed to a unix shell for execution. In contrast to COM_CUSTOM, the command does not execute in background and its output is immediately returned as notification SMS and/or EMAIL.<br>Version 0.9.18 supports definition of command text that accepts one or more arbitrary text parts. This allows to modify the shell command on a per sms-basis. See [[#Variable text parts in command definitions \| below]] for details.	+	* 'COM_SHELL': The command text must be a unix shell command. It is directly passed to a unix shell for execution. In contrast to COM_CUSTOM, the COM_SHELL command does not execute in background and its output is immediately returned as notification SMS and/or EMAIL. Due to synchronous execution, you should not call commands that run for unpredictable long time (like pure ping).<br>Version 0.9.18 supports the definition of command text that accepts one or more arbitrary text parts. This allows to modify the shell command on a per sms-basis. See [[#Variable text parts in command definitions \| below]] for details.
	* 'COM_ALARM': Command to play once a predefined [[#Files intended to be edited by user directly \| sound file]]. Alarm duration depends on sound file content; there is no command to stop playing the alarm sound.		* 'COM_ALARM': Command to play once a predefined [[#Files intended to be edited by user directly \| sound file]]. Alarm duration depends on sound file content; there is no command to stop playing the alarm sound.
	* 'COM_RESTART': Command to restart the daemon.		* 'COM_RESTART': Command to restart the daemon.
Line 293:		Line 293:
	For COM_SHELL the assignment of message chars to placeholders is not important. Placeholder just indicate variable parts of the message here. The unix command being executed consist of the complete message anyway (after message prefix/suffix was stripped away).		For COM_SHELL the assignment of message chars to placeholders is not important. Placeholder just indicate variable parts of the message here. The unix command being executed consist of the complete message anyway (after message prefix/suffix was stripped away).

-	~~This~~ smscon_script demonstrates how to manage multiple user scripts. It is an example that may serve as a basis for your own dispatching script. Note that it does not depend on how COM_CUSTOM is actually defined (unless it has at least 3 placeholders):	+	====An example user script for COM_CUSTOM====
		+
		+	The smscon_script below demonstrates how to manage multiple user scripts. It is an example that may serve as a basis for your own dispatching script. Note that it does not depend on how COM_CUSTOM is actually defined (unless it has at least 3 placeholders):
	<pre>		<pre>
	#!/bin/sh		#!/bin/sh
Line 356:		Line 358:

	</pre>		</pre>
		+
		+	====A powerful but dangerous example for COM_SHELL====
		+
		+	Since version 0.9.18 it is possible to define the command text for COM_SHELL as
		+	sh -c "*"
		+	'''SECURITY NOTE''': Don't do that if you haven't any shadow of what this means. For those who know and are crazy enough to do, it offers amazing possibilities to control the phone via SMS. You should have SMS_COMPREFIX and SMS_COMSUFFIX defined to some reasonable long text.

	===Prefix/suffix for all SMS command strings===		===Prefix/suffix for all SMS command strings===
Line 559:		Line 567:
	Shown is an example config file as stored in <code>smscon_config</code>. This is presented for the gentle user only. Normal users never need to see nor edit this directly. Please use smscon command line or SMSCON Editor to edit settings.		Shown is an example config file as stored in <code>smscon_config</code>. This is presented for the gentle user only. Normal users never need to see nor edit this directly. Please use smscon command line or SMSCON Editor to edit settings.

-	~~====Recent version====~~
	<pre>		<pre>
	# smscon user settings (initially written by version 0.9.16)		# smscon user settings (initially written by version 0.9.16)

Updating the firmware

topet2k12001 — Sun, 13 May 2012 14:09:28 GMT

Option 5:

←Older revision		Revision as of 14:09, 13 May 2012
Line 191:		Line 191:
	====== Option 5 ======		====== Option 5 ======

-	Install other version of update drivers. Step by step instructions can be found at [http://talk.maemo.org/showpost.php?p=849980&postcount=20 talk.maemo.org]	+	Install other version of update drivers. Step by step instructions can be found at [http://talk.maemo.org/showpost.php?p=849980&postcount=20 talk.maemo.org]. Video tutorial for setting up/installing the necessary drivers to enable flashing on Windows 7 64-bit OS can be found here: [http://www.youtube.com/watch?v=OkhjA9rztz0&hd=1]

	====== Option 6 ======		====== Option 6 ======

SMSCON

yablacky — Sun, 13 May 2012 12:39:33 GMT

remove details, link to them

(Difference between revisions)

Community Council/Council election Q1/2 2012

estel — Sat, 12 May 2012 22:33:42 GMT

Temporaly fixed wrong dates

←Older revision		Revision as of 22:33, 12 May 2012
Line 1:		Line 1:
-	The [[Community Council \| Maemo Community Council]] will have its next election in ~~April/~~May 2012, electing a new council for a 6 month term.	+	The [[Community Council \| Maemo Community Council]] will have its next election in May 2012, electing a new council for a 6 month term.

	The election page will eventually be available [http://maemo.org/vote here].		The election page will eventually be available [http://maemo.org/vote here].
Line 5:		Line 5:
	== Election Details ==		== Election Details ==

-	Initially pencilled in for April 2012, the Election was postponed for a month and the nomination period extended for that period ~~of time due to zero nominations~~.	+	Initially pencilled in for April 2012, the Election was postponed for a month and the nomination period extended for that period.

	== Election timetable ==		== Election timetable ==
Line 15:		Line 15:
	* April 30: Nominations close		* April 30: Nominations close
	* May 1: List of candidates announced		* May 1: List of candidates announced
-	* May 6: Voting opens	+	* May <fixme>: Voting opens
-	* May 13: Voting closes	+	* May <fixme>: Voting closes
-	* May 15: Results announced	+	* May <fixme>: Results announced

	== Eligibility ==		== Eligibility ==

SMSCON

yablacky — Sat, 12 May 2012 22:30:31 GMT

List of known sms commands: add internal link

Changing the eMMC filesystem

estel — Fri, 11 May 2012 00:04:14 GMT

Added line number in genfstab.awk

←Older revision		Revision as of 00:04, 11 May 2012
Line 59:		Line 59:
	''Making Maemo accept the new filesystem type.''		''Making Maemo accept the new filesystem type.''

-	Line no. 12, 17, 22, 23 and 25 of rcS-late got "ext3" hard-coded in it (line 6 contains ext3 in comment, but this don't affect funcionality of script - You can change it if You want). We need to edit these lines to represent our new filesystem.	+	Line no. 12, 17, 22, 23 and 25 of rcS-late got "ext3" hard-coded in it (line 9 contains ext3 in comment, but this don't affect funcionality of script - You can change it if You want). We need to edit these lines to represent our new filesystem.
	Ext4 example:		Ext4 example:
	<pre>		<pre>
Line 88:		Line 88:
	Make sure line 23 contains a valid fsck.X command. Try running the command with all its parameters manually before making it permanent.		Make sure line 23 contains a valid fsck.X command. Try running the command with all its parameters manually before making it permanent.

-	File <code>/usr/lib/genfstab.awk</code> also contain ext3 hardcoded in it. For switching to another ext filesystem (like ext4) change it to appropriate value.	+	File <code>/usr/lib/genfstab.awk</code> also contain ext3 hardcoded in it (line 19). For switching to another ext filesystem (like ext4) change it to appropriate value.

	<code>//Note for Geeks:</code>		<code>//Note for Geeks:</code>

Updating the firmware

joerg_rw — Thu, 10 May 2012 22:08:49 GMT

Troubleshooting: added note about blacklisting to "terse complete foolproof procedure"

←Older revision		Revision as of 22:08, 10 May 2012
Line 85:		Line 85:
	'''Some notes''':		'''Some notes''':
	# If you get this error while trying to run flasher-3.5 <br /><pre>./flasher-3.5: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory</pre> you are probably on 64 bit and you need to install a libusb compatibility package. For example, on openSUSE 11.4 you just run <br /><pre>zypper in libusb-0_1-4-32bit</pre><br />On a debian based system you can download and install the 32-bit version in a separate location (don't install it on your system itself) <br />First download the libusb-0.1-4_0.1.12-13_i386.deb library (google is your friend) and then:<br/><pre>dpkg-deb -c libusb-0.1-4_0.1.12-13_i386.deb</pre><pre>sudo dpkg -x libusb-0.1-4_0.1.12-13_i386.deb libusb-0.1-4_0.1.12-13_i386</pre><pre>sudo mv libusb-0.1-4_0.1.12-13_i386/lib/* /lib32</pre><pre>cd /usr/lib32</pre><pre>sudo ln -s /lib32/libusb-0.1.so.4</pre><br/>Now Set the library path (as su):<pre>sudo su</pre><pre>export LD_LIBRARY_PATH=/usr/lib32/:$PATH</pre>Now you can run the flasher application (as su)<br/>		# If you get this error while trying to run flasher-3.5 <br /><pre>./flasher-3.5: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory</pre> you are probably on 64 bit and you need to install a libusb compatibility package. For example, on openSUSE 11.4 you just run <br /><pre>zypper in libusb-0_1-4-32bit</pre><br />On a debian based system you can download and install the 32-bit version in a separate location (don't install it on your system itself) <br />First download the libusb-0.1-4_0.1.12-13_i386.deb library (google is your friend) and then:<br/><pre>dpkg-deb -c libusb-0.1-4_0.1.12-13_i386.deb</pre><pre>sudo dpkg -x libusb-0.1-4_0.1.12-13_i386.deb libusb-0.1-4_0.1.12-13_i386</pre><pre>sudo mv libusb-0.1-4_0.1.12-13_i386/lib/* /lib32</pre><pre>cd /usr/lib32</pre><pre>sudo ln -s /lib32/libusb-0.1.so.4</pre><br/>Now Set the library path (as su):<pre>sudo su</pre><pre>export LD_LIBRARY_PATH=/usr/lib32/:$PATH</pre>Now you can run the flasher application (as su)<br/>
-	# If flasher runs but exits when you plug in the phone saying <br /><pre>Unable to enumerate USB buses!</pre> the problem is the kernel module cdc_phonet that is automatically loaded. The solution is to temporarily blacklist it, until you are done flashing. On openSUSE this can be done by ~~editing this~~ file:<br /><pre>/etc/modprobe.d/50-blacklist.conf~~</pre>Add one line at the end:<br /><pre>blacklist cdc_phonet~~</pre>When you finish flashing, remove the ~~line~~.<br /><br />	+	# If flasher runs but exits when you plug in the phone saying <br/>
-	~~On archlinux blacklisting (alone?) did not work~~. ~~waiting a few seconds with the device (in update mode) connected then running~~ the command again ~~worked fine~~.	+	<pre>Unable to enumerate USB buses!</pre>
		+	the problem usually is the kernel module cdc_phonet that is automatically loaded. The solution is to temporarily blacklist it, until you are done flashing. On openSUSE this can be done by creating a file like this:<br /><pre>echo "blacklist cdc_phonet" >/etc/modprobe.d/00-blacklist-cdcphonet.conf</pre>When you finish flashing, remove the file.<br /><br />
		+	There are other, probably timing, reasons causing occasional "unable to enumerate USB". Immediately issue the flasher command again, up-arrow usually helps fetching last command to re-issue it.

	=== Mac OS X ===		=== Mac OS X ===
Line 318:		Line 320:
	* If flashing stops with "Write failed after 1048576 bytes usb_bulk_write: Resource temporarily unavailable", do not disconnect your N900 from usb and try again the flasher command.		* If flashing stops with "Write failed after 1048576 bytes usb_bulk_write: Resource temporarily unavailable", do not disconnect your N900 from usb and try again the flasher command.
	* If you cannot establish a connection with N900, or got any other problems during starting or completing the flashing process, do the following steps which describe '''the complete foolproof flashing procedure''' again in terse form: ''(use a Linux machine to flash! Windows isn't really backed up with much support from community, for obvious reasons.)''		* If you cannot establish a connection with N900, or got any other problems during starting or completing the flashing process, do the following steps which describe '''the complete foolproof flashing procedure''' again in terse form: ''(use a Linux machine to flash! Windows isn't really backed up with much support from community, for obvious reasons.)''
		+	*# blacklist cdc_phonet (see above)! Run modprobe -r cdc_phonet
	*#(try to) Turn off the device - if nothing else helps, holding power key for >8s is the ultimate means (except next point 2.) to do this.		*#(try to) Turn off the device - if nothing else helps, holding power key for >8s is the ultimate means (except next point 2.) to do this.
	*#Remove the battery - even if you were not able to shut device down in 1.		*#Remove the battery - even if you were not able to shut device down in 1.
Line 323:		Line 326:
	*#Plug the device to computer with a good USB cable.		*#Plug the device to computer with a good USB cable.
	*#Insert battery while holding "u" key. You can release the key as soon as screen turns on and shows the USB logo. Flashing shall start automatically. ''(If flasher answers "unable to enumerate USB buses!" as soon as N900 gets battery, just re-issue same flasher cmd immediately - cursor-up helps ;-D). If flasher doesn't detect the device, a Ctrl+C abort and re-issuing of the flasher command may help''		*#Insert battery while holding "u" key. You can release the key as soon as screen turns on and shows the USB logo. Flashing shall start automatically. ''(If flasher answers "unable to enumerate USB buses!" as soon as N900 gets battery, just re-issue same flasher cmd immediately - cursor-up helps ;-D). If flasher doesn't detect the device, a Ctrl+C abort and re-issuing of the flasher command may help''
-	*#Check for correct diagnostic output of flasher, as quoted above. After flashing has finished, remove battery ->(1.) 2.)	+	*#Check for correct diagnostic output of flasher, as quoted above. After flashing has finished, remove battery ->(2.) 3.)
-	#Repeat same procedure (1. - 6.) for each image to flash (sequence: eMMC first, then rootfs - some mess on rootfs may break eMMC flashing and require sequence rootfs eMMC rootfs again). ''So far this procedure always worked, given your PC side has no problems. Many known problems on PC side - esp "waits forever" / "doesn't find N900" - get fixed with a reboot immediately prior* to doing the flashing.''	+	#Repeat same procedure (2. - 7.) for each image to flash (sequence: eMMC first, then rootfs - some mess on rootfs may break eMMC flashing and require sequence rootfs eMMC rootfs again). ''So far this procedure always worked, given your PC side has no problems. Many known problems on PC side - esp "waits forever" / "doesn't find N900" - get fixed with a reboot immediately prior* to doing the flashing.''
	#After flashing unplug your device from PC prior to first boot. First boot can take several minutes, and screen may turn dark during that. You may try lock-slider switch, but '''do not power down''' device during first boot, until it finally finished - I.E. do not touch power button after flashing, unless you're sure* device hasn't already started to boot. Usually device will power down when unplugged from PC in flashing mode, you can tell this from white LED fading out, not even any dim backlight, and device not reacting to lockslider and kbd-open. Power it up from battery then, using the power button. ''Only then'' plugging in the wallcharger is a good idea. Make sure device charges and recharge battery while you're at it. After battery got fully charged again, it's probably safe to switch off your N900, as first boot setup should have finished.		#After flashing unplug your device from PC prior to first boot. First boot can take several minutes, and screen may turn dark during that. You may try lock-slider switch, but '''do not power down''' device during first boot, until it finally finished - I.E. do not touch power button after flashing, unless you're sure* device hasn't already started to boot. Usually device will power down when unplugged from PC in flashing mode, you can tell this from white LED fading out, not even any dim backlight, and device not reacting to lockslider and kbd-open. Power it up from battery then, using the power button. ''Only then'' plugging in the wallcharger is a good idea. Make sure device charges and recharge battery while you're at it. After battery got fully charged again, it's probably safe to switch off your N900, as first boot setup should have finished.

Updating the firmware

109.129.90.13 — Thu, 10 May 2012 21:18:13 GMT

Linux:

←Older revision		Revision as of 21:18, 10 May 2012
Line 84:		Line 84:
	# It should start flashing and then reboot. You can remove the USB cable when the flasher program exits back to the shell prompt.		# It should start flashing and then reboot. You can remove the USB cable when the flasher program exits back to the shell prompt.
	'''Some notes''':		'''Some notes''':
-	# If you get this error while trying to run flasher-3.5 <br /><pre>./flasher-3.5: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory</pre> you are probably on 64 bit and you need to install a libusb compatibility package. For example, on openSUSE 11.4 you just run <br /><pre>zypper in libusb-0_1-4-32bit</pre>	+	# If you get this error while trying to run flasher-3.5 <br /><pre>./flasher-3.5: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory</pre> you are probably on 64 bit and you need to install a libusb compatibility package. For example, on openSUSE 11.4 you just run <br /><pre>zypper in libusb-0_1-4-32bit</pre><br />On a debian based system you can download and install the 32-bit version in a separate location (don't install it on your system itself) <br />First download the libusb-0.1-4_0.1.12-13_i386.deb library (google is your friend) and then:<br/><pre>dpkg-deb -c libusb-0.1-4_0.1.12-13_i386.deb</pre><pre>sudo dpkg -x libusb-0.1-4_0.1.12-13_i386.deb libusb-0.1-4_0.1.12-13_i386</pre><pre>sudo mv libusb-0.1-4_0.1.12-13_i386/lib/* /lib32</pre><pre>cd /usr/lib32</pre><pre>sudo ln -s /lib32/libusb-0.1.so.4</pre><br/>Now Set the library path (as su):<pre>sudo su</pre><pre>export LD_LIBRARY_PATH=/usr/lib32/:$PATH</pre>Now you can run the flasher application (as su)<br/>
	# If flasher runs but exits when you plug in the phone saying <br /><pre>Unable to enumerate USB buses!</pre> the problem is the kernel module cdc_phonet that is automatically loaded. The solution is to temporarily blacklist it, until you are done flashing. On openSUSE this can be done by editing this file:<br /><pre>/etc/modprobe.d/50-blacklist.conf</pre>Add one line at the end:<br /><pre>blacklist cdc_phonet</pre>When you finish flashing, remove the line.<br /><br />		# If flasher runs but exits when you plug in the phone saying <br /><pre>Unable to enumerate USB buses!</pre> the problem is the kernel module cdc_phonet that is automatically loaded. The solution is to temporarily blacklist it, until you are done flashing. On openSUSE this can be done by editing this file:<br /><pre>/etc/modprobe.d/50-blacklist.conf</pre>Add one line at the end:<br /><pre>blacklist cdc_phonet</pre>When you finish flashing, remove the line.<br /><br />
	On archlinux blacklisting (alone?) did not work. waiting a few seconds with the device (in update mode) connected then running the command again worked fine.		On archlinux blacklisting (alone?) did not work. waiting a few seconds with the device (in update mode) connected then running the command again worked fine.

Special:Log/protect

andre — Thu, 10 May 2012 12:33:32 GMT

protected "Wiki gardeners": [edit=autoconfirmed:move=autoconfirmed]

Wiki gardeners

andre — Thu, 10 May 2012 12:33:20 GMT

Reverted edits by 188.143.232.12 (Talk); changed back to last version by Amigadave

←Older revision		Revision as of 12:33, 10 May 2012
Line 70:		Line 70:
	* Put together an categorical index with cover content/article.		* Put together an categorical index with cover content/article.

-	~~I don~~'~~t think so. It~~'~~s hard to get good facial prnotrpioos when doing a self-portrait. If you hold the camera at a wonky angle, you look weird. . .but it~~'~~s hard~~ to ~~hold the camera at a good angle when you are just holding the camera out and guessing~~. ~~But I also did just did focus point focus with piknic, blurring everything not in focus~~. ~~I suppose it does give it an underwater or dreamlike quality~~.	+	=== Other ===
		+	Check maintenance stuff in [[Special:Specialpages]]:
		+	* Create [[Special:Wantedpages\|wanted pages]], even as ''stubs''
		+	* Fix [[Special:Doubleredirects\|double redirects]]
		+	* Add links to [[Special:Lonelypages \| orphan pages]]
		+	* And more...

	== Members ==		== Members ==

Special:Log/protect

andre — Thu, 10 May 2012 12:33:16 GMT

protected "User:Jaffa": [edit=autoconfirmed:move=autoconfirmed]

Task:Community Council

andre — Thu, 10 May 2012 12:33:07 GMT

Reverted edits by 208.23.77.15 (Talk); changed back to last version by Jaffa

←Older revision		Revision as of 12:33, 10 May 2012
Line 1:		Line 1:
-	~~First all i would like to thank you~~ for the ~~amazing pudorct at our service, finally not only as~~ the ~~n series has blown the expectations~~ of ~~high end technology but as let~~ the ~~consumers all able full modify their mobile they way we want it, just like everyone~~'s ~~desktop is different at home. I am inspired music engineer(21) and i carried~~ the ~~N95-1~~, ~~my first nokia was when i was very young(canada) nokia 3330,than decided to get~~ a ~~new nokia,the symbian was easy,~~ and ~~i liked snake, so i got~~ the ~~nokia 6600(2004)and i fell in love with~~ the ~~phone and~~ the ~~nokia~~ the ~~brand~~ , ~~promised to buy any mobile from nokia~~. ~~carried~~ the ~~phone~~ for ~~two years, the camera was amazing back than~~. ~~Within the love with nokia i started to~~ a lot of ~~research on nokia~~ and the ~~beginning of smart phones~~. ~~Than the N95-1(2006~~) ~~was release and became my first n-series.~~'~~'To me a classic phone'' Unfortunately i do carry the phone with me~~ , ~~although its in my room~~ it ~~is broken(my friend dropped it , it was~~ the ~~first time~~ the ~~phone was damage~~. ~~I decided not~~ to ~~buy~~ a ~~cellphone until i see~~ the ~~next n series made a ''MOBILE DEVICE''~~, to ~~be honest the n958gb~~ and the ~~n96 did not appeal to me~~.~~I wanted something different~~,~~like~~ the ~~n93 to the n95~~. ~~Now this summer(2009) was remarkable~~, with the ~~announce~~ of the ~~n97~~, ~~defiantly my next phone~~.~~(actually yesterday was the first time i saw the phone~~ in ~~Canada~~, ~~a women from the mid~~-~~east had~~ the ~~white one) AMAZING!!~~. ~~since~~ the ~~release i've been planning~~ to ~~save to buy it~~. ~~Until later august I heard about~~ the ~~N900; and believe me i spent hours reading~~ the ~~specs~~ of ~~this phone,~~ and ~~i am blown~~. ~~It is~~ the ~~mobile device that i~~ have ~~dreamed of~~. ~~I know I've been typing a lot, i wanted to contact nokian900 but i couldn't find a canadian outsource for a question and inquiry~~. ~~I googled~~ the ~~VP of~~ the ~~pudorct~~ and ~~found your blog.~~....~~.I am not sure if it was announced or confirmed~~, ~~but~~ to ~~release~~ of the ~~phone~~. ~~''Will~~ the ~~N900 be release only by 3G HSDPA 1700~~ / ~~2100~~ / ~~900 ?Will the GSM 850~~ / ~~900~~ / ~~1800~~ / ~~1900 users (such as I~~,~~AT&T~~/~~Rogers~~/~~Fido)~~ be ~~able~~ to ~~use the N900? In request the phone doesn't have~~ to be ~~sold in countries such as~~ the ~~n95-1~~. ~~Mine was ordered from~~ the ~~UK. It leaves confused if the phone will be release in gsm capability. (labrecstudios@gmail.com)awaiting a response if possible.Thank you~~	+	#redirect [[Community_Council]]
		+
		+	{{Template:100Days agenda}}
		+	{{task\|completed}}
		+
		+	== Objective ==
		+	A process for electing a small "Community Council" should be created and elections held.
		+
		+	[[User:qgil\|Quim Gil]] is currently responsible for managing the Maemo community on behalf of Nokia. But who is the community? Getting consensus of hundreds of disparate people through mailing lists and wiki-edits means the person who shouts loudest wins.
		+
		+	Therefore —inspired by Debian's Project Leader concept— during the next [[100Days]], a process for electing a small "Community Council" should be created and elections held.
		+
		+	== The Community council ==
		+
		+	This is the proposal for a Community Council based on the [[Task:Community Council\|proposal]] from the [[100Days\|100 Days brainstorm]]. It is a work in progress to be thrashed out over the next 30 days, so these ideas are fluid and will change frequently. Please see the [[Talk:Community_Council\|talk page]] for discussion.
		+
		+	=== Purpose ===
		+	The maemo community currently lacks focus for its issues and ideas. There are a lot of great minds with lots of good ideas but they lack organization and focus. The council will serve to help distill and focus these ideas (from the maemo.org mailing lists, IRC, itT, Bugzilla, etc), bring them to Nokia's attention, and seek to understand Nokia's position on these issues and help to explain it to the rest of the community.
		+
		+	The council will also serve to facilitate a dialog between Nokia and the community on these issues, holding monthly IRC meetings with Nokia representatives to discuss progress on existing issues and raise new issues.
		+
		+	==== Roles of the council ====
		+	* Monthly IRC meeting with Nokia representatives. Open to all, but moderated so only the council members and Nokia representatives can talk.
		+	* Distill maemo community issues, from maemo-* mailing lists, ITT, etc. and raise with Nokia.
		+	* Understand, and help explain, Nokia's decisions and processes to the rest of the community to ensure that dialogue remains helpful, fruitful and progressive.
		+	* Advocate maemo.org, and involvement in its community, to end-users.
		+	* Help manage community involvement, for example [[Maemowiki Action Group]], [[100Days]] and [[2010 Agenda]].
		+	* Act as the definitive mouthpiece for the maemo.org community when questions are asked of the community by, say, Nokia.
		+	* Help direct efforts of Nokia employees working on behalf of the community.
		+
		+	=== Structure ===
		+	The council will be composed of 5 community members to be elected by the community with 1 member as the council chairman. The chairman will be selected by the council after the completion of elections and requires a majority vote of 3 out of 5 council members. If no majority can be reached, the chairman will be the member with the most community votes. Potential candidates must have 100 karma points on maemo.org.
		+
		+	==== Elections ====
		+	{{main\|Community_Council#Election_Process}}
		+
		+	==== Operations ====
		+	* The council will hold monthly IRC meetings with the contacts from the Maemo Software team at Nokia to discuss new issues and progress on existing issues.
		+	* Distill community issues to bring to Nokia's attention.
		+	* Help manage community involvement (e.g. [[Maemowiki Action Group]], [[100Days]] and [[2010 Agenda]])
		+
		+	== Election ==
		+
		+	The first election will take place between 3/9/2008 and 10/9/2008. Voting will be open to all members of the community who have an account on maemo.org for more than 3 months on the 10/9/2008 - that is, on 10/6/2008. Candidatures opened on 14/8/2008, and will close on 2/9/2008 at 23:59 UTC. Candidatures should be sent to maemo-community@maemo.org mentioning maemo username, real name, company affiliation and reasons for wanting to be on the council.
		+
		+	* [[Task:Community Council/Eligible candidates \| Eligible candidates]]
		+	* [[Task:Community Council/Candidate declarations \| Candidate declarations for the inaugural community council elections]]
		+	* [[Task:Community Council/Eligible voters \| Eligible voters]]

Category talk:Users

andre — Thu, 10 May 2012 12:32:57 GMT

Reverted edits by 83.21.235.84 (Talk); changed back to last version by Mrsellout

←Older revision		Revision as of 12:32, 10 May 2012
Line 1:		Line 1:
	I need opinions with this categorization. is users and its subclasses beginners & power users a logical way to divide articles?!? --[[User:ossipena\|ossipena]] 07:15, 10 November 2009 (UTC)		I need opinions with this categorization. is users and its subclasses beginners & power users a logical way to divide articles?!? --[[User:ossipena\|ossipena]] 07:15, 10 November 2009 (UTC)
-
-	~~== 24290 ==~~
-
-	~~<a href=http://czescisamochodowe.wunet.pl/>cz&#281&#347ci samochodowe</a>~~

Documentation

andre — Thu, 10 May 2012 12:32:36 GMT

Reverted edits by 92.255.66.183 (Talk); changed back to last version by 188.129.103.101

←Older revision		Revision as of 12:32, 10 May 2012
Line 1:		Line 1:
	== Maemo 5 ==		== Maemo 5 ==

-	* ~~Documenqweqweqwewqeq fdsfs dfs sdfs dfsdfs dfsd sdfsd~~	+	* Documentation in the wiki:
		+	**[[/Maemo 5 Final SDK\|Maemo 5 Final SDK]]
		+	**[[/Maemo 5 Developer Guide\|Maemo 5 Developer Guide]]
		+	**[[/devtools/maemo5\|Maemo 5 Developer Tools]]
		+	** [https://vcs.maemo.org/svn/maemoexamples/trunk/ Code sample library]
		+	**[[/Maemo 5 Final SDK Installation\|Maemo 5 Final SDK Installation Instructions]]
		+	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Flasher-3.5\|Maemo Flasher-3.5 Tutorial]]
		+	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo SDK Virtual Images\|Maemo SDK Virtual Image Tutorial]]
		+	** [[/Maemo PC Connectivity Tutorial\|Maemo PC Connectivity Tutorial]]
		+	** [[/Maemo For Symbian Developers Guide\|Maemo For Symbian Developers Guide]]
		+	** [[/Maemo Eclipse Tutorial\|Maemo Eclipse Tutorial]]
		+	** [[/Maemo Documentation Guidelines\|Maemo Documentation Guidelines]]
		+	* Further information:
		+	**[http://maemo.org/development/sdks/maemo_5_api_documentation/ Maemo 5 API reference]
		+	** [http://www.forum.nokia.com/info/sw.nokia.com/id/0ea5ec64-2d35-4363-94c0-dd2560c6524b/Get_started_with_Maemo_5.html Get Started with Maemo 5 \| Forum Nokia]
		+	**[[Open development/Maemo_roadmap/Fremantle\|Fremantle roadmap]]
		+	** [[Maemo 5 Clutter performance]]
		+	* Maemo 5 Final SDK release source code - http://repository.maemo.org/pool/maemo5.0/free/
		+
	* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]		* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]
	* [[/devtools\|Developer tools]] for Maemo development		* [[/devtools\|Developer tools]] for Maemo development

Special:Log/delete

andre — Thu, 10 May 2012 12:32:24 GMT

deleted "Talk:Task:Community Council/Eligible voters/": Vandalism

Documentation/devtools/maemo5

andre — Thu, 10 May 2012 12:30:51 GMT

Reverted edits by 92.255.66.183 (Talk); changed back to last version by Andre

←Older revision		Revision as of 12:30, 10 May 2012
Line 3:		Line 3:
	Installation instructions are available [[#Installation\|below]].		Installation instructions are available [[#Installation\|below]].

-	== Categories ==~~чяяяяяяяяяяяяяя~~	+	== Categories ==

	The tools are arranged into different categories so that you can easily see what tools are available for specific kinds of tasks. The same tool can be present in multiple categories.		The tools are arranged into different categories so that you can easily see what tools are available for specific kinds of tasks. The same tool can be present in multiple categories.
Line 19:		Line 19:
	\|}		\|}

-	~~Tunchaka qweqwe~~	+	=== Debugging ===
		+
		+	{\| class="wikitable"
		+	\|+ Debugging tools
		+	\|-
		+	! Tool !! Description
		+	\|-
		+	\| [[Documentation/devtools/maemo5/crash-reporter\|crash-reporter]] \|\| user-friendly graphical user interface for [[Documentation/devtools/maemo5/sp-rich-core\|sp-rich-core]]
		+	\|-
		+	\| [[Documentation/devtools/maemo5/gdb\|gdb]] \|\| GDB is the GNU debugger
		+	\|-
		+	\| [[Documentation/devtools/maemo5/functracer\|functracer]] \|\| an allocation backtrace tool
		+	\|-
		+	\| [[Documentation/devtools/maemo5/functracer-postproc\|functracer-postproc]] \|\| a post-processing tool for functracer output data
		+	\|-
		+	\| [[Documentation/devtools/maemo5/latrace\|latrace]] \|\| display a program's dynamic library calls
		+	\|-
		+	\| [[Documentation/devtools/maemo5/ltrace\|ltrace]] \|\| a library call tracer
		+	\|-
		+	\| [[Documentation/devtools/maemo5/maemo-debug-scripts\|maemo-debug-scripts]] \|\| a set of scripts to help with debugging tasks
		+	\|-
		+	\| [[Documentation/devtools/maemo5/sp-error-visualizer\|sp-error-visualizer]] \|\| displays log messages as banners
		+	\|-
		+	\| [[Documentation/devtools/maemo5/sp-rich-core\|sp-rich-core]] \|\| a core dump data saver
		+	\|-
		+	\| [[Documentation/devtools/maemo5/sp-rich-core-postproc\|sp-rich-core-postproc]] \|\| contains rich-core-extract to examine *.rcore.lzo files created by sp-rich-core
		+	\|-
		+	\| [[Documentation/devtools/maemo5/sp-response-time\|sp-response-time]] \|\| a library for monitoring UI response times
		+	\|-
		+	\| [[Documentation/devtools/maemo5/sp-startup-time\|sp-startup-time]] \|\| a library for calculating application startup times
		+	\|-
		+	\| [[Documentation/devtools/maemo5/strace\|strace]] \|\| a system call tracer
		+	\|-
		+	\| [[Documentation/devtools/maemo5/syslog\|syslog]] \|\| a log message collecting service
		+	\|-
		+	\| [[Documentation/devtools/maemo5/valgrind\|valgrind]] \|\| a suite of tools for debugging and profiling programs
		+	\|-
		+	\| [[Documentation/devtools/maemo5/x11-utils\|x11-utils]] \|\| a collection of X Window System debugging tools; xev, xwininfo, xprop, xlsatoms and xlsclients.
		+	\|}

	=== Miscellaneous ===		=== Miscellaneous ===
Line 153:		Line 191:
	\|-		\|-
	! Tool !! Description		! Tool !! Description
-	\|-~~ячячс~~	+	\|-
	\| [[Documentation/devtools/maemo5/bluez-hcidump\|bluez-hcidump]] \|\| a tool to monitor Bluetooth activity		\| [[Documentation/devtools/maemo5/bluez-hcidump\|bluez-hcidump]] \|\| a tool to monitor Bluetooth activity
	\|-		\|-

Special:Log/delete

andre — Thu, 10 May 2012 12:30:31 GMT

deleted "Talk:Maemo-Barcelona Long Weekend/UX meets Code/": Vandalism

Special:Log/block

andre — Thu, 10 May 2012 12:28:21 GMT

blocked User:nanqimuta with an expiry time of infinite (account creation disabled): Spamming links to external sites

Wiki gardeners

188.143.232.12 — Thu, 10 May 2012 03:48:35 GMT

Other:

←Older revision		Revision as of 03:48, 10 May 2012
Line 70:		Line 70:
	* Put together an categorical index with cover content/article.		* Put together an categorical index with cover content/article.

-	~~=== Other ===~~	+	I don't think so. It's hard to get good facial prnotrpioos when doing a self-portrait. If you hold the camera at a wonky angle, you look weird. . .but it's hard to hold the camera at a good angle when you are just holding the camera out and guessing. But I also did just did focus point focus with piknic, blurring everything not in focus. I suppose it does give it an underwater or dreamlike quality.
-	~~Check maintenance stuff in [[Special:Specialpages]]:~~	+
-	* Create [[Special:Wantedpages\|wanted pages]], even as ''~~stubs~~''	+
-	* Fix [[Special:Doubleredirects\|double redirects]]	+
-	* Add links to ~~[[Special:Lonelypages \| orphan pages]]~~	+
-	* And more...	+

	== Members ==		== Members ==

Task:Community Council

208.23.77.15 — Thu, 10 May 2012 02:07:08 GMT

fxKPtcxiSFCVi

←Older revision		Revision as of 02:07, 10 May 2012
Line 1:		Line 1:
-	~~#redirect [[Community_Council]]~~	+	First all i would like to thank you for the amazing pudorct at our service, finally not only as the n series has blown the expectations of high end technology but as let the consumers all able full modify their mobile they way we want it, just like everyone's desktop is different at home. I am inspired music engineer(21) and i carried the N95-1, my first nokia was when i was very young(canada) nokia 3330,than decided to get a new nokia,the symbian was easy, and i liked snake, so i got the nokia 6600(2004)and i fell in love with the phone and the nokia the brand , promised to buy any mobile from nokia. carried the phone for two years, the camera was amazing back than. Within the love with nokia i started to a lot of research on nokia and the beginning of smart phones. Than the N95-1(2006) was release and became my first n-series.''To me a classic phone'' Unfortunately i do carry the phone with me , although its in my room it is broken(my friend dropped it , it was the first time the phone was damage. I decided not to buy a cellphone until i see the next n series made a ''MOBILE DEVICE'', to be honest the n958gb and the n96 did not appeal to me.I wanted something different,like the n93 to the n95. Now this summer(2009) was remarkable, with the announce of the n97, defiantly my next phone.(actually yesterday was the first time i saw the phone in Canada, a women from the mid-east had the white one) AMAZING!!. since the release i've been planning to save to buy it. Until later august I heard about the N900; and believe me i spent hours reading the specs of this phone, and i am blown. It is the mobile device that i have dreamed of. I know I've been typing a lot, i wanted to contact nokian900 but i couldn't find a canadian outsource for a question and inquiry. I googled the VP of the pudorct and found your blog......I am not sure if it was announced or confirmed, but to release of the phone. ''Will the N900 be release only by 3G HSDPA 1700 / 2100 / 900 ?Will the GSM 850 / 900 / 1800 / 1900 users (such as I,AT&T/Rogers/Fido) be able to use the N900? In request the phone doesn't have to be sold in countries such as the n95-1. Mine was ordered from the UK. It leaves confused if the phone will be release in gsm capability. (labrecstudios@gmail.com)awaiting a response if possible.Thank you
-		+
-	~~{{Template:100Days agenda}}~~	+
-	~~{{task\|completed}}~~	+
-		+
-	~~== Objective ==~~	+
-	~~A process~~ for ~~electing a small "Community Council" should be created and elections held.~~	+
-		+
-	~~[[User:qgil\|Quim Gil]] is currently responsible for managing~~ the ~~Maemo community on behalf of Nokia. But who is~~ the ~~community? Getting consensus~~ of ~~hundreds of disparate people through mailing lists and wiki-edits means~~ the ~~person who shouts loudest wins.~~	+
-		+
-	~~Therefore —inspired by Debian~~'s ~~Project Leader concept— during~~ the ~~next [[100Days]]~~, a ~~process for electing a small "Community Council" should be created~~ and ~~elections held.~~	+
-		+
-	~~== The Community council ==~~	+
-		+
-	~~This is~~ the ~~proposal for a Community Council based on~~ the ~~[[Task:Community Council\|proposal]] from~~ the ~~[[100Days\|100 Days brainstorm]]. It is a work in progress to be thrashed out over~~ the ~~next 30 days~~, ~~so these ideas are fluid and will change frequently~~. ~~Please see~~ the ~~[[Talk:Community_Council\|talk page]]~~ for ~~discussion~~.	+
-		+
-	~~=== Purpose ===~~	+
-	~~The maemo community currently lacks focus for its issues and ideas. There are~~ a lot of ~~great minds with lots of good ideas but they lack organization~~ and ~~focus. The council will serve to help distill and focus these ideas (from~~ the ~~maemo~~.~~org mailing lists, IRC, itT, Bugzilla, etc~~)~~, bring them to Nokia~~'~~s attention~~, ~~and seek to understand Nokia's position on these issues and help to explain~~ it to the ~~rest of~~ the ~~community~~.	+
-		+
-	~~The council will also serve~~ to ~~facilitate~~ a ~~dialog between Nokia and~~ the ~~community on these issues~~, ~~holding monthly IRC meetings with Nokia representatives~~ to ~~discuss progress on existing issues~~ and ~~raise new issues.~~	+
-		+
-	~~==== Roles of~~ the ~~council ====~~	+
-	* Monthly IRC meeting with Nokia representatives. ~~Open to all~~, ~~but moderated so only~~ the ~~council members and Nokia representatives can talk~~.	+
-	* Distill maemo community issues, ~~from maemo-* mailing lists, ITT, etc. and raise~~ with ~~Nokia.~~	+
-	* Understand, and help explain, Nokia's decisions and processes to the ~~rest~~ of the ~~community to ensure that dialogue remains helpful~~, ~~fruitful and progressive~~.	+
-	* Advocate maemo.org, and involvement in ~~its community~~, ~~to end~~-~~users.~~	+
-	* Help manage community involvement, for example [[Maemowiki Action Group]], [[100Days]] and [[2010 Agenda]].	+
-	* Act as the ~~definitive mouthpiece for the maemo~~.~~org community when questions are asked of~~ the ~~community by, say, Nokia.~~	+
-	* Help direct efforts of Nokia employees working on behalf of the community.	+
-		+
-	~~=== Structure ===~~	+
-	~~The council will be composed of 5 community members~~ to ~~be elected by the community with 1 member as the council chairman~~. ~~The chairman will be selected by~~ the ~~council after~~ the ~~completion~~ of ~~elections~~ and ~~requires a majority vote of 3 out of 5 council members~~. ~~If no majority can be reached,~~ the ~~chairman will be the member with the most community votes. Potential candidates must~~ have ~~100 karma points on maemo~~.~~org~~.	+
-		+
-	~~==== Elections ====~~	+
-	~~{{main\|Community_Council#Election_Process}}~~	+
-		+
-	~~==== Operations ====~~	+
-	* The council will hold monthly IRC meetings with the ~~contacts from~~ the ~~Maemo Software team at Nokia to discuss new issues~~ and ~~progress on existing issues~~.	+
-	* Distill community issues to bring to Nokia's attention.	+
-	* Help manage community involvement (e.g. ~~[[Maemowiki Action Group]]~~, ~~[[100Days]] and [[2010 Agenda]])~~	+
-		+
-	~~== Election ==~~	+
-		+
-	~~The first election will take place between 3/9/2008 and 10/9/2008. Voting will be open~~ to ~~all members~~ of the ~~community who have an account on maemo~~.~~org for more than 3 months on~~ the 10/9/~~2008 - that is, on 10~~/6/~~2008. Candidatures opened on 14~~/~~8/2008~~, ~~and will close on 2~~/9/~~2008 at 23:59 UTC. Candidatures should~~ be ~~sent~~ to ~~maemo-community@maemo.org mentioning maemo username, real name, company affiliation and reasons for wanting~~ to be on the ~~council~~.	+
-		+
-	* [[Task:Community Council/Eligible candidates \| Eligible candidates]]	+
-	* [[Task:Community Council/Candidate declarations \| Candidate declarations for the ~~inaugural community council elections]]~~	+
-	* [[Task:Community Council/Eligible voters \| Eligible voters]]	+

Task:100Days

joerg_rw — Thu, 10 May 2012 01:09:13 GMT

Undo revision 47462 by 81.0.157.200 (Talk) vandalism

←Older revision		Revision as of 01:09, 10 May 2012
Line 1:		Line 1:
-	~~Sdraveite!Pisha Vi ot Linz Avstria~~.~~Mnogo bih iskala da se abaronin sa spisanieto vi~~.~~Moga li da napravja tova online ili samo v bankata~~?~~Bih se radvala na otgovora Vi~~,~~sa koeto predvaritelno blagodarja!Posdrav Velizara Jonjic~~	+	{{task\|completed}}
		+
		+	The '''100 Days Action Plan''' brainstorm for maemo.org has covered its first objective and now the list of proposal is closed. Now the help is needed in the committed tasks listed below. The strategic brainstorm continues at [[2010_Agenda\|maemo.org 2010]].
		+
		+	=Community-led action plan process=
		+	Planned sprints:
		+	* Sprint 1. Started on 2008/06/10. [https://garage.maemo.org/plugins/wiki/index.php?June2008Sprint&id=106&type=g Tasks committed]. IRC review meeting on 2008/06/30.
		+	* [[100Days/Sprint2\|Sprint 2]]. IRC review meeting on 2008/07/22.
		+	* [[100Days/Sprint3\|Sprint 3]]. IRC review meeting on 2008/08/12.
		+	* [[100Days/Sprint4\|Sprint 4]]. IRC review meeting on 2008/09/02.
		+	* [[100Days/Sprint5\|Sprint 5]]. Life/IRC review meeting at [[Maemo Summit 2008\|maemo summit]] on 2008/09/19.
		+
		+	=Agreed tasks=
		+
		+	== Defining maemo ==
		+	{{main\|Task:Defining maemo}}
		+	Crystal-clear definitions of maemo, maemo.org, OS2008 and so on.
		+
		+	[[User:Qgil\|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.
		+
		+	==Fast server==
		+	{{main\|Task:Fast Server}}
		+	Browsing and downloading from maemo.org should be simply fast. No excuses.
		+
		+	Nemein will work on this task. More details to come.
		+
		+	== Mapping openness ==
		+	{{main\|Task:Mapping openness}}
		+	* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.
		+
		+	[[User:Qgil\|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.
		+
		+	== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==
		+	{{main\|Task:ITt Collaboration}}
		+	maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org [[karma]].
		+
		+	Nemein will handle this task. Henri is the contact. More to come soon.
		+
		+	== Consolidation of extras ==
		+	{{main\|Task:Consolidation of Extras}}
		+	The Extras repository needs to become the single reference for developers willing to reach end users at large.
		+
		+	Niels to coordinate this. More details to come.
		+
		+	== Improving maemo.org ==
		+	{{main\|Task:Improving maemo.org}}
		+	maemo.org needs improvements in usability, content, format and style.
		+
		+	Dave to coordinate this task. More details to come up later.
		+
		+	Nemein will help on this, but there needs to be a clear plan first to see who pushes what.
		+
		+	=== Content cleanup ===
		+	{{main\|Task:Content Cleanup}}
		+	Dress up the most important content, dump what is not relevant, handle the rest via the wiki.
		+
		+	== Roadmap for the Maemo platform ==
		+	{{main\|Open development/Maemo roadmap}}
		+	A Maemo roadmap for developers, disclosing information about open source components and developer libraries.
		+
		+	[[User:Qgil\|qgil]] coordinates this task. Planned for the Sprint 5 (September) but you can start helping out now.
		+
		+	== Community Council ==
		+	{{main\|Community Council}}
		+	A process for electing a small "Community Council" should be created and elections held.
		+
		+	This task needs a coordinator.
		+	:''Jaffa, lardman, or myself are probably the ones to push this. Jaffa's currently on vacation, so I'll get together with lardman tomorrow to start getting the ball rolling on this. —[[User:generalantilles\|GeneralAntilles]] 01:01, 12 June 2008 (UTC)''
		+
		+	== More pre-agreed tasks ==
		+	Help planning them further and moving them to an own page.
		+
		+	* [[Task:Using garage.maemo.org]] - Ferenc
		+	* Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-community alongside existing mailing lists for overall discussions about maemo.org sites and community topics in general. Ferenc . '''[http://lists.maemo.org/mailman//listinfo/maemo-community DONE]'''.
		+
		+
		+	[[Category:Community]]
		+	[[Category:maemo.org]]

Task:100Days

81.0.157.200 — Thu, 10 May 2012 01:00:49 GMT

Undo revision 45763 by 70.135.114.247 (Talk)

←Older revision		Revision as of 01:00, 10 May 2012
Line 1:		Line 1:
-	~~{{task\|completed}}~~	+	Sdraveite!Pisha Vi ot Linz Avstria.Mnogo bih iskala da se abaronin sa spisanieto vi.Moga li da napravja tova online ili samo v bankata?Bih se radvala na otgovora Vi,sa koeto predvaritelno blagodarja!Posdrav Velizara Jonjic
-		+
-	~~The '''100 Days Action Plan''' brainstorm for maemo~~.~~org has covered its first objective and now the list of proposal is closed~~. ~~Now the help is needed in the committed tasks listed below. The strategic brainstorm continues at [[2010_Agenda\|maemo.org 2010]].~~	+
-		+
-	~~=Community-led action plan process=~~	+
-	~~Planned sprints:~~	+
-	* Sprint 1. Started on 2008/06/10. [https://garage.maemo.org/plugins/wiki/index.php?~~June2008Sprint&id=106&type=g Tasks committed]. IRC review meeting on 2008/06/30.~~	+
-	* [[100Days/Sprint2\|Sprint 2]]. IRC review meeting on 2008/07/22.	+
-	* [[100Days/Sprint3\|Sprint 3]]. IRC review meeting on 2008/08/12.	+
-	* [[100Days/Sprint4\|Sprint 4]]. IRC review meeting on 2008/09/02.	+
-	* [[100Days/Sprint5\|Sprint 5]]. Life/IRC review meeting at [[Maemo Summit 2008\|maemo summit]] on 2008/09/19.	+
-		+
-	~~=Agreed tasks=~~	+
-		+
-	~~== Defining maemo ==~~	+
-	~~{{main\|Task:Defining maemo}}~~	+
-	~~Crystal-clear definitions of maemo~~, ~~maemo.org, OS2008 and so on.~~	+
-		+
-	~~[[User:Qgil\|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.~~	+
-		+
-	~~==Fast server==~~	+
-	~~{{main\|Task:Fast Server}}~~	+
-	~~Browsing and downloading from maemo.org should be simply fast. No excuses.~~	+
-		+
-	~~Nemein will work on this task. More details to come.~~	+
-		+
-	~~== Mapping openness ==~~	+
-	~~{{main\|Task:Mapping openness}}~~	+
-	* Identifying closed-source components and the reasons why, addressing the community's concerns over openness.	+
-		+
-	~~[[User:Qgil\|qgil]] coordinates this task. Not included in the Sprint 1 (June) but you can start helping out now.~~	+
-		+
-	~~== [http://www.internettablettalk.com Internet Tablet Talk] Collaboration ==~~	+
-	~~{{main\|Task:ITt Collaboration}}~~	+
-	~~maemo.org and ITt services should integrate much better i.e. maemo.org Downloads syndicated in ITt and ITt users getting maemo.org [[karma]].~~	+
-		+
-	~~Nemein will handle this task. Henri is the contact. More to come soon.~~	+
-		+
-	~~== Consolidation of extras ==~~	+
-	~~{{main\|Task:Consolidation of Extras}}~~	+
-	~~The Extras repository needs to become the single reference for developers willing to reach end users at large.~~	+
-		+
-	~~Niels to coordinate this. More details to come.~~	+
-		+
-	~~== Improving maemo.org ==~~	+
-	~~{{main\|Task:Improving maemo.org}}~~	+
-	~~maemo.org needs improvements in usability, content, format and style.~~	+
-		+
-	~~Dave to coordinate this task. More details to come up later.~~	+
-		+
-	~~Nemein will help on this, but there needs to be a clear plan first to see who pushes what.~~	+
-		+
-	~~=== Content cleanup ===~~	+
-	~~{{main\|Task:Content Cleanup}}~~	+
-	~~Dress up the most important content, dump what is not relevant, handle the rest via the wiki.~~	+
-		+
-	~~== Roadmap for the Maemo platform ==~~	+
-	~~{{main\|Open development/Maemo roadmap}}~~	+
-	~~A Maemo roadmap for developers, disclosing information about open source components and developer libraries.~~	+
-		+
-	~~[[User:Qgil\|qgil]] coordinates this task. Planned for the Sprint 5 (September) but you can start helping out now.~~	+
-		+
-	~~== Community Council ==~~	+
-	~~{{main\|Community Council}}~~	+
-	~~A process for electing a small "Community Council" should be created and elections held.~~	+
-		+
-	~~This task needs a coordinator.~~	+
-	:''Jaffa, lardman, or myself are probably the ones to push this. Jaffa's currently on vacation, so I'll get together with lardman tomorrow to start getting the ball rolling on this. —[[User:generalantilles\|GeneralAntilles]] 01:01, 12 June 2008 (UTC)''	+
-		+
-	~~== More pre-agreed tasks ==~~	+
-	~~Help planning them further and moving them to an own page.~~	+
-		+
-	* [[Task:Using garage.maemo.org]] - Ferenc	+
-	* Close misnamed (and now misused) maemo2midgard-discuss mailing list and create maemo-community alongside existing mailing lists for overall discussions about maemo.org sites and community topics in general. Ferenc . '''[http://lists.maemo.org/mailman//listinfo/maemo-community DONE]'''.	+
-		+
-		+
-	~~[[Category:Community]]~~	+
-	~~[[Category:maemo.org]]~~	+

Category talk:Users

83.21.235.84 — Wed, 09 May 2012 22:27:22 GMT

24290: new section

←Older revision		Revision as of 22:27, 9 May 2012
Line 1:		Line 1:
	I need opinions with this categorization. is users and its subclasses beginners & power users a logical way to divide articles?!? --[[User:ossipena\|ossipena]] 07:15, 10 November 2009 (UTC)		I need opinions with this categorization. is users and its subclasses beginners & power users a logical way to divide articles?!? --[[User:ossipena\|ossipena]] 07:15, 10 November 2009 (UTC)
		+
		+	== 24290 ==
		+
		+	<a href=http://czescisamochodowe.wunet.pl/>cz&#281&#347ci samochodowe</a>

Documentation

92.255.66.183 — Wed, 09 May 2012 13:58:17 GMT

Maemo 5:

←Older revision		Revision as of 13:58, 9 May 2012
Line 1:		Line 1:
	== Maemo 5 ==		== Maemo 5 ==

-	* ~~Documentation in the wiki:~~	+	* Documenqweqweqwewqeq fdsfs dfs sdfs dfsdfs dfsd sdfsd
-	**[[/Maemo 5 Final SDK\|Maemo 5 Final SDK]]	+
-	**[[/Maemo 5 Developer Guide\|Maemo 5 Developer Guide]]	+
-	**[[/devtools/maemo5\|Maemo 5 Developer Tools]]	+
-	** [https://vcs.maemo.org/svn/maemoexamples/trunk/ Code sample library]	+
-	**[[/Maemo 5 Final SDK Installation\|Maemo 5 Final SDK Installation Instructions]]	+
-	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Flasher-3.5\|Maemo Flasher-3.5 Tutorial]]	+
-	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo SDK Virtual Images\|Maemo SDK Virtual Image Tutorial]]	+
-	** [[/Maemo PC Connectivity Tutorial\|Maemo PC Connectivity Tutorial]]	+
-	** [[/Maemo For Symbian Developers Guide\|Maemo For Symbian Developers Guide]]	+
-	** [[/Maemo Eclipse Tutorial\|Maemo Eclipse Tutorial]]	+
-	** [[/Maemo Documentation Guidelines\|Maemo Documentation Guidelines]]	+
-	* Further information:	+
-	**[http://maemo.org/development/sdks/maemo_5_api_documentation/ Maemo 5 API reference]	+
-	** [http://www.forum.nokia.com/info/sw.nokia.com/id/0ea5ec64-2d35-4363-94c0-dd2560c6524b/Get_started_with_Maemo_5.html Get Started with Maemo 5 \| Forum Nokia]	+
-	**[[Open development/Maemo_roadmap/Fremantle\|Fremantle roadmap]]	+
-	** [[Maemo 5 Clutter performance]]	+
-	* Maemo 5 Final SDK release source code - http://repository.maemo.org/pool/maemo5.0/free/	+
-		+
	* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]		* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]
	* [[/devtools\|Developer tools]] for Maemo development		* [[/devtools\|Developer tools]] for Maemo development

←Older revision		Revision as of 12:32, 10 May 2012
Line 1:		Line 1:
	== Maemo 5 ==		== Maemo 5 ==

-	* ~~Documenqweqweqwewqeq fdsfs dfs sdfs dfsdfs dfsd sdfsd~~	+	* Documentation in the wiki:
		+	**[[/Maemo 5 Final SDK\|Maemo 5 Final SDK]]
		+	**[[/Maemo 5 Developer Guide\|Maemo 5 Developer Guide]]
		+	**[[/devtools/maemo5\|Maemo 5 Developer Tools]]
		+	** [https://vcs.maemo.org/svn/maemoexamples/trunk/ Code sample library]
		+	**[[/Maemo 5 Final SDK Installation\|Maemo 5 Final SDK Installation Instructions]]
		+	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Flasher-3.5\|Maemo Flasher-3.5 Tutorial]]
		+	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo SDK Virtual Images\|Maemo SDK Virtual Image Tutorial]]
		+	** [[/Maemo PC Connectivity Tutorial\|Maemo PC Connectivity Tutorial]]
		+	** [[/Maemo For Symbian Developers Guide\|Maemo For Symbian Developers Guide]]
		+	** [[/Maemo Eclipse Tutorial\|Maemo Eclipse Tutorial]]
		+	** [[/Maemo Documentation Guidelines\|Maemo Documentation Guidelines]]
		+	* Further information:
		+	**[http://maemo.org/development/sdks/maemo_5_api_documentation/ Maemo 5 API reference]
		+	** [http://www.forum.nokia.com/info/sw.nokia.com/id/0ea5ec64-2d35-4363-94c0-dd2560c6524b/Get_started_with_Maemo_5.html Get Started with Maemo 5 \| Forum Nokia]
		+	**[[Open development/Maemo_roadmap/Fremantle\|Fremantle roadmap]]
		+	** [[Maemo 5 Clutter performance]]
		+	* Maemo 5 Final SDK release source code - http://repository.maemo.org/pool/maemo5.0/free/
		+
	* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]		* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]
	* [[/devtools\|Developer tools]] for Maemo development		* [[/devtools\|Developer tools]] for Maemo development

←Older revision		Revision as of 13:58, 9 May 2012
Line 1:		Line 1:
	== Maemo 5 ==		== Maemo 5 ==

-	* ~~Documentation in the wiki:~~	+	* Documenqweqweqwewqeq fdsfs dfs sdfs dfsdfs dfsd sdfsd
-	**[[/Maemo 5 Final SDK\|Maemo 5 Final SDK]]	+
-	**[[/Maemo 5 Developer Guide\|Maemo 5 Developer Guide]]	+
-	**[[/devtools/maemo5\|Maemo 5 Developer Tools]]	+
-	** [https://vcs.maemo.org/svn/maemoexamples/trunk/ Code sample library]	+
-	**[[/Maemo 5 Final SDK Installation\|Maemo 5 Final SDK Installation Instructions]]	+
-	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo Flasher-3.5\|Maemo Flasher-3.5 Tutorial]]	+
-	** [[Documentation/Maemo 5 Developer Guide/Development Environment/Maemo SDK Virtual Images\|Maemo SDK Virtual Image Tutorial]]	+
-	** [[/Maemo PC Connectivity Tutorial\|Maemo PC Connectivity Tutorial]]	+
-	** [[/Maemo For Symbian Developers Guide\|Maemo For Symbian Developers Guide]]	+
-	** [[/Maemo Eclipse Tutorial\|Maemo Eclipse Tutorial]]	+
-	** [[/Maemo Documentation Guidelines\|Maemo Documentation Guidelines]]	+
-	* Further information:	+
-	**[http://maemo.org/development/sdks/maemo_5_api_documentation/ Maemo 5 API reference]	+
-	** [http://www.forum.nokia.com/info/sw.nokia.com/id/0ea5ec64-2d35-4363-94c0-dd2560c6524b/Get_started_with_Maemo_5.html Get Started with Maemo 5 \| Forum Nokia]	+
-	**[[Open development/Maemo_roadmap/Fremantle\|Fremantle roadmap]]	+
-	** [[Maemo 5 Clutter performance]]	+
-	* Maemo 5 Final SDK release source code - http://repository.maemo.org/pool/maemo5.0/free/	+
-		+
	* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]		* [[Legacy Maemo 5 Documentation]] includes the superseded [[Legacy_Maemo_5_Documentation/Human_Interface_Guidelines\|Human Interface Guidelines]] and the [[Legacy_Maemo_5_Documentation/Graphical_UI_Tutorial\|Graphical UI Tutorial]]
	* [[/devtools\|Developer tools]] for Maemo development		* [[/devtools\|Developer tools]] for Maemo development

←Older revision		Revision as of 22:30, 12 May 2012
Line 1:		Line 1:
-	'''Please Note: Update for 0.9.16++ is in progress for this page. In particular section "Usage" still needs updates...'''. -- [[User:yablacky\|yablacky]] 00:20, ~~24 January~~ 2012 (UTC)	+	'''Please Note: Update for 0.9.18++ is in progress for this page. In particular section "Usage" still needs updates...'''. --[[User:yablacky\|yablacky]] 21:00, 12 May 2012 (UTC)

	==Introduction==		==Introduction==
Line 207:		Line 207:

	===List of known sms commands===		===List of known sms commands===
-	* 'COM_CHECK': Command to ask for help.	+
		+	These settings define text to trigger the corresponding command. You're encouraged to set them to words which are easy to remember in your language. The text may be set to the empty string which completely disables the command. It's not allowed to set two commands to the same text (except empty string).
		+
		+	A SMS message actually sent must consist of the command text prefixed/suffixed with text defined by [[#Prefix.2Fsuffix_for_all_SMS_command_strings \| SMS_COMPREFIX/SMS_COMSUFFIX]] settings respectively.
		+
		+	* 'COM_CHECK': Command to ask for help.<br/>You may forget all other commands but should keep this and the prefix/suffix in mind.
	* 'COM_REBOOT': Command to reboot the phone.		* 'COM_REBOOT': Command to reboot the phone.
	* 'COM_POWEROFF': Command to shutdown the phone.		* 'COM_POWEROFF': Command to shutdown the phone.
Line 217:		Line 222:
	* 'COM_CALL': Command to start an outgoing call.		* 'COM_CALL': Command to start an outgoing call.
	* 'COM_LOCK': Command to lock the phone.		* 'COM_LOCK': Command to lock the phone.
-	* 'COM_UNLOCK': Command to unlock the phone ~~(encrypted)~~.	+	* 'COM_UNLOCK': Command to unlock the phone.
	* 'COM_TRACKON': Command to start GPS tracking.		* 'COM_TRACKON': Command to start GPS tracking.
	* 'COM_TRACKOFF': Command to stop GPS tracking.		* 'COM_TRACKOFF': Command to stop GPS tracking.
-	* 'COM_CUSTOM': Command to run predefined user script.	+	* 'COM_CUSTOM': Command to run a predefined user script. The script runs asynchronously until it terminates itself.<br>Version 0.9.18 supports definition of command text that accepts one or more arbitrary text parts. This parts are extracted and passed to the user script. This indirectly adds support for multiple, unlimited number of user scripts. See below for details.
-	* 'COM_CUSTOMLOG': Command to ask for ~~user script~~ output.	+	* 'COM_CUSTOMLOG': Command to ask for output of last COM_CUSTOM command.
-	* 'COM_SHELL': ~~Command to execute that~~ shell command. ~~Returns~~ output as notification.	+	* 'COM_SHELL': The command text must be a unix shell command. It is directly passed to a unix shell for execution. In contrast to COM_CUSTOM, the command does not execute in background and its output is immediately returned as notification SMS and/or EMAIL.<br>Version 0.9.18 supports definition of command text that accepts one or more arbitrary text parts. This allows to modify the shell command on a per sms-basis. See below for details.
	* 'COM_ALARM': Command to play once the predefined <tt>alarm.wav</tt> sound file. Alarm duration depends on <tt>alarm.wav</tt> content; there is no command to stop playing the alarm sound.		* 'COM_ALARM': Command to play once the predefined <tt>alarm.wav</tt> sound file. Alarm duration depends on <tt>alarm.wav</tt> content; there is no command to stop playing the alarm sound.
	* 'COM_RESTART': Command to restart the daemon.		* 'COM_RESTART': Command to restart the daemon.
-	* 'COM_LOG': Command to ask for application log ~~(encrypted)~~.	+	* 'COM_LOG': Command to ask for application log.

	===Prefix/suffix for all SMS command strings===		===Prefix/suffix for all SMS command strings===
Line 845:		Line 850:
	Feel free to add requests below.		Feel free to add requests below.

-	* Add a provision for SMS reception without the UI being notified (so that SMSCON control is silent). INFO: Remote command server (CHECKHOST) already offers silent control.	+	* Add a provision for SMS reception without the UI being notified so that SMSCON control is silent.<br/>INFO: Remote command server (CHECKHOST) already offers silent control.
-	* ~~saving~~ all <code>smscon_config</code> user variables in gconf database. No need for <code>smscon_config</code> file anymore. (WONT IMPLEMENT)	+	* <del>Saving all <code>smscon_config</code> user variables in gconf database. No need for <code>smscon_config</code> file anymore.</del><br/>(WONT IMPLEMENT)
-	* ~~add~~ setting for user's country mobile number prefix.	+	* <del>Add setting for user's country mobile number prefix.</del><br/>(WONT IMPLEMENT: There is only one place where to specify the prefix anyway; namely the MASTERNUMBER)
-	* ~~add~~ setting for alternative number (where alternative is a number sent a command and does not match the default) and option to choose where reply should be send, i.e. default number, alternative or both. Default number should not be replaced. ~~INFO~~: Since 0.9.x there is a MASTERNUMBER concept. This is a default number that is never replaced	+	* <del>Add setting for alternative number (where alternative is a number sent a command and does not match the default) and </del>option to choose where reply should be send, i.e. default number, alternative or both. <del>Default number should not be replaced.</del><br/>(PARTLY IMPLEMENTED: Since 0.9.x there is a MASTERNUMBER concept. This is a default number that is never replaced.)
-	* ~~add~~ setting to choose the default internet connection (WLAN, GPRS, or ANY).	+	* Add setting to choose the default internet connection (WLAN, GPRS, or ANY).
-	* ~~when~~ the "Camera" command is sent, the process should wait for keyboard action to capture a picture and send the mail. In that way, there will be more chances to get better face portrait of the "new" user.	+	* When the "Camera" command is sent, the process should wait for keyboard action to capture a picture and send the mail. In that way, there will be more chances to get better face portrait of the "new" user.
-	* Add the ability to run more than one custom command.	+	* <del>Add the ability to run more than one custom command.</del><br/>(IMPLEMENTED SINCE 0.9.18).
-	* Application must be included in the ROM itself so that it cannot be removed. (CAN'T BE IMPLEMENTED)	+	* <del>Application must be included in the ROM itself so that it cannot be removed.</del><br/>(CAN'T BE IMPLEMENTED)
-	* Add a password so that no one else but the legitimate user can send an SMS to the phone and see where the phone is. (~~INFO~~: ~~Use the prefix/suffix option in smscon editor application or set~~ SMS_COMPREFIX/SMS_COMSUFFIX ~~options via command-line~~)	+	* <del>Add a password so that no one else but the legitimate user can send an SMS to the phone and see where the phone is.</del><br/>(IMPLEMENTED since 0.9.x: The SMS_COMPREFIX/SMS_COMSUFFIX settings supply the desired password functionality)
	* Auto remove the received SMS from conversations.		* Auto remove the received SMS from conversations.
	* Disable PhoneSpeakerSwitch on receipt of 'call' command.		* Disable PhoneSpeakerSwitch on receipt of 'call' command.
-	* EmailCON: check an specified email inbox, reading it with the program itself and not the built in default mail prog, at a given frequency, paying attention to commands written in the subject and/or body, accepting all the commands that are accepted via SMS. (WONT IMPLEMENT)	+	* <del>EmailCON: check an specified email inbox, reading it with the program itself and not the built in default mail prog, at a given frequency, paying attention to commands written in the subject and/or body, accepting all the commands that are accepted via SMS.</del><br/>(WONT IMPLEMENT)
-	* Improve handling of front camera to reduce the odds of crappy or plain blank black pictures being taken. (CAN'T BE IMPLEMENTED)	+	* <del>Improve handling of front camera to reduce the odds of crappy or plain blank black pictures being taken.</del><br/>(CAN'T BE IMPLEMENTED)
-	* When in "stolen" mode, replace the front cam "recording" LED pattern with a on-lighting pattern for stealthiness.	+	* When in "stolen" mode, replace the front cam "recording" LED pattern with a on-lighting pattern for stealthiness.<br/>(NOTE: The is no 'stolen mode')
	* Email, or post online somewhere you choose, any new photography taken with the main camera, geotagging whenever possible, preferably without showing any signs it's happening (if possible with an option to re-dimension the picture before sending).		* Email, or post online somewhere you choose, any new photography taken with the main camera, geotagging whenever possible, preferably without showing any signs it's happening (if possible with an option to re-dimension the picture before sending).
	* There should be an option to send email as text or as multipart html and text.		* There should be an option to send email as text or as multipart html and text.