Related
Hello,
Ever since I have gotten this phone, I have run into problems occasionally with messages failing to send out. They simply get stuck at "sending".
Mtmichaelson informed me that on the VZW community forums this is a main complaint of the phone. I spoke with tech support and of course they said they have never heard of this before and simply wanted me to perform a factory reset (Which I had already done previously, even before I was rooted) . I even went out to get a new sim card.
Today though, I think I may have found out what causes it. It appears it's happening from sending messages consecutively too fast.
For example, say I sent you a message at 11:00:01 AM saying "SCREW", followed by "YOU" at 11:00:04 while the first message is still attempting to send. (It doesn't always happen, but when it does its usually from sending messages consecutively too fast. At least with my own testing)
The first one will send and the second one will fail to send, along with any other messages you attempt to send, until you either put your phone in airplane mode or reboot.
I have corrected the situation by using Handcent and applying a 1.5 second delay of when I press send. Now, my texting problems have been solved. (Hopefully)
I live in Houston and there have been no reports of VZW network issues here, and I've had a Tbolt and a Charge and never had this issue.
Thanks,
Samsuck
I've run into the same thing numerous times. Always seem to happen when im in a low signal area.
Do you ever have the issue where only half of 2 part messages comes through?
yup.. i have problems with low signal texts, and im not a big handcent fan... can never get the stock notifications to stop so i always get two notifications per sms/mms... oh well.
xjli said:
yup.. i have problems with low signal texts, and im not a big handcent fan... can never get the stock notifications to stop so i always get two notifications per sms/mms... oh well.
Click to expand...
Click to collapse
I actually prefer GO SMS but the lack of nice free themes suck.
All you have to do is go to your stock messaging app, hit menu, settings, and scroll down to notifications, and turn it off
Sigh..
Nevermind.
Sent from my VS910 4G using XDA App
This is the biggest, most frustrating thing I've ever experienced. I'm glad I'm not the only person, but this is my only gripe with this phone.
When all my messages get stuck in "sending" I have to put it in airplanes mode one time for every message I'm trying to send.
I also have a horrible problem with not receiving all the sections of long text message.
Sent from my VS910 4G using XDA App
Samsuck said:
Sigh..
Nevermind.
Click to expand...
Click to collapse
i guess turning notifications off didnt work? lol
xjli said:
i guess turning notifications off didnt work? lol
Click to expand...
Click to collapse
That's not it, me setting a delay in handcent to prevent the texting issue didn't work.
Unfortunately, I think I may have to get a new phone, this is happening way too often, and as much as I love the phone, and Revolt rom. I am tired of my girlfriend *****ing at me for not replying, when I have it's just that I encounter the "stuck at sending" problem, at least 3 times a day
Samsuck said:
That's not it, me setting a delay in handcent to prevent the texting issue didn't work.
Unfortunately, I think I may have to get a new phone, this is happening way too often, and as much as I love the phone, and Revolt rom. I am tired of my girlfriend *****ing at me for not replying, when I have it's just that I encounter the "stuck at sending" problem, at least 3 times a day
Click to expand...
Click to collapse
Mine has only gotten stuck twice, but both times I cleared it by calling voicemail. Worth a try, easier than a reboot.
Sent from my VS910 4G using xda premium
mine only gets stuck when i have pretty much no service.. like cant make a phone call use data only type of service. otherwise, no issues.
This still happens to me alot
Sent from my VS910 4G using XDA App
one solution i just read is to delete your texts. once they start to become full the phone has a problem sending. try erasing your threads then it should work. i just googled this problem since i ran into it and am testing it now
I will be following this as it happens to me excessively.
Same here. i thought it had something to do with the handoff between wifi and 4G, but after reading this thread, I'm not so sure. For me it always seems to happen when I've been connected to a wifi network and switched to 4G. I'm testing not running wifi at all today to see if it happens again.
Same problem here. I concur that it appears to be an issue with sending text messages "too quickly."
I also called Verizon, got bumped up to "Tier 2 Support" and spent well over an hour on the phone doing every little thing they asked. I am going to try using the Handcent delay feature and see if that helps.
For those of us on Revolt...Does anyone know if/think it may have something to do with v1.5 still using V4 and not having the latest radio update? Or is this a problem for those using the stock rom and V6 as well?
jamRwoo said:
Same problem here. I concur that it appears to be an issue with sending text messages "too quickly."
I also called Verizon, got bumped up to "Tier 2 Support" and spent well over an hour on the phone doing every little thing they asked. I am going to try using the Handcent delay feature and see if that helps.
For those of us on Revolt...Does anyone know if/think it may have something to do with v1.5 still using V4 and not having the latest radio update? Or is this a problem for those using the stock rom and V6 as well?
Click to expand...
Click to collapse
Yup, sending messages to quickly is my theory as well but the handcent delay didn't work for me. I set it to 1.5 seconds which I figured should be enough.
Do any devs have any insight on how or why this may be occuring? It'd be awesome if someone knew of a fix. I'm pretty confident that it's a software issue and not phone related
Samsuck said:
Do any devs have any insight on how or why this may be occuring? It'd be awesome if someone knew of a fix. I'm pretty confident that it's a software issue and not phone related
Click to expand...
Click to collapse
It happens when your text threads are full. If you erase your texts they send. The the revolution had trouble with dealing with the threads
Sent from my VS910 4G using Tapatalk
jackpot08 said:
It happens when your text threads are full. If you erase your texts they send. The the revolution had trouble with dealing with the threads
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
I really don't think that has anything to do with it. The threads can't get "full" unless you set a limit (which I didn't), and I was still having the issue even after deleting all of my texts (one of the many things Verizon had me do on the phone). I'm no dev, so I could be wrong about this, but I feel like a fix that easy would've been diagnosed by now.
I agree it's a software issue of some sort...it doesn't seem consistent enough to be a hardware issue. There's threads on the LG forums about it. The handcent delay seems to have helped me, or at least I don't find myself wanting to throw my phone across the room as frequently.
On a lighter note, while on the phone with Verizon, the lady had me turn off my WiFi because "When it's turned on your phone sends the text messages through the wifi."
jamRwoo said:
I really don't think that has anything to do with it. The threads can't get "full" unless you set a limit (which I didn't), and I was still having the issue even after deleting all of my texts (one of the many things Verizon had me do on the phone). I'm no dev, so I could be wrong about this, but I feel like a fix that easy would've been diagnosed by now.
I agree it's a software issue of some sort...it doesn't seem consistent enough to be a hardware issue. There's threads on the LG forums about it. The handcent delay seems to have helped me, or at least I don't find myself wanting to throw my phone across the room as frequently.
On a lighter note, while on the phone with Verizon, the lady had me turn off my WiFi because "When it's turned on your phone sends the text messages through the wifi."
Click to expand...
Click to collapse
Verizon T1 tech's don't know anything. Their solutions to everything is usually a "factory reset"
SMS is in no way sent via WI-FI lol
I haven't seen this mentioned before, but: This is the first time I have gotten any Emergency Alerts. I get them all the time from Weather Bug and other kinds of weather alerts. Only over the past couple of days did I start seeing any of the actual installed app on the phone broadcasting the Emergency Alerts. It sets off the noise that we all know and jump to before the guy says "This is only a test..."
I really like that feature, cause I'm a weird guy like that.
I've gotten quite a few the past few days too ... never noticed them before that!
Sent from my Xoom using xda premium
I had 2 VZW Moto Xs and they rocked. About 10 days ago I switched to TMO Moto Xs and the GPS loses lock on both of them. Much like the first set, they get lock very quickly, but both the TMO units acted strangely during nav and when I installed GPS Status I see that the GPS gets lock, the coordinates are displayed, then about 10 sec later it searches for lock again, the coordinates aren't returned, and then it relocks.
This causes a real usability issue when it comes to navigation. If it was one of these I'd think I had a dud, but the VZW units worked fine and the TMO units both have this bug.
Has anyone seen similar issues?
Sent from my XT1053 using xda app-developers app
I use gps daily and i've only come across an issue with it 2x when i went to New York City. basically, it was putting my location all over the map, as if it couldnt find me. Im guessing the high rise buildings had something to do with it.
as far as gps losing lock, I have notice that as well. I never toggle it off and yet I have to turn it maybe once/twice a month
The lock problem I have is pretty continuous, and restarting doesn't seem to help. Wondering I'd there was a bad run somehow.
Sent from my XT1053 using xda app-developers app
I also encountered this issue.
I reset the phone and it went back normal; however, it occasionally still acts weird. I'm on tmobile as well.
Hope someone can figure this out
Sent from my XT1053 using xda app-developers app
For those of you seeing this issue, when it pops up, go into settings > location and see if you see LocationServices listed twice... One with a size of 120k, and the other 136k.
Solutions Etcetera said:
For those of you seeing this issue, when it pops up, go into settings > location and see if you see LocationServices listed twice... One with a size of 120k, and the other 136k.
Click to expand...
Click to collapse
As a matter of fact I do see this. Any idea what might be going on?
Sent from my XT1053 using xda app-developers app
Not yet... but it seems out of place.
My history with GPS "not quite working" was about it being extremely hit and miss about detecting me driving. When this would happen, I'd notice problems with Maps as well.
After a factory reset, it all worked fine. But as soon as I reinstalled Yelp, the issue returned. I'm not certain that yelp is the culprit as in hindsight, I really didn't confirm proper operation after the reset for a long enough period of time given the intermittent nature of the problem.
Next step is to try and determine if two of these same processes is normal, and if not, which one doesn't belong, and where it's coming from. There is a thread in the Moto forums I started. One person there who sees only one occurrence of the process stated his is 120k in size. One of my posts also has a list of all my third party apps that use location services. It would be helpful to know which apps are in common with folks having this issue. The thread is at:
https://forums.motorola.com/posts/8a2bf78f04?page=1
monorailmedic said:
I had 2 VZW Moto Xs and they rocked. About 10 days ago I switched to TMO Moto Xs and the GPS loses lock on both of them. Much like the first set, they get lock very quickly, but both the TMO units acted strangely during nav and when I installed GPS Status I see that the GPS gets lock, the coordinates are displayed, then about 10 sec later it searches for lock again, the coordinates aren't returned, and then it relocks.
This causes a real usability issue when it comes to navigation. If it was one of these I'd think I had a dud, but the VZW units worked fine and the TMO units both have this bug.
Has anyone seen similar issues?
Sent from my XT1053 using xda app-developers app
Click to expand...
Click to collapse
So you are saying this can be software issue? I have a T-Mobile Moto X and I use the phone mostly for Navigation and this is driving me crazy. I am thinking that my phone is defective and been on the phone for 30+ min trying to get support.
I have the same issue
Sent from my XT1053 using Tapatalk
Solutions Etcetera said:
Not yet... but it seems out of place.
My history with GPS "not quite working" was about it being extremely hit and miss about detecting me driving. When this would happen, I'd notice problems with Maps as well.
After a factory reset, it all worked fine. But as soon as I reinstalled Yelp, the issue returned. I'm not certain that yelp is the culprit as in hindsight, I really didn't confirm proper operation after the reset for a long enough period of time given the intermittent nature of the problem.
Next step is to try and determine if two of these same processes is normal, and if not, which one doesn't belong, and where it's coming from. There is a thread in the Moto forums I started. One person there who sees only one occurrence of the process stated his is 120k in size. One of my posts also has a list of all my third party apps that use location services. It would be helpful to know which apps are in common with folks having this issue. The thread is at:
https://forums.motorola.com/posts/8a2bf78f04?page=1
Click to expand...
Click to collapse
I went ahead and posted my situation to https://forums.motorola.com/posts/8a2bf78f04?commentId=755612#755612. There are no apps in common with all three devices (yours, mine, my wife's). The quest continues.
I must add that I also had this problem on my previous phones, Note 2 and Galaxy Mega 6.3. The problem started around the past summer.
Sent from my XT1053 using Tapatalk 2
I confirm that I force stop the 120 k location service file, and the problem is gone. Need to do that again after a reset though.
Sent from my XT1053 using Tapatalk 2
x2h said:
I confirm that I force stop the 120 k location service file, and the problem is gone. Need to do that again after a reset though.
Click to expand...
Click to collapse
When you say 'reset', do you mean reset or just rebooting your phone?
BTW, I have no LocationServices on my Nexus 4, so these seem to be Moto's binaries, which makes sense.
Would appreciate you keeping us posted if this continues to address the issue and causes no additional problems.
Solutions Etcetera said:
When you say 'reset', do you mean reset or just rebooting your phone?
BTW, I have no LocationServices on my Nexus 4, so these seem to be Moto's binaries, which makes sense.
Would appreciate you keeping us posted if this continues to address the issue and causes no additional problems.
Click to expand...
Click to collapse
I mean rebooting the phone. I use Waze everyday for commuting. I will report back if this fix doesn't work.
In terms of side effects, I have not seen any yet.
Sent from my XT1053 using Tapatalk 2
I see both, and if I stop one, I get no better GPS lock.
I've been getting g terrible GPS lock recently and also posted a thread.
Driving me nuts.
Sent from my XT1060 using XDA Premium 4 mobile app
monorailmedic said:
I went ahead and posted my situation to ... There are no apps in common with all three devices (yours, mine, my wife's). The quest continues.
Click to expand...
Click to collapse
I have the same problem. XT1053 on T-Mobile constantly loses GPS signal while driving. Happens in wide open areas with no buildings. I have tried wiping the device and not installing any additional apps and have the same results. I can be sitting at a traffic light have GPS signal, lose it for a few seconds then get it back without having moved.
Here is a poorly shot video of this happening. I will try and get something more clear tomorrow.
http://www.youtube.com/watch?v=N5MeEVS1DW0
Sent from my XT1053 using xda app-developers app
I returned my phone for this issue yesterday. I had navigation issues along with the drive assist problem. While driving maps world just stop. If I was at a turn and turned left the map would stay stuck at the turn long after I turned. It eventually would catch up. Loosing and gaining lock would perfectly explain this.
Update: I got a replacement phone. The new phone has the same problems. May be a bit worse.
Sent from my XT1053 using Tapatalk
Been chasing this one for a while and still think this isn't hardware related (lots of Nexus 5 users seeing this on KK as well).
My latest theory, which I have yet to disprove, is that the GPS data downloaded from some cell towers (this is the A in AGPS) is either wrong, or is somehow getting corrupted.
When this happens to me, turning on airplane mode immediately restores a quick and persistent lock. And using GPS Status to reset/erase the AGPS data returns normal operation... for a while.
It's like the initial fix info is fighting with the actual GPS readings. As soon as you turn off the cell towers, or clear the data they are providing, all is well.
I am in T-Mobile fringe area and see it fairly often. So far it has always cleared up by trying the above.
This is am interesting theory. I will check it out a bit. Most interesting is the idea that the agps data structure may be slightly different for kitkat v ICS, and that it may also be different for TMO. The main idea supporting this (though purely anecdotal) is that it does happen on both my tmo Xs but neither of my VZW Xs.
Sent from my XT1053 using xda app-developers app
I am checking to see if other people see this on there Nexus 6.
I get random reboots, like once every 2-3days I would say. (Is this Memory Leak?)
Also sometimes I cannot unlock with power button, it will stay black screen. Here sometimes it reboots, sometimes if I wait 10-20secs it works again.
I am wondering whether to return it for another one.
Actually I never faced with my device. And currently my device's Up Time is about 180 hrs. Running last 7 days without any problem.
Go to this link and look near the bottom of the page. Paul, from Google, is reporting that 5.1 should "reduce unexpected reboots." Hope that means they have fixed it and they just used the word "reduce" instead of fix because of the fact that any phone might reboot given the right set of circumstances. Hopefully, persisting reboots will finally be fixed. If you read the entire thread (very long) you will see that many people have reported random reboots and they have experienced them under different circumstances. I'd like to know if they've found what is triggering the repeated reboots for everyone---only time will tell. Some have exchanged their phone for another and had success. Quite a few others have reported receiving 1, 2, or even 3 different replacements and still experiencing reboot problems. Don't know what the answer is. I'm just sitting back observing, waiting to see if it gets resolved before purchasing the N6. If I don't see a satisfactory resolution, then I probably won't get one, even though, before it was released, it sounded like the just the phone I wanted.
https://productforums.google.com/fo...c/nexus/other-discussions/nexus-6/9aVUBrwdUZU
I have the same problem on my T-Mobile Nexus 6. 2 reboots in the past 24 hours. It occurs randomly too. I just got the phone like 3 days ago so I'm hoping that 5.1 will fix this issue. Next to the reboots I haven't had any issues with the phone. It pretty badass actually. I switched from the Note 4.
Thanks for the feedback! I really like the phone no way I will get rid of it for this issue. Its just annoying as nexus 5 I didn't. Have any issue like this but I guess KitKat was a more stable than LP.
I will await 5.1 which sound imminent
Sent from my Nexus 6 using XDA Free mobile app
I have had this issue since lollipop. people said it was a bug and would be fixed in marshmallow but I am on 7.0 right now and it still persists.
The problem I am facing is that whenever someone calls me, the phone though vibrates but the ringtone comes into effect like a 1-1.5 second later. Is there any fix to this?
OK, it's not April 1st so I'm assuming you're being serious. There are two "fixes" that I can think of...
1) turn vibration off so you don't notice any delay.
2) ignore it and get on with your life because insignificant things like this are not worth getting upset or annoyed over.
Sent from my Nexus 6 using Tapatalk