Related
Ok, so we all want the best of the best of experiences for our DX superphone. Well, I am here to tell you how I have my setup.
The goals of the ultimate setup are to:
1. Keep as much privacy as possible
2. Ensure the best performance
3. Ensure best method to extend battery life
4. Ensure best feel
5. Ensure HAPPINESS!
NUMBER ONE:
First things first; we need to install the absolute best ROM right now. The ROM is called FISSION 1.1 by Team DeFuse. You will most likely have to re-root the phone after installing though. It is worth the hassle.
Known issues with Fission 1.1 but I'm sure will be fixed:
1. Compass Calibration
2. No custom battery profiles
NUMBER TWO:
We need to install all of our applications.
NUMBER THREE:
If you don't have them already, download the paid version of Titanium Backup and the application called AUTOSTARTS and very very importantly, DROID WALL, SetCPU, CacheMate and also very importantly, Advanced Task Killer
NUMBER FOUR:
Restart phone. Upon reboot, we will first open up Droid Wall and give it root privileges. Then, we are going to fill in both boxes with checkmarks next to only the applications which you use a lot and need internet access! It is good practice to look at what all apps need access to when installing applications. If an app like Notepad for instance needs Internet Access, we know there is a problem. It is apps like these, we don't want to have access to the internet.
You will also have to have checkmarks next to "Media Server", "Browser", "Calender", "Calender Storage", "Email", "Google Search", "Maps", "Market", "Messaging", "Street View", and "Visual VM". Those are the ones which need to be allowed in order to not cripple your Android experience. Obviously, the remaining apps are UP TO YOU.
You should manually disable and re-enable the firewall after every reboot! You then want to kill Droid Wall and the other showing apps with Advanced Task Killer. Once Droid Wall sets the firewall rules, they stick regardless if the app is running or not. There is no need to leave it running.
NUMBER FIVE:
Now, we are going to open up the program AUTOSTARTS! It will take awhile to load all of the apps of your system. This app makes it so you can actually reliably use ADVANCED TASK KILLER without the apps you kill AUTOMATICALLY restarting and thus wasting precious battery.
You want to disable all your 3rd-party user apps in EVERY CATEGORY except for the Widget Categories at the bottom. For the first app you disable from starting, you will have to give AUTOSTARTS root privileges.
Don't disable "Google Voice", "Visual VM", "Dialer", "usb", "Dialer Storage", "Battery Manager", "Battery Manager (Power Profile Receiver)", "Google Partner Setup", "Google Services Framework", "Voice Dialer" (If you use it), "Email" (If you use it), "Messaging", "Bluetooth Share" (If you use Bluetooth), "Contacts Storage", "Droid Wall", "SetCPU", "ADW Launcher" (If use it), "Launcher Prof" (If use it) or "Launcher" (If use the stock launcher)
Everything else should be clicked on and disabled except for apps which are your widgets on your homescreens and in the Widget Categories!
You are going to notice a crazy increase in speed from this!!!!
NUMBER SIX:
We need to reboot. Upon reboot, open up ADVANCED TASK KILLER. We now need to put some apps on the ignore list.
The apps I have on my ignore list are:
SetCPU, Messaging, Music, Google Search, Market, Visual VM, Beautiful Widgets, Voice Search, K-9 Mail and Google Voice
You would also want to put any apps which are related to any widgets you have on your homescreens on the ignore list too!
This will effectively make it so any app we close, IS CLOSED FOR GOOD until we ourselves initiate it MANUALLY.
NUMBER SEVEN:
My phone is a dud; well at least the CPU is. It won't go over 1100mhz and be stable regardless of how much voltage I crank into 'er. So, for my phone, I modified the 1.1Ghz .zip folder which is installed in the Fission folder of your SDCard when you install Fission. I modified the setscaling.sh in text editor and changed the following values:
Changed the 800mhz to 900mhz. You may or may not have to raise the voltages that they have pre-set for the 800mhz and 1100mhz settings. If you are not stable, just give each of them a couple notches of increase.
NUMBER EIGHT:
Upon reboot, we need to setup SetCPU. We are going to create 3 profiles
1. Screen off --> 300min / 600max --> OnDemand
2. Charging AC/FULL --> 300min / 600max --> OnDemand
3. Charging USB/FULL --> 300min/ 600max --> OnDemand
We then go back to the homescreen "of SetCPU" and change our values of what we want the phone to do whenever the screen is on and it is not charging. Here we want to put 900mhz for the min and 1100mhz for the max.
For some reason, even if SetCPU is not disabled in AUTOSTARTS, it doesn't load the values upon reboot. You will have to manually open up SetCPU just one time for each reboot.
IMPORTANT: If you want to OC higher or maybe not even at all, have at it. However, I still think SetCPU and the profiles I listed above would be great for you.
NUMBER NINE:
This may not be an option for some of you, but I like to disable remembering form data, cookies, cache, passwords, and history on my browsers.
The best browser to use "IMHO" is the new XSCOPES version 6.
If you like some other browser, just change the privacy settings to those of above to be safe. If you can't live without, then just don't worry about it.
NUMBER TEN:
Install CacheMate for Root Users.
In the settings we want to have checked:
1. Clear TA Utility Caches
2. Close CacheMate on Close
3. Clear Admob and Google
4. Clear Flash Cache
5. Clear Temporary Cache
Then, we want to have everything checked in Data Experimental and SDCard which is Relevant to our phone. For any app you don't have, don't put a check next to it. If you use apps like APMobile (Associated Press), you want to uncheck that and apps like it so you don't have to set it up every time you open the app.
I don't really like letting CacheMate run all the time being set to automatically clear on intervals. I didn't mention it, but I NEVER leave ADVANCED TASK KILLER run all the time either.
Uncheck power clear on the main screen and clear the cache ever day or two.
NUMBER ELEVEN:
Install ADW Launcher. It is by far better than LauncherPro. Only continue to use LauncherPro if you can't live without its widgets.
In ADW Launcher, we want certain settings done.
1. In Screen Preferences, we want to have both Desktop Scrolling Speed and Desktop Overshoot set to "0"
2. In Drawer Settings, we want animated drawer check, show app labels checked, fade app labels checked and for background color, I like to use a dark color with some transparency!
For Zoom Effect speed, set it to its lowest setting of 300ms
3. Under System Preferences, we want to check Wallpaper Hack and set Scrolling Cache to "Auto". Obviously, if you have widgets, you will want to check scrollable widget support.
4. In UI Settings, I check everything besides:
Dockbar, Closing folder, Secondary ActionButtons and Show Desktop Indicator.
I have AB Scale Factor set to "5".
After you get your homescreens all set up EXACTLY how you want them, backup both the desktop configuration and backup ADW settings. Also, make sure to do another backup in Titanium so when you restore ADW Launcher after installing a new ROM, it is exactly how you had it before.
NUMBER TWELVE:
Open up the program which is already installed called Spare Parts. It will be in your App Drawer. Don't install it again from the market unless you for some reason don't already have it in your app drawer.
1. I have haptic feedback and compatibility mode checked.
2. Set the "Window Animations" and "Transition Animations" to FAST
NUMBER THIRTEEN:
Do a Titanium Backup via Batch operation.
1. There are only 2 options in the batch operation options which you should ever need to use!!! They are:
A) RUN - Backup all new apps & newer versions
B) RUN - Restore Missing Apps with data
Run the backup every once in awhile to keep the backup of your apps up to date.
IMPORTANT:
When restoring apps, UNCHECK ALL SYSTEM APPS FROM BEING RESTORED!
The paid version gives you HyperShell which means you don't have to manually click each app when it is restoring. It makes the process very simple.
You also want to uninstall the older version of Flash Player and get the newer one from the market.
I have followed this guide for Titanium and have installed numerous ROMS for the Droid 1, HTC Droid Incredible and now the Droid X WITHOUT EVER HAVING ISSUES!!!
NUMBER FOURTEEN:
Go into ROM Manager and install the AOSP Keyboard under /Download ROM/Drod2169/CHANGE OPTIONS-Focused-1.0/AOSP KEYBOARD
You will automatically have to check FIXED 8MP AOSP Camera as well. That is the camera installed by default on Fission 1.1 so it won't hurt anything. Don't check backup data or wipe data/cache!
Also, I would install both QuickOffice and DX_Music.zip under the SDCard/Fission/Add-Ons directory. You obviously have to do this in Recovery!!!
The Music player will be 100% identical to the one that comes installed by default on Fission 1.1, but it gives you the option to pause play and seek tracks from the lockscreen!
NUMBER FIFTEEN:
Install any themes or mods which are compatible with your ROM and set up your sounds and everything else you like to do and enjoy your android device to its fullest
I know I probably missed a couple things but will update when I remember.
VIVA LA ANDROID
EDIT: I had Fission 1.0 for some reason. I meant Fission 1.1. I'd also like to point out that Rubix 1.0 is the same exact thing as Fission but with more optimizations and tweaks. I ran them both but slightly prefer Fission 1.1
reserved...
Nice post!
Sent from my DROIDX using XDA App
Sleuth255 said:
Nice post!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Thanks a lot! That's all derived from months of obsessive learning along with trial and error
How dare you recommend Advanced Task Killer. You need to have your Android License revoke immediately.
Since we're talking about rooted phones and memory management, use Autokiller. It does what android already does natively, only better.
Nice write up, but do yourself a favor and get rid of ATK!
LexusBrian400 said:
How dare you recommend Advanced Task Killer. You need to have your Android License revoke immediately.
Since we're talking about rooted phones and memory management, use Autokiller. It does what android already does natively, only better.
Nice write up, but do yourself a favor and get rid of ATK!
Click to expand...
Click to collapse
Please don't get caught up on the ATK thing. I don't want this thread turning into a pro or con ATK. One will however say that ATK without AUTOSTARTS is pointless. Due to AUTOSTARTS, ATK is once again relevant and really beneficial.
If the app AUTOSTARTS or anything like it wasn't available, I wouldn't tell anyone to install ATK. With my setup, any app we kill with ATK will not be automatically restarting thus wasted battery. That was the biggest issue with ATK before AUTOSTARTS was available. Now, anything we kill are only apps we ourselves initiated.
Apps left running do still use CPU resources. The latest privacy study of Androids apps show that 50% or so of the tested apps sent private information to advertisers in the background.
When the Android system only has like ~40mb of free system RAM available, the system will no matter what bog down somewhat. We can get rid of this from ever happening.
Just put the little green ATK widget on your main homescreen and one tap and your done. The ATK widget takes the same amount of space as an icon. It is simple and easy.
Doing it like this ensure at no point EVER is the Android system going to lag.
Sleuth255 said:
Nice post!
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Well was I happy seeing those post when did you get a Droid X.
-McMex
A few weeks ago. Excellent device too. I'm confident that the locked BL will be defeated. I'm running through some of luv2increase's mods now... I like the idea of being able to defeat autostart and place strict control over the apps I allow to run.
Sleuth255 said:
A few weeks ago. Excellent device too. I'm confident that the locked BL will be defeated. I'm running through some of luv2increase's mods now... I like the idea of being able to defeat autostart and place strict control over the apps I allow to run.
Click to expand...
Click to collapse
Yes it is an excellent device just today I posted on Twitter I have all the high end Android phones and the Motorola implementation of the Droid X is by far the best nice polish too. I been playing a lot with SetCpu profiles (removing bloatware via adb) and power saving settings and can get over 18 hours of heavy usage. Just starting to try these other ROMs out. As always if you need a tester or I can help you with something let me know I have been on Android a while now and have a lot of experience and a ton of apps.
A lot of you guys have no idea the asset that Sleuth is having a Droid X.
-McMex
Alot of great tips in the OP. I actually run with almost this exact setup. I am using Rubix 1.0, though. Great rom. These tips will help tremendously with performance and battery life. Thanks for passing this along.
Suggestions
Gamer Mode
New Taks Manager
Game Mode
Description: When putting your phone into Game mode it will automaticly stop all the running background applications, freeing as many RAM as possible.
- You won't be able to recieve text messages
- All background application sync will be stopped
- All unnecessary applications will be stopped
- Still able to recieve calls
- All required system applications will still be running
More Functionality
Give the user the ability to add their own blacklist or whitelist, so if users choose that their application must remain active, it will.
New Taks Application
Description: When it comes to memory or RAM the galaxy doesn't actually narrow it down. It doesn't have much RAM space and when you run too much services in the back, it will drain your battery as the preformance of your phone.
New Options
- Add a checkbox so users can choose if the app must run or be excluded from start up.
- Add an option that when you close the application, all the running background services will close with it
Possible system structure
Active Processes (Apps) | System Processes | Downloaded | All Applications
All other ideas or suggestion are all welcome
Intensity007 said:
Suggestions
Gamer Mode
New Taks Manager
Game Mode
Description: When putting your phone into Game mode it will automaticly stop all the running background applications, freeing as many RAM as possible.
- You won't be able to recieve text messages
- All background application sync will be stopped
- All unnecessary applications will be stopped
- Still able to recieve calls
- All required system applications will still be running
More Functionality
Give the user the ability to add their own blacklist or whitelist, so if users choose that their application must remain active, it will.
New Taks Application
Description: When it comes to memory or RAM the galaxy doesn't actually narrow it down. It doesn't have much RAM space and when you run too much services in the back, it will drain your battery as the preformance of your phone.
New Options
- Add a checkbox so users can choose if the app must run or be excluded from start up.
- Add an option that when you close the application, all the running background services will close with it
Possible system structure
Active Processes (Apps) | System Processes | Downloaded | All Applications
All other ideas or suggestion are all welcome
Click to expand...
Click to collapse
Both of those are already avaiable, the first is the Gamerzrom (although not perfect), the second is avaiable as many system manager app, search for it.
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
if you rooted, you can use Autostarts or ROM toolbox from the playstore. it can change the receivers of the apps not to start at boot
CooLasFcuK said:
I know that android is very good at handling background processes and ram but I have so many apps that I don't use at all. They consume big amount of ram and for instance, sometimes browser loads pages again when I get back to it from another app. I assume this is because of ram. So I guess, if I can shut down some running apps in the background, available ram would be more.
I can see them at settings-apps-running(or cached processes).
For example, right now in "running" section I have 9 processes and 3 of them are poweramp, awesome beats, accuweather.com and in "cached processes" I have 10 processes and 6 of them are beautiful widgets,calendar storage,google account manager, google search, calendar, google play store. Other processes are system services that I have no problem with. When I go to developer settings-background process limit and block them, there are no cached processes anymore but that probably has a side effect. I wish I could choose which apps I want in the background.
I can shut down these apps manually but every time I restart the phone, they are there again. How can I stop them?
Click to expand...
Click to collapse
The simple answer is that you don't need to stop them!
As you say, Android is already very good at keeping track of background processes, to the extent that if a new program needs more RAM, Android itself will kill a background process that hasn't been used for a while to free up RAM for the new program.
The Cached processes screen SHOULD be full of recently used programs; it shows that Android is doing what it is supposed to do and is shifting inactive processes out of active RAM in case you want to load it again, without completely dumping the process memory.
Now, as for the side effect you mentioned, that would be a significant hit on battery life. By holding programs in RAM as it is supposed to do, the OS can load the program quickly and cleanly and more efficiently by simply reading the RAM rather than reading flash, writing to RAM, then reading from RAM. The general mantra for UNIX based systems is that unused RAM is wasted RAM.
Another thing to note is that if you do not close tabs when switching active programs (including going to homescreen) then the Browser is designed to hold that tab in memory. Even if you close the Browser (excluding closing the tab specifically with the "little x"). Even if you reboot the damn phone, it will still load the tabs/pages you had open last. The pages are not held in memory as such, just what was open and what tab order, so if you do open the browser after a while, it will load the last page from scratch.
TL;DR version: The running and the cached processes will remain exactly where they are until a new program needs more RAM than is available, at which point Android will kill something to make room. You do not need to do this manually. It will cause more power drain by making very inefficient use of RAM/Flash memory. Empty RAM is wasted RAM.
whilst Chaos is right, I notice severe performance drops when ram is filled, despite Androids theoretical advantage. It doesnt work...
Best to prevent from loading altogheter.
Root, lose warranty, backup apps, uninstall or freeze apps so the bloatware is removed.
For others, change autostart settings in Romtoolbox. So they wont start on boot.
Search for safe stuff to delete. There are lists for that
Sent from my GT-N7000 using Tapatalk 2
Or just dont install the apps that you dont really need.
Via GtN7000
LoVeRice said:
Or just dont install the apps that you dont really need.
Via GtN7000
Click to expand...
Click to collapse
Lol, even then you might still need to remove bloatware lol
Sent from my GT-N7000 using Tapatalk 2
Thanks so much for detailed answers.
The app 'Greenify' is a marvelous work by oasisfeng
This is the original thread : http://forum.xda-developers.com/showthread.php?t=2155737
Playstore link : https://play.google.com/store/apps/details?id=com.oasisfeng.greenify
*Why am I sharing this app?
Because this is going to help those who are running android 4.x or higher, having a feeling that our phone's ram and battery is not enough and still not aware of the process 'Greenifying'
*Are you depending on the process 'freeze' & 'unfreeze' to save your space and feeling it as little inconvenient to do it every time you use the frozen app ?
Then Greenify is the solution.
*This is the definition of Greenifying an app.
"Greenifying an app implies that you are aware that all the background functionality of this app will become out of service during the hibernation except when you are using this app:
Greenify helps you identify and put the bad behaving apps into hibernation when you are not using them, to stop them from lagging your device and leeching the battery, in an unique way! They can do nothing without explicit launch by you or other apps, while still preserving full functionality when running in foreground, similar to iOS apps."
When I read the above I was like " wow, this is the thing that I was searching for ! "
*It is designed and implemented in extremely light-weight, with an average RAM footprint at 2M in total, and nearly zero CPU and battery consumption.
Things to remember :
# The background functionality of the greenified apps will be disabled. The background functionality includes but not limited to:
> Persistent background services
> Broadcast receivers, which respond to global device events, such as network state change, SMS reception.
> Alarms, which activate background task at specific time or interval.
> Widget update. Widget should display but never update because periodic update involves background task.
> Push messages. Push is also disabled since it would activate background task on Android, unlike iOS which just shows up messages to user.
>Please DO NOT greenify alarm clock apps, instant messaging apps unless you never rely on them. Please be sure to verify the impact of greenified apps on which you heavily relies.
# not supported for Android 2.x
In my opinion, this app does what it says.Hope this will be helpful.
For more details, visit the original thread. :good: To the developer of this app.
IMPORTANT: I think i reach the final build for this script. All in all i present two version of the script. One codename Balanced that is the initial script (and there for is the most balances i've got) and another codename Ultra Smooth as it is very smooth but may be too aggressive on background secondary services.
Balanced:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
https://mega.nz/#!NoJEXIiI!NXTetoxuwBMBzxsUCVIcrvEB_jxUSp3sE1z5e6VQIkc
Click to expand...
Click to collapse
Ultra Smooth:
#!/system/bin/sh
echo "9472,13824,19968,44544,58368,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 228mb
Hidden Apps: 174mb
Secondary Server: 78mb
Visible Apps: 54mb
Foreground Apps: 37mb
https://mega.nz/#!N4IiSboa!v4tSk1X_RZeGBJesrJbJUpJZvcdMiN2rTE4loTWHsYI
Click to expand...
Click to collapse
Hello, for all the Moto G users who have the crDroid ROM and have tried the Pink Kernel, i've made this topic so we can try to find the root from the performance issues with the combination of said ROM and Kernel.
For who follow my last post on both the thread of the ROM and Kernel, i had a theory about what was the issue.
After read the experience other users had with it and my own i came to the conclusion that the stability issue, force stop from heavy apps and even small reboots ("BSOD") came from a very different philosophy on the OOM (Out of Memory) configurations of the ROM stock Kernel (that don't have this issues) vs the Pink Kernel on this ROM.
With the Stock, i realize that we have much more free RAM (i got from 400mb free to 240mb free) then on Pink Kernel (that i was ranging from 280mb free to 144mb free). That is a big difference.
Our devices are amazing phones, but it RAM amount isn't the best now days, so i figured that heavy Apps (such as the Facebook one, the one who most had issues with the ROM+Kernel) just don't have much free RAM from the pool. So it hit the page file/swap (there for cause a very laggy experience and force closes) and if the page file/swap don't do the cut it reboot the phone.
On the stock kernel as it give much more free RAM it didn't had any of those issues (even though on my experience the Facebook App never run as smooth as the other apps, even on the stock kernel). So i tried my first attempt to remedy this issue.
As my Kernel management app of choice don't apply OOM settings after reboot (it go back to the stock one of the Kernel we have), and i like it as if it go wrong on boot it is ok again, i've made a simple script, so on every reboot it apply my settings and too that is a simple way that who don't use Kernel management apps can have this "fix".
I also don't like to use INIT.D for this as if it go wrong it will bootloop. With SManager (a free app on the play store) it is very safe if go wrong and if not.. it work just as INID.D in this case.
To who don't know how to use SManager, just get it on the play store. After open the app click on the menu button and choose new program. It will ask you to give a name, you can choose any one you like (i've choose OOM-FIX).
After give the name open it from the list within the app and click (to enable) the SU and BOOT option. After it click on the edit button so you can write the script.
On the script editor, here is the code of the script:
#!/system/bin/sh
echo "9472,13824,19968,44544,58368,65536" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
Now save everything and either run it or reboot.
If you do use a Kernel Management app who apply OOM custom settings on each reboot, this settings on the script represent:
Empty Apps: 256mb
Content Providers: 228mb
Hidden Apps: 174mb
Secondary Server: 78mb
Visible Apps: 54mb
Foreground Apps: 37mb
Click to expand...
Click to collapse
This was the best middle ground i found from the Pinky Kernel OOM vs the Stock (with my settings i'm getting from 386mb free to 244mb free).
I only tester for two days so far, but my experience on Facebook (the app who most gave me trouble) was very satisfactory. It isn't 100% perfect but for my use it is a good 85% (must remember that even on the stock kernel it wasn't 100% good).
The app don't lag as much, only if we spam commands such as click on the back button more then once at the same time it lag more then acceptable. But scroll down on the timeline, messages and person profile was very good.
Open too many pages inside the app lag a little too but nothing close to force boot or even force close the app for me.
But i'm not the most heavy FB user, neither the most heavy Phone user.
That is where you guys come in. If you guys who use the amazing crDroid ROM and love the Pink Kernel want to keep this combination, try this script/OOM settings i just shared, so if it need more tweaks (and if it really is the cause of the issue) we can do it. As for my use it is fine, but i want to know about on other phones and users/uses.
Just to share the full spec and config of my phone, it is a Moto G 4G LTE XT1040 using the latest crDroid with the latest Pink Kernel. I am not a heavy user and my GAPPS is the minimum pack. I greenify almost all apps on the phone (including many system ones), i have a big wakelock setting to not allow apps to wakelock and all in all i do the best to only let the apps i want to run (and usually are the foreground ones i've choose to use).
How ever i do use also Xposed and a lot of custom tweaks.
My Pink Kernel configuration (With 3C Toolbox) is a CPU profile that i'll share:
Profile:
Intelliactive @ min:300mhz and max 1,18ghz
All cores setup as free
TCP/IP Algorithm: Veno
SD Cache: 512
I/O: ROW
Double tap to wake: On
When the screen is off i have a userspace profile locked at 300mhz min and max frequency.
So there you go, who want to use the ROM and Kernel try this script or OOM out (you can try a Tune for profiles like mine too in case to emulate what my phone got as a result) and post the results, if it got better, worse or if it fix.
For me the phone is very present to use, VERY smooth and the Facebook App is manageable now.
NEW: INIT.D script Download:
https://mega.nz/#!N4IiSboa!v4tSk1X_RZeGBJesrJbJUpJZvcdMiN2rTE4loTWHsYI
(please do a NanoBackup before apply it, for test if it work open the terminal and type: cat /sys/module/lowmemorykiller/parameters/minfree).
Click to expand...
Click to collapse
CHANGELOG:
v0.1:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
Click to expand...
Click to collapse
v0.2:
#!/system/bin/sh
echo "13312,17664,19968,37120,53248,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 208mb
Hidden Apps: 145mb
Secondary Server: 78mb
Visible Apps: 69mb
Foreground Apps: 52mb
Click to expand...
Click to collapse
v1.0:
#!/system/bin/sh
echo "8191,12544,19968,37120,53248,65536" > /sys/module/lowmemorykiller/parameters
Empty Apps: 256mb
Content Providers: 208mb
Hidden Apps: 145mb
Secondary Server: 78mb
Visible Apps: 49mb
Foreground Apps: 32mb
Click to expand...
Click to collapse
v2.0a-Codename-Balanced:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
Click to expand...
Click to collapse
v2.0b-Codename-Ultra_Smooth:
#!/system/bin/sh
echo "9472,13824,19968,44544,58368,65536" > /sys/module/lowmemorykiller/parameters/minfree
Empty Apps: 256mb
Content Providers: 228mb
Hidden Apps: 174mb
Secondary Server: 78mb
Visible Apps: 54mb
Foreground Apps: 37mb
Click to expand...
Click to collapse
Pupet_Master said:
Hello, for all the Moto G users who have the crDroid ROM and have tried the Pink Kernel, i've made this topic so we can try to find the root from the performance issues with the combination of said ROM and Kernel.
For who follow my last post on both the thread of the ROM and Kernel, i had a theory about what was the issue.
After read the experience other users had with it and my own i came to the conclusion that the stability issue, force stop from heavy apps and even small reboots ("BSOD") came from a very different philosophy on the OOM (Out of Memory) configurations of the ROM stock Kernel (that don't have this issues) vs the Pink Kernel on this ROM.
With the Stock, i realize that we have much more free RAM (i got from 400mb free to 240mb free) then on Pink Kernel (that i was ranging from 280mb free to 144mb free). That is a big difference.
Our devices are amazing phones, but it RAM amount isn't the best now days, so i figured that heavy Apps (such as the Facebook one, the one who most had issues with the ROM+Kernel) just don't have much free RAM from the pool. So it hit the page file/swap (there for cause a very laggy experience and force closes) and if the page file/swap don't do the cut it reboot the phone.
On the stock kernel as it give much more free RAM it didn't had any of those issues (even though on my experience the Facebook App never run as smooth as the other apps, even on the stock kernel). So i tried my first attempt to remedy this issue.
As my Kernel management app of choice don't apply OOM settings after reboot (it go back to the stock one of the Kernel we have), and i like it as if it go wrong on boot it is ok again, i've made a simple script, so on every reboot it apply my settings and too that is a simple way that who don't use Kernel management apps can have this "fix".
I also don't like to use INIT.D for this as if it go wrong it will bootloop. With SManager (a free app on the play store) it is very safe if go wrong and if not.. it work just as INID.D in this case.
To who don't know how to use SManager, just get it on the play store. After open the app click on the menu button and choose new program. It will ask you to give a name, you can choose any one you like (i've choose OOM-FIX).
After give the name open it from the list within the app and click (to enable) the SU and BOOT option. After it click on the edit button so you can write the script.
On the script editor, here is the code of the script:
#!/system/bin/sh
echo "8192,16384,24064,32768,49152,65536" > /sys/module/lowmemorykiller/parameters/minfree
Now save everything and either run it or reboot.
If you do use a Kernel Management app who apply OOM custom settings on each reboot, this settings on the script represent:
Empty Apps: 256mb
Content Providers: 192mb
Hidden Apps: 128mb
Secondary Server: 94mb
Visible Apps: 64mb
Foreground Apps: 32mb
This was the best middle ground i found from the Pinky Kernel OOM vs the Stock (with my settings i'm getting from 386mb free to 244mb free).
I only tester for two days so far, but my experience on Facebook (the app who most gave me trouble) was very satisfactory. It isn't 100% perfect but for my use it is a good 85% (must remember that even on the stock kernel it wasn't 100% good).
The app don't lag as much, only if we spam commands such as click on the back button more then once at the same time it lag more then acceptable. But scroll down on the timeline, messages and person profile was very good.
Open too many pages inside the app lag a little too but nothing close to force boot or even force close the app for me.
But i'm not the most heavy FB user, neither the most heavy Phone user.
That is where you guys come in. If you guys who use the amazing crDroid ROM and love the Pink Kernel want to keep this combination, try this script/OOM settings i just shared, so if it need more tweaks (and if it really is the cause of the issue) we can do it. As for my use it is fine, but i want to know about on other phones and users/uses.
Just to share the full spec and config of my phone, it is a Moto G 4G LTE XT1040 using the latest crDroid with the latest Pink Kernel. I am not a heavy user and my GAPPS is the minimum pack. I greenify almost all apps on the phone (including many system ones), i have a big wakelock setting to not allow apps to wakelock and all in all i do the best to only let the apps i want to run (and usually are the foreground ones i've choose to use).
How ever i do use also Xposed and a lot of custom tweaks.
My Pink Kernel configuration (With 3C Toolbox) is a CPU profile that i'll share:
Profile:
Intelliactive @ min:300mhz and max 1,18ghz
All cores setup as free
TCP/IP Algorithm: Veno
SD Cache: 512
I/O: ROW
Double tap to wake: On
When the screen is off i have a userspace profile locked at 300mhz min and max frequency.
So there you go, who want to use the ROM and Kernel try this script or OOM out (you can try a Tune for profiles like mine too in case to emulate what my phone got as a result) and post the results, if it got better, worse or if it fix.
For me the phone is very present to use, VERY smooth and the Facebook App is manageable now.
Click to expand...
Click to collapse
You did an amazing job! Yesterday when I tried the kernel everything was softrebooting, now the phone is smooth as butter! First time we got pink kernel working on a ROM! Have my thanks
Sparubens said:
You did an amazing job! Yesterday when I tried the kernel everything was softrebooting, now the phone is smooth as butter! First time we got pink kernel working on a ROM! Have my thanks
Click to expand...
Click to collapse
Thanks m8, anything you don't like feel free to tell and we tune it even more
New setup/tune.
I think this will be final, check out the new values and test
Final build release.