Related
Since the same questions seem to be getting asked a lot, here are some methods for getting past stock NookColor ROM limitations in a single thread:
1. How do I keep wifi from turning off when the screen goes to sleep?
- download Spare Parts from the market and set wifi sleep policy to never.
. . . mixed results have been reported with this method, but this appears to be the best known fix at the moment.
2. I restored and re-rooted, now I can't log in to my B&N account!
- get NookColorTools app (if not installed during root, it's on xda). Under All Settings, open the 2nd (of 3) setting called Wireless near the bottom. This will begin their registration process again.
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (mount system as r-w first). Look at the file's permissions (long hold on it and choose Permissions from the menu), and match it to the permissions of the other files in that folder. Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
4. How do I get Swype on here?
- right now, you can't. Swype requires a copy that matches your device's resolution, and the only version of Swype that matches ours (1024x600) is the copy that ships with the Galaxy Tab, but, to my knowledge, nobody has gotten it completely working on here without causing major system crashes (not to mention the apk couldn't be posted on xda even if it was eventually hacked to work).
SlideIT keyboard is another trace keyboard that DOES work on the NookColor, and I've been very happy with it (it's come a long way since I tried it last summer and quickly uninstalled it). The method in #3 above should work to install it.
5. Wait, I can't copy and paste on the NookColor??
- not through the OS, no. There is a solution though. It involves getting an app called Copy Paste It from the market (paid, but there's a trial version). You'll probably need to set it to rotate clockwise (in settings), or it'll get screwy.
When you want to copy, activate the function from the notification, and it'll let you frame the text to copy:
{
"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"
}
The second part, pasting, requires having a keyboard with a Paste setting in it. Again, SlideIT has this on the special characters keyboard (I'm not a troll for SlideIT, just a happy customer). I'm not sure which other keyboards have this feature, if any (if you know, post, and I'll update this). Assuming you have a keyboard with paste, it'll paste what the Copy Paste It app copied.
6. Why is everything on my screen so small?
- this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Here are two of my Galaxy Tab-esque homescreens set to 250:
. . . Now, jacking up your LCD density much above 200 will make your status bar look wonky and cut-off. One solution for this is to set it to 250, like above (by changing build.prop - I think the apps I mentioned only allow multiples of 20), which will make it look clean (as long as wifi is on). The only problem there is that you'll lose your status bar clock and Notifications in portrait mode . . .
. . . the solution for THIS is to get two apps: hellostatusbar, and quick launch. Set quick launch to open hellostatusbar on a home- button double press, and it will display your Notifications.
Also note that raising the density can cut-off parts of the stock Barnes & Noble software (they're designed for the lower density), so this mod is probably better for people like me who use the Kindle app and ezPDF for reading.
7. If I don't want to use softkeys, can I remap the hardware buttons to do something different?
Yes. In Root Explorer, navigate to system/usr/keylayout, make a backup of TWL4030_Keypad.kl, then open the original with text editor and change the entry for key 115 ( volume up) and/or key 114 (volume down) with something like BACK, MENU, or SEARCH. Save the file. Reboot, and they'll be whatever you changed the entry to.
If you want easy volume controls after remapping these buttons, a market app called Volumer++ can be set to live in your notifications for easy access. Otherwise, you can change them from settings.
8. How do I set my wallpaper so that the resolution looks good?
- I used a market app called Wallpaper Set & Save. It's easy, and resolution looks great. I think it cuts off the image a little bit, but not much. I think this method will suffice for many people, but if you want it to be sized perfectly, do the following (credit to swapdotavi for the instructions):
[Get an image that is at least 1200x1024, crop it (without scaling) to 1200x1024. If you're using Photoshop, copy the entire image, then create a new file sized 1200x1024. Then paste the image and use the arrow to drag it around to whatever looks best to you. Save the file as a .png, transfer to your nook, and use Wallpaper Set & Save to choose the new file.]
. . . Since we share the same resolution with the Galaxy Tab, the wallpapers that came with it look phenomenal (in my opinion) on the NookColor. Follow this link to pick them up:
http://galaxytabwallpapers.net/original-galaxy-tab/
9. Can I change the lockscreen slider to look like stock Android or Sense?
- yes - get an app called WidgetLocker. Set it to look how you want. Then, under Behavior, set Homehelper as your system home. Still under Behavior, go to Home to Launch, and pick your real launcher (Launcherpro, ADW, etc.). Also, under Advanced, be sure to check both the Root Bypass of 5 Second Rule, and Retain Keyguard.
10. My NookColor seems sluggish - is there a way to speed it up?
Most of you will already know this, but Setcpu is a market app that can speed things up and improve battery life. CPU Tuner is a free alternative that's similar, but I've had more experience with setcpu, and can vouch much more for it.
My recommended settings:
Min 600
Max 800
Governor: OnDemand*
check 'set on boot'
... And one profile enabled:
Screen Off
Min 300
Max 600
Governor: Ondemand
... And another optional setting (for even a little more extra zip):
under Advanced:
change "Up Threshold" to 35
* for the fastest setting, set the governor in the main CPU setting to Performance (with 800 max). It may drain your battery quicker, but mine still holds up surprisingly well on performance--and the nook is very fast.
These are just settings that work for me. Feel free to experiment. Also, some people were having their Nook randomly reboot, and changing the governor from conservative to ondemand helped.
11. Any other battery-saving tips?
In case you missed the rival xda threads arguing over who thought of it first, there was a potentially useful battery-saving trick in there:
Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine).
Basically, you're removing android system files that may be wasting juice looking for a non-existent cell service. It's unsure if or how much this actually improves battery life, but it very well could, and it certainly won't hurt anything changing their names.
12. Why aren't my favorite live wallpapers working?
I'm not sure, but here's how to get the rest of them going:
Download this file: http://db.tt/ur0c98s
It will fail installing, but if you use Root Explorer, copy it from your download directory, go to system/app, set as r-w... Then long-press on any file in that directory, and look at its permissions. Now paste your LiveWallpapers.apk there and change its permissions to match the others. Your live wallpapers should work now!
The Nexus wallpaper won't work, but just install Nexus Revamped from the market - it's identical, it's free, and it has customization.
If you're using one of the more system-intensive Live Wallpapers (like "Water"), I'd recommend using all of the Setcpu changes from #10 above to keep things snappy (also know that LWP's can drain battery quicker).
13. How can I get my Google contacts in here?
If you aren't concerned with them showing up in the B&N Contacts app, and are more interested in having them come up as auto-suggestions when typing an email address or Google Voice text number, there's a way (credit to jadambpharm):
- Go to gmail on the web, click on contacts (left side), then More Actions, then Export. Choose .vcard format. Transfer that file to your SD card.
- get a Market app on your Nook called Import Contacts. Point it to the contacts.vcard file you just got, and they'll now come up for auto-fill suggestions!
14. How can I prevent the Nook from automatically updating the firmware?
- Change the name of etc/security/otacerts.zip to anything else (doing this in Root Explorer works fine). So far, this had looked pretty solid in successfully disabling OTA updates.
15. Why won't YouTube play videos in HD?
For some reason, the YouTube that's installed from rooting won't do it. To get a version that plays HD:
- uninstall your current YouTube via Titanium Backup
- download this version from the Evo (credit aludal): http://db.tt/y5vVvI2
- rather than installing this one, rename it youtube.apk and copy it into system/app (w/permissions matching the other apk's in that folder)
It should be there now, ready to play HQ clips. If not, reboot first.
I'll update as I think of more. Enjoy your modestly-priced, unintentional Android tablets!
Reserved 10 chars
How about "What size should wallpaper images be?"
I suggest this because I dont know
swapdotavi said:
How about "What size should wallpaper images be?"
I suggest this because I dont know
Click to expand...
Click to collapse
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
pest789 said:
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
Click to expand...
Click to collapse
The Galaxy Tab wallpapers I've used all look phenomenal too. Same resolution, so its tailor-made. Easy to find them with a google search.
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
wvcachi said:
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (set system as r-w first). Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse
@beejis - make sure you're losing the xdpi and ydpi parts and merging it into a single entry. Look closely at the example in the OP. Also, make sure you're editing the entry that isn't commented out (don't bother editing the lcddensity entry with a # in front of it) a few lines earlier. If for some reason that didn't work, then use the free app from the market to change it.
@k8108 - if you're using Root Explorer, it's a little button up top when you're navigating system/, which lets you toggle mounting system as 'read-write' and 'read-only.'
Beejis said:
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
Click to expand...
Click to collapse
Comment out these lines (add # to beginning):
# ro.sf.lcd_density.xdpi=169.3333
# ro.sf.lcd_density.ydpi=169.3333
Add this line:
ro.sf.lcd_density=254
I already had a line similar that I uncommented, and I run mine at 254.
169.3333 / 2 = 84.6666
169.3333 + 84.6666 = 254
I am probably overthinking it, but it looks good. You can make that number 250 if you want.
The Program LCD Density lets you select specific densities as well, but is only soft. Nice for testing.
k8108 said:
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
ThrowingKs said:
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
Click to expand...
Click to collapse
...I got the impression he was using Root Explorer, in which case it's a little button that says r-w.
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
foethalove said:
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Good point - I'll note that in the OP. I don't use the B&N stuff, so it's easy for me to forget that not everyone on xda is in the same boat.
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
cgtombstone said:
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
Click to expand...
Click to collapse
Look in data/app, and find the file named com.dasur.slideit.apk. Copy/paste that into system/app (hit r-w first of course), then reboot and switch keyboards via NookColorTools.
My bad I was searching for it in root explorer and I gues the search function was skipping the data folder for some reason ( or I'm missing something). Thanks anyway.
NookColor+ XDA 4 ever
Thanks bookmarking this thread
wvcachi said:
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
Click to expand...
Click to collapse
Ah perfect did not see your update. I see you found Set and Save, but you mentioned you might update with exact size instructions later. I actually went and did a bit of research, so maybe I can save you some time
To get an perfect wallpaper using 5 screens, like in ADW:
- Get an image that is at least 1200x1024
- Crop (dont scale) it to 1200x1024. A really easily way to do this is open the file in Photoshop, copy the entire image, then create a new file that's exactly 1200x1024. Then just paste the image and use the arrow to drag it around to whatever looks best to you.
- Save the file as a .png
- Get it on to your nook. (SD card transfer, email and download, whatever)
- Open Wallpaper Set & Save
- Point it towards the folder you have your wallpapers in
- Select the wallpaper you want
- Hit apply
Bam. Perfect wallpaper, no stretching, no compression. Looks great! I'll post screens later today if I remember
I used a 1920x1200 wallpaper I had on my PC, cropped it, emailed it to myself, then used Set & Save to place my wallpaper. It's really crisp.
edit: And thanks for the lock screen information! Going to do that tonight; sick of the stock screen
MOD, can we get this stickied? Lots of good info!
Please read this post through thoroughly before downloading.
This app allows you to control your CPU voltages with an easy to use interface. You can increase or decrease voltages (undervolt or overvolt) for all frequencies or fine tune voltages for each individual frequency.
! HTC DEVICES, currently only single core devices are supported !
! ROOT is Required !
! Kernel that supports HAVS or SVS voltage adjustment REQUIRED !
In addition, if you are an Incredikernel user, the app may also be used to toggle Incredikernel specific features on and off, namely USB fast charging and audio boost.
Get it over at http://www.incredikernel.com
IncrediControl is now also available in the market:
IncrediControl
IncrediControl - Ad Free
Additionally, all donators are eligible to receive the Ad Free version. It doesn't matter how much or how little you donate or have donated. If you don't want to purchase the app from the market, you may donate using the button on this page. Please register on the site first and include your username in the comments box.
All previous donators, please register on the site if you have not done so and contact me with your username!
NOTE: The settings in the general tab are only functional in kernels that have implemented the simple sysfs interfaces for usb fast charging and audio boost. If you toggle them, its not going to break anything, but they won't work and the app may crash. If you would like your kernel dev to implement the interfaces, please direct them to these two commits:
https://github.com/Chad0989/android_kernel_common/commit/a7c21fa0391c225900f93960362535179c0cecc9
https://github.com/Chad0989/android_kernel_common/commit/41dc138bae23dc7582de72a4d9895aaa8e1f8b2d
NOTE2: It is a requirement of the HAVS adjustment that the kernel you are using has the HAVS sysfs interface implemented. If it does not, it will not work. Most non-stock gingerbread kernels have the HAVS adjustment. Very few sense kernels have the adjustment. I believe ziggy's latest is the only one that does.
NOTE3: Before using, please delete any boot scripts you may have in /etc/init.d that toggle any of the settings this app controls.
Get it at http://www.incredikernel.com
Restore script - use this if you went too low and find yourself in a boot loop. Flash through recovery:
http://www.incredikernel.com/?p=229
This excites me.
Neat
Sent from my Synergy Rom using Tapatalk
Great chad! Finally an app that does all the work.
Sent from my ADR6300 using XDA App
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
mikeymop said:
Hey Preview 2 has the HAVS, I think you should put the minus on the left of each number field. So that way it's like
- [voltage] +
Click to expand...
Click to collapse
I concur. And will this work on the incredikernel?
J/k on the the question part (because I know someone will take that seriously ). Great work, chad.
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Great thanks!
I know viperboy was working on something similar.
I have to say though your aggressive undervolt package is the tits. It is rock solid for me, and I can't lower anything -25v from there without crashing.
RebelShadow said:
Chad, here's something to ponder or consider. Please think about putting in some way to back-up your settings. That way when flashing new roms you could just restore from back rather than settings all again. Just a thought.
Click to expand...
Click to collapse
That may come in the future.
@everyone: Anyone try it on other devices that have havs + sysfs interface? Evo, desire?
effing sweet..... no more term emulator for me
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
POQbum said:
Chad, I've noticed that after I reboot the phone and go back into the app, the boxes for "set on boot" are unticked.
Also I know you already know this but it's sort of a pain in the ass to set the SD card speed (your other app) after every boot, so if you could do a "set on boot" for that one too that'd be awesome.
Keep up the good work, I like how every time I check back here you have a bunch of updates
Click to expand...
Click to collapse
The boxes are unticked on purpose, so that the file is only written when you specify that you want to set the current settings on boot. The other option is to have it ticked when the boot script is found, but then you would have to untick it when you want to just play with voltages (but not change your boot script) and then tick it again to set on boot. Would everyone prefer it that way?
I should also specify that when you tick set on boot, you also must click set in order to truly set it on boot. There is also the option to have it write the file when set on boot is ticked. I just need to know what everyone's preference is.
SDspeed might be added to a future release and would have the set on boot option.
PonsAsinorem said:
I've noticed after installing a new nightly with no wipes, the values revert to stock, even with set on boot.
Click to expand...
Click to collapse
That's because new nightlies overwrite the /system folder where the boot script is stored. I'll probably add a backup option too so you can load the defaults, either that or change over to storing the values in a database and loading them via the app on boot as opposed to the boot script.
Looks cool.
Backup database - yes!
Default set on boot once it's been ticked - yes!
Thanks for this, Chad!
Zeam & Incredikernel
CM7 latest Nightly
7/19/2011 - Preview 3:
Changes include:
Added +/- All Min and All Max buttons
Reordered the + and – buttons to flank the voltages to clean up the layout a bit.
Removed the title bar for more vertical screen space
Next up is feature checking / disabling of functions your kernel doesn’t support as well as voltage checking.
Get it at http://www.incredikernel.com
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
nagasgura said:
Here's an icon I made in photoshop for the time being, so there won't have to be that plain android icon.
Download it here: http://dl.dropbox.com/u/12361010/volts.png
Click to expand...
Click to collapse
Thanks, I'll add it for the next release.
The + on the Max voltage doesn't display for me.
Love it, fast and simple volt changing.. Makes viperMOD ancient news.
Content deprecated and removed to avoid confusion.
Note 31/07/2011: Updated for Nova Script
Note 10/08/2011: The method is a bit different but you get the overall idea after reading this
II. How to overclock (applies to Nova)
So, you just want to overclock eh?
Ok, you have several ways to do this:
a) Using Nova built-in overclock script
b) Typing commands by hand (terminal, adb, etc)
(No, SetCPU does not work on OMAP devices, only for choosing governors)
I will also cover how you get your Optimus Black to auto-overclock (at least in Nova).
But first of all, very very important, please open this spreadsheet - it has a listing of values of clocks and the corresponding voltages which can be: stock ones, low ones, ultra low ones and high ones. For speed & battery compromise, I suggest low ones. However, if you're a gamer, you better stick with stock for instance.
Print that.
Done? let's move on.
a) Using Nova built-in overclock script
Now, I made a hilariously simple script for you to use on Nova to facilitate your overclock.
You just have to open the terminal application and:
Type "su" (without ""), press enter, click allow if it asks - very important step (needs root).
Type "nova" (without ""), press enter and congratulations, you've just entered the nova (overclock) script!
There just choose "overclock!". Remember, first the voltage, then the clock.
For example:
Type "su" (without "") on terminal, press enter. Click allow if it asks.
Type "nova" (without "") on terminal, press enter.
Type "1" (without "") and press enter.
Type "62" (without "") and press enter.
Type "1100000" (without ""; this is 1.1 Ghz) and press enter.
Enjoy your overclocked and undervolted phone.
Oh, terminal emulator has some kinks:
- If your keyboard disappears hit menu button and click 'toggle soft keyboard'.
- If you exit and it stays on the statusbar, re-enter terminal, hit menu button and click 'reset'.
P.S. You can also run this via ADB.
But how to auto-overclock on boot?
Now in latest Nova Script it will ask you if you want to set them on boot!
If by some reason you didn't test and found out that your device is stable with those settings and you can't boot your device or if it does it's all laggy and craps, you can just power it off, remove microSD card, use an adapter and put it on your PC or laptop and remove the file, then insert the microSD card back and reboot the phone. I chose a file in the microSD card especially because of this safeguard.
b) Typing commands by hand
If you're feeling too pro for the overclock script, you can just type them by hand:
- echo "xx" > /proc/overclock/max_vsel
- echo "xxxxxxx" > /proc/overclock/max_rate
If you want to auto-overclock, use the same method as above.
This is it. Simple.
A few reminders:
Voltage first; then frequency.
Check the table in the beginning of the post for frequencies and recommended voltages
Frequency has to be for example 1200000, not 1.2. It's in Mhz, not Ghz.
Test the **** out of your device with a frequency/voltage before setting it at boot.
Most Optimus Black won't be stable beyond 1.2 Ghz.
If you can't boot or are having problems because of auto-overclock, just delete the file.
Done.
Sorry for the delay, I'm finished now.
Time to go upload Nova v1.7.27.
Instructions updated; I forgot the "su" part.
Thanks for the detailed tutoring!
Thanks! I really appreciate this
Interesting...
From where have you obtained the recommended voltaje/freq?
Thanks!
From a reference of Droid X which uses the same chipset as us.
my first thing is to set the min freq to about 100Mhz XD
Is not working...
After boot, cat /proc/overclock/max_rate says 550000
Changing auto_ocuv in /sdcard/nova/overclock/ has no effect. After reboot, the same 550000...
Changing manually with oc script works, after that the report is correct.
Anyway, is not much difference between the two cases... It seems a little bit increased speed, but maybe is just me...
I used 62 and 1150000...
Untill now it is OK.
How the setting must be arranged in auto_ocuv? Mine is 621150000.. Is this correct?
rgabi88 said:
Is not working...
After boot, cat /proc/overclock/max_rate says 550000
Changing auto_ocuv in /sdcard/nova/overclock/ has no effect. After reboot, the same 550000...
Changing manually with oc script works, after that the report is correct.
Anyway, is not much difference between the two cases... It seems a little bit increased speed, but maybe is just me...
I used 62 and 1150000...
Untill now it is OK.
How the setting must be arranged in auto_ocuv? Mine is 621150000.. Is this correct?
Click to expand...
Click to collapse
That's because you have vold/179:16.
It works for 179:17.
Today I will get it working for everyone. I suppose you can't also use App Inj.
But no worries, just wait for today's version.
Noejn said:
From a reference of Droid X which uses the same chipset as us.
Click to expand...
Click to collapse
That's why quadrant advanced bar results precentage is very similar. Both suck in cpu processing very nice in I/O hhahaha.
Sent from my LG-P970 using Tapatalk
Noob question, could optimus black get more overclock potential with Android 2.3 ? Or always unstable with 1.2 ghz+ ?
Thanks! Using your overclock, I could overclock my Optimus Big (Only for Korea)!
I used 1200/64... However I tried to overclock my phone more than 1.2GHz, but I can't do that. It's so hard to find right voltage for 1.3GHz or 1.25GHz
Hi I'm new to this. What is the different between overlocking and unlocking a the phone? Thanks.
{
"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"
}
Hello dear XDA users, today we are going to talk about improving the performance of your freshly flashed Official CyanogenMod 7.2 ROM on your Galaxy Mini!.
I am going to cover a couple of simple stages that could make your Mini run happier and be more responsive! This is strictly performance orientated, we are going to disable various animations and speed them up wherever possible.
Do not expect miracles. To be honest, I think many of you already know this stuff, but it can help newbies or somebody who doesn't know it.
What you're going to need for this is 2 things:
1. Galaxy Mini with Official CM7.2 flashed on it (doh!)
2. Common sence and ability to understand every word I've written here
DISCLAIMER
I am not responsible for anything that happens to your device during the following of these procedures. Also, don't blame me for undesirable effects, you're doing this on your own responsibility. Every operation should be harmeless if you follow it correctly. DO A NANDROID BACKUP BEFORE DOING ANYTHING!
Okay. Ready? Let's start!
Disable CPU Rendering
The original guide is in this thread: [GUIDE] Disable CPU Rendering, thanks & credits are going to leolawliet!!!
This modification will speed things up since the system will use GPU instead of CPU for some of the graphics rendering.
To get this mod, you first have to download the egl.zip which you can find in that thread. Extract it, and copy the egl.cfg to the root of your sdcard. Then, navigate to /system/lib/egl and delete libGLES_android.so. After that, copy the egl.cfg from the SD card to that system/lib/egl folder, overwrite it with the original one, and change the permissions to rw-r-r. After that, it's just a matter of rebooting your device!
Warning! There is a small chance of bootloop, so have a nandroid backup handy!
You can do all this deleting and copying with Root Explorer or any other file manager which can mount the /system partition and mess with permissions of files. Also, all this can be done with Terminal Emulator if you know how, but it's waaay more complicated.
ADW Launcher tweaking
I recommend you do not switch to another launcher. The reason for that is this one is lightweight and fast. CyanogenMod team had a reason to integrate this launcher and not some other within their ROM
Open ADW launcher settings. In the Screen preferences, go ahead and disable Wallpaper scrolling, and Desktop overshoot. Also, change the desktop scrolling speed to 0 (my prefered setting, because the launcher isn't that smooth and I love speed, not animations)
In the Drawer Settings, disable Animated drawer, disable Fade app labels and also change the background color of the drawer to whatever color you like, mine is set to black (that will disable the transparent drawer, which lags A LOT)
In the General Behaviour section, disable Sense like previews, and, if you want, go ahead and disable Show notifications (don't worry, notifications will show up in the status bar, this is just for the sms and dialer icons, on top of them the number of missed sms's and calls show up)
And lastly, in the UI Settings, disable New icons selector and disable Show desktop indicator, else is optional
Here is a pic where you can find all of the settings I mentioned:
The ROM settings and tweaks
I am a personal fan of non-animated things, because that makes me fell I have a faster phone. And animations use a little bit of battery since every time phone has to render an animation, it uses CPU and GPU power. However, battery savings here are unmeasurable, but they do exist.
If you want to do that, go to the Display section in the main settings menu, and under Animation dropbar select "No window animations are shown". Also, in the CyanogenMod settings, there is also a Display section. Go there and disable Rotation and Screen off animation.
I find "Sliding Tab" lockscreen style faster too, so go ahead and change that if you want to try it out. You can find it in the CyanogenMod settings->Lockscreen settings->Style options.
And now we come to the "Performance" part of the CyanogenMod settings menu. In there, go ahead and disable "Enable surface dithering", enable "Use 16bit transparency, set Scrolling cache to Force Disable, check "Allow purging of assets", and disable boot animation. Do not check Lock home and messaging app in memory since they do almost nothing, and we need them disabled for another tweak coming on later!
Overclocking is something you should also consider doing. I think that part you will have to do for yourself, because every phone has different overclocking ranges on which it works stable. But I think that every phone should run at 710MHz without problems. Give it a shot, if it reboots imidiately or later as you use the phone, try the lower values and see what works the best for you. If everything works fine, and you want more, go for it.
The best way to test your overclocked setting is to just use your phone like you would always do. Playing games alo is not a bad idea, however if you don't play them you might be able to jump the frequecy one step further, since everyday operations don't stress the CPU so much. Keep an eye on the temperatures, if your phone gets very hot quickly you might consider going a couple of notches down.
Removing apps that came with the ROM
Everything is covered in this article: Cyanogenmod Wiki: Barebones
You can read everything you're worried about there. My knowledge also comes form that place, so credits go to the CyanogenMod team!
For the lazy ones who don't want to mess with Terminal Emulator, you have alternative ways of doing this which are listed a little below!
Why would you want to remove system apps? Basically, if you use a replacement app or there is a app you do not use at all, the apps that are left over use internal memory, and potentialy RAM memory!
To delete an app:
1. Open Android Terminal Emulator (comes preinstalled on the ROM, so nothing to download form the Market)
2. Type
Code:
su
- to give it SuperUser permissions (Superuser app might come up asking you do you want to allow the emulator root access, allow it)
3. Then type
Code:
mount -o rw,remount /system
-to allow read/write operations on the /system partition, or basically to "mount" it.
4. And then, to remove an acctual app, type:
Code:
rm -f /system/app/app_you_wanna_remove.apk
- rm stands for remove, -f is force, and the rest is where the terminal can find the app for deleting. If you're deleting Email app, it would go like this:
Code:
rm -f /system/app/Email.apk
Carefull! This is case sensitive, and you're using the -f command. If you make a typo, nothing will be deleted, nor you will be warned about it! Check it before you press "enter"
List of apps you can delete (that i've deleted):
1. CarHomeGoogle.apk (App for using in the car, while the phone is mounted on the carholder)
2. CMStats.apk (CyanogenMod statistics)
3. CMUpdateNotify.apk (CyanogenMod update notifications. Not working without ROM Manager premium)
4. CMWallpapers.apk (CyanogenMod Wallpapers)
5. Development.apk (The development app, not needed by an average Joe)
6. DSPManager.apk (DSP Manager app. It's that equalizer app you can acces trough your music player. Eats 3megs of RAM!)
7. Email.apk (Email applications. Does NOT affect GMail)
8. GenieWidget.apk (Weather and News app and widget)
9. GoogleQuickSearchBox.apk (Google Search)
10. LiveWallpapersPicker.apk (Live Wallpapers selector)
11. PicoTts.apk (Copilot Live or Copilot GPS need this app (noted by ArthurBorsboom ). Also, might break Voice Search. Otherwise, safe to remove)
12. Protips.apk (That widget that shows up right after flashing the ROM. It even tells you that you can delete it lol)
13. RomManager.apk (DELETE DELETE DELETE!!!)
14. SoundRecorder.apk (Stock sound/voice recorder app)
15. Talk.apk (Google Talk)
16. ThemeChooser.apk (Theme Chooser. If you delete it - no themes, only the stock one!)
17. ThemeManager.apk (Theme Manager. The app that can't work without the chooser, themes your system when you apply a theme)
18. VoiceDialer.apk (Voice Dialer app. Not to be confused with Phone app)
19. VoiceSearch.apk (Google Voice Search)
20. LiveWallpapers.apk (Live Wallpapers that are included in the ROM)
21. MagicSmokeWallpapers.apk (Some wallpapers, I don't know everything)
22. VisualizationWallpapers.apk (Some wallpapers, I don't know everything)
23. SpareParts.apk (I don't know, never opened it - don't need it)
24. FM.apk (FM radio)
25. TtsService.apk (again something related to text-to-speech features. Might break Voice Search)
If you're using a non-stock keyboard, you can delete LatinIME.apk
If you're using a non-stock gallery, you can delete Gallery3D.apk
If you're using a non-stock music player, you can delete Music.apk
If you're using a non-stock internet browser, you can delete Browser.apk (PLEASE NOTE: This is apparently a hard-coded requirement for Google Voice Search (along with Talk and Voice); without it, Voice Search will FC after recognizing speech. Having Dolphin, etc., installed will not work. )
Beware of deleting LatinIME.apk! That's the keyboard app! If you don't have another keyboard which is already set up as the default one, don't delete it, otherwise you'd get stuck with no keyboard, and you kinda don't want that lol
If you want to find out if there is more apps to delete (but I assure you that you won't find anything worth bothering), navigate the stock FileManager to /system/app and check it out.
Alternative, more easy methods for app deleteing
I would avoid them if you feel taking that kind of time. Why? Well, installing an app to delete another one... no... just no. If you want, go ahead and do that
1. You can use Root Uninstaller from the Google Play to uninstall apps. (suggestion by ChunkFlip)
2. If you have bought Titanium Backup Pro, you can use it to remove apps as well. Also, you can use the app to make backup of the programs you're deleting, although you can pull them from the flashable .zip of the ROM anytime you want, and for the most part, just install them. (suggestion by avrox and R.A.G.E)
3. If you happen to have Root Explorer bought, you can easily delete apps by just navigating to the /system/app folder and delete the .apks you want. However, do not pirate the app. If you haven't bought it, I strongly encourage you to follow the original method using the Terminal Emulator. Do not pirate an app if you have free alternatives! NEVER!
Delete apps you do not use, and use as light-weight apps as possible
If you have a game or an app that is just sitting there and you don't really use it, delete it! I know it sounds silly, but those apps can have some services that run in our percious RAM and practically waste it. Not to mention you have less internal memory available, which is pretty obvious.
Use light-weight apps! Don't just throw a 5MB stopwatch app on the phone or something like that. Look for an app that's smaller and does exactly the same job. If you look hard you will usually find some stonning small apps that do the same thing as even 10x larger ones. And larger ones open slower, run slower, and use more RAM memory! Not what you really want, do you?!
Install V6 SuperCharger script by zeppelinrox
It's awesome! It will stop launcher redraws and potentially improve performance even more! I'm not going to write anything about it, because the download link and the instructions are all found in his thread, check it out!
[U9RC11T9] STOP! -=SuperCharger Time=- You Can't Touch This! Please zep don't hurt em
BTW, you do not have to downgrade the BusyBox, the one included in the CM7.2 (1.20.x) works great. There was some problems with BusyBox 1.18 at that time, that's why he mentions it. Don't worry about it, just install the damn script!
Don't forget to give him a thanks!
Speaking of scripts: don't use like all the scripts and tweaks that are out here. They usually tend to conflict and that is not what you want! If you install one RAM script tweak, don't install another one! Same goes for transfering apps to ext partition and a bunch of other things.
Don't use task managers
Why you may ask? It's simple, and you will have to get over it - Android is better at app and memory management than you . Killing apps with a task manager doesn't do a thing except waste resources, because Android will run the app again if it wants to. Using auto kill app function is even worse, because the task manager will kill the app, Android will launch it, the task manager is going to kill it again, Android is going to launch it and the cycle repeats over and over again...
It's pretty obvious that will kill the performance, and impact battery life a lot. Not something you want, right? Yes, a task manager is included in stock sammy ROMs, but hey, stock ROM is crap anyway, and the point of it is to have as much of bloatware as it can possibly handle. Don't worry about free RAM and loaded apps, Android does a better job than you on it's own.
That's it, for now! I will keep updating the thread with something new, and possibly better. YOU make a suggestion how to improve performance, and I can add it here in the first post!
Note:
I will no longer update this thread. The reason for this: I have a new device now. Sorry about that
Non-performance related stuff
Apps restoring
For this one we will use the infamous Terminal Emulator again. The operation is actually quite easy.
I guess you have a PC, the CM7.2 ROM you flashed on your hard drive, and a program that can mess with .zip files
Open the .zip file and in /system/app you can find all the apps that came stock. Extract the one you need from the .zip file and copy it to the root of your sd card.
Now, fire up Terminal emulator and type
Code:
su
Mount the system partition:
Code:
mount -o rw,remount /system
Return the app back where it was
Code:
mv /sdcard/app_name.apk /system/app
And we are almost done! Since the permissions are ****ed up, type
Code:
chmod 644 /system/app/app_name.apk
app_name.apk is the app you are restoring. Be carefull, the app name is case sensitive!
Reboot the phone and... that should be it! Next time watch out what apps you need, so you don't have to go through this
great tut bro
domcale said:
Hello dear XDA users, today we are going to talk about improving the performance of your freshly flashed official CyanogenMod 7.2 ROM on your Galaxy Mini!.
I am going to cover a couple of simple stages that could make your Mini run happier and be more responsive! This is strictly performance orientated, we are going to disable various animations and speed them up wherever possible.
Do not expect miracles. To be honest, i think many of you already know this stuff, but it can help newbies or somebody who doesn't know it.
What you're going to need for this is 2 things:
1. Galaxy Mini with Official CM7.2 flashed on it (doh!)
2. Common sence and ability to understand every word i've written here
DISCLAIMER
I am not responsible for anything that happens to your device during the following of these procedures. Also, don't blame me for undesirable effects, you're doing this on your own responsibility. Every operation should be harmeless if you follow it correctly. DO A NANDROID BACKUP BEFORE DOING ANYTHING
Okay. Ready? Let's start!
ADW Launcher tweaking
I recommend you do not switch to another launcher. The reason for that is this one is lightweight and fast. CyanogenMod team had a reason to integrate this launcher and not some other within their ROM
Open ADW launcher settings. In the Screen preferences, go ahead and disable Wallpaper scrolling, and Desktop overshoot. Also, change the desktop scrolling speed to 0 (my prefered setting, because the launcher isn't that smooth and i love speed, not animations)
In the Drawer Settings, disable Animated drawer, disable Fade app labels and also change the background color of the drawer to whatever colour you like, mine is set to black (that will disable the transparent drawer, which lags A LOT)
In the General Behaviour section, disable Sense like previews, and, if you want, go ahead and disable show notifications (don't worry, notifications will show up in the status bar, this is just for the sms and dialer icons, on top of them the number of missed sms's and aclls show up)
And lastly, in the UI Settings, disable New icons selector and disable Show desktop indicator, else is optional
Here is a pic where you can find all of the settings i mentioned
The ROM settings and tweaks
I am a personal fan of non-animated things, because that makes me fell I have a faster phone. And animations use a little bit of battery since every time phone has to render an animation, it uses CPU and GPU power. However, battery savings here are unmeasurable, but they do exist.
If you want to do that, go to the Display section in the main settings menu, and under Animation dropbar select "No window animations are shown". Also, in the CyanogenMod settings, there is also a Display section. Go there and disable Rotation and Screen off animation.
I find "Sliding Tab" lockscreen style faster too, so go ahead and change that if you want to try it out. You can find it in the CyanogenMod settings->Lockscreen settings->Style options.
And now we come to the "Performance" part of the CyanogenMod settings menu. In there, go ahead and disable "Enable surface dithering", enable "Use 16bit transparency, set Scrolling cache to Force Disable, check " Allow purging of assets, and disable boot animation. Do not check Lock home and messaging app in memory since they do almost nothing, and we need them disabled for another tweak coming on later!
Overclocking is something you should also consider doing. I think that part you will have to do for yourself, because every phone has different overclocking ranges on which it works stable. But I think that every phone should run at 710MHz without problems. Give it a shot, if it reboots imidiately or later as you use the phone, try the lower values and see what works the best for you. If everything works fine, and you want more, go for it.
Removing apps that came with the ROM
Everything is covered in this article: Cyanogenmod Wiki: Barebones
You can read everything you're worried about there. My knowledge also comes form that place, so credits go to the CyanogenMod team!
Why would you want to remove system apps? Basically, if you use a replacement app or there is a app you do not use at all, the apps that are left over use internal memory, and potentialy RAM memory!
To delete an app:
1. Open Android Terminal Emulator (comes preinstalled on the ROM, so nothing to download form the Market)
2. Type
Code:
su
- to give it SuperUser permissions (Superuser app might come up asking you do you want to allow the emulator SU rights, allow it)
3. Then type
Code:
mount -o rw,remount /system
-to allow read/write operations on the /system partition, or basically to "mount" it.
4. And then, to remove an acctual app, type:
Code:
rm -f /system/app/app_you_wanna_remove.apk
- rm stands for remove, -f is force, and the rest is where the terminal can find the app for deleting. If you're deleting Email app, it would go like this:
Code:
rm -f /system/app/Email.apk
Carefull! This is case sensitive, and you're using the -f command. If you make a typo, nothing will be deleted, nor you will be warned about it! Check it before you press "enter"
List of apps you can delete (that i've deleted):
1. CarHomeGoogle.apk (App for using in the car, while the phone is mounted on the carholder)
2. CMStats.apk (CyanogenMod statistics)
3. CMUpdateNotify.apk (CyanogenMod update notifications. Not working without ROM Manager premium)
4. CMWallpapers.apk (no need for an explanation)
5. Development.apk (The development app, not needed by an average Joe)
6. DSPManager.apk (DSP Manager app. It's that equalizer app you can acces trough your music player. Eats 3megs of RAM!)
7. Email.apk (nothing to explain here)
8. GenieWidget.apk (Weather and News app and widget)
9. GoogleQuickSearchBox.apk (Google Search)
10. LiveWallpapersPicker.apk (no explanation needed)
11. PicoTts.apk (Text-to-voice, or voice-to-text, i'm not sure. I don't need it)
12. Protips.apk (That widget that shows up right after flashing the ROM. It even tells you that you can delete it lol)
13. RomManager.apk (DELETE DELETE DELETE!!!)
14. SoundRecorder.apk (again, no need to wear my keyboard)
15. Talk.apk (Google Talk app)
16. ThemeChooser.apk (Theme Chooser. If you delete it - no themes, only the stock one!)
17. ThemeManager.apk (Theme Manager. The app that can't work without the chooser, themes your system when you apply a theme)
18. VoiceDialer.apk (Voice Dialer app. Not to be confused with Phone app)
19. VoiceSearch.apk (no need for explanations)
20. LiveWallpapers.apk (^read the above^)
21. MagicSmokeWallpapers.apk (Some wallpapers, i don't know everything lol)
22. VisualizationWallpapers.apk (^read the above^)
23. SpareParts.apk (also not needed for average Joes)
If you're using a non-stock keyboard, you can delete LatinIME.apk
If you're using a non-stock gallery, you can delete Gallery3D.apk
If you're using a non-stock music player, you can delete Music.apk
Beware of deleting LatinIME.apk! That's the keyboard app! If you don't have another keyboard which is already set up as the default one, don't delete it, otherwise you'd get stuck with no keyboard, and you kinda don't want that lol
If you want to find out if there is more apps to delete (but i assure you that you won't find anything worth bothering), navigate the stock FileManager to /system/app and check it out.
Install V6 SuperCharger script by zeppelinrox
It's awesome! It will stop launcher redraws and potentially improve performance even more! I'm not going to write anything about it, because the download and the instructions are all found in his thread check it out!
[U9RC10] V6. SuperCharger or: How I Learned to Stop Laggying and Love the Launcher
Don't forget to give him a thanks!
That's it, for now! I will keep updating the thread with something new, and possibly better. YOU make a suggestion how to improve performance, and I can add it here in the first post!
Let me know what you think!
Click to expand...
Click to collapse
launcherpro is faster than adw.launcher anyways.
Depends on what do you think of when you say "fast". Disabling homscreen transition animations makes the launcher blazing fast
I prefer freezing over removing completely in case I need it
And u can also add buil.prop tweak
Sent from my GT-S5570 using Tapatalk 2
is this work for rom that uses cm7 as its base?
droidface said:
is this work for rom that uses cm7 as its base?
Click to expand...
Click to collapse
For cm setting Yes
For launcher and remove app it mostly universal
Sent from my GT-S5570 using Tapatalk 2
R.A.G.E said:
I prefer freezing over removing completely in case I need it
And u can also add buil.prop tweak
Sent from my GT-S5570 using Tapatalk 2
Click to expand...
Click to collapse
That's not a bad idea, but then again it's still in the internal memory taking up valuable space. Deleting all those apps and i have enough internal memory space to not need an sd-ext partition!
droidface said:
is this work for rom that uses cm7 as its base?
Click to expand...
Click to collapse
For the most part, it should. Athough this is for pure CM7, that ROM that it's based on could have come other apps for removing, or the ROM builder could've removed something on his own. System tweaks are the same, and if you use ADW launcher - it's the same too.
it wud be better to use TITANIUM BACKUP PRO-ALL for installing and uninstalling apps..
Titanium Backup Pro is a paid app, and there is no place for piracy on xda . Bare in mind we are removing bloatware from the ROM, not adding it
im using new experience v1.1 for me the best rom, but i have a high ram usage, task manager indicates 215 / 280. and sometimes facebook app closes when im not using it, can u recomend me something to fix that?. btw the room works fast etc. :laugh:
sry for my translator english :silly:
I am not sure if that ROM has any memory tweak preinstalled, but don't bother looking at task managers, beacuse Android manages RAM on its own pretty good. Sometimes it is perfectly normal for an app you do not use to close. It remains cached for fast startup, so it is not that big deal of an issue.
domcale said:
I am not sure if that ROM has any memory tweak preinstalled, but don't bother looking at task managers, beacuse Android manages RAM on its own pretty good. Sometimes it is perfectly normal for an app you do not use to close. It remains cached for fast startup, so it is not that big deal of an issue.
Click to expand...
Click to collapse
yep but is bad to me, because i lost my contacts sincronisation, and i have to log in every time is >.<!
There could be something wrong with account management of the ROM or the Facebook application itself. RAM memory issues should not cause a log off from your Facebook account. Consult with the ROM creator, maybe he can help you.
okay guys, thanks for your answers
Sent from my GT-S5570 using Tapatalk 2
for dealting system apps you could also use root uninstaller from the market.
Good point, I'll add it to the first post, but like I said, I do not prefer to intall an app to delete another one . Terminal emulator comes with the ROM, and you are going to need it at some point in time anyway, so that's IMO the best option. However, I will include it for the lazy ones
i just delete the apps and then i uninstall root uninstaller
That's ok, but i'm still tracking the habbit from Windows... never install an app you will use just once and then uninstall it. The reason - registry clogging.
I know Android doesn't function that way, it's just a habbit
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.