7 replies to this topic

[bobbyp]

I have used Nova Launcher off and on for about a year on my original Droid Razr. I did the manual update to Jelly Bean after it was released. I just reinstalled Nova a couple of days ago and it just closes. It is not a FC close but if I am in an app (mostly text but others as well) when I exit out it goes back to my stock launcher. Nova is set as my default and I can not find a setting anywhere to fix it. All I have to do is hit my home button and Nova starts up again.

What am I missing?

Thanks for any help.

[tmyinc]

Go into Nova settings then advanced and tick "aggressive desktop" and see if it helps. Ive noticed this bug on JB in general. If i hit the home button i am fine but if i try to back out of an app it sometimes happens.

Sent from my DROID BIONIC using Tapatalk 2

[bobbyp]

Thanks for the fees back. I just made the change and will see if it keeps doing it.

[tmyinc]

Thanks for the fees back. I just made the change and will see if it keeps doing it.

No problem. Let me know if you have any issues. Basically that setting tries to keep nova launcher in memory to reduce redraws and fc's but I think it will help keep it from being killed like it is doing fir you.

Sent from my DROID BIONIC using Tapatalk 2

[bobbyp]

Well it didn't stop it but I will see how often it happens. I really like Nova but its pretty annoying when it closes. I might email the developer and see if they have a solution to it and post back.

[mamawm]

this also happens to me on my zoom, but only when i'm in gmail and hit the back button. if i just use the home key when i'm finished in gmail, i have no issues and i haven't noticed it happening on any other apps.

[bobbyp]

Well it hasn't been happening since I hard rebooted my phone several times in a row. I did send an email to the devoloper last week and they never responded. I am very disappointed in that. I don't expect a response in the first 24 hours but 5 days does seem pretty reasonable to get back to a person.

[mamawm]

I'm really disapointed that the developer didn't respond to you. There is definitely an issue on jb.