Has anyone else noticed that their Moto X doesn't seem as "snappy" as it used to? It feels like I'm waiting a lot longer for the camera to open and take a picture, it takes several seconds to attach a photo to a message using Hangouts, SwiftKey doesn't pop up as quickly, etc. I've been running 4.4 since AT&T pushed it out. I'm considering doing a factory data reset to see if it helps speed things up, but that's a bit of a hassle so I've been holding off. Just wondering if anyone else has noticed this.
Nope. Has never slowed down here.
Sent from my Moto X cellular telephone...
Wipe dalvik and cache and see if that helps.
Sent from my Dev Edition Moto X
lifetechnician said:
Has anyone else noticed that their Moto X doesn't seem as "snappy" as it used to? It feels like I'm waiting a lot longer for the camera to open and take a picture, it takes several seconds to attach a photo to a message using Hangouts, SwiftKey doesn't pop up as quickly, etc. I've been running 4.4 since AT&T pushed it out. I'm considering doing a factory data reset to see if it helps speed things up, but that's a bit of a hassle so I've been holding off. Just wondering if anyone else has noticed this.
Click to expand...
Click to collapse
Wow! I almost made a thread about having this same issue recently. My x keep lagging and home screen scrolling was choppy and opening apps was very choppy also. I did clear cache partition and it has fixed it so far.
Sent from my XT1060 using Tapatalk
Schaweet said:
Wipe dalvik and cache and see if that helps.
Click to expand...
Click to collapse
I reset the cache, will update with results.
I've been using this.
http://forum.xda-developers.com/showthread.php?t=2132878
I think it helps out but not too sure if anyone wants to test it out. Just flash through recovery I have safestrap.
Schaweet said:
Wipe dalvik and cache and see if that helps.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
Forgive the noob question, but can this be done if I'm not rooted? If so how? Thanks for any help.
Sent from my XT1060 using XDA Premium 4 mobile app
Ryano89 said:
Forgive the noob question, but can this be done if I'm not rooted? If so how? Thanks for any help.
Sent from my XT1060 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Good question. I haven't had stock recovery on a device for longer than about 20 seconds so I'm not sure. Maybe someone else can answer that question.
Sent from my Dev Edition Moto X
Schaweet said:
Good question. I haven't had stock recovery on a device for longer than about 20 seconds so I'm not sure. Maybe someone else can answer that question.
Sent from my Dev Edition Moto X
Click to expand...
Click to collapse
I don't remember where I found these instructions but they work for me.
To wipe the cache partition, follow these steps:
With the phone powered off, press and hold the Volume down key and Power key for 2-3 seconds until the the Boot options screen appears.
Release the keys.
Use the Volume down key to scroll to highlight Recovery.
Press the Volume up key to select.
The phone will display the Motorola logo then the Android recovery screen.
Once the Android recovery screen displays, press and hold the Volume up key for 10-15 seconds.
Quickly tap and release the Power key.
The Android recovery screen will appear.
Scroll down using the Volume down key to highlight wipe cache partition.
Use the Power key to select.
The phone will power-cycle.
Related
Don't know about other models, but such an option is not available on my XT1053. Did I miss something here?
Sent from my XT1053 using Tapatalk 2
x2h said:
Don't know about other models, but such an option is not available on my XT1053. Did I miss something here?
Sent from my XT1053 using Tapatalk 2
Click to expand...
Click to collapse
Root with gravity box.
MOTO X SLAPPED
If you're rooted and don't want Xposed/gravity box, try quick boot from the playstore. Has all the reboot, boot to recovery ...etc...options.
Sent from my N5 cell phone telephone....
I thought if you held it down it just rebooted..
Slapped X on Tapatalk
Never understood why this hasn't been implemented into stock android yet. Most of the OEM skins include it.
Flexia32 said:
I thought if you held it down it just rebooted..
Slapped X on Tapatalk
Click to expand...
Click to collapse
Thanks. That answers my question.
Sent from my XT1053 using Tapatalk 2
kj2112 said:
If you're rooted and don't want Xposed/gravity box, try quick boot from the playstore. Has all the reboot, boot to recovery ...etc...options.
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
Great app, used it for years before I got Gravity Box.
Flexia32 said:
I thought if you held it down it just rebooted..
Slapped X on Tapatalk
Click to expand...
Click to collapse
Yes, holding down Power and VOL DOWN will reboot the phone, simulating pulling the battery out. Using an app like QuickBoot or Gravity Box is just faster and more convenient.
[email protected] said:
Root with gravity box.
MOTO X SLAPPED
Click to expand...
Click to collapse
For clarity's sake: you need to obtain root, disable read/write access (probably) and then install Xposed Framework and the Gravity Box module. If you're already on 4.4.2, the only real option is holding power and volume down, as you can't revert to obtain root.
You don't have to hold volume down. Just holding power works
-Moto X-
fury683 said:
Yes, holding down Power and VOL DOWN will reboot the phone, simulating pulling the battery out...
Click to expand...
Click to collapse
FWIW - the power+vol "trick" is meant to simulate a battery pull since the battery is inaccessible (think phone frozen/unresponsive). What this means is that it is a hard stop on ALL processes, which is bad for memory allocation and may cause Android system slowness while it recovers from the abrupt stop. I never figured out if the Quick-Boot app does the same thing.
So when I hear/read people say they've performed a "soft-reboot" on their device, i often wonder what this technically means since there isn't an actual way to accomplish a "soft-reboot" gracefully. it's the equivalent of hitting the reset button on your PC while Windows is running.
640k said:
FWIW - the power+vol "trick" is meant to simulate a battery pull since the battery is inaccessible (think phone frozen/unresponsive). What this means is that it is a hard stop on ALL processes, which is bad for memory allocation and may cause Android system slowness while it recovers from the abrupt stop. I never figured out if the Quick-Boot app does the same thing.
So when I hear/read people say they've performed a "soft-reboot" on their device, i often wonder what this technically means since there isn't an actual way to accomplish a "soft-reboot" gracefully. it's the equivalent of hitting the reset button on your PC while Windows is running.
Click to expand...
Click to collapse
That's why I'd say use the quick boot app or gravity box. Then it reboots more "gracefully ".
Sent from my N5 cell phone telephone....
I am puzzled that the Moto X also doesn't have a restart. I feel like Android is so smart in so many ways, but misses some of the most basic functions...
Just root and use xposed + gravity
Enviado desde mi XT1053 mediante Tapatalk
640k said:
FWIW - the power+vol "trick" is meant to simulate a battery pull since the battery is inaccessible (think phone frozen/unresponsive). What this means is that it is a hard stop on ALL processes, which is bad for memory allocation and may cause Android system slowness while it recovers from the abrupt stop. I never figured out if the Quick-Boot app does the same thing.
So when I hear/read people say they've performed a "soft-reboot" on their device, i often wonder what this technically means since there isn't an actual way to accomplish a "soft-reboot" gracefully. it's the equivalent of hitting the reset button on your PC while Windows is running.
Click to expand...
Click to collapse
The soft reboot is exactly the same as a normal reboot from gravitybox or quickboot or anything else. The ONLY difference is that soft reboot starts the boot at a kernel level, and the 'hard' reboot starts at the bootloader level. They both stop processes in the exact same way.
Sent from my XT1060 using Tapatalk
Hey guys,
i have a weird problem.. Some of my background apps such google play music app sometimes closes for no reason.. its not crashing since i cant see any error message.. it just closes on its on.. not only Google play music some times my weather app closes and then restarts for no reason..
Also asphalt 8 which was working for a few days keeps closing when i choose a race and it loads the race..i dont face any problem opening the app and chooosing cars and other stuff...when this happens all my other apps even launcher(nova) closes and restarts..
Just bought the phone 1 week ago..
Any solution..i dont have any memory booster apps or task managers installed other than stock..i use CM antivirus only...
Details:
MOTO G 2014
unrooted, stock 4.4.4..
Thanks in advance guys..
I have seen this problem too. I think it's KitKat which is killing apps to free memory. But it's not configured correctly. I have observed if the free memory reduces to 300mb, the app killing starts. Moto need to fix this. Some people got the bug fix update, but not sure if that fixes the issue.
Sent from my Nexus 4 using Tapatalk
Try To Clear Cache N Dalvic cache..
How do you do that with stock recovery? I don't think that's a problem. I think it's related to min free memory setting in the rom. But only moto can change it.
Sent from my Nexus 4 using Tapatalk
I can't guarantee but give a try... Just Goto Stock Recovery And Clear Cache & Dalvic data Cache..
jbanti said:
I can't guarantee but give a try... Just Goto Stock Recovery And Clear Cache & Dalvic data Cache..
Click to expand...
Click to collapse
There are few more threads opened by people with same problem. So I have raised this issue with the motorola support forums. Interested people can go and comment there.
https://forums.motorola.com/posts/6168839e0e
anshumandash said:
How do you do that with stock recovery? I don't think that's a problem. I think it's related to min free memory setting in the rom. But only moto can change it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Follow these steps..
You first have to power off your Android smartphone. In order to do that, press the power button and select “power off”.
Wait a few seconds and then press the volume up and volume down buttons along with the power button at the same time for about 3, or 4 seconds.
Release the buttons; the Moto G boot menu must be now displayed on your phone.
Use the Volume Down button in order to scroll down and also up as the Volume Up button can be used only for selecting an option.
Scroll down until you reach “recovery” and the press the Volume Up button once.
The android logo will now be displayed on your phone.
Hold down Volume Up and Volume Down buttons for about 5 seconds and press power button once.
The recovery mode menu should now be displayed.
But i already tried this but no use..It keeps clearing my memory still..Its not life threatening but still annoying when it happens during a race..
Hello and Happy Turkeyday to all. I have an issue with my wife's note. When she gets any notifications they turn the screen on and it doesn't turn off. I feel pretty knowledgeable about the android O.S. in a whole, I have my S5 rooted and running AICP. I just can't figure out why the notifications cause the screen to stay on. Has anyone else had this problem maybe you could help shed some light on my issue. Thanks in advance.
Is the phone rooted?
Sent from my SM-N910T using Xparent Pink Tapatalk 2
No she won't let me root her phone.
Same problem
I have the exact same problem on my Note 4 (N910F).
My phone is rooted and I have had the problem from the start.
I am also running a custom kernel now but the problem persists.
Any ideas on why this is happening anyone? I've got it to not turn the screen on for a notification but now it won't turn off when plugged in.
Turn off the lock screen notifications, or everything you can on the lock screen settings, most likely something is causing the screen to wake lock. My bet is the weather widget.
Sent from my SM-N910T using XDA Free mobile app
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Bullet_King1996 said:
I just searched for the same problem on the Galaxy s5 and someone said to download wakelock-detector to see if it's an app.
Will keep you updated if it helps.
Click to expand...
Click to collapse
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Bullet_King1996 said:
So a little update, so far, my problem seems to be fixed.
After the app told me that Dsploit was causing a lot of screen-on time, I disabled the app.
Haven't had it happen so far today so I hope this helps you too.
Click to expand...
Click to collapse
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
u1988 said:
Can anyone else have other fix? I have new note 4 with rom stock and very few apps (5-8 apps)
the "Wakelock Detector-Save Battery" app requird root this not my phone so I can't root for now.
Click to expand...
Click to collapse
arjun90 said:
If you have very few apps installed, uninstall those apps one by one to see which one is potentially keeping the screen on. Otherwise, do a factory reset, clear cache; also ensure power button is sticky and is fully functional.
Click to expand...
Click to collapse
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Boot into recovery and clear cache
or factory reset like everyone said
Great to hear all is well. Please tell me that you're going to root.
u1988 said:
Thx, What I did in the end is disble a few stock apps (I add a pic)
And set the Screen time to 30 sec and shut down the deivce got the battery out turn on, set the Screen time to 1 min and shut down...
a few times in the end got it back to the time I want, all of this fore "soft" reset the database of the settings
..now for about a week+ the problems won't show again :highfive:
Click to expand...
Click to collapse
arjun90 said:
Great to hear all is well. Please tell me that you're going to root.
Click to expand...
Click to collapse
It's not my phone, so for now no need to root .
btort1 said:
Boot into recovery and clear cache
or factory reset like everyone said
Click to expand...
Click to collapse
I gave you Another solution.
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Aruarian said:
Not exactly experiencing the same problem, but I've been having this odd power-button issue since today. If I leave my phone locked/screen off for about 5 minutes, it does not respond to a press of the power button. The weird thing is, it does respond after exactly 3 presses, every time. It's a non-issue when Smart Unlock is engaged on my home wifi-network. On 5.0.1. Chroma, haven't updated it in a week or two.
Click to expand...
Click to collapse
Sounds like a different issue.
Mine was a complete one of, switch made me suspect software asop issue.
Monitoring.....
Sent from my Nexus 6
Happened again, dead power button, woke by volume buttons, reboot, works fine again.
So this isn't intermittent, in that when it fails it won't work again until restart, which says to me software.
I'm now using this thread as log. To see if RMA necessary.
Chroma 5.1 22/03/2015
Sent from my Nexus 6
Happened again later in the day.
Sent from my Nexus 6
ben_pyett said:
Has anyone had any power button issues? Or heard of anything similar.
Suddenly found that the power button was completely unresponsive, in that it wouldn't wake the sleeping device, fortunately I'd enabled volume buttons to wake, once device was awake, power button still did nothing, so I couldn't get to access reboot menu, so installed Franco's reboot application, rebooted, and it's working absolutely fine again? As if nothing was ever wrong, makes me suspect a software rather than hardware related problem.
Strange? Familiar? Can anyone relate?
I've had many previous, non nexus devices which suffered from dead power button, but nothing of late, plus the device is only weeks old.
I'm running latest Chroma build (as per sig) so asop.
Sent from my Nexus 6
Click to expand...
Click to collapse
Do you have a screen protector covering the sensor? If so that's probably the issue, disable ambient display and see if you can reproduce the problem.
Sent from my Nexus 6 using XDA Free mobile app
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
ben_pyett said:
No screen cover, just a ringke slim cover. But I don't think that covers the sensors.
Sent from my Nexus 6
Click to expand...
Click to collapse
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
No that wouldn't, still try turning off ambient display and see if the issue persists.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Feature is disabled. ?
Sent from my Nexus 6
ben_pyett said:
Feature is disabled. ?
Sent from my Nexus 6
Click to expand...
Click to collapse
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
It was already disabled when you were having the problem?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
ben_pyett said:
Sorry, yes, looks like the option has always been disabled.
Sent from my Nexus 6
Click to expand...
Click to collapse
Then short of backing up and doing a clean install I am out of ideas, sorry.
Sent from my Nexus 6 using XDA Free mobile app
Cheers. Literally only just did that for stable Chroma 22/03 version... Will wait until further versions come out and will consider doing that. Cheers anyway
Sent from my Nexus 6
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
happened to me today, like it was in a deep sleep and took ages for the power button to work.
Im on stock 5.1
Happened once 31/01 soft reboot resolved it
Still believe this is software.
ben_pyett said:
26/03/2015 Happened about four times today. Rebooted once, another time out went away after a bit... So sounding like could be hardware for first time... Hmmm
Sent from my Nexus 6
Click to expand...
Click to collapse
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I would get this issue on Chroma if I had enabled the option Display--Ambient Display--Overwrite Value.
See if thats enabled, and if so, try with it disabled for awhile.
mgear356 said:
actually i encountered this issue even after a reboot...
but most of the time it would go away.. i really wonder why is this so.. my power button is confirm working fine because it allows me to do a force reboot (by holding on to the powerbutton for like 5-7 secs).
using 31/3 chroma.. didnt experience this from stock or terminus rom..
have you all tried a clean install?
Click to expand...
Click to collapse
I was clean install on 5.1 but not since, although did import apps and data from TB not that it should impact it at all. Only ever run Chroma, jumped straight to it after initial unlock.
Fortunately volume keys always wake - so far.
Let me know how you get on - in this thread.
If I find it continues to happen then I'll consider clean install and then maybe even a replacement device.
Everything was fine after last reboot.
Immediately after plug in into charger, the power button stop working. First time experiencing this. Able to try this to guys?
Edit: I toggled 2 things.. Enabled / disabled ambient display overwrite defaults and screen on when plug / unplug charger..
Power button is working again without any restart.. @githyanki @ben_pyett
Hi All, quick question. Since upgrading to 5.1 on my verizon Moto X, I noticed that they removed the option to restart the phone. When I just "power off" all my recent apps are still remaining. This makes me think it is not truly resetting cache and doing a full re-boot. Is this true? If so, is there a way to do a "cold boot" or full restart? (Not wipe, just reboot)
Thanks in advance!
mikeosu said:
Hi All, quick question. Since upgrading to 5.1 on my verizon Moto X, I noticed that they removed the option to restart the phone. When I just "power off" all my recent apps are still remaining. This makes me think it is not truly resetting cache and doing a full re-boot. Is this true? If so, is there a way to do a "cold boot" or full restart? (Not wipe, just reboot)
Thanks in advance!
Click to expand...
Click to collapse
i believe you need to root to enable reboot mode.
jco23 said:
i believe you need to root to enable reboot mode.
Click to expand...
Click to collapse
Bummer, kind of lame there is no option.
Sent from my XT1060 using Tapatalk
mikeosu said:
Bummer, kind of lame there is no option.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
check on the play store, I know that some apps (although may require root), may let you reboot. look at titanium backup for example.
jco23 said:
check on the play store, I know that some apps (although may require root), may let you reboot. look at titanium backup for example.
Click to expand...
Click to collapse
That's a little annoying Motorola would make it so that I have to root my phone just to reboot it.
Sent from my XT1060 using Tapatalk
Not Motorola, Google Android.
Sent from my Moto X using XDA Free mobile app
jco23 said:
Not Motorola, Google Android.
Sent from my Moto X using XDA Free mobile app
Click to expand...
Click to collapse
Oh, didn't realize it was Android that prevents that. So there is no way to really refresh the system if it seems to be getting bogged down?
mikeosu said:
Oh, didn't realize it was Android that prevents that. So there is no way to really refresh the system if it seems to be getting bogged down?
Click to expand...
Click to collapse
Turn it off, turn it back on.
Jizzylax said:
Turn it off, turn it back on.
Click to expand...
Click to collapse
Oh, I was doubting whether that really reset anything because all my recent apps are still there. But if it has a similar effect, awesome.
Sent from my XT1060 using Tapatalk
mikeosu said:
Oh, I was doubting whether that really reset anything because all my recent apps are still there. But if it has a similar effect, awesome.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
here's how to root on the latest OS: http://forum.xda-developers.com/moto-x/general/root-moto-x-att-xt1058-5-1-lpa23-12-21-1-t3164125
you may also be able to boot in the stock recovery by holding down all 3 buttons (power + volume up + volume down) for 5 seconds, then release power & volume up. once in recovery, navigate with the volume down button only (volume up = enter). from there, you may be able to wipe cache/dalvik which can help clear out the cob webs. this is safe and does not wipe data or factory resets.
also, if you go to your settings -> storage, you can clear out cached data.
hope this helps.