Introduction & Disclaimer:
If you've ever flashed a new rom, updated a firmware, or plain reformatted - all because you just had to have the newest __blank__? Then you have come to the right place.
READ THE FAQ's!
There isn't one yet, but a kind user should donate some time and it will be posted
Click to expand...
Click to collapse
Click to expand...
Click to collapse
AmeriCanAndroid Alpha Series Kernels
For SENSE **AND** NONSENSE Android ROMs
Brought to you by: Warrenb213 & Copenhagen: Two **RECOGNIZED** XDA-developers
Image Gallery:
Not Applicable - Kernel Build
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Description:
AmeriCanAndroid Alpha Series Kernels
HTC Shooter_U 3.0.16 based
latest updates always compiled from git source.
changelog: GOOGLE GIT SITE
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
Current Release:
12.29.12 - ACA Alpha Series V11 - BT may or may not work in SENSE
-See GIT
Click to expand...
Click to collapse
Previous Releases:
10.13.12 - ACA Alpha Series V10 - BT may or may not work in SENSE
-See GIT - NOT SYNC'D YET
10.1.12 - Initial Release:
Switched defconfig back to bcm4329_248. Other slight mod.
==> name kernel, enable swap, set CIQ as default, set interactive as default, disable perflock, remove spi_spidev, enable zram, enable ext2, ext3, cifs,
Some config changes. Switch back to BCMHD.
Scaling governers perm fix
Lowered Wifi Voltage
==> MMC_VDD_21_22,
Slight change
PM_FAST in standby
CPU speed stuff
Config Changes. Some clock change
CPUFreq Permission
Enable CFQ
Update version info
Update 2D GPU clock
==> not really the 2d clock, but the struct/table used to define the 2d clock speeds..
==> removed 228MHz, and replaced it with 266
Updated config
mm: adjust vm ratios (mdj)
==> vm_dirty_ratio = 10 // vm_swappiness = 90;
include: mm: increase readahead buffer (mdj)
==> VM_MAX_READAHEAD 1040
Makefile: Added Snapdragon optimizations (originally from mdj)
Added ACA compile scripts and made a default copy of existing config to work from.
First Commit. Let Alpha Series Live.
Click to expand...
Click to collapse
Installation & Updating:
Installation & Updating Proceedure is the same!:
NAND:
Download the Alpha Series Kernel to your PC or Android Device - Just make sure it ends up on your Android's SD card.
1. Reboot to Recovery.
2. Select the ZIP file.
3. Flash.
4. Win!
ATTENTION: I know this kernel/modules combo works well with CM9, CM10, and Viper3D MULTI (V3D may have BT issue now?).
If Wifi or Bluetooth do not work, the ROM may need to be modded (init.shooteru)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
12.29.12 - V11
Alpha Series Kernel V11 - http://americanandroid-evo3d-alphaseries-htc-3016.googlecode.com/files/ACAAlphaKernel-V11.zip
mirror - None Yet
10.13.12 - V10
Alpha Series Kernel V10 - http://americanandroid-evo3d-alphaseries-htc-3016.googlecode.com/files/ACAAlphaKernel-V10.zip
mirror - None Yet
discussion for this release starts on this page
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Donations:
if you truly feel we are deserving, your donations are appreciated <--clicky!.
Coffee to keep us awake and working
THANKYOU to those who have already done so. We'll keep working on making you a better build as best we can.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Major thanks to:
google - obviously...
cyanogenmod team - for the great effort they put into their very high quality work. the ground floor to the roof and then some. Amazing Amazing.
copenhagen - I saw we needed to thank you too Mr Canadian. haha. You rock.
warrenb213 - its great working with you... its way better to have an team mate for these projects. and you've brought alot to this build. thankyou so much
mdj - researching your builds have helped us tremendously in accomplishing this.. major thankyou.
agrabren - Thank you for your consistent contributions to the community!
anryl - for the updater script which I adapted. Kudos!.
xda - for the forums.. the info.. and the users
to everyone else we missed. Thankyou
working for a community on a community project; to those who came before us, thankyou for everything you have done.. Thankyou.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Source:
The AmeriCanAndroid Alpha Series Source Code can be found at:
http://code.google.com/p/americanandroid-evo3d-alphaseries-htc-3016/
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Secure 1
Secure 2
Secure 3
Good to see you here, was worried about development from you all.
Many will be very happy.
scariola said:
Good to see you here, was worried about development from you all.
Many will be very happy.
Click to expand...
Click to collapse
Development takes forever. I've been sitting on this for a while, as you'll probably notice when you look at my commit dates. LOL. I can say it's solid.
In my personal testing in CM9, I can go roughly 12-14 hours moderate usage stock battery.
scariola said:
Good to see you here, was worried about development from you all.
Many will be very happy.
Click to expand...
Click to collapse
Like me =)
warrenb213 said:
Development takes forever. I've been sitting on this for a while, as you'll probably notice when you look at my commit dates. LOL. I can say it's solid.
In my personal testing in CM9, I can go roughly 12-14 hours moderate usage stock battery.
Click to expand...
Click to collapse
Cool. Gonna test.
Sent from my HTC EVO 3D X515m using xda premium
so this kernel is supposed to work on GB/ICS with SENSE 3.6 series onwards?
or just those Cyanogen etc?
am only aware that its SENSE/NONSENSE
now i wonder who's willing to bite the bullet
Welcome Back
What a good start of the day ! :victory:
Hopping you good success in our 3vo cooking.
Having been an addict on your work for HD2, I am impatient to go back home (after work) and test your creation.
Thanks for coming back :highfive:
Any changelog?
Hope will support exFAT or NTFS later:good:
warrenb213 said:
Development takes forever. I've been sitting on this for a while, as you'll probably notice when you look at my commit dates. LOL. I can say it's solid.
In my personal testing in CM9, I can go roughly 12-14 hours moderate usage stock battery.
Click to expand...
Click to collapse
Yes it can but at the same it can fast as well. Built my first sense kernel in less than 24 hours. http://forum.xda-developers.com/showthread.php?t=1866375
You only have one commit?
good old AmericanAndroid
the most awesome roms back in the HD2 days
MikeC84 said:
Yes it can but at the same it can fast as well. Built my first sense kernel in less than 24 hours. http://forum.xda-developers.com/showthread.php?t=1866375
You only have one commit?
Click to expand...
Click to collapse
Nav to the other branch....
Sent from my HTC EVO 3D X515m using xda app-developers app
So what offer this kernel?
LoKKeR said:
So what offer this kernel?
Click to expand...
Click to collapse
Solid performance?
AmeriCanAndroid always offers a rock solid performance. We may not do all the little things others do, or as in as much of a hurry, but we thoroughly test and try to bring the best experience.
I have a new kernel I just cooked up with some interesting changes which I'm about to try. This is I'll probably test/tweak for a few days before release.
May I suggest some info would be beneficial to those who might want to try your kernel, is it a secret? All we know is it is based on the stock HTC kernel????????????????? Nothing against you or your kernel but we do have abundance of inferior kernels available already
(don't ask me for help, as I couldn't care less if you phone explodes,eh!!!)
here is a change log for those who wish to know whats up..
(going off of the AOSP branch)
Code:
Switched defconfig back to bcm4329_248. Other slight mod.
==> name kernel, enable swap, set CIQ as default, set interactive as default, disable perflock, remove spi_spidev, enable zram, enable ext2, ext3, cifs,
Some config changes. Switch back to BCMHD.
Scaling governers perm fix
Lowered Wifi Voltage
==> MMC_VDD_21_22,
Slight change
PM_FAST in standby
CPU speed stuff
Config Changes. Some clock change
CPUFreq Permission
Enable CFQ
Update version info
Update 2D GPU clock
==> not really the 2d clock, but the struct/table used to define the 2d clock speeds..
==> removed 228MHz, and replaced it with 266
Updated config
mm: adjust vm ratios (mdj)
==> vm_dirty_ratio = 10 // vm_swappiness = 90;
include: mm: increase readahead buffer (mdj)
==> VM_MAX_READAHEAD 1040
Makefile: Added Snapdragon optimizations (originally from mdj)
Added ACA compile scripts and made a default copy of existing config to work from.
First Commit. Let Alpha Series Live.
OP:
may want to make use of the 266MHz entry you created for 2D GPU, 2D clock seems to be capped at 200MHz in devices-msm8x60.c
you also may wanna define item 4 in your FSB struct/table as your L2 cache is pointing to it
Code:
[17] = {1296000, 1, 0x18, 1200000, 1225000, 3},
[18] = {1350000, 1, 0x19, 1200000, 1225000, 3},
[19] = {1404000, 1, 0x1A, 1200000, 1250000, 3},
[20] = {1458000, 1, 0x1B, 1225000, 1275000, [B]4[/B]},
[21] = {1512000, 1, 0x1C, 1225000, 1275000, [B]4[/B]},
[22] = {1566000, 1, 0x1D, 1225000, 1275000, [B]4[/B]},
Code:
static struct msm_bus_paths bw_level_tbl[] = {
[0] = BW_MBPS(824), /* At least 103 MHz on bus. */
[1] = BW_MBPS(1336), /* At least 167 MHz on bus. */
[2] = BW_MBPS(2008), /* At least 251 MHz on bus. */
[3] = BW_MBPS(2480), /* At least 310 MHz on bus. */
};
also, is the WiFi voltage stable for you? - its lower than the whitepaper spec, never seen any other kernel go this low.
Code:
.ocr_mask = MMC_VDD_21_22,
warrenb213 said:
Solid performance?
AmeriCanAndroid always offers a rock solid performance. We may not do all the little things others do, or as in as much of a hurry, but we thoroughly test and try to bring the best experience.
I have a new kernel I just cooked up with some interesting changes which I'm about to try. This is I'll probably test/tweak for a few days before release.
Click to expand...
Click to collapse
Does it have ZSL?
Sent from HTC EVO 3D loaded with mwakious3Drom v12.4 coolexe kernel 2.9
jimmy_coolguy2006 said:
Does it have ZSL?
Sent from HTC EVO 3D loaded with mwakious3Drom v12.4 coolexe kernel 2.9
Click to expand...
Click to collapse
I think "That other kernel" that is not on XDA was the only one to even bring ZSL to the 3D
TweetyBear said:
here is a change log for those who wish to know whats up..
(going off of the AOSP branch)
Code:
Switched defconfig back to bcm4329_248. Other slight mod.
==> name kernel, enable swap, set CIQ as default, set interactive as default, disable perflock, remove spi_spidev, enable zram, enable ext2, ext3, cifs,
Some config changes. Switch back to BCMHD.
Scaling governers perm fix
Lowered Wifi Voltage
==> MMC_VDD_21_22,
Slight change
PM_FAST in standby
CPU speed stuff
Config Changes. Some clock change
CPUFreq Permission
Enable CFQ
Update version info
Update 2D GPU clock
==> not really the 2d clock, but the struct/table used to define the 2d clock speeds..
==> removed 228MHz, and replaced it with 266
Updated config
mm: adjust vm ratios (mdj)
==> vm_dirty_ratio = 10 // vm_swappiness = 90;
include: mm: increase readahead buffer (mdj)
==> VM_MAX_READAHEAD 1040
Makefile: Added Snapdragon optimizations (originally from mdj)
Added ACA compile scripts and made a default copy of existing config to work from.
First Commit. Let Alpha Series Live.
OP:
may want to make use of the 266MHz entry you created for 2D GPU, 2D clock seems to be capped at 200MHz in devices-msm8x60.c
you also may wanna define item 4 in your FSB struct/table as your L2 cache is pointing to it
Code:
[17] = {1296000, 1, 0x18, 1200000, 1225000, 3},
[18] = {1350000, 1, 0x19, 1200000, 1225000, 3},
[19] = {1404000, 1, 0x1A, 1200000, 1250000, 3},
[20] = {1458000, 1, 0x1B, 1225000, 1275000, [B]4[/B]},
[21] = {1512000, 1, 0x1C, 1225000, 1275000, [B]4[/B]},
[22] = {1566000, 1, 0x1D, 1225000, 1275000, [B]4[/B]},
Code:
static struct msm_bus_paths bw_level_tbl[] = {
[0] = BW_MBPS(824), /* At least 103 MHz on bus. */
[1] = BW_MBPS(1336), /* At least 167 MHz on bus. */
[2] = BW_MBPS(2008), /* At least 251 MHz on bus. */
[3] = BW_MBPS(2480), /* At least 310 MHz on bus. */
};
also, is the WiFi voltage stable for you? - its lower than the whitepaper spec, never seen any other kernel go this low.
Code:
.ocr_mask = MMC_VDD_21_22,
Click to expand...
Click to collapse
Thanks for the feedback.
I will adjust.
Also, yes my WiFi is stable.
Related
Installation Instructions:
Here's a step by step instruction to install this kernel:
************************** Ice Cream Sandwich (S-OFF ONLY) **************************
[ CFS ] (Ultimate Edition - should work with most phones but NOT GUARANTEED!)
The File ==> Amaze ICS Kernel <==
MD5SUM ==> <==
************************** Gingerbread **************************
[ CFS ] (Ultimate Edition - should work with most phones but NOT GUARANTEED!)
The File ==> Amaze GB Kernel <==
MD5SUM ==> <==
CWM Flash Instructions: (NO LONGER SUPPORTING CWM METHOD DUE TO HTC's STUPID S-ON UNLOCK!!!)
1. Copy file to SDcard
2. Reboot to CWM recovery
3. Flash the Zip file (if you noticed an error, Flash the same file the 2nd time)
4. Reboot, Done!
Easy Kernel Flasher Instructions:
1. download the above file (via phone directly or to a PC)
2. unzip to a folder then depends on PC or Linux
[ Windows ] open command prompt window and type Flash.bat
[ Linux ] open terminal window and type ./Flash.sh (make sure permission is set to 755 for the Flash.sh)
3. Let the script complete!
NOTE: Because the previous kernel included a Secured RAM Disk, so you may need to run the script twice. (Once this is done, then any subsequent flash should complete on the first time)
Note: After FLASHING, the first reboot may take longer than usual, please be patient... After the first reboot, it may lag during initial load (let everything finish loading). Once everything is loaded and phone is ready for use, reboot the phone a 2nd time and the lag will be gone and everything should be silky smooth...
[ Optional: ]
NOTE: if you come from a ROM with my kernel pre-installed, you DO NOT NEED to flash the reset kernels from above!
[ For Kernel Devlopers ONLY: ]
Optional Under voltage: Version 0.0.x+ ONLY
Code:
[ to over volt ALL frequencies by 25000 uv (microvolts) ]
echo "+25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to under volt ALL frequencies by 25000 uv (microvolts) ]
echo "-25000" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
[ to set a specific frequency (ie 1.18 GHz)
with a specific voltage (ie 1.0875 volts) ]
echo "1188000 1087500" > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
CPU Frequency Voltage Table Example
Code:
192000: 812500
310500: 812500
384000: 812500
432000: 812500
486000: 837500
540000: 850000
594000: 862500
648000: 875000
702000: 900000
756000: 925000
810000: 937500
864000: 962500
918000: 962500
972000: 962500
1026000: 975000
1080000: 987500
1134000: 1000000
1188000: 1012500
1242000: 1025000
1296000: 1050000
1350000: 1075000
1404000: 1100000
1458000: 1112500
1512000: 1125000
1566000: 1150000
Optional: Stock Clock Frequencies for Dual CPUs
Code:
su
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpu1/cpufreq/online
echo 192000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq
echo 1188000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq
Low Voltage - Under Volt the processor, therefore uses Less Battery, but NOT ALL CHIPS can handle Under Volt.. If you experience instability, try the Stock Voltage Version.
Stock Voltage - Uses the voltage values from ORIGINAL HTC Kernel Source.
There are NO PERFORMANCE DIFFERENCE between the Under Volted and Stock Voltage versions!
Please don't hesitate to talk among yourselves and help each other out... The XDA community is what inspired me to hack kernels for everyone since everyone here is nice and helpful to each other... Keep helping each other.... Famous proverb: It's better to give than to receive...
Not All CHIPS ARE CREATED EQUAL
Standard Disclaimer: Not responsible for bricking your phone, voiding your warranty, or any other pain or suffering you may feel as result of using this kernel!!!
My github Complying with GPL and XDA rulez
Follow me on
:
If you find this Kernel useful, feel free to hit the [Thanks] button below
FauxClock App recommended Settings"
CPU Control
Max clock - GHz 1.72 GHz for performance, 1.512 GHz for battery
Min clock - MHz 192 MHz for both
CPU Governor - Ondemand for performance, Intellidemand for battery
mpdecision - Off
Set On Boot - On
SOC Control
Set On Boot - On
C0 - On
C1 - On
C2 - On
Voltage Control
Set On Boot -
Global CPU Voltage - Your preference
intellidemand gov control
Up Threshold - 90 for both
Two Phase Freq - 1134000 for both
Limit Max Freq - 1728000 for performance, 1512000 for battery
Sampling Rate - 30000 for both
Set On Boot - On
GPU Control
GPU Governor - ondemand for both
GPU Clock - 300Mhz for performance and 266Mhz for battery
GPU Vsync Toggle - On for both
Set On Boot - On for both
I/O Scheduler Control
I/O Scheduler (eMMC) - SIO for both
Readhead Size (eMMC) - 384 for both
Set On Boot - On for both
Misc Control
Dynamic File Sync - On for both
TCP Congestion Control - Westwood for both
Vibration Control
Set On Boot - On for both
Vibration Control - Your own Preference
Above is what I use personally. MAY NOT be optimal for all :fingers-crossed:
[ History Gingerbread]
Version 004 - Dec 16, 2011 (Deprecated, GB)
Add OC to 1.73 GHz
Add UV table
Add PPP async for VPN users
add CIFS+UTF-8
add Fast NoHz RCU option
CFS Auto Group V2
Optimized memmove and memcpy
Opitmized JHash
code sourcery: fixed code sourcery compilation warnings
dm-cache: block level disk cache target for device mapper
kernel:sched: LOAD_FREQ (4*HZ+61) avoids loadavg Moire
Version 005 - Dec 17, 2011 (deprecated, GB)
Removed some annoying kernel debugging messages from Spamming dmesg log
Switched to Xboarder's Easy Kernel Flasher Version 3 (EKF)
Version 006 - Dec 17, 2011 (deprecated, GB)
Lowered LED button back light current
Enabled Automatic Brightness on LED button back light.
Version 008 - Jan 22, 2011 (Short Term Release, GB)
http://faux.eth0.it/Amaze-EKF-008b13-sense.zip
Disable CPU time statistics (this is the same as my Sensation kernel, a slow memory leak which leads to a kernel crash!)
Patched KGSL (GPU)
Patched MMC for better battery savings
PM / Hibernate: Correct additional page calculation
arm: Allow CPU-supported unaligned accesses
ARM/MM: reduce memory footprint
partition_sched_domains: Do not destroy old sched domain on cpu_up
lockdep: print lock name for lockdep_init_error
init/main.c: execute lockdep_init as early as possible
cpufreq: ondemand gov tweaks
msm: audio: qdsp6v2: Close smd ports upon failure to open.
msm: audio: qdsp6v2: Reduce the pcm write timeout value
cpufreq: add ondemand two-phase scheduling
msm: cpufreq: Use INIT_COMPLETION instead of init_completion
cpufreq: add CPU sibling code to remember last cpu freq before unplug
msm: cpufreq: Create cpufreq workqueue for freq changes
Fixed CPU1 voltage and frequency issues introduced in Beta 9
added XZ compression (reduce kernel size)
more MMC patch
added SHA-1 for faster boot
added SMP optimization
disable USB OTG capability
Updated USB, OTG, VIDC, Camera and DMA drivers from Telus Kernel source.
disabled CPU overclocking
sdio: Handle graceful shutdown
sdio: fix MCI_CLK corruption
driver/vibrator: reduce debug message spam to dmesg log
Added JRCU (thanks to Joe Korty!)
Patched MMC lock up issue
Removed additional Panasonic Gyro Log Spams
Patched RPC and SMD drivers
Version 009 - Mar 13, 2011 (Current, GB)
Reverted back to Fast NoHz RCU (better battery life than jRCU)
disabled Gentle Fair Sleepers (supposedly better for Android interactivity)
tweaked RAMDISK settings for kernel scheduling parameters for better interactivity
Reduced 2D instantaneous bandwidth demand to conserve more battery life
Hello and welcome faux.
I have your kernels on my G2X (DS OC/UV) and family plan member's MT4G (stock).
I will be trying this as soon as the link is up. Will also be helping you to get the phone, but am traveling (back in CA) right now.
I like this device so far. Has the best camera and video cam I have tried so far.
Will be even better after HTC drops the source - it needs AOSP/Cm7(?)/Miui real bad.
Xboarder (all 16 years) has been doing all the heavy lifting so far, so your coming over here - especially with respect to kernels, is a very good thing.
Thanks faux, gonna update my rom today how about tmobile compatibilty?
Sent from my HTC Sensation Z710e using Tapatalk
I need some help....
Can someone with the phone tell me which partition the boot.img is located?
My guess is either /dev/block/mmcblk0p28 or /dev/block/mmcblk0p32
Thanks!
Faux123 it's so great to see you over here in the Amaze forum, loved your great work over on the MT4G. Hope to see the bounty take off so you don't have to dev blind.
faux123 said:
I need some help....
Can someone with the phone tell me which partition the boot.img is located?
My guess is either /dev/block/mmcblk0p28 or /dev/block/mmcblk0p32
Thanks!
Click to expand...
Click to collapse
I am not sure how to find that out. There had been a thread on the partition layout of the Amaze, but now can't find it.
New thread in General says Amaze source just dropped - will that show it?
http://www.mobileburn.com/17631/news...ire-s-amaze-4g
Actual link:
http://www.htcdev.com/devcenter/downloads
faux123 said:
I need some help....
Can someone with the phone tell me which partition the boot.img is located?
My guess is either /dev/block/mmcblk0p28 or /dev/block/mmcblk0p32
Thanks!
Click to expand...
Click to collapse
i'm still waiting for my precious and, by the way, it's great to see you here
but maybe this will help
http://forum.xda-developers.com/showthread.php?t=1306211
Amaze Enhanced Kernel with JRCU is OUT.. Check OP for link and check 2nd post for change log for this initial BETA.
WARNING: THIS IS A BLIND BUILD, please keep this in mind when flashing this kernel. This kernel is stock @ 1.512 GHz with NO OC and NO UV enabled. Once I get my hand on the hardware and TEST the OC/UV myself, I will add those capabilities to this phone.
ALSO this is BASED ON T-MOBILE kernel source. I realize there's a separate Telius source and I WILL MERGE the two together as 1 unified kernel but again I will reserve it until I have the hardware in hand.
Thank you Faux. Will SetCPU work for underclocking?
Just tried installation and received error: assert failed:
write_raw_image (" /emp/newboot.img", "boot")
E:Error in /sdcard/download/Amaze-kernel-001B-J-sense.zip
(Status 7)
Installation aborted.
pc2828 said:
Thank you Faux. Will SetCPU work for underclocking?
Just tried installation and received error: assert failed:
write_raw_image (" /emp/newboot.img", "boot")
E:Error in /sdcard/download/Amaze-kernel-001B-J-sense.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Give this one a try...
First time Kernel for Amaze:
http://www.multiupload.com/F4N05ZCH32
Welcome bro,
I hear your a kernel god.
And thanks for further clarifying what kernels do for us semi-noobs lol
Can't wait for your releases.
Sent from my HTC Amaze 4G using xda premium
faux123 said:
Give this one a try...
First time Kernel for Amaze:
http://www.multiupload.com/F4N05ZCH32
Click to expand...
Click to collapse
Recovery flash says successful... however still shows HTC kernel. Should I push ADB or do I have to do fastboot because I am HTCDev unlocked S-On...?
macheteZen said:
Recovery flash says successful... however still shows HTC kernel. Should I push ADB or do I have to do fastboot because I am HTCDev unlocked S-On...?
Click to expand...
Click to collapse
Hm.. that is interesting! I wonder if S-On had something to do with it
Also, can someone please post a screenshot of the
Stock kernel Version number...
Settings->about phone->software information->more
and post it here.
I believe you have to flash the kernel with xboarders method.. There's a thread for it, but I'm on my phone so i can't link it
Sent from my HTC_Amaze_4G using XDA App
{
"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 think this is stock, looks like it.don't remember if i messed with it or not. Someone else confirm?
Sent from my HTC_Amaze_4G using XDA App
Because we're s-on you have to use xboarders work around to flash kernels, thats one of the few things you cant change with htc unlock method normally
That is the stock kernel information with the latest public ota applied
Sent from my HTC Ruby using xda premium
Teo032 said:
I think this is stock, looks like it.don't remember if i messed with it or not. Someone else confirm?
Sent from my HTC_Amaze_4G using XDA App
Click to expand...
Click to collapse
That's the same as what I have after installing the kernel script. It appears to be stock kernel.
{
"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"
}
The Beastmode-LTE kernel Project
This is a Kernel for the Evo 4g LTE the source is from HTC with mods by myself. You can find my modified source code at https://github.com/zarboz/EvilZ-Kernel
and at my teams github here
https://bitbucket.org/teamblackout/evilz.213.blackout_edition/
What is a kernel you might ask?
A kernel is the lowest level of easily replaceable software that interfaces with the hardware in your computer. It is responsible for interfacing all of your applications that are running in “user mode” down to the physical hardware, and allowing processes, known as servers, to get information from each other using inter-process communication (IPC).
Click to expand...
Click to collapse
If you dont see something on future plans that you would like. Please shoot me a message
What is Sweep2wake?
It Allows you to make a Sweeping action along the bottom of your screen to wake or sleep the screen (mimics action of the power button) So just sweep to wake or sleep your phones screen
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)
Click to expand...
Click to collapse
Source is available for you to download and compile. I also have the boot.img's and some handy dandy update.zips for everyone to try out.
flash at your own risk
i am not responsible for bricks malfunctions or any other hardware issues you may run into while running my software
overclocking does break manufacturers warranty and pushes your devices limits physically....
I HIGHLY suggest you use Kernel Tuner to tune this kernel as you can control your GPU/Sweep2wake/Individual Core control/Mpdecision control/profiles
and its Free!
RC7
http://www.androidfilehost.com/?fid=9390214368362234322
Special thanks to ExiledLife
he let me guineapig his phone for the first test runs
would like to extend thanks to:
Sbryan12144, Ca1ne, Mdeejay, Faux123, DooMLorD , TwistedUmbrella, Imoseyon. ThickLizard, ToastCFH, Rydah805, The people who donated and continue to donate, and all the great people on XDA
all upstream patches came from kernel.org and were applied using the standard patch command and then cleaning up .rej files as they come
some upstream patches were cherry-picked from github and are noted as such
HUGE HUGE HUGE HUGE HUGE HUGE thanks to:
Showp1984 For all his help and for thinking up a great thing like sweep2wake
Please track all bugs issues here
http://code.google.com/p/this-project-is-zarboz/issues/list
please include rom revision s-off or on status and description of problem
I would appreciate the reporting
ONLY REPORT BUGS FOR MY KERNEL DOWNLOADED FROM THIS THREAD
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
Code:
adb shell dmesg > errorreportdump.txt
this will spawn a .txt file in the directory your shell is in upload this file this will suffice for a stacktrace
If the bug is determined to be a USERSPACE problem i will notify you via the bug tracker and close your issue
otherwise im pretty good about responding i get to it about once every 2 weeks
Common bugs and fixes for them:
Unable to boot
I have started the phone slightly undervolted and due to this it causes some units to fail to boot. This will be resolved in a future release
only try this fix for rc5 and under
-viperboy- said:
Sorry for the delay with this, here is something that might help those who cannot fully boot on this kernel...
https://dl.dropbox.com/u/6621763/HTC_EVO_4G_LTE_Kernel_Voltage_Stabilizer.zip
It increases the voltage all across the board by 75mv.
To remove the mod
https://dl.dropbox.com/u/6621763/HTC_EVO_4G_LTE_Kernel_Voltage_Stabilizer_Remover.zip
Click to expand...
Click to collapse
Downloads for older base kernel
https://www.dropbox.com/s/csryh6zczcts89b/EvilAroma.122.005-revised.zip
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
Downloads for the New 2.13 Based kernel
RC1
https://www.dropbox.com/s/qqn8n7dp0mj3fb4/EvilZ.BLACKOUT.213.zip
RC2 GPU OC (this is getting screenoff reboots per reports)
https://www.dropbox.com/s/hpdtp7w39qqtjrc/EviLZ.213.BLACKOUT.RC2.zip
RC2 NO GPU oc
https://www.dropbox.com/s/2o9sr42pznychme/EvilZ.BLACKOUT.RC2.noGPU.zip
----------------------------------------
Rc3
https://www.dropbox.com/s/ryl869a7r3cr0rd/EvilZ.231.RC3.zip
RC4
https://www.dropbox.com/s/xzo2r60l8ka8o79/EvilZ.213.RC4.zip
S2w Rc4
https://www.dropbox.com/s/e6udgmvmr5ho1tn/EvilZ.S2W.3.zip
RC5
https://www.dropbox.com/s/4rt5bplt9gol38n/EvilZ.231.RC5.zip
RC6
https://www.dropbox.com/s/2v0kxw71863zqgo/EvilZ.RC6.zip
Banners:
Changelog for old base
Code:
Removed GPU OC
Added more Max OC options
Reworked multipaging/tasking
reworked CFQ Scheduler
Custom Governors added: Performance, Powersave, Userspace, Ondemand, Interactive, Conservative, Smartass, Smartassv2, lagfree, ondemandx, interactivex, minmax, savagedzen, lionheart ,intellidemand,brazillian wax
MHL refresh hack
Adjustable undervolt
reworked alot of this that and the other
added some Z power
hrew it in the kitch and gave it to yall
Changelog 2.31 Base 09/22/12 rc1
Code:
Custom Governors added: Performance, Powersave, Userspace, Ondemand, Interactive, Conservative, Smartass, Smartassv2, lagfree, ondemandx, interactivex, minmax, savagedzen, lionheart ,intellidemand, brazillian wax
Adjustable under volt
reworked CFQ Scheduler
GPU OC added backin
Adjusted Voltage tables to mirror selected OC instead of having mismatched values
Disabled Fsync call
Adjusted Vsprint calltos &pV handling with kasprintF
No longer call dump_stack in binder_vma_open
Patched missing jtag portions
Changelog 10/8/12 rc2
Code:
Removed GPU OC upon request.
Removed bad Governors until i can iron out the kinks in them
S On Friendly installer < big one
Changelog 10/9/12 rc3
Code:
Removed Sweep2wake bits causing screenoff KP (coming soon tho)
Removed bad Governors lulzactive was ruining our fun for some reason!!
Changelog 10/13/12 rc4
Code:
- Added in new governors: Wheatley, Scary, Asswax
- AssWax is a blend of brazillianwax smartass and interactive.
It is intended to bring you a well balanced VERY responsive experience
it also does great with deep cycling on sleep
- Added L2 Cache boosting up to 1 step below your max clock choice.
So if you choose 1.5ghz your l2 is boosted to 1.4, If you choose
1.7ghz your L2 is boosted to 1.6 ghz etc. etc..
Oct 27 2012
Code:
-Added Sweep2wake Switch is located in /sys/android_touch/sweep2wake 0=off 1=on
-New Governor Should be included Badass. If not showing please post and i will correct
Oct 28 2012 RC5
Code:
-Kernel Based Mpdecision See OP for instructions and benefits :D some from thicklizard, Some from Showp1984.. its all the same thing Thanks thick for giving me a good start
-Hotplugging enabled
-Userspace VDD Enabled (IE ThermalD control)
-Fixed sweep2wake so that left->right is on right->left is off
Nov 4 2012 RC6.1
Code:
-Updated source to compile with newest linaro toolchain
-Some Linaro modifications
-Updated voltages back to stock levels
-Removed GPU OC
Nov 10 2012 RC6.2
Code:
-Patched upstream to 3.0.51
-Fixed Framebuffer Overruns
-Fixed Voltages
-Fixed Graphical Glitching
-Fixed OTG support
-Fixed incorrect MDP formats for unpack patterns
-Fixed Race between DBS_Refresh and hotplug
-Made the Scaling_governor sysfs node polable
-Fixed Sysfs Deadlock on Cocurrent hotplug/freq switch
-Forcing use of insecure mode to RIVA (wifi controller to load my modules)
-Powered OTG (thanks koush&thicklizard&ca1ne)
-Built with -O2 flags
-Corrected mdp_iommu
-Enable ALL iommu's
-added a psuedo planar output for interleaved format
Nov 23
Code:
Beastmode-LTE 6.3
-Patched upstream to 3.0.52 - kernel.org
-Altered GPU Clocking/scaling in system
-Changed FSB Clocks increased a bit
-Changed L2 Cache boost stepping
Dec 09
Code:
-Ringbuffer patch to fix graphical slowness / glitching (showp1984)
-Cmdline interface support for max/min screen off clock gpu clock etc all installer controlled - showp
-Completely disabled perflock - Show-p
-Patched upstream to 3.0.56 - Kernel.org
-put together a aroma installer for a user configurable kernel
http://db.tt/BVUbkNXM
from my EVO using xda app-developers app
my voltage levels have been reverted to stock to cut down on problems
Nice to see someone on this. If you need a tester, please let me know.
opps.. still sweet!!!!!! thanks
Macropoutsis said:
Nice to see someone on this. If you need a tester, please let me know.
Click to expand...
Click to collapse
Me too pm me if you need a tester
Sent from my EVO using xda app-developers app
Guys you will have to bear with me ... i write code and deal with some porting here and there but this is the first kernel i have poked at.. any input would be apprecaited
Code:
net/netfilter/xt_mark.c:16:37: error: linux/netfilter/xt_mark.h: No
such file or directory
net/netfilter/xt_mark.c: In function 'mark_tg':
net/netfilter/xt_mark.c:32: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c:32: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c: In function 'mark_mt':
net/netfilter/xt_mark.c:41: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c:41: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c:41: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c: At top level:
net/netfilter/xt_mark.c:49: error: invalid application of 'sizeof' to
incomplete type 'struct xt_mark_tginfo2'
net/netfilter/xt_mark.c:58: error: invalid application of 'sizeof' to
incomplete type 'struct xt_mark_mtinfo1'
make[2]: *** [net/netfilter/xt_mark.o] Error 1
make[1]: *** [net/netfilter] Error 2
make: *** [net] Error 2
think i got it squared away
Unfortunately I've noticed a giant void in kernel devs in this place so far. Maybe they're just hiding... I dunno.
Sent from my EVO using xda app-developers app
PsiPhiDan said:
Unfortunately I've noticed a giant void in kernel devs in this place so far. Maybe they're just hiding... I dunno.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Its not that its just that the Mods shut down any and all talk about Custom Kernels in this place which is counter progressive if you ask me....
Sent from my EVO using xda app-developers app
Zarboz said:
Guys you will have to bear with me ... i write code and deal with some porting here and there but this is the first kernel i have poked at.. any input would be apprecaited
Code:
net/netfilter/xt_mark.c:16:37: error: linux/netfilter/xt_mark.h: No
such file or directory
net/netfilter/xt_mark.c: In function 'mark_tg':
net/netfilter/xt_mark.c:32: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c:32: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c: In function 'mark_mt':
net/netfilter/xt_mark.c:41: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c:41: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c:41: error: dereferencing pointer to incomplete type
net/netfilter/xt_mark.c: At top level:
net/netfilter/xt_mark.c:49: error: invalid application of 'sizeof' to
incomplete type 'struct xt_mark_tginfo2'
net/netfilter/xt_mark.c:58: error: invalid application of 'sizeof' to
incomplete type 'struct xt_mark_mtinfo1'
make[2]: *** [net/netfilter/xt_mark.o] Error 1
make[1]: *** [net/netfilter] Error 2
make: *** [net] Error 2
think i got it squared away
Click to expand...
Click to collapse
I think I'll fork your github and see what I can do, this is based off the lte's official kernel source correct?
Sent from my EVO using Tapatalk 2
DB13 said:
Its not that its just that the Mods shut down any and all talk about Custom Kernels in this place which is counter progressive if you ask me....
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
ughhhh miss informed people dont help anyone in the end, and all they do is make things worse too overall...
We have not shut down talk of any and all custom kernels on here....just one and its owners name...this was the result of an AGREEMENT b/w BOTH sides in the matter as they didn't want their name on this site at all.
If you have any questions on the matter PM me...and in the future if you have a complaint or question about anything going on in here, please feel free to ask any of the mods here...were all pretty open
now lets not derail the OP thread here and see if this can get going...
Can I get in on this? And by that, I mean with helping with the kernel. I'm setting up my workstation right now...unfortunately I'm not rooted so this'll be interesting. Gonna have to trust the gut I guess
Zarboz said:
Currently you will have to download the source and compile it. Use Git to accomplish this as this is my tool of choice. If this is too much for you please google around to figure out how to achieve this it takes about ten minutes. This thread is not to discuss HOW to compile a kernel but to discuss plans mods and implementation into the current tree. I will work on this off and on until I purchase a Evo LTE next month.
Click to expand...
Click to collapse
Really? It takes ten minutes with some googling for someone who has never compiled a kernel to setup a linux install (live disc/usb or not), setup a proper environment with all needed bits and learn how to compile? I would love to see this 10 minute guide you speak of.
I can't tell you enough how much I appreciate what you and devs do, but try to throw us peons a bone! The linux community is the most 'elitist' of them all and it makes it very difficult to start and learn. I'm a pretty sharp guy. I'm in school right now for electrical engineering and have already taken a class in c++ where we had to use linux boxes locally and remotely, but I can't find a single SIMPLE and straightforward guide to setting up a kernel compiling environment. I've found many that LOOK simple, but half of the commands the post to copy and paste don't work because they're too old or for whatever reason and then they completely lose us.
I don't want to make this a thread on how to compile like you said, but throwing a link in the OP would really be appreciated because seeing stuff like this without being able to get the help we need to use it is really REALLY frustrating for us 'lesser' users. Thank you so much.
spankmaster said:
Really? It takes ten minutes with some googling for someone who has never compiled a kernel to setup a linux install (live disc/usb or not), setup a proper environment with all needed bits and learn how to compile? I would love to see this 10 minute guide you speak of.
I can't tell you enough how much I appreciate what you and devs do, but try to throw us peons a bone! The linux community is the most 'elitist' of them all and it makes it very difficult to start and learn. I'm a pretty sharp guy. I'm in school right now for electrical engineering and have already taken a class in c++ where we had to use linux boxes locally and remotely, but I can't find a single SIMPLE and straightforward guide to setting up a kernel compiling environment. I've found many that LOOK simple, but half of the commands the post to copy and paste don't work because they're too old or for whatever reason and then they completely lose us.
I don't want to make this a thread on how to compile like you said, but throwing a link in the OP would really be appreciated because seeing stuff like this without being able to get the help we need to use it is really REALLY frustrating for us 'lesser' users. Thank you so much.
Click to expand...
Click to collapse
This is a little old, but should give you an idea what you would be doing. http://forum.xda-developers.com/showthread.php?t=915435
I could compile it for you but chance are it won't boot with it oc that much.
Sent from my EVO using Tapatalk 2
Thread cleaned, back to the development.
Thank you Haus.. and if u need a guinea pig for some testing
Sent from my Supercharged ELiTE
husker91 said:
I think I'll fork your github and see what I can do, this is based off the lte's official kernel source correct?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
sgt. slaughter said:
ughhhh miss informed people dont help anyone in the end, and all they do is make things worse too overall...
We have not shut down talk of any and all custom kernels on here....just one and its owners name...this was the result of an AGREEMENT b/w BOTH sides in the matter as they didn't want their name on this site at all.
If you have any questions on the matter PM me...and in the future if you have a complaint or question about anything going on in here, please feel free to ask any of the mods here...were all pretty open
now lets not derail the OP thread here and see if this can get going...
Click to expand...
Click to collapse
ms79723 said:
Can I get in on this? And by that, I mean with helping with the kernel. I'm setting up my workstation right now...unfortunately I'm not rooted so this'll be interesting. Gonna have to trust the gut I guess
Click to expand...
Click to collapse
thicklizard said:
I could compile it for you but chance are it won't boot with it oc that much.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
\
i got nettables fixed im pushing now
having a issue with the keyboard compilation .. stupid because the keyboard doesnt exist on this unit..
have pushed the changes to my GIT
the git is based off HTCs official source and has some mods to it
i have posted source because obviously we have not got a product as of yet..
i am working on getting in touch with the creator of sweep2wake to include it in this code for you guys as i think its a neat feature
i really appreciate the input.. i was going to play some diablo 3 today but i think ill work some more thanks guys
thicklizard said:
I could compile it for you but chance are it won't boot with it oc that much.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
the OC itself just has a roof of 2.13ghz
that high of a table is reported working on other krait boards (one XL etc..) so i figured it was worth a shot
i still have another set of tables at 1.83 ghz as well we can try
this is the error
http://pastebin.com/k36t3yaT
Code:
/home/zardoz/jewel/jewel/scripts/gcc-wrapper.py /home/zardoz/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-gcc -Wp,-MD,drivers/input/keyboard/.atkbd.o.d -nostdinc -isystem /home/zardoz/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/../lib/gcc/arm-eabi/4.4.3/include -I/home/zardoz/jewel/jewel/arch/arm/include -Iarch/arm/include/generated -Iinclude -include include/generated/autoconf.h -D__KERNEL__ -mlittle-endian -Iarch/arm/mach-msm/include -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Werror-implicit-function-declaration -Wno-format-security -fno-delete-null-pointer-checks -Os -marm -fno-dwarf2-cfi-asm -fstack-protector -mabi=aapcs-linux -mno-thumb-interwork -funwind-tables -D__LINUX_ARM_ARCH__=7 -march=armv7-a -msoft-float -Uarm -Wframe-larger-than=1024 -fomit-frame-pointer -g -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow -fconserve-stack -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(atkbd)" -D"KBUILD_MODNAME=KBUILD_STR(atkbd)" -c -o drivers/input/keyboard/.tmp_atkbd.o drivers/input/keyboard/atkbd.c
_motley kernel for the Nexus 4
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!
Features
Highly customizable with scripts. See post #2 for all the tuning options.
Google 3.4 base. All stock features are of course supported (camera, NFC etc.)
Compiler optimizations (-O2 + others) - using 2012.12 Linaro toolchain
Full ramdisk install with init.d support for stock/AOSP (CM already has support, for stock you must install busybox!)
CPU Overclock steps 1.56, 1.62, and 1.67GHz (default freq is still stock on boot, OC is optional)
304MHz lowest CPU freq step added with lower voltage than stock, since the device spends a lot of time at this frequency.
Safe UV by default for nominal, fast, and faster binned chips.
Voltage control - be careful to not save the setting on boot until you are 100% sure it is stable! (thanks faux123! + my tweaks)
In-kernel auto_hotplug (thanks to thalamus). I have added and exposed all the tuning parameters and a debug mode to userspace.
Customized in-kernel thermal solution smart scaling, dynamic polling, and configurable throttle temp.
Custom PowerHAL module (spam-free Android log from PowerHAL events)
Controllable touchboost frequency and duration
Gamma and Sound control (thanks faux123!)
Fsync control (3 modes)
USB Force Fast Charge
I/O schedulers - SIO(optimized), deadline (optimized), row, cfq, noop, and fiops
TCP Congestion Control (several choices available) - veno is the default
Governors - Interactive (default), OnDemand, PowerSave, Conservative
CIFS, NFS, NTFS r/w, TUN - built-in, no need for any kernel modules
Other misc patches and tweaks (see github link at the bottom of this post)
GPL compliant - source is kept up to date at github.com and released at the time the kernel is released to the public via this post. Demand that other devs do the same!
Requirements (please read carefully and visit the other dev threads as necessary)
Boot-loader must be unlocked and you must have a custom recovery installed (CWM or TWRP).
Have your ROM zip on your /sdcard so you can restore your whole ROM if necessary.
Do a complete backup using custom recovery so you can restore your boot.img and ROM if necessary!
System Tuner is recommended for monitoring/tuning the CPU, especially for voltage control. Other kernel apps like faux123's will likely work as well, but they have not been tested.
AOSP ROMs including stock - for init.d support, you must have a working busybox install in /system/xbin.
Installation
Check the requirements above and read release notes below for the build # you are installing for any extra instructions!
If coming from another kernel, read the instructions in red below and follow them before flashing.
Flash the the kernel zip using your custom recovery.
Optional: if you want to revert back to what you had, restore your backup of your boot.img in recovery. Another option for reset back to stock is to flash the stock reset zip above. For other custom ROMs, dirty flash your custom ROM in recovery to get your default kernel and ramdisk back.
If you have issues and are coming from another custom kernel or ROM, follow these instructions first before the install. Many custom kernels are changing the ramdisk or other binaries that require a reset before moving back to stock or another kernel.
Reset for Stock ROM - flash this reset package that includes the stock kernel, ramdisk, thermald, mpdecision, and PowerHAL binary. This can also be used if you are using the stock ROM and want to go back to stock.
4.2.1 View attachment N4_421_stock_kernel_and_components.zip
4.2.2 View attachment N4_422_stock_kernel_and_components.zip
Reset for any non-stock ROMs like CM, AOKP etc - dirty flash your current ROM or nightly zip then your gapps in recovery (just flash, no wiping). This will give you back your original ramdisk, kernel, and other binaries that other kernel devs may have tweaked, renamed, replaced etc.
Builds
Build 49 - 2013-03-10 (stable) - Android 4.2.2
Added faux123's "Sound Control: Sound control for WCD93xx codec" for testing (thanks!)
AnyKernel UPDATE ONLY - must already be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_49.zip
Build 48 - 2013-03-09 (stable) - Android 4.2.2
Turned off touchscreen accuracy filter by default and allow users to turn them on via the same interface (see git for all the details). In the commit comments on github, I also document how the stock kernel already allows these adjustments, but now we have easier control of them individually. Let me know if this fixes issues for those having them.
Reverted back the changes for notification delays. They didn't fix anything. If you swapped out your prime WiFi INI file, I recommend changing back to stock for now.
AnyKernel UPDATE ONLY - must already be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_48.zip
Build 44 - 2013-03-04 (beta) - Android 4.2.2
Updated touchscreen Accuracy Filter Control with franco's cleanup patch. Reverting back to a single threaded workqueue should hopefully help fix the touchscreen issues some reported.
Per Google's kernel devs, we should not have CONFIG_NF_CONNTRACK_SIP/CONFIG_NF_NAT_SIP turned on in the config. Testing is under way (introduced in b43 posted in the thread).
AnyKernel UPDATE ONLY - must already be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_44.zip
Build 42 - 2013-03-02 (beta) - Android 4.2.2
Added faux123 Speaker Amp Control by request for testing (thx!)
Added franciscofranco touchscreen Accuracy Filter Control by request for testing (thx!)
Reverted "Mako Gamma: allow values greater than 31 for array positions 5 and 6". Brought to faux's attention and his app is now fixed, so this is no longer needed. Values should be capped at 31 like we have always known.
AnyKernel UPDATE ONLY - must already be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_42.zip
Build 40 - 2013-02-25 (stable) - Android 4.2.2
Added upstream smp patches from 4.2.1 back into 4.2.2 build
Added optimized ARM RWSEM algorithm backin into 4.2.2 build
AnyKernel UPDATE ONLY - must be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_40.zip
Build 39 - 2013-02-20 (stable) - Android 4.2.2
Added usb/hsic patches into 4.2.2 build
Turned off prima debugging in 4.2.2 build
AnyKernel UPDATE ONLY - must be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_39.zip
Build 38 - 2013-02-17 (stable) - Android 4.2.2
Loosen up validation for gamma interface to allow values greater than 31 for array positions 5 and 6.
AnyKernel UPDATE ONLY - must be on b37 or higher first! Anykernel is the same for both Stock/AOSP and CM 10.1
View attachment motley_anykernel_422_nexus_4_build_38.zip
Build 37 - 2013-02-17 (stable) - First build with 4.2.2 support added
4.2.2 - rebased upon android-msm-mako-3.4-jb-mr1.1, ramdisk updated etc.
All major features added back in, but I have left a few patches out (hsic etc.) so we can evaluate before adding them back in.
Back to b32 colors, from here out you are on your own using the gamma interface of choice.
Fixed issue where fsync was still on like in previous builds. Dynamic fsync is now the default (see post 2)
Added franco gamma interface, so the kernel can support all popular interfaces until/if a standard interface is adopted.
Added refresh_screen sysfs (see post 2). This should only be called by apps or scripts while adjusting colors "live" with the motley or faux interface and NOT implemented on startup via init.d or apps since it will compete with the normal power on process and the colors will be set twice.
Use a 4.2.2 ROM and binaries. I will not troubleshoot any issues if you use this on 4.2.1 ROMs and binaries
Stock/AOSP with init.d support: View attachment motley_422_n4_exp_build_37_initd.zip
-or-
CM 10.1: View attachment motley_422_build_37_CM.zip
Previous builds and release notes:
Exp build 35 - 2013-02-11 (stable) - Last build for 4.2.1 for now
New default gamma values (this is an experiment, so let's see how everyone likes it)
cifs support for 4.2 (no modules required) - make sure you pass unc=\\\\server_name\\share_name as a mount option, or it will not work. It is a problem in the mainline kernel for 3.4 where they seem to have accidentally made the unc option mandatory. Also, no promises that the mount will be solid after the device sleeps. For now, I suggest you unmount after you are done using the file system unless we find a workaround. I have tested with cifsmanager from the app store. Other apps may or may not work.
Vibrator default is now 80 in init.mako.rc. This thing was anemic and it was about time.
FIOPS io scheduler added for testing by request
Applied several kernel\sched patches
auto_hotplug tweaks, nothing major.
Added dynamic fsync (thanks faux123) - I will update post 2 with the 3 different FSYNC options. Both toggles were left in the kernel since they are both available in different apps. If someone liked it the way it was, I didn't want to take that away.
Stock/AOSP with init.d support: View attachment motley_n4_exp_build_35_initd.zip
-or-
CM 10.1: View attachment motley_exp_build_35_CM.zip
Exp build 32 - 2013-02-03 (stable)
Merged Google's latest kernel patches for off-mode charging (from android-msm-mako-3.4-jb-mr1)
Interactive governor default tweaks - seems to give better user experience in testing thus far.
One other patch from Google's common 3.4 repo (sync: Fix race condition between merge and signal)
AnyKernel UPDATE ONLY - You must already be on exp b31. If not flash that first, then flash this. This works for both Stock/AOSP and CM
View attachment motley_anykernel_nexus_4_EXP_build_32.zip
Exp build 31 - 2013-01-28 (stable)
Added support for generic gamma control via sysfs with scripts (will update post #2 with details and examples). Again, thanks to faux123 for sharing his code.
Back on Linaro toolchain. Touch Control (PGM) support is still working fine.
TCP Congestion Control default changed to "veno" to see if it helps achieve faster speeds for some. Also added cubic, bic, illinois, and yeah for testing. Westwood+, reno, and vegas still available.
Stock/AOSP with init.d support: View attachment motley_n4_exp_build_31_initd.zip
-or-
CM 10.1: View attachment motley_exp_build_31_CM.zip
-or-
AnyKernel UPDATE ONLY - If you already on this kernel exp b17 or higher. For both Stock/AOSP and CM (keep this around for those who may want it for some reason)
View attachment motley_anykernel_nexus_4_EXP_build_31.zip
Exp build 28 update - 2013-01-24 (alpha 3)
Added support for gamma control (thanks to faux123, the faux123 app is required). Will likely provide something more generic in the future for tuning via sysfs without a 3rd party app.
Added some modest CPU OC steps of 1.56, 1.62, and 1.67GHz (voltages are scaled by bin but might not yet be optimal as the defaults). It still boots to the stock 1.5GHz, so it won't affect those that don't want to OC.
Giving the Google 4.7 toolchain a try. This base will give Touch Control a chance to work when the dev has a change to take a look. I am also inquiring to see if he thinks we can give Linaro a try. Google has made a lot of strides in this latest version, but I don't think it is yet on par with Linaro. I may do another alpha build with Linaro so we can compare. Perhaps I don't have the proper optimizations in place. we will see where this goes.
Thermal throttling improvements (new tuneable "min_freq_index" - what freq does it throttle down to before returning to max?)(default = 7 = 1.13GHz). This is the index in the frequency table as seen in Trickster MOD, System Tuner etc. It is zero based (i.e. 304MHz is zero). Several other changes, see my git commits for details.
Touch Control (PGM) support now available (thanks to bponury for his support!)
AnyKernel UPDATE ONLY - If you are not on b17 or higher already, flash build 17 first (Stock/AOSP or CM), then flash the AnyKernel zip for both Stock/AOSP and CM
Exp build 22 update - 2013-01-19 (stable)
Added hsic/usb patches (thanks to code aurora, harsh, thracemerin, and all the other kernel devs that helped with testing and troubleshooting)
See this post for some more info and why it was first released. It is now considered beta and not alpha.
AnyKernel UPDATE ONLY - If you are not on it already, flash build 17 first (Stock/AOSP or CM), then flash the AnyKernel zip for both Stock/AOSP and CM
motley_anykernel_nexus_4_EXP_build_22.zip
Exp build 21 update - 2013-01-19 (stable)
I am hoping this has us back to the b12 smoothness and we have settled in on some good defaults for moving forward.
Upgraded prima WLAN driver to 3.2.1.13 (connected to 3 different WiFi networks yesterday and it is working flawless for me)
Interactive gov tweaks based upon testing and feedback (boostpulse freq is now stock)
Default throttle temp now 67C
Other minor patches: auto_hotplug kick start on resume, update L2 voltage table, etc. (see github)
AnyKernel UPDATE ONLY - If you are not on it already, flash build 17 first (Stock/AOSP or CM), then flash the AnyKernel zip for both Stock/AOSP and CM
View attachment motley_anykernel_nexus_4_EXP_build_21.zip
Exp build 17 - 2013-01-16 (stable)
Back to new 3.4 Google interactive governor base like in b12
PowerHAL and boostpulse setup from b12 is also back. Touchboost default settings have been tweaked based on user feedback (how long does it boost? boostpulse_duration, what freq to boost to? hispeed_freq). If you want to use OnDemand, or don't want any touchboost, then you can flash the "inert" PowerHAL at the bottom of this post.
auto_hotplug enhancements rev 3 (see github) - I will update post #2 as soon as I can. We now have control over how many cpu cores you want online (for battery or performance). Thanks to mathkid for the min_online_cpus commit. It gave me the idea for max_online_cpus.
Back to the partial mako display partial revert by popular demand. My RBG tweak was reverted back to stock (255,255,255). Remember, the RGB can be changed in this kernel and it will persist after screen off/on without an app (see post #2). Trickster MOD can be used to tweak RGB.
OnDemand gov - latest patches from Code Aurora.
Note: Make sure you test with out of the box voltages, especially in the mid-range! There is already a healthy amount of under-volting in this kernel for all binned chips except "slow".
Stock/AOSP with init.d support: View attachment 1651464
-or-
CM 10.1: View attachment 1651468
Exp build 14 - 2013-01-14 (beta)
Reverted back to stock interactive governor base.
Added touchboost changes into stock interactive gov base and tweaked touchboost default settings based on user feedback.
Reverted back to b10 inert PowerHAL (same a separate flash I provided for b12 for those having issues)
Reverted one other scheduler patch that I thought could be playing a role in the reboot. I also didn't think it showed benefits after testing.
Notes: you can control touchboost using the interactive gov (turn off/on touchboost: input_boost, length of boost pulse: above_hispeed_delay, freq to boost to: hispeed_freq)
Stock/AOSP with init.d support: View attachment 1645970
-or-
CM 10.1: View attachment 1645993
Exp build 12 - 2013-01-13 (beta)
Touchboost control - connected custom Android PowerHAL module with interactive touchboost. Then, I married interactive touchboost with autoplug touchboost. If you want to tune tune interactive governor touchboost differently, you can use sysfs scripts, Trickster MOD or other capable apps (how long does it boost? boostpulse_duration, what freq to boost to? hispeed_freq)
Added touchscreen patch (thanks faux123) - seems to make the touchscreen more usable and responsive in my testing.
autoplug enhancements rev 2 - added ability to change # of sampling_periods on the fly using a module parameter (whilst preserving past history). Added get/set methods for all module parameters to make them safe. See github for all the details.
Added "row io scheduler by request - SIO is still the default for now.
Some other misc patches
Stock/AOSP with init.d support: View attachment 1641515
-or-
CM 10.1: View attachment 1641518
Exp build 10 - 2012-12-30 (stable)
Important: Since freqs have been added at the high end below 1.5GHz for smoother scaling, if you use voltage control make sure voltage data is not applied on start-up since you won't have the values for the new freqs.
Userspace tuning for thermal and hotplug (see post 2 for details shortly)
Enhanced thermal throttling and frequency scaling (see github commits for details, too many changes to list here)
Merged Code Aurora HSIC patches that hopefully will reduce duration of the infamous wakelock (and revert of prior trial workaround)
Added optimized ARM RWSEM algorithm
SMP patches from 3.5 that address hotplug efficiency and lay the foundation for other future patches I am studying.
Some other minor patches and changes (see github)
Stock/AOSP with init.d support: View attachment 1604553
-or-
CM 10.1: View attachment 1604557
Exp build 8 - initial release
Same base features as build 57 mainline
ARM auto hotplug v0.220 by _thalamus
Custom PowerHAL (chatter-free Android log)
Interactive (default) - with input boost
MSM-thermal in-kernel solution
thermald and mpdecision are disabled (services are not started in the ramdisk)
Inert PowerHAL library
This is a shell PowerHAL library that allows Android to function and stops the input boostpulse requests
(same as included in b8 and b10 Exp kernels).It was originally released for testing b12, but can be used in other builds. Personally, I would only flash the "inert PowerHAL" if you are using OnDemand full-time and no longer using interactive (set on boot), OR if you are using interactive and want to completely remove the boostpulse requests coming from Android. In the later case, UI performance may be sacrificed a bit for better battery.
View attachment motley_inert_powerhal.zip
Mirror site - thanks tlongren! - will typically be updated within a day after I post
http://www.longren.org/nexus4/motley
Git repo:
https://github.com/motley-git/kernel-Nexus4
{
"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)
Setting custom RGB color settings via sysfs
This can be done from the adb shell on your PC, or any terminal app. If you change them, they will not persist after a reboot. However, you can set them in an init.d script if you found another color combination that you like better than the one I have used.
Code:
echo "255 255 255" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
Command 1 sets the color and Command 2 commits them. Stock is 255 255 255.
Setting custom Gamma settings via sysfs - Exp kernel build 31+ only - thanks to faux for sharing his code
Warning: changing these values can be potentially be dangerous to your display if you make a mistake. For those that feel comfortable with what they are doing and want to experiment, please report back and share your findings.
Important, please read!
There are ten digits in the string separated by one space
First digit is a checksum and is never stored. The checksum is simply the sum of the other 9 numbers. This is to make it harder to so the interface is respected and you are forced to think about what you are doing.
There are 3 sysfs interfaces for gamma, one for each color:
Code:
#!/system/bin/sh
# Show the current configuration and the checksum
cat /sys/devices/platform/mipi_lgit.1537/kgamma_red
cat /sys/devices/platform/mipi_lgit.1537/kgamma_green
cat /sys/devices/platform/mipi_lgit.1537/kgamma_blue
Update:
Recently molesarecoming started opening this up and showing us what the values can be used to adjust. Franco then suggested that the white and grays should be swapped in moles original work. So, for init.d values using this interface, we have the following "banks" if values if we agree with Franco on the swap of the whites and grays.
Code:
R: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
G: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
B: checksum, g_white, g_mids, g_black, 0, g_contrast, g_brightness, g_saturation, g_grey, 2
(the zero in position 5's and the 2's in position 10 are recommended to be left alone since they are currently unknowns)
Minus the checksum, the 27 values mirror the 3 color arrays (3 x 9 = 27) in the actual LG LCD driver. Minus the unknowns, we are left with 21 values. Note that every one of the variables can have their value tweaked by color (saturation for red, saturation for green etc.), however, it is recommended that you start with all the values of one type being the same and then tweak from there if you really want to fine tune.
You have a lot of power in your hands even without fine tuning. Many will argue that fine tuning isn't required. If you look at the stock settings by Google in post 2, they took advantage of fine tuning for whatever reason. Even though many don't like these settings by Google, it shows how flexible the interface can be.
Instructions:
1) Start with a preset config (LG or Google) as shown further below. This is a set of 3 lines, 10 numbers for each line.
2) Tweak columns for their values as above. For example, we tweak contrast and brightness as in faux's original app. We could also do the same for saturation, blacks, whites, grays etc.
Example: start with LG presets with numbers to adjust:
383 114 21 118 0 10 4 80 48 2
383 114 21 118 0 7 4 80 48 2
383 114 21 118 0 5 1 80 48 2
3) Now update the checksum in column 1 (first digit = sum of last 9 digits)
397 114 21 118 0 10 4 80 48 2
394 114 21 118 0 7 4 80 48 2
389 114 21 118 0 5 1 80 48 2
4) Create a script inside a text file - my recommendation for your first test
Code:
#!/system/bin/sh
# Set data color pro presets from shared Google spreadsheet (thanks user acer73!)
# Use LG presents as your starting values and then adjust columns 6 & 7 from the spreadsheet
echo "397 114 21 118 0 10 4 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "394 114 21 118 0 7 4 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "389 114 21 118 0 5 1 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
#Set the complimentary RGB values for this calibration
echo "248 248 248" > /sys/devices/platform/kcal_ctrl.0/kcal
echo 1 > /sys/devices/platform/kcal_ctrl.0/kcal_ctrl
5) Run the script (or you can echo each line manually to test from adb if you prefer).
6) Turn the screen off and on for the gamma change to take effect.
7) Check the dmesg output for any clues and to see the output of the result.
8) Place the script into your /system/etc/init.d/ folder (or equivalent) for a permanent color change!
Screen refresh (added in b37) - this should only be called by apps or scripts while adjusting and testing colors "live" with the motley or faux sysfs interface. It should NOT be implemented on startup via init.d or by apps since it will compete with the normal power on process.
Code:
echo 1 > /sys/devices/platform/mipi_lgit.1537/refresh_screen
Presets:
Code:
#!/system/bin/sh
# Set LG presets (motley stock) - i.e. popular partial revert of Google's tweaks just before release
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "383 114 21 118 0 0 0 80 48 2" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
Code:
#!/system/bin/sh
# Set stock Google presets (from kernel source code)
echo "332 64 68 118 1 0 0 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "332 64 68 118 1 0 0 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "364 32 35 116 0 31 16 80 51 3" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
Code:
#!/system/bin/sh
# Set faux Google presets (not sure why his numbers differ)
echo "460 64 68 118 1 32 96 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_red
echo "461 64 68 118 1 33 96 48 32 1" > /sys/devices/platform/mipi_lgit.1537/kgamma_green
echo "445 32 35 116 0 32 96 80 51 3" > /sys/devices/platform/mipi_lgit.1537/kgamma_blue
Spreadsheet with shared settings
https://docs.google.com/spreadsheet/ccc?key=0AoDp2qRui0u0dGE4T2gtSDBTRHVFSldPS2RrX1Rya0E#gid=0
FSYNC Control
Notes: I thought about combining these options, but many kernel apps already support these two options. So, I have them both and they can be controlled in combination to give us the 3 modes. If you set fsync_enabled = 0 it will be OFF regardless of how Dyn_fsync_active is set.
3 Modes:
Dynamic (default in b35 and higher)- fsync is asynchronous when screen is on, when screen is off it is committed synchronously
dynamic fsync ON
fsync ON
Code:
echo 1 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
Off (best performance, less safe) - fsync is always asynchronous (b32 and prior builds)
dynamic fsync OFF
fsync OFF
Code:
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 0 > /sys/class/misc/fsynccontrol/fsync_enabled
Stock (safest) - fsync is always committed synchronously
dynamic fsync OFF
fsync ON
Code:
echo 0 > /sys/kernel/dyn_fsync/Dyn_fsync_active
echo 1 > /sys/class/misc/fsynccontrol/fsync_enabled
There is a lot of info out there on fsync, that will not be discussed here. I have run fsync off on several devices for awhile now and haven't experienced any issues. If you are using a device that is not stable and crashes alot, I recommend enabling it via init.d or script manager on boot. Hopefully your N4 is as stable as is mine.
USB Force Fast Charge
You can turn it on with popular apps (like Trickster MOD) that support the common sysfs toggle as shown below.
If you don't like it or don't want to use it, it is off by default.
Turn ON:
Code:
echo 1 > /sys/kernel/fast_charge/force_fast_charge
Turn OFF:
Code:
echo 0 > /sys/kernel/fast_charge/force_fast_charge
Notes:
When it is ON, you will not be able to connect your phone to your PC (adb, mtp etc.). This is expected behavior.
To start charging: turn fast charge ON, plug the USB cable into your PC, and charge up.
To stop charging: unplug the USB cable and turn fast charge OFF. Now you can plug back into your PC for normal trickle charging, adb/mtp etc.
Tip: if you see it connect to your PC (media device or adb), it isn't working. Unplug the cable, wait a couple seconds and plug it in again.
Boostpulse control - Experimental build only
Trickster MOD works great to play with these.
How long does it boost when Android senses touch? (in b10 and b14 it is above_hispeed_delay)
Code:
/sys/devices/system/cpu/cpufreq/interactive/boostpulse_duration
What freq does it boost to?
Code:
/sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
Turn touchboost OFF/ON (in b10 and b14 only)
Code:
/sys/devices/system/cpu/cpufreq/interactive/input_boost
Thermal Throttling and Hotplug Control - Experimental build only
Warning: these do not have to be changed from the defaults and could potentially be dangerous if you make a mistake. For those that know what they are doing and want to experiment with settings, scripts etc. please report back your findings.
msm_thermal:
Throttle temp in C. Default is 70, valid range is 45 to 80 (recommend to not go over 75):
Code:
/sys/module/msm_thermal/parameters/throttle_temp
Minimum freq used in throttle down before returning to max, default is 7 = 1.13GHz. Range is 4 to 8 (810Mhz to 1.24GHz)
This is the index in the frequency table as seen in Trickster MOD, System Tuner etc. It is zero based (i.e. 304MHz is zero).
Code:
/sys/module/msm_thermal/parameters/min_freq_index
Turn on thermal debugging so you can see what is happening in the kernel log:
Code:
/sys/module/msm_thermal/parameters/thermal_debug
auto_hotplug:
Load based hotplugging parameters. I have taken _thalamus' base (thanks!) and have exposed most of the tuning parameters to userspace.
Turn off/on hot_plug debugging Y/N, default N, this spams the kernel log like crazy, turn on only when troubleshooting/testing
Code:
/sys/module/auto_hotplug/parameters/debug
Load at which a CPU is taken offline, 40-125, default 80:
Code:
/sys/module/auto_hotplug/parameters/disable_load_threshold
Load at which an extra CPU is put online, 130-250, default 200:
Code:
/sys/module/auto_hotplug/parameters/enable_load_threshold
Load at which all CPU's are enabled, 270-550, default is 400 (or 100 x number of cores):
Code:
/sys/module/auto_hotplug/parameters/enable_all_load_threshold
Sample rate in milliseconds, converted to jiffies at runtime, 10-50ms, default 20:
Code:
/sys/module/auto_hotplug/parameters/min_sampling_rate
Number of samples in the circular buffer, 5-50, default 10 (more samples = less aggressive; less samples = more aggressive):
Code:
/sys/module/auto_hotplug/parameters/sampling_periods
Maximum number of cores online (regardless of load) when screen is on, 1-4, default 4 (tune down for battery savings):
Code:
/sys/module/auto_hotplug/parameters/max_online_cpus
Minimum number of cores online (regardless of load) when screen is on, 1-4, default 1 (tune up for performance/bench-marking):
Code:
/sys/module/auto_hotplug/parameters/min_online_cpus
Vibration Intensity
You can also use Trickster MOD to set this.
Example increase intensity:
Code:
echo "90" > /sys/class/timed_output/vibrator/amp
To go back to stock:
Code:
echo "70" > /sys/class/timed_output/vibrator/amp
Why are the base voltage tables different on some phones
What CPU do you have? Nominal, Fast, Faster ...or Slow
The phones with the lower default voltage values use the "fast" or "faster" frequency table, consider yourself lucky. This explains why some can't UV as much as others since they are starting with lower mV's to start. These are built in factory tolerances that depend upon the binning of your chip. I am familiar with the same thing in the tegra3 world where I have had more experience. So, don't worry as this is commonly done in this industry. Hopefully folks don't go freaking out because they have a nominal chip like I do. It's probably good for a dev to have a nominal chip so we can better honor the limits.
http://en.wikipedia.org/wiki/Product_binning
How do I tell what I have?
If you boot up your phone fresh and look at the dmesg output (kernel log) while the messages are still there, you will find one of the following output messages where it selects it's frequency plan depending on the binning of the chip.
Code:
adb shell dmesg | grep PVS
acpuclk-8064 acpuclk-8064: ACPU PVS: Nominal
-or-
acpuclk-8064 acpuclk-8064: ACPU PVS: Fast
-or-
acpuclk-8064 acpuclk-8064: ACPU PVS: Faster
-or-
acpuclk-8064 acpuclk-8064: ACPU PVS: Slow
I have tweaked all the frequency tables nominal, fast, and faster (as well as slow to compensate for the lower freq) to keep them similarly scaled relative to stock. If you don't like the safe defaults (already UV'ed), then use voltage control and come up with your own preferred values.
SWEET!
Sweetness! New kernel!
Sent from my Galaxy Nexus using Tapatalk 2
I definitely giving this s try out.
Thanks for your work.
Sent from my Nexus 4 using xda premium
On my phone the zip is showing duplicate files inside?
Sent from my Nexus 4 using Tapatalk 2
stormtroopercs said:
On my phone the zip is showing duplicate files inside?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
File looks fine on a computer.
stormtroopercs said:
On my phone the zip is showing duplicate files inside?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
hol17 said:
File looks fine on a computer.
Click to expand...
Click to collapse
That is odd. I just looked at it on my phone with ES zip viewer and it looks fine. Also looks good in Linux and flashes fine using CWM touch. Does Root Explorer officially support JB4.2?
I've just added this kernel to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
KidCarter93 said:
I've just added this kernel to the Nexus 4 Complete Index
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Thx, appreciate it!
Nice work motley. I'm not an overclocker so I'll probably be running this often. Can you look at tweaking the voltage table a bit, 800 mV is not low enough. I think the lower steps will be able to go as low as 600 stable. Just a thought. Thanks for your work.
Sent from my Nexus 4 using xda premium
_motley said:
That is odd. I just looked at it on my phone with ES zip viewer and it looks fine. Also looks good in Linux and flashes fine using CWM touch. Does Root Explorer officially support JB4.2?
Click to expand...
Click to collapse
No idea but it flashed correctly! Good job!
Sent from my Nexus 4 using Tapatalk 2
Running great on the latest Xylon build .. Thanks
Sent from my Nexus 7 using Tapatalk 2
mikeyinid said:
Nice work motley. I'm not an overclocker so I'll probably be running this often. Can you look at tweaking the voltage table a bit, 800 mV is not low enough. I think the lower steps will be able to go as low as 600 stable. Just a thought. Thanks for your work.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thx, definitely will try to push it down for us so we can test it out what works best. Heading to bed now, but should be able to do some tweaks tomorrow and over the weekend.
stormtroopercs said:
No idea but it flashed correctly! Good job!
Click to expand...
Click to collapse
joshnichols189 said:
Running great on the latest Xylon build .. Thanks
Click to expand...
Click to collapse
Awesome, thanks for the quick feedback guys!
Wooow linaro!!! Amazing!!!!
Enviado desde mi Nexus 4 usando Tapatalk 2
mikeyinid said:
Nice work motley. I'm not an overclocker so I'll probably be running this often. Can you look at tweaking the voltage table a bit, 800 mV is not low enough. I think the lower steps will be able to go as low as 600 stable. Just a thought. Thanks for your work.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I noticed that Faux kernel's minimum is also 800mv. I wonder if this is some hard coded limit or something
Sent from my Nexus 4 using xda app-developers app
Glad to see you here motley! Your N7 kernel is legendary.... Can't wait to use this!
Sent from my Nexus 4 using Tapatalk 2
Logi_Ca1 said:
I noticed that Faux kernel's minimum is also 800mv. I wonder if this is some hard coded limit or something
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I don't think it's a limit, as such, I think that's the lower they know is definitely stable at the moment.
As motley said, he'll do some more testing when he's got time, so he'll be able to know for sure if lower would still be stable.
Sent from my GT-I9100 using xda premium
Usb otg work with this kernel?
Sent from my MyTouch 4G using Tapatalk 2
pnut22r said:
Usb otg work with this kernel?
Sent from my MyTouch 4G using Tapatalk 2
Click to expand...
Click to collapse
Features
304MHz lowest CPU freq step added with lower voltage than stock, since the device spends a lot of time at this frequency. 432 MHz removed since it doesn't seem to use it much.
Google 3.4 base. All stock features are of course supported (camera, OTG, NFC etc.)
Fsync disabled by default for performance and battery saving - enable/disable switch is available if you want to turn back on (see below).
Voltage control (thanks faux123!) - be careful to not save the setting on boot until you are 100% sure!
Compiler optimizations (-O2) - using 2012.10.22 Linaro 4.7.1 ARM toolchain
I/O schedulers - SIO(default), deadline (optimized), cfq, noop
Governors - OnDemand (stock ramdisk will set on boot), Interactive (my favorite, responsive + good standby battery usage), PowerSave, Conservative
CIFS, NFS, NTFS r/w, TUN - built-in, no need for any kernel modules
Increased mm read-ahead buffer to 1024
XZ compression
GPL compliant - source is kept up to date at github.com and released at the time the kernel is released to the public via this post. See github link at the bottom of this post.
Other misc patches and tweaks (see github)
Info & Thanks
What you need to know before you use this kernel.
This kernel got Selinux Permissive state as it supports more apps like TiTaniumbackup.
Reverting back to a Selinux enforced Kernel (stock) is no longer a problem from Rev3.0 and up.
You can set Selinux Status with the included Synapse app
You want to know why this kernel comes with Selinux included, google for Selinux and search your answers.
AllCast mirror will not work as this is a Samsung thing and not opensource.
If this is a problem for you, don't use this kernel.
DISCONTINUED , A NEW THREAD WILL BE OPENED FOR THE NEW KERNEL SUPPORTING ONLY THE KITKAT BOOTLOADER.
NO JELLYBEAN BOOLTOADER SUPPORT, IT IS TIME TO MOVE FORWARD.
INSTALLATION
Take a full nandroid backup.
NO NEED TO BE ON ANY KITKAT BOOTLOADER (your wifi will work with this kernel)
YOU NEED TO BE ON A KITKAT TOUCHWIZ ROM.
Install with cwm
Thanks:
sidmoraes for pointing me to other kernel source that I could use as base, still had to change some stuff but this is better then waiting for samsung to release there source, if they ever will. (Finally Samsung released source)
Andreilux - Faux123 - Yank555.lu for kernel work
ZaneZam for the zzmoove governor
{
"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"
}
This kernel comes with the policy: IT IS AS IT IS.Use at your own risk
Take a Nandroid backup of your system and of your boot.img
You need to be on custom cwm to install this
ONLY FOR SAMSUNG TOUCHWIZ BASED KITKAT ROMS
Benchmark scores:
Stock Normal Note8.0 Antutu Ranking. 17708 points
My Antutu = 23486 points
Stock Quadrant ranking = 6613 points
My Quadrant = 13685 points
CivZ-SphereKat-REV5.4-GT-N5110-5100/5120 And older versions.
Never install a kernel that is not for your device, it will cause a hard brick.
Stock kernels can be found in the SphereKat folder of your device
The only good app to control this Kernel is the included SYNAPSE appExample of what synapse looks like,THIS IS JUST A EXAMPLE.
SphereEngine KERNEL Features
If you change nothing these are the following Features/optimisations you get compared to Stock:
SELINUX protection included but set at Permissive = No problems wit apps like Paragon and Titainium.
SELinux control with Synapse
S-Pen Alignment fixed
Default Speeds 200MHz-1600MHz
Activating Saving power will result into 200MHz-1100MHz.
GPU Overclocking thanks ZaneZam / DerTeufel / AndreiLux
GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel
Init.d support
ARCH-Power enabled
DynamicFSYNC = Use Terminal command or Trickster Mod app. = enabled by default.
Memory Leak fixed
mmc cap erase disabled ( just as a precaution )
[*]IKCONFIG_PROC support
Driver support included in kernel:
NTFS_RW / FAT / FAT32 / EXFAT support
3Gusb Support (ppp widget)
CIFS / UFS / ISO9660 / UDF_FS / HF / HF_PLUS
Realtek RTL8192CU/RTL8188CU USB Wireless Network Adapter support
Ralink driver support : Ralink rt2500 (USB) / Ralink rt2501/rt73 (USB) / Ralink rt27xx/rt28xx/rt30xx(USB)/rt2800usb - Include support for rt33xx , rt35xx , rt53xx
Extra Drivers: MAC80211 / RTL8187 / EEPROM_93cx6 Support
Boeflla 1.6.0 Sound engine support
OTG Audio dock , Car dock support
[*]SideSync support
[*]Dynamic Samsung Hotplugging
Note on CIFS:
Example on what you enter, but your IP and share, if that wasn't clear. The option section is very important
Note on NTFS
You need to use Paragon!
You need to set your mount point yourself.
Example and recommended is:
Code:
/mnt/extSdCard/paragon
Advanced users support
OC & UV support for CPU
Max CPU speed is 1920MHz
Min CPU speed is 100MHz
Governors: Adaptive, Pegasusq (recommended), Performance, Ondemand, Interactive.
Schedulers: cfq, Noop, Deadline, Row, Sio, VR
Extra TCP wifi connection added: Westood, reno, htcp, vegas, veno.
Changelog:
07/Jun/2014 First Public release Rev2.0
08/Jun/2014 First Public release Rev2.1
[*]GPU step 5 included, now max it will go to 533MHz
[*]Auobrightness sensor fixes part2
[*]CPU sloop adjusted
[*]zzmoove profile nr8.
09/Jun/2014 First Public release Rev2.2
[*]Memory Leak fix cpu stats
[*]Memory Leak fix Kernel Ext4 & Power
[*]zzmoove profile nr6.
I recommend not to use Interactive and Powersave governor as they are buggy.
09/Jun/2014 First Public release Rev3.0
[*]Selinux included in the kernel as more security is better. This is the reason why I bumded to Rev3.0 to make a clear difference.
This kernel got Selinux Permissive state as it supports more apps like TiTaniumbackup.
Reverting back to a Selinux enforced Kernel (stock) is no longer a problem from Rev3.0 and up.
You can set Selinux Status with terminal command to ENFORCED with "setenforce 1". Or use a init.d script to have it on reboot also on ENFORCED.
You want to know why this kernel comes with Selinux included, google for Selinux and search your answers.
[*]Governors , powersave, userspace = Disabled as they are useless and buggy.
10/Jun/2014 Rev3.1 Released:
Ramdisk changes
Interactive set on all parameters as startup and default governor, this to prevent lockup of cores on boot.
Synapse SELinux status oprion, change to ENFORCED & PERMISSIVE , default is permissive
Small tweaks in kernel boot_up custom script.
12/Jun/2014 Rev3.2 Released:
Ramdisk changes
CPU freq rework to solve the hotplug problems
zzmoove and interactive removed = I strongly recomment pegasusq
Synapse Global voltage control added and some more info stuff
Github source updated
13/Jun/2014 Rev3.3 Released:
Ramdisk changes
Revert CPU freq rework to solve the hotplug problems
Compiled with Samsun Dynamic Hotplugging to resolve this problem
Synapse GPU info added
15/Jun/2014 Rev3.4 Released:
Bus_freq changes
A ton of missing driver commits for the KONA device added
Autobacklight 0.0 lux light problem fixed, no it works correctly even in a dark room
That is the problem working with a kernel that isn't for this device. You need to debug and add the stuff that is missing.
18/Jun/2014 Rev3.7 Released:
N5100 support added = no testers pm'd me so this is experimental
N5120 support added = no testers pm'd me so this is experimental
Ramdisk changes and github updated
20/Jun/2014 Rev3.8 Released:
Hotplug rework
Ramdisk changes for the s-pen
28/Jun/2014 Rev4.0 - 5110 Released: (support for the 5100 & 5120 will follow later)
Merged with official Samsung KK source = fixes all existing problems with wakelock and many other optimizations for our device
29/Jun/2014 Rev4.0 - support for the 5100 & 5120 added
Merged with official Samsung KK source = fixes all existing problems with wakelock and many other optimizations for our device
Github updated
02/Jul/2014 Rev4.1 - support for the 5110 , 5100 & 5120
Boeffla sound driver updated to 1.66
ZZMOOVE governor reactivated
06/Jul/2014 Rev4.2 - support for the 5110 , 5100 & 5120
Balanced the voltage settings
13/07/2014 Rev4.3 is released
DynamicFsync updated
IntelliHotplug introduced = replacement for the samsung hotplug driver. = Synapse controled
quad core stats for better performance
avg_running time for intelli hotplug support
Synapse settings backup/restore option
I/O advanced settings in Synapse.
Build.prop tweaks in Synapse
Network tweaks in Synapse
...............
15/07/2014 REV4.3_B released
[*]VPN - Reverse path filtering FIX = caused by wrong Synapse settings
[*]Synapse = Network settings changed to solve the vpn problem
16/07/2014 Rev5.0 is released
Dynamic Hotpluging enabled
Update governors
New source 5110NA commits added for the 5120LE
Music skipping problem solved (please use Pegasusq or interactive governor)
SideSync driver added and enabled
Ramdisk removed hotplug locks
Compiled on new toolchain arm-2010q1 from "code sourcery" as suggested by Samsung for the Note8.0 KitKat
...............
17/07/2014 Rev5.1 is released
Different setting for Dynamic Hotpluging, less agressive
Frandom added and enabled
CPU slope changed like on the JB kernel
Dirty writeback
Various performance tweaks
Toolchain arm-2010q1 from "code sourcery" uploaded for the people that want to compile it with this toolchain (look in the kernel folder) as suggested by Samsung for the Note8.0 KitKat
Github updated to Rev5.1
...............
24/08/2014 REV5.4 released
[*]Synapse settings updated
[*]Updated toolchain arm-2010q1(202) from "code sourcery"
[*]GPU Overclocking thanks ZaneZam / DerTeufel / AndreiLux
GPU settings are:
Step0 54MHz = new Idle step = when in browser mode and no gaming this low GPU speed will help save power
Step1 266MHz
Step2 350MHz
Step3 533MHz = new speed foe step3 for better performance in drawing
Step4 700MHz = New OC speed for the better gaming performance
GPU settings are not editable and hard set in the kernel
[*]Corrected CPU freq going above scaling_max thanks to Yank555.lu
Source
XDA:DevDB Information
SphereKat, Kernel for the Samsung Galaxy Note 8.0
Contributors
civato
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: Rev2.0 first public
Stable Release Date: 2014-06-07
Current Beta Version: Rev1.4 non public re
Beta Release Date: 2014-06-05
Created 2014-06-07
Last Updated 2014-09-16
Thank You very much!!!
I will try this kernel in order do fix the spen accuracy.
Doing a nandroid backup and trying.
I´ll let you now my experience.
Martín
It is almost perfect!!!
MartinBM said:
Thank You very much!!!
I will try this kernel in order do fix the spen accuracy.
Doing a nandroid backup and trying.
I´ll let you now my experience.
Martín
Click to expand...
Click to collapse
S-pen alignment is fixed in the kernel and rom so you need both to have 100% accuracy.
This kernel will fix it for 95%. The other 5% is in the roms framework.
#########################################################
Note to all users:
Don't be a lurker, hit thanks as it took plenty of hours to build this.
Samsung didn't release the kernel source (not yet) so a lot of debugging was needed to fix problems like the sensors not reporting correctly.
This is the only thing I ask, hit thanks if this helps you.
It is free and enjoy it.
#########################################
Edit:
About the lurkers,
Martin from this post isn't one as he is a donator and thanks hitter.
A example to you all.
I wanted that cleared out as I didn't want Martin to take that lurker thing personal.
civato said:
S-pen alignment is fixed in the kernel and rom so you need both to have 100% accuracy.
This kernel will fix it for 95%. The other 5% is in the roms framework.
Note to all users:
Don't be a lurker, hit thanks as it took plenty of hours to build this.
Samsung didn't release the kernel source (not yet) so a lot of debugging was needed to fix problems like the sensors not reporting correctly.
This is the only thing I ask, hit thanks if this helps you.
It is free and enjoy it.
Click to expand...
Click to collapse
Much appreciated adding dock & boeffla support. You are a super dev.. will test and report and thanks.
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi. [emoji106]
Sent from my GT-N5110 using Tapatalk
androidmonsta said:
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi. [emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Damn... if only I had waited.
THANK YOU CIVATO!!! What is arch-power?
androidmonsta said:
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi.
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
Oh I didn't know that, well that is a good thing, I will add this in my OP.
civato said:
Oh I didn't know that, well that is a good thing, I will add this in my OP.
Click to expand...
Click to collapse
Yup, I'm running FLEXNOTE 1.3 with 4.2.2 bootloader using this kernel. Did a full wipe in Philz using the "I want to install new rom" option.
Sent from my GT-N5110 using Tapatalk
Rev2.1 released
08/Jun/2014 First Public release Rev2.1
[*]GPU step 5 included, now max it will go to 533MHz
[*]Auobrightness sensor fixes part2
[*]CPU sloop adjusted
zzmoove profile nr8.
GPU control is not possible , maybe later as the GPU driver is totally different then on JB.
androidmonsta said:
Just wanna say, this kernel supports Civato's FLEXNOTE rom WITHOUT kitkat bootloader and still get wifi. [emoji106]
Sent from my GT-N5110 using Tapatalk
Click to expand...
Click to collapse
I confirm. Wifi working great. Thanks
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Flashed and while it seems to be working fine for the most part, my CPU is constantly maxed out for some reason. I changed no settings or anything, and it was idling fine before flashing. I'm sure it might be something with my device, but I thought I'd put it out there just in case it's not. I'm going to mess around with some settings, see what I can do, and see if it changes.
ArobeeTV said:
Flashed and while it seems to be working fine for the most part, my CPU is constantly maxed out for some reason. I changed no settings or anything, and it was idling fine before flashing. I'm sure it might be something with my device, but I thought I'd put it out there just in case it's not. I'm going to mess around with some settings, see what I can do, and see if it changes.
Click to expand...
Click to collapse
Like you said, it could be something with your device, mine goes into deep sleep and it has gone as high as 90% deep sleep. Pretty amazing I would say and great job by @civato. Are you on pegasusq governor?
cbrinnny said:
Like you said, it could be something with your device, mine goes into deep sleep and it has gone as high as 90% deep sleep. Pretty amazing I would say and great job by @civato. Are you on pegasusq governor?
Click to expand...
Click to collapse
I was indeed using pegasusq. After trying multiple different governors and nothing changing (even stayed at 1600mhz on powersaving), I've decided to wipe my device entirely and start from scratch. No biggie. If I narrow it down to a specific app or device setting that was causing it, I'll post it so people are aware.
09/Jun/2014 First Public release Rev2.2
[*]Memory Leak fix cpu stats
[*]Memory Leak fix Kernel Ext4 & Power
zzmoove profile nr6.
I recommend not to use Powersave governor as is very buggy. Next release will it have removed as it useless.
Best governors are Pegasusq - Adaptive and zzmoove.
I am running it an am happy to report no issues. The only changes I made were to up my top cpu speed to 1.8gzh. All govs are at default. Thanks again. Can't wait to see what is next in the works for this tablet.
Sent from my GT-N5110 using XDA Premium HD app
Scores
With my rom & kernel
Benchmark scores:
Stock Normal Note8.0 Antutu Ranking. 17708 points
My Antutu = 23486 points
Stock Quadrant ranking = 6613 points
My Quadrant = 13685 points
Running with rom v1.3 and civz kitkat bootloader. Is data wipe needed? Sorry for the stupid question.
Sent from my GT-N5110 using XDA Premium 4 mobile app
slushbilly said:
Running with rom v1.3 and civz kitkat bootloader. Is data wipe needed? Sorry for the stupid question.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Not needed, me as a habit always wipe cache and dalvik.
Sent from my GT-N5110 using Tapatalk
Hi androidmonsta, How did you get Nandroid added under your Backup Settings? I assume it is part of the FLEXNOTE rom. What app does this link to?
rjamer said:
Hi androidmonsta, How did you get Nandroid added under your Backup Settings? I assume it is part of the FLEXNOTE rom. What app does this link to?
Click to expand...
Click to collapse
It comes from the rom. Its an backup app. Never use before LOL.
Sent from my GT-N5110 using Tapatalk
Custom kernel for Samsung Galaxy S III Mini
Click to expand...
Click to collapse
Features:
CPU OC, stable up to 1200 MHz(yanpol199's device) - thanks to @cocafe
GPU OC)/b] - thanks to @cocafe
- thanks to @cocafe
F2FS support
Abbamp - thanks to @cocafe
BLN - tnx @Meticulus
Sources:
GitHub
Click to expand...
Click to collapse
Download:
Yandex disk UPDATE 13.11.2014
Click to expand...
Click to collapse
I'm not an author of this kernel, I just helped yanpol199 with creating this project.
Probably, we'll developing this kernel together
Credits:
NovaFusion for base for this kernel
cocafe for kernel tweaks and improvements
yanpol199 for testing CPU OC and adjusting voltage
Click to expand...
Click to collapse
XDA:DevDB Information
CroPol kernel, Kernel for the Samsung Galaxy S III Mini
Contributors
ChronoMonochrome, znchnk, cocafe, yanpol199 (4pda.ru user)
Source Code: https://github.com/yanpol199/android_kernel_samsung_golden
Kernel Special Features: CPU/GPU OC/ABBamp/worked USB audio/BLN-blink
Version Information
Status: Stable
Current Stable Version: R1.1
Stable Release Date: 2014-11-13
Current Beta Version: v.0.5.3
Beta Release Date: 2014-10-01
Created 2014-09-28
Last Updated 2014-11-12
Reserved
Bug list:
-
Changelog:
Next version
- lz4 compression,
- changes in OC,
- update kernel to LK 3.2 by ChronoMonochrome.
v 0.4
- added GPU OC
- added Abbamp
28.09.2014
Initial build:
CPU OC support
Bug reports:
after experiencing a random reboot, type in terminal:
Code:
su
cat /proc/last_kmsg > /storage/sdcard0/last_kmsg.txt
report it in the thread and attach the last_kmsg.txt
Kernel Features
Kernel features
Since most of features this kernel were developed by @cocafe that means that FULL credits for this goes to him
( GPU OC )
GPU clock controller valued in /sys/kernel/mali
Available interfaces:
mali_auto_boost
mali_available_frequencies
mali_boost_delay
mali_boost_high
mali_boost_low
mali_dvfs_config
mali_gpu_clock
mali_gpu_fullspeed
mali_gpu_load
mali_gpu_vape
version
Click to expand...
Click to collapse
Check mali_dvfs_config first.
mali_auto_boost
Click to expand...
Click to collapse
It's a simple GPU governor that can boost clock according to GPU load, enabled by default
To disable: echo 0 > /sys/kernel/mali/mali_auto_boost
mali_boost_delay
Click to expand...
Click to collapse
The delay of boosting frequency, in ms.
echo ??? > /sys/kernel/mali/mali_boost_delay
mali_boost_high
Click to expand...
Click to collapse
The high frequency performance profile.
Upthreshold: When GPU load is higher than this value, GPU clock will increase.
DVFS idx: DVFS data index in mali_dvfs_config.
echo ??????(a frequency) > /sys/kernel/mali/mali_boost_high
echo idx=??(a DVFS index) > /sys/kernel/mali/mali_boost_high
echo threshold=??? > /sys/kernel/mali/mali_boost_high
mali_boost_low
Click to expand...
Click to collapse
The low frequency performance profile.
Downthreshold: When GPU load is lower than this value, GPU clock will decrease.
DVFS idx: DVFS data index in mali_dvfs_config.
echo ??????(a frequency) > /sys/kernel/mali/mali_boost_low
echo idx=??(a DVFS index) > /sys/kernel/mali/mali_boost_low
echo threshold=??? > /sys/kernel/mali/mali_boost_low
mali_gpu_clock
Click to expand...
Click to collapse
Current GPU clock.
Say a frequency to tweak the clock directly.
echo ?????? > mali_gpu_clock
Notice! If auto-booster governor is enabled, this GPU will override.
mali_gpu_fullspeed
Click to expand...
Click to collapse
Value 1 means GPU is working at full speed.
Value 0 means GPU is working at half speed.
When on half speed, GPU clock will be divided by 2. Namely, 399 / 2 = 199 kHz.
Require full speed:
echo 1 > mali_gpu_fullspeed
Required half speed:
echo 0 >mali_gpu_fullspeed
mali_gpu_load
Click to expand...
Click to collapse
GPU load (aka: utilization)
mali_gpu_vape
Click to expand...
Click to collapse
GPU voltage on full speed.
version
Click to expand...
Click to collapse
GPU OC driver version.
( LiveOPP - CPU OC/UC/OV/UV )
LiveOPP can control the properties of each cpufreq step.
LiveOPP values in /sys/kernel/liveopp
View all files in that folder first.
CPU freq table:
(Showed freq) : (Real freq)
200000 kHz : 192000 kHz
400000 kHz : 399360 kHz
600000 kHz : 599040 kHz
800000 kHz : 798720 kHz
1000000 kHz : 998400 kHz
1050000 kHz : 1049600 kHz
1100000 kHz : 1100800 kHz
1150000 kHz : 1152000 kHz
1200000 kHz : 1200000 kHz
1250000 kHz : 1228800 kHz
Click to expand...
Click to collapse
Overclocking depends on the device CPU quality you have.
You need to enable setting voltage in the slot first, if it is disabled:
echo set_volt=1 > arm_slot<id>
Click to expand...
Click to collapse
To decrease the voltage (UV) of a step: Example: @200MHz
echo varm- > arm_step0
Click to expand...
Click to collapse
To increase the voltage (OV) of a step: Example: @200MHz
echo varm+ > arm_step0
Click to expand...
Click to collapse
To change the voltage of a step:
echo varm=0x?? > arm_step<id>
Click to expand...
Click to collapse
* It means it accepts a HEX value only.
* ARM voltage is in 12.5mV steps
* Recommended that not tweaking Overclocking steps voltage
(Screen off CPU freq limits)
You can set min/max CPU freq. which will uses with screen off:
Code:
SYSFS=/sys/kernel/cpufreq/screenoff_cpufreq_limits
echo min=100000 > $SYSFS # 100 MHz
echo max=400000 > $SYSFS # 400 MHz
echo on > $SYSFS
F2FS support?
JynAlek said:
F2FS support?
Click to expand...
Click to collapse
Since this kernel based on NovaFusion sources, it supports F2FS.
ChronoMonochrome said:
Since this kernel based on NovaFusion sources, it supports F2FS.
Click to expand...
Click to collapse
I will install and test and see if it works well haha, thanks for sharing
Awesome, could you make oc kernel for stock also??
galaxy mini said:
Awesome, could you make oc kernel for stock also??
Click to expand...
Click to collapse
I'm not a main developer I do not own s3 mini, so I can't test it.
But is it does not work on stock?
ChronoMonochrome said:
I'm not a main developer I do not own s3 mini, so I can't test it.
But is it does not work on stock?
Click to expand...
Click to collapse
I'm been waiting for this for ages. Thank you guys, will try it and report back!
edit : with tenshi PA rom and ext4 as system file it doesn't boot. It is based on novafusion sources too.
Balino said:
I'm been waiting for this for ages. Thank you guys, will try it and report back!
edit : with tenshi PA rom and ext4 as system file it doesn't boot. It is based on novafusion sources too.
Click to expand...
Click to collapse
What about stock? I suppose it won't work huh?
Sent from my GT-I8190 using XDA Free mobile app
Mike20017 said:
What about stock? I suppose it won't work huh?
Sent from my GT-I8190 using XDA Free mobile app
Click to expand...
Click to collapse
if it is based on nf sources and doesn't boot on roms based on the same sources, I don't think it could work on stock
EDIT It is booting on golden_guy omni rom and not on roms based on nf sources , strange!
I tried , boot on vanir to, but bluetooth still not work cz its nf based,, and i dont know why fifa14 fc since used this kernel,,
In other work fine,fast and stabile...
Back to default vanir kernel
hardi7690 said:
but bluetooth still not work cz its nf based
Click to expand...
Click to collapse
Probably because there are no kernel modules. I'll tell it yanpol199
So I tested it on stock based Virginity V14, Nova Fusion's AOSPA and Omnirom of golden-guy. On virginity I had bootloop. On AOSPA everything seemed fine but at 1150 MHz maximum. On Omni I have problems with WiFi and Bluetooth. I hope I helped
Sent from my GT-I8190 using XDA Free mobile app
Thank you!
First of all, thank you so much for this! I've been waiting for this moment ever since I bought this phone
Installed on todays (29/09/2014) CM11 release. I set the min & max frequencies to both 1.1GHz (with ondemand as the governor and noop as the scheduler). I then ran a Antutu benchmark (v5.1).
The score? Oh, It was only this much ...
{
"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 have high hopes for this kernel to be a success!
If 1.1GHz has a good result at 12000, maybe you guys (the developers) can make 1.25GHz possible and then a new benchmark would surely result in around 13000 or maybe more than that?
Once again, thank you!
tested in on latest Vanir build
get reboot, reboot, reboot, ....
but it doesn´t matter, cause i´m happy with great blackhawk+ kernel from A-A
Sn0wdune said:
First of all, thank you so much for this! I've been waiting for this moment ever since I bought this phone
Installed on todays (29/09/2014) CM11 release. I set the min & max frequencies to both 1.1GHz (with ondemand as the governor and noop as the scheduler). I then ran a Antutu benchmark (v5.1).
The score? Oh, It was only this much ...
I have high hopes for this kernel to be a success!
If 1.1GHz has a good result at 12000, maybe you guys (the developers) can make 1.25GHz possible and then a new benchmark would surely result in around 13000 or maybe more than that?
Once again, thank you!
Click to expand...
Click to collapse
Works well on cm11?
vytorhugo said:
Works well on cm11?
Click to expand...
Click to collapse
Yes it does! But after installing apps like Facebook, Twitter, Skype or Snapchat, I did another benchmark and unfortunatley, the score went down to just 11045 /) which isn't bad at all for this device. Yes there is some lag as such but all in all, a good kernel!
Heres a screenshot of that benchmark incase anyone wants to see it
Few are able to remove up to GHz?
Berkant Ayhan Karabudak said:
Few are able to remove up to GHz?
Click to expand...
Click to collapse
English please lol?
It says in the OP that it supports up to 1150MHz. That's 1.15GHz. Setting 1.15GHz in No-frills CPU Control causes a freeze then a reboot for me but 1.1GHz works just fine so I don't know what's wrong. Hopefully, it'll be fixed in future updates! :good: