mirror of
https://github.com/jberkel/sms-backup-plus.git
synced 2026-04-25 17:05:59 +03:00
[GH-ISSUE #64] Conversation order not working #59
Labels
No labels
AM+RCS
FAQ
awaiting response
backup
bespoke
bug
calendar
call log
cannot reproduce
cloudless
device-specific
documentation
dual- & multi-SIM
duplicate
feature-request
fixed in beta
good first issue
half-missing
help wanted
helpful
meta
misattribution
mms
other message sources
pull-request
question
rejuvenation
restore
schedule
security
stale
task
thanks
v1.5.1
v1.5.10
v1.5.11
v1.5.2
v1.5.3
v1.5.3
v1.5.4
v1.5.4
v1.5.5
v1.5.5
v1.5.6
v1.5.7
v1.5.8
v1.5.9
v1.6β
xoauth
~$ bounty $~
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/sms-backup-plus-jberkel#59
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Quirkyk on GitHub (Oct 27, 2010).
Original GitHub issue: https://github.com/jberkel/sms-backup-plus/issues/64
I have the latest 1.1.4 and it backs everything up just fine. In gmail it groups conversations but it won't put them in order based on their timestamp. On my droid x 2.2 it takes a conversation between two people, groups all the messages in one conversation but then groups responses by the participant in random message groups. Say there are 50 messages in a conversation. It will group the first five you see by recipient 1 then you see the next 8 are from the recipient 2, it may then go on to group the next batch of 3 messages by recipient 1. It shows the order fine as far as the day but it doesn't order the messages by timestamp. Am I missing something?
@kazuo commented on GitHub (Oct 30, 2010):
Are you talking about a (first) full backup? Or are you talking about increments? Check issue #52 because that thread is DROID X 2.2 specific.
Are your received SMS timestamps really matching up properly between your phone and what you see in Gmail? 2.2 introduced a timestamp issue with received SMS.
@Quirkyk commented on GitHub (Nov 2, 2010):
The backups are bringing over all messages, both sent and received so the first link didn't really help. The problem lies with the timestamp issue. So is this something that may get fixed or is it one of those issues you just have to live with?
@kazuo commented on GitHub (Nov 2, 2010):
Check the last couple posts on issue #52, it talks specifically about the received SMS timestamp issue on the DROID X 2.2. Basically it's a DROID X problem and not SMS Backup+. The way I got around it is by using SMS Time Fix in the Market.
@Quirkyk commented on GitHub (Nov 2, 2010):
Sorry I missed that! I got the SMS Time fix and it worked perfectly! Thanks!