Patch Request: (more useful/detail) Call Records

[DarkAvenger]

Here are some things that many people would find useful, and
I believe they shouldn't be impossible to hack:

1)
List the number of unanswered calls from the same person.
We already are given date+time for the last unanswered call.
All that would be needed is storing the last 5-10 (or whatever number is chosen) somewhere in the EEPROM, and then displaying them below the current "display".

For example I have:

Unanswered Calls
-----------------------
<-- blank line
Tom
+123456789
14.05.2003 00:49
<-- blank line
Button:Add Button:OK


but would be great to have a scrollable screen like this:

Unanswered Calls
-----------------------
Tom
+123456789 x39
14.05.2003 00:49
10.05.2003 02:14
04.05.2003 13:54
Button:Add Button:More

Note:
We get rid of the useless blank lines.
the Button:OK has changed to More, which means pressing it will give u the next page/line of data. To get out (same as the old OK button did), you just press the ESC/red phone button.
Also, next to the fone # we have "x39", which means this person has made 39 unanswered calls.
In fact, now that I think of it, we don't even need the NAME
line because we already selected the name to get this screen!! (look at how the Incoming/Outgoing screens display info)

Is this do-able? What do you think?

2)
List of incoming calls from the same person and times/duration

3)
List of outgoing calls from the same person and times/duration

Obviously for 2 and 3, there would be a problem of how many times to list for each phone/person. A fixed number like let's say the last 5 or 10 times would work well. A storage area would also have to be found for saving this info. I hope there's enough room in the EEPROM.

So I imagine of something like:

Incoming Calls
-----------------------
+123456789 x39
14.05.03 00:49 2
10.05.03 02:14 14
04.05.03 13:54 22
Button:Add Button:More

Note the differences:
we chop the year from 2003 to 03 because we need extra room per line to display the last column which is duration of call in minutes (2 mins, 14mins, 22mins). I think 2 columns is good (up to 99 minutes). I doubt
many people talk more than 99 mins STRAIGHT per call.. I mean, if you do, then you got SERIOUS brain problems and should try to patch your neurons and not your SL4x ;)


So what do you think?

I'd like your comments, in as good english as possible ;) Kinda hard to understand sometimes what is said on this forum :(
I know English is a crappy language and sometimes is a bitch, but I can't think of another ;)))

Thank you for taking the time to read this, and many thanks to all the great patchers who've made this fone just simply unbelievable!

[Bikonja]

We can speak Croatian :)
Pa gle, Hrvatski ti je bas jedan lijepi jezik kojeg ne razumije nitko osim nas Hrvata i mozda Bosanaca i Srba i djelomicno Slovenaca :)

Ok ok, I won't bother you on Croatian... I will speak English 'cause I speak it well... Well now, the idea is good... Few adjustments here and there but that varies from individuals... Someone should definitley make that patch....

[RAT2]

I've posted to another part of this forum>

I dont understand, why this is included in s45i phone but not in sl45i! On s45i u get a missed times number for each caller and more details

[DarkAvenger]

Thank you RAT.

I don't know either why they omit such simple things! I think it's either neglect, or a different team working on the phones, but still that's no excuse because even if it's a different team engineering the phones, the quality assurance and marketing teams SHOULD have noticed that these very similar phones have some WILDLY different micro-features. I say microfeatures, because things like MP3 playback (big feature) simply could not be made for S45 .... BUT small things like these surely can be made on any phones..

Can at least someone here who knows about patching tell us if it would be easy or do-able to add such patches?


Finally, I'm curious, and I haven't really found out, but are some of the patches that we use "modified" assembly code? I mean, that some are simple: add this "KEY CODE" instead of this "KEY CODE" (so it's not actually machine language, but just values), to make this function use another key.

But some other patches are quite big.. Are those new machine language code? And if so, did Rizapn or whoever use an assembler to produce it?

thanks for the info

[anustka]

this is the only problem in sl45 i think...

[rizapn]

*) S/ME-45 firmware is newer than SL45. That's why some functions in those phones is look more *modern* than in the SL45.
*) That kind of patch discussed here is not easy. I, personally, think it is not so usefull, and will give no time to work on it. Hope someone else think differently and share their finding ...
*) Yes, of course patching is including : decompile, assembler, byte-code, searching, guessing, and luck.

RizaPN