Welcome To Beastmode M7 for sense 5 android 4.2.2
{
"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"
}
There will be kind of a new way for you guys to check the status of the build the changelog and last a place for you to collect these finished downloadable zips
Below you will find a badge that will change to indicate the current build status... Failed, In progress, Success. Once you see success you can check the status of the builds here Buildmachine Thanks Showp for sharing
So where can I get these automagic builds??????!??!
You can find these builds on my Goo.im account. I will try to keep the folders in Current/Old builds
REMOVED
What the heck is with the zip name?!?!??! I can't make heads or tails of this!
Blackout_m7_20130506_205451_master-4a9e1a6
The Device Tree that was built
The date and time the kernel was built so in this example its 05/06/2013 @ 20:54min51seconds
Branch Name that was built
Shasum of last commit before build
But where can I find this Elusive changelog?!?!?!
http://repomachine.zapto.org/zarboz/blackout-m7/commits/master
https://github.com/Team-Blackout/Blackout-M7/commits/master
Source My github
Build machines github
Changelog
Last updated 06/02/2013 @ 6:52pm MST
Code:
78a0add updating defconfig
ef840d0 Revert "media: apply camera changes from 1.29.401.2_R"
39f1fcc gadget: enable adb by default
1b7caf8 get rid of hci_get_drvdata
612181c Revert "msm_rotator: bulk update from caf"
c553923 fixing unknown iocttl
8766980 final import of CAF drivers still have to cleanup
edd96a7 add vfe iommu domains back
a9f542b ion: ioctl compatibility with userland using old api
ac4d24c msm_rotator: bulk update from caf
0c6c24a Kbuild: copy msm headers
764fa23 iommu and ****.
c6d8bb2 kgsl and video/msm from msm8960 2.5 branch
0549a54 Init wfd writeback panel later ..
90b8f93 More clock changes for iommu
d8cc5b2 msm-3.4 (commit 35cca8ba3ee0e6a2085dbcac48fb2ccbaa72ba98) video/gpu/iommu .. and all the hacks that goes with that
c7578a3 m7-gpu: add adreno versioning logic according to soc
fa39db5 A bunch of crap. initial dcvs, some hacks in f_projector, a hack delaying writeback_panel init so that device one is inited first, some missing files, some board/devices things ..
6b32930 Updated iommu/msm_bus
18cbc69 Second row
72acfec First raw of porting old to new ion api calls
8651440 Copied caf 2.5.1 video/gpu genlock and rotator [WIP]
6e6fbc8 patching to 3.4.18
83c4a31 increasing readahead
3a564eb Fixing compile error
e28c7d8 patching upstream to 3.0.17
Man _______ doesn't work or is not working righ!!!!!!!!!!
If coming from Flar2's kernel you NEED to flash the stock boot.img attached to this post BEFORE you flash beastmode other wise you will receive a failure to boot
You can report all bugs on my bug tracker located here :
Bug tracker
The proper format for reporting is on the google code page but please attach the following to your bugreport post:
Adb logcat dump of event
kmesg dump of event < dont know what that is ?? here is a easy way to get it
after you have the problem promptly reboot your phone
Code:
adb pull /proc/last_kmsg ./last_kmsg.txt
this will spawn a .txt file in the directory your shell is in upload this file this will suffice for a stacktrace
If you fail to report a bug with a logcat+kmsg i will close it and ignore the bug until you provide a log
I WILL NOT REPLY TO BUG REPORTS IN THREAD PLEASE FILE A BUG REPORT AS INSTRUCTED IF YOU WANT YOUR PROBLEM RESOLVED IN A TIMELY MANNER!
Things I know are broken!
- Video playback only third party Software decoding (stuff like youtube wont work sorry guys)
- Infrared
- Im sure there is more
MSM_ThermalD
Kernel based 3-phase thermal control!
This replaces your /system/bin/thermald binary which is renamed by the installer to thermald_bck.
It will throttle your cpu speed to keep it cool and unleash it if the cpu has cooled down enough. (3 phases: low, mid and high)
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
Default: 100ms (=0.1sec)
shutdown_temp = if we reach this shut down the device!
Default: 80°C
Click to expand...
Click to collapse
MSM_MPDecision
100% kernel based multi core decision! (should cpu1/2/3 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_bck.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (20000)
delay = time between checks (70)
pause = if something else plugs in the cpu, fall asleep for 10000ms (10 secs)
scroff_single_core = if the screen is off, don't plug in cpu1/2/3. Additionally: Unplug all cpus except cpu0 when screen is turned off (1)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
min_cpus = min cpus to be online, cannot be < 1. Default: 1
max_cpus = max cpus to be online, cannot be > 4. (if you set it to 2 and min_cpus to 1 you will basically have a dualcore) Default: 4
idle_freq = a value against that will be checked if a core +/- is requested. (486000)
If cpu0 is below that value and a core up of another cpu is requested, nothing will happen.
If any other cpu is above that value and a core down of that cpu is requested, nothing will happen. (otherwise it would now put down that cpu even though it is still working, which isn't what we want)
Hot plug thresholds (aka now it gets 'complicated')
This small formula calculates which value will be used: (number_of_cpus_online - 1) * 2
The result of this formula will be the nwns_threshold where a new cpu is hotplugged.
The result of this formula + 1 will be the nwns_threshold where a cpu is unplugged.
nwns_threshold_x = runqueue threshold, if this is reached cpuX will be hot/unplugged
twts_threshold_x = time threshold, this amount of time must have passed for the related action to be taken (hot/unplug)
Example:
One cpu is online.
(1 - 1) * 2 = 0 ergo:
nwns_threshold_0 = cpu1 will be hotplugged at this value
((1 - 1) * 2) + 1 = 1
nwns_threshold_1 = cpu0 will be unplugged at this value
Since we can't unplug cpu0 this is '0'.
Two cpus are online.
(2 - 1) * 2 = 2 ergo:
nwns_threshold_2 = cpu2 will be hotplugged at this value
((2 - 1) * 2) + 1 = 3
nwns_threshold_3 = cpu1 will be unplugged at this value
etc...
The default values are:
NwNs_Threshold: 12, 0, 25, 20, 32, 28, 0, 35
TwTs_Threshold: 140, 0, 140, 190, 140, 190, 0, 190
Where the position and function of the number equals the result of the above explained formula.
(all times are in ms)
If you want to see the mpdecision magic happening:
Click to expand...
Click to collapse
What is ARM Topology:
ARM Topology allows individual queue'ing of tasks to cores by the scheduler, For intelligent load balancing and more data crunching power. This has come from the Linaro Team you can view the most recent patch at from http://patches.linaro.org/9894/ all patches at http://patches.linaro.org/project/linux-arm-kernel/
Click to expand...
Click to collapse
What is BB ?!
Blinking Backlight Buttons
n3ocort3x said:
BLINK BUTTONS
VIDEO:
Click to expand...
Click to collapse
Ok guys enjoy Sense 4.2.2 kernel
shoot a thanks over to Flemmard and the CM10 as they did ALL MY HARD WORK BY PORTING THE DRIVERS I JUST PICKED THEIR CODE!
Thanks @Zarboz!!
By the way when you said video playback is partially broken. Is the hardware decoding total broken or is it just only youtube?
Riyal said:
Thanks @Zarboz!!
By the way when you said video playback is partially broken. Is the hardware decoding total broken or is it just only youtube?
Click to expand...
Click to collapse
the codec that complains is OMX for youtube appears its for all playback but camera can capture still
im working on a fix
Zarboz said:
the codec that complains is OMX for youtube appears its for all playback but camera can capture still
im working on a fix
Click to expand...
Click to collapse
Thanks! Will try to look for a fix for this also. I had encountered these problems when making an ICS kernel on the Mytouch 4g slide a year ago.
I got it fixed by porting the vidc & libs which I ripped from the HTC One S though...
And regarding camera the viewfinder is using a different driver so there's no connection on them. However did you try video recoding on camera? The video recorder should use OMX also when recording since it's transcoding video resolution. So if my guess is right video recording should be broken too. It's either the camera app would force close or you would get a video showing only black color.
Riyal said:
Thanks! Will try to look for a fix for this also. I had encountered these problems when making an ICS kernel on the Mytouch 4g slide a year ago.
I got it fixed by porting the vidc & libs which I ripped from the HTC One S though...
And regarding camera the viewfinder is using a different driver so there's no connection on them. However did you try video recoding on camera? The video recorder should use OMX also when recording since it's transcoding video resolution. So if my guess is right video recording should be broken too. It's either the camera app would force close or you would get a video showing only black color.
Click to expand...
Click to collapse
I could grab the vidc from the CAF tree the egl came from
Sent from my HTC One using xda premium
Could someone point out the differences in the two kernels by the same dev..I can see one is linaro compiled..and has a higher linux version number..
Sent from my HTC One using Tapatalk 4 Beta
aamitabh28 said:
Could someone point out the differences in the two kernels by the same dev..I can see one is linaro compiled..and has a higher linux version number..
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
One is for sense 5 android 4.2.2 leaks one is for normal roms
Sent from my HTC One using xda premium
Nice, the Beast has been released. Who cares about youtube
jlevy73 said:
Nice, the Beast has been released. Who cares about youtube
Click to expand...
Click to collapse
This is for the 4.2.2 base josh
Checkout the other thread fir 4.1.2 kernel
Sent from my HTC One using xda premium
Zarboz said:
This is for the 4.2.2 base josh
Checkout the other thread fir 4.1.2 kernel
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I know, I'm on 4.2.2 so going to test your new kernel out now.
Or when the server comes back online
jlevy73 said:
I know, I'm on 4.2.2 so going to test your new kernel out now.
Or when the server comes back online
Click to expand...
Click to collapse
http://db.tt/i01CCG91
Sent from my HTC One using xda premium
Zarboz said:
http://db.tt/i01CCG91
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks my friend
I'm going through all the governors and I'm stuck between Intellidemand , SmartassV2 , Smartmax. Which one delivers the best battery ? I'm looking through governor controls and they have all different frequencies techniques. Any suggestions Zarboz ? I did notice while doing advanced setup for the kernel the default was listed as smartmax. Any particular reason. Ty for the input
after flashing this kernel. the phone stucks at the htc boot screen with red warning. :-\
Sent from my HTC One powered by TrickDroid
Hopie said:
after flashing this kernel. the phone stucks at the htc boot screen with red warning. :-\
Sent from my HTC One powered by TrickDroid
Click to expand...
Click to collapse
Are you running a 4.2.2 based Rom?
Sent from my HTC One using xda premium
Zarboz said:
I could grab the vidc from the CAF tree the egl came from
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes but you would need the corresponding libs that matches with the vidc driver where you will be taking it. That's why I mentioned yesterday about the ripping S4 sources and libs because practically they are the same hardware wise at least on the GPU and processor.
Related
motley kernel for the Nexus 7 and Jellybean
Disclaimer: You know the gig...I am not responsible for damaging your device or voiding your warranty. Play at your own risk!
ROM devs/cooks: If you want to use this kernel in your ROM, I am fine with that, but please include a "thanks" and a link back to this thread. Thanks!
Requirements (please read carefully and visit the other dev threads as necessary)
You must be unlocked and rooted.
You must have custom recovery installed (CWM or TWRP) to install the kernel.
Busybox is required for init.d support.
Do a backup using custom recovery (CWM or TWR) so you can restore your boot.img and ROM if necessary!
Have your ROM zip in /sdcard so you can restore your ROM if necessary.
System Tuner is recommended for tuning the CPU, especially for voltage control.
Main Features
GPL compliant - source is kept up to date at github.com and released at the time the kernel is released to the public for all builds. Ask other devs to do the same!
Asus\Nvidia\Google Linux 3.1.10 base. All stock features are supported (camera, OTG, NFC etc.)
OC to 1.6GHz (optional)
Voltage control - be careful to not save the setting on boot until you are 100% sure!
GPU OC from 416 to 520MHz (default is 446, adjust as you wish up to 520MHz)
Dynamic EDP - allows EDP to remain enabled (safer), but with an added simple temperature throttle switch (based on Asus Prime)
Compiler optimizations (-O2) - using Linaro 4.7 ARM toolchain
I/O schedulers - row (default), SIO, V(R), CFQ, NOOP, and deadline
TCP Congestion Control - default cubic + several different algos to choose from.
ZRAM - must be enabled by a script
Governors - Interactive (default), Performance, OnDemand, PowerSave, Conservative
initramfs - insecure (your ROM must have busybox)
CIFS/UTF8, NFS, NTFS r/w, TUN - built-in, no need for any kernel modules
fsync sysfs enable/disable switch (defaults to fsync enabled)
kexec with hardboot (for supporting Linux/MultiROM)
Many other misc patches and tweaks (see github link below)
Install:
Check the requirements above!
Flash the zip using custom recovery (no need to wipe anything)
See post 2 for performance tweaks and more info
build #249 for Jellybean 4.2.2 - WiFi and 3G 2013-02-24
Added ability to change GPU clock speed at runtime (referenced franco, morific, and metallice git repos)
Added row io scheduler and set as default (Tatyana Brokhman)
Added TCP Congestion Control, several different algos to choose from. Default is cubic (stock).
Added optimized ARM RWSEM (Ezekeel)
Input patch (Henrik Rydberg)
View attachment motley_anykernel_N7_build_249.zip
build #247 for Jellybean 4.2.2 - WiFi and 3G 2013-02-17
Merged 4.2.2 patches
Updated Linaro toolchain to 2012.12
View attachment motley_422_nexus7_anykernel_build_247_446GPU.zip
build #246 for Jellybean 4.2.1 - WiFi and 3G
kexec\MultiROM support
Download from here since I posted in the MultiROM thread
build #244 for Jellybean 4.2 - WiFi and 3G - Recommended for WiFi and 3G on 4.2.x
446 GPU build (stock + 30MHz). Let's see if this fixes touchscreen issues for those having them. My theory is that after the GPU heats up, this starts to affect touchscreen behavior on some devices. This is likely what happened to me on build 234 when I was testing. The GPU definitely gets hot on this device even with normal usage at 484+. At 446 this doesn't happen. IMHO, we are reducing the life of the device by overheating the GPU repeatedly. My Antutu scores actually tested higher after I flashed the 446 build.
Supports Android Jellybean 4.2.x
Reverted some commits from 233
Removed KSM from config, no ROM is using this AFAIK
Panel clock reduced to match Nvida cardhu sources (74180000). Having the panel clock cranked up fakes out scores on some benchmark tests, but adds no real value.
View attachment motley_nexus7_anykernel_build_244_446GPU.zip
Previous builds and release notes
build #234 for Jellybean 4.2 - First properly working 3G build
Supports Android Jellybean 4.2.x
Only change - added CONFIG_USB_NET_RAW_IP=y to hopefully address any issues with 3G (reported working by DiamondBack)
View attachment motley_nexus7_anykernel_build_234_484GPU.zip
build #233 for Jellybean 4.2 - if you don't have issues with GPU OC @484, this build may work well for you.
Supports Android Jellybean 4.2.x
Updated to latest Linaro toolchain 2012.10.22 and tweaked some compiler options.
Should support 3G as I have merged the Google patches, but I have not tested this.
Removed WiFi PM_FAST toggle as I see no need for this (PM_MAX for better battery is already the default in stock)
Stopped logging temp warnings until lit gets to 65C near the EDP throttle limit.
Quad-core tweaks - referenced showp1984's bricked grouper kernel source
See github for other minor details.
View attachment motley_nexus7_anykernel_build_233_484GPU.zip
build #232 - Recommended for WiFi on 4.1.2
Added support for Android Jellybean 4.1.2
Updated to latest Linaro toolchain 2012.10.22.
View attachment motley_nexus7_anykernel_build_232_484GPU.zip (GPU OC 484MHz)
stable v1.1.1 - builds #218-220 - Recommended for WiFi on 4.1.0 or 4.1.1
Supports Android Jellybean 4.1.1 or 4.1.0
DVFS tweaks and drop top cpu frequency to 1600, not much is lost and it should now be stable for everyone I hope. We pushed the envelope to 1.7 and 1.624 and now we are back to real world sensible decisions. My Nenamark2 520 GPU scores actually went up.
Dynamic EDP temp adjusted from 67 to 68C to catch temp notifier quicker when cooling back down.
Other miscellaneous patches
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
View attachment motley_anykernel_nexus7_1.1.1_NoGPUOC_build_220.zip (GPU stock 416GHz)
View attachment motley_anykernel_nexus7_1.1.1_GPU484_build_219.zip (GPU OC 484MHz)
View attachment motley_anykernel_nexus7_1.1.1_GPU520_build_218.zip (GPU OC 520MHz)
alpha v1.1.0 - builds #213-215
Added fsync sysfs enable/disable switch (thanks Ezekeel). fsync is still enabled by default. For more info and how to disable, see post 2.
Experimental: now forging speedo id 4 and process id 2 so that EDP limits are slightly raised and it narrows everyone down to a common DVFS record for everyone. Raised Dynanic EDP governor to 67C (from 60C) to give a little more room before edp is allowed to enable.
Minor cpu voltage table tweaks aiming for slightly better battery for those that don't undervolt.
Lowered the cold offsets from 50 to 25 for the top 4 cpu voltage slots. This will give folks a little more breathing room when undervolting and may help cold performance a bit if your voltages are lowered close to their lower limit.
Deadline i/o scheduler (morfic's secret 1:1 sauce that I remember back from my Iconia A500 days!). SIO is still the default, but we can try it out and see what we think.
OnDemand really wasn't usable in it's stock state since it was so laggy, so I have made some tweaks to the tuneables and it seems to be better now for those that want to give it a spin. Interactive is still the default governor.
cpu transtition latency lowered - fairly certain that it only affects OnDemand governor and not Interactive (reference morfic and http://permalink.gmane.org/gmane.linux.ports.tegra/1649)
Reverted most of the adjustments to the tegra 3 algorirthim for bringing cpus online and offline. I think it livened it up, but at the expense of battery.
Added kernel config option BCMDHD_WIFI_PM (thanks Ezekeel). See post 2 on how to enable it (not recommended unless you have music steaming issues when the screen is off). Not yet tested.
Other miscellaneous tweaks
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
View attachment motley_anykernel_nexus7_1.1.0_NoGPUOC_build_214.zip (GPU stock 416GHz)
View attachment motley_anykernel_nexus7_1.1.0_GPU484_build_213.zip (GPU OC 484MHz)
View attachment motley_anykernel_nexus7_1.1.0_GPU520_build_215.zip (GPU OC 520MHz)
stable v1.0.12 - builds #175-177
Changed highest frequency back to 1.624GHz and core voltage back to 1200mV. After experimenting with higher core voltages and 1.7GHz probing our limitations, it just doesn't seem right on this tablet. Why fry the butter?
CPU voltage is capped at 1237, so don't set it higher than that if tuning.
Refresh rate now adjusted with GPU OC clock at compile time. Higher FPS should be realized at 484 and 520 for most (thanks to clemsyn for sharing his research and findings)
Adjustments to the tegra 3 algorirthim for bring cpus online and offline, especially for the OC frequencies.
Fixed GPU clock compile time switch. Removed 500MHz choice.
Set cpu frequency policy to 1.3GHz on startup. This should help with heat build-up on startup and users where the highest OC clock rate is not desired.
Lowest brightness setting set back to stock since several users were requesting it (18 back to 13).
Minor adjustment to the interactive governor to make it slightly more responsive when demands increase.
PowerHAL change so it doesn't mess with a couple other interactive governor tunables on init.
All frequencies throughout the power range should be used in a more balanced manner.
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
View attachment motley_anykernel_nexus7_1.0.12_NoGPUOC_build_177.zip (GPU stock 416GHz)
View attachment motley_anykernel_nexus7_1.0.12_GPU484_build_176.zip (GPU OC 484MHz)
View attachment motley_anykernel_nexus7_1.0.12_GPU520_build_175.zip (GPU OC 520MHz)
alpha v1.0.11 - builds #126-128
Changed highest frequency from 1.624 to 1.7GHz
Increased core voltage for the highest frequency to 1250mV. This should bring some increased stability at the highest two overclock frequencies (thanks to clemsyn and Pinoyto for their help)
Tweaked DVFS table for the GPU. It should now scale a bit better and still bring the same performance and the top end.
Lowest brightness setting increased from 13 to 18 (thanks to clemsyn). Lets give this a try and we can increase it further if need be. The brightness levels can be tweaked on the ROM side as well in the N7 device tree, at least when you build from scratch, so we don't want to be too limiting here.
PowerHAL fix now included /vendor/lib/how/power.grouper.so (thanks to imoseyon). See this post to see the code I changed.
(Removed download links since many were reporting random reboots. I think v1.0.12 is better anyhow)
stable v1.0.10 - build #110/111
CPU frequecies back to 1400, 1500, 1600, and 1624 (leaving the new highest setting)
DVFS table tweaks
Frequency table fix fix for 1624 (thanks to Clemsyn for bringing to my attention!)
Only stock and 484MHz GPU OC version - code switch is still there for those that want to compile and experiment. Moving beyond 484 doesn't show any benefit. My best Nenamark2 score 62.7 was achieved on 484MHz.
Just in case, please note and then unset your saved voltage control settings before using the new version. You may need to clear your System Tuner App data to see the correct frequencies. Remember that the DVFS table and the scaling frequencies are different in some cases (see the second post for details)
experimental v1.0.9 - builds #102-105
CPU OC to 1.624GHz - higher end CPU frequencies are now at 1408, 1504, 1600, and 1624 (old 1400, 1500, 1600, N/A)
DVFS table tweaks - Just in case, please note and then unset your saved voltage control settings before using the new version.
GPU versions stock, 484, 500 and 520MHz builds for testing
Added a GPU OC kernel config choice switch to allow compile time selection of GPU speed (446, 484, 500, or 520MHz).
NTFS r/w enabled
PegasusQ governor no longer built in, but code remains if we want to look further into when time allows.
Reduce some temp reporting kernel log spam until the temp gets a little higher
stable v1.0.8 - build #77/78
Added PegasusQ governor - experimental only, not enabled by default (thanks Samsung SGSIII source and gokhanmoral for tweaks)
Revert "HACK: block fbearlysuspend to not break androids crt-off animation"
Added LulzActive governor, but not built-in due to issues.
stable v1.0.7 - build #70/71
Voltage Control tweak - let's ignore the highest freq slot for show and
save since it shows 1.6GHz twice in the voltage table in System Tuner.
We are are only allowing 1200mV for 1.6, so the top slot is not
currently used. See my notes in post 2 about voltage control.
cpu-tegra: let's skip the temporary downclock and kernel log spam if the
custom Dynamic EDP throttle is not currently enabled.
ARM/VFP compiler optimization
compilation: fix annoying and serious warnings (thanks faux123!)
video: tegra: host: Fix error case memory leaks
When a submit fails, the related nvhost_job is not freed. Add an
explicit free. Also, 3D is mapping the save buffer, but it is not
unmapped (Nvidia)
mm: Ensure pte and pmd stores ordering (Nvidia)
Get rid of some more kernel log spam.
HACK: block fbearlysuspend to not break androids crt-off animation
(thanks codeworx, drewis (repo) and aaronpoweruser for pointing it out). This is untested (by me), but this may help with ROMs that
have this functionality (AOKP etc.)
cpu-tegra3: modified the hot-plug governor down_delay to be 1s
instead of 2s
stable v1.0.6 - build #47/48
GPU clock increased to 484MHz - Nenamark2 scores of 61+
More compiler optimizations (-fmodulo-sched, -fmodulo-sched-allow-regmoves, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-vectorize, -floop-interchange, -floop-strip-mine, -floop-block, -mfpu=neon )
Now using Koush's AnyKernel delivery method. Uses your existing ramdisk so you can easily use with any ROM.
stable v1.0.5 - build #39
Honor your max frequency fix - no more spikes
alpha v1.0.4 - build #38
Fixes units that can't OC (process_id = 3)
Linaro 4.7.1 toolchain -O2 (2012-06-25)
Increased panel clock rate - increases fps without further GPU clock Nenamark2 scores 59.6 best score so far for Nexus 7
ramdisk added back in boot 1.3GHz, but device still spikes to max allowed CPU freq sometimes (see update below, will be fixed in 1.0.5)
Minor clock and voltage adjustments - should run a bit cooler and use less battery.
Added GPU OC compile switch in case we want a non-OC GPU build.
Added some VPN/networking capabilities for those that need it (L2TP, IP_GRE_DEMUX,INET_AH, INET_XFRM_MODE_BEET)
Some unnecessary debugging options turned off. Should save kernel RAM usage.
Some say it made wifi signal stronger again for them, but I never had any issues. Might be the toolchain and its effect on the broadcom driver. Reports that it is better are fine with me!
alpha v1.0.3 - build #17
UV support, minor voltage adjustments
V(R) i/o scheduler added
ramdisk removed custom init.rc line...hope this will fix the stock units that weren't booting!
alpha v1.0.2 - build #6
Mild GPU OC from 416 to 446MHz - baby steps...its been rock solid so far. NenaMark 2 scores are up from 55 to 57.2fps. A future release may have two versions, one with GPU OC and one without.
Upgraded toolchain to GCC v4.6.3 optimized google version by ezterry, see http://forum.xda-developers.com/showthread.php?t=1686310)
alpha v1.0.1 - build #4
Limit frequency to 1.3GHz on boot. It can then be OC'ed from there. This should make it safer for those that can't OC or don't want to.
Changes to allow OC for Process ID's 0 and 1. Theoretically, these should be earlier release versions like IO and earlier.
alpha v1.0.0 - build #1
This initial alpha release is working well on a Nexus 7 16GB (Speedo ID 7/Process ID 2) on JB 4.1.1. There are no open issues that I know about. Looking for some advanced users and testers to give some feedback, and then we can hopefully make it even better!
Thanks to:
fordwolden - for his generous donation of a Nexus 7
Google and Asus for releasing a nice, open, and inexpensive tablet for the masses.
drewis (Andrew Sutherland) - for the base kernel on github
paulobrien - thanks for the CWM touch recovery
birdman and FadedLite for their Unlock\Rooting instructions
clemsyn for his ideas and insight
Git repo:
https://github.com/motley-git/Kernel-Nexus7
{
"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"
}
(http://www.gnu.org/copyleft/gpl.html)
More info
last_kmsg
Please provide the dmesg output or last_kmsg if you experience any issues (random reboot or crashes) that you think are attributed to the kernel. I ask that you please test with the default/stock kernel first for your rom before you blame the issues on this kernel. Wait for the tab to reboot, or if it doesn't wait long enough so you can capture a good log. If you place this on your /sdcard, it will be easy to capture. Boot into recovery, flash this zip, and then flash a known kernel that works. Then reboot, and go grab the last_kmsg in /sdcard.
View attachment LastKMESG.zip (thanks go to CekMTL, I always keep this handy since you gave it to me!)
Voltage Control
What is voltage control?
It is simply allowing for the cpu voltage to be changed on the fly for each frequency step. CPU voltage is typically lowered (undervolting) for certain frequency steps to conserve power. For an overclocked device, some devices need more juice to be stable than others. Voltage control allows others not to pay this penalty and they can lower the voltage as they see fit for their device and usage needs.
Is undervolting safe?
If the lowered voltage values you enter are stable for the tablet, then absolutely it is safe.
What are the benefits?
Better battery life and less heat
Additional Info on voltage control
Only System Tuner is displaying the DVFS table frequency labels correctly and I recommend that you use this if you want to play with voltage control. SetCPU is showing the scaling frequencies when it displays them in the UI, some of which are for the LP core. This is not correct and is misleading, so it is best not to use it for this kernel.
Since the tools available only allow for tweaking one DVFS table (the high powered G cores), voltage control is not currently possible for the LP core. It is not needed anyhow IMO and setting it too low could result in SOD. There is more battery saving to be had with the G cores anyhow if you are into this sort of tweaking.
The frequencies shown may have two values for one frequency. This is how it came with the factory kernel as well and I have only tweaked the top end of the DVFS table. It may seem weird, but this gives us direct access to the DVFS table. I would recommend keeping it as a staircase, just like Nvidia has it even though some frequencies are listed twice.
The freqs shown in the System Tuner display will match the DVFS table for the cpu_process_id for your tablet (seen in the kernel log at startup). All tablets won't display the same frequencies. There are at least two maybe three or four variants we have found so far for the Nexus 7 with Tegra 3 SoC #7.
Also, some may not know, but the tegra3 kernel also has automatic UV using a "cold" zone in where 50mV undervolting is done automatically when the cpu is cool. Take this into consideration when playing around.
GPU OC
Valid max GPU frequency is 416 - 520 MHz. If you try higher or lower clock speeds, it will fail and remain unchanged.
Examples:
Code:
echo 484 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Code:
echo 520 > /sys/devices/system/cpu/cpu0/cpufreq/gpu_oc
Performance Tweaks
These are a couple of tweaks that many are using for faster benchmarks and better battery performance. Google it and decide for yourself if you like the risk or not. I recommend that you do a full backup in recovery and regularly backup your /data partion or cloud sync if you enable these options. Will many run them daily as I now do, there is some additional risk. These can be added to scripts and automated via init.d or other apps/tools that support them.
To disable fsync for better battery and better disk i/o performance:
Code:
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
To enable fsync for better data integrity (default)
Code:
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
Faster disk i/o - remount /data partition with noauto_da_alloc option (google it, better battery, less data integrity)
Code:
mount -o remount,noauto_da_alloc /data /data
TCP Congestion Control Algorithms
Only one can be set at a time, so only add one of the lines to your script. Here are some examples:
Code:
echo "reno" > /proc/sys/net/ipv4/tcp_congestion_control
echo "veno" > /proc/sys/net/ipv4/tcp_congestion_control
echo "vegas" > /proc/sys/net/ipv4/tcp_congestion_control
echo "westwood" > /proc/sys/net/ipv4/tcp_congestion_control
zRAM
What is zRAM?
This is a mainline kernel feature for Compressed RAM block device support (CONFIG_ZRAM)
http://en.wikipedia.org/wiki/ZRam
Like many of the other tweaks done in the Android world, ZRAM is another one of them that is controversial, probably because people only think in terms of immediate performance they can measure easily with benchmarks etc. *Here is my take...think I will add this to the Q&A section as well.
But, will it make my device faster? Will I score higher on benchmarks?
It depends, but for normal usage, the answer is no. zRAM is most useful for those that are configuring Android to be a true multitasking workhorse. For example, if I enable zRAM, open an bunch of apps at one time, and actually start to work towards depleting the memory of the system. *For example, say I open system tuner, a browser with several tabs, a word processing app, a game, and perhaps a picture viewing app or a movie. If I don't formally close out of each one by hitting back and just begin switching between apps and the home screen, you will see zRAM start showing benefits.*
If you tweak the Android memory and swappiness settings, this can also be useful in this type of environment.
How do I know it is initialized and working?
You can type "free" from an command line and see the swap space.
Also, you can look at the disksize to see if it is initialized
cat /sys/block/zram0/disksize
To see how much it is being used in your environment, you can look at the output from:
cat /sys/block/zram0/num_writes
cat /sys/block/zram0/num_reads
So, unless you have a heavy workload as stated above, then it won't be of a lot of use for normal Android users.
How do I enable zram?
It must be enabled by a script. Some ROMs may support activating it. If you need to do it yourself you have two choices.
1) Save this to a file and run the script from terminal, Script Manager or System Tuner.
2) Or better yet, save this to a file called 90zram (or whatever you prefer) in /system/etc/init.d and automate it (The ROM's ramdisk needs to supports init.d)
Code:
#!/system/bin/sh
# auto zram activation init script with busybox search
# by show-p1984
echo "[90ZRAM]: Firing up /system/etc/init.d/90zram";
if [ ! -e /sys/block/zram0/disksize ] ; then
echo "[90ZRAM]: ERROR unable to find /sys/block/zram0/disksize";
echo "[90ZRAM]: Is this a ZRAM kernel?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
else
#find busybox in /system
bblocation=$(find /system/ -name 'busybox')
if [ -n "$bblocation" ] && [ -e "$bblocation" ] ; then
echo "[90ZRAM]: busybox found in:" $bblocation;
echo "[90ZRAM]: Setting ZRAM disksize.";
echo $((100*1024*1024)) > /sys/block/zram0/disksize
echo "[90ZRAM]: Starting ZRAM...";
bblocation=${bblocation%/*}
cd $bblocation
./busybox mkswap /dev/block/zram0
./busybox swapon /dev/block/zram0
echo "[90ZRAM]: ZRAM activated.";
else
echo "[90ZRAM]: ERROR! busybox not found!";
echo "[90ZRAM]: Is busybox installed? Symlinks set?";
echo "[90ZRAM]: ZRAM NOT ACTIVATED. (404)";
fi
fi
Flashed with CWR and it doesn't boot past the Google screen Is there something special I need to do?
*Edit*
I am on the new 4.1.1 "D" or whatever but right now I'm using the Atlantis "1.5" kernel and it works so I donno.
Thanks for another addition to the nexus 7 kernel community, love having different kernels to try.
Clienterror said:
Flashed with CWR and it doesn't boot past the Google screen Is there something special I need to do?
*Edit*
I am on the new 4.1.1 "D" or whatever but right now I'm using the Atlantis "1.5" kernel and it works so I donno.
Click to expand...
Click to collapse
Thx, please grab the dmesg output while booting or last_kmsg if you can. Working fine here, but this why I put it out as an alpha. Even if you boot off another kernel, if you can send a dmesg captured right after boot, that would help so I can see your SoC/Process ID numbers. There are two lines written just after boot with the info. On the Prime, we had different CPUs in some models, but it may just be a voltage issue. I have run Antutu and Quadrant several times without issues though. Not sure about the D update...I I have 4.1.1.
Edit: Version 1.0.1 released, please test again and leave feedback when you can. Please let me know when you received your tab. Is it an early IO version? If this doesn't do it, I most likely will need to increase voltages a bit. Hopefully I won't have to do this so we can keep battery life at it's best.
oh s^&*, you developing here also. oh yeah! glad to see you here buddy. so you have your nexus 7 already? now that i see you here also, i will be unlocking my nexus 7, once it arrives, sooner than i thought. welcome aboard...glad to see familiar faces around here
I had the same issue. Couldn't pass the boot screen after flashing. On 4.1.1 latest update as of July 15th
Sobai said:
I had the same issue. Couldn't pass the boot screen after flashing. On 4.1.1 latest update as of July 15th
Click to expand...
Click to collapse
Thanks, I am dying to take a look at a log to see how I am so lucky to have it working! I've added LastKMSG.zip to the OP. If someone with a booting problem can do the following, I would really appreciate it:
1) Put LastKMSG.zip on your /sdcard along with the newest kernel zip
2) Flash the kernel zip
3) Wait for it to boot, give it a few seconds and then hold power down to reboot if it doesn't do it on its own.
4) Go back into recovery and flash LastKMSG.zip
5) Flash another booting kernel or your current rom to recover.
6) Boot and retrieve the file /sdcard/last_kmsg
7) Attach the log here or PM me with a dropbox link or whatever.
Thanks!
Just got some good news from a gentleman that didn't have enough posts to share with us here yet, so he PM'ed me and said that I can share the details of his experience.
First report was more of the same, sounded familiar, more bad news...
Flashed your kernel and couldn't boot pasted Google screen. Restarted in to boot and couldn't get into recovery. Was stock rooted on the latest 4.11. Went back to stock. Looking forward to trying again, now I'm on Modaco's latest. I'll let you know how it goes.
Next report was good using the latest version in the OP. Not sure, but this may help others.
Thanks! This kernel is fantastic! Makes this thing a real beast! Sorry I didn't give you the info you asked for! I got it Thursday from GameStop. The problems may have stemmed from the fact that I updated to 4.11 , rooted then side updated the newest little update and then ran a su zip to regain root (Paul o' Brian ROM) . I was also on his first cwm and then updated to his new one after I started from scratch. Loaded up his new ROM, rebooted then applied your 2nd kernel and this thing is hitting 15626 in CF benches!
Not sure what is going on, but I can't explain it. It may be my 2nd version of the kernel that fixes it, but I am not sure since I haven't seen a log yet. I suppose something may be jacked up with the early versions of recovery or roms, but the I was using the the same early versions when I tested just fine....maybe folks are losing recovery and don't realize it? I did the second step to keep recovery that is now automated in r2. If anyone has any ideas, let me know.
New version released
New version released...see OP. GPU OC to 446MHz (up from stock 416)
Looking for more feedback
_motley said:
New version released...see OP. GPU OC to 446MHz (up from stock 416)
Looking for more feedback
View attachment 1204164
Click to expand...
Click to collapse
Just out of curiously, would you ever try 520mhz for the gpu, to try to get it to t30 speeds? Or maybe would you consider some kind of app interface like extweeks for the galaxy s2 & s3 to control the GPU clock speed and maybe voltages instead of different kernels. As I would personally love to get the GPU to about 460-500mhz Anyway when I get my n7 (hopefully in a day or two) I can't wait to try this out (I am spoilt by the much more powerful 440mhz mali-400mp in the s3, so I would love to try to narrow the power difference between the devices GPU wise)
Nice man! The new versions fixed everything boots great! Now if we can just figure out how to make the Overclock stick after you turn the screen on/off. I'm not sure how to tell if the GPU OC is sticking.
Sent from my Nexus 7 using xda app-developers app
danielsf said:
Just out of curiously, would you ever try 520mhz for the gpu, to try to get it to t30 speeds? Or maybe would you consider some kind of app interface like extweeks for the galaxy s2 & s3 to control the GPU clock speed and maybe voltages instead of different kernels. As I would personally love to get the GPU to about 460-500mhz Anyway when I get my n7 (hopefully in a day or two) I can't wait to try this out (I am spoilt by the much more powerful 440mhz mali-400mp in the s3, so I would love to try to narrow the power difference between the devices GPU wise)
Click to expand...
Click to collapse
Sure, we may push the GPU OC version a bit, but I always like to walk before we run to see how things go. I would like to monitor heat output, battery usage etc. and then move forward in steps. I am very happy with it right now, but dynamic configuration would also be cool. Let me know what you think once you have it hand.
Clienterror said:
Nice man! The new versions fixed everything boots great! Now if we can just figure out how to make the Overclock stick after you turn the screen on/off. I'm not sure how to tell if the GPU OC is sticking.
Click to expand...
Click to collapse
Awesome, glad to hear it! I don't think I see this issue with the OC sticking after you turn the screen off/on, but I will do more checking after work today.
_motley said:
Awesome, glad to hear it! I don't think I see this issue with the OC sticking after you turn the screen off/on, but I will do more checking after work today.
Click to expand...
Click to collapse
Thanks a ton! Yea if you go into setcpu and make it 1.6 then turn the screen off then on (unlock) set CPU slider still shows 1.6 but if you read under that the smaller text says its actually set at.1.3 again. It seems to be a problem with the Atlantis kernel also something to do with hardcoded CPU freqs I think. Oh I wanted 5k soooo bad rofl got this twice rofl.
Sent from my Nexus 7 using xda app-developers app
Clienterror said:
Thanks a ton! Yea if you go into setcpu and make it 1.6 then turn the screen off then on (unlock) set CPU slider still shows 1.6 but if you read under that the smaller text says its actually set at.1.3 again. It seems to be a problem with the Atlantis kernel also something to do with hardcoded CPU freqs I think. Oh I wanted 5k soooo bad rofl got this twice rofl.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've just made profiles that automatically set the clock to 1.5 when the screen turns on again and back to 1.5 when the screen turns off.
Edit*
Just tried the newest version and it failed to boot. Got stuck at the Google Logo. Here is the last_kmsg. Hopefully it helps
(had to put a .txt extension on it btw. Uploader wont let me upload w/o extension)
The Nexus 7 GPU is better than the Transformer Prime due to the faster RAM, so more bandwidth? If I'm correct? Thats why we see a higher Nenamark score at a lower clock?
This kernel looks very promising, excellent work! How much "play" have you had with upping the voltages, before the battery quits? On my TF, I can only go so far before the battery cannot provide enough juice, and it freezes on me. It would be interesting to know for people who want to OC really high. Does anything above 1.6 GHZ actually boot (heat and battery drainage aside)? It would be nice to OC up to 2.0 GHZ, if only for a proof-of concept. Finally, what are the temps you are getting on the higher clocks? It sounds like overheating may start becoming a real issue, and I was just curious.
The ram disk version rendered my tablet unbootable had to flash the Atlantis kernel from fast boot to get it back up and running.
Sent from my Nexus 7 using Tapatalk 2
Good work there, I would suggest adding Smartassv2 as well since it has been a good choice for many dev
I for the life of me can't get this kernel to OC. Tried System Tuner, Setcpu etc. Max only reads 1300mhz nothing shows higher beyond 1300. I have no clue what the deal is. I've tried wiping also. Even tried Atlantis' kernel. on his, it won't allow me to set anything. Max shows 0 and Min shows zero. I am running Pauls Modaco Jr3 and even tried it on EOS' new release. I'm beginning to wonder if its something diff internally. Anyone have any guesses?Also showing root as setcpu requests superuser permissions.
This is what my device shows
Board: grouper
Product: nakasi
Model: Nexus 7
Device: grouper
Build: JRO03D (Modaco Custom ROM Jr3)
google/nakasi/grouper:4.1.1/JRO03D?402395:user/release-keys
Manufacturer:asus
Brand:google
CPU ABI: armeabi-v7a
Kernel
Linux version 3.1.10-motley+([email protected]) (gcc version 4.6.3 (GCC)) #6 SMP
PREEMPT Tue Jul 17 00:52:59 EDT 2012
This is a AOSP kernel for the lte.
since 4.2 is pretty stable I am going to start updating the changelog for it.
What is a kernel?
In computing, the kernel is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
{
"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"
}
Features
Cpu overclocking - I include 3 variants 1.7, 1.8, and max OC of 1.998
Gpu overcloking - Controlable with various apps on the market (I prefer kernel tuner)
Cpu governors - intellidemand, badass, interactive, conservitive, powersave, performance, lionheart, ondemand, and more
IO schedulers - sio, cfq, vr, zen, deadline, and noop
Sweep2wake with extra gestures - see bottom of OP
Compiled with the latest Linaro 4.7 toolchain - this is usually updated once a month here http://www.linaro.org/downloads/
Linaro -O3 optimized with extra build flags
Sound control
HTC perflock disabled
Voltage control - Controlable with various apps on the market (I prefer kernel tuner)
USB fast charge support
Code:
Changelog 4/8/13 rls30
merge latest cm commits
clean cpu and gpu clocks
linux 3.071
add sound control (Change gains for headset and headphones,sys/kernel/sound_control)
add variant for s2w with gestures
Changelog 3/5/13 rls29
sched_fair: improve group logic
vsprintf: make %pV handling compatible with kasprintf()
lib/vsprintf: replace link to Draft by final RFC number, lib:
nohz: Remove ts->inidle checks before restarting the tick
Revert "jewel: adjust refx100 to 6650." …
remove unused branch labels from trylock routine
disable preemption in machine_shutdown
remove redundant initialization in alloc_page_buffers()
Update amd use lzo compression
jewel: display: remove pinfo.clk_rate.
linux 3.0.67
update rqstats
wcnss: Configure bite interrupt as edge triggered
linux 3.0.68
Changlelof 2/25/13 rls 28
"msm_fb: display: fix compiler warning for uint64_t format" …
jewel: adjust refx100 to 6650. …
msm_fb: display: fix compiler warning for uint64_t format …
video: msm: Remove timeout from wait4vsync …
msm_fb: display: get mipi frame rate from panel file …
msm_fb: display: wait4vsync before set suspend flag …
msm_fb: display: wait4vsync after timing generator is turned off …
msm_fb: display: replace msleep with wait4vsync …
msm_fb: display: check bus scale handler for registration …
msm: msm_bus: Add support for 64-bit bandwidth requests …
add zram using snappy compression support
add frandom number generator support
linux 3.0.66
clean up crc32
update bfq v6
increase capture number of periods
up MDP clocks
tune sched_fair
msm_fb: display: clean pipes from commit queue at suspend …
msm: rotator: Support Fast YUV for 8960, 8064 and 8x30 targets. …
msm: rotator: clear rotator bus scale handler …
forget using aroma to set gpu users can change via app after boot
update usb fastcharge to 3.1
wcnss: Update Riva ramdump segments
update arm topology drivers
add strncpy_from_user
Changlelog 2/16/13 rls 27
Linux 3.0.65
Linux 3.0.64
more cmdline for aroma
linux 3.0.63
msm_fb: display: add mdp clock control to histogram enable/disable …
msm_fb: display: keep borderfill pipe's iommu info …
msm: display: Fix blend configuration for video layer with MDP compos… …
msm_fb:display: correct bus bw for downscale case …
add HYPER gov
Changelog 2/10/13 rls 26
implement aroma for soff (thanks to rom chef for the help still has things to be implented)
msm_fb: display: restore previous mdp bandwidth when resume
android, lowmemorykiller: Sync with Google/CAF
msm: vidc: Add ioctls for MPEG-2 extradata support
video: msm: Fix copyright attribution. …
msm: kgsl: initialize kgsl_sync_timeline_ops properly …
msm: kgsl: Don't wake up gpu on kgsl_ioctl calls if not necessary …
msm: kgsl: Avoid NULL pointer in adreno setstate functions …
msm_fb: Check for panel power on after Unblank.
clean up journal
Revert "ASoC: msm: Fix issues in proxy port driver due to early afe p…
linux 3.0.62
compiled with -O3 buildoptimizaton and -funroll-loops build flag
Changelog 2/2/13 rls 25 For JB 4.2
this will only work on roms who have added the changes from decks 2/2/13.build
linux 3.0.61
added ROW,FIFO,and ZEN I/O schedulers
Updated to the latest linaro 4.7.3 tooolchain (1/13)
Tweaked mp decision (some of CG KeRnEl ChEfs features)
added 178 commits from Deck And CM team (without these guys this project would not exist)
Changelog 1/14/13 RLS 22C
Linux 3.0.58
entropy tweaks
Fix bug when pausing music it stopped and started again for a second
tweaked wifi settings
Changelog 1/6/13 rls 22B
Linux 3.0.57
block: add and use scsi_blk_cmd_ioctl
get rid of on-stack debugging
dynamic fsync
dont oc gpu by default, let user control
some minor code clean up
Changelog 12/29/12 rls22
linux 3.0.56
linux 3.0.55
linux 3.0.54
usb fast charge credit to Chad Froebel
showps ring buffer patch
usb headset detection
Updated VFP to max from 3.4.Y Google Android.
Changelog 12/3/12 rls21
retweaked readahead
GPU oc is reworked to work with kernel tuner (on the apps next update)
tweak sio scheduler
upgrade to linux 3.0.53
Deactivate Notification LED Timeout
implement the ck1 patchset
iosched: prevent aliased requests from starving other I/O
tweaked deadline scheduler
Changelog 11/25/12
use ion instead of pnem(this is tha change in decks build 11/24)
tweak FSB
tweak ksm
GPU 2D/3D OC
msm: kgsl: Ensure glitch free changing of the GPU frequency
vfp: Use hard-float and neon libraries instead of vfp ones
mm: drop swap cache aggressively
mm: swaptoken only when swap full
android: binder: Allow using highmem for binder buffers
mm: drop swap cache aggressively
sched: task_times() explosion avoidance for tasks with
Changelog 11/20/12 rls 19
added cpu topology drivers
upgraded to linux 3.0.52
msm: memory: Use standard cache routines
mm, oom: fix potential killing of thread
Changelog 11/16/12 rls 18
Tweaked crt animation hack
passed with -O3 optimizations
Changelog 11/14/12 rls 17
Updated drivers to work on cm stable and decks newest releases.
Changelog 11/9/12 (decks irc build 11/10 will not work with this kernel)
linux 3.0.51
I/O-less dirty throttling
clock wrap bug
Move REPEAT_BYTE definition
JIT compiler for packet filters, ARM: net
Use AC charging for unknown chargers
Add optimized AES and SHA1 routines
Hack for CRT animations fix
force headset notifications single threaded
Compile with -pipe
aio.c: Asynchronous I/O latency to a solid-state disk greatly increased
optimize apply_slack
fix rq->cpu_load[] calculations
readjust readahead
reclaim som ram from logger
Changelog 11/5/12
fixed the black screen issue reulting in soft reboot
updated compression algorithm
Updated to linux 3.0.50
Changelog 10/28/12
rls14
Sweep2wake(thanks Zarboz)(currently sweep to wake only works in one direction)
MHL enabled
Upgrade to linux 3.0.48
ChangeLog 10/27/12
rls 13
2 kernel version oc capped at 1.89 and 2.1
added vr scheduler
Implemented Jrcu
tweaked block layer
SON is using ramdisk from decks 10/26 build
support for this encryption app [url]https://play.google.com/store/apps/details?id=com.sovworks.edslite&feature=more_from_developer#?t=W251bGwsMSwxLDEwMiwiY29tLnNvdndvcmtzLmVkc2xpdGUiXQ[/url]
Changelog 10/17/12
added Zarboz new asswax governor (thanks Zarboz)
Added Fsync toggle: (File syncronization)
It's disabled by default. Enabled = stock IO speed while having data integrity; disabled = more IO throughput but less data integrity
echo Y > /sys/module/sync/parameters/fsync_enabled (N to disable and Y to enable)
Reapplied patches that broke during the upgrade of linux versions
crc32 optimized
lib/string: use glibc version
lib/memcopy: use glibc version
use the git implementation of SHA-1
Changelog 10/8/12
currently only working for cm10
added BFQ scheduler
perflock disabled
block layer tweaks
auto group scheduling
New wifi driver built from source with BT-AMP feature
Changelog 9/22/12 rls .07
added governors badass,wheatley,pegasusq, and lagfree
tweaked mpdecision
enable ntfs
low memmory tweaks
camera flash functions to 5 percent now
use crc32 patch
many minor patches and tweaks
Changlelog 9/19/12 rls 0.6
better voltage for 2.1
OTG USB HOST MODE
More battery friendly mpdecision(to disable navigate to sys/kernel/msm_mpdecision/conf/enabled change the value to 0)
[COLOR="Red"]doing this can harm your phone I do not recomend but to each his own[/COLOR]
[COLOR="Red"]to change the low value for thermal navigate to sys/kernel/thermal/allowed_low_freq and change to desired frequency[/COLOR]
Changelog 9/12/12 rls .04
Improved mpdecision with cpu1 not so sleepy
utilizing Haus' SON kernel Update script(thanks Haus)
Changelog (9/11/12) rls .03
implemented kernel based mpdecision
implemented kernel based thermald
[COLOR="Red"]With these implimenattions this will rename your thermald and mpdecision binary in your rom to thermal_backup and mpdecision_backup.[/COLOR]
Changelog (9/7/12) rls .02
GPU OC
Added usercontrolled voltage
disabled fsync
Tweaked thermal (trying to manage cpu1)
Boost FSB to 533
tweak smartassv2 governor
and a few other tweaks
Changelog (9/6/12) rls .01
Added CPU OC to 1.89 ghz
Added schedulers VR, SIO, CFQ, DEADLINE; all optimized for flash devices
Addeded Governors smartass2,interacitve,intellidemand,savadgedzen,2 phase ondemand,performance,conservitive,lionheart
Disabled fair gentle sleepers for better performance on android
increased vm readahead to 1024
made memmory allocation optimizations (shows 726 mb of ram)
many little tweaks compiled with linaro 4.6
XZ compression
Sweep gestures (sweep finger across the capacitive buttons on bottom of phone):
Code:
Sweep2sleep: with screen on, swipe right to left to turn screen off
Sweep2power: with screen on, swipe left to right for power menu (simulated 2.5 second power button hold)
Sweep2snap: with screen on: swipe left to right and press Home within 2 seconds for a screen snap
Sweep2wake: with screen off: swipe left to right to turn screen on (disabled by default for better battery life)
Phantom volume down: with screen on, touch between back and home for vol-down one notch
Phantom volume up: with screen on, touch between home and recent apps for vol-up one notch
Sweep2mute: with screen on, swipe from home to back for vol full down (vibrate)
Sweep2loud: with screen on, swipe from home to recent apps for max volume
Sweep2skipback: with screen off, swipe from home to back to skip back a track (when listening to music)
Sweep2skipforward: with screen off, swipe from home to recent apps to skip forward a track (when listening to music)
Sweep2deepsleep: with screen off, swipe from right to left to temporarily disable sweeps while screen is off (until screen is turned back on: prevents pocket sweeps)
[IMG]http://forum.xda-developers.com/attachment.php?attachmentid=1479575&stc=1&d=1352840345[/IMG]
here is a little explanation of kernel based thermal and mpdecision control
What is msm_thermal?
Kernel based 3-phase thermal control!
This replaces your /system/bin/thermald binary which is renamed by the installer to thermald_backup.
Check /sys/kernel/msm_thermal/conf/ for the thermal configuration
allowed_max_high = highest threshold (phase 3)
allowed_max_low = remove the throttling if we cooled down to this (clr_thrshold)
allowed_max_freq = max frequency if throttled (limit)
[...]mid[...] = same as above, just for phase 2
[...]low[...] = Lowest threshold (phase 1)
check_interval_ms = how often shall we check? (sampling rate)
Default: 1000ms (=1sec)
If you want to see msm_thermal doing it's job:
Code:
adb shell cat /proc/kmsg | grep 'msm_thermal'
What is msm_mpdecision?
100% kernel based multi core decision! (should cpu1 be online or not?)
This replaces your /system/bin/mpdecision binary which is renamed by the installer to mpdecision_backup.
Check /sys/kernel/msm_mpdecision/conf/ for the configuration.
startdelay = time until mpdecision starts doing it's magic (70000)
delay = time between checks (500)
pause = if something else plugs in the cpu, fall asleep for 10000
scroff_single_core = if the screen is off, don't plug in cpu1 (1)
nwns_threshold_up = runqueue threshold, if this is reached cpu1 will be hotplugged (35)
nwns_threshold_down = runqueue threshold, if this is reached cpu1 will be unplugged (5)
twts_threshold_up = time threshold, this amount of time must have passed (250)
twts_threshold_down = same as above (250)
enabled = enable(1) or disable(0) mpdecision. This does not affect scroff_single_core!
idle_freq = a value against that will be checked if a core +/- is requested. (486000)
If cpu0 is below that value and a core up of cpu1 is requested, nothing will happen.
If cpu1 is above that value and a core down of cpu1 is requested, nothing will happen. (otherwise it would now put down cpu1 even though it is still working)
(all times are in ms)
NOT RESPONSIBE IF YOU BRICK,DROP,LOSE YOUR DEVICE. FLASH AT YOUR OWN RISK[/B
What is FSO?
Fso has greater speed, but there is a chance of corrupting if the phone has a random reboot.
Non-fso is what a stock kernel is and does not have the corruption issue.
It's a trade off, performance for stability or visa versa
If you have issues with reboots viperboy has created a script to increase voltages which may help with stability for the rebellious phones thanks viperboy
http://d-h.st/Kru
Downloads for the the latest releases
http://d-h.st/users/Thicklizard
gpl legalities
https://github.com/thicklizard
If you like my work buy me a coffee!
Thanks to cyanogenmod.
Reserved
Good to see you over here!
I'm on paranoid android so I'll probably test it tonight...
By the way you need to fix the link. You wrapped in lowercase tags when it should uppercase...
YESSS finally a JB kernel. give me give me give me!!!.
Flashing asap
Also what are the smartass2,intellidemand,savadgedzen,2 phase ondemand, and lionheart do, specifically what are the pros and cons?
Ive never heard of those before. But i have heard and used the other ones listed above.
Nice. Will give this a go next time I flash cm10.
Sent from my EVO using Tapatalk 2
Oh yeaaaaaa
Sent from my EVO using xda premium
Pithism said:
YESSS finally a JB kernel. give me give me give me!!!.
Flashing asap
Also what are the smartass2,intellidemand,savadgedzen,2 phase ondemand, and lionheart do, specifically what are the pros and cons?
Ive never heard of those before. But i have heard and used the other ones listed above.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1663809
Check out this thread
Sent from my EVO using Tapatalk 2
Running smooth so far on PA sir
Sent from my EVO using xda premium
Flashing NAOO!
Edit: Runnin great! Lovin more RAM.
very very Nice!
on PA intellidemand works good. too bad no voltage tweaking but good none the less :thumbsup:
syaoran68 said:
on PA intellidemand works good. too bad no voltage tweaking but good none the less :thumbsup:
Click to expand...
Click to collapse
In time this is initial release.
Sent from my EVO using Tapatalk 2
Ooohhooohhooo today is a good day! Thank you! I'm on AOKP. I love the thread you linked for CPU governor explanation. That's a great read. Can't wait to see undervolting capability, especially since AOKP has that available in settings.
Did I say, 'thank you'? :thumbup:
via xda premium on my AOKP'd Evo LTE
Savage Zen is pretty snappy if I must say at 1.809
Sent from my EVO using xda premium
For those of us that are S-ON and dev unlocked, how do we go about installing this? It's not in a .img file so no flash image gui or fastboot.
Can someone repackage it?
Sent from my EVO using xda premium
I will have boot.imgs up in less than an hour
Sent from my EVO using Tapatalk 2
foobz said:
For those of us that are S-ON and dev unlocked, how do we go about installing this? It's not in a .img file so no flash image gui or fastboot.
Can someone repackage it?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I'm not mistaken, the image you need is in the flashable zip. Just download the zip, extract it somewhere, and grab the IMG.
May be wrong though. Been a while since I actually looked inside of a kernel zip haha
Sent from my EVO using Tapatalk 2
thicklizard said:
I will have boot.imgs up in less than an hour
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
This guy here! Awesome Job, Really Awesome!
Linking this thread From Paranoid.
Awesome! Thanks for the work!!
Sent from my EVO using xda premium
Oh my gosh! Is it my birthday? can't wait to try and see where this goes!
Will future releases have GPU tweaks?
Thomas.Raines presents
The Lightning Zap! kernel for the Nexus 4 Mako
ATTN:
I thomas.raines, nor it's affiliates claim responsibility for anything you do to damage, destroy, brick, explode, or otherwise mess up your device.
{
"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"
}
Features:
Improved performance
Improved battery life
Improved network speeds
Improved boot times
Smoother scrolling
Better responsiveness
Cleaner file systems
Governor tweaks for amazing speed and performance without sacrificing battery life
Improved Memory and Ram tweaks
Improved Internet speed
kexec hack for dual booting with MultiRom.ak
Overclocked cpu
sweep2wake/doubletab2wake (disabled by default. must be enabled via script by uncommenting lines 7 and 8 in /etc/init.d/05s2w then reboot)
Amazing kernel tweaks, build.prop mods, init.d scripts and more!
Governors:
POWERSAVE
USERSPACE
ONDEMAND
INTERACTIVE
BADASSS
INTELLIDEMAND
LIONHEART
ONDEMANDX
SMARTASS2
GALLIMAUFRY
LAZY
io-schedulers
NOOP
DEADLINE
CFQ
SIO
See 2nd post for download links and changelogs
Instructions:
Make a backup
Download .zip to PC
Transfer .zip to your sdcard
Or just download it straight to your phone
Reboot to recovery
Flash
Reboot
Wait 10 minutes
Enjoy the Lightning Zap!
See 2nd post for download links and changelog
**The first boots usually takes the longest especially after a fresh install. If you pull a logcat during the first boot, you may see a few errors with the vacuum script. This is normal, and will be "fixed" after the phone has built the databases for the apps.
Please allow 24 hours after install and 1 full charge cycle before reporting results. Always provide me with a logcat with any issues you may experience.
Source Code:
mako-lz kernel
vendor_lz-kernel (LZ vendor files for ROM compiling)
Special thanks to:
jrummy16 for Root Browser Lite
show-p1984 for bricked kernel (used for rebase)
Download Links and Changelogs
Nexus-4-Mako-LightningZap_p5.1.2.zip
cpufreq adjustments
led driver adjustments
Import RB tree adjustments from Motorolla
Input packet management adjustments
EOL
https://github.com/LightningZap/and...mmit/9ee0e0e3f9cf2733c554f0da69724c79f71cb4d9
Nexus-4-Mako-LightningZap_p5.1.1.zip
Fixed voltages and frequencies
uv_bin overhaul
Fixed inconstancies in installer
Guys and gals with slow binned cpus, MAKE SURE YOU SET THE MIN VOLTAGE TO 700. Or you will get random reboots like crazy. On a side note. I would strongly suggest wiping dalvik (art) and cache before flashing. If not, your device may shutdown immediately after it is done booting. Nothing to really worry about, just simply hold the power button for a few seconds till the google screen appears, and you should be good.
Nexus-4-Mako-LightningZap_p5.1.0.zip (dl link unavailable)
Major upstream update (166 commits)
TCP tweaks
Added GCC optimizations
Updated linaro toolchains
If you are having random reboot issues or you get stuck on the Google screen, try raising your min voltage to 700MHz. If that still doesn't work, let me know here. Please try to attach a dmesg log and make sure you tag me in the post so I don't miss it (@thomas.raines)
Enjoy!
Nexus-4-Mako-LightningZap_p5.0.2.zip
Added intelli_plug to handle CPU hot swapping
Disbabled MSM_HOTPLUG
Bumped to 5.0.2
Set min CPUFREQ to 9450
Changed Aroma installer defaults to my recommendations.**NOTE** If overclocking, I recommend using higher voltage min...
Included a LightningZap! tailored init.mako.rc that sets vibrator amp to 100, disables all that unneeded cpu governor junk and more...
Nexus-4-Mako-LightningZap_p5.0.1.zip
Bump to 5.0.1
added 5.0 emmc support
speedup /proc/net/unix
network speed tweak
exec_hardboot:updated with more current patch.
Avoids bogus error messages for the suspend aborts.
Avoid using global variable total_cpus
added sound control Thanks @faux123
Nexus-4-Mako-LightningZap_p5.0.zip
Update kernel to Lollipop 5.0
Added script to fix wonky sdcard issue. (5.0 was changing it from /sdcard/<your files> to /sdcard/0/<your files>. Script prevents that from happening and all is well)
All the same greatness of Lightning Zap! 4.4.X with no issues
Enjoy folks!
Nexus-LightningZap_p4.4-3.3.zip
Added remaining uv options to table
Backlight dimmer options
USB Fast Charge
CPUFREQ:rework of all tables. New implementation of freq's using PVS.
cpufreq: properly sync current scaling governor across all cores
Slight boost in L2 cache. Corrected number of cpufreqs
enable max screen off freq on/off support
added RESTRICT_ROOTFS_SLAVE
Added fsync on/off support:Enabled by default
Added f2fs and exfat support
Inspired by elementalx's flashing format using Aroma Installer, I have revamped cpufreq and uv tables, as well as added a few options.
You can now set your default options with the installer. Just follow the prompts as you go thru.
The flashing instructions are the same; however, at the end of the flashing process, you will have an option to save the log. I would recommend doing so. But only share it with me if you have an issue.
The installer is not without it's little glitch. Occasionally, your screen might flash and appear to be going from screen to screen in recovery after the installation process has finished. Nothing to worry about. Just let it settle down and then reboot. I only had this issue in philz_touch.
With the L2 cache boost, and the lightningzap booster, those pesky random reboots due to L2 cache failing to sync are a thing of the past.
One thing to note, when selecting your cpufreq, this will set you MAXIMUM. Meaning, even with an app, you will not be able to go over the default you set. Select carefully. I would recommend setting core 1 to the highest you desire and then setting the other 3 cores lower in the case you need more. And just use trickstermod to adjust as necessary. Oddly enough, even if you set the cores individually and cores 2-3 lower than core 1, your max will be whatever core 1 was set on. But if you adjust them reverse to what I said, then you will be limited to whatever default core 1 is. Hopefully that makes sense.
I have also linked all cores. This means that when you use Trickstermod app to set your cpufreq, it applies it to ALL cores. I have notice some apps, like kernel tweaker, do not do this as they are not written correctly for multi-core processors. Most of the defaults like voltages, fsync, and sweep2* can still be controlled with trickstermod even if you disable them during install.
TBH the only thing you cannot change, is your max cpufreq (meaning, if you choose 1512(stock) as your max during install, the only way to raise it is to re-install the kernel. However, you can still fine tune it).
Another note, max freq is set to 1620; however, if you can still set it higher, will just have to use trickster mod to fine tune it...
Previous Changelogs and links
Nexus4-LightningZap_p4.4-3.2.zip
Dropped mpdecision
Added msm_hotplug (With updates)Reconfigured voltage table. Boots @ 700000uV on 94500mHz
Possible UV/OV is now 600000uV min 1450000uV max (Be careful with this as too low/high for your device could cause instability. Test your settings BEFORE setting it to set at boot. If you go below the thresholds, your device will become EXTREMELY unstable, reboot, say you should have listened and then blow up in your face...lol. Not really, but it will go into a kernel panic and reboot)
And FYI, the voltages are reported in uV not mV. If you don't know, 1000uV = 1mV; therefore, the kernel boots @ 700000 is 700mV...
Nexus4-LightningZap_p4.4-3-1.zip
Added sec_dvfs_dual. All CPU's handle hotplugging better now
Added lulzactive cpu gov
add row and fiops schedulers
set fiops as default scheduler
Working on getting smartassv2 to compile...
added LCD Gamma Hack from faux kernel
Nexus4-LightningZap_p4.4-3.zip
2 stage update on this one.
Stage 1
Dropped bricked base and went back to kk4.4 (AOSP & CAF) base
Revamped OC/UV. Still compatible with Trickster Mod app
(Because I dropped the bricked base and went back to original base, you won't have full control on thermald and mpdecision for now. Working on adding it, please be patient)
Stage 2 With results of the latest poll in mind:
Dropped the following governors:
Conservative
Gallimaufry
Ondemandx
Userspace
Made Intellidemand/deadline as default
Nexu4-LightingZap_p4.4-2.zip
Complete revamp of base. Used bricked kernel as base (thanks to show-p1984)
Created new branch for revamp (bricked-lz) Keeping kk4.4 branch for now.
Per user requests:
Moved RootBrowser to /data **Must remove it from /system/app prior to flashing
Removed voltage control app. No longer compatible with vc.
Fully compatible with TricksterMod app
Vote on the next poll for your favorite governor & io-scheduler (If I can get it setup right)
Nexu4-LightingZap_p4.4-1.2.zip
Reverted back to Linux Android Kernel version 3.4.0 due to instability
Bumped to p4.4-1.2
Revamped mako_defconfig in order to enable loadable modules
changed build cifs & tun as modules
Left WiFi modules as hard-coded drivers to avoid WiFi issues on other Roms (Sorry about this one guys and gals)
Nexus4-LightningZap_p4.4_1.1.zip
Bumped to latest stable kernel version 3.84.4 (LightningZap version p_4.4-1.1)
Added sweep2wake and doubletap2wake from bricked-kernel Mako (special thanks to show-p1984)
sweep2wake and doubletap2wake is disabled by default. To enable one or both, refer to this post
Nexus4-LightningZap_p4.4_1.zip
Initial release
Just a note, some combinations of governors and io-schedulers don't mix well and you could experience instability like freezes and reboots. Before posting an issue, change your governor and or io-scheduler. This will help me narrow down any issues. And by all means, please let me know which combination you experienced an issue with, and what exactly occurred.
Note that certain ROMs like Omni and Ubuntu Touch that use a modified initramfs or some other kernel modification, may not work with this kernel. I am working on it now.
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
Great seeing you here! My brother uses your kernel on his E4GT and he likes it a lot.
I hope you do good work for the N4 as well. :good::good::good::good:
thomas.raines said:
Hold up... getting the link now
Click to expand...
Click to collapse
The OP says it's for Blaze 4G You might want to edit it to avoid confusion Thanks for your work, sir. I had use yours in my Blaze 4G.
Maybe a bit explanation of governors? Like for lionheart and galli
Nexus 4 cihazımdan Tapatalk kullanılarak gönderildi
Wow I saw you in the Blaze fourms. Great to see you developing on the N4!
Sent from my Nexus 4 using xda app-developers app
Saw you in the et4g forums
Sent from my Nexus 4 using Tapatalk
I'm glad people say this is real looked like a hoax to zap my n4!
So who has flashed this?
sent from a toilet...
phone always fc's for me on 3 different AOSP roms
Thanks for the kernel......Testing-----------------:good:
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
Can you be more specific?
CallMeAldy said:
phone always fc's for me on 3 different AOSP roms
Click to expand...
Click to collapse
by chance you tried it in the rom Purity? by that I have not had problems with.:good:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Yadro said:
Hello.
Thank you for you hard work.
I was wondering which governor and scheduler do you suggest.
Edit : Can you possibly add swipe to wake?
Click to expand...
Click to collapse
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
thomas.raines said:
The governor and scheduler really varies from person to person and dependent upon their usage of the device. I think Lionheart with noop is a great combination for power and battery saving from the light user all the way up to the medium user which is why I made it default. Some have suggested that intellidemand is very good as well, but sacrifices a bit of battery saving yet adds a slight bit of performance.
I have considered adding sweep 2 wake on some of my other kernels, but haven't truly decided on it yet. I think I'm going to give it a try tonight though.
Click to expand...
Click to collapse
Thanks! So far i'm enjoying this kernel a lot! Working out for me on XenonHD.
---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------
thomas.raines said:
Update available
Read changelog for details
To enable sweep2wake and doubletab2wake:
use an app like kcontrol
in and adb shell or in terminal on the phone type:
Code:
echo 1 > /sys/android_touch/sweep2wake
echo 1 > /sys/android_touch/doubletap2wake
Or, I have made it even easier. In root browser, navigate to /system/etc/init.d. Open the script named 05s2w and remove the # from lines 7 and/or 8, then reboot. This will enable sweep2wake and/or doubletab2wake. You can enable both or just one of them.
Click to expand...
Click to collapse
okay i'll try that now too.
---------- Post added at 09:00 AM ---------- Previous post was at 08:49 AM ----------
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
M3drvr said:
Why is the default read ahead on the scheduler 16xxx? Isn't that a bit much?
Click to expand...
Click to collapse
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
I wasn't too worried. Just wondering. Thanks! So far the new kernel very good. The first 5 minutes of it being installed there were quite a few lags and glitches. But after that, its smooth as ever!
thomas.raines said:
That's max, and yes it is very high, but nothing to worry about. But to be honest, the deice itself will never go that high.
On that note, if you look through my commits I never set that. That came from an upstream change quite some time ago. So far back that I can't find when it happened...lol
The reference is in block/partitions/ultrix.c on or about line 29. You can see that it can be as high as 16384 but 512 is actually the default.
I looked in my Linux kernel source and the file is the same. So this could have been the default from forever ago.
Again, nothing to worry about though...
Click to expand...
Click to collapse
That's to be expected while the kernel settles in. Glad you're enjoying it!
Sent from my Nexus 4 using xda app-developers app
Should MPDecision be enabled if using the noop scheduler and Lionheart governor? Or whats your recomendation?
{
"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"
}
G+ Community - RACER KERNEL NEXUS 5: https://plus.google.com/u/0/communities/111573013590626593533
Donations through play store app: https://play.google.com/store/apps/details?id=com.racerkernelpal&hl=en
Donate through paypal:
RACER Kernels are built from android-6.0.1_r0.24 / cm-13.0 /cm-13.0-caf base. All features are working! It is fast, silky smooth and only sips battery. I make these builds purely for fun, and for myself, but am sharing these just in case others find it useful. I am only a cherry-picker and not an original developer. Those looking for original stuff, please head over to the work done by the great developers I have mentioned later in this post. I have been running this kernel with no problems. The plan is to keep improving it with regular updates. Do try this kernel and all feedback is welcome.
Enjoy extra battery life by enabling CPUQUIET Hotplug and disabling all other Hotplugs. Use Kernel Adiutor or Kernel Tweaker app to enable and tune CPUQUIET. This feature is now built into all RACER kernels.
DOWNLOAD LINKS
FOR MMB29V/ CM-13.0 / AOSP ROMS
RACER_M: racer features built over official cm-13.0 repo as base
FOR CM-13.0 CAF ROMS
RACER_CAF:.......... official cm-13.0-caf repo as base
RACER_CAF_MF............myfluxi's caf repo as base
Changelogs
Features
Read this before installing:
Boot Loop / Boot Hang (stuck with endless bootanimation) - This could be an issue, especially with AOSP ROMS that have a built in Super Su. See this for clues - http://forum.xda-developers.com/showpost.php?p=64453860&postcount=3262
The kernel can be set with any kernel app. Synapse is officially recommended because it can set almost all the features available. Most features of the kernel can be set with the script from here: https://www.androidfilehost.com/?w=files&flid=44487. Before flashing, you can change the settings in init.settings.rc to your liking. After boot you will have all your settings. If using Synapse, flash UKM 3.8.1 with every kernel update to make sure all new features are visible.
CPUQUIET can be set and tuned only with Kernel Tweaker app . Kernel Auditor can also be used to enable CPUQUIET but not tune it. Do not set any other hotplug on if your enable CPUQUIET.
F2FS Support: No need to modify the ramdisk of the ROM. The kernel does it for you.
For more on F2FS - benefits and working details, please visit: http://en.wikipedia.org/wiki/F2FS
Using the power-key to shut off the screen during charging will save battery and increase charging speed. This settings is available in Synapse / Wake
For best results, clear data from your kernel setting app, clean cache and dalvik, reinstall rom and kernel and boot
I do hope you like this release
Acknowledgements:
Google, @CyanogenMod, @show-p1984 , @myfluxi, @flar2, @franciscofranco, @neobuddy89, @savoca, @maxwen, @Tasssadar, @Cl3Kener, @faux123, Jaegeuk Kim <[email protected]> (Samsung, Inventor of F2FS)
Sources:
Build Sources-
https://github.com/rachanta/kernel_n5_racer/commits/racer-cm
https://github.com/rachanta/kernel_n5_racer/commits/racer-caf-mf
https://github.com/rachanta/kernel_n5_racer/commits/racer-caf
MPDecision, Bricked Thermal and Wake Controls - https://github.com/showp1984/bricked-hammerhead
AOSP Base - https://android.googlesource.com/kernel/msm/+/android-6.0.1_r0.24/
CM Base - https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commits/cm-13.0
CM-CAF Base - https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commits/cm-13.0-caf
CM-CAF-MF Base - https://github.com/myfluxi/android_kernel_lge_hammerhead/commits/cm-13.0-caf-160310
Build Platform:
Ubuntu 15.10, 64 Bit on Dell E5440
Toolchain - UBERTC GCC 6.0.0: https://bitbucket.org/UBERTC/arm-eabi-6.0
Hot plug settings for best battery life
This is how power user @FunkyRasta has mimicked @franciscofranco recommendations
http://forum.xda-developers.com/showpost.php?p=58794360&postcount=1451
http://forum.xda-developers.com/showpost.php?p=58794959&postcount=1453
Settings & Tunings from power users
From @xeraphael
http://forum.xda-developers.com/showpost.php?p=63311535&postcount=2693
Stable working range for RACER L7.0+
Posts by @FunkyRasta, reproduced here for the record:
A quick guide to MSM MPDecision and Three Phase Thermal control by show-p1984
Hotplug section „MSM MPDecsion” in Synapse:
I will not not explain stuff already explained in Synapse itself, I'd rather provide a point of reference and a few profiles for you.
Defaults values for reference:
Runqueue Threshold Hotplug CPU1 - 12
Runqueue Threshold Unplug CPU0 - 0
Runqueue Threshold Hotplug CPU2 - 20
Runqueue Threshold Unplug CPU1 - 7
Runqueue Threshold Hotplug CPU3 - 25
Runqueue Threshold Unplug CPU2 - 10
Runqueue Threshold Hotplug CPU4 - 0
Runqueue Threshold Hotplug CPU3 - 18
Time Threshold Hotplug CPU1 – 140
Time Threshold Unplug CPU0 - 0
Time Threshold Hotplug CPU2 - 140
Time Threshold Unplug CPU1 - 190
Time Threshold Hotplug CPU3 - 140
Time Threshold Unplug CPU2 - 190
Time Threshold Hotplug CPU4 - 0
Time Threshold Unplug CPU3 - 190
Slow Hotplug and Slow unplug of cores – Best battery life, great performance
Runqueue Threshold Hotplug CPU1 - 22
Runqueue Threshold Unplug CPU0 - 0
Runqueue Threshold Hotplug CPU2 - 37
Runqueue Threshold Unplug CPU1 - 18
Runqueue Threshold Hotplug CPU3 - 47
Runqueue Threshold Unplug CPU2 - 22
Runqueue Threshold Hotplug CPU4 - 0
Runqueue Threshold Hotplug CPU3 - 26
Time Threshold Hotplug CPU1 - 400
Time Threshold Unplug CPU0 - 0
Time Threshold Hotplug CPU2 - 400
Time Threshold Unplug CPU1 - 400
Time Threshold Hotplug CPU3 - 400
Time Threshold Unplug CPU2 - 400
Time Threshold Hotplug CPU4 - 0
Time Threshold Unplug CPU3 – 400
HINT: You can combine Hotplugs and Unplugs from these two profiles to get Default Hotplug/Slow unplug etc. mixes to achieve what you want. The presented profiles are delivered with Kcontrol app by show-p1984 himself, if you want to support him then buy it.
Thermal:
Here Synapse screwes up a bit when it comes to naming stuff.
Allowed Low/Mid/High Low should be Low/Mid/High Clear
Allowed Low/Mid/High High should be Low/Mid/High Limit
Firs let's talk about Limit values. If SOC reaches limit value of Low phase it throttles the freq to Allowed Low frequency value. Same goes for Mid and High. If a clear value is reached for Low phase the throttling goes off. Same goes for Mid phase if you set Mid Clear lower than Low Limit. If you set it higher the SOC will go in Low phase and analogically with Mid and High phases.
My recommended settings to keep phone cool without noticeable performance decrease. Completely different than default, which nearly doesn't throttle the phone till it is very hot to drop freq all the way down. Experiment with this values to your liking and compromise beetwen performance/temperature
Low limit – 58 low freq – 1958 MHz
Low clear – 55
Mid limit - 65 mid freq – 1728 MHz
Mid clear – 60
High limit – 70 high freq – 1574 Mhz
High clear - 63
Hope I helped !
For my nearly 40000 bench everything was stock apart and in fact I even set hotplug to slow. Stock thermal would be OK too, not my settings from guide that are supposed to keep phone cool.
With stock settings and stock thermal there's no way you could not have at least 39000 something.
For 43500 run I've raised thermal limits to 80 C, set hotplug Fast in Kcontrol, cooled my phone in the fridge and OC'ed to 2,5 Ghz. Later without cooling at 2,4 Ghz I got 42000.
And I've got to say that battery now on Racer is F***** AWESOME. Exactly two hours screen on with 50 percent battery left ! That's great considering I mostly get 3 hours something SOT from 100 percent with my use. Even greater given the fact that Lollipop drains battery with wifi on (misc battery use in battery history) and that I was playing real racing for 30 minutes.
I'm running 7.0 before it was limited to 2.8 GHz. Today factory images should be relased. Will flash one a post Antutu score with latest build and without any settings editing.
My phone has PVS 3 and undervolted by 35mV.
No cheating no per app setting. Just straight simple, four cores @2,2 GHz ,ondemand governor, deadline scheduler. Minimum freq all the way down to what Synapse allows. Hotplug as in my guide, slow hotplug (try with default) slow unplug. All free thermal phases rased above 80 C using Kcontrol (scroll down and hit apply ! That got me like two times, maybe that's why your antutu runs at 1,9 GHz)
Awesome!! Another Aicp ROM. I will try both flavors now!! Appreciate you're work!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
razrlover said:
Awesome!! Another Aicp ROM. I will try both flavors now!! Appreciate you're work!!
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No that was only the kernel.
Ah that's why i couldn't find it. Even better
Sent from my Nexus 5 using XDA Premium 4 mobile app
rachanta said:
No that was only the kernel. My AICP ROM with the RACER kernel is here:
http://www.androidfilehost.com/?fid=23329332407587747
Click to expand...
Click to collapse
Can I maybe ask what the difference between your aicp & the other one in these threads, either way I'm defiantly going to try the kernel.
Sent from my Nexus 5 using JellyBombed Tapatalk 2
aheeejd said:
Can I maybe ask what the difference between your aicp & the other one in these threads, either way I'm defiantly going to try the kernel.
Sent from my Nexus 5 using JellyBombed Tapatalk 2
Click to expand...
Click to collapse
AICP uses n3ohammer in which kexec hardboot patch is broken, because of which multi ROM does not work.
RACER is cyanogenmod + faux sound + kexec hardboot. MultiROM works. Everything works as it us supposed to. You are welcome to try.
Sent from my Nexus 5 using Tapatalk
Kernel update 22-04-2014
RACER KERNEL update - merged latest cyanogenmod commit
http://www.androidfilehost.com/?fid=23329332407588171
UNOFFICIAL AICP ROM WITH RACER KERNEL - UPDATE 22-04-2014:
http://www.androidfilehost.com/?fid=23329332407588175
Working on n3ohammer fix which is slated to be included in the official AICP ROM.
Latest Unofficial AICP Kernel & ROM
MultiROM enabled:good:
Kernel
http://www.androidfilehost.com/?fid=23329332407589785
ROM
http://www.androidfilehost.com/?fid=23329332407588832
Unofficial Builds update!
RACER KERNEL UPDATE 24-04-2014:
http://www.androidfilehost.com/?fid=23329332407588846
Changelog:
https://github.com/rachanta/kernel_h..._racer/commits
Coming Soon,,,
Official RACER ROM (AICP Unofficial with RACER Kernel)
UNOFFICIAL AICP KERNEL - UPDATE 24-04-2014:
http://www.androidfilehost.com/?fid=23329332407588790
Changelog:
https://github.com/AICP/kernel_lge_hammerhead/commits
UNOFFICIAL AICP ROM - UPDATE 24-04-2014
http://www.androidfilehost.com/?fid=23329332407588832
Note: This version may contain open commits not yet merged to github
Changelog:
http://gerrit.aicp-rom.com/#/q/statuspen,n,z
RACER ROM
Official RACER ROM (AICP Unofficial with RACER Kernel)
http://www.androidfilehost.com/?fid=23329332407589765
Does your kernel feature dt2w? Thanks for your hard work
Sent from my Nexus 5 using XDA Premium 4 mobile app
razrlover said:
Does your kernel feature dt2w? Thanks for your hard work
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No dt2w or s2w atm. RACER is plain CM with faux and sound and kexec harboot.
Cool. Very smooth and fast
Sent from my Nexus 5 using XDA Premium 4 mobile app
razrlover said:
Cool. Very smooth and fast
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My current build at the link has some CPUQUIET Hotplug elements that are supposed to improve battery performance, but their control is not fully functional. I am eliminating CPUQUIET in the next build which I am currently testing.
Sent from my Nexus 5 using Tapatalk
New RACER kernel build in up
New RACER Kernel build is up:
http://www.androidfilehost.com/?fid=23329332407588982
Changelog 25-04-2014:
https://github.com/rachanta/kernel_h..._racer/commits
- Default CPU Freq Governor set to 'ondemand'
- RACER Branding
rachanta said:
New RACER Kernel build is up:
http://www.androidfilehost.com/?fid=23329332407588982
Changelog 25-04-2014:
https://github.com/rachanta/kernel_h..._racer/commits
- Default CPU Freq Governor set to 'ondemand'
- RACER Branding
Click to expand...
Click to collapse
What's the advantages of your kernel? And can I flash it over resurrection remix rom? Thanks in advance
{
"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"
}
I will update this as long as I have time, introducing new features and fixes for any issues that may arise.
If you have any feature requests or ideas that haven't been seen before, don't hesitate to throw it out there, I love new things!
If you're concerned about benchmarks, go here.
Features:
Android: KK (aosp) / L-Preview (l-preview) / CAF (cm-11.0)
CC: Linaro 4.9.1 1406
Ver: 3.4.102
Kernel Compression: LZ4
Ramdisk Compression: LZ4
Min Freq: 94500
Max Freq: 1836000
TCP: HTCP/HSTCP/HYBLA/VEGAS/SCALABLE/LP/VENO/YEAH/ILLINOIS/WESTWOOD(default)
FS: exFAT/F2FS
IO: ROW/BFQ/SIO/FIOPS/ZEN/VR/NOOP/CFQ/DEADLINE(default) / (default readahead - 512)
GOV: intelliactive/ondemandplus/wheatley/ondemand(default)/userspace/powersave/performance/interactive
HotPlug: MPDecision/msm_hotplug(default)
Voltage Control
TouchWake
Semaphore DoubleTap2Wake
DoubleTap2Wake Profiles
DoubleTap2Wake Feather
Bidirectional Sweep2Sleep
Sweep2Dim
Gamma Control
Battery Life eXtender
Force Fast Charge
FSync system call control
Faux123's Sound Control
FRandom
VFP Hardfloat
CPU-Boost
Linaro's Power-Efficient Workqueue
Click to expand...
Click to collapse
Sweep2Dim uses a modified version of the sweep2wake drivers in combination with LG's LCD KCAL driver to raise or lower RGB multipliers based on sweep gestures.
Right -> Left sweeps drop the kcal multipliers by 73 (or, 33% of the 220 avail)
Left -> Right sweeps raise the kcal mulitpliers by 73
If you sweep left continuously, or until your display goes "black", the driver will trigger a powerkey press and turn off the display.
Since KCAL does not alter your backlight's brightness, you Sweep2Dim can work parallel to auto-brightness, and you can even use it to dim the display lower than the brightness 'slider' allows for.
Sweep2Dim is enabled by default, if you want to disable it, just enable Sweep2Wake/Sleep.
Click to expand...
Click to collapse
Main builds have a stock max frequency of 1512MHz
OC tagged builds enable max frequency up to 1836Mhz
Click to expand...
Click to collapse
download / source / changes
Dev Resources:
You will need to get a hold of the latest unpackbootimg/mkbootimg/lz4demo/dtbToolCM binaries, here's a copy of my ~/bin
Boot partition is located here: /dev/block/platform/msm_sdcc.1/by-name/boot
To unpack:
Code:
mkdir output
./unpackbootimg -i boot.img -o output
To repack:
Code:
./mkbootimg --kernel output/boot.img-zImage --ramdisk output/boot.img-ramdisk.lz4 --cmdline "console=ttyHSL0,115200,n8 androidboot.hardware=mako lpj=67677 user_debug=31" --base 0x80200000 --pagesize 2048 --ramdisk_offset 0x02000000 --tags_offset 0x00000100 -o boot.img
note: this kernel requires ramdisk_offset 0x02300000
Unpacking/Repacking ramdisk as .lz4
Code:
lz4demo -d /path/to/ramdisk.lz4
mkbootfs /path/to/ramdisk_dir | lz4demo -c stdin ramdisk.lz4
Packing as .gz
Code:
mkbootfs /path/to/ramdisk_dir | gzip > ramdisk.gz
looks very interesting, thanks
second.. Will test.. Works with L port?
Rohit02 said:
second.. Will test.. Works with L port?
Click to expand...
Click to collapse
If it does, I don't support it. My branch is 4.4.4 but I might make a go at L.
@savoca : Fnally one of the top kernel of N5 to N4...
Great work...
Btw just 1 quick ques...implementation of dt2w, s2w etc have your own modification or standard implementation that most kernel use ?
Reason being 99% implementation have screen freeze issues especially in pocket...so asked...
Screen2dim looks classy
vampire36 said:
@savoca : Fnally one of the top kernel of N5 to N4...
Great work...
Btw just 1 quick ques...implementation of dt2w, s2w etc have your own modification or standard implementation that most kernel use ?
Reason being 99% implementation have screen freeze issues especially in pocket...so asked...
Screen2dim looks classy
Click to expand...
Click to collapse
I used showp's implementation if that helps, but you can see all my changes on github. The S2D video was after an early build on M8, so there's visible quirks there like a delayed setting (this has been fixed for this release)
savoca said:
I used showp's implementation if that helps, but you can see all my changes on github. The S2D video was after an early build on M8, so there's visible quirks there like a delayed setting (this has been fixed for this release)
Click to expand...
Click to collapse
Thanx a lot Checking out :good:
vampire36 said:
Thanx a lot Checking out :good:
---------- Post added at 08:20 AM ---------- Previous post was at 08:11 AM ----------
Am checking out S2D and just read your detailed explanation of it...am planning to use it in place of S2S and S2W...for that will need to set value to 255 for drop or increase...
My query is is S2D with 255 drop working differently than S2S/S2W...?
Click to expand...
Click to collapse
Well that would be a poor choice, in my opinion. S2D just manipulates RGB mulitpliers, so if you set them all to 0, you still have a backlight shining through a black screen, a major major drain. You could use it inplace of S2S only, however you would need to use DT2W for screen on (I can actually allow S2W aswell, I'll make some changes tomorrow).
To change the amount that is raised/dropped per gesture the sysfs is below.
Code:
echo "1/255" > /sys/module/sweep2wake/parameters/down_kcal
echo "1/255" > /sys/module/sweep2wake/parameters/up_kcal
savoca said:
Well that would be a poor choice, in my opinion. S2D just manipulates RGB mulitpliers, so if you set them all to 0, you still have a backlight shining through a black screen, a major major drain. You could use it inplace of S2S only, however you would need to use DT2W for screen on (I can actually allow S2W aswell, I'll make some changes tomorrow).
To change the amount that is raised/dropped per gesture the sysfs is below.
Code:
echo "1/255" > /sys/module/sweep2wake/parameters/down_kcal
echo "1/255" > /sys/module/sweep2wake/parameters/up_kcal
Click to expand...
Click to collapse
Yup get the point...Would be great if you could look at it from s2w point...s2s working good...s2w i don't know...almost all have given me screen unresponsive issue...will test furnace 2...if you could allow s2w with s2d i don't know if it will work together with s2s...but if it does hope gives a good solution for non power button use...
Btw are default setting optimal or need to modify any values ? Whats the config you use ?
vampire36 said:
Yup get the point...Would be great if you could look at it from s2w point...s2s working good...s2w i don't know...almost all have given me screen unresponsive issue...will test furnace 2...if you could allow s2w with s2d i don't know if it will work together with s2s...but if it does hope gives a good solution for non power button use...
Btw are default setting optimal or need to modify any values ? Whats the config you use ?
Click to expand...
Click to collapse
I'll definitely work in S2W+S2D no problem. The default settings are fine for me as well.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Everything working fine so far. I report battery life and more impressions later.
Edit: maybe you take a look into semaphore dt2w implementation. For me it is better and I don't have the problem of unresponsive touchscreen after boot and not touch the screen in 30 sec.
Very happy to see you here!!
Been using your MotoG kernel from beginning and now for my N4 too
Nice something new to flash
Is there are reason for not implenting ROW?
Oh and any preferred kernel app ?
@savoca
time to jumping from Semaphore to this !
Let's try this out, always love when new kernels come for our device
N⁴
vampire36 said:
Yup get the point...Would be great if you could look at it from s2w point...s2s working good...s2w i don't know...almost all have given me screen unresponsive issue...will test furnace 2...if you could allow s2w with s2d i don't know if it will work together with s2s...but if it does hope gives a good solution for non power button use...
Btw are default setting optimal or need to modify any values ? Whats the config you use ?
Click to expand...
Click to collapse
kevinnol said:
Nice something new to flash
Is there are reason for not implenting ROW?
Oh and any preferred kernel app ?
Click to expand...
Click to collapse
Preferred kernel app is trickster, I make the sysfs with that app in mind (e.g. intelliplug 3.7 w/ eco_mode_active obj) and their dev team told me they added sweep2dim as a todo for next release.
Here's a boot.img that allows S2D to work with S2W, overriding S2W+S2S only if S2D is enabled, if that makes sense. I also added back all the original TCP/IO (reno,cubic,bic..noop,cfq) and added ROW, didn't catch that Google didn't include it by default. Lastly, I made S2W bidirectional, I guess I'll update this into the next version at the next linux kernel bump.
savoca said:
Preferred kernel app is trickster, I make the sysfs with that app in mind (e.g. intelliplug 3.7 w/ eco_mode_active obj) and their dev team told me they added sweep2dim as a todo for next release.
Here's a boot.img that allows S2D to work with S2W, overriding S2W+S2S only if S2D is enabled, if that makes sense. I also added back all the original TCP/IO (reno,cubic,bic..noop,cfq) and added ROW, didn't catch that Google didn't include it by default. Lastly, I made S2W bidirectional, I guess I'll update this into the next version at the next linux kernel bump.
Click to expand...
Click to collapse
i would like to make a request please: kindly add pocket mod in your kernel as there is one in elemental x kernel in HTC One M7... (my phone always wake in my pocket and starts tee toun tee taan... Emergency call pee poon paan... etc...
Mortal Eternity said:
i would like to make a request please: kindly add pocket mod in your kernel as there is one in elemental x kernel in HTC One M7... (my phone always wake in my pocket and starts tee toun tee taan... Emergency call pee poon paan... etc...
Click to expand...
Click to collapse
There's some major differences between the drivers on N4 and M7 so I'm not sure how hard that would be, but I do have this commit I can use to make dt2w more less (or more, it's configurable) as well, let me know what you think.
Nekator said:
Everything working fine so far. I report battery life and more impressions later.
Edit: maybe you take a look into semaphore dt2w implementation. For me it is better and I don't have the problem of unresponsive touchscreen after boot and not touch the screen in 30 sec.
Click to expand...
Click to collapse
+1 for semaphore dt2w. By far the most consistent/efficient for me.
savoca said:
There's some major differences between the drivers on N4 and M7 so I'm not sure how hard that would be, but I do have this commit I can use to make dt2w more less (or more, it's configurable) as well, let me know what you think.
Click to expand...
Click to collapse
I feel too configurable cool but you should look at Stratosk's implementation...Semaphore kernel...best and no screen unresponsive issue
Btw tried s2w with 5 min of stay in pocked got unresponsive screen Had to use power button using gravity screen on/off with furnace for now Btw changed governor to intellidemand...uv -75 rest default...working a treat Thanx again