Hi all.
I just today discovered that at some point in the past, while backing-up/restoring all my SMS/MMS, that I had duplicated a TON of them. I think somewhere on the order of a couple thousand. I've played with a ton of different ROMs, sometimes flashing every day, or even multiple times a day. What can I say, I'm a ROM junkie.
Anyway, not totally sure when, but somewhere along the way this happened. I've used MyBackup Pro, SMS Backup +, and something else I tried once I can't remember. I think it was MyBackup Pro that did it. I think I tried the merge option or whatever it was.
Well, however it happened, here I am now. It's a huge giant PITA. How can I get rid of the dupes? I want to keep the MMS'es, along with the "links" or whatever so they'll show in the actual SMS threads. I saw SMS Backup & Restore that will check for dupes while restoring, but it doesn't support MMS.
I looked around and couldn't find a solution that sounds like it would work for this specific problem. If there's something out there and I missed it, I apologize. So anybody got anything?
Thanks.
So as the title says I have a "2 new voicemails" notification that will not go away, even though i have no new or old voicemails, and don't even use my sprint voicemail anymore! I have searched this forum and google for an answer but nothing i have read and tried worked. Strange thing is it only happens on gee roms. I have tried all the things mentioned like leaving a new voicemail then deleting them, changing voicemail # and using google voice, editing preferences in data/data/com.android.phone, and none of them have worked. Even after clearing data it goes away for a little while but then comes back. Even called sprint and had them check it out and reset my voicemail account but still no go, which makes me think it's in the software in my phone somewhere. I have an Optimus G on sprint. If anyone has any ideas please throw them my way because i need the help!
hey, i've been using the Gear S3 since half a year now, after being disappointed by AW 2.0 ruining my Moto 360 2nd gen
since the 3.0 update, i often get an error using s-voice with simple commands like "set timer for ten minutes"
sometimes it works, but often getting an error after a few seconds, show either "an error has occurred. i'm unable to answer your question. please try again later" or "an error has occured, try again later"
has anyone else encountered this problem and found a fix?
i did a factory reset twice now, didn't help, not changing the s voice language from automatic to us english
the other stuff i wanted from the update also didn't happen, but i guess that's a different discussion
I am having the same problem. I had purchased the S3 Frontier when it 1st came out. I returned it due to problems with svoice. I just purchased it again last week and svoice is still garbage. Was hoping for it to be better. Will be returning again.
i did not have this problem with 2.x, voice commands like this never showed the error, for me it started after the 3.0 update
Same problem here can't reply to a message with voice and errors when simple commands like the OP stated.
I get around the message problem by setting the language to English UK
I still get the error message after the latest update on the gear update. I need to re-flash the stock Tezin on it hoping it will fix it.
Same issue with S3 Classic
Same issue here with my S3 Classic. Occasionally it works but most of the time I get the error. Reported it to Samsung but they were unaware of the issue and were non-responsive.
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Same x 2
My S3 Tmobile LTE failed in 6 days. They exchanged it for a new one at the store yesterday and that one failed also. So I returned it since it's a defective product. I'll buy again when the issue is fixed.
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
WaxysDargle said:
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Click to expand...
Click to collapse
how often to you have to clear out the s-voice ??
matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
Every time you want it to work.
gboybama said:
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
Click to expand...
Click to collapse
I have the exact same experience Gboybama! Some contacts i can call, some produce an error message, some let svoice "synchronice contacts", which is never finished, letting the problem persist even after clearing cache, stopping the app, restart etc... **** this.
matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
i only had to do it once. it has been working "fine" ever since.
s-voice never quite works properly. never has. i doubt it ever will. seems like samsung just doesn't care.
I just got my s3 today to go with my new s8+ having tons of iss6 with s voice. Looks like I'm not alone. Probably going to be returning this and researching other options.
good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care
good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care
First off, I'd like to thank whoever takes the time to read and put any thought into this. Next, the reason I absolutely do not want to do anything that is going to erase/lose my SMS history; I'm an auto mechanic, and there is far too much various information on customers' vehicles, repair history and such...losing it all would be a huge setback. If I have to do something like a factory reset, I'm going to have to spend too many hours to even think about, manually going through 4 years of text messages to record everything. I tried a couple of options to backup said history, and nothing came up with even 100 messages to backup.
On to the problem... When SMS is received from person A, it shows up in a random, different person's(person B) thread. I then need to check the contact info to the left of the message to see who person A is, then back out, go to to person A's thread and respond there. If I respond in the thread that it's delivered to, person B gets the response. Any messages in the thread prior to this starting shows the proper contact, person B. Looking at message details, it shows the correct # in the 'From' section, but for 'To', it shows my number and the number for person B as if it was sent as a group text. This however is not the case...the message only comes to me.
I have tried deleting and reentering contacts, doing the same while the involved threads are archived, visaversa...and I haven't found any solutions. I'm very hesitant to even do a simple restart, as a couple of instances like mine that I've read, all SMS history vanished after rebooting. Any thoughts, ideas, or help of any kind would be amazing...and once again, thanks for taking the time.
Edit:The phone in question is a Moto G7 Optimo Maxx(XT1955DL) running stock Android 9, in case this info helps/makes a difference.
Basically what happens is I get old texts from previous conversations as if they were new. They will come in randomly but tend to follow the sequence of the conversation, so it basically replays the conversation but slowly over the day. Seems to affect group chats more. It makes following conversations very hard since they are full of old texts that are not relevant but they show up as new. Also annoying to keep getting notifications when I'm actually waiting for a text only to see that it's an old text that I got days ago.
Current phone is Google Pixel 4A with CalyxOS, but I've also tried Graphene OS and had the same issue. I've tried the stock app as well as QKSMS. I did not get the issue with Signal (using as SMS client) but they dropped support for SMS, so this started back again as soon as I switched off Signal. I even tried putting the sim card in my old phone (stock android) and it's still doing it! This part is strange to me because when this problem first surfaced, doing this did fix the problem.
How do I make this stop or begin troubleshooting this? Nobody in my contacts is having this issue so trying to convince them to switch to another messaging system is kind of futile, this is my problem. I am starting to wonder if I should just get an iphone like everyone else because it just works, but I really hate the closed nature of apple ecosystem.
I was thinking of looking into how to do app development and modify an existing open source client so that it ignores texts that have a send date older than 24h, but before I do that, is there already a text client for Android available in the F droid store or as an APK that would have such a feature?
So this is not just group chats like I thought. Starting to get old texts I got from single conversations now. Even pictures get resent. These show up as new texts, though they still have the original send date. This will at least make it easier to filter these out.
Anyone have an ideas how to make this stop? Driving me insane. I really don't want to have to write my own app.
Anyone? This problem is driving me insane. It started happening with a vengeonce again. I am being bombarded by old texts that I already got days ago. It's just playing out the entire conversation over the course of a few days. Have to put the phone in airplane mode to make it stop otherwise the phone is just lit up non stop with old texts coming in.
At very least is there some kind of logging of sorts I can enable that would help me better troubleshoot this?
Inreally dont know but i Remember this happened to me sometime ,maybe Just try a factory reset or change rom , i dont know
I tried several roms, resets etc. While it was happening I even put the sim card in another phone and it started doing it on that phone too. It's also not a carrier issue since I'm the only person having this issue. I've also tried all sorts of text apps. The only one it didn't do it with was Signal but they dropped SMS support, which really sucks.