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.
Related
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.
I have a T-Mobile Moto X running 4.4 with an unlocked bootloader and TWRP installed with ART. Today, while taking exams, I felt my phone getting really hot in my pocket and after exams were done, I checked my battery usage to find that Android OS, which normally takes up about 15~25 percent of my battery, was taking up 41% of my battery. I also checked Wakelock Detector, which revealed that "GsmInboundSmsHandler" kept my phone awake for over 3 hours. I searched this up on Google, which only revealed some code, and then I searched it up on xda, which revealed that it had something to do with my voice mail. This makes sense as somebody called me and left me a voice mail, but I checked my voice mail and deleted it right before taking my exam, so the voice mail was only there for about half an hour while the problem persisted for over 3 hours. Also, I placed 2 calls that lasted about a minute long after my exams, and somehow, that combined with my call to voice mail drained 23% of my battery.
Any light on this situation would be greatly appreciated.
If someone could report this to Moto... It doesn't seem like a widespread issue as Google brings up nothing.
Sent from my XT1053 using Tapatalk
Do you use tmobile visual voice mail or other tmobile app?
I used to have that too, but after uninstall it, you'll be fine. Don't know if greenify will work or not, but I figured I don't really need tmobile's app.
Sent from my XT1053 using xda app-developers app
For me it happens even without any visual voicemail apps. What truly impressed me is that even with this wakelock, I was still able to get around 20hrs with around 4.5 hours of screen time.
Sent from my XT1053 using Tapatalk
Did this happen allot of times? One time? Sometimes things just get stuck. Reboot, fixed.
Sent from my XT1058 using Tapatalk
The problem seems to have gone away and no, I do not have the visual voicemail installed. I was just hoping that somebody could give advice on how to prevent this in the future, but I think a reboot would have worked.
I'm running the TMO kangkat ROM on Bell. I get this wakelock after I receive a SMS quite often. Not sure how to prevent it. Don't see any TMO apps anywhere.
Sent from my XT1053 using Tapatalk
I too am getting this wakelock. I can reproduce it by calling my phone and leaving a voicemail. Thus far the only way I have been able to get rid of it is to check voice mail to clear the indicator and the reboot.
I should note this is on AT&T using a developer edition phone. Kit Kat was installed via an OTA. Phone is rooted via TWRP method but is otherwise stock.
FYI. I switched from ART to dalvik today to install xposed and the wakelock still occurs when I get voicemail. So it's not an ART problem. I tried clearing cache and dalvik cache again and no luck either. Switching default sms app didn't have an effect.
It looks like the update to 4.4.2 has fixed this issue for me. Made a call to my phone. Left voicemail and no wakelock this time.
I have same problem. Did anyone find a solution?
Sent from my XT1032
i'm having same issue for 2 days now. Here's my screen shot.
*PUSH*
Same problem here. Did anyone find a proper solution? gsminboundsmshandler ist preventing my Moto G (KK 4.4.4) from going into deep sleep mode.
Hi, I hate to just jump into a new forum with a "cry for help", but I have been trying to get to the bottom of this issue and someone suggested that I post about it here. I am wondering if anyone has seen the following issues or has any insight into what might be the cause and/or a solution?
I apologize in advance for being long winded, but I am hoping the more infor I provide the more likely someone will be able to help me.
Since I got my (original) Moto X in December the driving mode worked most of the time. It wasn't until somewhere between or around the contextual services update and the subsequent Assist update that I noticed the problem, it could have been there before, but i became very aware of it once I noticed that my assist was not "learning" my cars bluetooth as described in the update. Since then I have noticed that assist recognizes when I am driving 1/3-1/2 the time at best. I have gone through motorola tech support and they tried clearing all related data, reinstalling apps and even a factory reset, nothing eliminated the problem for more than a day or so. They replaced my phone despite me insisting it's not a hardware issue. New phone has the same symptoms. Here are the symptoms and what I have tried.
-When it works it takes 1-5 minutes usually, it used to kick in within seconds of being in motion.
-Works >80% of the time if i go somewhere first thing in the AM after it's been charging or after a power cycle.
-Works ~50-75% of the time if I begin to drive again after it works once so long as it's after a fairly short stop.
-Fails to recognize driving 75-90% of the time if I have been in one place for a long period of time (ie after leaving work or running an errand after being home most of the day)
-Toggling "talk to me" under assist driving options while driving sometimes gets it to kick in.
-Opening google maps will kick it in sometimes as well.
-When it's not working I've had my wife watch it in the car and it will show the location services icon in the top as though it is checking, but not kick on.
-I am not using any task killers, I have tasker installed, but I have deactivated it.
I have been trying all kinds of different scenarios to isolate what the problem is so if there is anymore info i can provide to help make it clearer I probably have it so please ask.
Thanks for any help you can provide.
-Kev
You're describing my phone exactly except I can get Drive Assist to turn on every time if I use the app called GPS Status before I start driving. I think it has something to do with the GPS.
Sent from my Nexus 7 using Tapatalk
I have a thread about what is likely related to this on both xda and moto support forums. I will link in the morning, but I just **** this [poor quality] video this evening, it seems to demonstrate the issue.
http://www.youtube.com/watch?v=N5MeEVS1DW0
Sent from my XT1053 using xda app-developers app
Is this a known bug with all moto x phones or just a few. Is it futile to return the phone?
Sent from my XT1053 using Tapatalk
Exchanging seems futile, perhaps 4.4.2 will help but that's just blind hope which is worthless
Here is a link to the other XDA thread. I still need to update and link the Moto Support thread too.
http://forum.xda-developers.com/showthread.php?t=2593098
Sent from my XT1053 using xda app-developers app
I have updated to the lollipop update like many and my phone is warm and sometimes hot.
I am not using my phone and it still gets warm and drains the battery life.
In 4 hours I will go from 100% to dead with no use.
My screen was off but shows it as being on. **See attached photo
I searched the MOTO threads and cant find anything as of now to resolve this issue.
Anyone else having this issue and find a fix?
Tried wifi channels to see if this issue fixes this, cleared cache and nothing........
Hope help comes quick!
If I can get some help I will buy them a beer or coffee!
Okay here's an updated seems to fix the issue......
I disabled the WiFi location settings, download clean master -- https://play.google.com/store/apps/details?id=com.cleanmaster.mguard -- and seemed to have fixed the issue so far.
Keep you posted as the day goes on.
After you updated, did you do a factory reset? If not, and before you do, what apps do you have installed? You might have an unruly app that's just constantly running. I hear Google Fit hasn't been too friendly...
Since Google services is pretty high on the usage list, it could have something to do with syncing errors or maybe problems with updating Google Play services/Play Store. Make sure you have the latest versions.
Google Play services (6.5.85) - http://www.apkmirror.com/apk/google.../google-play-services-6-5-85-1589008-438-apk/
Google Play Store (5.0.38) - http://www.apkmirror.com/apk/google-inc/google-play-store/
Also, unsync any services in your Google account that you aren't using.
Don't forget to turn off extraneous radios like WiFi (if you don't use it for location), GPS, NFC, and Bluetooth when you're not using them.
If all else fails, factory reset and pay attention to the apps that are being downloaded. Uninstall garbage and disable what you can't uninstall, but don't use. Hopefully this helps.
EDIT: Seems you fixed it. Nice! Well, use this as a reference for your next step if things don't stay behaved.
Anfeldt24 said:
I have updated to the lollipop update like many and my phone is warm and sometimes hot.
I am not using my phone and it still gets warm and drains the battery life.
In 4 hours I will go from 100% to dead with no use.
My screen was off but shows it as being on. **See attached photo
I searched the MOTO threads and cant find anything as of now to resolve this issue.
Anyone else having this issue and find a fix?
Tried wifi channels to see if this issue fixes this, cleared cache and nothing........
Hope help comes quick!
If I can get some help I will buy them a beer or coffee!
Click to expand...
Click to collapse
Clear cache and reboot. If you still have the problem, do a factory reset. Also, has the phone stabilized? Have you been through a couple of charge/use cycles? There could be a load of background processes setting up for the first day or so.
Seems the Qualcomm battery guru is a culprit as is the xfinity WiFi app.
Motorola said do a factory reset but I don't want to if something else can be done.
Think it's fixed by the WiFi location and the clean matter app showing the apps that kill the battery.
Here is a great article about asps that keep restarting in lollipop. It's a bug in ART. Google is working on a fix.
http://www.androidpit.com/android-5-0-lollipop-bug-apps-frequently-restart-in-background
Another great way to help save battery. http://www.androidpit.com/android-5-0-lollipop-problems-and-solutions
Best method... Root and use greenify...
Sent from my XT1092 using XDA Free mobile app
I'll post my battery drain/overheating story just to join the fray...i updated to Lollipop 4 days ago and I have had to charge my S5 at least a dozen times. I have tried power save mode, disabling every nonessential app and anything else I can find in the forums.
I used to get 15-16hrs of battery life (6am-10pm) with charge to spare, but immediately after the update my CPU sits maxed (monitored by Micro CPU Monitor) and constantly overheats (GSAM Battery Monitor). The phone went from 95°F to 105°F in 10min with standard use. I only had it overheat one other time in the last year (on my dash in the summer). I hope Google/Verizon will replace my battery because this abuse of it is going to shorten the life considerably!
See screen shots from the last charge at 4pm to now (10:15pm) all while UNUSED and in powersave mode plus battery at 107°F (a new record for me)!
I really don't want to reset the phone and lose my app settings, plus it seems to be hit/miss with other's issues. Any suggestions would be great.
Seems hit or miss.
Not sure what to tell you but try making sure you're Wi-Fi isn't always searching for locations when not connected. Seems this is a huge problem for many as Verizon threads and Android forums are filling up. I don't have an S5 but will keep looking for the fix.
Quick read-
http://www.gottabemobile.com/2015/02/09/verizon-galaxy-s5-lollipop-update/ many are having this issue but not all.
Posted from my Moto X 2014
i am facing similar problem with my moto g2 if you find any solution please let me now
same problem to me also friend if u found any solution for it please mail to me [email protected]
My Nexus 6 is compeletely stock and untouched software. I have attached screenshots from Nexus 6 (5.0.1) and Note 3 (5.0) to show the point I'm talking about.
When I'm sleeping as you can see on the Note 3 it has very few awakes. But Nexus 6 on the other hand is almost always awake. It drains about 20-25% battery overnight.
I have performed factory reset 3 times and now it has almost no additional apps installed but still the same. (don't judge by the facebook on the screenshot it's just installed and the problem is the same with or without it) I'm not rooted so i can't use the wakelock detector. I've installed GSam and it shows Android OS and Android system as biggest drainers for the current situation (16%, 6%) which i suspect nothing extraordinary.
I have play services 6.7.76 on both devices if it has anything to do with it. I tried something like turning the ambient display off and some other settings to see if theyre waking it but no luck yet. Do you think it is a software thing and Google will eventually fix it and I should wait or what should i do?
I really want to keep this phone but the battery is a big concern for me right now. every morning seeing the battery down without touching the phone is a big problem. Any help and information on the subject is appreciated.
Edit: I have added a screenshot from safe mode. I restarted in safe mode to see if any 3rd party is the cause of the problem. But the problem persists. And I have noticed that when the wifi is compeletely off (Keep awake, Always scanning etc.) the problem is solved. But whenever i turn on the wifi, even when it is not connected to any network, it starts draining battery and keeping phone awake like on the graphics. Can anyone give me a hint if this can be a hardware related issue with the wifi receiver? Or it looks like a software issue and can be solved with the 5.1 update? I have 3 days to return the phone if its a hardware thing. Thanks
You should probably update to 5.1 and see if that helps.
biggiestuff said:
You should probably update to 5.1 and see if that helps.
Click to expand...
Click to collapse
Do you know if it is a common issue and 5.1 fixes it? I've checked the updates but nothing showed up so far. I'm close to 14 day window for my T-Mobile purchase so i need info on 5.1 about this issue and i didn't see anything related :/
HKNRN said:
Do you know if it is a common issue and 5.1 fixes it? I've checked the updates but nothing showed up so far. I'm close to 14 day window for my T-Mobile purchase so i need info on 5.1 about this issue and i didn't see anything related :/
Click to expand...
Click to collapse
You might have the sensor ind bug that was in 5.01 that kept the phone from sleeping properly. From my short experience with 5.1, it's gone. Hard to tell about your situation without screenshots from better battery stats and the app list.
biggiestuff said:
You might have the sensor ind bug that was in 5.01 that kept the phone from sleeping properly. From my short experience with 5.1, it's gone. Hard to tell about your situation without screenshots from better battery stats and the app list.
Click to expand...
Click to collapse
Thank you for the info. Root is not an option on the Nexus 6 cause my sister will be using it and she's not a techie. Without root I can't properly see what keeps it awake :/ As i said, besides the screen, biggest consumers are the Android OS and Android system in Battery settings list. But they're similiar on the Note 3 too so i dont think i can get somewhere with them.
I guess i will have to wait for 5.1 and hope it is fixed as you've said. Do you know what sensor is causing the sensor ind error? Does it have anything with the Ambient display?
HKNRN said:
My Nexus 6 is compeletely stock and untouched software. I have attached screenshots from Nexus 6 (5.0.1) and Note 3 (5.0) to show the point I'm talking about.
When I'm sleeping as you can see on the Note 3 it has very few awakes. But Nexus 6 on the other hand is almost always awake. It drains about 20-25% battery overnight.
I have performed factory reset 3 times and now it has almost no additional apps installed but still the same. (don't judge by the facebook on the screenshot it's just installed and the problem is the same with or without it) I'm not rooted so i can't use the wakelock detector. I've installed GSam and it shows Android OS and Android system as biggest drainers for the current situation (16%, 6%) which i suspect nothing extraordinary.
I have play services 6.7.76 on both devices if it has anything to do with it. I tried something like turning the ambient display off and some other settings to see if theyre waking it but no luck yet. Do you think it is a software thing and Google will eventually fix it and I should wait or what should i do?
I really want to keep this phone but the battery is a big concern for me right now. every morning seeing the battery down without touching the phone is a big problem. Any help and information on the subject is appreciated.
Click to expand...
Click to collapse
Do you use Microsoft Exchange services?
I mean, did you setup other e-mail accounts. Like- Outlook, hotmail .etc??
Because last time I found, that service kept my phone to always wake up..
Masum56k said:
Do you use Microsoft Exchange services?
I mean, did you setup other e-mail accounts. Like- Outlook, hotmail .etc??
Because last time I found, that service kept my phone to always wake up..
Click to expand...
Click to collapse
Oh yeah it has a hotmail account set up besides gmail. I will remove the hotmail account and restart the phone at night and observe in the morning again. Thanks for the suggestion!
If it is the problem, how did you overcome the issue? Are you using browser for your exchange mail account? If so, it will be a pain not getting mails to the app :/
Made some edits on the original post. If it helps..