Database Develop

[MOD] LCD Density - DIY!

Ok guys, people seem to be having problems using the LCD Density changer app, so I am making this write up to help you out
If you would like to make your Droid X look like this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then follow these steps.
Method 1 - ADB
1. Download LCD Density w/ 2.2 market Fix - This also contains the 2.2 market fix (without the stagefright)
2. Put the build.prop in your android-sdk\tools folder
3. Connect your phone via usb, make sure it shows up with adb devices
4. adb remount
5. adb push build.prop /system/build.prop
6. adb reboot
Method 2 - Root Explorer
1. Copy the build.prop to the root of your SD card
2. Long press on build.prop
3. Select "Copy"
4. Navigate to /system
5. Click R/W in the top right corner
6. Paste, and overwrite
7. Reboot
Your screen will now look like this, giving you much more space. And If using ADW launcher, you can use 6 X 5 rows of icons!!
Now if you really like to do things yourself, in the build.prop..
Change
ro.sf.lcd_density=240
to
ro.sf.lcd_density=200
push, reboot.
If you want to revert back, just push this Stock Build prop back into place.
Credit to the guy who made LCD Density app, but it did not work with Droid X phone and koush's recovery installed. People had to SBF, so this post was necessary.

does this change the resolution ? does it affect any apps from running correctly ?
Looks great, I think I'd like to try it. Just want to make sure it's safe I guess.

JustinD2473 said:
does this change the resolution ? does it affect any apps from running correctly ?
Looks great, I think I'd like to try it. Just want to make sure it's safe I guess.
Click to expand...
Click to collapse
Its safe, I've tested and ran this in other forums.
You can read others trials here...
http://androidforums.com/droid-x-all-things-root/163974-mod-lcd-density-diy.html

Jacked mine up.. the method works fine, the only problem is that apps are completely screwy now.. the apps only show up in the original size so if your screen is 4 inches the app is only displaying in like 2.5 inches of space and the rest is just black now, also cause some fuzziness with some various icons in the notification bar ( battery etc).. definately gonna revert back

Joe92T said:
Jacked mine up.. the method works fine, the only problem is that apps are completely screwy now.. the apps only show up in the original size so if your screen is 4 inches the app is only displaying in like 2.5 inches of space and the rest is just black now, also cause some fuzziness with some various icons in the notification bar ( battery etc).. definately gonna revert back
Click to expand...
Click to collapse
Weird. Works perfect for me.

LexusBrian400 said:
Weird. Works perfect for me.
Click to expand...
Click to collapse
Only seemed to have resolution problems in the root explorer app, all other apps work fine Aside from that, i think 200 is probobly a little on the low side, may try 220 or 230 for a improvement

Yea I love it but a few of my apps are also little now. I'm gonna rock it tonight and see how I feel in the morning.
Sent from my DROIDX using XDA App

Worked well for me as well.
Thanks very much.
FYI
I couldnt adb remount (got an error, not sure why but whatever)
I had to boot into recovery, then do an
Code:
adb shell
then just (assuming your modified build.prop is on the sdcard root)
Code:
mv /sdcard/build.prop /system
exit & reboot!

230 was a good middle ground

Yeah, I like how it looks mostly but some apps don't strech which is kinda annoying. I'll give it a shot for a day or two and see what I think.
Sent from my DROIDX using XDA App

JustinD2473 said:
Yeah, I like how it looks mostly but some apps don't strech which is kinda annoying. I'll give it a shot for a day or two and see what I think.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Let me know what you think about it.... would Launcher Pro dock items still be the same size???

i recently Download app running 2.2. Changes resolution to 220 and let app reboot phone only to be stuck on Black screen after moto logo.tried rebooting and wiping with no luck. PC wont connect with phone either... i can only get into system recovery> any ideas guys????

jdifiore1 said:
i recently Download app running 2.2. Changes resolution to 220 and let app reboot phone only to be stuck on Black screen after moto logo.tried rebooting and wiping with no luck. PC wont connect with phone either... i can only get into system recovery> any ideas guys????
Click to expand...
Click to collapse
Yeah, dont use that app. That is the whole reason I created this mod. That app is causing problems.
Restore your nandroid backup, assuming u were smart enough to make one before messing with the phone the like that IF not, now you know! always nandroid before a mod!!!

i wasnt smart enough.. i guess that means my phones shot???

jdifiore1 said:
i wasnt smart enough.. i guess that means my phones shot???
Click to expand...
Click to collapse
No. I'll help you out. Do you use Gtalk? if so, PM me your email so we can make this easier.

Android Market Update comes with Tablet Tweaks

[Update: Screenshots below]
I just installed the latest update for Android Market (was v3.0.27 now v3.1.3).
First things I checked out were the Announced +1 buttons and PIN lock for Purchases features but I've noticed something else interesting.
First thing I noticed was that everything is slightly bigger (My PixelDensity is the same as before the update). Next thing I noticed is when I went to the Apps section, is that the Categories now Pull out into a Side-Pane instead of their own screen. But the most interesting thing I noticed is that instead of getting the "Staff Picks" screen, I get "Staff Picks for Tablets". To me it seems the App Market now detects your screen size and adjusts some things accordingly.
This can be a Good thing and a Bad thing. Good because tablet designed Apps(including the Market UI tweaks) do look better on the Nook's screen but also Bad because it could alow Google to adjust things depending on Device even more, ie: certain phone apps might only show up on "Phone sized" screens.
What do you guys think of the new Market Update(v3.1.3)?
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Does it fix the missing My Apps problem?

FletchF said:
Does it fix the missing My Apps problem?
Click to expand...
Click to collapse
Nope...
---
- Sent from my LG Optimus V using Tapatalk

FletchF said:
Does it fix the missing My Apps problem?
Click to expand...
Click to collapse
Here's the Fix.
If you don't see "Movies" category or the "Videos" app in the New Market here's a Fix.
NOTE: DO NOT USE IF USING OLD MARKET!!
If you have issues return it back to 161!
Root Explorer Method
1. Clear Market data in Application Info
2. Navigate to System folder in Root Explorer and "Mount R/W"
3. Long-press build.prop and "Open in Text Editor"
4. Find "qemu.sf.lcd_density=161" or "ro.sf.lcd_density=161" and change it to 160
5. Reboot
6. Run Market
File Expert Method
1. Clear Market data in Application Info
2. Navigate to /System folder in File Expert
3. Menu-->More-->Mount-->Mount as ReadWrite
4. Copy build.prop to sdcard
5. Press build.prop, Open as Text, Select a Text Editor
6. Find "qemu.sf.lcd_density=161" or "ro.sf.lcd_density=161" and change it to 160, now Save
7. Copy build.prop back to /System, Overwrite when asked
8. Reboot
9. Run Market
If it doesn't work try Clearing the Market data again.
This should allow you to see most missing Apps and Access the Movies category.
If you lose Movies in the Future just Clear the Market data and it'll work again.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk

Does this "fix" also deal with the issue that some of your installed apps don't show up in the Market's Update queue when they have updates available?

DiDGR8 said:
Does this "fix" also deal with the issue that some of your installed apps don't show up in the Market's Update queue when they have updates available?
Click to expand...
Click to collapse
Yes
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk

japzone said:
Here's the Fix.
Click to expand...
Click to collapse
...to a different problem. The issue with My Apps is the reason CM7 defaults to 161 in the first place, and only applies to those who have already applied the 160 dpi fix. In a CM7 NC set to 160 dpi, My Apps will eventually display only a white space, requiring us go to the Market's App Info and hit Clear Data again.
AFAIK, we're more likely to see a fix for the limited market than for the My Apps issue.
One thing many people seem to miss: any app's individual App Manager page is accessible by longpressing the app shortcut and choosing App Info.

Japzone, you're doing people a disservice by failing to mention that the fix does not persist once the market app does its data update, which occurs at least once a day.
Edit: damn, once again, ninja'ed by the lizard...

Taosaur said:
...to a different problem. The issue with My Apps is the reason CM7 defaults to 161 in the first place, and only applies to those who have already applied the 160 dpi fix. In a CM7 NC set to 160 dpi, My Apps will eventually display only a white space, requiring us go to the Market's App Info and hit Clear Data again.
AFAIK, we're more likely to see a fix for the limited market than for the My Apps issue.
One thing many people seem to miss: any app's individual App Manager page is accessible by longpressing the app shortcut and choosing App Info.
Click to expand...
Click to collapse
I know about the Icon long-press shortcut but the app screen sits on scanning for awhile, instead I pull-up Titanium Backup as it's usually quicker.
Now concerning the Market My App issues with 160dpi, personally I'd rather deal with the occasional data wipe then the Oversized UI of 240dpi but that's me. Sorry if I seemed misleading.
____________________________________________________
Sent from NookColor CM7 uSD using Tapatalk

does widgets make my phone laggy?

am on xxjvs and am using touchwiz 3 with transparent app drawer
my free ram is always too low and my phone is laggy
this is some pics of my widgets and running services
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

soudy1994 said:
am on xxjvs and am using touchwiz 3 with transparent app drawer
my free ram is always too low and my phone is laggy
this is some pics of my widgets and running services
Click to expand...
Click to collapse
Most probably widgets have nothing to do with lag, but the feed widget and some weather widget will drain you battery faster since they must be syncing a lot.
Normaly free ram is low most of times, because Android put apps there to load them faster when you need them, but running processes will in fact affect your phone performace, check out if there is anything running that you don't need and close it.
Just recently, I changed from custom roms to stock roms, and I think stock roms are a little more responsive.

gtluis said:
Most probably widgets have nothing to do with lag, but the feed widget and some weather widget will drain you battery faster since they must be syncing a lot.
Normaly free ram is low most of times, because Android put apps there to load them faster when you need them, but running processes will in fact affect your phone performace, check out if there is anything running that you don't need and close it.
Just recently, I changed from custom roms to stock roms, and I think stock roms are a little more responsive.
Click to expand...
Click to collapse
thanks for your reply can u tell me how much free ram do u have normal?
btw am on stock jvs deodexed and i have like 70 apps installed
and do you think i shud move apps to usb storage or leave em on phone ?

soudy1994 said:
thanks for your reply can u tell me how much free ram do u have normal?
btw am on stock jvs deodexed and i have like 70 apps installed
and do you think i shud move apps to usb storage or leave em on phone ?
Click to expand...
Click to collapse
I have like 5 or 6 apps installed and free memory is curently on 129mb.
Running stock JVT.
You should try your apps and keep only the ones you need or use, anything else will just slow down your phone (and drain battery)

soudy1994 said:
thanks for your reply can u tell me how much free ram do u have normal?
btw am on stock jvs deodexed and i have like 70 apps installed
and do you think i shud move apps to usb storage or leave em on phone ?
Click to expand...
Click to collapse
Try using advanced task killer pro. In setting set kill mode to crazy. It automatically kills unused apps on screen lock.
Android starts to lag if RAM falls below 50MB. So, you should try removing some apps.

sohebq said:
Try using advanced task killer pro. In setting set kill mode to crazy. It automatically kills unused apps on screen lock.
Android starts to lag if RAM falls below 50MB. So, you should try removing some apps.
Click to expand...
Click to collapse
Android. Is. Not. Windows.
Android kills apps when it needs memory. If it doesn't need memory, it does not kill apps; if you do, it will relaunch apps—this is because it is more efficient to have apps cached in memory for when you want to use them, as opposed to relaunching the app every time you need it.
Killing apps does one thing: it causes the Android system to utilize free RAM by launching more apps. Doing so takes processing power, and does nothing but drain your battery.

upichie said:
Android. Is. Not. Windows.
Android kills apps when it needs memory. If it doesn't need memory, it does not kill apps; if you do, it will relaunch apps—this is because it is more efficient to have apps cached in memory for when you want to use them, as opposed to relaunching the app every time you need it.
Killing apps does one thing: it causes the Android system to utilize free RAM by launching more apps. Doing so takes processing power, and does nothing but drain your battery.
Click to expand...
Click to collapse
I've read this to be true, task killers are not a good idea on android, it is better to delete unused apps, or have them backed up with titanium in case you need them.

why shud i uninstall apps even if they r not running in background?
and why when i click the home button while am on an app the app closes instead of staying in background

And am on jvs now shud i update to jvt ??
Sent from my GT-I9000 using XDA App

soudy1994 said:
why shud i uninstall apps even if they r not running in background?
and why when i click the home button while am on an app the app closes instead of staying in background
Click to expand...
Click to collapse
Because Android decided that app needed to be closed in order to reclaim memory for other purposes. If you're unhappy with the way Android manages your RAM, there are various options available to tweak it. Adjusting the amount of RAM the system keeps free will allow for better multi-tasking.

soudy1994 said:
And am on jvs now shud i update to jvt ??
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'm on JVT and it feels like better than JVS to me.
Slight differences:
You'll have overscroll effect as default
My battery seems to last a LOT longer (at least for me on stock rom)

[Q] RAM Manager app to prevent redraws

Hi,
This is sort of a continuation to a thread I made a few weeks ago, which was about launcher redraw problems I had with every single launcher I tried. I'm on FroyoPro v2.5, and on the recommendation of a fellow board member (thanks, Dagger) I'm running Nemus launcher. Basically, whenever i install or uninstall an app, my launcher prompts me to either force close or wait, and when I choose wait, it becomes slow for the next five or ten seconds and then returns to normal. It was worse before, but ticking "Lock launcher into memory" solved the most of the problems. Seems that the lack of RAM was actually the source of the problem.
I was recommended the SuperCharger script. However, I needed a newer version of BusyBox to install it, so I scrapped the idea for the fear I might brick the phone.
I investigated further for a solution, and found the app called RAM Manager (free version), which was made by a developer here at XDA. I installed it, set the "balanced" profile, and it actually fixed the problem. No redraws so far, and I even think the launcher is a tad smoother than before.
Has anyone tried this app? Is it a good thing to have or would you rather recommend I try something else? Are there any apps like it that are perhaps more efficient? It seems that all I need is better RAM management for the issue to be solved.
EDIT: Forgot to add the link to the XDA thread: http://forum.xda-developers.com/showthread.php?t=1305060
So far so good. Battery seems more or less unaffected. No negative effects on AnTuTu and Quadrant benchmark scores. Played five games in total, seemingly no negative or positive effects. What are your feedbacks on this?

The ram manager is actually a substitute to the supercharger script.
I personally recommend it if you are having ram issues.
Also you may freeze or uninstall the useless apps(mainly system apps) so as to free more memory.

Hm, now two days into the testing I've noticed that launcher redraws still do happen on occasion. However, it also seems that this app does the job well the moment it started and several minutes after running, but its effectiveness sort of degrades afterwards. Two days after I don't even notice any difference than before. What's the reason behind this? Is it fully compatible with CM ROMs?
There's only one more thing that I would also like to try before dropping this whole issue completely. Obviously it's a RAM thing, because running the backup I made a day after flashing FroyoPro seems to have no problems until I choke it with more apps. Then the same thing starts occurring. Not much can be done with the limited RAM X8 has.
However, what do you think about tweaking the VM heap size and MinFree values in CM settings? Is it possible to alleviate the problem with some tweaks from there?

Ahhhhhhh
V6 supercharger is just a ....beep.....
Before using that my antutu benchmark was 4005 - after installing script my score had a freefall @ ~3500~ ( lost 500 scores)
I'm using ram manager pro too, I can say that its awesome for setting to -multitasking option ( 3 apps at the same time)
HIGHLY RECOMMENDED
Sent from my E15i using Tapatalk 2

jay-z-s said:
Ahhhhhhh
V6 supercharger is just a ....beep.....
Before using that my antutu benchmark was 4005 - after installing script my score had a freefall @ ~3500~ ( lost 500 scores)
I'm using ram manager pro too, I can say that its awesome for setting to -multitasking option ( 3 apps at the same time)
HIGHLY RECOMMENDED
Sent from my E15i using Tapatalk 2
Click to expand...
Click to collapse
Yes, and I might actually try buying this app. Even though it didn't resolve the redraw issue completely, the general feeling of better performance seems to linger. I'm going to keep running the free version for a few more days and see what would happen

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There you go...
Download "system tuner pro" or any similar apps from market.
Press "tweak " button
Set "hidden apps" option to maximum value (now its 24mb but u can raise it to 32 or higher )
That's it...
*launcher pro OR adw launcher are too light and don't need to increase memory (I use adw with Widgets without reddraws

Use thishttp://forum.xda-developers.com/showthread.php?t=1987032
It works for me.
Just install the apk and tick both yes and run at boot.
sent from my phone using hands and brain...

[Q] RAM became a monster, system stuffs become "restarting"

Hello guys!
I would like to share something weird I encountered and to me, I feel weird about it. Any clarification would be appreciated!
You see, whenever I intensively uses my phone, that is when I use my browser to do everything (manage my site post to forums bla bla bla), I found out that my phone seems to be lacking memory, well you know that event where some apps are closed and does not run in background. After checking the running apps section in settings I found out 4 system process shown to be restarting without being actually restarted!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Qualcomm.atfwd makes me more afraid about this problem!
Can someone give me a thorough explanation? I faced this once on DoomLord's advanced stock kernel, however (flashed and) being on the stock (Sony) kernel does relieves this problem but at some point in time I got this problem again. The difference between now and then is that then, the free RAM is merely 20MB (DoomLord's kernel) but gladly now the free RAM is about 170MB (Stock kernel). However this problem still bugs me out. Sometimes it throws me into an unexpected soft reboot!
There is a fix - a reboot turns the system back into its calm state. However, I want to know more about this and if there is a workaround, I would really appreciate it!
UPDATE
If I experience this problem for only less processes (eg 2), the processes will return to be okay after leaving the phone without use.

Test supercharger
Gesendet von meinem Xperia SP

Main post updated. For easy understanding....

joke19 said:
Test supercharger
Gesendet von meinem Xperia SP
Click to expand...
Click to collapse
I will look into that, but at the time being, I want to know what actually causes this to happen

This happens when you use Chrome, is it?
And.. can you post what are values you get when doing following command in a terminal emulator..
Code:
cat /sys/module/lowmemorykiller/parameters/minfree

mrhnet said:
This happens when you use Chrome, is it?
And.. can you post what are values you get when doing following command in a terminal emulator..
Code:
cat /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
No, I use Firefox... Here is the terminal output:
15000,17532,20065,22598,25131,30263

(## This post got longer than I thought.. apologies mate.. )
TechnoSparks said:
No, I use Firefox... Here is the terminal output:
15000,17532,20065,22598,25131,30263
Click to expand...
Click to collapse
I haven't used Firefox much.. is it a memory hog? I'm assuming you're on stock kernel.
Those output values indicate minfree values of low memory killer (LMK) driver, as you may already know. It's in pages, 1 page=4K, so those values in MB:
58,68,78,88,98,118
These stock rom values don't make much sense.. it means that when "free ram" goes below 58mb, LMK driver should kill the Foreground app, which is in the foreground and which we're interacting with! Why do we need to kill that?? So, these values were causing problems for me (I think ) eg. Asphalt8 shutting down in the middle of the game [it's memory intensive, so ram might be going down to that level]. What might be happening in your case is that when using Firefox with many web pages open, if free ram goes quite low, apps might be shutting down. Some techie things about that below.. skip if boring
As you may already know, apps/processes in Android are assigned an oom_adj value, which indicates the likelihood of it being killed when an out of memory (OOM) situation occurs. More higher it's value, more likelihood of it getting killed. Valid range -17 to +15. (-17 range means it won't get killed). According to that, there are six groups, into which apps/processes will be assigned:
1. Foreground app
2. Visible app
3. Secondary server
4. Hidden app
5. Content provider
6. Empty app
Read details about them here: http://forum.xda-developers.com/showthread.php?t=622666
Foreground apps usually have an oom_adj value of 0 or less, so they are the least killable. Empty apps have a higher oom_adj and they are killed early. Also, oom_adj value changes according to the state of the user app; 0 when it's at foreground and assigned a higher value when the app goes to the background.
Above 6 categories correspond with the 6 memory limits which are set in LMK minfree values. Practically in your case, Empty apps will get killed when ram goes below 118mb, content providers when 98mb, and so on.. lastly killing foreground apps when ram goes below 58mb. So, what you see being killed belong to one of the groups, which might have got killed accordingly when ram went low.
[Highlight]Note:[/highlight] In our SP (and newer kernels), oom_score_adj is used instead of old oom_adj. (oom_score_adj valid range is -1000 to 1000). But oom_adj is maintained for compatibility I think. End of boring stuff..
##You can check the minfree values (also change them) and see the app states with this Memory Manager app easily:
If you click on an app in the list and select 'more info', you can see it's oom_adj value. In my case, System UI has -12 (foreground), Home Launcher has 1 (visible group) etc.. You can check this manually in a terminal too.. but boring.. : (commands with output posted below)
E.g. take home launcher. Find out it's PID (process ID) like this..
Code:
$ ps |grep home
u0_a26 1653 721 471408 78076 ffffffff 00000000 S com.sonyericsson.home
It's pid is 1653. To see it's oom_adj value..
Code:
$ cat /proc/1653/oom_adj
1
It's 1 (foreground). You might get 6 (hidden). So, your home is easily killed than my home . See below why..
At the same time you can see the new oom_score_adj..
Code:
$ cat /proc/1653/oom_score_adj
58
To convert it to old oom_adj value..
oom_adj=(oom_score_adj x 17)/1000
So, 58 x 17 /1000 = ~1
*There's another value (0-1000) of oom_score (cat /proc/1653/oom_score), which is THE actual indicator of how likely a process will get killed. It changes according to the tunable oom_score_adj and other factors..? something like that.. forget it!
[Highlight]So, the things you can do..[/highlight]
1. Change the minfree values to suit your needs. Use lower values if you want more multitasking. Higher values if need more "free ram" for gaming etc.. (see below.. what's this "free ram"?). I use 8,12,45,65,95,165 for more multitasking and for foreground apps to stay until ram becomes much lower. Asphalt8 never crashed with this!
You can set those values with the above Memory Manager app (and tick 'apply at boot'). Need root access..
Or do the boring manual way..
Code:
echo "2048,3072,11520,16640,24320,42240" > /sys/module/lowmemorykiller/parameters/minfree
(after "su" command of course; need root for that).
This won't survive reboot. You can run this command as a script with init.d every boot. (For init.d support, check this). If you have init.d support, you can use Minfree Manager app to set minfree values, and it saves a script under init.d. No hassle.
2. Use 'App Settings' xposed module to make any app "stay" in memory (make it "Resident"). It possibly reduces the oom_adj value so it won't get killed. That's why you can see Opera Mini in the Foreground app list above in my screenshot. It's oom_adj is 0. You can do this for your home launcher and any app you wan't to stay un-killed in the background.
3. Use zeppelinrox's jar patcher tools to patch services.jar, where it changes Home Launcher priority and many other LMK related tweaks. This is why you see my home launcher is under visible apps (oom_adj 1). No launcher redraws even after asphalt8! See the particular thread for details.
4. With the above jar patching, you can use zeppelinrox's supercharger script to change the minfrees and re-group the OOM categories. It has tons of other tweaks. But for me, this OOM regrouping made some task killings much difficult and didn't relese ram readily when needed for heavy games.. So I'm not using it. I'm setting up minfrees as described above. There are some boring techie stuff about this OOM grouping thing.. but no need here.
5. Override the "Hidden app limit" of Android. In addition to the LMK thing described above, this is another mechanism that kills hidden and empty apps. Apps are killed when hidden app numbers go beyond the specified limit. Traditionally it's 15, so no more than 15 hidden apps will stay in the background even if there's plenty of ram. There's a build.prop setting which can control that in our SP. (Btw, jar patching mentioned above makes that limit to 70). With the build.prop setting mentioned below, we could make it to 150 ! (This way, we can maximize multitasking and app killing is fully handed over to LMK minfrees, which we can control).
Code:
ro.sys.fw.bg_apps_limit=150
Add this line to end of build.prop file and leave another blank line below that, and reboot. Use 70, if 150 looks scary [Highlight](Always keep cwm backups before doing these kind of things).[/highlight]
Credits to @zeppelinrox for finding that setting. You can read what happens and how to test it here in his thread.
One last thing about "free ram"..
What's reported in many apps as "free ram" is actually not free/empty. Linux/Android always tries to utilise the whole ram in some way.. So the ram is not wasted. Ram which is not used by active apps, is used for caching apps and for some buffers. You can see the ram usage with this.. "cat /proc/meminfo"
Code:
$ cat /proc/meminfo
MemTotal: 859764 kB
[B]MemFree: 26380 kB
Buffers: 2008 kB
Cached: 136600 kB[/b]
SwapCached: 0 kB
Active: 557312 kB
Inactive: 70520 kB
...blah.. ..blah...
....
Reported "free ram" was ~150mb when this was taken. ["Free RAM"=MemFree+Cached]. Out of that, most (135mb) is already cached. Actual free is very little. So, increasing "free ram" makes the phone much snappier because a larger part of the ram is used for caching things.
** I'd be more than glad if anyone points out shortcomings/improvements.
@TechnoSparks, Do you think it's useful if I organize this into a thread?