As many of others Optimus 4x owners I've notice that when I use a ram intensive application, JB 4.1.2 automatically kills LG Home application, so return to home screen take some time (4 seconds), Is there a way to maintain LG Home app alive even with high RAM use?
I don't think so. S3 had a Redraw problem as well.
If it helps, I use Apex Launcher, which has the option to keep it constantly in memory.
ro.HOME_APP_ADJ=1
to build.prop
Emmanuel2000 said:
ro.HOME_APP_ADJ=1
to build.prop
Click to expand...
Click to collapse
Yup...This is one way by forcing launcher into memory to prevent re-draw,,,
Emmanuel2000 said:
ro.HOME_APP_ADJ=1
to build.prop
Click to expand...
Click to collapse
Thanks, it worked, by the way, you need root privileges and build.prop it's located under /system
Related
Hi, is possible to increase the speed of rotation for screen in topaz ?
thanks for reply
sorry for my english
uberto.costanzo said:
Hi, is possible to increase the speed of rotation for screen in topaz ?
thanks for reply
sorry for my english
Click to expand...
Click to collapse
I would think this would be related to performance in general. So if the phone is performing well, it rotates quickly. If it's performing poorly, it rotates slowly...
There's a few things you can try to improve performance. Overclocking helps a little, but it's not a huge difference. Keeping apps from auto-starting on boot helps, I'm not sure of a simple way on how to do it... Suggested method for preventing apps from auto-starting.
That same user also uses an app called 'DroidWall' to prevent apps from connecting without permission. Might help with performance as well (not sure, but it can't hurt).
Anything that will slow down your phone has to go. Widgets are killer I've found... As much as I like them, they made the home screen SO slow. On that same tangent of home screens, have you looked at different launchers? The stock 'Launcher2' is kinda slow itself. I like ADW myself - there's many others out there (Zeam, GoLauncher EX, Launcher Pro to name a few...)
arrrghhh said:
I would think this would be related to performance in general. So if the phone is performing well, it rotates quickly. If it's performing poorly, it rotates slowly...
There's a few things you can try to improve performance. Overclocking helps a little, but it's not a huge difference. Keeping apps from auto-starting on boot helps, I'm not sure of a simple way on how to do it... Suggested method for preventing apps from auto-starting.
That same user also uses an app called 'DroidWall' to prevent apps from connecting without permission. Might help with performance as well (not sure, but it can't hurt).
Anything that will slow down your phone has to go. Widgets are killer I've found... As much as I like them, they made the home screen SO slow. On that same tangent of home screens, have you looked at different launchers? The stock 'Launcher2' is kinda slow itself. I like ADW myself - there's many others out there (Zeam, GoLauncher EX, Launcher Pro to name a few...)
Click to expand...
Click to collapse
thanks arrrgggh,
the my android is very very fast i have problem only with rotation when is in landscape 3-4 second for portrait is normal?
uberto.costanzo said:
thanks arrrgggh,
the my android is very very fast i have problem only with rotation when is in landscape 3-4 second for portrait is normal?
Click to expand...
Click to collapse
So it rotates quickly portrait -> landscape, but landscape -> portrait is slow...? I don't think I've heard of that one... Anyone else?
I'm not sure what can be done to fix that to be honest... new one to me .
In Nitrality and Spare parts,
There is an option to make the animations faster. After enabling it, the lag on my Note completely disappears !
What does it really do ? Where can I manually adjust those parameters in the system without using those third party apps ?
Thanks!
Framework Res APK does not hold any adjustable parameters regarding Menu transitions that has a delay. :-(
Still Searching...
All it does is either speed up or remove the animations which are one of the causes of lag..
joshnichols189 said:
All it does is either speed up or remove the animations which are one of the causes of lag..
Click to expand...
Click to collapse
By Any chance do you know, How it is manually done ?
I do not, sorry. All I know is how to do it through Spare Parts or developer options on ICS.
Nitrality Still works. !
Wondering whether its a lib file!
hello guys I want to know in iphone when you click power button the screen turns on immediately but in Zeus 6.33Bn (also all roms I have tested contains stock rom ) it opens after 2/3 seconds some times if there is a lot of apps are working it take 5-15 seconds to open
any solutions ??
Why not using task killer ?
Vinzgore said:
Why not using task killer ?
Click to expand...
Click to collapse
what??
will it affect ??!!!
He mean: Why dont you close some unnecessary app?
and I don't see a big difference between 2/3s and immediately to wake up the phone ^^
no14me said:
He mean: Why dont you close some unnecessary app?
and I don't see a big difference between 2/3s and immediately to wake up the phone ^^
Click to expand...
Click to collapse
I agree!
But using auto task killer will speed up a bit your phone.
If you want you phone even better, use supercharger script.
Sent from my LG-P970 using Tapatalk 2
Some guys say that the ATK are bad for phone
hemo-ali said:
Some guys say that the ATK are bad for phone
Click to expand...
Click to collapse
To my mind, it changes nothing or nearly nothing i use advanced task killer and im using it seldom, after charging only, or when i want to play some demanding game...
But, sticking to the topic, i would advice changing processor governor, what were you using? Are you using custom lockscreen like go launcher or widget locker?
Hbohd said:
To my mind, it changes nothing or nearly nothing i use advanced task killer and im using it seldom, after charging only, or when i want to play some demanding game...
But, sticking to the topic, i would advice changing processor governor, what were you using? Are you using custom lockscreen like go launcher or widget locker?
Click to expand...
Click to collapse
I'm using zeus and it has the default ginger bread lockscreen and I'm on smartass2
Its quite weird, because smartass2 is rather aggressive governor. However, this long-time waiting (5-15sec) comes from lowering CPU frequency to really low, deep sleep numbers.
If its a real problem for you, you can easily increase lowest CPU freq and see if it changes anything. And second thing which comes to my mind, check in build.prop line "pm.sleep_mode=1". It causes device to get into deep sleep.
But, of course these changes will affect battery life... quite strongly :/
Hbohd said:
Its quite weird, because smartass2 is rather aggressive governor. However, this long-time waiting (5-15sec) comes from lowering CPU frequency to really low, deep sleep numbers.
If its a real problem for you, you can easily increase lowest CPU freq and see if it changes anything. And second thing which comes to my mind, check in build.prop line "pm.sleep_mode=1". It causes device to get into deep sleep.
But, of course these changes will affect battery life... quite strongly :/
Click to expand...
Click to collapse
thnx all
So, I have galaxy mini with slim cm7 revision 1(I think it's fastest) with Zeam launcher and I was just wondering is there a way to kill launcher while playing games? I can kill it from settings but when i come to apps list it opens again(and it's normal because without it you can't see that list)...any way to switch directly from settings to game you want to play without auto re-opening launcher? Or some other way? Thanks.
nope, btw. with zeam's ram consumption it's actually pointless
yackovsky said:
nope, btw. with zeam's ram consumption it's actually pointless
Click to expand...
Click to collapse
Thanks if you are sure there is no way(if anyone other knows way please say it), but I need to correct you: yes, if you look at applications and cached processes, you will see that Zeam uses about 6.8 MB RAM, BUT it uses as other launchers: cache + task, and I think you didn't look at Zeam task org.zeam.core which uses about 24.53 MB RAM(that's current size when i looked at it now)...so total consumption of Zeam is about 31.4 MB of RAM...just saying...I think it will help a little for games if there is a way to kill it while playing games...
minicm7 said:
Thanks if you are sure there is no way(if anyone other knows way please say it), but I need to correct you: yes, if you look at applications and cached processes, you will see that Zeam uses about 6.8 MB RAM, BUT it uses as other launchers: cache + task, and I think you didn't look at Zeam task org.zeam.core which uses about 24.53 MB RAM(that's current size when i looked at it now)...so total consumption of Zeam is about 31.4 MB of RAM...just saying...I think it will help a little for games if there is a way to kill it while playing games...
Click to expand...
Click to collapse
But btw don't think that Zeam isn't better than other launchers, yes, it's better, it uses about 5-8 MB less than other launchers(3 MB less in task + 3 MB less in cache than ADW launcher)
I found a way
OK it doesn't matter anymore...I found a way...
1.Just first open game you want to play so that it will be in recent apps(when you press long home)
2. then go home, then go to settings
3. close launcher,
4. now with recent apps switch to game and again switch with recent apps back to settings
5. now kill settings with settings, now settings will close and it will switch to game because that game is last app opened before settings app...
plz press thanks if I helped you and saved your RAM...
NOTE: this metod won't work if usually can't kill launcher, for the example if you have bulletproof launcher installed with V6 it won't work because no matter to what, you can't kill launcher, even with some root killer...
STEP 4 EXPLAIN: if you skip this step, when you finish step 6, it won't switch you to game, it will switch you to home, so launcher will open again, because it will remember home as last app
Also you can after 3. step switch to game, and then stay at game and play, but remember: settings will still be opened in background, and it uses about 13 MB of RAM...
lmfao
Holo launcher its better
Push to system
Sent from my GT-S5570 using xda app-developers app
have u tried holo launcher?
I have no problems witch force close when using it...
Or Launcher Pro...
hi all
my Xperia TX 4.3 maybe have problem all icon at main home screen always redraw when i run an app then quit by press Home button, i add
this code ro.HOME_APP_ADJ=1 to build.prop but didn't solve my problem. please help me. thanks.
ok, i've got it. check Disable HW overlays in develop options and no more redraw icons
devilmaycry2020 said:
ok, i've got it. check Disable HW overlays in develop options and no more redraw icons
Click to expand...
Click to collapse
http://www.jeffmixon.com/examining-build-prop-tweaks-android-ics-comprehensive-guide-part-2/
I recommend reading part 1 also, but just to summarize:
ro.HOME_APP_ADJ – BUSTED
This property is supposed to “keep the launcher in memory” under the assumption that it would somehow make it faster. Unfortunately, this is a leftover Gingerbread property that no longer functions in ICS.
Gingerbread:
Code:
// These values are set in system/rootdir/init.rc on startup.
...
HOME_APP_ADJ = getIntProp("ro.HOME_APP_ADJ", true);
ICS:
Code:
static final int HOME_APP_ADJ = 6;
Google likely removed the ability to configure this value via a build.prop setting in ICS so that users could not set inappropriate values here.
SUMMARY
As we have seen many times already, there are no “magic properties” that you can set that will simply make your phone [insert desired superlative]. That is not to say that all build.prop settings are pointless. Some can actually provide some useful functionality. The key is not to blindly throw a slew of “tweaks” into your build.prop, but to carefully consider each one and know what they do (if anything) before using them.
That’s it for part two. Let me know what build.prop settings you want to see in part three!
Click to expand...
Click to collapse
If you really want to keep your launcher in memory, you can use App Settings (xposed module); I know for a fact it works because I use it, or you can even do it yourself with a script such as:
#!/system/bin/sh
sleep 60
PPID=$(pidof com.whatsapp)
echo "-17" > /proc/$PPID/oom_adj
Click to expand...
Click to collapse
To lower the oom value of the app you want to avoid getting killed off by android.