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

[KERNEL] [GPL] [4.3/4.4] [8th June] Oxydo -V18 - Nexus 7 Android Development

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.

Related

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

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.

[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

[T-Mobile TW][Nadia Kernel][05-March-2015][4.4.4][Faux Sound]Emotroid Team

- Nadia nightly Kernel Note 4 -
SM-N910F/ SM-N910G/ SM-N910T/ SM-N910W8
Introducing the Emotion Revolution Roms & Nadia Kernels for Android Devices.Emotroid Rom/Kernel is a modified, aftermarket firmware/Kernel distribution few Android devices (Note 2, Note 4, HTC M8). Based on the Android Open Source Project , Emotroid Rom & Kernel is intended to increase performance and stability over Android-based Devices released by sellers, for example, Samsung, HTC and so forth. Emotroid additionally offers a mixed bag of features & improvements that are not presently found in stock variants of Android.
{
"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"
}
*** Disclamer***
Your warranty is now void.
We are not responsible for any damage or problems you may have!
YOU are choosing to make these modifications.
Click to expand...
Click to collapse
First of all I want to say this that is one project which just started and gradually we will improve it. In this community there are very good developers and we are not traying to compete with them. This is just a hobby and we do it because we like Android. This kernel is only for SM-N910F SM-N910G SM-N910T and SM-N910W8 and we don't have plans to make it compatible with other versions of Galaxy Note 4. We hope that you will not only download the kernel but also you will leave your feedback with pros and cons and you should respect our efforts.
Don't be scared by the nightly denomination of the kernel.
Thread IndeX
POST 1: Kernel Information, Changelog, Credits,Screenshots
POST 2: Synapse, Recommended settings, FAQ, etc.
POST 3: Know/Reported issues
Request new features here
Features:
Quote:
Based on Samsung Open Source N910FXXU1ANIE
Compiled with Toolchain Linaro GCC 4.9.3 2014.12 Cortex A15
Linux version 3.10.0
PowerSuspend Driver
Intelli-Plug V3.9
Sweep2wake
Simple GPU Algorithm
Voltage Control
Intelli-Thermal
mDNIe Hijack Mode
Led Control
CRC Settings
Advanced TCP control
S-View flip cover hack
Selinux Permissive
Sched: LOAD_FREQ (4*HZ+61)
Reduced wakelocks
Frandom number generator
Synapse full support
March- 5 -2015 nightly r7
-Added KCAL - Advanced color control (Thanks to @savoca for his great job) check this thread for more info
March- 3 -2015 nightly r6
-Based on XXU1ANK4 (KitKat version) and compatible with "F,G,T,V,W8"
-Kernel compiled with Linaro Toolchain 4.9.3 2015-02
-FauxSound updated to 3.6
-Fixed some issues in FauxSound and Synapse
-cpufreq: Introduced new relation for freq selection Introduce CPUFREQ_RELATION_C
-Interactive Governor: Use CPUFREQ_RELATION_C
-Added Gentle fair sleepers (Synapse -> KERNEL TWEAKS)
-Enabled Kernel SamePage Merging (KSM) (Synapse -> KSM)
-Added key disabler (Synapse-> SCREEN/MISC)
-Added userspace vibration strength control (Synapse-> SCREEN/MISC)
-Changed some stuff in Synapse
-Reverted some commits
-Another minor changes
January- 27 -2015 nightly beta r5
-FauxSound implemented
-FauxSound in Synapse (Thanks to Placiano)
-Added high performance mode in Synapse->Sound
-Fixed battery drain on wifi (My fault)
-Reverted another commits
January- 16 -2015 nightly r4
-Fixed cpu voltage control (No more 0MHz frequency in cpu voltage table)
-ASoC: wcd9xxx: use hwdep node for codec calibration
-ASoC: wcd9320: use hwdep nodes to get calibration
-ASoC: wcd9xxx: Changes for High performance mode
-ASoC: wcd9xxx: Change PA on and VDDIO switch sequence
-ASoC: wcd9xxx: Avoid micbias glitches during audio playback
-In conclusion better quality sound on headsets
-Sched/fair: reduced latency
-Decreased DHD_PACKET_TIMEOUT_MS to 250 ms (Before 500ms)
-Drecreased time to enter sleep
-Net: wireless: Increased scan entry expiration to fit new scan time
-PM: devfreq: Use high priority workqueue
-Msm: kgsl: Report correct GPU frequency in sysfs
-Some minor changes
January- 11 -2015 nightly r3
-Added Frandom as module and set by default (Synapse>I/O>Frandom) "For more info check this"
-Network speed tweak
-Reduced wakelocks "wlan_rx_wake" and "wlan_ctrl_wake"
-dtsi: realigned voltages with userspace values (Thanks to twistedumbrella)
-cpu-boost more performance (Thanks to franciscofranco)
-sched: LOAD_FREQ (4*HZ+61) "For more info check this"
-Interactive governor imported from the Nexus 6 (No more lag on interactive)
-Added bluactive and interactive_pro governors
-Reverted some changes that made the kernel laggy in some cases.
-Selinux set to permissive by default
-Gpu: msm: for higher priority you want to use nice level of -7
-Now you can change the governor tunables from Synapse (Issue fixed) (Thanks for the tip to AndreiLux)
-Synapse shows all the available gpu governors (Thanks to my friend Friedrich!)
-Cleaned some things in Synapse
-Other minor changes
January- 4 -2015 nightly r2
-Fixed Ondemand governor
-mm: slub: Default slub_max_order to 0 (Improved performance)
-Increased io performance
-writeback: fix occasional slow sync
-Fixed min frequency (Finally!)
-msm: Fix high load average from uninterruptible waits
-Cpu boost sysfs to enable/disable it (Synapse>cpu drivers)
-S-View hack (Twistedumbrella) enable/disable (Synapse>miscellaneous)
-Minor fixes
January- 1 -2015 nightly r1
-Based on Samsung Open Source N910FXXU1ANIE
-Compiled with Toolchain Linaro GCC 4.9.3 2014.12 Cortex A15
-PowerSuspend Driver
-Intelli-Plug V3.9
-Stereo Call Recording Support
-cpufreq_limit: don't override cpu min frequency
-Fast Charge V1.2
-Sweep2wake
-Simple GPU Algorithm
-Sysfs interface to Enable/Disable Logger Android (Default disable)
-Voltage Control
-Intelli-Thermal V1
-mDNIe Hijack control
-Advanced TCP control (westwood default)
-Sysfs interface to Enable/Disable CRC
-Dynamic Fsync Control V1.5
-Added Intelliactive, Smartmax and SmartassV2 governors
-Led Control
-Panel Color Control
-mDnie mode adapter for Synapse
-Selinux Enforcing/Permissive
-Synapse Support
Click to expand...
Click to collapse
Installation instructions
You need to have TWPR, CWM o Philz Recovery.
Download the last kernel
Reboot in recovery mode
Make backup (recommended)
Flash the zip
Downloads
Strictly No Mirrors Please. In the event that you need to make one ask us first with purpose behind what valid reason.
Current Version
After flash the kernel go to play store and download Synapse apk.
Nadia nightly r7 KK (Mediafire)
App to control your display : Color Control
Old version
Nadia nightly r6 LL (Mediafire)
Nadia nightly r6 KK (MEGA)
Nadia nightly beta r5 (Mediafire)
Nadia nightly r3 (Mediafire)
Nadia nightly r4 (MEGA)
Nadia nightly r4 (AndroidFileHost)
Nadia nightly r3 (Mediafire)
Nadia nightly r3 (MEGA)
Nadia nightly r3 (AndroidFileHost)
Nadia nightly r2 (Mediafire)
Nadia nightly r2 (MEGA)
Nadia nightly r2 (AndroidFileHost)
Nadia nightly r1 (Mediafire)
Nadia nightly r1 (MEGA)
Nadia nightly r1 (AndroidFileHost)
Click to expand...
Click to collapse
Our Projects:
Emotion Revolution for N7100 XDA / HtcSpain
EmotionMIUI for N7100 XDA / HtcSpain
Nadia nightly kernel for N7100
Nadia nightly kernel for m7
N910F/G XDA


Source code:
Nadia kernel Github
Thanks To/Credits
Andip71, AndreiLux, apb_axel, Civato, Christopher83, DerTeufel, Faux123, Ffolkes, Flar2, Franciscofranco, Franlov, Friedrich420, Gokhanmoral, Infernum, LoungeKatt (TwistedUmbrella), Vanito, Yank555.lu, ZaneZam.
I hope I have not forgotten anyone!
Hit the "thanks" button if you like our work.
You can follow new updateshere (Spanish)
XDAevDB Information
Nadia Kernel, Kernel for the Samsung Galaxy Note 4
Contributors
Pafcholini, aukhan, jcanonico
Source Code:https://github.com/Pafcholini/Nadia-...-KK-OpenSource
Kernel Special Features: Faux Sound Support
Version Information
Status: Nightly
Current Stable Version: Nadia nightly r4
Stable Release Date: 2015-01-16
Current Beta Version: Nadia nightly beta r
Beta Release Date: 2015-01-27
Created 2015-01-01
Last Updated 2015-01-27
Twitter: @Pafcholini
Click to expand...
Click to collapse

Reserved
Recommended settings & FAQ Synapse and all available options:
- LIVE STATISTICS: Time in states, Uptime,etc.
- CPU - GOV: cpu scaling, cpu governor and governor tunables.
- CPU voltage: separate frequency voltage.
- GPU: GPU scaling min/max frequency, GPU governor, Simple GPU Algorithm.
- I/O: schedulers, internal storage read-ahead, externalSD read-ahead, Frandom Module, Scheldure Tunables Internal/External
- CPU DRIVERS: PowerSuspend and Intelli-Plug
- THERMAL: Intelli-Thermal Control
- MISCELLANEOUS: Dynamic FSYNC Driver, Logger Mode, CRC Settings, S-View bypass, Selinux Status, Optimize Database.
- BATTERY: Live Statistics and Fast Charge
- MDNIE/SCREEN: Panel Control, mDNIe Mode and mDNIe Mode Hijack
- LED: Led Control
- SCREEN WAKE CONTROL: Sweep2Wake Control
- KERNEL TWEAKS: low memory killer, kernel entropy, panic and panic on oops.
- NETWORK: tcp congestion control, hardering the TCP/IP stack to SYN attack,ignore pings,etc.
- VM-FS: dirty radio, swappiness,etc.
- BUILD.PROP: Build.prop Tweaks
- LOGS: Clearn Synapse, Logcat and Dmseg
- INFO-REBOOT: info about the kernel, reboots,etc.
Click to expand...
Click to collapse
Balance between performance and battery
Quote:
Above is what I use personally. MAY NOT be optimal for all. Share your settings.
CPU frequency: 2649MHz/300MHz
CPU governor: Intelliactive or Bluactive for performance/ Interactive for battery
CPU voltaje: -25uV ((Be careful!! If you low voltages much you can get bootloop or battery drain.)
GPU: default values
I/O schedulers: row for both
PowerSuspend: hybrid hook
MPDECISION for performance/ Intelli-Plug for battery
Intelli-Thermal: enabled
MISCELLANEOUS: fsync enabled, logger mode disabled, crc disabled (you choice), Selinux Permissive
TCP: westwood for both
Click to expand...
Click to collapse
Aukhan recommended settings
1.
2.
F.A.Q
Can I flash this kernel on Note 4 SM-N910C or other variant?
No, you can not. This kernel is only for SM-N910F, SM-N910G, SM-N910T and SM-N910W8.
When I switch to Ondemand governor I noticed that cpu-boost is disabled.
Exactly, Ondemand and cpu-boost doesn't work well together. When you switch to Ondemand governor cpu-boost will be disabled automatically. Don't re-enable cpu-boost if you are using Ondemand governor. (Synapse>CPU DRIVERS)
Which app can control this kernel?
By default, the kernel is controlled by Synapse, but you can use the app that you like (Trickster Mod, Kernel Tweaker, etc.).
I flashed the kernel and Synapse says: "No support UCI detected".
Reflash the kernel, since it was a bad installation and Synapse does not detect the scripts.
After flashing the kernel lost root what to do?
In case you loose root just flash SuperSU
Any recommended settings to follow using Synapse?
At the beginning of the second post.
After flash the kernel some apks give me FC.
Go to Google Play Store and reinstall those apks.
From where can I remove int.d script?
Go to /system/etc/init.d using any root based file manager and delete.
Note: There is an important one related to superSU and if you remove it by mistake you're gonna have trouble with root permissions.
My device doesn't show any reaction to undervolting (battery life is same as before) or gets unstable even on light undervolting?
Use DVFS disabler Module(standalone) (dynamic voltage and frequency scaling), this feature was kept in touchwiz for benchmark boosting purposes and will conflict with any undervolting and custom governors because it scales the voltages and frequency on regular intervals and is framework integrated, so gets a higher priority than kernel based voltage and scaling controls.
For people who don't know what is DVFS please refer Wikipedia.
Min/Max frequency don't stick?
If your frequency settings don’t stick, it's because on certain Qualcomm devices, there are certain system services (thermald/mpdecision/project butter) or kernel service that rewrite frequency settings based on current thermal status and/or touch input.
I made a logcat but my file is empty. How I can "fix" it?
By default Android logger is disable. Go to Synapse > MISCELLANEOUS and enable Logger Mode.
What is it PowerSuspend?
This new powersuspend PM kernel driver is a replacement for it and existing early_suspend drivers. It should give better battery life.
What is it Intelli-Plug?
Intelliplug is a replacement for mp decision. Intelli-Plug is Faux123 open source solution to Qualcomm's closed source mpdecision. Intelli-Plug is disable by default. It conflicts with mpdecsion, so is HIGHLY recommend turning off mpdecision when using intelli-plug! (If you use Synapse the change is automatic. If you enable Intelli-plug mpdecision will turn off).
What is it Intelli-Thermal?
an intelligent MSM thermal throttling kernel driver designed to replace the
closed sourced thermald(aemon) from Qualcomm.
What is it Frandom?
Frandom is a kernel random number generator, which is 10-50 times faster than what you get from /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
What is it CRC?
CRC is a mechanism aiming to prevent data corruption when is enabled (reduce the performance around 30%). So if you disable it improve the performance but your data can be corrupted. Use it at your risk.
/sys/module/mmc_core/parameters/crc

Reserved1
Know/Reported/Fixed issues Know issues
1. Synapse doesn't show CPU governor tunables.
I'm trying to fix it. FIXED
2. Sometimes Synapse (and others kernel control apks) show that the min frequency is 1190MHz (or other frequency).
Just cancel it. FIXED
3. Ondemand doesn't work well. FIXED
Thanks for the report @Vangelis13
Any other Issues you may Report us and we will fix it

Reserved2
Reserved2

Reserved3
Reserved3

Reserved4
Reserved4

Reserved
Reserved last

Does WiFi calling works in this kernel?

mliou said:
Does WiFi calling works in this kernel?
Click to expand...
Click to collapse
I am assuming yes could you please flash and report back.

aukhan said:
I am assuming yes could you please flash and report back.
Click to expand...
Click to collapse
I will test it tonight but I read somewhere that it needs to be based on T-Mobile source for it to work.

I just want to say that I'm SO glad to see this thread / kernel in this subforum. To all my fellow N910T users: I've been using this kernel for a few weeks now after testing every other kernel available, and I've had the best experience by far on my N4 running Nadia kernel. The most recent release is incredible; stable as... something that's super-stable , FauxSound implementation! I have the paid FauxSound app and the sound quality of everything (in call and otherwise) is simply fantastic, if anything ever "goes wrong" for any reason, in my experience booting into recovery, reflashing the kernel and wiping dalvik/cache will fix it 99% of the time. I really encourage N910T users to give this kernel a shot. It solved pretty much every problem I was experiencing previously with my N4, and really made it run like I felt that the current primo device on the market should run! :good:
Edit: Make sure to install BusyBox on Rails, free from the Play store along with this kernel. You'll have problems with Synapse otherwise... very important - just wanted to make a note of that Also, settings-wise, I mostly used @aukhan's settings in the video and undervolted -25mV across the board, which is a very solid place to start from.

Just FYI wifi calling fails to connect

papped said:
Just FYI wifi calling fails to connect
Click to expand...
Click to collapse
I think the only way this works is if OP start from scratch using tmobile base.

I can also confirm that Wi-Fi calling gets error 82 failure to connect while using this kernel.
That said, if you don't need Wi-Fi calling this is an excellent, snappy, and stable build from my testing despite being in beta. I live in an area with good signal and I am impressed with it for sure. Dev has done good work here and brought another excellent kernel option to our device. :good:

jazzmachine said:
I just want to say that I'm SO glad to see this thread / kernel in this subforum. To all my fellow N910T users: I've been using this kernel for a few weeks now after testing every other kernel available, and I've had the best experience by far on my N4 running Nadia kernel. The most recent release is incredible; stable as... something that's super-stable , FauxSound implementation! I have the paid FauxSound app and the sound quality of everything (in call and otherwise) is simply fantastic, if anything ever "goes wrong" for any reason, in my experience booting into recovery, reflashing the kernel and wiping dalvik/cache will fix it 99% of the time. I really encourage N910T users to give this kernel a shot. It solved pretty much every problem I was experiencing previously with my N4, and really made it run like I felt that the current primo device on the market should run! :good:
Edit: Make sure to install BusyBox on Rails, free from the Play store along with this kernel. You'll have problems with Synapse otherwise... very important - just wanted to make a note of that Also, settings-wise, I mostly used @aukhan's settings in the video and undervolted -25mV across the board, which is a very solid place to start from.
Click to expand...
Click to collapse
Thanks a lot as you were first to confirm that the kernel is running smooth that is when we decided let's have a dedicated thread in here.

AlkaliV2 said:
I can also confirm that Wi-Fi calling gets error 82 failure to connect while using this kernel.
That said, if you don't need Wi-Fi calling this is an excellent, snappy, and stable build from my testing despite being in beta. I live in an area with good signal and I am impressed with it for sure. Dev has done good work here and brought another excellent kernel option to our device. :good:
Click to expand...
Click to collapse
Starting from the scratch becomes a little difficult I am sure there should be an alternate way of fixing this let me talk to @Pafcholini as he has moved to new place Internet is not setup yet so waiting for him.

AlkaliV2 said:
I can also confirm that Wi-Fi calling gets error 82 failure to connect while using this kernel.
That said, if you don't need Wi-Fi calling this is an excellent, snappy, and stable build from my testing despite being in beta. I live in an area with good signal and I am impressed with it for sure. Dev has done good work here and brought another excellent kernel option to our device. :good:
Click to expand...
Click to collapse
Starting from the scratch becomes a little difficult I am sure there should be an alternate way of fixing this let me talk to @Pafcholini as he has moved to new place Internet is not setup yet so waiting for him.

Flashing now.

Ditto

Me, too.

[Kernel][FEATURED] Venom Kernel v3.1 [aio_otfp][MM][N]

{
"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"
}
Venom Kernel for K3 Note (aio_otfp) -- Based on Renice kernel source
Venom is designed for maximum performance and battery backup. It is made for people who depend on their phone every day.
It is feature Enriched kernel which makes your device even better than before.
Compiled with UBERTC 6.x
Features :
RGB color control
Working LED.
Vibration control using thunderquake engine module by varun.chitre15
Performance optimizations
USB fast Charging enabled by default
TCP Congestion Algorithm (TCPCA) set to Westwood by default
All other TCPCA added
Double tap to wake enabled
So much customisable dt2w, like screen area, time for tap, relative distance between taps... Much more
Fixes for blueborne bluetooth vulnerability at kernel level
Entropy tweaks -- Increased entropy values in random.c
Network tcp window tweak -- Lock window size to full for maximum speed
Enabled Forced fast charge
CPU governors :
(In alphabetical order)
Alucard
Conservative
Darkness
Intelliactive
Intellidemand
InteractiveB
InteractivePlus
Ondemand
Pegasusq
Performance
Poison --- Default custom governor made by me (based on ThunderX)
Powersaver
Renice
ThunderX
Userspace
Wheatley
Features of my Poison governor :
Dynamic CPU frequency transition mode engine. More info in Poison governor thread.
Smoothness tuning.
Best governor for this device because it is K3-specific
Custom tunables :
Can be found here, in my poison governor thread.
Has a total of 12 custom tuneables !!!!! :laugh::victory::highfive:
NOTE : There are 21 only for A7000-a and K3 release only has 12 tunables.
https://forum.xda-developers.com/lenovo-a7000/development/explanation-poison-cpu-governor-t3691304
(All information about the modes and tuneables in Poison governor thread)
Installation :
For custom roms:
Reboot to recovery
Flash the Kernel Zip
Reboot to system and Enjoy
For Vibe/Bootlooping Roms:
Reboot to Recovery
Take Nandroid backup of boot partition
Unpack ROM's boot.img (present in ROM zip almost always)
Replace the kernel file (Image-gz.dtb, bootimg-kernel, zImage) with proper name
Repack the boot image and flash
Reboot to System and Enjoy
Download links and Changelog :
See second post
Works Better in Custom roms (MM and N (based on MM libs) only)
Stock + Vibe Roms also Supported [MM only]
Note:
* Take a Nandroid backup before installing
Appreciate me by thanking me... Or... You could donate to me if you're an Indian!!!
Donation :
How to donate ??
---> Simple. Send me a PM or mail me ( [email protected] ) and say that you're willing to donate. Further instructions will be sent by me.
---> Or you can simply gift me xda ad-free
I also want to build venom for myself!
Sure! You can find the link for the venom kernel source below in xda DevDB info.
The source link is for A7000 device only so it doesn't work on K3 out of the box.
Everything that venom has is present in the given source link.
You can pick the features from there and Base it on renice source by sandeep.sethi
XDA:DevDB Information
Venom Kernel for aio_otfp [MM][N], Kernel for the Lenovo K3 Note
Contributors
tanish2k09, Sandeep.sethi, GSandeep, daniel_hk, Aryan Kedare, Rohan Taneja, Team M.A.D
Source Code: https://github.com/tanish2k09/Kernel_aio_row-Venom-S/
Kernel Special Features: Custom CPU governor, custom code, dynamic tuneables
Version Information
Status: Stable
Current Stable Version: 3.1
Stable Release Date: 2017-11-15
Created 2017-11-15
Last Updated 2018-04-22

Latest build :
Venom carnage edition :
http://goo.gl/r5KhkA
Old builds :
http://goo.gl/BuwKEh
(Venom kernel initial maximum edition)
Changelog :
Latest Build (Carnage) (25122017) :
Code:
1) Tweaked poison for more performance. Now you will feel that kernel is much more smooth than ever.
2) Added vibrator engine with real-time linking with poison. You'll feel it when you try yourself and see what this means.
3) Upgraded to dt2w 2.0 with haptic feedback (customisable vibration level) and more efficient structure and checks. My code is 1/3 of original code. Now dt2w is much faster and smoother.
4) Livedisplay fixed thax to painkiller3
5) WiFi autoconnect fixed thax to [user=4948627]@daniel_hk[/user]
6) Open hotspot fixed (use hotspot fix zip by sandeep) with venom
7) Added pocket mode override mechanism. Now you can tap 3 times within 0.8 seconds to override proximity sensor. Number of taps and timeout is customisable with poison.
8) New tunables details :
a) dt2w_vibe : Control vibration level on dt2w. Change to 0 to disable dt2w haptic feedback.
b) vibrator_on_lock : Disables vibrator on screen off completely. Capacitive buttons won't vibrate on screen off, notifications won't vibrate phone on screen off, but calls will turn screen on and then vibrator will activate. This is a good feature for those who want no notification disturbances but also don't want to enable silent mode.
c) pocket_mode_dt2w_override_taps_number : This is the value of the number of taps that you will have to tap within timeout to wake up the screen even in proximity mode.
d) pocket_mode_dt2w_override_taps_timeout : This is the value of the time in milliseconds within which you will have to tap to override pocket mode.
e) dt2w_tap_distance : Merged dt2w_tap_distance_x and _y into a single variable and changed the distance calculation from rectangular linear to circular radial. This us the radius of the circular region with the center as the first tap coordinates, within which you will have to tap second time within timeout to activate dt2w. Easy.
9) Merged x and y distance tunables into a single radius.
10) Enabled 5Ghz WiFi by default (thanks to daniel_hk) (request by [user=4695623]@FPSUsername[/user])
11) Enabled 7 cores while booting. (Thax to gsandeep)
Build 15112017-1244 :
Code:
Initial release.

Misc
Deleted and reserved again.

Users told me that the link I posted was bootlooping.
I've uploaded a last known working stable build instead.
Link in post 2 updated.
Kindly re-flash

tanish2k09 said:
Users told me that the link I posted was bootlooping.
I've uploaded a last known working stable build instead.
Link in post 2 updated.
Kindly re-flash
Click to expand...
Click to collapse
Great Work!
And
Im here for testing your kernel.

Works on stock 6.0 roms?
Or just for 7.0 LOS based?

Is there a posivility having bootloop if normal flashing it kn vibesavon 3.6?

inouext said:
Works on stock 6.0 roms?
Or just for 7.0 LOS based?
Click to expand...
Click to collapse
It works on all roms which are compatible with renice kernel.
TatsuyaKaneki2015 said:
Is there a posivility having bootloop if normal flashing it kn vibesavon 3.6?
Click to expand...
Click to collapse
Same behaviour like renice kernel.
I have mentioned that I don't have device so you can't expect me to tell you anything related to working or not working.
However, since this kernel is based on renice, it will do the exact same things like renice kernel. Think of this kernel as a renice kernel but with some extra features.

Anyone tested this, how the performance after this??

Eduardo27 said:
Anyone tested this, how the performance after this??
Click to expand...
Click to collapse
You should try yourself instead of asking others.
Your own opinion matters. :good::highfive:

u did a good job on poison...getting good screen on time...but there's some drawbacks like it lags while trying to play 1080p 60 fps in youtube...and lags while browsing with chrome
yup it's kind of laggy... even while browsing through photos..using es file manager+so on......
I'm in mode 1....I know mode 2 would be smoother....
but I'm liking the battery backup.....is there any possible way to tune up it a little more to get a little more performance +backup balance?
@tanish2k09

Cpt.mactavish said:
u did a good job on poison...getting good screen on time...but there's some drawbacks like it lags while trying to play 1080p 60 fps in youtube...and lags while browsing with chrome
yup it's kind of laggy... even while browsing through photos..using es file manager+so on......
I'm in mode 1....I know mode 2 would be smoother....
but I'm liking the battery backup.....is there any possible way to tune up it a little more to get a little more performance +backup balance?
@tanish2k09
Click to expand...
Click to collapse
It is quite obvious that battery backup and performance are inverse of each other. Both can't be perfect at the same time. One of them has to be sacrificed for other.
I'm warning you that increasing performance WILL decrease BB.
In case you still want to proceed to a better performance, do following :
1) Change poison tuneable "Awake_ideal_freq" to the max freq (16xx)
2) Or use some more powerful governor. Note that others aren't mtk-specific so battery backup will be less than poison 100%
3) While the step 1 should be enough for faster processing, you may use poison with addition to mode 2.
4) Change ROM to other than compiled nougat ones. They have a lag problem with low cpu frequencies. Marshmallow should be fine.
5) For faster pic loading, it has been tested that fiops iosched performs fastest. Slightly noticable.
6) Use darkness governor as an alternative for slightly performance oriented device.
// Destroy the thanks button on my post and kernel if you like it

Sir, does this kernel support with lenovo a7000 plus? Because i got bootloop when flash the kernel. Not even reaching the boot animation, its just get on the first lenovo logo then just black screen, and sometimes keep rebooting. Really wanted to try it.
device : Lenovo a7000 plus
twrp : 3.1.1-3 when install rom then 3.0.2-7 to install modem patch for a7k plus.
rom : Daniel_hk's latest LineageOs rom, (31oct)

tanish2k09 said:
It is quite obvious that battery backup and performance are inverse of each other. Both can't be perfect at the same time. One of them has to be sacrificed for other.
I'm warning you that increasing performance WILL decrease BB.
In case you still want to proceed to a better performance, do following :
1) Change poison tuneable "Awake_ideal_freq" to the max freq (16xx)
2) Or use some more powerful governor. Note that others aren't mtk-specific so battery backup will be less than poison 100%
3) While the step 1 should be enough for faster processing, you may use poison with addition to mode 2.
4) Change ROM to other than compiled nougat ones. They have a lag problem with low cpu frequencies. Marshmallow should be fine.
5) For faster pic loading, it has been tested that fiops iosched performs fastest. Slightly noticable.
6) Use darkness governor as an alternative for slightly performance oriented device.
// Destroy the thanks button on my post and kernel if you like it
Click to expand...
Click to collapse
your fastcharging seems to be good too.....I'm using gsandeep's unofficial RR....so far it is the best rom for k3.....
I've changed to mode 2..which is performance oriented ....and performance has increased..... but I thought is there any tweak to be made for tweaking mode 1...for slight performance increase...

Cpt.mactavish said:
your fastcharging seems to be good too.....I'm using gsandeep's unofficial RR....so far it is the best rom for k3.....
I've changed to mode 2..which is performance oriented ....and performance has increased..... but I thought is there any tweak to be made for tweaking mode 1...for slight performance increase...
Click to expand...
Click to collapse
Step 1 and step 6
Good to hear that you're liking the kernel. Unfortunately there are only 12 customisable variables in k3 version. My a7000 has almost everything customisable from cpu modes to dt2w screen trigger area to gesture sensitivity...

tanish2k09 said:
Step 1 and step 6
Good to hear that you're liking the kernel. Unfortunately there are only 12 customisable variables in k3 version. My a7000 has almost everything customisable from cpu modes to dt2w screen trigger area to gesture sensitivity...
Click to expand...
Click to collapse
btw,your kernel doesn't support livedisplay of LOS/LOS based roms...any fix for that?

Cpt.mactavish said:
btw,your kernel doesn't support livedisplay of LOS/LOS based roms...any fix for that?
Click to expand...
Click to collapse
I didn't get the time to add that.
I can't help you with it this year at least.
My main motive for releasing this kernel was to prove my skills with my poison governor. There are people like daniel_hk himself who doubt me greatly. He is failing to understand that I am not underskilled, but rather I prefer to not spend the time I have right now as a student, into ROM development.
With poison, you would experience at least 10-15% battery increase and a decent performance, unless needed for heavier tasks, which can be adopted to using the modes.
I hope you liked poison. Maybe early 2018 I will update this kernel with more new features. One of them being livedisplay. If you actually see, there isn't too much time to wait. It's just a month approx and you'll not even know when it passes. That's the thing about time. It's mind-boggling
//Some people need to learn to press the thanks button.

looking for your next updates....with livedisplay....and hope to have more optimizations...on backup+minimum usable performance

Battery Backup
Please tell me about battery backup of k3 note after flash this kernel in vibe os . ???

Like Renice kernel v11, sometimes wifi dropped and not auto reconnect. Can you fix that in next version?

Database Info

welcome