PDA

View Full Version : autokeylock in DCT3



Bütyök
12-05-2004, 09:30 PM
Knows anybody how can I find the keylock routine in a flash?
(press menu & * or keylock entry until calls in headset mode)

set
21-05-2004, 09:09 AM
been looking for that for some time now...
I think it has something to do with "show_main_menu" routine and "nokia_calced_key" routine... I couldn't figure it out though... :(

spaceimpact33
24-05-2004, 01:14 PM
Hi set,

i found that in 3310 6.07 the key pads status (locked/ unlocked) is stored at ram address 0x0011FF1E look 0 -> not locked 3-> locked but i think there are more status then just locked and unlocked
there is a function at 0x000C8F8E that i also found

just some info,
Spaceimpact33 ;)

Bütyök
24-05-2004, 01:49 PM
Thanx, it is very good.

But how can I access to RAM?
How can I read RAM?
Can I read it when phone is work?
(I think, the real and usable datas are in RAM during work)
Or how get any data to RAM?

(is it not too much? :-))


Thanx,
Bütyök

NokDoc
24-05-2004, 08:23 PM
Hi,

>> is it not too much?

Nah, simplest answer is nHexR.

It does show U an inphone tool for it, and also how to use functions to read and write to ram.

Bout the autokeylock:

Long ago I tried to put it from 3310-579 into 3310-513.

I gave up... ;)

Every addition gave new problems too.

I recall my main problem was timer related, like 513 had no mm:ss. :)

NokDoc

Kontact
25-05-2004, 06:41 AM
Hi,

>> is it not too much?

Nah, simplest answer is nHexR.

It does show U an inphone tool for it, and also how to use functions to read and write to ram.

Bout the autokeylock:

Long ago I tried to put it from 3310-579 into 3310-513.

I gave up... ;)

Every addition gave new problems too.

I recall my main problem was timer related, like 513 had no mm:ss. :)

NokDoc

nHexR is great... :)

AKL! i doubt u gave-up. it's just hibernating on ur table. :D

@Butyok

the routine of AKL, is in the 5e0 table... i just don't recall the exact loc. but it's there... NokDoc found it... no data/loc escapes from Mr. NokDocZ.

@spaceimpact

yes. it does write some data on RAM.. what u mentioned and also timer flags and durations.. i think AKL uses around 4 or more vars. like AKL on or off. timer on/off, duration etc. they are on RAM. but r saved on EERPOM.

regards

NokDoc
25-05-2004, 07:28 AM
Hi,

Some hints, start on 05E0_03

Essential ram locs:
513 579
00118BFC 0011018C
00118293 0010F683
0011FCE8 0011FCE8
0011**** 0011FCF5
0011**** 0011187C
(The ones with the * gave me headaches)

Sting Id's to get there:
(020A - Set delay:)
(01EC - Done)
(0144/0145 - Off)
(0144/0145 - On)

1st function to patch ain't hard.

But it uses these 2 new ram locs, which also need to be filled in other functions.

For the real interested, I still have this incomplete 513 file on which I started...

NokDoc

Bütyök
25-05-2004, 04:35 PM
.....For the real interested, I still have this incomplete 513 file on which I started...

NokDoc

Hi!
Can You send me this 513 file?
I don't need timer, because I want to lock keypad automatically when LEDs are faded.
I realized LED fade off when don't touch keypad to 15 sec only. In other case it isn't faded. I will to link automatic_keypad_lock routine to LED_fade_off routine.

Bütyök

spaceimpact33
25-05-2004, 05:17 PM
@Bütyök

You could also hook it from krisha's clock ( with the variable time outs )

just an idea
Spaceimpact33