Related
In my new Moto G Indian dual sim bversion Asphalt 8 is sometimes crashing suddenly without any error message like 'Unfortunately Asphalt 8 stopped' etc. It's directly comes to the homescreen quitting the game all of a sudden... Is there any problem with the game or firmwire? I downloaded directly from PlayStore. Any same incident or help?
Did you try reinstalling it?
Sent from my Moto G running Carbon ROM 4.4.4
noeticdm said:
In my new Moto G Indian dual sim bversion Asphalt 8 is sometimes crashing suddenly without any error message like 'Unfortunately Asphalt 8 stopped' etc. It's directly comes to the homescreen quitting the game all of a sudden... Is there any problem with the game or firmwire? I downloaded directly from PlayStore. Any same incident or help?
Click to expand...
Click to collapse
try freeing some space & clear cache
I did it.. Cleared cache and data too several times. Even did fresh reinstall from PlayStore. Same problem occurring again. Even sometimes just before the end of a race and coming 1st position game suddenly crashed. Total frustration! Space available a lot already!
noeticdm said:
I did it.. Cleared cache and data too several times. Even did fresh reinstall from PlayStore. Same problem occurring again. Even sometimes just before the end of a race and coming 1st position game suddenly crashed. Total frustration! Space available a lot already!
Click to expand...
Click to collapse
Are you playing in High Specs or in the Recommended Medium one ?
Marakatu said:
Are you playing in High Specs or in the Recommended Medium one ?
Click to expand...
Click to collapse
All spec.. Very low, low, high, medium.. same problem occurring.
noeticdm said:
All spec.. Very low, low, high, medium.. same problem occurring.
Click to expand...
Click to collapse
That's really strange. Does someone else have the same issue with their Moto G 2nd ? I still can't test it because mine did not arrive yet. Hope to get it till next Monday.
Moto g crashes
Marakatu said:
That's really strange. Does someone else have the same issue with their Moto G 2nd ? I still can't test it because mine did not arrive yet. Hope to get it till next Monday.
Click to expand...
Click to collapse
I've just got a moto g (1 gen) LTE model running 4.4.4... from amazon in the UK. I thought I'd try Asphault 8 to test out the phone today. Crashes back to the homescreen with no message whatsoever from the menus, during loading and sometimes I can get it to just get into the game.. when I use task manager to got back into the game it just loads from the start again (Gameloft logo). I haven't actually been able to get through the tutorial at all. Medium (default) settings.
Any ideas?
i think ram management problem in the new moto g 2nd gen... I never have this problem on moto g(2013)
same
same problem tried it several times always crashes no matter what u do
same problem here is due to low ram clear ram before playing game.
Asphalt 8 not working for me too..
The same happening to me too..
you are right---"i think ram management problem in the new moto g 2nd gen"
This happens with the background apps also.. closes for no reason...
Yeah the problem exists.
Asphalt 8 does crash to main screen and many apps are closed in the background. Can someone tell what issue is that and how can that be handalled. Also Firefox and Chrome don't keep the tabs loaded in the background. The tabs reload even if you jump from tab to tab, which is very bad and inconvenient. If someone finds a solution please tell, waiting for reply.
All this problem have only 1 reason low ram problem try to free up ram before playing any game u always disable apps that you dont use like some motorola app to free up ram.
Clearing RAM is not a proper solution. It crashes even after that. In KK ram is cleared a=by automatic in built tasker. Anyway, after a much research and tinkling with my Moto G2 I finally came with a successful solution. Most of the time with high graphic most part like Dubai track with high speed car the chance of crashing suddenly is more. Moto G 2 has a serious RAM management problem. Hope this bug may be corrected in L update very soon. With smaller application it is not felt particularly.
Anyway, root your phone first. Install RAM manager (paid app) and any build.prop editor. First edit your build.prop section the VM Heap size to 512 mb and VM Heap growth limit 256 mb. No matter, due to less collection of paging garbage your battery backup should also increase a little. But your RAM potential will be utilised at fullest. Now go to ram manager set 'Hard Multitasking Mode' and clear memory with it before playing the game. Asphalt 8 will never crash!! Tested!!
noeticdm said:
Clearing RAM is not a proper solution. It crashes even after that. In KK ram is cleared a=by automatic in built tasker. Anyway, after a much research and tinkling with my Moto G2 I finally came with a successful solution. Most of the time with high graphic most part like Dubai track with high speed car the chance of crashing suddenly is more. Moto G 2 has a serious RAM management problem. Hope this bug may be corrected in L update very soon. With smaller application it is not felt particularly.
Anyway, root your phone first. Install RAM manager (paid app) and any build.prop editor. First edit your build.prop section the VM Heap size to 512 mb and VM Heap growth limit 256 mb. No matter, due to less collection of paging garbage your battery backup should also increase a little. But your RAM potential will be utilised at fullest. Now go to ram manager set 'Hard Multitasking Mode' and clear memory with it before playing the game. Asphalt 8 will never crash!! Tested!!
Click to expand...
Click to collapse
I changed only build.prop as you write on my Moto G LTE (1 gen.) and now Asphalt 8 works fine. No more force close. Thanks!
I had this problems with asphslt 8 and other big games... I wont root until 5.0, but I hope motorola release an ota to fix thid ram bug...My 1st gen Moto G didnt have this bug
Same Problem.. But is Rooting the only solution
I am facing the same problem as GT racing 2 also force closes. and Real Racing 3 too tried several apps but i'm unable to run all the apps. what to do
asphalt 8 :airborne
I have installed Asphalt 8: Airborne on my XT1068 , and it runs smoothly with good graphics ( i didn't change any settings for graphics in the game )
the game crashed 2 times after installing , but it has worked fine ever since i rebooted the device once
my device is rooted but there is no optimization apps .
Real racing 3 also worked fine without a single crashed, since i haven't installed many apps there is always about 300mb RAm free
Asphalt 8 crash on Moto G2
I'm facing the exact same problem on my Moto G 2nd Gen. What do I do? I really want to play this game.
My gf's Moto X (1st gen, stock, unrooted, Verizon, 4.4.4) has been freaking out lately and she brought it to me to investigate. The thing will sporadically tie up all of its RAM and basically become unusable. Phone gets hot and battery drains fast.
I understand how Android handles memory, so this isnt me being paranoid about available RAM...im talking about less than 20mb of available RAM and I cant even open the app drawer because it crashes. I clear all recent apps, force close anything i can, and no RAM opens up at all. Only solution is reboot and then its only good for a few hours until it gets jammed up again.
Sounds like a software issue to me, so a factory reset should fix it, but i just dont want to deal with backing up my gf's crap and heaven forbid i miss something and lose it forever. Anyone have any ideas?
PS - gsam battery monitor shows nothing noteworthy...doesnt report weird app usage, and no wakelocks or anything like that seems out of the ordinary.
prittjr said:
My gf's Moto X (1sr gen, stock, unrooted) has been freaking out lately and she brought it to me to investigate. The thing will sporadically tie up all of its RAM and basically become unusable. Phone gets hot and battery drains fast.
I understand how Android handles memory, so this isnt me being paranoid about available RAM...im talking about less than 20mb of available RAM and I cant even open the app drawer because it crashes. I clear all recent apps, force close anything i can, and no RAM opens up at all. Only solution is reboot and then its only good for a few hours until it gets jammed up again.
Sounds like a software issue to me, so a factory reset should fix it, but i just dont want to deal with backing up my gf's crap and heaven forbid i miss something and lose it forever. Anyone have any ideas?
PS - gsam battery monitor shows nothing noteworthy...doesnt report weird app usage, and no wakelocks or anything like that seems out of the ordinary.
Click to expand...
Click to collapse
Version of Android? Carrier?
What apps are installed? Non-stock launcher?
k_t_b said:
Version of Android? Carrier?
What apps are installed? Non-stock launcher?
Click to expand...
Click to collapse
Updated in OP. Verizon, latest version (i believe Verizon has 4.4.4 up for moto x, so that would be the one)
prittjr said:
Updated in OP. Verizon, latest version (i believe Verizon has 4.4.4 up for moto x, so that would be the one)
Click to expand...
Click to collapse
Something like Watchdog Task Manager or a memory monitor app might help you figure out what's misbehaving. Logcat might give some clues.
Personally, I think I would just prefer to backup what is necessary and reset the device. You might spend a lot of time trying to attack this from any other direction. Good luck.
I'm a really big fan of the look and feel of this phone, but I have noticed an alarming issue. It reminds me of the original HTC One that only had 1GB of RAM.
If I test it side-by-side with my OnePlus One, LG G3, or Note 4, I get the same results: Clearing all apps from memory and then systematically opening the same apps on both phones, if I multitask back to any of them on the Moto X, they have to completely reload. Every Chrome page reloads, too. I have also noticed that Nova launcher redraws with regularity, even when I check the option to force it to stay in memory.
My question is: Was it this bad on 4.4.4? Or is it a Lollipop issue? Because I updated to 5.0 right out of the box and if rolling it back will fix this, I'm all for it. There's no excuse for apps reloading this frequently on a modern smartphone with 2GB of RAM.
That's a Lollipop issue. No such problems on KitKat.
_MetalHead_ said:
That's a Lollipop issue. No such problems on KitKat.
Click to expand...
Click to collapse
Thanks, dude. Looks like I'll be rolling back.
greyhulk said:
Thanks, dude. Looks like I'll be rolling back.
Click to expand...
Click to collapse
Yep, no prob. That's why all my devices are still on KK.
Flashed back to Kitkat. Memory management is definitely worse on 5.0, but even 4.4.4 kills apps faster than it should. Even with 1GB available most of the time, apps have to refresh much more often than they should.
Testing Methodology:
Side-by-side with OnePlus One
Open the same 7 apps on both phones (Dialer, Feedly, Reddit Sync Pro, Chrome to androidcentral.com, camera, Nine email client, messaging)
Cycle back and forth between apps using multitasking button on both phones
Observe app reload instances
Results: The OPO NEVER reloads anything. My Moto X will be fine for the first 3 or 4 apps, then it will reload the app completely, including androidcentral.com on Chrome. And if I have multiple tabs open in Chrome, it's worse. Yes, the OPO has 3GB of RAM, but there is still 1GB free on the Moto X when I perform this test, so there's no reason it should be actively killing the apps that quickly.
That being said, it is markedly better than on 5.0. Nova launcher NEVER redraws now, whereas it did constantly before. And I was never even able to cycle between two apps without one of them reloading. Still, I wish it handled memory a little better. This is eerily similar to the issue that plagued the original HTC One and it drove me to sell that phone.
I'm not here to bag on this phone. I'm a huge fan. I just want people to be informed.
greyhulk said:
Flashed back to Kitkat. Memory management is definitely worse on 5.0, but even 4.4.4 kills apps faster than it should. Even with 1GB available most of the time, apps have to refresh much more often than they should.
Testing Methodology:
Side-by-side with OnePlus One
Open the same 7 apps on both phones (Dialer, Feedly, Reddit Sync Pro, Chrome to androidcentral.com, camera, Nine email client, messaging)
Cycle back and forth between apps using multitasking button on both phones
Observe app reload instances
Results: The OPO NEVER reloads anything. My Moto X will be fine for the first 3 or 4 apps, then it will reload the app completely, including androidcentral.com on Chrome. And if I have multiple tabs open in Chrome, it's worse. Yes, the OPO has 3GB of RAM, but there is still 1GB free on the Moto X when I perform this test, so there's no reason it should be actively killing the apps that quickly.
That being said, it is markedly better than on 5.0. Nova launcher NEVER redraws now, whereas it did constantly before. And I was never even able to cycle between two apps without one of them reloading. Still, I wish it handled memory a little better. This is eerily similar to the issue that plagued the original HTC One and it drove me to sell that phone.
I'm not here to bag on this phone. I'm a huge fan. I just want people to be informed.
Click to expand...
Click to collapse
Actually WOW. I made same comparison with N5 running 5.0.1. And Moto X is worse.. I'm surprised nobody noticed that fact earlier or in the reviews. If L on X is worse than KK I am definitely not updating. Love that phone, it's such a bummer that memory management is so aggressive.. But it's behavior on KK is little bit wired and different than L. Apps running in the background like for example last pass, are always there. And on L those were the ones to kill in the first place.
k_myk said:
Actually WOW. I made same comparison with N5 running 5.0.1. And Moto X is worse.. I'm surprised nobody noticed that fact earlier or in the reviews. If L on X is worse than KK I am definitely not updating. Love that phone, it's such a bummer that memory management is so aggressive.. But it's behavior on KK is little bit wired and different than L. Apps running in the background like for example last pass, are always there. And on L those were the ones to kill in the first place.
Click to expand...
Click to collapse
Thanks for confirming. Usually when I post something like this, people reply and tell me I'm crazy or that their phone "multitasks fine".
Assuming that it's intentional, the only reason I can think Moto would do this is for battery life reasons (so nothing is running in the background draining), since it has a smaller battery. The other possibility is that they did it for the Moto G, which has 1GB of RAM and then just used the same image for both phones for the sake of consistency.
Either way, it's disappointing, especially after using the OPO and seeing the difference side-by-side. Really love this phone, but this bothers me more than it should.
I've noticed L is worse on the X versus my N5 as well. Navigating with maps and playing google music in the car is a nightmare.
Is this supposed to be fixed in 5.1?
I'm surprised not to see more posts about this issue. I've been noticing on my own phone that whenever I launch chrome or Google maps it tends to kill anything else that's running in the background (pocket casts, swipe pad, smart lock, stock launcher, etc.) it basically makes for a pretty unpleasant experience. Does anyone know if this is supposed to be fixed in 5.1?
I can confirm this issue too. Just to add more monitoring tool when you want to check the memory when such thing happens: developer options>>process stats>>duration 1 day>>click on the green bar and note the timing for which the memory was critical. I think the system deems the memory to be critical when it passes 1gb and starts to kill apps in the background. It never used to be like this on 4.4.4.
Please help contribute if you have any knowledge about using these stats.
Edit: i also noticed that during the time the memory was critical, the battery level dropped like a stone from 65%-55%. So i think its all also connected to the battery consumption being too much at times.
Sent from my XT1092
Her'es my figures (phone uptime: only 17h)
Very bad I guess:
CoolRaoul said:
Her'es my figures (phone uptime: only 17h)
Very bad I guess:
Click to expand...
Click to collapse
OMG that is pretty bad! Was your phone going wonky at that time? I mean battery life and apps crashing etc
Sent from my XT1092
grubber24 said:
OMG that is pretty bad! Was your phone going wonky at that time? I mean battery life and apps crashing etc
Click to expand...
Click to collapse
No crashes nor battery drain but many launcher restarts.
I've now uninstalled an app ( "Lazy Swipe" which was on the "top" list) and seen a little improvement (no more launcher restart for the last 3 hours)
I plan to investigate a bit further, I may have another potential culprit (HeadsUp which I'm only using in car dock mode but appear to consume a lot of RAM and is running all of the time)
**EDIT**
BTW, I'm not running very memory intensive app like games.
CoolRaoul said:
No crashes nor battery drain but many launcher restarts.
I've now uninstalled an app ( "Lazy Swipe" which was on the "top" list) and seen a little improvement (no more launcher restart for the last 3 hours)
I plan to investigate a bit further, I may have another potential culprit (HeadsUp which I'm only using in car dock mode but appear to consume a lot of RAM and is running all of the time)
**EDIT**
BTW, I'm not running very memory intensive app like games.
Click to expand...
Click to collapse
Yeah unfortunately even when there is so much ram and you cant use many apps. I you wish you can report this to motorola on their forum. I have created a thread there: https://forums.motorola.com/posts/115c66d6c7
Sent from my XT1092
After having uninstalled HeadsUp I've noticed a significant boot in responsiveness.
I'm going to keep an eye on memory stats for the next few hours
CoolRaoul said:
After having uninstalled HeadsUp I've noticed a significant boot in responsiveness.
I'm going to keep an eye on memory stats for the next few hours
Click to expand...
Click to collapse
I would suggest observing these for a full day without restarting. Then report to motorola. For me it was google plus updates causing the issue with memory. When i uninstalled updates it stopped. So also check the timing for which the apps are running in Application settings>>running. If the time for which the app is running is lesser than the total uptime, it might be your suspect.
Sent from my XT1092
grubber24 said:
I have created a thread there: https://forums.motorola.com/posts/115c66d6c7
Click to expand...
Click to collapse
I was already subscribed to that thread. But since my memory issues are pretty new, I prefer to start investigating by myself
Just a quick question for everyone. My apps close by themselves in the background. WhatsApp and Facebook Messenger are the 2 worst perpetrators. I will stop receiving messages unless I open the app once every 15 minutes. If I forget, I'll open the app and suddenly get flooded with a ton of "new" messages.
This only started happening since 5.0. I've unlocked my bootloader and installed the Pure Edition 5.0.1 and then upgraded to 5.1 leak and have the same issue. I've wiped my phone and that does nothing. I don't think it's the memory leak glitch because I will have more than 1gb of RAM free when these problems are happening.
Is it a rogue setting in 5.0 that's causing these problems? Has anyone seen this before? I'm back on my 2013 Moto X temporarily until I figure this out, but I'd love to go back to my 2014 X.
Thanks everybody!
This is a known memory leak issue with 5.0. It's supposed to be fixed with 5.1 but I haven't had an update so I can't confirm. Music playing in the background and Bluetooth are issues for me.
ShensMobile said:
My apps close by themselves in the background.
Click to expand...
Click to collapse
Same problem here. For me, the app which gets restarted most often is Nova Launcher. Rebooting the phone fixes this for some time (one or two days) but eventually it come back again
TriumphGuy said:
This is a known memory leak issue with 5.0. It's supposed to be fixed with 5.1
Click to expand...
Click to collapse
This only started happening since 5.0. I've unlocked my bootloader and installed the Pure Edition 5.0.1 and then upgraded to 5.1 leak and have the same issue. I've wiped my phone and that does nothing. I don't think it's the memory leak glitch because I will have more than 1gb of RAM free when these problems are happening.
Is it a rogue setting in 5.0 that's causing these problems? Has anyone seen this before? I'm back on my 2013 Moto X temporarily until I figure this out, but I'd love to go back to my 2014 X.
Click to expand...
Click to collapse
I agree with TriumphGuy and am pretty sure the source *is* the memory leak bug since the symptoms are the same.
BTW I will be very disapointed if this issue is confirmed not being fixed un the upcoming 5.1 official release
Hello there,
I'm experiencing a problem with my Moto G 2014 XT1068.
When I'm inside an app and tab the multitask button. The app shrinks to a certain size and then it jumps to the stack of running apps. This looks very unsmooth and buggy. I'm wondering if this is a problem with 5.0.2 or some kind of bug and if i;m the only one experiencing this problem.
Kind regards
5.0.2 has a memory leak and Moto G only has 1GB of RAM so the multitasking is not the best on our phone unfortunately.