Related
Genocide EC05 Kernel 2.0 |1.4GhzOC|UV|VoodooSound10|VoodooColor|DualBoot
(Compatible with DK28, EB13, and EC05)
I am NOT responsible for any damages, fires, race-wars, riots, temporary blindness, killer bee attacks, or anything else that could be remotely tied to downloading this file. You have been warned!
Features:
Dual Boot Support!
Overclockable (1400MHz, 1300MHz, 1200MHz, 1120MHZ)
Undervolt via sysfs
ROM MANAGER compatible!
Working redirector
Root and busybox built in
Voodoo Sound v10
Voodoo Color
Cifs and tun modules (not loaded by default)
MANY patches and tweaks
Much much more!!!
REQUIRED READING: IF YOU DO NOT READ ALL OF THIS THEN I WILL NOT PROVIDE SUPPORT FOR YOU UNTIL YOU DO!!!!
1. This kernel is capable of 1.3 & 1.4GHz however the voltage required slightly exceeds (roughly 50mV) the manufacturer's recommended voltage. Enable these AT YOUR OWN RISK.
2. Just because the kernel is capable of higher clock speeds DOES NOT mean every device will handle them.
3. DO NOT gripe or complain and trash my thread if you're device doesn't support anything past 1.2GHz. I WILL NOT increase the voltages anymore past recommended specifications.
4. DO NOT get mad or get your feelings hurt if I tell you to read the original post (OP) instead of answering your question. It means I have already answered it here OR I felt your question(s) needed to be answered in the OP and updated it accordingly.
5. DO a complete nandroid backup in ClockworkMod BEFORE flashing the kernel or messing with the undervolt settings. Setting values too low CAN cause data corruption. Simply restore your backup that I know you just made. YOU HAVE BEEN WARNED!
6. BY DEFAULT the ONLY active frequencies are 100MHz, 200MHz, 400MHz, 600MHz, 800MHz, and 1000MHz. In order for the device to use higher frequencies they must be specifically enabled. If you install the kernel you will NOT be automatically overclocked.
7. The kernel should work with any rom EXCEPT Stock EC05 that is converted to EXT4 AND is NOT deodexed. This is a known issue I am looking into.
8. PLEASE PLEASE PLEASE take time to read and search this thread before asking questions. I am not a baby sitter and I should not have to spend my time answering the same questions over and over and over again as it takes time away from me improving the kernel or working on my other projects. If you see some one ask a question that has already been answered please do not flame them. It would help me greatly if you could take 5 seconds to answer them or link them to the post with the appropriate answer.
NOTE: If you are going to overclock I personally recommend you UNINSTALL SetCPU and set your max with Voltage Control or by hand.
Installation:
Download the kernel and flash with ClockworkMod.
How to Dual Boot:
Information on dual booting can be found here: http://forum.xda-developers.com/showthread.php?p=15378860
Easy Overclock/Undervolt Method:
Setting up your frequencies:
Required software: Voltage Control by xan http://devphone.org/files/epic4g/kernels/VoltageControl_3.0.apk
1. Backup your device in ClockworkMod and flash the kernel. If you get messed up or confused just reboot your device to undo the changes.
2. After flashing the kernel, uninstall SetCPU and install Voltage Control (VC).
3. Open VC and hit 'States' at the bottom to open the States drawer.
4. Enable your desired frequencies and hit the menu button and 'Apply for now' (DO NOT 'Save as boot settings')
5. Hit 'States' to retract the States drawer.
6. Leave the Scheduler as 'cfq' and change Limit clock to your desired max frequency.
7. Hit the menu button and 'Apply for now' (DO NOT 'Save as boot settings' unless you are 110% sure the settings are stable and you have adequately tested)
Setting up your personal undervolt settings: (Caution: When figuring out your maximum undervolt settings there is a good chance you will get some data corruption so make sure your backup in ClockworkMod is up to date)
1. Open VC and select the desired frequency you wish to undervolt.
2. The green slider goes in increments of -25mV so select that first and take note of the frequency and value. (It is important when testing that you reduce the voltage ONE step at a time)
3. Hit the menu button and 'Apply for now'
4. Test the device's stability THOROUGHLY before you move the slider down any further. See the FAQ below for tips on testing stability.
5. If you feel it is stable then repeat this process and move the slider down one step, write it down, and THOROUGHLY test.
6. When your device freezes or starts acting weird then you know that value is too much and you should use your previously stable value.
Repeat this process for each of the other frequencies you wish to undervolt. When you feel you have the stable values that you are comfortable with, open VC and apply your stable values and THOROUGHLY test your device again. After you do all of this, make sure you are 110% certain of the stability before you 'Save as boot settings' and remember you may need to restore your ClockworkMod backup before setting up your final values to ensure no data corruption.
Advanced Overclock/Undervolt Method:
Required software: Working 'adb shell' or terminal emulator
There is NO hand holding here. Make sure you read the Easy Method to familiarize yourself with the process! If you don't know what you are doing then DO NOT attempt this method. If you get messed up or confused just reboot your device to undo the changes.
Enable active states: echo "0 0 1 1 1 1 1 1 1 1" > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
Accepted values are 0 and 1. All ten values must be set and this example enables 1200000 to 100000.
Set maximum frequency: echo "1200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
Accepted values are 1400000, 1300000, 1200000, 1120000, 1000000, 800000, 600000, 400000, 200000, and 100000.
Set minimum frequency: echo "200000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Accepted values are 1400000, 1300000, 1200000, 1120000, 1000000, 800000, 600000, 400000, 200000, and 100000.
Set undervolt values: echo "0 0 0 0 25 50 0 0 0 0" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
Values are in millivolts. Accepted values are 25, 50, 75, 100, 125, 150, 175, 200. DO NOT USE NEGATIVE NUMBERS. All ten values must be set.
This example applies a -25mV at 1000000 and -50mV undervolt at 800000.
To set your values on boot once you find what is stable creat a file name S_volt_scheduler with the following contents and change the values accordingly:
Code:
#!/system/bin/sh
#set UV
echo "0 0 0 0 25 50 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
#select enabled states
echo "0 0 1 1 1 1 1 1 1 1 " > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
#set scheduler for stl, bml and mmc
for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk*
do
echo "cfq" > $i/queue/scheduler
done
Put the file in /etc/init.d/ to apply the settings when the device boots.
FAQ (Frequently Asked Questions):
Q. Why isn't my device stable at higher clock speeds?
A. Many processors are cut at a time from one big wafer of silicon and other materials by the manufacturer. No two processors are exactly the same. From a cost stand point these chips are designed to yield a certain percentage of working chips at given specifications. These chips are made to withstand specific currents and voltages. When we exceed the currents and voltages the chips are designed to handle some will fail.
Q. What else can I try if I can't run the higher frequencies?
A. There is not a whole lot you can do. Some things I would suggest is make sure SetCPU is uninstalled. It has been reported SetCPU can cause some stability issues. Another option is to try different roms. Other than that there isn't much you can do. Sorry.
Q. Do you plan on pushing past 1.4GHz?
A. No. I do not plan to push any higher than 1.4GHz. Why? I am not going to push the higher voltages that would be required to go any higher. Please don't bother asking me to.
Q. What are some good ways to test stability while I am figuring out what undervolts my device can handle?
A. The best way to test stability is going to be setting your max frequency to the frequency you are testing and run benchmark programs like SmartBench that test multiple areas of your device. I recommend spending atleast 5-10 minutes running benchmarks and doing other tasks before you decide a given undervolt is stable.
Q. Help I was messing with the undervolts and now I get force closes (FC). What can I do?
A. This is why you made a backup in ClockworkMod. Setting voltage too low can corrupt your data and cause programs to FC. Typically you can reinstall the program or clear the applications data to fix it. As a last resort (and recommended to do anyway after you find your stable values) is to restore your backup from ClockworkMod.
Q. Why can't I use SetCPU?
A. You can use SetCPU, how ever I do not recommend it as it can cause conflicts. I am not going to support using it but if you get it working for you then by all means. I have no problems with the program or it's author and I think it is a great program but it just isn't needed and can make things tricky to get working correctly.
Q. How can I tell what frequencies I will benefit most undervolting or if they are even working?
A. There are two ways. The easy way is to install CPU Spy http://forum.xda-developers.com/showthread.php?t=1011497. The advanced way is to 'cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state'
Q. What are the default voltages for the avialable frequencies?
A. 1400000 @ 1375 mV WARNING: above recommended voltage
1300000 @ 1325 mV WARNING: above recommended voltage
1200000 @ 1300 mV
1120000 @ 1300 mV
1000000 @ 1275 mV
800000 @ 1200 mV
600000 @ 1175 mV
400000 @ 1050 mV
200000 @ 950 mV
100000 @ 950 mV
Q. I have enabled 100MHz but I can not scale down to 100MHz. Why?
A. By default the kernel sets 200MHz minimum. In order to scale down to 100MHz you can flash this script to set 100MHz on boot http://devphone.org/files/epic4g/kernels/Genocide_set_min_100MHz.zip or add this line to /system/etc/init.d/S_volt_scheduler:
Code:
echo "100000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
Q. How do I change the governor with terminal emulator or adb shell?
A. See the answer here: http://forum.xda-developers.com/showpost.php?p=13118624&postcount=1705
Q. This kernel has Voodoo Sound but I don't hear a difference. What gives?
A. There are indeed changes but to look at the settings and adjust the volume, download Voodoo Control App from the Market. I highly encourage people to donate to supercurio as he has done some awesome modification and more of his mods will find their way into this kernel soon!
Q. What is this flashing android on top of my boot animation now? How do I fix it?
A. On a stock rom, enabling boot animation support in the kernel plays the default boot animation (flashing android logo) over top of Samsung's own boot animation. Check out this thread to get rid of the flashing android or clear Samsung's animation for your custom animations.
Q. How do I enable CIFS support?
A. From 'adb shell' or a terminal emulator type 'insmod /lib/modules/cifs.ko'
Q. How do I enable TUN support?
A. From 'adb shell' or a terminal emulator type 'insmod /lib/modules/tun.ko'
Q. How come there is no frame rate increase?
A. The current method to increase the frame rate is by bumping up the LCD refresh rate. While I am told it should not break the LCD I decided it would be best to not mess with this setting for now until we find some proper documentation on the LCD in our devices. The documentation is kept under tight wraps and requires a signed non disclosure agreement for access.
Q. How do I set the timer delay for mkasick's keyboard patch?
A. Please refer to his post on more information about the keyboard patch http://forum.xda-developers.com/showthread.php?t=975611
A2. theimpaler747 has suggested a lower default value for the keyboard patch and has provided flashable scripts to set it lower. Please refer to his post here: http://forum.xda-developers.com/showthread.php?t=1025533 (If reports are good I will bump this down to the default value on my next release)
Q. I don't want to overclock or undervolt. Can I still use the kernel and will it automatically overclock/undervolt my device?
A. Yes you can absolutely still use the kernel. The default frequencies are 200MHz - 1000MHz at stock voltages. This will not change until you change it yourself.
Q. I flashed a different kernel and I lost root. What gives?
A. Root is now included in the kernel. If you flash a kernel that does not have root built-in then you will need to re-root.
Q. I didn't read or my settings became unstable after setting them on boot. Now my phone freezes when it boots up. What can I do?
A. You have two options. Option 1 is to restore your ClockworkMod backup that I KNOW you did before you started. Or option 2 flash this file with ClockworkMod to erase the boot settings: http://devphone.org/files/epic4g/kernels/Genocide_undervolt_recovery.zip
Q. Where are your sources?
A. Kernel sources can be found here: https://github.com/Rodderik/Genocide-Kernel
Q. Where can I find the link to download the kernel already?
A. After you have read everything, check the next post for links and changelogs.
If you like what I've done please consider a donation. I'm usually not one to ask for donations but it's pretty difficult finding a job for me right now so I'm doing what I can.
Please share your undervolt settings so I can compile and recommend a 'safe' starting point to help future flashers. Thanks.
Many thanks to DRockstar, nubecoder, gzub, supercurio, tanimn, mkasick, DevinXtreme, thomasskull666, nullghost, existz, rasdeep, and any other devs that I have forgotten. I apologize in advance. If you feel you deserve credit for something then please PM me and we will get the situation solved quickly.
Changelog: (Legend: "+" introduce addition/modification, "-" removed addition/modification, "*" changed addition/modification)
*updated su binary and Superuser.apk (if you still have the old Superuser installed either delete it from /system/app/ or simply update it via market)
Genocide2.0_superuser.zip
2.0
+dual boot support
+new boot logo for v2.0
*fixed typo in cpu code
*Voodoo Sound updated to v10
Genocide2.0_voodoosnd10.zip
1.1
*Tweaks to initramfs for root in adb
-Revert RNDIS patch due to breaking linux (wired tether still works) https://github.com/Rodderik/Genocide-Kernel/commit/b6b221bcb622ff369fa7c1c82543b3e75bb32748
+ClockworkMod 3.1.0.1 Purple Edition & working redirector (DRockstar https://github.com/DRockstar/Clean-Kernel-EC05/commit/ac713f90ec2a2560bc7fb05225341a4e4772a199)
*Busybox handled by recovery binary
*Moved superuser.apk location
*Swapped redbend_ua for bmlwrite
+Other scripts and tweaks from DRockstar into initramfs
+interactive governor + fixes
*ondemand governor fix to not scale below min frequency (nubecoder)
*Voodoo Sound updated to v9
+mountums & umountums added for USB Mass Storage in CWM (DRockstar)
+DroidDream malware prevention code in custom_init.sh script
*Voodoo Sound updated to v8
-Revert lowmemorykiller.c patch (causes kswapd0 to be stuck awake and eat cpu time)
+Kernel splash image was disabled after DK28 - Re-enabled (Stored in Kernel/drivers/video/samsung/logo_rgb24_wvga_portrait_victory.h)
*Add KBUILD_BUILD_VERSION to build.sh
+keytimer script and mods from DRockstar http://forum.xda-developers.com/showthread.php?p=13017148
*initramfs changes (persistant Superuser.apk)
Genocide1.1_FINAL.zip
1.0:
Voodoo Color by supercurio (http://perso.curio.be/android/Voodoo_color_mDNIe_GT-I9000.patch)
*New Overclocks and sysfs undervolting support (rasdeep, existz, tanimn, gzub, and thomasskull666...pulling my hair out over this one)
+Root, custom init scripts, misc tweaks (care of tanimn)
*Voodoo Sound updated to v7
+Conservative governor minimum frequency fix (You rock GZub https://github.com/gzub/EC05-Zub/commit/8a47c52d85d982ef035d24da293bcc046412b63e)
-Remove refresh rate change (We need proper LCD documentation before I can support changing this)
-Clean up github files and rename repo
-Removed video lag & camera force close fix (Samsung fixed the camera issues for EC05)
+Removed iqmsd service from initramfs (CIQ bad!)
+Keyboard delay runtime sysfs patch by mkasick http://forum.xda-developers.com/showthread.php?p=11755093
+TV compile fix (thanks tanimn and nullghost)
*Tweaked config flags and recompiled modules (thanks gzub for the help)
-Keyboard patch by mkasick in preparation for updated patch
+Refresh rate changed from 60 to 72 (slightly better framerates)
*Voodoo Sound updated to v6
+EC05 source merge
+scaling_available_frequencies sysfs patch from nullghost http://forum.xda-developers.com/showthread.php?t=1000309
Genocide_1.0_EC05_1.4GHzOC_UV_VS7_VC_Kernel.zip
0.4a:
+lowmemorykiller.c patch https://github.com/existz/kernel-i9000-suckerpunch/
+Voodoo Sound v4 by supercurio https://github.com/project-voodoo/sound_kernel_patches
+Added sched_autogroup v4 patch (Patch to smooth system under load) https://github.com/existz/kernel-i9000-suckerpunch/ & http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1 NOTE: Enable/disable by echoing either 0 or 1 to /proc/sys/kernel/sched_autogroup_enabled
+Changed swappiness from 60 to 10 (dumps RAM to swap less often for those with a swap partition)
+Wireless Tether fixes by mkasick http://forum.xda-developers.com/showpost.php?p=11808622&postcount=88 (should fix 4G tethering issues)
+Keyboard patch by mkasick http://forum.xda-developers.com/showthread.php?p=11755093
+Battery Status Polling Interval changed from 2000 to 30000 (30 seconds)
+RDNIS Froyo Fix by mkasick (use wired tether from http://forum.xda-developers.com/showthread.php?t=964925)
+Added RNDIS support for Wired Tether https://github.com/DevinXtreme/Xtreme_Epic_Kernel
+Added CONFIG_ARM_THUMBEE=y (as suggested by gzub)
+Set 4k read ahead in mtd_blkdevs.c (faster boot?)
+existz-initramfs-i9000-suckerpunch ported to Epic - BROKEN RIGHT NOW DO NOT USE!!!
+Removed CONFIG_DEBUG_INFO=y (gives us smaller kernel image and all modules including new cifs.ko)
+CFLAGS_KERNEL = -O2 -pipe -mcpu=cortex-a8 -mtune=cortex-a8 -mfloat-abi=soft -mfpu=neon
-Removed About Phone information (Caused FC and weird bugs in apps)
*Fixed error that wouldn't let cpu drop below 200MHz
Genocide0.4a_voodoosnd_20110316.zip
0.3a:
+Set defaults speeds to 200MHz min and 1000MHz max (NOW REQUIRES SETCPU TO OVERCLOCK)
+Compiled in video lag & camera force close fix by mkasick http://forum.xda-developers.com/showthread.php?t=970452
*Fixed issue with Firmware version in About Phone (FIXES PANDORA)
+Set initramfs root UID/GID
+Compiled and added cifs.ko to initramfs
-Removed cifs from kernel (you can try the module if you want but it broke the initramfs with it in there plus it is a nasty 2.3MB)
Genocide_0.3a_EB13_OC-UV_Kernel.zip mirror
0.2a:
+New EB13 initramfs (no more DK28 stuff)
+Added EXT4 Support
+Added bootanimation support
+Updated kernel modules from EB13
+Added recovery (need to test redirector)
+Added Firmware version to About Phone
+Started on Voodoo mods
Genocide_1.2GHzOC_EB13_Kernel_v0.2a.zip mirror
0.1a:
+1.2GHz overclock
+1Ghz 25mV undervolt
+DK28 initramfs (for pre-EB13/OTA compatibility)
Genocide_1.2GHzOC_EB13_Kernel_v0.1a.zip
If for some reason you want to revert back to the kernel that came with your rom you have two options. Before reverting back, I would suggest that you use SetCPU to lock in 1GHz to take advantage of the slight undervolt at 1GHz to save a little more battery. But if you insist the first option is to download and flash one of the following kernels based off which rom you are running:
VIPERrom DK28 RFS/EXT4 Modded Kernel HERE
Bonsai4all DK28 EXT4 Modded Kernel HERE (this includes roms based off of Bonsai as well)
The second option is to be 100% sure you get the right kernel back is to download either zip above and place the zImage into the kernel folder with 7zip. Typically the zImage can be found in your rom of choice's zip under /kernel or /kernel_update.
backing up now lol w00t
Nicely done! +400 to my quandrant scores and almost a full 4.0 increase with linpack. Cannot wait to see what else is to come!
darkjje said:
Nicely done! +400 to my quandrant scores and almost a full 4.0 increase with linpack. Cannot wait to see what else is to come!
Click to expand...
Click to collapse
+1 i was avg around 1100/2300 in smartbench!1ghz, pulling 1300/2900 @1.2ghz
so far so good here THANKS
I love lamp!
Great job brother
WOW!
Team Viper 'STAY STRONG' with these Great ROMS!!!
YOur testers say Thank You!!!
Nice job man,I knew you guys would have somthing from EB13 flashable before the weekend was over.
Sent from my MyFrankenstein ROM using XDA App...
ecooce said:
Nice job man,I knew you guys would have somthing from EB13 flashable before the weekend was over.
Sent from my MyFrankenstein ROM using XDA App...
Click to expand...
Click to collapse
What are your scores for Frankenstein? ...cuz i know you're ROM comes stock like 98MB or something like that ...so it's already quick as Puff-N-Stuff lol
ViperCom?
Why didn't ViperCom show this kernel being available?
edit--EST--5:03am--just saw in ViperCom-Thanks!!!
Thanks, this is really fast. Any chance of someone compiling the browser from it as well? The ones we have are sort of hacky.
BThomas22x said:
What are your scores for Frankenstein? ...cuz i know you're ROM comes stock like 98MB or something like that ...so it's already quick as Puff-N-Stuff lol
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nuff said,awesome job,this thing is FAST... Cant wait to see what else is to come. And I have tons of things loaded atm,so I could post better scores when I get an EB13 ROM out.
I just got 2450 quadrant on bonsai rom! I didnt even kill other apps
Sent from my SPH-D700 using XDA App
Oooo first to post this...
LOVE the kernel name man lol
Genocide ftw!
Sent from my baked and emotionless SPH-D700
Can anyone help with the scaling settings. Would like a good mix of speed and battery strength. Current setting are conservative (1000000max and 400000min)
id love to see a vid, time lapse or something, of you unfolding this kernel into rich goodness. I'm very interested to learn more about how this works. Maybe start a xda webinar for those wanting to get the skills down...imagine where that could take us, having more educated folks pumping time into creative dev. Either way, Capital R you are the man! Keep the wheels turning.
Sent from my SPH-D700 using XDA App
Runs great. Awesome job man. Finally an oc/uv for froyo!
Sent from my SPH-D700 using XDA App
backing up and installing now, is it possible to post or get a link to the stock trinity 2.0 kernel incase we run into errors later on ?
It's been so long since I've had a custom kernel I almost forgot what it felt like!
Runs beautifully on Nebula rom. Actually logged in on my browser just to send you a thanks.
Fangs87 said:
backing up and installing now, is it possible to post or get a link to the stock trinity 2.0 kernel incase we run into errors later on ?
Click to expand...
Click to collapse
nandroid
but u could prolly grab the zImage from T2 and manualy flash?
Read new informations in installation guide
Click to expand...
Click to collapse
Click to expand...
Click to collapse
IF YOU HAVE REBOOTS WHEN YOU ARE USING THE PHONE, IT'S BECAUSE YOU SET A UV TOO AGGRESSIVE, SO, YOUR CPU CAN'T BE STABLE. CHOSE A LOWER UNDERVOLTAGE
IF YOU WANT TO KNOW HOW VOLTAGE CAN REACH YOUR CPU, START STABILITY TEST (DOWNLODABLE FROM MARKET) AND USE IT FOR ABOUT 10 MINUTES, IF PHONE REBOOTS IN THAT TIME, THAT VOLTAGE IS TOO LESS FOR A STABLE CHIP
NOT ALL CHIP ARE THE SAME, IF YOU HAVE A LUCKY CHIP, YOU CAN REACH A LOWER VOLTAGE (AS MINE)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Ok Guyz, since show creates the badass governor, i'd want to use it for a better one multicore configurtion
What's the advantages of multicore sistem?
Symply, more parallelization means more performance per second, as i can say, 2 core can compile at last the double quantity of threads than 1, so, 1 core at double frequency can't compile the same number of thread, but it do it faster..
ex..
if you have 2 thread (impossibile), 1 audo and 1 video, a single core @ 2ghz compile firstly the audio, than the video.. the dualcore architecture can compile on core0 the audio and on core1 the video!! this is the powerfully of multicore system.
Ok, since i say it, i create a MOD witch TRY to use this logically.. this MOD uses the limitate frequency of the badass governor, that's why, with ondemand, all of 2 core goes at maxFreq too fast, now, with this badass, the system will not grow up the first limitate frequency until the single core uses more than that frequency.. so.. we can limitate the "ondemand" issue in 3 freq phases..
thus, the actual MOD configuration is it:
Click to expand...
Click to collapse
SCREEN ON:
- dualcore with all cores TURNED ON (hope you understand now )
- governor badass for all of 2 cores
- min freq at 384mhz for all of 2 cores
- max freq at 1.566ghz for all of 2 cores
- first phase freq at 810mhz for bla bla bla
- second phase freq at 1.188ghz for bla bla bla
- third phase freq at 1.566ghz (is the maxfreq)
SCREEN OFF:
- only core0 is TURNED ON
- governor conservative
- minfreq 192mhz
- maxfreq 540mhz
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Badass governor has the same configuration as last show's ondemand governor
So, now, with this MOD we have a pure functional dualcore with the advantages of multicore system, with limitate frequency. The stock situation is 384-810mhz, if the single core (is the same, qualcomm uses asyncronic frequency) needs more than 810mhz, it increases the max freq to 1.188ghz (the sensation original frequency), if 1.188 isn't sufficently, it increeses at 1.566
remember, qualcomm has asyncronic frequency, so, one core can be run at 1.56ghz, the other at minimum mhz..
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How to use it?
Click to expand...
Click to collapse
INSTALLATION:
-) flash a kernel witch has badass governor (i advise bricked 1.1) with NO GPU OC and what governor you want, the same for the frequency, mod autochanges those, chose what scheduler you prefer.
1) Flash MOD zip file by recovery
2) Select what MOD YOU want
3) Reboot.
#) You have to reinstall at every Rom Upgrade
# If you want only the UV, select Remove in mod choseing (it's the same as no installing it); you can use the UV mod with all kernels, and all governors
# If you come from V2.0 to 3.0, go to recovery, wipe, format system partition, after that, reinstall rom, reinstall bricked kernel (if it hasn't), reinstall other mods (like battery %), install my mod, reboot.. You will not loose your data
# ONDEMAND VERSION IS NOT FOR GOOD BATTERY CONSUPTION, IF YOU HAVE HUGE BATTERYDRAIN (IT'S WHAT YOU'LL HAVE) INSTALL THE BADASS - BOOST+BOOST VERSION.
DISINSTALLATION:
1) Boot in recovery, flash the Mod
2) Select Remove
3) Reboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Code:
bricked 1.2 -above
V 11.9
> Fixed Screenoff chose
> Changed DEFAULT first phase for better reactive with less power usage
> Other minor changes
###
Added Version for AOSP kernel (NoSense)
V 11.8
> Changed some settings
V 11.7
> Changed some settings for a better fluidity
V 11.6
> Added Remove chose
> Fixed an installation issue of the Aroma
V 11.5
> Added possibility to know if MOD is working, you have to give a cycle on/off of the screen, after that, if it works, you will find a new file in home of sdcard!
V 11
> Changed configuration for less battery drain
V 10.5
> Tweaked badass experience for better battery life (only with bricked kernel 1.4)
V 10.1
> Tweaked screen off conservative
V 10.0
>> BIG RELEASE
> Added possibility to chose frequency
> Added possibility to chose screen off governor
V 1.01
> Fixed freq values in Aroma installer
V 1.0
> Initial Release
HaVe FuN!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FAQ in second post
VIDEO
Click to expand...
Click to collapse
FAQ
Click to expand...
Click to collapse
Witch version could you chose?
The versions of the mod are two:
The 3.7 is the older, it's for the bricked 1.1 version AND for other kernels (don't know if all rom will boot up with my mod, some has issues)
The version 10 and above are for bricked 1.36 and 1.40
What setting could you use?
You can intall what you want, i create those (expecially the 10 versions) witch has the possibilities to be changed as users experience.
I advice to use default settings if you don't know how change, but, you should try to, it will not brick your phone, in fact, you could find a new setting could it be better for your use.
So, try try try
One EX:
If you want a faster phone, grow up the minfreq to 300-400mhz, grow up the first phase at 1.2ghz, put the second to 1.2 or more, and change the maxfreq as you would, OC too.
If you want a better battery experience, decrese minfreq, the first and second phase, decrese the maxfreq too, maybe, with this settings: 192 - 648 - 1020 - 1180 mhz
If you want the lowest battery experience, try with this setting: 192 - 648 - 1020 - 1020 mhz
Be careful, you could have some lags if you chose the lower setting, but, for ex, if you don't play, you can chose a setting as like, 192 - 810 - 1020 - 1180 mhz
So, you have to install, select one setting with you think it's ok, try, if you have lags in some situation, grow up some setting, an re-try til you find your best settages. I don't have your use, so, i don't know if you could have a good esperience with my setting.
How to see if mod is working?
If you have the version 10 or above, you will find a new file in SD card, it calls IBA21ModWorking. if you don't find that, turn on the screen, wait 5 seconds, turn on, refresh the explorer app, and try to see if there is.
If you have the 3.7v you have to download and install system tuner, and see if all cores are turned on.
Why my phone doesen't boot after apply the mod?
Not al roms has the same quality, some doesen't have some little features; my mod uses a whyle cicle witch chages settings from screen-on use to screen-off (standby). If phone doesen't boot up, rom doesen't have the possibility to use the cycles in the script, so, script is unusefull.
Do you need to delete or wipe the rom at every upgrade?
ABSOLUTELY NO, mod auto removes the old script and changes that with the newer one, so, YOU DON'T NEED TO DO ANYTHING, ONLY FLASH THE UPGRADE OR THE NEW SETTINGS WITCH YOU ARE CHANING!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
enjoy my work and, press a lot of thanks buttons! :d
Very very good, the system is smooth and stable, I've only a lag after reboot, and sometimes when start synchronization...
Good work!
Hi nice script. Must the CPU values be truly stock ? Could it take something like 384-1566?
Sent from my Sensation running HyperNonsense v2.3
remus82 said:
Hi nice script. Must the CPU values be truly stock ? Could it take something like 384-1566?
Sent from my Sensation running HyperNonsense v2.3
Click to expand...
Click to collapse
Yep, i could do it.. but.. i tryed it, and.. it only increase the power consuption
framir said:
Very very good, the system is smooth and stable, I've only a lag after reboot, and sometimes when start synchronization...
Good work!
Click to expand...
Click to collapse
Lags depends on badass governor.. it's "normally".. but.. 1 lag per day is not bad, remember, with my configuration you have a better badass configuration with lower power consuption than faux kernel..
Looks awesome
Noticed bug appears after every reboot?
How to change second phase to 810-1134 and delete third phase? Or I don't need it
And soo.. It's fully better than original badass?
http://i.imgur.com/gavOn.png
Standby power consuption with data active!
D-SHEL said:
Looks awesome
Noticed bug appears after every reboot?
How to change second phase to 810-1134 and delete third phase? Or I don't need it
And soo.. It's fully better than original badass?
Click to expand...
Click to collapse
You don't need to delete it since system uses third phase (1.2 to 1.5) only in heavy games and web browsing+flash player.. in web usage cores goes to 1.2 max
Btw.. third phase is the maxfreq governor.. i can change it by script if you want to try
Take.. flash it as you would.. you can come back with stock script
For who doesen't understand.. the phase limis is a real limit.. since system needs more performance, system use the lower limit.. as i can see in my use:
For home scrolling 1 core goes to 1.2ghz, the other is at 192mhz (low power consuption)
For notice bar scrolling 1 or 2 cores goes to 810mhz, it depends on other app.. 1 core at 810mhz can calculate the notify bar
For chrome beta browsing.. in web rendering ( page loading) all of 2 cores goes to 1.2ghz, after that, core goes to 192-810 since heavy scrolls, heavy zoom, or animations in the web page (in google page cores goes to 192mhz )
For browser + flash player, 2 cores are uset at 100% at 1.56ghz since it comes down.. after that.. system uses 192-810.. sometimes only one core goes to 192-1.2
In games core i dont know why i dont play games
So.. the third pase is only a turbo boost, it's used only when system needs more and more power.. the phase is a real limit..
For example.. you have a stock 192-810.. when system needs more than 100% (810mhz) badass grow up the frequency to second phase.. it's the same for third phase.. so.. if system doesen't need more power, badass doesen't grow up the cpu frequency..
In my test i see.. ondemand tweaked + core1 off at my usage has a cpu temperature at about 55degrees C.. with badass, 47
So.. lower tenperature.. lower power consuption!
Sure.. ondemand has a faster one response.. since it grow up frequency every time, for low needs too..
you couldn't have performance plus heavy power..
The "busg" is too.. until system needs more than phase freq, it doesent grow up, so, when there's the necessity of more freq, upgrading is slower than ondemand, and it creates a little lag..
On boot, don't know why but.. only one core is turned on.. it's a system fault of reading script.. if you turn off screen, and turn on, it returns at normally (so.. needs an off-on cicle)
iba21 said:
You don't need to delete it since system uses third phase (1.2 to 1.5) only in heavy games and web browsing+flash player.. in web usage cores goes to 1.2 max
Btw.. third phase is the maxfreq governor.. i can change it by script if you want to try
Click to expand...
Click to collapse
Thanks! Maybe really don't need this
Noticed bug appears after every reboot?
"69force192-1188.zip"
As I can see, this is version without third phase?
D-SHEL said:
Thanks! Maybe really don't need this
Noticed bug appears after every reboot?
"69force192-1188.zip"
As I can see, this is version without third phase?
Click to expand...
Click to collapse
Yep that has only 2 phase.. 192-810 and 810-1.2
I edited last message with informations about your questions
Shouldn't this be in the Development section?
nope.. it's not a developement app.. those are some settages..
if you load the script, and delete it, the settages has been changed..
when you turn on display
screen ON:
- dualcore able
- governor badass for all of 2 cores
- min freq at 192mhz for all of 2 cores
- max freq at 1.566ghz for all of 2 cores
- first phase freq at 810mhz for bla bla bla
- second phase freq at 1.188ghz for bla bla bla
- third phase freq at 1.566ghz (is the maxfreq)
when you turn off
screen OFF:
- only core0 able
- governor conservative
- minfreq 192mhz
- maxfreq 540mhz
it changes that values at every turn on-off of the display.. only 1 time.. so.. if you load the script, and delete it, at display turning off, the script doesen't change the values, and, you will not have the "screen off" setting, so, you'll have the stock badass, so, more power consuption
i repeat, my script is only a numerical setting, it's not a kernel, it changes only the superficially values of the kernel, after that, is the kernel governor the real fault of frequency changing
sure.. with my script you have that 2 configuration.. and.. if you see.. conservative in standby means low power consuption (from 20 to 70ma in standby, depends on the system performance needed)
Is step 6 necessary? I don't have that function in root explorer
Sent from my Sensation running HyperNonsense v2.3
remus82 said:
Is step 6 necessary? I don't have that function in root explorer
Sent from my Sensation running HyperNonsense v2.3
Click to expand...
Click to collapse
it's not obbligatory.. but.. you have it.. long press.. OPEN WITH -> LINUX script (it's the third link from top)
http://i.imgur.com/BbeS0.png
Or you can reboot 2 times.. in first run script changes the name of the file witch turn on the second core.. the mpdecision.. so.. or you do a first manually run.. or you do a first reboot.. script changes the name, but the mpdecision script is already loaded.. second reboot use only my script
Thanks! Will report back after a day of use!
Sent from my Sensation running HyperNonsense v2.3
Edit: solved.
Sent from my Sensation running HyperNonsense v2.3
Iba I notice that media scanner takes extremely long to complete after applying the script. Is it possible to use badass or on demand as screen off governor?
Sent from my Sensation running HyperNonsense v2.3
Sure.. but you loose the advantages of low power consuption..
What is media scanner? How many mhz does it needs?
Hello,
I’m proud to share with you my little contribution to easily change GPU speed.
Intro:
In AOKP rom based android 4.1+, it’s easy to change the GPU frequency. Many devices are stable while GPU overclocked.
To change GPU speeds simply edit /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Values:
0: normal frequency (for example, 307 Mhz on some devices)
1: medium
2: high (for example, 512 Mhz on some devices)
But, it’s not my goal to discuss it.
My app:
Here is my app to select GPU speed on the fly (normal, medium or high).
This app need root and secure settings plugin (from google play). Write in system need root.
The app change only the value in the file “gpu_oc” with 0, 1 or 2. The design is simple, don’t blame me.
If I helped, then press my thanks button
Before use it, go to edit the following file to check value:
/sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
If there is 0, 1 or 2, then you are able to use this app. If not, or if the file is missing, then don’t use this app.
Use this app only with AOKP rom based with Android JB 4.1+
Some devices can't handle GPU overclocking well and might freeze/reboot and it may be necessary to adjust voltages.
After GPU OC, if your device freeze, just reboot and GPU will not be overclocking.
Use at your own risk, I’m not responsible of any damage on your device.
Required:
- AOKP rom based
- Android JB 4.1+
- Secure settings plugin from google app store
- File "gpu_oc" here in /sys/devices/system/cpu/cpu0/cpufreq
If you tried on other rom and if it worked, then come back to tell me.
Downloads:
Click on attached files below to download the app : GPU_OC.apk
>>> To test GPU speed, use nenamark2 from google app store.
Screenshots:
excellent thank you
you should probably warn people that some phones cant handle gpu oc well and might freeze/reboot and it may be necessary to adjust voltages
Doesn't even ask for root access. Its either fake or poorly wrote.
Sent from my Nexus 10 using xda app-developers app
blmvxer said:
Doesn't even ask for root access. Its either fake or poorly wrote.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
If you don't have anything positive or productive to say about the app don't say nothing at all
Don't listen to this guy
-App DOES ask for root permission
-I checked /sys/devices/system/CPU.... And its written like it should be.
-Ran a benchmark on my GS3 before usage , ran it again with higher scores... So it does make a difference.
Device: ATT GS3
ROM: AOKP 4.2.2
no OC or extra kernel features.
Thnx for this app
Sent from my SGH-I747 using Tapatalk 2
My app use the app “secure settings plugin”, which need root to write in system. So, in fact, my app need root.
@ Miguel : ok, summary modified.
jayRokk said:
If you don't have anything positive or productive to say about the app don't say nothing at all
Don't listen to this guy
-App DOES ask for root permission
-I checked /sys/devices/system/CPU.... And its written like it should be.
-Ran a benchmark on my GS3 before usage , ran it again with higher scores... So it does make a difference.
Device: ATT GS3
ROM: AOKP 4.2.2
no OC or extra kernel features.
Thnx for this app
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
You know, he does have a point.
Required:
- AOKP rom based
- Android JB 4.1+
- Secure settings plugin from google app store
- File "gpu_oc" here in /sys/devices/system/cpu/cpu0/cpufreq
If you tried on other rom and if it worked, then come back to tell me.
Click to expand...
Click to collapse
i was trying at Lewa Os, and stuck :crying:
Running on Mokee 4.4.2, Tab 2, Dohllmen Kernel. Have yet to test with above-mentioned app, but will do tomorrow. My Tabs animations do seem to be snappier on the medium setting. Look forward to seeing the numbers tomorrow. Thank you!
Sent from my GT-P5113 using XDA Premium 4 mobile app
Dhollmen Kernel results (Nenamark2)
1.0ghz with GPU 0 = 28.2 fps
1.4ghz with GPU 0 = 28.6 fps
1.4ghz with GPU 1 = 30.0 fps
1.4ghz with GPU 2 = 35.2 fps
GPU 0 means 300mhz
GPU 1 means 384mhz
GPU 2 means 512mhz
your results should be as follows
Great work. Tested it on Samsung Tab 2 10.1 with Dhollmen kernel n CM11 nightly. Question is, how do I set the higher gpu rate at boot?
jcsy said:
Dhollmen Kernel results (Nenamark2)
1.0ghz with GPU 0 = 28.2 fps
1.4ghz with GPU 0 = 28.6 fps
1.4ghz with GPU 1 = 30.0 fps
1.4ghz with GPU 2 = 35.2 fps
GPU 0 means 300mhz
GPU 1 means 384mhz
GPU 2 means 512mhz
your results should be as follows
Click to expand...
Click to collapse
So it means that this app basically works fine? is this available for android M also?
philippe734 said:
Hello,
I’m proud to share with you my little contribution to easily change GPU speed.
Intro:
In AOKP rom based android 4.1+, it’s easy to change the GPU frequency. Many devices are stable while GPU overclocked.
To change GPU speeds simply edit /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Values:
0: normal frequency (for example, 307 Mhz on some devices)
1: medium
2: high (for example, 512 Mhz on some devices)
But, it’s not my goal to discuss it.
My app:
Here is my app to select GPU speed on the fly (normal, medium or high).
This app need root and secure settings plugin (from google play). Write in system need root.
The app change only the value in the file “gpu_oc” with 0, 1 or 2. The design is simple, don’t blame me.
If I helped, then press my thanks button
Before use it, go to edit the following file to check value:
/sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
If there is 0, 1 or 2, then you are able to use this app. If not, or if the file is missing, then don’t use this app.
Use this app only with AOKP rom based with Android JB 4.1+
Some devices can't handle GPU overclocking well and might freeze/reboot and it may be necessary to adjust voltages.
After GPU OC, if your device freeze, just reboot and GPU will not be overclocking.
Use at your own risk, I’m not responsible of any damage on your device.
Required:
- AOKP rom based
- Android JB 4.1+
- Secure settings plugin from google app store
- File "gpu_oc" here in /sys/devices/system/cpu/cpu0/cpufreq
If you tried on other rom and if it worked, then come back to tell me.
Downloads:
Click on attached files below to download the app : GPU_OC.apk
>>> To test GPU speed, use nenamark2 from google app store.
Screenshots:
Click to expand...
Click to collapse
I can't see the file in my Xperia C4 E5303. Does that mean that It will not work for me?
hi i need help i saw some folders in sys directory called folder name sys/module/fuse/《《 is this folder knox fuse??
sys/module/dm-verity/
and sorry for off topic ?
Presenting the Stone Kernel for ASUS Padfone 2 (A68), a custom kernel designed to get a little more out of the Padfone 2.
DISCLAIMER: As per all custom kernel disclaimers, while I do test this kernel on my own device, I'm not responsible for you voiding your warranty, or any damage/bricking/weirdness that may occur to your Padfone. If you're not comfortable with this, do not proceed.
v0.9
Main features:
Based on ASUS source code v10.4.16.8, compatible with Android 4.1.1 stock PadFone2 firmwares
init.d support (init.rc busybox runparts)
USB OTG Host in phone mode
UI rendered with GPU instead of CPU, making it very snappy
Lowest CPU frequency set to 162mhz
CPU frequency locked to 162mhz-1512mhz during boot
Undervolted to save power & reduce heat
Undervolt interface (compatible with System Tuner, Kernel Tuner, etc)
Additional CPU Governors: Wheatley, InteractiveX v2, MSM_DCVS
Set InteractiveX v2 CPU Governor to default instead of Performance, to lower battery consumption, maintain snappy performance, and improve CPU freq config
GPU normal freq set to 200mhz to lower battery usage (will still scale upto 266/400/533mhz when busy)
Simple IO Scheduler (SIO) added, and set as default
Increased min/max read-ahead values from 16/128 to 32/2048
USB FastCharge upto 1400mA (enable using Kernel Tuner, sysfs, etc)
Lower minimum brightness to save power
Lower voltage for display (~13% lower voltage) to save power
NTFS USB drives need USB OTG Helper software or similar - working on fixing the NTFS module
Increased file cache ratio to improve storage performance
Standard edition: CPU max 1.51ghz, GPU max 400mhz
Overclock edition: CPU max 1.72ghz, GPU max 533mhz, low voltages
Powersaver edition: CPU max 1.35ghz, GPU max 266mhz, low voltages
Minor tweaks:
Replace Wifi modules with AOSP versions (needed due to the way the stock modules were compiled by ASUS)
Disabled swap
Disabled "Compile the kernel with debug info"
Disabled Debug memory initialisation
Disabled Magic SysRq key
NTFS in kernel (instead of module)
FAT support
Improved CPU multi-core frequency limiting
GitHub: https://github.com/lindsaytheflint/stone
Download:
Stock kernel 10.4.12.24: https://docs.google.com/file/d/0ByOiY1XD_cLvNVFwVi1Yc3lmS2M/edit?usp=sharing
Stock kernel 10.4.15.1: https://docs.google.com/file/d/0ByOiY1XD_cLvVU5KWkJqZzVrU00/edit?usp=sharing
Stock kernel 10.4.16.8: https://docs.google.com/file/d/0ByOiY1XD_cLvaGR2X19RS2hOa28/edit?usp=sharing
Stone kernel v0.1 "Dual": https://docs.google.com/file/d/0ByOiY1XD_cLva0Q3el9VbU1vd1k/edit?usp=sharing
Stone kernel v0.1 "Quad": https://docs.google.com/file/d/0ByOiY1XD_cLvdk9EcTAtdXdDRGM/edit?usp=sharing
Stone kernel v0.2 "Standard voltage": https://docs.google.com/file/d/0ByOiY1XD_cLvUFpSenoyXzFYRVk/edit?usp=sharing
Stone kernel v0.2 "Low voltage": https://docs.google.com/file/d/0ByOiY1XD_cLvclVXdEs4Qm1sb0U/edit?usp=sharing
Stone kernel v0.3 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvd28ybVB2MHhXTXc/edit?usp=sharing
Stone kernel v0.3 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvUnI4Z01YYzZBY1k/edit?usp=sharing
Stone kernel v0.4 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvd1lOQmI4c2duaGc/edit?usp=sharing
Stone kernel v0.4 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvM2QxdXVFMGcxRm8/edit?usp=sharing
Stone kernel v0.6 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvSm9XQVBqTWtBUEU/edit?usp=sharing
Stone kernel v0.6 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvN3otdjM3elNHYUk/edit?usp=sharing
Stone kernel v0.7 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvbTBralZ4aVZFOVk/edit?usp=sharing
Stone kernel v0.7 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvTGc2YWJFWFYxWGM/edit?usp=sharing
Stone kernel v0.8 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvNGxheldqTThNT2c/edit?usp=sharing
Stone kernel v0.8 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvOWw4cFBGb0xyUEk/edit?usp=sharing
Stone kernel v0.8 "PS": https://docs.google.com/file/d/0ByOiY1XD_cLvemtzSTlMZEpGcU0/edit?usp=sharing
Stone kernel v0.9 "STD": https://docs.google.com/file/d/0ByOiY1XD_cLvbUxWRHVPd1cyX2s/edit?usp=sharing
Stone kernel v0.9 "OC": https://docs.google.com/file/d/0ByOiY1XD_cLvd3FQOXJnbVZVbFE/edit?usp=sharing
Stone kernel v0.9 "PS": https://docs.google.com/file/d/0ByOiY1XD_cLvbm5qNFdHZWcwYjA/edit?usp=sharing
Installation:
1. Copy StoneK_A68_v0.9_OC.zip or StoneK_A68_v0.9_STD.zip to /sdcard/ via USB.
2. Copy StockKern_A68_10.4.16.8.zip to /sdcard/ via USB, in case you have trouble booting, and need to uninstall.
3. Boot into TWRP or CWM Recovery.
4. Perform backup of at least your "Boot" partition.
5. Install zip from step 1.
6. Reboot.
Uninstallation:
1. Copy StockKern_A68_10.4.16.8.zip to /sdcard/ via USB.
2. Boot into TWRP or CWM Recovery.
3. Install zip from step 1.
4. Reboot.
ChangeLog
ToDo:
Possibly faster CPU & GPU overclocking, pending successful testing
GPU undervolt
GPU freq sysfs interface
WiFi undervolt
Enable additional audio codecs: WMA, AAC, etc
BLN?
v0.9 - 2013/08/19
Raised voltage slightly for display, to increase compatibility with other's phones, and prevent flickering
Increase storage read-ahead from 1024kb to 2048kb
Increased file cache ratio to improve storage performance
v0.8 - 2013/07/29
Lower minimum brightness to save power
Lower voltage for display (~16% lower voltage) to save power
CPU lowest freq set to 162mhz (from 192mhz)
GPU idle frequency set to 200mhz (from 128mhz)
Fixed USB OTG for both phone & pad
NTFS USB drives need USB OTG Helper software or similar - working on fixing the NTFS module
Disabled MPDecision?
OC edition: GPU max freq set to 533mhz (from 487mhz)
New edition: Power Saver - lower CPU & GPU limits, useful when travelling
v0.7 - 2013/06/14
Built from 10.4.16.8 ASUS source code
Fixed camera
Removed Faux123 MSM CPUFreq_limit to improve multi-core freq limiting
Modified CPU freq limits so that cores 2-4 will never exceed core 1 frequency
v0.6 - 2013/06/05
Disabled Android Low Memory Killer (2GB RAM is quite a bit, and the perf cost of relaunching processes is annoying)
Enabled USB OTG Host in phone mode
Minor voltage tweaks
Added MSM_DCVS Governor
Added Faux123 MSM CPUFreq_limit to improve multi-core freq limiting
UI rendered with GPU instead of CPU, making it very snappy
Minor init.rc/build.prop tweaks
v0.5 - 2013/05/18
Enabled init.d support (init.rc busybox runparts)
v0.4 - 2013/05/13
Lowered InteractiveX default boost freq from 1512000 to 1350000
Increased USB Fast Charge limit from 1000mA to 1400mA
Fixed LCD backlight during calls
Reverted from GCC 4.7 to GCC 4.6 so ASUS modules load ok
v0.3 - 2013/05/07
Based on ASUS source code v10.4.15.1
Two versions - OC & Standard
Switched compiler from GCC 4.6 to 4.7
Further voltage tweaking
Fixed CPU throttling
Added InteractiveX v2 Governor - very good for properly setting CPU freqs across all cores
Set default Governor to InteractiveX v2
GPU overclock to 487mhz - working
GPU normal freq set to 128mhz to lower battery usage (will still scale upto 487mhz when busy)
Simple IO Scheduler (SIO) added, and set as default
Increased min/max read-ahead values from 16/128 to 32/1024
USB FastCharge (enable using Kernel Tuner, etc) - working
Removed Sysctl syscall support
Removed software controlled Adaptive Voltage Scaling (AVS)
Removed adaptive voltage scaling (AVS)
Removed Generic Dynamic Voltage and Frequency Scaling (DVFS) support
Removed CPU frequency translation statistics details
Reduced max CPU voltage back to 1.30v
Re-enabled "Monitor thermal state and limit CPU Frequency"
v0.2
Removed dual/quad versions - quad-core is running stably for me with revised voltages
Added standard/low voltage versions, for anyone having trouble booting, please try the standard version
Lowest CPU frequency set to 192mhz
Android Logger re-enabled temporarily, for USB FastCharge troubleshooting
CONFIG_SCHED_MC=n (not needed with HotPlugging CPU)
CONFIG_SCHED_SMT=n (not needed)
Disabled "Monitor thermal state and limit CPU Frequency"
Increased max CPU voltage from 1.30v to 1.45v (always monitor your temperature when increasing the voltage/frequency!!)
Further tuned CPU voltages
Added Wheatley Governor, and set to default
Disabled "Use MSM_DCVS for CPU/GPU frequency control"
GPU overclock to 487mhz - not verified yet - I think some kind of ASUS lock may still be preventing this
USB FastCharge (can be turned on with Kernel Tuner etc) - not verified yet - I think some kind of ASUS lock may still be preventing this
FAQ
Q. My phone is running hot!
A. This is usually related to the voltage being too high. Try lower voltage, and try to determine which frequencies are running hot for you. You may need to also restrict your max CPU frequency with SetCPU, System Tuner, Kernel Tuner, etc, if the frequency won't run stably on your phone.
Q. CPU-intensive apps (particularly games) terminate abnormally after a bit of use.
A. This usually means the voltage is a little too low for that frequency. Try to raise the voltage (only 12.5mv at a time) until you find a stable voltage, and let the rest of us know what value is best for you.
Q. My phone won't even boot with this kernel.
A. Sounds like the voltages are too low for you. Try the "STD" version, which uses voltages only slightly lesser than stock.
Q. I want GPU overclocking, but I don't want CPU overclocking.
A. Use the "OC" version, and use SetCPU, System Tuner, Kernel Tuner, etc, to set the max CPU freq you want.
Q. Proximity sensor doesn't work during a call
A. Fixed in version 0.4
How stable is it?
And also, if I read/understood the "main features" right, you limited the CPU to only use 2 cores instead of 4?
I read that you did it for more stability when overclocked, but if this only uses 2 cores out of it's 4, I will be very hesitant to flashing it...
Either way though, this is great progress! We are finally getting a handfull of developers for the Padfone 2! Hopefully we can get Cyanogenmod ported soon aswell!
Great job!
Lidenburg said:
How stable is it?
And also, if I read/understood the "main features" right, you limited the CPU to only use 2 cores instead of 4?
I read that you did it for more stability when overclocked, but if this only uses 2 cores out of it's 4, I will be very hesitant to flashing it...
Either way though, this is great progress! We are finally getting a handfull of developers for the Padfone 2! Hopefully we can get Cyanogenmod ported soon aswell!
Great job!
Click to expand...
Click to collapse
I've been using it for a few weeks, and when I had 4 cores enabled, I found it a bit unstable. With 2 cores enabled only, it flies along due to the higher frequency, and is rock-solid.
Unless you're using the MSM_DCVS Governor (which isn't default even on stock kernel), not all the cores are used except for under high load. Using Interactive, Performance, and other Governors, it usually keeps 3 cores off, and just powers the second one up when doing things. Only when running very CPU-intensive tasks will all 4 cores be used, and the phone will run very hot. If using the MSM_DCVS Governor, it'll continually lower the CPU frequency anyway. These factors are why I've limited the CPU cores - the end-result is a faster, cooler, and less power-hungry kernel.
Nevertheless, I'll upload another one in the next couple of days with all 4 cores enabled, so people can test it out.
First of all nice work here ! Good to see people progressing. As im still bit of a noob and my question maybe quite noobish.
I have NOS installed on my padfone 2 atm and its working flawlessly. Just before I try this I wanted to ask you if this will some way interfere with NOS ?
I would happily be our test monkey if needed
One more time,
Thank you !
Hey first of all this is very nice that you develop kernel to padfone and its nice to see some progress , but i would like that if you make the kernel with 4 cores and little bit smaller clocks ex 1.5 or 1.6 and if you set low freg to somewhere near 100mhz. That would be nice to see
Sent from my PadFone 2 using xda app-developers app
Great work! We finally have our first custom kernel
Great work... I will test soon as possible
Sent from my PadFone 2 using xda app-developers app
Quad core
I've recompiled the kernel with all 4 cores enabled, and will update after I've done some stress testing. (I won't upload it if it's not stable for me.)
When I tested it a few weeks ago, quad core was too hot, but I've tweaked the voltages quite a bit since then, so hopefully it'll be upload-worthy.
How to download link using phone?
Quad core version uploaded
I've uploaded the Quad core version too.
Curious to here other people's experiences on that - I personally find that my PF2 barely uses the 3rd & 4th cores (even on stock kernel), so I prefer the dual core kernel version (faster, more stable, less heat, less voltage requirements), but CPUs differ a little from phone to phone.
Keen to here people's tests from the dual core kernel vs the quad core kernel.
Me currently testing dual core version
Just downloaded and installed the QuadCore version. Will be back here in a couple of days!
Can you say thank you too many times ? NOT!
Thank you once more !
Thank you for quadcore version wil try it out!
Sent from my PadFone 2 using xda app-developers app
Reboots in Padfone Station
I tried to use the dual core version today during some meetings and it was fine when in phone mode, but after using it in the station for a while it would get very hot and then reboot. I was overclocking it to 1.7. Anybody else have similar experience?
sunshine333 said:
I tried to use the dual core version today during some meetings and it was fine when in phone mode, but after using it in the station for a while it would get very hot and then reboot. I was overclocking it to 1.7. Anybody else have similar experience?
Click to expand...
Click to collapse
Usually "very hot" means that the voltage needs to be lowered. Can you try using System Tuner to lower the voltage slightly for 1.7ghz frequency, and advise whether that helps?
i have flash the dual core ver.
But when i boot and at the asus loading logo, it keep shining white screen and some color line.
After booted into system it soft reboot again and again. then i revert to stock kernel it fine.
i already wipe cache/dalvik
i am using TWRP 2.5 and stock rom
Undervolting 1.7
I have not tried it in the padstation yet, but the 4 core version undervolted 1 step down (1125 I think?) was stable when I just played Final Fantasy 3 for about 20 mins. CPU spy shows that it was running at 1.7 during that time. No apparent heat issues and no reboots or anything like that. I will try it in the padstation and report back later.
---------- Post added at 03:49 AM ---------- Previous post was at 03:40 AM ----------
Just to be clear I only further undervolted the highest frequency (1.7). Other parts of the table were default for your 4c kernel.
Which app is recommended to overclocking and undervolting?
/// JellyBeanX-kernel ///
DISCLAIMER
Me, XDA-Developers.com and anyone else doesn't take any repsonsibilty for damages on your device!
Rooting your device will void your warranty!
Don't play with settings you aren't familiar with, you could burn your device!!
Click to expand...
Click to collapse
READ THIS: I added almost all important topics which have been discussed around the kernel thread to the OP and wrote this FAQ just that you guys don't have to browse through 100+ pages of the thread. READ BEFORE YOU ASK and HELP TO KEEP THIS THREAD MORE CLEAN! BUT ALSO BETTER ASK ONCE MORE BEFORE YOU MESS UP YOUR PHONE! If you find something missing in this OP/FAQ, please PM me and I will add it. Thank you!
You can find the FAQ at the bottom of this post!
This is a direct port of my RAZR-JBX-Kernel Hybrid for Motorola Razr!
This kernel is built of the Kexec Project which was initiated first by Kholk & [mbm] and finished by the STS-Dev-Team (Hashcode, Dhacker). Using this kernel will provide addtional features to your ATRIX 2.
LATEST CHANGES (for latest release and NIGHTLIES)
--> DETAILED CHANGELOG JBX-kernel Hybrid <--
Kernel Guide by Placca 1.8!!
Check the FAQ section at the bottom of this post to download it! It will make many things easier for you and help you to understand the kernel and its features!
FEATURES
JBX-Kernel Hybrid
Battery Friend toggle (a battery friendly mode)
Intelli-Plug (Kernel side replacement for msm MPDecisions) by Faux123 + patches by me (no hotplugging when screen is ON)
Dynamic Hotplug: Second core will be turned off ONLY while screen is off - independent from selected governor. (Not needed when using Intelli-Plug)
Optimized OPP Table for smooth CPU scaling
Frequencies: 100, 200, 300, 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300
Modifed Smartreflex driver (Custom Sensor for detecting n-Value).
Smartreflex Tuning Interface: Set min/max calibrated voltage
Overclocking using Live OC (mine runs stable at a maximum frequency of 1,498ghz!)
hwmod, uart, IRQs - cleanups from pre-kexec config to safe power
CPU: lower voltages for CORE and IVA. Give CORE the abbility to scale up to higher voltage if needed
Added IVA_NITROSB
Dynamic fsync control: FSYNC interval is dynamic depending on screen state (SCREEN OFF: synchronous, SCREEN ON: asynchronous)
HTC's Asynchronous Fsync port - read explanation below*
Dynamic page-writeback: Page writeback interval is dynamic depending on screen state.
Frandom v2
JRCU / Tiny RCU (currently JRCU in use)
Raised voltage limits for mpu a bit
Raised the temperature limits from 64c* to 74c* (degrees)
optimized CRC32 algorithm (better code generation)
RW Readahead dynamically depending on storage device (automatic detection of the best value)
zRAM support
GPU has 4 scaling steps and OC to 384mhz (Base freq: 102 mhz --> 154 mhz, 307 mhz, 384 mhz)
GPU C4 states / GPU Control (Governors, Frequencies)
Multicore Power Saving Mode Control
ARCH Dependant Power feature
Gamma Control
Front Buffer Delay Control (draw in x msecs on early suspend)
Screen/Display: Modified OMAPDSS for sharpness and lightning colors
OMAPDSS: Added variable clock rate and OPP - allows the screen to scale down power and voltage
lowmemkiller: Heavy modified for R/W Speed and efficient performance
ZCACHE, ZSMALLOC, XVMALLOC backported from 3.4, 3.7 and 3.10 (ZCACHE currently not in use)
Custom Voltage Support
IO-Schedulers: SIOPlus, Fifo, Row, VR, Noop, Deadline, CFQ, BFQ
ROW Scheduler is heavily tweaked to be the fastest scheduler ever!
CPU: More Governors
Deep Idle
ARM Topology
Many improvements in overall OMAP PM
SELinux permissive
GREAT performance!
battery life!
Support for Trickster Mod Kernel Control App (Download from Gplay)
*]Too much stuff to list here. See "Sources" below and check my Github
* HTC's Asynchronous Fsync and Dynamic Fsync:
Asynchronous fsync (called "afsync" or "async fsync") from HTC is ported into this kernel. By default it's enabled and dynamic fsync is disabled (and as well it isn't needed anymore).
The dynamic fsync toggle in Trickster Mod is now serving both functions - the dynamic fsync AND the asynchronous fsync! How? By default Dynamic Fsync is disabled, and Afsync is enabled. If you now enable Dynamic fsync using the toggle, Afsync will be automatically disabled, so both functions are not conflicting each other - and this way we have a working toggle for both of them.
CAUTION
This is a work in progress! Some of the current features are still not in final stat. If you are facing issues report back here and DON'T spam the threads of the rom you're using!
Be careful with some settings such like Voltage and Overclocking!!! If you aren't experienced with these things, dont play with 'em!
Click to expand...
Click to collapse
REQUIREMENTS
Rooted device
Must use a Kexec Rom (CM, AOKP, AOSP)
Recovery (BMM, SS)
REMOVE any kernel modules you used before
DEACTIVATE ANY CPU tweaks, onboot settings etc otherwise your phone may not boot!
CAUTION: The kernel needs a clean setup related to CPU tweaks / Settings, etc...Keep your device as clean as possible regarding to Tweaks, CPU special settings, etc. The Kernel brings its own CPU settings and after you can boot it succesfully, you can set it like you want!
Some roms may use CPU tweaks. This can cause issues like reboots and freezes. Check the init.d folder for any CPU related stuff and Kernel modules - then remove it. E.g. Remove any scripts which include "insmod" commands.
The best setting is to have stock CPU settings set
This kernel may not work on all roms! Check and report.
TO DO LIST
- Fix bugs
- Fix compile warnings
- More features.
INSTRUCTIONS
NOTE: CLICK here for a detailled Installation Guide (about the Aroma Installer, the features to select and more)
Download zip file from below
Reboot into recovery
Flash the kernel (BMM users: DON'T use the "Flash Kernel" Option! This is a usual zip file!)
Reboot
Download Trickster Mod App from Gplay! Read the FAQ to learn about playing with kernel features!
Enjoy!
EMERGENCY RESTORE
If you have tried a Nightly build and you phone is acting crazy, you can follow these steps:
Check the thread or ask for the latest stable kernel build
NO WIPES!
Flash the Rom (Yes, again! That one you're currently using.)
Flash Gapps
Flash Kernel
Reboot
DOWNLOAD
JBX-Kernel 3.0.8 Versions:
0.8.x ==> Android 4.2.2
1.x == > Android 4.3
2.x == > Android 4.4
JBX-Kernel 3.0.31 Versions:
3.x == > Android 4.4
TEST BUILDs
Test builds are potential prerelease builds which need some more testing before pushing to all users.
CAUTION: Should be stable mostly! But use at your own risk though!!
---> TEST BUILDS [CF] <---
XPERIMENTAL BUILDs
These builds include features without promises to work.
CAUTION: There is no promise that these version are stable/working/whatever! Use at your own risk!!
---> XPERIMENTAL Builds [Dev-Host] <---
---> XPERIMENTAL Builds [CF] <---
Click to expand...
Click to collapse
Something went wrong?
If you think you have set wrong "on-boot-values" in Trickster Mod flash this:
TRICKSTER RESET: http://dtrailer.de/kernel/trickster_reset.zip
FAQ
CAUTION: This FAQ and the whole OP, additional informations about Governors, IO Schedulers and detailed informations about the usage of Trickster Mod and this kernel can be viewed in the awesome Kernel Guide by Placca!
Kernel Guide 1.8
PDF: http://www.mediafire.com/download/7zaddcmvtxfk9ry/JBX+Kernel+Guide_v1.8.pdf
CHM: http://www.mediafire.com/download/g3ck1bf1k3a3j38/JBX+Kernel+Guide_v1.8.chm
CLICK HERE TO OPEN THE FAQ
Please check the following points if you don't know how to use the features of the kernel or you are facing any kind of issues.
INDEX
1. Kernel Features
1.1 Smartreflex (Turn ON/OFF, adjust min/max range)
1.2 Live OC (Realtime Overclocking)
1.3 Custom Voltage (EMIF)
1.4 GPU Overclock
1.5 Gamma Control
1.6 Battery Friend
1.8 IVA Overclock
1.9 DPLL Cascading (Currently not in use)
1.10 HDMI toggle
1.11 Intelli-Plug
2. Issues
1.1 How can I change the smartreflex minimum/maximum voltage
What is Smartreflex?
SR is compareable with an CPU governor but not for scaling frequencies but for voltages. That means SR has a fixed range of voltage (min/max) and calculates the optimal voltage for each CPU frequency. In example on light use of the CPU it scales down to lower voltage - on heavy use it can sclae to higher voltage. This is an efficient system to save power! Compared to EMIF which uses the hardcoded voltages it saves more power because it's variable. EMIF cannot vary between the values.
This interface has a hardcoded range of 830mV min to 1450mV max. Usually there is no need to adjust these values but irt can be usefull in example when using high overclocked frequencies above 1,5ghz! Usually SR cannot handle frequencies above 1,5ghz and I have hardcoded the maximum range of 1,45mV which should allow SR to handle it. In prior times the users had to turn off SR when OCing above 1,5ghz which causes the CPU to eat more power. But you can try around and report your results.
CAUTION: Don't raise the maximum SR voltage too high! It can burn your board = no phone anymore! I recommend to not use higher values than 1490mV! As already mentioned: THe default value should be enough!
ANd also: USUALLY THERE IS NO NEED TO CHANGE ANYTHING ON SR! IF YOU DON'T KNOW WHAT YOU'RE DOING, PLEASE LEAVE IT ALONE!
Ok, now let's see how to do this:
Turn ON/OFF SR
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. You can toggle ON/OFF SR for each component (IVA, CORE, MPU)
Usually I recommend to keep SR ON because it saves power! But in some cases when overclocking the CPU (MPU) the device could freeze - whether you OCed too much or SR couldn't handle the frequency! In this case you can try to raise the vmax value of SR a little bit (CAREFULLY!) and try again. If it sitll freezes and you're sure that you didn't OC too much, turn SR OFF at least for MPU!
Maximum Voltage
Currently there is no app which supports the feature of adjusting the SR vmax value, because I wrote this feature some days ago.
But in the next Trickster Mod version this option will be supported!
example:
# To read the current vmax value. Replace XXX with one of the following:
sc_core - for core max sr voltage
sr_iva - for iva max sr voltage
sr_mpu - for mpu max sr voltage (mpu is most related for CPU scaling)
cat /sys/kernel/debug/smartreflex/XXX/vmax
# You will get an output, e.g. for mpu = 1450000 (1450mV)
# To set a new value, do the following command (replace XXX with a value like above - BE CAREFUL! USUALLY THE DEFAULT VALUE ENOUGH AND YOU CAN LEAVE IT UNTOUCHED!)
echo XXX > /sys/kernel/debug/smartreflex/XXX/vmax
Minimum Voltage
It's easy because Trickster Mod supports it!
1. Open Trickster Mod
2. Head to the "Specific section"
3. Scroll down to "Smartreflex"
4. Below each SR component (IVA, CORE, MPU) there is displayed a value (usually 830 default) which means this is the lowest scalable voltage for this component. You can try to decrease this value for the case you want to UV a bit more - or raise it a bit for the case you think that the set range is too low and causes freezes on your device.
1.2 How do I use Live OC (Live OVerclock)?
This feature allows you to overclock the CPU in realtime. It works with a multiplier value set by the user. The default multplier value is "100", which means: No OC! If you want to raise the OC frerquency, just raise this value step by step.
FOr my device the maximum working OC value is "111" which means the maximum frequency is running at 1498mhz!
NOTE: Keep in mind that you tunr Smartreflex OFF for higher freqs than 1500mhz - or raise the maximum SR voltage range for "MPU" a little bit and test if it works.
Ok, how to use Live oC in action:
Open Trickster Mod App and swipe to the tab "Specific". There you will find something like this:
Code:
MPU OC [100]
DON'T TOUCH THE "CORE OC" SECTION, IT WILL CAUSE FREEZES!
Now slowly increase the value "100" to something higher, e.g. "105". Tap the hook in the right upper corner to confirm. To see your new set of frequencies you can now whether close and restart Trickster Mod or just use any monitoring app like Cool Tool which will show your frequencies in real time. That's it!
CAUTION: You can damage your phone forever!!!! This feature allows you to set very high frequencies (also up to 2,0ghz...) - That DOESN'T mean that your phone can run these frequencies!
If your phone freezes or crashes you have probably set too high OC - or your voltage is too low.
1.3 How do I use Custom Voltage (EMIF)?
NOTE: This only adjusts the fixed voltage! When you have Smartreflex ON it can still vary! You have to see the bigger picture: This voltage value sets the "middle point" for voltages. Smartreflex is still able to increase or decrease the voltage. When Smartreflex is OFF the CPU will stay on this voltage you set here and probably eats also more power.
How does EMIF works together with Smartreflex:
Code:
-------
| CPU |
-------
|
------------------ ------------------
|Voltage 1015 mV | ---->| SMARTREFLEX ON| = 1015mV +/- "vmax"/"vmin"
------------------ -------------------
|
--------------------
|SMARTREFLEX OFF| ----> 1015mV FIXED! No changes!
-------------------
Thi smeans if you change the voltage for a scaling step (OPP) while SR is ON, SR will adjust the voltage from this value, means: mV-Value +/- SR vmin/vmax. WHen SR is OFF it will stay on this mV as a fixed value.
How to adjust the voltage?
Well, this feature can be used with all generic apps which are supporting voltage settings. But we are prepared well, you can adjust voltages also with the "Trickster Mod App".
When you open the app, head to the tab "Specific" and below the "Live OC Section" you will find your voltage table, which looks like this:
Code:
<-->
1200 [1398]
1000 [1388]
900 [1371]
...
..
..
Now just tap the arrows in the right upper above the first voltage value and just type or tap (per direction) a value, e.g. "-25". To apply it, confirm by tapping the hook in the right upper corner of your screen. That's it, your new voltage values are now set and applied. And also mind here: If your phone freezes you porbably have set it too low.
CAUTION: NEVER SET HIGHER VOLTAGE THAN 1490mv here!!!!! Or you might damage your phone FOREVER!
This voltage is not the same like Smartreflex! But it's still voltage! Just be carefull!!
1.4 How can I use GPU OC and GPU Governor?
GPU Overclock doesn't work like Live OC! You cannot really set custom frequencies for the GPU, but you can select and set the maximum frequency from a hardcoded range!
For the GPU there are the following available frequencies:
154mhz (FIXED!)
307mhz
384mhz
416mhz
The minimum frequency of 154 is FIXED! This means you cannot change it because the GPU needs a minimum speed to run with. But the kernel allows you to select the maximum speed. This can be usefull for playing games and also for saving power . In example when not playing games you don't need the GPU to run at 416mhz! Set it to 307mhz in this case and save power.
When you open Trcikster Mod and head to the "specific section tab", you will find "GPU MAX FREQUENCY" and it's currently set maximum frequency. Tap on it to select your preferred one:
- 154 Mhz
- 307 MHz
- 384 MHz
That's it. The new setting will be your new maximum GPU frequency.
Below there's another option called "GPU Governor". Just tap on it and select your prefered one.
NOTE: If you want to track current GPU frequencies and watch governor's behavior, just switch to Trickster's "Informations" - Tab and watch the frequencies clock.
1.5 How can I use Gamma Control?
What is gamma? The gamma setting sets the color range for the screen. You can compare it to the contrast. We all know that the touchscreen eats most of the power compaerd to all other components in a smartphone! A lower brightness causes less power consumption and a lower gamma or contrast range alos helps a little bit to save power.
In this kernel you can choose from a range of "5 - 10" while "5" is very bright while "10" is very dark. The default setting is "5" BUT CAUTION: Trickster Mod will display a range of "0" to "10" and the default setting will be shown as "0". This is caused by the fact that this feature was ported from the Gnex device where you can choose from a higher range. The only sideeffect is that the values "0" - "5" won't show any difference.
How to set the gamma value?
Well, once again open Trickster Mod and swipe to the tab on the right end. Just select your preferred value by using the slider.
Alternately you can use sysfs by terminal or adb:
OMAP Gamma interface:
echo i > /sys/devices/platform/omapdss/manager0/gamma
Replace i with 0-10 of your choice.
1.6 What is "Battery Friend and how to use it?
Battery Friend is a simple toggle (ON/OFF) which sets your device into a battery friendly mode without the need to play with all settings in Trickster Mod /sysfs until you find a good setting. In fact it does the job for you.
What does it affect?
NOTE: Doesn't lock anyx frequencies anymore!
locks dynamic Fsync enabled
locks Fsync disabled
Doesn't allow any OC (Live OC will not have any effect, Core OC is not allowed in this kernel)
Increases the dirty ratio interval to 90% (starts working at this value)
Enables Dynamic Hotplug: This doesn't allow hotplugging during device is active - and it will always turn CPU1 OFF during suspend! It also prevents from conflicts when user uses a hotplug governor (which isn't a good idea though) - but hotplug governors are causing higher battery drain!
Dynamic Page-writeback always enabled
How to toggle Battery Friend:
For now the only way is via terminal, adb shell or root explorer (text editor)
For terminal and adb:
Code:
echo 1 > sys/kernel/battery_friend/battery_friend_active /* Enable */
echo 0 > sys/kernel/battery_friend/battery_friend_active /* Disable */
For Root Explorer
Open Root Explorer
Navigate to sys/kernel/battery_friend/
Open "battery_friend_active" with Text Editor
Change "0" to "1" and safe the file to enable
Change "1" to "0" and safe the file to disable
1.7 Suspend Governor Control (CURRENTLY DISABLED)
Suspend Governor Control is a kernel module written by me. You can use it to set your preferred Screen-Off-governor.
For now it's only supported by sysfs (Trickster Mod will support all my current and upcoming features as soon as it gets updated with its new UI mode!
How to set suspend governor
Open a terminal or use adb shell
Code:
su
echo "x" > /sys/kernel/suspend_gov/suspend_gov
Replace x with one of these values:
0 = Ondemand
1 = Ktoonservative
2 = Conservative
3 = OndemandX
NOTE: No matter what governor you use for suspend mode, if Battery Friend is enabled the second core will be turned off during suspend!
1.8 IVA Overclock
What is IVA OC?
IVA OPPs are controlling the CPU load for sound events. It could be useful (in some cases) when you get sound related laggs. Just set the maximum frequency to highspeed. This will allow more CPU power for sound events but also will cause higher battery consumption.
How to use IVA OC?
If you want to check the current IVA frequency. Just type in Terminal or ADB:
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/iva_clock
You will get an output like this:
Code:
132 Mhz
2. You can whether enable IVA highspeed: 130 - 430 Mhz ["1"] or enable IVA normal speed: 130 - 332 Mhz ["0"]
320 Mhz max: echo "0" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
430 Mhz max: echo "1" > sys/devices/system/cpu/cpu0/cpufreq/iva_freq_oc
1.9 DPLL Cascading
DPLL: Davis–Putnam–Logemann–Loveland (DPLL) algorithm
To get more info about this please see wiki
But to sum it up shortly: It helps to use/stream media (music) in a low power mode.
NOTE: DPLL Cascading will be available to be switched easily via Trickster Mod App soon!
How to switch DPLL?
DPLL is ENABLED by default!
Open Trickster Mod -> Speicific Tab --> DPLL (soon)
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/dpll/dpll_active
Turn on:
Code:
echo 1 > /sys/kernel/dpll/dpll_active
1.10 HDMI toggle
Some users are facing a RAZR-sepcific problem: HDMI cable is detected, even though there is no cable plugged!
Therefor I included a toggle to switch HDMI wether ON or OFF. Additinally there's an init.d script included within the AROMA Installer you can select during the installation of JBX-Kernel.
To enable/disable HDMI on-the-fy:
sysfs:
Turn off:
Code:
echo 0 > /sys/kernel/hdmi/hdmi_active
Turn on:
Code:
echo 1 > /sys/kernel/hdmi/hdmi_active
1.11 Intelli-Plug
For intelli-plug hotplugging is now only allowed when the device enters sleep.
To enable hotplugging universally just change the value of the following entry whether to 1 (on) or 0 (off):
Code:
sys/module/intelli-plug/parameters/int_hotplug
*Unfortunately I don't have enough space in the OP to write all this into the FAQ, that's why the I only added the sysfs path, but the description is simply here
2. If anyone has the following issues:
Issue
Media Process FC
No SD-Card in File Explorer
My CPU Settings (frequencies, etc) won't be saved (it sets itself back to Kernel default after screen off)
My phone freezes/reboots always when I try to set options in Trickster Mod
The device is lagging very hard
Solution
Media FC: Open App settings, head to "Download Manager" and "Media Storage" and hit the "delete data" button. Reboot. Now it shouldn't give any FCs anymore and after a little bit of waiting it will find all Media (Pictures, Videos, etc..)
No SD-Card: Reboot into recovery, go to "Mounts & Storage", tick "mount int" or "mount ext".
USB: Make sure the screen is ON while plugging the cable in.
CPU Settings: This is a bug which cannot be solved at the moment. Temporary solution: In Trickster Mod just activate the "Frequency Lock" and your settings will persist.
Trickster Mod:: Open App settings, Trickster Mod and select "uninstal updates". Now it should work.
Crashes, Freezes, lagging, something doesn't work, etc
There are too many reasons which could cause crashes! So here is a checklist for you to look for. Check each point and try the following workaround:
- Your rom has CPU tweaks (e.g. Kernel modules, init.d folder, etc)
- You have set custom CPU settings (e.g. custom frequencies with apps like No-Frills CPU Control, Set-CPU, Antutu, etc...)
- You have undervolted too low
- You have overclocked too high
- You have applied higher "Core OC" value in Trickster Mod App
- You are running any other kernel tweaks which are regarding to the CPU and/or performance (e.g. Kernel modules by Whirleyes eventually set by init.d, etc..)
- After setting some settings (e.g. in Trickster Mod) your device doesn't boot anymore
- adb doesn't work / shows only "device offline"
- You are facing hard lagging
If any point here matches your setting, please revert from it:
- Remove any CPU init.d script from /System/etc/init.d
- Uninstall any CPU controling app (e.g. Set-CPU, No-Frills, etc..)
- Remove all extra kernel modules from system/lib/modules (e.g. cpu_control.ko, cpufreq_smartass2.ko, etc..)
- Unset any custom settings from any other kernel / CPU - tweaking app which is NOT Trickster Mod
- Maybe your governor causes issues. Hotplug is know for bugs at the moment...I'm going to fix it..
- NEVER set your CPU Settings (e.g. in Trickster Mod App) on boot!!!! - before you aren't sure that your settings are safe!!!
- You may flash the kernel again after reverting related settings
- to make adb work / show device online, download latest SDK platform-tools and confirm access on device (4.2 security feature of Android)
- Don't use any task killers, memory killers, seeder apps! They may conflict with the kernel/Rom settings.
If none of these suggestions work for you your rom may be incompatible. Please report it here that I can add the rom to the list of imcompatible roms
If you have any issue, please read this:
First check:
- is it really a kernel issue?
- did I see this bug with the roms original kernel?
- what are the people in the rom thread saying?
- what are the people in the kernel thread saying?
- can I find this issue on a bug list?
- how about my settings? Is it my fault it crashed?
- can I find something useful in the kernel FAQ?
- Is it maybe a well known issue and can be solved
withing seconds? Just like wifical.sh?
- Where to repeat that issue? Rom or kernel?
I know it's sometimes difficult to track the issues, and we can't know for sure if it's caused by the rom or by the kernel, but if you try at least to get some information you might find an answer sometimes. If you are able to understand logs, you may report whatever you find.
All this helps to keep the threads more clear. Thank you.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
DONATE
If you like my work and want to support me, I'd enjoy a little beer or coffee. You can find my beer mug below my username
SOURCE
3.0.8 Base:
JBX-Kernel 4.2.2
JBX-Kernel 4.3
CREDITS
Kholk & [mbm] - Kexec inital Release
Hashcode & Dhacker - Making Kexec stable and initiating compatible kernels
Motorola - 3.0.8 Kernel Source
Surdu_Petru - Sharing Knowledge and helping with problems
nithubhaskar - Hints and answering my questions
Ezekeel, Imoseyon - Custom Voltage, Live OC, Temp Control, Gamma Control Source Code
faux123 - Some features, like Intelli-Plug, Intellidemand, Intelliactive
bigeyes0x0 - Trickster Mod App
Team Trickster - Great support and adding new features from my suggestions
Placca - Awesome kernel guide
Click to expand...
Click to collapse
3.0.8 / 3.0.31
There is the classic JBX 3.0.8 Kernel (a hybrid of 3.0.8, 3.0.21, 3.4, 3.7, 3.8, 3.10, 3.11, mostly backports from these versions)
And now there is also JBX 3.0.31 (also a hybrdig including the above backports, but also from 3.0.101)
I won't list the whole version history, too long
3.0.31 first TEST-BUILD now coming!
- also reserved -
And it arrives...
Many thanks man...
Really appreciate you doing this...
---------------------------------------------------
May the -Mass times Acceleration-be with You...
I need the internal storage mount points from someone with stock kernel, please. I saw something about mmcblk0 - int ? Please anyone check the /mnt partitions and tell where the internal and external sdcards are mounted. thx
Edit: nevermind, I didn't know this device doesn't include an internal storage. Now I need to know if USB mount works on Devesh's Rom ports.
Used Stock ICS Based ROM on System 1 with BMM , and Mobile Terminal .
hope its ok .
Wow !
I see some awesomeness coming to our A2s *Respect*
All is set up. Everything works, so I will now build the first test kernel for you guys.
First test kernel in NIGHTLIES folder. Please test and report. Keep in mind that you have to be on one of Devesh's Rom Ports!
Edit: Sorry, forgot something! Please wait 5 mins...
Edit: Done!
Dirty flashed, liquid smooth slot 6 oc1350 running good.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2
JB leak?
Sorry for asking dummy question. Can i flash it on the JB leak because we still need JB leak for installing kexec room right? So if I want to try what possibly would happen?
dtrail1 said:
First test kernel in NIGHTLIES folder. Please test and report. Keep in mind that you have to be on one of Devesh's Rom Ports!
Edit: Sorry, forgot something! Please wait 5 mins...
Edit: Done!
Click to expand...
Click to collapse
Man! You really are damn energetic and enthusiastic, aren't you? Really glad to have you around.. Thanks again.. :thumbup:
Sent from my MB865 using Tapatalk 2
amynjimmy said:
Dirty flashed, liquid smooth slot 6 oc1350 running good.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2
Click to expand...
Click to collapse
How did you OC ? i just can't get the phone to Overclock properly with this trickster app ..
afeeq said:
Sorry for asking dummy question. Can i flash it on the JB leak because we still need JB leak for installing kexec room right? So if I want to try what possibly would happen?
Click to expand...
Click to collapse
You cannot. It needs a kexec Rom. So flash it first
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.6 - Tapatalk4
New nightly online with fixed CPU and live oc! @Brantuck84
Edit: sorry, wrong thread!
But ne nighty comes here too in 5 mins
M.o.t.o.r.o.l.a.R.a.z.r - JBX-Kernel 0.6 - Tapatalk4
So with the current version there is a bug with OC ? ( i don't see TEST2 for Atrix like with the Razr version).
Yes, device starts lagging when OC too high (over oc value of ~107). But new release comes with fixes - OC up to 1,5ghz possible without any problems (Mine crashes when OC higher than 1,498mhz, each silicon is different).
I think I will push it as a release (not NIGHLTY) - only thing left to be fixed is the random black screen while booting. But that's not that important as long as the kernel works well when booted successful.
Edit. done!
Great can't wait to boot 1498mz!
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2
Not boot, just set it after boot - and if you're sure you have it running stable, set the "Apply on boot" function in Trickster Mod with a delay of ~90 sec - just to be safe!
RELEASE for Atrix 2
CHANGELOG JBX-kernel 0.6 Hybrid
This version includes fixes for performance and stability
CPU: Set bootup policy to static frequency
CPU: Revert some accidently failed cleanups
CPU: Reset CPU delay on tickless
CPU: Changed margins and sr settings for some OPPs
CPU: Default trimmed dpll mpu
CPU: Added Uilization
SR: Fixed SR return value check
Decreased RCZ_CPU_STALL_TIMEOUT to 60
emif, lpddr: Re-added 466mhz timings
USB: Change ehci performance mode to static scaling freq
Disabled PM_DEBUG for performance
Reduced RW READAHEAD Buffer to 1024
OMAP, CPU, RCU: Re-enabled watchdog
Universal performance invreased
dtrail1 said:
Not boot, just set it after boot - and if you're sure you have it running stable, set the "Apply on boot" function in Trickster Mod with a delay of ~90 sec - just to be safe!
RELEASE for Atrix 2
CHANGELOG JBX-kernel 0.6 Hybrid
This version includes fixes for performance and stability
CPU: Set bootup policy to static frequency
CPU: Revert some accidently failed cleanups
CPU: Reset CPU delay on tickless
CPU: Changed margins and sr settings for some OPPs
CPU: Default trimmed dpll mpu
CPU: Added Uilization
SR: Fixed SR return value check
Decreased RCZ_CPU_STALL_TIMEOUT to 60
emif, lpddr: Re-added 466mhz timings
USB: Change ehci performance mode to static scaling freq
Disabled PM_DEBUG for performance
Reduced RW READAHEAD Buffer to 1024
OMAP, CPU, RCU: Re-enabled watchdog
Universal performance invreased
Click to expand...
Click to collapse
Is his gonna allow then use of 1498 then.
MB865/ATT/BMM
1. Stock 4.0.4
2. Miui 4.0.4
3. Pac man 4.2.2 (6/3)nonkexec
4. Mt
5. MT
6. Cm 10.1 4.2.2 (6/7)kexec
Can I get a wohooo for the A2