Re: Milestone CM Help!
Received this via PM but I'm replying here so it can assist others.
There is no way ADW would have such a low priority if it's the only launcher.
And yes, when you set an app to Keep Alive or increase its priority, it's not permanent - that's why I came up with the bulletproof launcher command.
It shouldn't matter, but I'm on CM612 and I don't see ADW anywhere in AMM's process list on my phone.
It's just lumped in with android.process.acore and in the process details it doesnt say ADW either - it's referred to as "com.android.launcher"
Also, be sure to have a blank line at the end of local.prop after the bulletproof launcher entry and be sure the set the permissions of local.prop properly. ie.
Also, you can take a look at the screen cap at the end of the OP to see what the permissions look like in SuperManager so you can do it graphimagically.
Received this via PM but I'm replying here so it can assist others.
Do you have more than one launcher?BlazinFire said:Hi there,
I saw your posts regarding AMM and the Home Screen redraws in the Milestone forums. I'm running a CM7 RC3 0.07-11.03.09 right now on my Milestone. Im pretty happy with it except for the frequent and annoying Home resets.(I just have 2 Home Screens with a SoundHound and Clock/Weather widget)
So basically i tried the AMM Values that you suggested (6,10 etc...)
But that didnt work. I tried setting ADW (Which shows up as a Hidden Application) to the Never Kill in AMM( -17 priority) But it would still end up redrawing and resetting the priority back to 6.
Neither did the Bulletproof launcher thingie work
If i add the ro.HOME~ line in local.prop and untick Keep in Memory in Cyanogen settings, the Priority is still 6. (And it still dies)
If i keep it ticked, its at 1. (Donno if it matters but im desperate here!)
Sorry for the long msg and i hate to be a bother but id REALLY appreciate your help!
Thanx!
There is no way ADW would have such a low priority if it's the only launcher.
And yes, when you set an app to Keep Alive or increase its priority, it's not permanent - that's why I came up with the bulletproof launcher command.
It shouldn't matter, but I'm on CM612 and I don't see ADW anywhere in AMM's process list on my phone.
It's just lumped in with android.process.acore and in the process details it doesnt say ADW either - it's referred to as "com.android.launcher"
Also, be sure to have a blank line at the end of local.prop after the bulletproof launcher entry and be sure the set the permissions of local.prop properly. ie.
Code:
chmod 644 /data/local.prop