[GUIDE] Jay's Recipe for Buttery Goodness (cross-posted from AF) (REVISED! 10/10/12)

Search This thread

aidanbree

Senior Member
Apr 20, 2005
267
3
Been trying to get this working but with no luck.

Set everything back to normal and started again. When I set the boot options in system tuner I noticed that I got an unsupported or not rooted message.

I am running stock and rooted. I applied the kernel and RAM zips without issue. Super user shows that permission is being granted to the system tuner.

Any suggestions?

Sent from my Nexus 7 using xda app-developers app
 

Jay Aristide

Senior Member
Jun 27, 2011
996
894
49
Dyer, Tennessee
www.daede.com
Been trying to get this working but with no luck.

Set everything back to normal and started again. When I set the boot options in system tuner I noticed that I got an unsupported or not rooted message.

I am running stock and rooted. I applied the kernel and RAM zips without issue. Super user shows that permission is being granted to the system tuner.

Any suggestions?

Sent from my Nexus 7 using xda app-developers app

Yeah, use farmer's scripts and forget systun. It just does that to some people...
 

panic.exe

Senior Member
Feb 10, 2012
89
16
Frederick
Stuck on "8) Tap the CPU option and tap Boot Settings. For CPU and SD, set the method to init.d"

when i click cpu tap and click boot settings in not seeing a option to a set a "method" or anything i only see:

re-apply SD tweak
re-apply memory limits
re-apply cpu settings
re-apply SysCtl settings
and Force all CPUs online

when i click on either the re-apply SD tweak or re-apply cpu settings i have 2 options: "disabled" or "on boot completed"

im confused on what im supposed to do..

*EDIT* Found my issue.. the script wasn't working because my file explorer was uppercasing the i in the init.d folder name so i changed it from Init.d to init.d and all is well now :)
 
Last edited:
  • Like
Reactions: Jay Aristide

Jay Aristide

Senior Member
Jun 27, 2011
996
894
49
Dyer, Tennessee
www.daede.com
Stuck on "8) Tap the CPU option and tap Boot Settings. For CPU and SD, set the method to init.d"

when i click cpucreate and click boot settings in not seeing a option to a set a "method" or anything i only see:

re-apply SD tweak
re-apply memory limits
re-apply cpu settings
re-apply SysCtl settings
and Force all CPUs online

when i click on either the re-apply SD tweak or re-apply cpu settings i have 2 options: "disabled" or "on boot completed"

im confused on what im supposed to do..

You don't appear to have init.d support. To get init.d support you can flash the 1.0.5 kernel then immediately flash 1.1.1 (don't forget to create /system/etc/init.d and chmod it 0755) or flash a ROM that comes with init.d support (like Paranoid Android). Alternatively, you can just choose on boot completed in System tuner and continue without init.d support

Edit: glad you got it working :)
 

kevinngck1

Senior Member
Aug 4, 2011
381
45
i just apply these settings. After reboot, i checked only Cache Size"1024" not stick (reboot and back to 2046 automatically). How can i solve it??
 

NicholasQ

Senior Member
Oct 16, 2010
919
344
I tried using farmers scripts but they don't appear to run. Still got a ram disk size 0.

Sent from my Nexus 7 using xda app-developers app

I did everything jay listed in first post and things work. You must be missing a step. Check all file locations and make sure stuff is where it should be.

Sent from my Nexus 7 using xda premium
 

aidanbree

Senior Member
Apr 20, 2005
267
3
I did everything jay listed in first post and things work. You must be missing a step. Check all file locations and make sure stuff is where it should be.

Sent from my Nexus 7 using xda premium



Sent from my Nexus 7 using xda app-developers app

---------- Post added at 10:51 PM ---------- Previous post was at 10:50 PM ----------

I did everything jay listed in first post and things work. You must be missing a step. Check all file locations and make sure stuff is where it should be.

Sent from my Nexus 7 using xda premium

Actually, just tried again and worked...absolutely fantastic!

Sent from my Nexus 7 using xda app-developers app
 

Jay Aristide

Senior Member
Jun 27, 2011
996
894
49
Dyer, Tennessee
www.daede.com
I'm using Paranoid Android. Thanks man.

Just flash the _motley 1.1.1 kernel of your choice, reboot, use the file manager of your choice to create /data/local/userinit.d, set it's permissions to:

XXX
X-X
X-X

(rwxr-xr-x, or 0755)

then unzip farmerbb's scripts, put them in that folder, and give them the same permissions you gave the folder. No need for system tuner or anything else :) I recommend the 128mb script set, personally, but it all depends on how much multitasking you plan to do. Hit me up if you get stuck :)
 
  • Like
Reactions: TahrirSquare

daveleebond

Senior Member
Dec 14, 2009
75
4
using farmerbb's scripts in the userinit.d folder on the latest paranoid on N7.
Do the scripts alter voltages since the min one is still 800mv?
 

zedlor

Senior Member
May 1, 2012
135
24
North West UK
This has probably been asked and answered, but I can't find it, so I'm wondering if the 1.0.5 kernel is the 1.0.5b kernel which the first post mentions? Cheers.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 77
    IMPORTANT: If you updated your system to Android 4.1.2, *DO NOT* flash either _motley kernel, as they are built on 4.1.1 and contain the wrong interface to the power management chip. This will result in a bootloop at the least, and possibly much much worse

    What we're doing, here, is turning your n7 into a multitasking muscle-machine, and giving it the I/O throughput to match. These instructions are for the stock ROM, but can be applied to any ROM with a little modification. Enjoy!

    Do the OTA update to 4.1.1 (if you're stock and haven't, already), and then......

    [KERNEL][GPL][Linaro][OC 1.6GHz][UV][GPU+][ZRAM][SIO+V(R)] 2012-08-10 motley 1.1.1


    From that thread, you need:

    a) the 1.1.1 kernel of your choice
    b) the 1.0.5b kernel with ramdisk (if you're already running a custom ROM with init.d support, you don't need this, nor do you need to create /system/etc/init.d in a future step)

    You'll also need:

    a) root
    b) cwm
    c) busybox (absolute must, make sure your symlinks are proper)
    d) some type of root-enabled text editor (I use root explorer)
    e) a full featured cpu/sd management app (I use System Tuner)


    BEYOND THIS POINT, THERE BE DRAGONS. I'm not responsible if you FUBAR your device, but if you follow my instructions to the letter, you won't

    0.5) READ THIS ENTIRE POST BEFORE PROCEEDING

    1) install cwm and root your tab (if you haven't already)

    2) reboot into CWM, flash the 1.0.5b kernel with ramdisk (if you're on stock or a stock-based ROM without init.d support), then immediately flash the 1.1.1 kernel you chose (gpu overclocking is nice and all, but I haven't found a game that doesn't run perfectly with the stock GPU speed of 416MHz..Looks great on benchmarks, though)

    3) reboot back into JB, fire up root explorer, remount /system rw, create a folder in /system/etc called init.d (permissions rwxr-xr-x), create a file in it called S90zRAMandSpeedTweaks (permissions rwxrwxrwx), and long-press to open it in a text editor

    4) make it look like this:

    Code:
    #!/system/bin/sh
    
    #remount /data for faster i/o
    mount -o remount,noauto_da_alloc /data /data
    
    #disable fsync (controversial, I've been doing it for years with no real issues)
    echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
    
    #set zRAM size (recommended sizes are 64 and 128, as this compresses an actual block of RAM. Setting it higher will likely impede performance)
    echo $((1024*1024*128)) >  /sys/block/zram0/disksize
    
    #use busybox to create and activate zram0, if busybox is not in /system/xbin, modify accordingly
    /system/xbin/busybox mkswap /dev/block/zram0
    /system/xbin/busybox swapon /dev/block/zram0
    It's important to leave at least one trailing line in scripts. Just trust me, it's a linux thing.
    *NOTE* The above script does NOT check to see if it was successful, but if you copied it directly and installed busybox to /system/xbin then it will work. Once you reboot in a few minutes, you can check by using the command "busybox free" from a terminal emulator or adb shell

    5) Save the file, delete the .bak now in that folder, and close root explorer.

    6) Open System Tuner, tap on the SD option, change cache to 1024 and scheduler to deadline

    7) Tap the Voltage option and hit -25 4 times and save the settings as voltage_table_uv

    8) Tap the CPU option and tap Boot Settings. For CPU and SD, set the method to init.d

    9) Close System Tuner and reboot your device.

    10 Profit/consume butter

    It seems like a lot, but it really only takes about 15 minutes if you're a complete rooting n00b, and the end result is a buttery-smooth multitasking powerhouse (that blows iOS *away*). The 100mV undervolt also greatly extends battery life. I haven't had ANY issues at -100mV, but if you do, just increase it by hitting +25 on the voltage tab of System Tuner until you have something that works for you (in fact, you might want to start at -25mV and slowly grow it to -100mV, playing games and checking for instablity along the way)

    It's also worth mentioning that if you're currently completely stock, you will need to unlock your bootloader to root and install CWM, and unlocking the bootloader wipes your device (no way around it, unfortunately. Hook your N7 up to your computer and backup the entire contents of /storage/sdcard0 to make restoring your data as painless as possible)

    farmerbb's scripts - If you're having trouble getting your scripts to stick, or just don't want to be assed with installing System Tuner, use these! There are three different packages, for 64MB, 128MB, and 256MB zRam setups. Thanks, farmerbb!!

    ------- Revisions as of 9/1/12 -------

    Fixed first line of script so it will actually run
    Fixed zRam settings, as zRam is a block of actual RAM, not written to storage
    Removed JRummy busybox installer as recommended. Use whichever you like, just make sure your symlinks are good :)
    5
    Gotcha. I've got to say...it's amazing what you can do in Android with the help of the XDA community. You guys are awesome.

    Thanks, man. It should be pretty obvious by now that I'm learning as much as you guys are as I go, here. My helpful nature insists on a 'pay it forward' mentality, so as I learn something, I do my best to educate others, as well :)

    Now, to go see if the new Dr. Who is available anywhere, yet.. TTYL & never stop learning!
    5
    If anyone's still having trouble getting this to work, here's some premade script packages, with differing zRAM values. The number in the filename of each zip gives you that many megabytes of zRAM. The "0MB" package completely disables zRAM. 64MB and 128MB are the values that are recommended by Jay. The 256MB version is great if you're a heavy multitasker like me :)

    Extract these to /system/etc/init.d/ (if you're on a CyanogenMod-based ROM, it's better to use /data/local/userinit.d/). Set the permissions to rwxrwxrwx, and enjoy!
    4
    I'm sure this is a stupid question, bare with me I'm a noob. But since I'm running a CM based rom, I need to create a folder called userinit.d and put the scripts in there?

    Sent from my Nexus 7 using xda premium

    Normally what you'd do is install the script to the /system/etc/init.d/ folder. CyanogenMod ROMs also run init.d scripts from another place: the /data/local/userinit.d/ folder. This puts the script on your /data partition instead, so that when you upgrade to a new version of your ROM you don't have to put it on /system again (because /system is wiped whenever you update CM)
    3
    I'm out of thanks for the next few hours, so here's a ^5! Glad it's working well for you :)