Related
Sometimes I'm in areas where I don't get the best reception (i.e. some lecture halls during school hours) and I choose to put my phone in airplane mode so as to conserve battery when the class is over. However I find after trying to come out of Airplane Mode my Revo always reboots. As far as I can remember this issue has also happened in Decrapped 1.0. The same thing happens when I turn on GPS and choose to go to Google Navigation I get rebooted. After the reboot occurs I can turn on the gps/airplane mode etc without any problems. But does this issue happen to anyone else or is it perhaps just my phone? Thanks!!
I find that my revo does the same thing with google nav beta, it will sometimes hang and reboot too. I am running stock rom with a root. When I rotate phone the landscape view is sometimes corrupted with tiny blocks instead of the maps drawn correctly. I have to exit nav app and reload
I've had the same thing happen with airplane mode. I don't really use it often so I figure I can live with it.
Same here. The Revo doesn't seem to like hardware mode changes at times. I get reboots when switching into Bluetooth occasionally.
[I'm Revolting -- are you? Beamed directly into your brain by Revolt 1.3]
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Cryofalcon said:
I'm happy to hear I'm not the only one this happens to. Do you think LG will possibly release a fix? (or more people will have to raise concern about it) or possible for a dev to take a crack at it in their free time? Thanks for the feedback guys!
Click to expand...
Click to collapse
I'm only adding this due to the fact that I was constantly having issues when tethering with the Verizon 4g Hot Spot app. When running it, I found myself needing to reboot because the data connection would get lost and sometimes go into 3g, causing all sorts of headaches with doing things on my computer, such as redesigning websites, including my own.
What I found, though, related to this post, is using the airplane mode to kill the data connection and restart it, was getting me 4g and a few minutes to a few hours of Internet again until the next glitch.
Overall, modded, ota updated, downgraded, whatever, using that method never rebooted my phone. My thoughts are that it's possible some app might be causing that. I don't use Nav anymore, except as a last resort because it is so buggy, it would cause my phone to crash over and over, and rebooting. So, as for LG or Verizon coming up with a fix for this issue, I don't know if they would see it as one because it's not something everyone is experiencing and with as much as I use(d) that method, it never once happened to me. Please don't take that wrongly, just wanted to point out that it might be a certain app and allow those having this issue to seek another solution, maybe comparing apps installed to see a common denominator.
And, because I see a lot of posts relating to tethering issues with Internet freezing or dropping out, I found, on my LINUX machine (so far), that setting the MTU to 1300 seems to have solved that issue. I know this last part isn't directly related to the original post, but is the reason I kept using the airplane mode method and thought this added information might help someone doing what I was...
-Cybie
Sorry for the bump, but as of flashing Revolt 1.5, the issue in my original post seems to have been corrected as I was able to go from airplane mode to google nav multiple times and didn't reboot at all. so whatever the issue was seems to have been corrected. Thanks MT!!
Hi there,
just wondering if anyone else are having issues of their phone randomly rebooting? does anyone know of a fix?
also, sending photos as an attachment does not work. in order to send a photo to anyone on your contact list.
found a work around by going through gallery and sending it directly from there.
if anyone know of a fix for either issues. the help would be greatly appreciated.
Thanks,
kevin
I've had several random reboots. Oddly enough, they usually occurred overnight when I wasn't using the phone. I would hear the vibration on my windowsill and saw it was rebooting. I did a factory reset yesterday and while in the midst of setting everything up on my phone, it rebooted again. I thought that maybe there was too much going on and it overloaded. But last night when I was out and not using my phone, it rebooted again. I'm gonna have to go to Verizon to swap the phone.
It keeps happening on mine, but almost always in the car while attached with BT. I'm wondering if BT has something to do with it, in my case.
Same thing
I am also experiencing the issue specifically at night. I have yet to actually have it interrupt me in anything but its still a concern. Just curious about whether for those of you who are experiencing it are using the Assist app or Android Assistant?
I only use the Assist app for when I'm in the car. It's not setup for night time. I exchanged my phone at Verizon today and so far so good. One of the employees tried telling me that the reboots could have been because I had Better Battery Stats installed on my phone and the battery saver apps can conflict with the OS. I blew his mind when I told him that BBS wasn't a battery saver app and simply lets people know about specific wakelocks. Seemed like no one there had any idea this phone even existed.
For the reboots, I guess tonight will be the big test.
It happened again to me this morning as soon as I got in the car and it connected to Bluetooth. Once it reboots, it's solid.
MVPete1 said:
I only use the Assist app for when I'm in the car. It's not setup for night time. I exchanged my phone at Verizon today and so far so good. One of the employees tried telling me that the reboots could have been because I had Better Battery Stats installed on my phone and the battery saver apps can conflict with the OS. I blew his mind when I told him that BBS wasn't a battery saver app and simply lets people know about specific wakelocks. Seemed like no one there had any idea this phone even existed.
For the reboots, I guess tonight will be the big test.
Click to expand...
Click to collapse
Please report back. I have gone 24 hours without a reboot with no changes to the device which is a first. If it doesn't have a Samsung or Apple logo no one seems to care anymore.
I can't get Assist to work at all. I typically listen to podcasts in the car and when texts come in I get a notification sound but I've never had one read to me. I disabled Assist to see if this was the cause of my Bluetooth reboots, and it's not.
With Assist disabled entirely, each time my phone pairs with Bluetooth it connects but the moment I start to play something it reboots. It's very consistent.
Phibaroptik said:
Please report back. I have gone 24 hours without a reboot with no changes to the device which is a first. If it doesn't have a Samsung or Apple logo no one seems to care anymore.
Click to expand...
Click to collapse
Just wanted to let everyone know that I haven't had any reboots with the new phone. I exchanged my old one for this one on Monday and so far everything's been good.
I have now had 3-4 random reboots that I have seen. I have also witnessed a complete lock up of the phone. I will be heading into Verizon today to exchange my phone.
Just wanted OP to know more people are having issues.
ricwhic414 said:
I have now had 3-4 random reboots that I have seen. I have also witnessed a complete lock up of the phone. I will be heading into Verizon today to exchange my phone.
Just wanted OP to know more people are having issues.
Click to expand...
Click to collapse
Same here and wondering if that's "Normal" too...
My Moto X turns off at night during charging.
So I've been using and enjoying Motorola assist since I got this phone. Recently, however, it's running constantly in the background and absolutely killing my battery and making the phone run hot. The only remedy is to disable it altogether. Is anyone else experiencing this?
Yes, I'm experiencing the same starting today. I, too, had to disable the app because nothing else worked. There are a couple Play Store reviews saying the same, so this is definitely happening to a number of people, but I haven't found anything more detailed yet.
sivarticus85 said:
So I've been using and enjoying Motorola assist since I got this phone. Recently, however, it's running constantly in the background and absolutely killing my battery and making the phone run hot. The only remedy is to disable it altogether. Is anyone else experiencing this?
Click to expand...
Click to collapse
This just happened to me today. Dropped me to 20% battery by lunch when I noticed, with Assist eating 41% of the battery. Haven't had time to troubleshoot it myself, but I shut it down as well.
lordbannon said:
This just happened to me today. Dropped me to 20% battery by lunch when I noticed, with Assist eating 41% of the battery. Haven't had time to troubleshoot it myself, but I shut it down as well.
Click to expand...
Click to collapse
Appreciate the responses. It literally just started happening today, but as far as I can tell there have been no new updates to Assist since 12/19, so I'm totally at a loss for why it's not closing properly. I really like using it. I've reported the issue to Motorola, so hopefully it gets addressed soon.
Moto Assist went nuts last night on both of my Moto X's. One running 4.4 retail, one running 4.2.2 Rogers. I can only guess it has a bug with the new year or something. It killed the battery on both of my phones, this is the first problem I have had with it.
I am only using the sleeping feature. Even after a reboot it is still killing the battery, I have had to force stop it.
I am thinking there will be a lot of people with a dead Moto X on a pretty important night tonight.
I just began having problems with it last night as well. Kept my phone awake 51% of the time and woke my phone up some 6000 times according to Wakelock Detector. Eager to see how soon Moto comes out with a fix. Pretty nice to see them responding to some of the Play store reviews (not any regarding this bug so far though).
Make it a user app and greenify? I've never used it.... But just throwing this out there.
Sent from my Moto X cell phone telephone.....
Sleeping mode is causing the issue. I just talked to a friend with a Moto X who only uses driving mode in Assist and he isn't having the issue. Just tested it on my end (I normally have all 3 enabled) and keeping the driving and meeting modes active while turning off sleeping mode resolves the issue. I suspect it's date-related.
Hey guys, I started having this problem today. The "top" function in Elixer2 shows "Motorola Assist" and "Settings Storage" both using 18% and 33% CPU, respectively. My phone is also very warm and the battery is draining fast.
I disabled Sleep Mode within Motorola Assist, and force-stopped the service (as well as Settings Storage) and the problem seems to have subsided.
That's quite interesting about it being related to the date!
Glad I froze it on day one. Lol
Sent from my Moto X cell phone telephone.....
Wow... I'll have to try disabling sleep mode. I don't really use it that much. I do use driving mode since I commute frequently.
Sent from my XT1060 using XDA Premium 4 mobile app
polarimetric said:
Sleeping mode is causing the issue. I just talked to a friend with a Moto X who only uses driving mode in Assist and he isn't having the issue. Just tested it on my end (I normally have all 3 enabled) and keeping the driving and meeting modes active while turning off sleeping mode resolves the issue. I suspect it's date-related.
Click to expand...
Click to collapse
Ooooh thanks for posting this. I'm going to re-enable mine and try it out!
Moto assist
If you go to the time setting and set the date for January 2nd 2014 you will see that assist starts working again. When I set it back to today's date it's a no go, so Io bet after tomorrow it will be fine.
tonyguy2000 said:
If you go to the time setting and set the date for January 2nd you will see that assist starts working again. When I set it back to today's date it's a no go, so Io bet after tomorrow it will be fine.
Click to expand...
Click to collapse
Jan 2nd 2014?
Yeah, I noticed last night that Sleep mode didn't work at all. Even tried removing updates, clearing data, and re-downloading the update.
I re-enabled it after my clock went to Jan 1 2014 and it has been fine on both 4.2.2 and 4.4.
Yeah, working fine here but I had to disable and re-enable it today.
So weird... Glad to hear it was a simple issue to work around.
Sent from my XT1060 using XDA Premium 4 mobile app
Motorola acknowledged the Assist Dec 31st bug in G+ forum.
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've had my new Seat Leon for a week now and have been using Android Auto a little in this time. I really like it but it seems buggy. For example when using maps, the images will freeze, only updating every couple of minutes. When you are trying to follow an on screen map while travelling at 60mph, this can be very annoying. The other bug I seem to have is that my car seems picky when connecting to my phone (Nexus 5) sometimes. It will say 'not compatible' and will refuse to connect. The only way to solve these two issues is to restart my phone and sometimes to also toggle the USB debugging check box.
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
nimdy said:
Is there anywhere to report bugs to Google? I'd like to help the community in ironing out these issues.
Click to expand...
Click to collapse
Open the Android Auto app.
Tap the 3 dots at top right.
Select "Help & Feedback" and then select Feedback at the bottom.
I'm honestly not sure it will help too much though. There are no idle employees waiting for problem reports who spring into action at a new report.
But if Google sees 100 reports of Problem X, it might move X a bit higher in their priority list.
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
themcfly said:
The freeze problem is actually new to Android Auto, and it started for me on July 31th. Google changed something server-side because even two clean installs didn't solve the issue, and it was working flawlessy until that day. No solutions found so far, had to switch to an iPhone to navigate. Read my report here:
http://forums.androidcentral.com/as...-5-android-auto-lags-when-using-gps-maps.html
Click to expand...
Click to collapse
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
I see a lot of people having problems with certain phones. I have Note Edge and never a problem. My wife has a s6 and used to have problems about 10 minutes into a drive (Black Screen, no control, most other probs mentioned here). Read somewhere if you load the "Android Auto App" on the phone first and then plug in. She has never had a problem Since. Something happens on App load that is not happening on "Auto Launch on detection" (My gut feeling is something to do with bluetooth). Just wanted to pass it along for those people having issues. I am sure google will fix at some point but give it a try and see if it solves your issues. It did ours.
nimdy said:
That seems to be the same issue I'm getting. But strangely this isn't happening all the time. The pattern seems to be when I connect the phone to the car, set up the Google maps navigation, stop and disconnect the phone (for example getting lunch on my way into work), then connect again and continue the navigation. When connecting for the second time I get the issue whereby the refreshing doesn't seem to happen. As you say in your other forum post, this seems to update when you touch the screen.
Hopefully if this bug has only appeared in the last few days, hopefully someone will spot it and report back to get a fix. I've written a brief feedback note saying that I have found a bug and am interested to help them get it fixed!
Click to expand...
Click to collapse
BPryde said:
My gut feeling is something to do with bluetooth.
Click to expand...
Click to collapse
Yes! If something fails with Bluetooth, then the AA connection disconnects. I hope Google fix this soon.