Related
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.
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.
So to quickly sum up, the battery of my Moto X is good for precisely 3 days after I got it, and then started draining quickly in it's sleep. I performed a factory reset, installed the same applications, and the battery was once again good for 3 days, until it experienced the same symptoms. Anybody have any idea why this would happen? Thanks.
P.S. Battery stats reports that my Wi-Fi is always on even if I turn it off. The only way to "turn off" the wifi is to turn off the low-battery location tracking in the wifi menu, so this is kindof leading me to believe that the phone is pinging for location quite often, thus always keeping my wifi on. Just a thought.
Guessing you are on 4.4
Sent from my XT1058 using Tapatalk
murso74 said:
Guessing you are on 4.4
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Yep. I just ran my phone in safe mode for a bit and the battery is marginally better.
I troubleshoot for a living. You've already solved the mystery:
It's fine for 3 days. You install YOUR (key) usual apps. It doesn't sleep....
It's one of your apps
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
I troubleshoot for a living. You've already solved the mystery:
It's fine for 3 days. You install YOUR (key) usual apps. It doesn't sleep....
It's one of your apps
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
See you would be right, if it weren't for the fact that I install and completely set up all my apps within an hour of restoring the phone, and don't install any after that.
Ok so I've now taken the device out of safe mode, let it run on Wifi a bit, and then let it run on LTE. Even though the phone isn't registering it, the device is waking. I can determine this by the CPU run time vs the screen-on time vs the wake time. You can see in the screenshots.
You can see the dip as soon as I turn on LTE. The CPU total goes up so wakelocking is the problem on idle, even though it's not showing it.
dsass600 said:
So to quickly sum up, the battery of my Moto X is good for precisely 3 days after I got it, and then started draining quickly in it's sleep. I performed a factory reset, installed the same applications, and the battery was once again good for 3 days, until it experienced the same symptoms. Anybody have any idea why this would happen? Thanks.
P.S. Battery stats reports that my Wi-Fi is always on even if I turn it off. The only way to "turn off" the wifi is to turn off the low-battery location tracking in the wifi menu, so this is kindof leading me to believe that the phone is pinging for location quite often, thus always keeping my wifi on. Just a thought.
Click to expand...
Click to collapse
Do you have a custom kernel or ROM installed? these kind of problems are usually caused by a 'bad flash'
dsass600 said:
See you would be right, if it weren't for the fact that I install and completely set up all my apps within an hour of restoring the phone, and don't install any after that.
Click to expand...
Click to collapse
So you're saying that out of ALL of your apps, it's impossible that one creates a rogue or persistent process? Lol. Well, you're wrong.
I'm done trying to help. Examine your apps. I gave you your answer.
Sent from my XT1060 using Tapatalk
1ManWolfePack said:
So you're saying that out of ALL of your apps, it's impossible that one creates a rogue or persistent process? Lol. Well, you're wrong.
I'm done trying to help. Examine your apps. I gave you your answer.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
that's not what I'm saying, and that's not what you suggested either. You said to examine the last after I installed and see if it's waking my device. Then I told you that I installed all my applications immediately after factory reset on the device. It makes no sense that an app would not display rogue behavior until three days later. Plus, after running in safe mode, the battery life did not improve.
joemon871 said:
Do you have a custom kernel or ROM installed? these kind of problems are usually caused by a 'bad flash'
Click to expand...
Click to collapse
nope. Completely stock.
dsass600 said:
nope. Completely stock.
Click to expand...
Click to collapse
Would you be willing to root your phone and installing a custom recovery so you can wipe cache and dalvik cache? Or maybe manually install a ROM yourself. Its worth a try. You can just Unroot it back if you don't want root
joemon871 said:
Would you be willing to root your phone and installing a custom recovery so you can wipe cache and dalvik cache? Or maybe manually install a ROM yourself. Its worth a try. You can just Unroot it back if you don't want root
Click to expand...
Click to collapse
yes but I do not want to lose root as soon as the 4.4.2 update is released on February 1st. I plan on rooting the phone after that. I'm worried that after I root though, I discover it is a hardware issue, its going to be a long process of unrooting the phone to send back to Motorola.
Get Gsam and see what is going on. Simple. The stock battery info is next to useless.
Then you can take screen shots that have better info.
Sent from my XT1058 using Tapatalk
If you suspect its a hardware issue then its best to have the phone replaced as soon as possible before messing with it too much you know?
Sent from my SGH-M919 using Tapatalk
I figured it out. Installed a CPU monitoring application since I'm not rooted and saw that the phone was barely sleeping. Purely by chance I guessed it was Snapchat, greenified the application, and it worked! Thanks for your help guys.
dsass600 said:
I figured it out. Installed a CPU monitoring application since I'm not rooted and saw that the phone was barely sleeping. Purely by chance I guessed it was Snapchat, greenified the application, and it worked! Thanks for your help guys.
Click to expand...
Click to collapse
So.....I was right?
Rogue processes happen, my man.
Sent from my XT1060 using Tapatalk
Gsam would have pointed it out quickly. Its my number one app.
Sent from my Moto X cellular telephone...
battery drain
I've had the same issue over the last 2 days, and the Kernel (Adroid OS) takes 26.5% of the battery drain, allthough CPU has only had to work 3m 30s...
Gsam. Lol
Sent from my Moto X cellular telephone...
Hey,
Ever since the OTA update my phone reboots randomly about once every two days [I'm on Verizon].
Is anyone else experiencing this?
Screen just goes black, vibrates once quickly, then its back on that LG G2/Verizon screen and then boots. Then everything is fine.
Vexorg said:
Hey,
Ever since the OTA update my phone reboots randomly about once every two days.
Is anyone else experiencing this?
Screen just goes black, vibrates once quickly, then its back on that LG G2/Verizon screen and then boots. Then everything is fine.
Click to expand...
Click to collapse
Nope... Have you done a FDR yet? It is highly recommended to do one after taking this OTA if you have ANY kind of trouble at all.
acejavelin said:
Nope... Have you done a FDR yet? It is highly recommended to do one after taking this OTA if you have ANY kind of trouble at all.
Click to expand...
Click to collapse
Fdr is a full factory reset?
Sent from my VS980 4G using Tapatalk
Vexorg said:
Fdr is a full factory reset?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yes, FDR = Factory Data Reset, basically a factory default, not reflashing the original factory images.
acejavelin said:
Yes, FDR = Factory Data Reset, basically a factory default, not reflashing the original factory images.
Click to expand...
Click to collapse
Sorry for all the questions but you're just referring to go going to settings > backup and reset > factory data reset?
Sent from my VS980 4G using Tapatalk
Vexorg said:
Sorry for all the questions but you're just referring to go going to settings > backup and reset > factory data reset?
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
Yes
Sent from my Nexus 4 using Tapatalk
acejavelin said:
Yes
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Cool thanks
Sent from my VS980 4G using Tapatalk
Problem still persists, I'm surprised I'm the only person getting this issue.
Vexorg said:
Problem still persists, I'm surprised I'm the only person getting this issue.
Click to expand...
Click to collapse
Your not the only one, but this is a very rare occurrence... Across all the major forums only 3 or 4 users have reported this issue.
Sent from my Nexus 4 using Tapatalk
Fairly common on custom builds
Vexorg said:
Problem still persists, I'm surprised I'm the only person getting this issue.
Click to expand...
Click to collapse
It's a fairly common occurrence for people on custom builds. I've noticed it when trying to do too many things at once.
There also apparently appears to be a link between SwiftKey and this problem from what I've read, or maybe that's an entirely different problem.
Mine have stopped after I disabled Google Services Sound Search.
hardheart1 said:
It's a fairly common occurrence for people on custom builds. I've noticed it when trying to do too many things at once.
There also apparently appears to be a link between SwiftKey and this problem from what I've read, or maybe that's an entirely different problem.
Mine have stopped after I disabled Google Services Sound Search.
Click to expand...
Click to collapse
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
substitutesam said:
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
Click to expand...
Click to collapse
I haven't looked at any logs or anything on a remotely technical level. I noticed the google sound search was eating battery so I disabled it. Reboots are gone.
substitutesam said:
I just rooted my phone about a week ago, I'm still on the 4.4.2 KK ROM and have Swiftkey and Google Services enabled. I also am using the Complete Keyguard Disabler.
A few things I've noticed are:
1)Random reboots/Phone overheating
2)Sluggish/unresponsive phone performance coming out of 'sleep' using double tap
3)Speaker/headphone Viper4 mod not working properly
Is a factory reset something I should consider if I didn't root the device until after the 4.4.2 update or is there something else causing these issues? I'm sure there is some user error in #3 as I'm going through the learning curve, but the most concerning is by far the #1 and 2, as I rooted it for the main purpose of increasing performance speed.
Any insights?
Click to expand...
Click to collapse
hardheart1 said:
I haven't looked at any logs or anything on a remotely technical level. I noticed the google sound search was eating battery so I disabled it. Reboots are gone.
Click to expand...
Click to collapse
First and foremost, I was not rooted or using anything customer. I never tried rooting this phone because I figured there would be updates in the near future (I was optimistic).
I am also receiving:
Random Reboots
Overheating
Random Apps Crash frequently (Kindle, Search, Home, etc)
I am also using swiftkey.
Vexorg said:
First and foremost, I was not rooted or using anything customer. I never tried rooting this phone because I figured there would be updates in the near future (I was optimistic).
I am also receiving:
Random Reboots
Overheating
Random Apps Crash frequently (Kindle, Search, Home, etc)
I am also using swiftkey.
Click to expand...
Click to collapse
I believe there are known issues with the G2 and Swiftkey on stock roms (rooted, custom, or otherwise).
What language are you using on Swiftkey. I'm on Swiftkey and Carbon and I'm not having any problems.
Using English (US)
Sent from my VS980 4G using Tapatalk
Vexorg said:
Using English (US)
Sent from my VS980 4G using Tapatalk
Click to expand...
Click to collapse
I'm also on Swiftkey and am experiencing very similar issues, using English as well.
On a side note, I also work in a building that has no cell service and continuously cycles through wifi connections because the 3 networks I have entered vary greatly in strength based on a 10 ft radius of where I walk.. could this be a cause as well and is there a way to stop it from happening?
I've tried removing all of the connections except 1 wifi signal but then I'm really only connected when I'm at my desk and if I standup to walk somewhere it's disconnected...
#1stWorldProblems
These issues are still persisting... anyone think taking it to Verizon would do anything?
My phone is completely stock. I am wondering if I should just flash a new ROM or something.
Vexorg said:
These issues are still persisting... anyone think taking it to Verizon would do anything?
My phone is completely stock. I am wondering if I should just flash a new ROM or something.
Click to expand...
Click to collapse
I second this, still having random reboots and running completely stock. I'm getting close to just removing Swiftkey all together?
I stopped using swiftkey and I'm still getting random reboots
When I use Google now voice feature to set my alarm to a certain time, the phone always sets it 6 hours ahead of what I want. I checked the clock settings, good now settings, and other stuff but can't not find a solution.
Does anyone know what to do?
Thanks.
Set it for 6 hours before you want it to go off!
Not a solution
Actually, it technically is. It just isn't a good one, or one you like.
Unfortunately I don't have any ideas either.
Sent from my SM-N920V using Tapatalk
The fact is that it shouldn't behave this way.
Maybe the time zone on your phone is not the same time zone Google thinks you are in?
I checked the time zone in the phone settings to make sure it is all correct. I tried changing from auto to manual and that didn't help either.
Do you have a bunch of things debloated? I got a new android wear watch yesterday and noticed the time was way off...
Tried various things, couldn't get the time right.
Then enabled everything I had debloated, and the time started to work correctly after a reboot of the phone and the watch.
Don't know which thing messes it up, but was definitely something that was debloated, so that could be something to try...
Sent from my SM-N920V using Tapatalk
JasonJoel said:
Do you have a bunch of things debloated? I got a new android wear watch yesterday and noticed the time was way off...
Tried various things, couldn't get the time right.
Then enabled everything I had debloated, and the time started to work correctly after a reboot of the phone and the watch.
Don't know which thing messes it up, but was definitely something that was debloated, so that could be something to try...
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Enable everything but still have the same issue.
updated the app to 5.5 beta version and now everything works normal