Related
These steps are intended for use on the stock Droid X2. I'm sure they will be close to the same on other phones, but if your phone is not a stock Droid X2, know that the steps may be different or you may get unfavorable results. Always backup anything you don't want to lose.
Before even considering this, READ ALL THE STEPS. Then READ IT AGAIN.
There are two tweaks recommended here: V6_Supercharger and SD Speed Increase.
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
3. BusyBox 1.18.2 or earlier
NOTE: I haven't confirmed the script works on 2.3.4... You may want to use the latest version of the script if you have 2.3.4
Installing/Using the script:
1. Install BusyBox. There are a number of ways to get this... it comes as part of Titanium Backup, for example. If you're not sure if you have it, or not, you can use BusyBox Installer (free on Market) to detect whether or not you have it and install it if you don't.
- Note: BusyBox Installer tells you which version you have installed on the main screen after it loads... it should be in a list that starts with "Your device is Rooted"
- Note: Make sure you don't install BusyBox 1.19 or anything newer than 1.18.2
2. Download the script. Save it in a place where you'll be able to find it.
3. Launch Script Manager and find the downloaded file (usually in /mnt/sdcard/download). Long-press no it and select rename, then delete the .txt from the end. You should have a file named "V6_SuperCharger_for_Android-update8.sh"... Press once on the script file to load it into Script Manager, check the 'Run as Root' box (DO NOT select "Run at Boot") and push "Run" to execute the script.
4. The script will run and ask for a speed. Touch anywhere on the screen to open your keyboard. Type 1 if this is your first time running the script, 0 if you're a fast reader or you are in a hurry. Next, it lists 17 options and gives an input prompt. Type 8 and push Enter. (This selects the called MegaRAM 1 preset, but feel free to try others, if you're so inclined)
5. Once script finishes, type 17 and push enter to end the script. Push the phone's Menu button and select 'exit' to return to the list of scripts.
6. Pushing the phone's Back button should bring you to a file browser. Push the '..' line (second from top) until the top line reads '/'.
7. Push the phone's Menu button, push 'More' and then 'Config'. Check the box 'Browse as root'. Push the phone's Back button to return to the file browser.
8. Browse to /data and select '99SuperCharger.sh' (This script was created by the first script and makes sure the settings from the first script are re-applied on boot)
9. Select both 'Run as root' and 'Run at boot'. Push 'Save' and then 'Run'. If it says "Exit code 0" at the top of the screen, the script ran successfully. Any other Exit codes should be reported.
10. Almost all the settings are now in place... but reboot your phone to get the last ones implemented.
11. After reboot, launch Script Manager and run V6_SuperCharger_for_Android-update8.sh (the first script). Select 0 at the first prompt, look for the current minfrees values... it should say "Launcher is HARD TO KILL!" and "Current minfrees = 6, 12, 40, 60, 80, 100". If the settings are correct, type 17 to exit and you are done. If not, re-read steps because you missed something.
Credit goes to Zeppelinrox, see this thread for more info on this script.
Requirements for SD Speed Increase:
1. Rooted Phone (Gingerbreak 1.20)
2. SD Speed Increase (free on Market)
Configuring SD Speed Increase:
1. Open the app and adjust the memory slider to 2048
2. Check 'Set on every reboot'
3. Push the red button
4. Reboot the phone
Advanced: 3G TurboCharge
- I'll post full step-by-step instructions soon, but for now, here are two more scripts from Zepplinrox that will boost 3G performance... (Forum Post) Run 3GTurboChargerInstaller.sh and 98KickAssKernelTweaksInstaller.sh once each (Hint: Don't forget to remove the .txt extension). The second script creates this boot script: /system/etc/init.d/98kickasskernel, so you will have use this thread to get init.d created (Side note: I haven't been able to get it to actually run the scripts that are placed in init.d... we're stuck with Script Manager for now). Run all scripts as root, obviously.
Questions, Comments & Corrections are welcome!
To Do:
Update SuperCharger to update7 (need to test it myself first)
Test and implement AutoStart script
Edit:
06/27/2011 - Removed ro.Home_app_adj tweak. It's handled by the SuperCharger script.
06/27/2011 - Updated SuperCharger script instructions to use v4 of the script.
07/14/2011 - Updated SuperCharger script instructions to use v5 of the script.
07/25/2011 - Added BusyBox requirement to the SuperCharger script.
07/25/2011 - Updated SuperCharger script instructions to use v8 of the script. Rewrote most steps for improved clarity.
08/19/2011 - Updated 3G and Kernel links.
Using it now... Cant see a major difference but I can tell some things are faster... and havent had any reason to kill any apps because the phone starts to get sluggish so IMO thats a major plus and a sign that it is working...
Oh yeah... use option 9! Megamemory device....
Sent from my DROID X2 using XDA App
alright so I did all the steps... but when i re-open it (step 10) it goes back to the original 1-3 menu. what did i do wrong?
falconfan101 said:
alright so I did all the steps... but when i re-open it (step 10) it goes back to the original 1-3 menu. what did i do wrong?
Click to expand...
Click to collapse
What does the script say those numbers mean?
The 1-3 settings are just setting the scroll speed of the text when the script runs. I personally like to set it to 1 (fastest) but it really doesn't matter. 3rd gives you a chance to read everything.
Works, like a charm, now if i wanted to get rid of it would it just be going back through the steps and undoing what i did?
slowz3r said:
Works, like a charm, now if i wanted to get rid of it would it just be going back through the steps and undoing what i did?
Click to expand...
Click to collapse
No, all you have to do is uninstall script manager and reboot. Deleting the scripts is optional.
Sent from my DROID X2 using XDA App
This script really made a big difference.
Great work, and there is no battery drain...
Sent from my DROID X2 using XDA Premium App
vvildcard said:
Before even considering this, READ ALL THE STEPS. Then READ IT AGAIN.
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
Installing/Using the script:
1. Download this ZIP and extract the script to your sdcard.
2. Load the V6_SuperCharger_for_Android-update4.sh script into Script Manager and check the 'Run as Root' box (DO NOT select "Run at Boot"). Push "Run" to execute the script.
3. The script will run and display a list of 16 options and a prompt. Touch anywhere on the screen to open your keyboard. Type 9 and push Enter. (This selects the option called MegaMemory Device)
4. Once script finishes, type 16 and push enter to end the script. Push the phone's Menu button and select 'exit' to return to the list of scripts.
5. Pushing the phone's Back button should bring you to a file browser. Push the '..' line (second from top) until the top line is '/'.
6. Push the phone's Menu button, push 'More' and then 'Config'. Check the box 'Browse as root'. Push the phone's Back button to return to the file browser.
7. Browse to /data and select '99SuperCharger.sh' (This script makes sure the other script runs on boot. Otherwise you would have to do steps 2-5 everytime you boot your phone)
8. Select both 'Run as root' and 'Run at boot'. Push 'Save' and then 'Run'. You will most likely see 2 errors at the end of the 99SuperCharger script... this is expected.
9. Reboot your phone, but you might already notice a significant difference in speed and zero redraws from your launcher.
10. After reboot, launch Script Manager and run the V6_SuperCharger_for_Android.sh script, but this time don't select any options just look at your current settings and make sure they are the same as the Step values you put in. Right under the list of options, it should say: 'NOTE: Current minfrees =' If they are correct, type 16 to exit and you are done. If not re-read steps because you missed something.
Credit goes to Zeppelinrox, see this thread for more info on this script.
These steps were posted a while ago on droidforums.net... you might run through the comments on that forum if you have any trouble and don't want to wait for a reply.
Click to expand...
Click to collapse
What are the values that it sets? I currently am running the V6 script and unless this is a newer version my option 9 is called "Gaming settings". At any rate I did option 10 and set values at 6,12,75,125,150,175. What does this set them to?
disregard my previous post. I ran it and found they are the same settings I have been using. Thanks for the updated script though.
is their a script dev thread where updated scripts are posted
THANK YOU!
I was about 10 mins away from calling VZW and telling them to take this back and send me my original X back... I wasn't able to get ANY Ver. of Pandora to play or even Slacker half the time. The complete phone would freeze ALL the time to the point I could not do anything unless I performed a Battery Pull to hard reset.
This fixed ALL my issues. I don't even have the 1-3 second wake delay I was experiencing before. So far so GREAT!! As I type I even realize that while Pandora is playing and the phone is charging it is not getting nearly as hot as it was before? I don't care why it's working better now, but I'm glad it is!
I can't wait until we can get a decent rom with these fixes already in place! I loved Liberty on my old X. I miss it!
A+++\
slowz3r said:
is their a script dev thread where updated scripts are posted
Click to expand...
Click to collapse
The end of the OP has the link.
This's pretty slick. While I haven't noticed huge gains in most areas, due to having cleaned and optimized my phone, the whole thing just seems to run with extra smoothness. Also, there's no more delay when waking the phone.
Sent from my DROID X2 using XDA App
I ran this script on my phone and couldn't be happier. Stock I'd get about 115mb ram free on ATK. After root and de-bloat I topped out at 170. After this script, 220+!!!
Sent from my DROID X2 using XDA App
This is a godsend!
Thanks for creating this thread and providing the most excellent script for memory mgmt. I've just installed it on my DX2 and boy, does it fly! I now see 130m+ memory free whereas before it would bounce between 50M-90M. Many thanks! I will run the remainder of this week and see if there are other impacts.
I do have one question, however, since I'm a newbie to all this: can I now remove the ATK application and disable the native Task Manager application with this script now in place? Or should I keep these as add'l failsafes?? Please advise and thanks for all the great info on this forum!
droid4ever said:
I do have one question, however, since I'm a newbie to all this: can I now remove the ATK application and disable the native Task Manager application with this script now in place? Or should I keep these as add'l failsafes?? Please advise and thanks for all the great info on this forum!
Click to expand...
Click to collapse
Try using Titanium Backup Pro to freeze these programs. I have both apps frozen, and my phone is fine
Sent from my rooted, supercharged Droid X² using XDA App
Does this increase benchmark scores at all? I know they don't mean anything but I think we can all agree, they're fun.
Also does this JUST manage memory or does it do other things as well?
Sent from my SCH-I500 using XDA Premium App
In my limited and completely amateur testing, there was no noticeable improvement in benchmarks... but I'm sure mileage will vary. You should seek out Zepplinrocks (the scripts writer) for a better answer.
I am sure this is a stupid question, but I'm a droid Newb. Is it nessicary to have the script manager app constantly running once you have already ran the script? Or is it good to go once I have exited it the last time? And after rooting, and running this script my weather widget keeps on saying i am in rockport il. And I'm not.... any suggestions?
When I click the Zip to download V6 on my phone it say "download unsuccessful"
And I have done these:
Requirements for V6_Supercharger:
1. Rooted Phone (Gingerbreak 1.20)
2. Script Manager (free on Market)
On certain boot settings such as CPU overclocking is it better to use on boot completed setting or the init.d script? Kinda confused on what the init.d script is any help would be nice..
Using ziggys new kernel and running androtech 3d rc2..
Sent from my Nocturnal 3D using XDA App
Say what?
And using system tuner pro if you overclock and don't use the set on boot option this will revert the settings to whatever they were from the kernal you flashed if you reboot your phone, however if you use the set on boot option then it will set the CPU to your settings when you boot up,
I believe when you check the force all cpus online is when system tuner adds a file to int.d folder to enable the second core,
From my understanding the stuff in int.d folder can be deleted without problems if you know what your doing.
I currently run my CPU at
1.18ghz max.
.3 ghz min.
With out the second core on, and set on boot is checked, I don't use the boot script or the faster app booting options,
Why fix something that ain't broke, it works great.
Shot from my shooter in 3D
injected with cleanrom2.7
elimon91 said:
On certain boot settings such as CPU overclocking is it better to use on boot completed setting or the init.d script? Kinda confused on what the init.d script is any help would be nice..
Using ziggys new kernel and running androtech 3d rc2..
Sent from my Nocturnal 3D using XDA App
Click to expand...
Click to collapse
technical details:
on boot completed is essentially a java function. the android system, after boot has been completed sends a system wide broadcast and any java application which has registered to listen for this broadcast can take action once the broadcast is given. this broadcast is probably the very last step in the complete system booting process.
the init.d script is done more at the linux level. it is usually called and trigger by the init.rc file. essentially, init.d is trigger during the hand off from ramdisk of the kernel to the android operating system.
init.d will technically execute before boot completed signal is sent so it will run first of the two methods.
boot completed will continue to work as long as the java application is installed
init.d will continue to work as long as the kernel supports it and the specific file is present under the init.d directory.
hope that helps!
joeykrim said:
technical details:
on boot completed is essentially a java function. the android system, after boot has been completed sends a system wide broadcast and any java application which has registered to listen for this broadcast can take action once the broadcast is given. this broadcast is probably the very last step in the complete system booting process.
the init.d script is done more at the linux level. it is usually called and trigger by the init.rc file. essentially, init.d is trigger during the hand off from ramdisk of the kernel to the android operating system.
init.d will technically execute before boot completed signal is sent so it will run first of the two methods.
boot completed will continue to work as long as the java application is installed
init.d will continue to work as long as the kernel supports it and the specific file is present under the init.d directory.
hope that helps!
Click to expand...
Click to collapse
Thanks for very usefull information, I use init.d
Well, the time has come that I think my kernel is ready for public consumption.
THIS IS ONLY FOR THE USA VERSION OF THE GALAXY PLAYER 5.0 (YP-G70). If you have a mechanical home button instead of capacitive buttons at the bottom, do not flash this (rumirand has a kernel for you)! If you have a 4.0, do not flash this (SteveS has a kernel for you)!
Read the first three posts of this thread COMPLETELY before asking questions - if you ask a question that is answered in the first three posts, you WILL be flamed.
I'm continuing my Daily Driver name, even though it isn't as good of a name as it used to be. It is my daily driver - but what kernel dev doesn't use their own kernel as a daily driver? It made more sense in the Infuse days when I was running my own unreleased kernel for months and a few people asked for it. Oh well, I'm lazy - same name for now.
This is going to be maintained in the same manner and spirit as my other Daily Driver releases for the Samsung Infuse and Samsung SGH-I777 (AT&T Galaxy S II) - http://forum.xda-developers.com/showthread.php?t=1212795 and http://forum.xda-developers.com/showthread.php?t=1289460
It is built from sources at https://github.com/Entropy512/linux_kernel_galaxyplayer and initramfs at https://github.com/Entropy512/initramfs_yp-g70
Current features:
coolbho3k's Samsung Sleep of Death patch - allows stable use of screen-off profiles with limits below 800 MHz in SetCPU
netarchy's conservative governor tuning patch - Reduces the polling interval, allowing conservative to ramp up/down faster. Over in I9100 land they're calling this "lionheart" and it's all the rage. (It makes me sad when people won't accept a governor until it's renamed and hyped up way beyond what it is...) As an example, a GSII would take 0.4 seconds to ramp from 200 to 1200 MHz with the default conservative governor, it can go all the way in 0.1 second with this patch.
conservative set to default governor - use SetCPU or a similar app to change it
jhash3
TinyRCU
CIFS and Tunneling modules included
ext4 partition mounting support in kernel and initramfs thanks to rumirand - ghetto Lagfix baby!
CWM 5.0.2.7 based recovery - Mostly tested, seems working, but may have a few bugs still to work out, rumirand helped a lot on this one
Insecure kernel - gives you automatic root in ADB shells
Per-file fsync() disable capability - see "dangerous features" documentation below
Standard bootanimation (/system/media/bootanimation.zip) support
Charginghacks - faster charging at low battery, slightly slower near the end, overall faster charging while trying to minimize battery stress
CPU core voltage control - use SetCPU or a similar app
CPU overclock to 1.2 GHz - use SetCPU or a similar app
Planned features, short-term:
Pull a few other bugfix commits from my other kernels
Clean up CWM implementation
Planned features, mid-term:
Proper Voodoo Lagfix support (Automatic partition conversion instead of manual)
Planned features, long-term:
Overclock beyond 1.2 if people prove they can handle 1.2 with maturity (Infuse community couldn't handle any OC in a responsible manner...)
Features not planned:
Anything that has a high risk of trading off stability for performance, unless it can be completely disabled by default
Alternative governors - They almost always cause wacky behavior in some cases, and they don't offer anything that can't be done with a combo of SetCPU profiles and tuning the conservative governor now that the minimum poll rate has been dropped.
How to flash .tar releases:
Linux/MacOS:
I forgot that Heimdall doesn't like this particular device - you will need to use a Windows virtual machine with USB passthrough support (like VirtualBox) and Odin, or root the device using the zergRush exploit and follow the "rooted device" instructions. (Ambrice has a fixed version of heimdall, but it must be compiled from source. If you know how to do that you don't need tips on how to use it. )
Windows:
Enter download mode - Power off your device completely, hold VolDn, and insert the USB cable
Use Odin - Google it or search these forums for details - try AdamOutler's resurrector thread in this Development forum
Any rooted device:
Extract the zImage from the .tar file of the release. On Linux, it can be the following (which should work in an ADB or Terminal Emulator shell on the Player itself.)
Code:
tar xvf <releasefile>.tar
From a shell with root access (ADB or Terminal Emulator), do the following:
Code:
dd if=zImage of=/dev/block/mmcblk0p11
How to flash .zip releases:
Put it on your sdcard, enter CWM, flash the .zip using CWM
If you do not have CWM, install an older .tar release then flash, or follow the "Any rooted device" instructions above, but extract the zImage from the .zip instead of a .tar
3/5/2012 Release:
Overclocking to 1.2 GHz (use SetCPU or a similar app to enable)
Support for running scripts in /system/etc/init.d
3/3/2012 Release:
Voltage control (no overclock yet, coming next)
1/29/2012 Release:
charginghacks from Infuse: Charging current on a wall adapter raised to 800 mA at lower battery, dropping to 700, then 600 (stock), then 550 (slightly below stock) as battery voltage reaches maximum. This gives overall lower charge times while trying to not stress the battery too much.
Also, final charge termination happens earlier - while this results in slightly less battery capacity per charge, it will help the battery retain capacity over time.
1/23/2012 Release:
Initramfs: Standard bootanimation support. Place a standard bootanimation in /system/media/bootanimation.zip - Note: The "stock" bootup sound still plays.
1/22/2012 Release:
A few bugfixes and power management improvements pulled in from other kernels
Ability to disable per-file fsync() - good for benchmark epeen, potentially dangerous for your data
1/14/2011 Release:
Initial release
FAQ
Q: Why does CWM default to my external SD card for backup/restore/flashing ZIPs?
A: This is the standard for Android devices going forward - internal on /emmc and external on /sdcard
Q: How do I enter CWM?
A: Until ROMs come out that have extended power menu mods: Power off your device, then:
Hold VolUp
Hold Power
Release Power when the SAMSUNG screen appears (continue holding VolUp)
Release VolUp when CWM appears
Q: I'm still not rooted?
As stated in the features, an insecure kernel only provides root in an ADB shell. Either use ADB to push /system/bin/su and /system/app/Superuser.apk and chmod them to the correct permissions, or take the easy way out and flash ChainsDD's Superuser package in CWM - http://androidsu.com/superuser/
Q: I used ROM Manager to do something, and something weird happened/went wrong. Why?
A: ROM Manager has not worked properly on any device I have ever owned. It softbricked any Infuse that had Voodoo Lagfix enabled, and never works properly on the SGH-I777. The only thing I've ever seen it do right was install gapps on CM7 on the I777.
Q: My battery will never charge past 80%, why?
A: The way Samsung estimates state of charge on our devices is extremely primitive and, in general, poor. Instead of a dedicated fuel gauge IC, they have tried to estimate battery directly from voltage with some funky compensation offsets depending on current operating state - the offset for wall charging is so high that it is impossible for the battery to read higher than 80% when on a wall charger unless you're putting the device under heavy load to activate some of the other compensation offsets. Sometimes it seems like the compensation code doesn't "kick in" when plugging in a charger, allowing you to see a higher number, other times it'll get "stuck on" even after removing the charger. The general thing, though, is that any percentage estimates of battery state are WILDLY inaccurate.
Q: Can you implement Voodoo Sound?
A: No - We have the same audio chip as the Galaxy S2 and Galaxy Note (Yamaha MC1N2) - Voodoo Sound requires a Wolfson WM8994.
Documentation on "dangerous" features:
Per-File fsync() disable:
This allows you to disable per-file write forced syncs. (e.g. if an app tries to force a write straight to disk, it'll just go to cache). This achieves the same goal as the modded sqlite hacks seen in tweaks such as USAS, however it can be disabled at runtime.
WARNING: THIS CAN CAUSE DATA LOSS OR CORRUPTION IN A CRASH
To enable, do the following in a terminal, or add it to an init.d script (look at my ondemand script as an example):
Code:
echo "1" > /sys/module/sync/parameters/fsync_disabled
And to disable (return to the default):
Code:
echo "0" > /sys/module/sync/parameters/fsync_disabled
Good for around 200 points of epeen in the database benchmarks in Antutu or 500-600 points of epeen in Quadrant. Real-world benefit: Probably not worth the data integrity risk, but you've got a choice now.
*reserved for whatever the heck I forgot above*
Thanks a ton Entropy512!! Been waiting for this.
Going to have to buy you a six pack via the Donate button!
Congrats Entropy512. I'm really thankful for your cooperation.
Its finally here!! Thanks so much entropy
Nice job entropy! Good to see that there is at least some development going on for these devices. This makes me wish I got a 5.0 instead..but I'm stuck with a 4.0.
Sent from my YP-G1 using Tapatalk
Thank You
I myself along with others appreciate you developing for the Galaxy Player 5.0 it is a great music player and it falls in the Galaxy family its a good device
Sent from my Galaxy Nexus using Xparent Blue Tapatalk
Says we can use Odin...do see put this in a phone or pda slot
Zei said:
Says we can use Odin...do see put this in a phone or pda slot
Click to expand...
Click to collapse
PDA - only modems go in phone I believe.
Just like flashing any other kernel in Odin.
Edit: CRAP I have Heimdall instructions but Heimdall won't work on the Player... I'm so habitually used to Heimdalling...
Would a factory stock image + root + this be good enough to post if done w/ the backup/restore feature?
Zei said:
Says we can use Odin...do see put this in a phone or pda slot
Click to expand...
Click to collapse
Yes when you use odin you will need to put the rom in PDA slot.If yiu use heimdall you will need to extract and flash the files separatly.
I hope this helps.
---------- Post added at 11:53 AM ---------- Previous post was at 11:53 AM ----------
Entropy512 said:
PDA - only modems go in phone I believe.
Just like flashing any other kernel in Odin.
Edit: CRAP I have Heimdall instructions but Heimdall won't work on the Player... I'm so habitually used to Heimdalling...
Click to expand...
Click to collapse
Heimdall does work on the player. I use it.
Hmm... odd, I tried to use it and it gave me some odd errors I've never seen before (I forget what at the moment) and then put me into forced download mode. I know a pit-dump has some rather odd looking results. Maybe if I just try and flash a kernel it will work.
I'll try again later today, and edit the instructions if it works.
I have my Player shut off for most of today - I've been having strange battery drain problems on my GSII for the past week or so, only when at home - and it seems like it started when I got the Player. So I'm shutting it off to see if it actually is affecting my phone.
Edit: Heimdall still isn't working for me
Code:
Heimdall v1.3.1, Copyright (c) 2010-2011, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
Claiming interface...
Attempt failed. Detaching driver...
Claiming interface again...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
100%
ERROR: Failed to confirm end of file transfer sequence!
KERNEL upload failed!
Ending session...
Rebooting device...
Re-attaching kernel driver...
After I flashed your kernel it won't let me connect to the market, my Wi-Fi is turned on and I connect to the browser just fine but not the market, help?
That's strange - no problems with market connections here. (Edit: Just updated BetterBatteryStats...)
Try rebooting?
Or wait a bit - sometimes the Market just goes down.
Entropy512, I've been studying your github and how you enable ext4 support in the kernel. Could you explain how you did it? I know it has to do with editing "/ arch / arm / configs / yp_g70_usa_defconfig" but I can't find that file in samsung's source or on Steve'S github. And after you do that you just edit the mount points in init.rc, right? I'm asking because I'm gonna try to get ext4 (lagifx) for my 4.0!
Thanks.
P.S. sorry if I'm a noob
klin1344 said:
Entropy512, I've been studying your github and how you enable ext4 support in the kernel. Could you explain how you did it? I know it has to do with editing "/ arch / arm / configs / yp_g70_usa_defconfig" but I can't find that file in samsung's source or on Steve'S github. And after you do that you just edit the mount points in init.rc, right? I'm asking because I'm gonna try to get ext4 (lagifx) for my 4.0!
Thanks.
P.S. sorry if I'm a noob
Click to expand...
Click to collapse
yp_g70_usa_defconfig was copied from venturi_usa_defconfig prior to modifying it - I decided to start maintaining my own defconfig rather than overwriting the original one.
Galaxy Player 4.0 is palladio instead of venturi. SteveS also uses a renamed defconfig though - something like steves_blahblahblah_defconfig
To change things for a 4.0, it would be something like
Code:
make steves_blahblahblahwhateverthisis_defconfig
make menuconfig (enable ext4 support in the menus here)
cp .config arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git add arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git commit
Entropy512 said:
yp_g70_usa_defconfig was copied from venturi_usa_defconfig prior to modifying it - I decided to start maintaining my own defconfig rather than overwriting the original one.
Galaxy Player 4.0 is palladio instead of venturi. SteveS also uses a renamed defconfig though - something like steves_blahblahblah_defconfig
To change things for a 4.0, it would be something like
Code:
make steves_blahblahblahwhateverthisis_defconfig
make menuconfig (enable ext4 support in the menus here)
cp .config arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git add arch/arm/configs/steves_blahblahblahwhateverthisis_defconfig
git commit
Click to expand...
Click to collapse
Cool thanks! Will definitely try it out.
This thread Is a compilation of speed tweaks and mods I have gathered from the forums and used on my Galaxy Player 4.0. I can vouch for all of these tweaks, and all provide at least a modest performance improvement. I claim no credit for any of these mods, the glory goes to the fabulous devs who have created them.
To show you the possible performance increase, I have all of these tweaks installed with the Terrasilent kernel and Klin's R5 ROM, plus an Overclock to 1.5 GHZ, and I have scored over 2750 in Quadrant, as indicated in the screenshot below.
If you have any potential tweaks or suggestions, PM me, and I will check them out!
Note to devs: I believe I have posted this in the right section, as this does not 100% pertain to development.
Now, let's get cracking!
Tweak No. 1: convert RFS filesystem to EXT4.
RFS has been tweaked since it debuted on the galaxy S over two years ago, but still is not quite up to par with today's standards.
Steps:
1. Flash the Terrasilent kernel/ Klin's R3 (basically a kernel with Clockwork recovery 5+ on it)
2. Make a nandroid backup (make sure you have enough free space!)
3.after you reboot, navigate using a file explorer on the Gplayer to the recovery directory and rename all files (excluding boot.img) from .rfs.tar to .ext4.tar.
4. Open up nandroid.md5 and change all filenames (again, excluding boot.img) from .rfs.tar to .ext4.tar
5.Save that, reboot into recovery, perform a full restore, and reboot into download mode.
6. reflash the kernel you were using, and you are done!
The performance improvement is amazing, and I would recommend using this tweak to anyone, since it's safe, and provides a huge boost!
Tweak no.2: Universal Adrenaline shot.
This is an amazing tweak that has provided the biggest improvement for me. It should be pretty risk-free if you follow my directions. Do NOT try to unzip and manually install, as you will have to reflash you rom (bootloop). Additionally, you will have to reinstall any init.d tweaks you have currently, as this script wants to ensure no conflictions, and deletes them all
Steps:
1. Head to this link, read, and download Adrenaline shot v14 (don't worry, our device can handle the two risky tweaks).
2. Boot into recovery, and flash!
3. After flashing, I would optionally format /cache. After reboot, you should see a drastic performance increase!
Tweak no.3: EXT4 Journalism tweaks.
EXT4 is much faster than RFS, but on our Players, the lag is still noticeable, just navigating around the UI.
WARNING:This provides a nice speed increase, especially to large games, but if you have an unclean shutdown, or force restart your Gplayer, YOU WILL HAVE TO RESTORE!
Dire warnings said, This actually increases the smoothness of the Gplayer a decent amount, although for me the risk far outweighs the benefit.
Your partitions are as follows:
System: STL9
Data: mmcblk0p2
Dbdata: stl10
cache (use this partition if you want to test):stl11
Remember, you need su permissions for all of this!
Instructions:
1.First, FSCK the partitions (make sure you answer no to all but the first questions, as that could lead to file corruption! the errors are generated when the partition is accessed during the FSCK, which generates an error, since data is in a different section than it was before. Don't worry, most/all of those errors are flukes. The instruction is: e2fsck -f /dev/block/(partition name)
2. Disable journalism with tune2fs: tune2fs -O ^has_journal /dev/block/(partition name)
Note: tune2fs will not have the capabilities necessary unless you install the one from the one shot adrenaline tweak above.
3.reboot and enjoy!
If you want to reverse this, you will have to restore a nandroid backup, as CWM formats EXT4 with journalism, and a format is required to reset it. On the same note, you will have to reapply this tweak every time you restore a nandroid backup, just something to keep in mind.
Tweak no.4: Supercharge, and apply Loopy smoothness!
I am sure everyone knows about the ubiquitous v6 supercharger script out there, and it provides a big performane increase! Also, Loopy smoothness helps a lot in stabilizing launcher performance, and I view them to be equally valuable.
1. Visit here to download the latest supercharger script, and here to download T2 of loopy smoothness.
2. Launch the supercharger from the /sdcard/download directory, go throught the basic instructions, and the custoomize, reboot, and install nitro lag nullifier. Optionally install for easier access. I would also explore some of the other options especially reindexing.
3. move the loopy smoothness script into the init.d directory, open it, and remove the quotation marks around the launcher name if you are using the touchwiz launcher, or delete the quotations and name and add your launcher's process name (run ps in terminal emulator and find the most likely name, or look it up).
That's it! you should notice a definite performance increase, especially improvements in multitasking thanks to v6 supercharger. The launcher should also be a lot smoother.
Bonus (I have it in R5 rom, but have not actually applied it)
head here, download the latest script, and run it. It should add some extra build.prop tweaks that will greatly boost performance!
Some final suggestions:
1. Move to a custom launcher.
Using touchwiz, I always had about 125+- ram free after using a taskiller, but when I moved to go launcher EX (imho, the best launcher for the gplayer out there, beautiful, not hard on resources, and very customizable), I had over 160+ free after using a taskiller, which resulted in far smoother operation, and excellent multitasking!
2. use ondemand or ondemandx.
All the Gplayer profiles are good, but ondemand, although not the best at power saving, provides the best performance on our aging system, and gives a little extra juice when you need it.
3. use the deadline governor.
None of the other I/O governors come even close to NOOP and Deadline, but deadline is better for everyday use, and noop is better if you have several file transfers occurring at once (eg. hooked up to a computer, updating apps, and browsing the web). It comes down to your usage style, but I prefer Deadline.
4. Disable uneeded /system/app apps.
Fortunately our Gplayer is pretty bloat free, but you can disable more apps if you want. You should rename them to .apk1 instead of deleting them, just in case. Do not delete phone.apk, because for some reason it breaks the default camera app ( you can delete it if you don't use it).
Open up a terminal, run the ps command, and disable any system, apps you recognise in the list (una, fota, etc.).
Beta: Format sdcard as ext2
I had limited success with this mod, and it is definitely worth hassle of converting to ext2. Unfortunately, you must have an init.d script that runs at boot, and there will be the occaisonal permissipn issue, but chmoding the sdcard fixes that.
Steps:
1. Backup all of your /sdcard data
2.connect the gplayer to a linux computer in mtp mode.
3. Open a terminal, and type:
sudo umount /dev/sdx
sudo mkfs.ext2 /dev/sdx
4. Disconnect it from the computer. It will output an error when the media scanner runs, this is okay.
5. Create an init.d script with the following info:
#!/system/bin/sh
mount rw /dev/block/vold/179:1 /mnt/sdcard
chmod 777 /mnt/sdcard
chmod 777 /mnt/sdcard/*
chmod 777 /mnt/sdcard/Android
chmod 777 /mnt/sdcard/Android/*
6. Reboot, and restore your data.
That should be it! I used ext2 because i got permission errors with ext3/4 constantly, and ext2 was stable. The performance improvement is amazing, especially with apps that store data to /sdcard. My performance is at least doubled! Even thouh this is beta, I STRONGLY recommend doing this, as the performance is incredible (as I said)!
Note: after doing this, windows machines will not recognize the player, you will have to do all file transfers via linux.
Note: of app data is not recognized after restore, delete and redownload, after backing up the save file/s. At the moment, it is the only way I have to fix it.
Enjoy the speed!
Dalvik machine: the ULTIMATE speed booster.
I was poking around lately, and I discovered that dalvik settings are really far more powerful than most people give them credit for. Using them on an (unreleased) version of EtherealRom gave me a nice speed increase!
All of these can be added/edited in build.prop, if you so choose, under the variable "dalvik.vm.dexopt-flags=".
The most important one is u=y. This indicates that you want all VM code to be optimized for a single core, and provides a NICE speed boost. The next most important is o=a, as that indicates that you want it to optimize ALL the code, instead of selective batches.
I will update this later, I am exhausted right now, and need some sleep.
I now have my own custom rom that you can flash, that includes most of these amazing features (no ext converting, that has to be manual), plus some more! Note: this rom is ONLY for the 4.0. you will have to restore if you flash it onto the 5.0!
Download
That's it! I will certainly add on as time progresses, but at the moment that is all I can remember/know about, so be sure to pm me with potential tweaks so I can put it up here!
hanthesolo said:
This thread Is a compilation of speed tweaks and mods I have gathered from the forums and used on my Galaxy Player 4.0. I can vouch for all of these tweaks, and all provide at least a modest performance improvement. I claim no credit for any of these mods, the glory goes to the fabulous devs who have created them.
To show you the possible performance increase, I have all of these tweaks installed with the Terrasilent kernel and Klin's R5 ROM, plus an Overclock to 1.5 GHZ, and I have scored over 2750 in Quadrant. If you don't believe me, I will put up a screenshot, as I don't have screen capturing software on my Gplayer right now, and it's too much of a hassle.
If you have any potential tweaks or suggestions, PM me, and I will check them out!
Note to devs: I believe I have posted this in the right section, as this does not 100% pertain to development.
Now, let's get cracking!
Tweak No. 1: convert RFS filesystem to EXT4.
RFS has been tweaked since it debuted on the galaxy S over two years ago, but still is not quite up to par with today's standards.
Steps:
1. Flash the Terrasilent kernel/ Klin's R3 (basically a kernel with Clockwork recovery 5+ on it)
2. Make a nandroid backup (make sure you have enough free space!)
3.after you reboot, navigate using a file explorer on the Gplayer to the recovery directory and rename all files (excluding boot.img) from .rfs.tar to .ext4.tar.
4. Open up nandroid.md5 and change all filenames (again, excluding boot.img) from .rfs.tar to .ext4.tar
5.Save that, reboot into recovery, perform a full restore, and you are done!
Note: after converting, my /data partition is deleted/not recognized when booting into recovery on the terrasilent kernel. I think this may be an isolated incident, but you have been warned!
Tweak no.2: Universal Adrenaline shot.
This is an amazing tweak that has provided the biggest improvement for me. It should be pretty risk-free if you follow my directions. Do NOT try to unzip and manually install, as you will have to reflash you rom (bootloop). Additionally, you will have to reinstall any init.d tweaks you have currently, as this script wants to ensure no conflictions.
Steps:
1. Head to this link, read, and download Adrenaline shot v14 (don't worry, our device can handle the two risky tweaks).
2. Boot into recovery, and flash!
3. After flashing, I would optionally format /cache. After reboot, you should see a drastic performance increase!
Tweak no.3: EXT4 Journalism tweaks.
EXT4 is much faster than RFS, but on our Players, the lag is still noticeable, just navigating around the UI.
WARNING:This provides a nice speed increase, especially to large games, but if you have an unclean shutdown, force restart your Gplayer, YOU WILL HAVE TO RESTORE!
Dire warnings said, This actually increases the smoothness of the Gplayer a decent amount, although for me the risk far outweighs the benefit.
Your partitions are as follows:
System: STL9
Data: mmcblk0p2
Dbdata: stl10
cache (use this partition iuf you want to test):stl11
Remember, you need su permissions for all of this!
Instructions:
1.First, FSCK the partitions (make sure you answer no to all but the first questions, as that could lead to file corruption! the errors are generated when the partition is accessed during the FSCK, which generates an error, since data is in a different section than it was before. Don't worry, most/all of those errors are flukes. The instruction is: e2fsck -f /dev/block/(partition name)
2. Disable journalism with tune2fs: tune2fs -O ^has_journal /dev/block/(partition name)
Note: tune2fs will not have the capabilities necessary unless you install the one from the one shot adrenaline tweak above.
3.reboot and enjoy!
If you want to reverse this, you will have to restore a nandroid backup, as CWM formats EXT4 with journalism, and a format is required to reset it. On the same note, you will have to reapply this tweak every time you restore a nandroid backup, just something to keep in mind.
Tweak no.4: Supercharge, and apply Loopy smoothness!
I am sure everyone knows about the ubiquitous v6 supercharger script out there, and it provides a big performane increase! Also, Loopy smoothness helps a lot in stabilizing launcher performance, and I view them to be equally valuable.
1. Visit here to download the latest supercharger script, and here to download T2 of loopy smoothness.
2. Launch the supercharger from the /sdcard/download directory, go throught the basic instructions, and the custoomize, reboot, and install nitro lag nullifier. Optionally install for easier access. I would also explore some of the other options especially reindexing.
3. move the loopy smoothness script into the init.d directory, open it, and remove the comments around the launcher name if you are using the touchwiz launcher, or delete comments and name and add your launcher's process name (run ps in terminal emulator and find the most likely name, or look it up).
That's it! you should notice a definite performance increase, especially improvements in multitasking thanks to v6 supercharger. The launcher should also be a lot smoother.
Bonus (I have it in R5 rom, but have not actually applied it)
head here, download the latest script, and run it. It should add some extra build.prop tweaks that will greatly boost performance!
Some final suggestions:
1. Move to a custom launcher.
Using touchwiz, I always had about 125+- ram free after using a taskiller, but when I moved to go launcher EX (imho, the best launcher for the gplayer out there, beautiful, not hard on resources, and very customizable), I had over 160+ free after using a taskiller, which resulted in far smoother operation, and excellent multitasking!
2. use ondemand or ondemandx.
All the Gplayer profiles are good, but ondemand, although not the best at power saving, provides the best performance on our aging system, and gives a little extra juice when you need it.
3. use the deadline governor.
None of the other I/O governors come even close to NOOP and Deadline, but deadline is better for everyday use, and noop is better if you have several file transfers occurring at once (eg. hooked up to a computer, updating apps, and browsing the web). It comes down to your usage style, but I prefer Deadline.
4. Disable uneeded /system/app apps.
Fortunately our Gplayer is pretty bloat free, but you can disable more apps if you want. You should rename them to .apk1 instead of deleting them, just in case. Do not delete phone.apk, because for some reason it breaks the default camera app ( you can delete it if you don't use it).
Open up a terminal, run the ps command, and disable any system, apps you recognise in the list (una, fota, etc.).
That's it! I will certainly add on as time progresses, but at the moment that is all I can remember/know about, so be sure to pm me with potential tweaks so I can put it up here!
Click to expand...
Click to collapse
Very nice thread! I'll try it once my device finishes charging. How did you manage to get 1.5 OC?
Thanks! you can tell I am more than a little OCD about my device's performance
I was able to achieve a stable OC by setting the internal voltage to 1.19V, and my core voltage to 1.4V, using Tegrak Overclock. This gives a nice increase to the performance of my player!
hanthesolo said:
Thanks! you can tell I am more than a little OCD about my device's performance
I was able to achieve a stable OC by setting the internal voltage to 1.19V, and my core voltage to 1.4V, using Tegrak Overclock. This gives a nice increase to the performance of my player!
Click to expand...
Click to collapse
I'm not really familiar with OC at all but you just change the voltage and the 1.5 OC option will appear? Didin't you modify your kernel a bit to do this?
As I said in the OP, I have the Terrasilent kernel installed, which allows by default overclocking up to 1.2 GHZ. If you install Tegrak Overclock Ultimate, you can load it's module and overclock up to 2 GHZ with a max internal voltage of 1250mv, and a max core voltage ov 1400MV. Suprisingly easy, actually, and an invaluable tool. You can also change the I/O governor like I suggested from it as well. Attached is A screenshot of my quadrant score (I decided to do it anyway). The score is slightly lower than I said because I have Journalling disabled (to much of a hassle to keep restoring every day).
hanthesolo said:
As I said in the OP, I have the Terrasilent kernel installed, which allows by default overclocking up to 1.2 GHZ. If you install Tegrak Overclock Ultimate, you can load it's module and overclock up to 2 GHZ with a max internal voltage of 1250mv, and a max core voltage ov 1400MV. Suprisingly easy, actually, and an invaluable tool. You can also change the I/O governor like I suggested from it as well. Attached is A screenshot of my quadrant score (I decided to do it anyway). The score is slightly lower than I said because I have Journalling disabled (to much of a hassle to keep restoring every day).
Click to expand...
Click to collapse
Oh ok you have tegrak ultimate. I had tegrak free and the limit was 1.3. Also for the journaling why don't you make a script to execute it at each boot?
Yeah, You can do some crazy stuff in the ultimate version!
I will upload the screenshot in the OP, the way I did it wouldn't work the first time
I didn't make journalism a init.d script because it is a one-time tweak, you apply it, and you have to reformat to go back! I also didn't spell out the instructions verbatim in case someone wants to selectively apply this tweak or use it as reference.
zaclimon said:
Oh ok you have tegrak ultimate. I had tegrak free and the limit was 1.3. Also for the journaling why don't you make a script to execute it at each boot?
Click to expand...
Click to collapse
Also, I have triesd to make an init.d script to disable journaling and putting tune2fs in /system/xbin, but it errors out because you can only disable journaling when the partitions aren't mounted. So what I did was copy tune2fs to a directory, boot into recovery, unmount all the partitions and then disable journaling.
Surprisingly my quadrant score jumped by 400 points.
Sent using Tapatalk
klin1344 said:
Also, I have triesd to make an init.d script to disable journaling and putting tune2fs in /system/xbin, but it errors out because you can only disable journaling when the partitions aren't mounted. So what I did was copy tune2fs to a directory, boot into recovery, unmount all the partitions and then disable journaling.
Surprisingly my quadrant score jumped by 400 points.
Sent using Tapatalk
Click to expand...
Click to collapse
I was able to do it (albeit with warnings during e2fsck) using merely the terminal emulator, and after fixing permissions on tune2fs (I manually placed it). I checked it with tune2fs -l /dev/block/(partition) | grep features, and it claimed that I removed the has_journalism flag. Plus, I got the wonderful benefit of corruption after an unclean shutdown.
Is Rom compatibile with SGP 5.0(International) if not can you please pm me some advice about how to port it on SGP 5.0 ?
Unfortunately, This rom is based soly on the SGP 4.0, and would be very difficult to port onto the 5.0. I am currently working on a flashable zip file that contains most of these tweaks, so you won't have to use the rom.
Ok thanks mate , i try two tweaks and its amazing....its awesome feeling when onecore processor 1.5Ghz defeat dualcore Tegra 2
Which two did you try?
what score did you get?
It DOES feel pretty awesome to see quadrant shoot up past a tegra device
Sneak preview: me and Klin are working together on his next version of his rom, and it will have all of these tweaks, plus some extras (read: ext4 sdcard)!
One thing I am not certain about with the adreneline shot; do I need to manually delete my init.d scripts, or will flashing this delete them?
Sent using Tapatalk
The scipt will delete them for you when you flash, but it shouldn't cause any issues if they are not deleted. If some conflict, it may reduce the overall performance boost, but that's the worst that could happen.
hanthesolo said:
Which two did you try?
what score did you get?
It DOES feel pretty awesome to see quadrant shoot up past a tegra device
Sneak preview: me and Klin are working together on his next version of his rom, and it will have all of these tweaks, plus some extras (read: ext4 sdcard)!
Click to expand...
Click to collapse
I try Ext4 and Adrenaline and i get 2612 points I enjoy for flashable pack of tweaks Nice work mate and good luck with all your projects PS sorry for my bad english
Glad it works! I am almost done testing ext4 sdcard, and I will have the steps up here soon. Additionally, Klin will release an update to his ROM with my tweaks includded in the next couple of days, along with more than one new goody
I don't get how you get such a high io score! My io is around 800!? I installed the adreneline tweak, but nothing noticeable, perhaps even worse performance. I have ext4 (I think, since I installed klin's r5). I use deadline scheduler. I also use v6 supercharger. What are you people's quadrant score with just the adrenaline and supercharger? No overclock.
Sent using Tapatalk
Klin's R5 only formats /system as ext4. to get the full benefit (and the noticeable increase), do it on all partitions using the guide on the OP. I would also use noop, as it seems to be slightly faster than deadline on ext4. Once you do that, you should get the increase.
Well, I just tried to convert to ext4 following your instructions, but following the reboot, it has been on the solid "samsung" (not the pulsing one) screen for several minutes, is this normal, or did something bad happen?
[kernel][v3.5] leanKernel: minimalistic kernel (1/28/16)
leanKernel is not for everyone.
My philosophy is to keep the kernel footprint as small as possible by trimming as much fat as possible, and at the same time keeping it stable, power efficient, and fast. leanKernel is designed to be a drop in replacement for stock kernel, and so it tries not to deviate too far from stock.
You will find that it's lacking some of the bells and whistles of other custom kernels, so if you like features you came to the wrong thread.
Here's a longer post on what leanKernel is about.
Also folks, please read the FAQ before asking questions.
INSTRUCTIONS
If you like to stay as close to stock as possible: 1) Download and flash the normal leanKernel build here (find the latest zip file) in recovery. 2) Reboot and enjoy better performance and battery life (hopefully). That's it! There's no need to flash stock kernel first, or to wipe caches.
If you like to customize, read through the feature list below, the FAQ (post #2), the changelogs, and optionally the entire thread. Then you'll know what to do.
DOWNLOAD (flash in recovery)
v1.x is for Android 5.0, and v2.x is for Android 5.1
main download
mirror (may need to refresh browser to see latest)
PREREQUISITE
Unlocked bootloader, custom recovery installed
Push bullet channel: imoseyon
FEATURES
custom voltage control - use your favorite app
updated to latest 3.10 Linux
interactiveX - screen_off_maxfreq support (default 2.2Ghz)
sw crypto drivers updated (to use arm NEON instructions) for better encryption/decryption performance. Sequential 180MB/s reads, 60MB/s writes (using dd)
latest Linaro gcc 4.9 toolchain (optimized for a15 - thanks to Christopher83)
fat trimmed and various performance tweaks
f2fs support (updated to latest source from Samsung)
force encryption turned off (changed to encryptable)
overclocked to 2.9ghz (experimental - available as a separate build for now)
underclocked to 223mhz (experimental - available as a separate build for now)
Async Fsync
init.d support
cpu-boost control - enable/disable via lkconfig
lkconfig script for customizing leankernel (open terminal app, become superuser, then type "lkconfig" without quotes)
patched mpdecision to prevent changing min/max freq provided as flashable zip (in util directory)
color control (thanks to @savoca)
charging led support
a lot of unnecessary stuff removed from stock kernel
some components updated to Linux 3.18
random generation optimization including e/frandom support
pc/usb charging with boosted current ~300-400mA
some selinux fixes, selinux is enforced by default - staying true to stock (you can easily disable using lkconfig)
SLUB allocator updated to Linux 3.18
wake gesture control from flar2, modified for leankernel (also disabled in-call)
vibe strength control
much of the code is up to date with latest from CodeAurora
(mostly for devs) /sys/module/selinux/parameters/force_audit sysfs node to audit all/hidden selinux denies.
power aware cpu scheduling
faux sound enable/disable by sysfs (and lkconfig)
wakelock control (smb135x, wlan_rx, msm_hsic and sensor_ind)
leanKernel core control script
user option to prevent mpdecision/msm_thermal from changing min/max frequencies: frequency mitigation preventer
supports kexec for multirom
LKCONFIG
You can use lkconfig script to make custom changes to leanKernel (along with popular apps like Kernel Tweaker and Trickstermod). To run lkconfig, open terminal app, "su" (without quotes) to become superuser, enter, and then type "lkconfig" without quotes, then enter.
Code:
[email protected]:/ $ su
[email protected]:/ # lk
leanKernel configurator
---
0) display current settings
1) cpu frequency control
2) wake gesture control
3) wakelock control
4) charging led
5) rgb/picture control (advanced)
6) rgb/picture control (simple)
7) vibe strength
8) power saving mode for cpu scheduler
9) faux sound control
10) selinux mode
11) min/max freq change prevention
21) check top 10 wake locks (ie. wakeup sources)
please enter a number (or press enter to exit):
CHANGELOG
https://github.com/imoseyon/leanKernel-shamu/wiki/Marshmallow-ChangeLog
Thanks to @guitarshredder87, @Wera750, @akellar, and @grisha1 for testing test builds!
XDA:DevDB Information
Leankernel: Minimalistic Kernel, Kernel for the Nexus 6
Contributors
Imoseyon
Source Code: https://github.com/imoseyon/leanKernel-shamu
Kernel Special Features:
Version Information
Status: Stable
Created 2014-11-26
Last Updated 2016-01-31
FAQ
I'm having trouble waking the phone sometimes. Help!
We haven't really figured out exactly what's causing it - but there seems to be evidence that it's not limited just to leanKernel. One thing to try: if your ROM has a feature that prevents accidental wakeups, disable it!
I can't seem to get min and max freq to stick! What are these mpdecision zip files in the util directory?
* Read this post: http://forum.xda-developers.com/showpost.php?p=58135730&postcount=1474
* Short version: This is actually by design of mpdecision. If you want this behavior to change, I recommend that you 1) flash latest stable leankernel, 2) flash the custom no-freq mpdecision, and then 3) disable cpu-boost via lkconfig. Do not disable mpdecision if you go this route. Also, if you flash ROM, you must re-flash custom mpdecision. To go back to normal, flash the stock mpdecision file.. Launch lkconfig, choose core control, and choose one of the options in core control.
Will flashing leankernel decrypt my phone storage?
If you're already encrypted, then it will stay encrypted after flashing kernel, *until* you format data. Once you format you will stay decrypted until you decide to encrypt again (see below). If you're already decrypted, leanKernel will not force encrypt automatically.
What do I do to encrypt again?
There are several ways to do this. One way (easiest for me at least) is to adb in (or in terminal emulator):
Code:
[email protected]:/ # start encrypt
You will see the phone hot boot and once it comes up you will be encrypted again. Keep in mind that if you want to decrypt again you'll have to wipe.
How do I check the PVS BIN of my cpu?
Code:
[email protected]:/ # cat /proc/cpu/msm_acpu_pvs
The number you get should range between 0 and 15 (inclusive). If you ended up with 15 congratulations. If you ended up with 0, go get it exchanged! Stock frequency/voltage table: http://pastebin.com/ZyGA9Tec
Which kernel control app do you recommend?
When v1.0 gets released it should come with "lkconfig" for tweaking some of the options. Otherwise, I tried Trickster and KernelTweaker, and they both seem to work ok.
What are ondemandX and interactiveX?
ondemandX and interactiveX are very very close to "stock" ondemand and interactive governors, respectively. The only difference is screen_off_maxfreq sysfs support. This means that it gives you the ability to limit phone's max frequency when screen is off. This feature could be effective in reducing battery usage, especially if you have a misbehaving app (or two) that consume cpu cycles while screen is off. The default value is 2265600 - if you change the value to your top speed you're effectively disabling the feature and restoring stock behavior completely. You can use an app like Trickster or Kernel Tweaker to modify screen_off_maxfreq.
HELP! I messed up with lkconfig - how do I go back?
Do not fret. Flash lkconfig_cleaner.zip from the "util" directory.
(If you want to do this manually), reboot the phone into recovery, mount /data, and delete everything in /data/data/leankernel. Once things are back to normal, re-run lkconfig to re-do your settings.
What is cpu-boost?
Read this post: http://forum.xda-developers.com/showpost.php?p=57215289&postcount=535
What is the best RGB setting?
http://forum.xda-developers.com/showpost.php?p=57265483&postcount=620 (old)
http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017 (new)
What is power aware scheduling?
Read this post: http://forum.xda-developers.com/showpost.php?p=58313978&postcount=1651
I missed your kernel when I switched to N5. Glad to have you here
hmm.. a kernel. since its the first one posted here, im trying it out
Hell yeah. Ready to flash
Sent from my AOSP on Shamu using XDA Free mobile app
If I flash this it will decrypt right cool
digweed4me said:
If I flash this it will decrypt right cool
Click to expand...
Click to collapse
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
What app should we use to control? I remember you used to have your app right
holy **** Imoseyon. you made my Thunderbolt usable way back when. so glad to see you developing for the N6 now
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
Flashed it and yes decrypted thanks a lot
IMO!! Good to see ya again man. Can't wait to run your work again.
Appreciate it!
digweed4me said:
What app should we use to control? I remember you used to have your app right
Click to expand...
Click to collapse
You mean lkconfig? Yeah that's coming later (along with a whole lot more).. If you're talking about f2fs, you'd want to use custom recovery but TWRP for shamu doesn't support f2fs yet - i had to do everything manually.
Imoseyon said:
It should not decrypt if you're already encrypted, unless you re-format/wipe. But no guarantees.
Click to expand...
Click to collapse
i am still encrypted, and did not decrypt after flashing. so, all worked as it should.
Can we flash on stock ROM or is a custom ROM required?
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
I'm on a stock ROM.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
pathtologos said:
So let me see if I get this straight: I'm on stock, unlocked bootloader, rooted, and encrypted (as far as I know--I never decrypted), so if I flash this it won't decrypt my device? I was kinda hoping it would.
Secondly, I'm good to flash this with stock ROM? I'm hoping for a bit better battery life.
Thanks devs! I got a feeling development for our device is gonna be NUTS!!
You don't buy a Mustang for the gas mileage.
Click to expand...
Click to collapse
AFAIK, there's no way to decrypt without having to wipe unfortunately. Going the other way (unencrypted to encrypted) is super easy though, and no data loss.
nycdiplomat said:
Can we flash on stock ROM or is a custom ROM required?
Click to expand...
Click to collapse
im on rastapop, an aosp based custom rom.
simms22 said:
wipe before flashing, youll be decrypted. if you dont wipe, you stay encrpted.
Click to expand...
Click to collapse
Thanks for your quick response. Wipe what tho? Cache, dalvik, and what else? Hope you don't mean all my data.
You don't buy a Mustang for the gas mileage.