My pops got the Moto X, and he's not receiving some texts because of iMessage. I'm sure you've all heard this before.
I'm looking for the best solution if anyone has any information?
By googling, it seems the methods are:
-turn off iMessage on the device
-change password of the apple account
-unregister the apple device
-have the person who is trying to text you delete their text message thread and start a new one
I've done the first 2. The third one I can't seem to do because when I login to the site, the device isn't listed, so I guess it was never registered in the first place?
Besides those first 3, it seems the last one is important. The problem is, how can you know who is having problems and who isn't? So how do you know who to tell to delete the thread?
Does anyone else have any easier methods to quickly resolve this? Any help would really be appreciated.
i would call apple support and see what they say i just did some reading on this issue and there are 100s of different so called fixes but none of them work for everyone. so my best bet for you is to call apple support
but here are some websites that might help you idk apple need to get on there game and get this fixed
The only approved steps so far are to turn off iMessage on your old iPhone, have Apple Support revoke the certificate to disassociate your phone number from iMessage/Facetime, and for anyone using an iPhone to send you messages to update to the newest iOS (7.1 for iPhone 4 and higher, 6.1.6 for 3GS).
Code:
Other possible steps:
1. Go to www.icloud.com and make sure the device is removed from Find My iPhone.
2. Backup and then restore as new your old iPhone.
3. Go to id.apple.com and change your Apple ID's primary email address to something different than it currently shows.
4. Go to id.apple.com and change your Apple ID password
5. Have the other iPhone users delete the existing message thread, delete your contact from their iPhone, backup and restore from backup, and then re-add your contact using only your phone number. Also, make sure they have 'Send as SMS' turned on.
The core issue is usually the other iPhones not sending the message as SMS when it should.
Code:
"If you have access to your iPhone 4 you are going to want to go into the phone and turn your iMessaging off, http://vz.to/1hRAZNz.
If you don’t have access to your iPhone follow the steps below:
Step 1
Go to supportprofile.apple.com/MySupportProfile.do.
Step 2
Log in with your Apple ID and password.
Step 3
Select the product you need to de-register (your iPhone, for example).
Step 4
Click ‘Unregister’.
Step 5
You’ll see the message ‘Are you sure you want to unregister and delete this product?’ – Click ‘Unregister’ again.
other info i read was to put the sim card back in the iPhone. restore the iPhone to stock and then go back threw and make sure imessage and facetime is off. and then to call Apple support and have them revoke your certifications.
the issue is a simple problem the iphones are trying to send you a msg via imessage because there iPhone still thinks you have it. why apple can't find a simple and easy fix is blowing my mind.
how long has this been going on. usually after you process steps 1 and 2.. it clears off after 12-24 hours. if its still not.. then double check your other devices.. is it set up on the ipad? or on an apple computer? those can also interfere... gotta turn off imessage on all devices where the phone/imessage account was set up on.
that happened to me with my when i first picked up my moto x... couldn't figure out what was wrong.. even verizon and apple customer service coudldn't tell.. then i noticed my ipad kept going off with missed notifications.. turned it off there.. and voila! problem solved..
steps 3-5 aren't that important... just 1 and 2 are the key ones...
aldouse said:
how long has this been going on. usually after you process steps 1 and 2.. it clears off after 12-24 hours. if its still not.. then double check your other devices.. is it set up on the ipad? or on an apple computer? those can also interfere... gotta turn off imessage on all devices where the phone/imessage account was set up on.
that happened to me with my when i first picked up my moto x... couldn't figure out what was wrong.. even verizon and apple customer service coudldn't tell.. then i noticed my ipad kept going off with missed notifications.. turned it off there.. and voila! problem solved..
steps 3-5 aren't that important... just 1 and 2 are the key ones...
Click to expand...
Click to collapse
Yeah, I figured I would give it time. They also seemed the most important to me. Question: did you turn iMessage off before you switched devices? I didn't think to do that until a day or 2 after the Moto X was up and running. So I turned iMessage off on the iPhone. It was still connected to WiFi so I assume it could still make the connection to apple's servers to remove that account from iMessage.
dray_jr said:
...the issue is a simple problem the iphones are trying to send you a msg via imessage because there iPhone still thinks you have it. why apple can't find a simple and easy fix is blowing my mind.
Click to expand...
Click to collapse
They have a simple fix - switch back to (or never switch from) iPhone. Just as their lack of a published solution blows your mind, Apple's mind is blown by the fact that anyone who has EVER used an iPhone would EVER choose to use anything else.
With Apple, your once standard SMS becomes needlessly intertwined with iMessage. Stepping into the Apple ecosystem is like stepping into any of the following:
La Brea Tar Pits
Roach Motel
Hotel California
Escape is rare, and often requires outside assistance.
Apple has an official article on this subject; it took me ten seconds to find it via Google...
http://support.apple.com/kb/ts5185
somerandomname1 said:
Yeah, I figured I would give it time. They also seemed the most important to me. Question: did you turn iMessage off before you switched devices? I didn't think to do that until a day or 2 after the Moto X was up and running. So I turned iMessage off on the iPhone. It was still connected to WiFi so I assume it could still make the connection to apple's servers to remove that account from iMessage.
Click to expand...
Click to collapse
No I didn't... And that's what caused it. Had to move the sim card back yo the iPhone, set up Imessage again... Then turn it off. Then finally switched back to the moto x. And then issue resolved almost immediately.
Sent from my XT1060 using Tapatalk
Solutions Etcetera said:
Apple has an official article on this subject; it took me ten seconds to find it via Google...
http://support.apple.com/kb/ts5185
Click to expand...
Click to collapse
and if you would of read the OP you would know he has already done that and still has the problem
dray_jr said:
and if you would of read the OP you would know he has already done that and still has the problem
Click to expand...
Click to collapse
In which case the article suggests contacting Apple support.
I would assume, since it's no secret there can be issues with Apple's cloud services, that there may be times they'd have to give the server a kick from their end.
Also, there is a link at the bottom that accesses another article with more information about unlinking a number from iMessage and FaceTime...
http://support.apple.com/kb/HT5538
Solutions Etcetera said:
Apple has an official article on this subject; it took me ten seconds to find it via Google...
http://support.apple.com/kb/ts5185
Click to expand...
Click to collapse
You can also take 10 seconds to google and see that those instructions are mostly bull**** for a major proportion of people who make the switch. Especially after ios7 which made the "fall back to SMS if iMessage fails to deliver" off by default. People are trying to send via iMessage and when it fails, it doesn't fall back to SMS like it should. People are even continuing to have problems after their iPhone friends/family turn that setting on anyway. It's a really ****ed up system.
You're not supposed to leave iPhone. Can't you take the hint?
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
---------- Post added at 08:51 PM ---------- Previous post was at 08:50 PM ----------
Bet apple goons show up at your door after you've switched....to "persuade " you to return to them. I think they just implemented that procedure.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
somerandomname1 said:
You can also take 10 seconds to google and see that those instructions are mostly bull**** for a major proportion of people who make the switch. Especially after ios7 which made the "fall back to SMS if iMessage fails to deliver" off by default. People are trying to send via iMessage and when it fails, it doesn't fall back to SMS like it should. People are even continuing to have problems after their iPhone friends/family turn that setting on anyway. It's a really ****ed up system.
Click to expand...
Click to collapse
Possibly, but I did not have a problem with it. I simply signed out of all iCloud based accounts before moving to android... with the exception of iCal.
My wife stole my Moto x recently, and finally gave up her just brutal iPhone 4s..(iPhone updated the iPhone 4s into uselessness (slow slow slow)....to sell more 5's I figure)...and yeah, she signed out of imessage first, like I told her..then switched to the Moto x.....and had no issues by the next day.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
I'm glad you guys are getting this working.
I've done every step in this thread and then some and I can't SEND texts to an iPhone, I can receive them with a delay.
Hopefully time will resolve this.
Related
i just installed this Rom on my Nexus:
FRF83-update-nexusone-rooted-signed.zip
i wiped everything before installing and everything is running smooth.
i love the Rom, but i started noticing that ppl kept texting me back ? marks
or saying what was i talking about. i guess texts are scrambling and sending to diff ppl, and im receiving text's under ppl that didnt originally send the text if that makes any sence.
is any one else experiencing this? i remember reading an article about it i think on engadget or gizmodo. but im wondering if its a ROM or Google thing.
in all fairness i did use the search button, no flaming or being rude or else u get a stick trown at you
this has been reported long time ago on 2.1 when the nexus first came out. then other phones reported it like the droid. google never figured out what exactly caused it, it was baffling. i've always used handcent insstead just because of this "possible" glitch. i could get in a lot of trouble if i sent a text to the wrong person.
Weird this is the 1st time its happend to me or any one telling me about it. i rebooted hopefully it wont happen, cause i can also get in trouble sending wrong texts to the wrong person. The GF was already asking ?'s because the text she got wasnt related to anything we talked where texting about.
Android Phones Play “Chat-Roulette” With Your Text Messages
I have always been a big fan of Google Android phones. Sure the user interface may not be as polished as the iPhone. I admit the Exchange support might not be as tightly integrated as it is on the Blackberry. But, I’m a geek and I’m willing to put up with some annoyances as a trade-off for speed and flexibility and customization. And I’m not alone. Market researchers Canalys and NPD Group both recently published reports stating Android was running on > 40% of all smart phones in the United States. It would seem Android is destined for dominance.
Except somewhere along the way, Google seems to have forgotten first and foremost Android phones need to be phones. And that is why I’m seriously considering making the move to Blackberry or Windows Phone 7. For the last six months now I’ve been dealing with a huge flaw that makes my phone unusable for SMS texting. From what I’ve been able to tell using analytics provided by Google’s developer site, as many as 77% of Android phone users are at risk of having their text messages sent to a random contact.
That sounds unlikely right? I mean you pay upwards of $200 for a smart phone, and next to making phone calls, sending SMS text messages is probably the most used feature of the phone. But it’s true, and if you don’t believe me just type “android SMS wrong contact” into Google’s search engine and see how many hits you get. It’s astounding. It’s happening. And Google seems to be ignoring it altogether.
The first time I responded to a text message from recipient A, and it went to recipient B, I just wrote it off to user error. I was in a hurry. I fat fingered it. Who knows, right? In time though I’ve begun to qualify and quantify this serious bug and disaster waiting to happen. The worst part is you don’t even know your text message went to the wrong person until you get a call or new message from someone in your contact list asking “what was that last message all about?”
On the sender’s phone, the text message actually shows as sent to the correct recipient, yet I’ve been able to get all three parties with their phones to sit down in one room and verify that in fact the intended recipient did not receive my text, and a random contact did. I will put up with a lot of minor issues for a cool phone, but having my privacy threatened is not one of them.
What irks me the most is that owners of these phones, me included, have no recourse. The bug is part of the core operating system, and has been since Android 2.1, (though it seems worse with 2.2). Phone model doesn’t matter. Using a third-party SMS application won’t help. Contact your phone carrier and you will be told to do a factory reset then call the phone manufacturer. Contact the manufacturer and you will be told to do a factory reset then get in touch with your carrier. This is a flaw with Google’s code so how is it they managed to slip out of the support loop altogether?
Ah, I think now we have reached the heart of the problem haven’t we? By making it an open source solution, Google isn’t really accountable. Or are they? I guess that depends on you and me. Google has a vested interest in fixing any flaws that are impacting their continued effort for world smart phone dominance. If those of us who have made this platform so successful for them draw a line in the sand perhaps someone at Google will take notice.
The issue at hand has been logged in the Google forums for some time now. Sadly, it’s rated as only having a priority of “medium” and I’ve yet to see anyone from Google comment on the current state. I would urge any of you who have Android phones to log into the Google forum and star the issue. You can find the link in the code google forums. In the mean time, I’m going to continue evaluating some of the new Windows phone offerings. Just in case Google decides new UI bounce effects on widgets are more important than where my SMS text messages end up.
I've never had a text message go astray, personally.
I just had this about two or three times.
The chosen recipient didn't got my text message. But to be honest, noone contacted me, that he got my message, and the reciplient has a very bad mobile network coverage. So hopefully noone is laughing his ass off about my stupid messages
Attackers could force phones from Google's Nexus line to reboot or fail to connect to the mobile Internet service by sending a large number of special SMS messages to them.
The issue was discovered by Bogdan Alecu, a system administrator at Dutch IT services company Levi9, and affects all Android 4.x firmware versions on Google Galaxy Nexus, Nexus 4 and Nexus 5. Alecu is presenting the vulnerability Friday at the DefCamp security conference in Bucharest, Romania.
Class 0 SMS, or Flash SMS, is a type of message defined in the GSM specification that gets displayed directly on the phone's screen and doesn't automatically get stored on the device. After reading such a message, users have the option to save it or dismiss it.
On Google Nexus phones, when such a message is received, it gets displayed on top of all active windows and is surrounded by a semi-transparent black overlay that has a dimming effect on the rest of the screen. If that first message is not saved or dismissed, and a second message is then received, the latter is placed on top of the first one and the dimming effect increases.
When such messages are received, there is no audio notification, even if one is configured for regular incoming SMS messages. This means that users receiving Flash messages won't know about them until they look at the phone.
Alecu found that when a large number of Flash messages—around 30—are received and are not dismissed, the Nexus devices act in unusual ways.
The most common behavior is that the phone reboots, he said. In this case, if a PIN is required to unlock the SIM card, the phone will not connect to the network after the reboot and the user might not notice the problem for hours, until they look at the phone. During this time the phone won't be able to receive calls, messages or other types of notifications that require a mobile network connection.
According to Alecu, a different behavior that happens on rare occasions is that the phone doesn't reboot, but temporarily loses connection to the mobile network. The connection is automatically restored and the phone can receive and make calls, but can no longer access the Internet over the mobile network. The only method to restore the data connection is to restart the phone, Alecu said.
On other rare occasions, only the messaging app crashes, but the system automatically restarts it, so there is no long term impact.
A live test at the conference performed on a Nexus 4 phone with the screen unlocked and running Android 4.3 did not immediately result in a reboot. However, after receiving around 30 class 0 messages the phone became unresponsive: Screen taps or attempts to lock the screen had no effect. While in this state, the phone could not receive calls and had to be rebooted manually.
A second attempt with the screen locked also failed to reboot the phone because only two of over 20 messages were immediately received. This may have been caused by a network issue or operator-imposed rate limiting. The messages did arrive later and the phone rebooted when unlocking the screen.
Alecu said that he discovered this denial-of-service issue over a year ago and has since tested and confirmed it on Google Galaxy Nexus, Nexus 4 and Nexus 5 phones running various Android 4.x versions, including the newly released Android 4.4, or KitKat.
Around 20 different devices from various vendors have also been tested and are not vulnerable to this problem, he said.
This doesn't exclude the possibility that some devices from other vendors are vulnerable, but so far it has only been confirmed on the previously mentioned Google Nexus phones.
Alecu claims he contacted Google several times since he found the flaw, but mostly got automated responses. Someone from the Android Security Team responded in July and said the issue would be fixed in Android 4.3, but it wasn't, Alecu said, adding that this contributed to his decision to disclose the problem publicly.
"We thank him for bringing the possible issue to our attention and we are investigating," a Google representative said via email.
via PCWorld
Click to expand...
Click to collapse
What is your intake on this?
Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
TLDR
joke, Well since I can't achieve the effect (reboot and unusual behaviour) I am saying this doesn't affect my life & the way my nexus works.. so..
Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
My ... ummm, intake ... on this is that I never cease to be amazed at the lengths that a corporate security weenie will go to in order to justify his salary.
I recently retired from a large IT services firm in the US, and this is exactly the kind of far-fetched crap our corporate security people cited to justify taking away my Android connectivity to our Exchange servers. Grrrr...
JM2¢
Last I checked, only the provider can send class 0 messages.
This. No one can send them, and almost no carriers... at least in the U.S. use them. I have never seen a single one. The chances of getting 30 at one time is zero. It's a non-issue IMO.
If you want a crash bug, look to the iOS bug that caused any iOS phone or app to crash when a certain string of characters is displayed by it.
Unfortunately there is software out there that allows a user to send an anonymous class 0 sms messages, so I guess this bug needs looking at by the Google techies
Sent from my Nexus 5 using Tapatalk
I don't have a take on this
Sent from my Nexus 5 using Tapatalk
I award you no points & may God have mercy on your soul.
Lol but seriously, is this REALLY an issue?
Sent from my Nexus 5 using Tapatalk
cbutt said:
I award you no points & may God have mercy on your soul.
Lol but seriously, is this REALLY an issue?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I'm not really concerned about this, just thought I'd create a discussion about it. Don't worry about my soul, my friend.
Sent from my Nexus 5 using Tapatalk
If anyone is that worried, ... https://play.google.com/store/apps/details?id=com.silentservices.class0firewall
Deeco7 said:
What is your intake on this?
Click to expand...
Click to collapse
Meh... It's just a bug. Can be inconvenient if you reboot and don't connect to your network until you insert your PIN, but there are no security issues mentioned.
I'd be more worried about the bug in many american cell subscriptions that share SMS cost between sender and receiver. But fortunately I live in a sane country where only the sender pays for the messages
Hello,
I've been trying to figure this out for days now and I can't seem to find any permanent solution. My Nexus 6 on Sprint (Android L 5.0 / LRX21O / Up to Date PRL) 50%-75% of the time sends duplicate SMS messages to recipients. On my end I see one SMS message outbound and it sends without issue. On the other end, people will get the same message one to six times. I've seen it myself on a separate Sprint phone and a Verizon phone.
From what I can tell, sometimes updating the profile helps for a few minutes and that's it. It doesn't matter if I uninstall/disable the stock Google Messenger or Hangouts. This issue happens in every single 3rd party SMS messenger I've used. The only time I've got the problem to stop is if I force 3G service and not the Global or LTE settings. Strangely enough, If I'm on LTE, and I switch to WiFi, the issue remains. If I force 3G and then go on WiFi, the issue is gone.
I've tried uninstalling certain applications that come stock with the phone.. I've tried not updating any applications. I've done factory resets (and I sent an SMS to test without doing 1 update) and it still duplicated. I returned the phone and got another phone. Same issue. On the Sprint end, they changed some settings on my phone and had me reset the network connection via the phone *#*# etc. menu. That fixed the issue, and it lasted 24 hours. Upon either a reboot, or perhaps just a power cycle, the problem returned.
Any ideas as to why this is happening? I have zero Data issues. Hangouts works fine. Youtube, Gmail, Chrome etc are all super fast without issue.
Thank you in advance.
off1c3r said:
Hello,
I've been trying to figure this out for days now and I can't seem to find any permanent solution. My Nexus 6 on Sprint (Android L 5.0 / LRX21O / Up to Date PRL) 50%-75% of the time sends duplicate SMS messages to recipients. On my end I see one SMS message outbound and it sends without issue. On the other end, people will get the same message one to six times. I've seen it myself on a separate Sprint phone and a Verizon phone.
From what I can tell, sometimes updating the profile helps for a few minutes and that's it. It doesn't matter if I uninstall/disable the stock Google Messenger or Hangouts. This issue happens in every single 3rd party SMS messenger I've used. The only time I've got the problem to stop is if I force 3G service and not the Global or LTE settings. Strangely enough, If I'm on LTE, and I switch to WiFi, the issue remains. If I force 3G and then go on WiFi, the issue is gone.
I've tried uninstalling certain applications that come stock with the phone.. I've tried not updating any applications. I've done factory resets (and I sent an SMS to test without doing 1 update) and it still duplicated. I returned the phone and got another phone. Same issue. On the Sprint end, they changed some settings on my phone and had me reset the network connection via the phone *#*# etc. menu. That fixed the issue, and it lasted 24 hours. Upon either a reboot, or perhaps just a power cycle, the problem returned.
Any ideas as to why this is happening? I have zero Data issues. Hangouts works fine. Youtube, Gmail, Chrome etc are all super fast without issue.
Thank you in advance.
Click to expand...
Click to collapse
I always just thought this was an issue on Sprints side and not the phone itself. I just started with Sprint myself when I picked up the Nexus, prior to this I had Verizon.
My girlfriend however has been with Sprint forever and no matter what ROM or phone she had, this issue would pop up from time to time.
Now that I'm with Sprint she's told me a few times that she's gotten duplicate messages from me. It seems to happen when we are in spotty service areas from what I can tell. I haven't even bothered calling Sprint like you have though... I just chalked it up as Sprint service is sketchy.
Mistertac said:
I always just thought this was an issue on Sprints side and not the phone itself. I just started with Sprint myself when I picked up the Nexus, prior to this I had Verizon.
My girlfriend however has been with Sprint forever and no matter what ROM or phone she had, this issue would pop up from time to time.
Now that I'm with Sprint she's told me a few times that she's gotten duplicate messages from me. It seems to happen when we are in spotty service areas from what I can tell. I haven't even bothered calling Sprint like you have though... I just chalked it up as Sprint service is sketchy.
Click to expand...
Click to collapse
The issue here is that it's not popping up from time to time...it's pretty consistent. I've been with Sprint for at least 7 years and have never ran into the issue until this phone. My prior phone was a Nexus 5...and I have a galaxy s3 here which I can't duplicate the issue on.
We all need to complain to Sprint so they either fix it on their side, or put pressure on Google to fix it on their own side.
---------- Post added at 06:07 AM ---------- Previous post was at 06:04 AM ----------
Let Sprint know you're experiencing the issue here: https://community.sprint.com/baw/thread/179054
Call and complain, perhaps we should also complain to google? Here is their Nexus 6 product forum: https://productforums.google.com/forum/#!categories/nexus/nexus-6
iil said:
The issue here is that it's not popping up from time to time...it's pretty consistent. I've been with Sprint for at least 7 years and have never ran into the issue until this phone. My prior phone was a Nexus 5...and I have a galaxy s3 here which I can't duplicate the issue on.
We all need to complain to Sprint so they either fix it on their side, or put pressure on Google to fix it on their own side.
---------- Post added at 06:07 AM ---------- Previous post was at 06:04 AM ----------
Let Sprint know you're experiencing the issue here: https://community.sprint.com/baw/thread/179054
Call and complain, perhaps we should also complain to google? Here is their Nexus 6 product forum: https://productforums.google.com/forum/#!categories/nexus/nexus-6
Click to expand...
Click to collapse
I'll try and contact them today if I have time. Its worth a shot right?!
Let me know how you make out and I'll do the same. Thanks for the links
This phone is really flaky for me with SMS. Doesn't want to send when I am on wifi. My wife did get a duplicate from me one night when I was trying to figure out why it won;t send when wifi is on but she hasn't mentioned it since. ( I am on Sprint)
Evo_Shift said:
This phone is really flaky for me with SMS. Doesn't want to send when I am on wifi. My wife did get a duplicate from me one night when I was trying to figure out why it won;t send when wifi is on but she hasn't mentioned it since. ( I am on Sprint)
Click to expand...
Click to collapse
What SMS application are you using? Did you install any 3rd part SMS applications?
off1c3r said:
Hello,
I've been trying to figure this out for days now and I can't seem to find any permanent solution. My Nexus 6 on Sprint (Android L 5.0 / LRX21O / Up to Date PRL) 50%-75% of the time sends duplicate SMS messages to recipients. On my end I see one SMS message outbound and it sends without issue. On the other end, people will get the same message one to six times. I've seen it myself on a separate Sprint phone and a Verizon phone.
From what I can tell, sometimes updating the profile helps for a few minutes and that's it. It doesn't matter if I uninstall/disable the stock Google Messenger or Hangouts. This issue happens in every single 3rd party SMS messenger I've used. The only time I've got the problem to stop is if I force 3G service and not the Global or LTE settings. Strangely enough, If I'm on LTE, and I switch to WiFi, the issue remains. If I force 3G and then go on WiFi, the issue is gone.
I've tried uninstalling certain applications that come stock with the phone.. I've tried not updating any applications. I've done factory resets (and I sent an SMS to test without doing 1 update) and it still duplicated. I returned the phone and got another phone. Same issue. On the Sprint end, they changed some settings on my phone and had me reset the network connection via the phone *#*# etc. menu. That fixed the issue, and it lasted 24 hours. Upon either a reboot, or perhaps just a power cycle, the problem returned.
Any ideas as to why this is happening? I have zero Data issues. Hangouts works fine. Youtube, Gmail, Chrome etc are all super fast without issue.
Thank you in advance.
Click to expand...
Click to collapse
Yep, this has been happening to me. My girlfriend started complaining she was getting my text 2x-3x for each message. She is on T-Mo, I'm on Sprint. Tested with a few coworkers on different providers and only 1 out 4 received it more than once and they are on Verizon. Rebooted, tried updating PRL and data profile. She hasn't complained about it doing it anymore but we will see. Super frustrating
unregistered825 said:
What SMS application are you using? Did you install any 3rd part SMS applications?
Click to expand...
Click to collapse
Just google messenger.
Evo_Shift said:
Just google messenger.
Click to expand...
Click to collapse
I've tried every combination you can think of:
1. Google Messenger as default with and without Hangouts installed.
2. Hangouts as default with and without Google Messenger installed.
3. SMS Messenger AOSP, ChompSMS, 8sms, Textra, Handcent, all with and without Google Messenger and or Hangouts installed.
I've tried forcing 1x, updating PRL and Profile and then going back to LTE. Same issue. Multiple Hard Resets and Data Network Resets. Only ONCE the Sprint support person did something on their end ("Changed a number") and out of nowhere the duplicates stopped. But it only lasted 1 day while using Google Messenger.
This happened to me with my G3 on Att, it just stopped one day and I still don't know what started it
Mistertac said:
I'll try and contact them today if I have time. Its worth a shot right?!
Let me know how you make out and I'll do the same. Thanks for the links
Click to expand...
Click to collapse
I posted on the Sprint Community page. I'm glad others are finding this issue too.
off1c3r said:
I posted on the Sprint Community page. I'm glad others are finding this issue too.
Click to expand...
Click to collapse
I just joined you over on the Community Page as well.. Guess we'll see how it plays out, although I must admit I don't have much faith this will get fixed lol
But, I'm willing to take it the distance in an effort to try!!
Evo_Shift said:
This phone is really flaky for me with SMS. Doesn't want to send when I am on wifi. My wife did get a duplicate from me one night when I was trying to figure out why it won;t send when wifi is on but she hasn't mentioned it since. ( I am on Sprint)
Click to expand...
Click to collapse
I'm having the same exact issue
Mistertac said:
I just joined you over on the Community Page as well.. Guess we'll see how it plays out, although I must admit I don't have much faith this will get fixed lol
But, I'm willing to take it the distance in an effort to try!!
Click to expand...
Click to collapse
Lol. Yeah. Doesn't hurt. I'm on the phone with Sprint again and they said they are making a ticket with their engineers.
Just picked mine up today from sprint. My buddy who is also on sprint made me aware that he was getting repeat sms from me already. It's funny because I would always complain that I was getting them from him before I jumped to sprint. He's on a LG G2 though.
kmmxracer said:
Just picked mine up today from sprint. My buddy who is also on sprint made me aware that he was getting repeat sms from me already. It's funny because I would always complain that I was getting them from him before I jumped to sprint. He's on a LG G2 though.
Click to expand...
Click to collapse
Don't get me wrong.. the phone is absolutely amazing. I love it. I can't go back to my Moto X, which to me was one of the best Android phones ever made. Again, what people don't understand is this is a REAL issue. People are very quick to say that "bad service" caused it. We're all smart enough to know that if you have bad service, 1 or 2 duplicates can happen, on occasion. Not repeatedly in a full service area or on WiFi.
As an Update:
Everything Sprint tried has failed. However, my original debug information holds true:
1. If the phone is set to 3G mode only: The problem is SOLVED.
2. If the phone is on WiFi, AFTER being set to 3G mode only: The problem is SOLVED.
3. If the phone is set to LTE mode only: The problem REMAINS, unless you are in a no LTE service area and revert to 3G or less.
4. If the phone is on WiFi, AFTER being set to LTE mode only: The problem REMAINS.
kmmxracer said:
Just picked mine up today from sprint. My buddy who is also on sprint made me aware that he was getting repeat sms from me already. It's funny because I would always complain that I was getting them from him before I jumped to sprint. He's on a LG G2 though.
Click to expand...
Click to collapse
Please post to the Sprint forums of your issue here: https://community.sprint.com/baw/thread/179054
Somebody also started a thread in the Nexus forum: https://productforums.google.com/forum/#!category-topic/nexus/nexus-6/JM44M3bofBc
Well both me and my girlfriend have reset the network settings from the dialer like suggested, so I guess today we'll see if that helps.
She's already complained of getting my messages 4x a piece this morning, so I'm thinking positive!
iil said:
Please post to the Sprint forums of your issue here: https://community.sprint.com/baw/thread/179054
Somebody also started a thread in the Nexus forum: https://productforums.google.com/forum/#!category-topic/nexus/nexus-6/JM44M3bofBc
Click to expand...
Click to collapse
I just posted my issue.
When there is going to be a thread for Urbane 2nd gen? It is out for almost a week now. I can not believe that nobody got it?
That's a good question. I am also waiting for it.
Came here to ask the same question. Lots of other people have it on android central forms. Please create a thread!!
I agree. I have one and keep checking back here
Your experience with the Urbane 2 LTE
Hi there, I'm also waiting on a forum. But, in the meantime, I'm thinking seriously about buying an Urbane 2 LTE, but have several concerns and thought perhaps you guys might be able to answer them. And all of my questions relate to when it is NOT connected to my smartphone.
1. Will it send and receive calls even when connected to wifi (I don't mean through wifi as I know that isn't possible)? I read in one review that this was a problem.
2. Can I receive my Exchange email through the watch?
3. Are you able to connect to a secured wifi network (i.e., insert a password) without being connected to your phone? Again, this concern came up in a recent review.
4. Can the watch accept Google Voice text messages?
5. How is the call quality talking (for the person you call) and listening (is the speaker loud enough under normal conditions)?
6. Can you easily connect the watch to a bluetooth headset?
7. How is OK Google working? One reviewer said it failed a bunch.
8. How well does it maintain a steady data connection with a link to a phone? Another reviewer concern.
9.
FYI, verizon launch was canceled and all pre-orders orders will be canceled. Big red strikes again.
Same here. I got mine from AT&T on Tuesday. Love it so far.
---------- Post added at 09:34 AM ---------- Previous post was at 09:11 AM ----------
drjim said:
Hi there, I'm also waiting on a forum. But, in the meantime, I'm thinking seriously about buying an Urbane 2 LTE, but have several concerns and thought perhaps you guys might be able to answer them. And all of my questions relate to when it is NOT connected to my smartphone.
1. Will it send and receive calls even when connected to wifi (I don't mean through wifi as I know that isn't possible)? I read in one review that this was a problem.
2. Can I receive my Exchange email through the watch?
3. Are you able to connect to a secured wifi network (i.e., insert a password) without being connected to your phone? Again, this concern came up in a recent review.
4. Can the watch accept Google Voice text messages?
5. How is the call quality talking (for the person you call) and listening (is the speaker loud enough under normal conditions)?
6. Can you easily connect the watch to a bluetooth headset?
7. How is OK Google working? One reviewer said it failed a bunch.
8. How well does it maintain a steady data connection with a link to a phone? Another reviewer concern.
9.
Click to expand...
Click to collapse
My experiences so far on the AT&T Urbane LTE and a T-Mobile Galaxy Note 5:
1. Yes, as far as I can tell as it has its own SIM card, so it has a full cellular radio in it and has its own phone # assigned to it.
2. I don't think it has a full email client on it that I have found anyway. I am also an exchange user trying to find how to get notifications.
3. Yes, you can join WiFi networks that use a passkey/password, but nothing certificate based. Mine pulled the ones my phone knew of.
4. Kind-of. I took the Phone # assigned to the watch and added it to Google Voice as another phone. The notifications I get on a GV Text Message show the random numbers that GV uses as a portal, not the actual # of the person sending me a text message. I don't think there is a google voice app for android wear. At least not one I have found.
5. I think the call quality from the watch itself is quite good. Plenty loud enough and definitely clear. I wouldn't use it often, but in a pinch I wouldn't hesitate to use it either.
6. I have not tried this yet, but I will and let you know.
7. OK Google has not failed me yet. It is responsive and works just like it would on a Nexus Phone as far as I can tell.
8. As far as I can tell, the connection (bluetooth) between my Note 5 and the Urbane is quite robust. I went down the hall to the restroom in my office and left my phone on my desk. I had a phone call on my Note 5 while I was away from my desk and it "rang" on my watch just fine.
As an afterthought, it is probably worth noting that as I am not a current AT&T customer, I bought the watch outright with no contract for $299 so I wasn't locked into a data plan more than month-to-month. As such, I am currently paying a ridiculous $30 a month for a measly 300MB of data for the watch by itself and I am still trying to determine exactly how, when, where, and why it uses data on its own 3G/LTE radio.
I don't plan to separate the watch and my phone often, and I can't see the need to make a voice call on the watch without using my phone, so I am not sure I am going to keep the data plan from AT&T until I learn more about how it works. I have one of those "free" 200MB per month SIM cards from T-Mobile, and I can tell you the watch does NOT appear to be SIM-locked, much to my surprise.
More experimentation to follow. I'd love to hear what others have learned in using theirs thus far.
-Rob
Great insights!
robroy90 said:
Same here. I got mine from AT&T on Tuesday. Love it so far.
---------- Post added at 09:34 AM ---------- Previous post was at 09:11 AM ----------
My experiences so far on the AT&T Urbane LTE and a T-Mobile Galaxy Note 5:
1. Yes, as far as I can tell as it has its own SIM card, so it has a full cellular radio in it and has its own phone # assigned to it.
2. I don't think it has a full email client on it that I have found anyway. I am also an exchange user trying to find how to get notifications.
3. Yes, you can join WiFi networks that use a passkey/password, but nothing certificate based. Mine pulled the ones my phone knew of.
4. Kind-of. I took the Phone # assigned to the watch and added it to Google Voice as another phone. The notifications I get on a GV Text Message show the random numbers that GV uses as a portal, not the actual # of the person sending me a text message. I don't think there is a google voice app for android wear. At least not one I have found.
5. I think the call quality from the watch itself is quite good. Plenty loud enough and definitely clear. I wouldn't use it often, but in a pinch I wouldn't hesitate to use it either.
6. I have not tried this yet, but I will and let you know.
7. OK Google has not failed me yet. It is responsive and works just like it would on a Nexus Phone as far as I can tell.
8. As far as I can tell, the connection (bluetooth) between my Note 5 and the Urbane is quite robust. I went down the hall to the restroom in my office and left my phone on my desk. I had a phone call on my Note 5 while I was away from my desk and it "rang" on my watch just fine.
As an afterthought, it is probably worth noting that as I am not a current AT&T customer, I bought the watch outright with no contract for $299 so I wasn't locked into a data plan more than month-to-month. As such, I am currently paying a ridiculous $30 a month for a measly 300MB of data for the watch by itself and I am still trying to determine exactly how, when, where, and why it uses data on its own 3G/LTE radio.
I don't plan to separate the watch and my phone often, and I can't see the need to make a voice call on the watch without using my phone, so I am not sure I am going to keep the data plan from AT&T until I learn more about how it works. I have one of those "free" 200MB per month SIM cards from T-Mobile, and I can tell you the watch does NOT appear to be SIM-locked, much to my surprise.
More experimentation to follow. I'd love to hear what others have learned in using theirs thus far.
-Rob
Click to expand...
Click to collapse
Really helpful, Rob! I can't wait till xda gets a forum for this smarthwatch.
I had a typo for #8. I'm interested in the quality and consistency of the data connection when NOT connected to your phone.
A few follow-up questions.
1. So it sounds like you receive GV text messages even with a funky sender #. But can you also send texts through GV? I seem recall reading that Hangouts (into which GV is now integrated) has a smartwatch app. But I find Hangouts cumbersome because you have to go through several screens to just get to text messages.
2. Without Exchange, what are you doing about email? I emailed an called Nine that appears to do what we want, but haven't heard back. Will report when I do.
I'm going to test out a U2 (that's a much better shortened name!) this morning and will report back if I learn anything.
Many thanks!
I just downloaded and installed the Nine email client. It seems to work great, but I can't figure out how or where to enable Wear notifications.
robroy90 said:
I just downloaded and installed the Nine email client. It seems to work great, but I can't figure out how or where to enable Wear notifications.
Click to expand...
Click to collapse
I haven't explored it much yet. Did you install Nine on your watch as well? Perhaps go to their customer support and email them?
drjim said:
I haven't explored it much yet. Did you install Nine on your watch as well? Perhaps go to their customer support and email them?
Click to expand...
Click to collapse
I didn't see an option to install it on the watch. I sent a query to them.
robroy90 said:
I didn't see an option to install it on the watch. I sent a query to them.
Click to expand...
Click to collapse
Here a few possibilities:
https://play.google.com/store/apps/details?id=me.bluemail.mail
https://play.google.com/store/apps/details?id=com.microsoft.office.outlook
None of them indicate specifically about standalone smartwatches, but they say they are for Android Wear.
Also, do you have a gmail account? I believe there is a way to have Exchange email forwarded to gmail and have emails from gmail to show your Exchange email address.
Oh, is there a keyboard for inputting texts and emails?
BTW, did you see this app? Looks really practical: https://play.google.com/store/apps/details?id=com.npi.wearminilauncher
It looks like something happened. Watch are out of stock on AT&T web site, Verizon cancelled pre orders and no information on LG web site about watch.
I Will have to wait much longer than i expected for availability in europe.
@robroy90 hey dude when you make your wirst go up.. does it push the crown everytime.. would be cool if we could put the watch on the other hand and the screen will rotate accordingly
LG Watch Urbane 2 has been canceled indefinitely
http://www.techradar.com/news/wearables/lg-urbane-2-has-been-canceled-indefinitely-1309332
while I have an love mine, I am still going to wait for a more detailed reason other then Unspecified Hardware Issue. I had it for a week tomorrow and the only issue I have is LTE connection is spotty at best, it seems to be stuck mostly on HSPA
One negative effect is see from this is software updates. When I had the LG G watch, I remember that being rooted. So if this "issue" is nothing to major, maybe someone with the experience will be able to root this beast so we can essentially still have updates, just not from LG specifically
Wow. I wonder why they were shelved? I was going to upgrade to this from a G Watch.
Maybe we can find them on a fire clearance sale?
chachin said:
@robroy90 hey dude when you make your wirst go up.. does it push the crown everytime.. would be cool if we could put the watch on the other hand and the screen will rotate accordingly
Click to expand...
Click to collapse
I have no issues with gestures engaging the crown button. I am not sure I follow the second part of your comment.
---------- Post added at 07:47 AM ---------- Previous post was at 07:44 AM ----------
Wow, glad I grabbed mine so aggressively when I did. I am not going to blindly just return mine (unless my wrist catches on fire... lol). I would like a detailed explanation on what this "serious hardware issue is". As far as it maybe being an issue where it drops to HSPA in an otherwise strong LTE service area, I could not care less. I don't think my watch needs the blazing fast speeds of LTE anyway. Someone posted about how cool it would be for it to be a hotspot?!? What, for 10 minutes before the battery dies... LOL. I am happy, and unless mine starts acting really wonky, I am definitely keeping it.
Well regardless of possible reasons, I'll be keeping mine. Yeah its only been a few days with the watch, but it has been a few days of heavy usage bliss. This is the first smart watch, that I have ever used, that does everything well, (well at least the things that are important for me to have in a smartwatch). So a later patch not coming for my device, (can't speak for others owners), won't be so bad for me, since everything I want to work....works great already, and if I return it, what other option is out there? All the other watches I tried don't work as good as this one for the things I want to work.....and this one has the best battery life to boot. Besides, I don't know why everyone thinks a software update won't come. Google controls android wear, an I don't think their going to not update their software.
If they scrap this one and release a new one a year from now, I'll check out that option when that bridge is crossed, but in the mean time, i'm keeping this bad boy.
Oh and if anyone has every used watchmaker before (lets you design your own watch faces), It appears to be working great for me. Just a heads up.
I was lucky enough to buy one of these from AT&T without a contract a couple of days before they were pulled. So far the watch is great. Battery life is good, calls are clear, and the screen is big and bright. However, there is one major flaw: You can't pair a Bluetooth headset to the watch and use it for voice calls. I tried a few different Bluetooth headsets, and they can only be used for audio playback. The only way to send and receive voice calls is using the integrated speaker and microphone on the watch. Another minor annoyance is you must have the phone with you to connect to a new WiFi network. If you try to connect to a new WiFi network using the settings on the watch, it asks you to enter the password on the phone.
The inability to use a Bluetooth headset for calls is pretty big weakness compared to other smart watches, but probably not severe enough to pull the watches from the shelves. Maybe it has something to do with the fact that the device is unlocked, and it is so easy to switch carriers without a contract. Also, AT&T was offering this device at the same cost of an LTE tablet ($10/month), but the watch has a SIM that supports both voice and data which usually costs 3-4 times as much. I tried using the watch SIM in an Android smartphone, and it seemed to work fine.
A couple months ago I got my 12 year old his first phone, the Moto G6. Since day 1, there has been a strange texting issue. He can't receive a text from his mom if he is the only recipient. If it's a group text, like to all 3 of our kids, he can get the text. This issue only happens with texts from his mom. All the rest of us are not impacted. He can send a text to her, and it goes through just fine. The issue is only on inbound text and only from his mom.
I'm hoping someone here in XDA can offer some trouble-shooting ideas. Here are the variables that I know:
He is on the Sprint BYOD plan and his mom has an iPhone on Verizon. His phone is stock, no mods at all.
We have been to Sprint, Verizon, and the Apple store. No one knows how to fix.
Sometimes issues happen like this because of Apple iMessage. Does his mother own any other Apple devices under the same Apple ID? She might try signing out of and back into iMessage and/or going to Settings --> Messages and turning iMessage off and back on. She might also try toggling "Send as SMS" on if it isn't already. Let me know if any of these resolve the issue but the problem is definitely on the Apple side, somewhere in the iMessage settings. This happened to my wife when she switched from an iPhone to an Android phone, and she couldn't get texts from her mom's iPhone at first.