Active Topics
-
The N900 is now 15 years old! (9)
to Nokia N900 by Arno_11 - 12 hrs, 2 mins ago -
Sailfish OS for the Motorola Moto G7 Power (XT1955-5) - (ocean) (4)
to SailfishOS by Maemish - 6 days ago - more...
gurkki |
2010-04-27
, 17:07
|
|
Posts: 14 |
Thanked: 1 time |
Joined on Apr 2010
|
#41
|
eventlogger missing..
|
|
2010-04-30
, 12:28
|
|
Posts: 121 |
Thanked: 75 times |
Joined on Oct 2009
|
#42
|
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.
Last edited by matrim; 2010-04-30 at 15:14.
0.3 in testing is OK, but 0.3 in devel has currently some dependency issues. 0.2 in extras i OK, but lacks some features
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.
Last edited by matrim; 2010-04-30 at 15:14.
| The Following User Says Thank You to matrim For This Useful Post: | ||
|
|
2010-04-30
, 16:02
|
|
Posts: 28 |
Thanked: 8 times |
Joined on Feb 2010
@ Portugal
|
#43
|
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.
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.
|
|
2010-04-30
, 18:24
|
|
Posts: 121 |
Thanked: 75 times |
Joined on Oct 2009
|
#44
|
Originally Posted by kerneld
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/)
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.
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?
 |
|
2010-05-02
, 13:03
|
|
Posts: 861 |
Thanked: 936 times |
Joined on Feb 2010
@ Bulgaria
|
#45
|
Extended Call Log not working after UNofficial PR1.2. flash. App starts loading and then crashes.
|
|
2010-05-02
, 14:13
|
|
Posts: 121 |
Thanked: 75 times |
Joined on Oct 2009
|
#46
|
Originally Posted by zlatko
Can you start it from the terminal and see what the output is?
Extended Call Log not working after UNofficial PR1.2. flash. App starts loading and then crashes.
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.
|
|
2010-05-03
, 19:43
|
|
Posts: 28 |
Thanked: 8 times |
Joined on Feb 2010
@ Portugal
|
#47
|
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.
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.
|
|
2010-05-14
, 09:25
|
|
Posts: 121 |
Thanked: 75 times |
Joined on Oct 2009
|
#48
|
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
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
|
|
2010-05-14
, 18:49
|
|
Posts: 28 |
Thanked: 8 times |
Joined on Feb 2010
@ Portugal
|
#49
|
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.
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.
|
|
2010-05-15
, 18:25
|
|
Posts: 121 |
Thanked: 75 times |
Joined on Oct 2009
|
#50
|
Originally Posted by kerneld
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.
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.
Maybe I could include a script that is easy to run that can be used to set up the triggers
