M65v50

A114CB3C CalledBy__IllByKey_On_5mX_5_GX__KeyPress
A114CB3C 6C 48                       LDR     R0, =ram_keypress_buffer
A114CCF0 E0 5D 65 A8 off_A114CCF0    DCD ram_keypress_buffer A8655DE0
+18: Key currently pressed * Write access to A8655DFC, PC=A08298EC

A114CA90 Keypress_Off_Store2Ram ; Called when pressed key is released. writes 0 to ram_keypress_buffer
A114C9D2 Keypress_On_Store2Ram ; Called with pressed key in R0. writes to ram_keypress_buffer
70B5041C251C802085439999999999990020183EF060B0600123F056052833DA281C

Call_Keypress_On:




A8655EE0 Keylock-Status: 1=An. Da auch aktiv setzbar!

A114CB3C CalledBy__IllByKey_On_5mX_5_GX__KeyPress
A114CB3C 6C 48                       LDR     R0, =ram_keypress_buffer
A114CCF0 E0 5D 65 A8 off_A114CCF0    DCD ram_keypress_buffer A8655DE0
+18: Key currently pressed * Write access to A8655DFC, PC=A08298EC

A114C9D2             Keypress_On_Store2Ram
A114CA90             Keypress_Off_Store2Ram


-----------------------------------
			M65v50		SL65v50		S65v58		CX70v56		cx70v56Funze	
KeyPress
KeyPress_entry		010602D59999999910BD9999999910BDB0B5999900200831
			A114CB62	A11503B6	A1158642	A0CB6236
Keypress_On		70B5041C251C802085439999999999990020183EF060B0600123F056052833DA281C
			A114C9D3	A1150227	A11584B3	A0CB60A7 	A0CB6082
Keypress_Off		next function after Keypress_On
			A114CA91	A11502E5	A1158571	A0CB6165	A0CB6164

ram_keypress_currently	A8655DF8					A86A802C	A86A802C
=ram_keypress_buffer+0x18
_ram_keypress_buffer
			A114CCF0					A86A8014



A16310B2 Screensaver_GetAddress 
(A0680028999901219999999910BD) + 0xE
			A16310B2	A163ECC6	A16960A6
Gets address of screensaver






---- menu / mainscreen stati
A8638E10 funny status byte, shortly on keypress and sometimes in between
A1217928 90 64 9F E5                 LDR     R6, =0xA8638D80
0 oder 1, wenn ruhig, hher kurz, wenn irgendein event oder wechsel anliegt


A1633C18 3C 49 LDR     R1, =0xA863A540 ( + 2 )
A1633A90 9E 49 LDR     R1, =0xA863A540 ( + 2 )
A1633C4C 2F 48 LDR     R0, =0xA863A540 ( + 2 ) ; in NetiCONrOUTIne
A1633D0C 40 A5 63 A8 off_A1633D0C    DCD ram_mainscreen_menu_state_minus2 
"00AB998B992899999999CE43301C999999990028"+ 0x20


A863A542: 2C, wenn on mainscreen, sonst FF. 00 beim Startup :-)
leider hin und wieder mal "kurz" bei normalen Tastendrcken auch FF
Write access to A863A544, PC=A1633A96
ca. 2 sekndl. entry. luft nicht im idlen, nur bei licht an?

A1633F26 6E 49 LDR     R1, =0xA863A55C (+8) im Prinzip gleich wie oben. 



-----------------


Ein paar Muster-Sequences (der "number of key sequences" counter muss im Patch auf die Anzahl der KEy Sequences gestellt werden)

[CODE]

; toggle Keylock, registers=0, key-sequence "#","#", Mode=direct+only at mainscreen+send red key after, sound: 0x23, sound-len: 3
10: 0xFFFFFFFE,00,00,00,00,23,23,00,00,00,0E,23,03

; SwitchOffPhone (func lib), registers=0, key-sequence=softkey_left+joystick_right, sound: 0x7b, sound-len: 5
20: 0x00000009,00,00,00,00,01,3E,00,00,00,00,00,00

; SetProfile (func lib), R0=(profile-1), key-sequence: "4". mode=by hotkey. no sound
30: 0x00000003,04,00,00,00,"4",00,00,00,00,01,00,00

; Midlet (filename is in string_number 3), R0=(string_number-1), key-sequence= "12345", direct+always, no sound
40: 0xFFFFFFFF, 02,00,00,00,"12345",00,00,00

; Lock device, registers=0, key-sequence: "99#", direct+send red key after+only if keylock off, sound: 0x22, len:1
50: 0xFFFFFFFD,00,00,00,00,"99#",00,00,22,22,01

; Unlock device, registers=0, key-sequence: "9999#", direct+send red key after, sound: 0x22, len:1
60: 0xFFFFFFFC,00,00,00,00,"99#",00,00,02,22,01

Die bisherigen Key Sequences sind nicht FW-abhngig. Man kann aber auch eine Firmware-Adresse reinschreiben, hier die vom M65v50 frs NativeMen:
; Native-Menu,registers=0, key-sequence="0","0". Mode=by hotkey. no sound.
00: 0xA08E714B,00,00,00,00,30,30,00,00,00,01,00,00

[/CODE]


0FDF500: "2:\\amark.jar",00 ; string 0
0FDF530: "0:\\Java\\jam\\Applications\\QuotD\\Qotd.jad",00 ; ; string 1




