Customizing maemo for power users - Revision history

imported_>ossipena: Redirecting to Customizing Maemo

2010-01-26T08:03:29Z

← Older revision	Revision as of 08:03, 26 January 2010
Line 1:	Line 1:
		#REDIRECT [[Customizing Maemo]]

213.28.7.254: Removing all content from page

2010-01-26T08:01:10Z

Removing all content from page

← Older revision		Revision as of 08:01, 26 January 2010
Line 1:		Line 1:
	~~'''THIS PAGE WILL BE REMOVED! THIS WILL BE REDIRECTED TO [[Customizing Maemo]]'''~~

	~~led article has moved to [[LED patterns]]~~

	~~[[Category:Power users]]~~

imported_>f2thak: Replacing page with ''''THIS PAGE WILL BE REMOVED! THIS WILL BE REDIRECTED TO Customizing Maemo''' led article has moved to LED patterns Category:Power users'

2010-01-20T13:30:51Z

Replacing page with ''''THIS PAGE WILL BE REMOVED! THIS WILL BE REDIRECTED TO Customizing Maemo''' led article has moved to LED patterns Category:Power users'

← Older revision		Revision as of 13:30, 20 January 2010
Line 1:		Line 1:



	'''THIS PAGE WILL BE REMOVED! THIS WILL BE REDIRECTED TO [[Customizing Maemo]]'''		'''THIS PAGE WILL BE REMOVED! THIS WILL BE REDIRECTED TO [[Customizing Maemo]]'''

Line 7:		Line 4:

	[[Category:Power users]]		[[Category:Power users]]



	~~== Remote WLAN Access To Root / System Files ==~~
	~~for easy file manipulation~~

	~~(please note: all these apps and steps may not be necesarry but I got it working like this)~~

	~~this help file assumes you know the risks and how to at least download and install apps from the extra repos..~~


	~~i think you also need~~
	~~diablo_kernel_usbnet_patch_windows_v0.4~~
	~~available here:~~
	~~https://garage.maemo.org/frs/?group_id=801~~




	~~To get remote access to N900 thru wifi:~~
	~~---------------------------------------~~

	~~1. install the following apps/software~~



	~~n900 end: (all these apps are in extras repos)~~

	~~ssh server/client - this will request password when installing (WRITE DOWN / TAKE NOTE OF PASSWORD !!)~~
	~~rootsh~~
	~~maemo-pc-connectivity~~
	~~mad developer~~


	~~for pc end:~~

	~~winscp~~
	~~http://winscp.net/download/winscp425setup.exe~~



	~~2. goto 'settings' > connectivity > 'pc-connectivity-manager'~~

	~~3. click "advanced" button > select environment 'default'~~

	~~4. select connectiont type 'usb'~~

	~~5. options > select 'network' from drop-down list~~

	~~6. select connectiont type 'internet' > options > connect using 'WLAN'~~

	~~7. Save and apply~~

	~~8. open "mad developer" > manage usb > 'gfile_storage' > close~~

	~~9. open winscp and put the WLAN ip address shown in mad developer in the 'host name'~~

	~~10. user name "root", password "(password created during ssh install)"~~

	~~11. save > login~~

	~~12. you should now have access!!~~

imported_>ossipena at 11:34, 20 January 2010

2010-01-20T11:34:34Z

← Older revision		Revision as of 11:34, 20 January 2010
Line 1:		Line 1:
	~~'''Please remember, that doing anything instructed here is potentially dangerous. Please see [[General precautions]] for further information.'''~~


	~~== Modifying led colours and patterns ==~~

	~~There are multiple triggers for led blinking. All can be found in~~		'''THIS PAGE WILL BE REMOVED! THIS WILL BE REDIRECTED TO [[Customizing Maemo]]'''
	~~/etc/mce/mce.ini~~

	~~The file can be edited with any text editor that can be run with~~ [[~~Root access~~]] ~~and open the file. So GUI - editors probably don~~'~~t work, but terminal versions all will.~~

	~~=== Step by step instructions ===~~

	* Open terminal
	* Gain [[Root access]]
	* Make a backup (not necessary!) from original mce.ini -file, for example:
	~~cp /etc/mce/mce.ini /etc/mce/mce.ini_old~~
	* Open /etc/mce/mce.ini with a text editor (nano, vim, leafpad...)
	* Search for a line:
	~~[LEDPatternLystiRX51]~~
	* Make your changes to the lines below
	* Save
	* Restart mce -process. Either reboot or type to terminal:
	~~initctl stop mce; sleep 2; initctl start mce~~

	~~=== Constructing own patterns ===~~

	~~The mce.ini -file has description header before pattern defining start. Here are the same instructions with longer explanations.~~

	~~Example string:~~
	~~PatternCommunicationCall=30;1;0;r;9d80400002ff03ff02ff03ff71080000;9d800000~~


	~~Dissection:~~
	~~{\| class="wikitable" border="0"~~
	\|-
	~~\| PatternCommunicationCall=~~
	~~\| 30;~~
	~~\| 1;~~
	~~\| 0;~~
	~~\| r;~~
	~~\| 9d80400002ff03ff02ff03ff71080000;~~
	~~\| 9d800000~~
	\|-
	~~\| Alert pattern~~
	~~\| priority~~
	~~\| screen on~~
	~~\| timeout~~
	~~\| led mapping~~
	~~\| Engine 1 pattern~~
	~~\| Engine 2 pattern~~
	\|}


	~~==== Priority ====~~
	~~This defines that which blinking pattern is the strongest. So if multiple alerts are enabled, which pattern will be shown. Values from 0 to 255 are accepted.~~

	~~==== Screen on ====~~
	~~from mce.ini:~~
	~~0 only show pattern when the display is off~~
	~~1 show pattern even when the display is on~~
	~~2 only show pattern when the display is off, including acting dead~~
	~~3 show pattern even when the display is on, including acting dead~~
	~~4 only show pattern if the display is off, or if in acting dead~~
	~~5 always show pattern, even if LED disabled~~

	~~==== Timeout ====~~

	~~Time in seconds after blinking is stopped. 0 = infinite blinking.~~

	~~==== Led mapping ====~~
	*r/g/b maps led to engine 1,
	*R/G/B maps led to engine 2.

	~~examples:~~
	~~rGB = red led is mapped to engine 1, green and blue to engine 2~~

	~~rBg = red and green leds are mapped to engine 1, blue to engine 2.~~

	~~You can of course define only one colour, for example:~~
	~~r = red led is mapped to engine~~

	~~==== Engine patterns ====~~

	~~from mce.ini:~~
	~~# 0000 -- Jump to the start of the pattern for the channel~~
	~~# 40xx -- Set channel brightness~~
	~~# 9d80 -- Refresh Mux (use as first command in every pattern!)~~
	~~# xxyy -- Increment/decrement~~
	~~# xx determines the speed;~~
	~~# 02-3f -- short step time (granularity 0.49ms)~~
	~~# 42-7f -- long step time (granularity 15.6ms)~~
	#
	~~# If xx is even, increment~~
	~~# If xx is odd, decrement~~
	~~# yy determines the increment/decrement steps~~
	~~# 00-ff -- in/decrement steps~~
	#
	~~# Use 0 steps to create pauses~~
	~~# Two consecutive increment/decrement sequences are needed~~
	~~# to cover the entire range from 0-255~~
	~~# c000 -- End pattern execution~~
	~~# e002 -- Send engine 1 trigger~~
	~~# e004 -- Send engine 2 trigger~~
	~~# e008 -- Send engine 3 trigger <used by key backlight!>~~
	~~# e080 -- Wait for engine 1 trigger~~
	~~# e100 -- Wait for engine 2 trigger~~
	~~# e200 -- Wait for engine 3 trigger <used by key backlight!>~~



	~~source: http://talk.maemo.org/showthread.php?t=37691~~

			led article has moved to [[LED patterns]]

	[[Category:Power users]]		[[Category:Power users]]

imported_>f2thak: /* Remote WLAN Access To Root / System Files */

2010-01-20T11:28:36Z

Remote WLAN Access To Root / System Files

← Older revision		Revision as of 11:28, 20 January 2010
Line 118:		Line 118:
	== Remote WLAN Access To Root / System Files ==		== Remote WLAN Access To Root / System Files ==
	for easy file manipulation		for easy file manipulation

			(please note: all these apps and steps may not be necesarry but I got it working like this)

			this help file assumes you know the risks and how to at least download and install apps from the extra repos..


			i think you also need
			diablo_kernel_usbnet_patch_windows_v0.4
			available here:
			https://garage.maemo.org/frs/?group_id=801




	To get remote access to N900 thru wifi:		To get remote access to N900 thru wifi:
	---------------------------------------		---------------------------------------

	1. install the following apps/software		1. install the following apps/software



	n900 end:		n900 end: (all these apps are in extras repos)

	ssh server/client - this will request password when installing (WRITE DOWN / TAKE NOTE OF PASSWORD !!)		ssh server/client - this will request password when installing (WRITE DOWN / TAKE NOTE OF PASSWORD !!)
Line 132:		Line 145:
	maemo-pc-connectivity		maemo-pc-connectivity
	mad developer		mad developer

	~~(please note: all these apps and steps may not be necesarry but I got it working like this)~~


Line 139:		Line 150:

	winscp		winscp
			http://winscp.net/download/winscp425setup.exe



	2. goto 'settings' > connectivity > 'pc-connectivity-manager'		2. goto 'settings' > connectivity > 'pc-connectivity-manager'

	3. click "advanced" button > select environment 'default'		3. click "advanced" button > select environment 'default'

	4. select connectiont type 'usb'		4. select connectiont type 'usb'

	5. options > select 'network' from drop-down list		5. options > select 'network' from drop-down list

	6. select connectiont type 'internet' > options > connect using 'WLAN'		6. select connectiont type 'internet' > options > connect using 'WLAN'

	7. Save and apply		7. Save and apply

	8. open "mad developer" > manage usb > 'gfile_storage' > close		8. open "mad developer" > manage usb > 'gfile_storage' > close

	9. open winscp and put the WLAN ip address shown in mad developer in the 'host name'		9. open winscp and put the WLAN ip address shown in mad developer in the 'host name'

	10. user name "root", password "(password created during ssh install)"		10. user name "root", password "(password created during ssh install)"

	11. save > login		11. save > login

	12. you should now have access!!		12. you should now have access!!

imported_>f2thak: Remote WLAN Access To Root

2010-01-20T11:22:00Z

Remote WLAN Access To Root

← Older revision		Revision as of 11:22, 20 January 2010
Line 113:		Line 113:

	[[Category:Power users]]		[[Category:Power users]]



			== Remote WLAN Access To Root / System Files ==
			for easy file manipulation

			To get remote access to N900 thru wifi:
			---------------------------------------

			1. install the following apps/software



			n900 end:

			ssh server/client - this will request password when installing (WRITE DOWN / TAKE NOTE OF PASSWORD !!)
			rootsh
			maemo-pc-connectivity
			mad developer

			(please note: all these apps and steps may not be necesarry but I got it working like this)


			for pc end:

			winscp



			2. goto 'settings' > connectivity > 'pc-connectivity-manager'

			3. click "advanced" button > select environment 'default'

			4. select connectiont type 'usb'

			5. options > select 'network' from drop-down list

			6. select connectiont type 'internet' > options > connect using 'WLAN'

			7. Save and apply

			8. open "mad developer" > manage usb > 'gfile_storage' > close

			9. open winscp and put the WLAN ip address shown in mad developer in the 'host name'

			10. user name "root", password "(password created during ssh install)"

			11. save > login

			12. you should now have access!!

imported_>ossipena: /* Step by step instructions */

2010-01-20T07:53:42Z

Step by step instructions

← Older revision		Revision as of 07:53, 20 January 2010
Line 15:		Line 15:
	* Make a backup (not necessary!) from original mce.ini -file, for example:		* Make a backup (not necessary!) from original mce.ini -file, for example:
	cp /etc/mce/mce.ini /etc/mce/mce.ini_old		cp /etc/mce/mce.ini /etc/mce/mce.ini_old
	* Open /etc/mce/mce.ini with a text editor		* Open /etc/mce/mce.ini with a text editor (nano, vim, leafpad...)
	* Search for a line:		* Search for a line:
	[LEDPatternLystiRX51]		[LEDPatternLystiRX51]

imported_>ossipena at 07:50, 20 January 2010

2010-01-20T07:50:18Z

← Older revision		Revision as of 07:50, 20 January 2010
Line 110:		Line 110:

	source: http://talk.maemo.org/showthread.php?t=37691		source: http://talk.maemo.org/showthread.php?t=37691


			[[Category:Power users]]

imported_>ossipena: /* Constructing own patterns */

2010-01-20T07:48:59Z

Constructing own patterns

← Older revision		Revision as of 07:48, 20 January 2010
Line 25:		Line 25:
	=== Constructing own patterns ===		=== Constructing own patterns ===

	The mce.ini -file has description header before pattern defining start. Here ~~will be hopefully easier way to visualize~~ the ~~long strings~~.		The mce.ini -file has description header before pattern defining start. Here are the same instructions with longer explanations.

	Example string:		Example string:

imported_>ossipena: /* Constructing own patterns */

2010-01-20T07:48:01Z

Constructing own patterns

← Older revision		Revision as of 07:48, 20 January 2010
Line 26:		Line 26:

	The mce.ini -file has description header before pattern defining start. Here will be hopefully easier way to visualize the long strings.		The mce.ini -file has description header before pattern defining start. Here will be hopefully easier way to visualize the long strings.

			Example string:
			PatternCommunicationCall=30;1;0;r;9d80400002ff03ff02ff03ff71080000;9d800000


			Dissection:
			{\| class="wikitable" border="0"
			\|-
			\| PatternCommunicationCall=
			\| 30;
			\| 1;
			\| 0;
			\| r;
			\| 9d80400002ff03ff02ff03ff71080000;
			\| 9d800000
			\|-
			\| Alert pattern
			\| priority
			\| screen on
			\| timeout
			\| led mapping
			\| Engine 1 pattern
			\| Engine 2 pattern
			\|}


			==== Priority ====
			This defines that which blinking pattern is the strongest. So if multiple alerts are enabled, which pattern will be shown. Values from 0 to 255 are accepted.

			==== Screen on ====
			from mce.ini:
			0 only show pattern when the display is off
			1 show pattern even when the display is on
			2 only show pattern when the display is off, including acting dead
			3 show pattern even when the display is on, including acting dead
			4 only show pattern if the display is off, or if in acting dead
			5 always show pattern, even if LED disabled

			==== Timeout ====

			Time in seconds after blinking is stopped. 0 = infinite blinking.

			==== Led mapping ====
			*r/g/b maps led to engine 1,
			*R/G/B maps led to engine 2.

			examples:
			rGB = red led is mapped to engine 1, green and blue to engine 2

			rBg = red and green leds are mapped to engine 1, blue to engine 2.

			You can of course define only one colour, for example:
			r = red led is mapped to engine

			==== Engine patterns ====

			from mce.ini:
			# 0000 -- Jump to the start of the pattern for the channel
			# 40xx -- Set channel brightness
			# 9d80 -- Refresh Mux (use as first command in every pattern!)
			# xxyy -- Increment/decrement
			# xx determines the speed;
			# 02-3f -- short step time (granularity 0.49ms)
			# 42-7f -- long step time (granularity 15.6ms)
			#
			# If xx is even, increment
			# If xx is odd, decrement
			# yy determines the increment/decrement steps
			# 00-ff -- in/decrement steps
			#
			# Use 0 steps to create pauses
			# Two consecutive increment/decrement sequences are needed
			# to cover the entire range from 0-255
			# c000 -- End pattern execution
			# e002 -- Send engine 1 trigger
			# e004 -- Send engine 2 trigger
			# e008 -- Send engine 3 trigger <used by key backlight!>
			# e080 -- Wait for engine 1 trigger
			# e100 -- Wait for engine 2 trigger
			# e200 -- Wait for engine 3 trigger <used by key backlight!>



	source: http://talk.maemo.org/showthread.php?t=37691		source: http://talk.maemo.org/showthread.php?t=37691