Patching: Technical Discussion ...

[coollang]

Hello, Riza
about these function:
0xE49486 GBSS_po_open
0xE4952E GBSS_po_read
0xE49672 GBSS_po_write
0xE497E0 GBSS_po_close
I found system use these to r/w file on mmc, but if using these directely phone would turn off.
in fact these function oprate file throught sending message to MMC_FILE_SYSTEM_proc and waiting retvalue, i think there is some action for init, but i cann't find.
example this SysProcess:0xDC5DA2 LoadImageSystemOnAndWait
it is called by 0xDC652A STOREBITMAP_PROCESS.
i known mamaich has used these function to read filedata at his java patch. but i write a test and call it by at+cgsn, it would turn on system.

sorry my bad english, my national language is chinese!

[DeadManS]

2RizaPN: another question about fileread function,if file not found on mmc what i get? and how i know about this

[rc-flitzer]

Originally Posted by Seklth

Can i on\off illumination?
I want use in java midlet.

Best thing to handle illumination in Java is to import Light class and use SetLightOn() and SetLightOff(). The difference between "Java light" and "firmware light" is that by firmware the light goes off after 15 seconds without keystroke, while Java light is on forever. But if you use some Canvas class in your midlet you can set a Timer that does making light off after 15 seconds like in MicroReader midlet.
The other way is to use System calls, you need Extension class from mamaich and the phone has to be patched to allow this. Then illumination is switched with firmware routine 0xDC4680 - but without notification whether illumination is on or off.

[rizapn]

File Access

fileOpen (and also GBSS_po_Open) return r4 as a file Handle. If it is FFFF means something wrong with opening the file.

GBSS_po_xxx, yes I knew them. As I said, direct access to them (also) will turn the phone Off. I also think about the Init process. But, after made a long time search, I think, I prefer to patch the built-in fileAccess to do it. That's the reason why FAM patch is exist.

All existing file access patches (calling images by chaos and java access by mamaich), insert their code in the location where the (MMC) INIT function is already established. My FAM patch put a possibility for us, to read (and also write with some tricks) any file in any condition.

rizapn

[DeadManS]

Thanks, a have a question about bin melody format for my patch LRT, if i convert melody from mid file, melody play a once not in loop, but if i download standart melody from flash and store in bin file his play in loop i try to use for conver you FFMod and RingToneConverter but melody after conversion by this prog not play in loop

[DeadManS]

and if you know how i can play a free dictafone file, and how i know plugged HandsFree or not (patch idea: when handsfree is plugged on, play VMO file istead ringtone)

[rizapn]

@DeadManS:

as far as I know, looping in the playTone is depend on their "ID". If the ID to be used is "All calls" or "VIP", then it will be looped. But, if the "ID" is Appointments, Message, or Cell Broadcast then it will not be looped. Means, same bin data, will have different output, depend on the "ID".

playVMO() is 0D536B2h, r13:r12 is pointer to the VMO filename (ASCIIZ) to be played. There is a clear example in the address 0d875ceh.

Check earphone is done by firmware in 0db3880h (to display the earphone icon). I think the function itself is 0c2487eh, but I can not test it becuase I do not bring my headset now ...

rizapn

[DeadManS]

What a max file size i can read from MMC, samtimes i reading some garbage

[DeadManS]

about error whenfile reading, i test, but you functoin not return ffff in r4 if file not found or read error, what i do wrong ? in my proc i simply called you file reading functions like this

calls fileread
calls playmelody
rets

[rizapn]

File Access (Using FAM)

1. Read dummy file (any small file), using my example (in my previous posting),
2. Put your real openFile, readFile, and closeFile in the function which will be executed after the dummy file is accessed (i call it after_loading_func in that posting).
3. openFile will return FFFF (in r4) if something wrong in the file access, not returned by my (FAM) function.
4. So, myReadFile_start (refer to my previous posting) is only a trigger, unless you really sure that filename is really exists (for example, executing from Card-Explorer).
5. Maximum fileSize (theoritically) is 10x16KB = 160KB ... The actual bytes read is recorded as a 1st word in the FACBuff (36h:3FF8h) area.

rizapn

[DeadManS]

if i know you right, i need read the dummy file with you function, and after you function executed, i read real needed file whith firmware function ?

[rizapn]

@DeadManS:
yes... unless you are sure that the 1st file (the dummy ones) is always exists, or you don't need fileOpen return value ...

reading dummy file with FAM is a trigger, and to do some INIT_MMC which is really need when we will access the file.

rizapn

[DeadManS]

another stupid question what function is used for read file in memory in my address after i read dummy file with you function, and how i take this function parameters (filename addres, memory address for file). and after i loding file i must close this file ?

[rizapn]

fileOpen (0xDFA73E)
- r15:r14 = pointer to ASCIIZ filename
- r4 = Open result, if success r4=fileHandle, if failed, r4=FFFF

fileRead (0xDFABAE)
- r12=fileHandle
- r15=size
- r14:r13 = pointer to buffer

fileClose (0xDFC570)
- r12=fileHandle

There are also some GBSS_po_xxx function, but they need more parameter. I prefer to use those 3 functions.

rizapn

[DeadManS]

how i know filesize ?
P.S. It is difficult to be stupid for me