Hi,
Just want to say i love this software and its better than software i've purchased before.
Anyway the only issue i have is my backing up my messages to the pc via PhoneExplorer 1.7 and prevsious versions. When looking at messages currently on the phone, sent items all the messages have no date/time sent. It displays No Indication for all of them, if i copy them to the archive, the date /time displays the minute they were copied. This also effects sorting, as they cant be sorted by latest-oldest etc.
Using a Sony W810i. Anyone else have this issue, or is it just down to my phone? Anything i can do?
Thanks in advance
Sent Messages TimeStamp - No Indication
-
Guest
Sent messages timestamps
Regarding this issue:
1) What are the exact reasons that the timestamps aren't accessible? My apologies for being sceptical, but I find it hard to accept that the internal telephone software CAN access and display the details, but MPE can't. In my view, there has to be SOME place the phone retrieves the timestamps from (and it seems natural to me that that is just the phone's internal memory). And thus, in my view again, it should be at least theoretically possible to access that location from other software as well. I can imagine there perhaps are no factory supported facilities to access the timestamp information but what about extending the phone software? Or an additional piece of software on the phone to help MPE get the information? I of course trust the development team to have investigated all the possibilities regarding this issue, but I couldn't find any information about the "why" of this problem or any information on solutions beyond MPE (i.e. extended phone software or an additional piece of software if that is even possible), so therefore this remark.
2) As an alternative, that I think should be relatively easy to program and I think could benefit many users, is is possible to add an option, to automatically add timestamps to every message, with the timestamp of message N being the timestamp of message N - 1 plus 1 second? In this way at least the ORDER of the messages is maintained when storing them in the archive. Example: message 1 00:00:01, message 2 00:00:02 etc.
Sorry for opening this "wound" again, but what I'm just wondering about, if there are still some ideas or (even extreme) possibilities or we have reached a "dead end" with regard to this issue?
If it makes any difference for you, I'm a long time user and fan of MPE and even donated to the project so I hope you'll not see me as someone coming down here without thinking and yelling about what isn't good about the program but seriously consider what I said here. And I understand, MPE is free software, so of course no one has an obligation to programming anything anyone asks for, and the programming has to be done in spare time and with a minimal budget, but I know there is a big demand for a feature like this, so perhaps it is still worth to give it another look?
Thanks in advance for your answer.
1) What are the exact reasons that the timestamps aren't accessible? My apologies for being sceptical, but I find it hard to accept that the internal telephone software CAN access and display the details, but MPE can't. In my view, there has to be SOME place the phone retrieves the timestamps from (and it seems natural to me that that is just the phone's internal memory). And thus, in my view again, it should be at least theoretically possible to access that location from other software as well. I can imagine there perhaps are no factory supported facilities to access the timestamp information but what about extending the phone software? Or an additional piece of software on the phone to help MPE get the information? I of course trust the development team to have investigated all the possibilities regarding this issue, but I couldn't find any information about the "why" of this problem or any information on solutions beyond MPE (i.e. extended phone software or an additional piece of software if that is even possible), so therefore this remark.
2) As an alternative, that I think should be relatively easy to program and I think could benefit many users, is is possible to add an option, to automatically add timestamps to every message, with the timestamp of message N being the timestamp of message N - 1 plus 1 second? In this way at least the ORDER of the messages is maintained when storing them in the archive. Example: message 1 00:00:01, message 2 00:00:02 etc.
Sorry for opening this "wound" again, but what I'm just wondering about, if there are still some ideas or (even extreme) possibilities or we have reached a "dead end" with regard to this issue?
If it makes any difference for you, I'm a long time user and fan of MPE and even donated to the project so I hope you'll not see me as someone coming down here without thinking and yelling about what isn't good about the program but seriously consider what I said here. And I understand, MPE is free software, so of course no one has an obligation to programming anything anyone asks for, and the programming has to be done in spare time and with a minimal budget, but I know there is a big demand for a feature like this, so perhaps it is still worth to give it another look?
Thanks in advance for your answer.
I am tired of explaining it again and again. If you want to find out why its not possible then you have to get informed about the interfaces to the phone. Ypu can download a document of the "AT-Commands" on the developersites of SE. besides this you need the knowledge of SMS PDU-Format.
Its not possible - even not with a firmwarepatch or something similar.
I also don't know which sense a Auto-Timestamp should have since its not possible to define the same order than in phone.
Its not possible - even not with a firmwarepatch or something similar.
I also don't know which sense a Auto-Timestamp should have since its not possible to define the same order than in phone.
-
Guest
Sent messages timestamps
Thanks for the effort of answering - even if you're tired - then. I already said "my apologies for being sceptical" and "sorry for opening this "wound" again", I'll stay with those two remarks!
(But maybe add to the FAQ that it is a unsolvable technical problem? For the next one being as annoying as me
)
(But maybe add to the FAQ that it is a unsolvable technical problem? For the next one being as annoying as me
)
-
noxxing