Re: Extended Call Log - extras-devel
 

eventlogger missing..

Re: Extended Call Log - extras-devel
 

Someone posted this in another thread

So for anyone having problems it might be worth checking what repository you are trying to install from, and if you want v0.3 make sure you are using extras-testing by disabling extras-devel

Edit: An update on this. Someone tested using another application of mine (webtexter) that was having the same problem. When they had devel enabled, they could not install. Then they disabled devel and enabled testing it installed correctly.

Re: Extended Call Log - extras-devel
 

Install yes, updating is the issue. If you download from one repository you can't update from another repository's version (well, at least as far as I can tell).

I did what you said, but in order to get the testing Extended Call Log, I had to uninstall the one I had. I get the feeling the version number for the one in devel was higher (ie, newer) than the one I got from testing.

Re: Extended Call Log - extras-devel
 

I don't know how the application manager deals with applications from different repos. I thought it was based on version number and they should both have the same version (see http://maemo.org/packages/view/extcalllog/)

I'm considering pushing it to extras in the hope that it will solve the issue for most people but I'm slightly worried that it would cause issues for people in extras. Does anyone know if promoting it might cause any issues now?

Re: Extended Call Log - extras-devel
 

Extended Call Log not working after UNofficial PR1.2. flash. App starts loading and then crashes.

Re: Extended Call Log - extras-devel
 

Can you start it from the terminal and see what the output is?

To do this in terminal type extcalllog

It also might be worth trying to install the version from extras-devel and see if this works better.

Re: Extended Call Log - extras-devel
 

Hmm.. Seems I was wrong, matrim. Even though my current Extended Call Log was downloaded from testing, I intermittently get prompted to update from devel (which results in the issues we discussed).

Glad it works this way, though. If it's the same app, and I enable a certain repository, I should be able to download an update if one is available even if it's through a different repository than the one I obtained my app through.

Re: Extended Call Log - extras-devel
 

A quick question for the people using extended call logger, how many of you run the call end time update script from kovach in this thread.

For the next version of Extended Call Logger I've copied the code for the Eventlogger-UI into my application so that I can make changes to it.

I already have it displaying the incoming number in the main call list, for example
Matrim (+123456789)

And if there is enough interest I might make it display the call end time in the call details page

I also hope that this will allow me to improve the loading speed when you are trying to get a lot of calls

Re: Extended Call Log - extras-devel
 

Hadn't seen it.. Weird, though, that the "fix" is so simple and wasn't implemented by default. Oh well..

Anyway, probably more important than displaying end time for a call is the duration of said call (preferably in human-readable form.. 1:20 as opposed to 80seconds). Of course, if we could have all of it, start;end;duration, even better.

The talk says adding those triggers is relatively safe.. There doesn't seem to be any system-default triggers and running that batch command resets the list so unless some other app decides to overwrite them, it should be relatively safe putting that into your app's pre- or post-installation scripts.

Re: Extended Call Log - extras-devel
 

Human readable format shouldn't be too much extra effort so would be ok. Although, I probably won't put the triggers as part of my install script, as I'd prefer to have that left somewhat separate to allow people to choose if they want to try it just in case it causes issues.
Maybe I could include a script that is easy to run that can be used to set up the triggers

Re: Extended Call Log - extras-devel
 

Hi,
Same symptom:
"Extended Call Log not working after UNofficial PR1.2. flash. App starts loading and then crashes"

In x terminal i got this error:
"extcallog: error while loading shared libraries: librtcom-eventlogger.so.0: cannot open shared object file: No such file or directory"

I have search this file and i didn't found it, I found only librtcom-eventlogger.so.1 file. Maybe this version mismatch could be the problem.

Is there any solution to run this app on the new swversion ?

Re: Extended Call Log - extras-devel
 

@Dibcsi: that's kinda what you get when you flash unofficial firmware into a device that's not supposed to be running it. Most apps found in the extra* repositories right now are made for PR1.1.1. If any of them use a lib that's been updated in PR1.2 (such as the librtcom suite) then you'll have trouble running them.

As for a fix: a while back one Extended Call Log version was mistakenly built against the PR1.2 libs, and I think it can still be found in one of the extra* repositories.. I think it's devel, but I'm not sure. Fire up the app manager, uninstall the version you currently have, activate only one of the extra repositories at a time and look for the app again. Install the one that doesn't report any problems when you press "Details".

Re: Extended Call Log - extras-devel
 

I'm experiencing the same problem after updating to the official PR1.2

You could try uninstalling the version you have and reinstalling from extras-devel. I haven't tried yet myself but it might work.

Also there will probably be an issue with some of the filters with PR1.2. This is because of a change to the rtcom-eventlogger library and the DB format used to store the call logs.
I have them fixed in development and should be releasing a new version to extras-devel over the next couple of days. I've just updated my device to the official PR1.2 and need to test the development version tonight \ tomorrow before uploading.

Re: Extended Call Log - extras-devel
 

Thanks for quick reply. Then I am waiting for the new version. Thanks again.

Re: Extended Call Log - extras-devel
 

The new version is in extras-devel now. Changelog is

* Added ability to filter by date
* Allow -1 in the limit to show all calls
* Show number in main list
* Added startup notification to warn that load times can be long
* Changed "Received" to "In" and "Dialled" to "Out" in filter menu
* Fixed issue with filters caused by new rtcom-eventlogger library and database in PR1.2

Note: This version requires PR1.2 to work.

There can still be a problem with long loading times when you are loading alot of calls.
This will show up if you
* Use a large limit
* Use -1 to show all calls
* Select a large time period (with alot of calls) in the date filter

Also the UI is usable but has problems if you use ctrl + shift + r to cause \ enable rotation in the application

Re: Extended Call Log - extras-devel
 

im tring to update extended call log it give me missing pacakage
librtcom-eventlogger-plugin1
librtcom-eventlogger1
?
any help?

Re: Extended Call Log - extras-devel
 

Re: Extended Call Log - extras-devel
 

If you are using PR1.2 use extras-devel to update
For PR1.1 use extras / extras-testing

Re: Extended Call Log - extras-devel
 

Thank you. It is working.

Re: Extended Call Log - extras-devel
 

Good to hear. Let me know if there are any problems.

I plan on giving it a few days for people to update to PR1.2 then moving to it to testing

Re: Extended Call Log - extras-devel
 

Hi

I have found a little bug, I think.
When I doubleclicked on contact in the list, I got a new surface with delete button.
When I click delete button to remove this one occurrence from the calllist, then It seems to nothing happened, because of the window remain and doesn't go back to the full calllist. BTW, the delete function is working, but this is a little annoying and there is no any "delete ok" message or something.

Re: Extended Call Log - extras-devel
 

I'd noticed this before but forgot to go back to fix it.

I've raised Bug 10549 and Bug 10550 on the problems to remind me to go back and look at them.

I think I was unable to make the details stackable window disappear and will try get that working again, but at the very least I'll add a banner saying call deleted

Re: Extended Call Log - extras-devel
 

I've uploaded v0.5 to extras-devel

This new version allows calling back of GSM numbers and opening the contact card if the call is from a contact.
There is still no support for calling back a VoIP call if it's not from a contact.

Also, if you are using the trigger hack from Kovach \ hcm to update the end-time field, extended call log will display the length of the call in the details window.


The full changelog is

* Add about box using he-about-dialog
* bug 9649 - Add option to call back a GSM contact
* Add option to open the contact card if the call is from a contact
* Unknown numbers now displayed correctly in detailsWindow
* Change how calls not from a contact display
* bug 10550 - display a banner when a call is deleted
* bug 10549 - close detailsWindow when that call is deleted
* single tap will now open detailsWindow. No need for double click any more
* display length of call if end-time db field in use (see trigger hack http://talk.maemo.org/showthread.php?t=42624)

Re: Extended Call Log - extras-devel
 

Hi.

Thank you. It is very good.

Re: Extended Call Log - extras-devel
 

Does anyone know where the settings for this are ?
I need to reset the displayed amount from unlimited back to 30.

I set it to -1 now it just takes to long to load, I really needed to filter by date. But it is taking to long for the menu to open so I can not set it back.

I have linux skills, just need t oknow where the settings are configured.

Thanks

Re: Extended Call Log - extras-devel
 

The setting is a gconf setting at /apps/extcalllog/limit

Running a command like

gconftool -s /apps/extcalllog/limit --type int 30

should reset it

Re: Extended Call Log - extras-devel
 

The time shown in the call record, is the start or the end time of the call? Is it possible to see the duration of a call or both the start and end time for a call?

Re: Extended Call Log - extras-devel
 

This isn't logged in the database by default.

You can use the triggers mentioned it this thread to make a hacked way to put in the end time of the call and if that is there Extended Call Log will display the length of the call in the call details.

Re: Extended Call Log - extras-devel
 

matrim

Would you consider adding the triggers as part of your application?

Thanks for your contribution :)

Re: Extended Call Log - extras-devel
 

Which database are we talking about? And which process/application is responsible, or should be responsible, for putting the call start and end time (or duration) into the database?

I would like extended call log to just include the call duration, but it seems like this application is dependent upon something putting the information into this database first.

So, what is the process that needs enhancing to put the info into the db and when will it be improved to do so?

Thanks!

Re: Extended Call Log - extras-devel
 

The database is the rtcom eventlogger (call and sms \ im) database at /home/user/.rtcom-eventlogger/el-v1.db

The call information is added to by a Nokia application which I assume is the phone UI although I'm not sure exactly which process \ application adds it. I notice you've already voted for the enhancement in bugzilla but TBH I wouldn't expect it to be added until at least Harmattan

There is a workaround here that can cause the end time to be added to the database.

For extended call log, I don't add anything to the database and the aim of the application is to provide an alternate view of the log which provides extra information and ways to view \ filter the information rather than modify the information in the database

Re: Extended Call Log - extras-devel
 

This is no biggie but is it possible to tweak the name :) ? It appears on my screen as "Extended Call Lo"

Re: Extended Call Log - extras-devel
 

Should call duration show up on the "first" "main" screen?

I recently implemented the event-logger tweak. If I select the details of a call I get the duration, but I would like to see it on the main screen. There's certainly enough space. :-)

Is this because I only have 5 calls with duration, and 100s without? should I delete the database and start over?

I appreciate it may not be economical to modify the code for the 6 of us with call durations, but I can hope.... :-)

Thanks!

Re: Extended Call Log - extras-devel
 

is there not anything which integrates with the contacts in the phone and shows the Call Log Histroy in the area where we see the call received or made, rather than clicking on a seperate Icon of Extended Call Log.

Re: Extended Call Log - extras-devel
 

I see PR1.3 has broken Extended Call Log

Re: Extended Call Log - extras-devel
 

I'm not certain what this does. Other than a longer "tail" of the call log.

It would be killer if it had call durations!

Or at least have something usable to me...

Re: Extended Call Log - extras-devel
 

Opps my mistake it's not broken. :rolleyes:
There is an sqlite script that adds the duration.
http://talk.maemo.org/showpost.php?p...3&postcount=20

Re: Extended Call Log - extras-devel
 

why there is no call duration in extended call log? also when i click any contact to see details and then back botton the app doesn't respond and close now option comes up!!!

Re: Extended Call Log - extras-devel
 

It will only show duration if it is logged in the database and by default end time isn't logged.

To get it to log see this thread

Can you give details of the second issue? When do you see it? Do the call details come up etc

Re: Extended Call Log - extras-devel
 

yes the call detail comes up and there are three option to choose open contact card , call no. Delete.(i did not check whether they are working or not ) and when i press back botton it stops responding(or it freez,or stuck here ) nothing i can do there and later like every app give option when stuck "blah blah application is not responding close now?yes or no...

And good news is that it happaned two times with me.and from third time when i try it back botton was working properly.
perhaps it was happaning only me (i was in a hurry and did not let it load properly)cheers