[KERNEL] [Dec 19] ElementalX v3.2 | OTG | S2W | OC | UV | ZRAM

[KERNEL] [Dec 19] ElementalX v3.2 | OTG | S2W | OC | UV | ZRAM - AT&T, Rogers HTC One X, Telstra One XL

Important Notes (please read!)
Jelly Bean
This kernel does not work with Jelly Bean. You need this: http://forum.xda-developers.com/showthread.php?t=2061577
Make sure you clean up after installing other stuff
You should check your /etc/init.d/ folder to see if there is anything from previous installations that might interfere with this kernel.
Configuration
There is now a config file and init script where you can change settings for GPU frequency, sweep2wake, zram and intellidemand. The settings can be changed by editing /etc/elementalx.conf and rebooting. Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root.
There is no need to edit /etc/init.d/99elementalx. All settings are configured in /etc/elementalx.conf.
If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file.
Please check to see if any /etc/init.d scripts or apps are interfering with your settings If you're on ViperXL, make sure your settings in Venom Tweaks are the same as the ones in /etc/elementalx.conf
CPU frequencies
No CPU apps are necessary. By default, your CPU will run at the max frequency chosen during installation. Minimum frequency will be 192MHz and governor will be intellidemand. If you want to change CPU frequency, I recommend No-Frills CPU control with the setting "Prevent changes from other apps" checked. This will ensure your minimum stays at 192MHz. As of version 3.1, CPU1 frequencies will stick.
CPU voltages
CPU voltages can be changed with Venom Tweaks, Kernel Tuner or System Tuner.
In version 3.2, there are five voltage ranges to choose from in the installer. I recommend the stock voltage (850-1300mV) to start. If you want to undervolt, you'll need to test to make sure it's stable. Previous versions of ElementalX used undervolting (800-1300mV) as default.
GPU frequencies
Maximum GPU frequencies can now be set on the fly. At the moment, Kernel Tuner does not show the correct frequencies for our device. You have to change them manually in sysfs or set GPU overclock in /etc/elementalx.conf
The sysfs entries for the GPU are in the following locations:
3D Graphics:
/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0
2D Graphics:
/sys/devices/platform/kgsl-2d0.0/kgsl/kgsl-2d0
/sys/devices/platform/kgsl-2d1.1/kgsl/kgsl-2d0
gpuclk shows the current frequency (it scales according to usage just like the CPU)
max_gpuclk shows the maximum frequency, you can edit this to limit the max frequency for GPU overclocking on the fly
gputime_in_state shows the amount of time the GPU has used each frequency. You can see what frequencies are available here
Installing a new ROM
If you install a new ROM, it will overwrite /etc/init.d/99elementalx and /etc/elementalx.conf. The kernel will run perfectly fine without these files, but will revert to default settings (S2W enabled, zRam disabled, stock GPU speed) . To get the files back, reinstall the kernel. Or, before you install a new ROM, save the files to your sdcard and replace them after installation.
Using OTG (USB Host Mode):
1. You need an OTG cable to hook up perhipherals!
2. If you connect a mouse or keyboard via OTG cable, it will just work.
3. At this time, most ROMs do not mount usb storage automatically. You will need to install StickMount or a similar app. Google for the StickMount apk (Play store says it's incompatible, but it's not). ViperXL 2.3.
You can also mount usb storage manually by typing something like the following into the terminal:
su
mkdir /mnt/usb
mount -t vfat /dev/block/sda1 /mnt/usb
4. Please refer to the OTG discussion thread in the General Section for details on how to use OTG.
http://forum.xda-developers.com/showthread.php?t=1893960
What is zRam
zRam creates a compressed block device in RAM that is used as swap. Although it claims some of your RAM as swap, everything written to swap is compressed. This increases the apparent memory available to the system and helps with multitasking. Swap files on disk are very slow, but with zRam the swap is on RAM so it can be read as quickly as regular memory. Even though the data need to be decompressed, modern CPUs can decompress quicker than if it had to be to read from disk. The penalty is cpu usage, which could drain battery; however, this is likely negligable in daily use. I didn't enable this by default because not everyone will want it. This is for heavy multitaskers and will allow you to quickly switch between more apps and have more tabs open in your browser without refreshes.
zRam is disabled by default. If you want to enable it, edit /etc/elementalx.conf
change ZRAM=0 to ZRAM=1 and reboot.
You can check if zRam is working by typing the command "free" into the terminal. You should see the total used and free swap. If these are all 0, then zRam is not enabled. Please ensure that other apps are not changing your minfrees, zRam works best with low minfrees and high swappiness.
Sweep2Wake
Sweep2Wake is enabled by default. It allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). There are now options for sweep2wake/sweep2sleep, sweep2sleep only, and disabled. Sweep2sleep only should be better on battery.
If you want to have sweep2sleep only or disable completely, edit /etc/elementalx.conf
Intellidemand
The powersave_bias setting for the Intellidemand governor can be changed in /etc/elementalx.conf. The default is 0. You can get better battery life, at the expense of speed, by setting this to a higher number, like 60.
Underclock to 192MHz not sticking
By default, this kernel sets the CPU's lowest frequency to 192MHz and sets read-only permissions on /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq. If you don't do anything, it will always stay at 192MHz.
Many overclocking apps will change the permissions of /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq to read/write. When the permissions are changed to read/write, the lowest frequency will change to 384MHz as soon as you use your network (either wifi or 3G or LTE). This is due to some HTC software bs. In order to stop the minimum frequency from changing to 384MHz, make sure the permissions on /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq remain set to read only.
If you want to change CPU frequencies, I recommend using No-frills CPU Control with the setting "Prevent changes from other apps" checked. This will keep those permissions set to read-only and your underclock to 192MHz will stick.
Game Controllers
Support for USB gamepads and joysticks was added to v2.0. The best way to know if yours works is to hook it up. As soon as I hooked up my generic usb gamepad (via the OTG cable), I was able to flip between homescreens and play Beach Buggy Blitz.
CHANGELOG:
December 19, 2012 - ElementalX-v3.2
-add voltage options to installer
-fix installer (automatically wipe Dalvik and remove reboot checkbox)
-code clean up
-make intellidemand more responsive
-adjust l2 cache frequency for stability
-change swappiness to 80 when zram enabled
December 7, 2012 - ElementalX-v3.1
-new config file /etc/elementalx.conf
-GPU frequency selectable in sysfs
-GPU overclock option in config file
-fixed CPU1 max frequency not sticking
-max CPU frequency selectable in Aroma installer
-increase refresh rate for mhl output
-autodetect devices that need extra cpu voltage
-fixed voltage control bug from v3.0
-add modules to installer
-automatically install camera libs
November 27, 2012 - ElementalX-v3.0
-Rebased to 2.41
-optimized boot
-thermald fix
-revert dimmed capacitive buttons
-GPU overclock option extended to all versions
-add camera libraries to installer
-xz compression
-AROMA installer
-more zram tweaks
-memory tweaks
-re-enable fsync
-default voltage option in init script
November 18, 2012 - ElementalX-v2.1
-fix cpu voltage interface
-use Google snappy compression for zRam
-add fudgeswap
-add Ultimate version
-GPU overclock in Ultimate version
-add sweep2sleep only option
November 9, 2012 - ElementalX-v2.0
-made 1.7 and 2 GHz versions
-add sweep to wake
-add gamepad and joystick support
-add voltage control via sysfs
-add zram support (disabled by default)
-disabled fsync
November 4, 2012 - ElementalX-v1.3
-attempt to fix 192MHz min freq not sticking
-remove lowmemorykiller tweaks
November 3, 2012 - ElementalX-v1.2
-changed name to ElementalX from flar2-performance
-disabled gentle_fair_sleepers
-made intellidemand the default governor
-made 192MHz the default minimum cpu frequency
-override init.qcom.post_boot.sh
-adjust lowmemorykiller for better multitasking
November 2, 2012 - flar2-performance-v1.1
-now based on 2.34 kernel
-defaults to simple i/o scheduler
November 1, 2012 - flar2-performance-v1.0
-self powered OTG
-ntfs r/w support
-overclock to 2GHz
-slight undervolt
-intellidemand governor
-simple i/o scheduler
-dimmed capacitive buttons
-readahead buffer tweak
-init.d support
November 1, 2012 - flar2-stock-v1.0
-now based on 2.34 kernel
-remove overclock
-remove undervolt
October 28, 2012 - flar2-OTG1 (beta)
-self powered OTG
-ntfs r/w support
-oc to 1.6 GHz
-undervolt
-init.d support
Click to expand...
Click to collapse
SOURCE:
kernel source code: http://goo.gl/8KXH9

Interesting, would love to hear what everyone uses this for.
Sent from my HTC One X using Tapatalk 2

So far so good. Flashed on top of Viper latest instead of the Beastmode kernel I've been running. using the 2Ghz setup and setting it to 1.7ghz with Setcpu and underclock.
5705 benchmark on Quadrant with 1.7ghz and intellidemand/deadline.
Pretty nice.
Thanks TS

Thanks for more choices.
I'll give it a go when I flash back to CRV later today.
WR
Sent from my One X

Awesome!!!

techlogik said:
So far so good. Flashed on top of Viper latest instead of the Beastmode kernel I've been running. using the 2Ghz setup and setting it to 1.7ghz with Setcpu and underclock.
5705 benchmark on Quadrant with 1.7ghz and intellidemand/deadline.
Pretty nice.
Thanks TS
Click to expand...
Click to collapse
'
Do you have the supply the power for OTG to work? or does it pull power from the board? and if so, wouldn't that burn out the mainboard in the phone?

r1sky said:
'
Do you have the supply the power for OTG to work? or does it pull power from the board? and if so, wouldn't that burn out the mainboard in the phone?
Click to expand...
Click to collapse
English please, have no idea what your are talking about?

oh nice to see new kernels popping up. :good::good:

I pluged in a usb card reader, but phone still asking for an external power source

r1sky said:
'
Do you have the supply the power for OTG to work? or does it pull power from the board? and if so, wouldn't that burn out the mainboard in the phone?
Click to expand...
Click to collapse
No, you don't have to supply the power, the board is capable of providing 5V.

caviera said:
I pluged in a usb card reader, but phone still asking for an external power source
Click to expand...
Click to collapse
Are you sure it's not a message about not being able to charge when you plug in an otg cable? If that's what it is you can ignore it. My card reader works fine. Please verify that you are actually running this kernel.

Where do I go on root explorer to see if it works? Thanks!
Sent from my HTC One XL using xda app-developers app

^^You need to install Stickmount or similar app to mount usb storage in Sense.
You could also mount it manually. Write something like this in the terminal:
su
mkdir /mnt/usb
mount -t vfat /dev/block/sda1 /mnt/usb

Edit: USB Host Controller works
Sent from my HTC One XL using xda app-developers app

Stock version is now as close to stock as possible, only adds self powered OTG and NTFS read/write support.

Very nice to see more kernels.
Sent from my Nocturnalized One XL using Forum Runner

I just ordered an USB OTG adapter on amazon for $1.40.. Can't wait to start using this on my phone!

I've only tested these kernels with CRV and Viper. It would be nice to hear if anyone has feedback using other ROMS.
I realize a lot of people don't have otg cables (yet), but any feedback about your experiences would be helpful.
Also, I will post a minor update to the performance kernel either tonight or tomorrow night.

flar2 said:
I've only tested these kernels with CRV and Viper. It would be nice to hear if anyone has feedback using other ROMS.
I realize a lot of people don't have otg cables (yet), but any feedback about your experiences would be helpful.
Also, I will post a minor update to the performance kernel either tonight or tomorrow night.
Click to expand...
Click to collapse
I'm on Calkulin's ROM.. Seem fine to me
Sent from my HTC One XL using xda app-developers app

Running CR4.5. I can confirm that this works just fine, though I had to sideload Stickmount to get it to see the flash drive.
I can also confirm from experience with my N7 that OTG+TWRP makes recovering from stupid mistakes a hell of a lot easier.

Related

[KERNEL] [Sep 26] ElementalX-8.3.2 | OC | UV | S2W | DT2W | BLN | Sense 5

{
"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"
}
Kernel for Sense-based ROMs
LATEST STABLE RELEASE: ElementalX-8.3.2 (Sept 26, 2013)
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
FEATURES:
based on HTC Sense 5 Android 4.2.2 source code
Aroma installer
choose CPU optimization level: vanilla, elementalx, or ultra
optimized for extended battery life
overclocking options
choose max screen off frequency
user voltage control
choose voltage profile in installer
GPU overclocking
button light notification
sweep2wake
doubletap2wake
pocket detection (prevents accidental wakes in pocket)
/system writable
force fastcharge
NTFS r/w support
exFAT support
i/o schedulers: FIOPS (default), SIO
option to disable fsync
faux sound control support
increased refresh rate for HDMI output via MHL adapter
optimized -O3 linaro 4.7
DOWNLOAD
Sense 5 Android 4.2.2
ElementalX-8.3.2
mirror: http://www.androidfilehost.com/?fid=23212708291674213
If you experience cell signal drops and reboots, you need the latest firmware and matching radio.
Earlier versions
ElementalX-7.0.2
Previous releases:
ElementalX-6.7
ElementalX-6.6
ElementalX-6.5
ElementalX-6.4
ElementalX-5.4
ElementalX-5.2
ElementalX-JB-v2.5: http://goo.gl/I9DHA
Please hit the Thanks button if you download this
If you really like it, please consider buying me a beer
Actually, I won't spend it on beer. I'm saving it all up to buy my next device
Thanks to those who have donated!
INSTALLATION
1. Install zip from TWRP Recovery
2. Follow the instructions, if you don't know what to do, use the preselected option
3. Reboot!
S-OFF required!
First boot will take a while. Let it load all the way, then let it settle in for a few minutes, then reboot again.
FAQ
Q. I installed ElementalX and now I'm stuck in a bootloop
A. Go to this thread and get S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Q. I installed ElementalX and now my phone is laggy/sdcard is corrupt/camera doesn't work/other random problem not related to the kernel
A. Please don't fill up my thread with vague complaints. As long as you pick reasonable voltage and frequency settings, this kernel is 100% stable and problem free. I know what I'm doing and I don't do anything to the kernel that will mess up your phone. If you have problems, it's because of something else you've done. If you think you've found a bug with the kernel, please include dmesg output or /proc/last_kmsg
Q. I installed ElementalX and I get random reboots
A. If the reboots occur when your phone is idle, increase your voltage or increase your max screen off frequency. If the reboots occur while you are using the device, scale back your overclock and/or increase voltage. If all else fails, choose the vanilla option.
Q. What if I am still having problems?
A. If you are having problems the key to getting help is to provide appropriate detail.
Number 1: Description of your issue
I'm most cases people in this thread will try and help you. The more information, the better chance someone in the thread will be able to help you.
If you can't be helped by one of the experienced ElementalX users it would generally be referred to the dev
Number 2: Details of installation options e.g.
- ElementalX 6.5 Vanilla
- CPU Max: 1.7ghz
- CPU Min: 384mhz
- GPU OC: On
- S2W: On
- fsync: On
- Zram: On
Number 3: Logs, refer to the following details on gathering appropriate logs
In the below example the adb path is c:adb
Open command prompt type cd c:adb
The following two commands can be used to provide logs to help troubleshoot slowdown/freezing issues.
adb shell top -n 1 > c:top.txt
adb shell dmesg > c:dmesg.txt
If you experience a non-user initiated reboot please follow the below steps to provide last_kmesg
* After reboot issue is encountered boot to recovery
* use the file manager to copy /proc/last_kmsg to sdcard/download/
* mount usb and copy it to your computer
* zip it
* post it with details of your issue in this thread.
* restore your nandroid and boot into your last stable config
Click to expand...
Click to collapse
Special thanks:
zarboz and Sbryan12144 for porting S2W to our device
jrior001 for CPU1 fix
backfromthestorm for fstrim
xHausx and amarullz for installer stuff
anarchychris for FAQ and troubleshooting
tbalden for BLN

NOTES:
Configuration
Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
The settings can be changed by editing /etc/elementalx.conf and rebooting. Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root.
There is no need to edit /etc/init.d/99elementalx. All settings are configured in /etc/elementalx.conf.
If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file.
Please check to see if any /etc/init.d scripts or apps are interfering with your settings If you're on ViperXL, make sure your settings in Venom Tweaks are the same as the ones in /etc/elementalx.conf (for example, sweep2wake settings)
Kernel Tuner
You don't need Kernel Tuner because the ElementalX installer sets everything up automatically, but if you want to check or change settings, Kernel Tuner is recommended. Just be aware that Kernel Tuner is set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.
Venom Tweaks force close
If Venom Tweaks closes when you try to access the CPU tab, go to Settings->Apps->Venom Tweaks and push the Clear Data button. This should fix the problem.
CPU Optimization
Vanilla: stock voltages, stock l2 cache frequency, stock bus bandwidth
ElementlaX: increases l2 cache frequency and bus bandwidth, allows you to choose voltage level in installer
Ultra: increases l2 cache frequency and bus bandwidth even more. May cause instability, please test thoroughly for stability if you use this option.
Overclocking
Overclocking (underclocking) is optional. Whatever frequency you chose in the installer will be set at boot for both CPUs. Frequencies can be changed any time using apps like No Frills or Kernel Tuner. WARNING: not all devices can handle overclocking. The stock maximum CPU frequency is 1.5GHz. In versions of the kernel prior to 6.4, the frequencies were labeled wrong so you won't be able to overclock as high with version 6.4+.
CPU voltages
CPU voltages can be changed with Venom Tweaks, Kernel Tuner or System Tuner. Be careful, lowering voltages could cause instability. If you have stability problems even at the highest voltages, try the vanilla version
Minimum CPU frequency
Sets the minimum CPU scaling frequency. 192MHz is the recommended default and should work fine on the vast majority of devices. The 384MHz option is available for devices that experience random reboots while the device is idle. It is recommended that you try increasing the minimum voltage by 25mV before changing the minimum CPU frequency.
Max screen off frequency
This sets the highest CPU frequency available while the screen is off. It is recommended to disable this for stability. Also, do not set this to 192MHz or 384MHz, as many devices experience random reboots at these frequencies. The default is 486MHz, which should be safe for most devices. If you experience random reboots while the device is asleep, set this to a higher frequency. This setting can be changed in /etc/elementalx.conf or using an app like Venom Tweaks.
GPU frequencies
3D GPU: 480 (overclocked) or 400 (stock)
2D GPU: 266 (overclocked) or 200 (stock)
Governors
Intellidemand is the default CPU governor. There are other governors included, however, intellidemend is recommended for best balance of battery life and performance.
Installing a new ROM
If you install a new ROM, it will overwrite /etc/init.d/99elementalx and /etc/elementalx.conf. The kernel will run perfectly fine without these files, but you will lose your settings and certain features.
Sweep2Wake
Sweep2wake (S2W) allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). There are now options for sweep2wake/sweep2sleep, sweep2sleep only, and disabled. If you use ViperXL, make sure to enable sweep2wake in Venom Tweaks.
/sys/android_touch/sweep2wake
0=disabled
1=enable sweep2wake + sweep2sleep
2=enable sweep2sleep only
DoubleTap2Wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping in the bottom inch or so of the screen, including the capacitive buttons. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/doubletap2wake
0=disabled
1=enable doubletap2wake
Pocket Detection
Pocket detection protects against accidental wakes while S2W, DT2W or L2W are enabled and the phone is in your pocket. Pocket detection uses the proximity sensor. A few people have a problem with their proximity sensor that makes DT2W not work, so I've made an option to disable pocket detection. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/pocket_detect
0=disabled
1=enable pocket detection
Button Light Notification
With Button Light Notification (BLN), the capacitive buttons will blink on and off when you have a new notification. As soon as the screen comes on, BLN is canceled and the lights will no longer blink until you have another notification. Please note that if you have your screen set to turn on when a message arrives, you will not see the buttons blinking because once the screen comes on, the button light notification is canceled. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/class/leds/button-backlight/bln
0 = disabled
1 = BLN enabled
What is zRam
zRam creates a compressed block device in RAM that is used as swap. Although it claims some of your RAM as swap, everything written to swap is compressed. This increases the apparent memory available to the system and helps with multitasking. Swap files on disk are very slow, but with zRam the swap is on RAM so it can be read as quickly as regular memory. Even though the data need to be decompressed, modern CPUs can decompress quicker than if it had to be to read from disk. The penalty is cpu usage, which could drain battery; however, this is likely negligable in daily use. I didn't enable this by default because not everyone will want it. This is for heavy multitaskers and will allow you to quickly switch between more apps and have more tabs open in your browser without refreshes.
zRam is disabled by default. If you want to enable it, edit /etc/elementalx.conf
change ZRAM=0 to ZRAM=1 and reboot.
You can check if zRam is working by typing the command "free" into the terminal. You should see the total used and free swap. If these are all 0, then zRam is not enabled. Please ensure that other apps are not changing your minfrees, zRam works best with low minfrees and high swappiness.
NTFS support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS filesystem. You will need Stickmount or a similar app, HTC Sense+ won't detect NTFS.
Enable/disable fsync
Disabling fsync can increase filesystem performance. However, there is a small risk of data loss if the system suddenly crashes. If you can't afford to lose data, keep fsync enabled. Many custom kernel disable fsync, I leave it enabled by default for safety reasons.
XBox controller support
There is an experimental module that supports XBox gamepads, however, some people have reported that it draws too much power and doesn't work. I've suggested trying a powered USB hub, but still not sure if it works.
CHANGELOG:
Sept 26, 2013 - ElementalX-8.3.2
-fix fsync setting
-fix BLN setting
-battery saving and speed tweaks
Sept 22, 2013 - ElementalX-8.2
-compile with linaro 4.7
-fix touches registering during calls with sweep2wake
-update installer
-start fresh with HTC 4.2.2 source
-remove zram
-remove 192 min freq
-default governor is ondemand
-default i/o scheduler is fiops
August 18, 2013 - ElementalX-7.0.2
-fix installer
-fix init.d support
August 17, 2013 - ElementalX-7.0.1
-fix installer
August 16, 2013 - ElementalX-7.0
-remove OTG whitelist to enable more devices
-build with Linaro 4.8
-add TCP congestion control algorithms
-enable Netfilter XT target log support
-update installer
May 26, 2013 - ElementalX-6.7
-dt2w works with buttons
-no pocket detection when screen is on
-fix fm radio
-revert autogroup: group by current UID
May 17, 2013 - ElementalX-6.6
-add DoubleTap2Wake (DT2W)
-add button light notification (BLN)
-enable/disable pocket detection
-pocket detection (prevent accidental wakes with s2w and dt2w)
-enable/disable s2w and dt2w separately
-add faux sound control support (untested)
-other minor tweaks and fixes
April 5, 2013 - ElementalX-6.5
-modification to work with SD Manager in ViperXL 3.2.7
April 5, 2013 - ElementalX-6.4
-correct oc frequencies
-adjust l2 cache frequencies
-gpu overclock frequencies now 480 3D and 266 2D
-fix max screen off limit
-various patches from Linaro and CAF
-WiFi module fix (thanks thicklizard)
-avoid loadavg moire
-enable automatic process group scheduling
-max screen off frequency can be disabled
March 13, 2013 - ElementalX-5.4
-optimized build compiled with -O3
-linaro 4.6.3 -> linaro 4.7.3
-force ac for unknown chargers
March 10, 2013 - ElementalX-5.3
-re-add use glibc memcpy
-re-add use glibc string
-adjust dirty_background_ratio = 10
-adjust vm_dirty_ratio = 20
-revert fudgeswap
-revert minfree stats
-tweak clock settings
-add /dev/frandom
-add force fastcharge
March 3, 2013 - ElementalX-5.2
-review and clean up code
March 1, 2013 - ElementalX-5.1RC
-tweak GPU settings
-change installer defaults
-made sure that if you flash boot.img in fastboot you get vanilla version
February 26, 2013 - ElementalX-5.0.6-beta
-add another CPU optimization setting (Ultra)
-switch do_fsync() to fget_light()
-adjust readahead to 2048
-tweak GPU clock settings
February 24, 2013 - ElementalX-5.0.5-beta
-updated aroma installer
-CPU optimization options: Vanilla or ElementalX
-zram enabled by default
-small tweaks to GPU settings
-fstrim at boot
February 23, 2013 - ElementalX-5.0.4-beta
-dual zram
-use zcache instead of qcache
-use zsmalloc instead of zxmalloc
-CPU1 governor can be set independently
-set max screen off frequency
-choose 192 or 384 minimum CPU frequency
-update cpupower according to cpu load
February 21, 2013 - ElementalX-5.0
-fix installer conflicts
-option to install new ElementalX bootsplash
-option to install HTC bootsplash
February 19, 2013 - ElementalX-v4.5beta
-default i/o scheduler is now ROW
-add fix for crash when wp_mod.ko loaded
-add fudgeswap
-disable gentle fair sleepers
-xz kernel compression
February 17, 2013 - ElementalX-v4.4beta
-add lionheart, badass governor
-add row i/o scheduler
-adjust l2 cache frequencies
-re-add 200MHz step for 2d GPU (ElementalX-v4.4beta only)
-remove smartassv2 (broken)
February 16, 2013 - ElementalX-v4.3beta
-based on HTC source code 3.17
-overclock to 2.1GHz
-minimum frequency 192MHz
-optional overclock GPU
-full voltage control
-enable/disable fsync
-intellidemand default governor
-fiops default scheduler
-add sweep2wake
-add zRam with snappy compression
-init.d support
-ntfs r/w support
-fix HDMI refresh rate
February 3, 2013 - ElementalX-JB-v2.5
-added 384 MHz frequency step when selecting 192MHz as min frequency (needed because CPU1 will not stay at 192MHz)
-adjustments to init script
-option to install extra governors (lionheart, lagfree, interactivex2, and badass)
January 26, 2013 - ElementalX-JB-v2.2
-choose minimum CPU frequency (192MHz or 384MHz)
-option to leave minimum voltage at default
-optimized CPU control module, now reads PVS efuse and sets appropriate voltage levels
-streamlined options and config file
-optional XBox controller support
January 21, 2013 - ElementalX-JB-v2.1
-Option to completely disable overclocking/undervolting
-If overclocking, choose between optimization for stability or performance
-stability option does not increase L2 cache frequency and bus bandwidth
January 20, 2013 - ElementalX-JB-v2.0
-added intellidemand governor (default)
-added fiops i/o scheduler (default)
-optional zram with snappy compression
-optional ntfs r/w support
-select minimum voltage (800, 825, 850, 875, or 900mV)
-added 1134 and 1242 MHz underclocking options
-increased bus bandwidth
-many changes to installer and configuration files
January 14, 2013 - ElementalX-JB-v1.5
-minor fixes to init script
January 12, 2013 - ElementalX-JB-v1.4
-fix low 3D GPU setting
-undervolt option now undervolts 384MHz frequency step to 800mV
-boost L2 cache frequency for extra performance
-increase readahead buffer to 4096
January 8, 2013 - ElementalX-JB-v1.3
-added voltage options
January 2, 2013 - ElementalX-JB-v1.2
-removed 1998MHz frequency step
-added 1647MHz frequency step
-increased voltages slightly for stability
-added option to install without boot.img
January 1, 2013 - ElementalX-JB-v1.1
-minor tweaks to install method
-adjust lowmemorykiller
December 31, 2012 - ElementalX-JB-v1.0beta
-same max freq for both CPUs
December 29, 2012 - ElementalX-JB-v0.4alpha
-new overclocking method
-more frequency choices, underclock or overclock
-option for completely stock CPU
-increased overclock voltages
December 28, 2012 - ElementalX-JB-v0.3alpha
-enable system write
December 24, 2012 - ElementalX-JB-v0.2alpha
-overclock to 1998MHz
Click to expand...
Click to collapse
Source:
ElementalX-v7.x
ElementalX-v8.x
XDA:DevDB Information
ElementalX-8.3.2 | OC | UV | S2W | DT2W | BLN | Sense 5, a Kernel for the AT&T HTC One X
Contributors
flar2
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 8.3.2
Stable Release Date: 2013-09-26
Created 2013-09-23
Last Updated 2013-11-04

Reserved

flar2 said:
Kernel for Sense-based Jelly Bean ROMs
LATEST VERSION: ElementalX-JB-v0.1alpha (December 23, 2012)[/size]
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!

WARNING: This is an alpha build. For testing purposes only!!
I will add more features and get things working properly later.
Download
ElementalX-JB-v0.1alpha: http://goo.gl/24bdo
Instructions:
Install from TWRP recovery
init.d not starting at the moment, so execute /etc/init.d/40overclock as root
Notes:
1. I will be away for the next week and a half, so progress will be slow, otherwise I'd have things going right away
2. CPU Spy doesn't show the real frequency
3. I can't wait to add more stuff
4. New stuff will be: min frequency 192MHz, Intellidemand, Zram, NTFS support
Click to expand...
Click to collapse
Thank you

Dang. Great work! Can't wait til this is stable with all the features. If you need help let me know!

Does this happen to bypass the write protection on /system?

absolutelygrim said:
Does this happen to bypass the write protection on /system?
Click to expand...
Click to collapse
No
I don't have the source, all I can do is add modules. I don't know if wp can be disabled using a module. I'll look into it next week when I'm back from Christmas holidays. Starting tomorrow, I'll be away from any decent computer.
UPDATE: Yes, this does bypass write protection

flar2 said:
No
I don't have the source, all I can do is add modules. I don't know if wp can be disabled using a module. I'll look into it next week when I'm back from Christmas holidays. Starting tomorrow, I'll be away from any decent computer.
Click to expand...
Click to collapse
Well, looks like we have to get you a decent laptop don't we? :L
Sent from my HTC One XL using Tapatalk 2

Anyone know if this works on newts Rom or a jb Rom I could flash that this works on?

WhatTheAndroid? said:
Anyone know if this works on newts Rom or a jb Rom I could flash that this works on?
Click to expand...
Click to collapse
It would work on any jelly bean sense rom

Edit:Nevermind

How do we know if it installed properly, I didn't check the kernel name before the flash but it looks stock. Is this correct, and as you said apps are not showing the over clock.
I got a 6475 with no OC, forgot to do Antutu.
With the kernel I got: 6189 (I know quadrant can be inaccurate)
Antutu: 11659
Sent from my HTC One XL using Tapatalk 2
EDIT: Got scores in the 7000's after some tweaking.

lsmod in terminal should show oc_mod. But right now, basically if you don't know how to check stuff like this you shouldn't install. My first step was getting a module to load, now I've got to get it working properly.

Nice will be watching to see how the this progresses
Sent from my HTC One X using Tapatalk 2

How do you execute the 40overclock? Yes I'm asking!
Sent from my HTC One XL using Tapatalk 2

monkboy24 said:
How do you execute the 40overclock? Yes I'm asking!
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Use script manager app
Sent from my Nexus 7 using Tapatalk 2

currydude said:
Use script manager app
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I used script manager to execute 40overclock and it says oc_mod exists already. And then permission is denied on the next operation. So if I have the oc_mod file it must have worked?
flar2 said:
lsmod in terminal should show oc_mod. But right now, basically if you don't know how to check stuff like this you shouldn't install. My first step was getting a module to load, now I've got to get it working properly.
Click to expand...
Click to collapse
I used adb shell, su, then lsmod and I got the output:
oc_mod 1902 0 - Live
So I guess I'm all good.
Sent from my HTC One XL using Tapatalk 2

Can't wait for this! Thank you so much!
Viper Rom, baby!

Tried playing around with this.. Don't understand too much.. Was hoping to get rebelrom screaming even more that it already is
Sent from my HTC One XL using Tapatalk 2

Thanks for a great JB kernel. Anyway to have 2 way call recording patch in the future version of ElementalX kernel as there isn't any patch for HTC ONE XL till now. Thanks in advanced and waiting for 2 way recording feature!
Sent from my HTC One XL using xda premium

Just uploaded version 0.2
Should "just work" (init.d support is added)
The only feature is rudimentary overclocking still, I haven't a chance to work on any of the good stuff.

[KERNEL] [Sep5] ElementalX 7.1 | Sense 6/5.5/5 Android 4.4.2/4.3

Previous versions:
ElementalX-6.1
ElementalX-6.0
ElementalX-S-4.3
ElementalX-S-4.2
ElementalX-S-3.4
ElementalX-S-3.3
ElementalX-3.2
ElementalX-S-v3.1.1beta: http://goo.gl/B6Xxd
ElementalX-S-v3.1beta: http://goo.gl/0T3B3
ElementalX-S-v3.0beta: http://goo.gl/TWRIU
Elemental-S-v2.5: http://goo.gl/9I8GZ
Elemental-S-v2.2: http://goo.gl/o5xCq
Elemental-S-v2.1: http://goo.gl/aE124
Elemental-S-v1.0: http://goo.gl/MfWmp[/B]
INSTALLATION
1. Do not install over other custom kernels. Please ensure you have the stock kernel installed by reflashing your ROM.
2. Install zip from TWRP Recovery
3. Follow the instructions, if you don't know what to do, use the preselected option
4. Reboot!
Code:
* Standard disclaimer:
* Your warranty is now void. Use at your own risk.
* In other words: It is your choice to use this software,
* I am not responsible for any damage or problems!
Special thanks:
@bilal_liberty for 4.4.2/4.3 port
@pirlano for 4.2.2 port
@showp-1984 for S2W
@tbalden for BLN
NOTES:
Configuration
Your choices in the Aroma installer are used to build a configuration file. The config file is located at /etc/elementalx.conf. You can edit this file to change kernel settings. Whatever is set in this file will take effect when the device is booted (unless other scripts or apps interfere!)
The settings can be changed by editing /etc/elementalx.conf and rebooting. Advanced users can apply settings on the fly by running /etc/init.d/99elementalx as root.
There is no need to edit /etc/init.d/99elementalx. All settings are configured in /etc/elementalx.conf.
If settings are not sticking, make sure the file permissions for /etc/init.d/99elementalx are set to execute. Every time the settings are applied, a log file is created at /data/local/tmp/elementalx-kernel.log. Problems can be diagnosed by looking at the log file.
Please check to see if any /etc/init.d scripts or apps are interfering with your settings If you're on ViperXL, make sure your settings in Venom Tweaks are the same as the ones in /etc/elementalx.conf (for example, sweep2wake settings)
Kernel Tuner
You don't need Kernel Tuner because the ElementalX installer sets everything up automatically, but if you want to check or change settings, Kernel Tuner is recommended. Just be aware that Kernel Tuner is set by default to apply settings on boot, which can interfere with the settings you chose in the ElementalX installer.
CPU Optimization
Vanilla: stock voltages, stock l2 cache frequency, stock bus bandwidth
ElementlaX: increases l2 cache frequency and bus bandwidth, allows you to choose voltage level in installer
Ultra: increases l2 cache frequency and bus bandwidth even more. May cause instability, please test thoroughly for stability if you use this option.
Overclocking
Overclocking (underclocking) is optional. Whatever frequency you chose in the installer will be set at boot for both CPUs. Frequencies can be changed any time using apps like No Frills or Kernel Tuner. WARNING: not all devices can handle overclocking. The stock maximum CPU frequency is 1.5GHz. In versions of the kernel prior to 4.2, the frequencies were labeled wrong so you won't be able to overclock as high with version 4.2+.
CPU voltages
CPU voltages can be changed with Venom Tweaks, Kernel Tuner or System Tuner. Be careful, lowering voltages could cause instability. If you have stability problems even at the highest voltages, try the vanilla version
Minimum CPU frequency
Sets the minimum CPU scaling frequency. 192MHz is the recommended default and should work fine on the vast majority of devices. The 384MHz option is available for devices that experience random reboots while the device is idle. It is recommended that you try increasing the minimum voltage by 25mV before changing the minimum CPU frequency.
Max screen off frequency
This sets the highest CPU frequency available while the screen is off. It is recommended to disable this for stability. Also, do not set this to 192MHz or 384MHz, as many devices experience random reboots at these frequencies. The default is 486MHz, which should be safe for most devices. If you experience random reboots while the device is asleep, set this to a higher frequency. This setting can be changed in /etc/elementalx.conf or using an app like Venom Tweaks.
GPU frequencies
GPU frequencies can now be set on the fly using Kernel Tuner. There is also an option in /etc/elementalx.conf. Available maximum frequencies:
3D GPU: 480 (overclocked) or 400 (stock)
2D GPU: 266 (overclocked) or 200 (stock)
Governors
Intellidemand is the default CPU governor. There are other governors included, however, intellidemend is recommended for best balance of battery life and performance.
Installing a new ROM
If you install a new ROM, it will overwrite /etc/init.d/99elementalx and /etc/elementalx.conf. The kernel will run perfectly fine without these files, but you will lose your settings and certain features.
Sweep2Wake
Sweep2wake allows you to wake up your device by swiping your finger across the capacitive buttons from left to right. Swiping from right to left will put it back to sleep (sweep2sleep). There are now options for sweep2wake/sweep2sleep, sweep2sleep only, and disabled. If you use ViperXL, make sure to enable sweep2wake in Venom Tweaks. Note that in Venom Tweaks, the sweep2sleep only option can be selected by choosing Enable (no buttons backlight).
DoubleTap2Wake
DoubleTap2Wake (DT2W) allows you to wake the device by double tapping the capacitive buttons.
/sys/android_key/doubletap2wake
0=disabled
1=enable doubletap2wake using back button
2=enable doubletap2wake using home button
3=enable doubletap2wake using recent apps button
DoubleTap2Sleep (Version 6.4+ only)
DoubleTap2Sleep (DT2S) allows you to put the device to sleep by double tapping the capacitive buttons.
/sys/android_key/doubletap2sleep
0=disabled
1=enable doubletap2sleep using back button
2=enable doubletap2sleep using home button
3=enable doubletap2sleep using recent apps button
Pocket Detection
Pocket detection protects against accidental wakes while S2W or DT2W are enabled and the phone is in your pocket. Pocket detection uses the proximity sensor. This is disabled by default. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/android_touch/pocket_detect
0=disabled
1=enable pocket detection
Button Light Notification
With Button Light Notification (BLN), the capacitive buttons will blink on and off when you have a new notification. You can edit /etc/elementalx.conf to change the setting on boot.
/sys/class/leds/button-backlight/bln
0 = disabled
1 = BLN enabled
What is zRam (not included in version 6.0)
zRam creates a compressed block device in RAM that is used as swap. Although it claims some of your RAM as swap, everything written to swap is compressed. This increases the apparent memory available to the system and helps with multitasking. Swap files on disk are very slow, but with zRam the swap is on RAM so it can be read as quickly as regular memory. Even though the data need to be decompressed, modern CPUs can decompress quicker than if it had to be to read from disk. The penalty is cpu usage, which could drain battery; however, this is likely negligable in daily use. I didn't enable this by default because not everyone will want it. This is for heavy multitaskers and will allow you to quickly switch between more apps and have more tabs open in your browser without refreshes.
zRam is disabled by default. If you want to enable it, edit /etc/elementalx.conf
change ZRAM=0 to ZRAM=1 and reboot.
You can check if zRam is working by typing the command "free" into the terminal. You should see the total used and free swap. If these are all 0, then zRam is not enabled. Please ensure that other apps are not changing your minfrees, zRam works best with low minfrees and high swappiness.
NTFS support
This is for anyone who wants to use OTG to connect a USB stick or portable harddrive formatted with Microsoft's NTFS filesystem. You will need Stickmount or a similar app, HTC Sense+ won't detect NTFS.
exFAT support (version 6.0 only)
exFAT filesystem support is available on version 6.0 via a kernel module. You will need Stickmoutn or similar app to mount exFAT volumes.
Enable/disable fsync
Disabling fsync can increase filesystem performance. However, there is a small risk of data loss if the system suddenly crashes. If you can't afford to lose data, keep fsync enabled. Many custom kernel disable fsync, I leave it enabled by default for safety reasons.
Game controller support
There is some support for Gamepads, including X-Box and PS3 controllers.
CHANGELOG:
ElementalX 7.0
-support Sense 6/5.5/5 Android 4.4.2/4.3
-various fixes and optimizations
ElementalX 6.4
-fix bln not working without s2w enabled
-add doubletap2sleep
ElementalX 6.3
-fix errors
ElementalX 6.2
-update installer
-fix to work with any hboot
-add ROW i/o scheduler
-various fixes and optimizations
ElementalX 6.1
-fix in-call sound (thanks @pirlano)
ElementalX 6.0
-support for Android 4.2.2
-battery saving and speed tweaks
-compile with linaro 4.7
-update installer
-remove zram
-default governor is ondemand
-default i/o scheduler is fiops
ElementalX 5.0.1
-fix init.d support
ElementalX 5.0
-remove OTG whitelist to enable more devices
-build with Linaro 4.8
-add TCP congestion control algorithms
-default governor is ondemand
-default scheduler is fiops
-update installer (nust be s-off!)
-add pocket detection (disabled by default)
-fix doubletap2wake in deep sleep
-fix sweep2sleep only
-remove 192MHz frequency step
-max screen off default is 702MHz
ElementalX 4.3
-add doubletap2wake
-add button light notification
-fix fm radio
-remove autogroup: group by current UID
-arm/crypto: Add optimized AES and SHA1 routines
ElementalX 4.2
-correct oc frequencies
-adjust l2 cache frequencies
-gpu overclock frequencies now 480 3D and 266 2D
-fix max screen off limit
-various patches from Linaro and CAF
-WiFi module fix (thanks thicklizard)
-avoid loadavg moire
-enable automatic process group scheduling
-max screen off frequency can be disabled
ElementalX 3.4
-optimized build compiled with -O3
-linaro 4.6.3 -> linaro 4.7.3
-force ac for unknown chargers
ElementalX 3.3
-add /dev/frandom
-add force fastcharge
-change makefile optimizations
-tweak init script
ElementalX 3.2
-fix gpu oc
-add row i/o scheduler
-add governors
-use glibc memcpy
-disable gentle fair sleepers
-add zram
-disable qcache
-use zcache and zsmalloc
ElementalX 3.1
-gpu oc
-option to disable fsync
ElementalX 3.0
-HTC Jelly Bean source
-vanilla, elementalx and ultra CPU optimization options
-overclock to 2.1GHz
-minimum frequency 192MHz
-full voltage control
-intellidemand default governor
-fiops default scheduler
-add sweep2wake
-add zRam with snappy compression
-init.d support
-ntfs r/w support
-ARM topology
-fix HDMI refresh rate
-disable gentle fair sleepers
-xz kernel compression
-add fix for crash with wp_mod.ko
-fix installer conflicts
-switch do_fsync() to fget_light()
-CPU1 governor can be set independently
-set max screen off frequency
-choose 192 or 384 minimum CPU frequency
-update cpupower according to cpu load
-adjust readahead to 2048
February 3, 2013 - Elemental-S-JB-v2.5
-added 384 MHz frequency step when selecting 192MHz as min frequency (needed because CPU1 will not stay at 192MHz)
-adjustments to init script
-option to install extra governors (lionheart, lagfree, interactivex2, and badass)
January 26, 2013 - Elemental-S-JB-v2.2
-choose minimum CPU frequency (192MHz or 384MHz)
-option to leave minimum voltage at default
-optimized CPU control module, now reads PVS efuse and sets appropriate voltage levels
-streamlined options and config file
-optional XBox controller support
January 21, 2013 - Elemental-S-v2.1
-Option to completely disable overclocking/undervolting
-If overclocking, choose between optimization for stability or performance
-stability option does not increase L2 cache frequency and bus bandwidth
January 20, 2013 - Elemental-S-v2.0
-added intellidemand governor (default)
-added fiops i/o scheduler (default)
-optional zram with snappy compression
-optional ntfs r/w support
-select minimum voltage (800, 825, 850, 875, or 900mV)
-added 1134 and 1242 MHz underclocking options
-increased bus bandwidth
-many changes to installer and configuration files
Elemental-S-v1.0:
-minor tweaks to init.d script
Elemental-S-v0.6:
-added voltage options
-boost L2 cache frequency for extra performance
-fix 3D GPU setting
-increase readahead buffer to 4096
Click to expand...
Click to collapse
SOURCE:
ElementalX-5.x
ElementalX-6.x
ElementalX-7.x
XDA:DevDB Information
ElementalX-ville, Kernel for the HTC One S
Contributors
flar2, pirlano bilal_liberty
Source Code: https://github.com/flar2/ElementalX-ville-6.0
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 6.4
Stable Release Date: 2013-10-25
Current Beta Version: 7.1
Beta Release Date: 2014-09-05
Created 2013-10-06
Last Updated 2017-03-29

Nice but say if I want to merge this with a rom is the boot.img and system folder all I need?

The boot.img is stock JB with init.d support added. You can use any boot.img as long as it has init.d support. That's why flashing the boot.img is optional.
The rest is two kernel modules and some config files that load the modules and apply settings.

flar2 said:
The boot.img is stock JB with init.d support added. You can use any boot.img as long as it has init.d support. That's why flashing the boot.img is optional.
The rest is two kernel modules and some config files that load the modules and apply settings.
Click to expand...
Click to collapse
Thanks just wasn't sure on the other folders in the zip.

Thanks for coming here and providing solutions. :good:

Darknites said:
Thanks just wasn't sure on the other folders in the zip.
Click to expand...
Click to collapse
Darknites, have you got this working man?

dr_rick13 said:
Darknites, have you got this working man?
Click to expand...
Click to collapse
No not tried yet, is it not working for you?

Darknites said:
No not tried yet, is it not working for you?
Click to expand...
Click to collapse
haven't tried either not in the mood to backup my stuff, so wanted to see if it's working before trying it lol

I flashed it several times on my wife's One S, worked perfectly.
Just be sure your phone can handle the overclock. I think the vast majority could handle 1728MHz. My wife's phone can handle up to 1809MHz.

dr_rick13 said:
haven't tried either not in the mood to backup my stuff, so wanted to see if it's working before trying it lol
Click to expand...
Click to collapse
What rom you on?

flar2 said:
I flashed it several times on my wife's One S, worked perfectly.
Click to expand...
Click to collapse
It works perfectly.
Installation was bloody fast on hboot 1.06.

Darknites said:
What rom you on?
Click to expand...
Click to collapse
blackout v1.5, you?

rootrider said:
It works perfectly.
Installation was bloody fast on hboot 1.06.
Click to expand...
Click to collapse
Took about 5 minutes on hboot 1.13, but the kernel installed successfully

dr_rick13 said:
blackout v1.5, you?
Click to expand...
Click to collapse
Same about to reflash it and see if it works there since I don't need overclock.
---------- Post added at 07:06 AM ---------- Previous post was at 07:05 AM ----------
flar2 said:
Took about 5 minutes on hboot 1.13, but the kernel installed successfully
Click to expand...
Click to collapse
Ya don't miss that lol.

flashing this on my ROM should work

dr_rick13 said:
blackout v1.5, you?
Click to expand...
Click to collapse
Zarboz said:
flashing this on my ROM should work
Click to expand...
Click to collapse
Ya working great.

working on both zarboz's v1.5 and sense best v3.0 for me

Darknites said:
Ya working great.
Click to expand...
Click to collapse
hmm flashes fine, but mine only goes up to 1512..
did you flash the boot.img too? or did you select to not flash it?

dr_rick13 said:
hmm flashes fine, but mine only goes up to 1512..
did you flash the boot.img too? or did you select to not flash it?
Click to expand...
Click to collapse
I merged it with the rom and I see no overclock.

There should be a log file at /data/local/temp/elementalx.log
If not, the init script didn't run, in which case try flashing the boot.img

Padfone 2 A68 [Kernel] Stone custom kernel for ASUS Padfone 2 - OC/UV/GPL/etc

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?

[KERNEL][3.0.31][HDMI][FULL HD][GUIDE 1.8]JBX-Kernel Hybrid [1,5ghz]

/// 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

[KERNEL] [GPL] [4.3/4.4] [8th June] Oxydo -V18

Presenting Oxydo kernel for the Nexus 7 Grouper and Tilapia
{
"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"
}
1. Features
Nothing here. Move along to post #2. See the changelog.
[/LIST]
2. Instructions
Flash in recovery. You know how to.
3. Warning and disclaimer
The usual. I am not responsible for any harm caused to your tablet by this kernel. You decide whether you want to flash this or not and therefore you face the consequences. But don't worry. This has been tested and the results were pretty good.
4. Downloads
https://www.dropbox.com/sh/pwe87rpzciojb9z/I3UHL9pLE4
Notes are available in changelog.
GENERAL:
1) For modules ZIPs, extract and insmod manually.
2) The last one is usually for the latest version of Android.
5. SOURCE: https://github.com/souljaboy11792/oxydo-grouper
6. Credits
In no specific order
franciscofranco
flar2
Mahdi-786
Metallice
spasrksco
_motley
ashik992
faux123
show-p1984
intersectRaven
davidmore
poondog
Tasssadar
redeyedjedi
dexviajiboy
Everyone else whose patches I may have used directly or indirectly
Google and Android
Supporters and testers and well-wishers and haters and random people.
Allah Almighty

7. Changelog
V1 (XX)
Initial release
Linux 3.2.46
Franco's hotplug
Various small changes
V2 (XX)
JRCU
Scaling bug fixed. Goes as far as 102MHz now.
Slight (pointless, but fun) increase in RAM (about 0.5MB), as logger is compiled as module.
Included hso.ko and ppp_async.ko modules on user demand. ( @xDeadaheaDx )
Included Lazy CPU governor and ZEN I/O scheduler on user demand. ( @ckisgen )
Updated to Linux 3.2.47
V3 (XX)
Merged changes required for 4.3.
Updated to Linux 3.2.49.
Fixed ADB issues that persisted on stock kernel.
No longer build the modules because I think unsigned modules loading is messed up now. Have to check.
V4 (XX)
Ramdisk from M-KERNEL. Fixes all issues.
New method for enabling/disabling logger (more info in 3rd post).
V5 (XX)
Sysfs interface to control min/max backlight. Highly experimental. Referenced M-KERNEL. Check post #3.
V6 (XX)
Backlight control still isn't fixed. Going to try something else now.
sweep2wake and doubletap2wake in experimental versions. Check post #3.
V7 (XX)
New code for min/max backlight and brightness. Check post #3
sweep2wake and doubletap2wake given newer life thanks to flar2.
Reverted to 446MHz GPU OC.
V8 (XX)
Added shortsweep option.
Enabled AUDIT to fix SELinux issues.
Added a table in /sys/devices/system/cpu/cpu0/cpufreq (gpuc_UV_mV_table) that shows the clock speed and voltage applied to GPU. Intended for it to be rw but it cannot be saved for some reason.
Updated ASIX drivers to USB 3.0.
hso and ppp_async as modules.
CIFS (optional) available as module.
Enabled KSM.
V9 (XX)
Decreased s2w timeout to allow more time for valid swipes.
Fix s2s in portrait mode.
Fix mounts in the ramdisk. They are as hey should be now.
Added USB DAC patches (please try this and lemme know whether this works)
Added USB host mode patch.
May be more changes but I'm too tired right now.
V10 (XX)
Dynamic Fsync. Credits - faux123.
Reverted the USB hostmode patches that broke OTG.
smartassv2 governor as a module. Credits - Ricardo Gomez.
Changed dithering mode to fix gradients.
Another attempt at USB DACs. Please test it.
700MHz GPU OC as default. Set it to boot at 446MHz if you want to (will stick properly). Certain freqs that are not listed as steps in the DVFS will not stick.
V11 (XX)
600MHz GPU OC as default. Scales properly now. Don't increase in TricksterMOD (doesn't stick between boots; supposed to be that way because 600+MHz causes screen turds). Decreasing works.
V11-446 (XX)
V11 with 446MHz GPU default. Should reduce FCs.
V12 (11th October, 2013)
Switched to 484MHz GPU OC.
Switched to SLAB on user request.
Introduced wake_locks to help with wake functions.
Introduced sysfs parameter to control area of screen that can be used to complete s2s.
V13 (8th November, 2013)
Now has s2w and s2s portrait mode area parameters exposed to sysfs.
PPP and hso now built inline
smartass2 tunables exposed to sys/devices/system/cpu/cpu0/smartass2. Takes ages and at least ten Terminal Windows to configure.
Uses zImage, so compatible with every 4.3+ ROM for now. Even 4.4.
cifs.ko module already in ZIP file so bye-bye modules.zip
V14 (27th November, 2013)
Now s2w and s2s trigger area are in sysfs (properly; no modular interface now).
logger enabled by default.
Use UKSM
GPU OC till 750 supported (may be unsupported in some devices; but it works).
OTF scaling included.
t3_variant info in debugfs.
Include smartmax governor from maxwen. Really good.
Updated to 4.4 source.
V15 (16th December, 2013)
All s2s trigger area functions are in android_touch (even landscape ones)
USB hostmode patches added. Check FAQ
USB DAC patches added but I dunno if this works
logger has been allocated even less RAM. Some of it is there just so you can debug crap.
audit debug is disabled.
interactive governor updated from Francisco Franco's repo.
smartmax is now the default governor.
Updated to 4.4.1 (??) source. I don't really remember.
Updated all the way to Linux 3.2.53 (the last in the 3.2.y series). First ever grouper kernel to do so. There are some nasty reverts though.
V15 SELinux=disabled (19th December, 2013)
NOTE:FLASH THIS ONLY IF THE OTHER VERSION DOESN'T WORK. PLEASE HAVE A BACKUP OF THE ENTIRE TABLET ESPECIALLY THE BOOT PARTITION BEFORE EXPERIENTING.
SELinux disabled. Hopefully fixes fragmentation issues over Kit Kat ROM. Just a temporary fix for now.
V16 (2nd February, 2014)
Linux 3.2.54.
interactive governor updated from Francisco Franco's repo.
BFQ scheduler
V16-aospal (2nd February, 2014)
Selinux disabled for a few kk ROMs like aospal.
V17 (11th April, 2014)
Linux 3.2.56.
SELinux disabled by default.
f2fs support (thanks @ss2man44). RAMDISK NOT INCLUDED!! Flash LegoKernel first and then oxydo over that to have f2fs and oxydo kernel.
baseband_xmm wakelock given timeout. More info in post #3.
Stock hotplug.
Various changes here and there.
V18 (8th June, 2014)
Merged changes for 4.4.3 from Google
Revert to Franco's initial hotplug routine, and instad of disabling screen, just disable framebuffer for faster wakeups. Courtesy of franciscofranco.

8. FAQ
1. How do I enable logger? What about hso and ppp_async?
Ans:
For builds with modules:
Download the modules zip. Unzip them to you sdcard, and note the path. Fire up the Terminal. Issue these commands one by one:
Code:
su
insmod /path/to/logger.ko (only in V2)
insmod /path/to/hso.ko
insmod /path/to/cifs.ko
insmod /path/to/ppp_async.ko
To check whether they are working (they are, don't worry):
Code:
lsmod
Should output something like
logger.ko 54334 [permanent] ... blah.
You can also try:
Code:
dmesg | grep "logger"
dmesg | grep "hso"
ppp_async doesn't show any message.
To disable hso.ko and ppp_async.ko (you can't disable logger.ko once it's insmod'ed, but a simple reboot will rmmod it):
Code:
rmmod hso.ko
rmmod ppp_async.ko
For builds without modules:
To enable logger (it is off by default), issue this command in Terminal Emulator
Code:
echo "1" > sys/kernel/logger_mode/logger_mode
To disable it, just echo 0 instead.
2. Why won't my device reach 51MHz even though it's listed in the frequency list?
Ans: I have set the min rate for G cores to 102MHz. 51MHz IMO is a very stupid frequency in that it will do nothing basically. Even my 3 year old cellphone doesn't stay at 51MHz. It should be a LP core frequency (it actually was) but since Franco's hotplug driver doesn't call on the LP core, it's not reachable.
3. How do I control minimum - maximum backlight through sysfs?
Let me begin by saying that this feature is highly experimental. I can tell though that it works.
Okay so in /sys/module/board_grouper_panel/parameters you'll see two files:
min_bl - Write in a reasonable value preferably at least 30 less than max_bl. Default is 10. Not safe. Switch to 11.
max_bl - Write in a reasonable value preferably at least 30 more than min_bl.
This is what happens. *takes deep breath*
When your brightness is greater than zero but less than the min_bl, it gets changed to the min_bl. And when it's greater than max_bl, it's changed to max_bl. Otherwise it's just normal brightness levels (where's the fun in that, right? )
PLEASE DON'T WRITE THE VALUES OF min_bl OR max_bl WHILE YOU'RE HIGH, DRUNK OR JUST DOWNRIGHT BAT-CRAP CRAZY!
There's no limit to the madness that may happen as a result.
4. How do I configure sweep2wake and doubleetap2wake? What exactly are they?
Sweep2wake and doubletap2wake are basically two versions of the same thing - they wake your device up after you have put it to sleep (not metaphorically) without using the physical buttons on the side. This is still slightly buggy. If at first it doesn't work. Touch the screen once and then tap it twice.
For sweep2wake/sleep you basically swipe along the bezels (not on the bezels though) where the soft keys would be.
For doubletap2wake, just tap twice on the screen during sleep, and it should wake up.
To configure sweep2wake go to /sys/android_touch and open up sweep2wake
0 = disbaled
1 = sweep2wake/sleep
2 = sweep2sleep
To configure doubletap2wake go to /sys/android_touch and open up doubletap2wake
0 = disabled
1 = enabled
To configure shortsweep go to /sys/android_touch and open up shortsweep
0 = disabled.
1 = enabled.
This drains battery a little faster than stock would, so yeah. Don't use it (i.e. disable it) if you want to save battery, or set up a script.
There is also a wake_timeout file. It holds the time that the dt2w wakelock will remain active after the screen is suspended.
NOTE: s2w wakelock times aren't configurable and it will stay on for 15 seconds after the screen has been suspended.
Insert the time in seconds. (60 = 1 minute; 3600 = 1 hour)
If both are disabled no wakelocks are registered and held.
5. How do I get USB OTG to work?
Go to /sys/kernel/usbhost.
echo 0 to usbhost_fixed_install_mode.
I haven't tested (hostmode, and fast charge/hostmode charge) this myself, so feedback is appreciated.
You need StickMount unless your ROM supports native OTG.
6. Why is SELinux disabled?
To get it booting on some Kit Kat ROMs. Booting in permissive may work, but I haven't tested it yet.
8. Why is my device so awesome now?
OH STAHP IT YOU! And you weren't reading carefully enough, otherwise you would have pointed out that I missed #7.
69. <== LOL!11eleventy!!1! How do I configure baseband wakelock timeout?
Go to /sys/module/baseband_xmm_power/parameters and open up the bb_timeout file.
0 means the wakelock will be held for 1 second after it is acquired.
Values are in seconds.
I used timeout instead of disabling it completely because, although there have been no problems reported, thus far, to arise from this modification, it's better to be safe (not disabling completely but making it timeout after a while) than sorry (losing functionality although it seems unlikely)
9. A POST ON RECOMMENDED SETTINGS AND STUFF
"Interactive @ 1.5GHz and GPU @ 484MHz (or even 446MHz) + no screen wake controls (if you don't use them) should give you excellent battery life and performance. You can adjust CPU speeds too."
- sgt. meow
Idea of @keneth_c
Oh and this works awesome with the IceColdJelly AOKP ROM for Tilapia. Be sure to try it out.
Works fab on 4.3 stock. Don't believe in benchmarks though.

First downloading now
Sent from my Nexus 7 using Tapatalk 4 Beta

Sweet gonna try this out
Sent from my Nexus 7 using Tapatalk HD

Using it and loving it....THANKS MAN.... :good:

Glad you guys like it. I'm building v2 right now. But it'll be a number of builds before I get the next bits right.

Take Your time......we are here for testing...

New kernel for our n7. Fine:thumbup:
Sent from my Xperia Neo using xda app-developers app

So any UV UC or OC support? Most probably to be announced in v2....

Thanks for the kernel, will test soon!

This kernel has proper OC and UV/OV. It works for me.

Think I'm gonna test this - looks interesting... :cyclops:

sgt. Meow said:
glad you guys like it. I'm building v2 right now. But it'll be a number of builds before i get the next bits right.
Click to expand...
Click to collapse
your kernel is by far the best...it made ppsspp games smoother.......

Will check it out soon! Should be interesting to see where this goes in 4.3. You should try build with the optimizations that are in Purified Kernel. And add lower brightness support (from M-Kernel)
Sent from my GT-I9300 using xda premium

@sgt. meow is it possible to update to 3.4?
Sent from my Nexus 7 using Tapatalk 4 Beta

infatality said:
@sgt. meow is it possible to update to 3.4?
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Its already 3.2
Not an easy job that
Sent from my Nexus 7 using xda app-developers app

poondog said:
Its already 3.2
Not an easy job that
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Haha.. Was wondering if possible.. Well.. Good to see a kernel updated beyond 3.1.10
Sent from my GT-I9100 using Tapatalk HD

infatality said:
Haha.. Was wondering if possible.. Well.. Good to see a kernel updated beyond 3.1.10
Sent from my GT-I9100 using Tapatalk HD
Click to expand...
Click to collapse
Well to put this in context, its very easy to update from say 3.0.86 to 3.0.87, its only a diff patch and its applied and built in 3 mins on a fast machine.
To update from 3.0.y to 3.1.y, or in this case 3.1.y to 3.2.y is a lot of work, there's no patch for it as its all porting if code mostly manually, very big feat. Its nearly impossible
Sent from my Nexus 7 using xda app-developers app

Saber-Toothed-Squirrel was also updated to 3.2.46.
And yes it is possible. But it won't be an update as much as a slight change in the Makefile. I tried it once.

Database Info

welcome