This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
From what I understand it tells android to keep your home app in the system memory.
I use quickdesk along with adwlauncher and quickdesk is actually used as the default "launcher" even though its basically an app laid over the top of adw. The echo code works flawlessly for me.
do you only put the code in when you switch roms? or every time you reboot?
also, never herd of quick desk. what is its function?
Additionally, i can confirm that the camera in the dark acts a little weird since the flash flickers in an attempt to auto focus, but I do get a good quality picture
do you only put the code in when you switch roms? or every time you reboot?
also, never herd of quick desk. what is its function?
Additionally, i can confirm that the camera in the dark acts a little weird since the flash flickers in an attempt to auto focus, but I do get a good quality picture
do you only put the code in when you switch roms? or every time you reboot?
also, never herd of quick desk. what is its function?
Additionally, i can confirm that the camera in the dark acts a little weird since the flash flickers in an attempt to auto focus, but I do get a good quality picture
do you only put the code in when you switch roms? or every time you reboot?
also, never herd of quick desk. what is its function?
Additionally, i can confirm that the camera in the dark acts a little weird since the flash flickers in an attempt to auto focus, but I do get a good quality picture
The code works for ALL launchers as long as it is your default, and Quickdesk is a drawer that you can set up to open from the bottom with a gesture. I make the "swipe up" gesture to open it so it looks like an extra pane.
How is this any different than the "keep in memory" options of ADW and LP? Also youre experience may be a lot different than ours since youre technically running CM on completely different hardware than us since youre using an iPhone.
Myself I've been having a ton of problems with the builds after 169, including the RC4.
How is this any different than the "keep in memory" options of ADW and LP? Also youre experience may be a lot different than ours since youre technically running CM on completely different hardware than us since youre using an iPhone.
Myself I've been having a ton of problems with the builds after 169, including the RC4.
I'm not running CM on an iPhone! It runs donut, basically.
I actually USE my droid and it has had many version of CM on it for quite a long time. And the "keep in memory" options, to my knowledge are all launcher specific. The code actually builds a local.prop file with that code in it that is only specific to whatever is set as the default.